Charging method and related equipment

Abstract

The invention relates to the field of charging. Specifically, the invention relates to a charging method and related equipment. The method comprises the following steps: a first R-CHF entity receives a first charging request from a charging trigger function CTF entity, wherein the first charging request is used for requesting to create or update or release a first charging resource; the first R-CHF entity sends a second charging request to the main CHF entity; the second charging request is used for a second charging resource, and the second charging resource is a charging resource between the R-CHF entity and the main CHF entity; the first R-CHF entity receives a second charging response message sent by the main CHF entity and used for responding to the second charging request; and the first R-CHF entity sends a first charging response message to the CTF entity. By adopting the scheme provided by the invention, the normal charging can be ensured when the main CHF entity cannot provide the charging service.

Description

Technical Field

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

[0002] In the 5G architecture, the billing architecture adopts the integrated architecture of online billing and offline billing. Figure 1 As shown in the figure: The converged charging system (CCS) is a charging system that integrates online charging and offline 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] When the location of the user equipment changes or the user uses a new service, the CHF entity to which the user equipment belongs cannot continue to provide billing services, which may cause user service interruption or operator loss. Summary of the invention

[0006] The embodiment of the present application provides a billing method and related equipment. The embodiment of the present application can ensure that billing is performed normally when the main CHF entity cannot provide billing services, and is conducive to avoiding the problem of billing errors caused by capability differences.

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

[0008] The first R-CHF entity receives a first charging request from a charging trigger function CTF entity, where the first charging request is used to request the creation, update or release of a first charging resource, where the first charging resource is a charging resource for charging interaction between the CTF entity and the first R-CHF entity; the first R-CHF entity sends a second charging request to the main CHF entity according to the first charging request; the second charging request is used for a second charging resource, where the second charging resource is a charging resource for charging interaction between the first R-CHF entity and the main CHF entity; the first R-CHF entity receives a second charging request sent by the main CHF entity in response to the second charging request The first R-CHF entity generates a first charging response message for responding to the first charging request according to the second charging response message, and sends a first charging response message to the CTF entity, wherein the first charging response message includes fourth capability information, and the fourth capability information is capability information determined by the first R-CHF entity according to the third capability information and used for interaction between the first R-CHF entity and the CTF entity.

[0009] By introducing the R-CHF entity, normal billing can be ensured when the main CHF entity cannot provide billing services; and capability negotiation between the CTF entity, the first R-CHF entity and the main CHF entity is conducive to solving the problem of billing errors caused by capability differences.

[0010] In combination with the first aspect, in a possible implementation manner, the first charging request also includes first capability information; the first capability information is capability information provided by the CTF entity and can be used for the first R-CHF entity to interact with the CTF entity; the second charging request includes second capability information, the second capability information represents the capability for the main CHF entity to interact with the first R-CHF entity, and the second capability information is determined by the first R-CHF entity based on the first capability information; the third capability information is determined by the main CHF entity based on the second capability information.

[0011] The master CHF entity considers the capability information of the CTF entity and the capability information of the first R-CHF entity when determining the capability information, which is further helpful to solve the problem of billing errors caused by capability differences.

[0012] In combination with the first aspect, in a possible implementation manner, the first capability information includes at least one of a first payload size of a charging message for a first charging resource supported by the CTF entity, a first idle time for charging information collection of the CTF entity for the first charging resource, or a first charging characteristic;

[0013] The fourth capability information includes at least one of a fourth payload size of a charging message for the first charging resource, a fourth idle time for charging information collection of a CTF entity for the first charging resource, a fourth charging characteristic, or a first charging resource trigger condition setting;

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

[0015] The third capability information includes at least one of a third payload size for charging messages in the second charging resource, a third idle time for charging information collection of the first R-CHF entity for the second charging resource, a third charging characteristic, or a second charging resource trigger condition setting.

[0016] The charging message for the first charging resource is a message exchanged between the first R-CHF entity and the CTF entity, such as a first charging request and a first charging response message. The charging message for the second charging resource is information exchanged between the first R-CHF entity and the main CHF entity, such as a second charging request and a second charging response message.

[0017] In combination with the first aspect, in a possible implementation manner, the second capability information is determined by the first R-CHF entity according to the first capability information, including:

[0018] When the first capability information includes the first payload size, the second capability information also includes the second payload size, and the second payload size is the smaller of the first payload size and the payload size of the billing message supported by the first R-CHF entity for the first billing resource; when the first capability information includes the first idle duration, the second capability information also includes the second idle duration, and the second idle duration is the smaller of the first idle duration and the idle duration for billing information collection of the first R-CHF entity for the second billing resource; when the first capability information includes the first billing characteristic, the second capability information also includes the second billing characteristic, and the second billing characteristic is the intersection of the first billing characteristic and the billing characteristic supported by the first R-CHF entity.

[0019] The above method can realize capability negotiation between the CTF entity and the first R-CHF entity.

[0020] In combination with the first aspect, in a possible implementation manner, when the third capability information includes the first payload size, the fourth capability information also includes the fourth payload size, and if the second capability information includes the second payload size, the fourth payload size is the third payload size; if the second capability information does not include the second payload size, the fourth payload size is the smaller of the third payload size and the payload size of the charging message for the first charging resource supported by the first R-CHF entity;

[0021] When the third capability information includes the third idle duration, the fourth capability information also includes the fourth idle duration, and if the second capability information includes the third idle duration, the fourth idle duration is the third idle duration; if the second capability information does not include the second idle duration, the fourth idle duration is the smaller of the third idle duration and the idle duration for charging information collection of the first R-CHF entity for the second charging resource;

[0022] If the third capability information includes the third charging characteristic, the fourth capability information also includes the fourth charging characteristic. If the second charging characteristic is included, the fourth charging characteristic is the third charging characteristic. If the second capability information does not include the second charging characteristic, the fourth charging characteristic is the intersection of the third charging characteristic and the charging characteristics supported by the first R-CHF entity.

[0023] The above method can realize the capability negotiation among the CTF entity, the first R-CHF entity and the main CHF entity.

[0024] In combination with the first aspect, in a possible implementation manner, the third capability information includes a second charging resource trigger condition setting, and the fourth capability information also includes a first charging resource trigger condition setting, and the state information in the first charging resource trigger condition setting is a union of the state information in the second charging resource trigger condition setting and the state information of the trigger condition determined by the first R-CHF entity;

[0025] The threshold value of the trigger condition in the first charging resource trigger condition setting is the smaller one of the threshold value of the trigger condition in the second charging resource trigger condition setting and the threshold value of the trigger condition determined by the first R-CHF entity.

[0026] The above method can realize the capability negotiation among the CTF entity, the first R-CHF entity and the main CHF entity.

[0027] In combination with the first aspect, in a possible implementation manner, the first charging request is used to request creation of a first charging resource, and the method of this embodiment further includes:

[0028] When the first billing request is used to request session-based convergent billing, the first R-CHF entity generates a first billing resource corresponding to the first billing request; the first R-CHF entity opens the first R-CHF call record in the first billing resource, and writes the billing information in the first billing request into the first R-CHF call record; when the first billing request is used to request one-time event billing, the first billing resource corresponding to the first billing request is generated, the first R-CHF entity generates a first R-CHF call record based on the first billing resource and the billing information of the first billing request, and the first R-CHF call record includes the billing information in the first billing request.

[0029] In combination with the first aspect, in a possible implementation manner, the first charging request carries an identifier of a second charging resource generated by the primary CHF entity, and the method of this embodiment further includes:

[0030] The first R-CHF entity generates a second charging request according to the identifier of the second charging resource, where the second charging request is used to request to update or release the second charging resource.

[0031] The second charging request includes an identifier of a second charging resource, and the second charging resource is a charging resource generated by the primary CHF entity.

[0032] In combination with the first aspect, in a possible implementation manner, the second charging request further carries a notification receiving address of the first R-CHF, where the notification receiving address is used to update a notification address corresponding to the second charging resource on the primary CHF entity.

[0033] The notification address is used by the main CHF entity to subsequently send a notification message to the first R-CHF entity.

[0034] In combination with the first aspect, in a possible implementation manner, the second charging request is used to request updating or releasing the second charging resource update, and the second charging request carries adjustment indication information, which is used to indicate that the first R-CHF entity has adjusted the trigger condition setting sent by the main CHF entity.

[0035] In combination with the first aspect, in a possible implementation manner, the first charging request is used to update or release the first charging resource, and the method of this embodiment further includes:

[0036] The first R-CHF entity determines a second R-CHF entity, where the second R-CHF entity is a CHF entity that provides relay capability for the CTF entity and the main CHF entity before the first R-CHF entity acts as a relay CHF entity; the first R-CHF entity obtains relevant information about the first billing resource from the second R-CHF entity, and the first billing information is a billing resource generated by the second R-CHF entity.

[0037] In combination with the first aspect, in a possible implementation manner, the first charging request carries the switching information of the second R-CHF entity to the first R-CHF entity, and the first R-CHF entity obtains the relevant information of the first charging resource from the second R-CHF entity, including:

[0038] The first R-CHF entity obtains first charging resource information from the second R-CHF entity according to the switching information;

[0039] The method of this embodiment also includes: the first R-CHF entity generates a second charging request according to the acquired first charging resource information.

[0040] The switching from the second R-CHF entity to the first R-CHF entity is achieved by acquiring the first charging resource generated by the second R-CHF entity.

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

[0042] The first R-CHF entity receives a remove R-CHF request sent by the CTF entity; the remove R-CHF request includes a remove indication, and the remove indication is used for the first R-CHF to return relevant information of the second billing resource generated by the main CHF entity; and sends a remove response message to the CTF entity, where the remove response message includes relevant information of the second billing resource generated by the main CHF entity.

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

[0044] The first R-CHF entity releases the first charging resource according to the remove R-CHF request, and the remove response message also includes a first charging resource release result.

[0045] When the first R-CHF entity provides a relay function between the CTF entity and the main CHF entity, if the main CHF entity can directly provide billing for the CTF entity, the first R-CHF entity is removed, which simplifies the billing system and reduces the power consumption of the first R-CHF entity.

[0046] In a second aspect, an embodiment of the present application provides another charging method. The method is applied to a CTF entity. The method includes:

[0047] The CTF entity sends a charging request to the first R-CHF entity, when the charging request is a request to remove the R-CHF on the premise that the charging resources have been established on the first R-CHF entity and the main CHF entity; the request to remove the R-CHF includes a removal indication, and the removal indication is used to instruct the R-CHF to return the relevant information of the second charging resource generated by the main CHF entity; the main CHF entity provides online quota management and billing call record generation;

[0048] The method of this embodiment also includes:

[0049] The CTF entity receives a removal response message sent by the first R-CHF entity, where the removal response message includes relevant information of the second billing resource generated by the primary CHF entity, and the relevant information of the first billing resource includes a second billing resource identifier; the CTF entity sends a third billing request to the primary CHF according to the second billing resource identifier, where the third billing request is an operation request for the second billing resource.

[0050] The third charging request is a charging resource update request or a charging resource release request.

[0051] In combination with the second aspect, in a possible implementation manner, before or after sending the third charging request, the method of this embodiment further includes:

[0052] The CTF entity sends a release billing resource request to the first R-CHF entity, where the release billing resource request is used to request the release of relevant information of the billing resources created by the first R-CHF entity; the CTF entity receives a release billing resource response message sent by the first R-CHF entity, where the release billing resource response message is used to indicate that the first R-CHF entity has released relevant information of the billing resources created by the first R-CHF entity.

[0053] When the first R-CHF entity provides a relay function between the CTF entity and the main CHF entity, if the main CHF entity can directly provide billing for the CTF entity, the first R-CHF entity is removed, which simplifies the billing system and reduces the power consumption of the first R-CHF entity.

[0054] In conjunction with the second aspect, in a possible implementation, when the charging request is an insert R-CHF request under the premise that charging resources have been established on the CTF entity and the primary CHF entity, the insert R-CHF request includes relevant information of the second charging resource generated by the primary CHF entity;

[0055] The method of this embodiment further includes: the CTF entity receives a charging response message sent by the first R-CHF entity, where the charging response message includes a result of the first R-CHF sending a third charging request to the primary CHF according to relevant information of the second charging resource.

[0056] 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 generation unit.

[0057] A transceiver unit, configured to receive a first charging request from a charging trigger function CTF entity, the first charging request creating, updating or releasing a first charging resource;

[0058] The transceiver unit is further configured to send a second charging request to the primary CHF entity; the second charging request is used to request to create, update or release a second charging resource; receive a second charging response message sent by the primary CHF entity to respond to the second charging request, the second charging response message including third capability information, the third capability information being capability information determined by the primary CHF entity according to the second charging request for interaction between the primary CHF entity and the first R-CHF entity;

[0059] The generating 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,

[0060] The transceiver unit is further used to send a first charging response message to the CTF entity, where the first charging response message includes fourth capability information, where the fourth capability information is capability information determined by the first R-CHF according to the third capability information for interaction between the first R-CHF entity and the CTF entity.

[0061] In combination with the third aspect, in a possible implementation, the first charging request also includes first capability information; the first capability information is capability information provided by the CTF entity and can be used for the first R-CHF entity to interact with the CTF entity; the second charging request includes second capability information, the second capability information represents the capability for the main CHF entity to interact with the first R-CHF entity, and the second capability information is determined by the first R-CHF entity based on the first capability information; the third capability information is determined by the main CHF entity based on the second capability information.

[0062] In conjunction with the third aspect, in a possible implementation manner, the first capability information includes at least one of a payload size of a charging message for a first charging resource supported by the CTF entity, a first idle duration for charging information collection of the CTF entity for the first charging resource, or a charging characteristic;

[0063] The fourth capability information includes at least one of a payload size of a charging message for the first charging resource, a fourth idle time for charging information collection of a CTF entity for the first charging resource, a charging characteristic, or a trigger condition setting of the first charging resource;

[0064] The second 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 of charging information collection of the first R-CHF entity for the second charging resource, or a charging characteristic;

[0065] The third capability information includes at least one of a payload size of a charging message in a second charging resource, a third idle time for charging information collection of a first R-CHF entity for the second charging resource, a charging characteristic, or a second charging resource trigger condition setting.

[0066] In conjunction with the third aspect, in a possible implementation manner, the second capability information is determined by the first R-CHF entity according to the first capability information, including:

[0067] When the first capability information includes a first payload size, the second capability information also includes a second payload size, and the second payload size is the smaller of the first payload size and the payload size of the billing message supported by the first R-CHF entity for the first billing resource; when the first capability information includes a first idle duration, the second capability information also includes a second idle duration, and the second idle duration is the smaller of the first idle duration and the idle duration for billing information collection of the first R-CHF entity for the second billing resource; when the first capability information includes a first billing characteristic, the second capability information also includes a second billing characteristic, and the second billing characteristic is the intersection of the first billing characteristic and the billing characteristic supported by the first R-CHF entity.

[0068] The above method can realize capability negotiation between the CTF entity and the first R-CHF entity.

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

[0070] When the third capability information includes the first payload size, the fourth capability information also includes the fourth payload size, and if the second capability information includes the second payload size, the fourth payload size is the third payload size; if the second capability information does not include the second payload size, the fourth payload size is the smaller of the third payload size and the payload size of the charging message for the first charging resource supported by the first R-CHF entity;

[0071] When the third capability information includes the third idle duration, the fourth capability information also includes the fourth idle duration, and if the second capability information includes the third idle duration, the fourth idle duration is the third idle duration; if the second capability information does not include the second idle duration, the fourth idle duration is the smaller of the third idle duration and the idle duration for charging information collection of the first R-CHF entity for the second charging resource;

[0072] If the third capability information includes the third charging characteristic, the fourth capability information also includes the fourth charging characteristic. If the second charging characteristic is included, the fourth charging characteristic is the third charging characteristic. If the second capability information does not include the second charging characteristic, the fourth charging characteristic is the intersection of the third charging characteristic and the charging characteristics supported by the first R-CHF entity.

[0073] In combination with the third aspect, in a possible implementation manner, the third capability information includes a second charging resource trigger condition setting, and the fourth capability information also includes a first charging resource trigger condition setting, and the status information in the first charging resource trigger condition setting is a union of the status information in the trigger condition setting of the second charging resource and the status information of the trigger condition determined by the first R-CHF entity;

[0074] The threshold value of the trigger condition in the first charging resource trigger condition setting is the smaller one of the threshold value of the trigger condition in the second charging resource trigger condition setting and the threshold value of the trigger condition determined by the first R-CHF entity.

[0075] In conjunction with the third aspect, in a possible implementation manner, the first R-CHF entity further includes:

[0076] The execution unit is used to execute the billing process according to the first billing request.

[0077] In conjunction with the third aspect, in a possible implementation manner, the first charging request is used to request creation of a first charging resource, and the first R-CHF entity further includes an execution unit, which is used to:

[0078] When the first billing request is used to request session-based convergent billing, a first billing resource corresponding to the first billing request is generated; a first R-CHF call record in the first billing resource is opened, and the billing information in the first billing request is written into the first R-CHF call record; when the first billing request is used to request one-time event billing, a first billing resource corresponding to the first billing request is generated, and a first R-CHF call record is generated according to the first billing resource and the billing information of the first billing request, and the first R-CHF call record includes the billing information in the first billing request.

[0079] In combination with the third aspect, in a possible implementation manner, the first charging request carries an identifier of a second charging resource generated by the primary CHF entity, and the first R-CHF entity further includes an execution unit, which is configured to:

[0080] A second charging request is generated according to the identifier of the second charging resource, where the second charging request is used to request updating or releasing the second charging resource.

[0081] In combination with the third aspect, in a possible implementation manner, the second charging request further carries a notification receiving address of the first R-CHF, where the notification receiving address is used to update a notification address corresponding to the second charging resource on the primary CHF entity.

[0082] The notification address is used by the main CHF entity to subsequently send a notification message to the first R-CHF entity.

[0083] In combination with the third aspect, in a possible implementation, the second charging request is used to request updating or releasing the second charging resource, and the second charging request carries adjustment indication information, where the indication information is used to indicate that the first R-CHF entity has adjusted the trigger condition setting sent by the main CHF entity.

[0084] In conjunction with the third aspect, in a possible implementation manner, the first charging request is used to update or release the first charging resource, and the first R-CHF entity further includes an execution unit, which is used to:

[0085] Determine a second R-CHF entity, where the second R-CHF entity is a CHF entity that provides relay capability for the CTF entity and the main CHF entity before the first R-CHF entity serves as a relay CHF entity; obtain relevant information of the first billing resource from the second R-CHF entity, where the first billing information is a billing resource generated by the second R-CHF entity.

[0086] In conjunction with the third aspect, in a possible implementation manner, the first charging request carries the switching information of the second R-CHF entity to the first R-CHF entity, and in terms of obtaining the relevant information of the first charging resource from the second R-CHF entity, the execution unit is specifically used to:

[0087] Acquire first charging resource information from the second R-CHF entity according to the switching information,

[0088] The generating unit is further configured to generate a second charging request according to the acquired first charging resource information.

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

[0090] receiving a remove R-CHF request sent by a CTF entity; the remove R-CHF request includes a remove indication, where the remove indication is used for the first R-CHF to return relevant information of a second charging resource generated by a main CHF entity; and sending a remove response message to the CTF entity, where the remove response message includes relevant information of the second charging resource generated by the main CHF entity.

[0091] In conjunction with the third aspect, in a possible implementation manner, the first R-CHF entity further includes:

[0092] The releasing unit is used to release the first charging resource according to the remove R-CHF request, and the remove response message also includes the first charging resource release result.

[0093] In a fourth aspect, an embodiment of the present application further provides a CTF entity, including: a sending unit and a receiving unit.

[0094] A sending unit, configured to send a charging request to a first R-CHF entity, when the charging request is a request to remove the R-CHF on the premise that charging resources have been established between the first R-CHF entity and the main CHF entity; the request to remove the R-CHF includes a removal indication, the removal indication is used to instruct the R-CHF to return the relevant information of the second charging resource generated by the main CHF entity; the main CHF entity provides online quota management and charging call record generation;

[0095] A receiving unit, configured to receive a removal response message sent by the first R-CHF entity, where the removal response message includes relevant information of the second charging resource generated by the primary CHF entity, and the relevant information of the first charging resource includes a second charging resource identifier;

[0096] The sending unit is further configured to send a third charging request to the primary CHF according to the second charging resource identifier, where the third charging request is an operation request for the second charging resource.

[0097] In conjunction with the fourth aspect, in a possible implementation, before or after the sending unit sends the third charging request,

[0098] The sending unit is further used to send a request to release charging resources to the first R-CHF entity, where the request to release charging resources is used to request to release relevant information of the charging resources created by the first R-CHF entity;

[0099] The receiving unit is further configured to receive a release charging resource response message sent by the first R-CHF entity, where the release charging resource response message is used to indicate that the first R-CHF entity has released relevant information of the charging resources created by the first R-CHF entity.

[0100] In conjunction with the fourth aspect, in a possible implementation, when the charging request is an insert R-CHF request under the premise that charging resources have been established on the CTF entity and the primary CHF entity, the insert R-CHF request includes relevant information of the second charging resource generated by the primary CHF entity;

[0101] The receiving unit is configured to receive a charging response message sent by the first R-CHF entity, wherein the charging response message includes a result that the first R-CHF sends a third charging request to the main CHF according to relevant information of the second charging resource.

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

[0103] In a sixth aspect, an embodiment of the present application provides a CTF 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.

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

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

[0106] In a ninth aspect, an embodiment of the present application further provides a charging method, which is applied to a charging system, the charging system including a first R-CHF entity, a CTF entity and a main CHF entity, and the charging method includes:

[0107] The CTF entity sends a first charging request to the first R-CHF entity, where the first charging request is used to request to create, update or release a first charging resource;

[0108] The first R-CHF entity sends a second charging request to the main CHF entity; the second charging request is used to request to create, update or release a second charging resource; the main CHF entity provides online quota management and charging call record generation;

[0109] The primary CHF entity performs charging processing according to the second charging request, and generates a second charging response message for responding to the second charging request; sends the second charging response message to the first R-CHF entity, where the second charging response message includes third capability information, where the third capability information is capability information determined by the primary CHF according to the second charging request for interaction between the primary CHF entity and the first R-CHF entity;

[0110] The first R-CHF entity generates a first charging response message for responding to the first charging request according to the second charging response message, sending the first charging response message to the CTF entity, where the first charging response message includes fourth capability information, where the fourth capability information is capability information determined by the first R-CHF according to the third capability information for interaction between the first R-CHF entity and the CTF entity;

[0111] The CTF entity performs charging processing according to the first charging response message.

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

[0113] The CTF entity is used to send a first charging request to the first R-CHF entity, where the first charging request is used to request to create, update or release a first charging resource;

[0114] The first R-CHF entity is used to send a second charging request to the main CHF entity; the second charging request is used to request to create, update or release a second charging resource; the main CHF entity provides online quota management and charging call record generation;

[0115] The main CHF entity is configured to perform charging processing according to the second charging request and generate a second charging response message for responding to the second charging request; send the second charging response message to the first R-CHF entity, where the second charging response message includes third capability information, where the third capability information is capability information determined by the main CHF according to the second charging request for interaction between the main CHF entity and the first R-CHF entity;

[0116] a first R-CHF entity, configured to generate a first charging response message for responding to the first charging request according to the second charging response message, and send a first charging response message to the CTF entity, where the first charging response message includes fourth capability information, where the fourth capability information is capability information determined by the first R-CHF according to the third capability information for interaction between the first R-CHF entity and the CTF entity;

[0117] The CTF entity is used to perform charging processing according to the first charging response message.

[0118] 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 above refers 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 CTF 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

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

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

[0121] Figure 3 A flowchart of a billing method provided in an embodiment of the present application;

[0122] Figure 4 A flowchart of another billing method provided in an embodiment of the present application;

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

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

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

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

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

[0128] Fig.10 A schematic diagram of the structure of a CTF entity provided in an embodiment of the present application;

[0129] Fig.11 A schematic diagram of the structure of another first R-CHF entity provided in an embodiment of the present application;

[0130] Fig.12 A schematic diagram of the structure of another CTF entity provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0132] "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.

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

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

[0135] Optionally, the R-CHF entity is a local CHF entity, an edge CHF entity or a service CHF entity. The edge CHF entity is a CHF entity that provides charging for edge services.

[0136] 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, the recharge center, the billing capability service system, the accounting system, etc. to manage the account information and contract information of the user equipment. The main CHF entity 203 usually does not change with the change of the location of the user equipment.

[0137] For a certain user equipment, when the user uses a service that exceeds the processing scope of the main CHF 203 of the user equipment, etc., resulting in the main CHF entity 203 being unable to provide billing, the connection between the CTF entity 201 and the main CHF entity 203 can be realized through the R-CHF entity 202. The R-CHF entity generates a first billing resource for the CTF entity, establishes and maintains an 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. Optionally, the R-CHF entity 202 and the main CHF entity 203 belong to the same operator or to different operators. As the user moves or the user accesses a change in the service, the R-CHF entity 202 may change.

[0138] In one example, the functions of the R-CHF entity 202 include but are not limited to: discovery of the main CHF entity 203 , forwarding of charging information, generation of R-CHF charging bills, and insertion, removal and switching of the R-CHF entity 202 .

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

[0140] See also Figure 3 , Figure 3 A flowchart of a charging method provided in an embodiment of the present application is provided. The method is applied to a first R-CHF entity. In one example, the first R-CHF entity is Figure 2 R-CHF entity 202 in. Figure 3 As shown, the method includes:

[0141] S301: A first R-CHF entity receives a first charging request from a CTF entity.

[0142] The first charging request is used to request to create, update or release a first charging resource, and the first charging resource is a charging resource for charging interaction between the CTF entity and the first R-CHF entity.

[0143] Optionally, the first charging request includes first capability information, where the first capability information is capability information provided by the CTF entity and can be used for interaction between the first R-CHF entity and the CTF entity.

[0144] In one example, the first capability information includes at least one of a payload size of a charging message for a first charging resource supported by the CTF entity, a first idle duration for charging information collection of the CTF entity for the first charging resource, or a charging characteristic. In another example, the charging characteristic is a characteristic defined in 6.1.8 of 3GPP TS 32.291, and whether the quota management suspension capability is supported.

[0145] The charging message of the first charging resource refers to a message exchanged between the first R-CHF entity and the CTF entity through the first charging resource, such as a first charging request message and a first charging response message.

[0146] S302: The first R-CHF entity generates a second charging request according to the first charging request, and sends the second charging request to the main CHF entity.

[0147] The second charging request is used to request to create, update or release a second charging resource, and the second charging resource is a charging resource for charging interaction between the first R-CHF entity and the main CHF entity.

[0148] Optionally, the second charging request includes second capability information, where the second capability information represents a capability for the primary CHF entity to interact with the first R-CHF entity. The second capability information is determined by the first R-CHF entity according to the first capability information.

[0149] In one example, the second 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 charging characteristic.

[0150] The charging message used for the second charging resource is information exchanged between the first R-CHF entity and the main CHF entity, such as a second charging request and a second charging response message.

[0151] In a specific implementation manner, the second capability information is determined by the first R-CHF entity according to the first capability information, including:

[0152] When the first capability information includes the first payload size, the second capability information also includes the second payload size, and the second payload size is the smaller of the first payload size and the payload size of the charging message for the second charging resource supported by the first R-CHF entity; when the first capability information does not include the payload size, the second capability information may include the payload size or may not include the payload size, in which case, when the second capability information includes the payload size, the payload size of the second capability information is the payload size of the charging message supported by the first R-CHF entity;

[0153] When the first capability information includes the first idle duration, the second capability information also includes the second idle duration, and the second idle duration is the smaller of the first idle duration and the idle duration for collecting the charging information of the first R-CHF entity used for the second charging resource; when the first capability information includes the first idle duration, the second capability information may include the second idle duration or may not include the second idle duration, in which case, when the second capability information includes the second idle duration, the second idle duration is the idle duration for collecting the charging information of the first R-CHF entity used for the second charging resource;

[0154] When the first capability information includes the billing characteristic, the second capability information also includes the billing information, and the billing characteristic of the second capability information is the intersection of the billing characteristic of the first capability information and the billing characteristic supported by the first R-CHF entity; when the first capability information does not include the billing characteristic, the second capability information may include the billing characteristic or may not include the billing characteristic. At this time, when the second capability information includes the billing characteristic, the billing characteristic of the second capability information is the billing characteristic supported by the first R-CHF entity.

[0155] It should be pointed out that the above-mentioned capability information determination process is for the scenario where the first billing request is used to request session-based converged billing. For the scenario where the first billing request is used to request one-time event billing, the second billing request carries the billing information in the first billing request sent by CTF, but does not carry the first capability information.

[0156] S303: The first R-CHF entity receives a second charging response message sent by the primary CHF entity to respond to the second charging request.

[0157] The second charging response message includes third capability information; the third capability information is capability information used for interaction between the main CHF entity and the first R-CHF entity, determined by the main CHF entity according to the second charging request.

[0158] In a specific example, when the second charging request does not include the second capability information, the third capability information is capability information supported and provided by the main CHF entity for the interaction between the main CHF entity and the first R-CHF entity; when the second charging request includes the second capability information, the third capability information is capability information determined by the main CHF entity according to the second capability information for the interaction between the main CHF entity and the first R-CHF entity.

[0159] In one example, the third capability information includes at least one of a payload size of a billing message for a second billing resource, a third idle time for billing information collection of a first R-CHF entity for the second billing resource, a fourth billing characteristic, or a second billing resource trigger setting.

[0160] In a specific implementation manner, the third capability information is determined by the master CHF entity according to the second capability information, including:

[0161] When the second capability information includes the second payload size, the third capability information also includes the third payload size, and the third payload size is the smaller of the second payload size and the payload size of the charging message for the second charging resource supported by the primary CHF entity; when the second capability information does not include the second payload size, the third capability information may include the third payload size or may not include the third payload size, and when the third capability information includes the third payload size, the third payload size is the payload size of the charging message for the second charging resource supported by the primary CHF entity;

[0162] When the second capability information includes the second idle duration, the third capability information also includes the third idle duration, and the third idle duration is the smaller of the second idle duration and the idle duration for the second billing resource supported by the primary CHF entity; when the second capability information does not include the second idle duration, the third capability information may include the third idle duration or may not include the third idle duration. At this time, when the third capability information includes the third idle duration, the billing resource idle duration of the third capability information is the idle duration for the second billing resource supported by the primary CHF entity;

[0163] When the second capability information includes the second charging characteristic, the third capability information also includes the third charging information, and the third charging characteristic is the intersection of the second charging characteristic and the charging characteristic supported by the primary CHF entity; when the second capability information does not include the second charging characteristic, the third capability information may include the third charging characteristic or may not include the third charging characteristic, and when the third capability information includes the third charging characteristic, the third charging characteristic is the charging characteristic supported by the primary CHF entity.

[0164] The third capability information may also include a second billing resource trigger condition setting, and the second billing resource trigger condition setting includes: trigger status information (such as: trigger list, activation / deactivation status of the trigger in the list, immediate reporting / delayed reporting status of the trigger in the list), trigger threshold value (some triggers have thresholds, such as: threshold value of statistical duration or traffic or number of events).

[0165] S304: The first R-CHF entity generates a first charging response message for responding to the first charging request according to the second charging response message, and sends the first charging response message to the CTF entity.

[0166] The first charging response message includes fourth capability information, and the fourth capability information is capability information determined by the first R-CHF entity according to the third capability information and used for interaction between the first R-CHF entity and the CTF entity.

[0167] In an example, the fourth capability information includes at least one of a payload size of a charging message in a first charging resource, an idle time of the first charging resource, a charging feature supported by the first charging resource, or a trigger setting of the first charging resource.

[0168] In a specific embodiment, the fourth capability information is determined by the first R-CHF entity according to the third capability information, and includes:

[0169] When the third capability information includes the third payload size, the fourth capability information also includes the fourth payload size, and the fourth payload size is the smaller of the third payload size and a payload size of a charging message for a first charging resource supported by the first R-CHF entity.

[0170] When the third capability information includes the third idle duration, the fourth capability information also includes the fourth idle duration, and the fourth idle duration is the smaller of the third idle duration and the idle duration for charging information collection of the first R-CHF entity for the second charging resource.

[0171] When the third capability information includes the third charging characteristic, the fourth capability information also includes the fourth charging characteristic, and the fourth charging characteristic is an intersection of the third charging characteristic and the charging characteristic supported by the first R-CHF entity.

[0172] When the third capability information includes the second charging resource trigger condition setting, the fourth capability information includes the first charging resource trigger condition setting. The trigger state information in the first charging resource trigger condition setting is the union of the trigger state information in the second charging resource trigger condition setting and the trigger state information determined by the first R-CHF entity, and the trigger threshold limit in the first charging resource trigger condition setting is the smaller of the trigger threshold limit in the second charging resource trigger condition setting and the trigger threshold limit determined by the first R-CHF entity.

[0173] In a specific implementation manner, when the second charging request includes the second capability information, the fourth capability information is determined by the first R-CHF entity according to the third capability information and the second capability information, including:

[0174] When the third capability information includes the third payload size, the fourth capability information also includes the fourth payload size, and if the second capability information includes the second payload size, the fourth payload size is the third payload size. It should be noted that, since the second payload size has been considered when determining the third payload size, the fourth payload size here implies the smaller of the third payload size and the payload size of the charging message for the second charging resource supported by the first R-CHF entity.

[0175] When the third capability information includes the third idle duration, the fourth capability information also includes the fourth idle duration, and if the second capability information includes the second idle duration, the fourth idle duration is the third idle duration. It should be noted that, since the second idle duration has been considered when determining the third idle duration, the fourth idle duration here is implicitly the smaller of the third idle duration and the idle duration for charging information collection of the first R-CHF entity for the second charging resource.

[0176] When the third capability information includes the third charging characteristic, the fourth capability information also includes the fourth charging characteristic, and if the second capability information includes the second charging characteristic, the fourth charging characteristic is the third charging characteristic. It should be noted that, since the second charging characteristic has been considered when determining the third charging characteristic, the fourth charging characteristic here is implicitly the intersection of the third charging characteristic and the charging characteristics supported by the first R-CHF entity.

[0177] Among them, the Trigger setting of the third capability information is used to indicate the triggering condition and method for the main CHF entity to instruct the first R-CHF to report the charging information in the second charging resource, and the Trigger setting of the fourth capability information is used to indicate the triggering condition and method for the first R-CHF entity to instruct the CTF entity to report the charging information.

[0178] The trigger setting includes the state information of the trigger setting and the threshold value of the trigger setting; the state information of the trigger setting includes: the activation state of the trigger, the immediate reporting / delayed reporting state of the activated trigger, and the threshold value of the activated trigger, such as the threshold value of the statistical duration, traffic, or number of events.

[0179] In one example, the trigger status information in the first charging resource trigger condition setting (i.e., the status information of the Trigger setting of the fourth capability information) is the union of the trigger status information in the second charging resource trigger condition setting (i.e., the status information of the Trigger setting of the third capability information) and the status information of the Trigger setting determined by the first R-CHF entity, including:

[0180] When the Trigger of the third capability information is set to an activated state and / or the Trigger determined by the first R-CHF entity is set to an activated state, the Trigger of the fourth capability information is set to an activated state;

[0181] When the Trigger of the third capability information is set to the immediate reporting state and / or the Trigger determined by the first R-CHF entity is set to the immediate reporting state, the Trigger of the fourth capability information is set to the immediate reporting state;

[0182] The threshold value of the Trigger in the fourth capability information is the smaller one of the threshold value of the Trigger in the third capability information and the threshold value of the Trigger determined by the first R-CHF entity.

[0183] In an example, the parameter value here can be traffic, statistical duration, number of events, etc.

[0184] For example, the Trigger setting of the third capability information indicates that the user terminal reports when the traffic usage exceeds 500M, and the Trigger setting determined by the first R-CHF entity indicates that the user terminal reports when the traffic usage exceeds 200M. Then the Trigger setting of the fourth capability information indicates that the user terminal reports when the traffic usage exceeds 200M.

[0185] Capability negotiation between the CTF entity, the first R-CHF entity and the main CHF entity is helpful to solve the problem of billing errors caused by capability differences.

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

[0187] The first R-CHF entity performs charging processing according to the first charging request.

[0188] In a possible implementation, for a scenario in which a first charging resource is not established between the CTF entity and the first R-CHF entity, and a second charging resource is not established between the first R-CHF entity and the main CHF entity (scenario one), the CTF entity needs to establish a first charging resource with the first R-CHF entity. At this time, the first charging request is a first charging resource creation request for requesting to create a first charging resource. The first R-CHF entity performs charging processing according to the first charging request, including:

[0189] When the first billing request is used to request session-based convergent billing, the first R-CHF entity generates billing resources corresponding to the first billing request, opens the first R-CHF call record in the first billing resource, and writes the billing information in the first billing request into the first R-CHF call record.

[0190] When the first billing request is used to request a one-time event billing, the first R-CHF entity generates billing resources corresponding to the first billing request, and generates a first R-CHF call record based on the billing resources corresponding to the first billing request and the first billing, and the first R-CHF call record includes the billing information in the first billing request.

[0191] The first R-CHF entity needs to establish a second billing resource with the main CHF entity, and the second billing request is a billing resource creation request; the second billing response message includes but is not limited to the identifier of the second billing resource generated by the main CHF entity for the first R-CHF entity, the billing processing result and the third capability information. When the first R-CHF entity receives the second billing response message sent by the main CHF entity, it indicates that the establishment of the second billing resource between the first R-CHF entity and the main CHF entity is completed.

[0192] For the first charging request, the first charging response message includes but is not limited to the identifier of the first charging resource generated by the first R-CHF entity for the CTF entity, the charging processing result, and the fourth capability information. When the CTF entity receives the first charging response message, it indicates that the establishment of the charging resources between the first R-CHF entity and the CTF entity is completed.

[0193] In another possible implementation, for a scenario where billing resources have been established between the CTF entity and the main CHF entity (scenario 2), if the location of the user equipment changes, or the service changes, or the CTF entity providing services to the user equipment changes, resulting in the main CHF entity being unable to provide billing, it is necessary to introduce a first R-CHF entity as a relay. At this time, the first billing request is a billing resource update request, and the first billing request carries an identifier of a second billing resource generated by the main CHF entity. The first R-CHF entity performs billing processing according to the first billing request, including:

[0194] The first R-CHF entity obtains the second billing resource from the CTF entity according to the identifier of the second billing resource, opens the first R-CHF bill in the second billing resource, and writes the billing information in the first billing request into the first R-CHF bill, thereby completing the update of the billing resource. The first R-CHF entity generates a second billing request according to the identifier of the second billing resource, and the second billing request is an operation request for the second billing resource.

[0195] In one example, the second billing request is a billing resource update request or a billing resource release request, and the second billing request carries an identifier of a second billing resource generated by the main CHF entity, so that when the main CHF entity receives the second billing request, it performs billing processing according to the second billing resource to complete the update of the billing resource or releases the relevant information of the second billing resource when the main CHF entity completes the billing processing.

[0196] Optionally, the second charging request also carries a notification receiving address of the first R-CHF entity, where the notification receiving address is used to update the notification address corresponding to the second charging resource on the primary CHF entity. The notification address is used by the primary CHF entity to subsequently send a notification message to the first R-CHF entity.

[0197] In another possible implementation, the second charging request is a charging resource update request, and the second charging request carries adjustment indication information, where the adjustment indication information is used to indicate that the first R-CHF entity has adjusted the trigger setting sent by the main CHF entity.

[0198] In another possible implementation, the method of this embodiment further includes:

[0199] The first R-CHF entity determines the address of the main CHF entity in two specific ways:

[0200] Method 1: The first charging request carries the address of the main CHF entity, and the first R-CHF entity directly obtains the address of the main CHF entity from the first charging request.

[0201] Mode 2: The first charging request carries a user identifier, and the first R-CHF entity queries information in a network resource function (NRF) entity or charging configuration information of a CTF entity according to the user identifier to determine the address of the main CHF entity.

[0202] It should be understood that the address of the main CHF entity here refers to a uniform resource identifier (URI) that provides a corresponding service in the main CHF entity.

[0203] In a possible implementation, when charging resources have been established between the CTF entity and the second R-CHF entity, and charging resources have been established between the second R-CHF entity and the main CHF entity, if the location of the user equipment changes, or the service changes, or the CTF entity providing services for the user equipment changes, resulting in the second R-CHF entity being unable to provide relay for the CTF entity and the main CHF entity, the CTF entity determines to switch the R-CHF entity, that is, to switch from the second R-CHF entity to the first R-CHF entity. In this case, the method of this embodiment also includes:

[0204] The first R-CHF entity determines the second R-CHF entity, and obtains relevant information of the first charging resource from the second R-CHF entity; the first charging resource is the charging resource generated by the second R-CHF entity for the CTF entity.

[0205] The relevant information of the above-mentioned charging resource includes but is not limited to the charging resource identifier and context information of the charging resource, such as user information, quota information allocated by the primary CHF, etc.

[0206] By migrating the relevant information of the first charging resource cached in the second R-CHF entity to the first R-CHF entity, the switching from the second R-CHF entity to the first R-CHF entity is achieved.

[0207] In a possible implementation, the first charging request carries switching information of the second R-CHF entity switching to the first R-CHF entity, and the first R-CHF entity obtains relevant information of the first charging resource from the second R-CHF entity, including:

[0208] The first R-CHF entity obtains relevant information of the first charging resource from the second R-CHF entity according to the switching information,

[0209] The method of this embodiment also includes:

[0210] The first R-CHF entity generates a second charging request according to the acquired relevant information of the first charging resource.

[0211] In one example, the switching information of the second R-CHF entity switching to the first R-CHF entity includes but is not limited to a switching indication or an identifier or address of the second R-CHF entity, and the switching indication is used to instruct the second R-CHF entity to switch to the first R-CHF entity. At the same time, the first R-CHF entity can also determine the address of the second R-CHF entity based on the switching information, and the first R-CHF entity obtains relevant information of the first billing resource from the second R-CHF entity based on the address of the second R-CHF entity.

[0212] In a possible implementation, when charging resources have been established between the CTF entity and the first R-CHF entity, and charging resources have been established between the first R-CHF entity and the main CHF entity, if the location of the user equipment changes, or the service changes, or the CTF entity providing services to the user equipment changes, resulting in the main CHF entity being able to directly provide charging without the first R-CHF entity acting as a relay, the CTF entity determines to remove the first R-CHF entity.

[0213] In view of the above situation, the method of this embodiment further includes:

[0214] The first R-CHF entity receives a remove R-CHF request sent by the CTF entity, where the remove R-CHF request includes a remove indication, where the remove indication is used for the first R-CHF to return relevant information of the second billing resource generated by the main CHF entity; the first R-CHF entity sends a remove response message to the CTF entity in response to the remove R-CHF request, where the remove response message includes relevant information of the second billing resource generated by the main CHF entity.

[0215] The relevant information of the second billing resource includes but is not limited to the second billing resource identifier and the context information of the second billing resource.

[0216] The CTF entity executes the next charging application according to the relevant information of the second charging resource, that is, the CTF entity sends an update or release request of the charging resource to the main CHF according to the relevant information of the second charging resource.

[0217] Further, after the CTF entity interacts successfully with the primary CHF, the CTF entity sends a first charging resource release request to the first R-CHF entity, requesting the first R-CHF entity to release the first charging resource.

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

[0219] When the first R-CHF entity receives the remove R-CHF request sent by the CTF entity, it directly releases the first charging resource when returning the relevant information of the second charging resource to the CTF entity.

[0220] When the first R-CHF entity is not needed to provide relay for the CTF entity and the main CHF entity, the storage resources of the first R-CHF entity are saved by deleting the relevant information of the charging information cached in the first R-CHF entity.

[0221] It can be seen that in the scheme of the embodiment, when the main CHF entity cannot provide billing, the R-CHF entity is dynamically introduced between the CTF entity and the main CHF entity, which can ensure that billing is carried out normally when the main CHF entity cannot provide billing services, and at the same time simplifies the implementation of the operator network, and does not affect the user's use of services and the operator's billing of users, thereby improving the user experience. In order to avoid the inability to interact normally between the CTF entity and the R-CHF entity, and between the R-CHF entity and the main CHF entity, capability negotiation is performed between the CTF entity and the R-CHF entity, and between the R-CHF entity and the main CHF entity. For the scenario where billing resources have been established between the CTF entity and the R-CHF entity and billing resources have been established between the R-CHF entity and the main CHF entity, when the main CHF entity can charge, the CTF entity dynamically removes the R-CHF entity, which simplifies the implementation of the operator network, does not affect the user's use of services and the operator's billing of users, and improves the user experience. For the scenario where billing resources have been established between the CTF entity and the second R-CHF entity and billing resources have been established between the second R-CHF entity and the main CHF entity, if the second R-CHF entity cannot provide relay services between the CTF entity and the main CHF entity, the normal billing is guaranteed by switching the second R-CHF entity serving as a relay to the first R-CHF entity, thereby simplifying the implementation of the operator's network, and having no impact on the user's use of services and the operator's billing of users, thereby improving the user experience.

[0222] See also Figure 4 , Figure 4 A flowchart of another billing method provided in an embodiment of the present application. Figure 4 The method shown is applied to Figure 2 The CTF entity 201 in Figure 4 As shown, the method includes:

[0223] S401. The CTF entity sends a charging request to the first R-CHF entity.

[0224] In a specific implementation, when the charging request is a request to remove the R-CHF on the premise that the charging resources have been established on the first R-CHF entity and the main CHF entity, the request to remove the R-CHF includes a removal instruction, and the removal instruction is used to instruct the first R-CHF to return the relevant information of the second charging resource generated by the main CHF entity. The main CHF entity provides online quota management and billing call record generation.

[0225] Specifically, under the premise that charging resources have been established between the CTF entity and the first R-CHF entity, and charging resources have been established between the first R-CHF entity and the main CHF entity, due to a change in the location of the user equipment, or a change in the service, or a change in the CTF entity providing services for the user equipment, the main CHF entity can directly provide charging without the first R-CHF entity as a relay, and the CTF entity determines to remove the first R-CHF entity. At this time, the CTF entity sends a remove R-CHF request to the first R-CHF entity.

[0226] S402: The CTF entity receives a removal response message sent by the first R-CHF entity, where the removal response message includes relevant information of the second charging resource generated by the primary CHF entity.

[0227] In an example, the relevant information of the second charging resource includes, but is not limited to, the second charging resource identifier and the address of the main CHF entity.

[0228] It should be noted that the second charging resource is a charging resource generated by the main CHF entity for the first R-CHF entity.

[0229] S403: The CTF entity sends a third charging request to the primary CHF according to the second charging resource identifier, where the third charging request is an operation request for the second charging resource.

[0230] Optionally, the third billing request is a billing resource update request or a billing resource release request.

[0231] In a possible implementation, before or after the CTF entity sends the third charging request to the first R-CHF entity, the method of this embodiment further includes:

[0232] The CTF entity sends a release billing resource request to the first R-CHF entity, where the release billing resource request is used to request the release of relevant information of the billing resources created by the first R-CHF entity; the CTF entity sends a release billing resource response message to the first R-CHF entity, where the response message is used to indicate that the first R-CHF entity has released relevant information of the billing resources created by the first R-CHF entity.

[0233] By instructing the first R-CHF entity to release the relevant information of the charging resources, the storage resources of the first R-CHF can be saved.

[0234] In another possible implementation, when the charging request is an insert R-CHF request under the premise that charging resources have been established on the CTF entity and the primary CHF entity, the insert R-CHF request includes relevant information of the second charging resource generated by the primary CHF entity;

[0235] The CTF entity receives a charging response message sent by the first R-CHF entity, and the charging response message includes the result of the first R-CHF sending the third charging request to the main CHF according to the relevant information of the second charging resource. The result here includes the success or failure of the charging process for the third charging request.

[0236] It can be seen that in the solution of this embodiment, for the scenario where billing resources have been established between the CTF entity and the R-CHF entity and billing resources have been established between the R-CHF entity and the main CHF entity, when the main CHF entity is capable of billing, the CTF entity dynamically removes the R-CHF entity, which simplifies the implementation of the operator's network and does not affect the user's use of services and the operator's billing of users, thereby improving the user experience.

[0237] See also Figure 5 , Figure 5 The following is an interactive flow chart of a billing method provided in an embodiment of the present application. Figure 5 As shown, the method includes:

[0238] S501. The CTF entity determines to perform billing relay.

[0239] In one example, a user uses a new service through a user device, but the main CHF entity cannot provide billing for the new service, and billing relay is required at this time.

[0240] In another example, the user's location changes, causing the user device to be located in an area where the primary CHF cannot provide billing. For example, the user device moves from an area covered by one operator's network to an area covered by another operator's network, or the same network operator covers multiple areas, and the user device moves from one area to another, resulting in the primary CHF being unable to provide billing. In this case, billing relay is required.

[0241] It should be noted that Figure 5 The charging process shown is for the scenario where convergent charging resources are not established. For the above situation, if convergent charging resources are not established, then convergent charging resources are established.

[0242] S502: The CTF entity determines the address of the first R-CHF entity and generates a first charging request.

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

[0244] It should be noted that there is no clear order for the CTF entity to perform the operation of "determining the address of the first R-CHF entity" and the operation of "generating the first charging request". Optionally, the CTF entity first performs the operation of "determining the address of the first R-CHF entity" and then performs the operation of "generating the first charging request", or the CTF entity first performs the operation of "generating the first charging request" and then performs the operation of "determining the address of the first R-CHF entity", or both are performed simultaneously.

[0245] Optionally, the first charging request includes first capability information, and the first capability information is capability information provided by the CTF entity and can be used for the interaction between the first R-CHF entity and the CTF entity. The first capability information includes at least one of a first payload size of a charging message for a first charging resource supported by the CTF entity, a first idle duration for charging information collection of the CTF entity for the first charging resource, or a first charging characteristic. Of course, the first capability information can also include other information, which is not limited here.

[0246] In one example, the charging characteristic is a characteristic defined in 6.1.8 of 3GPP TS 32.291, and whether the management quota suspension capability is supported.

[0247] The charging message of the first charging resource is a message exchanged between the first R-CHF entity and the CTF entity, such as a first charging request message and a first charging response message.

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

[0249] In one example, the CTF entity sends a first charging request to the first R-CHF entity according to the address of the first R-CHF entity.

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

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

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

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

[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, etc. are stored in the NRF entity or the billing configuration information of the CTF entity.

[0255] S504: The first R-CHF entity performs charging processing and generates a second charging request.

[0256] The second charging request is used to request to establish a second charging resource for charging interaction between the first R-CHF and the main CHF.

[0257] Specifically, when the first billing request is used to request the execution of convergent billing based on the first billing resource, the first R-CHF entity generates the first billing resource corresponding to the first billing request, and opens the first R-CHF bill in the first billing resource so that the billing center can write the bill; when the first billing request is used to request the execution of one-time event billing, the first R-CHF generates the first billing resource corresponding to the first billing request, and generates the first R-CHF bill. It should be understood that opening the first R-CHF bill refers to creating an R-CHF bill and waiting for the billing information to be written; generating the first R-CHF bill includes creating the first R-CHF bill, writing the billing information into the first R-CHF bill, and then closing the first R-CHF bill.

[0258] It should be understood that the first R-CHR bill here includes a CDR bill. The first billing resources include but are not limited to user identification, user equipment identification, location of user equipment, services subscribed by the user, traffic packages, used traffic, and the like.

[0259] Optionally, the second charging request includes second capability information, where the second capability information represents a capability for the primary CHF entity to interact with the first R-CHF entity. The second capability information is obtained by the first R-CHF entity according to the first capability information.

[0260] The second capability information includes at least one of a second payload size of a charging message for a second charging resource supported by the first R-CHF entity, a second idle duration of charging information collection for the first R-CHF entity for the second charging resource, or a second charging characteristic. Of course, the second charging request can also include other information, which is not limited here.

[0261] The charging message used for the second charging resource is information exchanged between the first R-CHF entity and the main CHF entity, such as a second charging request and a second charging response message.

[0262] In a specific implementation manner, the second capability information is determined by the first R-CHF entity according to the first capability information, including:

[0263] When the first capability information includes the first payload size, the second capability information also includes the second payload size, and the second payload size is the smaller of the first payload size and the payload size of the charging message for the second charging resource supported by the first R-CHF entity; when the first capability information does not include the first payload size, the second capability information may include the second payload size or may not include the second payload size, in which case, when the second capability information includes the second payload size, the second payload size is the payload size of the charging message for the second charging resource supported by the first R-CHF entity;

[0264] When the first capability information includes the first idle duration, the second capability information also includes the second idle duration, and the second idle duration is the smaller of the first idle duration and the idle duration for collecting the billing information of the first R-CHF entity used for the second billing resource; when the first capability information does not include the first idle duration, the second capability information may include the second idle duration or may not include the second idle duration, and when the second capability information includes the second idle duration, the second idle duration is the idle duration for collecting the billing information of the first R-CHF entity used for the second billing resource;

[0265] When the first capability information includes the first charging characteristic, the second capability information also includes the second charging information, and the second charging characteristic is the intersection of the first charging characteristic and the charging characteristic supported by the first R-CHF entity; when the first capability information does not include the first charging characteristic, the second capability information may include the second charging characteristic or may not include the second charging characteristic, and when the second capability information includes the second charging characteristic, the second charging characteristic is the charging characteristic supported by the first R-CHF entity.

[0266] It should be pointed out that the above-mentioned capability information determination process is for the scenario where the first billing request is used to request session-based converged billing. For the scenario where the first billing request is used to request one-time event billing, the second billing request carries the billing information in the first billing request sent by CTF, but does not carry the first capability information.

[0267] When the first charging request is used to request to perform a one-time event charging, the second charging request is used to request to perform a one-time event charging between the first R-CHF entity and the main CHF entity, wherein the second charging request includes the charging information in the first charging request.

[0268] Optionally, before the first R-CHF entity performs the billing process, 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 performs the billing process; when it is determined that the user equipment is not authorized to use the current service, the first R-CHF entity does not perform the billing process.

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

[0270] The first R-CHF entity queries the NRF entity according to the user equipment identifier or determines the address of the main CHF entity from the local configuration, and then sends a second charging request to the main CHF entity according to the address of the main CHF entity.

[0271] S506: The main CHF entity performs charging processing and generates a second charging response message.

[0272] Specifically, when the second charging request is used to request to perform convergent charging based on the second charging resource, the primary CHF entity generates the second charging resource, performs charging processing according to the second charging resource, including online charging processing or offline charging processing, to obtain a charging processing result, including an online charging processing result or an offline charging processing result. The primary CHF opens the primary CHF call record to write the charging information, and performs account balance management, such as granting a quota.

[0273] Optionally, when the first R-CHF entity and the main CHF entity belong to different operators, the main CHF entity determines whether to authorize the user equipment to use the current service based on the user's contract information; if the user equipment is authorized to use the current service, the main CHF entity performs billing processing; when it is determined that the user equipment is not authorized to use the current service, the main CHF entity does not perform billing processing.

[0274] When the second charging request is used to request execution of one-time event charging, the primary CHF entity generates charging resources corresponding to the second charging request, generates a primary CHF call record, or performs a balance deduction.

[0275] It should be understood that opening the main CHF bill refers to creating a main CHF bill, and generating the main CHF bill includes creating the main CHF bill, writing the billing information into the main CHF bill, and then closing the main CHF bill.

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

[0277] The second charging response message includes a charging processing result, which includes an online charging processing result and / or an offline charging processing result.

[0278] When the second charging request is a charging resource creation request, the second charging response message further includes a second charging resource identifier. Optionally, the second charging response message further includes third capability information. The third capability information is capability information determined by the primary CHF entity according to the second charging request for interaction between the primary CHF entity and the first R-CHF entity.

[0279] Among them, the third capability information includes at least one of a third payload size for billing messages in the second billing resource, a third idle time for billing information collection of the first R-CHF entity for the second billing resource, a third billing characteristic, or a second billing resource trigger condition setting.

[0280] In a specific example, when the second charging request does not include the second capability information, the third capability information is capability information provided by the main CHF entity for the main CHF entity to interact with the first R-CHF entity; when the second charging request includes the second capability information, the third capability information is determined by the main CHF entity based on the second capability information.

[0281] In a specific implementation manner, the third capability information is determined by the master CHF entity according to the second capability information, including:

[0282] When the second capability information includes the second payload size, the third capability information also includes the third payload size, and the third payload size is the smaller of the second payload size and the payload size of the charging message for the second charging resource supported by the primary CHF entity; when the second capability information does not include the second payload size, the third capability information may include the third payload size or may not include the third payload size. At this time, when the third capability information includes the third payload size, the third payload size is the payload size of the charging message for the second charging resource supported by the primary CHF entity;

[0283] When the second capability information includes the second idle duration, the third capability information also includes the third idle duration, and the third idle duration is the smaller of the second idle duration and the idle duration for the second billing resource supported by the primary CHF entity; when the second capability information does not include the second idle duration, the third capability information may include the second idle duration or may not include the second idle duration. At this time, when the third capability information includes the third idle duration, the third idle duration is the idle duration for the second billing resource supported by the primary CHF entity;

[0284] When the second capability information includes the second billing characteristic, the third capability information also includes the third billing information, and the third billing characteristic is the intersection of the second billing characteristic and the billing characteristic supported by the primary CHF entity; when the second capability information does not include the second billing characteristic, the third capability information may include the third billing characteristic or may not include the third billing characteristic. At this time, when the third capability information includes the third billing characteristic, the third billing characteristic is the billing characteristic supported by the primary CHF entity.

[0285] The third capability information may also include a second billing resource trigger condition setting, and the second billing resource trigger condition setting includes: trigger status information (such as: trigger list, activation / deactivation status of the trigger in the list, immediate reporting / delayed reporting status of the trigger in the list), trigger threshold value (some triggers have thresholds, such as: threshold value of statistical duration or traffic or number of events).

[0286] S508: The first R-CHF entity generates a first charging response message according to the second charging response message.

[0287] Specifically, the first charging response message includes a charging processing result, wherein the charging processing result includes an online charging processing result and / or an offline charging processing result. When the first charging request is used to request a charging resource creation request, the first charging response message also includes a first charging resource identifier.

[0288] Optionally, the first billing response message also includes fourth capability information, which includes a fourth payload size of the billing message for the first billing resource, a fourth idle time for billing information collection of the CTF entity for the first billing resource, a fourth billing characteristic, or at least one of the first billing resource trigger condition settings.

[0289] In a case where the first charging request is used to request to perform convergent charging based on the first charging session, and the second charging request does not include the second capability information, when the third capability information includes the third payload size, the fourth capability information also includes the fourth payload size, and the fourth payload size is the smaller of the third payload size and the payload size of the charging message for the first charging resource supported by the first R-CHF entity;

[0290] When the third capability information includes the third idle duration, the fourth capability information also includes the fourth idle duration, and the fourth idle duration is the smaller of the third idle duration and the idle duration for charging information collection of the first R-CHF entity for the second charging resource;

[0291] When the third capability information includes the third charging characteristic, the fourth capability information also includes fourth charging information, and the fourth charging characteristic is an intersection of the third charging characteristic and the charging characteristic supported by the first R-CHF entity;

[0292] In the case where the first charging request is used to request the execution of convergent charging based on the first charging session, and the second charging request includes the second capability information, when the third capability information includes the third payload size, the fourth capability information also includes the fourth payload size, and if the second capability information includes the second payload size, the fourth payload size is the third payload size. It should be pointed out here that since the second payload size of the second capability information has been considered when determining the third payload size of the third capability information, the fourth payload size of the fourth capability information here is implicitly the smaller of the third payload size included in the third capability information and the payload size of the charging message for the first charging resource supported by the first R-CHF entity. If the second capability information does not include the second payload size, the fourth payload size is the smaller of the third payload size and the payload size of the charging message for the first charging resource supported by the first R-CHF entity;

[0293] When the third capability information includes the third idle duration, the fourth capability information also includes the fourth idle duration. If the second capability information includes the second idle duration, the fourth idle duration is the third idle duration. It should be noted that since the second idle duration has been considered when determining the third idle duration, the fourth idle duration here is implicitly the smaller of the third idle duration and the idle duration for billing information collection of the first R-CHF entity for the second billing resource. If the second capability information does not include the second idle duration, the fourth idle duration is the smaller of the third idle duration and the idle duration for billing information collection of the first R-CHF entity for the second billing resource;

[0294] When the third capability information includes the third billing characteristic, the fourth capability information also includes the fourth billing characteristic, and if the second capability information includes the second billing characteristic, the fourth billing characteristic is the third billing characteristic. It should be noted that, since the second billing characteristic has been considered when determining the third billing characteristic, the fourth billing characteristic here is implicitly the intersection of the third billing characteristic and the billing characteristic supported by the first R-CHF entity. If the second capability information does not include the second billing characteristic, the fourth billing characteristic is the intersection of the third billing characteristic and the billing characteristic supported by the first R-CHF entity.

[0295] The first charging session is a charging session between the CTF entity and the first R-CHF entity.

[0296] In a possible implementation, the third capability information further includes a second charging resource trigger condition setting, and the fourth capability information includes a first charging resource trigger condition setting. The trigger state information in the first charging resource trigger condition setting is a union of the trigger state information in the second charging resource trigger condition setting and the trigger state information determined by the first R-CHF entity, and the trigger threshold limit in the first charging resource trigger condition setting is the smaller of the trigger threshold limit in the second charging resource trigger condition setting and the trigger threshold limit determined by the first R-CHF entity.

[0297] The threshold value of the trigger condition in the Trigger setting of the fourth capability information is the smaller of the threshold value of the trigger condition in the Trigger setting of the third capability information and the threshold value of the trigger condition determined by the first R-CHF entity.

[0298] The Trigger setting of the third capability information is used to indicate the condition and method under which the main CHF entity instructs the CTF entity to report charging information, and the Trigger setting of the fourth capability information is used to indicate the condition and method determined by the first R-CHF entity to instruct the CTF entity to report charging information.

[0299] The trigger setting includes the state information of the trigger setting and the threshold value of the trigger setting; the state information of the trigger setting includes: the activation state of the trigger, the immediate reporting / delayed reporting state of the activated trigger, and the threshold value of the activated trigger, such as the threshold value of the statistical duration, traffic, or number of events.

[0300] In one example, the trigger status information in the first charging resource trigger condition setting (i.e., the status information of the Trigger setting of the fourth capability information) is the union of the trigger status information in the second charging resource trigger condition setting (i.e., the status information of the Trigger setting of the third capability information) and the status information of the Trigger setting determined by the first R-CHF entity, including:

[0301] When the Trigger of the third capability information is set to an activated state and / or the Trigger determined by the first R-CHF entity is set to an activated state, the Trigger of the fourth capability information is set to an activated state;

[0302] When the Trigger of the third capability information is set to the immediate reporting state and / or the Trigger determined by the first R-CHF entity is set to the immediate reporting state, the Trigger of the fourth capability information is set to the immediate reporting state;

[0303] In an example, the parameter value here can be traffic, statistical duration, number of events, etc.

[0304] For example, the Trigger setting of the third capability information indicates that the user terminal reports when the traffic usage exceeds 500M, and the Trigger setting supported by the first R-CHF entity indicates that the user terminal reports when the traffic usage exceeds 200M. Then the Trigger setting of the fourth capability information indicates that the user terminal reports when the traffic usage exceeds 200M.

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

[0306] The first billing response message is used to respond to the first billing request.

[0307] S510. The CTF entity processes a service according to the first charging response message.

[0308] Specifically, processing the service includes continuing to collect service billing information, such as counting service usage, or executing quotas. Optionally, the first charging response message includes fourth capability information, and the CTF entity performs settings according to the fourth capability information included in the first charging response message.

[0309] S511. The CTF entity, the first R-CHF entity and the main CHF entity perform subsequent charging interaction.

[0310] It should be understood that the subsequent interaction process can refer to the relevant description of S502-S510, which will not be described here. The difference between the subsequent interaction process and S502-S510 is:

[0311] 1. In S502, the CTF entity does not need to determine the address of the R-CHF.

[0312] 2. In S504, the first R-CHF entity does not need to generate a first billing resource, does not need to create a new call list, writes billing data in the opened call list, and the first R-CHF entity does not need to determine the address of the main CHF entity. If the Trigger setting in the third capability information is inconsistent with the Trigger setting sent by the first R-CHF to the CTF entity, when the first R-CHF receives the Trigger setting sent by the CTF entity, it sends the Trigger setting to the main CHF entity, and adds adjustment indication information to the message reporting the Trigger setting of the CTF entity to the main CHF entity (such as the billing request subsequently sent by the first R-CHF entity to the main CHF entity), and the adjustment indication information is used to indicate that the first R-CHF entity has adjusted the Trigger setting sent by the main CHF entity.

[0313] 3. In S506, the main CHF entity does not need to generate billing resources or create a new call bill. The billing data, including quota deduction, is written into the call bill. If there is a quota, the quota is granted.

[0314] 4. If the main CHF entity needs to send a notification message, the main CHF entity sends the notification message to the first R-CHF entity, and the first R-CHF entity forwards the notification message to the CTF entity.

[0315] It can be seen that in this embodiment, when the main CHF entity cannot provide billing, the R-CHF entity is dynamically introduced between the CTF entity and the main CHF entity, which can ensure that billing is carried out normally when the main CHF entity cannot provide billing services, and at the same time simplify the implementation of the operator network, and does not affect the user's use of services and the operator's billing of users, thereby improving the user experience. In addition, in order to avoid the inability to interact normally between the CTF entity and the R-CHF entity, and between the R-CHF entity and the main CHF entity, capability negotiation is performed between the CTF entity and the R-CHF entity, and between the R-CHF entity and the main CHF entity.

[0316] See also Figure 6 , Figure 6 An interactive flowchart of another billing method provided in an embodiment of the present application. Figure 6 This is for scenarios where billing resources have been established on the CTF entity and the main CHF entity. Figure 6 As shown, the method includes:

[0317] S601: The CTF entity determines to insert a first R-CHF entity, obtains the first R-CHF entity, and generates a first charging request.

[0318] Specifically, in one example, a user uses a new service through a user device, but the main CHF entity cannot provide billing for the new service, and billing relay is required. At this time, the CTF entity determines that the first R-CHF entity needs to be inserted.

[0319] In another example, the user's location changes, causing the user equipment to be located in an area where the primary CHF cannot provide billing, such as the user equipment moves from an area covered by an operator's network to an area covered by another operator's network, or the same network operator covers multiple areas, and the user equipment moves from one area to another, resulting in the primary CHF being unable to provide billing. At this time, the CTF entity determines that the first R-CHF entity needs to be inserted. Therefore, the above-mentioned first billing request can be regarded as an insertion R-CHF request.

[0320] In another example, the current CTF cannot provide billing for the user equipment, and the CTF entity providing billing for the user equipment switches to a new CTF entity, and it is also determined that an R-CHF entity needs to be inserted. The operations performed by the CTF entity in the subsequent steps are performed by the new CTF entity.

[0321] When it is determined that the first R-CHF entity needs to be inserted, the CTF entity determines the address of the first R-CHF entity. The specific determination process can refer to the relevant description of S503 and will not be described here.

[0322] The first billing request is a billing resource update request or a billing resource creation request. The first billing request also includes an identifier of a second billing resource generated by the main CHF entity; the first billing request also includes billing information, wherein the billing information includes but is not limited to an identifier of the user device, a location of the user device, services subscribed by the user, traffic packages, and the amount of traffic already used. Optionally, the first billing request also includes first capability information. For a specific description of the first capability information, please refer to the relevant description in S502, which will not be described here.

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

[0324] S603: The first R-CHF entity performs charging processing and generates a second charging request.

[0325] Specifically, after receiving the first billing request, the first R-CHF entity caches the second billing resource indicated by the identifier of the second billing resource to facilitate the use of the second billing resource in subsequent billing interactions. For example, the first R-CHF entity opens the first R-CHF call sheet and writes billing data to the first R-CHF call sheet according to the billing information. The first R-CHF entity generates a second billing request according to the identifier of the second billing resource, and the second billing request is an operation request for the second billing resource. In other words, the second billing request is an update request for the second billing resource or a release request.

[0326] The second charging request includes an identifier of the charging resource of the CTF entity. Optionally, the second charging request also includes second capability information. The second capability information is obtained by the first R-CHF entity according to the first capability information. For the specific process, please refer to the relevant description of S504, which will not be described here.

[0327] Optionally, the second charging request also carries a notification receiving address of the first R-CHF entity, where the notification receiving address is used to update the notification address corresponding to the second charging resource on the primary CHF entity. The notification address is used by the primary CHF entity to subsequently send a notification message to the first R-CHF entity.

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

[0329] The first R-CHF entity queries the NRF entity according to the user equipment identifier or determines the address of the main CHF entity from the local configuration, and then sends a second charging request to the main CHF entity according to the address of the main CHF entity.

[0330] S605: The primary CHF entity performs charging processing and generates a second charging response message.

[0331] Specifically, the primary CHF entity obtains the billing resources of the CTF entity according to the identifier of the billing resources of the CTF entity, performs billing processing according to the billing resources of the CTF entity, including online billing processing or offline billing processing, to obtain a billing processing result, including an online billing processing result or an offline billing processing result. The primary CHF opens the primary CHF call list to write billing data and perform account balance management, such as granting quotas.

[0332] Optionally, when the first R-CHF entity and the main CHF entity belong to different operators, the main CHF entity determines whether to authorize the user equipment to use the current service based on the user's contract information; if the user equipment is authorized to use the current service, the main CHF entity performs billing processing; when it is determined that the user equipment is not authorized to use the current service, the main CHF entity does not perform billing processing.

[0333] The second charging response message includes the charging processing result. Optionally, the second charging response message includes the third capability information. The determination process of the third capability information can refer to the relevant description of S507, which will not be described here.

[0334] Among them, the third capability information includes at least one of a third payload size for billing messages in the second billing resource, a third idle time for billing information collection of the first R-CHF entity for the second billing resource, a third billing characteristic, or a second billing resource trigger condition setting.

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

[0336] S607: The first R-CHF entity generates a first charging response message according to the second charging response message.

[0337] Optionally, the first billing response message includes fourth capability information. The fourth capability information includes at least one of a fourth payload size of a billing message for the first billing resource, a fourth idle duration for billing information collection of a CTF entity for the first billing resource, a fourth billing characteristic, or a first billing resource trigger condition setting. It should be noted here that the process of determining the fourth capability information can be referred to the relevant description of S508 and will not be described here.

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

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

[0340] Specifically, processing services includes continuing to collect service billing information, such as counting service usage, or executing quotas.

[0341] Optionally, the first charging response message includes the fourth capability information, and the CTF entity includes the fourth capability information according to the first charging response message.

[0342] S610: The CTF entity, the first R-CHF entity and the main CHF entity perform subsequent charging interaction.

[0343] Specifically, if the first charging request is used to request to update the charging resources, the CTF entity obtains the updated charging resources from the first charging response message and caches them; the CTF entity, the first R-CHF entity and the main CHF entity perform subsequent charging interactions. The subsequent interaction process can refer to the relevant description of S502-S510, which will not be described here. The difference between the subsequent interaction process and S502-S510 is:

[0344] 1. In S504, if the Trigger setting in the third capability information is inconsistent with the Trigger setting sent by the first R-CHF to the CTF entity, when the first R-CHF receives the Trigger setting sent by the CTF entity, it sends the Trigger setting to the main CHF entity, and adds adjustment indication information to the message reporting the Trigger setting of the CTF entity to the main CHF entity (such as the billing request subsequently sent by the first R-CHF entity to the main CHF entity), where the adjustment indication information is used to indicate that the first R-CHF entity has adjusted the Trigger setting sent by the main CHF entity.

[0345] 2. If the main CHF entity needs to send a notification message, the main CHF entity sends the notification message to the first R-CHF entity, and the first R-CHF entity forwards the notification message to the CTF entity.

[0346] If the first charging request is a charging resource release request, the CTF entity, the first R-CHF entity and the main CHF entity perform a charging resource release operation.

[0347] It can be seen that in this embodiment, when the main CHF entity cannot provide billing, the R-CHF entity is dynamically introduced between the CTF entity and the main CHF entity, which can ensure that billing is carried out normally when the main CHF entity cannot provide billing services, and at the same time simplify the implementation of the operator network, and does not affect the user's use of services and the operator's billing of users, thereby improving the user experience. In addition, in order to avoid the inability to interact normally between the CTF entity and the R-CHF entity, and between the R-CHF entity and the main CHF entity, capability negotiation is performed between the CTF entity and the R-CHF entity, and between the R-CHF entity and the main CHF entity.

[0348] See also Figure 7 , Figure 7 A flowchart of another billing method provided in an embodiment of the present application. Figure 7 This is for the scenario where the first charging resource has been established between the CTF entity and the first R-CHF entity, and the second charging resource has been established between the first R-CHF entity and the main CHF entity. Figure 7 As shown, the method includes:

[0349] S701: The CTF entity determines to remove the first R-CHF entity.

[0350] Specifically, when converged billing resources have been established between the CTF entity and the first R-CHF entity and between the first R-CHF entity and the main CHF entity, if the location of the user equipment changes, or the service changes, or the CTF entity providing services to the user equipment changes, resulting in the main CHF entity being able to directly provide billing services without the first R-CHF entity acting as a relay, it is determined to remove the first R-CHF entity.

[0351] S702: The CTF entity sends a remove R-CHF request to the first R-CHF entity.

[0352] The remove R-CHF request is used to request to prepare to remove the first R-CHF entity. The remove R-CHF request includes a remove indication, and the remove indication is used for the first R-CHF to return the relevant information of the second charging resource generated by the main CHF entity.

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

[0354] The removal response message includes the relevant information of the second charging resource generated by the primary CHF, and the relevant information of the second charging resource includes but is not limited to the identifier of the second charging resource and the address of the primary CHF entity.

[0355] Specifically, after receiving the remove R-CHF request, the first R-CHF entity sends the relevant information of the second charging resource to the CTF entity, so that the CTF entity completes subsequent charging interaction with the main CHF entity.

[0356] S704: The CTF entity generates a third charging request, and sends the third charging request to the main CHF entity.

[0357] The third charging request is a charging resource update request or a charging resource release request, which is used to request to update or release the second charging resource generated by the main CHF entity.

[0358] S705: The main CHF entity performs charging processing and generates a third charging response message.

[0359] Specifically, the primary CHF entity performs billing processing according to the billing resources of the primary CHF, including online billing processing or offline billing processing, to obtain a billing processing result, including an online billing processing result or an offline billing processing result. The primary CHF opens the primary CHF call list to write billing data and perform account balance management, such as granting quotas.

[0360] After executing the charging process, the main CHF entity generates a third charging response message, and the third charging response message includes the charging process result.

[0361] Optionally, when the R-CHF entity and the main CHF entity belong to different operators, the main CHF entity determines whether to authorize the user equipment to use the current service based on the user's contract information; if the user equipment is authorized to use the current service, the main CHF entity performs billing processing; when it is determined that the user equipment is not authorized to use the current service, the main CHF entity does not perform billing processing.

[0362] S706: The primary CHF sends a third charging response message to the CTF entity.

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

[0364] The charging resource release request is used to request the first R-CHF entity to release relevant information of the charging resources created by the first R-CHF entity, and the relevant information includes but is not limited to the charging resources created by the first R-CHF entity.

[0365] S708: The first R-CHF entity performs a release operation.

[0366] Specifically, the first R-CHF entity releases the first charging resource created by the first R-CHF entity, and deletes the locally stored related information of the second charging resource created by the main CHF entity. The related information includes but is not limited to the first charging resource identifier created by the main CHF entity and the interaction information between the first R-CHF entity and the main CHF entity.

[0367] S709: The first R-CHF entity sends a release charging resource response message to the CTF entity.

[0368] The charging resource release response message is used to respond to the charging resource release request, and the charging resource release response message is used to indicate that the first R-CHF entity has released the relevant information of the charging resources created by the first R-CHF entity.

[0369] S710: The CTF entity and the main CHF entity perform subsequent charging interaction.

[0370] The subsequent charging interaction may be to update the charging resources or release the charging resources. The specific implementation process may refer to the relevant description of S704-S706, which will not be described here.

[0371] It should be noted here that S707-S709 may be executed before or after S704. The purpose of S707-S709 being executed after S704 is to verify whether the CTF entity and the main CHF entity can perform billing normally after the first R-CHF entity feeds back the billing resource identifier of the main CHF entity and the address of the main CHF entity to the CTF entity, and if billing cannot be performed normally, since the first R-CHF entity has not been removed, the first R-CHF entity can continue to be used as a billing relay, thereby ensuring normal billing.

[0372] It can be seen that in this embodiment, for the scenario where billing resources have been established between the CTF entity and the R-CHF entity and billing resources have been established between the R-CHF entity and the main CHF entity, when the main CHF entity is capable of billing, the CTF entity dynamically removes the R-CHF entity, which simplifies the implementation of the operator's network and does not affect the user's use of services and the operator's billing of users, thereby improving the user experience.

[0373] See also Figure 8 , Figure 8 A flowchart of another billing method provided in an embodiment of the present application. Figure 8 This is for scenarios where converged charging resources have been established between the CTF entity and the second R-CHF entity and between the second R-CHF entity and the main CHF entity. Figure 8 As shown, the method includes:

[0374] S801: The CTF entity determines to switch to a first R-CHF entity and generates a first charging request.

[0375] When the location of the user equipment changes, or the service changes, or the CTF entity providing services to the user equipment changes, the second R-CHF entity may not be able to continue to provide billing services, and the first R-CHF entity needs to be introduced to take over the work of the second R-CHF entity. The CTF entity determines to switch to the first R-CHF entity.

[0376] The first charging request is a first charging resource update request or a first charging resource release request. The first charging request includes switching information of the second R-CHF entity switching to the first R-CHF entity. In one example, the switching information includes switching indication information and an address or identifier of the second R-CHF entity.

[0377] It should be noted that, in this embodiment, if the CTF entity is switched, all operations related to the CTF entity in this embodiment are performed by the switched CTF entity.

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

[0379] Specifically, the CTF entity sends the first charging request to the first R-CHF entity according to the address of the first R-CHF entity.

[0380] It should be noted here that the manner in which the CTF entity determines the address of the first R-CHF entity can be found in the relevant description of S503 and will not be described again here.

[0381] S803: The first R-CHF entity interacts with the second R-CHF entity to transmit charging resources.

[0382] Specifically, the first R-CHF entity interacts with the second R-CHF entity according to the address or identifier of the second R-CHF entity to obtain the relevant information of the first charging resource cached in the second R-CHF entity. The first R-CHF entity obtains the relevant information of the first charging resource from the second R-CHF entity according to the switching information in the first charging request.

[0383] It should be understood that after the first R-CHF entity obtains the relevant information of the first charging resource, the second R-CHF entity deletes the locally stored charging resource and the relevant information of the charging resources of the second R-CHF entity and the main CHF entity.

[0384] When the switching information does not include the address or identifier of the second R-CHF entity, the first R-CHF entity determines the address or identifier of the second R-CHF entity from the NRF entity according to the CTF entity identifier, or according to the location information of the user equipment, or according to the location information of the user equipment and the user identifier.

[0385] S804: The first R-CHF entity performs charging processing and generates a second charging request.

[0386] S805. The first R-CHF entity sends a second charging request to the main CHF entity.

[0387] S806: The primary CHF entity performs charging processing and generates a second charging response message.

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

[0389] S808: The first R-CHF entity generates a first charging response message according to the second charging response message.

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

[0391] S810. The CTF entity processes a service according to the first charging response message.

[0392] S811. The CTF entity, the first R-CHF entity, and the main CHF entity perform subsequent charging interaction.

[0393] It should be noted that the specific process of S804-S811 can refer to the relevant description of S504-S511 and will not be described here.

[0394] It can be seen that in this embodiment, for the scenario where billing resources have been established between the CTF entity and the second R-CHF entity and billing resources have been established between the second R-CHF entity and the main CHF entity, if the second R-CHF entity cannot provide a relay service between the CTF entity and the main CHF entity, by switching the second R-CHF entity serving as a relay to the first R-CHF entity, normal billing is ensured, thereby simplifying the implementation of the operator's network, and having no impact on the user's use of services and the operator's billing of the user, thereby improving the user experience.

[0395] Reference Fig. 9 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 1 R-CHF entity 202 in. Fig. 9 As shown, the first R-CHF entity 202 includes:

[0396] The transceiver unit 901 is configured to receive a first charging request from a charging trigger function CTF entity, where the first charging request creates, updates or releases a first charging resource;

[0397] The transceiver unit 901 is further configured to send a second charging request to the primary CHF entity; the second charging request is used to request to create, update or release a second charging resource; receive a second charging response message sent by the primary CHF entity to respond to the second charging request, the second charging response message including third capability information, the third capability information being capability information determined by the primary CHF entity according to the second charging request for interaction between the primary CHF entity and the first R-CHF entity;

[0398] The generating unit 902 is further configured to generate a first charging response message for responding to the first charging request according to the second charging response message,

[0399] The transceiver unit 901 is further configured to send a first charging response message to the CTF entity, where the first charging response message includes fourth capability information, where the fourth capability information is capability information determined by the first R-CHF according to the third capability information for interaction between the first R-CHF entity and the CTF entity.

[0400] In combination with the third aspect, in a possible implementation, the first charging request also includes first capability information; the first capability information is capability information provided by the CTF entity and can be used for the first R-CHF entity to interact with the CTF entity; the second charging request includes second capability information, the second capability information represents the capability for the main CHF entity to interact with the first R-CHF entity, and the second capability information is determined by the first R-CHF entity based on the first capability information; the third capability information is determined by the main CHF entity based on the second capability information.

[0401] In conjunction with the third aspect, in a possible implementation manner, the first capability information includes at least one of a first payload size of a charging message for a first charging resource supported by the CTF entity, a first idle duration for charging information collection of the CTF entity for the first charging resource, or a first charging characteristic;

[0402] The fourth capability information includes at least one of a fourth payload size of a charging message for the first charging resource, a fourth idle time for charging information collection of a CTF entity for the first charging resource, a fourth charging characteristic, or a first charging resource trigger condition setting;

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

[0404] The third capability information includes at least one of a third payload size for charging messages in the second charging resource, a third idle time for charging information collection of the first R-CHF entity for the second charging resource, a third charging characteristic, or a second charging resource trigger condition setting.

[0405] In conjunction with the third aspect, in a possible implementation manner, the second capability information is determined by the first R-CHF entity according to the first capability information, including:

[0406] When the first capability information includes the first payload size, the second capability information also includes the second payload size, and the second payload size is the smaller of the first payload size and the payload size of the billing message supported by the first R-CHF entity for the first billing resource; when the first capability information includes the first idle duration, the second capability information also includes the second idle duration, and the second idle duration is the smaller of the first idle duration and the idle duration for billing information collection of the first R-CHF entity for the second billing resource; when the first capability information includes the first billing characteristic, the second capability information also includes the second billing characteristic, and the second billing characteristic is the intersection of the first billing characteristic and the billing characteristic supported by the first R-CHF entity.

[0407] The above method can realize capability negotiation between the CTF entity and the first R-CHF entity.

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

[0409] When the third capability information includes the first payload size, the fourth capability information also includes the fourth payload size, and if the second capability information includes the second payload size, the fourth payload size is the third payload size; if the second capability information does not include the second payload size, the fourth payload size is the smaller of the third payload size and the payload size of the charging message for the first charging resource supported by the first R-CHF entity;

[0410] When the third capability information includes the third idle duration, the fourth capability information also includes the fourth idle duration, and if the second capability information includes the third idle duration, the fourth idle duration is the third idle duration; if the second capability information does not include the second idle duration, the fourth idle duration is the smaller of the third idle duration and the idle duration for charging information collection of the first R-CHF entity for the second charging resource;

[0411] If the third capability information includes the third charging characteristic, the fourth capability information also includes the fourth charging characteristic. If the second charging characteristic is included, the fourth charging characteristic is the third charging characteristic. If the second capability information does not include the second charging characteristic, the fourth charging characteristic is the intersection of the third charging characteristic and the charging characteristics supported by the first R-CHF entity.

[0412] In combination with the third aspect, in a possible implementation manner, the third capability information includes a second charging resource trigger condition setting, and the fourth capability information also includes a first charging resource trigger condition setting, and the state information in the first charging resource trigger condition setting is a union of the state information in the second charging resource trigger condition setting and the state information of the trigger condition determined by the first R-CHF entity;

[0413] The threshold value of the trigger condition in the first charging resource trigger condition setting is the smaller one of the threshold value of the trigger condition in the second charging resource trigger condition setting and the threshold value of the trigger condition determined by the first R-CHF entity.

[0414] In conjunction with the third aspect, in a possible implementation manner, the first R-CHF entity 202 further includes:

[0415] The execution unit 903 is configured to execute a billing process according to the first billing request.

[0416] In combination with the third aspect, in a possible implementation manner, the first charging request is used to request creation of a first charging resource, and the first R-CHF entity 202 further includes an execution unit 903, where the execution unit 903 is used to:

[0417] When the first billing request is used to request session-based convergent billing, a first billing resource corresponding to the first billing request is generated; a first R-CHF call record in the first billing resource is opened, and the billing information in the first billing request is written into the first R-CHF call record; when the first billing request is used to request one-time event billing, a first billing resource corresponding to the first billing request is generated, and a first R-CHF call record is generated according to the first billing resource and the billing information of the first billing request, and the first R-CHF call record includes the billing information in the first billing request.

[0418] In combination with the third aspect, in a possible implementation manner, the first charging request carries an identifier of a second charging resource generated by the primary CHF entity, and the first R-CHF entity 202 further includes an execution unit 903, which is configured to:

[0419] A second charging request is generated according to the identifier of the second charging resource, where the second charging request is used to request updating or releasing the second charging resource.

[0420] In combination with the third aspect, in a possible implementation manner, the second charging request further carries a notification receiving address of the first R-CHF, where the notification receiving address is used to update a notification address corresponding to the second charging resource on the primary CHF entity.

[0421] The notification address is used by the main CHF entity to subsequently send a notification message to the first R-CHF entity.

[0422] In combination with the third aspect, in a possible implementation, the second charging request is used to request updating or releasing the second charging resource, and the second charging request carries adjustment indication information, where the indication information is used to indicate that the first R-CHF entity has adjusted the trigger condition setting sent by the main CHF entity.

[0423] In combination with the third aspect, in a possible implementation manner, the first charging request is used to update or release the first charging resource, and the first R-CHF entity 202 further includes an execution unit 903, and the execution unit 903 is used to:

[0424] Determine a second R-CHF entity, where the second R-CHF entity is a CHF entity that provides relay capability for the CTF entity and the main CHF entity before the first R-CHF entity serves as a relay CHF entity; obtain relevant information of the first billing resource from the second R-CHF entity, where the first billing information is a billing resource generated by the second R-CHF entity.

[0425] In combination with the third aspect, in a possible implementation manner, the first charging request carries the switching information of the second R-CHF entity to the first R-CHF entity, and in terms of obtaining the relevant information of the first charging resource from the second R-CHF entity, the execution unit 903 is specifically used to:

[0426] Acquire first charging resource information from the second R-CHF entity according to the switching information,

[0427] The generating unit 902 is further configured to generate a second charging request according to the acquired first charging resource information.

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

[0429] receiving a remove R-CHF request sent by a CTF entity; the remove R-CHF request includes a remove indication, where the remove indication is used for the first R-CHF to return relevant information of a second charging resource generated by a main CHF entity; and sending a remove response message to the CTF entity, where the remove response message includes relevant information of the second charging resource generated by the main CHF entity.

[0430] In conjunction with the third aspect, in a possible implementation manner, the first R-CHF entity 202 further includes:

[0431] The releasing unit 904 is configured to release the first charging resource according to the remove R-CHF request, and the remove response message further includes a first charging resource release result.

[0432] It is worth pointing out that, the specific functional implementation of the first R-CHF entity 202 refers to the description of the above-mentioned charging method, for example, the transceiver unit 901 is used to execute the relevant contents of S301-S304, the generation unit 902, the execution unit 903 and the release unit 904 are used to execute the relevant contents of S302 and S304. Each unit or module in the first R-CHF entity 202 can be respectively or completely combined 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 practical 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).

[0433] Reference Fig.10 FIG. 1 is a schematic diagram of a structure of a CTF entity provided in an embodiment of the present application. The CTF entity is Figure 2The CTF entity 201 includes a sending unit 1001 and a receiving unit 1002.

[0434] The sending unit 1001 is configured to send a charging request to the first R-CHF entity. When the charging request is a request to remove the R-CHF on the premise that the charging resources have been established on the first R-CHF entity and the main CHF entity, the request to remove the R-CHF includes a removal indication, and the removal indication is used to instruct the first R-CHF to return the relevant information of the second charging resource generated by the main CHF entity; the main CHF entity provides online quota management and charging call record generation;

[0435] The receiving unit 1002 is configured to receive a removal response message sent by the first R-CHF entity, where the removal response message includes relevant information of the second charging resource generated by the primary CHF entity, and the relevant information of the first charging resource includes a second charging resource identifier;

[0436] The sending unit 1001 is further configured to send a third charging request to the primary CHF according to the second charging resource identifier, where the third charging request is an operation request for the second charging resource.

[0437] In a possible implementation, before or after the sending unit sends the third charging request,

[0438] The sending unit 1001 is further configured to send a request to release charging resources to the first R-CHF entity, where the request to release charging resources is used to request to release relevant information of charging resources created by the first R-CHF entity;

[0439] The receiving unit 1002 is further configured to receive a release charging resource response message sent by the first R-CHF entity, where the release charging resource response message is used to indicate that the first R-CHF entity has released relevant information of the charging resources created by the first R-CHF entity.

[0440] In conjunction with the fourth aspect, in a possible implementation, when the charging request is an insert R-CHF request under the premise that charging resources have been established on the CTF entity and the primary CHF entity, the insert R-CHF request includes relevant information of the second charging resource generated by the primary CHF entity;

[0441] The receiving unit 1002 is configured to receive a charging response message sent by the first R-CHF entity, where the charging response message includes a result of the first R-CHF sending a third charging request to the primary CHF according to relevant information of the second charging resource.

[0442] It is worth pointing out that, the specific functional implementation of the CTF entity 201 refers to the description of the above-mentioned billing method, such as the sending unit 1001 and the receiving unit 1002 are used to execute the relevant contents of S401 and S402. Each unit or module in the CTF entity 201 can be separately or completely merged into one or several 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 effects of the embodiments of the present invention. The above-mentioned units or modules are divided based on logical functions. In actual applications, the functions of one unit (or module) are implemented by multiple units (or modules), or the functions of multiple units (or modules) are implemented by one unit (or module). Of course, the CTF entity 201 also includes a functional unit for data processing, which is not schematically shown in the figure.

[0443] Based on the description of the above method embodiments and related device embodiments, please refer to Fig.11 , an embodiment of the present invention also provides a structural diagram of a first R-CHF entity 1100. Fig.11 The first R-CHF entity 1100 shown (the first R-CHF entity 1100 is specifically a computer device) includes a memory 1101, a processor 1102, a communication interface 1103 and a bus 1104. The memory 1101, the processor 1102 and the communication interface 1103 are connected to each other through the bus 1104.

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

[0445] The memory 1101 can store programs. When the program stored in the memory 1101 is executed by the processor 1102, the processor 1102 and the communication interface 1103 are used to execute Figure 3 The various steps of the charging method of the illustrated embodiment.

[0446] The processor 1102 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 first R-CHF entity 202 in the embodiment of the present application, or to execute the billing method of the method embodiment of the present application.

[0447] Processor 1102 can also be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the billing method of the present application can be completed by the hardware integrated logic circuit or software instructions in the processor 1102. Optionally, processor 1102 is a general-purpose processor, a digital signal processor (Digital Signal 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. Processor 1102 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 conjunction with 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 1101, and the processor 1102 reads the information in the memory 1101, and combines its hardware to complete the functions required to be executed by the units included in the first R-CHF entity 202 of the embodiment of the present application, or executes Figure 3 The billing method of the illustrated embodiment.

[0448] The communication interface 1103 uses a transceiver such as, but not limited to, a transceiver to implement communication between the first R-CHF entity 1100 and other devices (such as Figure 2 For example, the first R-CHF entity 1100 can receive a charging response message from the main CHF entity 203 through the communication interface 1103.

[0449] The bus 1104 may include a path for transmitting information between various components of the first R-CHF entity 1100 (eg, the memory 1101 , the processor 1102 , and the communication interface 1103 ).

[0450] It should be noted that although Fig.11 The first R-CHF entity 1100 shown only shows a memory, a processor, and a communication interface. However, in the specific implementation process, those skilled in the art should understand that the first R-CHF entity 1100 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 first R-CHF entity 1100 may also include hardware devices for implementing other additional functions. In addition, those skilled in the art should understand that the first R-CHF entity 1100 may also only include the devices necessary for implementing the embodiments of the present application, and does not necessarily include Fig.11 All devices shown in .

[0451] 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 structural diagram of a CTF entity 1200. Fig.12 The CTF entity 1200 shown (the CTF entity 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.

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

[0453] 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 4 The various steps of the charging method of the illustrated embodiment.

[0454] The processor 1202 uses a general-purpose 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 CTF entity 201 of the embodiment of the present application, or to execute the billing method of the method embodiment of the present application.

[0455] Processor 1202 can also be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the billing method of the present application can be completed by the hardware integrated logic circuit or software instructions in the processor 1202. Optionally, processor 1202 is a general-purpose processor, a digital signal processor (Digital Signal 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. 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 conjunction with 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 completes the functions required to be executed by the units included in the CTF entity 201 of the embodiment of the present application in combination with its hardware, or executes Figure 4 The billing method of the illustrated embodiment.

[0456] The communication interface 1203 uses a transceiver such as, but not limited to, a transceiver to implement communication between the CTF entity 1200 and other devices (such as Figure 2 For example, the CTF entity 1200 can obtain the charging response message from the first R-CHF entity through the communication interface 1203.

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

[0458] It should be noted that although Fig.12 The CTF entity 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 CTF entity 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 CTF entity 1200 may also include hardware devices for implementing other additional functions. In addition, those skilled in the art should understand that the CTF entity 1200 may also only include the devices necessary to implement the embodiments of the present application, and does not necessarily include Figure 8 All devices shown in .

[0459] 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 method of the embodiment of the present application.

[0460] 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 method.

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

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

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

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

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

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

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

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

[0469] 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 charging method, characterized in that: Applied to a first relay charging function R-CHF entity, the method comprises: receiving a first charging request from a charging trigger function CTF entity, where the first charging request is used to request to create, update or release a first charging resource; Sending the second charging request to the main CHF entity according to the first charging request; the second charging request is used to request to create, update or release a second charging resource; the main CHF entity provides online quota management and charging call record generation; receiving a second charging response message sent by the primary CHF entity to respond to the second charging request, where the second charging response message includes third capability information, where the third capability information is capability information determined by the primary CHF entity according to the second charging request and used for interaction between the primary CHF entity and the first R-CHF entity; generating a first charging response message for responding to the first charging request according to the second charging response message, and sending the first charging response message to the CTF entity, where the first charging response message includes fourth capability information, where the fourth capability information is capability information determined by the first R-CHF according to the third capability information for interaction between the first R-CHF entity and the CTF entity.

2. The method according to claim 1, characterized in that The first charging request further includes first capability information; the first capability information is capability information provided by the CTF entity and can be used for interaction between the first R-CHF entity and the CTF entity; The second charging request includes second capability information, where the second capability information represents a capability for the main CHF entity to interact with the first R-CHF entity, and the second capability information is determined by the first R-CHF entity according to the first capability information.

3. The method according to claim 2, characterized in that The first capability information includes at least one of a first payload size of a charging message for the first charging resource supported by the CTF entity, a first idle duration for charging information collection of the CTF entity for the first charging resource, or a first charging characteristic; The fourth capability information includes at least one of a fourth payload size of a charging message for the first charging resource, a fourth idle time for charging information collection of the CTF entity for the first charging resource, a fourth charging characteristic, or a first charging resource trigger condition setting; The second capability information includes at least one of a payload size of a charging message for the 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; The third capability information includes at least one of a third payload size of a charging message for the second charging resource, a third idle time for charging information collection of the first R-CHF entity for the second charging resource, a third charging characteristic, or a second charging resource trigger condition setting.

4. The method according to claim 3, characterized in that The second capability information is determined by the first R-CHF entity according to the first capability information, including: When the first capability information includes the first payload size, the second capability information also includes the second payload size, and the second payload size is the smaller of the first payload size and a payload size of a charging message for a first charging resource supported by the first R-CHF entity; When the first capability information includes the first idle duration, the second capability information also includes the second idle duration, and the second idle duration is the smaller of the first idle duration and the idle duration for charging information collection of the first R-CHF entity for the second charging resource; When the first capability information includes the first charging characteristic, the second capability information also includes the second charging characteristic, and the second charging characteristic is an intersection of the first charging characteristic and a charging characteristic supported by the first R-CHF entity.

5. The method according to claim 3, characterized in that: When the third capability information includes the third payload size, the fourth capability information also includes the fourth payload size, and if the second capability information includes the second payload size, the fourth payload size is the third payload size; if the second capability information does not include the second payload size, the fourth payload size is the smaller of the third payload size and the payload size of the charging message for the first charging resource supported by the first R-CHF entity; When the third capability information includes the third idle duration, the fourth capability information also includes the fourth idle duration, and if the second capability information includes the second idle duration, the fourth idle duration is the third idle duration of the third capability information; If the second capability information does not include the second idle duration, the fourth idle duration is the smaller of the third idle duration and the idle duration for charging information collection of the first R-CHF entity for the second charging resource; If the third capability information includes the third charging characteristic, the fourth capability information also includes the fourth charging characteristic; if the second capability information includes the second charging characteristic, the fourth charging characteristic is the third charging characteristic; if the second capability information does not include the second charging characteristic, the fourth charging characteristic is an intersection of the third charging characteristic and the charging characteristics supported by the first R-CHF entity; If the third capability information includes a second billing resource trigger condition setting, the fourth capability information also includes a first billing resource trigger condition setting, the status information in the first billing resource trigger condition setting is the union of the status information in the second billing resource trigger condition setting and the status information of the trigger condition determined by the first R-CHF entity, and the threshold value of the trigger condition in the first billing resource trigger condition setting is the smaller of the threshold value of the trigger condition in the second billing resource trigger condition setting and the threshold value of the trigger condition determined by the first R-CHF entity.

6. The method according to any one of claims 1 to 5, characterized in that: The first charging request is used to request the creation of the first charging resource, and the method further includes: When the first charging request is used to request execution of session-based convergent charging, generating a first charging resource corresponding to the first charging request; opening a first R-CHF bill in the first charging resource, and writing the charging information in the first charging request into the first R-CHF bill; When the first billing request is used to request a one-time event billing, a first billing resource corresponding to the first billing request is generated, and the first R-CHF call record is generated according to the first billing resource and the billing information of the first billing request, wherein the first R-CHF call record includes the billing information in the first billing request.

7. The method according to any one of claims 1 to 5, characterized in that: The first charging request carries an identifier of a second charging resource generated by the primary CHF entity, and the method further includes: The second charging request is generated according to the identifier of the second charging resource, where the second charging request is used to request updating or releasing the second charging resource.

8. The method according to claim 7, characterized in that The second charging request also carries a notification receiving address of the first R-CHF, where the notification receiving address is used to update a notification address corresponding to the second charging resource on the primary CHF entity.

9. The method according to any one of claims 1 to 5, characterized in that: The second charging request is used to request updating or releasing the second charging resource, and the second charging request carries adjustment indication information, where the indication information is used to indicate that the first R-CHF entity has adjusted the trigger condition setting sent by the main CHF entity.

10. The method according to any one of claims 1 to 5, wherein the first charging request is used to update or release a first charging resource, and the method further comprises: Determine a second R-CHF entity, where the second R-CHF entity is a CHF entity that provides relay capability for the CTF entity and the main CHF entity before the first R-CHF entity serves as a relay CHF entity; The related information of the first charging resource is obtained from the second R-CHF entity, where the first charging information is the charging resource generated by the second R-CHF entity.

11. The method according to claim 10, characterized in that The first charging request carries switching information of the second R-CHF entity switching to the first R-CHF entity, and the acquiring relevant information of the first charging resource from the second R-CHF entity includes: acquiring relevant information of the first charging resource from the second R-CHF entity according to the switching information; The method further comprises: Generate the second billing request according to the acquired first billing resource information.

12. The method according to any one of claims 1 to 11, characterized in that: The method further comprises: receiving a remove R-CHF request sent by the CTF entity; the remove R-CHF request includes a remove indication, where the remove indication is used by the first R-CHF to return relevant information of the second charging resource generated by the main CHF entity; Send a removal response message to the CTF entity, where the removal response message includes relevant information of the second charging resource generated by the main CHF entity.

13. The method according to claim 12, characterized in that The method further comprises: The first charging resource is released according to the remove R-CHF request, and the remove response message also includes a first charging resource release result.

14. A charging method, characterized in that: The method is applied to a charging trigger function CTF entity, and includes: Sending a charging request to a first relay charging function R-CHF entity; When the charging request is a request to remove R-CHF on the premise that charging resources have been established on the first relay charging function R-CHF entity and the main CHF entity, the request to remove R-CHF includes a removal indication, and the removal indication is used for the first R-CHF to return the relevant information of the second charging resource generated by the main CHF entity; the main CHF entity provides online quota management and charging call record generation; The method further includes: receiving a removal response message sent by the first R-CHF entity, the removal response message including relevant information of the second charging resource generated by the primary CHF entity, the relevant information including the second charging resource identifier; A third charging request is sent to the primary CHF according to the second charging resource identifier, where the third charging request is an operation request for the second charging resource.

15. The method according to claim 14, characterized in that When the charging request is an insert R-CHF request under the premise that charging resources have been established on the CTF entity and the primary CHF entity, the insert R-CHF request includes relevant information of the second charging resource generated by the primary CHF entity; The method further includes: receiving a charging response message sent by the first R-CHF entity, wherein the charging response message includes a result of the first R-CHF sending the third charging request to the primary CHF according to relevant information of the second charging resource.

16. The method according to claim 14, characterized in that Before or after sending the third charging request, the method further includes: Sending a request for releasing charging resources to the first R-CHF entity, where the request for releasing charging resources is used to request the release of relevant information of charging resources created by the first R-CHF entity; A charging resource release response message sent by the first R-CHF entity is received, where the charging resource release response message is used to indicate that the first R-CHF entity has released relevant information of the charging resources created by the first R-CHF entity.

17. A first relay charging function R-CHF entity, characterized in that: include: A transceiver unit, configured to receive a first charging request from a charging trigger function CTF entity, wherein the first charging request creates, updates or releases a first charging resource; The transceiver unit is further configured to send a second charging request to the primary CHF entity; the second charging request is used to request to create, update or release a second charging resource; receive a second charging response message sent by the primary CHF entity to respond to the second charging request, the second charging response message including third capability information, the third capability information being capability information determined by the primary CHF entity according to the second charging request for interaction between the primary CHF entity and the first R-CHF entity; The generating 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; the first charging response message includes fourth capability information, and the fourth capability information is capability information determined by the first R-CHF according to the third capability information for interaction between the first R-CHF entity and the CTF entity. The transceiver unit is further configured to send the first charging response message to the CTF entity.

18. The R-CHF entity according to claim 17, characterized in that The first charging request further includes first capability information; the first capability information is capability information provided by the CTF entity and can be used for interaction between the first R-CHF entity and the CTF entity; The second charging request includes second capability information, where the second capability information indicates a capability for the primary CHF entity to interact with the first R-CHF entity, and the second capability information is determined by the first R-CHF entity according to the first capability information; and the third capability information is determined by the primary CHF entity according to the second capability information.

19. The R-CHF entity according to claim 18, characterized in that The first capability information includes at least one of a payload size of a charging message for the first charging resource supported by the CTF entity, a first idle duration for charging information collection of the CTF entity for the first charging resource, or a charging characteristic; The fourth capability information includes at least one of a payload size of a charging message for a first charging resource, a fourth idle duration for charging information collection of a CTF entity for the first charging resource, a charging characteristic, or a first charging resource trigger condition setting; The second capability information includes at least one of a payload size for a charging message in 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 charging characteristic; The third capability information includes at least one of a payload size of a charging message for the second charging resource, a third idle duration for charging information collection of the first R-CHF entity for the second charging resource, a charging characteristic, or a second charging resource trigger condition setting.

20. The R-CHF entity according to claim 19, characterized in that The second capability information is determined by the first R-CHF entity according to the first capability information, including: When the first capability information includes the first payload size, the second capability information also includes the second payload size, and the second payload size is the smaller of the first payload size and a payload size of a charging message for a second charging resource supported by the first R-CHF entity; When the first capability information includes the first idle duration, the second capability information also includes the second idle duration, and the second idle duration is the smaller of the first idle duration and the idle duration for charging information collection of the first R-CHF entity for the second charging resource; When the first capability information includes the first charging characteristic, the second capability information also includes the second charging characteristic, and the second charging characteristic is an intersection of the first charging characteristic and a charging characteristic supported by the first R-CHF entity.

21. The R-CHF entity according to claim 19, characterized in that: When the third capability information includes the third payload size, the fourth capability information also includes the fourth payload size, and if the second capability information includes the second payload size, the fourth payload size is the third payload size; if the second capability information does not include the second payload size, the fourth payload size is the smaller of the third payload size and the payload size of the charging message for the first charging resource supported by the first R-CHF entity; When the third capability information includes the third idle duration, the fourth capability information also includes the fourth idle duration, and if the second capability information includes the second idle duration, the fourth idle duration is the third idle duration of the third capability information; If the second capability information does not include the second idle duration, the fourth idle duration is the smaller of the third idle duration and the idle duration for charging information collection of the first R-CHF entity for the second charging resource; If the third capability information includes the third charging characteristic, the fourth capability information also includes the fourth charging characteristic; if the second capability information includes the second charging characteristic, the fourth charging characteristic is the third charging characteristic; if the second capability information does not include the second charging characteristic, the fourth charging characteristic is an intersection of the third charging characteristic and the charging characteristics supported by the first R-CHF entity; The third capability information includes the second charging resource trigger condition setting, the fourth capability information also includes the first charging resource trigger condition setting, and the state information in the first charging resource trigger condition setting is a union of the state information in the second charging resource trigger condition setting and the state information of the trigger condition determined by the first R-CHF entity; The threshold value of the trigger condition in the first charging resource trigger condition setting is the smaller one of the threshold value of the trigger condition in the second charging resource trigger condition setting and the threshold value of the trigger condition determined by the first R-CHF entity.

22. The R-CHF entity according to any one of claims 17 to 21, characterized in that The first charging request is used to request the creation of the first charging resource, and the first R-CHF entity includes an execution unit, and the execution unit is used to: When the first charging request is used to request execution of session-based convergent charging, generating a first charging resource corresponding to the first charging request; opening a first R-CHF bill in the first charging resource, and writing the charging information in the first charging request into the first R-CHF bill; When the first billing request is used to request a one-time event billing, a first billing resource corresponding to the first billing request is generated, and the first R-CHF call record is generated according to the first billing resource and the billing information of the first billing request, wherein the first R-CHF call record includes the billing information in the first billing request.

23. The R-CHF entity according to any one of claims 17 to 21, characterized in that The first charging request carries an identifier of a second charging resource generated by the primary CHF entity, and the first R-CHF entity further includes an execution unit, which is configured to: The second charging request is generated according to the identifier of the second charging resource, where the second charging request is used to request updating or releasing the second charging resource.

24. The R-CHF entity according to claim 23, characterized in that The second charging request also carries a notification receiving address of the first R-CHF, where the notification receiving address is used to update a notification address corresponding to the second charging resource on the primary CHF entity.

25. The R-CHF entity according to any one of claims 17 to 21, characterized in that The second charging request is used to request updating or releasing the second charging resource, and the second charging request carries adjustment indication information, where the indication information is used to indicate that the first R-CHF entity has adjusted the trigger condition setting sent by the main CHF entity.

26. The R-CHF entity according to any one of claims 17 to 21, wherein the first charging request is used to update or release the first charging resource, and the first R-CHF entity further comprises an execution unit, wherein the execution unit is configured to: Determine a second R-CHF entity, where the second R-CHF entity is a CHF entity that provides relay capability for the CTF entity and the main CHF entity before the first R-CHF entity serves as a relay CHF entity; The related information of the first charging resource is obtained from the second R-CHF entity, where the first charging information is the charging resource generated by the second R-CHF entity.

27. The R-CHF entity according to claim 26, characterized in that The first charging request carries switching information of the second R-CHF entity switching to the first R-CHF entity, and in the aspect of acquiring the relevant information of the first charging resource from the second R-CHF entity, the execution unit is specifically used to: acquiring the first charging resource information from the second R-CHF according to the switching information, The generating unit is further configured to generate the second charging request according to the acquired first charging resource information.

28. The R-CHF entity according to any one of claims 17 to 27, characterized in that The transceiver unit is also used for: receiving a remove R-CHF request sent by the CTF entity; the remove R-CHF request includes a remove indication, where the remove indication is used by the first R-CHF to return relevant information of the second charging resource generated by the main CHF entity; Send a removal response message to the CTF entity, where the removal response message includes relevant information of the second charging resource generated by the main CHF entity.

29. The R-CHF entity according to claim 28, characterized in that The R-CHF entity further comprises: A releasing unit is used to release the first charging resource according to the remove R-CHF request, and the remove response message also includes the first charging resource release result.

30. A charging trigger function CTF entity, characterized in that: include: a sending unit, configured to send a charging request to the CTF entity, When the charging request is a request to remove R-CHF on the premise that charging resources have been established on the first relay charging function R-CHF entity and the main CHF entity; the request to remove R-CHF includes a removal indication, and the removal indication is used to instruct the first R-CHF to return the relevant information of the second charging resource generated by the main CHF entity; The main CHF entity provides online quota management and billing record generation; The CTF entity also includes: a receiving unit, configured to receive a removal response message sent by the first R-CHF entity, wherein the removal response message includes relevant information of the second charging resource generated by the primary CHF entity, and the relevant information includes an identifier of the second charging resource; The sending unit is further configured to send a third charging request to the primary CHF according to the second charging resource identifier, where the third charging request is an operation request for the second charging resource.

31. The CTF entity according to claim 30, characterized in that: When the charging request is an insert R-CHF request under the premise that charging resources have been established on the CTF entity and the primary CHF entity, the insert R-CHF request includes relevant information of the second charging resource generated by the primary CHF entity; The CTF entity also includes: A receiving unit is configured to receive a charging response message sent by the first R-CHF entity, wherein the charging response message includes a result of the R-CHF sending a third charging request to the primary CHF according to relevant information of the second charging resource.

32. The CTF entity according to claim 30, characterized in that: before or after sending the third charging request; The sending unit is further used to send a request to release charging resources to the first R-CHF entity, where the request to release charging resources is used to request to release relevant information of charging resources created by the first R-CHF entity; The receiving unit is further configured to receive a release charging resource response message sent by the first R-CHF entity, where the release charging resource response message is used to indicate that the first R-CHF entity has released relevant information of the charging resources created by the first R-CHF entity.

33. A charging method, characterized in that: The method is applied to a charging system, the charging system comprising a first relay charging function R-CHF entity, a charging trigger function CTF entity and a main CHF entity, and the method comprises: The CTF entity sends a first charging request to the first R-CHF entity, where the first charging request is used to request to create, update or release a first charging resource; The first R-CHF entity sends the second charging request to the main CHF entity; the second charging request is used to request to create, update or release a second charging resource; the main CHF entity provides online quota management and charging call record generation; The primary CHF entity performs charging processing according to the second charging request, and generates a second charging response message for responding to the second charging request; sends the second charging response message to the first R-CHF entity, where the second charging response message includes third capability information, where the third capability information is capability information determined by the primary CHF according to the second charging request for interaction between the primary CHF entity and the first R-CHF entity; The first R-CHF entity generates a first charging response message for responding to the first charging request according to the second charging response message, and sends the first charging response message to the CTF entity, where the first charging response message includes fourth capability information, where the fourth capability information is capability information determined by the first R-CHF according to the third capability information and used for interaction between the first R-CHF entity and the CTF entity; The CTF entity performs charging processing according to the first charging response message.

34. A billing system, characterized in that: The charging system comprises a first relay charging function 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, where the first charging request is used to request to create, update or release a first charging resource; The first R-CHF entity is used to send the second charging request to the main CHF entity; the second charging request is used to request to create, update or release the second charging resource; the main CHF entity provides online quota management and charging call record generation; The master CHF entity is configured to perform charging processing according to the second charging request and generate a second charging response message for responding to the second charging request; send the second charging response message to the first R-CHF entity, where the second charging response message includes third capability information, where the third capability information is capability information determined by the master CHF according to the second charging request for interaction between the master CHF entity and the first R-CHF entity; the first R-CHF entity, configured to generate a first charging response message for responding to the first charging request according to the second charging response message, and send the first charging response message to the CTF entity, where the first charging response message includes fourth capability information, where the fourth capability information is capability information determined by the first R-CHF according to the third capability information and used for interaction between the first R-CHF entity and the CTF entity; The CTF entity is used to perform charging processing according to the first charging response message.

35. A first 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 13.

36. A CTF 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 14 to 16.

37. 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 16 is implemented.

Images