CN101990254B - Policy and charging control method as well as policy control and charging rule functional entities - Google Patents

Abstract

The invention discloses a policy charging control method and a policy control and charging rule functional entity. The policy charging control method includes: a first functional entity receives a request message from a second functional entity, and the request message carries a request allocation The first packet filter of the resource; the first functional entity updates the rules containing the second packet filter according to the first packet filter, wherein the second packet filter is the packet filter to be associated with the first packet filter; the first The functional entity sends the updated rule to the second functional entity. The present invention realizes that when the user equipment initiates a resource modification request, the policy control and charging rule functional entity can add a new one to the user equipment. or multiple new packet filters associated with an existing business data flow.

Description

Policy charging control method and policy control and charging rule functional entity

technical field

The present invention relates to the field of communication, in particular, to a policy charging control method and a policy control and charging rule functional entity.

Background technique

In the 3rd Generation Partnership Project (3rd Generation Partnership Project, referred to as 3GPP) Phase 7 (Release7) standard system, the policy and charging functions are implemented by the policy and charging control (Policy and Charging Control, referred to as PCC) architecture . The PCC architecture is a functional framework that can be applied to multiple access technologies. For example, it can be applied to the UMTS Terrestrial Radio Access Network (UMTS Terrestrial Radio Access Network, referred to as UMTS) of the Universal Mobile Telecommunications System (UMTS for short). UTRAN), Global system for Mobile Communication (GSM for short)/GSM Data Enhanced Evolution (Enhanced Data rates for Global Evolution, EDGE for short) wireless access network, and interworking wireless local area network (I-WLAN) wait.

In order to improve the performance of the 3GPP access system, the 3GPP standard organization further formulated the Evolved Packet System (EPS for short). E-UTRAN), Mobility Management Entity (MME for short), Serving Gateway (S-GW), Packet Data Network Gateway (P-GW or PDN GW for short), attribution It is composed of Home Subscriber Server (HSS for short), 3GPP Authentication, Authorization and Accounting (AAA for short) server and other supporting nodes. In order to implement the policy and charging control of the ESP system, the PCC architecture has also been enhanced, that is, the PCC of Phase 8 (Release 8) of the 3rd Generation Partnership Project (3GPP) for short.

Figure 1 is a Rel-8 PCC non-roaming architecture diagram of the related technology. The following describes each logical functional entity and its interface function in the PCC architecture with reference to Figure 1: Application Function Entity E (Application Function, referred to as AF), which provides business applications The network resources used by these business applications require dynamic policy control. When negotiating parameters on the service plane, the AF transmits relevant service information to the Policy and Charging Rules Function (Policy and Charging Rules Function, PCRF for short). 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 may return these parameters to the user equipment (User Equipment, UE for short). Wherein, the interface between the AF and the PCRF is the Rx interface.

The Policy Control and Charging Rule Function (PCRF) is the core of the PCC, 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 for short) 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 PCRF to formulate policies and charging rules includes: obtaining service-related information from AF; obtaining subscription information related to user policy and charging control from the Subscription Profile Repository (SPR); Information.

Policy and Charging Enforcement Function (Policy and Control Enforcement Function, referred to as PCEF) is usually located in the gateway (Gate-Way, referred to as GW), and executes the policies and charging rules formulated by 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 it is online charging, PCEF needs to perform credit management together with the Online Charging System (OCS for short). During offline charging, relevant charging information is exchanged between the PCEF and the Offline Charging System (OFCS for short). 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) in GPRS and the Packet Data Gateway (PDG for short) in I-WLAN.

Bearer Binding and Event Reporting Function (BBERF for short). Its functions include bearer binding, verification of uplink bearer binding, and event reporting. When UE accesses through E-UTRAN, and the PMIPv6 protocol is used between S-GW and P-GW, BBERF is located in S-GW. When UE accesses through a trusted non-3GPP access system, BBERF is located in trusted non-3GPP 3GPP access gateway, when the UE accesses through an untrusted non-3GPP access system, BBERF is located at the evolved packet data gateway (Evolved Packet Data Gateway, ePDG for short). At this point, the PCEF no longer performs the bearer binding function.

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

The Online Charging System (OCS) and the PCEF together control and manage user credits in the online charging mode.

The offline charging system (OFCS) and the PCEF complete charging operations in the offline charging mode.

Rel-8PCC supports resource modification requests initiated by the UE, including allocating resources for adding one or more new packet filters, modifying resources related to one or more existing packet filters, and deleting one or more Resources related to existing packet filters. Modifying one or more existing packet filter-related resources includes modifying one or more existing packet filter-related QoS, modifying the value of the packet filter itself (such as the port number of the packet filter) and modifying the priority of the packet filter grade etc. Different from the resource modification request initiated by the UE in Rel-7PCC based on the bearer level, the resource modification request initiated by the UE in Rel-8PCC is based on the service data flow (Service Date Flow, SDF for short) level.

However, the existing Rel-8PCC UE-initiated resource modification request process cannot support the UE to request to add one or more new packet filters, and the newly added packet filters must be associated with an existing SDF.

For the resource modification request process initiated by the UE of the existing Rel-8PCC in the related art, it cannot support the problem that the UE requests to add one or more new packet filters and the new packet filter must be associated with an existing SDF , no effective solution has been proposed so far.

Contents of the invention

In view of the resource modification request process initiated by the UE of the existing Rel-8PCC, it is not possible to support the UE to request to add one or more new packet filters and the new packet filter must be associated with an existing SDF. Invention, therefore, the main purpose of the present invention is to provide a policy charging control method to solve the above problems.

In order to achieve the above object, according to one aspect of the present invention, a policy charging control method is provided.

The policy charging control method according to the present invention includes: the first functional entity receives a request message from the second functional entity, and the request message carries a first packet filter requesting resource allocation; Updating the rule including the second packet filter, where the second packet filter is the packet filter to be associated with the first packet filter; the first functional entity sends the updated rule to the second functional entity.

Preferably, the first functional entity updating the rule including the second packet filter according to the first packet filter further includes: the first functional entity adds the first packet filter to the service data flow filter of the rule.

Preferably, the request message also carries a second packet filter identifier, and before the first functional entity adds the first packet filter to the regular service data flow filter, the method further includes: the first functional entity according to the first Two-packet filter identifies the found rule containing the second-packet filter.

Preferably, the request message also carries the identifier of the rule containing the second packet filter, and before the first functional entity adds the first packet filter to the service data flow filter of the rule, the method further includes: first The functional entity finds the rule containing the second packet filter according to the identifier of the rule containing the second packet filter.

Preferably, the request message also carries QoS information requested by the first packet filter, and the method further includes: the first functional entity updates the QoS information of the rule according to the QoS information requested by the first packet filter.

Preferably, before the first functional entity receives the request message from the second functional entity, the method further includes: the second functional entity finds the The rules of the packet filter, and include the identifier of the rule in the request message sent to the PCRF.

Preferably, either or both of the first packet filter and the second packet filter are one or more packet filters.

Preferably, the first functional entity is a policy control and charging rule functional entity, and the second functional entity is a policy and charging enforcement functional entity or a bearer binding and event reporting functional entity.

Preferably, if the second functional entity is a policy and charging enforcement functional entity, the rules are policy and charging control rules; if the second functional entity is a bearer binding and event reporting functional entity, the rules are quality of service rules and quality of service rules Corresponding policies and charging control rules.

In order to achieve the above object, according to another aspect of the present invention, a policy control and charging rule functional entity is provided.

The policy control and charging rule functional entity includes: a receiving module, configured to receive a request message from the second functional entity, the request message carrying a first packet filter requesting resource allocation; a requesting module, configured to subscribe to the user database Requesting user policy charging control subscription information; an update module, configured to update the rules including the second packet filter according to the first packet filter, wherein the second packet filter is a packet filter that needs to be associated with the first packet filter ; A sending module, configured to send the updated rule to the second functional entity.

Preferably, the updating module further includes: an updating submodule, configured to associate the first packet filter with the rule containing the second packet filter.

According to the present invention, the first functional entity is used to receive the request message from the second functional entity, and the request message carries the first packet filter requesting resource allocation; the first functional entity includes the second packet filter according to the update of the first packet filter The rules of the device, wherein, the second packet filter is the packet filter to be associated with the first packet filter; the first functional entity sends the updated rule to the second functional entity, which solves the problem of the existing Rel-8PCC UE-initiated The resource modification request process does not support the problem that UE requests to add one or more new packet filters and the new packet filter must be associated with an existing SDF, so that when the user equipment initiates a resource modification request, The policy control and charging rule functional entity PCRF can associate one or more new packet filters newly added by the user equipment with an existing service data flow SDF.

Description of drawings

The accompanying drawings described here are used to provide a further understanding of the present invention and constitute a part of the application. The schematic embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations to the present invention. In the attached picture:

FIG. 1 is a block diagram of a PCC structure according to Release8 of the related art;

FIG. 2 is a flow chart of a policy charging control method according to an embodiment of the present invention;

FIG. 3 is a flow chart of Embodiment 1 of a preferred policy charging control method according to an embodiment of the present invention;

FIG. 4 is a flow chart of Embodiment 2 of a policy charging control method according to an embodiment of the present invention;

FIG. 5 is a flow chart of Embodiment 3 of a policy charging control method according to an embodiment of the present invention;

FIG. 6 is a flow chart of Embodiment 4 of a policy charging control method according to an embodiment of the present invention;

Figure 7 is a schematic diagram of a preferred PCRF according to an embodiment of the present invention.

Detailed ways

Functional Overview

Considering that the resource modification request process initiated by the UE of the existing Release8PCC cannot support the UE to request to add one or more new packet filters and the newly added packet filters must be associated with an existing SDF, the embodiment of the present invention provides A policy charging control method is provided, the method comprising: a first functional entity receives a request message from a second functional entity, and the request message carries a first packet filter requesting resource allocation; the first functional entity The filter update includes rules of the second packet filter, where the second packet filter is the packet filter to be associated with the first packet filter; the first functional entity sends the updated rule to the second functional entity.

It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other. The present invention will be described in detail below with reference to the accompanying drawings and examples.

method embodiment

According to an embodiment of the present invention, a method for policy charging control is provided.

Fig. 2 is a flowchart of a policy charging control method according to an embodiment of the present invention.

As shown in Figure 2, the method includes the following steps S202 to S206:

Step S202, using the first functional entity to receive a request message from the second functional entity, where the request message carries a first packet filter requesting resource allocation;

Step S204, the first functional entity updates the rule including the second packet filter according to the first packet filter, where the second packet filter is the packet filter to be associated with the first packet filter;

Step S206, the first functional entity sends the updated rule to the second functional entity.

The implementation process of the embodiment of the present invention will be described in detail below with reference to examples.

Method embodiment one

According to the embodiment of the present invention, a policy and charging control is provided to realize UE-initiated bearer resource modification request, which is applied in the PCC architecture of Release 8, UE accesses through E-UTRAN and adopts between S-GW and P-GW GTP protocol.

Figure 3 shows that after the UE establishes an IP-CAN session access service, it initiates a resource modification request to request resource allocation for one or more newly added packet filters, and the packet filter is associated with the existing SDF (with one or more existing SDFs) packet filter association), that is, all packet filters belong to one SDF.

Fig. 3 is a flow chart of Embodiment 1 of a preferred policy charging control method according to an embodiment of the present invention. As shown in Figure 3, the method includes the following steps:

In step S301, the PCEF receives a resource modification request message, requesting resource allocation for one or more newly added packet filters, and the packet filter is associated with one or more existing packet filters. The message carries the new packet filter (new packet filter) and the associated packet filter identifier (linked EPS bearer packet filter id). The message can also carry the QoS information requested by the new packet filter, including QCI and GBR. new packet filter indicates the packet filter to be added, and linked EPS packet filter id indicates the identifier of the packet filter requested by the UE to associate the newly added packet filter with. This identifier is assigned by PCEF when the linked packed filter is added. An EPS packet filter identifier (packet filter id) can be used to indicate the SDF to be associated with the UE or all packet filters in the SDF;

Step S302, PCEF finds the corresponding linked SDF packet filter id according to the linked EPS bearer packet filter id. The SDF packet filter id is assigned by PCRF when the linked packet filter increases. PCEF maintains the corresponding relationship between EPS bearerpacket filter id and SDF packet filter id. PCEF sends an IP-CAN session modification request message to PCRF, that is, Credit-Control-Request, and CC-Request-Type AVP is set to UPDATE_REQUEST. PCEF carries new packet filter and linked SDF packet filter id in the message. The message can also carry the QoS information requested by the new packet filter;

Step S303, if the PCRF does not have relevant information about the user's subscription. The PCRF sends a request message to the SPR. SPR sends user-related subscription information to PCRF, and PCRF saves it;

In step S304, the PCRF makes a policy decision, and updates the PCC rule as follows: PCRF finds the PCC rule that previously included the linked SDF packet filter according to the linked SDF packet filter id. The business data flow filter in this PCC rule includes other packet filters besides the packet filter corresponding to the linkedSDF packet filter id. PCRF composes the new packet filter and the existing packet filter into the service data flow filter in the updated PCC rule. The PCRF assigns the SDF packet filter id to the new packet filter and forms the QoS information in the updated PCC rule according to the QoS information requested by the new packet filter and the QoS information of the original PCC rule. For example, the UE requests GBR for the new packet filter, then PCRF sets the GBR of the updated PCC rule to the sum of the newly requested GBR and the GBR in the original PCC rule;

In step S305, the PCRF sends an IP-CAN session modification confirmation message, namely Credit-Control-Answer, to the PCEF, and the message carries the updated PCC rule;

In step S306, the PCEF updates the PCC and returns a response message.

Method embodiment two

Fig. 4 is a flow chart of Embodiment 2 of the policy charging control method according to the embodiment of the present invention.

As shown in Figure 4:

Fig. 4 is an embodiment of the present invention, which provides a policy and charging control to implement UE-initiated bearer resource modification request, which is applied in the PCC architecture of Release 8, UE accesses through E-UTRAN and S-GW and P-GW The GTP protocol is adopted between them. The method includes the following steps:

In step S401, the PCEF receives a resource modification request message, requesting resource allocation for one or more newly added packet filters, and the packet filter is associated with one or more existing packet filters. The message carries new packet filter and linked EPSbearer packet filter id. The message can also carry the QoS information requested by the new packet filter, including QCI and GBR. new packet filter indicates the packet filter to be added, and linked EPS bearer packet filter id indicates the identifier of the packet filter requested by the UE to associate the newly added packet filter with. This identifier is assigned by PCEF when the linked packed filter is added;

Step S402, PCEF finds the previously corresponding linked SDF packet filter id according to the linked EPS bearer packet filter id, so as to find the PCC rule including the linked SDF packet filter. The service data flow filter in this PCC rule may include other packet filters besides the packet filter corresponding to the linkedSDF packet filter id. PCEF sends an IP-CAN session modification request message to PCRF, that is, Credit-Control-Request, and CC-Request-Type AVP is set to UPDATE_REQUEST. PCEF carries the new packet filter and the PCC rule identifier corresponding to the PCC rule in the message. The message can also carry the QoS information requested by the new packet filter;

Step S403, if the PCRF does not have relevant information about the user's subscription. The PCRF sends a request message to the SPR. SPR sends user-related subscription information to PCRF, and PCRF saves it;

In step S404, the PCRF makes a policy decision and updates the PCC rule as follows: PCRF finds the previous corresponding PCC rule according to the PCC rule identifier. PCRF combines the new packet filter and the existing packet filter in the PCC rule into the service data flow filter in the updated PCC rule. The PCRF assigns the SDF packetfilter id to the new packet filter, and forms the QoS information in the updated PCC rule according to the QoS information requested by the new packet filter and the QoS information of the original PCC rule. For example, the UE requests GBR for the newpacket filter, then PCRF sets the GBR of the updated PCC rule to the sum of the newly requested GBR and the GBR in the original PCC rule;

Step S405, the PCRF sends an IP-CAN session modification confirmation message, namely Credit-Control-Answer, to the PCEF, and the message carries the updated PCC rule;

Step S406, PCEF updates PCC, and returns a response message;

Method embodiment three

According to the embodiment of the present invention, a policy and charging control is provided to realize UE-initiated bearer resource modification request, which is applied in the PCC architecture of Release 8, UE accesses through E-UTRAN and adopts between S-GW and P-GW PMIPv6 protocol, or UE access through a trusted non-3GPP access network.

Fig. 5 is a flow chart of Embodiment 3 of the policy charging control method according to the embodiment of the present invention. As shown in Figure 5, the method includes the following steps:

Step S501, BBERF receives a resource modification request message, requesting resource allocation for one or more newly added packet filters, and the packet filter is associated with one or more existing packet filters. The message carries new packet filter and linked EPSbearer packet filter id. The message can also carry the QoS information requested by the new packet filter, including QCI and GBR. new packet filter indicates the packet filter to be added, and linked EPS bearer packet filter id indicates the identifier of the packet filter requested by the UE to associate the newly added packet filter with. This identifier is assigned by PCEF when the linked packed filter is added;

Step S502, BBERF finds the corresponding linked SDF packet filter id according to the linked EPS bearer packet filter id. The SDF packet filter id is assigned by PCRF when the linked packet filter increases. PCEF maintains the corresponding relationship between EPS bearerpacket filter id and SDF packet filter id. BBERF sends a gateway control session modification request message to PCRF, that is, Credit-Control-Request, and CC-Request-Type AVP is set to UPDATE_REQUEST. BBERF carries new packet filter and linked SDF packet filter id in the message. The message can also carry the QoS information requested by the new packet filter;

Step S503, if the PCRF does not have relevant information about the user's subscription. The PCRF sends a request message to the SPR. SPR sends user-related subscription information to PCRF, and PCRF saves it;

Step S504, PCRF makes a policy decision, and updates the PCC rule and QoS rule as follows: PCRF finds the PCC rule and QoS rule that previously included the linkedSDF packet filter according to the linked SDF packet filter id. In addition to the packet filter corresponding to the linked SDF packet filter id, the service data flow filter in the PCC rule/QoS rule may also include other packet filters. PCRF composes the new packet filter and the existing packet filter in the rule into the service data flow filter in the updated PCC rule/QoS rule. The PCRF assigns the SDF packetfilter id to the new packet filter, and forms the QoS information in the updated PCC rule/QoS rule according to the QoS information requested by the new packet filter and the QoS information of the original PCC rule/QoS rule. For example, the UE requests GBR for the new packet filter, then PCRF sets the GBR of the updated PCC rule/QoS rule to the sum of the newly requested GBR and the GBR in the original PCC rule/QoS rule;

Step S505, the PCRF sends a gateway control session modification confirmation message to the BBERF, namely Credit-Control-Answer, which carries the updated QoS rule;

Step S506, BBERF updates the QoS rule, and returns a response message;

Step S507, the PCRF sends a policy and charging rule provision message to the PCEF, carrying updated PCC rules;

In step S508, after the PCEF updates the PCC rule, it returns a confirmation message.

Method Embodiment Four

According to the embodiment of the present invention, a policy and charging control is provided to realize UE-initiated bearer resource modification request, which is applied in the PCC architecture of Release 8, UE accesses through E-UTRAN and adopts between S-GW and P-GW PMIPv6 protocol, or UE access through a trusted non-3GPP access network.

Fig. 6 is a flow chart of Embodiment 4 of the policy charging control method according to the embodiment of the present invention. As shown in Figure 6, the method includes the following steps:

Step S601, BBERF receives a resource modification request message, requesting resource allocation for one or more newly added packet filters, and the packet filter is associated with one or more existing packet filters. The message carries new packet filter and linked EPSbearer packet filter id. The message can also carry the QoS information requested by the new packet filter, including QCI and GBR. new packet filter indicates the packet filter to be added, and linked EPS bearer packet filter id indicates the identifier of the packet filter requested by the UE to associate the newly added packet filter with. This identifier is assigned by PCEF when the linked packed filter is added;

Step S602, BBERF finds the previously corresponding linked SDF packet filter id according to the linked packet filter id, so as to find the QoS rule including the linked packet filter. The service data flow filter in this QoS rule includes other packet filters besides the packet filter corresponding to the linked SDF packet filter id. BBERF sends a gateway control session modification request message to PCRF, that is, Credit-Control-Request, and CC-Request-Type AVP is set to UPDATE_REQUEST. BBERF carries the new packet filter and the QoS rule identifier corresponding to the QoS rule in the message. The message can also carry the QoS information requested by the new packet filter;

Step S603, if the PCRF does not have relevant information about the user's subscription. The PCRF sends a request message to the SPR. SPR sends user-related subscription information to PCRF, and PCRF saves it;

In step S604, the PCRF makes a policy decision and updates the PCC rule and the QoS rule. The PCRF finds the previous corresponding QoS rule according to the QoS rule identifier, so as to further find the PCC rule corresponding to the QoS rule. The service data flow filter in this PCC rule/QoS rule includes other packet filters besides the packet filter corresponding to the linked SDF packet filter id. PCRF composes the new packet filter and the existing packet filter in the rule into the service data flow filter in the updated PCC rule/QoS rule. The PCRF assigns the SDF packet filter id to the new packet filter, and forms the QoS information in the updated PCC rule/QoS rule according to the QoS information requested by the new packet filter and the QoS information of the original PCC rule/QoS rule. For example, the UE requests GBR for the newpacket filter, then PCRF sets the GBR of the updated PCC rule/QoS rule to the sum of the newly requested GBR and the GBR in the original PCC rule/QoS rule;

Step S605, the PCRF sends a gateway control session modification confirmation message, namely Credit-Control-Answer, to the BBERF, and the message carries the updated QoS rule;

Step S606, BBERF updates the QoS rule, and returns a response message;

Step S607, the PCRF sends a policy and charging rule provision message to the PCEF, carrying updated PCC rules;

Step S608, after the PCEF updates the PCC rule, it returns a confirmation message.

Device embodiment

According to an embodiment of the present invention, a method for a policy control and charging rule functional entity is provided.

Fig. 7 is a schematic diagram of a preferred policy control and charging rule functional entity according to an embodiment of the present invention.

As shown in FIG. 7, preferably, the policy control and charging rule functional entity 700 includes: a receiving module 702, an updating module 704, a sending module 706, and a requesting module 708, wherein the updating module 704 may also include an updating submodule 710, The policy control and charging rule function entity 700 may also include a request module 708 .

The functions of each module are described in detail below:

The receiving module 702 is configured to receive a request message from the second functional entity, where the request message carries identifiers of the first packet filter and the second packet filter requesting resource allocation, wherein the second packet filter is The first packet filter needs an associated packet filter; the update module 704 is used to update the policy and charging control rules according to the identification of the second packet filter; the sending module 706 is used to send a session modification confirmation to the second functional entity message, the session modification confirmation message carries updated policies and charging control rules; wherein, the updating module 704 may also include an updating sub-module 710, which is used to combine the first packet filter with the quality of service rules or policies and charging control rules Rules are associated; the policy control and charging rule functional entity may also include a request module 708, configured to request user policy charging control subscription information from the user subscription database.

From the above description, it can be seen that the present invention achieves the following technical effect: when the user equipment initiates a resource modification request, the policy control and charging rule functional entity One or more new packet filters are associated with an existing business data flow.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (11)

1. A policy charging control method, characterized in that, comprising: The first functional entity receives a request message from the second functional entity, where the request message carries a first packet filter requesting resource allocation; The first functional entity updates a rule including a second packet filter according to the first packet filter, where the second packet filter is a packet filter to be associated with the first packet filter; The first functional entity sends the updated rule to the second functional entity. 2. The method according to claim 1, wherein the first functional entity updating the rule containing the second packet filter according to the first packet filter comprises: The first functional entity adds the first packet filter to the service data flow filter of the rule. 3. The method according to claim 2, wherein the request message also carries the second packet filter identifier, and the first functional entity adds the first packet filter to the Before the business data flow filter of the above rule, the method also includes: The first functional entity finds a rule including the second packet filter according to the second packet filter identifier. 4. The method according to claim 2, wherein the request message also carries an identifier of a rule that includes a second packet filter, and the first packet filter is added to the first functional entity at the first functional entity. Before entering the ruled service data flow filter, the method also includes: The first functional entity finds the rule containing the second packet filter according to the identifier of the rule containing the second packet filter. 5. The method according to claim 1, wherein the request message also carries the quality of service information requested by the first packet filter, and the method further comprises: The first functional entity updates the quality of service information of the rule according to the quality of service information requested by the first packet filter. 6. The method according to claim 1, wherein before the first functional entity receives the request message from the second functional entity, the method further comprises: the second functional entity according to the received first functional entity A second packet filter identifier to be associated with finds a rule containing the second packet filter, and includes the identifier of the rule in a request message sent to the first functional entity. 7. The method according to any one of claims 1 to 6, wherein either or both of the first packet filter and the second packet filter are one or more packet filter. 8. The method according to any one of claims 1 to 6, wherein the first functional entity is a policy control and charging rule functional entity, and the second functional entity is a policy and charging enforcement functional entity or a bearer binding entity. Define and event report functional entity. 9. The method according to claim 8, if the second functional entity is a policy and charging enforcement functional entity, the rule is a policy and charging control rule; if the second functional entity is a bearer binding and An event reporting function entity, where the rules are quality of service rules and policy and charging control rules corresponding to the quality of service rules. 10. A policy control and charging rule functional entity, characterized in that it includes: a receiving module, configured to receive a request message from the second functional entity, where the request message carries a first packet filter requesting resource allocation; A request module, configured to request user policy and charging control subscription information from the user subscription database; An update module, configured to update a rule including a second packet filter according to the first packet filter, wherein the second packet filter is a packet filter that needs to be associated with the first packet filter; A sending module, configured to send the updated rule to the second functional entity. 11. The policy control and charging rule functional entity according to claim 10, wherein the updating module further comprises: The update submodule associates the first packet filter with the rule containing the second packet filter.

Images