WO2012116600A1

WO2012116600A1 - Function negotiating method and system for policy and charging control function entity

Info

Publication number: WO2012116600A1
Application number: PCT/CN2012/071282
Authority: WO
Inventors: 周晓云
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-03-01
Filing date: 2012-02-17
Publication date: 2012-09-07
Also published as: CN102655634A; CN102655634B

Abstract

Disclosed are a function negotiating method and system for a policy and charging control function entity. The method comprises: a visited location PCRF, on the basis of functions supported by self and functions supported by a visited location policy enforcement function entity, reporting to a home location PCRF the functions supported by the visited location; and the home location PCRF, on the basis of functions supported by self and the functions supported by the visited location, returning to the visited location PCRF the functions supported after negotiation. Employment of the present invention solves the incapability of a V-PCRF to issue a policy to the visited location policy enforcement function entity when the functions supported by the V-PCRF is different from the functions supported by the visited location policy enforcement function entity, thus allowing the technical effect of having the policy generated via negotiation to be enforced correctly.

Description

TECHNICAL FIELD The present invention relates to the field of communications, and in particular, to a method and system for policy negotiation of a policy and a charging control function entity. BACKGROUND The Policy and Charging Control (PCC) architecture of the 3rd Generation Partnership Project (3GPP) is a functional framework that can be applied to multiple access technologies. For example, a Universal Mobile Telecommunications System (UMTS) UMTS Terrestrial Radio Access Network (UTRAN), and a Global System for Mobile Communication (Global System for Mobile Communication) GSM)/Enhanced Data Rates for Global Evolution (EDGE) radio access network, interworking wireless local area network (I-WLAN), and Evolved Packet System (EPS). Figure 1 is a schematic diagram of a related art Rel-8 PCC non-roaming architecture, including: Application Function Entity 102 (Application Function, abbreviated as AF), and Policy and Charging Rules Function (PCRF) , Bearer Binding and Event Reporting Function (BBERF), Policy and Charging Enforcement Function (PCEF), User Subscription Database 110 (Subscription Profile) Repository, referred to as SPR, Online Charging System (OCS) and Offline Charging System 114 (OFCS). The following describes the logical function entities and their interface functions in the PCC architecture with reference to FIG. 1 : Application Function Entity 102 (Application Function, referred to as AF), provides access points for service applications, and network resources used by these service applications. Dynamic policy control is required. When the parameter negotiation is performed on the service plane, the AF transmits the related service information to the Policy and Charging Rules Function 104 (PCRF). If the service information is consistent with the PCRF policy, the Bayu PCRF accepts The negotiation; otherwise, the PCRF rejects the negotiation and simultaneously gives the business parameters acceptable to the PCRF in the feedback. The AF can then return these parameters to the user equipment (User Equipment, UE for short). The interface between AF and PCRF is the Rx interface. The PCRF 104 is the core of the PCC and is responsible for policy decision making and billing rules. The PCRF 104 provides network control rules based on service data flows, including traffic data flow monitoring, Gating Control Quality of Service (QoS) control, and data flow based charging rules. The PCRF 104 sends the policy and the charging policy to the Policy and Charging Enforcement Function 108 (PCEF). The PCRF 104 also needs to ensure that the rules are consistent with the user's subscription information. The PCRF 104 formulates the policy and the charging rule according to the following: the information about the service is obtained from the AF; the user policy charging control subscription information is obtained from the subscription profile database 110 (SPR); and the bearer-related network is obtained from the PCEF 108. Information. The PCEF 108 is configured to execute the policy and charging rules formulated by the PCRF 104 on the bearer plane. PCEF108 follows

The service data flow filter in the rule sent by the PCRF 104 monitors the service data flow, and then executes the policy and charging rules formulated by the PCRF 104 for these service data flows. When the bearer is established, the PCEF 108 performs QoS authorization according to the rules sent by the PCRF 104, and performs gate control according to the execution of the AF. According to the charging rule sent by the PCRF 104, the PCEF 108 performs a corresponding service data flow charging operation, and the charging can be either online charging or offline charging. If it is online charging, the PCEF 108 needs to perform credit management together with the Online Charging System 112 (OCS). In the case of offline charging, the PCEF and the offline charging system 114 (OFCS) exchange relevant charging information. The interface between PCEF108 and PCRF 104 is a Gx interface, the interface with OCS 112 is a Gy interface, and the interface with OFCS 114 is a Gz interface. The PCEF 108 is usually located in a Gateway (Gate-Way, GW for short), such as a GPRS Gateway Support Node (GGSN) in GPRS and a Packet Data Gateway (PDG) in I-WLAN. Bearer Binding and Event Reporting Function (BBERF), whose functions include bearer binding, verification of uplink bearer binding, and event reporting. When the UE accesses through the E-UTRAN, and the PM-IPv6 protocol is adopted between the S-GW and the P-GW, the BBERF 106 is located at the S-GW, and when the UE accesses through the trusted non-3GPP access system, the BBERF 106 is located in the trusted non- The 3GPP access gateway, when the UE accesses through the untrusted non-3GPP access system, the BBERF 106 is located in an Evolved Packet Data Gateway (ePDG). At this time, the PCEF 108 no longer performs the bearer binding function. The User Contract Database 110 (SPR) stores user policy charging control subscription information related to policy control and charging. The interface between the SPR 110 and the PCRF 104 is an Sp interface. The online charging system 112 (OCS), together with the PCEF 108, controls and manages user credits in an online charging mode. The offline charging system 114 (OFCS), together with the PCEF 108, completes the charging operation in the offline charging mode. The above PCC architecture implements a policy plan for an IP Connectivity Access Network (IP-CAN) session established by the UE to access a Packet Data Network (PDN) through various functional entities. Fee control. In addition, the PCC also supports roaming scenarios. Figure 2 and Figure 3 show the PCC architecture in two roaming scenarios: home routing and local grooming. Referring to FIG. 2, the architecture of the home routing roaming scenario includes: The visited PCRF 202 (hereinafter referred to as V-PCRF) and the home PCRF 204 (hereinafter referred to as H-PCEF) are exchanged through the S9 interface. The visited PCRF 202 is connected to the visited BBERF 206, and the home PCRF 204 is connected to the home SPR 208, the home AF 210, and the home PCEF 212, respectively, and the home PCEF 212 is connected to the OCS 214 and the OFCS 216. Referring to FIG. 3, the architecture in the local grooming roaming scenario includes: the visited PCRF 302 and the home PCRF 304 interact through the S9 interface. The visited PCRF 302 is connected to the visited AF 306, and the visited PCRF 302 is connected to the visited BBERF 08 and the visited PCEF 310. The home PCRF 304 is connected to the home SPR 312, the home AF 314, and the home PCEF 316 respectively, and the visited PCEF 310 and the home PCEF 316 are respectively associated with the OCS 214. Connected to OFCS216. As the 3GPP network continues to evolve, the functionality of the PCC architecture continues to increase. Currently 3GPP PCC has four versions of Rel-7, Rel-8, Rel-9 and Rel-10. In each version, the PCC supports all of the required features defined in the previous version and the newly defined mandatory features in that version. In addition, each version may also support some optional features of the previous version and some of the new optional features defined in that version. This will involve a functional negotiation mechanism between PCC functional functions. Currently, the Supported-Feature AVP is used in the PCC for function negotiation. For example in Rel-10

The six values of Rel8, Rel9, RellO, ProvAFsignalFlow, IFOM, and SponsoredConnectivity are defined in the Supported-Feature AVP of the Gx interface. Rel8, Rel9, and RellO respectively represent the required features of Rel-8, Rel-9 and Rel-10, and ProvAFsignalFlow is an optional feature of Rel-9, which is used to indicate that PCEF or PCRF supports IMS Restoration IF0M, and SponsoredConnectivity is Rel. -10 optional feature, IFOM indicates that PCEF or PCRF supports IP stream migration, and SponsoredConnectivity indicates that PCEF or PCRF supports sponsored data connection Sponsored Data Connectivity. Since the Rel-7 is the basic version of the Gx interface, the PCEF does not carry the Supported-Feature in the initial Credit Control Request (CCR) message, indicating that the PCEF supports Rel-7. The Supported-Feature is not carried in the response (Credit Control Answer, CCA for short), indicating that the PCRF also supports Rel-7. In this way, the PCEF and the PCRF complete the function negotiation, and learn that the other party supports the mandatory function of the Rel-7. If the PCEF is in the initial CCR message, it carries the Supported-Feature, and the Supported-Feature values include, Rel7, Rel8, Rel9, and ProvAFsignalFlow, indicating that the PCEF supports Rel-7, Rel-8, and Rel-9. All of the required features, and also support an optional feature of Rel-9, namely IMS Restoration; if the PCRF supports the same value in the returned CCA message, the PCRF also supports Rel-7, Rel- 8, all mandatory Feature Rel9 IMS Restoration ₀ and the PCRF if the returned CCA message carries supported-Feature value of Rel7, Rel8 and Rel9, said support supports only PCRF Rel7, Rel8, All required features of Rel-9 do not support IMS Restoration. After this, the interaction of PCEF and PCRF can only be based on the required features of Rel-7, Rel-8, and Rel-9. However, the function negotiation of the Supported-Feature AVP is based on the negotiation between two functional entities (including the message carrying the Supported-Feature AVP for negotiation and not supporting the Supported-Feature AVP for negotiation). For example, for the Gx interface, it is limited to the functions of the PCEF and the PCRF itself. For those features that require multiple functional entities to support, it is not enough to negotiate the functions of two functional entities, but to negotiate the functions of multiple policy charging control functional entities involved in the IP-CAN session. That is to say, it is considered that the function of the policy control of the entire IP-CAN is negotiated. The policy charging control function entity includes a policy charging rule function entity and a policy execution function entity (for example, BBERF, PCEF). In the roaming scenario, the policy charging control function entity involved in an IP-CAN session of the user has visited PCEF (hereinafter referred to as V-PCEF), V-PCRF, and H-PCRF. If V-PCEF does not support Sponsored Data Connectivity, both V-PCRF and H-PCRF support Sponsored Data Connectivity. According to the prior art V-PCEF and V-PCRF, the value of Supported-Feature carried by V-PCEF is not Including SponsoredConnectivity, and the values of Supported-Feature of V-PCRF and H-PCRF include SponsoredConnectivity. However, when H-PCRF issues a Sponsored Data Connectivity-related strategy to V-PCRF based on the results of functional negotiation, V-PCRF However, in the prior art, the S9 interface of the S9 interface is user-level, that is, one UE has only one S9 session. When the UE establishes multiple IP-CAN sessions at the same time, S9 The session includes multiple S9 subsessions (S9 Subsession), and each subsession corresponds to one IP-CAN session. In the prior art, the functional negotiation between V-PCRF and H-PCRF is S9 session level, V-PCRF and The function between the H-PCRFs is only negotiated once (ie, negotiated when the S9 session is established), and applies to S9. All sub-sessions in the session, because the PCEFs selected by multiple IP-CAN sessions may be different, Multiple functional IP-CAN session functional entities involved are likely to be different, feature negotiation prior art can not support a user entity's functional features multiple IP-CAN session does not involve negotiation function simultaneously. SUMMARY OF THE INVENTION The present invention provides a method and system for negotiating policy and charging control function entity functions, so as to at least solve the V-PCRF and the function of the visited policy execution function entity, and the V-PCRF cannot deliver the policy to the visit. The problem of the local policy enforcement function entity. According to an aspect of the present invention, a method for negotiating a policy and a charging control function entity function is provided, including: the visited PCRF reports the visited location to the home PCRF according to the function supported by the visited function and the function supported by the visited function execution function entity. Supported functions; The home PCRF returns the function supported by the negotiation to the visited PCRF according to the functions supported by itself and the functions supported by the visited place. For each IP-CAN session, the visited PCRF performs a reporting operation, and the home PCRF performs a return operation. The visited PCRF sets the functions supported by the visited place by the following steps: The visited PCRF sets the intersection of the set of functions supported by itself and the set of functions supported by the visited policy execution function entity as functions supported by the visited place. If the policy charging control of the IP-CAN session involves more than one visited policy execution function entity, the visited PCRF sets the functions supported by the visited place by the following steps: The visited PCRF performs its own supported functions and the visited local policy execution function. The intersection of the functions supported by the entity is set to the function supported by the visited place, wherein the function supported by the visited policy execution function entity is required for the function provided by the IP-CAN session, and the visited policy execution function entity and the visited PCRF are both Supported features. The visited PCRF indicates the function supported by the home PCRF visited by including the function supported by the visited location in the S9 subsession corresponding to the IP-CAN session. The step of the home PCRF returning the function supported by the visited PCRF to the visited PCRF according to the function supported by the self and the function supported by the visited place includes: the intersection of the set of functions supported by the home PCRF and the set of functions supported by the visited place Set to the function supported after negotiation. The home PCRF indicates the function supported by the visited PCRF negotiation by including the function supported after the negotiation in the S9 sub-session corresponding to the IP-CAN session. The policy enforcement function entity includes: a visited bearer binding and event reporting function entity BBERF and/or a visited policy and charging execution function entity PCEF. The visited PCEF or the visited BBERF corresponding to different IP-CAN sessions are different. According to another aspect of the present invention, a system for policy and charging control function entity function negotiation is provided, including: a visited PCRF and a home PCRF, where: the visited PCRF is set to perform a reporting step: according to a function supported by itself And the function supported by the visited policy execution function entity reports the function supported by the visited location to the home PCRF; the home PCRF is set to perform the returning step: returning the negotiation to the visited PCRF according to the function supported by the user and the function supported by the visited place Supported features. For each IP-CAN session, the visited PCRF is set to perform a reporting step, and the home PCRF is set to perform a return step. The visited PCRF includes: a first setting unit, configured to: when the policy charging control of the IP-CAN session involves a visited policy execution function entity, the set of functions supported by the visited PCRF and the visited local policy execution function entity are supported. The intersection of the set of functions is set to the function supported by the visited place; when the policy charging control of the IP-CAN session involves more than one visited policy execution function entity, the function supported by the visited PCRF and the function of the visited place execution function are supported. The intersection of the functions is set to the function supported by the visited place, wherein the function supported by the visited policy execution function entity is required for the function provided by the IP-CAN session, and the visited policy execution function entity and the visited PCRF support Features. The visited PCRF further includes: a first indicating unit, configured to include the function supported by the visited place

The S9 sub-session corresponding to the IP-CAN session indicates the function supported by the home PCRF visited. The home PCRF includes: a second setting unit configured to set an intersection of a set of functions supported by the home PCRF and a set of functions supported by the visited place as a function supported after the negotiation. The home PCRF further includes: a second indication unit, configured to indicate a function supported after the visited PCRF negotiation by including the function supported after the negotiation in the S9 sub-session corresponding to the IP-CAN session. The policy enforcement function entity includes: a visited local BBERF and/or a visited local policy and charging enforcement function entity PCEF. The visited PCEF or the visited BBERF corresponding to different IP-CAN sessions are different. According to another aspect of the present invention, a visited location policy and a charging rule function entity PCRF is provided, including: a reporting module, configured to report to a home PCRF according to a function supported by the function and a function supported by the visited function execution function entity Visit the features supported by the place. Preferably, for each IP-CAN session, the reporting module is arranged to perform a reporting step. Preferably, the visited policy enforcement function entity comprises: a visited bearer binding and event reporting function entity BBERF and/or a visited policy and charging execution function entity PCEF. According to the present invention, the visited PCRF negotiates with the function supported by the function entity and the self-support function according to the function of the visited locality to negotiate with the function supported by the home PCRF, and solves the difference between the functions supported by the V-PCRF and the visited policy execution function entity. The V-PCRF fails to deliver the policy to the visited domain to execute the functional entity, and thus achieves the technical effect of correctly executing the policy generated by the negotiation. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the drawings: FIG. 1 is a schematic diagram of a Rel-8 PCC non-roaming architecture according to the related art; FIG. 2 is a schematic diagram of a Rel-8 PCC home routing roaming architecture according to the related art; FIG. 3 is a Rel-8 according to the related art. FIG. 4 is a schematic flowchart of a method for negotiating a policy and a charging control function entity function according to an embodiment of the present invention; FIG. 5 is a policy and charging control function according to an embodiment of the present invention; A preferred structural block diagram of a system for entity function negotiation; FIG. 6 is a first flow chart of a method for policy negotiation of a policy and charging control function entity according to an embodiment of the present invention; FIG. 7 is a policy and according to an embodiment of the present invention. A second flowchart of a method for negotiating a billing control function entity function; FIG. 8 is a third flowchart of a method for negotiating function of a policy and charging control function entity according to an embodiment of the present invention; and FIG. 9 is a diagram according to the present invention A fourth flow chart of a method for policy and charging control function entity function negotiation of an embodiment. 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. Embodiment 1 FIG. 4 is a preferred flowchart of a method for negotiating function of a policy and charging control function entity according to an embodiment of the present invention. The method includes steps S402 and S404: Step S402, the visited PCRF according to the function supported by itself And the function supported by the visited policy execution function entity reports the function supported by the visited place to the home PCRF. Preferably, the function supported by the visited PCRF to report the visited place is a set of functions. Step S404, the home PCRF visits the place according to the function supported by the home and the function supported by the visited place.

The PCRF returns the functions supported after negotiation. In the preferred embodiment, the visited PCRF negotiates the functions supported by the function entity and the self-support function according to the function of the visited-placed policy, and solves the functions supported by the V-PCRF and the visited-policy execution function entity. The problem that the V-PCRF fails to deliver the policy to the visited domain to execute the functional entity is different, and the technical effect of the correct execution of the policy generated by the negotiation is achieved. Preferably, steps S402-S404 are applied to a scenario in which the UE roams. Preferably, the foregoing roaming scenario may include: the user equipment UE initially attaches, the visited PCRF establishes a first IP-CAN session for the UE; the UE completes the initial attach, and the visited PCRF establishes at least one second IP-CAN for the UE. Conversation. In the preferred embodiment, for the first IP-CAN session and the second IP-CAN session, the visited PCRF performs a function to the home PCRF according to the function supported by itself and the function of the visited policy execution function entity. In the operation of reporting the function supported by the visited place, the home PCRF performs an operation of returning the function supported after the negotiation to the visited PCRF according to the function supported by the support and the function supported by the visited place. That is to say, for each IP-CAN session, the visited PCRF performs the reporting operation once, and the home PCRF performs the return operation once. In the preferred embodiment, since a function negotiation is performed for each IP-CAN session, it is ensured that when the UE establishes multiple IP-CAN sessions at the same time, and the functional entities involved in multiple IP-CAN sessions are different, Make the correct function negotiation. Preferably, the visited PCRF indicates the function supported by the home PCRF visited by including the function supported by the visited location in the S9 sub-session corresponding to the IP-CAN session. Of course, the present invention is not limited thereto, and other functions may be used to indicate the functions supported by the home PCRF visited. Preferably, the visited PCRF can set the function supported by the visited place by the following steps, that is, the visited PCRF sets the intersection of the set of functions supported by itself and the set of functions supported by the visited policy execution function entity to Visit the features supported by the place. Further, if the policy charging control of the IP-CAN session involves more than one visited policy execution function entity, the visited PCRF can also set the functions supported by the visited place by the following steps: The visited PCRF will support the functions and visits supported by itself. The intersection of the functions supported by the local policy enforcement function entity is set to the function supported by the visited place, wherein the function supported by the visited policy execution function entity is required for the function provided by the IP-CAN session, and the visited policy execution function entity and Visit the function supported by the PCRF. In the preferred embodiment, only the corresponding functions required for the functions provided by the IP-CAN session are interleaved, so that when the functions required for the IP-CAN session involve one or more visited policy enforcement functional entities, The report operation is performed to improve the operation efficiency and achieve correct function negotiation. That is, if the function required for the IP-CAN session involves more than one visited policy execution function entity, the visited PCRF sets the set of functions supported by itself and the required function of the visited local policy execution function entity. The intersection is set to the function supported by the visited place. For example, when the policy charging control of the IP-CAN session involves BBERF, the V-PCRF needs to comprehensively consider the functions supported by the BBERF and the PCEF when setting the function supported by the visit, that is, the set of functions supported by the visited PCRF. The intersection of the functions supported by the PCEF and the functions supported by the BBERF are set to the functions supported by the visited place; when the policy charging control of the IP-CAN session involves only the functions supported by the PCEF, the visited PCRF will The intersection of the set of functions supported by itself and the set of functions supported by the visited PCEF is set to the function supported by the visited place. Preferably, the home PCRF indicates the function supported by the visited PCRF negotiation by including the post-negotiation supported function in the S9 sub-session corresponding to the IP-CAN session. Of course, the present invention is not limited thereto, and the functions supported after the visited PCRF negotiation may be indicated by other sessions. Preferably, when the visited policy execution function entity is the visited PCEF, the step of the home PCRF returning the post-negotiation supported function to the visited PCRF according to the function supported by the home and the function supported by the visited place includes: the home PCRF supports itself The intersection of the set of functions and the set of functions supported by the visited place is set to a function supported after negotiation. In the preferred embodiment, the functions supported by the visited PCRF and the visited policy enforcement function entity and the home PCRF are guaranteed to be on the same function that can be correctly negotiated. Preferably, the foregoing policy enforcement function entity includes: a visited BBERF (bearer binding and event reporting function entity) and/or a visited PCEF (policy and charging execution function entity). In the preferred embodiment, it is guaranteed that the BBERF and/or PCEF can correctly perform the negotiated policy. Preferably, the visited PCEF or the visited BBERF corresponding to different IP-CAN sessions are different. In the preferred embodiment, it is ensured that the policy generated by the visited PCEF not being negotiated at the same time can also be correctly executed. Of course, the present invention is not limited to the difference between the visited PCEF or the visited BBERF, and the same applies when the visited PCEF or the visited BBERF are the same. Embodiment 2 FIG. 5 is a block diagram showing a preferred structure of a system for policy and charging control function entity function negotiation according to an embodiment of the present invention. According to another aspect of the present invention, a policy and charging control function entity function is provided. The negotiated system, the system includes a visited PCRF 502 and a home PCRF 504, wherein: the visited PCRF 502 is configured to perform a reporting step, that is, to the home PCRF 504 according to the functions supported by the self-supported function and the visited policy execution function entity. The function supported by the visited place is reported; the home PCRF 504 is set to perform a returning step, that is, returning the function supported by the negotiation to the visited PCRF 502 according to the function supported by itself and the function supported by the visited place. In the preferred embodiment, the visited PCRF negotiates the functions supported by the function entity and the self-support function according to the function of the visited-placed policy, and solves the functions supported by the V-PCRF and the visited-policy execution function entity. The problem that the V-PCRF fails to deliver the policy to the visited domain to execute the functional entity is different, and the technical effect of the correct execution of the policy generated by the negotiation is achieved. The visited PCRF 502 may include: a first setting unit, configured to set an intersection of a set of functions supported by the visited PCRF and a set of functions supported by the visited policy execution function entity as a function supported by the visited place (preferred And performing the step when the policy charging control of the IP-CAN session involves a visited policy execution function entity; or, when the policy charging control of the IP-CAN session involves more than one visited policy execution function entity, The intersection of the function supported by the visited PCRF and the function supported by the visited policy execution function entity is set to a function supported by the visited place, wherein the function supported by the visited policy execution function entity is required for the function provided by the IP-CAN session And the function supported by both the local policy enforcement function entity and the visited site PCRF. In the preferred embodiment, only the corresponding functions required for the functions provided by the IP-CAN session are interleaved, so that when the functions required for the IP-CAN session involve one or more visited policy enforcement functional entities, The report operation is performed to improve the operation efficiency and achieve correct function negotiation. Preferably, the visited PCRF 502 further includes: a first indication unit, configured to indicate a function supported by the home PCRF visited by including the function supported by the visited location in the S9 sub-session corresponding to the IP-CAN session. The home PCRF 504 includes: a second setting unit, configured to set an intersection of a set of functions supported by the home PCRF and a set of functions supported by the visited location as a function supported after the negotiation. Preferably, the home PCRF 504 further includes: a second indication unit, configured to indicate a function supported after the visited PCRF negotiation by including the function supported after the negotiation in the S9 sub-session corresponding to the IP-CAN session. For example: When the policy charging control of the IP-CAN session involves BBERF, the V-PCRF needs to comprehensively consider the functions supported by BBERF and PCEF when setting the function supported by the visited place, that is, the set of functions supported by the visited PCRF. The intersection of the functions supported by the PCEF and the functions supported by the BBERF are set to the functions supported by the visited place; when the policy charging control of the IP-CAN session involves only the functions supported by the PCEF, the visited PCRF will The intersection of the set of functions supported by itself and the set of functions supported by the visited PCEF is set to the function supported by the visited place. Preferably, the visited PCRF 502 and the home PCRF 504 can be applied to a scenario in which the UE roams. The foregoing roaming scenario may include multiple types, for example, the user equipment UE initially attaches, and the visited PCRF 502 establishes a first IP-CAN session for the UE; the UE completes the initial attach, and the visited PCRF 502 establishes at least one for the UE. Two IP-CAN sessions. In the preferred embodiment, for the first IP-CAN session and the second IP-CAN session, the visited PCRF 502 performs a function to the home location according to the functions supported by the client and the function of the visited policy execution function entity. The PCRF 504 reports the operation of the function supported by the visited place, and the home PCRF 504 performs an operation of returning the function supported by the negotiation to the visited PCRF 502 according to the function supported by itself and the function supported by the visited place. That is to say, for each IP-CAN session, the visited PCRF 502 performs the above-mentioned reporting operation, and the home PCRF 504 performs a return operation accordingly. In the preferred embodiment, since a function negotiation is performed for each IP-CAN session, it is ensured that when the UE establishes multiple IP-CAN sessions at the same time, and the functional entities involved in multiple IP-CAN sessions are different, Make the correct function negotiation. Preferably, the foregoing policy enforcement function entity includes: a visited BBERF (bearer binding and event reporting function entity) and/or a visited PCEF (policy and charging execution function entity). In the preferred embodiment, it is guaranteed that the BBERF and/or PCEF can correctly perform the negotiated policy. Preferably, the visited PCEF or the visited BBERF corresponding to different IP-CAN sessions are different. The implementation of the preferred embodiment ensures that the policies generated by the visited PCEFs at different times can also be correctly executed. Of course, the present invention is not limited to the case where the visited PCEF or the visited place BBERF is different, and the same applies when the visited PCEF or the visited place BBERF is the same. In the above preferred embodiment, the visited PCRF can be independently a visited policy and a charging rule function entity, and the entity includes a reporting module, and is configured to perform function-based attribution according to the functions supported by the calling function and the visited policy. The PCRF reports the functions supported by the visited place. The visited place policy execution function entity may include a visited bearer binding and event reporting function entity BBERF or a visited place policy and charging execution. The functional entity PCEF can also be a combination of the two. In the implementation process, for each IP-CAN session, the reporting module is set to perform a reporting step. Of course, the present invention is not limited to setting the visited PCRF as a separate device, and the home PCRF can be set as an independent home policy and charging rule function entity, and details are not described herein again. Embodiment 3 Referring to FIG. 6 , in a local grooming roaming scenario, when a UE initially attaches, a system for negotiating policy and charging control function entity functions includes: a visited visited PCEF1 602, a V-PCRF 604, and an H-PCRF 606, and The home SPR 608, the process of performing function negotiation between the above functional entities includes steps S601 to S608, where the IP-CAN session established by the UE does not involve the BBERF. Step S601, in the process of the initial attachment of the UE, the gateway where the PCEF1 602 is located receives the IP-CAN session establishment request message, and carries the user identifier and the PDN identifier of the PDN network requested to be accessed in the IP-CAN session establishment request message. 1. In step S602, the PCEF1 602 notifies the V-PCRF 604 that the IP-CAN session is established. The PCEF1 602 sends a CCR message to the V-PCRF 604, and the CC-Request-Type AVP in the message is set to INITIAL_REQUEST. PCEF 1 provides the V-PCRF with the user identity, the PDN identity 1 and the IP address assigned to the UE (IP Addressl). If PCEF 1 602 supports at least Rel-8, PCEF 1 602 also carries a Supported-Feature AVP in the CCR message to identify the Feature supported by PCEF1 602. For the PCEF of Rel-7, the Supported-Feature AVP is not carried in the CCR message. For example: For PCEF1 of Rel-8, the value of Supported-Feature can be Rel8; for PCEF of Rel-9, the value of Supported-Feature is (Rel8), (Rel8, Rel9) or (Rel8, Rel9, Prov AF signalF low ); For Rel-10 PCEF, the value of Supported-Feature is (Rel8, Rel9, RellO) or (Rel8, Rel9, ProvAFsignalFlow RellO) or (Rel8, Rel9, Rell0, SponsoredConnectivity) or (Rel8, Rel9, ProvAFsignalFlow Rell0, SponsoredConnectivity) or (Rel8, Rel9, Rell0, IFOM) or (Rel8, Rel9, ProvAFsignalFlow Rell0, IFOM) or (Rel8, Rel9, ProvAF signalFlo w Rell0, SponsoredConnectivity, IFOM). Step S603, the V-PCRF 604 determines that the user is a roaming user according to the user identifier. Since the initial attachment, V-PCRF 604 has not established an S9 session for the user, V-PCRF 604 sends a request message to H-PCRF 606, An S9 session is established and an S9 subsession is also requested. The specific implementation is as follows: The V-PCRF 604 sends a CCR message to the H-PCRF 606, and the CC-Request-Type AVP in the message is set to INITIAL_REQUEST. The V-PCRF 604 message includes a Subsession-Enforcement-Info AVP, and carries the Subsession-Id AVP in the AVP (the value is the identifier assigned by the V-PCRF 604 for the sub-session, identified as ID1), Subsession-Opeartion AVP ( The value is ESTABLISHMENT and the Supported-Feature AVP. The V-PCRF 604 also carries the information received in step S602, such as the user identifier, the PDN identifier 1, and the IP address 1, in the Subseson-Enforcement-Info AVP. The V-PCRF 604 will report the supported functions to the H-PCRF 606 according to the function of the V-PCRF 604 and the function reported by the PCEF1 602 (the function reported by the Supported-Feature AVP or the Supported-Feature AVP) (not carried) Supported-Feature AVP or Carryed-Feature, which is the intersection of PCEF1 602 and V-PCRF 604. For example: For Rel-8 V-PCRF, there is no Supported-Feature AVP in the message; for Rel-9 V-PCRF: If the value of Supported-Feature reported by PCEF1 is (Rel8), the V-PCRF does not carry in the message.

Supported-Feature AVP. If the value of Supported-Feature reported by PCEF1 is (Rel8, Rel9), the value of Supported-Feature set by Bayu V-PCRF is (Rel9). If the value of Supported-Feature reported by PCEF1 (Rel8, Rel9, ProvAFsignalFlow), according to the function of V-PCRF itself, the value of Supported-Feature of V-PCRF is set to (Rel9) or (Rel9, ProvAF SignalFlow); V-PCRF of Rel-10: If the value of Supported-Feature reported by PCEF1 is (Rel8), the V-PCRF does not carry the Supported-Feature AVP in the message. If the value of Supported-Feature reported by PCEF1 is (Rel8, Rel9), Bay U V-PCRF is set.

The value of Supported-Feature is (Rel9). If the value of Supported-Feature reported by PCEF1 is (Rel8, Rel9, RellO), the value of Supported-Feature of V-PCRF is set to (Rel9, Rell0). If the value of Supported-Feature reported by PCEF1 is (Rel8, Rel9, ProvAFsignalFlow RellO), the value of Supported-Feature of the Bay U V-PCRF is (Rel9, RellO) or (Rel9, ProvAF signalFlo w Rel-10). If the value of Supported-Feature reported by PCEF1 is (Rel8, Rel9, RellO, SponsoredConnectivity), then the value of Supported-Feature of V-PCRF is set to (Rel9, RellO) or (Rel9, Rell0, SponsoredConnectivity). If the value of Supported-Feature reported by PCEF1 is (Rel8, Rel9, Rell0, IFOM), the value of Supported-Feature of V-PCRF is set to (Rel9, RellO) or (Rel9, Rell0, IFOM). If the value of Supported-Feature reported by PCEF1 is (Rel8, Rel9, ProvAF SignalFlow Rell0, SponsoredConnectivity), the value of Supported-Feature of V-PCRF may be (Rel9, RellO) or (Rel9, ProvAF signalF low Rell0). , (Rel9, Rell0, SponsoredConnectivity) (Rel9, ProvAF signalF low Rell0, SponsoredConnectivity). If the value of Supported-Feature reported by PCEF1 is (Rel8, Rel9, ProvAF SignalFlow Rell0, IFOM), the value of Supported-Feature of V-PCRF may be (Rel9, RellO) or (Rel9, ProvAF signalFlo w Rell0). , (Rel9, Rell0, IFOM) (Rel9, ProvAFsignalFlow Rell0, IFOM). If the value of Supported-Feature reported by PCEF1 is (Rel8, Rel9, ProvAF SignalFlow Rell0, SponsoredConnectivity IFOM), the value of Supported-Feature of V-PCRF may be (Rel9, RellO) or (Rel9, ProvAF signalF low Rell0). ), (Rel9, Rell0, IFOM), (Rel9, ProvAFsignalFlow Rell0, IFOM), (Rel9, Rell0, SponsoredConnectivity) (Rel9, ProvAF signalF low Rell0, SponsoredConnectivity) (Rel9, ProvAF signalF low RellO, SponsoredConnectivity IFOM). Step S604: If the H-PCRF 606 determines that there is no subscription data of the user according to the user identifier, the H-PCRF 606 sends a subscription document request to the home SPR 608, and carries the user identifier and the PDN identifier 1 in the subscription document request. Step S605, the home SPR 608 returns the user subscription information (ie, the contracted document response) according to the user identifier and the PDN identifier 1. Step S606, the H-PCRF 606 formulates a policy according to the user subscription information, the network policy, the access information of the UE, and the like, and the policy includes a PCC rule, an event trigger, and the like, and the H-PCRF 606 returns the formulated to the V-PCRF 604. Strategy. The specific implementation is as follows: H-PCRF 606 sends a CCA to the V-PCRF 604, and includes a Subsession-Decision-Info AVP in the message, and carries the Subsession-Id AVP = ID1 (which is reported by the V-PCRF) in the AVP and Supported-Feature AVP. The H-PCRF 606 also carries the established PCC rules, event triggers, etc. in the Subsession-Decision-Info AVP. For the Rel-8 H-PCRF, the Supported-Feature AVP is not carried in the message. The H-PCRF 606 returns the negotiated function to the V-PCRF according to its own function and the function reported by the Supported-Feature of the V-PCRF 604 (including not including the Supported-Feature AVP or carrying the Supported-Feature value as the H-PCRF 606 and V-PCRF 604 supports the intersection of features). In step S607, the V-PCRF 604 provides the formulated policy to the PCEF 1602. The V-PCRF 604 may modify the policy delivered by the H-PCRF 606 according to the visited network policy. The specific implementation is as follows: The V-PCRF 604 sends a CCA message to the PCEF1 602, where the message carries a PCC rule and an event trigger. The V-PCRF 604 also includes a Supported-Feature AVP in the message. The value is the value returned by the H-PCRF 606 in step S606. In step S608, the PCEF1 602 installs and executes a policy, such as a PCC rule, an event trigger, and the like. The gateway where PCEF1 602 is located returns a response to establish an IP-CAN session carrying the assigned IP address (IP Addressl). Through the above process, PCEF1 602, V-PCRF 604 and H-PCRF 606 complete the function negotiation. H-PCRF

606 is aware that the feature supported by each network element involved in the first IP-CAN session established by the user can be considered as a feature supported by the IP-CAN. Embodiment 4 Referring to FIG. 7 , in a local grooming roaming scenario, when the UE performs the initial P1 connection request and then requests another PDN connection establishment request, the system for negotiating the policy and the charging control function entity function includes: The process of performing function negotiation between the above functional entities includes the step S701 to the step S708, where the UE-established IP-CAN session is not connected, where the visited PCEF2 702, the V-PCRF 704, the H-PCRF 706, and the home SPR 708 are sequentially connected. Involved in BBERF. Step S701, in the process of the UE's additional PDN connection establishment request, the gateway where the PCEF2 702 is located receives the IP-CAN session establishment request message, and carries the user identifier and the requested PDN in the IP-CAN session establishment request message. The PDN ID of the network 2. The PDN identifier 2 may or may not be the same as the PDN identifier 1. PCEF2 702 and PCEF1 602 may or may not be identical. Step S702, PCEF2 702 notifies V-PCRF 704 that the IP-CAN session is established. PCEF2 702 sends a CCR message to V-PCRF 704, and the CC-Request-Type AVP in the message is set to INITIAL_REQUEST. PCEF2 702 provides the V-PCRF 704 with a user identity, a PDN identity 2, and an IP address (IP Address2) assigned to the UE. If PCEF2 702 supports Rel-8, PCEF2 702 also carries a Supported-Feature AVP in the CCR message to identify the Feature supported by PCEF2 702. Step S703, the V-PCRF 704 determines that the user is a roaming user according to the user identifier, and has established an S9 session for the user. The V-PCRF 704 sends a request message to the H-PCRF 706, modifies the S9 session, and also requests to establish an S9 session. Conversation. The specific implementation is as follows: The V-PCRF 704 sends a CCR message to the H-PCRF 706, and the CC-Request-Type AVP in the message is set to UPDATE_REQUEST. The V-PCRF 704 message includes a Subsession-Enforcement-Info AVP, and carries the Subsession-Id AVP in the AVP (the value is the identifier assigned by the V-PCRF for the sub-session, identified as ID2), and the Subsession-Opeartion AVP (taken) The value is ESTABLISHMENT) and the Supported-Feature AVP. The V-PCRF also carries the information received in step S702, such as the user identifier, the PDN identifier 2, and the IP address 2, in the Subseson-Enforcement-Info AVP. The V-PCRF 704 will report the supported functions to the H-PCRF 606 according to the functions of the V-PCRF 704 itself and the functions reported by the PCEF2 702 (the functions not reported by the Supported-Feature AVP or the Supported-Feature AVP) (without Supported) -Feature AVP or Carry Support-Feature AVP, which is the intersection of PCEF2 702 and V-PCRF 704 support features). Step S704: If the H-PCRF 706 determines that there is no subscription data of the user according to the user identifier, the H-PCRF 706 sends a subscription document request to the home SPR 708, and carries the user identifier and the PDN identifier 2 in the subscription document request. Step S705, the home SPR 708 returns the user subscription information (ie, the contracted document response) according to the user identifier and the PDN identifier 2. Step S706: The H-PCRF 706 formulates a policy according to the user subscription information, the network policy, and the access information of the UE. The policy includes a PCC rule, an event trigger, and the like, and the H-PCRF 706 returns the formulated policy to the V-PCRF 704. Specifically, the H-PCRF 706 sends a CCA to the V-PCRF 704, and the Subsession-Decision-Info AVP is included in the message, and the Subsession-Id AVP = ID2 (which is reported by the V-PCRF) is carried in the AVP and Supported-Feature AVP. The H-PCRF also carries the established PCC rules, event triggers, etc. in the Subsession-Decision-Info AVP. For the Rel-8 H-PCRF, the Supported-Feature AVP is not carried in the message. The H-PCRF 706 returns the negotiated support to the V-PCRF according to its own function and the function reported by the V-PCRF 704 (without the Supported-Feature or the function reported by the Supported-Feature). Function (does not carry Supported-Feature AVP or carry Supported-Feature, the value is the intersection of H-PCRF 706 and V-PCRF 704 support Feature). In step S707, the V-PCRF 704 provides the formulated policy to the PCEF2 702. The V-PCRF 704 may modify the policy delivered by the H-PCRF 706 according to the visited network policy. The specific implementation is as follows: The V-PCRF 704 sends a CCA message to the PCEF2 702, where the message carries a PCC rule and an event trigger. The V-PCRF 704 also includes a Supported-Feature AVP in the message. The value is the value returned by the H-PCRF 706 in step S706. In step S708, the PCEF2 702 installs and executes a policy, such as a PCC rule, an event trigger, and the like. The gateway where PCEF2 702 is located returns a response to establish an IP-CAN session, carrying the assigned IP address 2. Through the above process, PCEF2 702, V-PCRF 704 and H-PCRF 706 complete the function negotiation. The H-PCRF 706 learns the features supported by the various network elements involved in the second IP-CAN session established by the user, and can be considered as the feature supported by the IP-CAN. This procedure is also applicable to the functional negotiation of visited PCEF, V-PCRF and H-PCRF when establishing more than two IP-CAN sessions. Embodiment 5 Referring to FIG. 8, in a local grooming roaming scenario, when a UE initially attaches, a system for negotiating policy and charging control function entity functions includes: a visited BBERF1 800, a visited PCEF1 802, and a sequentially connected V-PCRF 804. And the H-PCRF 806 and the home SPR 808, wherein the visited BBERF1 800 is connected to the visited PCEF2 802 and the V-PCRF 804, and the visited PCEF2 802 is connected to the V-PCRF 804, and the function negotiation process between the above functional entities is performed. Step S801 to step S814 are included, wherein the IP-CAN session established by the UE involves BBERF. Step S801, in the process of the initial attachment of the UE, the gateway where the BBERF1 800 is located receives the IP-CAN session establishment request message, and carries the user identifier and the PDN identifier of the PDN network requested to be accessed in the IP-CAN session establishment request message. 1. Step S802, the BBERF1 800 notifies the V-PCRF 804 that the gateway controls session establishment. The BBERFl 800 sends a CCR message to the V-PCRF 804, and the CC-Request-Type AVP in the message is set to INITIAL_REQUEST. The BBERFl 800 provides the user identification, PDN identification 1, to the V-PCRF 804. If the BBERFl 800 supports at least Rel-9, the BBERFl 800 also carries a Supported-Feature AVP in the CCR message to identify the Feature supported by the BBERFl 800. For the BBERF of Rel-8, the Supported-Feature AVP is not carried in the CCR message. For example: For Rel-9 BBERF, the value of Supported-Feature is (Rel9). Step S803, the V-PCRF 804 determines that the user is a roaming user according to the user identifier. Since it is the initial attachment, V-PCRF 804 has not yet established an S9 session for the user, V-PCRF 804 sends a request message to H-PCRF 806, establishes an S9 session, and also requests to establish an S9 subsession. The specific implementation is as follows: The V-PCRF 804 sends a CCR message to the H-PCRF 806, and the CC-Request-Type AVP in the message is set to INITIAL_REQUEST. The V-PCRF 804 message includes a Subsession-Enforcement-Info AVP, and carries the Subsession-Id AVP in the AVP (the value is the identifier assigned by the V-PCRF 604 for the sub-session, identified as ID1), Subsession-Opeartion AVP ( The value is ESTABLISHMENT and the Supported-Feature AVP. The V-PCRF 804 also carries the information received in step S802, such as the user identity and the PDN identity 1, in the Subseson-Enforcement-Info AVP. The V-PCRF 804 will report the supported functions to the H-PCRF 806 according to the functions supported by the V-PCRF 804 and the support functions reported by the BBERF1 800 (the functions not reported by the Supported-Feature AVP or the Supported-Feature AVP). (Do not carry Supported-Feature or carry Supported-Feature, which is the intersection of BBERF1 800 and V-PCRF 804 to support Feature). Step S804, if the H-PCRF 806 determines that there is no subscription data of the user according to the user identifier,

The H-PCRF 806 sends a subscription document request to the home SPR 808, and carries the subscriber identity and the PDN identity 1 in the subscription document request. Step S805, the home SPR 808 returns the user subscription information (ie, the contracted document response) according to the user identifier and the PDN identifier 1. Step S806, the H-PCRF 806 formulates a policy according to the user subscription information, the network policy, and the access information of the UE, and the policy includes a PCC rule, a QoS rule, an event trigger, etc., and the H-PCRF 806 returns to the V-PCRF 804. Strategy. The specific implementation is as follows: The H-PCRF 806 sends a CCA to the V-PCRF 804, and the Subsession-Decision-Info AVP is included in the message, and the Subsession-Id AVP = ID 1 is carried in the AVP (the value is reported by the V-PCRF) And Supported-Feature AVP. The H-PCRF 806 also carries the established PCC rules, event triggers, etc. in the Subsession-Decision-Info AVP. For the Rel-8 H-PCRF, the Supported-Feature AVP is not carried in the message. The H-PCRF 806 returns the function supported by the negotiation to the V-PCRF 806 according to its own function and the function supported by the V-PCRF 804 (without the Supported-Feature AVP or the function reported by the Supported-Feature) (without Supported) -Feature or carry Supported-Feature, the value is H-PCRF 806 and P V-PCRF 804 supports the intersection of Feature). In step S807, the V-PCRF 804 provides the formulated policy to the BBERF1 800. The V-PCRF 804 may modify the policy delivered by the H-PCRF 806 according to the visited network policy. The specific implementation is as follows: The V-PCRF 804 sends a CCA message to the BBERF1 800, where the message carries a QoS rule and an event trigger. V-PCRF 804 also includes a Supported-Feature AVP in the message. The above value is the value returned by the H-PCRF 806 in step S806. Step S808, the gateway where the BBERF1 800 is located sends a request to the gateway where the PCEF1 802 is located.

IP-CAN session message, carrying user ID, PDN ID 1, etc. In step S809, the PCEF1 802 notifies the V-PCRF 804 that the IP-CAN session is established. PCEF 1 802 sends a CCR message to V-PCRF 804, and the CC-Request-Type AVP in the message is set to INITIAL_REQUEST. PCEF 1 provides the V-PCRF with the user identity, the PDN identity 1 and the IP address assigned to the UE (IP Addressl). If PCEF1 802 supports at least Rel-8, PCEF1 802 also carries a Supported-Feature AVP in the CCR message to identify the Feature supported by PCEF1 802. For the PCEF of Rel-8, the Supported-Feature AVP is not carried in the message. Step S810, the V-PCRF associates the message of step S802 and step S809 according to the user identifier and the PDN identifier, that is, the gateway control session requested to be established in step S802 is associated with the Gx session requested by S809, and then the Gx session is established with step S803. The S9 session is associated with the S9 subsession. The V-PCRF 804 sends a request message to the H-PCRF 806, modifies the S9 session, and also requests modification of an S9 subsession. The specific implementation is as follows: The V-PCRF 804 sends a credit control request CCR (Credit Control Request) message to the H-PCRF 806, and the CC-Request-Type AVP in the message is set to UPDATE_REQUEST. The V-PCRF 804 message includes a Subsession-Enforcement-Info AVP, and carries the Subsession-Id AVP (valued ID1), Subsession-Opeartion AVP (the value is MODIFICATIONS V-PCRF 804 and also in Subseson-Enforcement). The information received in step S802, such as the user identifier, the PDN identifier 1 and the IP address 1, etc., wherein the V-PCRF 804 will be based on the function of the V-PCRF 804 itself, the support function reported by the BBERF1 800, and the PCEF1 802. The supported functions (without the Supported-Feature AVP or the function reported by the Supported-Feature AVP) are used to report the supported functions to the H-PCRF 806 (without the Supported-Feature AVP or the Supported-Feature AVP). For those who need BBERF The functions supported by PCEF, the value of Supported-Feature is the intersection of the support functions of BBERF1 800, PCEF 802 and V-PCRF 804. For those functions that only need PCEF support, the value of Supported-Feature is PCEF 802 and V-. The intersection of the functions is supported by the PCRF 804. Since the policy charging control for the IP-CAN session involves BBERF, the V-PCRF needs to be comprehensively tested when setting the functions supported by the visited place. BBERF PCEF and support functions. For those who need BBERF, The functions supported by PCEF, the value of Supported-Feature is the intersection of BBERF, PCEF (V-PCEF) and V-PCRF support functions. For those functions that only need PCEF support, the value of Supported-Feature is PCEF and V-. The intersection of the PCRF support functions. It can be further understood that the functions supported by the visit are the intersection of the functions supported by the function execution function entities required by the functions and functions supported by the V-PCRF. If the V-PCRF 804 finds that the value of the Supported-Feature is different from the value reported in the step S803, the V-PCRF 804 includes the new Supported-Feature in the Subsession-Enforcement-Info AVP and the H-PCRF 806. Negotiation function. For example: For Rel-9 optional feature IMS Restoration, BBERF is not affected, ie IMS Restoration only requires PCEF support. For the function of Rel-10, whether it is optional or mandatory, it does not affect BBERF, that is, the function of Rel-10 only needs PCEF support. If the value of the Supported-Feature reported by the BBERF is (Rel9) and the value of the Supported-Feauter reported by the PCEF is (Rel9, Rel 10), then the value of the Suppoted-Feature reported by the V-PCRF to the H-PCRF is (Rel9, Rell0). In step S811, the H-PCRF 806 returns the established policy to the V-PCRF 804. Specifically, the H-PCRF 806 sends a CCA to the V-PCRF 804, and the Subsession-Decision-Info AVP is included in the message, and the Subsession-Id AVP=ID1 (which is reported by the V-PCRF) is carried in the AVP and Supported-Feature AVP. The H-PCRF 806 also carries the established PCC rules, event triggers, etc. in the Subsession-Decision-Info AVP. The H-PCRF 806 returns the function supported by the negotiation to the V-PCRF 804 according to the support function and the support function reported by the V-PCRF 804 (the function reported by the Supported-Feature) (with Supported-Feature, the value is H- The PCRF 806 supports the intersection of functions and V-PCRF 804 reporting support functions). In step S812, the V-PCRF 804 provides the formulated policy to the PCEF1 802. The V-PCRF 804 may modify the policy delivered by the H-PCRF 806 according to the visited network policy. The specific implementation is as follows: The V-PCRF 804 sends a CCA message to the PCEF1 802, where the message carries a PCC rule and an event trigger. V-PCRF 804 also includes a Supported-Feature AVP in the message. The value is the value returned by the H-PCRF 806 in step S811. In step S813, the PCEF1 802 installs and executes a policy, such as a PCC rule, an event trigger, and the like. The gateway where PCEF1 802 is located returns a response to the gateway where the BBERF1 800 is located to establish an IP-CAN session, carrying the assigned IP address (IP Addressl). Step S814, the gateway where the BBERF1 800 is located answers the establishment of the IP-CAN session, and carries the assigned IP address (IP Addressl). Through the above process, BBERF1 800, PCEF1 802, V-PCRF 804 and H-PCRF 806 complete the function negotiation. The H-PCRF 806 is aware of the features supported by the various network elements involved in the first IP-CAN session established by the user, and can be considered as the feature supported by the IP-CAN policy charging control. Embodiment 6 Referring to FIG. 9, in a local grooming roaming scenario, the system for negotiating the function of the policy and charging control function entity when the UE completes the initial P1 connection request after the initial attachment is completed as shown in FIG. Visiting the BBERF2 900, visiting the PCEF2 902, and sequentially connecting the V-PCRF 904 and the P H-PCRF 906 and the attribution SPR 908, wherein the visited BBERF2 900 is connected to the visited PCEF2 902 and the V-PCRF 904, The visited PCEF2 902 is connected to the V-PCRF 904. The process of function negotiation between the above functional entities includes steps S901 to S914, where the IP-CAN session established by the UE involves the BBERF. Step S901, in the process of the UE performing another PDN connection establishment request, the gateway where the BBERF2 900 is located receives the IP-CAN session establishment request message, and carries the user identifier and the PDN requested to be accessed in the IP-CAN session establishment request message. The PDN ID of the network 2. The PDN ID 2 may or may not be the same as the PDN ID 1. In a multiple access scenario, BBERF1 and BBERF2 are different. Step S902, the BBERF2 900 notifies the V-PCRF 904 that the gateway controls session establishment. The BBERF2 900 sends a CCR message to the V-PCRF 904, and the CC-Request-Type AVP in the message is set to INITIAL REQUESTo. The BBERF2 900 provides the V-PCRF with the user identity and the PDN identity 2. If the BBERF2 900 supports at least Rel-9, the BBERF2 900 also carries a Supported-Feature AVP in the CCR message to identify the functions supported by the BBERF2 900. For the BBERF of Rel-8, the Supported-Feature AVP is not carried in the CCR message. For example: For Rel-9 BBERF, the value of Supported-Feature is (Rel9). Step S903, the V-PCRF 904 determines that the user is a roaming user according to the user identifier, and has established an S9 session for the user, and the V-PCRF 904 sends a request message to the H-PCRF 906 to modify the S9 session, and also requests to establish an S9 sub-item. Conversation. The specific implementation is as follows: The V-PCRF 904 sends a CCR message to the H-PCRF 906, and the CC-Request-Type AVP in the message is set to UPDATE_REQUEST. The V-PCRF 904 message includes a Subsession-Enforcement-Info AVP, and carries the Subsession-Id AVP in the AVP (the value is the identifier assigned by the V-PCRF for the sub-session, identified as ID2), Subsession-Opeartion AVP (taken The value is ESTABLISHMENT) and the Supported-Feature AVP. V-PCRF will also be in The Subseson-Enforcement-Info AVP carries the information received in step S902, such as the user identifier and the DN identifier 2. The V-PCRF 904 will report the supported functions to the H-PCRF 906 according to the functions supported by the V-PCRF 904 and the support functions reported by the BBERF2 900 (the functions not reported by the Supported-Feature AVP or the Supported-Feature AVP). (Do not carry Supported-Feature or carry Supported-Feature, which is the intersection of BBERF2 900 and V-PCRF 904 support Feature). Since the policy charging control for the IP-CAN session involves BBERF, the V-PCRF needs to comprehensively consider the functions supported by the BBERF and PCEF when setting the function supported by the visit. For those functions that require BBERF and PCEF support, the value of Supported-Feature is the intersection of BBERF, PCEF and V-PCRF support functions. For those functions that only require PCEF support, the value of Supported-Feature is PCEF and V-. The intersection of the PCRF support functions. It can be further understood that the functions supported by the visit are the intersection of the functions supported by the function execution function entities required by the functions and functions supported by the V-PCRF. Step S904, if the H-PCRF 906 determines that there is no subscription data of the user according to the user identifier, the H-PCRF 906 sends a subscription document request to the home SPR 908, and carries the user identifier and the PDN identifier 2 in the subscription document request. In step S905, the home SPR 908 returns the user subscription information (ie, the contracted document response) according to the user identifier and the PDN identifier 2. Step S906, the H-PCRF 906 formulates a policy according to the user subscription information, the network policy, and the access information of the UE, and the policy includes a PCC rule, a QoS rule, an event trigger, etc., and the H-PCRF 906 returns to the V-PCRF 904. Strategy. Specifically, the H-PCRF 906 sends a CCA to the V-PCRF 904, and the Subsession-Decision-Info AVP is included in the message, and the Subsession-Id AVP = ID2 (which is reported by the V-PCRF) is carried in the AVP and Supported-Feature AVP. The H-PCRF 906 also carries the established PCC rules, event triggers, etc. in the Subsession-Decision-Info AVP. For the Rel-8 H-PCRF, the Supported-Feature AVP is not carried in the message. The H-PCRF 906 returns the function supported by the negotiation to the V-PCRF 906 according to its own support function and the function supported by the V-PCRF 904 (without the Supported-Feature AVP or the function reported by the Supported-Feature) (without Supported) -Feature or carry Supported-Feature, the value is the intersection of H-PCRF 906 and V-PCRF 904 support Feature). In step S907, the V-PCRF 904 provides the formulated policy to the BBERF2 900. The V-PCRF 904 may modify the policy delivered by the H-PCRF 906 according to the visited network policy. The specific implementation is as follows: The V-PCRF 904 sends a CCA message to the BBERF2 900, where the message carries a QoS rule and an event trigger. V-PCRF 904 also includes a Supported-Feature AVP in the message. The value is the value returned by the H-PCRF 906 in step S906. Step S908, the gateway where the BBERF2 900 is located sends a request to the gateway where the PCEF2 902 is located.

IP-CAN session message, carrying user ID, PDN ID 2, etc. In step S909, the PCEF2 902 notifies the V-PCRF 904 that the IP-CAN session is established. PCEF2 902 sends a CCR message to V-PCRF 904, and the CC-Request-Type AVP in the message is set to INITIAL_REQUEST. PCEF2 902 provides the V-PCRF with the user identity, the PDN identity 2, and the IP address (IP Address2) assigned to the UE. If PCEF2 902 supports at least Rel-8, PCEF2 902 also carries a Supported-Feature AVP in the CCR message to identify the Feature supported by PCEF2 902. For the PCEF of Rel-8, the Supported-Feature AVP is not carried in the message. In step S910, the V-PCRF 904 associates the message of step S902 and step S909 according to the user identifier and the PDN identifier, that is, the gateway control session requested to be established in step S902 is associated with the Gx session requested by S909, and then the Gx session is stepped with step S903. The established S9 session is associated with the S9 subsession. The V-PCRF 904 sends a request message to the H-PCRF 906, modifies the S9 session, and also requests modification of an S9 subsession. The specific implementation is as follows: The V-PCRF 904 sends a CCR message to the H-PCRF 906, and the CC-Request-Type AVP in the message is set to UPDATE_REQUEST. The V-PCRF 904 message contains the Subsession-Enforcement-Info AVP, and carries the Subsession-Id AVP (valued ID2), Subsession-Opeartion AVP (the value is MODIFICATIONS V-PCRF 904 and also in Subseson-Enforcement). The -Info AVP carries the information received in step S902, such as the user identifier, the PDN identifier 2, the IP address 2, etc. The V-PCRF 904 will be based on the functions supported by the V-PCRF 904, the support function reported by the BBERF2 900, and the PCEF2. The 902 reports the supported functions (without the Supported-Feature AVP or the function reported by the Supported-Feature AVP) to report the supported functions to the H-PCRF 906 (without the Supported-Feature AVP or the Supported-Feature AVP). The functions supported by BBERF and PCEF, the value of Supported-Feature is the intersection of BBERF2 900, PCEF2 902 and V-PCRF 904. For those functions that only require PCEF support, the value of Supported-Feature is PCEF2 902 and V. - The intersection of the functions is supported by the PCRF 904. If the V-PCRF 904 finds that the value of the Supported-Feature is different from the value reported in the step S903, the V-PCRF 904 will The Supported-Feature included in Subsession-Enforcement-Info AVP re-negotiation with the H-PCRF 906. For example: For Rel-9 optional feature IMS Restoration, BBERF is not affected, ie IMS Restoration only requires PCEF support. For the function of Rel-10, whether it is optional or mandatory, it does not affect BBERF, that is, the function of Rel-10 only needs PCEF support. If the value of the Supported-Feature reported by the BBERF is (Rel9) and the value of the Supported-Feauter reported by the PCEF is (Rel9, RellO), then the value of the Supported-Feature reported by the V-PCRF to the H-PCRF is (Rel9, RellO). ). In step S911, the H-PCRF 906 returns the established policy to the V-PCRF 904. The implementation is as follows: The H-PCRF 906 sends a CCA to the V-PCRF 904, and the Subsession-Decision-Info AVP is included in the message, and the Subsession-Id AVP=ID2 (which is reported by the V-PCRF) is carried in the AVP and Supported-Feature AVP. The H-PCRF 906 also carries the established PCC rules, event triggers, etc. in the Subsession-Decision-Info AVP. The H-PCRF 906 returns the function supported by the negotiation to the V-PCRF 904 according to the support function and the support function reported by the V-PCRF 904 (the function reported by the Supported-Feature) (with Supported-Feature, the value is H- The PCRF 906 supports the intersection of the function and the V-PCRF 904 reporting support function). In step S912, the V-PCRF 904 provides the formulated policy to the PCEF2 902. The V-PCRF 904 may modify the policy delivered by the H-PCRF 906 according to the visited network policy. The specific implementation is as follows: The V-PCRF 904 sends a CCA message to the PCEF2 902, where the message carries a PCC rule and an event trigger. V-PCRF 904 also includes a Supported-Feature AVP in the message. The above value is the value returned by the H-PCRF 906 in step S911. In step S913, the PCEF2 902 installs and executes a policy, such as a PCC rule, an event trigger, and the like. The gateway where PCEF2 902 is located returns a response to the gateway where the BBERF2 900 is located to establish an IP-CAN session, carrying the assigned IP address (IP Address2). o Step S914, the gateway where the BBER2F 900 is located responds to establish an IP-CAN session, carrying the assigned IP address (IP Address2). . Through the above process, BBERF2 900 PCEF2 902, V-PCRF 904 and H-PCRF 906 complete the function negotiation. The H-PCRF 906 knows the functions supported by the various network elements involved in the second IP-CAN session established by the user, and can be considered as the function supported by the IP-CAN policy charging control. As can be seen from the above description, the present invention achieves the following technical effects: With the present invention, the visited PCRF negotiates with the function supported by the function entity and the self-support function according to the visited local policy to negotiate with the function supported by the PCRF itself. The V-PCRF and the visited local policy enforcement function entity support different functions, which causes the V-PCRF to fail to deliver the policy to the visited local policy execution function entity, thereby achieving the technical effect of correctly executing the policy generated by the negotiation. 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.

Claims

Claim

A method for negotiating a policy and a charging control function entity function, including:

The visited policy and charging rule function entity PCRF reports the function supported by the visited place to the home PCRF according to the function supported by the function and the function supported by the visited function execution function entity; the home PCRF is based on the function supported by the home The function supported by the visited place returns the function supported by the negotiation to the visited PCRF.

The method according to claim 1, wherein, for each IP-CAN session, the visited PCRF performs the reporting operation once, and the home PCRF performs the returning operation once.

3. The method according to claim 1, wherein the visited PCRF sets the functions supported by the visited place by the following steps:

The visited location PCRF sets the intersection of the set of functions supported by itself and the set of functions supported by the visited policy execution function entity to the functions supported by the visited place.

The method according to claim 1, wherein, if the policy charging control of the IP-CAN session involves more than one of the visited policy execution function entities, the visited PCRF sets the visited place by the following steps: Supported features:

The visitor PCRF sets the intersection of the function supported by the visitor and the function supported by the visited policy execution function entity to the function supported by the visited place, wherein the function supported by the visited policy execution function entity is the IP - The functions required by the functions provided by the CAN session and supported by the visited policy enforcement function entity and the visited PCRF.

The method according to any one of claims 1 to 4, wherein the visited PCRF indicates the home PCRF by including the function supported by the visited location in an S9 subsession corresponding to the IP-CAN session. The functions supported by the visited place.

The method according to claim 1, wherein the step of the home PCRF returning the function supported by the negotiation to the visited PCRF according to the function supported by the UE and the function supported by the visited location includes:

The home PCRF sets an intersection of a set of functions supported by itself and a set of functions supported by the visited place as the function supported after the negotiation.

The method according to claim 1, 2, 3, 4 or 6, wherein the home PCRF indicates the visited location by including the post-negotiation supported function in an S9 subsession corresponding to the IP-CAN session The function supported by the PCRF after negotiation.

The method according to any one of claims 1 to 4, wherein the policy enforcement function entity comprises: a visited bearer binding and event reporting function entity BBERF and/or a visited policy and a charging execution function entity PCEF.

9. The method of claim 8, wherein the visited PCEF or visited BBERF corresponding to different IP-CAN sessions are different.

10. A system for negotiating policy and charging control function entity functions, comprising: a visited policy and a charging rule, a functional entity, a PCRF, and a home policy and charging rule function entity, PCRF, where:

The visited PCRF is configured to perform a reporting step: reporting the function supported by the visited place to the home PCRF according to the function supported by the function and the function supported by the visited function execution function entity; the home PCRF is set to perform the returning step : returning the post-negotiation supported function to the visited PCRF according to the function supported by itself and the function supported by the visited place.

The system according to claim 10, wherein, for each IP-CAN session, the visited PCRF is set to perform the reporting step once, and the home PCRF is set to perform the returning step once.

12. The system according to claim 10, wherein the visited location PCRF comprises:

a first setting unit, configured to set an intersection of a set of functions supported by the visited PCRF and a set of functions supported by the visited policy execution function entity as a function supported by the visited place; or, when IP- When the policy charging control of the CAN session involves more than one of the visited policy execution function entities, the intersection of the function supported by the visited PCRF and the function supported by the visited policy execution function entity is set to be supported by the visited place. The function, wherein the function supported by the visited policy execution function entity is a function required by the function provided by the IP-CAN session, and the visited policy execution function entity and the visited PCRF support.

The system according to any one of claims 10 to 12, wherein the visited PCRF further comprises: a first indication unit, configured to include the function supported by the visited place in an IP-CAN session The corresponding S9 sub-session indicates the function supported by the visited location of the home PCRF.

The system according to claim 10, wherein the attribution PCRF comprises: The second setting unit is configured to set an intersection of the set of functions supported by the home PCRF and the set of functions supported by the visited place as the post-negotiation supported function.

The system according to any one of claims 10 to 12, wherein the home PCRF further comprises: a second indication unit, configured to include the function supported by the negotiation in an IP-CAN session The S9 subsession is used to indicate the post-negotiation supported functionality of the visited PCRF.

The system according to claim 10 or 11, wherein the policy enforcement function entity comprises: a visited bearer binding and event reporting function entity BBERF and/or a visited policy and charging execution function entity PCEF.

17. The system of claim 13, wherein the visited PCEF or visited BBERF corresponding to different IP-CAN sessions are different.

18. A visitor policy and charging rule function entity PCRF, comprising:

The reporting module is configured to report the function supported by the visited place to the home PCRF according to the function supported by the function and the function supported by the visited function execution function entity.

19. The visitor PCRF of claim 18, wherein, for each IP-CAN session, the reporting module is configured to perform the reporting step once.

The visitor PCRF according to claim 18 or 19, wherein the visited policy execution function entity comprises: a visited bearer binding and event reporting function entity BBERF and/or a visited policy and a charging execution function entity PCEF.