Charging exception processing method and related equipment

Abstract

The invention relates to the field of charging. The invention particularly relates to a charging exception processing method and related equipment. The method comprises the following steps: a first R-CHF entity receives a first charging request sent by a CTF entity, detects interaction abnormity of a target CHF entity related to the first charging request, and executes abnormal charging processing. Wherein the target CHF entity is a main CHF entity or a second R-CHF entity. The primary CHF entity provides online quota management and charging ticket generation, and the second R-CHF entity is a CHF entity that provides a relay for the CTF entity and the primary CHF entity before the first R-CHF entity is used as a relay CHF entity. When the main CHF entity is abnormal or the second R-CHF entity is abnormal, the abnormal charging processing is executed through the first R-CHF entity, and the situation that charging cannot be carried out normally can be avoided.

Description

Technical Field

[0001] The present application relates to the field of billing, and in particular to a method for handling billing anomalies and related equipment. Background Art

[0002] In the 5G architecture, the billing architecture adopts a fusion architecture of online billing and offline one-time event billing, such as Figure 1 As shown in the figure: The converged charging system (CCS) is a charging system that integrates online charging and offline one-time event charging, and is connected to the charging trigger function (CTF) entity through the Nchf interface. CCS receives the charging request sent by the CTF entity, which includes the quota application information of CTF, the usage information collected by CTF, etc. CCS performs billing processing based on the billing request and relevant information of the user's service, such as user type, customer information, account balance, service white / blacklist, account balance change trend, remaining validity period of the package, etc., and sends the billing processing results to the CTF entity so that the CTF entity can adjust the billing operation for the user's service.

[0003] CCS includes a charging function (CHF) entity, an account balance management function (ABMF) entity, a charging gateway function (CGF) entity, and a rating function (RF) entity.

[0004] Among them, the CHF entity includes an online charging function (OCF) entity and a charging data function (CDF) entity. Among them, the CDF function is responsible for receiving the charging information from the CTF entity or the CEF entity through the Nchf interface, generating CDR, and transmitting it to the CGF entity. Finally, the CGF entity creates a charging data record (CDR) file and forwards it to the relevant processing equipment in the charging domain; the OCF function, as the quota control node of online charging, provides quota management functions and performs quota processing of online charging for various services of users. The RF entity is responsible for pricing the charging information provided by the OCF entity. RF can handle various types of charging, such as data volume charging, session / connection time charging, and service event charging. The CGF entity receives the CDR transmitted by the CHF entity, completes the functions of sorting, merging, filtering, decoding, routing, and distribution of the call record, and transmits the call record to the charging domain through the Bx interface.

[0005] In a charging system including a CTF entity, an R-CHF entity and a main CHF entity, if the main CHF entity is abnormal or the relay CHF (relay RCH, R-CHF) entity is abnormal, charging cannot be performed normally. Summary of the invention

[0006] The embodiment of the present application provides a billing exception method and related devices. The embodiment of the present application can avoid the situation where billing cannot be performed normally due to the abnormality of the main CHF entity or the abnormality of the R-CHF entity.

[0007] In a first aspect, an embodiment of the present application provides a method. The method is applied to a first R-CHF entity. The method comprises:

[0008] The first R-CHF entity receives the first charging request sent by the CTF entity, detects that the target CHF entity interaction related to the first charging request is abnormal, and performs abnormal charging processing.

[0009] The target CHF entity is a main CHF entity or a second R-CHF entity. The main CHF entity provides online quota management and billing call record generation. The second R-CHF entity is a CHF entity that provides relay for the CTF entity and the main CHF entity before the first R-CHF entity acts as a relay CHF entity.

[0010] When the main CHF entity is abnormal or the second R-CHF entity is abnormal, the first R-CHF entity performs abnormal billing processing, thereby preventing the situation where billing cannot be performed normally.

[0011] In combination with the first aspect, in a possible implementation manner, the target CHF entity is a primary CHF entity, the first charging request is a first charging resource creation request, which is used to request the creation of a first charging resource for charging interaction between the CTF entity and the first R-CHF entity, and the first R-CHF entity performs abnormal charging processing, including:

[0012] The first R-CHF entity generates a first billing resource for billing interaction between the CTF entity and the first R-CHF entity; the first R-CHF entity caches the billing information in the first billing request; the first R-CHF entity sends a first billing response message to the CTF entity for responding to the first billing request, the first billing response message including an identifier of the first billing resource.

[0013] It should be noted that the charging information cached by the first R-CHF entity is the charging information that needs to be provided to the main CHF entity.

[0014] By sending the first charging response message to the CTF entity, the CTF entity is made aware that the session with the first R-CHF entity has been established.

[0015] In combination with the first aspect, in a possible implementation, the first charging request includes a quota request, and the first response message includes suspended quota indication information or a granted quota, and the suspended quota indication information is used to instruct the CTF entity to continue the service according to the suspended quota management mode.

[0016] The quota suspension indication information or the granted quota is sent to the CTF entity so that the charging process proceeds normally.

[0017] In combination with the first aspect, in a possible implementation, the first charging response message includes the granted quota, and the CTF entity receives usage of the granted quota, and the cached charging information includes a quota suspension identifier corresponding to the usage of the granted quota.

[0018] In combination with the first aspect, in a possible implementation manner, the first R-CHF entity caches the charging information in the first charging request, including:

[0019] The first R-CHF entity writes the charging information in the first charging request into the first R-CHF call record or saves it in the first charging resource.

[0020] In combination with the first aspect, in a possible implementation, caching the billing information in the first billing request includes:

[0021] The charging information in the first charging request is written into the first R-CHF bill or stored in the first charging resource.

[0022] By caching the charging information, it is convenient to provide the charging information to the main CHF entity after the interaction with the main CHF entity is normal, thereby realizing normal charging.

[0023] In combination with the first aspect, in a possible implementation manner, the method of this embodiment further includes:

[0024] When it is detected that the target CHF entity interaction related to the first billing request is normal, a second billing request is sent to the main CHF entity, where the second billing request is a second billing resource creation request, which is used to request the creation of a second billing resource for the billing interaction between the first R-CHF entity and the main CHF entity, or the second billing request is a third billing resource update or release request, which is used to request the update or release of the third billing resource between the CTF entity and the main CHF entity.

[0025] In combination with the first aspect, in a possible implementation manner, the second charging request carries cached charging information.

[0026] In one example, the cached billing information includes the billing information in the first billing request. In another example, the cached billing information includes the billing information in the first billing request and a corresponding quota suspension identifier.

[0027] In combination with the first aspect, in a possible implementation manner, the method of this embodiment further includes:

[0028] When it is detected that the target CHF entity related to the first charging request interacts normally, a first R-CHF call record is sent to the main CHF entity. Here, the target CHF entity related to the first charging request is the main CHF entity.

[0029] In combination with the first aspect, in a possible implementation manner, the method of this embodiment further includes:

[0030] Before generating the second charging request, a notification message is sent to the CTF entity, the notification message is used to instruct the CTF entity to restore quota management; a third charging request sent by the CTF entity is received, the third charging request carries a quota request and usage for restoring quota management; the second charging request includes the quota request and usage carried by the third charging request.

[0031] It should be noted that the usage here refers to the usage of the suspended quota or the usage of the granted quota.

[0032] In combination with the first aspect, in a possible implementation manner, the target CHF is a primary CHF entity corresponding to the first charging request, the first charging request is a second charging resource update request or a second charging resource release request, which is used to request to update or release a second charging resource for charging interaction between the first R-CHF entity and the CTF entity, and the first R-CHF entity performs abnormal charging processing, including:

[0033] caching the billing information of the first billing request; and sending a first billing response message in response to the first billing request to the CTF entity.

[0034] In combination with the first aspect, in a possible implementation, if the first charging request includes a quota request, the first response message includes suspended quota indication information or a granted quota, and the suspended quota indication information is used to instruct the CTF entity to continue the service according to the suspended quota management mode.

[0035] In combination with the first aspect, in a possible implementation, the cached billing information includes first billing information and a corresponding quota consumption identifier, or second billing information and a corresponding quota suspension identifier, the first billing information is the billing information that uses the available quota granted by the main CHF entity in the billing information, and the second part of the billing information is the billing information that does not use the available quota granted by the main CHF entity in the billing information.

[0036] In combination with the first aspect, in a possible implementation, caching the billing information of the first billing request includes:

[0037] The first charging information and the corresponding consumption quota identifier, or the second charging information and the corresponding quota suspension identifier are written into the first R-CHF call bill or stored in the first charging resource.

[0038] In combination with the first aspect, in a possible implementation manner, the method of this embodiment further includes:

[0039] When it is detected that the target CHF interaction related to the first charging request is normal, a second charging request is sent to the main CHF entity, and the second charging request is a second charging resource update request or a second charging resource release request, which is used to request to update or release the second charging resource of the charging interaction between the first R-CHF entity and the main CHF entity.

[0040] In combination with the first aspect, in a possible implementation manner, the method of this embodiment further includes:

[0041] When it is detected that the target CHF interaction related to the first charging request is normal, a first R-CHF call record is sent to the main CHF entity.

[0042] In combination with the first aspect, in a possible implementation, if the billing information and the corresponding quota suspension identifier are stored in the first billing resource, the second billing request carries the billing information and the corresponding quota suspension identifier or quota consumption identifier.

[0043] In combination with the first aspect, in a possible implementation manner, the method of this embodiment further includes:

[0044] Before generating the second charging request, a notification message is sent to the CTF entity, where the notification message is used to instruct the CTF entity to restore quota management; a third charging request sent by the CTF entity is received, where the third charging request carries a quota request and usage for restoring quota management; and the second charging request includes the quota request and usage carried by the third charging request.

[0045] It should be noted that the usage here refers to the usage of the suspended quota or the usage of the granted quota.

[0046] In combination with the first aspect, in a possible implementation, the target CHF entity is a primary CHF entity corresponding to the first charging request, the first charging request is a one-time event charging request for online direct deduction or offline one-time event charging, and abnormal charging processing is performed, including:

[0047] caching the billing information of the first billing request; and sending a first billing response message in response to the first billing request to the CTF entity.

[0048] In combination with the first aspect, in a possible implementation manner, the method of this embodiment further includes:

[0049] Writing the charging information and the corresponding online direct deduction indication information or offline one-time event charging indication information into the first R-CHF call record;

[0050] When it is detected that the target CHF interaction related to the first charging request is normal, a first R-CHF call record is sent to the main CHF entity.

[0051] In combination with the first aspect, in a possible implementation manner, the method of this embodiment further includes:

[0052] The charging information of the first charging request and the corresponding online direct deduction indication information or offline one-time event charging indication information are stored in the first charging resource;

[0053] When it is detected that the target CHF interaction related to the first billing request is normal, a second billing request is sent to the main CHF entity, the second billing request is a one-time event billing request, and the second billing request carries billing information and corresponding online direct deduction indication information or offline one-time event billing indication information.

[0054] In combination with the first aspect, in a possible implementation manner, the target CHF entity is a second R-CHF entity, and the second R-CHF entity is a CHF entity that provides relay for the CTF entity and the main CHF entity before the first R-CHF entity; the first charging request is a first charging resource update request or a first charging resource release request, which is used to request to update or release a first charging resource for charging interaction between the second R-CHF entity and the CTF entity; performing abnormal charging processing includes:

[0055] Generate a fourth billing resource between the CTF entity and the first R-CHF entity according to the first billing request, and use the first billing resource identifier as the identifier of the fourth billing resource; generate a second billing request according to the first billing request, send the second billing request to the main CHF entity, the second billing request is used to request the creation of a second billing resource for billing interaction between the first R-CHF entity and the main CHF entity, and the second billing request carries the identifier of the third billing resource; receive a second billing response message from the main CHF entity in response to the second billing request; the second billing response message carries the identifier of the second billing resource; generate a first billing response message for responding to the first billing request according to the second billing response message; and send the first billing response message to the CTF entity.

[0056] In a second aspect, an embodiment of the present application provides another method for handling billing exceptions. The method is applied to a main CHF entity. The main CHF entity provides online quota management and billing call record generation. The method includes:

[0057] Receive relevant billing information cached by the first R-CHF entity, where the cached relevant billing information is carried in a billing call or a billing message, and the cached relevant billing information includes the billing information and a corresponding quota suspension identifier or a quota consumption identifier; and perform billing processing according to the quota suspension identifier or the quota consumption identifier.

[0058] In conjunction with the second aspect, in a possible implementation, performing billing processing according to a quota suspension identifier or a quota consumption identifier includes:

[0059] The service usage in the billing information is directly deducted from the corresponding account balance in the billing resource of the main CHF entity;

[0060] The method of this embodiment also includes:

[0061] If the cached billing information has a corresponding quota consumption identifier, the service usage in the billing information is directly deducted from the corresponding account of the first billing resource, and the locked account balance is released at the same time; or, if the cached billing information includes billing information without quota management, the billing information without quota management is written into the main CHF call list.

[0062] In a third aspect, an embodiment of the present application provides a first R-CHF entity. The first R-CHF entity includes a transceiver unit and a processing unit.

[0063] a transceiver unit, configured to receive a first charging request sent by a CTF entity,

[0064] A processing unit, configured to detect that the target CHF entity interaction related to the first charging request is abnormal, and perform abnormal charging processing;

[0065] The target CHF entity is the main CHF entity or the second R-CHF entity, the main CHF entity provides online quota management and billing call record generation; the second R-CHF entity is a CHF entity that provides relay for the CTF entity and the main CHF entity before the first R-CHF entity acts as a relay CHF entity.

[0066] In combination with the third aspect, in a possible implementation manner, the target CHF entity is a primary CHF entity corresponding to the first charging request, the first charging request is a charging resource creation request for creating a convergent charging session, and is used to request the creation of a charging interaction session between the CTF entity and the first R-CHF entity, and the processing unit is specifically used to:

[0067] Generate a first charging resource for charging interaction between the CTF entity and the first R-CHF entity; cache the charging information in the first charging request;

[0068] The transceiver unit is further configured to send a first charging response message for responding to the first charging request to the CTF entity, where the first charging response message includes an identifier of the first charging resource.

[0069] In combination with the third aspect, in a possible implementation, if the first charging request includes a quota request, the first response message includes suspended quota indication information or a granted quota, and the suspended quota indication information is used to instruct the CTF entity to continue the service according to the suspended quota management mode.

[0070] In combination with the third aspect, in a possible implementation, the first charging response message includes the granted quota, and the CTF entity receives usage of the granted quota, and the cached charging information includes a quota suspension identifier corresponding to the usage of the granted quota.

[0071] In conjunction with the third aspect, in a possible implementation manner, in terms of caching the billing information in the first billing request, the processing unit is specifically configured to:

[0072] The charging information in the first charging request is written into the first R-CHF bill or stored in the first charging resource.

[0073] In conjunction with the third aspect, in a possible implementation, the transceiver unit is further configured to:

[0074] When it is detected that the target CHF entity interaction related to the first billing request is normal, a second billing request is sent to the main CHF entity, where the second billing request is a second billing resource creation request, which is used to request the creation of a second billing resource for the billing interaction between the first R-CHF entity and the main CHF entity, or the second billing request is a third billing resource update or release request, which is used to request the update or release of the third billing resource for the billing interaction between the CTF and the main CHF entity.

[0075] In combination with the third aspect, in a possible implementation manner, the second charging request carries cached charging information.

[0076] Optionally, the cached billing information includes billing information, or includes billing information and a corresponding quota suspension identifier.

[0077] In conjunction with the third aspect, in a possible implementation, the transceiver unit is further configured to:

[0078] When the processing unit detects that the target CHF entity related to the first charging request interacts normally, the first R-CHF call record is sent to the main CHF entity. Here, the target CHF entity related to the first charging request is the main CHF entity.

[0079] In conjunction with the third aspect, in a possible implementation,

[0080] The transceiver unit is also used to send a notification message to the CTF entity before generating a second billing request, the notification message is used to instruct the CTF entity to restore quota management; receive a third billing request sent by the CTF entity, the third billing request carries a quota request and usage for restoring quota management; the second billing request includes the quota request and usage carried by the third billing request.

[0081] In conjunction with the third aspect, in a possible implementation, the target CHF is a primary CHF entity corresponding to the first charging request, the first charging request is a first charging resource update request or a first charging resource release request, which is used to request to update or release a first charging resource for charging interaction between the first R-CHF entity and the CTF entity, and the processing unit is specifically used to: cache charging information of the first charging request;

[0082] The transceiver unit is further configured to send a first charging response message in response to the first charging request to the CTF entity.

[0083] In combination with the third aspect, in a possible implementation, if the first charging request includes a quota request, the first response message includes suspended quota indication information or a granted quota, and the suspended quota indication information is used to instruct the CTF entity to continue the service according to the suspended quota management mode.

[0084] In combination with the third aspect, in a possible implementation, the cached billing information includes first billing information and a corresponding quota consumption identifier, or second billing information and a corresponding quota suspension identifier, the first billing information is the billing information that uses the available quota granted by the main CHF entity in the billing information, and the second billing information is the billing information that does not use the available quota granted by the main CHF entity in the billing information.

[0085] In conjunction with the third aspect, in a possible implementation, in terms of caching the billing information of the first billing request, the processing unit is further configured to:

[0086] The first billing information and the corresponding quota consumption identifier, or the second billing information and the corresponding quota suspension identifier are written into the first R-CHF call record or saved in the first billing resource.

[0087] In conjunction with the third aspect, in a possible implementation, the transceiver unit is further configured to:

[0088] When it is detected that the target CHF interaction related to the first charging request is normal, a second charging request is sent to the main CHF entity, and the second charging request is a second charging resource update request or a second charging resource release request, which is used to request to update or release the second charging resource of the charging interaction between the first R-CHF entity and the main CHF entity.

[0089] In conjunction with the third aspect, in a possible implementation, the transceiver unit is further configured to:

[0090] When the processing unit detects that the target CHF interaction related to the first charging request is normal, the first R-CHF call record is sent to the main CHF entity.

[0091] In combination with the third aspect, in a possible implementation, the second charging request carries the charging information and a corresponding quota suspension identifier or a quota consumption identifier.

[0092] In conjunction with the third aspect, in a possible implementation, the transceiver unit is further configured to:

[0093] Before generating the second charging request, a notification message is sent to the CTF entity, where the notification message is used to instruct the CTF entity to restore quota management; a third charging request sent by the CTF entity is received, where the third charging request carries a quota request and usage for restoring quota management; and the second charging request includes the quota request and usage carried by the third charging request.

[0094] In conjunction with the third aspect, in a possible implementation, the target CHF entity is a primary CHF entity corresponding to the first charging request, the first charging request is a one-time event charging request for online direct deduction or offline one-time event charging, and the processing unit is further used to: cache charging information of the first charging request;

[0095] The transceiver unit is further configured to send a first charging response message in response to the first charging request to the CTF entity.

[0096] In conjunction with the third aspect, in a possible implementation, in terms of caching the billing information of the first billing request, the processing unit is specifically used to: write the billing information and the corresponding online direct deduction indication information or the offline one-time event billing indication information into the first R-CHF call record;

[0097] The transceiver unit is further configured to send a first R-CHF call record to the main CHF entity when it is detected that the target CHF interaction related to the first charging request is normal.

[0098] In conjunction with the third aspect, in a possible implementation manner, the processing unit is specifically configured to:

[0099] The charging information of the first charging request and the corresponding online direct deduction indication information or offline one-time event charging indication information are stored in the first charging resource;

[0100] When it is detected that the target CHF interaction related to the first charging request is normal, a second charging request is generated, the second charging request is a one-time event charging request, and the second charging request carries charging information and corresponding online direct deduction indication information or offline one-time event charging indication information;

[0101] The transceiver unit is further configured to send a second charging request to the main CHF entity.

[0102] In combination with the third aspect, in a possible implementation manner, the target CHF entity is a second R-CHF entity, the first charging request is a first charging resource update request or a first charging resource release request, which is used to request to update or release a first charging resource for charging interaction between the second R-CHF entity and the CTF entity; and the processing unit is specifically used to:

[0103] generating a fourth charging resource between the CTF entity and the first R-CHF entity according to the first charging request, and using the first charging resource identifier as the identifier of the fourth charging resource; generating a second charging request according to the first charging request, the second charging request being used to request the creation of a second charging resource for charging interaction between the first R-CHF entity and the main CHF entity, and the second charging request carrying the identifier of the third charging resource;

[0104] The transceiver unit is further configured to send a second charging request to the primary CHF entity, and receive a second charging response message from the primary CHF entity in response to the second charging request; the second charging response message carries an identifier of a second charging resource;

[0105] The processing unit is further configured to generate a first charging response message for responding to the first charging request according to the second charging response message;

[0106] The transceiver unit is further configured to send a first charging response message to the CTF entity.

[0107] In a fourth aspect, an embodiment of the present application provides a main CHF entity, including a transceiver unit and a processing unit. The main CHF entity provides online quota management and billing call record generation.

[0108] The transceiver unit is further used to receive relevant billing information cached by the first R-CHF entity, where the cached relevant billing information is carried in a billing call bill or a billing message, and the cached relevant billing information includes the billing information and a corresponding quota suspension identifier or a quota consumption identifier;

[0109] The processing unit is used to perform billing processing according to the quota suspension identifier or the quota consumption identifier.

[0110] In conjunction with the fourth aspect, in a possible implementation manner, the processing unit is specifically configured to:

[0111] The service usage in the billing information is directly deducted from the corresponding account balance in the billing resource of the main CHF entity;

[0112] If the cached billing information has a corresponding quota consumption identifier, the service usage in the billing information is directly deducted from the corresponding account of the first billing resource, and the locked account balance is released at the same time; or,

[0113] If the cached billing information includes billing information without quota management, the billing information without quota management is written into the main CHF call list.

[0114] In a fifth aspect, an embodiment of the present application provides a first R-CHF entity, including a processor and a memory. The memory is used to store program code. The processor is used to call the program code stored in the memory to execute the method provided by the first aspect or any possible implementation of the first aspect.

[0115] In a sixth aspect, an embodiment of the present application provides a master CHF entity, including a processor and a memory. The memory is used to store program code. The processor is used to call the program code stored in the memory to execute the method provided in the second aspect or any possible implementation of the second aspect.

[0116] In the seventh aspect, an embodiment of the present application provides a computer storage medium, including computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes a method provided in any possible implementation of the first aspect, or a method provided in any possible implementation of the second aspect.

[0117] In an eighth aspect, an embodiment of the present application provides a computer program product. When the computer program product runs on a computer, it enables the computer to execute a method provided in any possible implementation of the first aspect, or a method provided in any possible implementation of the second aspect.

[0118] In a ninth aspect, an embodiment of the present application provides a method for handling charging exceptions, the method being applied to a charging system, the charging system including a first R-CHF entity, a second R-CHF entity, a CTF entity, and a main CHF entity, the method including:

[0119] The CTF entity sends a first charging request to the first R-CHF entity;

[0120] The first R-CHF entity determines that the target CHF entity interaction related to the first charging request is abnormal, and performs abnormal charging processing;

[0121] The target CHF entity is the main CHF entity or the second R-CHF entity. The main CHF entity provides online quota management and billing call record generation. The second R-CHF entity is a CHF entity that provides relay for the CTF entity and the main CHF entity before the first R-CHF entity acts as a relay CHF entity.

[0122] In a tenth aspect, an embodiment of the present application provides a charging system, the charging system comprising a first R-CHF entity, a second R-CHF entity, a CTF entity and a main CHF entity,

[0123] The CTF entity is configured to send a first charging request to the first R-CHF entity;

[0124] The first R-CHF entity is used to determine that the target CHF entity interaction related to the first charging request is abnormal, and perform abnormal charging processing;

[0125] The target CHF entity is the main CHF entity or the second R-CHF entity. The main CHF entity provides online quota management and billing call record generation. The second R-CHF entity is a CHF entity that provides relay for the CTF entity and the main CHF entity before the first R-CHF entity acts as a relay CHF entity.

[0126] It can be understood that the specific description of the CTF entity, the first R-CHF entity and the main CHF entity described in the ninth aspect or the tenth aspect is referred to the method described in any one of the first aspect and the method described in any one of the second aspect, which will not be described here. The first R-CHF entity described in the third aspect or the fifth aspect provided above is used to execute any method provided in the first aspect, the main CHF entity described in the fourth aspect or the sixth aspect is used to execute any method provided in the second aspect, and the computer storage medium described in the seventh aspect and the computer program product described in the eighth aspect are both used to implement any method provided in the first aspect or any method provided in the second aspect. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method, which will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0127] Figure 1 A schematic diagram of a system architecture;

[0128] Figure 2 A schematic diagram of a system architecture provided for an embodiment of the present application;

[0129] Figure 3 A flowchart of a method for handling billing exceptions provided in an embodiment of the present application;

[0130] Figure 4 A flowchart of another method for handling billing exceptions provided in an embodiment of the present application;

[0131] Figure 5 An interactive flow chart of a method for handling billing exceptions provided in an embodiment of the present application;

[0132] Figure 6 An interactive flow chart of another method for handling billing exceptions provided in an embodiment of the present application;

[0133] Figure 7 An interactive flow chart of another method for handling billing exceptions provided in an embodiment of the present application;

[0134] Figure 8 An interactive flow chart of another method for handling billing exceptions provided in an embodiment of the present application;

[0135] Fig. 9 An interactive flow chart of another method for handling billing exceptions provided in an embodiment of the present application;

[0136] Fig.10 A schematic diagram of the structure of a first R-CHF entity provided in an embodiment of the present application;

[0137] Fig.11A schematic diagram of the structure of a main CHF entity provided in an embodiment of the present application;

[0138] Fig.12 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0139] The terms "first", "second", "third", "fourth" and the like in the specification, claims and drawings of this application are used to distinguish different objects rather than to describe a specific order.

[0140] "Multiple" means two or more. "And / or" describes the association relationship of the associated objects, indicating that there are three relationships. For example, A and / or B means: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0141] The embodiments of the present application are described below in conjunction with the accompanying drawings.

[0142] See also Figure 2 , Figure 2 A schematic diagram of a system architecture provided in an embodiment of the present application. Figure 2 As shown, the system includes a CTF entity 201 , an R-CHF entity 202 , a main CHF entity 203 , an ABMF entity 204 , a CGF entity 205 and an RF entity 206 .

[0143] Optionally, the relay R-CHF is a local CHF, an edge CHF or a service CHF.

[0144] Among them, for a certain user equipment, the CHF that provides online quota management and / or billing call record generation for the user is called the main CHF entity 203 of the user equipment. The main CHF entity 203 is connected with the ABMF entity 204, the RF entity 206, and the CGF entity 205 to perform quota management, call record generation, account balance management, etc. The main CHF entity 203 is connected with the CRM, recharge center, billing capability service system, accounting system, etc. according to the contract information of the user equipment to manage the account information and contract information of the user equipment. The main CHF entity 203 will not change with the change of the location of the user equipment.

[0145] For a certain user equipment, when the user uses the service beyond the processing scope of the main CHF entity 203 of the user equipment, the main CHF entity 203 cannot provide billing; the R-CHF entity generates a first billing resource for the CTF entity, establishes and maintains the association between the second billing resource generated by the main CHF entity and the first billing resource, and uses the first billing resource and the second billing resource to enable the main CHF entity to bill for the service provided by the CTF entity. Among them, the R-CHF entity 202 is a CHF entity that is close to the user equipment and provides billing for the user equipment. Optionally, the R-CHF entity 202 and the main CHF entity 203 belong to the same operator or belong to different operators. As the user moves or the user accesses a change in the service, the R-CHF entity 202 may change.

[0146] In an example, the functions of the R-CHF entity 202 include, but are not limited to: discovery of the main CHF entity 203, forwarding of billing information, generation of R-CHF billing call records, and abnormal billing processing capabilities when the main CHF entity 203 is abnormal, such as abnormal billing processing when the main CHF entity 203 is congested, the main CHF entity 203 is unreachable, and the communication quality with the main CHF entity 203 is reduced (such as increased transmission delay and jitter). A series of methods are used to achieve abnormal perception and abnormal billing processing (such as: billing retransmission, billing information caching, billing method conversion, congestion control, abnormal recovery, and abnormal period billing information processing, etc.); when the original R-CHF entity is abnormal, the abnormal billing processing capabilities of the new R-CHF entity after switching.

[0147] The implementation process of this application is described in detail below.

[0148] See also Figure 3 , Figure 3 A flowchart of a method for handling charging anomalies provided in an embodiment of the present application is shown. The method is applied to a first R-CHF entity. The first R-CHF entity may be Figure 2 R-CHF entity 202 in. Figure 3 As shown, the method includes:

[0149] S301. A first R-CHF entity receives a first charging request sent by a CTF entity.

[0150] In one example, the first billing request is sent by the CTF entity in a scenario where no billing session is established between the CTF entity and the first R-CHF entity, and no billing session is established between the first R-CHF entity and the main CHF entity. At this time, the first billing request is a first billing resource creation request, which is used to request the creation of a first billing resource for billing interaction between the CTF entity and the first R-CHF entity.

[0151] In another example, the first billing request is sent by the CTF entity in a scenario where a billing session has been established between the CTF entity and the first R-CHF entity, and a billing session has been established between the first R-CHF entity and the main CHF entity. At this time, the first billing request is a second billing resource update request or a second billing resource release request, which is used to request to update or release the second billing resource for the billing interaction between the first R-CHF entity and the CTF entity.

[0152] In another example, the first charging request is a one-time event charging request for online direct deduction or offline one-time event charging sent by the CTF entity in a scenario where a charging session has been established between the CTF entity and the first R-CHF entity, and a charging session has been established between the first R-CHF entity and the main CHF entity.

[0153] In another example, the first billing request is a first billing resource update request or a first billing resource release request sent by the CTF entity to the first R-CHF in a scenario where a billing session has been established between the CTF entity and the second R-CHF entity, and a billing session has been established between the second R-CHF entity and the main CHF entity, and is used to request to update or release the first billing resource for the converged billing interaction between the first R-CHF entity and the CTF entity.

[0154] In another example, the first charging request is a scenario in which a charging session has been established between the CTF entity and the primary CHF entity, and the CTF entity sends a first charging resource creation request to the first R-CHF entity, wherein the first charging request is used to request the creation of a first charging resource for charging interaction between the CTF entity and the first R-CHF entity.

[0155] S302: When the first R-CHF entity determines that the target CHF entity interaction related to the first charging request is abnormal, the first R-CHF entity performs abnormal charging processing.

[0156] In a possible implementation, the target CHF entity is the primary CHF entity corresponding to the first charging request, and the first charging request is a first charging resource creation request, which is used to request the creation of a charging interaction session between the CTF entity and the first R-CHF entity. This situation is for two scenarios, scenario 1: no charging session is established between the CTF entity and the first R-CHF entity, and no charging session is established between the first R-CHF entity and the primary CHF entity; scenario 2: a charging session has been established between the CTF entity and the primary CHF entity.

[0157] For the above two scenarios, the first R-CHF entity performs abnormal charging processing, including:

[0158] The first R-CHF entity generates a first billing resource corresponding to the first billing request, and allocates a billing resource identifier for the first billing resource; the first R-CHF entity caches the billing information in the first billing request, and sends a first billing response message for responding to the first billing request to the CTF entity, the first billing response message including the identifier of the first billing resource. Optionally, the first billing response message includes suspended quota indication information or a granted quota, the suspended quota indication information may be determined based on the first indication information carried by the first billing request, the first indication information is used to indicate whether the CTF entity supports the suspended quota management capability, and the suspended quota indication information is used to instruct the CTF entity to continue the service according to the suspended quota management mode.

[0159] Specifically, for scenario 1: after receiving the first charging request, the first R-CHF entity generates a first charging resource identifier. The charging information in the first charging request includes charging information with quota management and / or charging information without quota management.

[0160] For the billing information without quota management, the first R-CHF entity caches the billing information without quota management. The cached billing information includes offline one-time event billing information, such as service type, service start time, etc. In one example, the first R-CHF entity directly caches the billing information without quota management in a first billing resource locally (such as local memory or local storage); or the first R-CHF entity generates a first R-CHF call record, and the first R-CHF call record includes the billing information without quota management.

[0161] For the billing information with quota management, since the first R-CHF entity has not established a billing session with the main CHF entity, that is, the main CHF entity has not allocated a quota to the user, the billing information with quota management includes a quota application, then:

[0162] If the CTF entity supports the ability to suspend quota management, the first R-CHF entity suspends the quota management of the service and caches the billing information with quota management. In one example, the first R-CHF entity directly caches the billing information with quota management in a first billing resource locally (such as local memory or local storage); or the first R-CHF entity generates a first R-CHF call sheet, and the first R-CHF entity call sheet includes the billing information with quota management. At this time, the first billing response message also includes suspended quota indication information, and the suspended quota indication information is used to instruct the CTF entity to continue the service in accordance with the suspended quota management mode. After the subsequent CTF entity reports the usage of the service after the quota is suspended to the first R-CHF entity, the first R-CHF entity caches the billing information of the suspended quota (such as: service usage) and the corresponding quota suspension identifier.

[0163] If the CTF entity does not support the suspension quota management capability, the first R-CHF entity performs a quota granting operation. Since the first R-CHF entity does not have the account information of the user, the granted quota is a virtual granted quota, and the billing information with quota management is cached. In one example, the first R-CHF entity directly caches the billing information with quota management in a first billing resource locally (such as local memory or local storage), or the first R-CHF entity generates a first R-CHF call sheet, and the first R-CHF entity call sheet includes the billing information with quota management. At this time, the first billing response message also includes the granted quota. After the CTF entity receives the first billing response message, it manages the service according to the granted quota and collects quota usage information. After the subsequent CTF entity reports the collected quota usage information to the first R-CHF entity, the first R-CHF caches the billing information with quota management (such as quota usage) and the quota suspension flag. For example, the quota granted by the first R-CHF entity is 30M. After the CTF entity uses up the granted 30M quota (the collected quota usage is 30M at this time), the CTF entity reports the quota usage of 30M to the first R-CHF entity; after receiving the quota usage reported by the CTF, the first R-CHF entity saves the usage of 30M and the corresponding quota suspension flag in the cached billing information.

[0164] For scenario 2: the first billing request also carries the third billing resource related information generated by the main CHF entity for the CTF entity, such as the third billing resource identifier. After receiving the first billing request, the first R-CHF entity creates the first billing resource between the CTF entity and the first R-CHF entity based on the information carried in the first billing request, and caches the third billing resource related information generated by the main CHF entity carried in the first billing request. The billing information in the first billing request includes billing information with quota management and / or billing information without quota management.

[0165] For the billing information without quota management, the first R-CHF entity caches the billing information without quota management. The cached billing information includes offline one-time event billing information, such as offline service usage, offline service information, etc. In one example, the first R-CHF entity directly caches the billing information without quota management in a first billing resource locally (such as local memory or local storage); or the first R-CHF entity generates a first R-CHF call record.

[0166] For the billing information with quota management, since the CTF entity has established a billing session with the main CHF entity, that is, the main CHF entity may have allocated a quota to the user, the billing information with quota management includes quota application and / or quota usage. The first R-CHF entity caches the billing information with quota management and the corresponding quota consumption identifier or quota suspension identifier. If the corresponding quota suspension identifier is cached, the main CHF entity needs to be notified to release the granted quota later. In one example, the first R-CHF entity directly caches the billing information with quota management and the corresponding quota consumption identifier or quota suspension identifier in a first billing resource locally (such as local memory or local storage), or the first R-CHF entity generates a first R-CHF call record, and the first R-CHF entity call record includes the billing information with quota management and the corresponding quota consumption identifier or quota suspension identifier. At the same time,

[0167] If the CTF entity supports the suspended quota management capability, the first R-CHF entity suspends the quota management of the service. At this time, the first charging response message also includes suspended quota indication information, which is used to instruct the CTF entity to continue the service in accordance with the suspended quota management mode. After the subsequent CTF entity reports the usage of the service after the quota is suspended to the first R-CHF entity, the first R-CHF entity caches the charging information of the suspended quota (such as: service usage) and the corresponding quota suspension identifier.

[0168] If the CTF entity does not support the suspended quota management capability, the first R-CHF entity performs a quota granting operation. Since the first R-CHF entity does not have the account information of the user, the granted quota is a virtual granted quota. After the CTF entity receives the first charging response message, it manages the service according to the granted quota and collects quota usage information. After the subsequent CTF entity reports the collected quota usage information to the first R-CHF entity, the first R-CHF caches the quota management-related charging information (such as quota usage) and the quota suspension flag.

[0169] In another possible implementation, the target CHF entity is the primary CHF entity corresponding to the first charging request, and the first charging request is sent by the CTF entity in a scenario in which a charging session has been established between the CTF entity and the first R-CHF entity, and a charging session has been established between the first R-CHF entity and the primary CHF entity. At this time, the first charging request is a first charging resource update request or a first charging resource release request, which is used to request to update or release the first charging resource for the charging interaction between the first R-CHF entity and the CTF entity.

[0170] The first R-CHF entity performs abnormal charging processing, including:

[0171] For the billing information without quota management, the first R-CHF entity caches the billing information without quota management. The cached billing information includes offline one-time event billing information, such as offline service usage, offline service information, etc. In one example, the first R-CHF entity directly caches the billing information without quota management in a first billing resource locally (such as local memory or local storage); or the first R-CHF entity generates a first R-CHF call record.

[0172] For the billing information with quota management, since a billing session has been established with the main CHF entity, that is, the main CHF entity may have allocated a quota to the user, the billing information with quota management includes quota application and / or quota usage. The first R-CHF entity caches the billing information with quota management and the corresponding quota consumption identifier or quota suspension identifier. If the corresponding quota suspension identifier is cached, CHF needs to be notified to release the granted quota later. In one example, the first R-CHF entity directly caches the billing information with quota management and the corresponding quota consumption identifier or quota suspension identifier in a first billing resource locally (such as local memory or local storage), or the first R-CHF entity generates a first R-CHF call record, and the first R-CHF entity call record includes the billing information with quota management and the corresponding quota consumption identifier or quota suspension identifier. At the same time,

[0173] In the case where the first R-CHF entity has no available quota, if the CTF entity supports the suspended quota management capability, the first R-CHF entity suspends the quota management of the service. At this time, the first charging response message also includes suspended quota indication information, and the suspended quota indication information is used to instruct the CTF entity to continue the service according to the suspended quota management mode. After the subsequent CTF entity reports the usage of the service after the quota is suspended to the first R-CHF entity, the first R-CHF entity caches the charging information of the suspended quota (such as: service usage) and the corresponding quota suspension identifier.

[0174] In the case where the first R-CHF entity has no available quota, if the CTF entity does not support the ability to suspend quota management, the first R-CHF entity performs a quota granting operation. Since the first R-CHF entity does not have the account information of the user, the granted quota is a virtual granted quota. After the CTF entity receives the first charging response message, it manages the service according to the granted quota and collects quota usage information. After the subsequent CTF entity reports the collected quota usage information to the first R-CHF entity, the first R-CHF caches the quota management-related charging information (such as quota usage) and the quota suspension flag.

[0175] In the case where the first R-CHF entity has available quota, if the CTF entity supports the suspended quota management capability, the first R-CHF entity may handle it in the following manner:

[0176] Mode 1: The first R-CHF entity suspends the quota management of the service, that is, the current available quota is not used, and the main CHF entity is notified to release the quota after the subsequent main CHF entity is restored. The exception handling of the first R-CHF entity in this scenario is the same as the above-mentioned case where the first R-CHF entity has no available quota.

[0177] Mode 2: The first R-CHF entity provides quota granting and deduction for the service based on the available quota; suspends the quota management of the service after the available quota is used up; the billing information with quota management includes two parts: first billing information and second billing information, wherein the first billing information is the billing information using the available quota granted by the main CHF entity, and the second billing information is the billing information not using the available quota granted by the main CHF entity; the first R-CHF entity caches the billing information with quota management, including: caching the first billing information and the corresponding quota consumption identifier, and caching the second billing information and the corresponding quota suspension identifier.

[0178] In the case where the first R-CHF entity has available quota, if the CTF entity does not support the suspended quota management capability, the first R-CHF entity may handle it in the following manner:

[0179] Mode 1: The first R-CHF entity grants a virtual quota, that is, the current available quota is not used, and the primary CHF entity is notified to release the quota after the subsequent primary CHF entity is restored. In this scenario, after receiving the usage information of the virtual quota reported by the subsequent CTF entity, the first R-CHF entity caches the usage information and the corresponding quota consumption identifier;

[0180] Mode 2: The first R-CHF entity provides quota granting and deduction for the service based on the available quota; grants the virtual quota after the available quota is used up; the billing information with quota management includes two parts: the first billing information and the second billing information, wherein the first billing information is the billing information using the available quota granted by the main CHF entity, and the second billing information is the billing information (corresponding to the virtual quota) without using the available quota granted by the main CHF entity; the first R-CHF entity caches the billing information with quota management, including: caching the first billing information and the corresponding quota consumption identifier, and caching the second billing information and the corresponding quota suspension identifier.

[0181] It should be understood that the available quota of the first R-CHF entity is the quota granted by the main CHF entity before the exception.

[0182] In a possible implementation, the manner in which the first R-CHF entity detects abnormal interaction with the target CHF entity (ie, the main CHF entity) includes:

[0183] 1. The first R-CHF entity determines that the interaction between the first R-CHF entity and the main CHF entity is abnormal according to the application layer congestion indication returned by the main CHF entity or when it detects that the delay of the main CHF entity returning the charging response message increases, that is, when it detects that the main CHF entity is congested.

[0184] 2. When the first R-CHF entity detects that the transport layer connection between the first R-CHF entity and the main CHF entity is interrupted, that is, when the main CHF entity is detected to be unreachable, it is determined that the interaction between the first R-CHF entity and the main CHF entity is abnormal.

[0185] 3. The first R-CHF entity determines, based on the transport layer congestion control mechanism or jitter, that the transport layer of the first R-CHF entity and the transport layer of the main CHF entity are congested, that is, the communication quality between the first R-CHF entity and the main CHF entity is degraded, and further determines that the interaction between the first R-CHF entity and the main CHF entity is abnormal.

[0186] It should be understood that the abnormal interaction between the first R-CHF entity and the main CHF entity means that after the above situation occurs, there is no backup main CHF.

[0187] Before performing abnormal billing processing, if the CTF entity and the first R-CHF entity belong to different operators, the first R-CHF entity determines whether to authorize the user equipment to use the current service according to the operator configuration information. When it is determined that the user equipment is authorized to use the current service, the above abnormal billing processing is performed; when it is determined that the user equipment is not authorized to use the current service, the above abnormal billing processing is not performed.

[0188] In a possible implementation, the method of this embodiment further includes:

[0189] When the first R-CHF entity detects that the target CHF entity interaction related to the first charging request is normal, the first R-CHF entity generates a second charging request and sends the second charging request to the main CHF entity. The second charging request is a first charging resource creation request for requesting to create a first charging resource for the charging interaction between the first R-CHF entity and the main CHF entity, or the second charging request is a charging resource update request or release request for requesting to update or release a third charging resource for the charging interaction between the CTF entity and the main CHF entity.

[0190] Optionally, if the cached billing information is cached in the first billing resource locally in the first R-CHF entity, the second billing request includes the cached billing information, that is, the second billing request carries the cached billing information and the corresponding quota consumption identifier or quota suspension identifier. Optionally, if the first R-CHF entity has an available quota allocated by the main CHF entity during the abnormal period but it is not used, the second billing request also includes release indication information for indicating the main CHF entity to release the quota granted by the main CHF entity to the first R-CHF entity; Optionally, if the first R-CHF entity has a quota application for CTF, the second billing request also includes a quota application.

[0191] In a possible implementation, this embodiment further includes:

[0192] When the first R-CHF entity detects that the target CHF entity interaction related to the first charging request is normal, if the cached charging information is cached in the first R-CHF call record, then:

[0193] Method 1: The first R-CHF entity sends a second charging request to the primary CHF, where the second charging request carries the charging information stored in the first R-CHF call record;

[0194] Method 2: The first R-CHF entity sends the first R-CHF call record to the primary CHF entity alone, regardless of whether it sends the second charging request to the primary CHF entity.

[0195] Specifically, the first R-CHF sends the first R-CHF bill to the main CHF entity through a file transfer protocol (FTP) or other methods. The first R-CHF entity may also carry the storage address of the first R-CHF bill in the charging request sent to the main CHF entity, so that the main CHF entity obtains the first R-CHF bill based on the storage address.

[0196] In a possible implementation, the method of this embodiment further includes:

[0197] Before generating the second charging request, the first R-CHF entity sends a notification message to the CTF entity, where the notification message is used to instruct the CTF entity to resume quota management; the first R-CHF entity receives a third charging request sent by the CTF entity, where the third charging request carries a quota request and usage for resuming quota management; the second charging request includes the quota request and usage carried by the third charging request.

[0198] It should be noted that the usage here refers to the usage of the suspended quota or the usage of the granted quota.

[0199] In a possible implementation, the target CHF entity is a primary CHF entity corresponding to a first charging request, the first charging request is an online direct deduction (i.e., Immediate Event Charging (IEC)) request or an offline one-time event charging (i.e., Post Event Charging (PEC)) request, and the first R-CHF entity performs abnormal charging processing, including:

[0200] The first R-CHF entity caches the charging information of the first charging request; and sends a first charging response message in response to the first charging request to the CTF entity.

[0201] In a possible implementation manner, the first R-CHF entity caches the charging information of the first charging request, including:

[0202] The first R-CHF entity writes the charging information and the corresponding online direct deduction indication information or the offline one-time event charging indication information into the first R-CHF bill, and when the first R-CHF entity detects that the target CHF interaction related to the first charging request is normal, the first R-CHF entity sends the first R-CHF bill to the main CHF entity. The first R-CHF bill includes the charging information and the corresponding online direct deduction indication information or the offline one-time event charging indication information.

[0203] The first R-CHF sends the first R-CHF bill to the main CHF entity through FTP or other methods. The first R-CHF entity may also carry the storage address of the first R-CHF bill in the charging request sent to the main CHF entity, so that the main CHF entity obtains the first R-CHF bill based on the storage address.

[0204] In a possible implementation, the method of this embodiment further includes:

[0205] The first R-CHF entity saves the billing information and the corresponding online direct deduction indication information or the offline one-time event billing indication information in the first billing resource; when detecting that the target CHF interaction related to the first billing request is normal, the first R-CHF entity generates a second billing request, which is a one-time event billing request, and the second billing request carries the billing information and the corresponding online direct deduction indication information or the offline one-time event billing indication information; the first R-CHF entity sends the second billing request to the main CHF entity.

[0206] After receiving the second billing request, if the second billing request includes online direct deduction indication information, the main CHF entity deducts the account balance according to the online usage of the billing information; if the second billing information includes offline one-time event billing indication information, the main CHF entity writes the offline one-time event billing information in the billing information into the main CHF call record.

[0207] In a possible implementation, the target CHF entity is a second R-CHF entity corresponding to the first charging request, and the second R-CHF entity is a CHF entity that provides relay for the CTF entity and the main CHF entity before the first R-CHF entity acts as a relay CHF entity; the first charging request is a first charging resource update request or a first charging resource release request, which is used to request to update or release a first charging resource for charging interaction between the second R-CHF entity and the CTF entity, and the first charging request carries an identifier of the first charging resource; the first R-CHF entity performs abnormal charging processing, including:

[0208] The first R-CHF entity creates a fourth charging resource between the CTF entity and the first R-CHF entity according to the first charging request, and uses the identifier of the first charging resource as the identifier of the fourth charging resource; the first R-CHF entity generates a second charging request according to the first charging request; sends the second charging request to the main CHF entity, because the first R-CHF entity cannot interact with the second R-CHF entity to obtain the charging resource identifier allocated by the main CHF for the user charging on the second R-CHF entity, so the second charging request is a second charging resource creation request, using The second billing resource for billing interaction between the first R-CHF entity and the main CHF entity is requested to be created, and the second billing resource creation request carries quota management billing information or no quota management billing information; the main CHF determines the existing billing resource identifier (i.e., the billing resource identifier allocated by the main CHF for the billing of the user on the second R-CHF) according to the user identifier, billing ID and other information in the second billing request, then performs billing processing (such as granting quota, deducting quota usage, writing main CHF call records, etc.), and returns the existing billing resource identifier. The first R-CHF entity receives the second billing response message of the main CHF entity in response to the second billing request; generates a first billing response message for responding to the first billing request according to the second billing response message; and the first R-CHF entity sends the first billing response message to the CTF entity.

[0209] When the interaction between the CTF entity and the second R-CHF entity is abnormal, switching from the second R-CHF entity to the first R-CHF entity is achieved in the above manner, which can ensure normal charging.

[0210] In a possible implementation, the method of this embodiment further includes:

[0211] If the first R-CHF entity detects that the billing resource identifier between the CTF entity and the second R-CHF entity is not a unique resource identifier locally, that is, the billing resource identifier between the CTF entity and the second R-CHF entity conflicts with other billing resource identifiers in the first R-CHF entity, the first R-CHF entity generates a new billing resource identifier, uses the new billing resource identifier as the identifier of the third billing resource, and returns it to the CTF entity to replace the current billing resource identifier to avoid conflict.

[0212] It can be seen that in the solution of the present application, for the abnormal interaction between the first R-CHF entity and the target CHF entity, different abnormal billing processing methods are adopted to ensure normal billing and avoid losses to the operator.

[0213] See also Figure 4 , Figure 4 A flowchart of another method for handling abnormal billing provided in an embodiment of the present application. The method is applied to a main CHF entity. The main CHF entity provides online quota management and billing call record generation. Figure 4 As shown, the method also includes:

[0214] S401: A primary CHF entity receives cached charging related information sent by a first R-CHF entity.

[0215] The cached billing related information is sent to the main CHF entity in the form of a call record or carried in a billing request to the main CHF, and the cached billing related information includes billing information and a corresponding quota suspension identifier or quota consumption identifier. The billing information includes billing information with quota management and / or billing information without quota management.

[0216] Specifically, when the cached billing-related information is sent to the main CHF entity in the form of a call record, the call record is sent to the main CHF entity via FTP or other means, or the first R-CHF entity can also carry the storage address of the first R-CHF call record in the billing request sent to the main CHF entity, so that the main CHF entity obtains the call record based on the storage address.

[0217] S402: The main CHF entity performs billing processing according to the quota suspension flag or the quota consumption flag.

[0218] Specifically, for the billing information with quota management cached by the first R-CHF entity sent through the call bill or the second billing request, for the billing information with a quota suspension mark, the main CHF entity directly deducts the service usage in the billing information from the account balance corresponding to the first billing resource. For the billing information with a quota consumption mark, the main CHF entity performs a quota consumption deduction operation (such as: deducting the balance, releasing the locked quota, etc.). It should be understood that the account balance locked by the main CHF entity is the quota granted by the main CHF entity to the first R-CHF entity before the interaction is abnormal. In one example, when the cached billing information includes release indication information, the main CHF entity also releases the locked account balance. Among them, the release indication information is used to instruct the main CHF entity to release the locked account balance, that is, to instruct the main CHF entity to release the quota granted to the first R-CHF entity before the interaction is abnormal.

[0219] For the billing information without quota management, the primary CHF entity writes the billing information without quota management into the primary CHF call record.

[0220] In one example, when the second billing request is a second billing resource creation request, used to request the creation of a second billing resource for billing interaction between the first R-CHF entity and the main CHF entity, the main CHF entity, when performing the above operation, also creates a second billing resource or binds it to an existing billing resource, and sends an identifier of the second billing resource to the first R-CHF entity.

[0221] It can be seen that in the solution of the present application, in the case of abnormal interaction between the first R-CHF entity and the main CHF entity, the main CHF entity can ensure normal billing by adopting the above processing method to avoid losses to the operator.

[0222] See also Figure 5 , Figure 5 An interactive flowchart of a method for handling billing exceptions provided in an embodiment of the present application. Figure 5 The illustrated embodiment is for the scenario where no charging session is established between the CTF entity and the first R-CHF entity and no charging session is established between the first R-CHF entity and the main CHF entity. Figure 5 As shown, the method includes:

[0223] S501. A CTF entity sends a first charging request to a first R-CHF entity.

[0224] The first charging request is a charging resource creation request for creating a converged charging session, which is used to request to establish a charging interaction session between the CTF entity and the first R-CHF entity. The first charging request includes charging information and first indication information. The first indication information is used to indicate whether the CTF entity supports the suspension quota management capability.

[0225] In one example, the billing information is billing information with quota management or billing information without quota management. In another example, the billing information includes billing information with quota management and billing information without quota management.

[0226] S502: The first R-CHF entity detects that the main CHF entity is abnormal, and performs abnormal billing processing.

[0227] In a possible implementation, the manner in which the first R-CHF entity detects abnormal interaction with the target CHF entity (ie, the main CHF entity) includes:

[0228] 1. The first R-CHF entity determines that the interaction between the first R-CHF entity and the main CHF entity is abnormal according to the application layer congestion indication returned by the main CHF entity or when it detects that the delay of the main CHF entity returning the charging response message increases, that is, when it detects that the main CHF entity is congested.

[0229] 2. When the first R-CHF entity detects that the transport layer connection between the first R-CHF entity and the main CHF entity is interrupted, that is, when the main CHF entity is detected to be unreachable, it is determined that the interaction between the first R-CHF entity and the main CHF entity is abnormal.

[0230] 3. The first R-CHF entity determines, based on the transport layer congestion control mechanism or jitter, that the transport layer of the first R-CHF entity and the transport layer of the main CHF entity are congested, that is, the communication quality between the first R-CHF entity and the main CHF entity is degraded, and further determines that the interaction between the first R-CHF entity and the main CHF entity is abnormal.

[0231] It should be understood that the abnormal interaction between the first R-CHF entity and the main CHF entity means that after the above situation occurs, there is no backup main CHF.

[0232] If the CTF entity and the first R-CHF entity belong to different operators, the first R-CHF entity determines whether to authorize the user equipment to use the current service according to the operator configuration information. When it is determined that the user equipment is authorized to use the current service, the first R-CHF entity generates a charging resource identifier for the CTF entity and performs the following abnormal charging process. When it is determined that the user equipment is not authorized to use the current service, the following abnormal charging process is not performed.

[0233] Specifically, the first R-CHF entity performs abnormal charging processing, which specifically includes:

[0234] For the billing information without quota management, the first R-CHF entity caches the billing information without quota management. The cached billing information includes offline one-time event billing information, such as offline service usage, offline service information, etc. In one example, the first R-CHF entity directly caches the billing information without quota management in a first billing resource locally (such as local memory or local storage); or the first R-CHF entity generates a first R-CHF call bill, and the first R-CHF call bill includes the billing information without quota management.

[0235] For the billing information with quota management, if the CTF entity supports the ability to suspend quota management, the first R-CHF entity suspends the quota management of the service and caches the billing information with quota management. In one example, the first R-CHF entity directly caches the billing information with quota management in a first billing resource locally (such as a local memory or local storage), or the first R-CHF entity generates a first R-CHF call sheet, and the first R-CHF entity call sheet includes the billing information with quota management.

[0236] If the CTF entity does not support the suspension quota management capability, the first R-CHF entity performs a quota granting operation and caches the quota-managed billing information. In one example, the first R-CHF entity directly caches the quota-managed billing information in a first billing resource locally (such as a local memory or a local storage), or the first R-CHF entity generates a first R-CHF call sheet, and the first R-CHF entity call sheet includes the quota-managed billing information.

[0237] After the CTF entity receives the first charging response message, it collects the usage of the granted quota; when the first R-CHF entity receives the usage reported by the CTF entity, the cached information also includes the quota suspension flag corresponding to the usage. For example, the quota granted by the first R-CHF entity is 30M, and the usage collected by the CTF entity is 20M. The CTF entity transmits the information of the usage of 20M to the first R-CHF entity; the first R-CHF entity receives the information of the usage of 20M, and in the cached charging information, the charging information corresponding to 20M is marked as quota suspension through the quota suspension flag.

[0238] S503: The first R-CHF entity sends a first charging response message to the CTF entity.

[0239] The first charging response message is used to respond to the first charging request. The first charging response message includes an identifier of a first charging resource for a CTF entity generated by the first R-CHF entity. Optionally, for the charging information with quota management in the charging information, if the CTF entity supports the suspended quota management capability, the first charging response message also includes suspended quota indication information, and the suspended quota indication information is used to instruct the CTF entity to continue processing the service in the suspended quota management mode; if the CTF entity does not support the suspended quota management capability, the first charging response message also includes the quota granted by the first R-CHF entity.

[0240] S504: The CTF entity processes the service according to the first charging response message.

[0241] Wherein, processing the service includes collecting offline one-time event billing information. Optionally, if the first billing response message includes quota suspension indication information, the CTF collects the usage of the quota suspension. Optionally, when the first billing response message includes the quota granted by the first R-CHF entity, the CTF entity monitors the usage of the granted quota and records the quota usage.

[0242] S505: The first R-CHF entity detects that the main CHF entity is normal.

[0243] S506: The first R-CHF entity sends a charging message to the CTF entity.

[0244] The charging message is used to instruct the CTF entity to resume the suspended quota management. Optionally, the charging message is sent by a charging notification message or a charging response. It should be understood that the charging notification message is actively sent by the first R-CHF entity to the CTF entity. The charging message is sent by a charging response, which means that the charging message is carried in the charging response sent by the first R-CHF entity to the CTF entity.

[0245] S507: The CTF entity sends a third charging request to the first R-CHF entity.

[0246] The third charging request is used for a quota request, and includes the applied quota amount. Optionally, the third charging request also includes the usage of the quota when the quota is suspended.

[0247] S508: The first R-CHF entity sends a second charging request to the main CHF entity.

[0248] Among them, the second billing request is a billing resource creation request for creating a converged billing session, which is used to request the establishment of a billing interaction session between the first R-CHF entity and the main CHF entity. If the first R-CHF entity caches the billing information and the corresponding quota suspension identifier in the first billing resource, the second billing request also includes the billing information cached by the first R-CHF entity, that is, the billing information and the corresponding quota suspension identifier. If the first R-CHF entity receives a third billing request sent by the CTF entity after resuming the suspended quota management, the second billing request also includes the quota request and usage carried by the third billing request. It should be pointed out that the usage here refers to the usage of the suspended quota, or the usage of the granted quota.

[0249] Since the main CHF entity is unreachable, the first R-CHF entity needs to obtain the address of the main CHF entity to interact with the main CHF entity.

[0250] Optionally, the first R-CHF entity determines the address of the main CHF entity in the following manner:

[0251] Method 1: The first R-CHF entity determines the address of the main CHF entity according to the identifier of the CTF entity. In one example, the first R-CHF entity queries a correspondence table according to the identifier of the CTF entity to determine the address of the main CHF entity, wherein the correspondence table is a correspondence table of the identifier of the CTF entity, the identifier of the main CHF entity, and the address of the main CHF entity.

[0252] Method 2: The first R-CHF entity determines the address of the main CHF entity according to the location information of the user equipment. In one example, the first R-CHF entity determines the location of the user equipment according to the location information of the user equipment, and then determines the main CHF entity that provides billing for the area to which the location of the user equipment belongs, and obtains the address of the main CHF entity.

[0253] Mode 3: The first R-CHF entity determines the address of the primary CHF according to the service information used by the user equipment; the primary CHF is a CHF entity that provides billing for the service used by the user equipment.

[0254] It should be understood that the above correspondence table, the coverage area of ​​the CHF and the service information that the CHF can provide for billing are stored in a network resource function (NRF) entity or in the billing configuration information of the CTF entity.

[0255] S509: The main CHF entity performs charging processing.

[0256] Specifically, the master CHF entity generates a second billing resource and an identifier of the second billing resource for the first R-CHF entity. Optionally, the second billing request includes billing information cached in the first billing resource of the first R-CHF entity; if the cached billing information includes billing information and a corresponding quota suspension identifier, the master CHF entity directly deducts the service usage in the billing information from the account balance corresponding to the second billing resource according to the billing information corresponding to the quota suspension identifier; if the billing information cached by the first R-CHF entity includes offline service usage, the master CHF entity writes the offline service usage into the master CHF call bill.

[0257] Optionally, if the second charging request includes a third charging request, the primary CHF entity performs quota granting according to the applied quota amount in the third charging request.

[0258] S510: The primary CHF entity sends a second charging response message to the first R-CHF entity.

[0259] The second charging response message includes a second charging resource identifier generated by the primary CHF entity for the first R-CHF entity, and a charging processing result, wherein the charging processing result includes an online charging processing result and an offline one-time event charging processing result.

[0260] S511. The first R-CHF entity sends a third charging response message to the CTF entity.

[0261] The third billing response message is used to respond to the third billing request. The third billing response message includes the content included in the second billing response message and the capability information fed back by the first R-CHF. The capability information includes at least one of the payload size of the billing message of the first billing resource, the idle time for the billing information collection of the CTF entity of the first billing resource, the billing characteristics, or the trigger condition setting of the first billing resource. The trigger condition setting includes the trigger condition for reporting the billing information, such as whether the billing information is reported, whether the billing information is delayed in reporting, and reporting when the parameter value of the billing information meets the preset value.

[0262] S512: The first R-CHF entity sends the cached first R-CHF call record to the main CHF entity.

[0263] Specifically, if the first R-CHF entity caches the billing information in the form of a first R-CHF call record, the first R-CHF entity sends the cached first R-CHF call record to the main CHF entity. Optionally, the first R-CHF entity sends the cached first R-CHF call record to the main CHF entity through FTP or other methods; or the first R-CHF entity sends a message to the main CHF entity through a billing session between the first R-CHF entity and the main CHF entity (the message may be a resource update message or a billing request), and the message carries the address of the space for storing the first R-CHF call record, so that the main CHF entity obtains the first R-CHF call record according to the address, and associates it with the corresponding billing resource identifier or billing resource, and performs billing processing according to the billing resource corresponding to the associated billing resource identifier or the associated billing resource.

[0264] S513: The primary CHF entity performs charging processing according to the first R-CHF call record.

[0265] Specifically, the main CHF entity associates the first R-CHF bill with the user account, or the main CHF entity generates the billing resource indicated by the billing resource identifier. The first R-CHF bill includes the billing information cached by the first R-CHF entity; if the cached billing information includes the billing information corresponding to the quota suspension identifier, the main CHF entity deducts the account balance according to the billing information corresponding to the quota suspension identifier; if the cached billing information includes the offline service usage, the main CHF entity writes the offline service usage into the main CHF bill.

[0266] It should be pointed out here that S506-S507 and S511 are optional. Optionally, S506-S507 are executed first, and then S508-S511; S508-S510 is executed directly. There is no clear order of execution between S512-S513 and S509-S511. Optionally, S512-S513 are executed first, and then S509-S511; or, S509-S511 are executed first, and then S512-S513; or S512-S513 and S509-S511 are executed simultaneously.

[0267] In the case where a charging session is not established between the CTF entity and the first R-CHF entity and between the first R-CHF entity and the main CHF entity, when the interaction between the first R-CHF entity and the main CHF entity is abnormal, the above process can enable the charging process to proceed normally.

[0268] See also Figure 6 , Figure 6 An interactive flowchart of another method for handling billing exceptions provided in an embodiment of the present application. Figure 6The illustrated embodiment is for a scenario where a charging session has been established between a CTF entity and a first R-CHF entity, and a charging session has been established between the first R-CHF entity and a main CHF entity. Figure 6 As shown, the method includes:

[0269] S601. A CTF entity sends a first charging request to a first R-CHF entity.

[0270] The first charging request is a charging resource update request or a charging resource release request, which is used to request to update or release the converged charging session between the first R-CHF entity and the CTF entity. It should be understood that the intermediate charging request here refers to a charging request sent on the premise that a charging session has been established between the CTF entity and the first R-CHF entity and a charging session has been established between the first R-CHF entity and the main CHF entity.

[0271] The first charging request includes charging information and first indication information. The first indication information is used to indicate whether the CTF entity supports the suspended quota management capability.

[0272] In one example, the billing information is billing information with quota management or billing information without quota management. In another example, the billing information includes billing information with quota management and billing information without quota management.

[0273] S602: The first R-CHF entity detects that the main CHF entity is abnormal, and performs abnormal charging processing.

[0274] It should be noted here that the specific manner in which the first R-CHF entity determines that the main CHF entity is abnormal can be found in the relevant description of S502 and will not be described again here.

[0275] Specifically, the first R-CHF entity performs abnormal charging processing, which specifically includes:

[0276] For the billing information without quota management, the first R-CHF entity caches the billing information without quota management. The cached billing information includes offline one-time event billing information, such as offline service usage, offline service information, etc. In one example, the first R-CHF entity directly caches the billing information without quota management in a first billing resource locally (such as local memory or local storage); or the first R-CHF entity generates a first R-CHF call record.

[0277] For the billing information with quota management, since a billing session has been established with the main CHF entity, that is, the main CHF entity may have allocated a quota to the user, the billing information with quota management includes quota application and / or quota usage. The first R-CHF entity caches the billing information with quota management and marks it as quota usage or quota suspension usage. If it is marked as quota suspension usage, CHF needs to be notified to release the granted quota later. In one example, the first R-CHF entity directly caches the billing information with quota management and the corresponding quota consumption identifier or quota suspension identifier in a first billing resource locally (such as local memory or local storage), or the first R-CHF entity generates a first R-CHF call record, and the first R-CHF entity call record includes the billing information with quota management and the corresponding quota consumption identifier or quota suspension identifier. At the same time,

[0278] In the case where the first R-CHF entity has no available quota, if the CTF entity supports the suspended quota management capability, the first R-CHF entity suspends the quota management of the service. At this time, the first charging response message also includes suspended quota indication information, and the suspended quota indication information is used to instruct the CTF entity to continue the service according to the suspended quota management mode. After the subsequent CTF entity reports the usage of the service after the quota is suspended to the first R-CHF entity, the first R-CHF entity caches the charging information of the suspended quota (such as: service usage) and the corresponding quota suspension identifier.

[0279] In the case where the first R-CHF entity has no available quota, if the CTF entity does not support the ability to suspend quota management, the first R-CHF entity performs a quota granting operation. Since the first R-CHF entity does not have the account information of the user, the granted quota is a virtual granted quota. After the CTF entity receives the first charging response message, it manages the service according to the granted quota and collects quota usage information. After the subsequent CTF entity reports the collected quota usage information to the first R-CHF entity, the first R-CHF caches the quota management-related charging information (such as quota usage) and the quota suspension flag.

[0280] In the case where the first R-CHF entity has available quota, if the CTF entity supports the suspended quota management capability, the first R-CHF entity may handle it in the following manner:

[0281] Mode 1: The first R-CHF entity suspends the quota management of the service, that is, the current available quota is not used, and the main CHF entity is notified to release the quota after the subsequent main CHF entity is restored. The exception handling of the first R-CHF entity in this scenario is the same as the above-mentioned case where the first R-CHF entity has no available quota.

[0282] Mode 2: The first R-CHF entity provides quota granting and deduction for the service based on the available quota; suspends the quota management of the service after the available quota is used up; the billing information with quota management includes two parts: first billing information and second billing information, wherein the first billing information is the billing information using the available quota granted by the main CHF entity, and the second billing information is the billing information not using the available quota granted by the main CHF entity; the first R-CHF entity caches the billing information with quota management, including: caching the first billing information and the corresponding quota consumption identifier, and caching the second billing information and the corresponding quota suspension identifier.

[0283] In the case where the first R-CHF entity has available quota, if the CTF entity does not support the suspended quota management capability, the first R-CHF entity may handle it in the following manner:

[0284] Mode 1: The first R-CHF entity grants a virtual quota, that is, the current available quota is not used, and the primary CHF entity is notified to release the quota after the subsequent primary CHF entity is restored. In this scenario, after receiving the usage information of the virtual quota reported by the subsequent CTF entity, the first R-CHF entity caches the usage information and marks it as the quota suspension usage;

[0285] Mode 2: The first R-CHF entity provides quota granting and deduction for the service based on the available quota; grants the virtual quota after the available quota is used up; the billing information with quota management includes two parts: the first billing information and the second billing information, wherein the first billing information is the billing information using the available quota granted by the main CHF entity, and the second billing information is the billing information (corresponding to the virtual quota) without using the available quota granted by the main CHF entity; the first R-CHF entity caches the billing information with quota management, including: caching the first billing information and the corresponding quota consumption identifier, and caching the second billing information and the corresponding quota suspension identifier.

[0286] It should be understood that the available quota of the first R-CHF entity is the quota granted by the main CHF entity before the exception.

[0287] S603: The first R-CHF entity sends a first charging response message to the CTF entity.

[0288] The first charging response message is used to respond to the first charging request. Optionally, if the CTF entity supports the suspended quota management capability, the first charging response message also includes suspended quota indication information, and the suspended quota indication information is used to instruct the CTF entity to continue the service according to the suspended quota management mode; if the first R-CHF entity performs a quota granting operation, the first charging response message also includes the quota granted by the first R-CHF entity.

[0289] S604: The CTF entity processes the service according to the first charging response message.

[0290] S605: The first R-CHF entity detects that the main CHF entity is normal.

[0291] S606: The first R-CHF entity sends a charging message to the CTF entity.

[0292] S607: The CTF entity sends a third charging request to the first R-CHF entity.

[0293] S608: The first R-CHF entity sends a second charging request to the main CHF entity.

[0294] S609: The main CHF entity performs charging processing.

[0295] Optionally, the second billing request includes the first billing information cached in the first billing resource; if the cached billing information includes the billing information corresponding to the quota suspension identifier, the main CHF entity directly deducts the service usage in the billing information from the corresponding account balance in the second billing resource according to the billing information corresponding to the quota suspension identifier; if the cached billing information includes offline service usage, the main CHF entity writes the offline service usage into the main CHF call record. If the cached billing information also includes release indication information, the main CHF entity releases the quota granted by the main CHF entity before the main CHF entity is abnormal; if the cached billing information also includes usage information of the quota granted by the main CHF entity before the first R-CHF entity is abnormal, the main CHF entity deducts the usage of the corresponding quota in the corresponding account balance in the second billing resource according to the usage information.

[0296] Optionally, if the second charging request includes a quota application for the third charging request, the primary CHF entity also includes a granted quota.

[0297] S610: The primary CHF entity sends a second charging response message to the first R-CHF entity.

[0298] S611. The first R-CHF entity sends a third charging response message to the CTF entity.

[0299] S612: The first R-CHF entity sends the cached first R-CHF call record to the main CHF entity.

[0300] S613: The primary CHF entity performs charging processing according to the first R-CHF call record.

[0301] It should be noted that the specific implementation process of S604-S608 can refer to the relevant description of S504-S508, and the specific implementation process of S610-S613 can refer to the relevant description of S510-S513, which will not be described again here.

[0302] It should be pointed out here that S606-S607 and S611 are optional. Optionally, S606-S607 is executed first, and then S608-S611; or, S608-S610 is executed directly. There is no clear order of execution between S612-S613 and S609-S611. Optionally, S612-S613 is executed first, and then S609-S611; or, S609-S611 is executed first, and then S612-S613; or S612-S613 and S609-S611 are executed simultaneously.

[0303] In the case where a charging session has been established between the CTF entity and the first R-CHF entity and a charging session has been established between the first R-CHF entity and the main CHF entity, when the interaction between the first R-CHF entity and the main CHF entity is abnormal, the above processing can enable the charging processing to proceed normally.

[0304] See also Figure 7 , Figure 7 An interactive flowchart of a method for handling billing exceptions provided in an embodiment of the present application. Figure 7 The illustrated embodiment is for a billing scenario in which a one-time billing event is performed. Figure 7 As shown, the method includes:

[0305] S701. A CTF entity sends a first charging request to a first R-CHF entity.

[0306] The first charging request is a one-time event charging request for online direct charging or offline one-time event charging. The first charging request is an online direct charging (ie, IEC) or offline one-time event charging (ie, PEC) request.

[0307] S702: The first R-CHF entity detects that the main CHF entity is abnormal, and performs abnormal charging processing.

[0308] It should be noted here that the specific manner in which the first R-CHF entity determines that the main CHF entity is abnormal can be found in the relevant description of S502 and will not be described again here.

[0309] Specifically, the processing after the first R-CHF entity detects that the main CHF entity is abnormal includes:

[0310] Optionally, if the CTF entity and the first R-CHF entity belong to different operators, the first R-CHF entity determines whether to authorize the user equipment to use the current service according to the operator configuration information. When it is determined that the user equipment is authorized to use the current service, the first R-CHF entity generates a charging resource identifier for the CTF entity and performs the following abnormal charging processing. When it is determined that the user equipment is not authorized to use the current service, the following abnormal charging processing is not performed.

[0311] S703: The first R-CHF entity sends a first charging response message to the CTF entity.

[0312] The first charging response message includes a charging processing result. The charging processing result includes a charging success or a charging failure. If the charging processing result is a charging failure, the charging processing result also includes the reason for the charging failure, such as a charging information format error, lost information, etc.

[0313] S704: The CTF entity processes the service according to the first charging response message.

[0314] Specifically, when the billing processing result is a billing failure, the CTF entity retransmits the billing information or terminates the service; when the billing processing result is a billing success, the CTF entity continues to collect offline one-time event billing information, online billing information, and the like.

[0315] S705: The first R-CHF entity detects that the main CHF entity is normal.

[0316] S706: The first R-CHF entity sends a second charging request to the main CHF entity.

[0317] If the second charging request is used to request one-time event charging, the second charging request includes the charging information cached by the first R-CHF entity.

[0318] S707: The main CHF entity performs charging processing.

[0319] Specifically, online charging processing is performed according to the online charging indication information in the cached charging information, the charging information with quota management and the corresponding consumption quota identifier, such as deducting the account balance; for offline service usage, the offline service usage is written into the main CHF call list.

[0320] S708: The primary CHF entity sends a second charging response message to the first R-CHF entity.

[0321] The second charging response message is used to respond to the second charging request.

[0322] S709: The first R-CHF entity sends the cached first R-CHF call record to the main CHF entity.

[0323] Specifically, if the first R-CHF entity caches the billing information in the form of a first R-CHF call record, the first R-CHF entity sends the cached first R-CHF call record to the main CHF entity. Optionally, the first R-CHF entity sends the cached first R-CHF call record to the main CHF entity through FTP or other methods; or the first R-CHF entity sends a message to the main CHF entity through a billing session between the first R-CHF entity and the main CHF entity (the message may be a resource update message or a billing request), and the message carries the address of the space for storing the first R-CHF call record, so that the main CHF entity obtains the first R-CHF call record according to the address, and associates it with the corresponding billing resource identifier or billing resource, and performs billing processing according to the billing resource corresponding to the associated billing resource identifier or the associated billing resource.

[0324] S710: The primary CHF entity performs charging processing according to the first R-CHF call record.

[0325] Specifically, online charging processing is performed according to the online charging indication information in the cached charging information, the charging information with quota management and the corresponding consumption quota identifier, such as deducting the account balance; for offline service usage, the offline service usage is written into the main CHF call list.

[0326] It should be pointed out here that, for S706-S708 and S709-S710, either one is executed.

[0327] In the case of one-time billing, when the interaction between the first R-CHF entity and the main CHF entity is abnormal, the above process can enable the billing process to proceed normally.

[0328] See also Figure 8 , Figure 8 An interactive flowchart of another method for handling billing exceptions provided in an embodiment of the present application. Figure 8 The illustrated embodiment is directed to a scenario where a charging session has been established between a CTF entity and a second R-CHF entity, and a charging session has been established between a first R-CHF entity and a primary CHF entity. Figure 8 As shown, the method includes:

[0329] S801: The CTF entity detects that the second R-CHF entity is abnormal, and determines the address of the first R-CHF entity.

[0330] Optionally, the CTF entity can determine that the second R-CHF entity is abnormal in the following manner:

[0331] 1. The CTF entity determines that the interaction between the CTF entity and the second R-CHF entity is abnormal based on the application layer congestion indication returned by the second R-CHF entity or when it detects that the delay of the second R-CHF entity returning the charging response message increases, that is, when it detects that the second R-CHF entity is congested.

[0332] 2. When the CTF entity detects that the transport layer connection between the CTF entity and the second R-CHF entity is interrupted, that is, when the CTF entity detects that the second R-CHF entity is unreachable, it is determined that the interaction between the CTF entity and the second R-CHF entity is abnormal.

[0333] 3. The CTF entity determines that the transport layer of the CTF entity and the transport layer of the second R-CHF entity are congested according to the transport layer congestion control mechanism or jitter, that is, the communication quality between the CTF entity and the second R-CHF entity is reduced, and then determines that the interaction between the CTFF entity and the second R-CHF entity is abnormal.

[0334] Optionally, the CTF entity determines the address of the first R-CHF entity in the following manner:

[0335] Method 1: The CTF entity determines the address of the R-CHF entity according to the identifier of the CTF entity. In one example, the CTF queries a correspondence table according to the identifier of the CTF entity to determine the address of the first R-CHF entity, wherein the correspondence table is a correspondence table of the identifier of the CTF entity, the identifier of the R-CHF entity, and the address of the R-CHF entity.

[0336] Method 2: The CTF entity determines the address of the first R-CHF entity according to the location information of the user equipment. In one example, the CTF entity determines the location of the user equipment according to the location information of the user equipment, and then determines the CHF entity that provides billing for the area to which the location of the user equipment belongs, determines the CHF entity as the first R-CHF entity, and obtains the address of the first R-CHF entity.

[0337] Mode 3: The CTF entity determines the address of the first R-CHF according to the service information used by the user equipment; the R-CHF is a CHF entity that provides billing for the service used by the user equipment. When there are multiple CHF entities that provide billing for the service used by the user equipment, the CTF entity selects the CHF entity with the smallest distance between the coverage area and the user equipment as the first R-CHF entity.

[0338] It should be understood that the above correspondence table, the coverage area of ​​the CHF and the service information that the CHF can provide for billing are stored in a network resource function (NRF) entity or in the billing configuration information of the CTF entity.

[0339] S802: The CTF entity sends a first charging request to the first R-CHF entity.

[0340] The first charging request is a first charging resource update request or a first charging resource release request, which is used to request to update or release the first charging resource between the second R-CHF entity and the CTF entity, and the first charging request carries the first charging resource identifier between the CTF entity and the second R-CHF entity. The first charging request includes charging information, a charging resource identifier and user information. The charging resource identifier here is generated by the second R-CHF entity for the CTF entity.

[0341] S803: The first R-CHF entity performs abnormal charging processing and generates a second charging request.

[0342] Since the second R-CHF entity is unreachable, the first R-CHF entity cannot obtain the first charging resource between the CTF entity and the second CHF entity from the second R-CHF entity, nor can it obtain the second charging resource between the second R-CHF entity and the main CHF entity. Therefore, the first R-CHF entity performs abnormal charging processing, including:

[0343] The first R-CHF entity creates a third billing resource according to the first billing resource identifier and user information included in the first billing request, uses the identifier of the first billing resource as the identifier of the third billing resource, and performs a billing operation according to the third billing resource and the billing information, such as opening the first R-CHF bill. It should be understood that opening the first R-CHF bill refers to creating the first R-CHF bill to facilitate writing of billing data.

[0344] Since the first R-CHF entity cannot obtain the second charging resource between the second R-CHF entity and the main CHF entity, the first R-CHF entity generates a second charging request, and the second charging request is used to request the creation of a converged charging session between the first R-CHF entity and the main CHF entity. The second charging request includes the charging information and user identification in the first charging request. Optionally, the second charging request also includes capability information determined by the first R-CHF entity. The capability information represents the capability for the main CHF entity to interact with the first R-CHF entity. The capability information is determined by the first R-CHF entity based on the capability information supported by the CTF entity. Here, the capability information supported by the CTF entity is the capability information provided by the CTF entity that can be used for the first R-CHF entity to interact with the CTF entity.

[0345] The capability information determined by the first R-CHF entity includes at least one of a payload size of a charging message for a second charging resource supported by the first R-CHF entity, an idle duration of charging information collection of the first R-CHF entity for the second charging resource, or a charging characteristic.

[0346] The capability information supported by the CTF entity includes at least one of a payload size of a charging message for the first charging resource supported by the CTF entity, an idle time for charging information collection of the CTF entity for the first charging resource, or a charging characteristic.

[0347] S804: The first R-CHF entity sends a second charging request to the main CHF entity.

[0348] S805: The main CHF entity performs charging processing.

[0349] Specifically, the primary CHF determines the existing billing resources (i.e., the billing resource identifier allocated by the primary CHF for the billing of the user on the second R-CHF) according to the user identifier, billing ID and other information in the second billing request, performs billing processing (such as granting quota, deducting quota usage, writing to the primary CHF call record, etc.), and returns the existing billing resource identifier.

[0350] It should be understood that each user has his own billing resources, the second billing request includes a user identifier, and the billing resources corresponding to the second billing request refer to the billing resources corresponding to the user indicated by the user identifier in the second billing request.

[0351] S806: The primary CHF entity sends a second charging response message to the first R-CHF entity.

[0352] The second charging response message is used to respond to the second charging request. The second charging response message includes a charging processing result and an identifier of a charging resource corresponding to the second charging request.

[0353] S807: The first R-CHF entity generates a first charging response message.

[0354] The first charging response message includes the content of the second charging response message and trigger configuration information. The trigger configuration information includes trigger conditions for reporting charging information, such as whether to report charging information, whether to delay reporting charging information, and reporting when parameter values ​​of charging information meet preset values.

[0355] S808. The first R-CHF entity sends a first charging response message to the CTF entity.

[0356] S809: The CTF entity processes the service according to the first charging response message.

[0357] Specifically, when the billing processing result is a billing failure, the CTF entity retransmits the billing information or terminates the service; when the billing processing result is a billing success, the CTF entity continues to collect offline one-time event billing information, online billing information, and the like.

[0358] Optionally, after the first R-CHF entity detects that the second R-CHF entity is restored, the first R-CHF entity sends a charging resource migration notification to the second R-CHF entity to instruct the second R-CHF entity to delete the locally stored first charging resource of the user generated for the CTF.

[0359] In the case where a charging session has been established between the CTF entity and the second R-CHF entity and a charging session has been established between the first R-CHF entity and the main CHF entity, when the interaction between the first R-CHF entity and the second R-CHF entity is abnormal, the above processing can enable the charging processing to proceed normally.

[0360] See also Fig. 9 , Fig. 9 An interactive flowchart of another method for handling billing exceptions provided in an embodiment of the present application. Fig. 9 The illustrated embodiment is for a scenario where a charging session has been established between a CTF entity and a main CHF entity. Fig. 9 As shown, the method includes:

[0361] S901: The CTF entity detects that the main CHF entity is abnormal, and determines the address of the first R-CHF entity.

[0362] It should be noted that the specific implementation process of the CTF entity detecting the abnormality of the main CHF entity can refer to the relevant description of S501, which will not be described here. The specific process of the CTF entity determining the first R-CHF entity can refer to the relevant description of S801, which will not be described here.

[0363] S902: The CTF entity sends a first charging request to the first R-CHF entity.

[0364] The first charging request is a first charging resource creation request, which is used to request the creation of a first charging resource for charging interaction between the CTF entity and the first R-CHF entity. The first charging request includes charging resource related information generated by the main CHF entity for the CTF entity, and the charging resource related information is used by the first R-CHF to send a second charging request to the main CHF.

[0365] S903: The first R-CHF entity performs abnormal charging processing and generates a second charging request.

[0366] The first R-CHF entity performs abnormal charging processing, including:

[0367] The first R-CHF entity generates, according to the first charging request, an identifier of a first charging resource used for charging interaction between the CTF entity and the first R-CHF entity.

[0368] Since the main CHF entity is abnormally unreachable, the first R-CHF entity performs abnormal charging processing. The specific process can be found in S602 for the charging information including the charging information without quota management and the charging information including the charging information with quota management and no available quota, which will not be described here.

[0369] S904: The first R-CHF entity sends a first charging response message to the CTF entity.

[0370] The first billing response message is used to respond to the first billing request. Optionally, if the CTF entity supports the suspended quota management capability, the first billing response message also includes suspended quota indication information, and the suspended quota indication information is used to instruct the CTF entity to continue the service in accordance with the suspended quota management mode; if the first R-CHF entity performs a quota granting operation, the first billing response message also includes the quota granted by the first R-CHF entity. Optionally, if the first R-CHF allocates a new billing resource identifier for the first billing resource generated above to replace the billing resource identifier included in the first billing request, the first billing response message also includes the new billing resource identifier.

[0371] S905. The CTF entity processes the service according to the first charging response message.

[0372] Wherein, processing the service includes collecting offline one-time event billing information. Optionally, if the first billing response message includes quota suspension indication information, the CTF collects the online quota usage of the quota suspension. Optionally, when the first billing response message includes the quota granted by the first R-CHF entity, the CTF entity monitors the usage of the granted quota.

[0373] S906: The first R-CHF entity detects that the main CHF entity is normal.

[0374] After the first R-CHF entity detects that the main CHF entity is normal, it gradually resumes sending according to the congestion control mechanism to avoid new congestion.

[0375] S907: The first R-CHF entity sends a charging message to the CTF entity.

[0376] The charging message is used to instruct the CTF entity to resume the suspended quota management. Optionally, the charging message is sent by a charging notification message or a charging response. It should be understood that the charging notification message is actively sent by the first R-CHF entity to the CTF entity. The charging message is sent by a charging response, which means that the charging message is carried in the charging response sent by the first R-CHF entity to the CTF entity.

[0377] S908. The CTF entity sends a third charging request to the first R-CHF entity.

[0378] The first charging request is for a quota request, and the third charging request includes the applied quota amount. Optionally, the third charging request also includes the quota usage when the quota is suspended.

[0379] S909: The first R-CHF entity sends a second charging request to the main CHF entity.

[0380] The second charging request is a third charging resource update or release request, which is used to request to update or release the third charging resource for the charging interaction between the CTF entity and the main CHF entity. The second charging request may also include the charging information cached by the first R-CHF entity, that is, the charging information and the corresponding quota suspension identifier or quota consumption identifier. If the first R-CHF entity receives the third charging request sent by the CTF entity after resuming the suspension quota management, the second charging request also includes the quota request and usage carried by the third charging request.

[0381] Optionally, the second charging request further includes capability information sent by the first R-CHF entity. The capability information includes at least one of a payload size of a charging message for a second charging resource supported by the first R-CHF entity, a second idle duration for charging information collection of the first R-CHF entity for the second charging resource, or a second charging characteristic.

[0382] Since the main CHF entity is unreachable, the first R-CHF entity needs to obtain the address of the main CHF entity to interact with the main CHF entity.

[0383] It should be noted here that the specific process of the first R-CHF entity determining the address of the main CHF entity can be referred to the relevant content of S508, which will not be described here.

[0384] S910: The main CHF entity performs charging processing.

[0385] Specifically, the second charging request includes the charging information cached by the first R-CHF entity; if the cached charging information includes the charging information and the corresponding quota suspension identifier, the main CHF entity directly deducts the service usage in the charging information from the account balance corresponding to the second charging resource according to the charging information corresponding to the quota suspension identifier; if the cached charging information includes the charging information and the corresponding quota consumption identifier, the main CHF entity deducts the charging information from the account balance corresponding to the second charging resource according to the charging information corresponding to the quota consumption identifier and releases the locked quota; if the charging information cached by the first R-CHF entity includes offline service usage, the main CHF entity writes the offline service usage into the main CHF call record. Optionally, if the second charging request includes the requested quota amount, the main CHF entity performs quota granting according to the requested quota amount.

[0386] S911. The primary CHF entity sends a second charging response message to the first R-CHF entity.

[0387] Optionally, when the second charging request is a charging resource creation request, the second charging response message includes an identifier of the charging resource bound to the second charging request. Optionally, the second charging response message also includes capability information fed back by the primary CHF entity.

[0388] The capability information fed back by the main CHF entity includes at least one of the payload size of the charging message for the second charging resource, the idle time for the charging information collection of the first R-CHF entity for the second charging resource, the third charging characteristic, or the trigger condition setting of the second charging resource. The trigger condition setting includes the trigger condition for reporting the charging information, such as whether the charging information is reported, whether the charging information is delayed in reporting, and reporting when the parameter value of the charging information meets the preset value.

[0389] S912. The first R-CHF entity sends a third charging response message to the CTF entity.

[0390] The third charging response message includes the content in the second charging response message and the content supplemented or modified by the first R-CHF entity, such as trigger configuration information.

[0391] S913: The first R-CHF entity sends the cached first R-CHF call record to the main CHF entity.

[0392] S914: The primary CHF entity performs charging processing according to the first R-CHF call record.

[0393] It should be pointed out here that the specific implementation process of S913-S914 can refer to the relevant description of S510-S513 and will not be described here.

[0394] It should be pointed out here that S907-S908 and S912 are optional steps. Optionally, S907-S908 are executed first, and then S909-S912; or, S909-S911 is executed directly. There is no clear order of execution between S909-S911 and S913-S914. Optionally, S909-S911 is executed first, and then S913-S914; or, S913-S914 is executed first, and then S909-S911; or S909-S911 and S913-S914 are executed simultaneously.

[0395] In the case where a charging session has been established between the CTF entity and the main CHF entity, when the interaction between the first R-CHF entity and the main CHF entity is abnormal, the above process can enable the charging process to proceed normally.

[0396] Reference Fig.10 FIG. 1 is a schematic diagram of the structure of a first R-CHF entity provided in an embodiment of the present application. The first R-CHF entity is Figure 2 R-CHF entity 202 in. Fig.10 As shown, the first R-CHF entity 1000 includes a transceiver unit 1001 and a processing unit 1002 .

[0397] The transceiver unit 1001 is configured to receive a first charging request sent by a CTF entity,

[0398] The processing unit 1002 is configured to detect that the target CHF entity interaction related to the first charging request is abnormal, and perform abnormal charging processing;

[0399] The target CHF entity is the main CHF entity or the second R-CHF entity, the main CHF entity provides online quota management and billing call record generation; the second R-CHF entity is a CHF entity that provides relay for the CTF entity and the main CHF entity before the first R-CHF entity acts as a relay CHF entity.

[0400] In combination with the third aspect, in a possible implementation manner, the target CHF entity is a primary CHF entity corresponding to the first charging request, the first charging request is a charging resource creation request for creating a convergent charging session, and is used to request the creation of a charging interaction session between the CTF entity and the first R-CHF entity, and the processing unit 1002 is specifically used to:

[0401] Generate a first charging resource for charging interaction between the CTF entity and the first R-CHF entity; cache the charging information in the first charging request;

[0402] The transceiver unit is further configured to send a first charging response message for responding to the first charging request to the CTF entity, where the first charging response message includes an identifier of the first charging resource.

[0403] In combination with the third aspect, in a possible implementation, if the first charging request includes a quota request, the first response message includes suspended quota indication information or a granted quota, and the suspended quota indication information is used to instruct the CTF entity to continue the service according to the suspended quota management mode.

[0404] In combination with the third aspect, in a possible implementation, the first charging response message includes the granted quota, and the CTF entity receives usage of the granted quota, and the cached charging information includes a quota suspension identifier corresponding to the usage of the granted quota.

[0405] In conjunction with the third aspect, in a possible implementation, in terms of caching the billing information in the first billing request, the processing unit 1002 is specifically configured to:

[0406] The charging information in the first charging request is written into the first R-CHF bill or stored in the first charging resource.

[0407] In conjunction with the third aspect, in a possible implementation, the transceiver unit 1001 is further configured to:

[0408] When it is detected that the target CHF entity interaction related to the first billing request is normal, a second billing request is sent to the main CHF entity, where the second billing request is a second billing resource creation request, which is used to request the creation of a second billing resource for the billing interaction between the first R-CHF entity and the main CHF entity, or the second billing request is a third billing resource update or release request, which is used to request the update or release of the third billing resource for the billing interaction between the CTF and the main CHF entity.

[0409] In combination with the third aspect, in a possible implementation manner, the second charging request carries cached charging information.

[0410] In conjunction with the third aspect, in a possible implementation, the transceiver unit 1001 is further configured to:

[0411] When the processing unit 1002 detects that the target CHF entity related to the first charging request interacts normally, the first R-CHF call record is sent to the main CHF entity. Here, the target CHF entity related to the first charging request is the main CHF entity.

[0412] In conjunction with the third aspect, in a possible implementation,

[0413] The transceiver unit 1001 is also used to send a notification message to the CTF entity before generating a second billing request, the notification message is used to instruct the CTF entity to restore quota management; receive a third billing request sent by the CTF entity, the third billing request carries a quota request and usage for restoring quota management; the second billing request includes the quota request and usage carried by the third billing request.

[0414] In combination with the third aspect, in a possible implementation manner, the target CHF is a primary CHF entity corresponding to the first charging request, the first charging request is a first charging resource update request or a first charging resource release request, which is used to request to update or release a first charging resource for charging interaction between the first R-CHF entity and the CTF entity, and the processing unit 1002 is specifically used to: cache the charging information of the first charging request;

[0415] The transceiver unit 1001 is further configured to send a first charging response message in response to the first charging request to the CTF entity.

[0416] In combination with the third aspect, in a possible implementation, if the first charging request includes a quota request, the first response message includes suspended quota indication information or a granted quota, and the suspended quota indication information is used to instruct the CTF entity to continue the service according to the suspended quota management mode.

[0417] In combination with the third aspect, in a possible implementation, the cached billing information includes first billing information and a corresponding quota consumption identifier, or second billing information and a corresponding quota suspension identifier, the first billing information is the billing information that uses the available quota granted by the main CHF entity in the billing information, and the second billing information is the billing information that does not use the available quota granted by the main CHF entity in the billing information.

[0418] In conjunction with the third aspect, in a possible implementation, in terms of caching the billing information of the first billing request, the processing unit 1002 is further configured to:

[0419] The first billing information and the corresponding quota consumption identifier, or the second billing information and the corresponding quota suspension identifier are written into the first R-CHF call record or saved in the first billing resource.

[0420] In conjunction with the third aspect, in a possible implementation, the transceiver unit 1001 is further configured to:

[0421] When it is detected that the target CHF interaction related to the first charging request is normal, a second charging request is sent to the main CHF entity, and the second charging request is a second charging resource update request or a second charging resource release request, which is used to request to update or release the second charging resource of the charging interaction between the first R-CHF entity and the main CHF entity.

[0422] In conjunction with the third aspect, in a possible implementation, the transceiver unit 1001 is further configured to:

[0423] When the processing unit 1002 detects that the target CHF interaction related to the first charging request is normal, the first R-CHF call record is sent to the main CHF entity.

[0424] In combination with the third aspect, in a possible implementation manner, the second charging request carries the charging information and a corresponding quota suspension identifier or a quota consumption identifier.

[0425] In conjunction with the third aspect, in a possible implementation, the transceiver unit 1001 is further configured to:

[0426] Before generating the second charging request, a notification message is sent to the CTF entity, where the notification message is used to instruct the CTF entity to restore quota management; a third charging request sent by the CTF entity is received, where the third charging request carries a quota request and usage for restoring quota management; and the second charging request includes the quota request and usage carried by the third charging request.

[0427] In conjunction with the third aspect, in a possible implementation, the target CHF entity is a primary CHF entity corresponding to the first charging request, the first charging request is a one-time event charging request for online direct deduction or offline one-time event charging, and the processing unit 1002 is further used to: cache charging information of the first charging request;

[0428] The transceiver unit 1001 is further configured to send a first charging response message in response to the first charging request to the CTF entity.

[0429] In conjunction with the third aspect, in a possible implementation, in terms of caching the billing information of the first billing request, the processing unit 1002 is specifically configured to: write the billing information and the corresponding online direct deduction indication information or the offline one-time event billing indication information into the first R-CHF call record;

[0430] The transceiver unit 1001 is further configured to send a first R-CHF call record to the primary CHF entity when it is detected that the target CHF interaction related to the first charging request is normal.

[0431] In conjunction with the third aspect, in a possible implementation, the processing unit 1002 is specifically configured to:

[0432] The charging information of the first charging request and the corresponding online direct deduction indication information or offline one-time event charging indication information are stored in the first charging resource;

[0433] When it is detected that the target CHF interaction related to the first charging request is normal, a second charging request is generated, the second charging request is a one-time event charging request, and the second charging request carries charging information and corresponding online direct deduction indication information or offline one-time event charging indication information;

[0434] The transceiver unit 1001 is further configured to send a second charging request to the primary CHF entity.

[0435] In combination with the third aspect, in a possible implementation manner, the target CHF entity is a second R-CHF entity, and the first charging request is a first charging resource update request or a first charging resource release request, which is used to request to update or release a first charging resource for charging interaction between the second R-CHF entity and the CTF entity; the processing unit 1002 is specifically used to:

[0436] generating a fourth charging resource between the CTF entity and the first R-CHF entity according to the first charging request, and using the first charging resource identifier as the identifier of the fourth charging resource; generating a second charging request according to the first charging request, the second charging request being used to request the creation of a second charging resource for charging interaction between the first R-CHF entity and the main CHF entity, and the second charging request carrying the identifier of the third charging resource;

[0437] The transceiver unit 1001 is further configured to send a second charging request to the primary CHF entity, and receive a second charging response message from the primary CHF entity in response to the second charging request; the second charging response message carries an identifier of a second charging resource;

[0438] The processing unit 1002 is further configured to generate a first charging response message for responding to the first charging request according to the second charging response message;

[0439] The transceiver unit 1001 is further configured to send a first charging response message to the CTF entity.

[0440] It is worth pointing out that, the specific functional implementation of the first R-CHF entity 1000 refers to the description of the above-mentioned charging exception processing method, such as the transceiver unit 1001 and the processing unit 1002 are used to execute the relevant contents of S301 and S302. Each unit or module in the first R-CHF entity 1000 can be respectively or completely merged into one or more other units or modules to form, or one (some) of the units or modules can be further divided into multiple smaller units or modules in function to form, which can achieve the same operation without affecting the realization of the technical effect of the embodiment of the present invention. The above-mentioned units or modules are divided based on logical functions. In actual applications, the function of one unit (or module) is realized by multiple units (or modules), or the functions of multiple units (or modules) are realized by one unit (or module).

[0441] Reference Fig.11 The figure is a schematic diagram of the structure of a main CHF entity provided in an embodiment of the present application. The main CHF entity provides online quota management and billing call record generation. The main CHF entity is Figure 2 The main CHF entity 203 in the main CHF entity 1100 includes:

[0442] The transceiver unit 1101 is further configured to receive relevant billing information cached by the first R-CHF entity, where the cached relevant billing information is carried in a billing call bill or a billing message, and the cached relevant billing information includes the billing information and a corresponding quota suspension identifier or a quota consumption identifier;

[0443] The processing unit 1102 is used to perform billing processing according to the quota suspension identifier or the quota consumption identifier.

[0444] In a possible implementation, the processing unit 1102 is specifically configured to:

[0445] The service usage in the billing information is directly deducted from the corresponding account balance in the billing resource of the main CHF entity;

[0446] The processing unit is also used to:

[0447] If the cached billing information has a corresponding quota consumption identifier, the service usage in the billing information is directly deducted from the corresponding account of the first billing resource, and the locked account balance is released at the same time; or,

[0448] If the cached billing information includes billing information without quota management, the billing information without quota management is written into the main CHF call list.

[0449] It is worth pointing out that, the specific functional implementation of the main CHF entity 1100 refers to the description of the above-mentioned charging exception processing method, for example, the transceiver unit 1101 is used to execute the relevant content of S401, and the processing unit 1102 is used to execute the relevant content of S402. Each unit or module in the main CHF entity 1100 can be respectively or completely merged into one or more other units or modules to form, or one (some) of the units or modules can be further divided into multiple smaller units or modules to form, which can achieve the same operation without affecting the realization of the technical effect of the embodiment of the present invention. The above-mentioned units or modules are divided based on logical functions. In actual applications, the function of one unit (or module) is realized by multiple units (or modules), or the functions of multiple units (or modules) are realized by one unit (or module).

[0450] Based on the description of the above method embodiments and related device embodiments, please refer to Fig.12 , an embodiment of the present invention also provides a schematic diagram of the structure of an electronic device 1200. The electronic device 1200 can be Figure 2 R-CHF entity 202 or main CHF entity 203 or Fig.10 The first R-CHF entity 1000 shown or Fig.11 A main CHF entity 1100 is shown. Fig.12 The electronic device 1200 shown (the electronic device 1200 is specifically a computer device) includes a memory 1201, a processor 1202, a communication interface 1203 and a bus 1204. The memory 1201, the processor 1202 and the communication interface 1203 are connected to each other through the bus 1204.

[0451] Optionally, the memory 1201 is a read-only memory (ROM), a static storage device, a dynamic storage device or a random access memory (RAM).

[0452] The memory 1201 can store programs. When the program stored in the memory 1201 is executed by the processor 1202, the processor 1202 and the communication interface 1203 are used to execute Figure 3 or Figure 4 The various steps of the method for handling billing exceptions in the illustrated embodiment.

[0453] The processor 1202 uses a general central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), a graphics processing unit (GPU) or one or more integrated circuits to execute relevant programs to implement the functions required to be performed by the units in the R-CHF entity 202 or the main CHF entity 203 in the embodiment of the present application, or to execute the billing exception processing method in the method embodiment of the present application.

[0454] The processor 1202 can also be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the charging exception processing method of the present application can be completed by the hardware integrated logic circuit or software instructions in the processor 1202. Optionally, the processor 1202 is a general-purpose processor, a digital signal processor (DigitalSignal Processing, DSP), an ASIC, a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The processor 1202 can implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor is a microprocessor or the processor is any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware decoding processor to execute, or the hardware and software modules in the decoding processor are combined and executed. Optionally, the software module is located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register or other mature storage media in the art. The storage medium is located in the memory 1201, and the processor 1202 reads the information in the memory 1201, and combines its hardware to complete the functions required to be executed by the units included in the R-CHF entity 202 or the main CHF entity 203 of the embodiment of the present application, or executes Figure 3 or Figure 4 The method for handling billing exceptions in the illustrated embodiment.

[0455] The communication interface 1203 uses a transceiver device such as but not limited to a transceiver to implement communication between the electronic device 1200 and other devices or a communication network.

[0456] The bus 1204 may include a path for transmitting information between various components of the electronic device 1200 (eg, the memory 1201 , the processor 1202 , and the communication interface 1203 ).

[0457] It should be noted that although Fig.12 The electronic device 1200 shown only shows a memory, a processor, and a communication interface, but in the specific implementation process, those skilled in the art should understand that the electronic device 1200 also includes other devices necessary for normal operation. At the same time, according to specific needs, those skilled in the art should understand that the electronic device 1200 may also include hardware devices for implementing other additional functions. In addition, those skilled in the art should understand that the electronic device 1200 may also include only the devices necessary to implement the embodiments of the present application, and does not necessarily include Fig.12 All devices shown in .

[0458] An embodiment of the present application further provides a chip, which includes a processor and a data interface. The processor reads instructions stored in a memory through the data interface to implement the billing exception processing method of the embodiment of the present application.

[0459] Optionally, as an implementation, the chip also includes a memory, in which instructions are stored, and the processor is used to execute the instructions stored in the memory. When the instructions are executed, the processor is used to execute the billing exception processing method.

[0460] An embodiment of the present application also provides a computer-readable storage medium, which stores instructions. When the computer-readable storage medium is executed on a computer or a processor, the computer or the processor executes one or more steps in any of the above methods.

[0461] The embodiment of the present application further provides a computer program product including instructions. When the computer program product is executed on a computer or a processor, the computer or the processor executes one or more steps in any of the above methods.

[0462] Those skilled in the art will appreciate that the functions described in conjunction with the various illustrative logic blocks, modules, and algorithm steps disclosed herein can be implemented by hardware, software, firmware, or any combination thereof. If implemented in software, the functions described by the various illustrative logic blocks, modules, and steps may be stored or transmitted as one or more instructions or codes on a computer-readable medium and executed by a hardware-based processing unit. Computer-readable media may include computer-readable storage media, which corresponds to tangible media, such as data storage media, or includes any communication media that facilitates the transfer of computer programs from one place to another (e.g., based on a communication protocol). In this manner, computer-readable media may generally correspond to (1) non-temporary tangible computer-readable storage media, or (2) communication media, such as signals or carrier waves. Data storage media may be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, codes, and / or data structures for implementing the techniques described in this application. A computer program product may include computer-readable media.

[0463] As an example and not limitation, such computer-readable storage media include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, flash memory, or any other media that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer. Also, any connection is properly referred to as a computer-readable medium. For example, if instructions are transmitted from a website, server or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio and microwaves, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio and microwaves are included in the definition of media. However, it should be understood that the computer-readable storage media and data storage media do not include connections, carriers, signals or other temporary media, but are actually directed to non-temporary tangible storage media. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD) and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0464] Instructions may be executed by one or more processors, such as one or more DSPs, general purpose microprocessors, ASICs, FPGAs, or other equivalent integrated or discrete logic circuits. Thus, the term "processor" as used herein may refer to any of the aforementioned structures or any other structures suitable for implementing the techniques described herein. Additionally, in some aspects, the functions described by the various illustrative logic blocks, modules, and steps described herein are provided within dedicated hardware and / or software modules configured for encoding and decoding, or incorporated in a combined codec. Moreover, the techniques may be fully implemented in one or more circuits or logic elements.

[0465] 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 unit is only a logical function division, and there are other division methods in actual implementation, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Optionally, the mutual coupling, direct coupling, or communication connection shown or discussed is an indirect coupling or communication connection through some interfaces, devices or units, such as electrical, mechanical or other forms.

[0466] Optionally, the units described as separate components are or are not physically separated, and the components shown as units are or are not physical units, i.e. located in one place, or distributed over multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0467] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part.

[0468] The above is only a specific implementation of the embodiment of the present application, but the protection scope of the embodiment of the present application is not limited thereto, and any changes or replacements within the technical scope disclosed in the embodiment of the present application should be included in the protection scope of the embodiment of the present application. Therefore, the protection scope of the embodiment of the present application should be based on the protection scope of the claims.

Claims

1. A method for handling billing exceptions, characterized in that: Applied to a first relay charging function R-CHF entity, the method comprises: Receiving a first charging request sent by a charging trigger function CTF entity; Determine that the target CHF entity interaction related to the first charging request is abnormal, and perform abnormal charging processing; the target CHF entity is a main CHF entity or a second R-CHF entity, and the main CHF entity provides online quota management and billing call record generation; the second R-CHF entity is a CHF entity that provides relay for the CTF entity and the main CHF entity before the first R-CHF entity acts as a relay CHF entity.

2. The method according to claim 1, characterized in that When the target CHF is the primary CHF entity, the first charging request is a first charging resource creation request for requesting to create a first charging resource for charging interaction between the CTF entity and the first R-CHF entity, and the performing abnormal charging processing includes: generating a first charging resource for a charging interaction between the CTF entity and the first R-CHF entity; caching the billing information in the first billing request; A first charging response message for responding to the first charging request is sent to the CTF entity, where the first charging response message includes an identifier of the first charging resource.

3. The method according to claim 2, characterized in that If the first charging request includes a quota request, the first response message includes suspended quota indication information or a granted quota, and the suspended quota indication information is used to instruct the CTF entity to continue the service according to a suspended quota management mode.

4. The method according to claim 3, characterized in that When the first charging response message includes the granted quota and the usage of the granted quota by the CTF entity is received, the cached charging information includes a quota suspension identifier corresponding to the usage.

5. The method according to any one of claims 2 to 4, characterized in that: The caching the billing information in the first billing request includes: The billing information is written into the first R-CHF call record or saved in the first billing resource.

6. The method according to any one of claims 2 to 5, characterized in that: The method further comprises: When it is detected that the target CHF entity interaction related to the first charging request is normal, a second charging request is sent to the main CHF entity, wherein the second charging request is a second charging resource creation request, which is used to request the creation of a second charging resource for the charging interaction between the first R-CHF entity and the main CHF entity, or the second charging request is a third charging resource update or release request, which is used to request the update or release of the third charging resource for the charging interaction between the CTF entity and the main CHF entity.

7. The method according to claim 5 or 6, characterized in that: The method further comprises: When it is detected that the target CHF entity interaction related to the first charging request is normal, the first R-CHF call record is sent to the main CHF entity.

8. The method according to claim 6, characterized in that The second charging request carries the cached charging information.

9. The method according to any one of claims 6 to 8, characterized in that: The method further comprises: Before generating the second charging request, sending a notification message to the CTF entity, where the notification message is used to instruct the CTF entity to resume quota management; A third charging request sent by the CTF entity is received, where the third charging request carries a quota request for resuming quota management and a usage amount; and the second charging request includes the quota request and the usage amount carried by the third charging request.

10. The method according to claim 1, characterized in that The target CHF is a primary CHF entity corresponding to the first charging request, the first charging request is a first charging resource update request or a first charging resource release request, which is used to request to update or release a first charging resource for charging interaction between the first R-CHF entity and the CTF entity, and the performing abnormal charging processing includes: caching the billing information of the first billing request; Sending a first charging response message in response to the first charging request to the CTF entity.

11. The method according to claim 10, characterized in that If the first charging request includes a quota request, the first response message includes suspended quota indication information or a granted quota, and the suspended quota indication information is used to instruct the CTF entity to continue the service according to a suspended quota management mode.

12. The method according to claim 10 or 11, characterized in that: The cached billing information includes first billing information and a corresponding quota consumption identifier, or second billing information and a corresponding quota suspension identifier, wherein the first billing information is the billing information in which the available quota granted by the main CHF entity is used, and the second billing information is the billing information in which the available quota granted by the main CHF entity is not used.

13. The method according to claim 12, characterized in that The caching the billing information of the first billing request includes: The first billing information and the corresponding quota consumption identifier, or the second billing information and the corresponding quota suspension identifier are written into the first R-CHF call record or saved in the first billing resource.

14. The method according to any one of claims 10 to 13, characterized in that: The method further comprises: When it is detected that the target CHF interaction related to the first charging request is normal, a second charging request is sent to the main CHF entity, where the second charging request is a second charging resource update request or a second charging resource release request, which is used to request to update or release the second charging resource of the charging interaction between the first R-CHF entity and the main CHF entity.

15. The method according to claim 13 or 14, characterized in that The method further comprises: When it is detected that the target CHF interaction related to the first charging request is normal, the first R-CHF call record is sent to the main CHF entity.

16. The method according to claim 14, characterized in that The second charging request carries the charging information and a corresponding quota suspension identifier or a quota consumption identifier.

17. The method according to claim 14, characterized in that The method further comprises: Before generating the second charging request, sending a notification message to the CTF entity, where the notification message is used to instruct the CTF entity to resume quota management; A third charging request sent by the CTF entity is received, where the third charging request carries a quota request for resuming quota management and a usage amount; and the second charging request includes the quota request and the usage amount carried by the third charging request.

18. The method according to claim 1, characterized in that The target CHF entity is a primary CHF entity corresponding to the first charging request, the first charging request is a one-time event charging request for online direct deduction or offline one-time event charging, and the performing abnormal charging processing includes: caching the billing information of the first billing request; Sending a first charging response message in response to the first charging request to the CTF entity.

19. The method according to claim 18, characterized in that The caching the billing information of the first billing request includes: Writing the charging information and corresponding online direct deduction indication information or offline one-time event charging indication information into the first R-CHF call record; The method further comprises: When it is detected that the target CHF interaction related to the first charging request is normal, the first R-CHF call record is sent to the main CHF entity.

20. The method according to claim 18, characterized in that The caching the billing information of the first billing request includes: The charging information and the corresponding online direct deduction indication information or offline one-time event charging indication information are stored in the first charging resource; The method further comprises: When it is detected that the target CHF interaction related to the first billing request is normal, the second billing request is sent to the main CHF entity, where the second billing request is a one-time event billing request, and the second billing request carries the billing information and corresponding online direct deduction indication information or offline one-time event billing indication information.

21. The method according to claim 1, characterized in that The target CHF entity is the second R-CHF entity, and the first charging request is a first charging resource update request or a first charging resource release request, which is used to request to update or release a first charging resource for charging interaction between the second R-CHF entity and the CTF entity; The performing of abnormal billing processing includes: generating a fourth charging resource between the CTF entity and the first R-CHF entity according to the first charging request, and using the first charging resource identifier as an identifier of the fourth charging resource; generating a second charging request according to the first charging request, and sending the second charging request to the primary CHF entity, wherein the second charging request is used to request creation of a second charging resource for charging interaction between the first R-CHF entity and the primary CHF entity, and the second charging request carries an identifier of the third charging resource; receiving a second charging response message from the primary CHF entity in response to the second charging request; generating a first charging response message for responding to the first charging request according to the second charging response message; the second charging response message carrying an identifier of the second charging resource; Sending the first charging response message to the CTF entity.

22. A method for handling billing exceptions, characterized in that: The method is applied to a main charging function CHF entity, and the main CHF entity provides online quota management and billing call record generation, and the method includes: Receiving relevant billing information cached by the first R-CHF entity, where the relevant billing information cached is carried in a billing call bill or a billing message, and the relevant billing information cached includes billing information and a corresponding quota suspension identifier or quota consumption identifier; Billing processing is performed according to the quota suspension identifier or the quota consumption identifier.

23. The method according to claim 22, characterized in that The billing process is performed according to the quota suspension identifier or the quota consumption identifier, including: Directly deducting the service usage in the billing information from the corresponding account balance in the billing resource of the primary CHF entity; The method further comprises: If the cached billing information has a corresponding quota consumption identifier, the service usage in the billing information is directly deducted from the corresponding account of the second billing resource, and the locked account balance is released at the same time; or, If the cached billing information includes billing information without quota management, the billing information without quota management is written into the main CHF bill.

24. A method for handling billing exceptions, characterized in that: The method is applied to a charging system, the charging system comprising a first relay charging function R-CHF entity, a second R-CHF entity, a charging trigger function CTF entity and a main CHF entity, and the method further comprises: The CTF entity sends a first charging request to the first R-CHF entity; The first R-CHF entity determines that the target CHF entity interaction related to the first charging request is abnormal, and performs abnormal charging processing; The target CHF entity is the main CHF entity or the second R-CHF entity, the main CHF entity provides online quota management and billing call record generation; the second R-CHF entity is a CHF entity that provides relay for the CTF entity and the main CHF entity before the first R-CHF entity acts as a relay CHF entity.

25. A billing system, characterized in that: The charging system comprises a first relay charging function R-CHF entity, a second R-CHF entity, a charging trigger function CTF entity and a main CHF entity, The CTF entity is used to send a first charging request to the first R-CHF entity; The first R-CHF entity is used to determine that the target CHF entity interaction related to the first charging request is abnormal, and perform abnormal charging processing; The target CHF entity is the main CHF entity or the second R-CHF entity, the main CHF entity provides online quota management and billing call record generation; the second R-CHF entity is a CHF entity that provides relay for the CTF entity and the main CHF entity before the first R-CHF entity acts as a relay CHF entity.

26. A first relay charging function R-CHF entity, characterized in that: The method comprises a functional unit for implementing the method according to any one of claims 1 to 21.

27. A CHF entity, characterized in that: It comprises a functional unit for implementing the method according to any one of claims 22-23.

28. A first relay charging function R-CHF entity, characterized in that: The method comprises a processor and a memory, wherein the memory is used to store program codes, and the processor is used to execute the program codes to implement the method according to any one of claims 1 to 21.

29. A home charging function CHF entity, characterized in that: The method comprises a processor and a memory, wherein the memory is used to store program codes, and the processor is used to execute the program codes to implement the method according to any one of claims 22 to 23.

30. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 23 is implemented.

Images