WO2008083621A1 - A service flow processing method and system, a method and system for associating a bear - Google Patents

Abstract

A service flow processing method and system and a method and system for associating a bear are provided to make clear of the associated processes in the service flow after incorporating the WiMAX network with the PCC framework. In the methods, a PCRF generates a PCC rule according to a policy decision(307A), after receiving a PCC rule request(304A), then provides the PCC rule and an authorized QoS to a PCC policy enforcement function entity in the WiMAX network(309A), and the PCC policy enforcement function entity performs the QoS policy control and charging (310A) according to the received PCC rule and authorized QoS. The various corresponding flows in the service process includes a preset stream establishment flow, a service establishment flow, a service modification flow and service deletion flow, etc.. The flows makes clear of the associated processes in the service flow relating to the WiMAX network after incorporating the WiMAX network with the PCC framework.

Description

 Business process processing method and system, method and system for bearing association

 The present invention relates to the field of Worldwide Interoperability for Microwave Access (WiMAX) network, especially when the WiMAX network convergence policy and the charging and charging control (PCC) are processed in the business process. Method and system.

Background technique

 The structure of the WiMAX network is shown in Figure 1A. The WiMAX network mainly includes three parts: a mobile terminal (MS), an access service network (ASN), and a connectivity service network (CSN). The ASN mainly includes a base station (BS) and an access service network gateway (ASN-GW); the CSN mainly includes a prepaid server (PPS) and authentication, authorization, and charging ( Authentication Authorization Accounting, AAA) A logical entity such as a server (AAA Server). The MS and the ASN are connected through the R1 interface. The MS and the CSN are connected through the R2 interface. The ASN and the CSN are connected through the R3 interface. The ASNs are connected through the R4 interface. The CSNs are connected through the R5 interface. The BS in the ASN is connected. Connected to the ASN-GW through the R6 interface. The wireless side, the R1 side, is based on the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard wireless metro access technology.

 The latest service quality of the WiMAX Network Work Group (NGWG) standard

The Quality of Service (QoS) framework is shown in Figure IB. The MS is the user's mobile terminal, and the user interacts with the network through the MS. The Service Flow Manager (SFM) is used to establish the user service flow and is established. The service flow allocates radio resources, etc., and the functional entity exists in the ASN; the service flow authorization (SFA) is used to authorize the service flow, and the functional entity exists in the ASN; the policy function entity (PF) use To provide a policy for the user's service flow, the functional entity is provided by the Network Service Provider (NSP). When the user roams, it will exist in the Visited PF (V-PF) and the Home PF (Home PF, In the H-PF), the AAA server is a system for providing authentication, authorization, and accounting services for storing user QoS descriptions and related policy rules; Application Function (AF) is a functional entity providing application services. The user's MS directly accesses the AF through the application layer protocol. The AF will notify the PF to actively create a service flow for the user. The functional entity is provided by the NSP.

FIG. 1C is a schematic diagram of the basic functional entity structure of the existing PCC architecture. As shown in FIG. 1C, the AF is a functional entity for providing applications, and these applications need dynamic policy control and charging control for the IP access network user plane. The Subscription Profile Repository (SPR) is used to store the subscription information of the user. The Policy Control and Charging Rules Function (PCRF) is used to perform control policy decision and flow-based charging policy decision. The execution control policy decision refers to the PCRF according to the service information from the AF. The subscription information in the SPR determines QoS authorization information, for example, QoS level, bit rate, etc. The flow-based charging policy decision means that the PCRF can use the subscription information as a benchmark for policy control decision and charging control decision, and determine the PCC rule. Provided to PCEF. The Policy Control and Charging Enforcement Function (PCEF) is used for QoS policy enforcement, service data flow detection, flow-based accounting, and gating. Service data flow detection refers to PCEF activation. The PCC Rule (PCC Rule) detects the service data flow to identify whether the data packet belongs to a service data flow. The execution of the QoS policy means that the PCEF performs authorized QoS control on a service data flow according to the activated PCC rule. Performing flow-based charging means that the PCEF charges the passed service data flow according to the charging policy and the Charging Key in the PCC rule, and the PCEF collects the charging information according to the charging requirement of the PCC rule. Reporting, the execution of the gate means that the PCEF only allows the service data stream to pass when the gate is opened. The Online Charging System (OCS) is used for online charging at the application layer. The PCEF requests the pre-paid quota from the OCS, and reports it to the online charging system in real time when the PCEF generates the bill. Offline billing system The Offline Charging System (OFCS) is used for offline charging at the application layer. The offline charging method is used. After the PCEF generates a bill, it reports to the OFCS periodically.

 Figure 2 is a schematic diagram of a WiMAX network and a PCC architecture. The PCEF is connected to the functional entity in the ASN-GW through the R3 interface, and is connected to the PCRF through the Gx interface. The PCEF acts as a protocol conversion between the PCRF and the functional entities of the ASN-GW. The PCEF can be further implemented as an implementation of the IP layer QoS policy control, that is, the PCEF converts the message from the Gx interface of the PCRF to the R3 interface and sends the message to the ASN-GW, and converts the message from the R3 interface of the ASN-GW into Gx. The message of the interface is sent to the PCRF. The PCEF may be specifically connected to the functional entity SFA in the ASN-GW, or the Data Path Function (DPF), or the Accounting Agent; or may be connected to the SFA, the DPF, and the charging agent respectively. PCC rules are used to distribute a service data stream to an IP Connectivity Access Network (IP-CAN) bearer. The PCC rules include: a PCC rule identifier (Rule ID), service data flow detection information, charging policy information, and policy control information.

 After the WiMAX network is integrated with the PCC architecture, the related processing in the business process involving the WiMAX network needs to be combined with the PCC architecture. However, the related processing in the business process after the WiMAX network and the PCC architecture are merged is not yet clear.

Summary of the invention

 In view of this, the embodiment of the present invention provides a service flow processing method, which clarifies related processing in a business process after a WiMAX network and a PCC architecture are merged.

 The technical solution adopted by the business process processing method in the embodiment of the present invention is as follows:

 A business process processing method, including:

 After receiving the PCC rule request, the PCRF generates a PCC rule according to the policy decision, and provides the PCC rule and the authorized QoS to the PCC policy enforcement entity in the global interoperability WiMAX network of the microwave access;

The PCC policy enforcement entity performs QoS policy control and charging based on the received PCC rules and authorized QoS. In the embodiment of the present invention, after receiving the PCC rule request, the PCRF generates a PCC rule according to the policy decision, and then provides a PCC rule and an authorized QoS to the PCC policy enforcement entity in the WiMAX network, and the PCC policy enforcement entity according to the received PCC rule and Authorize QoS to perform QoS policy control and charging. It is clear that the WiMAX network and PCC architecture are integrated, and the related processing in the business process involving WiMAX network is very beneficial to the promotion and application of WiMAX network.

 The embodiment of the present invention further provides another service flow processing method, which clarifies the processing of service deletion in the business process after the WiMAX network and the PCC architecture are merged.

 The technical solution adopted by the business process processing method in the embodiment of the present invention is as follows:

 A business process processing method, including:

 After receiving the PCC rule deletion request, the PCRF deletes the PCC rule and notifies the PCC policy enforcement entity in the WiMAX network to delete the PCC rule.

 The PCC policy enforcement entity deletes the PCC rule based on the received notification.

 In the embodiment of the present invention, after receiving the PCC rule deletion request, the PCRF deletes the PCC rule, and sends a PCC rule deletion notification to the PCC policy enforcement entity in the WiMAX network, and the PCC policy enforcement entity deletes the PCC rule according to the received notification. The embodiment of the invention clarifies the related processing of service deletion in the service process involving the WiMAX network after the WiMAX network is integrated with the PCC architecture, which is very beneficial to the promotion and application of the WiMAX network.

 The embodiment of the invention provides a business process processing system, which clarifies the related processing in the business process after the WiMAX network and the PCC architecture are merged.

 The technical solution adopted by the business process processing system in the embodiment of the present invention is as follows:

 A business process processing system, comprising:

 a PCC policy enforcement entity in the PCRF, PCEF, and WiMAX networks, where

 After receiving the PCC rule request, the PCRF generates a PCC rule according to the policy decision, and provides the PCC rule and the authorized QoS to the PCC policy enforcement entity;

The PCEF is configured to perform distribution/and or protocol conversion on a message exchanged between the PCRF and the PCC policy enforcement entity; The PCC policy enforcement entity is configured to perform QoS policy control and charging according to the received PCC rules and authorized QoS.

 In the embodiment of the present invention, after receiving the PCC rule request, the PCRF generates a PCC rule according to the policy decision, and then provides the PCC rule and the authorized QoS to the PCC policy enforcement entity in the WiMAX network. The PCC policy enforcement entity performs QoS policy control and charging according to the received PCC rules and authorized QoS, and clarifies the related processing in the service flow involving the WiMAX network after the WiMAX network and the PCC architecture are merged, which is very beneficial to the promotion of the WiMAX network. And application.

 The embodiment of the present invention further provides another service flow processing system, which clarifies the process of deleting the service in the business process after the WiMAX network and the PCC architecture are merged.

 The technical solution adopted by the business process processing system in the embodiment of the present invention is as follows:

 A business process processing system, comprising:

 a PCC policy enforcement entity in the PCRF, PCEF, and WiMAX networks, where

 After receiving the PCC rule deletion request, the PCRF deletes the PCC rule, and notifies the PCC policy enforcement entity to delete the PCC rule;

 The PCEF is configured to perform distribution and/or protocol conversion on a message exchanged between the PCRF and the PCC policy enforcement entity;

 The PCC policy enforcement entity is configured to delete the PCC rule based on the received notification.

 In the embodiment of the present invention, after receiving the PCC rule deletion request, the PCRF deletes the PCC rule, and sends a PCC rule deletion notification to the PCC policy enforcement entity in the WiMAX network, and the PCC policy enforcement entity deletes the PCC rule according to the received notification. The embodiment of the invention clarifies the related processing of service deletion in the service process of the WiMAX network after the WiMAX network is merged with the PCC architecture, which is very beneficial to the promotion and application of the WiMAX network.

 The embodiment of the invention provides a method for bearer association, which clarifies the process of implementing association between a PCC rule and a bearer.

 The technical solution adopted by the method for carrying the association in the embodiment of the present invention is as follows:

A method of bearing association, including: The PCRF receives the bearer identifier sent by the PCEF, and associates the PCC rule with the bearer; or

 The PCRF generates a bearer identifier and associates the PCC rule with the bearer; or

 The PCRF sends a PCC rule to the PCEF, the PCRF receives the bearer identifier sent by the PCEF, and associates the PCC rule with the bearer.

 The method for carrying the association in the embodiment of the present invention associates the PCC rule with the bearer through interaction between the PCEF and the PCRF, which facilitates accurate processing of the business process.

 The embodiment of the invention provides a system for bearer association, which clarifies the process of implementing association between a PCC rule and a bearer.

 The technical solution of the system for carrying the association in the embodiment of the present invention is as follows:

 A system for carrying associations, including:

 PCRF and PCEF, where

 The PCEF is configured to send a bearer identifier to the PCRF;

 The PCRF is configured to receive a bearer identifier sent by the PCEF, and associate the PCC rule with a bearer; or

 The PCRF is configured to generate a bearer identifier, and associate the PCC rule with the bearer; or the PCEF is configured to receive the PCC rule sent by the PCRF, and send the bearer identifier to the PCRF;

 The PCRF is configured to receive a bearer identifier sent by the PCEF, and associate the PCC rule with a bearer.

 In the embodiment of the present invention, the interaction between the PCEF and the PCRF is used to associate the PCC rule with the bearer, which facilitates accurate processing of the business process.

DRAWINGS

 1A is a schematic structural diagram of an existing WiMAX network;

 Figure 1B is a schematic diagram of an existing WiMAX NWG standard QoS framework;

1C is a schematic structural diagram of a basic functional entity of an existing PCC architecture; 2 is a schematic diagram of a fusion mode between a WiMAX network and a PCC architecture;

 FIG. 3A is a flowchart of establishing a preset flow initiated by an SFA according to an embodiment of the present invention;

 FIG. 3B is a flowchart of a preset flow establishment triggered by the AAA server transmitting the QoS description information to the SFA according to the embodiment of the present invention;

 FIG. 3C is a flowchart of a preset flow establishment triggered by a PCC rule issued by an AAA server according to an embodiment of the present invention;

 FIG. 3D is a flow chart of establishing a preset flow triggered by the AAA server sending the QoS description information to the PCRF according to the embodiment of the present invention;

 4 is a service establishment process initiated by a user side according to an embodiment of the present invention;

 FIG. 5 is a flowchart of a service establishment initiated by a network side according to an embodiment of the present invention;

 FIG. 6 is a flowchart of a service modification initiated by a user side according to an embodiment of the present invention;

 FIG. 7 is a flowchart of a service modification initiated by a network side according to an embodiment of the present invention;

 FIG. 8 is a flowchart of a service deletion initiated by a user side according to an embodiment of the present invention;

 FIG. 9 is a flowchart of a service deletion initiated by a network side according to an embodiment of the present invention;

 FIG. 10 is a schematic structural diagram of a system for implementing service flow processing according to an embodiment of the present invention.

detailed description

In the embodiment provided by the present invention, after receiving the PCC rule request, the PCRF generates a PCC rule according to the policy decision, and then provides a PCC rule and an authorized QoS to the PCC policy enforcement entity in the WiMAX network, and the PCC policy enforcement entity according to the received PCC Rules and Authorized QoS perform QoS policy control and accounting. After the authorization QoS provided to the PCC policy enforcement entity is generated, the PCRF may provide the PCC policy execution entity together with the PCC rule, or may include it in the PCC rule, and provide the PCC rule including the authorized QoS to the PCC rule. PCC policy enforcement entity. The PCC policy enforcement entity may include one of the entities such as SFA, Anchor DPF, Charging Agent, or any combination thereof. The PCC policy enforcement entity may further include a policy charging enforcement function entity within the home agent HA. When the PCC policy enforcement entity includes at least the SFA, the SFA performs QoS policy control according to the received PCC rule and the authorized QoS; when the PCC policy enforcement entity includes at least the anchor DPF, The anchor DPF classifies the data stream according to the received service data flow detection information; when the PCC policy execution entity includes at least the charging proxy, the charging proxy performs flow-based charging according to the charging policy information in the received PCC rule. Control; When the PCC policy enforcement entity includes at least the policy charging execution function entity in the home agent HA, the policy charging execution function entity in the HA performs QoS policy, charging, and data flow detection according to the received PCC rule and the authorized QoS. Further, the PCRF provides the PCC rule and the authorized QoS to the PCC policy enforcement entity through the PCEF; the PCEF forwards the message from the PCC policy enforcement entity to the PCRF, and if necessary, the PCEF first converts the message from the PCC policy enforcement entity into a Gx interface message and then forwards the message to the PCRF; and, the PCEF distributes the message from the PCRF to the PCC policy enforcement entity, if necessary, the PCEF first converts the message from the PCRF into a message within the WiMAX network and then distributes it to the PCC policy enforcement entity. The PCEF may be connected to only one functional entity in the PCC policy enforcement entity. For example, if the SFA receives the PCC rule information provided by the PCEF, the SFA may perform QoS policy control according to the received PCC rule and the authorized QoS. The charging policy information in the PCC rule is forwarded to the charging proxy, and the service data flow detection information in the PCC rule may be forwarded to the anchor DPF, and the PCC rule and the authorized QoS may be further forwarded to the policy charging execution in the HA. Functional entity. Performing flow-based charging control by the charging agent according to the received charging policy information, and classifying the data flow according to the received service data flow detection information by the anchor DPF, and the policy charging execution function entity in the HA is based on The received PCC rules and authorized QoS perform QoS policy, charging, and data flow detection. The PCEF may also be respectively connected to each functional entity of the PCC policy enforcement entity. For example, if connected to the SFA, the SFA performs QoS policy control according to the received PCC rule and the authorized QoS. If it is connected with the anchor DPF, the anchor DPF is anchored according to The service data flow detection information in the received PCC rule classifies the data flow, and if connected to the charging proxy, the charging proxy performs flow-based charging control according to the charging policy information in the received PCC rule, if Connected with the policy charging execution function entity in the home agent HA, the policy charging execution function entity in the home agent HA performs QoS policy, charging, and data flow detection according to the received PCC rules and authorized QoS.

The specific implementation of each related process involved in preset flow establishment, service establishment, service modification, and service deletion is described below. FIG. 3A is a flowchart of a preset flow establishment initiated by an SFA according to an embodiment of the present invention. As shown in FIG. 3A, after a WiMAX network is merged with a PCC architecture, a specific process of establishing a preset flow initiated by the SFA includes the following steps:

 Step 301 A to Step 302A: The initial authentication of the MS is completed, and the AAA server sends an Access-Accept message to the SFA, where the access permission message carries a User Profile.

Step 303A: After receiving the access permission message, the SFA waits for the MS IP address to allocate a PCC rule request that triggers the preset flow. The WiMAX network assigns an IP address to the MS. If the MS uses the Client Mobility Internet Protocol (CMIP) address, the IP address allocation process is the CMIP registration process. The specific processing is as follows: The foreign agent (FA) located in the ASN-GW sends the CoA address to the MS ( Care-of-Address, care-of address;); After receiving the CoA address, the MS initiates a Mobile IP (Mobility Internet Protocol, MIP) registration to the FA to register the MIP. If the MS uses a Proxy Mobility Internet Protocol (PMIP) address, the IP address allocation process is a Dynamic Host Configuration Protocol (DHCP) process. The specific processing is as follows: The MS sends a DHCP proxy to the ASN-GW. The DHCP Proxy/Relay server sends a DHCP Discover message requesting an IP address, and the DHCP proxy relays the DHCP Discover message to the DHCP server located in the CSN. After receiving the DHCP Discover message, the DHCP server is The MS assigns an IP address and provides the IP address to the MS through the DHCP proxy/relay server. After receiving the IP address, the MS sends a DHCP request (DHCP Request) to the DHCP server through the DHCP proxy/relay server, and the DHCP server receives the DHCP address. after the request, returns a DHCP response (DHCPAck) ₀ to the MS through the DHCP proxy / relay server

 Step 304A: After the MS IP address is successfully allocated, the PCC policy enforcement entity initiates a PCC rule request of the preset stream. The following takes the SFA in the PCC Policy Enforcement Entity as an example. The SFA sends a PCC rule request to the PCEF, where the PCC rule request carries the user identifier, the MS IP address, and the bearer type.

Step 305A: After receiving the PCC rule request, the PCEF requests the PCC rule to be cancelled by the R3 interface. The information is converted into a Gx interface message, and a Credit-Control-Request (CCR) is sent to the PCRF, and the PCEF sets the parameter CCR type (CC-Request-type) carried in the CCR to an initial request (INITIAL-REQUEST). In order to indicate to the PCRF that the current process is an IP-CAN session establishment, the CCR also carries a user identifier, an MS IP address, and a bearer type.

 Step 306A: After receiving the CCR, the PCRF obtains the QoS description information by interacting with the AAA server.

 Alternatively, the QoS description information may be actively provided to the PCRF by the AAA server after the access authentication succeeds. In this case, the step and the steps 303A to 305A are not performed in strict time sequence.

 Step 307A: The PCRF makes a policy decision according to the received QoS description information, generates a PCC rule and an authorized QoS, and stores the PCC rule and the authorized QoS.

 The user description is only part of the information in the user subscription information, and the information contained therein is not enough to establish a preset stream. The QoS description information refers to the information part of the user subscription information related to the preset stream. Therefore, the PCRF only obtains the QoS description. Information, in order to establish a preset stream.

 Step 308A: The PCRF sends a Credit-Control-Answer (CCA) to the PCEF, where the CCA carries the PCC rule and the authorized QoS.

 Through steps 305A and 308A, a session of the Gx interface is established between the PCRF and the PCEF, and the PCRF stores and maintains the user identifier, the MS IP address, the Gx interface session identifier, and the corresponding relationship.

 Step 309A: After receiving the CCA, the PCEF converts the CCA from the Gx interface message to the R3 interface message, and sends the PCC rule information and the authorized QoS to the SFA.

 Step 310A: After receiving the PCC rule information and the authorized QoS, the SFA performs QoS policy control according to the PCC rule information and the authorized QoS.

 Step 311A: The SFA initiates establishment of an air interface side and a network side bearer.

FIG. 3B is a flow chart of establishing a preset flow triggered by the AAA server transmitting the QoS description information to the SFA according to the embodiment of the present invention. As shown in FIG. 3B, after the WiMAX network is integrated with the PCC architecture, the AAA monthly service is performed. The specific processing procedure of the preset flow establishment triggered by the QoS description information sent by the SFA includes the following steps:

 Step 301B to step 302B: The initial network access authentication of the MS is completed, and the AAA server sends an access permission message to the SFA, where the access permission message carries the user description and the QoS description information.

 Step 303B: After receiving the access permission message, the SFA waits for the MS IP address to be allocated. The WiMAX network assigns an IP address to the MS. If the MS uses the CMIP address, the IP address allocation process is the CMIP registration process. The specific processing is as follows: The FA in the ASN-GW sends a CoA address (Care-of-Address) to the MS. After the MS receives the CoA address, Initiate a MIP registration with the FA to register the MIP. If the MS uses the PMIP address, the IP address allocation process is a DHCP process. The specific processing is as follows: The MS sends a DHCP discovery message request IP address to the DHCP proxy/relay server located in the ASN-GW, and the DHCP proxy relays the server to the CSN. The DHCP server forwards the DHCP discovery message. After receiving the DHCP discovery message, the DHCP server allocates an IP address to the MS and provides the IP address to the MS through the DHCP proxy/relay server. After receiving the IP address, the MS passes the DHCP. The proxy/relay server sends a DHCP request to the DHCP server. After receiving the DHCP request, the DHCP server returns a DHCP response to the MS through the DHCP proxy/relay server.

 Step 304B: After the MS IP address is successfully allocated, the PCC policy enforcement entity initiates a PCC rule request. The following takes the SFA in the PCC Policy Enforcement Entity as an example. The SFA sends a PCC rule request to the PCEF, where the PCC rule request carries the user identifier, the MS IP address, and the QoS description information.

 Step 305B: After receiving the PCC rule request, the PCEF converts the PCC rule request from the R3 interface message to the Gx interface message, and sends a CCR to the PCRF. The PCEF sets the parameter CCR type carried in the CCR as an initial request, to indicate the current to the PCRF. The process is established for an IP-CAN session, and the CCR also carries a user identifier, an MS IP address, and QoS description information.

 Step 306B: After receiving the CCR, the PCRF makes a policy decision according to the received QoS description information, generates a PCC rule and an authorized QoS, and stores the PCC rule and the authorized QoS.

Step 307B: The PCRF sends a CCA to the PCEF, where the CCA carries the PCC rules and grants QoS.

 Through steps 305B and 307B, a session of the Gx interface is established between the PCRF and the PCEF, and the PCRF stores and maintains the user identity, the MS IP address, the Gx interface session identifier, and the corresponding relationship.

 Step 308B: After receiving the CCA, the PCEF converts the CCA from the Gx interface message to the R3 interface message, and sends the PCC rule information and the authorized QoS to the SFA.

 Step 309B: After receiving the PCC rule information and the authorized QoS, the SFA performs QoS policy control according to the PCC rule information and the authorized QoS.

 Step 310B: The SFA initiates establishment of an air interface side and a network side bearer.

 FIG. 3C is a flowchart of a preset flow establishment triggered by a PCC rule issued by an AAA server according to an embodiment of the present invention. As shown in FIG. 3C, after the WiMAX network is merged with the PCC architecture, the specific processing of the preset flow establishment of the PCC rule issued by the AAA server is performed. The process includes the following steps:

 Step 301C to step 302C: The initial network access authentication of the MS is completed, and the AAA server provides the user description and QoS description information to the PCRF, and triggers the request of the PCC rule.

 Step 303C: The PCRF makes a policy decision according to the received QoS description information, generates a PCC rule and an authorized QoS, and stores the PCC rule and the authorized QoS.

 Step 304C: The PCRF provides PCC rules and authorized QoS to the AAA server.

 Step 305C: After receiving the PCC rule and the authorized QoS, the AAA server sends an access permission message to the SFA to trigger the establishment of the preset flow, where the access permission message carries the PCC rule and the authorized QoS. Further, PCC rules and authorized QoS will also be provided to other PCC policy enforcement entities.

Step 306C: After receiving the access permission message, the SFA waits for the IP address to be allocated. The WiMAX network assigns an IP address to the MS. If the MS uses the CMIP address, the IP address allocation process is the CMIP registration process. The specific processing is as follows: The FA in the ASN-GW sends a CoA address to the MS. After receiving the CoA address, the MS initiates MIP registration to the FA to register the MIP. If the MS uses the PMIP address, the IP address allocation process is a DHCP process. The specific processing is as follows: The MS sends a DHCP discovery message request IP address to the DHCP proxy/relay server located in the ASN-GW, DHCP proxy/ The relay server forwards the DHCP discovery message to the DHCP server located in the CSN; after receiving the DHCP discovery message, the DHCP server allocates an IP address to the MS, and provides the IP address to the MS through the DHCP proxy/relay server; the MS receives the IP address. After the address, the DHCP proxy/relay server sends a DHCP request to the DHCP server. After receiving the DHCP request, the DHCP server returns a DHCP response to the MS through the DHCP proxy/relay server.

 Step 307C: After the MS IP address is successfully allocated, the SFA modifies the classifier information in the PCC rule according to the MS IP address, so that the classifier adapts to the MS IP address, and then performs QoS policy control according to the PCC rule information and the authorized QoS. The classifier information in the PCC rule is generated by the PCRF, that is, the service data flow template in the PCC rule, and finally delivered to the anchor DPF for the detection of the service data stream.

 Step 308C: The SFA sends an IP-CAN session establishment indication to the PCEF, where the IP-CAN session establishment indication carries the MS IP address.

 Step 309C: After receiving the IP-CAN session establishment indication, the PCEF converts the IP-CAN session establishment indication from the R3 interface message to the Gx interface message, and sends a CCR to the PCRF to indicate to the PCRF that the IP-CAN session has been established, in the CCR. Carry the MS IP address.

 A session of the Gx interface is established between the PCRF and the PCEF through the steps 305C and 309C. The PCRF stores and maintains the user identity, the MS IP address, the Gx interface session identifier, and the corresponding relationship.

 Step 310C: After receiving the CCR, the PCRF sends a CCA to the PCEF to return to the IP-CAN session to establish a response.

 Step 311 C: After receiving the CCA, the PCEF sends an IP-CAN session establishment response to the SFA. Step 312C: After receiving the IP-CAN session establishment response, the SFA initiates establishment of the air interface side and the network side bearer.

3D is a flow chart of establishing a preset flow triggered by the AAA server transmitting the QoS description information to the PCRF according to the embodiment of the present invention. As shown in FIG. 3D, after the WiMAX network is merged with the PCC architecture, the AAA server delivers the QoS description to the PCRF. The specific processing of the preset flow of information includes the following steps: Steps 301D to 302D: The initial network access authentication of the MS is completed, and the AAA server sends an access permission message to the SFA, where the access permission message carries the user description.

 Step 303D: After receiving the access permission message, the SFA sends an SFA indication message to the PCEF, where the SFA indication message carries the user identifier and the SFA identifier.

 Step 304D: After receiving the SFA indication message, the PCEF sends a PCEF indication message to the PCRF, where the PCEF indication message carries the user identifier and the PCEF identifier. This step can be omitted if the PCRF is only connected to one PCEF.

 Step 305D: The AAA server sends the QoS description information and the Acct-Multi-Session-ID to the PCRF, and the charging multi-session identifier is used to perform charging association in the charging system.

 Steps 303D to 304D and step 305D are not strictly performed in time. As long as they are executed after step 302D, steps 303D to 304D may be performed first, and then step 305D may be performed. Step 305D may be performed first. Steps 303D to 304D are performed; Steps 303D to 304D and Step 305D can also be performed simultaneously.

 Step 306D: The PCRF makes a policy decision according to the received QoS description information, generates a PCC rule and an authorized QoS, and stores the PCC rule and the authorized QoS.

 Step 307D: The PCRF sends a Re-Auth-Request (RAR) to the PCEF, where the RAR carries the PCC rule, the authorized QoS, and the charging multi-session identifier.

 Step 308D: After receiving the RAR, the PCEF converts the RAR from the Gx interface message to the R3 interface message, and sends a resource reservation request message to the PCC policy enforcement entity, where the resource reservation request message carries the PCC rule information, the authorized QoS, and The multi-session ID is used for charging. The SFA in the PCC policy enforcement entity is used as an example to describe the subsequent steps.

Step 309D: After receiving the resource reservation request message, the SFA waits for the IP address to be allocated. The WiMAX network assigns an IP address to the MS. If the MS uses the CMIP address, the IP address allocation process is the CMIP registration process. The specific processing is as follows: The FA in the ASN-GW sends a CoA address to the MS. After receiving the CoA address, the MS initiates MIP registration to the FA to register the MIP. If the MS uses the PMIP address, the IP address allocation process is a DHCP process, and the specific processing is as follows: The MS is located at the ASN-GW. The DHCP proxy/relay server sends a DHCP discovery message requesting an IP address, and the DHCP proxy/relay server forwards the DHCP discovery message to a DHCP server located in the CSN; after receiving the DHCP discovery message, the DHCP server assigns an IP address to the MS. And providing the IP address to the MS through the DHCP proxy/relay server; after receiving the IP address, the MS sends a DHCP request to the DHCP server through the DHCP proxy/relay server, and after receiving the DHCP request, the DHCP server passes the DHCP proxy/relay The server returns a DHCP response to the MS.

 Step 310D: After the MS IP address is successfully allocated, the SFA modifies the classifier information in the PCC rule according to the MS IP address, so that the classifier adapts to the MS IP address, and then performs QoS policy control according to the PCC rule information and the authorized QoS.

 Step 311 D: The SFA initiates establishment of an air interface side and a network side bearer.

 Step 312D: The SFA sends a resource reservation response message to the PCEF, where the resource reservation response message carries an MS IP address.

 Step 313D: After receiving the resource reservation response message, the PCEF converts the resource reservation response message from the R3 interface message to the Gx interface message, and sends a Re-Auth- Answer (RAA) to the PCRF, where the RAA carries MS IP address.

 Through steps 307D and 313D, a session of the Gx interface is established between the PCRF and the PCEF, and the PCRF stores and maintains the user identity, the MS IP address, the Gx interface session identifier, and the corresponding relationship.

In the process of establishing the preset flows, the SFA may also establish an initial service flow (ISF) before the IP address allocation process of the MS, and the ISF information may be pre-configured in the ASN. The IP address allocation process of the MS and the execution of the preset stream establishment process are not strictly time-ordered. If the IP address of the MS is allocated before the PCRF makes a policy decision and the PCC rule information is sent, the classifier in the PCC rule does not need to be modified because of the subsequent MS IP address allocation. The PCC policy enforcement entity directly according to the received PCC rule. Information execution policy, billing, and data flow detection. If the IP address of the MS is allocated after the PCRF makes a policy decision and the PCC rule information is sent, the classifier in the PCC rule needs to be modified accordingly. At this time, the PCC policy enforcement entity is based on the obtained MS. The IP address is modified to the classifier in the PCC rule, and the MS IP address can be reported in the subsequent step of interacting with the PCRF, or a new interaction with the PCRF is initiated, and the MS IP address is reported. Further, during the subsequent interaction with the PCRF, the PCC policy enforcement entity may also trigger the request or modification of the related PCC rule information.

 FIG. 4 is a flow chart of the service establishment initiated by the user side in the embodiment of the present invention. As shown in FIG. 4, after the WiMAX network is merged with the PCC architecture, the specific processing of the service establishment initiated by the user side includes the following steps:

 Step 401: The MS interacts with the AF through application layer session signaling to request service establishment. Step 402: The AF determines the QoS parameters required by the service, and sends an authentication authorization request (AA-Request, AAR) to the PCRF, where the AAR carries related service information such as a user identifier, an application layer charging identifier, and a media description information, where The media description information includes service QoS parameters such as a classifier, a bandwidth requirement, and a media type. The AAR may further carry a specific behavior (Specific-Action) parameter to instruct the PCRF to request complete service information from the AF in the resource reservation process. And/or indicate whether the AF is notified after the subsequent resource flow is completed. In order to meet the needs of the WiMAX network, the media description information provided by the AF to the PCRF may further include WiMAX content, such as a Reduced Resource indication, a QoS Priority, and a Combined Resource Request. ) and other information. If the media description information provided by the AF to the PCRF does not include the above content, the PCRF may determine the content according to a pre-configured policy, or user subscription information, or user subscription information combined with a pre-configured policy. The PCRF needs to provide WiMAX content to the SFA via PCEF, which requires an extension of the Gx interface to enable WiMAX content to be transmitted over the interface.

 Step 403: After receiving the AAR, the PCRF performs QoS authorization and storage on the received service information, and associates the AF session to the corresponding IP-CAN session according to the user IP address and/or the user identifier in the service information. Right 4 is authorized to respond (AA- Answer, AAA).

Step 404: The MS initiates an IP-CAN bearer setup for the AF session, such as a Dynamic Service Addition (DSA) request sent to the SFA through the R1 interface and the R6/R4 interface (DSA). Request ), resource reservation request message.

 Step 405: The PCC policy enforcement entity sends a resource reservation request message to the PCEF. The following steps are taken as an example of the SFA in the PCC policy enforcement entity. The resource reservation request message carries a user identifier, a traffic flow template (TFT) generated by the MS, and bearer setup information. The TFT is generated by the MS and provided to the PCRF through the SFA and the PCEF for subsequent session association.

 Step 406: After receiving the resource reservation request message, the PCEF converts the resource reservation request message from the R3 interface message to the Gx interface message, and sends a CCR to the PCRF to request the PCC rule, where the CCR carries the user identifier and the TFT generated by the MS. And bearer establishment information. The PCEF can generate a bearer identifier and include it in the CCR message and send it to the PCRF.

 Since the bearer and the service can be separated in the PCC architecture, the PCRF must also be informed that the CCR message is used to request a PCC rule for the AF session by: the CCR message does not carry a charging report (charging-rule-report AVP), thereby indicating Requesting a PCC rule; or, adding a new display identifier to the CCR message to indicate a request for a PCC rule, such as an empty charging-rule-install AVP; or, specifying a bearer and a service in the WiMAX network, corresponding to the operation of the bearer For the PCC rule operation of the service, the CCR message carries a bearer identifier and a bearer setup indication, or a TFT, to indicate the request for the PCC rule.

 Step 407: After receiving the CCR, the PCRF stores the bearer setup information, and associates the PCC rule request to the corresponding AF session according to the classifier in the access network information.

 Step 408: If the AAR carried by the AF carries the Specific-Action parameter in the step 402, and the Specific-Action parameter is used to indicate that the PCRF requests complete service information from the AF in the resource reservation process, the PCRF passes the AF The interaction obtains relevant business information.

 Step 409: The PCRF also obtains the user subscription information through interaction with the SPR when the user subscription information is required. If user subscription information is already stored in the PCRF, this step can be omitted.

Step 408 and/or step 409 may be omitted. In addition, in the case that both step 408 and step 409 need to be performed, steps 408 and 409 have no strict time sequence in execution, as long as they are both After the step 407 is performed, the step 408 may be performed first, and then the step 409 may be performed; or the step 409 may be performed first, and then the step 408 may be performed; and the step 408 and the step 409 may be performed simultaneously.

 Step 410: The PCRF makes a policy decision according to the received user subscription information and the service QoS parameter: if the QoS resource in the access network information obtained from the PCEF can satisfy the authorized QoS for the service in step 403, the authorized QoS for the service As the authorized QoS for this decision, a PCC rule is generated according to the policy decision, and the PCC rule and the authorized QoS are stored;

 Otherwise, the PCRF reduces the authorized QoS of the service so that it can be satisfied by the access network QoS resources, and the reduced QoS is used as the authorized QoS for the decision, and the PCC rule is generated according to the policy decision, and the PCC rule and the authorized QoS are generated. The storage is performed; or the PCRF rejects the establishment of the service, and the service establishment process is terminated.

 In the case of a PCRF control bearer, if the PCEF informs the PCRF of the bearer identity in step 406, the PCRF associates the PCC rule with the bearer. Otherwise, the PCRF generates a bearer identity and associates the PCC rule with the bearer. The embodiment of the present invention can interact with the PCRF through the PCEF through the foregoing method or system, so that the PCRF can associate the PCC rule with the bearer. The PCRF may further generate a Packet Data Flow ID and a Service Data Flow ID, and the Packet Data Flow identifier is used to associate the packet data flow to the service flow, that is, associate the packet data flow identifier with the corresponding Business data flow identifier.

 Step 411: The PCRF sends CC A to the PCEF, where the CCA carries the PCC rule and the authorized QoS. If the bearer identifier is generated by the PCRF in step 410, the CCA message may also carry a bearer identifier, which is included in the charging-rule-installAVP of the CCA message. If the A-AR sent by the AF carries the Specific-Action parameter, and the Specific-Action parameter is used to notify the AF after the subsequent resource process is completed, the CCA further carries the Specific-Action parameter.

Step 412: After receiving the CCA, the PCEF converts the CCA from the Gx interface message to the R3 interface message, and sends a resource reservation response message to the SFA, where the resource reservation response message carries the PCC rule information and the authorized QoS. Step 413: After receiving the resource reservation response message, the SFA performs QoS policy control according to the received PCC rule information and the authorized QoS.

 Step 414 to step 415: The SFA returns an IP-CAN bearer setup response to the MS, such as a resource reservation response message, a DSA Response (DSA Response) sent to the MS through the R6/R4 interface and the R1 interface. „If the AAR is in step 402, Further carrying a specific-Action parameter, the specific-Action parameter is used to indicate that the PCRF reports the related event to the AF after the resource reservation is completed, and the CCA delivered by the PCRF further carries the same Specific-Action parameter in step 411. Then, the SFA reports the bearer establishment report to the AF through the PCEF and the PCRF.

 Step 416: The AF and the MS continue application layer interaction through application layer session signaling, and respond to service establishment.

 FIG. 5 is a flow chart of the service establishment initiated by the network side in the embodiment of the present invention. As shown in FIG. 5, after the WiMAX network is merged with the PCC architecture, the specific processing process initiated by the network side includes the following steps:

 Step 501: The MS interacts with the AF through application layer session signaling to request service establishment. Step 502: The AF determines the QoS parameters required by the service, and sends an AAR to the PCRF, where the AAR carries related service information such as a user identifier, an application layer charging identifier, and a media description information, where the media description information includes a classifier and a bandwidth requirement. Service QoS parameters such as media type; The AAR may further carry a Specific-Action parameter to instruct the PCRF to request complete service information from the AF in the resource reservation process, and/or to indicate whether to notify the AF after the subsequent resource process is completed. In order to meet the needs of the WiMAX network, the media description information provided by the AF to the PCRF may further include WiMAX content (WiMAX Content), such as resource reduction indication, QoS priority, combined resource request and the like. If the media description information provided by the AF to the PCRF does not include the above content, the PCRF may determine the content according to a pre-configured policy, or user subscription information, or user subscription information combined with a pre-configured policy. The PCRF needs to provide WiMAX content to the SFA via PCEF, which requires the Gx interface to be extended to enable WiMAX content to be transmitted over the interface.

Step 503: After receiving the AAR, the PCRF stores the service information. Step 504: When the PCRF further needs the user subscription information, the user subscription information is obtained through interaction with the SPR.

 Step 505: The PCRF associates the AF session to the corresponding IP-CAN session according to the access network information acquired from the PCEF and the service information previously acquired from the AF, and indexes to the corresponding PCEF. The PCRF makes policy decisions based on the received user subscription information and QoS parameters. When the AF QoS requirements are met, the PCC rules and authorized QoS are generated according to the policy decision, and the PCC rules and authorized QoS are stored. In the case of a PCRF control bearer, the PCRF may generate a bearer identity and associate a PCC rule with the bearer. The PCRF may further generate a packet data flow identifier and a service data flow identifier, the packet data flow identifier being used to associate the packet data flow to the service flow, that is, to associate the packet data flow identifier to the corresponding service data flow identifier.

 Step 506: The PCRF sends a RAR to the PCEF, where the RAR carries the PCC rule and the authorized QoS. If the PCRF generates the bearer identifier in the step 505, the Charing-rule-install AVP of the RAR message carries the identifier.

 Step 507: After receiving the RAR, the PCEF converts the RAR from the Gx interface message to the R3 interface message, and sends a resource reservation request message to the PCC policy enforcement entity, where the resource reservation request message carries the PCC rule information and the authorized QoS. The following steps are described by taking the SFA in the PCC policy enforcement entity as an example.

 Step 508: After receiving the resource reservation request message, the SFA performs QoS policy control according to the received PCC rule information and the authorized QoS.

 Step 509: The SFA initiates an IP-CAN bearer setup of the service session.

 Step 510: The SFA sends a resource reservation response message to the PCEF, where the resource reservation response message carries the bearer establishment result and the charging association information.

Step 511: After receiving the resource reservation response message, the PCEF converts the resource reservation response message from the R3 interface message to the Gx interface message, and sends the RAA to the PCRF, where the RAA carries the bearer establishment result and the charging association information. The RAA may further carry a rule modification report for identifying the PCC rules that have been processed. If the PCRF does not generate a bearer identifier in step 505, the PCEF at this time A bearer identifier is generated for the bearer, and can be carried in the RAA message and reported to the PCRF. If the PCEF does not report the bearer identifier to the PCRF, the PCF can interact with the PCRF again after the step, for example, through CCR and CCA message interaction. The bearer ID is informed to the PCRF. The embodiment of the present invention can interact with the PCRF through the PCEF through the foregoing method or system, so that the PCRF can associate the PCC rule with the bearer.

 Step 512: After the RAF receives the RAA, if the RAA message includes the bearer identifier, the PCC rule is associated with the bearer, and then the AAA message is sent to the AF. Otherwise, the PCEF is again required to interact with the PCRF to report the bearer identifier, and the PCC rule is The bearer is associated and then sends an AAA to the AF. The foregoing AAA carries a media stream establishment result, and the media stream establishment result may include an Access-Network-Charging Address and an Access-Network-Charging ID.

 Step 513: The AF and the MS continue application layer interaction through application layer session signaling, and respond to service establishment.

 The process of establishing the above service flow may involve gating of the traffic flow. In the AAR message sent by the AF to the PCRF, the gating information of the media stream is carried in each of the media descriptions, indicating that the gating status of the media stream is enabled or disabled. After receiving the AAR message, the PCRF also carries the gating information in the RAR message or the CCA message sent to the PCEF. In the subsequent process, the PCEF also needs to forward the received gating information to the PCC policy enforcement entity. Indicates the gating operation carried on this traffic flow.

 The process of performing the gating is as follows. The gating execution entity classifies the received data packet into a specific service flow, and then according to the gating state of the service flow, if the status is enable, the normal transmission is performed. Packet; if the status is disable, the packet is discarded.

Gating can be performed by the ASN-GW or BS. If the gate is controlled by the ASN-GW, the execution of the gating is: after receiving the gating information sent by the PCEF, the ASN-GW performs gating according to the gating information, that is, turns on or off the corresponding service flow bearer, and then A response message is returned to the PCEF. If the gating is performed by the BS, the execution gating is: after the PCEF sends the gating information to the ASN-GW, the ASN-GW The gate information must be delivered to the BS through the R6 interface message, and the BS performs the gating according to the received gating information, that is, the corresponding service flow bearer is turned on or off, and then the BS returns a response message to the ASN-GW.

The ASN-GW returns a response message to the PCEF.

 If the gate is performed by the BS, the R6 interface message needs to be extended to carry the gating information.

 The MS may also participate in the gated execution, and the gating information needs to be passed in the air interface DSA/DSC message. Figure 6 is a flowchart of the service modification initiated by the user side in the embodiment of the present invention. As shown in Figure 6, after the WiMAX network is integrated with the PCC architecture, the specific processing of the service modification initiated by the user side includes the following steps:

 Step 601: The MS interacts with the AF through application layer session signaling to request service modification. Changes to the business may involve QoS updates, or route optimizations, or updates to the classifier.

 Step 602: When the modification of the service involves modifying the service information, the AF determines the modified service information, and sends an AAR to the PCRF, where the AAR carries related service information such as a user identifier, an application layer charging identifier, and a media description information, where The media description information includes service QoS parameters such as a classifier, a bandwidth requirement, and a media type. The AAR may further carry a Specific-Action parameter to instruct the PCRF to request complete service information from the AF during the resource reservation process, and/or to indicate whether the AF is notified after the subsequent resource process is completed.

 Step 603: After receiving the AAR, the PCRF stores the service information, and performs an authorization operation on the modified service QoS parameter. If the PCRF does not have enough user information to support the current authorization, the PCRF obtains the user subscription information through interaction with the AAA server. After the authorization is completed, the PCRF sends AAA to the AF. If the PCRF has obtained the access network charging identifier at this time, and has not been provided to the AF before, the AAA carries the access network charging identifier.

 When the modification of the service does not involve modifying the service QoS parameters, steps 602 to 603 may be omitted. Step 604: The MS initiates an IP-CAN bearer modification request, such as a Dynamic Service Change (DSC) request (DSC Request) and a resource modification request message sent to the SFA through the R1 interface and the R6/R4 interface.

Step 605: The PCC policy enforcement entity sends a resource modification request message to the PCEF, where the resource is repaired. The request message carries the user ID, the PCC rule identifier, and the bearer modification information. The SFA in the PCC policy enforcement entity is used as an example to describe the subsequent steps.

 When the service modification involves only the modification of the classifier, such as the change of the source address and/or the destination address of the data packet caused by the route optimization, the SFA may not modify the classifier rule by interacting with the PCRF. Whether the modification of the classifier needs to interact with the PCRF, the SFA can be obtained by the description of the event trigger (Event Trigger) in the previously received PCC rule information, and the event triggering in the original PCC protocol is extended to support WiMAX network.

 Step 606: After receiving the resource modification request message, the PCEF converts the resource modification request message from the R3 interface message to the Gx interface message, and sends a CCR to the PCRF, where the CCR carries the user identifier, the PCC rule identifier, and the bearer modified content. The PCEF may include the bearer identifier corresponding to the currently modified bearer in the CCR message and send it to the PCRF.

 Since the bearer and the service can be separated in the PCC architecture, the PCRF must also be informed that the CCR message is used to modify the PCC rule for the AF session request. The method is as follows: The CCR message carries an event trigger (event-trigger) and a rule report to indicate the request modification. PCC rules, where event-trigger is used to indicate service modification, and rule report charging-rule-report is used to indicate corresponding PCC rules; or, a new display identifier is added to the CCR message to indicate that the request to modify a specific PCC rule, for example, carrying one Charging-rule-installAVP, which carries the PCC rule identifier or name; or, specifies that the bearer in the WiMAX network corresponds to the service, and the operation of the bearer corresponds to the PCC rule operation of the rule-based service, then the CCR message The rule identifier or rule name is carried, or the modification information is carried, to indicate that the request to modify the PCC rule.

Step 607: After receiving the CCR, the PCRF performs an authorization operation on the content that carries the modification. When the modification of the QoS is involved, if the resource corresponding to the QoS modification is consistent with the previous negotiation, such as the negotiation in step 602 to step 603 or the negotiation in the establishment of the service, the PCRF may perform the authorization operation directly; if the QoS is modified, the corresponding The resources are inconsistent with the previous negotiation, or the resources corresponding to the QoS modification are inconsistent with the previous negotiation, and the information obtained by the PCRF is insufficient to complete the authorization operation, and the PCRF can be based on the correspondence between the previous PCC rules and the AF session. Select the corresponding Rx interface The session interacts with the AF through the Rx interface session to obtain sufficient authorization related information, such as service information, and then performs an authorization operation. During this process, the AF can also perform authorization operations. If necessary, the PCRF can also obtain user subscription information through interaction with the AAA server. When it comes to the modification of the classifier, the PCRF can directly select the authorization operation.

 Step 608: After performing the authorization operation, the PCRF performs a policy decision according to the modified content of the bearer, generates a PCC rule, and then modifies the PCC rule, and stores the modified PCC rule and the authorized QoS. Here, generating a PCC rule may refer to an alternative to the original PCC rule, that is, the PCRF replaces the corresponding original content with the modified PCC rule content instead of generating a complete new PCC rule. If the PCEF informs the PCRF of the bearer identity in step 606, the PCRF may associate the PCC rule with the bearer. Otherwise, the PCRF may select the bearer identifier corresponding to the currently modified bearer and associate the PCC rule with the bearer. In the embodiment of the present invention, the PCRF implements the association between the PCC rule and the bearer in the foregoing manner.

 Step 609: The PCRF sends a CCA to the PCEF, where the CCA carries the modified PCC rules and authorized QoS. If the bearer identifier is selected by the PCRF in step 608, the CCA message may also carry a bearer identifier, which is included in the charging-rule-install AVP of the CCA message. If the AAR carried by the AF carries the Specific-Action parameter in the process of the VP or the previous service establishment process, and the specific-Action parameter is used to notify the AF after the subsequent resource process is completed, the CCA further carries the Specific -Action parameter.

 Step 610: After receiving the CCA, the PCEF converts the CCA from the Gx interface message to the R3 interface message, and sends a resource modification response message to the SFA, where the resource modification response message carries the modified PCC rule information and the authorized QoS.

 Step 611: After receiving the resource modification response message, the SFA performs QoS policy control according to the received PCC rule information and the authorized QoS.

Step 612 to step 613: The SFA returns an IP-CAN bearer modification response to the MS, such as a resource modification response message sent to the MS through the R6/R4 interface and the R1 interface, and a DSC Response (DSC Response). Further carrying the Specific-Action parameter, the The specific-Action parameter is used to indicate that the PCRF reports the related event to the AF after the resource modification is completed, and in step 609, the CCA delivered by the PCRF further carries the same Specific-Action parameter, and the SFA will carry the modification report through the PCEF and The PCRF is reported to the AF.

 Step 614: The AF and the MS continue application layer interaction through application layer session signaling, and respond to the service modification.

 FIG. 7 is a flowchart of the service modification initiated by the network side in the embodiment of the present invention. As shown in FIG. 7 , after the WiMAX network is merged with the PCC architecture, the specific processing procedure of the service modification initiated by the network side includes the following steps:

 Step 701: The MS interacts with the AF through application layer session signaling to request service modification. Step 702: The AF determines the modified service information, and sends an AAR to the PCRF, where the AAR carries related service information such as a user identifier, an application layer charging identifier, and a media description information, where the media description information includes a classifier and a bandwidth requirement. Service QoS parameters such as media type. The AAR may further carry a Specific-Action parameter to indicate whether the PCRF requests complete service information from the AF in the resource reservation process, and/or indicates whether the AF is notified after the subsequent resource process is completed.

 Step 703: After receiving the AAR, the PCRF stores the service information.

 Step 704: The PCRF makes a policy decision according to the received user subscription information and the modified QoS service parameter, generates a PCC rule, that is, modifies the PCC rule, and stores the modified PCC rule and the authorized QoS. Here, generating a PCC rule may refer to an alternative to the original PCC rule, that is, the PCRF replaces the corresponding original content with the modified PCC rule content instead of generating a complete new PCC rule.

 Before the PCRF generates the PCC rule, if the PCRF can generate the PCC rule according to the obtained user subscription information, the PCRF directly generates a PCC rule according to the obtained user subscription information and the modified QoS service parameter, if the PCRF cannot sign the contract according to the obtained user. The information generates a PCC rule, and the PCRF can obtain the user subscription information through the SPR.

The PCRF may select a bearer identifier corresponding to the bearer to be operated, and associate the PCC rule with the bearer. Step 705: The PCRF sends an RAR to the PCEF, where the RAR carries the modified PCC rule and the authorized QoS. In the case of the PCRF control bearer, the PCRF may also send the bearer identifier to the PCEF in the Charging-rule-install AVP in the RAR message.

 Step 706: After receiving the RAR, the PCEF converts the RAR from the Gx interface message to the R3 interface message, and sends a resource modification request message to the PCC policy enforcement entity, where the resource modification request message carries the modified PCC rule information and the authorized QoS. The following steps are described here by taking the SFA in the PCC Policy Enforcement Entity as an example.

 Further, if the PCRF does not select the corresponding bearer identifier in step 704 and associates it with the PCC rule, the PCEF may select the bearer identifier corresponding to the bearer to be operated, and return the bearer identifier to the PCRF in a subsequent step. Therefore, the PCRF can implement the association between the PCC rule and the bearer in the above manner.

 Step 707: After receiving the resource modification request message, the SFA performs QoS policy control according to the received PCC rule information and the authorized QoS.

 Step 708: The SFA initiates an IP-CAN bearer modification of the service session.

 Step 709: The SFA sends a resource modification response message to the PCEF, where the resource modification response message carries the bearer modification information.

 Step 710: After receiving the resource modification response message, the PCEF converts the resource modification response message from the R3 interface message to the Gx interface message, and sends an RAA to the PCRF, where the RAA carries the bearer modification information. The RAA may further carry a rule modification report for identifying the PCC rules that have been processed.

 Step 711: After receiving the RAA, the PCRF sends an AAA to the AF. If the PCRF has obtained the access network charging identifier at this time, and has not been provided to the AF before, the AAA carries the access network charging identifier. If the PCRF obtains the bearer identity selected by the PCEF in step 706 from the RAA, the PCRF associates the PCC rule with the bearer identity.

Step 712: The AF and the MS continue application layer interaction through application layer session signaling, and respond to service modification. If the QoS mapping is not done in the PCRF, if the QoS mapping is done in the PCEF or in the ASN domain, the PCC rule also needs to include the complete IP layer QoS parameter set. The IP layer QoS parameter set includes service priority, or maximum delay, or jitter tolerance, or maximum constant traffic rate, or minimum reserved traffic rate, or maximum traffic burst rate, or back-to-back, or maximum packet loss rate, or above. Any combination.

 The service modification initiated by the network side may involve modifying the gating state of the service flow, enabling or disabling the specific service flow. When it is necessary to modify the gating, enable or disable the service flow, the AF sends a Gate message in the AAR message sent to the PCRF, requesting to open or close the corresponding service flow bearer. After receiving the AAR message carrying the gating information, the PCRF sends a RAR message carrying the gating information to the PCEF, and the PCEF forwards the received gating information to the PCC policy enforcement entity, instructing to enable or disable the corresponding service flow bearer. After the network entity in the access network performs the gating, the PCEF returns a response message to the PCRF, and the PCRF returns an AAA message response gating request to the AF.

 The process of performing the gating is as follows. The gating execution entity classifies the received data packet into a specific service flow, and then according to the gating state of the service flow, if the status is enable, the normal transmission is performed. Packet; if the status is disable, the packet is discarded.

 Gating can be performed by the ASN-GW or BS. If the gate is controlled by the ASN-GW, the execution of the gating is: after receiving the gating information sent by the PCEF, the ASN-GW performs gating according to the gating information, that is, turns on or off the corresponding service flow bearer, and then A response message is returned to the PCEF. If the gating is performed by the BS, the execution of the gating is: after the PCEF sends the gating information to the ASN-GW, the ASN-GW must transmit the gating information to the BS through the R6 interface message, and the BS according to the received gating information. The gating is performed, that is, the corresponding traffic flow bearer is turned on or off, and then the BS returns a response message to the ASN-GW, and the ASN-GW returns a response message to the PCEF.

 If the gate is performed by the BS, the R6 interface message needs to be extended to carry the gating information.

The MS may also participate in the gated execution, and the gating information needs to be passed in the air interface DSA/DSC message. In each of the processes described above, the PCEF may be connected to an entity in the PCC policy enforcement entity. For example, if the SFA receives the PCC rule information, the SFA may send the service data flow detection information in the PCC rule to the anchor DPF, and then the anchor DPF classifies the data flow according to the service data flow detection information in the received PCC rule. The charging policy information in the PCC rule may also be sent to the charging proxy, and the charging proxy performs flow-based charging control according to the charging policy information in the received PCC rule; and/or sends the PCC rule information to the HA. . Further, the PCC rule may be sent to the policy charging execution function entity in the HA, and the policy charging execution function entity in the HA performs QoS policy, charging, and data flow detection. The PCEF may also be respectively connected to a plurality of functional entities in the PCC policy enforcement entity. For example, if connected to the anchor DPF, the service data flow detection information in the PCC rule is directly sent to the anchor DPF, and the anchor DPF is received according to the received The service data flow detection information in the PCC rule classifies the data flow; if connected to the charging proxy, sends the charging policy information in the PCC rule to the charging proxy, and the charging proxy charges according to the received PCC rule. The policy information performs flow-based charging control; if connected to the HA, sends the PCC rule information to the policy charging execution function entity in the HA, and the policy charging execution function entity in the HA executes the QoS policy according to the received PCC rule information. , billing and data flow detection.

 The PCC rules include the PCC rule identifier, the service identifier, the application layer charging identifier, the rate, the charging policy information, and the PCC rule priority information.

 FIG. 8 is a flowchart of the service deletion process initiated by the user side in the embodiment of the present invention. As shown in FIG. 8 , after the WiMAX network is merged with the PCC architecture, the specific processing process of the service deletion initiated by the user side includes the following steps:

 Step 801: The MS interacts with the AF through application layer session signaling to request service deletion. Step 802: The MS initiates an IP-CAN bearer deletion request, such as a Dynamic Service Deletion (DSD) request (DSD Request) and a resource release request message sent to the SFA through the R1 interface and the R6/R4 interface.

 Step 803: The SFA sends a resource release request message to the PCEF, where the resource release request message carries a bearer identifier and a bearer deletion indication, indicating that the IP-CAN bearer is deleted.

Step 804: After receiving the resource release request message, the PCEF sends the resource release request message by R3. The interface message is converted into a Gx interface message, and the CCR is sent to the PCRF, and the CCR message can carry the bearer identifier.

 The bearer is separated from the service in the PCC architecture. Therefore, the CCF message must be sent to the PCR session to delete the PCC rule. The method is as follows: The CCR message carries the bearer deletion indication and the rule report to indicate the request to delete the PCC rule; or A new display identifier is added to the CCR message to indicate that a specific PCC rule needs to be deleted, for example, carrying a charging-rule-remove AVP with a PCC rule identifier or name; or an event-trigger AVP defined in an existing protocol. The content of the bearer deletion is added, so that the CCR message carries the event-trigger and the rule report to indicate the request to delete the PCC rule; or, the bearer is inseparable from the service in the WiMAX network, and the PCC rule for the bearer operation and the rule-based service is specified. The operation is corresponding. The CCR message carries a bearer deletion indication to indicate that the request deletes all corresponding PCC rules on the bearer.

 Step 805 to step 807: After receiving the CCR, the PCRF identifies the PCC rule corresponding to the IP-CAN bearer requested to be deleted, and then deletes the corresponding PCC rule, and notifies the AF to terminate the AF session corresponding to the IP-CAN bearer, and the AF deletes the AF session.

 Step 808: The PCRF sends a CCA to the PCEF, where the CCA carries PCC rule information, indicating that the corresponding PCC rule is deleted.

 Step 809: After receiving the CCA, the PCEF converts the CCA from the Gx interface message to the R3 interface message, and sends a resource release response message to the SFA, where the resource release response message carries the PCC rule information.

 Step 810: After receiving the resource release response message, the SFA deletes the QoS control information according to the PCC rule information.

 Step 811: The SFA returns an IP-CAN bearer deletion response to the MS, such as a resource release response message sent by the R6/R4 interface and the R1 interface, and a DSD response of the MS (DSD Response).

 Step 812: The AF and the MS continue application layer interaction through application layer session signaling, and respond to service deletion.

FIG. 9 is a flowchart of a service deletion initiated by a network side according to an embodiment of the present invention, as shown in FIG. After the network is merged with the PCC architecture, the specific processing of the service deletion initiated by the network side includes the following steps:

 Step 901: The MS interacts with the AF through application layer session signaling to request service deletion. Step 902: The AF sends a Session Termination Request (STR) to the PCRF, where the STR carries an Rx session identifier corresponding to the AF session to be terminated, indicating that the AF session is terminated, and requests to delete the PCC rule.

 Step 903 to step 904: After receiving the STR, the PCRF identifies the IP-CAN bearer and the PCC rule corresponding to the AF session requested to be deleted, and then deletes the corresponding PCC rule.

 Step 905: The PCRF sends a RAR to the PCEF, where the RAR carries PCC rule information, indicating that the corresponding PCC rule is deleted.

 Step 906: After receiving the RAR, the PCEF converts the RAR from the Gx interface message to the R3 interface message, and sends a resource release request message to the SFA, where the resource release request message carries the PCC rule information.

 Step 907: After receiving the resource release request message, the SFA deletes the QoS control information according to the PCC rule information.

 Step 908: The SFA initiates an IP-CAN bearer deletion.

 Step 909: The SFA sends a resource release response message to the PCEF, indicating that the bearer deletion is completed. Step 910: After receiving the resource release response message, the PCEF converts the resource release response message from the R3 interface message to the Gx interface message, and sends the RRA to the PCRF.

 Step 911: After receiving the RRA, the PCRF sends a Session Termination Answer (STA) to the AF.

 Step 912: The AF and the MS continue application layer interaction through application layer session signaling, and respond to service deletion.

In the deletion process described above, the PCEF may be connected to an entity in the PCC policy enforcement entity, for example, the SFA, and after the SFA deletes the PCC rule, the anchor DPF may be notified to delete the information related to the PCC rule, and then the anchor DPF is stopped. The data stream is classified; the billing agent can also be notified to delete The information related to the PCC rule, the charging agent stops performing flow-based charging control; and further, the policy charging execution function entity in the HA may be notified to delete the information related to the PCC rule, and the policy charging execution function entity in the HA Stop performing policy accounting and data flow detection. The PCEF may also be respectively connected to multiple functional entities in the PCC policy enforcement entity. For example, if it is connected to the anchor DPF, the anchor DPF is directly notified to delete the information related to the PCC rule, and the anchor DPF stops classifying the data stream; If it is connected to the charging proxy, the charging proxy is directly notified to delete the information related to the PCC rule, and the charging proxy stops performing flow-based charging control; if connected to the HA, directly notifying the HA to delete the information related to the PCC rule, The policy charging execution function entity in the HA stops performing policy charging and data flow detection.

 The above-mentioned PCEF can be located in the same physical entity as the SFA, so that the interaction between the PCEF and the SFA can be completed through the internal interface; the PCEF can also be located in a different physical entity from the SFA, so that the PCEF and the SFA can directly interface through the interface. Connected, there is no interface between them, but through other functional entities to complete the interaction, such as anchor DPF, billing agent, HA and so on. The PCEF can also be in the same physical entity as the HA, so that the interaction between the PCEF and the policy charging execution function in the HA can be completed through the internal interface.

 The authorization QoS generated by the above policy decision may be included in the PCC rule, such that the PCC rule is generated in the PCRF policy decision, the PCRF stores the PCC rule, and the PCC rule is provided to the PCC policy enforcement entity.

 In order to support MIP version 6 (MIPv6) applications, the decision of the classifier can be implemented in two ways. One implementation method is to anchor the DPF to the PCRF without issuing any modification to the classifier, and directly apply, thus requiring PCRF. The complete information is sent; another implementation is that the SFA or the anchor DPF modifies the classifier delivered by the PCRF.

When the DPF directly applies the classifier delivered by the PCRF, the PCRF needs to care about the MIP-related information of the MS. That is, the PCRF obtains the MIP-related information of the MS through the relevant network element, such as whether the MS supports the MIPv6, MS care-of address (Care of Address) , Co A ) and the routing optimization core network (Core Network, CN) list of the MS. When creating a new business, PCRF retrieves the corresponding MS CoA, Home Address (HoA) and other information, also need to traverse its route optimization CN list of the MS to determine whether the corresponding new service has route optimization. The PCRF then generates a complete classifier according to the obtained MIP related information of the MS, and is included in the PCC rule. The classifier includes at least an IP header, a MIP header, and deep information. At this time, the anchor DPF needs to have deep decoding capability. That is, when the anchor DPF discovers that an IP packet is an MIPv6 data packet, it needs to be able to perform service data flow detection on the MIPv6 data packet in the payload, so that the SFA and the meter can be made. The fee agent performs the corresponding QoS policy control and the execution of the charging policy. When the MS moves to cause a CoA change or route optimization occurs, the MS needs to initiate a service data flow modification process to the SFA to modify the corresponding classifier information in the anchor DPF, and the SFA sends a policy modification request to the PCRF, where the policy modification request includes The CoA change identifier, the current CoA, the route optimization identifier, and the route optimization peer node identifier. After receiving the policy modification request, the PCRF modifies the classifier information and then delivers the information to the anchor DPF.

 When the PCRF does not need to care about the MIP related information of the MS, the classifier that is sent by the PCRF needs to be modified by the SFA or the anchor DPF. The PCRF does not need to care about the MIP-related information of the MS. That is, the PCRF does not need to obtain the MIP-related information of the MS through the relevant network element, directly uses the HoA obtained when establishing the IP-CAN session as the address of the MS, or uses the specific wildcard as the address of the MS. The SFA/anchor DPF needs to maintain the MS Home Agent (HA) address, the MS's CoA, and the MS's route optimization CN list. After the SFA/anchor DPF obtains the classifier delivered by the PCRF, the classifier information is modified according to the MIP related information of the MS maintained by it. If the MS supports MIPv6, the anchor DPF can extend the classification rule for the MIP header according to the CoA and HA addresses. If a new service is established with the existing route optimization node or the route optimization is performed with the peer of the existing service, The SFA/anchor DPF can modify the corresponding classifier according to the CoA. The anchor DPF also needs to have deep decoding capability. That is, when the anchor DPF discovers that an IP packet is an MIPv6 packet, it needs to be able to perform service data flow detection on the MIPv6 packet in its payload, so that the SFA and the charging proxy can be enabled. Do the corresponding QoS policy control and execution of the charging policy.

In the PCC architecture, the bearer identifier in the Gx session may correspond to a one-way or two-way service flow, and the service flow detection template in the PCC rule is composed of one or more one-way service flow detection filters; There is only one-way service flow in WiMAX. Therefore, the PCEF or PCC policy enforcement entity is required to split the PCC rules. The split PCC rules only include the one-way service flow detection filter, which can be applied to the corresponding WiMAX service flow respectively. The PCEF needs to maintain the original PCC. The mapping relationship between the rule and the split PCC rule is sent, and a rule binding processing instruction is sent at the same time as the PCC rule is sent. The processing result of all PCC rules obtained after splitting the same PCC rule is consistent, that is, all splits. If the post-rule is processed successfully, the PCC rule is processed successfully. If at least one post-split rule processing fails, the PCC rule processing fails, and the rule processing includes establishing, modifying, and deleting; or, in the PCC decision, if If the IP CAN type is detected as WiMAX, the service flow detection template in the PCC rule only includes the same-direction service flow detection filter, which can be applied to the corresponding WiMAX service flow. In the foregoing scenarios, the PCEF or the PCC policy enforcement entity may need to maintain a mapping relationship between the bearer identifier in the Gx session and the identifier contained in the access network information. The mapping relationship may be a one-to-one or one-to-many relationship.

 When an AF session corresponds to multiple service flows, one service will have multiple PCC rules. In this case, the processing results of all PCC rules generated by one PCC decision of a service may be consistent or successful. , or both fail. The PCC decision includes the generation, modification, and deletion of PCC rules. Therefore, the binding of the rule processing is required by the PCRF, and the rule binding processing indication is sent at the same time as the rule is delivered. Further, the AF can also control the binding of the rule processing, and the policy binding processing request indication is sent at the same time that the service information is sent, and the PCRF performs the rule binding according to the requirements of the AF, and then issues the rule binding processing indication at the same time that the rule is delivered. . After receiving the indication, the lower layer network reports success to the PCRF if all the PCC rules of the service decision are successfully processed; if at least one PCC rule fails to process, the failure is reported to the PCRF. Further, the PCRF can also report the PCC rule processing result of the service to the AF.

The system for implementing the business process processing includes: a PCC policy execution entity in the PCRF, the PCEF, and the WiMAX network, as shown in FIG. 10, wherein the PCRF is configured to generate a PCC rule according to the policy decision after receiving the PCC rule request, and execute the PCC policy to the PCC policy. The entity provides PCC rules and authorized QoS; the PCEF is used for protocol conversion of messages exchanged between the PCRF and the PCC policy enforcement entity; PCC The policy enforcement entity is configured to perform QoS policy control and charging of the service data flow based on the received PCC rules and authorized QoS. The PCC rule request may be from a PCC policy enforcement entity, or an AAA server further included in the system, or an AF further included in the system.

 The above system may further comprise an AF for providing WiMAX content to the PCRF; the PCRF for providing the PCEF with PCC rules containing the WiMAX content through an extended Gx interface with the PCEF.

 In addition, the PCRF is configured to delete the corresponding PCC rule after receiving the PCC rule deletion indication, and notify the PCC policy enforcement entity to delete the corresponding PCC rule by using the PCEF; the PCC policy enforcement entity is configured to delete the corresponding PCC rule according to the received notification. The PCC rule deletion indication may come from a PCC policy enforcement entity, or an AF further included in the system.

 The PCEF described above can be further used as an implementation of IP layer QoS policy control while acting as a protocol converter between the PCRF and the PCC policy enforcement entity in the WiMAX network.

 In various embodiments provided by the present invention, after receiving the PCC rule request, the PCRF generates a PCC rule according to the policy decision, and then provides a PCC rule and an authorized QoS to the PCC policy enforcement entity in the WiMAX network, and the PCC policy enforcement entity according to the received PCC rules and authorized QoS perform QoS policy control and accounting, which involves various related processes in the process of service processing, including preset flow establishment process, service establishment process, service modification process, and service deletion process in various situations. After the integration of WiMAX network and PCC architecture, the related processing in the business process involving WiMAX network is very beneficial to the promotion and application of WiMAX network. 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 processing a business process, the method comprising:  After receiving the policy and charging control PCC rule request, the policy control and charging rule function entity PCRF generates a PCC rule according to the policy decision, and provides PCC rules and authorizations to the PCC policy enforcement entity in the global interoperable WiMAX network of the microwave access. Quality of Service QoS;  The PCC policy enforcement entity performs QoS policy control and charging based on the received PCC rules and authorized QoS.  2. The method of claim 1 wherein  The PCRF receives the PCC rule request, and further includes: the terminal initial network access authentication is completed, and the authentication, authorization, and accounting AAA server sends an access permission message to the service flow authorization entity SFA in the PCC policy enforcement entity, and the PCC policy execution entity Sending a PCC rule request to the PCRF through the policy and charging execution function entity PCEF;  The PCRF receives the PCC rule request, and then further includes: the PCRF obtaining the QoS description information by using the AAA server;  The generating the PCC rule according to the policy decision is: making a policy decision according to the QoS description information, and generating a PCC rule and a 4 authorized QoS.  3. The method of claim 1 wherein:  The PCRF receives the PCC rule request, and the method further includes: the terminal initial network access authentication is completed, and the AAA server sends an access permission message carrying the QoS description information to the SFA in the PCC policy enforcement entity, and the PCC policy enforcement entity sends the PCRF to the PCRF. Sending a PCC rule request carrying the QoS description information;  The generating the PCC rule according to the policy decision is: making a policy decision according to the QoS description information, and generating a PCC rule and a 4 authorized QoS. The method according to claim 2 or 3, wherein the PCC rule request sent by the PCEF to the PCRF is a credit control request CCR, and before the PCEF sends the CCR to the PCRF Further comprising: the PCEF sets the parameter CCR type carried in the CCR as an initial request.  5. The method of claim 1 wherein:  The PCRF receives the PCC rule request, and the method further includes: the initial network access authentication of the terminal is completed, and the AAA server sends the QoS description information to the PCRF;  The generating a PCC rule according to the policy decision is: performing a policy decision according to the QoS description information, generating a PCC rule and a 4 authorized QoS;  The providing the PCC rule and the authorized QoS to the PCC policy enforcement entity is: providing the PCC rule and the authorized QoS to the AAA server, and the AAA server sends an access permission message carrying the PCC rule and the authorized QoS to the SFA.  6. The method of claim 1 wherein:  The PCRF receives the PCC rule request, and further includes: the terminal initial network access authentication is completed, the AAA server sends an access permission message to the SFA in the PCC policy enforcement entity, and the PCC policy enforcement entity sends a PCC rule request to the PCRF through the PCEF, AAA The server delivers QoS description information to the PCRF.  The generating the PCC rule according to the policy decision is: making a policy decision according to the QoS description information, and generating a PCC rule and a 4 authorized QoS.  7. A method according to any of claims 2, 3, 5 or 6, characterized in that  The method further includes: the MS obtaining an IP address.  8. A method according to any of claims 2, 3, 5 or 6, characterized in that  The method further includes: the SFA initiating establishment of the preset flow bearer.  9. The method of claim 1 wherein:  The PCRF receives the PCC rule request, and the method further includes: the terminal interacts with the application function entity AF through the application layer session signaling, requests the service establishment, the AF provides the service QoS parameter to the PCRF, and the terminal initiates the bearer establishment request for the AF session, the PCC The policy enforcement entity sends a PCC rule request to the PCRF through the PCEF; The generating the PCC rule according to the policy decision is: according to the obtained user subscription information and service QoS Parameters make policy decisions, generate PCC rules and authorize QoS.  The method according to claim 9, wherein the PCRF receives the PCC rule request, and further comprises: associating the AF session to the corresponding internet protocol according to the user IP address and/or the user identifier in the service information. - Connect the access network IP-CAN session;  After the receiving the PCC rule request, the method further includes: associating the PCC rule request with the corresponding AF session according to the classifier in the access network information.  The method according to claim 9, wherein the AF further provides a specific behavior parameter to the PCRF, instructing the PCRF to request complete service information from the AF in the resource reservation process; and generating the PCC rule according to the policy decision, before The method further includes: the PCRF acquires service information by using the AF.  12. The method of claim 1 wherein:  The PCRF receives the PCC rule request, and the method further includes: the terminal interacts with the application function entity AF through the application layer session signaling to request the service establishment, and the AF provides the user identifier and the service information including the service QoS parameter to the PCRF;  The generating the PCC rule according to the policy decision is: performing a policy decision according to the obtained user subscription information and the service QoS parameter, and generating a PCC rule and an authorized QoS.  13. The method of claim 12, wherein  The AF provides service information to the PCRF, and then further includes: the PCRF associates the AF session to the corresponding IP-CAN session according to the received service information and the access network information acquired by the policy and charging execution function entity PCEF, and indexes To the corresponding PCEF.  14. The method of claim 1 or 9, wherein  The PCC rule request does not carry a rule report; or  The PCC rule request carries a rule request indication parameter; or  The PCC rule request carries a bearer identifier, a bearer setup indication, or a classifier.  15. The method of claim 1 wherein: The PCRF receives the PCC rule request, and the method further includes: the terminal interacts with the application function entity AF through the application layer session signaling, requests the service modification, and the AF provides the service information to the PCRF. The terminal initiates a bearer modification request, and the PCC policy enforcement entity sends a PCC rule request carrying the modified content to the PCRF through the PCEF;  The generating the PCC rule according to the policy decision is: performing policy decision according to the modified content of the bearer, and generating a PCC rule and an authorized QoS.  16. The method of claim 1 wherein:  The PCRF receives the PCC rule request, and the method further includes: the terminal interacts with the application function entity AF through the application layer session signaling to request the service modification, and the AF provides the PCRF with the service information including the service QoS parameter;  The generating the PCC rule according to the policy decision is: performing a policy decision according to the obtained user subscription information and the service QoS parameter, and generating a PCC rule and an authorized QoS.  17. A method according to claim 1 or 15, characterized in that  The PCC rule request carries an event trigger and a rule report; or  The PCC rule request carries a rule modification indication parameter; or  The PCC rule request carries a rule identifier or a rule name or bearer information.  18. A method according to claim 15 or 16, characterized in that  When the service modification involves QoS modification, the PCRF receives the PCC rule request, and then further includes: if the resource corresponding to the QoS modification is consistent with the previous negotiation, the PCRF directly performs the authorization operation; if the QoS is modified, the corresponding resource and the previous Inconsistent negotiation, the PCRF obtains authorization related information through AF, and performs authorization operations.  19. A method according to claim 12 or 16, wherein  The providing the PCC rule and the authorized QoS to the PCC policy enforcement entity is: providing the PCC rule and the authorized QoS to the PCC policy enforcement entity through the PCEF.  20. A method according to claim 9, 12, 13 or 16, characterized in that  The generating the PCC rule according to the policy decision, the method further includes: the PCRF acquiring the user subscription information by using the subscription information storage function entity SPR. 21. The method of claim 2, 3, 6, 9, 10, 11 or 15 wherein The policy enforcement entity sends a PCC rule request for the R3 interface to the PCEF, and the PCEF converts the PCC rule request from the R3 interface message to the Gx interface message, and then sends a PCC rule request of the Gx interface to the PCRF.  22. A method according to any of claims 2, 3, 6, 9 to 11, 12 to 15 or 16, characterized in that  The providing the PCC rule and the authorized QoS to the PCC policy enforcement entity is: providing the PCC rule and the authorized QoS to the PCC policy enforcement entity through the PCEF.  23. The method of claim 22, wherein  The PCEF provides the PCC rule and the authorized QoS to the PCC policy enforcement entity by the PCEF, so that: the PCRF sends a Gx interface message carrying the PCC rule and the authorized QoS to the PCEF, and the PCEF converts the Gx interface message into an R3 interface message, and then sends the PC3 policy to the PCC policy. The executing entity sends an R3 interface message carrying the PCC rule and the authorized QoS.  24. The method according to claim 22, wherein the method further comprises: the AF providing the WiMAX content to the PCRF, and the PCRF providing the PCEF with the PCC rule containing the WiMAX content through the extended Gx interface with the PCEF.  25. A method according to any of claims 1 to 3, 6, 9 to 11, 12 to 15 or 16, characterized in that  When the QoS mapping is not completed in the PCRF, the PCC rule received by the PCC policy enforcement entity includes a complete IP layer QoS parameter set.  26. A method according to any of claims 1 to 3, 6, 9 to 11, 12 to 15 or 16, characterized in that  The PCC policy enforcement entity includes one of the following entities or any combination thereof:  SFA, anchor data path functional entity DPF, or billing agent;  The SFA performs QoS policy control according to the received PCC rule and the authorized QoS; The anchor DPF performs the data stream according to the service data flow detection information in the received PCC rule. Classification  The charging agent performs flow-based charging control according to the charging policy information in the received PCC rule.  27. The method of claim 26, wherein 28. A method according to any of claims 1 to 3, 6, 9 to 11, 12 to 15 or 16, characterized in that  The generating the PCC rule includes: the PCRF acquiring the mobile IP MIP related information of the terminal, and generating a complete classifier according to the MIP related information, where the PCC rule included in the PCC policy execution entity includes the classifier, the PCC policy The QoS policy control and charging performed by the executing entity according to the received PCC rule and the authorized QoS to perform the service data flow includes: directly applying the classifier to the anchor DPF in the PCC policy enforcement entity; or  The PCC policy enforcement entity performs QoS policy control and charging of the service data flow according to the received PCC rule and the authorized QoS. The SFA or the anchor DPF in the PCC policy enforcement entity performs the PCC rule according to the MIP related information of the terminal. The classifier included in the modification is modified to anchor the DPF to apply the classifier.  29. The method of claim 28, wherein  The anchoring DPF directly applies the classifier, and the method further includes: the PCC policy enforcement entity requests the PCRF to modify the classifier information, and the PCRF sends the modified classifier to the anchor DPF.  30. The method of any of claims 1 to 3, 6, 9 to 11, 12 to 15 or 16, wherein the method further comprises: the PCEF performing IP layer QoS policy control.  31. The method of any of claims 1 to 3, 5 to 6, 9 to 11, 12 to 15 or 16, wherein  The PCC rule carries the gating information, and the gating execution entity performs the gating operation on the service flow according to the gating information. 32. The method of claim 31, wherein The gated execution entity is at least one of an ASN-GW, a BS, and an MS.  33. The method of claim 32, wherein  After receiving the gating information, the ASN-GW performs gating according to the gating information; and/or, the BS acquires gating information from the ASN-GW through the R6 interface, according to the received gate. Controlling information to perform gating; and/or,  The MS acquires gating information from the BS air interface DSA/DSC message, and performs gating according to the received gating information.  The method according to any one of claims 1, 2, 3, 6, 9, 13, or 15, wherein the PCC policy enforcement entity splits the PCC rule into only one-way service flow detection The PCC rules of the filter, and maintain the mapping relationship of the PCC rules before and after the split; and / or,  The PCC policy enforcement entity maintains a mapping relationship between the bearer identifier in the Gx session and the bearer identifier in the bearer information.  35. The method of any of claims 2, 3, 6, 9, 13 or 15, wherein the method further comprises  The PCEF splits the PCC rules into PCC rules that only contain one-way service flow detection filters, and maintains the mapping relationship of PCC rules before and after splitting; and/or,  The PCEF maintains a mapping relationship between the bearer identifier in the Gx session and the bearer identifier in the bearer information.  36. The method of claim 1 wherein:  The PCC rule includes: a service flow detection template including only the same service flow detection filter. 37. The method of claim 1 wherein:  The PCRF sends a rule binding processing indication.  38. A method for processing a business process, the method comprising:  After receiving the PCC rule deletion request, the PCRF deletes the PCC rule and notifies the PCC policy enforcement entity in the WiMAX network to delete the PCC rule. The PCC policy enforcement entity deletes the PCC rule according to the received notification. 39. The method of claim 38, wherein  The PCRF receives the PCC rule deletion request, and the method further includes: the terminal interacts with the application function entity AF through the application layer session signaling to request the service deletion, and the PCC policy execution entity sends the PCC rule deletion request to the PCRF through the PCEF; or  The PCRF receives the PCC rule deletion request, and the method further includes: the terminal interacts with the application function entity AF through the application layer session signaling, requests the service to be deleted, and the AF sends the PCC rule deletion request to the PCRF.  40. The method of claim 38, wherein  The PCC rule deletion request carries a bearer deletion indication and a rule report; or  The PCC rule deletion request carries a rule deletion indication parameter; or  The PCC rule deletion request carries a bearer deletion indication.  41. A business process processing system, characterized in that  The system includes: a PCC policy enforcement entity in a PCRF, a PCEF, and a WiMAX network, where the PCRF is configured to generate a PCC rule according to a policy decision after receiving a PCC rule request, and provide a PCC rule and authorization to the PCC policy enforcement entity. QoS;  The PCEF is configured to perform distribution/and or protocol conversion on a message exchanged between the PCRF and the PCC policy enforcement entity;  The PCC policy enforcement entity is configured to perform QoS policy control and charging based on received PCC rules and authorized QoS.  42. The system of claim 41, wherein:  The PCRF is further configured to associate the AF session to the corresponding IP-CAN session according to the received service information and the access network information acquired by the policy and charging execution function entity PCEF, and index the corresponding PCEF; or  The PCRF is further configured to acquire MIP related information of the terminal, and generate information according to the MIP related information. 43. A system according to claim 41 or claim 42 wherein: The PCEF is further configured to perform IP layer QoS policy control; or  The PCC rule request sent by the PCEF to the PCRF is a credit control request CCR, and the PCEF is further configured to set a parameter CCR type carried in the CCR as an initial request.  44. The system of claim 41 or 42, wherein the system further comprises: AF,  The AF is used to provide WiMAX content to the PCRF, and the PCRF is configured to provide a PCC rule including the WiMAX content to the PCEF through an extended Gx interface with the PCEF; or the AF is used to provide a specific behavior to the PCRF. The parameter indicates that the PCRF requests the complete service information from the AF in the resource reservation process, and provides the service information to the AF, and the PCRF is further configured to obtain the service information by using the AF according to the specific behavior parameter.  45. A system according to claim 41 or claim 42 wherein:  The PCC policy enforcement entity includes one of the following entities or any combination thereof:  SFA, anchor data path functional entity DPF, or billing agent;  The SFA is configured to perform QoS policy control according to the received PCC rule and the authorized QoS; the anchor DPF is configured to classify the data stream according to the service data flow detection information in the received PCC rule;  The charging proxy is configured to perform flow-based charging control according to the charging policy information in the received PCC rule.  46. The system of claim 45, wherein: 47. A business process processing system, characterized in that  The system includes: a PCC policy enforcement entity in the PCRF, the PCEF, and the WiMAX network, where the PCRF is configured to delete the PCC rule after receiving the PCC rule deletion request, and notify the PCC policy enforcement entity to delete the PCC rule; The PCEF is configured to perform distribution and/or protocol conversion on a message exchanged between the PCRF and the PCC policy enforcement entity; The PCC policy enforcement entity is configured to delete the PCC rule according to the received notification.  48. A method for bearer association, characterized in that the method comprises:  The PCRF receives the bearer identifier sent by the PCEF, and associates the PCC rule with the bearer; or the PCRF generates a bearer identifier, and associates the PCC rule with the bearer; or  The PCRF sends a PCC rule to the PCEF, and the PCRF receives the bearer identifier sent by the PCEF, and associates the PCC rule with the bearer.  49. A system for bearing association, characterized in that  The system includes: PCRF and PCEF, wherein  The PCEF is configured to send a bearer identifier to the PCRF;  The PCRF is configured to receive a bearer identifier sent by the PCEF, and associate the PCC rule with a bearer; or  The PCRF is configured to generate a bearer identifier, and associate the PCC rule with the bearer; or the PCEF is configured to receive the PCC rule sent by the PCRF, and send the bearer identifier to the PCRF;  The PCRF is configured to receive a bearer identifier sent by the PCEF, and associate the PCC rule with a bearer.