WO2016150143A1

WO2016150143A1 - Cats charging method, and charging-message request sending method and apparatus

Info

Publication number: WO2016150143A1
Application number: PCT/CN2015/091567
Authority: WO
Inventors: 郭文洁
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-03-20
Filing date: 2015-10-09
Publication date: 2016-09-29
Also published as: CN106034033A

Abstract

The embodiments of the present invention provide a CATS charging method, and a charging-message request sending method and apparatus. The CATS charging method comprises: when a service bottleneck occurs on a third-party application server (AS) and when an application policy functional entity CATSF is controlled to receive an interaction request message from said third-party AS, generating a CATSF policy according to preconfigured information and the request message; the CATSF sending the CATSF policy and configuration information to a terminal UE, so as to cause the UE to control a corresponding application flow according to the CATSF policy and configuration information, and sending a charging control message to a packet core network (PCN) by means of a charging interface Sxch with the PCN; the solution improves the accuracy of CATSF charging.

Description

CATS charging method, charging message request sending method and device

Technical field

The present invention relates to, but is not limited to, the field of mobile communications, and in particular, to a charging method (Control of Applications when Third Party Servers encounter difficulties), a method for transmitting a charging message request, and a device.

Background technique

Currently, 3GPP (3rd Generation Partnership Project) is studying a third-party business bottleneck that does not affect the CATS scenario of other applications, that is, when the performance of the third-party service server running the application is insufficient to cope with a large number of When a user accesses, the overall network speed decreases due to congestion or server downtime, which may affect the access of the user equipment UE or the mobile device to other applications. The 3GPP network proposes the need to detect or perceive such application congestion in order to be controllable (the congestion of an application on the same server does not affect the experience of accessing other applications). As far as possible, the 3GPP network assists the third party in applying bottlenecks. The business server reduces or avoids invalid traffic, helping the business server recover from an overloaded state.

Different applications on the service server encounter different bottlenecks, some of which are severely failing hardfailure. In this case, there is no application traffic, and some are soft failures. At this time, some traffic will still be generated, but the user experience is poor. . 3GPP proposes two design ideas of network side control and UE control, and proposes the need to differentiate the traffic of traffic in this scenario.

The design of the service traffic of the third-party AS (Application Server) is not affected by the network side. The EPC (Evolved Packet Core) in the existing 3GPP can be used in this scenario. Network evolution) charging interface, as shown in Figure 1: PCN (Packet Core Network) generally represents the packet domain core network element that generates charging information, including: SGSN (Serving GPRS Support Node, Serving GPRS Support Node) ), GGSN (Gateway GPRS (General Packet Radio Service) Support Node, Gateway GPRS Support Node), S-GW (Serving GateWay, Service Gateway), P-GW (PDN GateWay, PDN (Public Data Network) Gateway) (which can include PCEF (Policy and Charging Enforcement Function)) and TDF (Traffic Detection Function) Detection function). These core network elements are based on different deployment combinations of CTF (Charging Trigger Function), CDF (Charging Data Function), and CGF (Charging Gateway Function). The core of the design of the traffic flow of the third-party AS is controlled by the UE when the network senses that the application change of the third-party AS is controlled by the UE, thereby reducing the invalid service access directly in the air interface. Flow, for the purpose of thorough control. However, this design has a large impact on the existing billing interface, which makes it impossible to use the existing billing interface for billing, which makes the CATS billing management more difficult.

Summary of the invention

The following is a summary of the subject matter described in detail herein, and is not intended to limit the scope of the claims.

The embodiment of the invention provides a CATS charging method and a charging message request sending method and device, which can solve the problem that the method of controlling the service traffic of the third-party AS by using the UE side causes the CATS charging management to be difficult.

The embodiment of the present invention provides a CATS charging method, which includes: when a third party application server AS service bottleneck is used, the policy function entity CATSF of the control application receives the interaction request message from the third-party AS, according to the pre-configured information and the request message. Generating a CATSF policy; the CATSF sends the CATSF policy and configuration information to the terminal UE, so that the UE controls the corresponding application flow according to the CATSF policy and the configuration information, and controls the charging through the charging interface Sxch with the packet core network PCN. The message is sent to the PCN.

The interaction request message includes: an address of the third-party AS, a sub-application identifier, a sub-application congestion status, and a third-party provider identifier.

The CATSF policy includes at least one of the following information: an address of a third-party AS, a sub-application identifier, a sub-application congestion status, a sub-application control action, and a third-party provider identifier.

The sub-application control action is one of the following three actions: controlling the application flow to stop and hang Start or resume operation.

The pre-configured information of the operator includes: whether to control the CATS and CATS control mode when the third-party application server AS service bottleneck is performed, and whether to provide CDR (Charging Data Record) for assisting the third-party AS control service bottleneck. data record);

When the pre-configured information includes providing CDRs for assisting the third party AS to control the service bottleneck, after transmitting the intermediate charging data request message to the offline charging system, updating the content of the CDR of the UE, and creating a CATS for the third party AS a CDR; wherein the CDR of the CATS records traffic related to a CATS policy change, a timestamp, a sub-application identifier, and sub-application control action information.

According to another aspect of the embodiments of the present invention, a charging message request sending method is provided, including: the terminal UE sends a request for acquiring a CATSF policy to a policy function entity CATSF of a third-party application server AS service bottleneck control application; The CATSF policy and configuration information are used to control the corresponding application flow; when the sub-application control action changes, the charging control message is sent to the PCN through the charging interface Sxch with the packet core network PCN.

According to still another aspect of the embodiments of the present invention, a CATS charging apparatus is provided, including: a generating module, configured to control an application function function CATSF of an application to receive an interaction request from a third-party AS when the third-party application server AS service bottleneck The CATSF policy is generated according to the pre-configured information and the request message; the first sending module is configured to send the CATSF policy and the configuration information to the UE through the CATSF, so that the UE controls the corresponding application flow according to the CATSF policy and the configuration information. The charging control message is sent to the PCN through a charging interface Sxch with the packet core network PCN.

The sub-application control action is one of the following three actions: controlling the application flow to stop, suspend, or resume operation.

The pre-configured information includes: whether to control the CATS, the control mode of the CATS, and whether to assist the third-party AS control when performing the third-party application server AS service bottleneck The service bottleneck provides the CDR of the charging data record;

The apparatus further includes: an update module configured to: when the pre-configured information includes providing a CDR to assist the third-party AS control service bottleneck, update the content of the CDR of the UE after transmitting the intermediate charging data request message to the offline charging system And creating a CDR of the CATS for the third party AS; wherein the CDR of the CATS records the traffic related to the CATS policy change, the timestamp, the sub-application identifier, and the sub-application control action information.

According to still another aspect of the embodiments of the present invention, a charging message request sending apparatus is provided, including: a receiving module, configured to send a CATSF by a policy function entity CATSF of a third party application server AS service bottleneck control application through a terminal UE a policy request; the control module is configured to control the corresponding application flow according to the received CATSF policy and the configuration information; and the second sending module is configured to pass between the sub-application control action and the packet core network PCN The charging interface Sxch sends a charging control message to the PCN.

The beneficial effects of the embodiments of the present invention are as follows:

The embodiment of the present invention provides a charging interface for CATSF charging between a terminal and a core network based on terminal-side control, and sends a charging request to the core network through the interface when charging is required, so that the charging of the CATSF can be Effective management improves the accuracy of CATSF billing.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

1 is a schematic diagram of an existing interface architecture of EPC offline charging in Embodiment 1 of the present invention;

2 is a flowchart of a CATS charging method according to Embodiment 1 of the present invention;

3 is a flowchart of a charging message request sending method according to Embodiment 1 of the present invention;

FIG. 4 is a schematic diagram of the architecture of controlling CATS charging based on the UE side according to the embodiment.

5 is a schematic diagram of message handover of an Sxch interface for charging according to the present invention;

Figure 6 is a block diagram showing the structure of a CATS charging apparatus according to Embodiment 5 of the present invention;

FIG. 7 is a structural block diagram of a charging message request sending apparatus according to Embodiment 5 of the present invention; FIG.

FIG. 8 is a schematic diagram of a charging interface controlled by a CATS UE side according to Embodiment 5 of the present invention.

Preferred embodiment of the invention

The embodiment of the present invention provides a CATS charging method, a charging message request sending method, and an apparatus. The embodiments of the present invention are further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

The CATS Policy Server is a logical unit introduced in the 3GPP requirements. In the embodiment of the present invention, it is simply referred to as CATSF (a policy function for controlling an application when a third-party AS service bottleneck). The embodiment of the present invention proposes performing CATS-related pre-configuration on the CATSF, and the configuration information includes at least one of the following information:

Whether to perform CATS control: the value is yes or no;

CATS control mode: enumerated type, the value is UE side control or network side control;

Whether to help the third-party AS control service bottleneck CDR: The value is yes or no.

The embodiment of the present invention is based on a new charging architecture, interface, and method for controlling a traffic flow scenario CATS of a third-party AS on the UE side, to provide a CATSF charging method, where the CATSF may be a network in the core network. A meta can also be an entity that exists independently of the core network.

Example 1

The embodiment of the present invention provides a CATS charging method, which is implemented based on CATSF, and FIG. 2 is a flowchart of a CATS charging method according to Embodiment 1 of the present invention. As shown in FIG. 2, the method includes the following steps:

Step 201: When the third-party application server AS service bottleneck is used, the policy function entity CATSF of the control application receives the interaction request message from the third-party AS, and generates a CATSF policy according to the pre-configured information and the interaction request message.

Step 202: The CATSF sends the CATSF policy and the configuration information to the terminal UE, so that the UE controls the corresponding application flow according to the CATSF policy and the configuration information, and communicates with the packet core network PCN. The charging interface Sxch sends a charging control message to the PCN.

Optionally, in the foregoing step 201, the policy function entity CATSF of the third-party AS service bottleneck control application interacts with the third-party AS to obtain an interaction request message;

In this step, the third party CATSF may request an interaction request message from the third party AS; The third-party AS may actively report the interaction request message to the CATSF when the CATSF needs to be used.

Optionally, the interaction request message may include: an address of the third-party AS, a sub-application identifier, a sub-application congestion status, and a third-party provider identifier.

The CATSF formulates or updates a CATSF policy according to the pre-configured information and the interaction request message;

The pre-configured information includes: whether the application control CATS, the CATS control mode when the third-party application server AS service bottleneck is performed, and whether the charging data record CDR is provided to assist the third-party AS control service bottleneck.

Sending a policy update message to the UE when the CATSF policy is updated;

In this step, if the congestion status of the sub-application changes, the CATSF policy also needs to be changed accordingly. The application congestion status referred to here corresponds to different congestion levels, and the UE needs corresponding control of the application flow. status.

Transmitting the updated CATSF policy and configuration information to the UE according to the policy request message of the UE, so that the UE controls the corresponding application flow according to the CATSF policy and the configuration information, and adopts a charging interface Sxch with the PCN core network. The charging control message is sent to the PCN;

The UE controls the sub-application to one of the following three actions: controlling the application flow to stop, suspend, or resume operation. Among them, suspending refers to suspending the running of the application, but does not end the process of the application stream. Stopping means ending the app and exiting the app.

After receiving the CATS charging control message from the UE, the PCN sends an intermediate charging data request message to the offline charging system.

The PCN successfully receives the CATS charging control message from the UE, which may be a separate session-related or unrelated charging message serving the CATS, or may be a charging change message triggered by the CATS. Optionally, after the PCN successfully receives the CATS charging change message from the UE, the intermediate charging data request message is sent to the offline charging system, and the CATS charging change message is changed when the sub-application control action changes, and the sub-application control action A billing message that is generated when it is suspended, resumed, or stopped.

In this step, when the carrier configuration information includes providing a CDR for assisting the third party AS to control the service bottleneck, after transmitting the intermediate charging data request message to the offline charging system, the UE is updated. The content of the CDR, and the CDR of the CATS created for the third party AS, the CDR of the CATS records the traffic related to the CATSF policy change, the timestamp, the sub-application identifier, and the sub-application control action information.

With respect to the above-mentioned CATS charging method, the embodiment further provides a charging message request sending method, which can be implemented on the terminal, and is used to control and initiate the corresponding application flow after receiving the update policy of the CATSF. Billing request.

FIG. 3 is a flowchart of a method for sending a charging message request according to Embodiment 1 of the present invention. As shown in FIG. 3, the method includes the following steps:

Step 301: After receiving the policy update message from the CATSF, the UE sends a request for obtaining the updated CATSF policy to the CATSF.

Step 302: Control the corresponding application flow according to the received CATSF update policy and configuration information from the CATSF, and control the charging through the charging interface Sxch between the PCN core network when the sub-application control action changes. The message is sent to the PCN.

Example 2

This embodiment provides a process and method for using a UE-side control sub-application to suspend and provide a CDR for a third-party AS.

The configuration information pre-set by the operator on the CATSF is: whether to perform CATS control: the value is YES;

CATS control mode: enumerated type, the value is the UE side control;

Whether to help the third-party AS control service bottleneck CDR: the value is yes;

FIG. 4 is a schematic diagram of the architecture of controlling CATS charging based on the UE side according to the embodiment. As shown in FIG. 4, the method includes the following steps:

Step 1: The third-party AS interacts with the CATSF, and requests the CATSF to assist in controlling the messages and responses of certain applications that access the third-party AS. The interactive request message includes at least one of the following information: a third-party AS address, a sub-application identifier, and a sub-application. Congestion status, third party provider identification.

Step 2: The CATSF formulates or updates the CATSF policy according to the pre-configured information and the interaction request information received from the step 1: (eg, the sub-application congestion state: the congestion degree is high), and the sub-application control action is: suspend.

Step 3: CATSF sends a CATSF policy update when the policy is updated according to the configuration information. A notification message is sent to the UE.

Step 4: The UE receives the notification message of step 3 and sends a policy acquisition request message to the CATSF. The CATSF returns the updated CATSF policy and the configuration information on the CATSF to the UE. The CATSF policy contains at least one of the following information: a third-party AS address. Sub-application ID, sub-application congestion status, sub-application control action (suspend), and third-party provider ID; configuration information includes: whether to perform CATS control, value is, CATS control mode, enumeration type, and value is UE Side control, whether to assist the third-party AS control service bottleneck CDR: The value is yes.

Step 5: The UE suspends the corresponding sub-application flow according to the latest CATSF policy acquired in step 4, and sends a control message for charging, that is, a CATS charging change request message, on the Sxch charging interface. The message includes the configuration information related to the charging and the updated policy information, including: the third-party AS address, the sub-application identifier, the sub-application congestion status, the sub-application control action (suspend), the third-party provider identifier, whether to proceed CATS control: value is, CATS control mode: enumeration type, the value is the UE side control and whether it is to assist the third party AS control service bottleneck CDR: the value is yes, the message interaction of the Sxch interface for charging is detailed See Figure 5;

Step 6: After successfully receiving the CATS charging change request message from the UE, the PCN sends an intermediate charging data request message including the information of the UE from step 5 to the offline charging system. The PCN adds an update to the content of the CDR of the UE. Since the CDR is configured to assist the third-party AS to control the service bottleneck, the PCN also creates a CATS-related CDR for the third-party AS, and records the traffic related to the CATSF policy change, the timestamp, the sub-application identifier, and the sub-application control action. information.

Example 3

This embodiment provides a process and a method for using the UE side to control sub-application recovery, and does not need to provide a CDR for a third-party AS as follows:

The pre-configured information of the operator on the CATSF is: whether to perform CATS control: the value is YES;

CATS control mode: enumerated type, the value is the UE side control;

Whether to help the third-party AS control service bottleneck CDR: the value is no;

The method comprises the following steps:

Step 1: The third-party AS interacts with the CATSF and requests CATSF to assist in controlling access to the third party. The message and response of some applications of the AS, the interactive request message includes at least one of the following information: a third-party AS address, a sub-application identifier, a sub-application congestion status, and a third-party provider identifier.

Step 2: The CATSF according to the operator pre-configuration information and the interaction request information received from the step 1, the information includes: the sub-application congestion status (the congestion level returns to normal) to formulate or update the CATSF policy, and the sub-application control action is recovery.

Step 3: The CATSF sends a CATSF policy update notification message to the UE when the policy is updated according to the configuration information.

Step 4: The UE receives the notification message of step 3 and sends a policy acquisition request message to the CATSF. The CATSF returns the updated CATSF policy and the configuration information on the CATSF to the UE. The CATSF policy contains at least one of the following information: a third-party AS address. Sub-application identification, sub-application congestion status, sub-application control action (recovery), and third-party provider identification; configuration information includes: whether to perform CATS control: value is, CATS control mode: enumeration type, the value is the UE side Control, whether to assist the third-party AS control service bottleneck CDR: The value is no.

Step 5: The UE performs recovery processing on the sub-application flow according to the latest CATSF policy acquired in step 4, and sends a control message for charging, that is, a CATS charging change request message, on the Sxch charging interface. The CATS charging change request message includes configuration information related to charging and updated policy information: third-party AS address, sub-application identification, sub-application congestion status, sub-application control action (recovery), third-party provider identification, whether to proceed CATS control: value is, CATS control mode: enumeration type, value is UE-side control, and whether to assist the third-party AS control service bottleneck CDR: the value is no, the message interaction of the Sxch interface for charging is detailed. See Figure 5;

Step 6: After successfully receiving the CATS charging change request message from the UE, the PCN sends an intermediate charging data request message including the information of the UE from step 5 to the offline charging system. The PCN adds an update to the content of the CDR of the UE. Since the value of the CDR provided to assist the third-party AS control service bottleneck is not set in this embodiment, the PCN does not create a CATS-related CDR for the third-party AS.

Example 4

This embodiment provides a procedure and method for using the UE side control sub-application to suspend and transmitting a complete CATS charging message between the UE and the PCN.

The pre-configured information of the operator on the CATSF is: whether to perform CATS control: the value is;

CATS control mode: enumerated type, the value is the UE side control;

The method comprises the following steps:

Step 1: The third-party AS interacts with the CATSF, and requests the CATSF to assist in controlling the messages and responses of certain applications that access the third-party AS. The interactive request message includes at least one of the following information: a third-party AS address, a sub-application identifier, and a sub-application. Congestion status and third-party provider ID.

Step 2: The CATSF formulates or updates the CATS policy according to the pre-configured information and the sub-application congestion status in the interaction request information received from step 1, for example, the congestion degree is high, and the sub-application control action is: suspend.

Step 4: The UE receives the notification message of step 3 and sends a policy acquisition request message to the CATSF. The CATSF returns the updated CATSF policy and the configuration information on the CATSF to the UE. The CATSF policy contains at least one of the following information: a third-party AS address. , sub-application ID, sub-application congestion status, sub-application control action (suspend), and third-party provider ID; configuration information includes: whether to perform CATS control: value is, CATS control mode: enumeration type, the value is UE Side control, whether to assist the third-party AS control service bottleneck CDR: The value is yes.

Step 5: The UE suspends the sub-application flow according to the latest policy acquired in step 4 in combination with the configuration information, and sends a control message for charging on the Sxch charging interface, that is, a CATS charging event or a session-related CATS Accounting Start Request message. The CATS charging event or session related CATS charging start request message contains charging related configuration information and updated CATSF policy information: third party AS address, sub-application identification, sub-application congestion status, sub-application control action (suspend) And third-party provider identification, whether to carry out CATS control: value is, CATS control mode: enumeration type, the value is the UE-side control and whether it is to help the third-party AS control service bottleneck CDR: the value is yes, use The message interaction of the Sxch interface for charging is shown in Figure 5;

Step 6: After successfully receiving the CATS Charging Start Request message from the UE, the PCN sends a charging data request message including the information of the UE from step 5 to the offline charging system. PCN produces separate CDRs for CATS. This embodiment is configured to provide CDRs for assisting third-party AS control service bottlenecks: the value is yes, the PCN generates separate CDRs for the CATS, which can be used to create CDRs for third-party ASs, record CATS-related traffic, timestamps, and sub-application identifiers. Sub-application control Make information such as billing for third-party AS.

Example 5

The present invention provides a CATS charging device. FIG. 6 is a structural block diagram of a CATS charging device according to Embodiment 5 of the present invention. As shown in FIG. 6, the device 50 includes the following components:

The generating module 51 is configured to: when the third party application server AS service bottleneck controls the application, the policy function entity CATSF receives the interaction request message from the third party AS, and generates a CATSF policy according to the pre-configured information and the request message;

The first sending module 52 is configured to send the CATSF policy and the configuration information to the UE through the CATSF, so that the UE controls the corresponding application flow according to the CATSF policy and the configuration information, and adopts a charging interface with the packet core network PCN. Sxch sends a charging control message to the PCN. The interaction request message includes: an address of the third-party AS, a sub-application identifier, a sub-application congestion status, and a third-party provider identifier.

The pre-configured information includes: whether the application control CATS, the CATS control mode when the third-party application server AS service bottleneck is performed, and whether the charging data record CDR is provided to assist the third-party AS control service bottleneck; optionally, The foregoing apparatus 50 further includes: an updating module 53 configured to: when the pre-configured information includes a CDR for assisting a third party AS to control a service bottleneck, update the UE after sending the intermediate charging data request message to the offline charging system The content of the CDR, and the CDR of the CATS created for the third-party AS, records the traffic related to the change of the CATS policy, the timestamp, the sub-application identifier, and the sub-application control action information.

The embodiment of the present invention further provides a charging message request sending device. FIG. 7 is a structural block diagram of a charging message request sending device according to an embodiment of the present invention. As shown in FIG. 7, the device 60 includes the following components:

The receiving module 61 is configured to send, by the UE, a request for updating the CATSF policy after receiving the policy update message from the CATSF;

Control module 62, configured to receive a CATSF update policy from the CATSF and The configuration information controls the corresponding application flow;

The second sending module 63 is configured to send the charging control message to the PCN through the charging interface Sxch with the PCN core network when the sub-application control action changes.

Example 6

The embodiment of the present invention further provides a computer readable storage medium, which stores program instructions, and when the program instructions are executed by the processor, can implement a CATS charging method provided by the embodiments of the present invention.

Example 7

The embodiment of the present invention further provides a computer readable storage medium, which stores program instructions, and when the program instructions are executed by the processor, can implement a charging message request sending method provided by an embodiment of the present invention.

The embodiment of the invention provides a new charging architecture, interface and method in the scenario of a third-party AS service bottleneck UE side control application. An interface for charging between the UE and the PCN is proposed: Sxch, the CATS charging related message is exchanged on the Sxch interface, and may be a complete charging message serving the CATS separately, or may be a CATS charging change. Message request and response; at the same time, the interface for billing can be added to expand the existing S2c interface into an S2ch interface, or a new interface Scats serving CATS.

The present invention proposes an AMC (Accounting Metrics Collection) collection module of the CTF deployed in the UE, and an ADF (Accounting Data Forwarding) of the CTF is deployed in the PCN. The charging interface between the PCN and the offline charging gateway is the same as that of the prior art, as shown in FIG. 8.

One of ordinary skill in the art will appreciate that all or a portion of the steps of the above-described embodiments can be implemented using a computer program flow, which can be stored in a computer readable storage medium, such as on a corresponding hardware platform (eg, The system, device, device, device, etc. are executed, and when executed, include one or a combination of the steps of the method embodiments.

Alternatively, all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.

The devices/function modules/functional units in the above embodiments may be implemented by using a general-purpose computing device, which may be concentrated on a single computing device or distributed among multiple computing devices. On the network.

When each device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium. The above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

Industrial applicability

Claims

A CATS charging method includes:

When the third party application server AS service bottleneck, the policy function entity CATSF receives the interaction request message from the third party AS, generates a CATSF policy according to the pre-configured information and the interaction request message;

Sending, by the CATSF, the CATSF policy and the configuration information to the terminal UE, so that the UE controls the corresponding application flow according to the CATSF policy and the configuration information, and by using the packet core network PCN The charging interface Sxch sends a charging control message to the PCN.
The method of claim 1 wherein said interaction request message comprises:

The address of the third-party AS, the sub-application identifier, the sub-application congestion status, and the third-party provider identifier.
The method of claim 1 wherein said CATSF policy comprises at least one of the following:

The address of the third-party AS, the sub-application identifier, the sub-application congestion status, the sub-application control action, and the third-party provider identifier.
The method of claim 3 wherein said sub-application control action is one of three actions:

Controls application flow to stop, hang, or resume operation.
The method of claim 1 wherein said pre-configured information comprises:

Whether to control the CATS, CATS control mode, and whether to provide the charging data record CDR to assist the third party AS control service bottleneck when performing the third-party application server AS service bottleneck;

When the pre-configured information includes providing a CDR to assist a third-party AS to control a service bottleneck, the method further includes:

Updating the CDR of the UE after sending the intermediate charging data request message to the offline charging system Content, and creating a CDR of the CATS for the third party AS; wherein the CDR of the CATS records the traffic related to the CATS policy change, the timestamp, the sub-application identifier, and the sub-application control action information.
A method for sending a charging message request includes:

The terminal UE sends a request for acquiring a CATSF policy to the policy function entity CATSF of the third-party application server AS service bottleneck control application;

Controlling the corresponding application flow according to the received CATSF policy and configuration information;

When the sub-application control action changes, a charging control message is sent to the PCN through a charging interface Sxch with the packet core network PCN.
A CATS charging device, comprising: a generating module and a first sending module; wherein

The generating module is configured to: when the third-party application server AS service bottleneck controls the application, the policy function entity CATSF receives the interaction request message from the third-party AS, and generates a CATSF policy according to the pre-configured information and the interaction request message. ;

a first sending module, configured to send the CATSF policy and the configuration information to the UE by using the CATSF, so that the UE controls the corresponding application flow according to the CATSF policy and the configuration information, and passes the packet core network The charging interface Sxch between the PCNs sends a charging control message to the PCN.
The apparatus of claim 7, wherein the interaction request message comprises:

The address of the third-party AS, the sub-application identifier, the sub-application congestion status, and the third-party provider identifier.
The apparatus of claim 7, wherein the CATSF policy comprises at least one of the following:

The address of the third-party AS, the sub-application identifier, the sub-application congestion status, the sub-application control action, and the third-party provider identifier.
The apparatus of claim 9, wherein the sub-application control action is one of the following three actions:

Controls application flow to stop, hang, or resume operation.
The apparatus of claim 7, wherein the pre-configured information comprises:

Whether to control the CATS, CATS control mode, and whether to provide the charging data record CDR to assist the third party AS control service bottleneck when performing the third-party application server AS service bottleneck;

The apparatus further includes: an update module, configured to: when the pre-configured information includes providing a CDR to assist a third-party AS control service bottleneck, update the UE after sending the intermediate charging data request message to the offline charging system The content of the CDR, and the CDR of the CATS created for the third party AS; wherein the CDR of the CATS records the traffic related to the CATS policy change, the time stamp, the sub-application identifier, and the sub-application control action information.
A charging message request sending device includes: a receiving module, a control module and a second sending module; wherein

The receiving module is configured to issue a request for acquiring a CATSF policy by using a policy function entity CATSF of the third party application server AS service bottleneck control application;

The control module is configured to control the corresponding application flow according to the received CATSF policy and configuration information;

The second sending module is configured to send a charging control message to the PCN through a charging interface Sxch with the packet core network PCN when the sub-application control action changes.
A computer readable storage medium storing program instructions that, when executed by a processor, implement the method of any of claims 1-5.
A computer readable storage medium storing program instructions that, when executed by a processor, implement the method of any one of claims 6.