WO2008061477A1

WO2008061477A1 - A system and charging control method of network fuse policy charging control structure

Info

Publication number: WO2008061477A1
Application number: PCT/CN2007/071097
Authority: WO
Inventors: Xianhui He; Liang Gu; Yong Xie; Jianjun Wu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-11-20
Filing date: 2007-11-20
Publication date: 2008-05-29

Abstract

A system and charging control method of network fuse policy charging control structure are disclosed, based on the QoS parameter, charging policy and user subscribing information granted by the service layer, the PCRF confirms PCC rule, and provides the PCC rule to the policy distribution function PDF. As the interface between the PCRF and PCC policy performing entity, the PDF performs the protocol transform and message distribution. Based on the PCC rule, the PCC policy performing entity performs Qos granting of the service data flow and the detecting and charging of the service flow. A practical solution is provided to fuse the fused wireless network communication system structure such as WiMAX network and PCC structure of the 3GPP/3GPP2 network, the PCC structure is used to realize the policy control and charging control of the service, the fusing problem between the function entity in the PCC structure and the policy charging control entity SFA, DPF, charging client/charging proxy, home agency HA and so on, which belong to the function entity of the fused wireless network (such as WiMAX network) is solved, the PCC structure is used to realize the process flow and fuse solution of the policy control and charging control of the service.

Description

System and charging control method for network convergence policy charging control architecture This application claims to be submitted to China on November 20, 2006, December 06, 2006, February 05, 2007 and May 21, 2007, respectively. The Patent Office and the application numbers are 200610149176.9, 200610162104.8, 200710000424.8, and 200710106617.1, and the invention names are all "the system and processing method of the network convergence policy charging control architecture, and the priority of the Chinese patent application, the entire contents of which are incorporated by reference. In the present application.

The invention relates to a network convergence technology, in particular to a network convergence policy (PCC) architecture system and a charging control method. Background technique

The architecture of the Worldwide Interoperability for Microwave Access (WiMAX) network is shown in Figure 1A. The WiMAX network mainly includes mobile terminals (MS) and access to the network. (Access Service Network, ASN) and the Connectivity Service Network (CSN). Among them, ASN mainly includes Base Station (BS) and Access Service Network Gateway (ASN-GW). The CSN mainly includes a prepaid server (PPS) and a logical entity such as an authentication, an authorization authorization accounting (AAA) server, and an AAA server. The MS and the ASN pass the R1 interface. Connected, 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, and the BS in the ASN and the ASN-GW pass through the R6. The interfaces are connected. The wireless side, ie the R1 side, is based on the Institute of Electrical and Electronics Engineers (IEE). E) Wireless metropolitan area network access technology of the 802.16 standard.

The latest Quality of Service (QoS) framework of the WiMAX Network Work Group (NGG) standard 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 management entity ( Service Flow Manager (SFM) is used to establish a user service flow and allocate radio resources for the established service flow. The functional entity exists in the ASN; Service Flow Authorization (SFA) is used for the service flow. Authorization, the functional entity exists in the ASN; the Policy Function (PF) is used to provide a policy for the user's service flow. The functional entity is provided by a Network Service Provider (NSP). There will be PF ( Visited PF, V-PF) and Home PF (H-PF); Application Function (AF) is a functional entity that provides application services, and the user's MS directly passes the application layer protocol. When the connection accesses the AF, the AF will notify the PF to actively create a service flow for the user, and the functional entity is provided by the NSP.

FIG. 1C is a schematic diagram of a standard WiMAX NWG standard charging architecture. As shown in FIG. 1C, the MS is equivalent to a user in charging, and an accounting client is used to collect all charging information and provide it to the AAA server. The AAA proxy (AAAProxy) is an optional intermediate device. After processing the received accounting packet, it generates a new accounting packet and forwards it to the real AAA server, such as the home AAA server (Home AAA). Server) or visit AAA server (Visited AAA Server), etc.; Home AAA server is the home AAA server, that is, the AAA server that the user initially registers or the AAA server of the user's home. The home AAA server stores the user's subscription information, including billing. For the policy, the user's billing process is mainly performed in the home AAA server. The visited AAA server is the AAA server of the user's visited place, which is used to implement billing information recording, transparent transmission and forwarding when the user roams.

FIG. 1D is a schematic diagram of an existing charging reference model. As shown in FIG. 1D, a user logs in, accesses, and logs out of the network through a client terminal according to network requirements, and the charging point automatically initiates charging according to the network access situation of the user. The packet is generated by the accounting server according to the received accounting packet. Billing is transparent to the user, starting from the user logging in to the network and ending automatically when the user exits the network.

The Policy Control and Charging (PCC) framework is defined by the 3rd Generation Partnership Project (3GPP) and 3GPP2 for Internet Protocol (IP) connection access. The network policy control and charging control function framework, PCC is used to complete resource admission control, mainly implements certain service quality control and charging policy control for the characteristics of the mobile access network. The main functions provided include: User-based customized information Implement policy control and charge control based on service data flow. The PCC is located between the service control layer and the access or bearer layer, and blocks the specific technology and topology information of the access or bearer layer to the service control layer. The PCC receives the service-related QoS authorization parameters from the service control layer, and then The admission control strategy, the topology information of the network, etc. are combined, and the service QoS parameters are converted into IP QoS parameters, and then provided to the relevant access or bearer layer nodes and service gateway nodes, according to the received information and its own The function implements the corresponding QoS control. Among them, the policy control mainly refers to Gating Control and QoS Control, and the charging control refers to Flow Based Charging (FBC).

Figure IE is a schematic diagram of the basic functional architecture of the existing 3GPP/3GPP2 standard. As shown in Figure 1E, AF is a functional entity for providing applications. These applications require dynamic policy control and accounting for the IP access network user plane. control. The Subscription Profile Repository (SPR) is used to store the subscription information of the user. The Policy Control and Charging Rule Function (PCRF) is used to perform control policy decision and policy decision based on flow accounting. 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. Policy 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 based on activated PCC rules. (PCC Rule) The service data flow template detects the server 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, and performs The 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 and reports the charging information according to the charging requirement of the PCC rule. Execution gating 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 of 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. The Offline Charging System (OFCS) is used for offline charging at the application layer. In the offline charging mode, the PCEF periodically reports the CDRs to the OFCS.

With the requirements of network evolution and convergence, a unified architecture is required to implement policy and charging control for the network. Therefore, the WiMAX network needs to be integrated with the PCC architecture of the 3GPP/3GPP2 network. Achieve unified policy control and billing control, but there is no such integration scheme at present, the content of the invention

Embodiments of the present invention provide a system and a processing method for a network convergence policy charging control architecture, which integrates a WiMAX network with a 3GPP/3GPP2 PCC architecture.

An embodiment of the present invention provides a system for a network convergence policy charging control architecture, including: a policy control and charging rule function entity PCRF, a policy distribution entity PDF, and a PCC policy execution entity, where

The PCRF is configured to perform user QoS authorization according to quality of service QoS parameters, charging policy information, and user subscription information authorized by the service layer, and determine a policy control and charging PCC rule, and provide the PCC rule to the PDF;

The PDF is used for protocol conversion and message distribution as an interface between the PCRF and the PCC policy enforcement entity; authorization, QoS policy, and charging.

An embodiment of the present invention further provides a system for a network convergence policy charging control architecture, including: a global interoperability network for microwave access, an access service network in a WiMAX ASN, and a connection service network.

CSN, Policy Control and Charging Rules Function Entity PCRF, Policy Distribution Entity PDF and PCC Policy Enforcement Entity, where

The embodiment of the present invention further provides a policy charging control method for a network convergence policy charging control architecture, including:

The policy distribution entity PDF acquires a PCC rule determined by the policy control and charging rule function entity PCRF according to the QoS parameter, the charging policy information, and the user subscription information authorized by the service layer; The PDF provides the PCC rule to a PCC policy enforcement entity;

QoS authorization and billing.

In the embodiment provided by the present invention, the PCRF determines the PCC rule according to the QoS parameters and the charging policy authorized by the service layer and the subscription information of the user, and the policy distribution entity PDF serves as an interface between the PCRF and the PCC policy enforcement entity for protocol conversion and message distribution. , the PCC policy enforcement entity is based on

The PCC rule performs QoS authorization and charging of the service data flow, and proposes a feasible solution for the convergence of the communication system architecture of the fused wireless network, such as the WiMAX network and the 3GPP/3GPP2 network PCC architecture, and implements the policy control of the service by using the PCC architecture. Charging control, and solves functional entities such as policy control entity SFA, data path function entity DPF, billing client/accounting agent, and/or HA of functional entities in the PCC architecture and converged wireless networks (such as WiMAX networks) The problem of convergence is that a converged wireless network (such as a WiMAX network) uses a PCC architecture to implement a process and a convergence scheme for policy control and charging control of services. DRAWINGS

Figure 1A is a schematic diagram of the structure of an existing WiMAX network;

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

FIG. 1C is a schematic diagram of a current WiMAX NWG standard charging architecture;

1D is a schematic diagram of an existing charging reference model;

1E is a schematic diagram of a basic functional architecture of a PCC of the existing 3GPP/3GPP2 standard;

2A is a schematic diagram of a WiMAX network and a PCC architecture in a first embodiment of the present invention; FIG. 2B is a schematic diagram of a WiMAX network and a PCC architecture in a second embodiment of the present invention; FIG. 2C is a flowchart of QoS authorization control according to Embodiment 3 of the present invention;

2D is a flowchart of QoS authorization control in Embodiment 4 of the present invention;

3A is a schematic diagram of a WiMAX network and a PCC architecture in a fifth embodiment of the present invention; FIG. 3B is a flowchart of QoS authorization control in Embodiment 6 of the present invention;

4A is a schematic diagram of a WiMAX network and a PCC architecture in a seventh embodiment of the present invention; FIG. 4B is a flowchart of QoS authorization control according to Embodiment 8 of the present invention;

4C is a flowchart of QoS authorization control in Embodiment 9 of the present invention. detailed description In the embodiment provided by the present invention, the PCRF determines the PCC rule according to the QoS parameter and the charging policy information authorized by the service layer and the user subscription information, and the Policy Distribution Function (PDF) is used as the PCRF and the PCC policy enforcement entity. The interface performs protocol conversion and message distribution, and the PCC policy enforcement entity performs QoS authorization execution and charging of the service data flow according to the PCC rules. The PCC rules include quality of service (QoS) policy control information, charging policy information, service flow detection information, and the like. The PDF can be implemented as a separate entity, also in PCRF, or ASN, or HA, and can also be implemented within PCRF and ASN, or PCRF and HA, or PCRF, ASN, and HA. The PDF can be combined with the PCC policy execution entity. At this time, the PDF can implement the role of the PCC policy execution entity; the PDF and PCC policy execution entities can also be set separately. In this case, the role of the PDF is the proxy of the PCC policy enforcement entity. The forwarding entity performs protocol conversion and message distribution between the PCRF and the PCC policy enforcement entity. The PCC policy enforcement entity may be located in the ASN, or located in the CSN, or located in the ASN and CSN. For example, a PCC policy enforcement entity located within the CSN can be bound to the HA.

The home agent (HA) is the agent of the user data plane. In order to optimize the network structure, the PCC policy enforcement entity C-PCEF in the CSN can be bound to the HA, so that when the MS is located in the home network, it can be unified. Policy enforcement, data plane gating, and billing point functionality. At this time, the allocation of the PCC policy enforcement entity C-PCEF of the CSN and the allocation of the HA can be considered uniformly. If the HA is allocated by the home AAA (HAAA) server, the H-PCEF (C-PCEF of the home network) and the HA are located in the hometown. Network, if the HA is assigned by the Visiting AAA (VAAA) server, the V-PCEF (C-PCEF of the visited network) and the HA are both located in the visited network. When the MS roams to the visited network, if the HA is in the home network, the H-PDF (hometown policy distribution entity) does not perform the conversion of the R3 interface to the Gx interface, or the signaling protocol of the R3 interface to the Ty interface, and the distribution of the PCC rules. And QoS mapping, H-PCEF only has the function of data plane detection, gating and charging point. H-PCRF provides PCC rules to the policy charging execution function entity H-PCEF located in the home CSN through the Gx interface or the Ty interface. The H-PCEF is located on the same data path as the HA, and the PCC rule is a PCC rule of the H-CSN; the policy charging execution function entity V-PCEF or V-PDF (the visited policy distribution entity) in the visited network is responsible for Performing conversion of signaling protocols from R3 interface to Gx interface or R3 interface to Ty interface, distribution of PCC rules and/or QoS mapping, and providing PCC policies/rules to SFAs in ASN; when MS roams to visited networks, and hometown proxy When the HA is located in the visited network, the H-PCRF provides a PCC policy/rule of the H-CSN to the V-PCRF/V-PF entity located in the visited network through the R5 interface, or the Gx interface, or the Ty interface, the V-PCRF After further performing the decision of visiting the network, the PCC rule is provided to the PCC policy enforcement entity through V-PDF. The PCC policy enforcement entity in the ASN is one or more of the anchor service flow authorization entity SFA, the service flow authorization entity SFA of the service, the anchor data path entity Anchor DPF, the accounting client, the charging agent, and the service flow management entity. composition. When the policy is controlled, the PDF provides the IP QoS parameter to the ASN QoS policy enforcement entity SFA, and the SFA is further configured to map the IP QoS parameter to the access bearer QoS parameter, and perform the access network policy execution.

When the PDF does not perform IP layer policy control according to the IP QoS parameter, the SFA is further configured to map the QoS parameter or the IP layer QoS parameter of the service layer authorization to the access bearer QoS parameter to execute the access network;

The access network anchored service flow authorization entity Anchor SFA performs the PCC rule splitting and provides the charging policy to the charging client, and provides the QoS policy to the service SFA; the charging client or the service SFA further measures The fee proxy provides charging policy information, and provides service flow detection information to the anchor DPF. The charging client performs charging according to the received charging policy information, and the anchor DPF performs service flow detection according to the service flow detection information.

The anchor SFA is used as the anchor point of the PCC policy enforcement entity at the ASN GW. It is responsible for receiving the PCC rules issued by the PCRF or PDF entity and transmitting it to the service SFA, and receiving the message of the service SFA and uploading it to the PDF entity/PCRF. The anchor SFA is bound to the MS Anchor Authenticator and migrates to the new ASN-GW along with the anchor authenticator when the MS re-authenticates. After the anchor SFA is migrated, the anchor SFA needs to be updated or registered to the PDF entity or PCRF entity (updated to the new SFA's identity and/or SFA IP address) so that the PCRF/PDF entity can know the new anchor SFA. The location to pass and request PCC rules. This anchor SFA location update/registration procedure may be accompanied by IP session modification in the terminal, such as during the IP session modification process of the terminal, simultaneously updating the anchor SFA identity and/or SFA IP address, or a separate SFA location update procedure. .

The billing agent reports the billing record information to the billing client (which can be located in the ASN GW, or the PCC policy enforcement entity C-PCEF located in the CSN) on a regular or real-time basis. The billing client of the service reports the billing record information to the AAA server through the current WiMAX-defined billing interface. The AAA server acts as the unified portal of the billing system, implements the Gy and Gz interfaces on the AAA, and further the AAA interface on the Gy and Gz interfaces. The charging record information is reported to the online charging system and the offline charging system. Alternatively, the charging client for the terminal service directly reports the charging record information to the online charging system and the offline charging system through the Gy interface and the Gz interface (the online charging system and the offline charging system can be implemented in AAA or as separate The entity exists). Or, the charging client for the terminal service reports the charging record information to the CDF (accounting distribution entity), further implements the Gy and Gz interfaces by the CDF, and reports the charging record information to the online charging system on the Gy and Gz interfaces. And an offline billing system; the CDF described above can be combined with the PDFs of the embodiments of Figures 2A, 2B and 3A.

2A is a schematic diagram of a WiMAX network and a PCC architecture in a first embodiment of the present invention. As shown in FIG. 2A, a PDF is connected to an ASN-GW through an R3 interface, and is connected to a PCRF through a Gx/Ty interface. The PDF is used as a PCRF and an ASN-GW. The protocol converter and/or the IP layer's policy executive, that is, the PDF converts the message from the Gx/Ty interface of the PCRF to the R3 interface and sends the message to the ASN-GW to convert the message from the R3 interface of the ASN-GW. A message for the Gx/Ty interface is sent to the PCRF. The PDF can be specifically connected to the Data Path Function (DPF) in the ASN-GW, or the SFA, or the Accounting Client/Accounting Agent. The following is a description of the specific implementation of the PDF connected to the SFA in the ASN-GW. The PCRF is configured to determine a PCC rule according to the quality of service QoS parameters and the charging policy information and the user subscription information authorized by the service layer, and the PCRF may further map the QoS parameters authorized by the service layer to the IP QoS parameters, and thus the QoS information included in the PCC rule. QoS parameters that can be authorized for the service layer, can also be IP QoS parameters, and provide PCC rules to the PDF; PDF is used to convert PCC rules from the PCRF from Gx/Ty interface messages to R3 interface messages and send them to the SFA; Performing QoS authorization and performing a QoS control policy according to the network resource condition of the local ASN and the QoS control policy in the PCC rule, and transmitting the service data flow detection information in the PCC rule to the DPF (Data Path Function), and The charging policy in the PCC rule is sent to the charging client/accounting agent. If the SFA and the DPF or the charging client/accounting agent are located in different ASN-GWs, the SFA connects to the DPF or the charging client through the R4 interface. The end/accounting agent sends the corresponding information if the SFA is located in the same way as the DPF or the accounting client/accounting agent The ASN-GW sends corresponding information to the DPF or the charging client/accounting agent through the internal interface. In the subsequent process, the DPF is configured to classify the data stream according to the received service data flow detection information, and the charging agent is configured to perform flow-based charging according to the received charging policy. The billing agent reports the billing record information to the billing client periodically or in real time. The billing client of the terminal service reports the billing record information to the AAA server through the current WiMAX-defined billing interface. The AAA server acts as the billing system. Ingress, the Gy and Gz interfaces are implemented on the AAA, and the AAA reports the charging record information on the Gy and Gz interfaces to the online charging system and the offline charging system. Alternatively, the charging client for the terminal service directly reports the charging record information to the online charging system and the offline charging system through the Gy interface and the Gz interface (the online charging system and the offline charging system can be implemented in AAA or as separate The entity exists). Or, the charging client for the terminal service reports the charging record information to the CDF, further implements the Gy and Gz interfaces by the CDF, and performs the charging record information to the online charging system and the offline charging on the Gy and Gz interfaces. System; The above CDF can be combined in the PDF of Fig. 2A of the present embodiment. As can be seen from the description of FIG. 2A, the true QoS control policy and the enforcement point of charging are functional entities in the ASN GW. The PDF is only used as a proxy between the ASN-GW and the PCRF, and a protocol conversion between the R3 interface and the Gx/Ty interface. Device. The PDF can be implemented on the PCRF or it can be a separate entity.

2C is a flowchart of QoS authorization control in Embodiment 3 of the present invention. As shown in FIG. 2C, the AF-triggered QoS authorization processing process includes the following steps:

Step 201C: The AF, such as the IP Multimedia System (IMS), the Proxy-Call Session Control Function (P-CSCF) establishes an application layer interaction with the MS.

Step 202C: The AF performs the authorization of the service layer on the MS, and sends a service parameter authorization request to the PCRF, and sends the QoS parameter and the service layer association information authorized by the service layer to the PCRF. The service layer association information includes at least the streaming description information provided by the AF to the PCRF, for example, WiMAX Content, and the WiMAX content includes information such as Reduced Resources indication, QoS Priority, and the like. If the MS is located in the visited network, the AF will find the home PCRF (H-PCRF) based on the user's identity, such as the IMS private identity, and send the QoS parameters and service layer association information authorized by the service layer to the H-PCRF.

Step 203C to step 204C: QoS parameters and policy information of the PCRF according to the service layer authorization And the user subscription information is used to make a policy decision, and after determining that the local network can meet the QoS parameters required by the AF, the PCRF can map the QoS parameters authorized by the service layer to the IP QoS parameters, and generate a PCC rule, where the QoS information included in the PCC rule can be a service. The QoS parameters of the layer authorization may also be IP QoS parameters, and then the PCRF sends a service parameter authorization request to the PDF, and provides the PCC rule to the PDF. If the PCRF determines that the local network cannot meet the QoS parameters required by the AF, it notifies the AF local network that the QoS parameters cannot be met, and the AF performs subsequent processing, such as modifying the QoS parameters. If the MS is located in the visited network, the H-PCRF performs policy decision based on the QoS parameters authorized by the service layer to generate a PCC rule, and provides the PCC rule to the visited PCRF (V-PCRF), and the V-PCRF provides the PCC rule to the visited V. -PDF. Further, the V-PCRF can determine a new PCC rule according to the PCC rules provided by the H-PCRF and the local control policy decision, and then provide the PCC rule to the V-PDF. If the MS is located in the visited network, but the PCC control architecture is not deployed in the visited network, the H-PCRF sends the PCC rules to the decision function entity V-PF of the visited network. The V-PF functions similarly to the V-PCRF. At this time, the protocol conversion is performed by the V-PF or a specially configured protocol converter, the PCC rule is converted into a parameter recognizable by the WiMAX network, and a new QoS authorization is generated according to the control policy decision of the local network, and the parameters are sent to the service flow. Authorized entity SFA is used.

Step 205C: After receiving the PCC rule, the PDF converts the PCC rule of the Gx/Ty interface into the PCC rule of the R3 interface, and then sends a service parameter authorization request to the SFA to provide the PCC rule to the SFA.

Step 206C: After the SFC receives the PCC rule, if the QoS information included in the PCC rule is a QoS parameter authorized by the service layer, the SFA maps the QoS parameter authorized by the service layer to the access bearer QoS parameter, if the QoS included in the PCC rule If the information is an IP QoS parameter, the SFA maps the IP QoS parameter to the access bearer QoS parameter, and determines that the local network can meet the QoS requirements of the PCC rule according to the network resource condition of the local ASN and the QoS control policy in the PCC rule, and then performs QoS authorization. And implement the QoS control strategy. If the SFA determines that the local network cannot meet the QoS requirements of the PCC rule, the PDF and the PCRF notify the AF local network that the QoS parameters cannot be met, and the AF performs subsequent processing, such as modifying the QoS parameters. If the PDF is directly connected to the SFA in the ASN-GW, the SFA sends the service data flow detection information in the PCC rule to the DPF, and sends the charging policy in the PCC rule to the charging client/accounting agent; PDF is connected to SFA, DPF and billing client/accounting agent in ASN-GW respectively, then PDF to PCC rules Then, the splitting is performed, and the PCC rule provided to the SFA is the QoS control policy in the PCC rule, and the service data flow detection information in the PCC rule is sent to the DPF, and the charging policy in the PCC rule is sent to the charging client/ Billing agent.

Step 207C: The SFA completes resource allocation and bearer establishment according to QoS requirements.

Step 208C to step 211C: The SFA returns a service parameter authorization response to the PDF. After receiving the service parameter authorization response, the PDF returns the service parameter authorization response to the PCRF. After receiving the service parameter authorization response, the PCRF returns the service parameter authorization response to the AF. . After receiving the authorization response of the service parameters, the AF continues the upper layer business process.

In the service process, the DPF classifies and detects the data stream according to the received service data flow detection information, and the charging agent performs flow-based charging according to the received charging policy.

The rest of the solutions in this embodiment are the same as those in the first embodiment of the present invention.

2D is a flowchart of QoS authorization control in Embodiment 4 of the present invention. As shown in FIG. 2D, the process of establishing a QoS authorization for establishing an IP-CAN bearer triggered by an ASN includes the following steps:

Step 201D is the same as step 201C.

Step 202: The MS initiates an IP-CAN bearer setup or modification request, where the IP-CAN bearer setup or modification request carries the home address and bearer information of the MS, such as a WiMAX session identifier and an SFA identifier, for bearer binding.

Steps 203D to 204D: The SFA sends a service parameter authorization request to the PDF. After receiving the service parameter authorization request, the PDF converts the service parameter authorization request of the R3 interface into a service parameter authorization request of the Gx/Ty interface, and then sends the service request to the PCRF. Parameter authorization request. If the MS is located in the visited network, the SFA sends a service parameter authorization request to the V-PDF (the PDF entity of the visited place), and after receiving the service parameter authorization request, the V-PDF sends the service to the V-PCRF (the PCRF entity of the visited place). Parameter authorization request. The V-PCRF sends a service parameter authorization request request PCC rule to the policy decision function entity H-PCRF of the home network.

Step 205D to Step 206D: After receiving the service parameter authorization request, the PCRF sends the service parameter authorization request to the AF, requesting application layer information, such as QoS parameters and data mapping information authorized by the service layer. The data mapping information includes at least streaming media description information. After receiving the service parameter authorization request, the AF sends a service parameter authorization response to the PCRF, and provides the service layer authorization QoS parameter and data mapping information corresponding to the MS (using the home address identifier) to the PCRF. If the MS is located in the visited network The AF sends a service parameter authorization response to the V-PCRF.

Steps 207D to 208D: The PCRF performs policy decision according to the QoS parameters authorized by the service layer, determines that the local network can meet the QoS parameters required by the AF, generates a PCC rule, and then sends a service parameter authorization response to the PDF by the PCRF, and provides the PCC rule to the PDF. . If the PCRF determines that the local network cannot meet the QoS parameters required by the AF, it notifies the AF local network that the QoS parameters cannot be met, and the AF performs subsequent processing, such as modifying the QoS parameters. If the MS is located in the visited network, the V-PCRF receives the service parameter authorization response, and provides the QoS parameters authorized by the service layer to the H-PCRF. The H-PCRF performs policy decision according to the QoS parameters authorized by the service layer, determines that the local network can meet the QoS parameters required by the AF, generates a PCC rule, and then the H-PCRF returns a service parameter authorization response to the V-PCRF to provide the PCC rule. Further, the V-PCRF can determine new PCC rules according to the PCC rules provided by the H-PCRF and the policy decisions of the local network. The V-PCRF sends a service parameter authorization response to the V-PDF, and provides the PCC rule to the V-PDF. If the MS is located on the visited network, but the PCC control architecture is not deployed on the visited network, the H-PCRF sends the PCC rules to the decision function entity V-PF of the visited network. The V-PF functions similarly to the V-PCRF. At this time, the protocol conversion is performed by the V-PF or a specially set protocol converter, the PCC rule is converted into a parameter recognizable by the WiMAX network, and a new QoS authorization is generated according to the control strategy decision of the local network and sent to the service flow. Authorized entity SFA is used.

Step 209D: After receiving the PCC rule, the PDF converts the PCC rule of the Gx/Ty interface into the PCC rule of the R3 interface, and then sends a service parameter authorization response to the SFA to provide the PCC rule to the SFA.

Step 210D is the same as step 206C.

Step 211D to Step 212D: The SFA completes bearer establishment and modification according to QoS requirements. AF continues the upper business process.

If the PDF is only connected to the DPF of the ASN-GW or the charging client/accounting agent, the PDF needs to provide the PCC rule, ie the QoS control policy, to the SFA through the DPF or the charging client/accounting agent.

Because the PCC is located between the service control layer and the access or bearer layer, it is shielded from the service control layer. Specific technology and topology information of the ingress or bearer layer. The PCC receives the QoS authorization parameters related to the service from the service control layer, and then combines with the admission control policy, the topology information of the network, etc., and converts the service QoS parameters into IP QoS parameters, and then provides the relevant access or bearer layer. A node, such as an SFA, then the SFA implements corresponding QoS control based on the received QoS parameters and the policies of the access or bearer network. The mapping of IP QoS parameters to access bearer QoS parameters can be performed on the PCC Policy Enforcement Entity or PDF.

3A is a schematic diagram of a WiMAX network and a PCC architecture in a fifth embodiment of the present invention. As shown in FIG. 3A, the PDF serves as a proxy between the ASN-GW and the PCRF, and a protocol converter of the R3 interface and the Gx/Ty interface. It is further used to perform IP layer policy enforcement, that is, after the PDF receives the PCC rule, it is used to map the service QoS parameter to the IP QoS parameter, as the IP layer policy control execution point, and according to the IP QoS parameter, the IP layer flow-based charging policy. Perform billing and gating of data packets. The PDF can be further used to map the IP QoS parameters to the access bearer QoS parameters; the PDF can also directly provide the IP QoS parameters to the SFA, and the SFA is further used to map the received IP QoS parameters into the access bearer QoS parameters and the implementation. QoS policy enforcement of the incoming network. The PDF provides QoS parameters (access bearer QoS parameters, or IP QoS parameters) to the SFA through an interface with the SFA. In this way, separate QoS control and independent charging can be performed on the access bearer layer and the IP layer, and the topology structure of the specific access bearer layer is hidden from the IP layer. After the SFA receives the PCC rule, the SFA sends the service data flow detection information in the PCC rule to the DPF to filter the data packet, and sends the charging policy in the PCC rule to the charging client/accounting agent for charging. The connection relationship between the PDF and the ASN-GW can also be the same as that of FIG. 2B, that is, the PDF is respectively connected to the SFA, the DPF, and the charging client/accounting agent in the ASN-GW. The billing agent reports the billing record information to the billing client periodically or in real time. The billing client of the terminal service reports the billing record information to the AAA server through the current WiMAX-defined billing interface. The AAA server acts as the billing system. Ingress, the Gy and Gz interfaces are implemented on the AAA, and the AAA reports the charging record information on the Gy and Gz interfaces to the online charging system and the offline charging system. Alternatively, the charging client for the terminal service directly reports the charging record information to the online charging system and the offline charging system through the Gy interface and the Gz interface (the online charging system and the offline charging system can be implemented in AAA or as separate The entity exists). Or, the charging client for the terminal service reports the charging record information to the CDF, further implements the Gy and Gz interfaces by the CDF, and reports the charging record information to the online charging system on the Gy and Gz interfaces. And an offline charging system; the above CDF and the PDF in FIG. 3A of the present embodiment can be combined. The PDF/CDF can be located either in the ASN domain or in the CSN domain.

The home agent (HA) is the agent of the user data plane. In order to optimize the network structure, the PCC policy enforcement entity can be bound to the HA, so that when the MS is located in the home network, the policy execution and data plane can be unified. Gating, and billing point functions. At this time, the allocation of the policy enforcement entity C-PCEF (CSN PCEF) in the CSN and the allocation of the HA can be considered uniformly. If assigned by the home AAA (HAAA) server, the C-PCEF and the HA are located in the home network, if visited by the AAA (VAAA) Server Assignment, then C-PCEF and HA are located on the visited network. When the MS roams to the visited network, if the HA is in the home network, the C-PCEF described here is the home C-PCEF, and the C-PCEF only has the function of detecting, gating and charging points of the data plane; The V-PDF of the network is responsible for the conversion of R3/Gx or R3/Ty signaling protocols, the distribution of PCC rules, and QoS mapping.

FIG. 3B is a flowchart of QoS authorization control according to Embodiment 6 of the present invention. The difference between the procedure and the fourth embodiment is that the PDF performs mapping of IP QoS to access network QoS parameters in the PCC rule, and the PDF will map the access network QoS. The parameter is sent to the service flow authorization entity SFA in the access network for execution.

4A is a schematic diagram of a WiMAX network and a PCC architecture in a seventh embodiment of the present invention. As shown in FIG. 4A, the PCRF is used as a policy decision point, and the PCC policy execution entity that is a policy enforcement point is bound to the ASN-GW. Tightly coupled, tightly combining the policy control and charging policy control of the WiMAX network with the PCC architecture, unified the policy control and charging policy control system of the WiMAX network, and this method is consistent with the policy control architecture and charging. The original intention of the control architecture convergence can simplify the functional entity structure in the network, reduce the signaling interaction process, and reduce the service establishment time. The functions of the PCC Policy Enforcement Entity are implemented in one or more entities of the SFA, DPF and Accounting Client/Accounting Agent, SFM and HA within the ASN, respectively. At this time, the PCC policy enforcement entity needs to provide the corresponding information to other functional entities. For example, if the PCC policy enforcement entity is implemented in the SFA, the SFA needs to send the service data flow detection information in the PCC rule to the PCC rule. The DPF, and the charging policy in the PCC rule are sent to the charging client. Delivered PCC rules, request PCC rules from the PCRF, and provide PCC policy enforcement entities and PCRFs Between the PCC interface. When the terminal is initially connected to the network, the anchor SFA is located in the service GW of the initial network access of the MS, and the anchor SFA is bound to the anchor Authenticator of the MS. When the MS is re-authenticated, the anchor authentication device is accompanied. Migrate to the new ASN GW together.

The billing agent reports the billing record information to the billing client periodically or in real time. The billing client in the PCC policy enforcement entity reports the billing record information to the AAA server through the current WiMAX R3 interface, and the AAA server acts as the unified billing system. Ingress, the Gy and Gz interfaces are implemented on the AAA, and the AAA reports the charging record information on the Gy and Gz interfaces to the online charging system and the offline charging system. Alternatively, the charging client directly sends the charging information to the online charging system and the offline charging system through the Gy interface and the Gz interface (the online charging system and the offline charging system can be implemented in AAA or as a separate entity). presence). Considering the consistency with the PCC architecture, SFA, DPF, and billing agents can be bound. The difference between this implementation and the prior art is that the function of the PCEF is implemented by the functional entities SFA, DPF, and charging client/accounting agent and/or SFM of the ASN-GW, and does not require a dedicated R3 interface and a Gx/Ty interface. The protocol converter, the protocol conversion function is implemented in the ASN-GW, or directly implements the Gx/Ty protocol on the R3 interface to support the transmission of PCC rules.

4B is a flowchart of QoS authorization control in Embodiment 8 of the present invention. As shown in FIG. 4B, the QoS authorization processing procedure triggered by the AF includes the following steps:

Steps 401B to 402B are the same as steps 201C to 202C.

Step 403B to step 404B: The PCRF performs policy decision according to the QoS parameters authorized by the service layer, determines that the local network can meet the QoS parameters required by the AF, generates a PCC rule, and then the PCRF sends a service parameter authorization request to the SFA, and provides the PCC rule to the SFA. . If the PCRF determines that the local network cannot meet the QoS parameters required by the AF, it notifies the AF local network that the QoS parameters cannot be met, and the AF performs subsequent processing, such as modifying the QoS parameters. If the MS is located in the visited network, the H-PCRF performs a policy decision according to the QoS parameters authorized by the service layer to generate a PCC rule, and provides the PCC rule to the V-PCRF, and the V-PCRF provides the PCC rule to the SFA. Further, the V-PCRF may determine a new PCC rule according to the PCC rules provided by the H-PCRF and the local control policy decision, and then provide the PCC rule to the SFA. If the MS is located in the visited network, but the PCC control architecture is not deployed in the visited network, the H-PCRF sends the PCC rule to the decision function entity V-PF of the visited network. The V-PF functions similarly to the V-PCRF. At this time, by V-PF or special The protocol converter set by the gate performs protocol conversion, converts the PCC rule into a parameter recognizable by the WiMAX network, and generates a new QoS authorization and other parameters according to the control policy decision of the local network and sends the parameter to the service flow authorization entity SFA.

Step 405B: After receiving the PCC rule, the SFA converts the PCC rule of the Gx/Ty interface into the PCC rule of the R3 interface, and then maps the QoS parameter authorized by the service layer to the access bearer QoS parameter, according to the network resource condition of the local ASN. The QoS control policy in the PCC rule determines that the local network can meet the QoS requirements of the PCC rule, performs QoS authorization, and executes the QoS control policy. If the SFA determines that the local network cannot meet the QoS requirements of the PCC rule, the PCRF notifies the AF local network that the QoS parameters cannot be met, and the AF performs subsequent processing, such as modifying the QoS parameters. If the PCEF is only implemented in the SFA of the ASN-GW, the SFA also needs to send the service data flow detection information in the PCC rule to the DPF, and send the charging policy in the PCC rule to the charging client/accounting agent; The PCEF includes functional entities such as SFA, DPF, and charging proxy and/or service flow management entity SFM in the ASN. The SFA obtains the QoS control policy in the PCC rule, and the DPF obtains the service data flow detection information in the PCC rule, and the charging client The end/accounting agent obtains the charging policy in the PCC rule.

Step 406B is the same as step 207C.

Step 407B to step 409B: The SFA returns the service parameter authorization response to the PCRF. After receiving the service parameter authorization response, the PCRF returns the service parameter authorization response to the AF. After receiving the authorization response of the service parameters, the AF continues the upper-layer business process.

4C is a flowchart of QoS authorization control in Embodiment 9 of the present invention. As shown in FIG. 4C, the process of establishing a QoS authorization for establishing an IP-CAN bearer triggered by an ASN includes the following steps:

Steps 401C to 402C are the same as steps 201D to 202D.

Step 403C: The SFA sends the service parameter authorization request to the PCRF. If the MS is located in the visited network, the SFA sends the service parameter authorization request to the V-PCRF, and the V-PCRF sends a service parameter authorization request request PCC rule to the policy decision entity H-PCRF in the home network.

Steps 404C to 405C are the same as steps 205D to 206D.

Step 406C to step 407C: The QoS parameter and charging policy of the PCRF according to the service layer authorization The information and the user subscription information are used for policy decision. After determining that the local network can meet the QoS parameters required by the AF, the PCC rule is generated, and then the PCRF sends a service parameter authorization response to the SFA, and provides the PCC rule to the SFA. If the PCRF determines that the local network cannot meet the QoS parameters required by the AF, it notifies the AF local network that the QoS parameters cannot be met, and the AF performs subsequent processing, such as modifying the QoS parameters. If the MS is located in the visited network, the V-PCRF receives the service parameter authorization response, and provides the QoS parameter authorized by the service layer to the H-PCRF. The H-PCRF performs policy decision according to the QoS parameters authorized by the service layer, determines that the local network can meet the QoS parameters required by the AF, and generates a PCC rule, and then the H-PCRF returns a service parameter authorization response to the V-PCRF to provide the PCC rule. Advance to new PCC rules. The V-PCRF sends a service parameter authorization response to the V-PCEF, and provides the PCC rule to the V-PCEF. If the MS is located on the visited network, but the PCC control architecture is not deployed in the visited network, the H-PCRF sends the PCC rule to the decision function entity V-PF of the visited network. The V-PF functions similarly to the V-PCRF. At this time, the protocol conversion is performed by the V-PF or the specially set protocol converter, the PCC rule is converted into a parameter recognizable by the WiMAX network, and a new QoS authorization is generated according to the control strategy decision of the local network and sent to the service flow. Authorized entity SFA is used.

Step 408C is the same as step 405B.

Steps 409C to 410C are the same as steps 211D to 212D.

When the PCEF is combined with the PCC policy enforcement entity, it provides PCC rules to other PCC policy enforcement entities (accounting clients, data path entities DPF) through the internal interface.

As a policy decision point, PCRF can be located in the CSN domain. The PCRF is connected to the AAA server through the Sp interface. The Sp interface is used not only to obtain the description file, but also to obtain the information about the rate information corresponding to the service data flow.

The accounting client reports the accounting records generated by the accounting agent statistics to the AAA server. If the AAA server is the unified entry of the PCC architecture charging system, the AAA reports the charging record information to the online charging system and the offline charging system on the Gy and Gz interfaces. Or, the billing client for the terminal service directly goes to the online billing system and the offline meter through the Gy interface and the Gz interface. The fee system reports the billing record information. Alternatively, the charging client for the terminal service reports the charging record information to the CDF through the charging interface of the R3-PCC, further implements the Gy and Gz interfaces by the CDF, and reports the charging record information to the online charging on the Gy and Gz interfaces. System and offline billing system. Online charging systems and offline charging systems can be implemented in AAA or as separate entities.

In the embodiment provided by the present invention, the PCRF determines the PCC rule according to the QoS parameters and the charging policy authorized by the service layer and the subscription information of the user, and the PDF serves as an interface between the PCRF and the PCC policy enforcement entity, and performs protocol conversion and message distribution, PCC. The policy enforcement entity performs QoS authorization and charging of the service data flow according to the PCC rules, and proposes a feasible solution for the convergence of the WiMAX network and the 3GPP/3GPP2 network PCC architecture, realizing the WiMAX network using the PCC architecture to implement the policy control of the service and Billing control, and solves the problem that the functional entities in the PCC architecture are integrated with the SFA, DPF, billing client/accounting agent and/or HA of the WiMAX network, and the WiMAX network is utilized to utilize the PCC. The architecture implements a process flow and a convergence scheme for policy control and charging control of the service. In the basic process of service establishment, the WiMAX network is integrated with the PCC architecture to implement policy control and charging control for the service, and to solve the problem of interconnecting the WiMAX and the 3GPP/3GPP2 network through the unified PCC architecture when using the IMS service. In addition, this chapter provides a variety of possible implementations, which can be flexibly selected according to actual needs.

Those skilled in the art will appreciate that the present invention is applicable not only to networks in which WiMAX networks are integrated with 3GPP/3GPP2 networks, but also to other types of wireless and wired converged communication networks. The spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of the inventions

Claims

Rights request

A system for network convergence policy charging control architecture, characterized in that: the system comprises: a global interoperability network for microwave access, an access service network in a WiMAX, an access service network

2. The system according to claim 1, wherein the PDF is set separately, or implemented in the following units or any combination thereof:

PCRF, home agent HA and ASN.

3. The system according to claim 1, wherein the PCC policy enforcement entity comprises a service flow authorization entity SFA, a data path function entity DPF, a charging client/accounting agent, and/or a service flow management entity SFM. ,

The SFA performs QoS authorization and performs a QoS control policy according to the network resource condition of the local ASN and the QoS control policy in the PCC rule, and sends the service data flow detection information in the PCC rule to the DPF, and the PCC rule The charging policy is sent to the charging client/accounting agent.

4. The system of claim 3, wherein

The PCRF is further configured to map the QoS parameters authorized by the service layer to IP QoS parameters and provide the PDF parameters; or

The PDF is further configured to map the QoS parameters authorized by the service layer to IP QoS parameters.

5. The system of claim 4 wherein:

The PDF is further configured to map the IP QoS parameter to an access bearer QoS parameter, and provide the access bearer QoS parameter to a PCC policy enforcement entity; or The PDF is further configured to provide the IP QoS parameter to a PCC policy enforcement entity, and the PCC policy enforcement entity is further configured to map the IP QoS parameter to an access bearer QoS parameter.

6. The system of claim 1 wherein:

The PCC policy enforcement entity is disposed in the CSN and is bundled with the HA within the CSN.

7. A system according to any of claims 4 to 6, characterized in that

The PCC policy enforcement entity performs IP layer policy control according to the IP QoS parameter, and/or performs service flow policy control based on the access bearer QoS parameter.

8. The system of claim 2, wherein

The PDF is connected to an anchor SFA in the ASN, and the anchor SFA is configured to provide a QoS control policy in the PCC rule to the service SFA, and provide service data flow detection information in the PCC rule to The DPF, and providing a charging policy in the PCC rule to the charging client/accounting agent.

The system according to any one of claims 1 to 3, wherein when the terminal roams to the visited network, the system includes:

Visiting the PCRF of the visited place in the network and the PDF of the visited place, the PCRF of the home place in the home network, and the PCRF of the visited place is used to request the PCC rule from the PCRF of the home place and execute the decision of the visited network, and The PDF of the visited place provides the PCC rule after the decision; or the system includes: a PCRF of the visited place, a PDF and a PCRF of the home location, the attribution of the PCC rule is converted, and the converted parameter is provided To the PCRF of the visited place of the visited network, the PCRF of the visited place acts as an interface between the WiMAXASN and the home CSN and performs a decision to visit the network.

10. The system of claim 9 wherein:

When the HA is located in the home network, the PCRF of the home is used to provide a PCC policy/rule to the PCC policy enforcement entity located in the home CSN, and the PCRF of the visited place is used to further perform the decision of the visited network and then visit the visited place. The PDF entity provides PCC policies/rules to the PCC policy enforcement entity;

When the HA is located in the visited network, the PCRF of the home location is used to worship the visited network. The visited PCRF provides the PCC policy/rule of the home CSN, and the PCRF of the visited place is used to perform the decision of the visited network and then provide the PCC policy/rule to the PCC policy enforcement entity through the visited PDF entity.

11. The system of claim 1 or 2, wherein

The PCC policy enforcement entity generates the charging record information according to the received charging statistics, and reports the charging record information to the charging server through the charging distribution entity CDF;

The billing server includes an online billing system OCS, an offline billing system OFCS and/or an AAA server.

12. The system of claim 11 wherein:

If the AAA server is used as the unified entry for the billing client in the PCC-based billing system, the PCC policy enforcement entity reports the billing information to the AAA, and then the AAA reports the information to the OCS or OFCS system through the Gy or Gz interface; or

The PCC policy enforcement entity reports the charging record information to the online charging system and the offline charging system through the Gy interface and the Gz interface; or

The PCC policy enforcement entity reports the charging information to the CDF entity, and the CDF entity passes the

The Gy interface and the Gz interface are reported to the online charging system and the offline charging system to report the charging record information; or

The OCS/OFCS is located on the AAA server, and the PCC policy enforcement entity uses the Gy/Gz interface.

The AAA server reports the accounting information.

13. The system of claim 11 wherein:

The PCC policy enforcement entity performs an IP layer charging function or a traffic flow based charging function.

A system for a network convergence policy charging control architecture, the system comprising: a policy control and charging rule function entity PCRF, a policy distribution entity PDF, and a PCC policy enforcement entity, wherein

The PDF is used for protocol conversion and message distribution as an interface between the PCRF and the PCC policy enforcement entity; Flow QoS authorization, QoS policy, and accounting.

15. The system according to claim 14, wherein the PCC policy enforcement entity comprises a service flow authorization entity SFA, a data path function entity DPF, a charging client/accounting agent, and/or a service flow management entity SFM. ,

16. The system of claim 15 wherein:

17. The system of claim 16 wherein:

The PDF is further configured to map the IP QoS parameter to an access bearer QoS parameter, and provide the access bearer QoS parameter to a PCC policy enforcement entity; or

The PDF is further configured to provide the IP QoS parameter to a PCC policy enforcement entity, and the PCC policy enforcement entity is further configured to map the IP QoS parameter to an access bearer QoS parameter.

18. System according to claim 14 or 15, characterized in that

The charging server includes an online charging system 0CS, an offline charging system 0FCS and/or an AAA server;

A policy charging control method for a network convergence policy charging control architecture, the method comprising:

Policy distribution entity PDF acquisition policy control and charging rule function entity The PCRF determines the PCC rule according to the QoS parameters of the service layer authorization, the charging policy information, and the user subscription information;

The PDF provides the PCC rule to a PCC policy enforcement entity; QoS authorization and accounting for flows.

The method according to claim 19, wherein the providing the PC to the PCC policy enforcement entity by the PDF comprises:

The PDF performs protocol conversion, and the PCC rule is carried to an interface protocol supported by the PCC policy enforcement entity, and sent to the PCC policy execution entity.

The method according to claim 19, wherein after the PDF receives the PCC rule, the method further includes:

The PCRF obtains the IP QoS parameter through the QoS parameter mapping of the service layer authorization and provides the PDF QoS parameter, or obtains the IP QoS parameter by the PDF through the QoS parameter mapping authorized by the service layer.

22. The method of claim 21, wherein

After the PDF receives the PCC rule, the PDF further includes:

The PDF maps the IP QoS parameters to the access bearer QoS parameters, and provides the access bearer QoS parameters to the PCC policy enforcement entity; or

The PDF provides the IP QoS parameters to a PCC policy enforcement entity, and the PCC policy enforcement entity maps the IP QoS parameters to access bearer QoS parameters.

23. A method according to claim 21 or 22, characterized in that

The method according to any one of claims 19 to 22, wherein the PCC policy enforcement entity in the ASN comprises a service flow licensor entity SFA, a data path function entity DPF, a charging client/billing One or more of the agents, business flow management entities SFM,

The PDF is connected to the SFA, and after receiving the PCC rule, the ASN further includes: the SFA providing the service data flow detection information in the PCC rule to the DPF, and providing the charging policy in the PCC rule To the billing client/accounting agent.

After receiving the PCC rule, the PCC policy enforcement entity in the ASN further includes: The SFA maps the QoS parameters of the service layer authorization to the access bearer QoS parameters. After the PCC policy enforcement entity in the ASN receives the PCC rule, the method further includes: the PDF provides the IP QoS parameter to the SFA, and the SFA provides the IP QoS parameter. The parameters are mapped to access bearer QoS parameters.

The method according to any one of claims 19 to 22, wherein when the terminal roams to the visited network,

The PCRF of the visited place in the visited network is used to request a PCC rule from the PCRF of the home location and execute a decision of the visited network, and provide the PCC rule of the decision to the PDF of the visited place; or

The PCRF of the home location in the home network provides a PCC rule to the PCRF of the visited network decision function entity by using a protocol converter, and the protocol converter is configured to convert the PCC rule, and convert the converted parameter Provided to the PCRF of the visited place of the visited network, the PCRF of the visited place further performs a policy of visiting the network.

27. The method of claim 26, wherein

When the terminal roams to the visited network and the HA is located in the home network, the PCRF of the home location provides a PCC policy/rule to the PCC policy enforcement entity located in the home CSN, and the PCRF of the visited place further performs the decision of the visited network and then visits the place The PDF entity provides PCC policies/rules to the PCC policy enforcement entity;

When the terminal roams to the visited network and the HA is located in the visited network, the PCRF of the home location provides the PCC policy/rule of the home CSN to the PCRF entity located in the visited place of the visited network, and the PCRF of the visited place further performs the decision of the visited network. The PCC policy/rule is then provided to the PCC policy enforcement entity via the visited PDF entity.

The method according to any one of claims 19 to 22, wherein the PCRF provides the PCC rule to the PCC policy enforcement entity C-PCEF in the CSN, and the PCC policy enforcement entity in the CSN according to the PCC policy / Rules enforce QoS and or billing policies.