CN102137368B - Enhanced policy and charge control method and system and PCC (Policy Charge Control) system - Google Patents

Abstract

The invention discloses an enhanced policy and charging control method. A PCC (Policy Charge Control) system is internally provided with a TDEF (Traffic Detection Executing Function) entity. The method comprises the steps: when formulating the PCC rule, a PCRF (Policy and Control Reporting Function) determines whether more than four layers of policy and charging control are carried out on service data streams matched with the PCC rule; when sending the PCC rule to a policy and control executing function (PCEF) entity, the PCRF indicates whether more than four layers of policy and charging control are carried out on the service data streams matched with the PCC rule; if yes, the PCRF sends the rule for carrying out more than four layers of policy and charging control on the service data streams to the TDEF; and the TDEF implements the rule for carrying out more than four layers of policy and charging control on service data streams, and returns an implementation result to the PCRF. The invention discloses an enhanced policy and charging control system and the PCC system. The invention realizes multilevel and multi-latitudinal charging control on service data.

Description

Enhanced policy and charging control method and system, PCC system

technical field

The present invention relates to enhanced policy and charging control (PCC, Policy and Charging Control) technology, in particular to an enhanced policy and charging control method and system, and a PCC system.

Background technique

The PCC system of the 3rd Generation Partnership Project (3GPP, 3rd Generation Partnership Project) is a functional framework that can be applied to multiple access technologies, for example, it can be applied to the Universal Mobile Telecommunications System (UMTS, Universal Mobile Telecommunications System) Terrestrial Radio Access Network (UTRAN, UMTS Terrestrial Radio Access Network), Global System for Mobile Communications (GSM, Global system for Mobile Communication)/GSM Data Enhanced Evolution (EDGE, Enhanced Data rates for Global Evolution) radio access network, intercommunication Wireless Local Area Network (I-WLAN) and Evolved Packet System (EPS, Evolved Packet System), etc.

Figure 1 is a schematic diagram of the Rel-8 PCC non-roaming architecture of the related technology. As shown in Figure 1, the PCC system includes a user subscription database (SPR, Subscription Profile Repository), an application function entity (AF, Application Function), policies and charging rules Functional entity (PCRF, Policy and Charging Rule Function), bearer binding and event reporting functional entity (BBERF, Bearer Binding and Event Reporting Function), policy and control enforcement functional entity (PCEF, Policy and Control Enforcement Function) and charging system, among which, SPR is connected to PCRF through Sp interface, AF is connected to PCRF through Rx interface, BBERF is connected to PCRF through Gxx interface, and PCEF is connected to PCRF through Gx interface; the charging system includes online charging system (OCS, Online Charging System) and offline charging System (OFCS, Offline Charging System), PCEF is connected to OCS through Gy interface, and PCEF is connected to OFCS through Gz interface. The following describes each logical functional entity and its interface function in the PCC system with reference to Figure 1:

AF is used to provide access points for service applications, and the network resources used by these service applications require dynamic policy control. When negotiating parameters on the service plane, the AF transmits relevant service information to the PCRF. If the service information is consistent with the PCRF policy, the PCRF accepts the negotiation; otherwise, the PCRF rejects the negotiation, and gives the PCRF acceptable service parameters in the feedback. Subsequently, the AF can return these parameters to the user equipment (UE, User Equipment). Wherein, the interface between the AF and the PCRF is the Rx interface.

The PCRF is the core of the PCC and is responsible for making policy decisions and charging rules. PCRF provides network control rules based on service data flow. These network controls include service data flow detection, gating control (Gating Control), quality of service (QoS, Quality of Service) control, and data flow-based charging rules. The PCRF sends the policies and charging rules formulated by it to the PCEF for execution. 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 policy and charging rules includes: obtaining service-related information from the AF; obtaining subscription information related to user policy and charging control from the SPR; obtaining information related to the bearer network from the PCEF.

The PCEF is usually located in a gateway (GW, Gate-Way), and executes policies 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 rules sent by the PCRF, and then executes the policies and charging rules formulated by the PCRF on these service data flows. When the bearer is established, the PCEF performs QoS authorization according to the rules sent by the PCRF, and performs gate control according to the execution of the AF. According to the charging rule sent by the PCRF, the PCEF executes the corresponding service data flow charging operation, and the charging can be either online charging or offline charging. If online charging is used, PCEF needs to perform credit management together with OCS. During offline charging, related charging information is exchanged between PCEF and 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. PCEF is generally located on the gateway of the network, such as the GPRS Gateway Support Node (GGSN, Gateway GPRS Support Node) in GPRS and the Packet Data Gateway (PDG, Packet Data Gateway) in I-WLAN.

BBERF is used for bearer binding, verification of uplink bearer binding, and event reporting. When the UE accesses through E-UTRAN, and the mobility management protocol between S-GW and P-GW is a dual-stack mobile IPv6 (DSMIPv6, Moblie IPv6 support for dual stack Hosts and Routers) protocol, BBERF is located S-GW, when the UE accesses through a trusted non-3GPP access system, the BBERF is located at the trusted non-3GPP access gateway, and when the UE accesses through an untrusted non-3GPP access system, the BBERF is located at the evolved packet data gateway ( ePDG, Evolved Packet Data Gateway. At this point, PCEF no longer performs the bearer binding function.

The 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 work together to control and manage user credit in the online charging mode. The OFCS and the PCEF complete the charging operation in the offline charging mode.

The PCC system realizes the policy charging control of the IP Connectivity Access Network (IP-CAN, IP Connectivity Access Network) session established by the UE for accessing a PDN through the above functional entities.

With the current PCC architecture, there are several problems:

(1) The service information is provided by the AF, and the PCRF makes policy decisions based on the information. However, in existing network applications, there is no AF in many scenarios. Session-based services such as IP Multimedia Subsystem (IMS, IMS IPMultimedia Subsystem) can use Initial Session Protocol (SIP, SIPSession Initiation Protocol) signaling to carry out session service layer negotiation (such as codec mode, media type, required bandwidth, etc.), the P-CSCF (that is, the AF in the PCC system) notifies the PCRF of the negotiated service information, and the PCRF performs QoS authorization. However, there are a large number of non-conversational services in the existing network, such as the current application of IP-based voice protocol (VoIP, Voice Over Internet Protocol), Internet Protocol Television (IPTV, IPTV Internet Protocol Television), video on demand (VoD, Video OnDemand), Services such as online games will not perform media negotiation at the application layer, nor will they perform the process of sending service information to the PCRF. For these non-session services, although certain policy authorization can be performed by configuring some static policies on the PCRF, this method greatly limits the advantages of the PCC system.

(2) At present, the filters used to detect IP packets in the PCC rules issued by the PCRF all use quintuples. However, in some scenarios, two different services cannot be distinguished only by using the quintuple, which requires detection of information on layers above four.

Contents of the invention

In view of this, the main purpose of the present invention is to provide an enhanced policy and charging control method and system, as well as a PCC system, which can implement policy and charging control for non-conversational services, especially for business data flow four The information above the layer is detected, which broadens the practical performance of the PCC system.

In order to achieve the above object, technical solution of the present invention is achieved in that way:

A method for enhanced policy and charging control, in which a business detection executive function entity TDEF is set in a policy and charging control PCC system; the method includes:

After the policy and charging rule functional entity PCRF determines that the business data flow of the IP connection access network IP-CAN session is controlled by more than four layers of policy and charging, it formulates business detection rules and/or business execution rules and sends them to the TDEF;

After the PCEF receives the instruction from the PCRF to perform policy and charging control over layer 4 on the service data flow, it sends the detected service data flow to the TDEF according to the instruction;

The TDEF executes the service detection rule on the service data flow, reports the identification information of the detected data service to the PCRF, and/or executes the service execution rule on the detected data service.

Preferably, during the IP-CAN session establishment or IP-CAN session modification initiation process, the PCRF formulates PCC rules according to the user's subscription information;

The method also includes:

When the PCEF determines that the service data flow matching the PCC rule is to be controlled over four layers of policy and charging, the PCEF forwards the service data flow matching the PCC rule to the TDEF; and, the The PCEF forwards to the TDEF the service data flow that does not match any PCC rule but is instructed by the PCRF to perform policy and charging control over layer 4 or above.

Preferably, the process of establishing the IP-CAN session is initiated by the gateway where the bearer binding and event reporting functional entity BBERF resides after receiving the IP-CAN session establishment request message;

The process of modifying the IP-CAN session is initiated when the application function entity AF provides IP-CAN service information, or after TDEF detects a new service, or when BBERF receives a request for a new service quality QoS rule or detects PCRF It is initiated after the subscribed event, or after the TDEF receives a request for a new QoS rule or detects an event subscribed by the PCRF.

Preferably, the method also includes:

In the process of deleting the IP-CAN session, when the PCRF determines that the PCC rules related to the IP-CAN session include the rules of the policy and charging control above layer 4, control the PCEF to delete the IP-CAN session session-related PCC rules, and control the TDEF to delete the service execution rules.

Preferably, the method also includes:

When the subscription data is updated, the PCRF re-determines whether to control the business data flow of the IP-CAN session above four layers of policy and charging, and re-determines the business execution rules and updates them into the TDEF.

Preferably, the TDEF is set in the PCC system, specifically:

The TDEF is respectively connected to the PCRF and the charging system.

A PCC system, including a user subscription database SPR, AF, PCRF, BBERF, PCEF and a charging system, the SPR, the AF, the BBERF and the PCEF are respectively connected to the PCRF, and the PCEF is connected to The charging system; the PCC system further includes a TDEF connected to the PCRF and the charging system respectively; the PCC system is used for the aforementioned enhanced policy and charging control method.

Preferably, the TDEF is connected to the PCRF through an Sx interface.

An enhanced policy and charging control system, including a setting unit, a formulation unit, a determination unit, a first sending unit, a second sending unit, and an execution and return unit, wherein:

A setting unit for setting TDEF in the PCC system;

A formulating unit, used to formulate PCC rules, business detection rules and business execution rules;

A determining unit, configured to determine whether to control the business data flow of the session with the IP-CAN above four layers of policy and charging;

The first sending unit is configured to send the PCC rule to the PCEF and/or indicate whether to control the policy and charging above layer 4 on the service data flow matching the PCC rule;

a second sending unit, configured to send the service detection rule and/or service execution rule to the TDEF;

An executing and returning unit, configured to execute the service detection rule on the service data flow, report the identification information of the detected data service to the PCRF, and/or execute the service execution rule on the detected data service .

Preferably, the formulating unit formulates PCC rules according to the user's subscription information during the establishment of the IP-CAN session or the initiation of the modification of the IP-CAN session;

Correspondingly, when the determination unit further determines that the service data flow of the IP-CAN session is controlled by a policy and charging above layer four, the PCEF forwards the service data flow matching the PCC rule to the The TDEF, and forward the service data flow that does not match any PCC rule but the PCRF indicates to control policies and charging above layer 4 to the TDEF.

Preferably, the process of establishing the IP-CAN session is initiated by the gateway where the bearer binding and event reporting functional entity BBERF resides after receiving the IP-CAN session establishment request message;

The process of modifying the IP-CAN session is initiated when the application function entity AF provides IP-CAN service information, or after TDEF detects a new service, or when BBERF receives a request for a new service quality QoS rule or detects PCRF It is initiated after the subscribed event, or after the TDEF receives a request for a new QoS rule or detects an event subscribed by the PCRF.

Preferably, the system also includes:

The deleting unit is configured to delete the PCC rules related to the IP-CAN session and the service execution rules during the process of deleting the IP-CAN session.

Preferably, when the subscription data is updated, the determination unit re-determines whether to control the business data flow with the IP-CAN session above four layers of policy and charging, and then re-determines the business execution rules, and by The second sending unit sends to TDEF.

In the present invention, a traffic detection function (TDF, Traffic Detection Function) is added in the current PCC system to detect the information of the traffic data flow above the fourth layer, so that the business information provided to the PCRF will be more abundant, which is beneficial to the PCRF to carry out strategies Decision-making, thus realizing multi-level and multi-latitude policy charging control on business data.

Description of drawings

FIG. 1 is a schematic diagram of a Rel-8PCC non-roaming architecture of related technologies;

Fig. 2 is the composition structure schematic diagram of PCC system of the present invention;

FIG. 3 is a flow chart of Embodiment 1 of the enhanced policy and charging control method of the present invention;

FIG. 4 is a flow chart of Embodiment 2 of the enhanced policy and charging control method of the present invention;

FIG. 5 is a flow chart of Embodiment 3 of the enhanced policy and charging control method of the present invention;

FIG. 6 is a flow chart of Embodiment 4 of the enhanced policy and charging control method of the present invention;

FIG. 7 is a flow chart of Embodiment 5 of the enhanced policy and charging control method of the present invention;

FIG. 8 is a flow chart of Embodiment 6 of the enhanced policy and charging control method of the present invention;

FIG. 9 is a flow chart of Embodiment 7 of the enhanced policy and charging control method of the present invention;

FIG. 10 is a schematic diagram of the composition and structure of the enhanced policy and charging control system of the present invention;

FIG. 11 is a schematic diagram of another composition structure of the enhanced policy and charging control system of the present invention.

Detailed ways

The basic idea of the present invention is: in the current PCC system, a Traffic Detection Enforcement Function (TDEF, Traffic Detection Enforcement Function) is set in order to perform gating, QoS policy control, etc. on the filters above the four layers of service data flow, thereby realizing Carry out multi-level and multi-latitude policy charging control on business data.

In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be further described in detail by citing the following embodiments and referring to the accompanying drawings.

Figure 2 is a schematic diagram of the composition structure of the PCC system of the present invention, as shown in Figure 2, the PCC system of the present invention is formed by adding TDEF to the PCC system shown in Figure 1, specifically, TDEF is set between the billing system and the PCRF , the TDEF is connected to the PCRF through the Sx interface. The main functions of TDEF include:

1. Execute service data message detection according to the message detection rules issued by PCRF (rules of policies and charging control above layer 4), and analyze and detect data packets above layer 4;

2. Report the detected business information to PCRF;

3. Gate control and QoS policy execution based on more than four layers of filters;

4. Report to the PCRF a request for modification of bearer layer resources;

5. Report the event subscribed by PCRF.

Based on the PCC system shown in FIG. 2 , the specific implementation manner of the enhanced policy and charging control method of the present invention will be further explained in detail below.

Embodiment one

Fig. 3 is the flow chart of embodiment one of the method embodiment 1 of the policy of the present invention enhancement and billing control, and as shown in Fig. 3, this embodiment describes IP-CAN session establishment process, and specific steps are as follows:

In step S301, the gateway where the BBERF resides receives an IP-CAN session establishment request message, which carries information such as user ID and PDN ID.

In step S302, the BBERF sends a gateway control session establishment request message to the PCRF, and the message carries user identification, PDN identification, and the like. This message is used to request the establishment of a gateway control session.

Step S303, if the PCRF has no subscription information related to the user, the PCRF sends a subscription document request message to the SPR, and the message carries the user ID and PDN ID, etc. If there is user-related subscription information stored in the PCRF, step S305 is directly executed to formulate a corresponding strategy according to the subscription information.

In step S304, the SPR returns the subscription information of the user according to the user ID and the PDN ID, including whether service detection is required and the service to be detected.

In step S305, the PCRF formulates a default policy according to the subscription information returned by the SPR, including PCC rules and corresponding QoS rules. If service detection is required, the PCRF formulates service detection rules according to the services that need to be detected. Business detection rules usually include more than four layers of filters. If the delivered PCC rules need to further implement policy control above layer four, PCRF will also customize corresponding service execution rules. Service detection rules usually include filters above layer four and corresponding QoS information, such as guaranteed rate (GBR , Guaranteed Bit Rate), maximum rate (MBR, Max Bit Rate), usage threshold (Usage Threshold), etc. Optionally, the PCRF may also formulate event triggers.

In step S306, the PCRF returns a gateway control session establishment confirmation message to the BBERF, and the message carries QoS rules, event triggers, and the like. BBERF installs QoS rules and event triggers.

In step S307, the gateway where the BBERF resides sends an IP-CAN session establishment request message to the gateway where the PCEF resides, and the message carries information such as user identification and PDN identification. In the present invention, step S307 and step S302 may be executed simultaneously.

In step S308, the gateway where the PCEF resides allocates an IP address for the IP-CAN session requested by the UE to be established. The PCEF sends an IP-CAN session establishment instruction message to the PCRF, and the message carries user identification, PDN identification, IP Address and other information. This message is used to request the establishment of a Gx session.

In step S309, the PCRF associates the request to establish the gateway control session in step S302 with the Gx session requested in step S308 according to the user identifier and the PDN identifier. The PCRF sends the PCC rules and event triggers formulated in S304 to the PCEF. PCRF will send an indication to PCEF whether the service data flow of the IP-CAN session needs service inspection, and if service inspection is required, PCEF will forward the service data flow that does not match any PCC rule to TDEF. For each PCC rule, PCRF will also send a policy and charging control instruction to PCEF whether it needs to filter more than four layers. The business data flow matching the rule is forwarded to TDEF. If not, the PCEF uses the PCC rule to control the policy and charging of the service data flow and then directly sends it to the PDN network.

Step S310, if at least one PCC rule is successfully activated, the gateway where the PCEF resides returns an IP-CAN session establishment response message to the gateway where the BBERF resides, carrying the IPAddress of the IP-CAN session.

In step S311, the gateway where the BBERF resides returns an IP-CAN session establishment response message, which carries the IP address of the IP-CAN session.

In step S312, the PCRF sends a service detection session establishment request message to the TDEF, and the message carries a service detection rule and/or a service execution rule. The request message is used to establish a service detection session.

In step S313, the TDEF returns a confirmation message to the PCRF after installing the service detection rule and/or the service execution rule.

In the present invention, step S312 can be executed after step S305.

Through the above procedure, the UE establishes an IP-CAN session, and the PCRF associates the gateway control session, the Gx session, and the service detection session for implementing policy control on the IP-CAN session. PCEF will filter service data packets according to the PCC rules issued by PCRF, and implement corresponding policy and charging control. If the service data flow can match the PCC rule, and the PCRF indicates that the service data flow detected by the PCC rule needs to be forwarded to TDEF for further policy and charging control, then the PCEF sends the service data flow to TDEF; if the service data flow can Matches the PCC rule, but the PCRF does not indicate that the service data flow detected by the PCC rule needs to be forwarded to the TDEF for further policy and charging control, then the PCEF will not send the service data to the TDEF, but directly to the PDN network; if The service data flow does not match any PCC rule but the PCRF instructs the PCEF that the service data flow of the IP-CAN session needs to perform service detection, then the PCEF also sends the service data flow to the TDEF for service detection.

Embodiment two

Fig. 4 is a flow chart of Embodiment 2 of the enhanced policy and charging control method of the present invention. As shown in Fig. 4, this embodiment describes the IP-CAN session initiated by the UE after the IP-CAN session is established based on Embodiment 1 In this process, the gateway where the BBERF resides and the gateway where the PCEF resides communicate using the PMIPv6 protocol. Specific steps are as follows:

In step S401, the gateway where the BBERF resides receives an IP-CAN session request message. The message carries the identifier of the IP-CAN session, such as the IP address of the IP-CAN session.

In step S402, the BBERF sends a gateway control session termination request message to the PCRF, and the PCRF identifies the relevant IP-CAN session and deletes the corresponding QoS rule.

In step S403, the PCRF returns a gateway control session termination confirmation message to the BBERF.

Step S404, the gateway where the BBERF resides sends a delete IP-CAN session request message to the gateway where the PCEF resides.

In step S405, the PCEF sends an IP-CAN session termination indication message to the PCRF.

In step S406, the PCRF identifies the relevant IP-CAN session and deletes the corresponding PCC rule.

In step S407, the PCEF deletes the PCC rule related to the IP-CAN session.

Step S408, if the AF associated with the IP-CAN session needs to be notified, the PCRF notifies the AF of the release of the transmission resource. If the AF does not need to be notified, step S410 is directly executed.

In step S409, the AF returns a response message.

In step S410, the PCRF returns an IP-CAN session termination confirmation message.

In step S411, the gateway where the PCEF resides returns a delete IP-CAN session response message to the gateway where the BBERF resides.

In step S412, the gateway where the BBERF resides returns a delete IP-CAN session response message.

In step S413, the PCRF identifies the service detection session related to the IP-CAN session, and sends a service detection session termination request message to the TDEF.

In step S414, the TDEF identifies the relevant service detection rules and service execution rules and then deletes them.

In step S415, the TDEF returns an acknowledgment message to the PCRF.

Step S416, if the SPR previously subscribed to the cancellation notification message, the PCRF sends a subscription cancellation notification request message to the SPR.

In step S417, the SPR returns a response message.

Embodiment three

Fig. 5 is a flow chart of the third embodiment of the method of enhanced policy and charging control in the present invention. As shown in Fig. 5, this embodiment describes the IP-CAN session modification process initiated by the AF. In this process, BBERF resides The gateway where the PCEF resides communicates with the gateway where the PCEF resides using the PMIPv6 protocol. Specific steps are as follows:

Step S501, AF sends application/service information to PCRF.

In step S502, the PCRF returns a confirmation message after saving the application/service information.

In step S503, the PCRF makes policy decisions according to subscription information, access information, service information and network policies. PCRF policies include PCC rules and corresponding QoS rules. If the issued PCC rules need to further implement policies and charging controls above four layers, the PCRF will also customize corresponding business execution rules. Service execution rules include filters for detecting information above four layers and corresponding QoS information, so that TDEF can control policy and charging of service data flow according to filters above four layers. PCC rules include four-layer filters, and PCEF performs policy and charging control on service data flows according to the four-layer filters. PCRF can also formulate an event trigger for event subscription to BBERF, PCEF or TDEF.

In step S504, the PCRF sends a gateway control and QoS rule provision message to the BBERF, carrying QoS rules and event triggers.

Step S505, BBERF installs QoS rules and event triggers. The gateway where BBERF is located will perform corresponding quality control according to the QoS rules, and establish, modify or terminate the bearer.

In step S506, the BBERF returns a confirmation message to the PCRF.

In step S507, the PCRF sends a policy and charging rule provision message to the PCEF, carrying PCC rules and event triggers. For each PCC rule, PCRF will also send policy and charging control instructions to PCEF whether filtering above layer 4 is required. If necessary, PCEF will forward the service data flow matching the PCC rule to TDEF.

Step S508, PCEF installs PCC rules and event triggers. The PCEF will forward the service data flow matching the PCC rule to the TDEF according to the policies and charging control instructions filtered by layers above four.

In step S509, the PCEF returns a confirmation message to the PCRF.

In step S510, PCRF sends a service execution rule providing message to TDEF, providing the service execution rule and event trigger customized in step S503.

Step S511, TDEF installs business execution rules and event triggers.

In step S512, the TDEF returns an acknowledgment message to the PCRF.

Through the above process, BBERF and PCEF realize the filtering, policy and charging control of business data flow at or below the fourth layer, while TDEF realizes the filtering, policy and charging of business data flow above the fourth layer control. Thereby realizing the multi-level control to the business.

Embodiment Four

Fig. 6 is a flow chart of the fourth embodiment of the method of enhanced policy and charging control in the present invention. As shown in Fig. 6, this embodiment describes the IP-CAN initiated by TDEF after detecting a new service according to the service detection rule Session modification process, in this process, the gateway where the BBERF resides and the gateway where the PCEF resides communicate using the PMIPv6 protocol. Specific steps are as follows:

In step S601, the TDEF detects the passing service data flow according to the service detection rules delivered by the PCRF, and detects services that have not been reported to the PCRF before.

In step S602, the TDEF reports the previously detected service to the PCRF. The TDEF can report to the PCRF by reporting the identifier of the corresponding service detection rule or the identifier of the service preconfigured between the PCRF and the TDEF.

In step S603, the PCRF returns a confirmation message to the TDEF after saving the information reported by the TDEF.

In step S604, the PCRF makes a policy decision according to the subscription information, access information, network policy, and service information reported by the TDEF. PCRF policies include PCC rules and corresponding QoS rules. PCC rules include four-layer filters, and PCEF detects service data flows according to the four-layer filters, and performs policy and charging control. If the delivered PCC rules need to further implement policy control above layer 4, the PCRF will also customize the corresponding business execution rules. Business execution rules include more than four layers of filters, so that TDEF can detect service data flow according to more than four layers of filters, and carry out policy and charging control. PCRF can also formulate an event trigger for event subscription to BBERF, PCEF or TDEF.

In step S605, the PCRF sends a gateway control and QoS rule provision message to the BBERF, carrying QoS rules and event triggers.

Step S606, BBERF installs QoS rules and event triggers. The gateway where BBERF is located will perform QoS control based on QoS, and perform bearer establishment, modification or termination.

In step S607, the BBERF returns a confirmation message to the PCRF.

In step S608, the PCRF sends a policy and charging rule provision message to the PCEF, carrying PCC rules and event triggers. For each PCC rule, PCRF will also send a policy control instruction to PCEF whether it needs to filter more than four layers. If necessary, PCEF will forward the service data flow matching the PCC rule to TDEF.

Step S609, PCEF installs PCC rules and event triggers. The PCEF will forward the service data flow matching the PCC rule to the TDEF according to the policy control instruction filtered by layers above four.

In step S610, the PCEF returns an acknowledgment message to the PCRF.

In step S611, the PCRF sends a service execution rule provision message to the TDEF, providing service execution rules and event triggers.

Step S612, TDEF installs business execution rules and event triggers.

In step S613, the TDEF returns an acknowledgment message to the PCRF.

Through the above process, BBERF and PCEF realize the filtering and policy control of business data flow at or below four layers, while TDEF realizes the filtering, policy and charging control of business data flow above four layers. Thereby realizing the multi-level control to the business.

Embodiment five

Fig. 7 is a flow chart of Embodiment 5 of the enhanced policy and charging control method of the present invention. As shown in Fig. 7, this embodiment describes that after BBERF receives a request for a new QoS rule or detects a PCRF subscription event, The initiated IP-CAN session modification process, in this process, the gateway where the BBERF resides and the gateway where the PCEF resides communicate using the PMIPv6 protocol. Specific steps are as follows:

In step S701, BBERF receives a new QoS rule request or detects an event subscribed by PCRF.

In step S702, the BBERF sends a gateway control and QoS rule request message to the PCRF, carrying a resource authorization request or detecting an event subscribed by the PCRF.

In step S703, the PCRF updates the policy according to the information reported by the BBERF. PCRF policies include PCC rules and corresponding QoS rules. If the issued PCC rules need to further implement policies and charging controls above four layers, the PCRF will also customize corresponding business execution rules. PCC rules include four-layer filters, and PCEF performs policy and charging control on service data flows according to the four-layer filters. PCRF may also update business execution rules (previously formulated) or develop business execution rules (previously not formulated). The business execution rules include filters for detecting information above four layers, so that TDEF can implement policy and charging control on service data flow according to the filters above four layers.

In step S704, the PCRF sends a return confirmation message to the BBERF, which carries the QoS rule.

Step S705, BBERF installs QoS rules. The gateway where BBERF is located will perform QoS control according to the QoS rules, and establish, modify or terminate the bearer

In step S706, the PCRF sends a policy and charging rule provision message to the PCEF, carrying PCC rules and event triggers. For each PCC rule, PCRF will also send a policy control instruction to PCEF whether it needs to filter more than four layers. If necessary, PCEF will forward the service data flow matching the PCC rule to TDEF.

Step S707, PCEF installs PCC rules and event triggers. PCEF will forward the service data flow matching the PCC rule to TDEF according to the policy control instructions filtered by layers above four.

In step S708, the PCEF returns a confirmation message to the PCRF.

In step S709, the PCRF sends a service execution rule providing message to the TDEF to provide the service execution rule and event trigger.

Step S710, TDEF installs business execution rules and event triggers.

In step S711, the TDEF returns an acknowledgment message to the PCRF.

Embodiment six

Fig. 8 is a flow chart of Embodiment 6 of the enhanced policy and charging control method of the present invention. As shown in Fig. 8, this embodiment describes that after the TDEF receives a request for a new QoS rule or detects a PCRF subscription event, The initiated IP-CAN session modification process, in this process, the gateway where the BBERF resides and the gateway where the PCEF resides communicate using the PMIPv6 protocol. Specific steps are as follows:

In step S801, the TDEF detects the occurrence of an event subscribed by the PCRF.

In step S802, the TDEF reports an event to the PCRF.

In step S803, the PCRF updates the policy according to the event reported by the TDEF. The modification of this policy will involve the change of bearer layer resources. The PCRF policy updates PCC rules and QoS rules.

In step S804, the PCRF returns a response message to the TDEF.

In step S805, the PCRF sends a gateway control and QoS rule provision message to the BBERF, carrying updated QoS rules.

Step S806, BBERF installs QoS rules. The gateway where BBERF is located will perform QoS control according to the QoS rules, and establish, modify or terminate the bearer.

In step S807, the BBERF returns a confirmation message to the PCRF.

In step S808, the PCRF sends a policy and charging rule provision message to the PCEF, carrying the updated PCC rule.

In step S809, the PCEF installs the updated PCC rules.

In step S810, the PCEF returns an acknowledgment message to the PCRF.

Embodiment seven

Fig. 9 is a flow chart of Embodiment 5 of the enhanced policy and billing control method of the present invention. As shown in Fig. 9, this embodiment describes the IP-CAN session modification process caused by the change of subscription data. In the process, the gateway where BBERF resides and the gateway where PCEF resides communicate using the PMIPv6 protocol. In this embodiment, it is assumed that whether to perform service detection and policy charging control on the user's service data flow above layer 4 is based on the user's subscription. That is, if the user's subscription does not allow service detection above layer 4, the policy charging control of service data flow above layer 4 will not be performed. Specific steps are as follows:

In step S901, the SPR detects that the user's subscription document has changed. This change can be understood as that the user has added service-aware permissions for certain services, or deleted service-aware permissions for certain services, or completely deleted service-aware permissions for all services.

In step S902, the SPR sends a subscription document update message to the PCRF, carrying the updated contract document.

In step S903, the PCRF returns a confirmation message to the SPR.

In step S904, the PCRF makes a policy decision according to the updated signing document. The PCRF update strategy includes one or more of the following:

(a) If the service-aware permission for certain services is added, the PCRF will formulate new service detection rules and initiate the process of modifying the service detection rules.

(b) If the service-aware permission of some services is deleted, and the PCRF has issued the service detection rules for these services, but the PCRF has not formulated the policy execution sessions (including PCC rules and service execution rules) for these services, that is, the If the policy and charging control above layer 4 is not performed, the PCRF will initiate the process of modifying the service detection session and delete the corresponding service detection rules.

(c) If the service-aware permission of certain services is deleted, and the PCRF has issued the service detection rules for these services and the PCRF has issued the policy execution rules (including PCC rules and service execution rules) for these services, it means that the Policy and charging control above layer 4, then PCRF not only initiates the delete service detection session modification process to delete the corresponding service execution rules, but also notifies the PCEF to modify the route orientation (that is, use the PCC rule to control the service data flow directly after policy control) To the PDN network, no need to send to TDEF).

(d) If the service awareness permission of all services is deleted, the PCRF will initiate the termination process of the service detection session and notify the PCEF to modify the routing orientation.

If the PCRF needs to notify the PCEF to modify the routing orientation of certain services, perform steps S905 to S906. If the PCRF needs to initiate the process of modifying the service detection session, execute steps S908 to S910.

Step S905, if the PCRF needs to notify the PCEF to modify the routing orientation of some services, the PCRF sends a policy and charging rule message to the PCEF, cancels the matching of the previously issued service data flow with the PCC rule, and continues the service data flow Instructions forwarded to TDEF.

In step S906, the PCEF executes the policy and cancels the binding relationship between the PCC rule and forwarding to the TDEF.

In step S907, the PCEF returns a confirmation message to the PCRF.

If the PCRF needs to initiate the process of modifying the service detection session, execute steps S908 to S910.

In step S908, the PCRF sends the service detection session modification process to the TDEF, carrying the service detection rules to be added or deleted, and/or carrying the service execution rules to be deleted.

Step S909, the TDEF executes the policy, adds or deletes the service detection rule, and/or deletes the service execution rule.

In step S910, the TDEF returns a confirmation message.

If the PCRF needs to terminate the service detection session, execute steps S911 to S913.

In step S911, the PCRF sends a service detection termination session request message to the TDEF.

In step S912, the TDEF deletes policies related to the service detection session (service detection rules, service execution rules, event triggers, etc.).

In step S913, the TDEF returns a confirmation message.

Fig. 10 is a schematic diagram of the structure of the enhanced policy and charging control system of the present invention. As shown in Fig. 10, the enhanced policy and charging control system of the present invention includes a setting unit 1001, a formulating unit 1002, and a determining unit 1003 , the first sending unit 1004, the second sending unit 1005 and the execution and return unit 1006, wherein:

A setting unit 1001, configured to set TDEF in the PCC system;

A formulation unit 1002, configured to formulate PCC rules, service detection rules and service execution rules;

A determining unit 1003, configured to determine whether to control the policy and charging of layers above four layers on the service data flow of the session with the IP-CAN;

The first sending unit 1004 is configured to send the PCC rule to the PCEF and/or indicate whether to control the policy and charging above layer 4 for the service data flow matching the PCC rule;

The second sending unit 1005 is configured to send the service detection rule and/or service execution rule to the TDEF;

The execution and return unit 1006 is configured to execute the service detection rule on the service data flow, report the identification information of the detected data service to the PCRF, and/or execute the service execution on the detected data service rule.

Wherein, the formulating unit 1002 formulates PCC rules according to the user's subscription information during the initiation of IP-CAN session establishment or IP-CAN session modification;

Correspondingly, when the determination unit 1003 further determines that the service data flow of the IP-CAN session is controlled by policies and charging above layer 4, the PCEF forwards the service data flow matching the PCC rule to the The TDEF, and forwarding to the TDEF the service data flow that does not match any PCC rule but the PCRF indicates that policy and charging control over layer 4 should be performed. The above IP-CAN session establishment process is initiated by the gateway where the bearer binding and event reporting functional entity BBERF resides after receiving the IP-CAN session establishment request message; the above IP-CAN session modification process is provided by the application functional entity AF IP-CAN service information is initiated from time to time, or initiated by TDEF after detecting a new service, or initiated after BBERF receives a request for QoS rules or detects an event subscribed by PCRF, or after TDEF receives a request for a new QoS rule or detection Initiated after the event subscribed by PCRF.

Fig. 11 is another schematic structural diagram of the enhanced policy and charging control system of the present invention. As shown in Fig. 11, on the basis of the enhanced policy and charging control system shown in Fig. 10, the present invention enhances The policy and charging control system further includes a deletion unit 1007, configured to delete the PCC rules related to the IP-CAN session and the service execution rules during the process of deleting the IP-CAN session.

In the enhanced policy and charging control system of the present invention, the formulating unit 1002 formulates PCC rules, and the determining unit 1003 determines whether to implement policies and charging for business data streams matching the PCC rules above layer 4 according to the user's subscription data control.

Correspondingly, when the determining unit 1003 determines to perform policy and charging control over layer 4 or above on the service data flow matching the PCC rule, the PCEF forwards the service data flow matching the PCC rule to the TDEF.

When the subscription data is updated, the determination unit 1003 re-determines whether to control the business data flow with the IP-CAN session above four layers of policy and charging, and then re-determines the business execution rule, and sends it by the second sending unit 1005 to TDEF.

Those skilled in the art should understand that the enhanced policy and charging control system shown in Figure 10 and Figure 11 is designed to implement the aforementioned enhanced policy and charging control method. The functions of each processing unit in the enhanced policy and charging control system can be understood with reference to the description of the methods shown in Figures 3 to 9, and the functions of each processing unit can be realized by programs running on the processor, or by Realized by specific logic circuit.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention.

Claims (13)

1. a kind of enhanced strategy and the method for charging control, in strategy and charging control PCC system, business detection executive function entity TDEF is set; It is characterized in that, described method comprises: After the policy and charging rule functional entity PCRF determines that the business data flow of the IP connection access network IP-CAN session is controlled by more than four layers of policy and charging, it formulates business detection rules and/or business execution rules and sends them to the TDEF; After the policy and control enforcement function entity PCEF receives the instruction from the PCRF to control the policy and charging above layer 4 on the service data flow, it sends the detected service data flow to TDEF according to the instruction; The TDEF executes the service detection rule on the service data flow, reports the detected service information of the service data flow to the PCRF, and/or executes the service execution rule on the service data flow. 2. The method of claim 1, wherein, During the initiation of IP-CAN session establishment or IP-CAN session modification, the PCRF formulates PCC rules according to the subscription information of the user; The method also includes: The PCEF forwards to the TDEF the service data flow that matches the PCC rule and the PCRF indicates that the policy and charging control of more than four layers is performed; and, the PCEF will not match any PCC rule but the PCRF The service data flow indicating service detection is forwarded to the TDEF. 3. method according to claim 2, it is characterized in that, the process that described IP-CAN session is set up is by the gateway that bearer binds and event reporting functional entity BBERF resides after receiving and establishes IP-CAN session request message initiated; The process of modifying the IP-CAN session is initiated when the application function entity AF provides IP-CAN service information, or after TDEF detects a new service, or when BBERF receives a request for a new service quality QoS rule or detects PCRF It is initiated after the subscribed event, or after the TDEF receives a request for a new QoS rule or detects an event subscribed by the PCRF. 4. The method according to claim 2, characterized in that the method further comprises: In the process of deleting the IP-CAN session, the PCRF instructs the PCEF to delete the PCC rules related to the IP-CAN session, and instructs the TDEF to delete the service detection rules and/or service execution rules related to the IP-CAN session . 5. The method according to claim 2, characterized in that the method further comprises: When the subscription data is updated, the PCRF re-determines whether to perform service detection and/or layer-4 or above policy and charging control on the service data flow of the IP-CAN session, and then re-determines service detection rules and/or service execution Rules, and update to TDEF. 6. The method according to any one of claims 1 to 5, wherein the TDEF is set in the PCC system, specifically: The TDEF is connected to the PCRF. 7. A PCC system, comprising a user subscription database SPR, an application functional entity AF, a policy and charging rule functional entity PCRF, a bearer binding and event reporting functional entity BBERF, a policy and control executive functional entity PCEF, and a charging system, the The SPR, the AF, the BBERF, and the PCEF are respectively connected to the PCRF, and the PCEF is connected to the billing system; it is characterized in that the PCC system also includes a business detection execution function entity TDEF, and The PCRF connection; wherein, The SPR is used for storing and policy controlling user policy charging control subscription information related to charging; The BBERF is used for bearer binding, verification of uplink bearer binding, and event reporting; The AF is used to transmit relevant service information to the PCRF when performing parameter negotiation on the service plane; The PCRF is used to determine that the business data flow of the IP connection access network IP-CAN session is controlled by more than four layers of policy and charging, and formulate business detection rules and/or business execution rules and send them to the TDEF; The PCEF is configured to send the detected service data flow to the TDEF according to the instruction after receiving the instruction from the PCRF to perform policy and charging control over layer 4 on the service data flow; The TDEF is configured to execute the service detection rule on the service data flow, report the detected service information of the service data flow to the PCRF, and/or execute the service execution rule on the service data flow. 8. The PCC system according to claim 7, characterized in that, the TDEF and the PCRF are connected through an Sx interface. 9. A system for enhanced policy and charging control, characterized in that it includes a setting unit, a formulating unit, a determining unit, a first sending unit, a second sending unit, and an execution and return unit, wherein: A setting unit for setting TDEF in the PCC system; A formulating unit, used to formulate PCC rules, business detection rules and business execution rules; A determining unit, configured to determine whether to perform service detection and/or control of policies and charging above layer 4 on the service data flow of the session with the IP-CAN; The first sending unit is configured to send the PCC rule to the PCEF and/or indicate whether to perform service detection and/or control of policy and charging above layer 4 on the service data flow; a second sending unit, configured to send the service detection rule and/or service execution rule to the TDEF; The executing and returning unit is configured to execute the service detection rule on the service data flow, report the detected service information to the PCRF, and/or execute the service execution rule on the service data flow. 10. The system according to claim 9, wherein the formulating unit formulates PCC rules according to the user's subscription information during the IP-CAN session establishment or IP-CAN session modification initiation process; Correspondingly, when the determination unit determines to perform service detection on the service data flow of the IP-CAN session, the PCEF forwards the service data flow that does not match any PCC rule but is instructed by the PCRF to perform service detection to the When the TDEF, and/or the determination unit further determines that the business data flow of the IP-CAN session is controlled by more than four layers of policy and charging, the PCEF forwards the business data flow that matches the PCC rule to The TDEF. 11. system according to claim 10, it is characterized in that, the process that described IP-CAN session is set up is by the gateway that bearer binds and event reporting functional entity BBERF resides after receiving and establishes IP-CAN session request message initiated; The process of modifying the IP-CAN session is initiated when the application function entity AF provides IP-CAN service information, or after TDEF detects a new service, or when BBERF receives a request for a new service quality QoS rule or detects PCRF It is initiated after the subscribed event, or after the TDEF receives a request for a new QoS rule or detects an event subscribed by the PCRF. 12. The system according to claim 10, further comprising: The deletion unit is configured to delete the PCC rules related to the IP-CAN session, and the service detection rules and/or service execution rules during the process of deleting the IP-CAN session. 13. The system according to claim 10, characterized in that, when the subscription data is updated, the determination unit re-determines whether to perform service detection and/or four-layer or above strategy on the service data flow of the IP-CAN session and charging control, when the service detection rule and/or service execution rule is re-determined, and sent to the TDEF by the second sending unit.