WO2016201999A1

WO2016201999A1 - Third-party application charging method and apparatus, and application function device

Info

Publication number: WO2016201999A1
Application number: PCT/CN2016/073922
Authority: WO
Inventors: 吴锦花; 王刚; 刘小华; 郑兴明; 金海�
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-06-18
Filing date: 2016-02-17
Publication date: 2016-12-22
Also published as: CN106332034A

Abstract

Provided are a third-party application charging method and apparatus, and an application function device. The third-party application charging method comprises: an operator charging control system receiving a user third-party application session request message initiated by an application function device, wherein the session request message includes a third-party application subscription user identifier of a user; and the operator charging control system performing charging management on a third-party application of the user according to the session request message. The solution solves the problem in the prior art that usage amount counting and charging execution cannot be performed according to a third-party subscription user identifier, providing an individual usage amount and charging bill regarding a third-party application for a subscription user of the third-party application, enabling settlement and account checking of the two parties.

Description

Charging method, device and application function device of third party application

The present application claims priority to Chinese Patent Application No. 201510341004.0 filed on Jun. 18, 2015, the entire disclosure of which is hereby incorporated by reference.

Technical field

The present invention relates to a policy and a charging control technology in a wireless communication system, and in particular, to a charging method, a device, and an application function device of a third-party application.

Background technique

The 3rd Generation Partnership Project (EPS) evolved Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (P-GW or PDN GW, Packet Data Network Gateway), Home Subscriber Server (HSS) The 3GPP AAA, Authentication, Authorization and Accounting server, the Policy and Charging Rules Function (PCRF) and other supporting nodes. among them,

The HSS is a permanent storage location for user subscription data, and is located in the home network to which the user subscribes. The MME is the location where the subscriber subscription data is stored in the current network, and is responsible for terminal-to-network non-access stratum signaling management, terminal security verification function, terminal mobility management, user idle mode tracking and paging management functions, and Bearer management. The S-GW is a gateway of the core network to the wireless system, and is responsible for the user plane bearer of the terminal to the core network, the data buffer in the terminal idle mode, the function of initiating a service request by the network side, the lawful interception and the packet data routing and forwarding function; The gateway is responsible for counting the situation in which the user terminal uses the wireless network, and generates a CDR that the terminal uses the wireless network to transmit to the charging gateway. The P-GW is a gateway of the evolved system and the external packet data network of the system. It is connected to the Internet and the packet data network, and is responsible for the Internet Protocol (IP) address allocation, charging function, packet filtering of the terminal. , policy control and other functions. The PDN is the carrier's IP service network, which provides IP services to users through the carrier's core network.

In addition, the policy control and charging control function (PCC, Policy and Charging Control) is embedded in the EPS architecture. The PCC functional entities in the EPS architecture can be distributed as follows: PCRF is a policy and charging rule function entity, and the policy and charging execution function entity The PCEF (Policy and Charging Enforcement Function) exists in the P-GW. The Bearer Binding and Event Report Function (BBERF) can exist in the S-GW. The application function entity (AF, Application Function) exists in the service network protocol (IP, Internet Protocol) service network, SPR (Subscription Profile Repository) Can be combined with HSS.

In 3GPP, the corresponding PDN network can be found through an Access Point Name (APN). A connection from a UE to a PDN network is usually referred to as an IP-Connected Access Network (IP-CAN) session. The PCC is applicable to all 3GPP IP-CANs. The architecture is shown in Figure 1. The PCRF is responsible for the formulation of the policy and accounting rules. The PCC policy and accounting rules are sent to the PCEF through the Gx interface. The PCEF installs and executes the PCC. Policy, and report related events, and exchange billing information with the billing system.

The PCRF sends the QoS (Quality of Service) rules to the BBERF through the Gxx interface. The BBERF does not exchange accounting information with the accounting system. It is only responsible for reporting bearer bindings and related events. The AF provides the service information to the PCRF through the Rx interface, and the SPR stores the service information subscribed by the user. The PCRF can query the SPR for the service information subscribed by the user through the Sp interface. The PCEF sends the online charging information to the online charging system (OSC, Online Charging System) through the Gy interface, and is responsible for online charging statistics. The offline charging information is sent to the offline charging system (OFCS, Offline Charging System) through the Gz interface. .

Currently, in the PCC architecture, the PCRF can dynamically send a PCC policy to the PCEF, and the policy information includes QoS and charging information. The PCRF formulates a PCC policy based on the service-related information provided by the AF, the bearer-related information reported by the PCEF, and the service information subscribed by the user in the SPR.

AF, which is used to provide access points for business applications. The network resources used by these business applications require dynamic policy control. When the parameter negotiation is performed on the service plane, the AF transmits the related service information to the Policy Control and Charging Rules Function (PCRF). If the service information is consistent with the policy of the PCRF, the PCRF accepts the negotiation; otherwise, the PCRF rejects the negotiation and gives the business parameters acceptable to the PCRF upon feedback. The AF can then return these parameters to the user equipment (UE, User Equipment). The interface between the AF and the PCRF is an Rx interface.

The PCRF is the core of the PCC and is responsible for policy decision making and billing rules. The PCRF provides network control rules based on service data flows, including detection of traffic data flows, Gating Control, Quality of Service (QoS) control, and traffic flow based charging rules. The PCRF sends its policy and charging rules to the Policy and Control Enforcement Function (PCEF). At the same time, the PCRF also needs to ensure that these rules are consistent with the user's subscription information. The basis for the PCRF to formulate the policy and the charging rule includes: the service-related information obtained from the AF, and the user policy charging control related to the policy control and charging obtained from the SPR (Subscription Profile Repository). Information, and information about the bearer-related network obtained from the PCEF through the Gx interface.

The PCEF is usually located in the gateway (GW, Gate-Way), and executes the policy and charging rules formulated by the PCRF on the bearer plane. The PCEF detects the service data flow according to the service data flow filter in the rule sent by the PCRF, and then performs the policy and charging rule defined by the PCRF for the service data flow; when the bearer is established, the PCEF performs the rule according to the PCRF. The resource allocation is performed according to the information provided by the AF. At the same time, the PCEF triggers the reporting of the event occurring on the bearer network according to the event subscribed by the PCRF. According to the charging rule sent by the PCRF, the PCEF performs the corresponding service data flow charging operation. Billing can be either online charging or offline charging. If it is For line billing, the PCEF needs to perform credit management together with the Online Charging System (OCS); when offline charging, the relevant billing information is exchanged between the PCEF and the Offline Charging System (OFCS). . The interface between the PCEF and the PCRF is a Gx interface, the interface between the PCEF and the OCS is a Gy interface, and the interface between the PCEF and the OFCS is a Gz interface. The PCEF can also be enhanced with a Traffic Detection Function (TDF). The PCEF can perform application detection and perform policy enforcement (such as gating, redirection, and bandwidth limitation) according to the local configuration or the PCC rules that are sent by the PCRF and include Application Detection and Control (ADC). The PCEF is generally located on the gateway of the network, such as the Packet Data Network Gateway (PDN-GW) of the EPS, the GPRS Gateway Support Node (GGSN) in the General Packet Radio Service (GPRS), and the Internet of the Internet (I). - Packet Data Gateway (PDG) in the WLAN (Interworking WLAN).

The TDF can also be deployed independently. In this case, the TDF and the PCRF are connected to the Sd interface. The TDF can perform application detection and policy execution according to the application detection control rules delivered by the pre-configuration or PCRF. The PCRF provides application detection control rules or activates TDF pre-configuration rules for the TDF, and the policy control execution operations of the independent TDF functions include gating, redirection, and bandwidth limitation. The TDF reports the related events and information of the detected service/flow to the PCRF (for example, reports the start and end of the detected service/flow to the PCRF), and sends a description of the service data flow to the PCRF, and transmits the flow detection from the PCRF. Signaling for service detection and policy rules.

The Bearer Binding and Event Reporting Function (BBERF) is usually located in the Access Network Gateway. For example, when the user equipment accesses the EPS through the E-UTRAN, and the Proxy Mobile Internet Protocol version 6 (PMIPv6) protocol is used between the serving gateway S-GW and the P-GW, the BBERF exists in the S-GW. . When the user equipment accesses through the trusted non-3GPP access network, the BBERF also exists in the trusted non-3GPP access gateway.

The User Contracted Database (SPR) stores user policy charging control subscription information related to policy control and charging. The interface between SPR and PCRF is the Sp interface.

OCS and PCEF jointly complete the control and management of user credit under online charging mode. The OFCS and the PCEF jointly perform the charging operation in the offline charging mode.

The above PCC architecture implements a policy plan for an IP Connectivity Access Network (IP-CAN) session established by the UE to access a Packet Data Network (PDN) through various functional entities. Fee control.

In the prior art, after the UE establishes an IP-CAN session to a certain PDN, the network provides a default subscription resource according to the corresponding authorized QoS. For the IMS (IP Multimedia Subsystem) service, the AF will provide new QoS information to the PCRF, and the PCRF initiates an IP-CAN session modification procedure to provide resource authorization for the service. For a non-IMS service of the third-party service, a third-party application provider and the PCRF deploy a network element for performing application access control on the third-party application (the non-roaming PCC architecture introduced after the AAC is shown in Figure 2). The Rx interface between the access control network element and the third party may communicate using, for example, a SOAP or restful protocol, and the Rx interface between the PCRFs may employ a communication based on the Diameter or xml protocol. Application access control network element (application access Control, AAC) has a protocol converter (PC) function, which enables protocol conversion between a third-party data application provider and PCRF, and completes the transmission of application provider information, service information, QoS requirements, and billing information.

However, the prior art can only solve the policy and charging control performed by the carrier network according to the operator's subscription user identifier after the subscription of the third-party application is accessed. In the existing requirements, the operator network needs to support multiple charging methods, including the tariff settlement method for the operator to represent the third party charging. The user only needs to process and sign the operator's tariff bill. The user's third-party service fee is included in the operator's bill, and no additional third party payment is required. At present, when the operator's billing system charges users, it simply performs credit authorization according to the user's operator logo, as well as billing usage and tariff statistics and execution, and cannot provide separate subscriptions for third-party applications. A detailed list of usage and tariffs for third-party applications for settlement and reconciliation by both parties. Moreover, the operator can perform the usage and tariff settlement according to the contracted user identifier of the third-party application and the third party, thereby ensuring the concealment and security of the user identity of the operator's own contracted user. The current technology cannot perform the usage statistics and accounting execution based on the third-party subscription user ID, and cannot meet the above charging requirements for the third-party application to shield the operator's subscription user identifier.

Summary of the invention

The invention provides a charging method, a device and an application function device for a third-party application, which solves the problem that the usage statistics and charging execution according to the third-party subscription user identifier cannot be performed in the prior art.

According to an aspect of the present invention, a charging method for a third-party application is provided, including:

The operator charging control system receives the user third party application session request message initiated by the application function device, where the session request message includes the third party application subscription user identifier of the user;

The operator charging control system performs charging management on the third-party application of the user according to the session request message.

In an embodiment of the present invention, the receiving, by the carrier charging control system, the application function device to initiate a third-party application session request message includes: the application access control function device in the operator charging control system receives the A third-party application session request message initiated by the application device.

In an embodiment of the present invention, before the operator charging control system performs charging management on the third-party application of the user according to the session request message, the method further includes: the operator charging control system The operator's subscriber subscription identifier and the third-party application subscription subscriber identity are associated;

The operator charging control system performs charging management on the third-party application of the user according to the associated operator subscription user identifier and the third-party application subscription user identifier and the session request message.

In an embodiment of the present invention, the operator charging control system associates the operator subscription user identifier of the user with the third-party application subscription user identifier, including:

After receiving the session request message, the application access control function device obtains the operator subscription user identifier of the corresponding user by using the third-party application subscription user identifier, and obtains the obtained operator subscription user identifier and the The third-party application subscribes to the user identity binding to establish an association;

Or, after receiving the session request message, the application access control function device sends the session request message to a policy and charging rule decision function device in the operator charging control system; the policy And the charging rule decision function device obtains the operator subscription user identifier of the corresponding user by using the subscription user identifier of the third-party application, and binds the obtained operator subscription user identifier to the third-party application subscription user identifier, and establishes Association.

In an embodiment of the present invention, after the application access control function device establishes an association between the operator subscription user identifier and the third-party application subscription user identifier, the method further includes:

The application access control function device sends a session establishment request message to the policy and charging rule decision function device, where the session establishment request message includes the associated operator subscription user identifier and the third party application subscription user. Identification

The policy and charging rule decision function device performs charging management on the third-party application of the user according to the session establishment request message.

In an embodiment of the present invention, the operator charging control system performs charging on the third-party application of the user according to the associated carrier subscription user identifier and the third-party application subscription user identifier and the session request message. Management includes:

The policy and charging rule decision function device in the operator charging control system formulates a charging rule according to the associated carrier subscription user identifier and the third party application subscription user identifier and the session request message, and the charging is performed. The rules are sent to the policy and charging execution function device in the operator charging control system;

The policy and the charging execution function device perform the charging rule, and feed back the charging information to the charging subsystem in the operator charging control system, where the charging information carries the associated operator subscription user identifier and Third party application subscription user ID.

In an embodiment of the present invention, before the policy and charging rule decision function device formulates the charging rule, the method further includes:

The policy and charging rule decision function device initiates a charging session request message to the charging subsystem in the operator charging control system, where the charging session request message carries the associated carrier subscription user identifier and a third party. Apply the contracted user ID;

The policy and charging rule decision function device receives a session response message that is sent by the charging subsystem according to the charging session request message, where the session response message carries service and charging related information.

According to another aspect of the present invention, a charging method for a third-party application is also provided, including:

The application function device receives a third-party application service request sent by the user;

The application function device initiates a session request message of the user's third-party application to the operator's charging control system according to the third-party application service request, where the session request message includes the third-party application subscription user identifier of the user.

According to another aspect of the present invention, a charging apparatus for a third party application is provided, including:

a message receiving module, configured to receive, by the operator's charging control system, a third-party application session request message initiated by the application function device, where the session request message includes a third-party application subscription user identifier of the user;

The billing management module is configured to perform billing management on the third-party application of the user according to the session request message.

In an embodiment of the present invention, the message receiving module is configured to receive, by the application access control function device in the operator charging control system, a user third party application session request message initiated by the application function device.

In an embodiment of the present invention, the method further includes an association establishing module, where the operator charging control system associates the operator subscription user identifier of the user with a third-party application subscription user identifier; The management module is configured to perform charging management on the third-party application of the user according to the associated carrier-signed user identifier, the third-party application subscription user identifier, and the session request message.

In an embodiment of the present invention, the association establishing module includes: an information acquisition submodule, where the information acquisition submodule is used by the application access control function device after receiving the session request message The third-party application subscription user identifier acquires the operator subscription user identifier of the corresponding user; the association establishment sub-module is used by the application access control function device to obtain the operator subscription user identifier and the third-party application subscription user identifier. Bind, establish association;

Or the association establishing module includes: an information sending submodule, configured to send, by the application access control function device, the session request message to the operator charging control system after receiving the session request message The policy and charging rule decision function device; the information obtaining submodule, wherein the policy and charging rule decision function device obtains the operator subscription user identifier of the corresponding user by using the subscription user identifier of the third party application; And establishing a sub-module, where the policy and charging rule decision function device binds the obtained operator subscription user identifier to the third-party application subscription user identifier to establish an association.

According to another aspect of the present invention, an application function device is further provided, including:

a communication module, configured to receive a third-party application service request sent by the user;

The processing module is configured to initiate a session request message of the user's third-party application to the operator's charging control system according to the third-party application service request, where the session request message includes the third-party application subscription user identifier of the user.

According to another aspect of the present invention, there is also provided a non-transitory computer readable storage medium having stored therein instructions that, when executed by a processor of an operator's billing control system, cause the operator to calculate The fee control system implements a charging method for a third party application, and the method includes the following steps:

The operator charging control system receives a user third party application session request message initiated by the application function device, where the session request message includes a third party application subscription user identifier of the user;

According to another aspect of the present invention, there is also provided a non-transitory computer readable storage medium having stored therein instructions that, when executed by a processor of an application function device, cause the application function device to implement a A charging method for a third-party application, the method comprising the following steps:

The application function device receives a third-party application service request sent by a user;

The application function device initiates a user to the operator charging control system according to the third-party application service request. A session request message of the three-party application, where the session request message includes a third-party application subscription user identifier of the user.

The beneficial effects of the invention are:

The charging method, the device, and the application function device of the third-party application provided by the present invention carry the user's number in the session request message of the third-party application initiated by the user to the operator's charging control system. The third party applies the subscription user identifier, and the operator charging control system performs charging management on the third party application of the user according to the session request message. The operator billing control system can perform billing execution and third party tariff settlement according to the third party application subscription user identifier, thereby realizing the separate usage and tariff details of the third party application for the contracted user for the third party application. For settlement and reconciliation by both parties.

DRAWINGS

1 is a schematic diagram of a PCC non-roaming architecture;

2 is a schematic diagram of a PCC non-roaming architecture in which an AAC function is deployed;

3 is a schematic flowchart 1 of a charging method of a third-party application according to Embodiment 1 of the present invention;

4 is a second schematic flowchart of a charging method for a third-party application according to Embodiment 1 of the present invention;

5 is a flowchart of an embodiment of a third-party data application provider's subscription user accessing an operator network to implement an online charging function through a Gy interface according to the first embodiment of the present invention;

FIG. 6 is a flowchart of an embodiment of a third-party data application provider's subscription user accessing an operator network to implement an offline charging function through a Gz interface according to Embodiment 1 of the present invention;

FIG. 7 is a flowchart of a method for implementing an online charging function by using a Sy interface by a subscriber of a third-party data application provider according to the first embodiment of the present invention;

8 is a schematic flowchart of a charging method of a third-party application according to Embodiment 2 of the present invention;

FIG. 9 is a schematic structural diagram of a charging apparatus of a third-party application according to Embodiment 3 of the present invention.

detailed description

The present invention will be further described in detail below with reference to the accompanying drawings.

Embodiment 1:

Referring to FIG. 3, the charging method of the third-party application provided in this embodiment includes:

S301: The operator charging control system receives a third-party application session request message initiated by the application function device, where the session request message includes a third-party application subscription user identifier of the user.

S302: The operator charging control system performs charging management on the third-party application of the user according to the session request message.

It should be understood that the third-party application includes: a non-operator application such as WeChat, QQ, Taobao, etc.; the third-party application subscription user identifier may be saved in the form of a mapping list; the third-party application subscription user identifier includes: Service information such as user ID, UE IP, and service data flow description of the third-party application; if necessary, if the third party The subscribed users of the application have different user levels. Different user levels have differentiated QoS and charging subscriptions, and the session request message also carries the user level information, as well as QoS and charging information. The billing management system of the operator performs charging management on the third-party application of the user, including charging and real-time monitoring the third-party application; and the operator charging control system includes two charging methods: online Billing method or offline billing method.

In step S301, the operator charging control system receives the user third party application session request message initiated by the application function device, where the application access control function device in the operator charging control system receives the first initiated by the application function device. The third party applies the session request message; in this embodiment, the communication protocol between the application function device and the application access control function device is not limited; for example, the SOAP or restful protocol may be included. If the roaming is performed, the carrier network where the application access control function device is located is not limited to the home network or the visited network of the UE, and may be a third-party carrier network other than the two. In this embodiment, the third-party application subscription user identifier is carried in the session request message, so that the operator charging control system performs charging for the corresponding third-party application when performing charging, and obtains the bill of the third-party application. Convenient user and third party reconciliation settlement operations.

Preferably, the embodiment further provides a charging method for another third-party application, as shown in FIG. 4, including:

S401: The operator charging control system receives a user third-party application session request message initiated by the application function device, where the session request message includes a third-party application subscription user identifier of the user;

S402: The operator charging control system associates the operator subscription user identifier of the user with the third-party application subscription user identifier.

S403: The operator charging control system performs charging management on the third-party application of the user according to the associated operator subscription user identifier and the third-party application subscription user identifier and the session request message.

In this embodiment, the third-party application subscription user identifier is associated with the operator user identifier of the corresponding user, so that the operator charging control system calculates the corresponding third-party application and the corresponding list of the operator user when performing charging. The fee, the bill of the third-party application and the corresponding operator user, further optimizes the reconciliation settlement of the user and the third party.

In step S402, the operator charging control system associates the operator subscription user identifier of the user with the third-party application subscription user identifier, and the application access control function device uses the conference after receiving the session request message. The third-party application subscription user identifier is used to obtain the operator subscription user identifier of the corresponding user, and the obtained operator subscription user identifier is bound to the third-party application subscription user identifier to establish an association; specifically: the application access control device is configured according to The third-party application subscription user identifier determines whether there is an operator subscription information corresponding to the user, and if not, sends a subscription information request to the SPR, and carries the third-party application subscription user identifier and the PDN identifier in the subscription information request; the SPR stores the reception After the third-party application has a valid subscription user identifier and a list of the user's PDN identifier, the identifier of the user is associated with the other identifier of the same user, for example, by the third-party application subscription user identifier (for example, the user ID of the application layer). Corresponding user's operator subscription user ID (eg IMSI or MSISDN), and the associated operator subscription user identifier is fed back to the application access control device; the application access control device locally stores the returned user identifier list (mapping), and performs third-party subscription user identification and operation according to the returned information. The binding of the merchant subscription identifier, and the associated third party subscription user identifier to the operator subscription subscriber identifier.

Further, after the application access control function device establishes an association between the operator subscription user identifier and the third-party application subscription user identifier, the method further includes: the application access control function device to the policy and charging rule decision function device Sending a session establishment request message, where the session establishment request message includes the associated operator subscription user identifier and the third party application subscription user identifier; and the policy and charging rule decision function device according to the session establishment request message Performing billing management on the third-party application of the user;

Or in step S402, after receiving the session request message, the application access control function device sends the session request message to the policy and charging rule decision function device in the operator charging control system. The policy and charging rule decision function device obtains the operator subscription user identifier of the corresponding user by using the subscription user identifier of the third party application, and obtains the obtained operator subscription user identifier and the third party application subscription user identifier. Bind to establish an association. Similarly, when the policy and charging rule decision function device does not have the operator subscription information of the corresponding user, the device needs to obtain the operator subscription user identifier of the corresponding user in the same manner, and then performs the first according to the returned information. The binding of the three-party subscription user identifier and the operator subscription identifier, and the third-party subscription user identifier to the operator subscription user identifier;

In step S403, the operator charging control system performs charging management on the third-party application of the user according to the associated carrier-signed user identifier and the third-party application subscription user identifier and the session request message, including: the operator The policy and charging rule decision function device in the fee control system formulates a charging rule according to the associated carrier subscription user identifier and the third party application subscription user identifier and the session request message, and sends the charging rule to the operator. a policy and charging execution function device in the charging control system; the policy and charging execution function device executes the charging rule, and feeds back charging information to a charging subsystem in the operator charging control system, The charging information carries the associated carrier subscription user identifier and the third-party application subscription user identifier. Specifically, in the online charging mode, the policy and charging execution function device executes the charging rule, and initiates a credit limit request to the online charging subsystem in the operator charging control system, where the credit is The quota request carries the associated carrier subscription user identifier and the third party application subscription user identifier; the online charging subsystem provides credit authorization information to the policy and charging execution device according to the credit quota request and the subscription user identifier; In the offline charging mode, the policy and charging execution function device executes the charging rule, and directly sends an offline charging report to the offline charging subsystem, where the associated charging carrier is carried in the offline charging report. The subscription user ID and the third-party application subscription user ID.

In another embodiment, before the policy and charging rule decision function device formulates the charging rule, the policy and charging rule decision function device initiates a metering to the charging subsystem in the operator charging control system. a fee session request message, where the charging session request message carries an associated carrier subscription user identifier and a third party application subscription user identifier; the policy and charging rule decision function device receives the charging subsystem according to the A session response message fed back by the charging session request message, where the session response message carries service and charging related information. This embodiment is generally implemented in online charging.

The following is a description of the solution in the specific implementation manner. FIG. 5 is a flowchart of an embodiment of the online charging function implemented by the subscriber of the third-party data application provider of the third-party data application provider through the Gy interface, as shown in FIG. The three-party AF (application function device) sends a session request message to the AAC (Application Access Control Function Device), and the message carries Binding the user ID in the third-party application with the user; AAC or PCRF (decision function device of the policy and charging rule) performs the binding of the third-party subscription user identifier and the operator subscription identifier (associating the third-party subscription user identifier to the operator subscription user) The message sent by the AAC to the PCRF carries the third-party application subscription user identifier, and the PCRF policy decision delivery rule is used to install and execute the PCEF (policy and charging execution function device), and the message carries the third-party application subscription user identifier. The rule charging method is online charging, and the PCEF sends a credit control request message to the OCS (Online Charging Subsystem) to request a credit authorization, where the message carries the operator's subscription user identifier and the user's third party subscription user identifier, and the OCS saves The user identifier signed by the user at the third party performs credit control for the user service according to the received credit control request message. Specifically, the following steps are included:

S501, in the process of the UE requesting to establish an IP-CAN session, the gateway where the PCEF is located receives the IP-CAN session establishment request message, where the IP-CAN session establishment request message carries the user identifier and the PDN requested to be accessed. The PDN identifier of the network;

S502. The PCEF sends an IP-CAN session establishment indication message to the PCRF, where the IP-CAN session establishment indication message carries a user identifier, a PDN identifier, and an IP address allocated for the UE.

S503, the PCRF sends a subscription document request to the SPR after determining that the operator has not signed the operator subscription information, and carries the user identifier and the PDN identifier in the subscription document request.

S504: The SPR returns corresponding user subscription information according to the user identifier and the PDN identifier (returned by the subscription document response);

S505. The PCRF makes a policy decision according to the returned user subscription information, the network policy, and the access information of the UE. Among them, may include the formulation of PCC rules;

S506. The PCRF sends an IP-CAN session establishment confirmation message to the PCEF, where the IP-CAN session establishment confirmation message carries the PCC rule.

S507, the PCEF installation policy, the gateway where the PCEF is located returns an IP-CAN session establishment response to the UE, where the IP-CAN session establishment response carries an IP address;

S508. If the online charging is performed, the PCEF sends a CCR (Credit Control Request) message to the OCS, activates the online charging session, provides corresponding input information to the OCS for decision, and the PCEF carries the charging policy or the charging policy. And the service ID to the OCS to request credit information;

S509, the OCS determines whether to provide credit authorization information to the PCEF according to the request message and the subscription information, and returns the information to the PCEF in a CCA (Credit Control Answer) message;

S510: The UE connects to the AF of the third-party data application provider and requests a service, and the AF sends an AF session request to the AAC, and triggers establishing an AF session with the PCRF. The request message carries the service information such as the user ID, the UE IP, and the service data flow description of the third-party application subscription;

Optionally, if the subscribers of the third-party application have different user levels, different user levels have differentiated QoS and charging subscriptions. The request message will also carry the user level information, as well as QoS and charging information; here the agreement between AF and AAC is not limited, including SOAP or restful protocol. If roaming, the carrier network where the AAC is located is not limited to the home network of the UE or the visited network, and may be the third of the two. Party operator network.

S511. After determining, according to the user identifier, the AAC does not have the operator subscription information of the user, and sends a subscription information request to the SPR, and carries the third-party application subscription user identifier (such as an application identifier) and the PDN identifier in the subscription information request.

S512. If S511 is performed, the SPR returns information such as the corresponding operator subscription user identifier according to the third-party application subscription user identifier and the PDN identifier (returned by the subscription information response).

Here, the SPR stores a list of valid subscription user identifiers provided by the third-party application, and a user's carrier subscription identifier. The other identifier of the same user may be identified by one of the identifiers, for example, by the subscriber identifier of the third party application (for example, the user ID of the application layer), and the operator's subscription identifier (for example, IMSI or MSISDN) is obtained.

S513, the AAC sends an AF session establishment request to the (H) PCRF, where the message carries the operator subscription user identifier and the third-party application subscription user identifier, and the corresponding content carried in step S510; optionally, if S511 is performed, the AAC local Storing the returned user identification list (mapping), performing binding of the third party subscription user identifier and the operator subscription identifier according to the returned information, and associating the third party subscription user identifier to the operator subscription user identifier;

S514: If the S511 is not executed, the (H) PCRF needs to perform identity binding, and execute the third-party application subscription user identifier and the operator subscription user according to the locally stored user identification list (map) obtained (stored and stored from the SPR). The binding of the identifier, associated with the third-party application subscription user identifier to the operator subscription user identifier. (H) The PCRF performs policy decision based on the AF session information such as service information, service provider information, and charging information provided by the AAC, the subscription information provided by the SPR, and the IP-CAN session information provided by the PCEF, and determines whether to authorize the service. QoS and generation of PCC rules, generating corresponding rules and corresponding subscription events. If the AF usage threshold is provided or the usage monitoring of the service is signed, the PCEF also needs to send the usage monitoring keyword and the threshold to monitor the usage of the service;

If the (H) PCRF rejects the authorization, the (H) PCRF returns a reject message to the AAC, the AF service fails, and the process ends;

S515, the (H) PCRF provides a PCC rule installation and execution to the PCEF, and the RAR (Re-Authentication Request) message of the PCEF carries the third-party application subscription user identifier and the rule and event subscription generated in step S514, and Possible usage monitoring related information, as described in detail in S514; the third-party subscription user identifier may be included in the rule or carried outside the rule to the PCEF;

S516, the PCEF saves the related information delivered by the S515, and after installing and executing the policy, returns a confirmation message to the PCRF.

S517, the PCEF performs rule matching according to the received rule and event information, and performs modification process processing of the IP-CAN session such as the modification or creation; if the PCRF or the AF subscribes to the rule execution result or the resource allocation result feedback, the PCEF initiates the CCR. The message will report the execution result;

S518, if it is online charging, the PCEF sends a CCR message to the OCS, requests a credit line, provides corresponding input information to the OCS for decision, the PCEF carries the charging policy, or the charging policy and the service ID to the OCS to request the credit information, in the message At the same time, the operator's subscription user ID and the user's subscription user identifier in the third-party application are carried.

S519, the OCS saves the user's subscription user identifier in the third party application, and determines according to the request message and the subscription information. No credit authorization information is provided to the PCEF and returned to the PCEF in the CCA message.

Through the above steps, the process of initiating the online charging of the service access operator network by using the third-party application subscription ID can be completed. The OCS carries the third-party application subscription user identifier in the CDR of the third-party subscription user, and the operator performs the tariff settlement through the third-party application subscription user identifier and the third-party application.

FIG. 6 is a flowchart of an embodiment of a third-party data application provider of a third-party data application provider accessing an operator network to implement an offline charging function through a Gz interface. As shown in FIG. 6, the AF sends a session request message to the AAC, and the message carries the message. The AAC or the PCRF performs the binding of the third-party application subscription user identifier and the operator subscription identifier (associated with the third-party subscription subscriber identifier to the operator subscription subscriber identifier), and the AAC sends the request message to the PCRF. The third-party application subscription user identifier is carried, and the PCRF policy decision delivery rule is executed to the PCEF, and the third-party application subscription user identifier is also carried in the message. The rule charging method is offline charging. The PCEF sends an offline charging report to the OFCS (offline charging device) according to the measurement method (time/traffic/event) and the charging trigger condition. The message carries the operator subscription user identifier and the user. User ID signed at a third party. Specifically, the following steps are included:

S601, in the process of the UE requesting to establish an IP-CAN session, the gateway where the PCEF is located receives the IP-CAN session establishment request message, where the IP-CAN session establishment request message carries the user identifier and the PDN requested to be accessed. The PDN identifier of the network;

S602. The PCEF sends an IP-CAN session establishment indication message to the PCRF, where the IP-CAN session establishment indication message carries a user identifier, a PDN identifier, and an IP address allocated for the UE.

S603, the PCRF sends a subscription document request to the SPR according to the user identifier, and carries the user identifier and the PDN identifier in the subscription document request.

S604. The SPR returns corresponding user subscription information according to the user identifier and the PDN identifier (returned by the contract document response);

S605. The PCRF makes a policy decision according to the returned user subscription information, the network policy, and the access information of the UE. Among them, may include the formulation of PCC rules, etc.;

S606, the PCRF sends an IP-CAN session establishment confirmation message to the PCEF, where the IP-CAN session establishment confirmation message carries a PCC rule or the like;

S607, the PCEF installation policy, the gateway where the PCEF is located returns an IP-CAN session establishment response to the UE, where the IP-CAN session establishment response carries an IP address.

S608. The UE connects to the AF and requests a service, and the AF sends an AF session request to the AAC, and triggers establishing an AF session with the PCRF. The request message carries the service information such as the user ID, the UE IP, and the service data flow description of the third-party application subscription.

Optionally, if the subscribers of the third-party application have different user levels, different user levels have differentiated QoS and charging subscriptions. The user message information, as well as QoS and charging information, are also included in the request message; the protocol between AF and AAC is not limited herein; includes: SOAP or restful protocol. If the roaming is performed, the carrier network where the AAC is located is not limited to the home network or the visited network of the UE, and may be a third-party carrier network other than the two.

S609. After determining, according to the user identifier, the AAC does not have the operator subscription information of the user, and sends a subscription information request to the SPR, and carries the third-party application subscription user identifier (such as an application identifier) and the PDN identifier in the subscription information request.

S610, if S609 is performed, the SPR returns information such as the corresponding operator subscription user identifier according to the third-party subscription user identifier and the PDN identifier (returned by the subscription information response);

Here, the SPR stores a list of valid subscription user identifiers provided by the third-party application, and a subscriber's subscriber subscription identifier. The other identifier of the same user may be identified by one of the identifiers, for example, by the third party application subscription user identifier (eg, the user ID of the application layer) to obtain the operator's subscription identifier (eg, IMSI or MSISDN).

S611, the AAC sends an AF session establishment request to the (H) PCRF, where the message carries the operator-signed user identifier and the third-party application subscription user identifier, and the related content carried by the AF in step S608; optionally, if S609 is performed The AAC locally stores the returned user identifier list (mapping), and performs binding of the third-party application subscription user identifier and the operator subscription user identifier according to the returned information, and associates the third-party application subscription user identifier to the operator subscription user identifier;

S612, if the S609 is not executed, the PCRF needs to perform identity binding, and performs binding of the third-party subscription user identifier and the operator subscription identifier according to the locally stored user identifier list (map) obtained (stored and stored from the SPR). Associate the third-party subscription user ID to the carrier subscription user ID. (H) The PCRF performs policy decision based on the AF session information such as service information, service provider information, and charging information provided by the AAC, the subscription information provided by the SPR, and the IP-CAN session information provided by the PCEF, and determines whether to authorize the service. QoS and generation of PCC rules, generating corresponding rules and corresponding subscription events. If the AF usage threshold is provided or the usage monitoring of the service is contracted, the PCEF also needs to send the usage monitoring keyword and the threshold to monitor the usage of the service; if the (H) PCRF rejects the authorization, then (H) PCRF The AAC returns a reject message, the AF service fails, and the process ends.

S613, the PCRF provides a PCC rule installation and execution to the PCEF, and the RAR message of the PCEF carries the third-party application subscription user identifier and the rule and event subscription generated in S612, and the related usage monitoring related information, as described in detail in step S612; The third-party application subscription user identifier may be included in the rule or carried outside the rule to the PCEF;

S614: The PCEF saves the related information sent by the S613, and after installing and executing the policy, returns a confirmation message to the PCRF.

S615. The PCEF performs rule matching according to the received rule and event information, and performs modification process processing of the IP-CAN session such as the modification or creation. If the PCRF or the AF subscribes to the rule execution result or the resource allocation result feedback, the PCEF initiates the CCR. The message will report the execution result;

S616, the charging method is offline charging. In the service process, the PCEF sends an offline charging report to the OFCS according to the measurement method (time/traffic/event) and the charging trigger condition, where the message carries the operator's subscription user identifier and the user is in the first The user ID of the three parties signing.

Through the above steps, the process of using the third-party application subscription ID to initiate the service access operator network to perform offline charging can be completed. The OFCS carries the third-party application subscription user ID in the CDR of the third-party subscription user, and operates The merchant settles the tariff through the third-party application subscription user ID and the third-party application.

FIG. 7 is a flowchart of an embodiment of a third-party data application provider's subscription user accessing an operator network to implement an online charging function through a Sy interface. As shown in Figure 7, the AF sends a session request message to the AAC, where the message carries the user's identity in the third-party application subscription; the AAC or PCRF performs the binding of the third-party application subscription user identifier and the carrier subscription identifier (associated with the third-party subscription user). The request message sent to the PCRF by the AAC carries the third-party application subscription user identifier. The PCRF sends a charging session request message to the OCS, where the message carries the operator subscription user identifier and the third party application subscription user identifier, and the OCS saves the third party application subscription user identifier that the user subscribes to by the third party, according to the received charging session. The request message returns a response message for decision by the PCRF. The PCRF policy determines and delivers the rules to the PCEF installation and execution, and the message carries the subscription user identifier of the third-party application. The charging method of the rule is online charging, and the PCEF sends a credit control request message (application credit quota) to the OCS, and the OCS performs credit control for the user service according to the received credit control request message. Specifically, the following steps are included:

S701, in the process of the UE requesting to establish an IP-CAN session, the gateway where the PCEF is located receives the IP-CAN session establishment request message, where the IP-CAN session establishment request message carries the user identifier and the PDN requested to be accessed. The PDN identifier of the network.

S702: The PCEF sends an IP-CAN session establishment indication message to the PCRF, where the IP-CAN session establishment indication message carries a user identifier, a PDN identifier, and an IP address allocated for the UE.

S703. After determining, according to the user identifier, the PCRF does not have the subscription information of the user, and sends a subscription document request to the SPR, and carries the user identifier and the PDN identifier in the subscription document request.

S704. The SPR returns corresponding user subscription information according to the user identifier and the PDN identifier (returned by the subscription document response).

S705: If the online charging is performed, the PCRF sends a charging session request message to the OCS, and activates the charging session, where the message carries the operator subscription user identifier. Optionally, if the request message carries the credit quota application, or does not carry the quota application, the steps S710 and S711 are performed to perform the credit quota request.

S706. The OCS returns a charging session response message to the PCRF according to the request message and the subscription information, and carries the service and charging related information. If the quota request is carried in step S705, the response message may carry the corresponding quota.

S707. The PCRF makes a policy decision according to the returned user subscription information, the network policy, and the access information of the UE. Among them, it may include formulating PCC rules and event triggers.

S708. The PCRF sends an IP-CAN session establishment confirmation message to the PCEF, where the IP-CAN session establishment confirmation message carries a PCC rule and an event trigger.

S709, the PCEF installation policy, the gateway where the PCEF is located returns an IP-CAN session establishment response to the UE, where the IP-CAN session establishment response carries an IP address.

S710. If the online charging is performed, the PCEF sends a CCR message to the OCS, activates the online charging session, provides corresponding input information to the OCS for decision, and the PCEF carries the charging policy or the charging policy and the service ID to the OCS to request the credit information. Optionally, the steps S710 and S711 may be combined in steps S705 and S706, performed by the PCRF. Credit quota application.

Step S711, the OCS decides whether to provide credit authorization information to the PCEF according to the request message and the subscription information, and returns the information to the PCEF in the CCA message.

S712. The UE connects to the AF and requests a service, and the AF sends an AF session request to the AAC, and triggers establishing an AF session with the PCRF. The request message carries the service information such as the user ID, the UE IP, and the service data flow description of the third-party application subscription.

Optionally, if the subscribers of the third-party application have different user levels, different user levels have differentiated QoS and charging subscriptions. The user level information, as well as QoS and charging information, are also carried in the request message. The agreement between AF and AAC here is not limited, including SOAP or restful protocols. If the roaming is performed, the carrier network where the AAC is located is not limited to the home network or the visited network of the UE, and may be a third-party carrier network other than the two.

S713. After determining, according to the user identifier, the AAC does not have the operator subscription information of the user, and sends a subscription information request to the SPR, and carries the third-party application subscription user identifier (such as an application identifier) and the PDN identifier in the subscription information request.

S714. If S713 is executed, the SPR returns information such as the corresponding operator subscription user identifier according to the third-party application subscription user identifier and the PDN identifier (returned by the subscription information response).

Here, the SPR stores a list of valid subscription user identifiers provided by the third-party application, and a user's carrier subscription identifier. The other identifier of the same user may be identified by one of the identifiers, for example, by the third party application subscription user identifier (eg, the user ID of the application layer) to obtain the operator's subscription identifier (eg, IMSI or MSISDN).

S715, the AAC sends an AF session establishment request to the (H) PCRF, where the message carries the user identifier signed by the operator and the user identifier signed by the third party application, and the corresponding content carried by the AF in step S712; optionally, if the step is performed S713, the AAC locally stores the returned user identifier list (mapping), and performs binding of the third party subscription user identifier and the operator subscription identifier according to the returned information, and associates the third party subscription user identifier to the operator subscription user identifier;

S716, the PCRF initiates a charging session request message to the OCS, where the message carries the operator subscription user identifier and the third party subscription user identifier. Optionally, the request message carries the credit quota application, or does not carry the quota application, and steps S721 and S722 are performed to perform the credit quota request.

S717: The OCS saves the user identifier that is signed by the user in the third party, and returns a charging session response message to the PCRF according to the request message and the subscription information, and carries the service and charging related information. If the PCRF carries the quota request in step S716, the response message is sent in the response message. May carry the corresponding quota.

S718. If the S713 is not executed, the (H) PCRF needs to perform identity binding, and execute the third-party application subscription user identifier and the operator subscription user according to the locally stored user identification list (map) obtained (stored and stored from the SPR). The binding of the identifier, associated with the third-party application subscription user identifier to the operator subscription user identifier. The PCRF performs policy decision based on the AF session information such as service information, service provider information, and charging information provided by the AAC, the subscription information provided by the SPR, and the IP-CAN session information provided by the PCEF, and determines whether to authorize QoS and generate the service. PCC rules, generating corresponding rules and corresponding subscription events. If the AF usage threshold is provided or the usage monitoring of the service is contracted, the PCEF also needs to send the usage monitoring keyword and the threshold to monitor the usage of the service; if the PCRF rejects the authorization, the (H) PCRF returns the rejection to the AAC. The message, the AF service fails, and the process ends.

S719, the PCRF provides the PCC rule installation and execution to the PCEF, and the RAR message to the PCEF carries the third-party subscription user identifier and the rule and event subscription generated in step S715, and the related usage monitoring related information, which is described in detail in step S715. The three-party application subscription user ID may be included in the rule or carried outside the rule to the PCEF;

S720, the PCEF saves the relevant information sent in step S718, and after installing and executing the policy, returns an acknowledgement message to the PCRF.

S721: The PCEF performs rule matching according to the received rule and event information, and performs a modification process of the IP-CAN session such as the modification or creation. If the PCRF or the AF subscribes to the rule execution result or the resource allocation result feedback, the PCEF initiates the CCR. The message will report the execution result;

S722, if it is online charging, the PCEF sends a CCR message to the OCS, requests a credit line, provides corresponding input information to the OCS for decision, and the PCEF carries the charging policy or the charging policy and the service ID to the OCS to request the credit information. The message carries both the operator's subscription user ID and the user's third-party application subscription user ID.

S723: The OCS saves the third-party application subscription user identifier of the user, and determines whether to provide the credit authorization information to the PCEF according to the request message and the subscription information, and returns the information to the PCEF in the CCA message.

In the foregoing specific embodiments, it should be noted that, in the roaming scenario, the PCRF here is an HPCRF (Home PCRF, Home PCRF). The interaction and interface between the HPCRF and the VPCRF (Visited PCRF) are implemented according to the prior art; for the DRA (Diameter Routing Agent) scenario, that is, the scenario where multiple PCRFs need to perform PCRF selection through the DRA, AAC The AF request is sent to the DRA, and the DRA selects the correct PCRF (eg, the PCRF associated with the IP-CAN session) based on the UE ID/IP and PDN identification. A PCRF selection technique that follows existing DRA routes.

Embodiment 2:

Referring to FIG. 8, the charging method of the third-party application provided in this embodiment includes:

S801: The application function device receives a third-party application service request sent by the user.

S802: The application function device sends a session request message of the third-party application to be started by the user to the operator charging control system according to the third-party application service request, where the session request message includes the third-party application subscription user identifier of the user. .

It should be understood that the third-party application includes: a non-operator application such as WeChat, QQ, Taobao, etc.; the third-party application subscription user identifier may be saved in the form of a mapping list; the third-party application subscription user identifier includes: Service information such as the user ID, UE IP, and service data flow description of the third-party application; if the contracted users of the third-party application have different user levels, and different user levels have differentiated QoS and charging subscriptions, The user request information, as well as QoS and charging information, are also carried in the session request message. The third-party application subscription user identifier is carried in the session request message sent to the operator's charging control system by the application function device, so that the operator charging control system, when performing the accounting management, applies the subscription user identifier to the third-party application. The user's third application performs charging, so that the third-party application subscription user identifier is carried in the CDR of the third-party subscription user, and the operator performs the tariff settlement through the third-party application subscription user identifier and the third-party application.

Embodiment 3:

Referring to FIG. 9, the charging device 90 of the third-party application provided by the embodiment includes: a message receiving module 901 and a charging management module 902; and the message receiving module 901 is configured to receive an application function by the operator charging control system. a third-party application subscription request message that is initiated by the device, where the session request message includes a third-party application subscription user identifier of the user; the charging management module 903 is used by the carrier charging control system according to the session The request message performs charging management on the third-party application of the user. By sending the user's third-party application subscription user ID to the operator's billing control system, the billing list for the specific third-party application can be implemented in the operator billing control system, facilitating the user and the third party to check the bill.

Further, the message receiving module 901 is configured to receive, by the application access control function device in the operator charging control system, a session request message of a third-party application initiated by the application function device to be activated by the user;

Specifically, the charging device 90 of the third-party application further includes: an association establishing module, where the association establishing module is used by the carrier charging control system to sign the operator subscription user identifier of the user and the third-party application. The user ID is associated with the user identifier; the billing management module 902 is configured to use, by the operator billing control system, the associated third party application subscription user identifier and the third party application subscription user identifier and the session request message to the third party of the user. The application performs charging management; the associated carrier identification user identifier and the third-party application subscription user identifier are sent to the operator charging control system, so that the corresponding carrier user and the operator can be implemented in the operator charging control system. Billing lists for specific third-party applications, further facilitating user and third-party reconciliations.

The association establishment module includes: an information acquisition sub-module, where the information acquisition sub-module is configured to obtain, by using the third-party application subscription user identifier, the application access control function device after receiving the session request message a subscriber identity subscriber identifier of the user; an association establishment sub-module, configured to bind the acquired operator subscription subscriber identifier to the third-party application subscription subscriber identity by the application access control function device, to establish an association; or The association establishing module includes: an information sending sub-module, configured to send, by the application access control function device, the session request message to the policy in the operator charging control system after receiving the session request message a billing rule decision function device; the information obtaining sub-module, wherein the policy and charging rule decision function device obtains an operator subscription user identifier of the corresponding user by using the subscription user identifier of the third-party application; Used by the policy and charging rule decision function device to obtain the carrier subscription user label The third-party application and subscriber identity binding, associate.

Embodiment 4:

The application function device provided in this embodiment includes: a communication module and a processing module; the communication module is configured to establish a communication connection with the user, and receive a third-party application service request sent by the user; the processing module is configured to use the third party according to the third party The application service request sends a session request message of the third-party application to be started by the user to the operator's charging control system, where the session request message includes the third-party application subscription user identifier of the user. The third-party application subscription user identifier is carried in the session request message sent to the operator's charging control system by the application function device, so that the operator charging control system performs the accounting for the third-party application when the user performs the charging management. The fee is such that the third party application subscription user identifier is carried in the CDR of the third party subscription user, and the operator performs the tariff settlement through the third party application subscription user identifier and the third party application.

Embodiment 5:

The non-transitory computer readable storage medium provided by this embodiment stores therein instructions for causing the operator billing control system to implement a third party when executed by a processor of the operator billing control system The charging method of the application, the method includes the following steps: the operator charging control system receives a user third party application session request message initiated by the application function device, where the session request message includes a third party application subscription user identifier of the user And the operator charging control system performs charging management on the third-party application of the user according to the session request message.

Example 6:

The non-transitory computer readable storage medium provided by the embodiment, wherein instructions are stored, the instructions, when executed by a processor of the application function device, causing the application function device to implement a charging method of a third-party application, The method includes the following steps: the application function device receives a third-party application service request sent by a user; and the application function device initiates a session of the user third-party application to the operator charging control system according to the third-party application service request. And a request message, where the session request message includes a third-party application subscription user identifier of the user.

The above is only the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in Within the scope of protection of the present invention.

Industrial applicability

The charging method, device and application function device of the third-party application of the present application can be applied to a network structure including an operator charging control system and an application function device, and the user initiated by the application function device to the operator charging control system The session request message of the third-party application to be started carries the third-party application subscription user identifier of the user, and the operator charging control system performs charging management on the third-party application of the user according to the session request message. Make operations The merchant billing control system can perform billing execution and third party tariff settlement according to the third party application subscription user identifier, thereby realizing the separate usage and tariff details of the third party application for the contracted user for the third party application. Both parties settle and reconcile.

Claims

A charging method for a third-party application, including:

The operator charging control system receives the user third party application session request message initiated by the application function device, where the session request message includes the third party application subscription user identifier of the user;

The operator charging control system performs charging management on the third-party application of the user according to the session request message.
The method for charging a third-party application according to claim 1, wherein the receiving, by the carrier charging control system, the application function device to initiate a third-party application session request message comprises: applying the application in the operator charging control system The ingress control function device receives a third party application session request message initiated by the application function device.
The method for charging a third-party application according to claim 2, wherein the operator charging control system further includes: the operation before performing charging management on the third-party application of the user according to the session request message. The merchant charging control system associates the operator subscription user identifier of the user with the third party application subscription user identifier;

The operator charging control system performs charging management on the third-party application of the user according to the associated operator subscription user identifier and the third-party application subscription user identifier and the session request message.
The method for charging a third-party application according to claim 3, wherein the operator charging control system associates the operator subscription user identifier of the user with the third-party application subscription user identifier, including:

After receiving the session request message, the application access control function device obtains the operator subscription user identifier of the corresponding user by using the third-party application subscription user identifier, and obtains the obtained operator subscription user identifier and the The third-party application subscribes to the user identity binding to establish an association;

Or, after receiving the session request message, the application access control function device sends the session request message to a policy and charging rule decision function device in the operator charging control system; the policy And the charging rule decision function device obtains the operator subscription user identifier of the corresponding user by using the third-party application subscription user identifier, and binds the obtained operator subscription user identifier to the third-party application subscription user identifier to establish an association. .
The method for charging a third-party application according to claim 4, wherein after the application access control function device establishes an association between the operator subscription user identifier and the third-party application subscription user identifier, the method further includes:

The application access control function device sends a session establishment request message to the policy and charging rule decision function device, where the session establishment request message includes the associated operator subscription user identifier and the third party application subscription user. Identification

The policy and charging rule decision function device performs charging management on the third-party application of the user according to the session establishment request message.
The charging method of the third party application according to any one of claims 3-5, wherein the operator charging control system is based on the associated operator subscription user identifier and the third party application subscription user identifier and the session request. The charging management of the third-party application of the user by the message includes:

The policy and charging rule decision function device in the operator charging control system formulates a charging rule according to the associated carrier subscription user identifier and the third party application subscription user identifier and the session request message, and the charging is performed. The rules are sent to the policy and charging execution function device in the operator charging control system;

The policy and the charging execution function device perform the charging rule, and feed back the charging information to the charging subsystem in the operator charging control system, where the charging information carries the associated operator subscription user identifier and Third party application subscription user ID.
The method for charging a third-party application according to claim 6, wherein the policy and charging rule decision function device further includes:

The policy and charging rule decision function device initiates a charging session request message to the charging subsystem in the operator charging control system, where the charging session request message carries the associated carrier subscription user identifier and a third party. Apply the contracted user ID;

The policy and charging rule decision function device receives a session response message that is sent by the charging subsystem according to the charging session request message, where the session response message carries service and charging related information.
A charging method for a third-party application, including:

The application function device receives a third-party application service request sent by the user;

The application function device initiates a session request message of the user's third-party application to the operator's charging control system according to the third-party application service request, where the session request message includes the third-party application subscription user identifier of the user.
A charging device for a third-party application, comprising:

The message receiving module is configured to enable the operator charging control system to receive the user third party application session request message initiated by the application function device, where the session request message includes the third party application subscription user identifier of the user;

The billing management module is configured to enable the operator billing control system to perform billing management on the third-party application of the user according to the session request message.
The charging device for a third-party application according to claim 9, wherein the message receiving module is configured to enable an application access control function device in the operator charging control system to receive a user third party initiated by the application function device Application session request message.
The charging device of the third party application according to claim 10, further comprising an association establishing module, setting In order for the operator charging control system to associate the operator subscription user identifier of the user with the third party application subscription user identifier; the charging management module is configured to make the carrier charging control system according to the association The operator subscription identifier and the third-party application subscription user identifier and the session request message perform charging management on the third-party application of the user.
The charging device for a third-party application according to claim 11, wherein the association establishing module comprises: an information acquiring sub-module, wherein the information acquiring sub-module is configured to enable the application access control function device to receive the After the session request message is described, the operator's subscription user identifier of the corresponding user is obtained by using the third-party application subscription user identifier; the association establishment sub-module is set to enable the application access control function device to obtain the operator subscription user identifier. Binding with the third-party application subscription user identifier to establish an association;

Alternatively, the association establishing module includes: an information sending submodule, configured to enable the application access control function device to send the session request message to the operator charging control after receiving the session request message The policy and charging rule decision function device in the system; the information obtaining sub-module is configured to enable the policy and charging rule decision function device to obtain the operator subscription user identifier of the corresponding user by using the third-party application subscription user identifier; The association establishing sub-module is configured to enable the policy and charging rule decision function device to bind the acquired operator subscription user identifier to the third-party application subscription user identifier to establish an association.
An application function device, including:

a communication module, configured to receive a third-party application service request sent by the user;

The processing module is configured to initiate a session request message of the user's third-party application to the operator's charging control system according to the third-party application service request, where the session request message includes the third-party application subscription user identifier of the user.