Method and system for processing user service and related equipment

Abstract

A method for processing a user service in a charging system: a charging trigger device (102) provides initial quota application mode indication information to a charging processing device (101) to indicate which mode of initial quota application is adopted by the charging trigger device (102) to the user service, and the charging processing device (101) performs charging processing on the user service based on the indication information, and issuing a charging processing result to the charging trigger device (102), so that the charging trigger device (102) changes the charging operation on the user service, thereby changing the matching relationship between the charging processing device (101) and the charging trigger device (102). The balance between the performance of the charging system and the credit control risk or between the access delay and the credit control risk is realized.

Description

[0001] This application is a divisional application. The application number of the original application is 202010251898.5, and the original application date is April 1, 2020. The entire contents of the original application are incorporated into this application by reference. Technical Field

[0002] The present application relates to the field of communications, and in particular to a method, system and related equipment for processing user services in a billing system. Background Art

[0003] According to the 3GPP (3rd Generation Partnership Project) standard specification, the Charging Trigger Function (CTF) device usually adopts the initial quota application in blocking mode for user services. Its characteristic is that the CTF device needs to apply for the quota before the user service starts. Although this helps to reduce credit control risks and reduce the possibility of losses for operators, it will not only increase the performance burden of the operator's billing system including CTF equipment and charging processing function (CHF) equipment, but also increase the access delay of user services, affecting the provision of delay-sensitive services, and thus affecting user experience.

[0004] The latency-sensitive services supported by 5G (5th Generation) networks, such as uRLLC (ultraHigh-Reliability and Low-Latency Communication) services, have high requirements for access latency. To this end, the 3GPP standard defines the initial quota application in non-blocking mode, which is characterized in that the CTF device applies for quota at the same time or after starting the user service, which is conducive to reducing the access latency of the user service.

[0005] 5G networks can support more and more user services. Among them, some services have extremely high network requirements. If the service is interrupted due to the network, it may cause serious consequences, such as: unmanned driving services, telemedicine services, industrial control services, etc. This application refers to such services as non-interruptible services; some services will not have serious consequences even if the service is interrupted due to network reasons, such as: VR (Virtual Reality) services, AR (Augment Reality) services, etc. This application refers to such services as interruptible services. For these two types of services, blindly adopting the initial quota application in non-blocking mode has the following problems: for non-interruptible services, the CTF device may find that the quota application has failed after the user service has started, and at this time the CTF device cannot arbitrarily interrupt the user service. The CTF device can only continue to allow the user service and allow it to consume the operator's network resources, which may cause losses to the operator; for interruptible services, the CTF device may also find that the quota acquisition has failed after the user service has started. Although the service can be interrupted at this time, this will affect the user experience on the one hand, and malicious users may use this mechanism to launch a DoS (Denial of Service) attack on the network on the other hand.

[0006] The current practice of unilaterally determining the blocking mode / non-blocking mode by the CTF device will result in the use of either the blocking mode or the non-blocking mode due to the lack of a large amount of supporting information required for quota granting. Blindly using the blocking mode for initial quota application will increase the performance burden of the billing system or increase the access delay of user services, while blindly using the non-blocking mode for initial quota application will affect user experience and even cause network security risks.

[0007] How to strike a balance between the performance burden of the billing system, the access latency requirements of user services, credit control risks and network security is a technical problem that needs to be solved urgently. Summary of the invention

[0008] In view of this, it is necessary to provide a method for processing user services in a billing system so as to process user services differently in different situations, including adjusting billing operations, controlling the on and off of user services, etc., to achieve a balance between the performance burden of the billing system, the access delay requirements of user services, credit control risks and network security.

[0009] In a first aspect, an embodiment of the present application provides a billing system, the billing system comprising a billing processing device (101) and a billing triggering device (102), wherein:

[0010] The charging trigger device (102) is used to: send initial quota application mode indication information to the charging processing device (101), wherein the initial quota application mode indication information indicates that the charging trigger device (102) adopts a first initial quota application mode for the user service when receiving a first start request for the user service;

[0011] The charging processing device (101) is used to: obtain the initial quota application mode indication information, and send a charging processing result to the charging trigger device (102), wherein the charging processing result is a result of charging the user service based on the initial quota application mode indication information;

[0012] The charging trigger device (102) is further used for processing the user service based on the charging processing result.

[0013] The billing system changes the coordination relationship between the billing trigger device and the billing processing device. On the one hand, the billing processing device can perform billing processing in combination with the initial quota application mode adopted by the billing trigger device for the user service, so that the billing processing process is more in line with the context and a more practical billing processing result can be obtained. On the other hand, the billing trigger device can process the user service according to the billing processing result that is more in line with the context. In this way, the billing processing device and the billing trigger device can work together to solve the problem currently caused by the unilateral adoption of the initial quota application mode by the CTF device.

[0014] In a possible solution, the billing trigger device (102) is further used to: adopt the first initial quota application mode for the user service when receiving the first start request, and send an initial billing request message for the user service to the billing processing device (101), wherein the initial billing request message includes the initial quota application mode indication information; the billing processing device (101) is further used to: obtain the initial quota application mode indication information from the initial billing request message.

[0015] In a possible solution, the billing processing device (101) is further used to send a billing processing result including any one of the following items to the billing trigger device (102): an indication parameter for instructing the billing trigger device (102) to suspend the quota management of the user service, or an indication parameter for instructing the billing trigger device (102) to interrupt the user service.

[0016] In a possible solution, the billing processing device (101) is also used to send a billing processing result including an indication parameter for instructing the billing trigger device (102) to suspend the quota management of the user service to the billing trigger device (102) when the first initial quota application mode is a non-blocking mode and it is determined that the billing trigger device (102) needs to suspend the quota management of the user service. The billing trigger device (102) is also used to suspend the quota management of the user service.

[0017] In a possible solution, the billing processing device (101) is further used to send a billing processing result to the billing trigger device (102), which includes an indication parameter for instructing the billing trigger device to adopt a second initial quota application mode for the user service when receiving a second start request for the user service, and the second start request occurs later than the first start request.

[0018] In a second aspect, an embodiment of the present application provides a method for processing user services, the method being applied to a charging processing device (101), the method comprising:

[0019] Acquiring initial quota application mode indication information of a user service, wherein the initial quota application mode indication information indicates that a charging trigger device (102) adopts a first initial quota application mode for the user service when receiving a first start request of the user service;

[0020] A billing processing result is sent to the billing trigger device (102), wherein the billing processing result is a result of billing processing on the user service based on the initial quota application mode indication information.

[0021] In a possible solution, the billing processing device (101) obtains the initial quota application mode indication information through an initial billing request message.

[0022] In a possible solution, the billing processing device (101) obtains the initial quota application mode indication information through a mid-term billing request message.

[0023] In a possible solution, the charging processing device (101) obtains the initial quota application mode indication information based on the charging policy sent by the policy control device, and the charging policy includes the initial quota application mode of the user service.

[0024] In a possible solution, the billing processing device (101) sends a billing processing result including any one of the following items through an initial billing response message of the user service:

[0025] an indication parameter for instructing the charging trigger device (102) to suspend the quota management of the user service, or

[0026] An indication parameter used to instruct the charging trigger device (102) to interrupt the user service.

[0027] In a possible solution, the billing processing device (101) sends a billing processing result including any one of the following via an interim billing response message of the user service or via a notification message:

[0028] an indication parameter for instructing the charging trigger device (102) to suspend the quota management of the user service, or

[0029] An indication parameter used to instruct the charging trigger device (102) to restore the quota management of the user service;

[0030] An indication parameter used to instruct the charging trigger device (102) to interrupt the user service.

[0031] In a possible solution, when the first initial quota application mode is a non-blocking mode, the billing processing result includes an indication parameter for instructing the billing trigger device (102) to suspend the quota management of the user service, and the billing processing of the user service based on the initial quota application mode indication information includes: authorization for the user service fails, and based on the initial quota application mode indication information, determining that the billing trigger device (102) needs to suspend the quota management of the user service.

[0032] In a possible solution, when the first initial quota application mode is a non-blocking mode and it is determined that the billing trigger device (102) needs to convert the user service (from online billing) to offline billing, a billing processing result including an indication parameter for instructing the billing trigger device (102) to convert the user service to offline billing is sent to the billing trigger device (102).

[0033] In a possible solution, when the first initial quota application mode is a non-blocking mode and it is determined that the billing trigger device (102) needs to adopt unlimited quota management for the user service, a billing processing result including an indication parameter for instructing the billing trigger device (102) to adopt unlimited quota management for the user service is sent to the billing trigger device (102).

[0034] In a possible solution, when the first initial quota application mode is a non-blocking mode and it is determined that the billing trigger device (102) needs to change the initial quota application for the user service to a blocking mode, a billing processing result including an indication parameter for instructing the billing trigger device (102) to adopt a blocking mode for the initial quota application for the user service is sent to the billing trigger device (102).

[0035] In a possible solution, when the first initial quota application mode is a non-blocking mode, and it is determined that the billing trigger device (102) needs to change the initial quota application for the user service to a blocking mode, and it is determined that the quota management of the user service by the billing trigger device (102) has been suspended, a billing processing result including the following contents is sent to the billing trigger device (102):

[0036] An indication parameter for instructing the charging trigger device (102) to apply an initial quota in a blocking mode for the user service;

[0037] An indication parameter used to instruct the charging trigger device (102) to resume quota management of the user service.

[0038] In a possible solution, the billing processing device (101) includes the granted quota in an interim billing response message corresponding to an interim billing request message that does not include quota application information, thereby instructing the billing triggering device (102) to resume quota management of the user service.

[0039] In a possible solution, when the first initial quota application mode is a non-blocking mode, the billing processing result includes an indication parameter for instructing the billing trigger device (102) to interrupt the user service, and the billing processing of the user service based on the initial quota application mode indication information includes: authorization for the user service fails, and determining that the billing processing device (101) needs to interrupt the user service based on the initial quota application mode indication information.

[0040] In a possible solution, the method further includes:

[0041] The quota-free usage of the user service is received from the charging trigger device (102).

[0042] In a possible solution, when the first initial quota application mode is a blocking mode and it is determined that the billing trigger device (102) needs to change the initial quota application for the user service to a non-blocking mode, a billing processing result including an indication parameter for instructing the billing trigger device (102) to adopt a non-blocking mode for the initial quota application for the user service is sent to the billing trigger device (102).

[0043] In a possible solution, when the first initial quota application mode is a blocking mode, and it is determined that the billing trigger device (102) needs to change the initial quota application for the user service to a non-blocking mode, and it is determined that the quota management of the user service by the billing trigger device (102) is not suspended or is proceeding normally, a billing processing result including the following contents is sent to the billing trigger device (102):

[0044] An indication parameter for instructing the charging trigger device (102) to apply for an initial quota in a non-blocking mode for the user service;

[0045] An indication parameter used to instruct the charging trigger device (102) to suspend the quota management of the user service.

[0046] In a possible solution, the billing processing result further includes an indication parameter for instructing the billing triggering device to adopt a second initial quota application mode for the user service when receiving a second start request for the user service, the second start request occurring later than the first start request.

[0047] In a possible solution, the first initial quota application mode is a non-blocking mode, and the second initial quota application mode is a blocking mode; or, the first initial quota application mode is a blocking mode, and the second initial quota application mode is a non-blocking mode.

[0048] In a possible solution, the billing process for the user service based on the initial quota application mode indication information is triggered by an initial billing request message of the user service, and the billing process result is sent to the billing trigger device (102) through a corresponding initial billing response message.

[0049] In a possible solution, the billing process for the user service based on the initial quota application mode indication information is triggered by a mid-term billing request message of the user service, and the billing process result is sent to the billing trigger device (102) through a corresponding mid-term billing response message.

[0050] In a possible solution, the billing process for the user service based on the initial quota application mode indication information is triggered by other billing request messages or account management messages, the other billing request messages are billing request messages for other user services, the other user services correspond to the same account as the user service, the account management message is a management message for the account corresponding to the user service, and the billing process result is sent to the billing trigger device (101) via a notification message.

[0051] In a possible solution, the billing processing device (101) further records or stores the initial quota application mode of the user service based on the initial quota application mode indication information.

[0052] In a third aspect, an embodiment of the present application provides a method for processing user services, which is applied to a charging trigger device (102), and the method includes:

[0053] Sending initial quota application mode indication information of the user service to the charging processing device (101), wherein the initial quota application mode indication information indicates that the charging triggering device (102) adopts a first initial quota application mode for the user service when receiving a first start request of the user service;

[0054] receiving a billing processing result of the user service from the billing processing device (101);

[0055] The user service is processed based on the charging processing result.

[0056] In a possible solution, the sending of the initial quota application mode indication information of the user service to the charging processing device (101) is specifically:

[0057] adopting the first initial quota application mode for the user service upon receiving the first start request;

[0058] The initial quota application mode indication information is sent to the charging processing device (101) via an initial charging request message.

[0059] In a possible solution, the charging trigger device (102) further sends the initial quota application mode indication information to the corresponding charging processing device (101) via a mid-term charging request message.

[0060] In a possible solution, the billing processing result includes any one of the following:

[0061] an indication parameter for instructing the charging trigger device (102) to suspend the quota management of the user service, or

[0062] The user instructs the charging trigger device (102) to restore the quota management parameter of the user service, or

[0063] An indication parameter used to instruct the charging trigger device (102) to interrupt the user service.

[0064] In a possible solution, the charging processing result includes an indication parameter for instructing the charging trigger device (102) to suspend the quota management of the user service, and the processing of the user service based on the charging processing result includes:

[0065] Suspend the quota management of the user service.

[0066] In a possible solution, the charging processing result includes an indication parameter for instructing the charging trigger device (102) to restore the quota management of the user service, and the processing of the user service based on the charging processing result includes:

[0067] Restore quota management for the user service.

[0068] In a possible solution, after the charging trigger device (102) sends an interim charging request message that does not include quota application information, the charging trigger device (102) receives the charging processing result from the charging processing device (101) through a response message corresponding to the interim charging request message, wherein the charging processing result includes the quota granted by the charging processing device (101) for the user service, and the interim charging response message processes the user service based on the charging processing result, including:

[0069] Restore quota management for the user service.

[0070] In a possible solution, the charging processing result includes an indication parameter for instructing the charging trigger device (102) to interrupt the user service, and the processing of the user service based on the charging processing result includes:

[0071] The user service is interrupted, and the quota-free usage of the user service is sent to the billing processing device (101).

[0072] In a possible solution, the charging processing result further includes an indication parameter for instructing the charging trigger device to adopt a second initial quota application mode for the user service when receiving a second start request for the user service, the second start request occurs later than the first start request, and the processing of the user service based on the charging processing result further includes:

[0073] The initial quota application mode of the user service is updated to the second initial quota application mode.

[0074] In a possible solution, the billing trigger device (102) receives the billing processing result through an initial billing response message of the user service; or receives the billing processing result through an interim billing response message of the user service; or receives the billing processing result through a notification message.

[0075] In a possible solution, the processing of the user service based on the charging processing result includes:

[0076] According to the charging processing result, the initial quota application mode of the user service is updated to a second initial quota application mode.

[0077] In one possible solution, the billing trigger device (102) updates the initial quota application mode of the user service to the second initial quota application mode based on an indication parameter in the billing processing result that is used to instruct the billing trigger device (102) to change the initial quota application mode of the user service to the second initial quota application mode.

[0078] In a possible solution, the charging trigger device (102) updates the initial quota application mode of the user service to the second initial quota application mode according to the information related to the granted quota in the charging processing result.

[0079] In a possible solution, updating the initial quota application mode of the user service to the second initial quota application mode includes:

[0080] Sending indication information to the policy control device (104) prohibiting the user service from using the first initial quota application mode; or,

[0081] Instruction information is sent to the policy control device (104) to instruct the initial quota application mode corresponding to the user service to be changed to the second initial quota application mode.

[0082] In a possible solution, the first initial quota application mode is a non-blocking mode, and the second initial quota application mode is a blocking mode; or, the first initial quota application mode is a blocking mode, and the second initial quota application mode is a non-blocking mode.

[0083] In a fourth aspect, an embodiment of the present application provides a billing processing device (101), comprising an acquisition module (701) and a sending module (702), wherein:

[0084] The acquisition module (701) is used to: acquire initial quota application mode indication information of a user service, wherein the initial quota application mode indication information indicates that the charging trigger device (102) adopts a first initial quota application mode for the user service when receiving a first start request of the user service;

[0085] The sending module (702) is used to send a billing processing result to the billing trigger device (102), wherein the billing processing result is a result of billing processing on the user service based on the initial quota application mode indication information.

[0086] In a possible solution, the acquisition module (701) is further used for:

[0087] Receiving an initial charging request message of the user service from the charging trigger device (102), wherein the initial charging request message includes the initial quota application mode indication information;

[0088] The initial quota application mode indication information is obtained from the initial charging request message.

[0089] In a possible solution, the sending module is further used for:

[0090] Generate any one of the following items based on the initial quota application mode indication information and include any one of the following items in the billing processing result:

[0091] an indication parameter for instructing the charging trigger device (102) to suspend the quota management of the user service, or

[0092] An indication parameter used to instruct the charging trigger device (102) to interrupt the user service.

[0093] In a possible solution, the sending module is further used for:

[0094] Based on the initial quota application mode indication information, an indication parameter is generated to instruct the billing trigger device to adopt a second initial quota application mode for the user service when receiving a second start request for the user service, and the indication parameter is included in the billing processing result, and the second start request occurs later than the first start request.

[0095] In a fifth aspect, an embodiment of the present application provides a charging trigger device (102), comprising a sending module (801), a receiving module (802) and a processing module (803), wherein:

[0096] The sending module (801) is used to: send initial quota application mode indication information of the user service to the charging processing device (101), wherein the initial quota application mode indication information indicates that the charging triggering device (102) adopts a first initial quota application mode for the user service when receiving a first start request of the user service;

[0097] The receiving module (802) is used to: receive the billing processing result of the user service from the billing processing device (101);

[0098] The processing module (803) is used to process the user service based on the billing processing result.

[0099] In a possible solution, the sending module is further used for:

[0100] adopting the first initial quota application mode for the user service upon receiving the first start request;

[0101] An initial charging request message of the user service is sent to the charging processing device (101), wherein the initial charging request message includes the initial quota application mode indication information.

[0102] In one possible solution, the receiving module (802) is further used to receive a billing processing result including an indication parameter for instructing the billing trigger device (102) to suspend the quota management of the user service from the billing processing device (101), and the processing module (803) is further used to suspend the quota management of the user service; or the receiving module (802) is further used to receive a billing processing result including an indication parameter for instructing the billing trigger device (102) to interrupt the user service from the billing processing device (101), and the processing module (803) is further used to interrupt the user service.

[0103] In a possible solution, the receiving module (802) is further used to receive from the billing processing device (101) a billing processing result including an indication parameter for instructing the billing trigger device to adopt a second initial quota application mode for the user service upon receiving a second start request for the user service, wherein the second start request occurs later than the first start request, and the processing module (803) is further used to update the initial quota application mode of the user service to the second initial quota application mode.

[0104] In a sixth aspect, an embodiment of the present application provides a billing processing device (101), comprising a processor and a memory, wherein:

[0105] The memory is used to store program instructions;

[0106] The processor is used to call and execute the program instructions stored in the memory, so that the billing processing device (101) executes the method for processing user services in the second aspect or any possible solution of the second aspect.

[0107] In the seventh aspect, an embodiment of the present application provides a computer-readable storage medium, comprising instructions, which, when executed on a computer, enables the computer to execute the method for processing user services in the second aspect or any possible scheme in the second aspect.

[0108] In an eighth aspect, an embodiment of the present application provides a charging trigger device (102), comprising a processor and a memory, wherein:

[0109] The memory is used to store program instructions;

[0110] The processor is used to call and execute the program instructions stored in the memory, so that the charging trigger device (102) executes the method for processing user services in the third aspect or any possible solution in the third aspect.

[0111] In the ninth aspect, an embodiment of the present application provides a computer-readable storage medium, comprising instructions, which, when executed on a computer, enables the computer to execute the method for processing user services in the third aspect or any possible scheme in the third aspect.

[0112] In a tenth aspect, an embodiment of the present application provides a method for processing user services, which is applied to a policy control device (104), and the method includes:

[0113] Sending initial quota application mode indication information of the user service to the charging trigger device (102), wherein the initial quota application mode indication information indicates that the charging trigger device (102) adopts a first initial quota application mode for the user service when receiving a first start request of the user service;

[0114] Receiving initial quota application mode indication information of the user service from the charging trigger device (102), the indication information being indication information prohibiting the use of the first initial quota application mode for the user service, or indication information indicating that the initial quota application mode corresponding to the user service is changed to a second initial quota application mode;

[0115] The initial quota application mode of the user service is updated to the second initial quota application mode based on the initial quota application mode indication information.

[0116] In an eleventh aspect, the present application provides an embodiment of a chip, which, when running, is used to implement the second aspect, the third aspect, any possible implementation scheme of the second aspect, or any possible implementation scheme of the third aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0117] Figure 1 A diagram of the billing system architecture provided for an embodiment of the present application;

[0118] Figure 2 A flow chart of a method for processing user services provided in an embodiment of the present application;

[0119] Figure 3A A flowchart of a first method for a charging processing device to process user services through an initial charging response message provided in an embodiment of the present application;

[0120] Figure 3B A flowchart of a first method for a billing processing device to process user services through an interim billing response message provided by an embodiment of the present application;

[0121] Figure 3C A flowchart of a second method for a charging processing device to process user services through an initial charging response message provided in an embodiment of the present application;

[0122] Figure 3D A flowchart of a second method for a billing processing device to process user services through an interim billing response message provided in an embodiment of the present application;

[0123] Figure 4A A flowchart of a first method for a billing processing device to process user services through a notification message provided in an embodiment of the present application;

[0124] Figure 4B A flowchart of a second method for a billing processing device to process user services through a notification message provided in an embodiment of the present application;

[0125] Figure 5A A flowchart of a first method for a charging trigger device to process user services based on a charging processing result provided in an embodiment of the present application;

[0126] Figure 5B A flowchart of a second method for a charging trigger device to process user services based on a quota grant result provided in an embodiment of the present application;

[0127] Figure 6 A schematic diagram of the hardware structure of a charging trigger device, a charging processing device or a policy control device provided in an embodiment of the present application;

[0128] Figure 7 A schematic diagram of the logical structure of the billing processing device provided in the embodiment of the present application;

[0129] Figure 8 A schematic diagram of the logical structure of a charging trigger device provided in an embodiment of the present application;

[0130] Fig. 9 A schematic diagram of the logical structure of a policy control device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0131] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Among them, in the description of the present application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship, for example, A / B can represent A or B; "and / or" in the present application is a kind of association relationship describing the associated objects, indicating that there can be three relationships, for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. And, in the description of the present application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same items or similar items with substantially the same functions and effects. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit the difference.

[0132] Figure 1 The billing system architecture diagram provided for the embodiment of the present application is used to control the billing trigger device to process user services, including a billing processing device 101, a billing trigger device 102 and a user device 103, and optionally, may also include a policy control device 104. The main functions of these devices are described as follows.

[0133] Billing processing device 101: with billing trigger device (including billing trigger device 102 and Figure 1For example, a connection with other billing trigger devices not shown is used to receive quota application information, usage information, etc. reported by the billing trigger device and perform billing processing on the user service accordingly. In addition, billing processing is performed according to the initial quota application mode of the user service reported by the billing trigger device, as well as according to relevant information of the user service, such as user type, customer information, account balance, service whitelist, service blacklist, account balance change trend, remaining validity period of the package, etc., and the billing processing result is sent to the billing trigger device so that the billing trigger device can adjust the billing operation on the user service.

[0134] The charging processing device 101 may be a CHF (Charging Function) device defined in the 3GPP standard specification, or may be a CCS (Converged Charging System) device defined in the 3GPP standard specification, which includes the functions of the CHF device.

[0135] It should be understood that in practical applications, Figure 1 The billing system shown can have more billing processing devices. For example, a cluster can be built, which includes multiple billing processing devices that back up each other, thereby improving disaster recovery capabilities and achieving high availability.

[0136] For the convenience of description, in the embodiments of the present application, the billing processing device is sometimes directly referred to as a CHF device.

[0137] The charging trigger device 102 is connected to the charging processing device 101, the policy control device 104 (if any) and the user equipment 103. The device can be used to:

[0138] (1) receiving a start request for a user service from the user equipment 103 (i.e., a request message for requesting the charging trigger device to start the user service), starting the user service according to the start request, and performing charging operations such as quota management and usage reporting on the user service;

[0139] (2) reporting to the billing processing device 101 the initial quota application mode adopted by itself for the user service, receiving the billing processing result from the billing processing device 101, and adjusting the billing operation for the user service accordingly, including adjusting the initial quota application mode adopted for the user service and / or adjusting the mid-term billing operation for the user service (such as suspending the quota management of the user service, interrupting the user service, etc.);

[0140] (3) deciding the initial quota application mode to be adopted for the user service according to the billing processing result (e.g., quota grant result) of the user service returned by the billing processing device 101;

[0141] (4) The initial quota application mode of the user service is stored in a local or external storage entity, or, if there is a policy control device 104, the relevant information of the initial quota application mode determined by itself or the billing processing device 101 is reported to the policy control device 104. In this way, the initial quota application mode of the user service can be shared among multiple billing trigger devices, which can reduce the synchronization and interaction between different billing trigger devices and reduce their own storage burden.

[0142] The billing trigger device 102 can be a CTF device defined in the 3GPP standard specification. When the user service is a 5G data connection service, the function of the billing trigger device 102 can be deployed in the SMF (Session Management Function) device defined in the 3GPP specification; when the user service is a voice service, the function of the billing trigger device 102 can be deployed in the AS (Application Server) or CSCF (call session control function) device in the IMS (IP Multimedia Sub-system). The embodiment of the present application does not limit the physical device where the function of the billing trigger device 102 is deployed.

[0143] It should be understood that in practical applications, Figure 1 The billing system shown can have more billing trigger devices, which can be connected to the same billing processing device (such as billing processing device 101) or to different billing processing devices. Multiple service start requests initiated by the same user device for the same user service may be processed by the same or different billing trigger devices.

[0144] For the convenience of description, the charging trigger device is sometimes referred to as a CTF device in the embodiments of the present application.

[0145] User equipment 103: and charging trigger device (charging trigger device 102 or Figure 1 The charging trigger device is connected to other charging trigger devices not shown in the figure, and is used to send a start request for user services to the charging trigger device, and access or use user services through the charging trigger device.

[0146] The user equipment 103 may be a user equipment (UE) defined by the 3GPP standard specification, and may be a wireless access device with wireless communication function or a wired access device without wireless communication function, including a handheld device, a vehicle-mounted device, a wearable device or a computing device; illustratively, it may be a mobile phone, a tablet computer or a computer with wireless transceiver function; the user equipment 103 may also be a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in a smart city, a wireless terminal in a smart home, etc.

[0147] It should be understood that in practical applications, Figure 1 The shown charging system may have more user equipments.

[0148] Policy control device 104: with charging trigger device (charging trigger device 102 or Figure 1 The charging trigger device is connected to other charging trigger devices not shown in the figure, and is used to provide the charging trigger device with a charging policy for the user service, and is also used to provide the charging trigger device with an initial quota application mode corresponding to a certain user service.

[0149] The policy control device 104 may be a Policy Control Function (PCF) device or a Policy and Charging Rules Function (PCRF) device defined in the 3GPP standard specification.

[0150] For the convenience of description, in the embodiments of the present application, the charging trigger device is sometimes directly referred to as a CTF device.

[0151] It should be noted that the “connected” or “connected” mentioned above includes direct connection or connection through one or more intermediate network devices.

[0152] Figure 1The billing system architecture shown can change the coordination relationship between the billing processing device and the billing trigger device, so that the billing trigger device can dynamically and on-demand adjust the billing operation of the user service, thereby realizing the use of the initial quota application in the non-blocking mode when the credit control risk of the user service is low, and the use of the initial quota application in the blocking mode when the credit control risk of the user service is high, and appropriately handling the use of the user service in the non-blocking mode, such as suspending the quota management of the user service or interrupting the user service, which can take into account the user service's demand for access delay and the operator's demand for system performance and credit risk control.

[0153] To facilitate understanding of the embodiments of the present application, some concepts are explained below.

[0154] User service refers to the user equipment 103 through the charging trigger device (charging trigger device 102 or Figure 1 Services accessed or used by the billing trigger device (not shown in the figure), including but not limited to:

[0155] (1) Data connection services, for example, one or more data streams corresponding to a certain rate group (RG) in a protocol data unit (PDU) session, or a data stream corresponding to a certain RG and a service identifier in a PDU session, can be understood as user services in the embodiments of the present application; in the embodiments of the present application, "user services in a PDU session" and "services in a PDU session" refer to multiple data streams corresponding to a certain RG in a PDU session, or may be a data stream corresponding to a service identifier in multiple data streams corresponding to a certain RG;

[0156] (2) IMS services;

[0157] (3) Capability opening business, etc.

[0158] For the convenience of description, in the embodiments of the present application, user services are sometimes referred to as "services".

[0159] Regarding the user services accessed or used by the user device 103, the embodiments of the present application will mainly illustrate the data connection services of the 5G network as an example; accordingly, regarding billing data, the embodiments of the present application will mainly illustrate the information related to data traffic as an example, and the information related to data traffic includes but is not limited to: information about PDU sessions collected by the billing trigger device, usage of released service units in the PDU session, billing trigger conditions, timestamps, etc.

[0160] Starting a user service means that the billing trigger device releases the user service after receiving a request to start the user service, including releasing the signaling or data of the user service. For example, when the user service is the above-mentioned data connection service, "starting the user service" includes allowing the establishment or update operation of the PDU session for the data connection service to continue (if the PDU session is not available) or releasing the service data flow (if the PDU session is already available).

[0161] Interrupting user services refers to the billing trigger device (billing trigger device 102 or Figure 1 The charging trigger device not shown in the figure) stops releasing the user service. For example, when the user service is the above-mentioned data connection service, "interrupting the user service" includes the operation of disconnecting the data flow corresponding to the user service.

[0162] Initial Quota Request Mode (IqrMod) refers to the billing trigger device (billing trigger device 102 or Figure 1 The mode in which a charging trigger device (not shown in the figure) applies for a quota for the user service for the first time after receiving a start request for the user service mainly reflects the time sequence relationship between the first application for a quota for the user service and the start of the user service after receiving the start request for the user service; according to whether the process of applying for the quota for the first time blocks the start operation of the user service, the initial quota application mode can be divided into a blocking mode and a non-blocking mode; therefore, the initial quota application is divided into "initial quota application in blocking mode" and "initial quota application in non-blocking mode", which are described as follows:

[0163] Blocking Mode Initial Quota Request (BIqr) refers to the billing trigger device (billing trigger device 102 or Figure 1 The charging trigger device (not shown) responds to the start request of the user service received from the user equipment 103, first applies for a quota for the user service from the charging processing device 101, and starts the user service only after receiving the quota granted by the charging processing device for the user service.

[0164] Non-Blocking Mode Initial Quota Request (NBIqr) refers to the billing trigger device (billing trigger device 102 or Figure 1The billing trigger device (not shown) responds to the start request of the user service received from the user equipment 103, and does not give priority to applying for a quota from the billing processing device 101 for the user service, but gives priority to starting the user service, or applies for a quota from the billing processing device 101 for the user service while starting the user service. That is to say, the operation of starting the user service does not depend on the quota granted by the billing processing device 101 for the user service. Although the billing trigger device has already released the user service when receiving the quota granted by the billing processing device 101 for the user service, in most scenarios, especially when the balance in the user account corresponding to the user service is sufficient, the billing trigger device can receive the quota granted by the billing processing device 101, and therefore can deduct the released service usage from the granted quota and report it to the billing processing device 101 through the service usage (Used Service Unit, USU) in the subsequent billing request message. However, the reliability of this mechanism is limited because the account information corresponding to the user's business changes dynamically. When the balance in the account is lower than a certain threshold, or the tariff package corresponding to the account changes, blindly applying for the initial quota in non-blocking mode may lead to serious credit control risks.

[0165] It can be seen from this that when the billing trigger device receives the indication information of the initial quota application of a certain mode that it has decided to adopt from the billing processing device 101, if the corresponding user service has started, the billing trigger device will apply the initial quota application of the mode to the user service only when it receives the next start request of the user service, instead of applying it immediately.

[0166] Initial quota request mode indication information (IqrModInd) is to indicate the billing trigger device (billing trigger device 102 or Figure 1 The charging trigger device (not shown in the figure) indicates which initial quota application mode (i.e., which of the above two modes) the user service has adopted when receiving the start request of the user service; the initial quota application mode indication information may only include the value of IqrMod, or may include the IqrMod field and its value, and may also include the SID (user service identifier) ​​field and its value. The embodiment of the present application does not limit the data structure of the initial quota application mode indication information.

[0167] The requirements for the initial quota application mode refer to the conditions that should be met by the attribute information of the user service, the account corresponding to the user service, etc. in order for the billing trigger device to adopt the initial quota application mode for the user service. For example, the requirements for the non-blocking mode may be "the user service is a delay-sensitive service, has been subscribed for more than 12 consecutive months, and the account balance exceeds 1,000 yuan", while the requirements for the blocking mode may be "the user service is a non-delay-sensitive service, and the account balance is less than 100 yuan". It should be understood that the requirements for the initial quota application mode are not limited to the requirements for the attribute information of the user service and the account corresponding to the user service, and can be configured in advance by the operator, or determined jointly by the operator and the user, and this is not limited in the embodiments of the present application.

[0168] Note that for the sake of convenience, in the embodiments of the present application, "adopting a certain initial quota application mode for a certain user service" is sometimes described as "adopting a certain mode of initial quota application for a certain user service".

[0169] The following further describes Figure 1 The billing system architecture shown in the figure can be implemented as an example of a method flow, such as Figure 2 , Figure 3A-3D , Figure 4A-4B and Figure 5A-Figure 5B As shown, the billing trigger device in the method flow corresponding to each figure corresponds to Figure 1 The billing trigger device 102 and the billing processing device in the Figure 1 The billing processing device 101 and the user equipment in the Figure 1 The user equipment 103 in the policy control device (if present) corresponds to Figure 1 The policy control device 104 in the following description of these method processes will not be repeated.

[0170] Figure 2 In the corresponding method flow, the charging trigger device changes the charging operation for the user service based on the charging processing result sent by the charging processing device. The method flow mainly includes the following steps:

[0171] Step 210: the charging triggering device sends the initial quota application mode indication information of the user service to the charging processing device, or the charging processing device obtains the initial quota application mode indication information.

[0172] Specifically, this step can be said to be that the charging trigger device sends the initial quota application mode indication information to the charging processing device, or it can be said that the charging processing device obtains the initial quota application mode indication information, which includes:

[0173] - the billing processing device directly reads the initial quota application mode indication information from a local storage facility, or reads the initial quota application mode of the user service from a local storage facility to indirectly obtain the initial quota application mode indication information; or

[0174] -determining the initial quota application mode indication information according to the configuration information of the user service; or

[0175] - receiving the initial quota application mode indication information from the charging trigger device.

[0176] The charging triggering device may send the initial quota application mode indication information to the charging processing device through an initial charging request message or a mid-term charging request message.

[0177] In the embodiment of the present application, the initial billing request message refers to the first billing request message of the user service sent by the billing trigger device to the billing processing device after receiving the start request of the user service, which is mainly used to apply for quota; for the convenience of description, in the embodiment of the present application, the initial billing request message of the user service is sometimes referred to as the initial billing request.

[0178] In the embodiment of the present application, the mid-term billing request message refers to the subsequent billing request message of the user service sent by the billing trigger device to the billing processing device after the initial billing request message of the user service is sent. It can be used to apply for quotas, to report usage, or to apply for quotas and to report usage. For the convenience of description, in the embodiment of the present application, the mid-term billing request message of the user service is sometimes referred to as the mid-term billing request.

[0179] Step 220: The billing processing device sends a billing processing result obtained by performing billing processing on the user service based on the initial quota application mode indication information to the billing triggering device.

[0180] Specifically, the billing processing device performs billing processing on the user service based on the initial quota application mode indication information, and sends the billing processing result obtained by the billing processing to the billing trigger device. Based on the initial quota application mode indication information, the billing processing device can know whether the current user service has started, and what mode of initial quota application mode the billing trigger device has adopted for the user service, so that in the billing processing process, it can further combine some attribute information of the user service, for example, the type of user service (such as interruptibility), to perform billing processing and generate corresponding billing processing results. The billing processing results include authorization results, indication parameters related to the initial quota application mode of the user service, etc., so that the billing trigger device can adjust the billing operation of the user service accordingly. Among them, the authorization result can be information on the granted quota, such as the amount of the granted quota, the reason for the failure to grant the quota, etc.

[0181] For example, when the initial quota application mode indication information indicates that the billing trigger device previously adopted the non-blocking mode (first initial quota application mode) for the initial quota application for the user service, on the one hand, if it is determined that the initial quota application mode of the user service needs to be changed to the blocking mode or the non-blocking mode initial quota application of the user service needs to be disabled, then the billing processing result includes an indication parameter "indicating that the billing trigger device adopts the second initial quota application mode (here, the blocking mode) for the user service upon receiving the next start request of the user service". Specifically, the indication parameter can be an indication parameter indicating disabling the non-blocking mode initial quota application, or an indication parameter indicating changing the initial quota application mode to the blocking mode, so that the billing trigger device adopts the blocking mode initial quota application upon receiving the next start request of the user service, thereby avoiding long-term credit control risks and network security risks (anti-DoS attacks); on the other hand, when determining the authorization When a failure occurs, the billing processing device may further determine that the user service needs to be interrupted (such as determining the interruptibility of the user service and determining that it is an interruptible service), and then include a billing operation control instruction of "interrupting the service" in the billing processing result. If it is determined that the quota management of the user service needs to be suspended (such as the user service is a non-interruptible service), then the billing processing result further includes a billing operation control instruction of "suspending quota management". Suspending quota management can be to convert the user service to offline billing or to use an unlimited quota (that is, the billing triggering device will not trigger a quota application due to the exhaustion of the quota). Although real-time credit control cannot be performed on the user service after suspending quota management, the billing information of the user service can still be collected as the basis for subsequent billing processing. By processing the billing of authorization failures based on the initial quota application mode indication information, appropriate processing measures can be taken for the user service, thereby avoiding credit control risks and network security risks.

[0182] For another example, when the initial quota application mode indication information indicates that the billing trigger device previously applied the initial quota application in the blocking mode for the user service (the first initial quota application mode), if it is determined that the initial quota application mode of the user service needs to be changed to the non-blocking mode or the non-blocking mode quota management of the user service needs to be restored (for example, when the quota is successfully granted, the billing processing device can further analyze the account information of the user service. If the account balance of the user service is sufficient), the billing processing result may include “instructing the billing trigger device to apply the first initial quota application mode to the user service when receiving the next start request of the user service”. Specifically, the indication parameter may be an indication parameter indicating that the initial quota application mode is changed to the non-blocking mode, or, if the initial quota application mode of the user service is configured as the non-blocking mode by default, and the non-blocking mode has been disabled by the billing processing device before, then the indication parameter may be an indication parameter for restoring the non-blocking initial quota application mode configured by default for the user service, so that the billing triggering device can adopt the initial quota application in the non-blocking mode for the user service when receiving the next start request of the user service, so as to reduce the access delay of the user service. In this case, the billing processing device may also include an indication parameter of "suspending quota management" (meaning that no quota management or restriction is performed on the user service before the end of the user service, unless the "restore quota management" indication parameter sent by the billing processing device is received again) in the billing processing result, so as to reduce complex credit control and improve system efficiency during the use of this service.

[0183] The billing processing device may also not include explicit indication parameters in the billing processing results, but, for example, by changing the number of granted quotas so that the quotas granted multiple times show an upward trend or a downward trend, thereby "implying" the billing triggering device to adjust the initial quota application mode adopted for the user service.

[0184] For more examples, see the subsequent embodiments of this application.

[0185] Step 230: The charging triggering device processes the user service based on the charging processing result.

[0186] Specifically, the charging triggering device receives the charging processing result from the charging processing device, and then processes the user service according to the charging processing result.

[0187] Specifically, if the billing processing result contains an indication parameter of "interrupting user service", the user service is interrupted, and optionally, the previously recorded quota-free usage is reported to the billing processing device; if the billing processing result contains an indication parameter of "suspending quota management", the quota management of the user service is suspended, for example, the user service may be converted to offline billing or to unlimited quota management (that is, the billing trigger device will not trigger a quota application due to the exhaustion of the quota); if the billing processing result contains an indication parameter of "indicating that the billing trigger device shall suspend the quota management upon receipt of the next opening of the user service", the quota management of the user service is suspended, for example, the user service may be converted to offline billing or to unlimited quota management (that is, the billing trigger device shall not trigger a quota application due to the exhaustion of the quota); If the billing processing result does not contain the indication parameter of "instructing the billing trigger device to adopt the second initial quota application mode for the user service when receiving the next start request for the user service", the billing trigger device may further determine whether to change the initial quota application mode of the user service based on the authorization result contained in the billing processing result (such as the reason for the failure to grant the quota, or the amount of granted quota that is much lower than the requested amount, etc.).

[0188] Specifically, the billing trigger device can also further determine whether to change the initial quota application mode of the user service based on the quota grant information contained in the multiple billing processing results. For example, when it is known that the quota grants were successful multiple times before, and the current initial quota application mode is the blocking mode, the billing trigger device can determine that the initial quota application for the user service should be changed to the non-blocking mode when the next start request of the user service is received; for another example, if the number of quotas granted multiple times before shows a downward trend, and the current initial quota application mode is the non-blocking mode, it can be determined that the initial quota application for the user service should be changed to the blocking mode when the next start request of the user service is received.

[0189] For more examples, see the subsequent embodiments of this application.

[0190] Above Figure 2 The corresponding method flow enables the billing processing device to perform billing processing on the user service based on the initial quota application mode adopted by the billing trigger device for the user service, and issue the corresponding billing processing results so that the billing trigger device processes the user service (mainly changing the billing operation on the user service), which helps to balance the relationship between the terminal user's demand for access delay and the operator's demand for system performance and credit risk control in real time and dynamically.

[0191] Regarding the above Figure 2 For the corresponding method flow, please refer to the embodiment of this application. Figure 3A-3D , Figure 4A-4B and Figure 5A-Figure 5B The corresponding method flow.

[0192] Figure 3A-3D A flow chart of a method for a billing processing device to process user services through a billing response message provided in an embodiment of the present application is provided. These method flows are described separately below.

[0193] Figure 3A In the corresponding method flow, the billing trigger device first applies an initial quota to the user service in a non-blocking mode (first mode), and then the billing processing device sends a billing control instruction through an initial billing response message, so that the billing trigger device adjusts the billing operation, for example, suspends the quota management of the user service, interrupts the user service, and changes the initial quota application to a blocking mode (second mode) for the user service. The method flow mainly includes the following steps:

[0194] Step 301: The charging triggering device receives the start request StartReq31 of the user service.

[0195] Specifically, the charging triggering device receives StartReq31 from the user equipment.

[0196] Taking the user service as a 5G data service as an example, StartReq31 can be a request message for establishing a PDU session for the data service, or, when the PDU session has been established, it can be an initial data packet in the data flow of the data service.

[0197] Step 302: The charging trigger device obtains the initial quota application mode IqrMod (=NB) of the user service.

[0198] Specifically, the billing trigger device can obtain the initial quota application mode of the user service based on the configuration information of the user service saved in a local or external storage facility, and can also obtain the initial quota application mode of the user service from the policy issued by the policy control device (for example, the initial quota application mode of the user service is obtained from the billing policy of the user service activated by the policy control device; or if there is no currently activated billing policy for the user service, the policy control device is requested for the billing policy of the user service, and the policy control device returns the initial quota application mode of the user service as the billing policy of the user service to the billing trigger device, and the billing trigger device obtains the initial quota application mode of the user service therefrom).

[0199] This method process assumes that the initial quota application mode IqrMod adopted for the user service is a non-blocking mode (NB).

[0200] Step 303: The charging triggering device starts the user service and records the non-quota usage NQUSU.

[0201] Since the initial quota application mode of the user service is a non-blocking mode, the billing trigger device can start the user service immediately without waiting for the result of the quota application in the subsequent steps; in addition, the billing trigger device starts to record the quota-free usage NQUSU. The quota-free usage refers to the service usage formed by the billing trigger device releasing the user service without the valid quota granted by the billing processing device for the user service. Taking the 5G data service as an example, its quota-free usage refers to the data traffic formed by the billing trigger device releasing the 5G data service without the valid quota granted by the billing processing device for the 5G data service.

[0202] Step 304: the charging triggering device sends an initial charging request for the user service to the charging processing device, which includes quota application information RSU31 and initial quota application mode indication information IqrModInd31.

[0203] Specifically, in order to apply for quota from the billing processing device to maintain the release of the user service, the billing triggering device sends the initial billing request message to the billing processing device, which includes quota application information RSU31 and initial quota application mode indication information IqrModInd31, IqrModInd31 includes the initial quota application mode IqrMod (=NB) of the user service.

[0204] Quotas can be shared between different user services (for example, if a user service is a data stream corresponding to a service identifier among multiple data streams corresponding to a certain RG, then multiple user services corresponding to the same rate group share the quota of the rate group), or user services can have exclusive quotas (for example, if a user service is multiple data streams corresponding to a certain rate group, then the user service exclusively enjoys the quota of the rate group). The data structures of the billing request messages and the initial quota application mode indication information therein corresponding to these two situations are exemplified below.

[0205] (1) User service exclusive quota (for example: user service is multiple data flows corresponding to a certain rate group), the charging trigger device can report the initial quota application mode in units of rate groups (the subsequent charging processing device will also manage the initial quota application mode in units of rate groups), then the exemplary charging request message is:

[0206]

[0207] Note: MUU is the abbreviation of Multiple Unit Usage, RG is the abbreviation of Rating Group, and RSU is the abbreviation of Requested Service Unit, the same below.

[0208] (2) Quotas are shared between different user services (e.g., if a user service is a data flow corresponding to a service identifier among multiple data flows corresponding to a certain rate group, then multiple user services corresponding to the same rate group share the quota of the rate group), as follows:

[0209] Assume that there are two user services: user service Service1 and user service Service2 share a quota, that is, Service1 is the data flow corresponding to Service ID=1 in rate group RG1, and Service2 is the data flow corresponding to Service ID=2 in RG1. The billing trigger device determines that the IqrMod of Service1 is in blocking mode and the IqrMod of Service2 is in non-blocking mode.

[0210] When the billing trigger device receives the start request of Service2, if the billing trigger device already has a quota corresponding to the rate group (assuming that Service1 has started, the quota corresponding to the rate group is granted to Service1), the billing trigger device directly uses the quota corresponding to the rate group for Service2. In this case, the billing trigger device does not adopt the non-blocking mode for Service2, and then does not report the initial quota application mode indication information adopted by Service2 to the billing processing device, or the reported initial quota application mode adopted by Service2 is the blocking mode.

[0211] When the billing trigger device receives the start request of Service2, if there is no quota corresponding to the rate group on the billing trigger device, the billing trigger device applies for the initial quota in non-blocking mode for Service2. At this time, the initial billing request message sent to the billing processing device carries the indication information of "Service2 applies for the initial quota in non-blocking mode". Specifically, there are two methods for reporting the initial quota application mode:

[0212] (2-1): The charging trigger device reports the initial quota application mode based on user services (the subsequent charging processing device can also manage the initial quota application mode based on user services). The exemplary charging request message is:

[0213]

[0214]

[0215] (2-2): The charging trigger device can report the initial quota application mode in units of rate groups (the subsequent charging processing device can also manage the initial quota application mode in units of rate groups), and the exemplary charging request message is:

[0216]

[0217] It should be understood that step 303 is not dependent on step 304 , that is, step 304 can be executed after, before, or simultaneously with step 303 .

[0218] The billing processing device receives and parses the above initial billing request, obtains RSU31 and IqrModInd31 from it, and based on the situation indicated by IqrModInd31 (i.e., the billing trigger device applies for the initial quota in non-blocking mode for the user service), performs billing processing on the user service, generates the current stage charging control command (Current Stage Charging Control Command, CurCmd) and / or the next stage charging control command (Next Stage Charging Control Command, NxtCmd), and sends it to the billing trigger device for execution. The current stage charging control command and the next stage charging control command are explained as follows:

[0219] In the embodiment of the present application, the current period charging control instruction refers to the indication parameter or instruction provided to the charging trigger device for the current period user service execution, and the next period charging control instruction refers to the indication parameter or instruction provided to the charging trigger device for the next period user service; wherein, the current period user service refers to the user service for which the quota is currently applied or the quota is being consumed, for example: assuming that a user service corresponds to a service data flow of a rate group in the 5G data service, then before the termination event (Termination of service data flow) of the service data flow occurs, the user service is called "the current period user service"; and the next period user service is relative to the current period user service, and refers to the same user service that starts after the current time point, for example: assuming that a user service corresponds to a service data flow of a rate group in the data service, which is currently being released, and the start event (Start of service dataflow) of the service data flow of the user service after the current time point occurs, then the started service data flow is called "the next period user service". Considering that user services can be executed concurrently, the current period user service and the next period user service may coexist in a certain time period.

[0220] The above process of generating the current period billing control instruction and the next period billing control instruction is exemplified as follows.

[0221] Example 3A-1

[0222] Step 305-1: The billing processing device grants the quota GSU31, determines the initial quota application for switching to the blocking mode, generates the next-period billing control instruction NxtCmd31=ToB for the user service, and saves the initial quota application mode for the user service.

[0223] Specifically, the billing processing device grants a quota GSU31 for the user service based on RSU31; the billing processing device determines whether it is necessary to change the initial quota application mode of the user service based on IqrModInd31, and generates NxtCmd31 when it is determined that the billing trigger device needs to use the initial quota application in the blocking mode; an exemplary value of NxtCmd31 is "ToB" (To Blocking Mode) to indicate that the billing trigger device (billing trigger device 102 or Figure 1 When the billing trigger device (not shown in the figure) receives the next start request of the user service (such as the start request StartReq32), it adopts the initial quota application in blocking mode for the user service; optionally, the billing processing device can also record or save the current initial quota application mode of the user service based on IqrModInd31 or NxtCmd31, so as to serve as the input for determining whether the initial quota application mode of the user service needs to be modified next time. Optionally, the billing processing device may also determine that the billing trigger device needs to use the initial quota application in blocking mode instead based on IqrModInd31, and then generate NxtCmd31.

[0224] For example, the billing processing device learns based on IqrModInd31 that the current billing trigger device has adopted a non-blocking mode for the initial quota application for the user service, and when it is determined that the user account no longer meets the requirements for the initial quota application in the non-blocking mode (for example, it no longer meets the condition that "the remaining validity period of the package in the account is greater than a certain threshold", or that "the rate of decrease in the account balance exceeds a certain threshold", etc.), thereby forming a credit control risk, it is determined that the billing trigger device needs to change the initial quota application mode to a blocking mode for the user service, and then generates NxtCmd31.

[0225] For another example, when the billing processing device determines that the user account no longer meets the requirements of the initial quota application in the non-blocking mode, no matter what mode of initial quota application the current billing triggering device adopts for the user service, it can directly generate NxtCmd31.

[0226] It should be understood that the representation of the NxtCmd instruction in the embodiment of the present application is exemplary rather than limiting. In addition to the above representation, other representations may also be used. For example, "enable NB" may be used to indicate an initial quota application in a non-blocking mode, while "disable NB" may be used to indicate an initial quota application in a blocking mode.

[0227] Specifically, in order to enable the billing processing device to know the initial quota application mode adopted by the billing triggering device for the user without reporting the initial quota application mode in the intermediate billing request, the billing processing device can further record or save the currently effective initial quota application mode in this billing context: if NxtCmd31 has not been issued before, then the initial quota application mode IqrMod of the user service is recorded or saved based on IqrModInd31; if the billing processing device updates the initial quota application mode, then the updated initial quota application mode is recorded or saved (for example, if NxtCmd31=ToB, then the quota application mode of the user service should be recorded or saved as a blocking mode). It should be understood that the above-mentioned step of generating NxtCmd31 is optional, and there is a corresponding "?" mark in the method flow chart. Conversely, if an action in the flow chart is suffixed with a "?" mark, it means that the action is an optional action; this representation method is applicable to all embodiments of the present application and will not be repeated.

[0228] Step 306-1: The charging processing device sends an initial charging response message to the charging triggering device, which includes GSU31 and NxtCmd31.

[0229] The initial charging response message is a response message corresponding to the initial charging request message. For the convenience of description, in the embodiments of the present application, the initial charging response message is sometimes referred to as the initial charging response, which will not be described in detail later.

[0230] NxtCmd31 is optional and has a corresponding "?" mark in the method flow chart; conversely, if a message field in the method flow chart is suffixed with a "?" mark, it means that the message field is optional; this representation method is also applicable to all embodiments of the present application and will not be repeated here.

[0231] It should be understood that step 305-1 of recording or saving the initial quota application mode of the user service may also be performed after the initial charging response message is successfully sent in this step.

[0232] Depending on whether quotas are shared between different user services, the data structure of the charging response message and NxtCmd therein are exemplified as follows (following the example of step 304).

[0233] (1) For a user service exclusive quota, the billing processing device can manage the initial quota application mode in units of rate groups. The exemplary billing response message is:

[0234]

[0235] Note: MUI is the abbreviation of Multiple Unit Information; GSU is the abbreviation of Granted Service Unit.

[0236] (2) Quotas are shared between different user services. There are two methods for reporting the initial quota application mode corresponding to step 304 (based on Service 1 and Service 2 in step 304):

[0237] (2-1): The billing processing device can manage the initial quota application mode based on user services. The exemplary billing response message is:

[0238]

[0239]

[0240] (2-2) The billing processing device can also manage the initial quota application mode based on rate groups:

[0241] Example 1: The charging trigger device is made to adopt blocking mode (or prohibit the use of non-blocking mode) for all user services in the entire rate group. The exemplary charging response message is:

[0242]

[0243] Assuming that some user services in the rate group (such as the user service of Service1 in the step 304 example) have been adopted in blocking mode before, then the response message (NxtCmd31) is equivalent to only being effective for user services that previously adopted non-blocking mode (such as the user service of Service2 in the step 304 example).

[0244] Example 2: If the non-blocking mode of Service2 has been disabled by the billing processing device, the billing triggering device determines to restore the original initial quota application mode of the Service2 user service (i.e., the non-blocking mode is used during the recovery period), and the exemplary billing response message is:

[0245]

[0246] Assuming that some user services in the rate group (such as the user service with ServiceID 1 in the step 304 example) have previously adopted the blocking mode, then the response message (NxtCmd31 in it) is equivalent to only being effective for the user services that previously adopted the non-blocking mode (such as the user services with ServiceID 2 in the step 304 example).

[0247] Step 307-1: The charging trigger device monitors the usage of GSU31 (taking NQUSU as the used amount), and updates the initial quota application mode of the user service based on NxtCmd31.

[0248] Specifically, the charging trigger device receives and parses the initial charging response message of step 306-1, obtains GSU31 and NxtCmd31 (if any) therefrom, and monitors the use of GSU31. At this time, the recorded quota-free usage NQUSU of the user service is used as the used amount of the quota GSU31.

[0249] Specifically, the billing trigger device updates the initial quota application mode of the user service based on NxtCmd31: obtains a new initial quota application mode of the user service based on the NxtCmd31 parameters, and corresponding to step 302, saves the initial quota application mode to the configuration information of the user service saved in a local or external storage facility, wherein the initial quota application mode saved in the external storage facility can be shared by multiple billing trigger devices. For data services, after updating the initial quota application mode in the locally effective billing policy of the user service, a policy update request is further sent to the policy control device, and the policy update request includes indication information for updating the initial quota application mode of the user service; or, instead of updating the initial quota application mode in the locally effective billing policy of the user service, a policy update request is directly sent to the policy control device, and the update request includes indication information for updating the initial quota application mode of the user service. Afterwards, the policy control device sends a new billing policy for the user service in a response message to the policy update request, and the new billing policy includes the updated initial quota application mode of the user service. The indication information may be prohibiting the use of a non-blocking mode for the user service, or indicating the use of a blocking mode for the user service. The embodiment of the present application does not limit the data structure and storage location of the initial quota application mode stored in the billing trigger device. For example, it may be placed in the data structure of the configuration data of the user service:

[0250] ServiceProfile{

[0251] "userID":"+8613800000000"

[0252] "SID":"1" / / User service identifier

[0253] … / / Other configuration parameters of this user service

[0254] "IqrModInd"

[0255] "IqrMod":"B" / / The initial quota application mode of the user service is blocking mode

[0256] }

[0257] }

[0258] Go to step 308.

[0259] Example 3A-2

[0260] Step 305-2: The billing processing device fails to authorize, and determines that the billing triggering device needs to suspend quota management / switch to the initial quota application in blocking mode, generates CurCmd32=HngQm / NxtCmd32=ToB, and saves the initial quota application mode of the user service.

[0261] Specifically, when the billing processing device fails to authorize the user service, it determines that the billing trigger device should suspend the quota management of the user service, and generates the current period billing control instruction CurCmd32 for suspending the quota management, and the example value is "HngQm" (Hang up quota management); optionally, the billing processing device can also determine that the billing trigger device should change the initial quota application for the user service to a blocking mode, and then generates the next period billing control instruction NxtCmd32, and the example value is "ToB". Optionally, the billing processing device can also update the initial quota application mode of the user service based on NxtCmd32. Among them, the authorization failure includes: insufficient balance, batch pricing failure, not allowing access to the user service, etc., resulting in authorization failure. In the embodiment of the present application, the authorization failure is mainly taken as an example of the failure to grant quota, which will not be repeated later.

[0262] The following is an example of generating CurCmd32.

[0263] For example, after the quota grant fails, the billing processing device further determines that the billing trigger device needs to suspend the quota management of the user service according to the configuration information of the user service (such as the type of the user service is an uninterruptible service, or the user contract agreement indicates that the user service is uninterruptible), and then generates the current period billing control instruction CurCmd32 with a value of "HngQm". The optional CurCmd32 may also include indication information of the quota grant failure, such as "Fail".

[0264] In actual deployment, the above-mentioned suspended quota management can be implemented by converting the user service from online billing to offline billing, which is equivalent to no quota management. The billing trigger device can convert the user service to offline billing based on the indication of CurCmd32; the above-mentioned suspended quota management can also be implemented by converting the user service from conventional quota management to unlimited quota management. The billing trigger device can, based on the indication of CurCmd32, set no quota for the user service or use a sufficiently large quota, and record the usage of the sufficiently large quota.

[0265] The above conventional quota management means that the billing processing device allocates quotas to user services based on the user account balance, and the billing triggering device releases user services according to the quota granted by the billing processing device, and triggers the sending of a billing request for applying for a quota to the billing processing device due to the exhaustion of the quota.

[0266] The so-called unlimited quota management refers to the suspended quota indication (such as "HngQm" above) issued by the billing processing device. Based on the indication, the billing triggering device will not limit the quota usage of the user's business (it will not trigger the quota application due to the quota being used up) and record the quota usage.

[0267] Regarding the above-mentioned suspended quota management, if the billing trigger device and the billing processing device have both realized the transition to offline billing (no quota management) and realized unlimited quota management, the billing processing device and the billing trigger device are faced with two choices. The above-mentioned "HngQm" indication parameter can be replaced by "ToOff" (To Offline Charging, switch to offline billing) or "ToNLQM" (To No Litmited Quota Management, switch to unlimited quota management) to distinguish them.

[0268] Regarding the generation of the next-period billing control instruction NxtCmd32, please refer to the relevant description in step 305-1.

[0269] Regarding recording or saving the initial quota application mode of the user service, reference may be made to the relevant description in step 305 - 1 .

[0270] Step 306-2: The charging processing device sends an initial charging response message to the charging triggering device, which includes CurCmd32 and NxtCmd32.

[0271] Among them, NxtCmd32 is optional, and the billing processing device can send an indication parameter in a subsequent mid-term billing response message to change the initial quota application mode of the user service to the blocking mode. For details, refer to the relevant description in step 306-1.

[0272] Step 307-2: The billing triggering device suspends quota management and updates the initial quota application mode of the user service based on NxtCmd32.

[0273] Specifically, the charging trigger device receives and parses the initial charging response message in step 306-2, obtains CurCmd32 and NxtCmd32 (if any), and suspends the quota management of the user service according to CurCmd32, specifically, converts the user service to offline charging (equivalent to no quota management) or performs unlimited quota management on the user service. The previously recorded no quota usage of the user service will be reported as USU to the charging processing device for charging processing.

[0274] Similarly, the charging trigger device also updates the initial quota application mode of the user service based on NxtCmd32, and specifically refers to the relevant description in step 307-1.

[0275] Then go to step 308.

[0276] Example 3A-3

[0277] Step 305-3: The billing processing device fails to authorize and determines that the user service needs to be interrupted / the initial quota application in blocking mode needs to be used instead, generates CurCmd33=Fail / NxtCmd33=ToB, and saves the initial quota application mode of the user service.

[0278] This step is similar to step 305-2, except that after the authorization fails, the billing processing device further determines that the billing trigger device should interrupt the user service (for example, the type of the user service is an interruptible service, or the user contract agreement indicates that the user service is an interruptible service), such as entertainment services such as VR services, and generates the current period billing control instruction CurCmd33=Fail.

[0279] It should be understood that the representation method of the CurCmd instruction for interrupting user services in the embodiment of the present application is exemplary rather than limiting. In addition to the above representation method, other representation methods can also be used. For example, a specific result code can also be used to indicate that the billing trigger device interrupts the user service.

[0280] Regarding the initial quota application mode for saving the user service, please refer to the relevant description in step 305-1. Step 306-3: The charging processing device sends an initial charging response message to the charging triggering device, which includes CurCmd33 and NxtCmd33.

[0281] This step is similar to step 306 - 2 and will not be described in detail.

[0282] Step 307-3: The charging triggering device interrupts the user service, reports NQUSU, and updates the initial quota application mode of the user service based on NxtCmd33.

[0283] The initial quota application mode for updating the user service based on NxtCmd33 is similar to step 307 - 1 .

[0284] Specifically, the charging triggering device interrupts the user service according to the "Fail" indication information in CurCmd33, and optionally further reports the non-quota usage NQUSU recorded so far.

[0285] Since the billing processing device instructs to interrupt the user service, the process will directly proceed to step 308 after this step to terminate the user service.

[0286] It should be understood that in this step, the order between interrupting the user service and updating the initial quota application mode of the user service is not fixed.

[0287] Step 308: The user service ends.

[0288] Specifically, the end of the user service may be triggered by the user, or authorization failure, etc.

[0289] Step 309: The charging triggering device receives the start request StartReq32 of the user service.

[0290] Specifically, the charging triggering device receives StartReq32 from the user equipment.

[0291] The device that receives the next start request of the user service may be the billing trigger device in steps 301-308, or it may be another billing trigger device, so the billing trigger device in step 309 may be the same billing trigger device as steps 301-308, or it may be a different billing trigger device.

[0292] Step 310: The charging triggering device obtains the initial quota application mode IqrMod (=B) of the user service.

[0293] This step is similar to step 302 and will not be described in detail. This step enables the charging trigger device to learn that an initial quota application in blocking mode should be applied for the user service, so that it is determined that a quota should be applied first and then the user service should be started.

[0294] Step 311: the charging triggering device sends an initial charging request message of the user service to the charging processing device, which includes quota application information RSU32 and initial quota application mode indication information IqrModInd32.

[0295] Specifically, according to the blocking mode (IqrMod=B) of the initial quota application mode of the user service, it is determined that the quota should be obtained first, and assuming that the charging trigger device does not have the quota available for the user service, the initial charging request message is sent first to apply for the quota. The initial quota application includes quota application information RSU32 and initial quota application mode indication information IqrModInd32, wherein IqrModInd32 is similar to IqrModInd31 in step 304.

[0296] Step 312: The billing processing device grants the quota GSU32.

[0297] Specifically, the billing processing device receives and parses the initial billing request message in step 311, obtains the quota application information RSU32 and the initial quota application mode indication information IqrModInd32 therefrom, grants the quota GSU32 for the user service, and records or saves the current initial quota application mode of the user service based on IqrModInd32 as an input for determining whether the initial quota application mode of the user service needs to be modified next time; for the process of granting the quota GSU32 and recording or saving the current initial quota application mode of the user service based on IqrModInd32, refer to the relevant description in step 305-1.

[0298] Step 313: The charging processing device sends an initial charging response to the charging triggering device, which includes the granted quota GSU32.

[0299] Step 314: The charging trigger device starts the user service based on GSU32.

[0300] In the above steps 309-314, the initial quota application mode of the user service may also be changed. For details, see Figure 3C Steps 341-346 of the present invention may also change the initial quota application mode of the user service after step 314, for details, see Figure 3D Steps 367-370.

[0301] In the process of the above steps 301 to 303, the user service is started before the quota is applied for, so this is the initial quota application process in the non-blocking mode; in the process of steps 309 to 314, the user service is started after the quota is applied for, so this is the initial quota application process in the blocking mode; the changes before and after are caused by the billing control instructions issued by the billing processing device.

[0302] Above Figure 3AThe corresponding method flow enables the billing processing device to determine whether the current user service has started according to the initial quota application mode adopted when authorization fails, and then determine the appropriate processing measures (such as instructing the billing trigger device to suspend quota management or interrupt user service, etc.) to handle the current user service, thereby preventing the current user service risk caused by the billing system operation. At the same time, when a credit control risk is found, the method flow also enables the billing processing device to promptly change the initial quota application mode adopted by the billing trigger device for the user service from non-blocking mode to blocking mode, which can prevent the poor user experience of the next user service from being immediately interrupted from the beginning, and can also prevent the billing system from being attacked by DOS.

[0303] Considering that user service related information (such as account balance, etc.) changes dynamically, the billing processing device cannot always evaluate the credit control risk when processing the initial billing request message, but is more likely to evaluate it after the user service starts as the user service related information changes to a certain extent. For this reason, the embodiment of the present application provides Figure 3B The corresponding method flow.

[0304] Figure 3B In the corresponding method flow, the billing trigger device first applies for an initial quota in a non-blocking mode (first mode) for the user service, and then the billing processing device sends a billing control instruction through a mid-term billing response message, so that the billing trigger device adjusts the billing operation, for example: suspending / resuming quota management, interrupting the user service, changing the user service to an initial quota application in a blocking mode (second mode), etc. The method flow mainly includes the following steps:

[0305] Step 321: The charging triggering device receives the start request StartReq33 of the user service.

[0306] The content of this step may refer to step 301 .

[0307] Step 322: Obtain the initial quota application mode IqrMod (=NB) of the user service.

[0308] The content of this step may refer to step 302 .

[0309] Step 323: The charging triggering device starts the user service and records the non-quota usage NQUSU.

[0310] The content of this step may refer to step 303 .

[0311] Step 324: the charging triggering device sends an initial charging request to the charging processing device, including quota application information RSU33 and initial quota application mode indication information IqrModInd33.

[0312] The content of this step may refer to step 304 .

[0313] Step 325: The billing processing device grants quota GSU33 and saves the current initial quota application mode of the user service based on IqrModInd33.

[0314] The content of this step can refer to step 305-1, the difference is that step 305-1 determines that the initial quota application mode of the user service needs to be changed, while this step determines that the initial quota application mode of the user service does not need to be changed (for example, the reason is: no credit control risk is found). Step 326: The billing processing device sends an initial billing response to the billing triggering device, including GSU33.

[0315] Step 327: The charging trigger device monitors the usage of GSU 33 (NQUSU as the used amount).

[0316] Specifically, the charging trigger device receives and parses the initial charging response message in step 326, obtains GSU33 therefrom, manages the use of GSU33, and at this time, uses the recorded quota-free usage NQUSU of the user service as the used amount of quota GSU31.

[0317] Thereafter, the charging trigger device requests charging processing from the charging processing device through a mid-term charging request. The mid-term charging request may include quota application information RSU and may also include usage USU, as shown in steps 328-1 and 328-4, respectively.

[0318] Step 328-1: the charging triggering device sends a mid-term charging request to the charging processing device, which includes quota application information RSU34 and initial quota application mode indication information IqrModInd33.

[0319] Specifically, in order to apply for a quota from the billing processing device to maintain the unblocking of the user service, the billing trigger device sends the mid-term billing request message to the billing processing device, including quota application information RSU34 and initial quota application mode indication information IqrModInd33, and IqrModInd33 is optional. When the mid-term billing request does not include IqrModInd33, the billing processing device determines the initial quota application mode of the non-blocking mode previously adopted by the billing trigger device for the user service based on the current initial quota application mode of the user service saved in step 325.

[0320] After receiving the mid-term billing request in step 328-1, different billing processes are performed according to the account information of the user service and the different information of the user service, as shown below.

[0321] Example 3B-1

[0322] Step 329-1: The billing processing device grants quota GSU34, determines to switch to blocking mode, generates NxtCmd34=ToB, and saves IqrMod.

[0323] Among them, generating NxtCmd34 is optional; the content of this step can refer to step 305-1.

[0324] Step 330 - 1 : The charging processing device sends an interim charging response to the charging triggering device, which includes GSU 34 and NxtCmd 34 .

[0325] This step is similar to step 306 - 1 , except that the initial charging response message is replaced by the mid-term charging response message. For other details, please refer to step 306 - 1 .

[0326] Step 331 - 1 : The charging trigger device monitors the use of GSU 34 and updates the initial quota application mode of the user service based on NxtCmd 34 .

[0327] This step is similar to step 307 - 1 , except that since there was no quota-free usage before, this step does not need to deduct the quota-free usage in GSU34.

[0328] Go to step 332.

[0329] Example 3B-2

[0330] Step 329-2: The billing processing device fails to authorize the user service, determines that the quota management of the user service needs to be suspended / the initial quota application in blocking mode needs to be switched, generates CurCmd35=HngQm / NxtCmd35=ToB, and saves IqrMod.

[0331] The content of this step may refer to step 305-2.

[0332] Step 330 - 2 : The charging processing device sends an interim charging response to the charging triggering device, which includes CurCmd35 and NxtCmd35.

[0333] This step is similar to step 306 - 2 , except that the initial charging response message is replaced by the mid-term charging response message. For other details, please refer to step 306 - 2 .

[0334] Step 331 - 2: The billing triggering device suspends quota management and updates the initial quota application mode of the user service based on NxtCmd35.

[0335] The content of this step may refer to step 307 - 2 .

[0336] Go to step 332.

[0337] Example 3B-3

[0338] Step 329-3: The billing processing device fails to authorize the user service and determines that the user service needs to be interrupted / the initial quota application in blocking mode needs to be used instead, generates CurCmd36=Fail / NxtCmd36=ToB, and saves IqrMod.

[0339] The content of this step may refer to step 305-3.

[0340] Step 330 - 3 : The charging processing device sends an interim charging response to the charging triggering device, including CurCmd36 and NxtCmd36.

[0341] This step is similar to step 306 - 3 , except that the initial charging response message is replaced by the mid-term charging response message. For other details, please refer to step 306 - 3 .

[0342] Step 331 - 3: The charging triggering device interrupts the user service and updates the initial quota application mode of the user service based on NxtCmd36.

[0343] The content of this step may refer to step 307 - 3 .

[0344] Go to step 333.

[0345] Example 3B-4

[0346] Step 328-4: The charging triggering device sends a mid-term charging request to the charging processing device, which includes usage information USU34 and initial quota application mode indication information IqrModInd33.

[0347] Specifically, in order to report usage information to the billing and charging processing device for billing processing, the billing trigger device sends a mid-term billing request message to the billing processing device, which includes usage information USU34; in order to enable the billing processing device to know the initial quota application mode of the user service, the mid-term billing request may also include initial quota application mode indication information IqrModInd33, that is, IqrModInd33 is optional. The content of IqrModInd33 can refer to IqrModInd31 in step 304. When IqrModInd33 is not included in the mid-term billing request, the billing processing device determines the initial quota application in non-blocking mode for the user service by the billing trigger device according to the current initial quota application mode of the user service saved in step 325.

[0348] After receiving the mid-term billing request in step 328-2, the billing process is exemplified as follows based on the account information of the user service and the information of the user service.

[0349] Step 329-4: The billing processing device determines that it is necessary to switch to the initial quota application in blocking mode / restore the quota management of the user service, generate NxtCmd37=ToB / CurCmd37=RsmQm; and save IqrMod.

[0350] Specifically, the billing processing device receives and parses the mid-term billing request described in step 328-4, obtains the usage information USU34 and the initial quota application mode indication information IqrModInd33 (if such field is provided), deducts the account balance based on USU34 or writes USU34 into the call bill, and determines whether the initial quota application mode of the user service needs to be changed based on IqrModInd33. For the specific judgment method, please refer to step 305-1. In the case of determining that the initial quota application mode of the user service needs to be changed to the blocking mode, the billing processing device can further determine that the quota management of the user service has been suspended (such as switching to offline billing, whether the quota management of the user service is currently suspended is recorded in the billing processing device), and then it can be further determined that the quota management needs to be restored. At this time, a quota can be granted for the user service: although there is USU but no RSU in the mid-term billing request message, that is, there is no quota request information, the billing processing device determines the granted quota amount GSU34X according to the configuration information or billing policy, and / or generates the current billing control instruction CurCmd37 with a value of "RsmQm" (Resume Quota Management) to instruct the billing trigger device to immediately resume the quota management of the user service. In order to restore the quota management of the user service, the billing processing device can send any one or both of CurCmd37 and GSU34X: if only CurCmd37 is sent, then the billing trigger device can send a billing request message to the billing processing device to apply for a quota for the user service after receiving the indication parameter; if only GSU34X is sent, it is equivalent to indicating to the billing trigger device through GSU34X that the quota management of the user service needs to be restored, so that the billing trigger device can use the granted quota GSU34X for the user service and continue to send a billing request message to the billing processing device to apply for a quota for the user service.

[0351] For information on how to determine that the initial quota application in non-blocking mode can no longer be used, please refer to Figure 3AThe factors for the billing processing device to determine that the quota management of the user service needs to be restored may include: determining that the initial quota application mode of the user service needs to be changed to a blocking mode, and further determining that there is currently a credit control risk.

[0352] In this way, the credit control risk of the user business in this period can be reduced by restoring the quota management, and the credit control risk of the user business in the next period can be reduced by changing the initial quota application mode of the user business to the blocking mode.

[0353] It should be understood that the representation method of the CurCmd instruction for restoring quota management in the embodiment of the present application is exemplary rather than limiting. In addition to the above method, other methods can also be used. For example, "enable QM" can be used to instruct the billing trigger device to restore quota management, and "disable QM" can be used to instruct the billing trigger device to suspend quota management.

[0354] For the process of recording or saving the initial quota application mode IqrMod of the user service by the billing processing device, please refer to Figure 3A Corresponding to the relevant description in the method flow, such as steps 305-1, 305-2, etc.

[0355] Step 330 - 4 : The billing processing device sends an interim billing response to the billing triggering device, which includes CurCmd37, GSU34X and NxtCmd37.

[0356] The content of this step can refer to the description of step 330-3, and whether the optional parameters are carried specifically refers to the description of the generated parameters in step 329-4.

[0357] Step 331 - 4: The billing trigger device resumes quota management and updates the initial quota application mode of the user service based on NxtCmd37.

[0358] Specifically, the charging triggering device receives and parses the interim charging response described in step 330-4, and performs the following operations:

[0359] If there is only GSU34X in the charging response (but no CurCmd37=RsmQm, etc.), the quota management of the user service is restored, and GSU34X is used for the user service (the user service is released based on GSU34X); or

[0360] If CurCmd37=RsmQm (but not GSU34X) is included in the charging response, the quota management of the user service is restored, and a charging request message for applying for a quota is sent to the charging processing device;

[0361] If the charging response includes CurCmd37=RsmQm and GSU34X, the quota management of the user service is restored according to CurCmd37=RsmQm, and GSU34X is used for the user service (the user service is released based on GSU34X);

[0362] Regarding the process of updating the initial quota application mode of the user service based on NxtCmd37, reference may be made to the description of step 307-1.

[0363] Step 332: The user service ends.

[0364] The content of this step may refer to step 308 .

[0365] Step 333: The charging triggering device receives the start request StartReq34 of the user service.

[0366] The content of this step may refer to step 309 .

[0367] Step 334: The charging triggering device obtains IqrMod (=B) of the user service.

[0368] The content of this step may refer to step 310 .

[0369] Step 335: the charging triggering device sends an initial charging request to the charging processing device, which includes quota application information RSU35 and initial quota application mode indication information IqrModInd34.

[0370] The content of this step may refer to step 311 .

[0371] Step 336: The billing processing device grants quota GSU35 and saves IqrMod.

[0372] The content of this step may refer to step 312 .

[0373] Step 337: The charging processing device sends an initial charging response to the charging triggering device, which includes the granted quota GSU35.

[0374] The content of this step may refer to step 313 .

[0375] Step 338: The charging trigger device starts the user service based on GSU35.

[0376] The content of this step may refer to step 314 .

[0377] In the above steps 333-338, the initial quota application mode of the user service may also be changed. For details, see Figure 3CSteps 341-346 of the present invention may also change the initial quota application mode of the user service after step 338. For details, see Figure 3D Steps 367-370.

[0378] Relative to Figure 3A The corresponding method flow, above Figure 3B The corresponding method flow enables the billing processing device to have more decision-making opportunities and balance the needs of credit risk control and access delay in a more timely manner (without having to wait until the user service starts again).

[0379] Above Figure 3A and Figure 3B The corresponding method flow can be used in the scenario where the existing initial quota application mode of the billing trigger device is a non-blocking mode. For the scenario where the existing initial quota application mode of the billing trigger device is a blocking mode, the embodiment of the present application provides Figure 3C and Figure 3D The corresponding method flow.

[0380] Figure 3C In the corresponding method flow, the billing trigger device firstly applies for the initial quota in the blocking mode (first mode) for the user service, and then the billing processing device sends a billing control instruction through an initial billing response message, so that the billing trigger device adjusts the billing operation, for example, suspends quota management and changes the initial quota application to the non-blocking mode (second mode) for the user service. The method flow mainly includes the following steps:

[0381] Step 341: The charging triggering device receives the start request StartReq35 of the user service.

[0382] The content of this step may refer to step 301 .

[0383] Step 342: The charging trigger device obtains the initial quota application mode IqrMod (= B) of the user service

[0384] The content of this step may refer to step 302, except that the initial quota application mode of the user service obtained in this step is a blocking mode.

[0385] Step 343: the charging triggering device sends an initial charging request to the charging processing device, which includes quota application information RSU36 and initial quota application mode indication information IqrModInd35.

[0386] Since the initial quota application mode is the blocking mode, the charging trigger device first applies for a quota from the charging processing device before starting the user service. Specifically, the charging trigger device sends the initial charging request to the charging processing device, which includes quota application information RSU36 and initial quota application mode indication information IqrModInd35. For the content of IqrModInd35, refer to IqrModInd31 in step 304.

[0387] The billing processing device receives and parses the above-mentioned initial billing request, and based on the situation indicated by IqrModInd35 (i.e., the initial quota application of the billing trigger device in blocking mode for the user service), performs billing processing on the user service, generates the current period billing control instruction CurCmd and / or the next period billing control instruction NxtCmd, and sends it to the billing trigger device for execution.

[0388] Step 344: The billing processing device grants quota GSU36, determines that non-blocking mode / suspended quota management should be used instead, generates NxtCmd38=ToNB / CurCmd38=HngQm, and saves IqrMod.

[0389] Specifically, the billing processing device determines, based on the situation indicated by IqrModInd35 and when it is determined that the requirements of the non-blocking mode are met, that the initial quota application for the user service to adopt the non-blocking mode should be changed, and then generates NxtCmd38. Optionally, it is also possible not to be based on the situation indicated by IqrModInd35, but when it is determined that the requirements of the non-blocking mode are met, to determine that the initial quota application for the user service to adopt the non-blocking mode, and then generate NxtCmd38. Optionally, when the requirements of the non-blocking mode are met, the billing processing device may also suspend the current quota management of the user service (because the satisfaction of the requirements of the non-blocking mode means that the current credit control risk is low), and then generate CurCmd38. If it is determined that the quota management is suspended, no quota is granted for the user service.

[0390] For example, the billing processing device learns that the current billing trigger device has adopted a blocking mode initial quota application for the user service, and when it is determined that the user account meets the requirements for the non-blocking mode initial quota application (for example, the condition of "the remaining validity period of the package in the account is greater than a certain threshold", or the condition of "the rate of decrease of the account balance is lower than a certain threshold", etc.), thereby confirming that the credit control risk is low, it is determined that the billing trigger device needs to change the initial quota application mode for the user service to a non-blocking mode, and then generates NxtCmd38.

[0391] For another example, the billing processing device may also directly generate NxtCmd38 upon determining that the user account meets the requirements of the non-blocking mode, regardless of the initial quota application mode adopted by the current billing triggering device for the user service.

[0392] The value of NxtCmd38 is "ToNB" (To Non-Blocking Mode) to instruct the charging trigger device to apply for an initial quota in non-blocking mode for the user service when it receives a start request for the user service again.

[0393] Optionally, the billing processing device can perform billing processing on the user service based on the situation indicated by IqrModInd35, including granting a quota GSU36 for RSU36, and determining in the quota granting process that the credit control risk of the user service is low and there is no need to perform online credit control on the user service of this period, and then generate CurCmd38 with a value of "HngQm" to instruct the billing triggering device to suspend the quota management of the user service of this period. This can timely reduce the performance burden of the billing processing device and the billing triggering device to a certain extent, after all, it can reduce the number of information interactions between the two.

[0394] Regarding the process of recording or saving the currently effective initial quota application mode of the user service, reference may be made to the relevant description in step 305 - 1 .

[0395] Step 345: The charging processing device sends an initial charging response message to the charging triggering device, which includes GSU36, CurCmd38 and NxtCmd38.

[0396] Among them, GSU36 and CurCmd38 are both optional.

[0397] Step 346: The charging trigger device starts the user service based on GSU36, suspends quota management, and updates the initial quota application mode of the user service based on NxtCmd38.

[0398] Specifically, the charging trigger device receives and parses the initial charging response message described in step 345-1, and obtains GSU36 (if any), CurCmd38 (if any), and NxtCmd38 therefrom. If the response message carries GSU36, the user service is started and quota management is performed based on GSU36; if the response message carries CurCmd38 but does not carry GSU36, the quota management of the user service is suspended according to CurCmd38; for the charging trigger device updating the initial quota application mode of the user service based on NxtCmd38, refer to the relevant description in step 307-1.

[0399] Step 347: The user service ends.

[0400] The content of this step may refer to step 308 .

[0401] Step 348: The charging triggering device receives the start request StartReq36 of the user service.

[0402] The content of this step may refer to step 321 .

[0403] Step 349: The charging trigger device obtains the initial quota application mode IqrMod (=NB) of the user service.

[0404] The content of this step may refer to step 322 .

[0405] Step 350: The charging triggering device starts the user service and records the non-quota usage NQUSU.

[0406] The content of this step may refer to step 323 .

[0407] Step 351: the charging triggering device sends an initial charging request to the charging processing device, which includes quota application information RSU37 and initial quota application mode indication information IqrModInd36.

[0408] The content of this step may refer to step 324 .

[0409] Step 352: The billing processing device grants quota GSU37 and saves IqrMod.

[0410] The content of this step may refer to step 325 .

[0411] Step 353: The charging processing device sends an initial charging response message to the charging triggering device, which includes the granted quota GSU37.

[0412] The content of this step may refer to step 326 .

[0413] Step 354: The billing triggering device monitors the usage of GSU 37 (deducting NQUSU first).

[0414] The content of this step may refer to step 327 .

[0415] In the above steps 348-354, the initial quota application mode of the user service may also be changed. For details, see Figure 3A Steps 301-307 of the present invention may also change the initial quota application mode of the user service after step 354. For details, see Figure 3B Steps 328-332.

[0416] In the process of the above steps 341 to 346-1 and 346-2, the user service starts after applying for the quota, so it is the initial quota application in the blocking mode. In steps 348 to 354, the user service starts before applying for the quota, which is the initial quota application in the non-blocking mode. The changes before and after are caused by the billing control instructions issued by the billing processing device.

[0417] Above Figure 3C The corresponding method flow enables the billing processing device to promptly adjust the initial quota application mode of the user service from a blocking mode to a non-blocking mode, which is conducive to timely meeting the access delay requirements of delay-sensitive services; on this basis, the method flow also enables the billing processing device to suspend quota management in a timely manner to reduce the communication interaction and data processing between the billing trigger device and the billing processing device, thereby further reducing the performance burden of the billing trigger device and the billing processing device.

[0418] Figure 3D In the corresponding method flow, the billing trigger device first applies an initial quota in a blocking mode (first mode) to the user service, and then the billing processing device sends a billing control instruction through a mid-term billing response message, so that the billing trigger device adjusts the billing operation, for example, suspends quota management, and changes the initial quota application to a non-blocking mode (second mode) for the user service. The method flow mainly includes the following steps:

[0419] Step 361: The charging trigger device receives the user service start request StartReq37.

[0420] The content of this step may refer to step 309 .

[0421] Step 362: The charging trigger device obtains the initial quota application mode IqrMod (=B) of the user service.

[0422] The content of this step may refer to step 310 .

[0423] Step 363: The charging triggering device sends an initial charging request message to the charging processing device, which includes quota application information RSU38 and initial quota application mode indication information IqrModInd37.

[0424] The content of this step may refer to step 311 .

[0425] Step 364: The billing processing device grants the quota GSU 38 and saves the initial quota application mode of the user service.

[0426] Specifically, the billing processing device grants the corresponding quota GSU38 according to RSU38, and records or saves the initial quota application mode of the user service based on IqrModInd37. For details, please refer to the relevant descriptions in steps 305-1 and 305-2.

[0427] Step 365: The billing processing device sends an initial billing response message to the billing triggering device, including the GSU 38 .

[0428] The content of this step may refer to step 313 .

[0429] Step 366: The charging trigger device starts the user service based on GSU38.

[0430] The content of this step may refer to step 314 .

[0431] At this point, the user service has started, and the charging trigger device can continue to apply for a quota from the charging processing device to maintain the release of the user service, as shown in the following steps.

[0432] Step 367: the charging triggering device sends a mid-term charging request to the charging processing device, which includes quota application information RSU39 and initial quota application mode indication information IqrModInd37, where IqrModInd37 is optional.

[0433] When the interim charging request does not include IqrModInd37, the charging processing device can determine the initial quota application of the charging trigger device in the blocking mode for the user service according to the initial quota application mode recorded or saved in step 364.

[0434] The billing processing device receives and parses the mid-term billing request, obtains the quota application information RSU39 and the initial quota application mode indication information IqrModInd37 therefrom, and then performs billing processing.

[0435] Step 368: The billing processing device grants the quota GSU39, generates CurCmd3a=HngQm / NxtCmd3a=ToNB, and saves IqrMod.

[0436] The content of this step may refer to step 344 .

[0437] Step 369: The charging processing device sends an interim charging response to the charging triggering device, including GSU39, CurCmd3a and NxtCmd3a.

[0438] This step is similar to step 345. Except for replacing the initial billing response of step 345 with an interim billing response, the rest of the steps can refer to step 345.

[0439] Step 370: The charging triggering device continues the user service, suspends the quota management of the user service, and updates the initial quota application mode of the user service based on NxtCmd3a.

[0440] Specifically, the billing trigger device receives and parses the mid-term billing response message described in step 369, obtains GSU39 (if any), CurCmd3a and NxtCmd3a therefrom, and if the response message carries GSU39, monitors the use of the granted quota GSU39 by the user service; if the response message carries CurCmd3a=HngQm but does not carry GSU39, suspends the quota management of the user service (such as switching to offline billing); the billing trigger device updates the initial quota application mode of the user service based on NxtCmd3a=ToNB, so as to adopt a non-blocking mode initial quota application for the user service when the billing trigger device receives the next start request of the user service.

[0441] Step 371: User service ends.

[0442] The content of this step may refer to step 308 .

[0443] Step 372: The charging triggering device receives the start request StartReq38 of the user service.

[0444] The content of this step may refer to step 321 .

[0445] Step 373: The charging trigger device obtains the initial quota application mode IqrMod (=NB) of the user service.

[0446] The content of this step may refer to step 322 .

[0447] Step 374: The charging triggering device starts the user service and records the non-quota usage NQUSU.

[0448] The content of this step may refer to step 323 .

[0449] Step 375: the charging triggering device sends an initial charging request to the charging processing device, which includes quota application information RSU3a and initial quota application mode indication information IqrModInd38.

[0450] The content of this step may refer to step 324 .

[0451] Step 376: The billing processing device grants quota GSU3a and saves IqrMod.

[0452] The content of this step may refer to step 325 .

[0453] Step 377: The charging processing device sends an initial charging response message to the charging triggering device, which includes the granted quota GSU3a.

[0454] The content of this step may refer to step 326 .

[0455] Step 378: The charging trigger device monitors the usage of GSU3a (deducts NQUSU first).

[0456] The content of this step may refer to step 327 .

[0457] In the above steps 372-378, the initial quota application mode of the user service may also be changed. For details, see Figure 3A Steps 301-307 of the present invention may also change the initial quota application mode of the user service after step 378. For details, see Figure 3B Steps 328-S332.

[0458] Relative to Figure 3C The corresponding method flow, above Figure 3D The corresponding method flow enables the billing processing device to have more decision-making opportunities and balance the needs of credit control, resource utilization and access delay in a more timely manner.

[0459] Above Figure 3A-3D The corresponding method processes are all to obtain the account balance, account status, account usage trend and other information of the user service through the billing process of the user service itself, and send the billing control instruction accordingly. But in fact, when multiple user services correspond to the same user account (for example, a user has subscribed to multiple user services from an operator), this information can also be obtained through the billing process of "brother services" (or "other services", which refers to services corresponding to the same account as the user service), and can even be obtained through management messages of the corresponding accounts of the user services (such as account management messages from the BSS system), and then send the billing control instruction to the billing trigger device based on this information. To this end, the embodiments of the present application further provide Figure 4A-4B The corresponding method flows are described below.

[0460] Figure 4A In the corresponding method flow, the billing trigger device first applies an initial quota to the user service in a non-blocking mode (first mode), and then the billing processing device sends a billing control instruction through a billing notification message, so that the billing trigger device adjusts the billing operation, for example, restores the quota management of the user service, changes the initial quota application to a blocking mode (second mode) for the user service, etc. The method flow mainly includes the following steps:

[0461] Step 401: the charging triggering device receives the start request StartReq41 of the user service.

[0462] The content of this step may refer to step 321 .

[0463] Step 402: The charging triggering device obtains the initial quota application mode IqrMod (=NB) of the user service.

[0464] The content of this step may refer to step 322 .

[0465] Step 403: The charging triggering device starts the user service and records the non-quota usage NQUSU.

[0466] The content of this step may refer to step 323 .

[0467] Step 404: the charging triggering device sends an initial charging request to the charging processing device, which includes quota application information RSU41 and initial quota application mode indication information IqrModInd41.

[0468] The content of this step may refer to step 324 .

[0469] Step 405: The billing processing device grants quota GSU41 and saves IqrMod.

[0470] The content of this step may refer to step 325 .

[0471] Step 406: The charging processing device sends an initial charging response message to the charging triggering device, which includes the granted quota GSU41.

[0472] The content of this step may refer to step 326 .

[0473] Step 407: The charging trigger device monitors the usage of GSU 41 (NQUSU is the used amount of the quota).

[0474] The content of this step may refer to step 327 .

[0475] Thereafter, the billing processing device continues to grant quotas for the user service (based on the billing request sent by the billing trigger device) so that the user is continuously allowed to access the service. At the same time, the billing processing device may also perform billing processing for other user services, which correspond to the same account as the user service, and may also receive change events regarding the attribute information of the user service (such as insufficient package changes for the user service, reduction in user level, etc.). The billing processing device may also send a billing control instruction to the billing trigger device based on the billing processing results of the other user services, change events regarding the attribute information of the user service, etc., so as to adjust the billing trigger device's billing operation on the user service, for example, to restore the quota management of the user service and to switch to an initial quota application in blocking mode.

[0476] Step 408: The billing processing device determines that the blocking mode / quota management should be used instead, generates the next-period billing control instruction NxtCmd41=ToB / this-period billing control instruction CurCmd41=RsmQm, and saves the initial quota application mode IqrMod of the user service.

[0477] Specifically, the billing processing device determines that the billing trigger device should change the quota management of the user service to the blocking mode, and then generates the next-period billing control instruction NxtCmd41 with a value of "ToB"; on this basis, optionally, the billing processing device can also generate the current-period billing control instruction CurCmd41 with a value of "RsmQm"; optionally, the billing processing device can also save / update the initial quota application mode indication information based on the generation of NxtCmd41.

[0478] Specifically, the billing processing device determines that the billing trigger device previously applied for the initial quota in the non-blocking mode for the user service based on the initial quota application mode previously saved for the user service, and based on the billing processing result of the billing request message of "brother service" or "other user service", or based on the processing of the management message of the account of the user service (for example, the account management message from the business support system, Business Support System, BSS), it is found that the requirement of the non-blocking mode of the user service is not met, and thus NxtCmd41 is generated. Regarding the situation where the requirement of the non-blocking mode is not met, the embodiment of the present application is not limited. For example, the billing processing result of the other user service shows that the account of the user service (which is also the account corresponding to the other user service) no longer meets the requirement of the initial quota application in the non-blocking mode. For another example, the event received by the billing processing device indicates that the level of the user corresponding to the user service has been reduced, and so on.

[0479] Optionally, if the billing processing device finds that the quota management of the user service has been suspended (which means that offline billing or unlimited quota management may have been adopted), if the account of the user service (which is also the account corresponding to the other user services) no longer meets the requirements for the initial quota application in the non-blocking mode, it means that the credit control risk has increased. In order to reduce the credit control risk, CurCmd41 with a value of "RsmQm" can also be generated to instruct the billing trigger device to promptly resume the quota management of the user service.

[0480] Regarding the process of saving / updating the user service initial quota application mode, reference may be made to the relevant description in step 305 - 1 .

[0481] Step 409: the charging processing device sends a notification request to the charging triggering device, which includes CurCmd41 and NxtCmd41.

[0482] Specifically, in order to send the billing control instruction generated by step 408-1 to the billing trigger device more timely, the billing processing device generates a notification request message, which includes the CurCmd41 and NxtCmd41, and sends the notification request message to the billing trigger device; wherein CurCmd41 is optional; the notification address (NotifyURL) of the notification request message can identify the billing trigger device and the user service; if the user service is a data service, the notification request message can further carry the identifier RG of the rate group to which the user service belongs.

[0483] Step 410: The billing trigger device resumes quota management and updates the initial quota application mode of the user service based on NxtCmd41.

[0484] Specifically, the billing trigger device receives and parses the notification request message, obtains CurCmd41 and NxtCmd41 therefrom, and on this basis, executes CurCmd41 and NxtCmd41 on the user service, specifically, restores the quota management of the user service (meaning that the billing trigger device restarts to request quota from the billing processing device for the user service), and changes the initial quota application mode of the user service based on NxtCmd41 (for example, it can be saved locally on the billing trigger device, or saved to an external storage facility, or sent to a policy control device, see step 307-1 for details), so that when the billing trigger device receives the next start request of the user service, the initial quota application in blocking mode is adopted for the user service.

[0485] Step 411: The charging triggering device returns a notification response message to the charging processing device.

[0486] Specifically, the charging triggering device returns a notification response message to the charging processing device according to the processing result of step 410, wherein the notification response message includes information indicating that the notification request of step 409 has been successfully processed.

[0487] Step 412: The user service ends.

[0488] The content of this step may refer to step 308 .

[0489] Step 413: The charging triggering device receives the start request StartReq42 of the user service.

[0490] The content of this step may refer to step 333 .

[0491] Step 414: The charging triggering device obtains the initial quota application mode IqrMod (=B) of the user service.

[0492] The content of this step may refer to step 334 .

[0493] Step 415: the charging triggering device sends an initial charging request to the charging processing device, which includes quota application information RSU32 and initial quota application mode indication information IqrModInd42.

[0494] The content of this step may refer to step 335 .

[0495] Step 416: The billing processing device grants quota GSU42 and saves IqrMod.

[0496] The content of this step may refer to step 336 .

[0497] Step 417: The billing processing device sends an initial billing response message to the billing triggering device, including GSU42.

[0498] The content of this step can refer to step 337.

[0499] Step 418: The charging trigger device starts the user service based on GSU42.

[0500] The content of this step can refer to step 338.

[0501] In the above steps 413-418, the initial quota application mode of the user service may also be changed. For details, see Figure 3C Steps 341-346 of the present invention may also change the initial quota application mode of the user service after step 418. For details, see Figure 3D Steps 367-370.

[0502] Compared with the above Figure 3A-3B The corresponding method flow, above Figure 4A The corresponding method flow further expands the opportunity for the billing processing equipment to discover risks and make decisions, from the context of billing processing for user services to the context of billing processing for other user services, and even to the context of processing management messages of the operation support system.

[0503] Figure 4B In the corresponding method flow, the charging trigger device firstly applies for the initial quota in the blocking mode (first mode) for the user service, and then the charging processing device sends a charging control instruction through a charging notification message, so that the charging trigger device adjusts the charging operation, for example, suspends the quota management of the user service, changes the initial quota application to the non-blocking mode (second mode) for the user service, etc. The method flow mainly includes the following steps:

[0504] Step 441: The charging trigger device receives a start request StartReq43 for a user service.

[0505] The content of this step may refer to step 309 .

[0506] Step 442: The charging triggering device obtains the initial quota application mode IqrMod (=B) of the user service.

[0507] The content of this step may refer to step 310 .

[0508] Step 443: the charging triggering device sends an initial charging request message to the charging processing device, which includes quota application information RSU46 and initial quota application mode indication information IqrModInd43.

[0509] The content of this step may refer to step 311 .

[0510] Step 444: The billing processing device grants quota GSU46 and saves IqrMod.

[0511] Specifically, the billing processing device grants the corresponding quota GSU46 according to the quota application information RSU46, and records or saves the initial quota application mode IqrMod of the user service based on IqrModInd43. For details, please refer to the relevant description in step 305-1.

[0512] Step 445: The billing processing device sends an initial billing response message to the billing triggering device, including GSU46.

[0513] The content of this step may refer to step 313 .

[0514] Step 446: The charging trigger device starts the user service based on GSU46.

[0515] The content of this step may refer to step 314 .

[0516] Thereafter, the billing processing device continues to grant quotas for the user service (based on the billing request sent by the billing trigger device) so that the user is continuously allowed to access the service. At the same time, the billing processing device may also perform billing processing for other user services, which correspond to the same account as the user service, and may also receive change events about the attribute information of the user service (such as package changes of the user service: extension, user level upgrade, account recharge, etc.). The billing processing device may also send a billing control instruction to the billing trigger device based on the billing processing results of the other user services, change events of the attribute information of the user service, etc., so as to adjust the billing operation of the billing trigger device on the user service, for example, suspending the quota management of the user service and changing to the initial quota application in non-blocking mode.

[0517] Step 447: The billing processing device determines that the non-blocking mode / suspended quota management should be used, generates the next-period billing control instruction NxtCmd43=ToNB / this-period billing control instruction CurCmd43=HngQm, and saves IqrMod.

[0518] Specifically, the billing processing device determines that the billing trigger device should change the quota management of the user service to non-blocking mode, and then generates the next-period billing control instruction NxtCmd43 with a value of "ToNB"; on this basis, optionally, the billing processing device can also generate the current-period billing control instruction CurCmd43 with a value of "HngQm"; optionally, the billing processing device can also save / update the initial quota application mode indication information based on the generation of NxtCmd43.

[0519] Specifically, the billing processing device determines the initial quota application for the user service in the blocking mode by the billing trigger device according to the initial quota application mode previously saved for the user service; at this time, the billing processing device finds that the requirements of the non-blocking mode are met, and thus generates NxtCmd43 with a value of "ToNB". Regarding the situation where the requirements of the non-blocking mode are met, the embodiment of the present application is not limited. For example, the billing processing result of the other user services shows that the account of the user service (which is also the account corresponding to the other user services) meets the requirements of the initial quota application in the blocking mode. For another example, the event received by the billing processing device indicates that the level of the user corresponding to the user service has been improved.

[0520] In addition, if the account of the user service (which is also the account corresponding to the other user services) meets the requirements for the initial quota application in the non-blocking mode at this time, it means that the credit control risk becomes lower. In order to reduce the system load, CurCmd43 with a value of "HngQm" can also be generated to instruct the billing trigger device to suspend the quota management of the user service in time.

[0521] Regarding saving / updating the initial quota application mode, please refer to the relevant description in step 305-1.

[0522] Step 448: The billing processing device sends a notification request to the billing triggering device, which includes CurCmd43 and NxtCmd43.

[0523] The content of this step may refer to step 409 - 1 .

[0524] Step 449: The billing triggering device suspends quota management and changes the initial quota application mode of the user service based on NxtCmd43.

[0525] Specifically, the billing trigger device receives and parses the notification request message, obtains CurCmd43 and NxtCmd43 therefrom, and on this basis, executes CurCmd43 and NxtCmd43 on the user service, specifically, suspends the quota management of the user service (if it is transferred to offline billing, it means that the billing trigger device no longer requests quota from the billing processing device for the user service; if it is an unlimited quota, it means that the billing trigger device applies for an equal amount of quota from the billing processing device based on the accumulated usage), and changes the initial quota application mode of the user service based on NxtCmd43 (for example, it can be saved locally in the billing trigger device, or saved to an external storage facility, or sent to the policy control device, refer to step 307-1 for details), so that when the billing trigger device receives the next start request of the user service, the initial quota application in non-blocking mode is adopted for the user service.

[0526] Step 450: The charging triggering device returns a notification response message to the charging processing device.

[0527] Specifically, the charging triggering device returns a notification response message to the charging processing device according to the processing result of step 449, wherein the message includes information indicating that the notification request of step 448 has been successfully processed.

[0528] Step 451: The user service ends.

[0529] The content of this step may refer to step 308 .

[0530] Step 452: The charging triggering device receives the start request StartReq44 of the user service.

[0531] The content of this step may refer to step 321 .

[0532] Step 453: The charging trigger device obtains the initial quota application mode IqrMod (=NB) of the user service.

[0533] The content of this step may refer to step 322 .

[0534] Step 454: The charging triggering device starts the user service and records the non-quota usage NQUSU.

[0535] The content of this step may refer to step 323 .

[0536] Step 455: the charging trigger device sends an initial charging request to the charging processing device, which includes quota application information RSU47 and initial quota application mode indication information IqrModInd44, where IqrModInd44 indicates that the charging trigger device adopts a non-blocking mode initial quota application for the user service.

[0537] The content of this step may refer to step 324 .

[0538] Step 456: The billing processing device grants quota GSU47 and saves IqrMod.

[0539] The content of this step may refer to step 325 .

[0540] Step 457: The charging processing device sends an initial charging response message to the charging triggering device, which includes the granted quota GSU47.

[0541] The content of this step may refer to step 326 .

[0542] Step 458: The billing triggering device monitors the usage of GSU 47 (deducting NQUSU first).

[0543] The content of this step may refer to step 327 .

[0544] In the above steps 452-458, the initial quota application mode of the user service may also be changed. For details, see Figure 3C Steps 341-346 of the present invention may also change the initial quota application mode of the user service after step 458. For details, see Figure 3D Steps 367-370.

[0545] Compared with the above Figure 3C-Figure 3D The corresponding method flow, above Figure 4BThe corresponding method flow further expands the opportunity for billing processing equipment to discover low risks and reduce user service access delays, from the context of billing processing for user services to the context of billing processing for other user services, and even to the context of processing management messages of the operation support system.

[0546] Above Figure 3A-3D as well as Figure 4A-4B The corresponding method flow is that the charging processing device is the controller and the charging trigger device is the controlled device. However, regarding the switching or change of the initial quota application mode, the charging trigger device can also participate in the decision-making based on the result returned by the charging processing device. To this end, the embodiment of the present application provides Figure 5A-Figure 5B The corresponding method flows are described below.

[0547] Figure 5A In the corresponding method flow, the billing trigger device initially applies an initial quota in a non-blocking mode (first mode) to the user service, and the billing processing device controls the billing trigger device to perform a billing operation on the user service of the current period accordingly. The billing trigger device changes the initial quota application in a blocking mode (second mode) to the user service according to the billing processing result returned by the billing processing device. The method flow mainly includes the following steps:

[0548] Step 501: The charging triggering device receives a start request StartReq51 for a user service.

[0549] The content of this step may refer to step 301.

[0550] To determine the time sequence of starting the user service and applying for a quota for the user service, the charging triggering device first obtains an initial quota application mode for the user service, as shown in step 502-1 or step 502-2.

[0551] Step 502-1: The charging trigger device obtains the initial quota application mode IqrMod (=NB) of the user service.

[0552] Specifically, the billing trigger device can obtain the initial quota application mode of the user service based on the configuration information of the user service stored in a local or external storage facility, or obtain the initial quota application mode of the user service from the billing policy of the user service activated by the policy control device, which is a non-blocking mode, and then determine the initial quota application in the non-blocking mode should be adopted for the user service.

[0553] Go to step 503.

[0554] Step 502-2:

[0555] If there is no local charging policy for the user service, the charging policy for the user service may be requested from the policy control device.

[0556] Step 502-2-1: The charging triggering device sends a policy request message to the policy control device.

[0557] The policy request message includes information such as a user identifier and PDU session information that can be used to identify the user service.

[0558] Step 502-2-2: The policy control device returns a policy response message to the charging trigger device, which includes the initial quota application mode of the user service.

[0559] Specifically, the policy control device returns a charging policy, which includes an initial quota application mode for the user service.

[0560] Therefore, the charging trigger device can receive and parse the policy response message, obtain the initial quota application mode of the user service therefrom, and further determine that the initial quota application in the non-blocking mode should be adopted for the user service.

[0561] Step 503: The charging triggering device starts the user service and records the non-quota usage NQUSU.

[0562] Specifically, since the charging trigger device has previously determined that an initial quota application in non-blocking mode should be used for the user service, the user service is started immediately (without waiting for the quota granted by the charging processing device), and the usage NQUSU without quota is recorded.

[0563] Step 504: the charging triggering device sends a charging request message to the charging processing device, which includes quota application information RSU51 and initial quota application mode indication information IqrModInd51.

[0564] Specifically, after the user service starts, in order to maintain the user service, the billing trigger device sends a billing request message to the billing processing device; the billing request message can be an initial billing request message or a mid-term billing request message; when the billing request message is an initial billing request message, it contains quota application information RSU51 and initial quota application mode indication information IqrModInd51; when the billing request message is a mid-term billing request message, it contains quota application information RSU51, and optionally, IqrModInd51. IqrModInd51 indicates that the billing trigger device adopts the non-blocking mode as the initial quota application mode for the user service.

[0565] After receiving and parsing the billing request message, the billing processing device obtains the quota application information RSU51 and the initial quota application mode indication information IqrModInd51 (if any) therefrom, and the subsequent processing process is as shown in Example 5A-1 or 5A-2.

[0566] Example 5A-1

[0567] Step 505 - 1 : The billing processing device grants quota GSU51 .

[0568] Specifically, the charging processing device grants the quota GSU51 for the user service based on the quota application information RSU51.

[0569] Step 506-1: The charging processing device sends a charging response message including GSU51 to the charging triggering device.

[0570] Accordingly, the charging response message may be an initial charging response message or an interim charging response message.

[0571] Step 507 - 1 : The charging triggering device monitors the usage of GSU 51 (NQUSU is the used amount of the quota).

[0572] Step 505 - 1 to step 507 - 1 is a successful authorization process. The granted quota can be used as one of the bases for the billing trigger device to determine the change of the initial quota application mode. See step 508 for details.

[0573] Go to step 508.

[0574] Example 5A-2

[0575] Step 505-2: The billing processing device fails to authorize the user service, determines that the user service needs to be interrupted or the quota management of the user service needs to be suspended, and generates CurCmd51=Fail or HngQm.

[0576] Specifically, the billing processing device fails to authorize the user service. For example, based on the quota application information RSU51, it determines that the conditions for granting the quota are not met (for example, the balance is less than the quota request amount in the quota application information RSU51). If the quota fails to be granted, it is further determined that the user service needs to be interrupted or the quota management of the user service needs to be suspended, and a current service control instruction CurCmd51 with a value of "Fail" or "HngQm" is generated.

[0577] For example, the billing processing device generates CurCmd51 based on the attribute information of the user service, such as the interruptibility of the service: if it is known that the user service is an interruptible service, a CurCmd51 with a value of "HngQm" is generated; if it is known that the user service is an interruptible service, a CurCmd51 with a value of "Fail" is generated.

[0578] Step 506-2: The charging processing device sends a charging response message including CurCmd51 to the charging triggering device.

[0579] Accordingly, the charging response message may be an initial charging response message or an interim charging response message.

[0580] Step 507 - 2 : The charging triggering device executes CurCmd51.

[0581] Specifically, if the value of CurCmd51 is "Fail", the user service is interrupted; if the value of CurCmd is "HngQm", the quota management of the user service is suspended, for example, switching to offline billing, but maintaining the user service.

[0582] Step 505-2 to step 507-2 is the process of authorization failure. The control instruction issued can be used as one of the bases for the billing trigger device to determine to change the initial quota application mode. See step 508 for details.

[0583] Step 508: The charging triggering device determines that the initial quota application mode of the user service should be changed to a blocking mode based on the charging processing result.

[0584] Specifically, the billing triggering device determines, based on the billing processing procedure of Example 5A-1 or Example 5A-2, that the initial quota application mode of the user service should be changed, that is, from the previous non-blocking mode (NB) to the blocking mode (B).

[0585] For example, the billing trigger device can determine that the billing processing device tightens credit control based on a downward trend in the amount of granted quotas in multiple consecutive billing processing results, and further determine that the initial quota application mode of the user service should be changed to a blocking mode; for another example, based on the cause and / or number of authorization failures, it is determined that the credit control risk of the user service has increased, and the initial quota application should subsequently be changed to a blocking mode.

[0586] After determining to change the initial quota application mode, the charging triggering device may save the new initial quota application mode for the user service, as shown in step 509 - 1 or step 509 - 2.

[0587] Step 509-1: The charging triggering device updates the initial quota application mode of the user service.

[0588] Specifically, the charging trigger device saves the initial quota application mode to the configuration information of the user service saved in a local or external storage facility, wherein the initial quota application mode saved in the external storage facility can be shared among multiple charging trigger devices.

[0589] Step 509-2:

[0590] Step 509-2-1: The charging trigger device sends a policy update request message to the policy control device, which includes instruction information for updating the initial quota application mode of the user service.

[0591] Specifically, after the billing trigger device updates the initial quota application mode in the locally effective billing policy of the user service, it further sends a policy update request to the policy control device, and the policy update request includes indication information for updating the initial quota application mode of the user service, so that the policy control device subsequently generates a billing policy for the user service based on the initial quota application mode; or, instead of updating the initial quota application mode in the locally effective billing policy of the user service, a policy update request is directly sent to the policy control device, and the update request includes indication information for updating the initial quota application mode of the user service. After that, the policy control device issues a new billing policy for the user service in a response message to the policy update request, and the new billing policy includes the updated initial quota application mode of the user service. The indication information may indicate prohibiting the use of a non-blocking mode for the user service, or indicating the use of a blocking mode for the user service.

[0592] An example of sending a policy update request message to a policy control device is as follows:

[0593]

[0594] Step 509-2-2: The policy control device returns a policy update response message (OK) to the charging trigger device.

[0595] Relative to Figure 3A-3D as well as Figure 4A-4B , the above Figure 5A The corresponding method flow can further reduce the performance burden of the billing processing device on this basis.

[0596] Figure 5BIn the corresponding method flow, the billing trigger device adopts the initial quota application in the blocking mode (first mode) for the user service, and the billing processing device performs billing processing accordingly and sends the billing processing result to control the billing trigger device for the current user service billing operation, and the billing trigger device switches to the initial quota application in the non-blocking mode (second mode) for the user service according to the billing processing result returned by the billing processing device. The method flow mainly includes the following steps:

[0597] Step 551: The charging trigger device receives a start request StartReq52 for a user service.

[0598] The content of this step may refer to step 301.

[0599] To determine the time sequence of starting the user service and applying for a quota for the user service, the charging triggering device first obtains the initial quota application mode of the user service, as shown in step 552-1 or step 552-2.

[0600] Step 552-1: The charging trigger device obtains the initial quota application mode IqrMod (=B) of the user service.

[0601] The content of this step can refer to step 502-1, except that the initial quota application mode of the user service is the blocking mode.

[0602] Go to step 553.

[0603] Step 552-2:

[0604] Step 552-2-1: The charging triggering device sends a policy request message to the policy control device.

[0605] The content of this step can refer to step 502-2-1.

[0606] Step 552-2-2: The policy control device returns a policy response message to the charging trigger device, which includes the initial quota application mode of the user service.

[0607] The content of this step can refer to step 502-2-2.

[0608] Step 553: the charging triggering device sends a charging request message to the charging processing device, which includes quota application information RSU52 and initial quota application mode indication information IqrModInd53.

[0609] The billing request message may be an initial billing request message or a mid-term billing request message; specifically, to start the user service, the billing trigger device sends an initial billing request message to the billing processing device, which includes quota application information RSU52 and initial quota application mode indication information IqrModInd53; after the user service starts, in order to maintain the user service, the billing trigger device sends a mid-term billing request message to the billing processing device, which includes quota application information RSU52 and, optionally, IqrModInd53. IqrModInd53 indicates that the initial quota application mode adopted by the billing trigger device for the user service is a blocking mode.

[0610] After receiving and parsing the billing request message, the billing processing device obtains the quota application information RSU52 and the initial quota application mode indication information IqrModInd53 (if any) therefrom, and the subsequent processing process is as shown in Example 5B-1 or 5B-2.

[0611] Example 5B-1

[0612] Step 554 - 1 : The billing processing device grants the quota GSU52 .

[0613] Specifically, the charging processing device grants the quota GSU52 for the user service based on the quota application information RSU52.

[0614] Step 555 - 1 : The charging processing device sends a charging response message including GSU52 to the charging triggering device.

[0615] Step 556 - 1 : The charging triggering device starts the user service based on GSU 52 , or monitors the use of GSU 52 .

[0616] Specifically, if the charging response message is an initial charging response message, the charging trigger device starts charging the user based on GSU52; if the charging response message is an interim charging response message, the charging trigger device monitors the use of GSU52.

[0617] Step 554 - 1 to step 556 - 1 is the normal process of granting quota. The granted quota can be used as one of the bases for the billing trigger device to determine the change of the initial quota application mode. See step 557 for details.

[0618] Go to step 557.

[0619] Example 5B-2

[0620] Step 554-2: The billing processing device successfully grants the quota and generates CurCmd=HngQm.

[0621] Compared with step 554-1, in addition to granting the quota GSU52, the billing processing device also generates CurCmd52=HngQm based on factors such as the performance burden of the billing system, so that the billing triggering device suspends the quota management of the user service.

[0622] Step 555 - 2 : The charging processing device sends a charging response message to the charging triggering device, which includes GSU52 and CurCmd52.

[0623] Compared with step 555-1, the charging response message further includes CurCmd52.

[0624] Step 556 - 2 : The charging triggering device executes CurCmd52 .

[0625] Compared with step 506 - 2 , the charging triggering device further suspends the quota management of the user service according to CurCmd52 = HngQm.

[0626] Step 554-1 to step 556-1 is the normal quota granting process. The granted quota and the issued billing control instruction (CurCmd52) can be used as one of the bases for the billing trigger device to determine the change of the initial quota application mode. See step 557 for details.

[0627] Step 557: The charging trigger device determines that the initial quota application mode of the user service should be changed to a non-blocking mode based on the charging processing result.

[0628] Specifically, the billing trigger device determines that the initial quota application mode of the user service should be changed, that is, from the previous blocking mode (B) to the non-blocking mode (NB), based on the billing processing process of Example 5B-1 or Example 5B-2. For example, the billing trigger device can determine that the billing processing device relaxes credit control based on the upward trend of the quota amount granted in multiple consecutive billing processing results, and further determines that the initial quota application mode of the user service should be changed to the non-blocking mode.

[0629] After determining to change the initial quota application mode, the charging trigger device may save the new initial quota application mode for the user service, as shown in step 558-1 or step 558-2.

[0630] Step 558-1: The charging triggering device updates the initial quota application mode of the user service.

[0631] The content of this step may refer to step 509-1.

[0632] Step 558-2:

[0633] Step 558-2-1: The charging trigger device sends a policy update request message to the policy control device, which includes instruction information for updating the initial quota application mode of the user service.

[0634] The content of this step can refer to step 509-2-1.

[0635] Step 558-2-2: The policy control device returns a policy update response message (OK) to the charging trigger device.

[0636] The content of this step can refer to step 509-2-2.

[0637] Relative to Figure 3A-3D as well as Figure 4A-4B The corresponding method flow, above Figure 5B The corresponding method flow can further reduce the performance burden of the billing processing device on this basis.

[0638] Figure 6 The hardware structure diagram of the charging trigger device, charging processing device or policy control device provided in the embodiment of the present application. All charging trigger devices (for example, Figure 1 102), billing processing equipment (for example, Figure 1 101), a policy control device (e.g., Figure 1 The policy control device 104) can be used Figure 6 The general computer hardware structure shown includes a processor 601, a memory 602, a bus 603, an input device 604, an output device 605, and a network interface 606, wherein the input device 604 and the output device 605 are optional.

[0639] Specifically, the memory 602 may include computer storage media in the form of volatile and / or nonvolatile memory, such as read-only memory and / or random access memory. The memory 602 may store an operating system, application programs, other program modules, executable code, and program data.

[0640] The input device 604 can be used to input information, so as to facilitate the system administrator to operate and manage the billing trigger device, the billing processing device or the policy control device, for example, to configure the user account risk threshold on the billing processing device, to manage the storage space of the initial quota application mode indication information on the billing trigger device, to manage the storage space of the initial quota application mode indication information on the policy control device, etc. The input device 604 can be a keyboard or a pointing device, such as a mouse, a trackball, a touchpad, a microphone, a joystick, a game pad, a satellite TV antenna, a scanner or a similar device, which can be connected to the processor 601 via the bus 603.

[0641] The output device 605 can be used to output information to facilitate the system administrator to operate and manage the billing trigger device, the billing processing device or the policy control device; for example, displaying the user account risk threshold on the billing processing device, displaying the remaining storage space on the billing trigger device, displaying the remaining storage space on the policy control device, etc.; in addition to the monitor, the output device 605 can also be other peripheral output devices, such as speakers and / or printing devices, which can also be connected to the processor 601 via the bus 603.

[0642] The charging trigger device, the charging processing device or the policy control device can be connected to a network, such as a local area network (LAN), through the network interface 606. In a networked environment, the computer execution instructions stored in the charging trigger device, the charging processing device or the policy control device can be stored in a remote storage device, rather than being limited to local storage.

[0643] When the processor 601 in the billing trigger device executes the executable code or application stored in the memory 602, the billing trigger device can execute the method steps corresponding to the billing trigger device in all the above embodiments, such as steps 230, 303, 307-2, 331-2, 346, 370, 410, 449, 507-2 and 556-2, etc.; the specific execution process can be found in the above embodiments and will not be repeated here.

[0644] When the processor 601 in the billing processing device executes the executable code or application stored in the memory 602, the billing processing device can execute the method steps corresponding to the billing processing device in all the above embodiments, such as steps 220, 305-1, 329-1, 344, 368, 408, 447, 505-2 and 554-2; the specific execution process can be found in the above embodiments and will not be repeated here.

[0645] When the processor 601 in the policy control device executes the executable code or application stored in the memory 602, the policy control can execute the method steps corresponding to the policy control device in all the above embodiments, such as steps 502-2, 509-2, 552-2 and 558-2; the specific execution process can refer to the above embodiments and will not be repeated here.

[0646] Figure 7 A schematic diagram of the logical structure of a billing processing device (101) provided in an embodiment of the present application, wherein the billing processing device (101) is used to control the billing operation of the billing trigger device (102) on the user service according to the initial quota application mode adopted by the billing trigger device (102) for the user service, including:

[0647] - Acquisition module 701, used to obtain the initial quota application mode indication information of the user service, etc., wherein the initial quota application mode indication information indicates that the billing trigger device (102) adopts the first initial quota application mode for the user service when receiving the first start request of the user service. For the specific execution process, please refer to the step description on the billing processing device side in the above embodiment, such as steps 201, 304, 324 and 328-1.

[0648] -Sending module 702, used to send the billing processing result, etc. to the billing trigger device (102), wherein the billing processing result is the result of billing processing of the user service based on the initial quota application mode indication information. For the specific execution process, please refer to the step description of the billing processing device side in the above embodiment, such as steps 330-1, 330-2 and 345, etc.

[0649] Figure 8 A schematic diagram of the logical structure of a charging trigger device (102) provided in an embodiment of the present application, wherein the charging trigger device (102) is used to send initial quota application mode indication information of a user service to a charging processing device (101), and adjust the charging operation of the user service according to the charging processing result sent by the charging processing device (101), including:

[0650] - A sending module 801 is used to send initial quota application mode indication information of the user service to the billing processing device (101), wherein the initial quota application mode indication information indicates that the billing trigger device (102) adopts the first initial quota application mode for the user service when receiving the first start request of the user service. For the specific execution process, please refer to the step description on the billing trigger device side in the above embodiment, such as steps 201, 304, 324 and 328-1.

[0651] - Receiving module 802, used to receive the billing processing result of the user service from the billing processing device (101), and the specific execution process refers to the step description of the billing triggering device side in the above embodiment, such as steps 330-1, 330-2 and 345.

[0652] -Processing module 803, used to process the user service based on the billing processing result, etc. For the specific execution process, please refer to the step description of the billing trigger device side in the above embodiment, such as steps 307-1, 307-2, 307-3, 331-1, 331-2, 331-3 and 331-4.

[0653] Fig. 9 A schematic diagram of the logical structure of a policy control device (104) provided in an embodiment of the present application, wherein the policy control device (104) is used to save an initial quota application mode of a user service for a charging trigger device (102), including:

[0654] -The transceiver module 901 is used to receive the initial quota application mode of the user service from the billing trigger device (102), or receive a query request for the initial quota application mode from the billing trigger device (102), etc. For the specific execution process, please refer to the step description on the billing trigger device side in the above embodiment, such as steps 502-2-1 and 509-2-1, etc.

[0655] - Storage module 902, used to save the initial quota application mode of the user service received from the billing trigger device (102) to a local storage facility, and optionally return a success response to the billing trigger device (102) through the transceiver module 901, or according to the query request of the initial quota application mode received from the billing trigger device (102), find out the initial quota application mode of the user service from the local storage setting, and send it to the billing trigger device (102) through the transceiver module 901, such as steps 502-2-2 and 509-2-2, etc.

[0656] Figure 7 The billing processing equipment shown, Figure 8 The billing trigger device and Fig. 9 The policy control device shown is presented in the form of functional modules. Here, "module" may refer to an application-specific integrated circuit (ASIC), a circuit, a processor and a memory that executes one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions. In a simple embodiment, those skilled in the art will recognize that these devices can also be used Figure 6 For example, the acquisition module 701, the sending module 702, the sending module 801, the receiving module 802, the processing module 803, the transceiver module 901 and the storage module 902 can all be implemented by Figure 6 For example, the function of the acquisition module 701 acquiring the initial quota application mode indication information of the user service, the function of the sending module 801 sending the initial quota application mode indication information, and the function of the storage module 901 storing the initial quota application mode of the user service can all be implemented by the processor 601 executing the code stored in the memory 602.

[0657] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0658] A person skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0659] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the division of the units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or it can be an electrical, mechanical or other form of connection.

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

[0661] 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.

[0662] 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 is essentially or partly contributed 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 for 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: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk.

[0663] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in the present application, and these modifications or replacements should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A billing system, comprising: The charging processing device (101) and the charging triggering device (102) are characterized by: The charging trigger device (102) is used to: send initial quota application mode indication information to the charging processing device (101), wherein the initial quota application mode indication information indicates that the charging trigger device (102) adopts a first initial quota application mode for the user service when receiving a first start request for the user service; The charging processing device (101) is used to: authorize the user service based on the initial quota application mode indication information, and return the authorization result; The charging trigger device (102) is also used to: process the user service based on the authorization result.

2. The billing system according to claim 1, characterized in that: The charging trigger device (102) is further used to: adopt the first initial quota application mode for the user service when receiving the first start request, and send an initial charging request message of the user service to the charging processing device (101), wherein the initial charging request message includes the initial quota application mode indication information; The charging processing device (101) is further used to obtain the initial quota application mode indication information from the initial charging request message.

3. The charging system according to claim 1 or 2, characterized in that: The charging processing device (101) is further configured to send an authorization result including any one of the following items to the charging triggering device (102): an indication parameter for instructing the charging trigger device (102) to suspend the quota management of the user service, or An indication parameter used to instruct the charging trigger device (102) to interrupt the user service.

4. The charging system according to claim 3, characterized in that: The billing processing device (101) is also used to send an indication parameter to the billing trigger device (102) to suspend the quota management of the user service when the first initial quota application mode is a non-blocking mode and it is determined that the billing trigger device (102) needs to suspend the quota management of the user service. The billing trigger device (102) is also used to suspend the quota management of the user service.

5. The charging system according to any one of claims 1 to 3, characterized in that: The charging processing device (101) is further used to send an indication parameter to the charging triggering device (102) to instruct the charging triggering device to adopt a second initial quota application mode for the user service when receiving a second start request for the user service, the second start request occurring later than the first start request.

6. A method for processing user services, applied to a billing processing device (101), characterized in that: include: Acquiring initial quota application mode indication information of a user service, wherein the initial quota application mode indication information indicates that a charging trigger device (102) adopts a first initial quota application mode for the user service when receiving a first start request of the user service; A billing authorization result is sent to the billing trigger device (102), wherein the billing authorization result is a result of authorization processing for the user service based on the initial quota application mode indication information.

7. The method according to claim 6, characterized in that The obtaining of the initial quota application mode indication information includes: Receiving an initial charging request message of the user service from the charging trigger device (102), wherein the initial charging request message includes the initial quota application mode indication information; The initial quota application mode indication information is obtained from the initial charging request message.

8. The method according to claim 6 or 7, characterized in that: The billing processing result includes any of the following: an indication parameter for instructing the charging trigger device (102) to suspend the quota management of the user service, or An indication parameter used to instruct the charging trigger device (102) to interrupt the user service.

9. The method according to claim 8, characterized in that When the first initial quota application mode is a non-blocking mode, the charging processing result includes an indication parameter for instructing the charging trigger device (102) to suspend the quota management of the user service, and the charging authorization for the user service based on the initial quota application mode indication information includes: Authorization for the user service fails, and based on the initial quota application mode indication information, it is determined that the charging trigger device (102) needs to suspend quota management of the user service.

10. The method according to claim 8, characterized in that When the first initial quota application mode is a non-blocking mode, the billing processing result includes an indication parameter for instructing the billing trigger device (102) to interrupt the user service, and the billing authorization for the user service based on the initial quota application mode indication information includes: Authorization for the user service fails, and based on the initial quota application mode indication information, it is determined that the charging processing device (101) needs to interrupt the user service.

11. The method according to claim 10, characterized in that The method further comprises: The quota-free usage of the user service is received from the charging trigger device (102).

12. The method according to any one of claims 6 to 8, characterized in that: The charging processing result further includes an indication parameter for instructing the charging triggering device to adopt a second initial quota application mode for the user service when receiving a second start request for the user service, the second start request occurring later than the first start request.

13. The method according to claim 12, characterized in that The first initial quota application mode is a non-blocking mode, and the second initial quota application mode is a blocking mode; or, the first initial quota application mode is a blocking mode, and the second initial quota application mode is a non-blocking mode.

14. The method according to any one of claims 6 to 13, characterized in that : The charging process for the user service based on the initial quota application mode indication information is triggered by an initial charging request message of the user service, and the sending of the charging process result to the charging trigger device (102) includes: sending an initial charging response message of the user service to the charging trigger device (102), wherein the initial charging response message includes the charging authorization result; or The billing process for the user service based on the initial quota application mode indication information is triggered by a mid-term billing request message of the user service, and the sending of the billing process result to the billing trigger device (102) includes: sending a mid-term billing response message of the user service to the billing trigger device (102), wherein the mid-term billing response message includes the authorization result; or The charging process for the user service based on the initial quota application mode indication information is triggered by other charging request messages or account management messages, the other charging request messages are charging request messages for other user services, the other user services correspond to the same account as the user service, the account management message is a management message for the account corresponding to the user service, and sending the authorization result to the charging trigger device (102) includes: sending a notification message to the charging trigger device (102), the notification message including the authorization result.

15. A method for processing user services, applied to a charging trigger device (102), characterized in that: include: Sending initial quota application mode indication information of the user service to the charging processing device (101), wherein the initial quota application mode indication information indicates that the charging triggering device (102) adopts a first initial quota application mode for the user service when receiving a first start request of the user service; Receiving the authorization result of the user service from the billing processing device (101); The user service is processed based on the authorization result.

16. The method according to claim 15, characterized in that The sending of the initial quota application mode indication information of the user service to the charging processing device (101) is specifically: adopting the first initial quota application mode for the user service upon receiving the first start request; An initial charging request message of the user service is sent to the charging processing device (101), wherein the initial charging request message includes the initial quota application mode indication information.

17. The method according to claim 15 or 16, characterized in that The authorization result includes any of the following: an indication parameter for instructing the charging trigger device (102) to suspend the quota management of the user service, or An indication parameter used to instruct the charging trigger device (102) to interrupt the user service.

18. The method according to claim 17, characterized in that The charging processing result includes an indication parameter for instructing the charging trigger device (102) to suspend the quota management of the user service, and the processing of the user service based on the authorization result includes: Suspend the quota management of the user service.

19. The method according to claim 17, characterized in that The charging processing result includes an indication parameter for instructing the charging trigger device (102) to interrupt the user service, and the processing of the user service based on the authorization result includes: interrupting the user's service, And the quota-free usage of the user service is sent to the billing processing device (101).

20. The method according to any one of claims 15 to 17, characterized in that: The charging processing result further includes an indication parameter for instructing the charging trigger device to adopt a second initial quota application mode for the user service when receiving a second start request for the user service, the second start request being generated later than the first start request, and processing the user service based on the charging processing result further includes: The initial quota application mode of the user service is updated to the second initial quota application mode.

21. The method according to claim 20, characterized in that The receiving the authorization result of the user service from the charging processing device (101) comprises: receiving an initial charging response message of the user service from the charging processing device (101), wherein the initial charging response message includes the authorization result; or receiving an interim billing response message of the user service from the billing processing device (101), wherein the interim billing response message includes the authorization result; or A notification message is received from the billing processing device (101), wherein the notification message includes the authorization result.

22. The method according to any one of claims 15 to 19, characterized in that: The processing of the user service based on the charging processing result includes: Determining, according to the charging processing result, that a second initial quota application mode should be adopted for the user service when a second start request for the user service is received, the second start request being generated later than the first start request; The initial quota application mode of the user service is updated to the second initial quota application mode.

23. The method according to any one of claims 20 to 22, characterized in that: The updating the initial quota application mode of the user service to the second initial quota application mode includes: Sending indication information to the policy control device (104) prohibiting the user service from using the first initial quota application mode; or, Instruction information is sent to the policy control device (104) to instruct the initial quota application mode corresponding to the user service to be changed to the second initial quota application mode.

24. The method according to any one of claims 20 to 23, characterized in that: The first initial quota application mode is a non-blocking mode, and the second initial quota application mode is a blocking mode; or, the first initial quota application mode is a blocking mode, and the second initial quota application mode is a non-blocking mode.

25. A method for processing user services, characterized in that: Applied to a policy control device, the method includes: Sending initial quota application mode indication information of the user service to the charging trigger device, wherein the initial quota application mode indication information indicates that the charging trigger device adopts a first initial quota application mode for the user service when receiving a first start request of the user service; Receiving, from the charging trigger device, indication information of the initial quota application mode of the user service, the indication information being indication information prohibiting the use of the first initial quota application mode for the user service, or indication information indicating that the initial quota application mode corresponding to the user service is changed to a second initial quota application mode; The initial quota application mode of the user service is updated to the second initial quota application mode based on the initial quota application mode indication information.

26. A method for processing user services, characterized in that: A charging trigger device, the method comprising: Receiving initial quota application mode indication information of a user service sent by a policy control device, wherein the initial quota application mode indication information indicates that the charging trigger device adopts a first initial quota application mode for the user service when receiving a first start request for the user service; Sending initial quota application mode indication information of the user service to the policy control device, where the indication information is indication information prohibiting the use of the first initial quota application mode for the user service, or indication information indicating that the initial quota application mode corresponding to the user service is changed to a second initial quota application mode; A second initial quota application mode sent by the policy control device is received, where the second initial quota application mode updates the initial quota application mode of the user service based on the initial quota application mode indication information.

27. A device, characterized in that: comprising a processor and a memory, wherein: The memory is used to store program instructions; The processor is used to call and execute the program instructions stored in the memory so that the device performs the method described in any one of claims 1-26.

28. A computer-readable storage medium, characterized in that: The method comprises instructions which, when executed on a computer, cause the computer to perform the method according to any one of claims 1 to 26.

Images