WO2011091682A1

WO2011091682A1 - Method and system for enhanced policy and charging control, policy and charging control (pcc) system

Info

Publication number: WO2011091682A1
Application number: PCT/CN2010/079118
Authority: WO
Inventors: 周晓云; 刘小华
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-01-26
Filing date: 2010-11-25
Publication date: 2011-08-04
Also published as: CN102137368A; CN102137368B

Abstract

A method for enhanced Policy and Charging Control (PCC) is provided in the present invention, wherein a Traffic Detection Enforcement Function (TDEF) is set in PCC system. The method includes that a Policy and Charging Rule Function (PCRF) determines whether to perform the policy and charging control which is at the layers above the fourth layer on service data flows matching with the PCC rules or not, when it establishes the PCC rules; the PCRF indicates whether to perform the policy and charging control which is at the layers above the fourth layer on service data flows matching with the PCC rules or not, when it sends the PCC rules to a Policy and Charging Enforcement Function (PCEF), and if the PCRF indicates yes, the policy and charging control rules which are at the layers above the fourth layer performing on the service data flows are sent to the TDEF; the TDEF performs the policy and charging control rules which are at the layers above the fourth layer on the service data flows, and then returns the performing results to the PCRF. A system for enhanced policy and charging control, as well as a PCC system, is provided in the present invention. The present invention enables a multi-level, multi-latitude policy and charging control for the service data.

Description

Enhanced policy and charging control methods and systems, policies and charging controls

(PCC) System Technical Field

The present invention relates to enhanced techniques for Policy and Charging Control (PCC), and more particularly to an enhanced method and system for policy and charging control, and a PCC system. Background technique

The PCC system of the 3rd Generation Partnership Project (3GPP) is a functional framework that can be applied to various access technologies, for example, it can be applied to the land of the Universal Mobile Telecommunications System (UMTS). UMTS, UMTS Terrestrial Radio Access Network, Global System for Mobile Communication (GSM), GSM, Enhanced Data Rates for Global Evolution (WLAN) Wireless Local Area Network ), interworking wireless office i or network (I-WLAN) and evolved packet system (EPS, Evolved Packet System).

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

AF is used to provide access points for business applications, and the network resources used by these business applications require dynamic policy control. When the parameters are negotiated on the service plane, the AF passes the related service information to the 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 simultaneously gives the business parameters acceptable to the PCRF in the feedback. The AF can then return these parameters to the user equipment (UE, User Equipment). The interface between AF and PCRF is the 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 traffic data flow detection, Gating Control, Quality of Service (QoS) control, and data flow based charging rules. The PCRF sends its policy and charging rules 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 formulating policies and charging rules by the PCRF includes: obtaining information related to the service from the AF; obtaining subscription information with the user policy charging control from the SPR; and acquiring information about the network related to the bearer from the PCEF.

The PCEF is usually located in the gateway (GW, Gate-Way), and performs the policy and charging rules established 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 executes the policy and charging rules formulated by the PCRF for 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 performs a corresponding service data flow charging operation, and the charging can be either online charging or offline charging. In the case of online charging, the PCEF needs to conduct credit management with the OCS. When offline charging, the relevant charging information is exchanged between the PCEF and the OFCS. The interface between the PCEF and the PCRF is a Gx interface, the interface between the OCE and the OCS is a Gy interface, and the interface between the OFCS and the OFCS is a Gz interface. PCEF They are generally located on the gateway of the network, such as the GPRS Gateway Support Node (GGSN) in GPRS and the Packet Data Gateway (PDG) in I-WLAN.

BBERF is used for bearer binding, authentication of upstream bearer bindings, and event reporting. When the UE accesses through the E-UTRAN, and the mobility management protocol is used between the S-GW and the P-GW to support the dual-stack mobile IPv6 (DSMIPv6, Moblie IPv6 support for dual stack Hosts and Routers) protocol, the BBERF Located at the S-GW, when the UE accesses through the trusted non-3GPP access system, the BBERF is located in the trusted non-3GPP access gateway, and when the UE accesses through the untrusted non-3GPP access system, the BBERF is located in the evolved packet data gateway. ( ePDG, Evolved Packet Data Gateway. At this point, PCEF no longer performs the 7-load 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 are used to control and manage user credit under online charging mode. The OFCS and the PCEF start the charging operation in the offline charging mode.

Through the above functional entities, the PCC system implements policy charging control for the IP-Connected Network (IP-Connected Access Network) session established by the UE to access the PDN.

With the current PCC architecture, there are several issues:

(1) The information of the service is provided by the AF, and the PCRF makes policy decisions based on the information. In the existing network applications, there are no AFs in many scenarios. Session-based services such as the IP Multimedia Subsystem (IMS) can use the SIP (Session Session Protocol) signaling for session layer service negotiation (such as codec mode, media type, and The required bandwidth, etc.), the P-CSCF (ie, the AF in the PCC system) notifies the PCRF of the negotiated service information, and performs QoS authorization by the PCRF. A large number of non-session services in the live network, such as the current application of IP-based voice protocols (VoIP, Voice Over Internet) Protocol ), Internet Protocol Television (IPTV), Video On Demand (VoD), online game services, etc. will not perform media negotiation at the application layer, nor will it perform service information transmission to the PCRF. process. For these non-session services, although some static policies can be configured on the PCRF to perform certain policy authorization, this approach 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 are all quintuples. In some scenarios, the use of a quintuple does not distinguish between two different services. This requires the detection of more than four layers of information. Summary of the invention

In view of this, the main object of the present invention is to provide an enhanced policy and charging control method and system, and a PCC system, which can implement policy and charging control for non-session services, especially for service data flow. The above information is detected and the practical performance of the PCC system is broadened.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

An enhanced policy and charging control method, in which a service detection execution function entity TDEF is set in a policy and charging control PCC system; the method includes:

The policy and charging rule function entity PCRF determines to perform four-layer policy and charging control on the service data flow of the IP-connected network IP-CAN session, and then formulates a service detection rule and/or a service execution rule and sends the same to the TDEF;

After receiving the indication that the PCRF performs four or more layers of policy and charging control on the service data flow, the PCEF sends the detected service data flow to the TDEF according to the indication;

The TDEF performs 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, in the initiation process of IP-CAN session establishment or IP-CAN session modification, The PCRF formulates PCC rules according to the user's subscription information;

The method further includes:

When the PCEF determines to perform four or more layers of policy and charging control on the service data flow that matches the PCC rule, the PCEF forwards the service data flow that matches the PCC rule to the TDEF; The PCEF will not match any PCC rules but the PCRF indicates that the service data flow for controlling more than four layers of policy and charging is forwarded to the TDEF.

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

The process of modifying the IP-CAN session is initiated by the application function entity AF providing the service information of the IP-CAN, or initiated by the TDEF after detecting the new service, or receiving the request for the new quality of service QoS rule or detecting the PCRF at the BBERF. Initiated after the subscribed event, or after the TDEF receives an event requesting a new QoS rule or detecting a PCRF subscription.

Preferably, the method further includes:

During the deletion of the IP-CAN session, the PCRF determines that the PCC rule related to the IP-CAN session includes the rule of the four-layer policy and the charging control, and controls the PCEF to delete the IP-CAN. Session-related PCC rules, and control TDEF to delete the business execution rules.

Preferably, the method further includes:

When the subscription data is updated, the PCRF re-determines whether more than four layers of policy and charging control are performed on the service data flow of the IP-CAN session, and the service execution rule is re-determined and updated into the TDEF.

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

The TDEF is connected to the PCRF and the billing system, respectively.

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

Preferably, the TDEF and the PCRF are connected through an Sx interface.

An enhanced policy and charging control system includes a setting unit, a developing unit, a determining unit, a first sending unit, a second sending unit, and an executing and returning unit, wherein:

Setting unit, configured to set TDEF in the PCC system;

a unit for determining a PCC rule, a service detection rule, and a service execution rule; and a determining unit, configured to determine whether to perform four or more layers of policy and charging control on the service data flow of the IP-CAN session;

a first sending unit, configured to send a PCC rule and/or an indication to the PCEF

The service data flow matched by the PCC rule performs control of more than four layers of policies and charging;

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

An execution and return unit, configured to perform 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 a PCC rule according to the subscription information of the user during the initiation process of the IP-CAN session establishment or the IP-CAN session modification;

Correspondingly, the determining unit further determines, when performing control over four layers of policy and charging on the service data flow of the IP-CAN session, the PCEF forwards the service data flow that matches the PCC rule to the The TDEF, and the service data flow that will not match any PCC rules but that the PCRF indicates to perform more than four layers of policy and charging control, is forwarded to the TDEF.

Preferably, the process of establishing the IP-CAN session is initiated by the gateway hosted by the bearer binding and event reporting function entity BBERF after receiving the establishment of the IP-CAN session request message; The process of modifying the IP-CAN session is initiated by the application function entity AF providing the service information of the IP-CAN, or initiated by the TDEF after detecting the new service, or receiving the request for the new quality of service QoS rule or detecting the PCRF at the BBERF. Initiated after the subscribed event, or after the TDEF receives an event requesting a new QoS rule or detecting a PCRF subscription.

Preferably, the system further comprises:

And a deleting unit, configured to delete a PCC rule related to the IP-CAN session and the service execution rule during deleting the IP-CAN session.

Preferably, when the subscription data is updated, the determining unit re-determines whether to perform four or more layers of policy and charging control on the service data flow of the IP-CAN session, and then re-determines the service execution rule, and The second sending unit sends the TDEF.

In the present invention, a service detection function (TDF, Traffic Detection Function) is added in the current PCC system to detect information of four or more layers of the service data stream, so that the service information provided to the PCRF is richer, which is beneficial to the PCRF policy. Decision making, thus achieving multi-level, multi-latitude policy charging control of business data. DRAWINGS

1 is a schematic diagram of a related art Rel-8 PCC non-roaming architecture;

2 is a schematic structural diagram of a PCC system according to the present invention;

3 is a flowchart of Embodiment 1 of an enhanced policy and charging control method of the present invention; FIG. 4 is a flowchart of Embodiment 2 of an enhanced policy and charging control method of the present invention; FIG. 5 is an enhanced strategy of the present invention; FIG. 6 is a flowchart of Embodiment 4 of the enhanced policy and charging control method of the present invention; FIG. 7 is a flowchart of an enhanced policy and charging control method according to the present invention; FIG. 8 is a flowchart of Embodiment 6 of the enhanced policy and charging control method of the present invention; FIG. 9 is a flowchart of Embodiment 7 of the enhanced policy and charging control method of the present invention; A schematic structural diagram of a system for enhanced policy and charging control of the present invention; FIG. 11 is another schematic structural diagram of a system for enhanced policy and charging control according to the present invention. detailed description

The basic idea of the present invention is to: set a Traffic Detection Enforcement Function (TDEF) in a current PCC system, so as to perform gate control and QoS policy control on a service data stream of four or more layers, thereby implementing Multi-level, multi-latitude policy charging control for business data.

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

2 is a schematic structural diagram of a PCC system according to the present invention. As shown in FIG. 2, the PCC system of the present invention is formed by adding TDEF to the PCC system shown in FIG. 1. Specifically, the TDEF is set between the charging system and the PCRF. The TDEF is connected to the PCRF through the Sx interface. The main features of TDEF include:

1. Perform service data packet detection according to the packet detection rule (four-layer policy and charging control rule) delivered by the PCRF, and perform four-layer analysis and detection on the data packet;

2. Reporting the detected service information to the PCRF;

3. Gating and QoS policy execution based on four or more filters;

4. Reporting to the PCRF a request for modifying the bearer layer resources;

5. Report the event of the PCRF subscription.

The specific implementation of the enhanced policy and charging control method of the present invention is further elaborated below based on the PCC system shown in FIG.

Embodiment 1

FIG. 3 is a flowchart of Embodiment 1 of an enhanced policy and charging control method of the present invention. As shown in FIG. 3, this embodiment describes an IP-CAN session establishment process, and the specific steps are as follows:

Step S301, the gateway where the BBERF resides receives the establishment of an IP-CAN session request message, and the message The user carries the identifier of the user, the PDN identifier, and the like.

Step S302: The BBERF sends a gateway control session establishment request message to the PCRF, where the message carries the user identifier, the PDN identifier, and the like. This message is used to request the establishment of a gateway control session.

Step S303: If the PCRF does not have the user-related subscription information, the PCRF sends a subscription document request message to the SPR, where the message carries the user identifier and the PDN identifier. If the user-related subscription information is stored in the PCRF, step S305 is directly executed, and a corresponding policy is formulated according to the subscription information.

Step S304: The SPR returns the subscription information of the user according to the user identifier and the PDN identifier, where the service includes the service detection and the service that needs to be detected.

Step S305: The PCRF formulates a default policy according to the subscription information returned by the SPR, including a PCC rule and a corresponding QoS rule. If service detection is required, the PCRF formulates service detection rules based on the services to be detected. Service detection rules usually include more than four layers of filters. If the issued PCC rules need to further implement policy control of more than four layers, the PCRF also formulates corresponding service execution rules. The service detection rules usually include four or more layers of filters and corresponding QoS information, such as the guaranteed rate (GBR). , Guaranteed Bit Rate ), Maximum Rate (MBR), Usage Threshold, etc. Optionally, the PCRF also creates an event trigger.

Step S306, the PCRF returns a gateway control session establishment confirmation message to the BBERF, where the message carries a QoS rule, an event trigger, and the like. BBERF installs QoS rules and event triggers.

Step S307: The gateway where the BBERF resides sends an IP-CAN session request message to the gateway where the PCEF resides, and the message carries information such as a user identifier and a PDN identifier. In the present invention, step S307 can be performed simultaneously with step S302.

Step S308, the gateway where the PCEF resides allocates an IP address for the IP-CAN session requested by the UE. The PCEF sends an IP-CAN session establishment indication message to the PCRF, where the message carries information such as a user identifier, a PDN identifier, and an IP Address. This message is used to request to establish a Gx session. Step S309, the PCRF associates the request to establish a gateway control session with the Gx session requested by the step S308 according to the user identifier and the PDN identifier. The PCRF sends the PCC rule and event trigger defined by S304 to the PCEF. The PCRF will send an indication to the PCEF whether the service data flow of the IP-CAN session needs to be checked for service. If service detection is required, the PCEF will forward the service data flow that does not match any PCC rule to the TDEF. For each PCC rule, the PCRF sends a policy and charging control indication to the PCEF whether it needs to perform four or more layers of filtering. If the policy and charging control of the data flow is required to be more than four layers, the PCEF will be associated with the PCC. The rule-matched service data stream is forwarded to the TDEF. If not required, the PCEF performs policy charging control on the service data flow by using the PCC rule, and then directly sends the data 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 response message to the gateway where the BBERF resides, carrying the IP Address of the IP-CAN session.

Step S311: The gateway where the BBERF resides returns an IP-CAN session response message, and carries the IP address of the IP-CAN session.

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

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 process, the UE establishes an IP-CAN session, and the PCRF associates the gateway control session, the Gx session, and the service detection session that implement policy control on the IP-CAN session. The PCEF will filter the service data packets according to the PCC rules delivered by the PCRF, and perform 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 the TDEF for further policy charging control Then, the PCEF sends the service data stream to the TDEF; if the service data stream can match 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 charging control, then the PCEF The service data will not be sent to the TDEF, but will be sent directly to the PDN network. If the service data stream does not match any PCC rules but the PCRF indicates that the PCEF service data flow of the IP-CAN session needs to be detected, the PCEF will also The service data stream is sent to the TDEF for service detection.

Embodiment 2

4 is a flowchart of Embodiment 2 of an enhanced policy and charging control method of the present invention. As shown in FIG. 4, this embodiment describes an IP-CAN session initiated by a UE after establishing an IP-CAN session according to Embodiment 1. The termination process in which the gateway hosted by the BBERF communicates with the gateway where the PCEF resides using the PMIPv6 protocol. Specific steps are as follows:

Step S401: The gateway where the BBERF resides receives the delete 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.

Step S402: The BBERF sends a gateway control session termination request message to the PCRF, and the PCRF identifies the related IP-CAN session and deletes the corresponding QoS rule.

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.

Step S405: The PCEF sends an IP-CAN session termination indication message to the PCRF.

Step S406, the PCRF identifies the relevant IP-CAN session and deletes the corresponding PCC rule. 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 transmission resource release. If it is not necessary to notify the AF, step S410 is directly executed.

Step S409, the AF returns a response message.

Step S410, the PCRF returns an IP-CAN session termination confirmation message. Step S411, the gateway where the PCEF resides returns a delete IP-CAN session response message to the gateway where the BBERF resides.

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

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

Step S414: The TDEF deletes the relevant service detection rule and the service execution rule.

Step S415, the TDEF returns an acknowledgement message to the PCRF.

Step S416: If the SPR subscribes to the cancel notification message before, the PCRF sends a cancel subscription notification request message to the SPR.

Step S417, the SPR returns a response message.

Embodiment 3

5 is a flowchart of Embodiment 3 of an enhanced policy and charging control method of the present invention. As shown in FIG. 5, this embodiment describes an IP-CAN session modification process initiated by AF, in which BBERF station The reserved gateway communicates with the gateway where the PCEF resides using the PMIPv6 protocol. Specific steps are as follows:

Step S501: The AF sends application/service information to the PCRF.

Step S502: After saving the application/service information, the PCRF returns an acknowledgement message.

Step S503: The PCRF performs policy decision according to the subscription information, the access information, the service information, and the network policy. The PCRF policy includes PCC rules and corresponding QoS rules. If the issued PCC rules need to further implement more than four layers of policy and charging control, the PCRF will also formulate corresponding service execution rules. The service execution rule includes a filter for detecting information of four or more layers and corresponding QoS information, so that the TDEF can perform policy and charging control on the service data flow according to the four or more filters. The PCC rule includes a four-layer filter, and the PCEF performs policy and charging control on the service data flow according to the four-layer filter. The PCRF can also formulate event triggers for BBERF, PCEF or TDEF for event subscription.

Step S504, the PCRF sends a gateway control and QoS rule providing message to the BBERF, carries the QoS rule, and an event trigger.

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

Step S506: The BBERF returns an acknowledgement message to the PCRF.

Step S507: The PCRF sends a policy and charging rule providing message to the PCEF, and carries the PCC rule and the event trigger. For each PCC rule, the PCRF also sends a policy and charging control indication to the PCEF whether more than four layers of filtering are required. If necessary, the PCEF forwards the service data flow matching the PCC rule to the TDEF.

Step S508, the PCEF installs a PCC rule and an event trigger. The PCEF will forward the traffic data matching the PCC rule to the TDEF according to the policy and charging control indication filtered by the four layers.

Step S509, the PCEF returns an acknowledgement message to the PCRF.

Step S510: The PCRF sends a service execution rule providing message to the TDEF, and provides a service execution rule and an event trigger defined in step S503.

Step S511, the TDEF installs a service execution rule and an event trigger.

Step S512, the TDEF returns an acknowledgement message to the PCRF.

Through the above process, BBERF and PCEF implement filtering, policy and charging control for service data flows of four or less layers, and TDEF implements filtering, policy and accounting for service data flows of four or more layers. control. Thereby achieving multi-level control of the business.

Embodiment 4

6 is a flowchart of Embodiment 4 of the enhanced policy and charging control method of the present invention. As shown in FIG. 6, this embodiment describes an IP-CAN initiated by the TDEF after detecting a new service according to the service detection rule. Session modification process, in which BBERF resides with gateway and PCEF station The remaining gateways communicate using the PMIPv6 protocol. Specific steps are as follows:

Step S601: The TDEF detects the service data flow flowing according to the service detection rule delivered by the PCRF, and detects the service that has not been reported to the PCRF before.

Step S602: The TDEF reports the detected service that was not previously detected to the PCRF. The TDEF can implement the report to the PCRF through the identifier of the service detection rule corresponding to the uplink or the identifier of the service preconfigured between the PCRF and the TDEF.

Step S603: After the PCRF saves the information on the TDEF, the PCRF returns an acknowledgement message to the TDEF. Step S604: The PCRF performs policy decision according to the subscription information, the access information, the network policy, and the service information reported by the TDEF. The PCRF policy includes PCC rules and corresponding QoS rules. The PCC rule includes a four-layer filter. The PCEF detects the service data flow according to the four-layer filter, and performs policy and charging control. If the issued PCC rules need to further implement policy control above four layers, the PCRF will also formulate corresponding service execution rules. The service execution rules include more than four layers of filters, so that TDEF can detect service data flows based on more than four layers of filters, and perform policy and charging control. The PCRF can also create event triggers for event subscriptions to BBERF, PCEF or TDEF.

Step S605: The PCRF sends a gateway control and QoS rule providing message to the BBERF, carries the QoS rule, and an event trigger.

Step S606, the BBERF installs QoS rules and event triggers. The gateway where the BBERF is located performs QoS control according to the QoS, and performs the establishment, modification, or termination of the bearer.

Step S607: The BBERF returns an acknowledgement message to the PCRF.

Step S608: The PCRF sends a policy and charging rule providing message to the PCEF, and carries the PCC rule and the event trigger. For each PCC rule, the PCRF also sends a policy control indication to the PCEF whether it needs to perform more than four layers of filtering. If necessary, the PCEF forwards the service data stream matching the PCC rule to the TDEF.

In step S609, the PCEF installs a PCC rule and an event trigger. PCEF will be based on four layers The upper filtered policy control indicates that the service data flow matching the PCC rule is forwarded to the TDEF. Step S610, the PCEF returns an acknowledgement message to the PCRF.

Step S611: The PCRF sends a service execution rule providing message to the TDEF, and provides a service execution rule and an event trigger.

Step S612, the TDEF installs a service execution rule and an event trigger.

Step S613, the TDEF returns an acknowledgement message to the PCRF.

Through the above process, BBERF and PCEF implement filtering and policy control of service data flow of four or less layers of services, and TDEF implements filtering, policy and charging control of service data flows of four or more layers. Thereby achieving multi-level control of the business.

Embodiment 5

7 is a flowchart 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 receiving an event requesting a new QoS rule or detecting a PCRF subscription by the BBERF, The initiated IP-CAN session modification process, in which the gateway hosted by the BBERF communicates with the gateway where the PCEF resides, using the PMIPv6 protocol. The specific steps are as follows: Step S701: The BBERF receives a new QoS rule request or detects a PCRF subscription event.

Step S702: The BBERF sends a gateway control and QoS rule request message to the PCRF, and carries a resource authorization request or detects an event of the PCRF subscription.

Step S703, the PCRF updates the policy according to the information reported by the BBERF. The PCRF policy includes PCC rules and corresponding QoS rules. If the issued PCC rules need to further implement the policy and charging control of more than four layers, the PCRF will also formulate corresponding service execution rules. The PCC rule includes a four-layer filter, and the PCEF performs policy and charging control on the service data flow according to the four-layer filter. The PCRF may also update business execution rules (previously developed) or develop business execution rules (not previously developed). The service execution rule includes a filter for detecting more than four layers of information, so that the TDEF can perform policy and charging control on the service data flow according to the four or more filters. Step S704, the PCRF sends a return confirmation message to the BBERF, where the QoS rule is carried.

Step S705, BBERF installs QoS rules. The gateway where the BBERF is located performs QoS control according to the QoS rules, and establishes, modifies, or terminates the bearer.

Step S706, the PCRF sends a policy and charging rule providing message to the PCEF, carrying the PCC rule and the event trigger. For each PCC rule, the PCRF also sends a policy control indication to the PCEF whether it needs to perform more than four layers of filtering. If necessary, the PCEF forwards the service data stream matching the PCC rule to the TDEF.

Step S707, the PCEF installs a PCC rule and an event trigger. The PCEF will forward the service data flow matching the PCC rule to the TDEF according to the policy control indication filtered by the four layers.

Step S708, the PCEF returns an acknowledgement message to the PCRF.

Step S709: The PCRF sends a service execution rule providing message to the TDEF to provide a service execution rule and an event trigger.

Step S710, the TDEF installs a service execution rule and an event trigger.

Step S711, the TDEF returns an acknowledgement message to the PCRF.

Embodiment 6

8 is a flowchart 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 receiving an event requesting a new QoS rule or detecting a PCRF subscription by the TDEF, The initiated IP-CAN session modification process, in which the gateway hosted by the BBERF communicates with the gateway where the PCEF resides, using the PMIPv6 protocol. The specific steps are as follows: Step S801: The TDEF detects that an event of the PCRF subscription occurs.

Step S802, the TDEF reports the event to the PCRF.

Step S803: The PCRF updates the policy according to the event reported by the TDEF. The modification of this policy will involve changes in the bearer layer resources. The PCRF policy updates PCC rules and QoS rules.

Step S804, the PCRF returns a response message to the TDEF. Step S805, the PCRF sends a gateway control and QoS rule providing message to the BBERF, and carries the updated QoS rule.

Step S806, the BBERF installs the QoS rule. The gateway where the BBERF is located performs QoS control according to the QoS rules, and establishes, modifies, or terminates the bearer.

Step S807, the BBERF returns an acknowledgement message to the PCRF.

Step S808: The PCRF sends a policy and charging rule providing message to the PCEF, and carries the updated PCC rule.

Step S809, the PCEF installs the updated PCC rule.

Step S810, the PCEF returns an acknowledgement message to the PCRF.

Example 7

9 is a flowchart of Embodiment 5 of the enhanced policy and charging control method of the present invention. As shown in FIG. 9, this embodiment describes an IP-CAN session modification process caused by a change in subscription data. In the process, the gateway hosted by the BBERF communicates with the gateway where the PCEF resides, using the PMIPv6 protocol. In this embodiment, it is assumed that whether more than four layers of service detection and policy charging control are performed on the user's service data stream are based on the user's subscription. That is, if the user's subscription does not allow more than four layers of service detection, the policy charging control of the four or more service data flows is not performed. Specific steps are as follows:

Step S901: The SPR detects that the user subscription document changes. This change can be understood as the user's increased service-aware license for certain services, or the removal of service-aware licenses for certain services or the complete removal of business-aware licenses for all services.

Step S902: The SPR sends a subscription document update message to the PCRF, and carries the updated subscription document.

Step S903: The PCRF returns an acknowledgement message to the SPR.

Step S904, the PCRF makes a policy decision according to the updated contract 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 a new service detection rule and initiate a service detection rule modification process.

(b) If the service-aware permission of some services is deleted, and the PCRF has already delivered the service detection rules for these services, but the PCRF has not yet formulated a policy execution session (including PCC rules and service execution rules) for these services, that is, If the policy and charging control of the four layers are not performed, the PCRF will initiate the process of modifying the service detection session and delete the corresponding service detection rule.

(c) If the service-aware permission of some services is deleted, and the PCRF has already delivered the service detection rules for these services and the PCRF has issued the policy enforcement rules for these services (including PCC rules and service execution rules), With more than four layers of policy and charging control, the PCRF not only needs to initiate the deletion service detection session modification process to delete the corresponding service execution rules, but also informs the PCEF to modify the routing orientation (that is, after using the PCC rules to control the service data flow directly after the policy control Send to the PDN network, no need to send to TDEF).

(d) If the service-aware 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 route orientation.

If the PCRF needs to notify the PCEF to modify the routing orientation of some services, step S905 to step S906 are performed. If the PCRF needs to initiate a process for modifying the service session, step S908 to step S910 are performed.

Step S905: If the PCRF needs to notify the PCEF to modify the routing direction of the certain service, the PCRF sends a policy and charging rule providing message to the PCEF, and cancels the matching of the service data stream and the PCC rule delivered before, and then continues the service data flow. Instructions forwarded to TDEF.

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

Step S907, the PCEF returns an acknowledgement message to the PCRF.

If the PCRF needs to initiate a process of service detection session modification, step S908 to step S910 are performed. Step S908: The PCRF sends a service detection session modification process to the TDEF, carries the service detection rule to be added or deleted, and/or carries the service execution rule to be deleted.

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

Step S910, the TDEF returns an acknowledgement message.

If the PCRF needs to terminate the service detection session, step S911 to step S913 are performed.

Step S911: The PCRF sends a service detection termination session request message to the TDEF.

Step S912: The TDEF deletes a policy (service detection rule, service execution rule, event trigger, and the like) related to the service detection session.

Step S913, the TDEF returns an acknowledgement message.

10 is a schematic structural diagram of a system for enhanced policy and charging control according to the present invention. As shown in FIG. 10, the system for enhanced policy and charging control of the present invention includes a setting unit 1001, a determining unit 1002, and a determining unit 1003. The first sending unit 1004, the second sending unit 1005, and the executing and returning unit 1006, wherein:

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

The determining unit 1002 is configured to formulate a PCC rule, a service detection rule, and a service execution rule. The determining unit 1003 is configured to determine whether to perform four or more layers of policy and charging control on the service data flow of the IP-CAN session.

The first sending unit 1004 is configured to send a PCC rule to the PCEF and/or to indicate whether to perform four or more layers of policy and charging control on the service data flow that matches the PCC rule;

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

The performing and returning unit 1006 is configured to perform the service detection rule on the service data flow, report the identification information of the detected data service to the PCRF, and/or perform the service execution on the detected data service. rule. The determining unit 1002 formulates a PCC rule according to the subscription information of the user during the initiation process of the IP-CAN session establishment or the IP-CAN session modification;

Correspondingly, the determining unit 1003 further determines, when performing control over four layers of policy and charging on the service data flow of the IP-CAN session, the PCEF forwards the service data flow that matches the PCC rule to the The TDEF, and the service data flow that will not match any PCC rules but that the PCRF indicates to perform more than four layers of policy and charging control is forwarded to the TDEF. The above IP-CAN session establishment process is initiated by the gateway hosted by the bearer binding and event reporting function entity BBERF after receiving the setup IP-CAN session request message; the above IP-CAN session modification process is provided by the application function entity AF The IP-CAN service information is initiated occasionally, or initiated by the TDEF after detecting a new service, or initiated after the BBERF receives an event requesting a QoS rule or detecting a PCRF subscription, or receives a request for a new QoS rule or detection at the TDEF. Initiated after the event of the PCRF subscription.

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

In the enhanced policy and charging control system of the present invention, the formulating unit 1002 formulates a service data flow of the PCC to perform control of four or more layers of policies and billing.

Correspondingly, the determining unit 1003 determines, when performing control over four layers of policy and charging on the service data flow that matches the PCC rule, the PCEF forwards the service data flow that matches the PCC rule to the TDEF.

When the subscription data is updated, the determining unit 1003 re-determines whether to perform four or more layers of policy and charging control on the service data flow of the IP-CAN session, and then re-determines the service execution rule. Then, it is sent to the TDEF by the second transmitting unit 1005.

Those skilled in the art will appreciate that the enhanced policy and charging control system illustrated in Figures 10 and 11 is designed to implement the aforementioned enhanced policy and charging control methods, as illustrated in Figures 10 and 11 The functions of the processing units in the enhanced policy and charging control system can be understood by referring to the description of the methods shown in FIG. 3 to FIG. 9. The functions of each processing unit can be implemented by a program running on the processor, or The specific logic circuit is implemented.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

An enhanced policy and charging control method, in which a service detection execution function entity TDEF is set in a policy and charging control PCC system, wherein the method includes:

The TDEF performs the service detection rule on the service data flow, reports the service information of the detected 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

In the initiation process of the IP-CAN session establishment or the IP-CAN session modification, the PCRF formulates a PCC rule according to the subscription information of the user;

The method further includes:

The PCEF will match the PCC rule and the PCRF indicates that a service data flow carrying more than four layers of policy and charging control is forwarded to the TDEF; and that the PCEF will not match any PCC rule but the PCRF A service data flow indicating that the service is detected is forwarded to the TDEF.

3. The method according to claim 2, wherein the IP-CAN session establishment process is performed by a gateway that hosts the bearer binding and event reporting function entity BBERF after receiving an IP-CAN session request message. Initiate

The process of modifying the IP-CAN session is initiated by the application function entity AF providing the service information of the IP-CAN, or initiated by the TDEF after detecting the new service, or receiving the request for the new quality of service QoS rule or detecting the PCRF at the BBERF. Initiated after the event of the subscription, or in TDEF Initiated after receiving an event requesting a new QoS rule or detecting a PCRF subscription.

The method according to claim 2, wherein the method further comprises: during the deleting the IP-CAN session, the PCRF indicating that the PCEF is deleted and the

The IP-CAN session is related to the PCC rules and instructs the TDEF to delete the service detection rules and/or service execution rules associated with the IP-CAN session.

The method according to claim 2, wherein the method further comprises: when the subscription data is updated, the PCRF re-determines whether to perform service detection on the service data flow of the IP-CAN session and/or four. Above layer policy and billing control, it is time to re-determine the service detection rules and/or business execution rules and update them to TDEF.

The method according to any one of claims 1 to 5, wherein the TDEF is set in the PCC system, specifically:

The TDEF is linked to the PCRF.

A PCC system, comprising a user subscription database SPR, AF, PCRF, BBERF, PCEF, and a charging system, wherein the SPR, the AF, the BBERF, and the PCEF are respectively connected to the PCRF, the PCEF Connecting to the charging system; wherein the PCC system further comprises a TDEF, and is connected to the PCRF; and the PCC system is used in the enhanced policy and charging control method according to claim 1.

The PCC system according to claim 7, wherein the TDEF and the PCRF are connected by an Sx interface.

9. An enhanced policy and charging control system, comprising: a setting unit, a formulating unit, a determining unit, a first transmitting unit, a second transmitting unit, and an executing and returning unit, wherein:

Setting unit, configured to set TDEF in the PCC system;

a unit for determining a PCC rule, a service detection rule, and a service execution rule; and a determining unit, configured to determine whether to perform a service on the service data flow of the IP-CAN session Detection and/or control of four or more policies and billing;

a first sending unit, configured to send a PCC rule to the PCEF and/or to indicate whether to perform service detection on the service data flow and/or control of four or more layers of policies and charging;

The execution and return 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.

The system according to claim 9, wherein the formulating unit formulates a PCC rule according to the subscription information of the user in the initiation process of the IP-CAN session establishment or the IP-CAN session modification;

Correspondingly, when the determining unit determines to perform service detection on the service data flow of the IP-CAN session, the PCEF will not match any PCC rule, but the PCRF indicates that the service data flow for performing service detection is forwarded to the The TDEF, and/or the determining unit further determines to perform control of the policy and charging of the service data flow of the IP-CAN session by four or more layers, and the PCEF forwards the service data flow that matches the PCC rule to The TDEF.

11. The system according to claim 10, wherein the IP-CAN session establishment process is performed by a gateway hosted by a bearer binding and event reporting function entity BBERF after receiving an IP-CAN session request message. Initiate

The system according to claim 10, wherein the system further comprises: a deleting unit, configured to delete the IP-CAN session during the deletion of the IP-CAN session Related PCC rules, and the business detection rules and/or business execution rules.

The system according to claim 10, wherein, when the subscription data is updated, the determining unit re-determines whether to perform service detection and/or a four-layer policy on the service data flow of the IP-CAN session. And charging control, when it is time to re-determine the service detection rule and/or the service execution rule, and send it to the TDEF by the second sending unit.