WO2009021466A1

WO2009021466A1 - A method, device and system for associating policy and charging enforcement functions

Info

Publication number: WO2009021466A1
Application number: PCT/CN2008/072012
Authority: WO
Inventors: Wei Zhang; Liang Gu; Xianhui He
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-08-15
Filing date: 2008-08-15
Publication date: 2009-02-19

Abstract

A method, device and system for associating Policy and Charging Enforcement Functions, to realize to establish the association relationship among different PCEFs belonging to the same session. The method includes: an association entity acquires information about each Policy and Charging Enforcement Function serving the same session (S1), and establishes the association relationship among different PCEFs serving the session (S2). The association entity includes a acquiring unit and a PCEF associating unit. The system includes the association entity and each PCEF.

Description

Method, device and system for associating strategy and charging execution function entity

The present invention relates to the field of communications, and in particular, to a method, apparatus, and system for an association policy and a charging execution function entity.

Background technique

First, WiMAX ( Worldwide Interoperability for Microwave Access), the Chinese name is global access to microwave interoperability, is a wireless metropolitan area network technology.

See Figure 1 for the WiMAX network structure diagram. The WiMAX network is mainly composed of three parts, namely, mobile terminal (Mobile Station MS/SS); access service network (ASN), which includes a base station (Base Station BS) and an access service network gateway (ASN Gateway ASN GW). And a Connectivity Service Network (CSN), which includes a logical function entity (PF), an authentication, authorization and accounting server (AAA Server), an application function entity (AF), and the like. The R1 interface is a wireless air interface and is mainly defined by IEEE802.16d/e.

See Figure 2 for the latest QoS framework for the WiMAX NWG standard.

The description of each functional entity in this framework is as follows:

MS is a mobile terminal;

The SFM is a service flow management entity, which is responsible for establishing a user service flow and allocating wireless resources to the service flow. The function body exists in the ASN;

The SFA is a service flow authorization entity and is responsible for authorizing the corresponding service flow. This function exists in the ASN.

The PF is a policy function entity that provides a policy for a user service flow. This function exists in the NSP. In the roaming scenario, there will be a Visited PF (visit policy function entity) and a Home PF (home policy function entity). ;

The AAA server is a system that provides authentication, authorization, and accounting services, and is responsible for preserving user QoS. Profile and related policy rules;

AF is an application function entity. The mobile terminal SS directly accesses the AF through the application layer protocol. The AF will notify the PF to actively create a service flow for the user. This function exists in the NSP.

2. The PCC framework is a generic policy control and charging control functional framework defined by 3GPP R7 that is suitable for various IP connection access networks. The policy control includes Gating Control and QoS Control; billing control refers to Flow Based Charging (FBC). The structure of the PCC frame is shown in Figure 3.

The main concepts in this framework are described below:

Policy Control and Charging Rules Function (PCRF), used for policy control decisions and flow-based billing-based control.

The Policy Control and Charging Enforcement Function (PCEF) is used for service data flow detection, policy enforcement, and flow-based billing-based execution.

SPR: Subscription Profile Repository, the subscription information database, the functional entity provides user subscription data to the PCRF.

AF: The Application Function applies a function entity. The function entity dynamically provides session information of the application layer to the PCRF. The PCRF dynamically generates or modifies the corresponding rule according to the information.

OCS: Online Charging System, online billing system, mainly to achieve online billing and authentication.

OFCS: Offline Charging System, an offline charging system that mainly performs offline charging. PCC Rule: Used to assign a service data stream to an IP CAN (IP Connectivity Access Network) bearer. Its contents include:

Refer to Rule ID;

• Service data flow detection information (Priority Precedence, business data detection template

Service data flow template ) ;

• Billing information (Charging Key, Charging method, Strategy method, Application layer billing information Application) Function Record Information, Service identifier level reporting );

• Policy control information (gate status, authorized Authorized QoS,

UL-bitrate, uplink and downlink rate DL-bitrate).

III. WiMAX Convergence The network architecture after the PCC architecture is shown in Figure 4. The Policy Distribution Function (PDF) is a logical entity that facilitates convergence with the 3GPP/2 PCC architecture. It has the following characteristics: It is connected to the PCRF through the Gx interface, and the Gx interface is terminated in PDF for the PCRF; PDF blocks the PCC policy enforcement point (policy and charging execution function entity) in the WiMAX network from the PCRF; PCEF mobility; PDF uses PCC The -R3 interface is connected to the ASN's Anchor SFA (an anchored service flow licensor) that supports SFA migration; PDF is the distribution point for PCC rules and is responsible for distributing PCC Rules to the PCEF. It forwards the message between A-PCEF and PCRF and the message between C-PCEF and PCRF. The physical location of the PDF in the CSN depends on the implementation choice.

During the process of the invention, the inventors found that there is no association between different PCEFs under the same IP CAN Session (IP connection session), for example: A-PCEF and C-PCEF are used simultaneously for the same IP CAN Session. Scene, and there is no relationship between A-PCEF and C-PCEF.

Summary of the invention

The embodiments of the present invention provide a method, a device, and a system for associating a policy and a charging execution function entity, so as to establish an association relationship between different PCEFs in the same session.

The method of the embodiment of the present invention includes: the associated entity acquires information of each policy and the fee execution function entity PCEF serving the same session; and the associated entity establishes an association relationship of different PCEFs serving the session.

The associated entity of the embodiment of the present invention includes: an obtaining unit, configured to acquire information about each PCEF serving the same session; and a PCEF association unit, configured to establish an association relationship of different PCEFs serving the session.

The system of the embodiment of the present invention includes: an associated entity, and each PCEF serving the same session; And an associated entity, configured to acquire information about the PCEFs serving the same session, and establish an association relationship between the PCEFs.

In the method, the device and the system of the embodiment of the present invention, the associated entity obtains the information of each policy and charging execution function entity PCEF serving the same session, and the associated entity establishes the association relationship of different PCEFs serving the session. Thereby, the relationship between different PCEFs under the same session is established.

DRAWINGS

Figure 1 is a structural diagram of an existing WiMAX network;

Figure 2 shows the latest QoS framework of the existing WiMAX NWG standard;

Figure 3 is a structural diagram of an existing PCC frame;

Figure 4 is a network architecture diagram of the existing WiMAX converged PCC architecture;

FIG. 5 is a flowchart of steps of a method according to an embodiment of the present invention;

6 is a schematic diagram of associating PCEFs in a manner in which an associated entity is located in a PDF, and a maintenance interface session is used in an embodiment of the present invention;

FIG. 7 is a schematic diagram of a method for associating PCEFs in a manner that maintains an interface session by using an associated entity in the PCRF as an example;

FIG. 8 is a schematic structural diagram of an associated entity 1 according to an embodiment of the present invention;

FIG. 9 is a schematic structural diagram of an associated entity 2 according to an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of an associated entity 3 according to an embodiment of the present invention;

11 is a schematic diagram of a system for associating a policy and a charging execution function entity according to an embodiment of the present invention; FIG. 12 is a schematic diagram of an application scenario 1 according to an embodiment of the present invention;

FIG. 13 is a schematic diagram of an application scenario 2 according to an embodiment of the present invention;

FIG. 14 is a schematic diagram of an application scenario 3 according to an embodiment of the present invention;

FIG. 15 is a schematic diagram of an application scenario 4 according to an embodiment of the present invention;

FIG. 16 is a schematic diagram of an application scenario 5 according to an embodiment of the present invention;

Figure 17 is a flowchart of Embodiment 1 of the present invention; Figure 18 is a flowchart of Embodiment 2 of the present invention;

Figure 19 is a flow chart of Embodiment 3 of the present invention;

Figure 20 is a first schematic view of Embodiment 5 of the present invention;

Figure 21 is a flowchart of Embodiment 6 of the present invention;

Figure 22 is a flowchart of Embodiment 7 of the present invention;

Figure 23 is a second schematic view of Embodiment 5 of the present invention;

Figure 24 is a flow chart for releasing an IP session when the associated entity is located in the PDF;

Figure 25 is a flow chart showing the release of an IP session when the associated entity is located in the PCRF.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

In order to establish an association relationship between different PCEFs in the same session, the embodiment of the present invention provides a method for associating a policy and a charging execution function entity, as shown in FIG. 5, including the following main steps:

Sl, the associated entity obtains information about each policy and charging execution function entity PCEF serving the same session.

The associated entity in the embodiment of the present invention may be located in a PDF, a V-PCRF (a visited policy control and a charging rule function entity) or an H-PCRF (a home policy control and charging rule function entity).

In this step, the related entity obtains each PCEF information, including:

The information about the A-PCEF is obtained by the A-PCEF in the process of initiating the rule configuration request of the session in the access service network A-PCEF; the A-PCEF information carries the identifier information; The identification information includes: one or more of a PCEF identifier, a PCEF address, or a PCEF type. According to the rule configuration request initiated by the A-PCEF for the session, the associated entity is from an allocating entity connecting the service network C-PCEF (the allocation entity includes but is not limited to: C-PCEF authentication The billing AAA server, or the C-PCEF home contract server HSS, or the C-PCEF subscription information database SPR) obtains the C-PCEF information. The information of the C-PCEF carries the identifier information; the identifier information includes one or more of a PCEF identifier, a PCEF address, or a PCEF type.

Case 12: The A-PCEF is assigned from the C-PCEF in the authentication process (the assignment entity includes but is not limited to: C-PCEF authentication authentication accounting AAA server, or C-PCEF home registration server) The HSS, or C-PCEF subscription information database SPR) obtains the information of the C-PCEF. When the A-PCEF first initiates a rule configuration request for the session, the request carries the information of the C-PCEF obtained from the allocated entity; the associated entity in the process of initiating the request by the A-PCEF, correspondingly Obtain the information of the A-PCEF and the information of the C-PCEF.

In the case that the A-PCEF and the C-PCEF respectively initiate a rule configuration request for the session, the associated entity obtains the information of the A-PCEF in the process of the A-PCEF initiating the rule configuration request for the session; The associated entity acquires information of the C-PCEF in a process in which the C-PCEF initiates a rule configuration request for the session. The rule configuration request of the session initiated by the A-PCEF and the C-PCEF respectively carries its own PCEF identification information; the identifier information includes: one or more of a PCEF identifier, a PCEF address, or a PCEF type. Kind.

S2. The associated entity establishes an association relationship between different PCEFs serving the session.

Corresponding to the three cases in S1, the association entity establishes the association relationship of different PCEFs of the session service in this step, including:

Case 21: If the information of each PCEF is obtained through Case 11 or Case 12 in S1, the associated entity determines that both A-PCEF and C-PCEF are the session service, and establishes an association relationship between the A-PCEF and the C-PCEF. .

Case 22: If the information of each PCEF is obtained through the case 13 in the S1, the rule configuration request for the session initiated by the A-PCEF and the C-PCEF respectively carries the rule configuration request corresponding to the session. User IP address and/or user identity, as described by C-PCEF If there is an association between the user IP address and/or the user ID carried in the rule configuration request of the session, it is determined that the A-PCEF and the C-PCEF are both the session service, and the A-PCEF and the C-PCEF are established. Relationship.

In a specific implementation, the association relationship may be established in the following manner:

Method 01. As shown in Figure 6, the associated entity is located in the PDF. For example, the PCEF is associated with the maintenance interface session. For an IP CAN Session, each PCEF maintains a session with the PDF. For A-PCEF, this session may be a session based on the R3-PCC interface. For C-PCEF, it may be a Gx-based session, and PDF A Gx-based interface session is also maintained with the PCRF for the same IP CAN Session. In the embodiment of the present invention, the C-PCEF and the PDF may be a session based on the Gx interface, or may be based on a session of another interface. The following is a detailed description of the session based on the Gx interface. After the session is established, the signaling of each interface indicates the IP CAN Session object of the operation by the identifier of the session. The PDF associates it with sessions of different PCEFs and associates these sessions with sessions from the PDF to the PCRF. In addition, when a service operation is initiated on the network side or a service operation is initiated on the terminal side, the corresponding PCEF and related sessions can be indexed.

Mode 02. As shown in Figure 7, the associated entity is located in the PCRF as an example, and each PCEF is associated with the maintenance interface session. Similar to the foregoing, for an IP CAN Session, a Gx interface session is maintained between the PCRF and each PCEF (the PDF may also exist on the path from the PCRF to the PCEF). The PCRF associates different Gx interface sessions based on the session-related user ID and/or user IP address, and associates these sessions to the same IP CAN Session. In addition, when a service operation is initiated on the network side or a service operation is initiated on the terminal side, the corresponding PCEF and related sessions can be indexed.

Further, since the A-PCEF can be migrated (for example, in the WiMAX converged PCC architecture), after the PDF is used as an anchor point of the A-PCEF, after receiving the new registration request, the PDF passes the user IP address carried in the signaling and / or the user ID and other information indexed to the session between the corresponding PDF and the PCRF, further can obtain the previously established PDF to A-PCEF session corresponding to the session, and update the associated information corresponding to the session, using the new A- PCEF related session information (such as PDF Information such as the ID of the session to the A-PCEF, the address or ID of the PCEF, etc.) Updates the previously registered A-PCEF-related session information. However, if the associated entity is in PDF, the PDF must ensure that the A-PCEF migration does not affect the session between C-PCEF and PDF associated with it.

By default, only the A-PCEF can be migrated. The PDF determines whether the current A-PCEF migration is based on the PCEF type. The PDF can maintain the correspondence between the PCEF address and the PCEF type. The PCEF address can be used to determine the type of the PCEF. Whether the PCEF is A-PCEF or C-PCEF; b) The PCEF carries the PCEF type in the registration signaling. When the PDF receives the registration signaling of the PCEF, it first determines the PCEF type. If it is A-PCEF, it is considered to be the initial registration if there is no corresponding A-PCEF registration before, otherwise the registration is updated with the new A-PCEF information. The A-PCEF information is updated as described above. Or

When A-PCEF migrates, it is explicitly indicated that the A-PCEF migration process is performed, and it can be specified in the signaling from which PCEF to migrate to the current PCEF. After receiving the request, the associated entity indexes the session between the corresponding PDF and the PCRF according to the information such as the user IP and the user identifier, and obtains the associated information saved before the session, and then updates the new A-PCEF information with the new A-PCEF information. The PCEF information specified by A-PCEF without affecting other PCEFs in the associated information.

In the process of the association policy and the charging execution function entity in the embodiment of the present invention, the associated entity obtains the information of each PCEF serving the same session and the different PCEFs that are established for the session. For example, the embodiment of the present invention is directed to the S1. Case 13, considering that the A-PCEF and the C-PCEF initiate the request at different points in time, the associated entity needs to have the ability to save the rule and associate the rule; and the rule modification and deletion request initiated by the terminal side, and the associated entity maintains the PCEF association relationship. At the same time, the correspondence between the PCC rules on each PCEF needs to be maintained, so that the corresponding operation of the corresponding PCEF can be initiated in response to the request of the initiator PCEF. That is, the associated entities must ensure that the configuration status of each PCEF is consistent during the configuration of the PCC rules. In addition, in the process of initiating a rule configuration request for the same session for the A-PCEF, the associated entity should ensure that the configuration status of each PCEF is consistent during the configuration process of the PCC rule. Specifically, the method for ensuring that the configurations of the PCEFs are consistent, and the related entities ensure that the configuration actions are consistent: the mode 21: when the PCRF actively initiates the configuration request of the PCC rule, the PCRF triggers the associated entity, and is established by the associated entity. The association relationship between the PCEFs is respectively sent to the PCEFs, and the corresponding PCC rules and configuration instructions are respectively sent; or the mode 22, when any PCEF in the PCEFs initiates a PCC rule configuration request, the PCRF triggers the associated entity, and Sending, by the associated entity, the PCC rules and configuration instructions corresponding to the PCEF to the PCEF that initiated the request, and the associated entity respectively sending the corresponding PCC rules to the other PCEFs in the PCEFs. Configuration instructions. In the mode 21 and the mode 22, if the configuration request of the PCC rule is for an existing service, the associated entity further sends an association according to the association relationship between the PCC rules stored in the PCEFs maintained by the associated entity. Describe PCC rules and configuration instructions.

Specifically, the ensuring that the configuration status of each PCEF is consistent, the associated entity ensures that the rule configuration result is consistent in the following manner: the associated entity learns that part of the rule configuration result of each PCEF is a configuration failure, and then the association entity is established according to the associated entity. The association between the PCC rules stored in the PCEFs is respectively sent to the PCEFs that are successfully configured by the rules, and the corresponding PCC rules and configuration instructions are respectively sent to restore the PCC rules in the configured PCEF.

Further, in the process of establishing the service, the PCRF needs to return the access network information to the AF through the Rx interface, and the associated entity shields the PCEF and the PDF connected to each PCEF to the AF side, and the associated entity selects One of the access network policy charging entity identifiers reported by the PCEF or the PDF, and the access network policy charging execution entity is identified by the identifier in the interaction with the AF; or the associated entity allocates the access network policy charging entity Identifying, and identifying the access network policy charging enforcement entity in the interaction with the AF.

The embodiment of the present invention further provides an association entity, which may be located in a PDF, a V-PCRF, or an H-PCRF. As shown in FIG. 8, the associated entity 1 of the embodiment of the present invention includes: an obtaining unit 100 and a PCEF association unit 200.

The obtaining unit 100 is configured to acquire information about each PCEF serving the same session. The PCEF association unit 200 is configured to establish an association relationship of different PCEFs serving the session. As shown in FIG. 9, the further acquiring unit 100 in the associated entity 2 of the embodiment of the present invention may include: a first obtaining subunit 110, a second obtaining subunit 120, and/or a third obtaining subunit 130.

The acquiring unit 100 includes a first obtaining sub-unit 110, configured to acquire information of the A-PCEF in a process of initiating a rule configuration request for the session by the A-PCEF, and a pairing initiated by the A-PCEF. The rule configuration request of the session, the information of the C-PCEF is obtained from the allocation entity of the C-PCEF; the PCEF association unit 200 includes a first association sub-unit 210, configured to establish an association between the A-PCEF and the C-PCEF. relationship.

The acquiring unit 100 includes a second obtaining sub-unit 120, configured to acquire information about the A-PCEF from the A-PCEF initiating a rule configuration request for the session, and information carried in the request configuration request. The C-PCEF information is obtained in the PCEF association unit 200, and the second association sub-unit 220 is configured to establish an association relationship between the A-PCEF and the C-PCEF.

The acquiring unit includes a third obtaining sub-unit 130, configured to acquire information about the A-PCEF in the process of initiating a rule configuration request for the session, and initiate the session in the C-PCEF. Obtaining the C-PCEF information in the process of the rule configuration request; the PCEF association unit includes a third association sub-unit 230, configured to determine a user carried in the rule configuration request initiated by the A-PCEF for the session The association between the IP address and/or the user identifier and the user IP address and/or the user identifier carried in the rule configuration request initiated by the C-PCEF for the session is established, and the A-PCEF and the C-PCEF are established. connection relation.

As shown in FIG. 10, the associated entity 3 of the embodiment of the present invention may further include: a determining unit 300 and an updating unit 400, based on the associated entity 2.

The determining unit 300 is configured to: after the acquiring unit 100 acquires the information of each PCEF in each PCEF, and determine that the PCEF is a PCEF that is re-registered for migration, issue a trigger signal; and the updating unit 400 is configured to receive The trigger signal sent by the determining unit 300 is used as a trigger condition to update the associated information of the session corresponding to the PCEF registration.

The associated entity may further include: a PCC rule association unit 500. The PCC rule association unit 500 is configured to obtain the PCEF information of the existing association relationship from the PCEF association unit, and maintain the association relationship between the PCC rules stored in the PCEF in which the association relationship exists.

The associated entity may further include: a shielding unit 600.

The shielding unit 600 is configured to shield the PCEF and the PDF connected to each PCEF to the AF side.

The embodiment of the present invention further provides a system for associating a policy and a charging execution function entity. As shown in FIG. 11, the method includes: an associated entity 1000, and each PCEF2000 serving the same session.

The associated entity may be located in a PDF, V-PCRF or H-PCRF, for obtaining information of the PCEFs serving the same session, and establishing an association relationship of the PCEFs.

The foregoing is an overview of an embodiment of the present invention. C-PCEF and HA are two different logical functional entities, but in a specific implementation, C-PCEF and HA may be separate physical entities or integrated in the same physical entity. In the following, a specific embodiment will be described by taking the C-PCEF in the HA as an example.

Considering the case of WiMAX roaming and non-roaming and the dynamic allocation of HA in the case of roaming, the embodiment of the present invention can be applied to the following application scenarios.

Application scenario 1: Non-roaming scenario, as shown in Figure 12.

After the terminal enters the network, the network allocates HA to it. The HA can transmit the PCC Rules through the interface set up with the PCRF or the interface with the PDF. That is, the PCRF authorizes and generates the PCRF and sends the PCC Rules to the HA. Used by the HA as the basis for performing the policy charging operation; or the PCRF authorizes and generates the PCC Rules to send to the PDF, and forwards the PDF to the ASN's policy charging enforcement entities PCEF and HA.

In summary, in the scenario, the PCRF sends the PCC Rule information to A-PCEF (ie, PCEF of ASN) and C-PCEF (ie, HA). The PDF can also be sent to the PDF. The PCRF sends the PCC Rule information to the PDF and then sends the PDF to the PCEF entity.

Since the delivery path may be different, and the PCC Rule performed by A-PCEF and C-PCEF may be different, different registrations initiated by A-PCEF and C-PCEF for the same session may end. PDF can also be terminated in PCRF. That is, the associated entity can be located in the PDF, and the A-PCEF and the C-PCEF under the same IP CAN Session are associated by the PDF, and the PDF is sent to the A-PCEF and the C-PCEF after receiving the PCC Rule issued by the PCRF. Or the associated entity may be located in the PCRF, and the PCRF associates the A-PCEF and the C-PCEF under the same IP CAN Session. When the PCRF issues the rule, the A-PCEF and the C-PCEF are distributed. There may also be a PDF on the distribution path, but the PDF is not associated.)

Application scenario 2: Roaming scenario, HA is allocated at the visited place, and HA obtains rules from the visited CSN, as shown in Figure 13.

When the terminal enters the network and the HA assigned by the network is located in the V-CSN, the HA transmits the PCC Rules through the interface set up with the V-PCRF or the interface with the PDF, that is, the H-PCRF authorization and generation. When the PCC Rules are sent to the V-PCRF, the V-PCRF can further decide and authorize according to the local policy (possibly cutting the PCC Rules), and then send the final authorized PCC Rules to the ASN's policy charging execution entity PCEF through the PDF. At the same time, the V-PCRF also sends the PCC Rules to the HA for the HA as the basis for performing the policy charging operation; or the V-PCRF sends the final authorized PCC Rules to the PDF, and the PDF sends the PCC Rule to the ASN's policy meter. The fee is executed by the entities PCEF and HA.

In summary, in scenario 2, the H-PCRF sends the PCC Rule information to the V-PCRF; the VC-PCRF sends the PCC Rule information to the A-PCEF (ie, the PCEF of the ASN) and the C-PCEF (ie, HA). The PDF can be sent to the V-PCRF. The V-PCRF sends the PCC Rule information to the PDF and then sends the PDF to the PCEF entity.

Multiple registrations of A-PCEF and C-PCEF can be terminated in PDF, V-PCRF or H-PCRF. That is, the associated entity can be located in the PDF, and the PDF associates the A-PCEF and the C-PCEF under the same IP CAN Session. After the PDF receives the PCC Rule issued by the V-PCRF, the A-PCEF and the C-PCEF are sent to the A-PCEF and the C-PCEF. Multi-distribution; or the associated entity may be located in the V-PCRF, the V-PCRF is the same as the H-PCRF, and the A-PCEF and C-PCEF under the same IP CAN Session by the H-PCRF Make an association.

The detailed description is similar to the scenario 1. It should be noted that there may be a PDF entity between the H-PCRF and the V-PCRF, but the PDF is not associated.

Application scenario 3: In the roaming scenario, the HA is allocated at the home location, and the HA obtains the PCC Rule through the visited CSN. See Figure 14.

The H-PCRF sends the PCC Rules information to the V-PCRF. The V-PCRF can further decide and authorize according to the local policy (possibly cutting the PCC Rules), and then send the final authorized PCC Rules to the ASN through PDF. The billing execution entity PCEF and C-PCEF (that is, HA); PDF can exist in the delivery path of the V-PCRF, and the V-PCRF sends the PCC Rule information to the PDF, and then the PDF is sent to the PCEF entity.

Multi-registration of A-PCEF and C-PCEF can be terminated by PDF, V-PCRF or H-PCRF. That is, the associated entity may be located in the PDF, and the A-PCEF and the C-PCEF under the same IP CAN Session are associated by the PDF; or the associated entity may be located in the V-PCRF, and the V-PCRF is under the same IP CAN Session. A-PCEF and C-PCEF are associated; or the associated entity may be located in the H-PCRF, and the A-PCEF and C-PCEF under the same IP CAN Session are associated by the H-PCRF.

Application scenario 4: In the roaming scenario, the HA is allocated at the home location, the HA acquires the PCC Rule through the home CSN, and the visited A-PCEF connects to the home CSN through the visited CSN. See Figure 15 for details.

The H-PCRF sends the PCC Rule information to the V-PCRF and the C-PCEF (ie, HA), and the PCC Rule information is sent by the V-PCRF to the A-PCEF (ie, the PCEF in the ASN). PDF can exist in the connection path between H-PCRF and V-PCRF and H-PCRF to C-PCEF, PDF between H-PCRF and V-PCRF and PDF between H-PCRF and C-PCEF are located In the home network; after the PDF in the connection path between the H-PCRF and the V-PCRF receives the PCC Rule information, The PCC Rule information is sent from the PDF to the V-PCRF; after the PCC Rule information is received in the PDF in the connection path between the H-PCRF and the C-PCEF, the PCC Rule information is sent to the C-PCEF by the PDF. It should be noted that a PDF may also exist on the connection path between the V-PCRF and the A-PCEF, and the PDF is located in the visited network. As mentioned above, if the same attribution PDF exists in the connection path between V-PCRF and H-PCRF and C-PCEF and H-PCRF, then A-PCEF passes V-PCRF to H-PCRF connection and C- The connection of the PCEF to the H-PCRF can be correlated by the PDF; otherwise it can be correlated by the H-PCRF.

As mentioned earlier, multiple registrations can end in PDF or H-PCRF. That is, the associated entity may be located in the PDF, and the PDF associates the A-PCEF and the C-PCEF under the same IP CAN Session, the PDF is the home PDF; or the associated entity may be located in the H-PCRF, and the H-PCRF is Associated with A-PCEF and C-PCEF under the same IP CAN Session.

Application scenario 5: In the roaming scenario, the HA is allocated at the home location, the HA obtains the PCC Rule through the home CSN, and the visited A-PCEF is directly connected to the home CSN. See Figure 16.

The H-PCRF sends the PCC Rule information to the visited site A-PCEF and C-PCEF (ie HA).

PDFs can exist in the connection path between H-PCRF and A-PCEF, and between H-PCRF and C-PCEF. Since the A-PCEF is directly connected to the home CSN without visiting the CSN, the PDF between the H-PCRF and the A-PCEF is the attribution PDF.

Multiple registrations can end in PDF or H-PCRF. The PDF is the attribution PDF.

The following is exemplified by the seven embodiments, and the following seven embodiments are exemplified by the application scenario 1 described above, and are also applicable to other application scenarios.

In the first embodiment, the PCRF obtains the HA information allocated by the AAA for the user when the user subscribes to the AAA/SPR/HSS (that is, the AAA/SPR/HSS is used as the allocation entity of the C-PCEF). When the PCRF needs to deliver the rule, When the associated entity is located in the PDF, the PCRF adds C-PCEF location or address related information to the message sent to the PDF and instructs the PDF to be sent to the C-PCEF; when the associated entity is located in the PCRF, the PCRF directly to the A-PCEF and C-PCEF Distribution rules. Referring to Figure 17, the following steps are included: Step 1001: A-PCEF sends a PCC rule request through the PDF, and initiates a PCC Rules configuration process to the PCRF for the IP-CAN session of the terminal; wherein the PCRF receives the PCC rule request sent by the A-PCEF through the PDF, and establishes the A-PCEF with the A-PCEF. Session, and record the A-PCEF service to the IP-CAN Session.

The configuration process may include: creation, modification, and/or deletion of PCC Rules, or establishment, modification, or release of an IP-CAN Session. The configuration process below is the same as here, and will not be described again.

Step 1002: Step 1003: The PCRF requests user subscription information from the AAA/SPR/HSS.

AAA/SPR/HSS has the ability to dynamically allocate HA. The AAA/SPR/HSS can also inform the PCRF user of the subscription information, and can also inform the terminal of the location of the HA corresponding to the currently used IP-CAN Session (port Home or Visited);

In this step, if the AAA/SPR/HSS knows the address of the HA, it can also inform the PCRF of the address of the HA at the same time, or it can also inform the PCRF only the address of the HA.

Optionally, in the embodiment of the present invention, the associated entity may further need to obtain the identifier information of the A-PCEF and/or the C-PCEF, where the identifier information includes one or more of the PCEF identifier, the PCEF address, or the PCEF type. . In the scenario of the embodiment, only the A-PCEF initiates the rule configuration request, so in this scenario, the A-PCEF implicitly carries the corresponding A in the rule configuration request sent by the A-PCEF to the associated entity. - PCEF identification information, if the PCRF receives the rule configuration request, it can directly determine that the PCEF type is A-PCEF (because only A-PCEF will initiate a rule configuration request in this scenario), and the PDF is based on the received A-PCEF. The IP data packet obtains the PCEF address. For example, the A-PCEF may send a registration message to the PDF, and the PDF obtains the address of the A-PCEF according to the IP header address of the registration message, thereby obtaining the identification information of the A-PCEF. If the associated entity is located in the PCRF, the PDF needs to carry the identifier information in the registration message sent to the PCRF. Of course, in the embodiment of the present invention, the A-PCEF may explicitly carry the PCEF identifier information in the rule configuration request. . The identification information of the C-PCEF obtained by the PCRF may be explicitly or implicitly carried in the registration process of the A-PCEF, or when the PCRF interacts with the AAA/SPR to obtain the C-PCEF information. Obtained explicitly or implicitly.

The associated entity interacts with the AAA/SPR according to the aforementioned PCEF identification information, and/or PCRF.

HA corresponds to C-PCEF). As described above, the PCRF can obtain two PCEF information from the AAA/SPR. Based on this information, the PCRE can be further verified. If the PCEF that initiates the registration is different from the AAA/SPR, the PCRF can refuse to register. Further, if different PCC rules need to be provided for A-PCEF and C-PCEF, the PCRF needs to obtain the foregoing identification information, and generate different rules according to the identification information. The acquisition and application of the identification information is the same as here, and will not be described again.

Step 1004: The PCRF may save the location of the HA associated with the IP-CAN Session and/or the address of the HA. If the associated entity is located in the PCRF, the IP-CAN session is established according to the previously recorded A-PCEF, and the IP CAN is established. Relationship between A-PCEF and HA (ie, C-PCEF) under Session; and performing policy decision based on user subscription information and its own policy requirements, authorizing and generating PCC Rules. If the associated entity is located in PCRF, PCRF respectively Authorize and generate a PCC Rule for A-PCEF and HA, and the corresponding PCC Rule may be the same or different.

Step 1005: The PCRF sends the generated PCC Rules to the PDF. If the associated entity is located in the PDF, the PDF can also inform the current location of the current HA and/or the address of the HA, and the indication information, which is used to inform the PDF to the HA. Distribute the corresponding PCC Rules.

Step 1006: Step 1007: If the associated entity is located in the PCRF, the PCRF sends the corresponding PCC Rules to the HA according to the location of the HA and/or the address of the HA, and associates the PCC rules for the A-PCEF with the PCC rules for the HA. Get up; and configure the received PCC rules by the HA, and respond to the PCC Rules configuration results;

It should be noted that the association of the PCC rules is associated by the identifier of the PCC rule, for example, the identifier of the PCC rule on the A-PCEF connection session is associated with the identifier of the PCC rule on the C-PCEF connection session. As mentioned above, the rules executed by each PCEF may be the same or different. If the identifiers of the two rules are the same, the association of the rules may be accompanied by the PCEF. In conjunction, if the identifiers of the rules are different, an explicit association is required to associate the two identifiers. It should be noted that, as described in the foregoing scenarios, the PDF may also appear in the connection path between the PCRF and the C-PCEF/HA.

Or,

Step 1006, step 1007, if the associated entity is located in the PDF, the PDF establishes the A-PCEF and the HA under the IP CAN Session according to the location of the HA and/or the address of the HA delivered by the PCRF in step 1005 (ie, C- The relationship between PCEF), the corresponding PCC Rules are sent and the received PCC rules are configured by the HA, and the PCC Rules configuration result is responded to.

Step 1008: The PDF sends the corresponding PCC Rules to the PCEF in the ASN where the terminal is located; Step 1009, Step 1010: Create, modify, or delete the IP-CAN bearer or IP-CAN Session according to the received configuration request in the ASN network, and A-PCEF configures the corresponding PCC Rules and returns the configuration results to the PDF.

Step 1011: The PDF returns the PCC Rules configuration result to the PCRF according to the configuration result returned by the PCEF. At the same time, if the associated entity is located in the PDF, the PDF must ensure that the A-PCEF and the HA configuration result are the same, and must be successful at the same time, otherwise it is considered to be a failure; if one of the configurations fails, the PDF is associated with the PCC rule maintained in step 1006. Relationship, the PCC Rule configuration process is initiated again to the other party, and the corresponding PCC rule is restored to the state before the configuration (ie, the state before step 1001) to ensure consistency of configuration of multiple PCEF rules.

If the associated entity is located in the PCRF, the PCRF needs to ensure that the A-PCEF and the HA configuration result are the same, and must be successful at the same time. Otherwise, the failure is considered. If one of the configurations fails, the PCRF proceeds to the other party according to the PCC rule association maintained in step 1006. The PCC Rule configuration process is initiated again, and the corresponding PCC rule is restored to the state before the configuration (that is, the state before step 1001) to ensure consistency of multiple PCEF rule configurations.

Embodiment 2: After the user authentication process succeeds, the A-PCEF obtains the HA information allocated to the user from the AAA/SPR/HSS (ie, AAA/SPR/HSS is used as the allocation entity of the C-PCEF), and is registered. Carry the PDF or PCRF to the process. When the PDF is used as the associated entity, the PDF saves and associates the relationship between A-PCEF and C-PCEF, and after obtaining the PCC Rule from the PCRF, it is delivered to A-PCEF and C-PCEF; when the associated entity is located in the PCRF, The PCRF distributes the rules directly to A-PCEF and C-PCEF, and PDFs may exist on the distribution path. Referring to Figure 18, the following steps are included:

Step 2001: The A-PCEF initiates a rule configuration request to the PCRF through the PDF, and carries the HA address and/or the HA location obtained in the authentication process during the initiated rule configuration request message. If the associated entity is located in the PDF, the PDF saves the HA. The information maintains the association between the A-PCEF and the HA (ie, C-PCEF) in the same IP-CAN session, and can no longer carry the HA address or location in the forwarded rule configuration request message. If the associated entity is located in the PCRF, The HA address and/or location is notified to the PCRF, and the PCRF maintains the association between A-PCEF and HA (ie, C-PCEF) under the same IP-CAN Session.

The configuration process may include: creation, modification, and/or deletion of PCC Rules, or establishment, modification, or release of an IP-CAN Session.

The rule configuration request may be initiated when the A-PCEF first initiates a rule request, or when the A-PCEF requests a rule configuration request after the migration, or the A-PCEF initiates a rule configuration request due to a change in the network configuration.

Optionally, in the embodiment of the present invention, the associated entity may further need to obtain the identifier information of the A-PCEF and/or the C-PCEF, where the identifier information includes one or more of the PCEF identifier, the PCEF address, or the PCEF type. . In the scenario of the embodiment, only the A-PCEF initiates the rule configuration request, so in this scenario, the A-PCEF implicitly carries the corresponding A in the rule configuration request sent by the A-PCEF to the associated entity. - PCEF identification information, if the PCRF receives the rule configuration request, it can directly determine that the PCEF type is A-PCEF (because only A-PCEF will initiate a rule configuration request in this scenario), and the PDF is based on the received A-PCEF. The IP data packet obtains the PCEF address. For example, the A-PCEF may send a registration message to the PDF, and the PDF obtains the address of the A-PCEF according to the IP header address of the registration message, thereby obtaining the identification information of the A-PCEF. If the associated entity is located in the PCRF, the PDF needs to carry the identification letter in the registration message sent to the PCRF. Of course, in the embodiment of the present invention, the A-PCEF may explicitly carry the PCEF identification information in its rule configuration request. The identification information of the C-PCEF obtained by the PCRF may be explicitly or implicitly carried in the registration process of the A-PCEF, or may be obtained explicitly or implicitly when the PCRF and the AAA/SPR interact to obtain the C-PCEF information.

The associated entity determines that the sessions of the two PCEFs can exist simultaneously according to the foregoing identification information, and/or the NAS or HA information obtained by the PCRF and the AAA/SPR interaction in the subsequent steps 2002 and 2003 (the NAS corresponds to the A-PCEF, and the HA corresponds to the C- PCEF). As mentioned above, the PCRF can obtain two PCEF information from the AAA/SPR. Based on this information, the PCRE can be further verified. If the PCEF that initiates the registration is different from the AAA/SPR, the PCRF can refuse to register. Further, if different PCC rules need to be provided for A-PCEF and C-PCEF, the PCRF needs to obtain the foregoing identification information, and generate different rules according to the identification information. The acquisition and application of the identification information is the same as here, and will not be described again.

Step 2002, step 2003: The PCRF requests the user to sign the subscription information, and the AAA informs the PCRF user of the subscription information.

Step 2004: The PCRF performs policy decision according to the user subscription information and its own policy requirements, and authorizes and generates PCC Rules. If the associated entity is located in the PCRF, the PCRF may also generate different PCC Rules for different PCEFs.

Step 2005: The PCRF sends the generated PCC Rules to the PDF.

Step 2006, step 2007: If the associated entity is located in the PCRF, the PCRF sends the corresponding PCC Rules to the HA according to the location of the HA and/or the address of the HA, and associates the PCC rules for the A-PCEF with the PCC rules for the HA. Get up; and configure the received PCC rules by the HA, and respond to the PCC Rules configuration results; or,

Step 2006, step 2007,: If the associated entity is located in the PDF, the PDF sends the corresponding PCC Rules to the HA according to the location of the saved HA and/or the address of the HA, and the PCC rules for the A-PCEF and the HA are The PCC rules are associated; and the received PCC rules are configured by the HA, and the PCC Rules configuration results are returned. Step 2008: The PDF sends the corresponding PCC Rules to the PCEF in the ASN where the terminal is located. Step 2009, Step 2010: Create, modify or delete the IP-CAN bearer or IP-CAN Session according to the requirements of the PCC Rules in the ASN network, and configure the corresponding PCC Rules in the A-PCEF, and return the configuration result to the PCRF.

Step 2011: The PDF returns the PCC Rules configuration result to the PCRF based on the configuration result returned by the PCEF. At the same time, if the associated entity is located in the PDF, the PDF must ensure that the A-PCEF and the HA configuration result are the same, and must be successful at the same time, otherwise it is considered to be a failure; if one of the configurations fails, the PDF is associated with the PCC rule maintained in step 2006. Relationship, the PCC Rule configuration process is initiated again to the other party, and the corresponding PCC rule is restored to the state before the configuration (ie, the state before step 2001) to ensure consistency of multiple PCEF rule configurations.

If the associated entity is located in the PCRF, the PCRF needs to ensure that the A-PCEF and the HA configuration result are the same, and must be successful at the same time. Otherwise, it is considered to be a failure. If one of the configurations fails, the PCRF proceeds to the other party according to the PCC rule association relationship maintained in step 2006. The PCC Rule configuration process is initiated again, and the corresponding PCC rule is restored to the state before the configuration (that is, the state before step 2001) to ensure consistency of multiple PCEF rule configurations.

Example 3. Both A-PCEF and C-PCEF initiate registration with PCRF/PDF. The associated entity associates the session of the associated entity to the A-PCEF with the session of the associated entity to the C-PCEF based on the user identity and the IP address of the user. See Figure 19, which includes the following steps:

Step 3001: The C-PCEF triggers the PCC Rules configuration process related to the IP-CAN Session according to the bearer requirement of the terminal IP-CAN Session. The configuration process may include: creating, modifying, and/or deleting the PCC Rules, or The establishment, modification or release of the IP-CAN Session.

Step 300: A-PCEF triggers the PCC Rules configuration process related to the IP-CAN Session according to the bearer requirement of the terminal IP-CAN Session; the configuration process may include: creating, modifying, and/or deleting the PCC Rules, or The establishment, modification or release of the IP-CAN Session.

The time points at which the two PCEFs initiate the request are not in order.

Step 3002: The C-PCEF notifies the PCRF of the bearer requirement of the IP-CAN Session (ie, requests for a note) The request may also need to be sent to the PCRF via PDF; if the associated entity is located in the PCRF, the registration initiated by the C-PCEF terminates in the PCRF (may pass through the PDF in the middle), if the associated entity is in the PDF, then the C-PCEF initiates Registration may end in PDF or may terminate in PCRF. If the registration ends in the PDF, the registration initiated by the C-PCEF does not trigger the PCRF to interact with the AAA, and the registration of another PCEF (A-PCEF) is sent to the PCRF, triggering the PCRF to interact with the AAA if necessary, and generating rules.

Step 3002,: A-PCEF informs the PCRF of the bearer requirement of the IP-CAN Session (ie, requests registration); the request may also need to be sent to the PCRF through the PDF; if the associated entity is located in the PCRF, the registration initiated by the A-PCEF is terminated. PCRF (may go through PDF in the middle), if the associated entity is in PDF, the registration initiated by A-PCEF may end in PDF or terminate in PCRF. If the registration ends in the PDF, the A-PCEF-initiated registration does not trigger the PCRF to interact with the AAA, and the other PCEF (C-PCEF) registration is sent to the PCRF, triggering the PCRF to interact with the AAA if necessary, and generating rules.

If the associated entity is located in the PDF, the PDF blocks multiple PCEF registrations to the PCRF, and one of the A-PCEF-initiated registrations or the HA-initiated registrations will terminate in the PDF. As in the previous step 3002 or step 3002, one of the registrations terminates in the PDF; If the associated entity is located in the PCRF, both the A-PCEF and the HA are registered to the PCRF, and the registration path may pass through the PDF, such as step 3002 and step 3002, and terminate in the PCRF. The associated entity associates multiple PCEF registrations by user IP address and/or user identification.

Optionally, in the embodiment of the present invention, the associated entity may further need to obtain the identifier information of the A-PCEF and/or the C-PCEF, where the identifier information includes one of the identifier of the PCEF, the address of the PCEF, or the PCEF type. A variety. The rule configuration request for the session sent to the associated entity carries the corresponding PCEF identification information, for example, the A-PCEF carries its own PCEF identification information in the configuration request sent by the A-PCEF, and the C-PCEF sends the same The configuration request carries its own PCEF identification information. The identification information may be explicitly carried in the configuration request, or may be obtained by the PDF according to the received IP packet of the PCEF, for example, the PCEF may send the registration message to the PDF. The PDF obtains the address of the PCEF according to the IP header address of the registration message, and further obtains the identification information of the PCEF. If the associated entity is located in the PCRF, the PDF needs to carry the identification information in the registration message sent to the PCRF.

The associated entity determines that the two PCEF sessions can exist simultaneously according to the foregoing identification information, and/or the NAS or HA information obtained by the PCRF and the AAA/SPR interaction in the subsequent step 3003 (the NAS corresponds to the A-PCEF, and the HA corresponds to the C-PCEF). . As mentioned above, the PCRF can obtain two PCEF information from the AAA/SPR. Based on this information, the PCRE can be further verified. If the PCEF that initiates the registration is different from the AAA/SPR notification, the PCRF can refuse to register. Further, if different PCC rules need to be provided for A-PCEF and C-PCEF, the PCRF needs to obtain the foregoing identification information, and generate different rules according to the identification information. The acquisition and application of the identification information is the same as here, and will not be described again.

Step 3003 to step 3005: The PCRF obtains corresponding user subscription information from the AAA, and generates PCC Rules.

Step 3006 to step 3010: The PCRF delivers the PCC Rules. If the associated entity is located in the PCRF, the PCRF sends the PCC Rules to the PDF for the A-PCEF, and also issues the PCC Rules for the HA, and delivers the PCC Rules for the HA. It may or may not be PDF. If the associated entity is located in the PDF and the association between A-PCEF and HA is maintained in PDF, the PCRF only issues the PCC Rules to the PDF and distributes the PDF to A-PCEF and HA.

Embodiment 4 Based on Embodiment 3, considering that the time point at which the A-PCEF initiates the request is different from the HA, the associated entity needs to have the ability to save the rule and associate the rule.

If the associated entity is located in the PDF, the associated entity saves the PCC Rules after obtaining the corresponding PCC Rules or the first registered PCEF return confirmation message for the first registered PCEF; when the second registered PCEF initiates the corresponding rule request, the PDF Sending the saved PCC Rules to the second registered PCEF; or when the first registration PCEF initiates the request, the PDF only establishes the association relationship without issuing the rule, and when the second registration PCEF initiates the request, the PDF issues the rule according to the request, and according to The previously established association relationship is delivered to the first registered PCEF; or the first registration When the PCEF initiates the request, the PDF does not immediately return the response after receiving the request, but establishes the association relationship and waits for the second registration PCEF to initiate the request. When the second registration PCEF initiates the request, the PDF issues the rule according to the request, and according to the previous The established association is sent to the first registered PCEF in response to the request of the first registered PCEF.

If the associated entity is located in the PCRF, the associated entity saves the PCC Rules after obtaining the corresponding PCC Rules or the first registered PCEF return confirmation message for the first registered PCEF; when the second registered PCEF initiates the request, the associated entity may directly The saved PCC Rules are issued; new PCC Rules can also be generated by the PCRF. Or, similar to the foregoing, when the first registration PCEF request is not sent, the rule is only established, and after receiving the request initiated by the second registration PCEF, the rule is delivered according to the request, and according to the previously established association relationship, the corresponding rule is The first registered PCEF is sent to the first registered PCEF. Alternatively, the similar associated entity is located in the PDF scenario. When the first registered PCEF initiates the request, only the association relationship is established, and no response is received. After receiving the request initiated by the second registered PCEF, the rule is delivered according to the request. And responding to the request of the first registered PCEF according to the previously established association relationship, and delivering the corresponding rule to the first registered PCEF.

As mentioned earlier, the rules obtained by different PCEFs may be the same or different, and the associated entities need to associate PCC rules on different PCEFs. Different PCC rules obtained by different PCEFs may be generated by PCRF or by PDF.

Embodiment 5: For the rule modification and deletion request initiated by the terminal side, the associated entity maintains the PCEF association relationship, and also needs to maintain the correspondence relationship of the corresponding PCC rules on each PCEF; in response to the request of the initiator PCEF, The corresponding rules of the related PCEF initiate corresponding operations. See Figure 20 for a schematic diagram of the modification or deletion of the rules.

For the modification or deletion of the service triggered by the AF side, the PCRF sends an operation instruction of the relevant PCC rule to each PCEF through the associated entity. If the associated entity is located in the PCRF, the PCRF maintains the association relationship between the PCC rules and the PCC rules on the PCEF. After receiving the service operation indication initiated by the AF, the corresponding PCC is sent to each PCEF according to the association relationship. The operation indication of the rule; if the associated entity is in the PDF, it corresponds to the rule issued by the same PCRF, PDF The association relationship between the corresponding PCC rules on each PCEF is maintained. After receiving the service operation indication initiated by the AF, the operation instruction corresponding to the PCC rule is sent to each PCEF according to the association relationship.

Optionally, in the embodiment of the present invention, the following embodiments may also be implemented. As shown in FIG. 23, the A-PCEF and PDF session, the C-PCEF and PDF session, and the PDF and PCRF session are respectively maintained by the PDF. The association between the three sessions is similar to the mode 01 in FIG. 6. The PDF and the PCRF have a Gx session corresponding to an IP session; the PCRF may need to generate different PCC rules for different PCEFs. This is because the different types of PCEFs are different. The PCRF sends different rules to different PCEFs in the same session. The PCEF is specified by the PCEF. The information (PCEF address, PCEF identifier, or PCEF type) is specified; after receiving the PCC rule sent from the Gx interface, the PDF sends a specific rule to its specified according to the previously maintained PCEF association relationship and the PCEF identification information corresponding to the rule. PCEF.

The associated entity establishes an association relationship of the corresponding PCC rules on the PCEFs when the PCC rules are established. The establishment of the PCC rule may occur during the rule configuration process of session establishment or the process of configuring subsequent rules.

Further, in the embodiment of the present invention, the process of modifying and deleting a rule may also be applied to a scenario in which an IP session is released, as shown in FIG. 24 and 25. Figure 24 is a flow chart of the terminal side triggering the release of the IP session when the associated entity is located in the PDF, and Figure 25 is a flow chart of the terminal side triggering the release of the IP session when the associated entity is located in the PCRF.

As shown in FIG. 24, in the embodiment of the present invention, the associated entity is located in the PDF, and the specific scheme is as follows: Steps 5001, 5002, the ASN initiates an IP session release request to the PDF, and the PDF receives the

After the IP session release request, the request is forwarded to the PCRF;

In the embodiment of the present invention, when the current IP session needs to be released, the PCEF (ie, A-PCEF) in the ASN may send an IP session release request to the PDF, and the PDF may be based on the session between the A-PCEF and the PDF maintained by the PDF. The association relationship between the PCRF sessions forwards the IP session release request to

PCRF. Steps 5003, 5004, after receiving the message, the PCRF returns an IP session release confirmation to the PDF, and the PDF returns an IP session release confirmation to the A-PCEF.

The PCRF acknowledges upon receiving an IP session release request from the PDF. The IP session release confirmation is then returned to the PDF, and the PDF returns it to the PCEF (i.e., A-PCEF) in the ASN upon receipt of the IP session release confirmation.

Step 5005: The related entity is located in the PDF, and the PDF may send a session release indication to the corresponding C-PCEF according to the association relationship of the PCEFs maintained by the PDF, and the indication manner may directly indicate that the corresponding IP session is released, or may be The process of deleting the rule to release the corresponding IP session, for example, the associated entity finds that the PCC rule corresponding to the IP session of the A-PCEF has been deleted, as described above, according to the association relationship of each PCEF saved by the associated entity, and/or PCC Rules The association relationship can be triggered when the C-PCEF is released.

Step 5006: After receiving the IP session release indication from the PDF, the C-PCEF returns an IP session release response to the PDF, and simultaneously releases the bearer resource corresponding to the session.

Step 5007: If the IP session requires the PCEF to explicitly initiate the release, optionally, the C-PCEF sends an IP session release request to the PDF.

Step 5008, the PDF returns an IP session release confirmation to the C-PCEF.

As shown in FIG. 24, in the embodiment of the present invention, the process of releasing an IP session when the associated entity is located in the PCRF is as follows:

Step 5101, 5102, the ASN initiates an IP session release request to the PDF, and after receiving the IP session release request, the PDF forwards the request to the PCRF;

For example, when the current IP session needs to be released, the PCEF (ie, A-PCEF) in the ASN can send an IP session release request to the PDF.

Steps 5103 and 5104, after receiving the message, the PCRF returns a confirmation to the PDF for releasing the IP session, and the PDF returns an IP session release confirmation to the A-PCEF.

The PCRF acknowledges upon receipt of the IP session release request from the PDF. Then release the IP session The confirmation is returned to the PDF, and the PDF returns it to the PCEF (ie A-PCEF) in the ASN after receiving the IP session release confirmation.

Steps 5105 and 5106, the PCRF may send an IP session release indication to the corresponding C-PCEF according to the association relationship between the PCEFs maintained by the PCRF, and the indication manner may directly indicate that the corresponding IP session is released, or The corresponding IP session is released by the foregoing process of deleting the rule. For example, the associated entity finds that the PCC rule corresponding to the IP session of the A-PCEF has been deleted. As described above, according to the association relationship of each PCEF saved by the associated entity, and/or The PCC Rules association may trigger the deletion of the PCC rule corresponding to the IP session on the C-PCEF. When the PCC rule on the corresponding IP session is deleted, the C-PCEF is triggered to release the session.

Steps 5107, 5108, the C-PCEF returns an IP session release response to the PCRF after receiving the IP session release indication, and simultaneously releases the bearer resource corresponding to the session.

Steps 5109 and 5110, if the IP session requires the PCEF to explicitly initiate the release, the C-PCEF may send an IP session release request to the PCRF.

Steps 5111, 5112, the PCRF returns an IP session release confirmation to the C-PCEF.

For the IP session release triggered by the network side, the associated entity initiates a session release process to each PCEF according to the association relationship maintained by the associated entity, and the association entity application association relationship is consistent with the modification and deletion process of the AF side initiation rule. Let me repeat.

Embodiment 6: In the process of establishing a service, the PCRF needs to return the access network information to the AF through the Rx interface, and the associated entity is responsible for shielding the presence of multiple PCEFs to the AF side, and each PCEF and its connected PDF (if the If there is a PDF on the link, report the access network information to the AF side, including the access network policy charging entity identifier (the charging point identifier) and the access network charging identifier, and the associated entity selects one of the reported The access network policy charging entity identifier or the associated entity self-allocation identifier is used to represent the access network policy charging execution entity in the interaction between the PCRF and the AF, and select one of the access network charging identifiers reported by the one of the associated entities or the associated entity itself. The corresponding access network charging identifier is allocated to the AF as the access network charging identifier. There is only one PCEF seen from the perspective of AF. If the associated entity is in PDF, then the PCRF sees only one PCEF. Taking the service flow triggered by the AF as an example, the associated entity shields multiple APEF entities from the AF side.

The association between PCEFs may have been established before. Referring to Figure 21, the following steps are included:

Step 6001: The AF sends an access authorization request to the PCRF, where the service information is carried.

Step 6002, step 6003, optionally, the PCRF obtains user subscription information and HA allocation information from the AAA. When the PCRF needs the above information, and the PCRF has not acquired it, the interaction between the PCRF and the AAA is triggered.

Steps 6004 to 6011, the PCRF authorizes and generates a corresponding PCC rule, and sends the corresponding rule to the A-PCEF and the HA/C-PCEF according to the association relationship established by the associated entity, and the specific delivery manner is similar to that of the foregoing Embodiment 1. , will not repeat them here.

It should be noted that the PCC rule configuration confirmation message in step 6007, step 6007, and step 6010 carries the access network charging identifier of the PCEF corresponding PCC rule.

If the associated entity is located in the PDF, the associated entity obtains the corresponding access network policy charging entity identifier (access network charging point identifier) that is reported by the A-PCEF and the C-PCEF after the step 6007 and the step 6010. Incoming network charging identifier. The associated entity selects one of the access network identifiers and the access network charging identifiers that need to be reported to the AF, or the associated entity may also choose to allocate the corresponding identifiers and the access network charging identifiers generated by the associated entities. . The PDF reports the selected access network charging point identifier and the access network charging identifier to the PCRF through step 6011.

If the associated entity is located in the PCRF, the associated entity obtains the corresponding access network charging point identifier and the access network charging identifier that are held by the A-PCEF and the C-PCEF or reported by the PDF after step 6007 and step 6011. The associated entity selects one of the access point identifiers and the access network charging identifiers that need to be reported to the AF, or the associated entity may also choose to allocate the corresponding identifiers of the access network charging points and the connections generated by the associated entities. The network access billing identifier is reported.

Step 6012: The PCRF returns an authorization response to the AF, where the access network corresponding to the access network charging point identifier and the access network charging identifier are carried.

The function of shielding multiple PCEFs and their corresponding access network charging identifiers is applicable to each of the texts herein. How to obtain various association relationships in the scene.

Embodiment 7. Referring to FIG. 22, the following describes the migration process of the A-PCEF in a flow manner. In step 7001, the newly migrated A-PCEF receives the trigger request of the A-PCEF to be updated.

Step 7002: The newly migrated A-PCEF sends a request message to the PDF, where the indication is an A-PCEF migration, and the signaling may also carry the newly migrated A-PCEF address, the newly migrated A-PCEF type, and/or the to be updated. A-PCEF address or logo.

In step 7003, the PDF updates the newly migrated A-PCEF to the information corresponding to the IP CAN Session, and indexes the A-PCEF to be updated, and prepares to issue a release request to the A-PCEF.

The PDF index can be updated to the A-PCEF to be updated. 1 . The PDF maintains the correspondence between the PCEF address and the PCEF type, and then obtains the corresponding PCEF type according to the newly migrated A-PCEF address, or step 7002. Directly carrying the newly migrated A-PCEF type; also carrying this information when registering the newly migrated A-PCEF; after obtaining the type, the PDF is indexed to the previous A-PCEF according to the type; 2. The newly migrated A-PCEF is being migrated In the request, the address or identifier of the A-PCEF to be updated is directly carried, and the PDF is directly indexed to the A-PCEF to be updated.

Step 7004, the PDF returns a confirmation response to the newly migrated A-PCEF.

Steps 7005 ~ 7007, the PDF initiates a release process to the A-PCEF to be updated.

Although the above embodiment takes a non-roaming scenario as an example, the foregoing roaming scenarios 2, 3, 4, and 5 are similar, except that the V-PCRF entity and the PDF entity that may exist in the home CSN are added. The functions of the associated entities are consistent.

In the method, the device and the system of the embodiment of the present invention, the associated entity obtains the information of each policy and charging execution function entity PCEF serving the same session, and the associated entity establishes the association relationship of different PCEFs serving the session. Thereby, the relationship between different PCEFs under the same session is established. For example, in the scenario where the A-PCEF and the C-PCEF are used in the same IP CAN session, the association between the A-PCEF and the C-PCEF can be established by using the embodiment of the present invention.

In turn, multiple policy enforcement points can be supported to work together.

Further, the embodiment of the present invention also considers that the A-PCEF can be migrated to use the new The A-PCEF is updated with the previously registered A-PCEF, and it is necessary to ensure that the C-PCEF is not affected when the A-PCEF is migrated.

Further, the embodiment of the present invention further considers that the A-PCEF and the C-PCEF initiate the request at different time points, and the associated entity needs to have the ability to save the rule and associate the rule; and the rule modification and deletion request initiated by the terminal side, the associated entity. While maintaining the PCEF association relationship, the correspondence between the PCC rules on each PCEF needs to be maintained, so that the corresponding operation of the corresponding PCEF can be initiated in response to the request of the initiator PCEF. Therefore, in the process of configuring the PCC rules, the associated entity can ensure that the configuration status of each PCEF is consistent. If one party fails, the configuration instruction is sent to the PCEF that is successfully executed, and the state of the relevant rule is restored.

Further, in the embodiment of the present invention, the PCRF needs to return the access network information to the AF through the Rx interface during the establishment of the service. At this time, the associated entity blocks the PCEFs and the PDFs connected to the PCEFs to the AF side, and the associated entity selects one of the access network policy charging entity identifiers reported by the PCEF or the PDF, and uses the identifier to In the interaction of the AF, the access network policy charging execution entity is identified; or the associated entity allocates the access network integration policy charging entity identifier, and identifies the access network policy charging execution entity in the interaction with the AF. Therefore, the effect is that there is only one PCEF seen from the perspective of AF. If the associated entity is located in PDF, the PCRF only sees one PCEF, and after introducing multiple PCEFs in the architecture, it can also guarantee the original PCC architecture. Compatibility. The spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of the inventions

Claims

Claim

A method for associating a policy and a charging execution function entity, comprising: an association entity acquiring information of each policy and charging execution function entity PCEF serving the same session; and the associated entity establishing the session service The relationship between different PCEFs.

The method for associating a policy and the charging execution function entity according to claim 1, wherein the information obtained by the associated entity for each policy and the charging execution function entity PCEF for the same session includes:

The associated entity obtains the information of the A-PCEF in the process of initiating a rule configuration request for the session by the access service network A-PCEF;

According to the rule configuration request for the session initiated by the A-PCEF, the associated entity acquires the information of the C-PCEF from the assigned entity of the connection service network C-PCEF.

The method for associating a policy and charging execution function entity according to claim 1, wherein the information about the policy and the charging execution function entity PCEF that the associated entity obtains for the same session includes: A-PCEF And transmitting, by the A-PCEF, the information of the A-PCEF and the information of the C-PCEF, in the process of initiating the request by the A-PCEF.

The method for associating a policy and the charging execution function entity according to claim 3, wherein the A-PCEF includes the information of the C-PCEF in the rule configuration request for the session that is initiated by the A-PCEF: The A-PCEF obtains the information of the C-PCEF from the assigned entity of the C-PCEF in the authentication authentication process.

The method for associating a policy and the charging execution function entity according to claim 2 or 4, wherein the information of the A-PCEF and the information of the C-PCEF carry the identification information;

The identification information includes one or more of a PCEF identifier, a PCEF address, or a PCEF type.

The method for associating a policy and a charging execution function entity according to claim 2 or 4, wherein the allocation entity comprises: an authentication authentication charging AAA server, or a home contracting server HSS, or signing a contract Information database SPR.

The method for associating a policy and the charging execution function entity according to claim 1, wherein the information about the policy and the charging execution function entity PCEF that the associated entity obtains for the same session includes: A-PCEF And the C-PCEF respectively initiate a rule configuration request for the session,

And the associated entity acquires the information of the A-PCEF in the process of initiating the rule configuration request for the session by the A-PCEF; and acquiring the information of the C-PCEF.

The method for associating a policy and the charging execution function entity according to claim 7, wherein the rule configuration request for the session initiated by the A-PCEF and the C-PCEF respectively carries the User IP address and/or user ID corresponding to the session;

The associated entity determines that the user IP address and/or the user identifier carried in the rule configuration request initiated by the A-PCEF for the session is carried in the rule configuration request initiated by the C-PCEF for the session. The association relationship between the user IP address and/or the user identifier is established, and the association relationship between the A-PCEF and the C-PCEF is established.

The method for associating a policy and a charging execution function entity according to claim 7, wherein the rule configuration request of the session initiated by the A-PCEF and the C-PCEF respectively carries its own PCEF identification information;

The method for associating a policy and the charging execution function entity according to claim 1, wherein the method further comprises: after the associated entity acquires the information of each PCEF, when the PCEF is migrated When the PCEF is re-registered, the related information of the session corresponding to the PCEF registration is updated.

The method for associating a policy and the charging execution function entity according to claim 10, wherein when the association information is updated, the manner of indexing the PCEF information to be updated in the association information includes:

The associated entity maintains the correspondence between the address and type of the PCEF and according to the newly migrated PCEF address. Obtaining the PCEF type, and indexing the PCEF information to be updated according to the PCEF type; or

The associated entity directly indexes the PCEF information to be updated according to the newly migrated PCEF type; or

The associated entity indexes the PCEF information to be updated according to the indication of the newly migrated PCEF.

The method for associating a policy and the charging execution function entity according to claim 2, 3, or 7, wherein the method further comprises: the associated entity ensuring that the configuration status of each PCEF is consistent during the configuration process of the PCC rule .

The method for associating a policy and the charging execution function entity according to claim 12, wherein the PCEF saves the PCC rule corresponding to the session, and the associated entity further maintains the PCC rule saved in each PCEF. The relationship between the two.

The method for associating a policy and the charging execution function entity according to claim 1, wherein the PCEF saves the PCC rule corresponding to the session, and the associated entity further maintains the PCC rule saved in each PCEF. The relationship between the two.

The method for associating a policy and the charging execution function entity according to claim 13, wherein the manner in which the configuration of the PCEF is consistent, and the associated entity ensures that the configuration actions are consistent: When the rule function entity PCRF actively initiates the configuration request of the PCC rule, the associated entity sends a corresponding PCC rule and a configuration instruction to each PCEF according to the established association relationship of the PCEFs; or

When any one of the PCEFs initiates a PCC rule configuration request, the associated entity sends a PCC rule and a configuration indication corresponding to the PCEF to the PCEF that initiated the request according to the established association relationship between the PCEFs. And the associated entity sends a corresponding PCC rule and a configuration indication to the other PCEFs in the PCEFs.

The method for associating a policy and the charging execution function entity according to claim 15, wherein the configuration request of the PCC rule is directed to an existing service, and the associated entity further depends on the association. Rules and configuration instructions.

The method for associating a policy and charging execution function entity according to claim 15, wherein the configuration request of the PCC rule comprises: a PCC rule establishment request, a PCC rule modification request, or a PCC rule deletion request. , or a request for an IP session establishment, a request for an IP session modification, or a request for an IP session release.

The method for associating a policy and the charging execution function entity according to claim 13, wherein the manner in which the associated entity ensures that the configuration of the PCEF is consistent, and the manner in which the associated entity ensures that the configuration of the rule is consistent includes:

If the association entity learns that the part of the rule configuration result of the PCEF is a configuration failure, the corresponding PCC is respectively sent to the PCEF that is successfully configured according to the association relationship between the PCC rules saved in the PCEFs established by the associated entity. The rule and configuration indicator are used to restore the PCC rules in the PCEF with successful configuration.

19. The method of associating a policy and charging execution function entity according to claim 1, wherein the associated entity is located in a PDF, a visited V-PCRF, or a home H-PCRF.

The method for associating a policy and the charging execution function entity according to claim 1, wherein the associated entity shields the PCEF and the PDF connected to each PCEF to the application function entity AF side, and associates the entity Selecting one of the access network policy charging entity identifiers reported by the PCEF or the PDF, and marking the access network policy charging execution entity in the interaction with the AF by using the identifier; or, the associated entity allocates the access network policy charging The entity identifies and marks the access network policy charging enforcement entity in the interaction with the AF.

21. An associated entity, comprising:

An obtaining unit, configured to acquire information about each PCEF serving the same session;

A PCEF association unit is used to establish an association relationship between different PCEFs serving the session.

The associating entity according to claim 21, wherein the acquiring unit includes a first acquiring sub-unit, in the process of initiating a rule configuration request for the session by the access service network A-PCEF Obtaining the information of the A-PCEF; and formulating the rules for the session initiated by the A-PCEF The request is to obtain the information of the C-PCEF from the allocation entity that connects the service network C-PCEF. The PCEF association unit includes a first association sub-unit for establishing the association relationship between the A-PCEF and the C-PCEF.

The associating entity according to claim 21, wherein the acquiring unit includes a second obtaining subunit, configured to acquire the A-in the process of initiating a rule configuration request for the session from the A-PCEF. The information of the PCEF and the information of the C-PCEF are obtained from the information carried in the rule configuration request. The PCEF association unit includes a second association sub-unit for establishing an association relationship between the A-PCEF and the C-PCEF.

The associating entity according to claim 21, wherein the acquiring unit includes a third acquiring subunit, configured to acquire the A in the process of initiating a rule configuration request for the session by the A-PCEF. - information of the PCEF, and obtaining information of the C-PCEF in the process of initiating a rule configuration request for the session by the C-PCEF;

The PCEF association unit includes a third association sub-unit, configured to determine a user IP address and/or a user identifier carried in the rule configuration request initiated by the A-PCEF for the session, and is initiated by the C-PCEF. The association relationship between the user IP address and/or the user identifier carried in the rule configuration request of the session is established, and the association relationship between the A-PCEF and the C-PCEF is established.

The associated entity according to any one of claims 21 to 24, further comprising: a determining unit, configured to determine, after the obtaining unit acquires information about each PCEF in each PCEF, that the PCEF is A trigger signal is issued when a PCEF that is re-registered after migration occurs;

The updating unit is configured to update the association information of the session corresponding to the PCEF registration by using the trigger signal sent by the receiving determining unit as a trigger condition.

The associated entity according to any one of claims 21 to 24, further comprising: a PCC rule association unit, configured to obtain PCEF information of the existing association relationship from the PCEF association unit, and maintain the existing association relationship The association between PCC rules saved in PCEF.

The associated entity according to any one of claims 21 to 24, further comprising: a shielding unit, configured to shield the PCEF and the PDF connected to each PCEF to the AF side.

The associated entity according to any one of claims 21 to 24, wherein the associated entity is located in a PDF, a V-PCRF or an H-PCRF.

A system for associating a policy and a charging execution function entity, comprising: an associated entity, and each PCEF serving the same session;

And an associated entity, configured to acquire information about the PCEFs serving the same session, and establish an association relationship between the PCEFs.

30. A system for associating a policy and a charging enforcement function entity according to claim 29, wherein the associated entity is located in a PDF, a V-PCRF or an H-PCRF.