WO2015100972A1

WO2015100972A1 - Policy control method, policy execution apparatus and policy delivery apparatus

Info

Publication number: WO2015100972A1
Application number: PCT/CN2014/080662
Authority: WO
Inventors: 周晓云; 梁爽
Original assignee: 中兴通讯股份有限公司
Priority date: 2013-12-30
Filing date: 2014-06-24
Publication date: 2015-07-09
Also published as: CN104754657A

Abstract

Disclosed are a policy control method, a policy execution apparatus and a policy delivering apparatus. In the method, a policy execution entity obtains a policy rule delivered by PCRF, wherein the policy rule carries a filter and indication information, the indication information is used for indicating the type of the bearer to which the policy execution entity is bound according to the policy rule, or for determining whether the filter is sent to UE according to the type of the bearer and whether a TFT exists on the bearer; and the policy execution entity determines whether the filter is sent to the UE according to the indication information. The provided technical solution achieves the effect that according to the indication information delivered by the PCRF, the policy execution entity can get an accurate grasp of the opportunity for sending the filter to the UE, so that the PCRF can correctly instruct PCEF or BBERF to send the filter to the UE.

Description

The present invention relates to the field of communications, and in particular to a policy control method, policy enforcement, and delivery device. BACKGROUND OF THE INVENTION FIG. 1 is a schematic diagram of an architecture of a Policy and Charging Control (PCC) defined by a 3rd Generation Partnership Project (3GPP) according to the related art. As shown in Figure 1, the Policy and Charging Rules Function (PCRF) is used to define the Quality of Service (QoS) and the charging policy for the service. The PCRF needs to combine the service information received from the Application Function (AF), the user subscription information received from the Subscription Profile Repository (SPR), and the policy configured by the operator. The PCRF sends the control policy to the policy and the Charging Enforcement Function (PCEF) or the Bearer Binding and Event Report Function (BBERF). At the same time, the PCRF can subscribe to the bearer layer related events to the PCEF and/or the BBERF, so that when the above events occur in the bearer layer, it can be perceived in time and change the control strategy. In addition, the PCEF and the Traffic Detection Function (TDF) can perform application detection based on the PCC rules (PCEF) or Application and Detection Control (ADC) rules (TDF) delivered by the PCRF. control function. PCC can support a variety of Internet Protocol (IP) Access Network (IP-Accessible Network, IP-CAN for short), such as: Evolved Packet System (EPS), General Packet Radio Service (General Packet) Radio System, referred to as GPRS). In order to achieve end-to-end QoS guarantee, the 3GPP network provides QoS guarantee based on bearer granularity. Services mapped to the same bearer will be forwarded using the same bearer layer packet. If different bearer layer packet forwarding processing needs to be provided, the service flow needs to be mapped to different bearers. Under normal circumstances, each bearer has an associated traffic template (TFT). The upstream traffic flow template (UL TFT) is a set of upstream packet filters in the TFT. The downlink traffic flow template (DL TFT) is a set of downlink packet filters in the TFT. One host is allowed to have no TFTs in each packet data network (PDN) connection. For EPS IP-CAN, the default bearer may not have a TFT. The User Equipment (UE) uses the UL TFT to map the uplink traffic to an EPS bearer. PCEF (GTP-based S5/S8) or BBERF (PMIP-based S5/S8) uses DL TFT to map downlink traffic to an EPS bearer. For example: The UE maps the uplink data packet to a different EPS bearer based on the UL TFT allocated to the bearer. When the users match, the packet filters in the lowest priority UL TFT are first compared, and when no match is found, the comparison of the upstream packet filters is continued by increasing the priority order. When a match is found or all of the upstream packet filters have been compared, the entire process ends. If a match is found, the upstream packet will be transmitted through the associated EPS bearer of the TFT in which the matched upstream packet filter is located. If no match is found, the upstream packet will be sent through the EPS bearer that has not yet assigned the upstream packet filter. If all EPS bearers (including the default EPS bearers corresponding to the PDN) have been assigned one or more uplink packet filters, the UE will abandon the uplink packets. The bearer may be unidirectional, and for the downlink unidirectional bearer, in addition to the associated DL TFT of the bearer, an uplink filter is required to reject all uplink data to prevent the UE uplink data from being matched to the bearer. Downstream one-way bearer. In the related art, if there is no TFT on the default bearer, it means that any TFT data that cannot match the dedicated bearer can be transmitted through the default bearer without TFT. In addition, if there is no downlink TFT and no uplink TFT on the default bearer, it means that any uplink data that cannot match the dedicated bearer uplink TFT can be transmitted through the default bearer.

The PCF or QoS rule delivered by the PCRF includes a service data flow filter template (SDF template). The SDF template can usually include one or more service data flow filters (SDF packet filters). The PCRF can provide a PCC or QoS rule containing a wild-carded traffic stream filter to allow packets that cannot match any other PCC or QoS rules to pass. After the PCEF or BBERF installs or activates the PCC rules or QoS rules provided by the PCRF, the PCEF or BBERF performs bearer binding according to the QoS Class Identifier (QCI)/Assignment Keep Priority (ARP) in the rule, and according to the SDF template in the rule. The TFT is constructed to be transmitted to the UE. Although the same QCI/ARP rules can be bound to the same bearer, not the same QCI/ARP rules are always bound to the same bearer (for example, because the number of filters in a TFT is limited, it is possible There are more than one bearer of the same QCI/ARP). Therefore, the PCRF cannot determine which bearer the rule is bound to when providing the PCC rule/QoS rule, and the PCEF/BBERF finally decides to bind the PCC/QoS rule to a specific bearer. During IP-CAN session establishment, the PCRF may provide PCEC or BBERF with PCC rules or QoS rules containing wildcarded traffic data filters to allow packets that cannot match any other PCC rules or QoS rules to pass, PCEF or BBERF Traffic data filters containing wildcards are also not sent to the UE. Thus, there is no TFT on the default bearer. Thereafter, it is possible for the PCRF to provide other PCC rules or QoS rules to the PCEF or BBERF. The PCEF or BBERF may also bind these rules to the default bearer. However, if the filters of these rules are not sent to the UE, then the default bearer is still No TFT. However, when the PCRF provides PCC rules and QoS rules to the PCEF and BBERF, respectively, and indicates that the traffic data stream filter needs to be sent to the UE. If the PCEF rule and the BBERF respectively bind the PCC rule and the QoS rule to the default bearer, the data that is originally available on the default bearer cannot be transmitted on the default bearer because the service data stream filter is sent to the UE. In a special case, if the PCRF finds that the rule to be authorized has only the downlink one-way service data stream filter, the PCRF adds a filter that rejects any uplink service data stream (ie, a packet filter for the uplink direction that effectively disallows any useful). Uplink packet flows ). In this case, if the PCEF, BBERF binds the rule to the default bearer, and the PCEF and BBERF reject the uplink filter of all service data flows to the UE, the uplink service data that can be transmitted on the default bearer is Unable to transfer. A filter that rejects any upstream traffic data can usually be expressed as:

Packet Filter Direction = uplink only; and Remote port = 9 (the discard port). Thus, there is a lack of a method in the related art that enables the PCRF to correctly instruct the PCEF or BBERF to send a filter to the UE. In addition, there is a lack of a method in the related art that enables the PCEF or BBERF to effectively determine whether to send a filter to the UE. SUMMARY OF THE INVENTION The present invention provides a policy control method, a policy enforcement, and a delivery device, to at least solve the problem that the PCRF in the related art cannot correctly indicate that the PCEF or the BBERF sends a filter to the UE. According to an aspect of the invention, a policy control method is provided. The policy control method according to the present invention includes: a policy enforcement entity acquires a policy rule delivered by a PCRF, where the policy rule carries a filter and indication information, where the indication information is used to indicate a bearer to which the policy execution entity is bound according to the policy rule. Or, determining whether to send a filter to the UE according to the type of the bearer and whether the TFT exists on the bearer; the policy enforcement entity determines, according to the indication information, whether to send the filter to the UE. If the policy enforcement entity determines that the type of bearer to which the policy rule is bound is a dedicated bearer, the policy enforcement entity sends a filter to the UE. If the policy enforcement entity determines that the type of the bearer to which the policy rule is bound is the default bearer and the TFT exists on the default bearer, the policy enforcement entity sends a filter to the UE; or if the policy enforcement entity determines the bearer to which the policy rule is bound If the type is the default bearer and there is no TFT on the default bearer, the policy enforcement entity does not send a filter to the UE. The policy enforcement entity sends the constructed TFT to the UE through IP-CAN bearer signaling after constructing the TFT according to the filter. The indication is one of the following: Explicit indication parameters, predefined filter values. The predefined filter value is the filter that rejects any upstream traffic. The policy enforcement entity is one of the following: PCEF, BBERF. The control policy rule is one of the following: PCC rules, QoS rules. According to one aspect of the invention, another method of policy control is provided. The policy control method according to the present invention includes: the policy rule execution function acquires a policy rule delivered by the PCRF, where the filter carried by the policy rule includes a filter added by the PCRF to reject any uplink service data flow; the policy execution function is based on the policy rule The type of the bearer to be bound to, or whether to send a filter to the UE according to the type of the bearer and whether the TFT exists on the bearer. When the type of the bearer is a proprietary bearer, the policy enforcement function sends a filter to the UE. When the type of the bearer is the default bearer and the default bearer exists in the TFT, the policy enforcement function sends a filter to the UE; or, when the bearer type is the default bearer and the default bearer has an uplink TFT, the policy enforcement function sends a filter to the UE. When the bearer type is the default bearer and the default bearer does not exist in the TFT, the policy enforcement function does not send a filter to the UE; or, when the bearer type is the default bearer and the default bearer does not have the uplink TFT, the policy enforcement function does not send the filter to the UE. Or; when the bearer type is the default bearer, the policy enforcement function does not send a filter to the UE. According to still another aspect of the present invention, a policy enforcement apparatus is provided. The policy execution apparatus according to the present invention includes: an obtaining module, configured to acquire a policy rule delivered by the PCRF, where the policy rule carries a filter and indication information, where the indication information is used to indicate that the policy execution entity is bound according to the policy rule Type of bearer, or, depending on the type of bearer and whether there is TFT on the bearer Determining whether to send a filter to the UE; determining a module, configured to determine whether to send a filter to the UE according to the indication information. The determining module is configured to send a filter to the UE when determining that the type of the bearer to which the policy rule is bound is a dedicated bearer. a determining module, configured to send a filter to the UE when determining that the type of the bearer to which the policy rule is bound is the default bearer and the TFT exists on the default bearer; or, determining the module, setting the policy rule to be bound to When the type of the bearer is the default bearer and there is no TFT on the default bearer, the filter is not sent to the UE. According to still another aspect of the present invention, a policy issuing device is provided. The policy issuing device according to the present invention includes: a sending module, configured to send a policy rule to the policy enforcement entity, where the policy rule carries a filter and indication information, where the indication information is used to indicate that the policy execution entity is The type of the bearer to which the policy rule is bound, or whether the filter is sent to the user equipment UE according to the type of the bearer and whether the filter template TFT exists on the bearer. According to still another aspect of the present invention, another policy enforcement device is provided. The policy execution apparatus according to the present invention includes: an obtaining module, configured to acquire a policy rule delivered by the PCRF, where the filter carried by the policy rule includes a filter added by the PCRF to reject any uplink service data flow; and the determining module is set to The type of the bearer to which the policy rule is bound, or whether to send a filter to the UE according to the type of the bearer and whether the TFT exists on the bearer. The determining module is configured to determine to send a filter to the UE when the type of the bearer is a dedicated bearer. The determining module is configured to: when the type of the bearer is the default bearer and the default bearer exists in the TFT, determine to send the filter to the UE; or, when the bearer type is the default bearer and the default bearer has the uplink TFT, determine to send the filter to the UE. The determining module is configured to: when the bearer type is the default bearer and the default bearer does not exist in the TFT, it is determined that the filter is not sent to the UE; or, when the bearer type is the default bearer and the default bearer does not have the uplink TFT, it is determined not to send to the UE. Filter; or, when the bearer type is the default bearer, it is determined that the filter is not sent to the UE. The above apparatus further includes: a sending module, configured to send a filter to the UE when the determining result of the determining module is YES. According to the embodiment of the present invention, the policy execution entity obtains the policy rule delivered by the PCRF, where the policy rule carries a filter and indication information, where the indication information is used to indicate the bearer to which the policy execution entity is bound according to the policy rule. Type, or, according to the type of the bearer and whether the TFT exists on the bearer, whether to send a filter to the UE; the policy enforcement entity determines, according to the indication information, whether to send a filter to the UE, that is, the PCRF passes the control policy rule sent to the policy enforcement entity. Adding indication information, so that the policy enforcement entity determines, according to the indication information, whether to send a filter to the UE, and the indication information is according to a type of the bearer bound to the control policy rule, or according to the type of the bearer and the type of the bearer. Whether the presence of the TFT is determined, and the problem that the PCRF in the related art cannot correctly indicate that the PCEF or the BBERF sends the filter to the UE is solved, and the policy execution entity can accurately grasp the filter sent to the UE according to the indication information sent by the PCRF. Timing, so that PCRF can correctly indicate PCEF BBERF transmission filter to the UE. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the drawings: FIG. 1 is a schematic structural diagram of a PCC defined according to the related art 3GPP; FIG. 2 is a flowchart of a policy control method according to an embodiment of the present invention; FIG. 3 is a diagram showing a lack of BBERF according to a preferred embodiment of the present invention. In the scenario, after the PCRF sends the rule, the PCEF updates the flowchart of the bearer TFT. FIG. 4 is a flowchart of updating the bearer TFT after the QoS rule is sent by the PCRF in the scenario where the BBERF exists in the scenario of the BFFF. According to a preferred embodiment of the present invention, in the scenario where there is no BBERF, the PCRF updates the bearer TFT according to the resource request of the UE, and FIG. 6 is a scenario when there is a BBERF according to a preferred embodiment of the present invention. The flowchart of updating the bearer TFT after the QoS rule is delivered by the PCRF according to the resource request of the UE; FIG. 7 is a flowchart of another policy control method according to an embodiment of the present invention; FIG. 8 is a policy according to an embodiment of the present invention. FIG. 9 is a structural block diagram of a policy issuing device according to an embodiment of the present invention; FIG. 10 is a structural block diagram of another policy execution apparatus according to an embodiment of the present invention; FIG. 11 is a block diagram showing the structure of another policy execution apparatus according to a preferred embodiment of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. 2 is a flow chart of a policy control method in accordance with an embodiment of the present invention. As shown in FIG. 2, the method may include the following steps: Step S202: The policy enforcement entity obtains a policy rule that is sent by the PCRF, where the policy rule carries a filter and indication information, where the indication information is used to indicate the policy execution entity. The type of the bearer to which the policy rule is bound, or whether the filter is sent to the UE according to the type of the bearer and whether the TFT exists on the bearer; Step S204: The policy enforcement entity determines whether to send the filter to the UE according to the indication information. In the related art, the PCRF cannot correctly indicate that the PCEF or the BBERF sends a filter to the UE. Using the method shown in FIG. 2, the PCRF adds the indication information to the control policy rule sent to the policy enforcement entity, so that the policy enforcement entity determines whether to send the filter to the UE according to the indication information, and the indication information is based on Controlling the type of the bearer bound by the policy rule, or determining whether the PCRF cannot correctly indicate that the PCEF or the BBERF sends the filter to the UE according to the type of the bearer and whether the TFT exists on the bearer of the type. The policy enforcement entity can accurately grasp the timing of sending the filter to the UE according to the indication information sent by the PCRF, so that the PCRF can correctly instruct the PCEF or the BBERF to send the filter to the UE. In a preferred implementation process, the foregoing policy enforcement entity may be, but is not limited to, one of the following: PCEF, BBERF; the foregoing control policy rule may be, but is not limited to, one of the following: a PCC rule, a QoS rule; the foregoing indication information may be, but is not limited to, One of the following: Explicit indication parameters, predefined filter values. In a preferred implementation process, the foregoing predefined filter value may be a filter that rejects any upstream service data flow. Preferably, in step S204, if the policy enforcement entity determines that the type of the bearer is a dedicated bearer, the policy enforcement entity sends a filter to the UE. Preferably, in step S204, if the policy enforcement entity determines that the type of the bearer is the default bearer according to the indication information and the TFT exists on the default bearer, the policy enforcement entity sends a filter to the UE; or if the policy enforcement entity determines according to the indication information. If the type of bearer is the default bearer and there is no TFT on the default bearer, the policy enforcement entity does not send a filter to the UE. Preferably, in step S204, the policy enforcement entity sends the constructed TFT to the UE by IP-CAN bearer signaling after constructing the TFT according to the filter. The above preferred implementation process will be further described below in conjunction with the preferred embodiments illustrated in Figures 3-6. Preferred Embodiment 1 FIG. 3 is a flowchart of a PCEF updating a bearer TFT after a PCRF issues a rule in a scenario in which a BBERF is absent according to a preferred embodiment of the present invention. As shown in FIG. 3, the process may include the following processing steps: Step S302: The PCEF obtains a request message for requesting to establish an IP-CAN session, where the information carried in the request message may include, but is not limited to: a user identifier, a PDN identifier. . Step S304: The PCEF sends a credit control request (CCR) message based on the Diameter protocol to the PCRF, where the information carried in the CCR message may include, but is not limited to, a user identifier, a PDN identifier, and an IP address. Step S306: The PCRF performs policy decision according to the user subscription, the network policy, and the IP-CAN bearer information, and the method may include: formulating a default PCC rule. If the PCRF does not have the user-related subscription information, the PCRF needs to interact with the SPR to obtain User's signing information. Step S308: The PCRF returns a credit control response (CCA) message based on the Diameter protocol to the PCEF, where the related policy carried in the CCA message may include: a default PCC rule. Step S310: The PCEF returns an IP-CAN session response message, where the information carried in the response message may include, but is not limited to, IP address information. At this time, the relevant TFT does not exist on the default bearer. Step S312: The PCEF may initiate a bearer-related operation, which may include, but is not limited to, a modification of a default bearer and a creation of a dedicated bearer. For the modification of the default bearer, the PCEF may be based on the service in the PCC rule bound to the default bearer. The data stream template constructs the TFT and further transmits it to the TFT. At this point, the IP-CAN session is established, and at least one PCC rule is bound to the default bearer. However, the default bearer may have TFTs, or there may be no TFTs or only downlink TFTs and no uplink TFTs, depending on PCRF and PCEF decisions. . For example: There is no filter sending indication in the PCC rule bound by PCEF to the default bearer. Step S314: During the lifetime of the IP-CAN session, the PCRF performs decision update. The PCRF formulates a PCC rule, and the QCI/ARP of the PCC rule is the same as the QCI/ARP of the default bearer. If the service data stream filter included in the PCRF decision PCC rule needs to be sent to the UE, the PCRF may include an unconditional transmission indication in the PCC rule; if the PCRF decision is made when the PCC rule is bound to the default bearer and the default bearer has no TFT, then the PCC The filter included in the rule is not sent to the UE; when the PCC rule is bound to the dedicated bearer or the PCC rule is bound to the default bearer and the existing TFT is carried by default, and the filter included in the PCC rule needs to be sent to In the case of the UE, the PCRF may include a conditional transmission indication in the PCC rule to indicate that when the PCC rule is bound to the default bearer and the default bearer has no TFT, the filter included in the PCC rule is not sent to the UE, but when the PCC rule is bound. When a proprietary bearer or PCC rule is bound to the default bearer and the TFT is carried by default, the filter included in the PCC rule can be sent to the UE. It should be noted that, if the PCRF finds that the rule to be authorized has only the downlink one-way service data stream filter, the PCRF adds a filter that rejects any uplink service data stream. At this point, the filter rejecting any upstream traffic data stream can be considered a conditional transmission indication. Of course, the operator can also pre-define some filter values in the PCRF and PCEF. When the PCEF receives the filter of this value, the PCEF can be understood as a conditional transmission indication. (A filter that rejects any upstream traffic data stream can be considered as a predefined filter value.) That is, if the PCEF binds the PCC rule to a dedicated bearer or binds the PCC rule to the default bearer and the default bearer exists in the TFT. Then, the PCEF can construct the TFT according to the filter included in the PCC rule and send it to the UE through the IP-CAN bearer signaling; if the PCEF binds the PCC rule to the default bearer and the default bearer does not exist in the TFT, the PCEF does not send the PCC. The filter contained in the rule is sent to the UE. Or, if the PCEF binds the PCC rule to the dedicated bearer or binds the PCC rule to the default bearer and the default bearer has an uplink TFT, the PCEF can construct the TFT according to the filter included in the PCC rule and carry the signaling through the IP-CAN. Sending to the UE; if the PCEF binds the PCC rule to the default bearer and the default bearer does not have an uplink TFT, the PCEF does not send the filter included in the PCC rule to the UE; or the PCEF binds the PCC rule to the dedicated bearer. The PCEF may construct the TFT according to the filter included in the PCC rule and send the signal to the UE through the IP-CAN bearer signaling; if the PCEF binds the PCC rule to the default bearer, the PCEF does not send the filter included in the PCC rule to the

Step S316: The PCRF sends a Re-authentication Request (RAR) message based on the Diameter protocol to the PCEF, where the information carried in the RAR message may include, but is not limited to, a PCC rule, where the PCC rule includes a filter sending indication. Step S318: The PCEF installs the PCC rule and returns a Diameter Protocol-based Re-authentication Response (RAA) message. Step S320: If the PCC rule carries an unconditional transmission indication, whether the PCEF rules the PCC rule to the dedicated bearer or the default bearer, the PCEF constructs the TFT according to the service data flow filter in the PCC rule, and passes the IP- The CAN bearer signaling is sent to the UE. If the PCC rule carries the conditional sending indication, if the PCEF binds the PCC rule to the dedicated bearer or binds the PCC rule to the default bearer and hosts the TFT by default, the PCEF can construct the TFT according to the filter included in the PCC rule. The IP-CAN bearer signaling is sent to the UE; if the PCEF binds the PCC rule to the default bearer and the default bearer has no TFT, the PCEF does not send the filter included in the PCC rule to the UE. It should be noted that, when the PCEF detects that the PCC rule delivered by the PCRF includes a filter added by the PCRF to reject any uplink service data flow, the PCEF will understand as a conditional transmission indication and perform corresponding operations, that is, if the PCEF will When the PCC rule is bound to the dedicated bearer or the PCC rule is bound to the default bearer and the default bearer exists in the TFT, the PCEF may construct the TFT according to the filter included in the PCC rule and send it to the UE through the IP-CAN bearer signaling; When the PCEF binds the PCC rule to the default bearer and the default bearer has no TFT, the PCEF does not send the filter included in the PCC rule to the UE. Or, if the PCEF binds the PCC rule to the dedicated bearer or binds the PCC rule to the default bearer and carries the uplink TFT by default, the PCEF can construct the TFT according to the filter included in the PCC rule and carry the signaling through the IP-CAN. Sending to the UE; if the PCEF binds the PCC rule to the default bearer and the default bearer does not have an uplink TFT, the PCEF does not send the filter included in the PCC rule to the UE; or the PCEF binds the PCC rule to the dedicated bearer. Then, the PCEF may construct the TFT according to the filter included in the PCC rule and send the signal to the UE through the IP-CAN bearer signaling; if the PCEF binds the PCC rule to the default bearer, the PCEF does not send the filter included in the PCC rule to the UE. Preferred Embodiment 2 FIG. 4 is a flowchart of updating a bearer TFT after a QoS rule is sent by a PCRF in a scenario where a BBERF exists in a scenario in which a BBERF is present. As shown in FIG. 4, the process may include the following processing steps: Step S402: The BBERF obtains a request message for requesting to establish an IP-CAN session, where the information carried in the request message may include, but is not limited to: a user identifier, a PDN identifier. . Step S404: The BBERF sends a credit control request (CCR) message based on the Diameter protocol to the PCRF, where the information carried in the CCR message may include, but is not limited to, a user identifier, a PDN identifier, and an IP address, requesting to establish a gateway control session. Step S406: The PCRF performs policy decision according to the user subscription, the network policy, and the IP-CAN bearer information, and the method may include: formulating a default PCC rule and a corresponding QoS rule. If the PCRF does not have user-related subscription information, the PCRF needs to interact with the SPR to obtain the subscription information of the user. Step S408: The PCRF returns a credit control response (CCA) message based on the Diameter protocol to the BBERF, where the related policy carried in the CCA message may include: a default QoS rule. Step S410: The gateway where the BBERF is located sends a request message for establishing an IP-CAN session to the gateway where the PCEF is located, where the information carried in the request message may include, but is not limited to, a user identifier and a PDN identifier. Step S412: The PCEF sends a credit control request (CCR) message based on the Diameter protocol to the PCRF, where the information carried in the CCR message may include, but is not limited to, a user identifier, a PDN identifier, and an IP address, requesting to establish a Gx session. Step S414: The PCRF associates the gateway control session with the Gx session according to the user identifier, and the PCRF sends the PCC rule defined above to the PCEF. Step S416: The gateway where the PCEF is located returns an IP-CAN session response message to the gateway where the BBERF is located, where the information carried in the response message may include but is not limited to: IP address information. At this time, there is no correlation on the default bearer. TFT. Step S418: The gateway where the BBERF is located returns an IP-CAN session response message, where the information carried in the response message may include but is not limited to: IP address information. At this time, the default bearer does not exist.

Step S420: The BBERF may initiate a bearer-related operation, where the BBERF may include, but is not limited to: a modification of a default bearer and a creation of a dedicated bearer; and for a modification of the default bearer, the BBERF may be based on the service in the BBERF rule bound to the default bearer. The data stream template constructs the TFT and further transmits it to the TFT. At this point, the IP-CAN session is established, and at least one QoS rule is bound to the default bearer. However, the default bearer may have TFTs, or there may be no TFTs or only downlink TFTs and no uplink TFTs, depending on PCRF and PCEF decisions. . For example: There is no filter sending indication in the QoS rule bound by PCEF to the default bearer. Step S422: During the lifetime of the IP-CAN session, the PCRF performs decision update. The PCRF formulates PCC rules and corresponding QoS rules, and the QCI/ARP of the PCC/QoS rule is the same as the QCI/ARP of the default bearer. If the service data flow filter included in the PCRF decision QoS rule needs to be sent to the UE, the PCRF may include an unconditional transmission indication in the QoS rule; if the PCRF decision is made when the QoS rule is bound to the default bearer and the default bearer has no TFT, then QoS The filter included in the rule is not sent to the UE; when the QoS rule is bound to the dedicated bearer or the QoS rule is bound to the default bearer and the existing TFT is carried by default, and the filter included in the QoS rule needs to be sent to At the time of the UE, the PCRF may include a conditional transmission indication in the QoS rule to indicate that when the QoS rule is bound to the default bearer and the default bearer has no TFT, the filter included in the QoS rule is not sent to the UE, but when the QoS rule is bound When a proprietary bearer or QoS rule is bound to the default bearer and the TFT is carried by default, the filter included in the QoS rule can be sent to the UE. It should be noted that, if the PCRF finds that the rule to be authorized has only the downlink one-way service data stream filter, the PCRF adds a filter that rejects any uplink service data stream. At this point, the filter rejecting any upstream traffic data stream can be considered a conditional transmission indication. Of course, the operator can also pre-define some filter values in the PCRF and BBERF. When the BBERF receives the filter of this value, the BBERF can be understood as a conditional transmission indication. (A filter that rejects any upstream traffic is considered to be a predefined filter value.) That is, if BBERF binds a QoS rule to a proprietary bearer or binds a QoS rule to the default bearer and the default bearer exists in the TFT Then, the BBERF can construct the TFT according to the filter included in the QoS rule and send it to the UE through the IP-CAN bearer signaling; if the BBERF binds the QoS rule to the default bearer and the default bearer has no TFT, the BBERF does not pass the QoS rule. The included filters are sent to the UE. Or, if the BBERF binds the QoS rule to the dedicated bearer or binds the QoS rule to the default bearer and carries the uplink TFT by default, the BBERF can construct the TFT according to the filter included in the QoS rule and carry the signaling through the IP-CAN. Send to the UE; if the BBERF binds the QoS rule to the default bearer and the default bearer does not have an uplink TFT, then the BBERF does not send the filter included in the QoS rule to the UE; or the BBERF binds the QoS rule to the dedicated bearer. Then the BBERF can construct the TFT according to the filter included in the QoS rule and send it to the UE through the IP-CAN bearer signaling; if the BBERF binds the QoS rule to the default bearer, the BBERF does not send the filter included in the QoS rule to the UE. Step S424: The PCRF sends a Diameter Protocol-based Re-authentication Request (RAR) message to the BBERF, where the information carried in the RAR message may include, but is not limited to: a QoS rule, where the QoS rule includes a filter sending indication. Step S426: The BBERF installs the QoS rule and returns a Diameter Protocol based Reauthentication Response (RAA) message. Step S428: If the QoS rule carries an unconditional transmission indication, whether the BBERF binds the QoS rule to the dedicated bearer or the default bearer, the BBERF constructs the TFT according to the service data flow filter in the QoS rule, and passes the IP- The CAN bearer signaling is sent to the UE. If the QoS rule carries a conditional transmission indication, if the BBERF binds the QoS rule to the dedicated bearer or binds the QoS rule to the default bearer and hosts the TFT by default, the BBERF can construct the TFT according to the filter included in the QoS rule. The packet is sent to the UE through the IP-CAN bearer signaling; if the BBERF binds the QoS rule to the default bearer and the default bearer has no TFT, the BBERF does not send the filter included in the QoS rule to the UE. It should be noted that, when the BBERF detects that the QoS rule delivered by the PCRF includes a filter added by the PCRF to reject any uplink service data flow, the BBERF will be understood as a conditional transmission indication and perform corresponding operations, that is, if the BBERF will When the QoS rule is bound to the dedicated bearer or the QoS rule is bound to the default bearer and the default bearer exists in the TFT, the BBERF can construct the TFT according to the filter included in the QoS rule and send it to the UE through the IP-CAN bearer signaling; When the BBERF binds the QoS rule to the default bearer and the default bearer has no TFT, the BBERF does not send the filter contained in the QoS rule to the UE. Or, if the BBERF binds the QoS rule to the dedicated bearer or binds the QoS rule to the default bearer and carries the uplink TFT by default, the BBERF can construct the TFT according to the filter included in the QoS rule and carry the signaling through the IP-CAN. Send to the UE; if the BBERF binds the QoS rule to the default bearer and the default bearer does not have an uplink TFT, then the BBERF does not send the filter included in the QoS rule to the UE; or the BBERF binds the QoS rule to the dedicated bearer. Then the BBERF can construct the TFT according to the filter included in the QoS rule and send it to the UE through the IP-CAN bearer signaling; if the BBERF binds the QoS rule to the default bearer, the BBERF does not send the filter included in the QoS rule to the UE. Step S430: The PCRF sends a Re-authentication Request (RAR) message based on the Diameter protocol to the PCEF, where the information carried in the RAR message may include, but is not limited to, a PCC rule. Step S432: The PCEF installs the PCC rule and returns a Diameter Protocol-based Re-authentication Response (RAA) message. Preferred embodiment three FIG. 5 is a flowchart of a PCEF updating a bearer TFT after a PCRF issues a rule according to a resource request of a UE, in a scenario where there is no BBERF in a preferred embodiment of the present invention. As shown in FIG. 5, the process may include the following processing steps: Step S502: The PCEF obtains a request message for requesting to establish an IP-CAN session, where the information carried in the request message may include, but is not limited to: a user identifier, a PDN identifier. . Step S504: The PCEF sends a credit control request (CCR) message based on the Diameter protocol to the PCRF, where the information carried in the CCR message may include, but is not limited to, a user identifier, a PDN identifier, and an IP address. Step S506: The PCRF performs policy decision according to the user subscription, the network policy, and the IP-CAN bearer information, and the method may include: formulating a default PCC rule. If the PCRF does not have the user-related subscription information, the PCRF needs to interact with the SPR to obtain User's signing information. Step S508: The PCRF returns a credit control response (CCA) message based on the Diameter protocol to the PCEF, where the related policy carried in the CCA message may include: a default PCC rule. Step S510: The PCEF returns an IP-CAN session response message, where the information carried in the response message may include, but is not limited to, IP address information. At this time, the relevant TFT does not exist on the default bearer. Step S512: The PCEF may initiate a bearer-related operation, which may include, but is not limited to, a modification of a default bearer and a creation of a dedicated bearer. For the modification of the default bearer, the PCEF may be based on the service in the PCC rule bound to the default bearer. The data stream template constructs the TFT and further transmits it to the TFT. At this point, the IP-CAN session is established, and at least one PCC rule is bound to the default bearer. However, the default bearer may have TFTs, or there may be no TFTs or only downlink TFTs and no uplink TFTs, depending on PCRF and PCEF decisions. . For example: There is no filter sending indication in the PCC rule bound by PCEF to the default bearer. Step S514: During the lifetime of the IP-CAN session, the PCEF obtains the IP-CAN bearer signaling, that is, the bearer resource modification request message initiated by the UE, where the information carried in the request message includes: the UE requests to add or Modified filters and possible QoS information. Step S516: The PCEF sends a credit control request (CCR) message based on the Diameter protocol to the PCRF, where the information carried in the CCR message may include, but is not limited to, a filter that the UE requests to add or modify and possible QoS information. Step S518: The PCRF performs decision update according to the request of the UE. The PCRF formulates a PCC rule, and the QCI/ARP of the PCC rule is the same as the QCI/ARP of the default bearer. If the service data stream filter included in the PCRF decision PCC rule needs to be sent to the UE, the PCRF includes an unconditional transmission indication in the PCC rule; if the PCRF decision is made when the PCC rule is bound to the default bearer and the default bearer has no TFT, then the PCC rule The included filter is not sent to the UE, but when the PCC rule is bound to the dedicated bearer or the PCC rule is bound to the default bearer and the existing TFT is carried by default, and the filter included in the PCC rule needs to be sent to the UE. Then, the PCRF may include a conditional sending indication in the PCC rule to indicate that when the PCC rule is bound to the default bearer and the default bearer has no TFT, the filter included in the PCC rule is not sent to the UE, and when the PCC rule is bound to When a proprietary bearer or PCC rule is bound to the default bearer and the TFT is carried by default, the filter included in the PCC rule is sent to the UE. It should be noted that, if the PCRF finds that the rule to be authorized has only the downlink one-way service data stream filter, the PCRF adds a filter that rejects any uplink service data stream. At this point, the filter rejecting any upstream traffic data stream can be considered a conditional transmission indication. Of course, the operator can also pre-define some filter values in the PCRF and PCEF. When the PCEF receives the filter of this value, the PCEF can be understood as a conditional transmission indication. (A filter that rejects any upstream traffic data stream can be considered as a predefined filter value.) That is, if the PCEF binds the PCC rule to a dedicated bearer or binds the PCC rule to the default bearer and the default bearer exists in the TFT. Then, the PCEF can construct the TFT according to the filter included in the PCC rule and send it to the UE through the IP-CAN bearer signaling; if the PCEF binds the PCC rule to the default bearer and the default bearer has no TFT, the PCEF does not pass the PCC rule. The included filters are sent to the UE. Or, if the PCEF binds the PCC rule to the dedicated bearer or binds the PCC rule to the default bearer and carries the uplink TFT by default, the PCEF can construct the TFT according to the filter included in the PCC rule and carry the signaling through the IP-CAN. If the PCEF binds the PCC rule to the default bearer and the default bearer does not have an uplink TFT, the PCEF does not send the filter included in the PCC rule to the UE; or, the PCEF binds the PCC rule to the dedicated bearer. The PCEF may construct the TFT according to the filter included in the PCC rule and send the signal to the UE through the IP-CAN bearer signaling; if the PCEF binds the PCC rule to the default bearer, the PCEF does not send the filter included in the PCC rule to the

Step S520: The PCRF returns a credit control response (CCA) message based on the Diameter protocol to the PCEF, where the related policy carried in the CCA message may include: a default PCC rule, where the PCC rule includes a filter sending indication. Step S522: The PCEF installs and executes the PCC rule. If the PCC rule carries an unconditional transmission indication, whether the PCEF rules the PCC rule to the dedicated bearer or the default bearer, the PCEF constructs the TFT according to the service data flow filter in the PCC rule, and carries the IP address through the IP-CAN. Order to send to the UE. If the PCC rule carries the conditional sending indication, if the PCEF binds the PCC rule to the dedicated bearer or binds the PCC rule to the default bearer and hosts the TFT by default, the PCEF can construct the TFT according to the filter included in the PCC rule. The IP-CAN bearer signaling is sent to the UE; if the PCEF binds the PCC rule to the default bearer and the default bearer has no TFT, the PCEF does not send the filter included in the PCC rule to the UE. It should be noted that, when the PCEF detects that the PCC rule delivered by the PCRF includes a filter added by the PCRF to reject any uplink service data flow, the PCEF will understand as a conditional transmission indication and perform corresponding operations, that is, if the PCEF will When the PCC rule is bound to the dedicated bearer or the PCC rule is bound to the default bearer and the TFT is carried by default, the PCEF can construct the TFT according to the filter included in the PCC rule and send it to the UE through the IP-CAN bearer signaling; When the PCC rule is bound to the default bearer and the default bearer has no TFT, the PCEF does not send the filter included in the PCC rule to the UE. Alternatively, if the PCEF binds the PCC rule to the dedicated bearer or binds the PCC rule to the default bearer and carries the uplink TFT by default, the PCEF can construct the TFT according to the filter included in the PCC rule and carry the signaling through the IP-CAN. Send to the UE; if the PCEF binds the PCC rule to the default bearer and the default bearer does not have an uplink TFT, the PCJ does not send the filter included in the PCC rule to the UE; or, the PCEF binds the PCC rule to the proprietary The bearer, the PCEF can construct the TFT according to the filter included in the PCC rule and send it to the UE through the IP-CAN bearer signaling; if the PCEF binds the PCC rule to the default bearer, the PCEF does not send the filter included in the PCC rule to the UE. Preferred Embodiment 4: FIG. 6 is a flowchart of updating a bearer TFT after a QoS rule is sent by a PCRF according to a resource request of a UE, in a scenario where a BBERF exists. As shown in FIG. 6, the process may include the following processing steps: Step S602: The BBERF obtains a request message for requesting to establish an IP-CAN session, where the information carried in the request message may include, but is not limited to: a user identifier, a PDN identifier. . Step S604: The BBERF sends a credit control request (CCR) message based on the Diameter protocol to the PCRF, where the information carried in the CCR message may include, but is not limited to, a user identifier, a PDN identifier, and an IP address, requesting to establish a gateway control session. Step S606: The PCRF performs policy decision according to the user subscription, the network policy, and the IP-CAN bearer information, and the method may include: formulating a default PCC rule and a corresponding QoS rule. If the PCRF does not have user-related subscription information, the PCRF needs to interact with the SPR to obtain the subscription information of the user. Step S608: The PCRF returns a credit control response (CCA) message based on the Diameter protocol to the BBERF, where the related policy carried in the CCA message may include: a default QoS rule. Step S610: The gateway where the BBERF is located sends a request message for establishing an IP-CAN session to the gateway where the PCEF is located, where the information carried in the request message may include, but is not limited to, a user identifier and a PDN identifier. Step S612: The PCEF sends a credit control request (CCR) message based on the Diameter protocol to the PCRF, where the information carried in the CCR message may include, but is not limited to, a user identifier, a PDN identifier, and an IP address, requesting to establish a Gx session. Step S614: The PCRF associates the gateway control session with the Gx session according to the user identifier, and the PCRF sends the PCC rule defined above to the PCEF. Step S616: The gateway where the PCEF is located returns an IP-CAN session response message to the gateway where the BBERF is located, where the information carried in the response message may include but is not limited to: IP address information. At this time, there is no correlation on the default bearer. TFT. Step S618: The gateway where the BBERF is located returns an IP-CAN session response message, where the information carried in the response message may include but is not limited to: IP address information. At this time, there is no relevant information on the default bearer.

Step S620: The BBERF may initiate a bearer-related operation, where the BBERF may include, but is not limited to, a modification of a default bearer and a creation of a dedicated bearer. For the modification of the default bearer, the BBERF may be based on the service in the BBERF rule bound to the default bearer. The data stream template constructs the TFT and further transmits it to the TFT. At this point, the IP-CAN session is established, and at least one QoS rule is bound to the default bearer. However, the default bearer may have TFT or no TFT, which depends on the decision of the PCRF and the PCEF. For example: There is no filter sending indication in the QoS rule bound by PCEF to the default bearer. Step S622: During the lifetime of the IP-CAN session, the BBERF obtains the IP-CAN bearer signaling, that is, the bearer resource modification request message initiated by the UE, where the information carried in the request message includes: the UE requests to add or Modified filters and possible QoS information. Step S624: The BBERF sends a credit control request (CCR) message based on the Diameter protocol to the PCRF. The information carried in the CCR message may include, but is not limited to, a filter that the UE requests to add or modify and possible QoS information. Step S626: The PCRF performs decision update according to the request of the UE. The PCRF formulates PCC rules and corresponding QoS rules, and the QCI/ARP of the PCC/QoS rule is the same as the QCI/ARP of the default bearer. If the service data flow filter included in the PCRF decision QoS rule needs to be sent to the UE, the PCRF includes an unconditional transmission indication in the QoS rule; if the PCRF decision is made when the QoS rule is bound to the default bearer and the default bearer has no TFT, then the QoS rule The included filter is not sent to the UE; when the QoS rule is bound to the dedicated bearer or the QoS rule is bound to the default bearer and the existing TFT is carried by default, and the filter included in the QoS rule needs to be sent to the UE Then, the PCRF may include a conditional sending indication in the QoS rule to indicate that when the QoS rule is bound to the default bearer and the default bearer has no TFT, the filter included in the QoS rule is not sent to the UE, and when the QoS rule is bound to When a proprietary bearer or QoS rule is bound to the default bearer and the TFT is carried by default, the filter included in the QoS rule can be sent to the UE. It should be noted that, if the PCRF finds that the rule to be authorized has only the downlink one-way service data stream filter,

The PCRF adds a filter that rejects any upstream traffic. At this point, the filter rejecting any upstream traffic data stream can be considered a conditional transmission indication. Of course, the operator can also pre-define some filter values in the PCRF and BBERF. When the BBERF receives the filter of this value, the BBERF can be understood as a conditional transmission indication. (A filter that rejects any upstream traffic is considered to be a predefined filter value.) That is, if BBERF binds a QoS rule to a proprietary bearer or binds a QoS rule to the default bearer and the default bearer exists in the TFT Then, the BBERF can construct the TFT according to the filter included in the QoS rule and send it to the UE through the IP-CAN bearer signaling; if the BBERF binds the QoS rule to the default bearer and the default bearer has no TFT, the BBERF does not pass the QoS rule. The included filters are sent to the UE. Or, if the BBERF binds the QoS rule to the dedicated bearer or binds the QoS rule to the default bearer and carries the uplink TFT by default, the BBERF can construct the TFT according to the filter included in the QoS rule and carry the signaling through the IP-CAN. Send to the UE; if the BBERF binds the QoS rule to the default bearer and the default bearer does not have an uplink TFT, then the BBERF does not send the filter included in the QoS rule to the UE; or the BBERF binds the QoS rule to the dedicated bearer. Then the BBERF can construct the TFT according to the filter included in the QoS rule and send it to the UE through the IP-CAN bearer signaling; if the BBERF binds the QoS rule to the default bearer, the BBERF does not send the filter included in the QoS rule to the UE. Step S628: The PCRF sends a credit control response (CCA) message based on the Diameter protocol to the BBERF, where the information carried in the CCA message may include, but is not limited to: a QoS rule, where the QoS rule includes a filter sending indication. Step S630: The BBERF installs and executes the QoS rule. If the QoS rule carries an unconditional transmission indication, then whether the BBERF binds the QoS rule to the dedicated bearer or the default bearer, the PCEF will construct the TFT according to the service data flow filter in the QoS rule, and carry the IP-CAN bearer signal. Order to send to the UE. If the QoS rule carries a conditional transmission indication, if the BBERF binds the QoS rule to the dedicated bearer or binds the QoS rule to the default bearer and hosts the TFT by default, the BBERF can construct the TFT according to the filter included in the QoS rule. The packet is sent to the UE through the IP-CAN bearer signaling; if the BBERF binds the QoS rule to the default bearer and the default bearer has no TFT, the BBERF does not send the filter included in the QoS rule to the UE. It should be noted that, when the BBERF detects that the QoS rule delivered by the PCRF includes a filter added by the PCRF to reject any uplink service data flow, the BBERF will be understood as a conditional transmission indication and perform corresponding operations, that is, if the BBERF will When the QoS rule is bound to the dedicated bearer or the QoS rule is bound to the default bearer and the default bearer exists in the TFT, the BBERF can construct the TFT according to the filter included in the QoS rule and send it to the UE through the IP-CAN bearer signaling; When the BBERF binds the QoS rule to the default bearer and the default bearer has no TFT, the BBERF does not send the filter contained in the QoS rule to the UE. Or, if the BBERF binds the QoS rule to the dedicated bearer or binds the QoS rule to the default bearer and carries the uplink TFT by default, the BBERF can construct the TFT according to the filter included in the QoS rule and carry the signaling through the IP-CAN. Send to the UE; if the BBERF binds the QoS rule to the default bearer and the default bearer does not have an uplink TFT, then the BBERF does not send the filter included in the QoS rule to the UE; or the BBERF binds the QoS rule to the dedicated bearer. Then the BBERF can construct the TFT according to the filter included in the QoS rule and send it to the UE through the IP-CAN bearer signaling; if the BBERF binds the QoS rule to the default bearer, the BBERF does not send the filter included in the QoS rule to the UE. Step S632: The PCRF sends a Re-authentication Request (RAR) message based on the Diameter protocol to the PCEF, where the information carried in the RAR message may include, but is not limited to, a PCC rule. Step S634: The PCEF installs the PCC rule and returns a Diameter Protocol-based Re-authentication Response (RAA) message. 7 is a flow chart of another policy control method in accordance with an embodiment of the present invention. As shown in FIG. 7, the method may include the following processing steps: Step S702: The policy rule execution function acquires a policy rule that is sent by the PCRF, where the filter carried by the policy rule includes filtering that is rejected by the PCRF and rejects any uplink service data flow. Step S704: The policy execution function is based on the type of the bearer to which the policy rule is bound, or determines whether to send a filter to the UE according to the type of the bearer and whether the TFT exists on the bearer. In a preferred implementation, when the type of bearer is a dedicated bearer, the policy enforcement function sends a filter to the UE. In a preferred implementation, when the type of the bearer is the default bearer and the default bearer exists in the TFT, the policy enforcement function sends a filter to the UE; or, when the bearer type is the default bearer and the default bearer has an uplink TFT, the policy execution function is The UE sends a filter. In a preferred implementation process, when the bearer type is the default bearer and the default bearer does not exist in the TFT, the policy enforcement function does not send the filter to the UE; or, when the bearer type is the default bearer and the default bearer does not have the uplink TFT, the policy is executed. The function does not send a filter to the UE; or, when the bearer type is the default bearer, the policy enforcement function does not send a filter to the UE. FIG. 8 is a structural block diagram of a policy execution apparatus according to an embodiment of the present invention. As shown in FIG. 8 , the policy execution apparatus may be located in a policy execution entity, where the policy execution apparatus may include: an obtaining module 10, configured to obtain a policy rule delivered by a PCRF, where the policy rule carries a filter and indication information The indication information is used to indicate the type of the bearer to which the policy enforcement entity is bound according to the policy rule, or to determine whether to send a filter to the UE according to the type of the bearer and whether the TFT exists on the bearer; the determining module 20 is set according to the indication The information determines whether a filter is sent to the UE. The device shown in FIG. 8 solves the problem that the PCRF in the related art cannot correctly indicate that the PCEF or the BBERF sends a filter to the UE, and the policy enforcement entity can accurately grasp the filtering sent to the UE according to the indication information sent by the PCRF. The timing of the device, so that the PCRF can correctly indicate that the PCEF or BBERF sends a filter to the UE. Preferably, the determining module 20 is configured to send a filter to the UE when determining that the type of the bearer to which the policy rule is bound is a dedicated bearer. Preferably, the determining module 20 is configured to send a filter to the UE when determining that the type of the bearer to which the policy rule is bound is the default bearer and the TFT exists on the default bearer; or, the determining module 20 is set to be When the type of bearer to which the policy rule is bound is the default bearer and there is no TFT on the default bearer, the filter is not sent to the UE. FIG. 9 is a structural block diagram of a policy issuing device according to an embodiment of the present invention. As shown in FIG. 9, the policy sending device may be located in a PCRF, where the policy sending device may include: a sending module 30, configured to send a policy rule to a policy enforcement entity, where the policy rule carries a filter and The indication information is used to indicate the type of the bearer to which the policy enforcement entity is bound according to the policy rule, or to determine whether to send the filter to the user equipment UE according to the type of the bearer and whether the filter template TFT exists on the bearer. FIG. 10 is a structural block diagram of another policy execution apparatus according to an embodiment of the present invention. As shown in FIG. 10, the policy execution apparatus may include: an obtaining module 40, configured to acquire a policy rule that is sent by the PCRF, where the filter carried by the policy rule includes a filter added by the PCRF to reject any uplink service data flow; The determining module 50 is configured to set the type of the bearer to be bound according to the policy rule, or determine whether to send the filter to the UE according to the type of the bearer and whether the TFT exists on the bearer. Preferably, the determining module 50 is configured to determine to send a filter to the UE when the type of the bearer is a dedicated bearer. Preferably, the determining module 50 is configured to: when the type of the bearer is the default bearer and the default bearer exists in the TFT, determine to send the filter to the UE; or, when the type of the bearer is the default bearer and the default bearer has an uplink TFT, determine to the UE. Send filter. Preferably, the determining module 50 is configured to: when the bearer type is the default bearer and the default bearer does not exist in the TFT, determine that the filter is not sent to the UE; or, when the bearer type is the default bearer and the default bearer does not exist, the uplink TFT is determined. The filter is not sent to the UE; or, when the bearer type is the default bearer, it is determined that the filter is not sent to the UE. Preferably, as shown in FIG. 11, the sending module 60 is configured to send a filter to the UE when the determination result of the determining module is YES. From the above description, it can be seen that the above embodiments achieve the following technical effects (it is required that these effects are achievable by some preferred embodiments): With the technical solution provided by the embodiment of the present invention, the PCRF passes Adding indication information to the control policy rule sent to the policy enforcement entity, so that the policy enforcement entity determines, according to the indication information, whether to send a filter to the UE, and the indication information is based on a type of bearer bound to the control policy rule, or According to the type of the bearer and the presence or absence of the TFT on the bearer of the type, the policy enforcement entity can accurately grasp the timing of sending the filter to the UE according to the indication information sent by the PCRF, so that the PCRF is accurately added on the default bearer. TFT. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention. Industrial Applicability As described above, a policy control method, a policy enforcement, and a delivery device provided by the embodiments of the present invention have the following beneficial effects: The policy execution entity can accurately grasp the filter sent to the UE according to the indication information sent by the PCRF. The timing, so that the PCRF accurately adds the TFT on the default bearer.

Claims

claims

1. A strategic control method, including:

The policy execution entity obtains the policy rules issued by the policy and charging rule function PCRF, wherein the policy rules carry filters and indication information, and the indication information is used to instruct the policy execution entity to be executed according to the policy rules. The type of bearer to which it is bound, or, determine whether to send the filter template TFT to the user equipment UE according to the type of the bearer and whether there is a filter template TFT on the bearer. The policy execution entity determines whether to send the filter template to the user equipment UE according to the indication information. The UE sends the filter.

2. The method according to claim 1, wherein if the policy execution entity determines that the type of the bearer is a dedicated bearer, the policy execution entity sends the filter to the UE.

3. The method according to claim 1, wherein, if the policy execution entity determines that the type of the bearer is a default bearer and the TFT exists on the default bearer, the policy execution entity sends a message to the UE. the filter; or, if the policy execution entity determines that the type of the bearer is a default bearer and the TFT does not exist on the default bearer, the policy execution entity does not send the filter to the UE .

4. The method according to claim 2 or 3, wherein, after the policy execution entity constructs a TFT according to the filter, the constructed TFT is sent through the Internet Protocol access network IP-CAN bearer signaling. to the UE.

5. The method according to claim 1, wherein: the indication information is one of the following: explicit indication parameters, predefined filter values.

6. The method according to claim 5, wherein the predefined filter value is a filter that rejects any upstream service data flow.

7. The method according to any one of claims 1 to 3, wherein the policy execution entity is the following policy and charging execution function PCEF, bearer binding and event reporting function BBERF.

8. The method according to any one of claims 1 to 3, wherein the policy rules are one of the following: policy and charging control PCC rules, quality of service QoS rules.

9. A policy control method, including: a policy rule execution function that obtains policy rules issued by the policy and charging rule function PCRF, wherein the filter carried by the policy rule contains the rejection of any uplink service data added by the PCRF A flow filter; the policy execution function determines whether to send the filter template TFT to the user equipment UE according to the type of the bearer to which the policy rule is bound, or according to the type of the bearer and whether a filter template TFT exists on the bearer. The filter.

10. The policy control method according to claim 9, comprising: when the type of the bearer is a dedicated bearer, the policy execution function sends the filter to the UE.

11. The policy control method according to claim 9, comprising: when the type of the bearer is a default bearer and a TFT exists in the default bearer, the policy execution function sends the filter to the UE; or, When the type of the bearer is a default bearer and the default bearer has an uplink TFT, the policy execution function sends the filter to the UE.

12. The policy control method according to claim 9, comprising: when the bearer type is a default bearer and there is no TFT on the default bearer, the policy execution function does not send the filter to the UE; or , when the bearer type is a default bearer and there is no uplink TFT on the default bearer, the policy execution function does not send the filter to the UE; or, when the bearer type is a default bearer, The policy enforcement function does not send the filter to the UE.

13. A policy execution device, including:

The acquisition module is configured to acquire the policy rules issued by the policy and charging rule function PCRF, wherein the policy rules carry filters and indication information, and the indication information is used to instruct the policy execution entity to execute the policy according to the policy. The type of the bearer to which the rule is bound, or, determining whether to send the filter to the user equipment UE according to the type of the bearer and whether a filter template TFT exists on the bearer;

A determining module configured to determine whether to send the filter to the UE according to the indication information.

14. The apparatus according to claim 13, wherein the determining module is configured to send the filter to the UE when it is determined that the type of the bearer is a dedicated bearer.

15. The apparatus according to claim 13, wherein the determining module is configured to send the filter to the UE when it is determined that the type of the bearer is a default bearer and the TFT exists on the default bearer. or, the determining module is configured to not send the filter to the UE when it is determined that the type of the bearer is a default bearer and the TFT does not exist on the default bearer.

16. A policy delivery device, including: a delivery module configured to deliver policy rules to a policy execution entity, wherein the policy rules carry filters and indication information, and the indication information is used to indicate the The policy execution entity determines whether to send the filter to the user equipment UE according to the type of the bearer to which the policy rule is bound, or according to the type of the bearer and whether a filter template TFT exists on the bearer.

17. A policy execution device, including:

The acquisition module is configured to acquire policy rules issued by the policy and charging rule function PCRF, wherein the filters carried by the policy rules include filters added by the PCRF that reject any upstream service data flow; the determination module is configured It is the type of the bearer to which the policy rule is bound, or, it is determined whether to send the filter to the user equipment UE according to the type of the bearer and whether a filter template TFT exists on the bearer.

18 The policy execution device according to claim 17, wherein: the determining module is configured to determine to send the filter to the UE when the type of the bearer is a dedicated bearer.

19. The policy execution device according to claim 17, wherein: the determining module is configured to determine to send the filter to the UE when the type of the bearer is a default bearer and a TFT exists in the default bearer. ; Or, when the type of the bearer is a default bearer and the default bearer has an uplink TFT, determine to send the filter to the UE.

20. The policy execution device according to claim 17, wherein: the determining module is configured to determine not to send the filter to the UE when the bearer type is a default bearer and there is no TFT on the default bearer. server; or, when the type of the bearer is default When the bearer is recognized and there is no uplink TFT for the default bearer, it is determined not to send the filter to the UE; or, when the bearer type is a default bearer, it is determined not to send the filter to the UE.

21. The policy execution device according to claim 17, wherein the device further includes: a sending module, configured to send the filter to the UE when the determination result of the determination module is yes.