WO2009036695A1

WO2009036695A1 - METHOD, APPARATUS AND SYSTEM FOR NEGOTIATING QoS

Info

Publication number: WO2009036695A1
Application number: PCT/CN2008/072365
Authority: WO
Inventors: Wei Zhang; Liang Gu; Yuhua Chen; Yali Zheng; Yong Xie
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-09-14
Filing date: 2008-09-12
Publication date: 2009-03-26

Abstract

A method for negotiating the quality of service is provided. The method includes: a policy charging enforcement function PCEF entity reporting the quality of service QoS reduced by an access network to a policy charging rule function PCRF entity; the PCRF entity authorizing the reduced QoS. The problem that the access network can not negotiate the QoS with PCRF entity under the frame of PCC existed in the prior art is solved by the method. Meanwhile a system and a network entity for negotiating the quality of service are provided. A method, an apparatus and a system for negotiating the quality of service are also provided.

Description

Method, device and system for QoS negotiation

The present invention relates to network communication technologies, and in particular, to a method, device and system for quality of service negotiation.

Background technique

Policy and Charging Control (PCC) is a universal fit for various IPs defined in Release 3 (R7) of the 3rd Generation Partnership Project (3GPP). Functional architecture of policy control and charging control for the IP Connectivity Access Network (IP CAN).

Worldwide Interoperability for Microwave Access (WiMAX) is a wireless metropolitan area network technology based on the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard.

The WiMAX network is mainly composed of three parts: a client (MS), an access service network (ASN), and a connection service network (CSN). The access service network includes a base station (BS) and an access service network gateway (ASN GW); the connection service network includes a home agent (HA), an application server (AF), and an authentication, authorization, and accounting server (AAA Server). entity. The wireless side of the WiMAX network is a wireless metropolitan area network access technology based on the IEEE 802.16d/e standard.

In order to integrate with the 3GPP, the WiMAX system also introduces the PCC architecture. As shown in Figure 1, the Policy Charging Rule Function (PCRF) entity is responsible for making policy decisions and performing policy charging (Policy Charging). The Enforcement Function, PCEF) entity provides PCC rules. The PCEF entity is responsible for performing policies and charging according to the PCC rules provided by the PCRF entity; the PCEF entity in WiMAX is a distributed functional entity, which includes a Policy Distribution Function (PDF), and a PCEF entity (A-PCEF) within the ASN. Entity) and/or PCEF entity (C-PCEF entity) within the CSN. The interface between the PCRF entity and the PCEF entity is called the Gx interface. The Policy Distribution Function (PDF) is a logical entity that facilitates integration with the 3GPP/PCC architecture. It has the following characteristics: It connects to the PCRF entity through the Gx interface, and the Gx interface terminates in PDF for the PCRF entity; PDF shields the mobility of the A-PCEF entity from the PCRF entity; PDF connects to the A-PCEF entity using the PCC-R3 interface, It also supports the migration of A-PCEF entities; PDF is the distribution point of PCC rules and is responsible for distributing PCC rules to PCEF entities. It forwards the message between the A-PCEF entity and the PCRF entity and the message between the C-PCEF entity and the PCRF entity. The physical location of the PDF depends on the implementation choice.

In the prior art, the PCRF entity provides policy and charging information for the IP CAN bearer. The information is carried in the PCC rule and sent to the PCEF entity. The PCEF entity performs corresponding operations on the IP CAN bearer according to the received PCC rule. There are two ways for a PCRF entity to provide PCC rules to a PCEF entity:

Pull mode: The PCEF entity sends a PCC rule request message, such as a CCR message, to the PCRF entity, and the PCRF entity generates a PCC rule according to at least one of information from the PCEF entity, service information, and user subscription information, and requests through the trust control. The (Credit-Control-Request, CCA) message is sent to the PCEF entity. The PCEF entity provides PCC rules to the access network, and the access network establishes/modifies the corresponding bearers.

Push mode: The PCRF entity generates a PCC rule based on the obtained service information and/or user subscription information, and sends the PCC rule to the PCEF entity through the RAR message. The PCEF entity provides PCC rules to the access network, the access network establishes/modifies the corresponding bearers, and then returns a response message to the PCEF entity. The PCEF entity returns a PCC Rule Response message, such as a RAA message, to the PCRF entity.

However, after receiving the QoS policy provided by the PCEF entity, the IP CAN may cut the QoS according to the resource situation. However, in the prior art, it is not defined how to allow the access network to perform resource reduction when the IP CAN resource is limited, and how the access network negotiates QoS reduction with the PCRF entity.

In summary, under the current PCC architecture, IP CAN and PCRF entities cannot perform QoS negotiation when IP CAN resources are limited. In addition, WiMAX QoS refers to some processes defined to ensure end-to-end QoS in a network with multiple service providers. A user can be associated with a number of traffic flows, which can have different QoS attributes, which can be considered to be defined in a user management system (eg, an AAA database) or a policy server. Under the static QoS service model, the user is not allowed to change the defined service flow data parameters or dynamically create a service flow. Under the dynamic QoS service model, the MS or BS can dynamically create, modify, or delete traffic flows. When an MS registers with a WiMAX network and begins IP data transmission, it can create, license, and activate a complete set of traffic flows by default. After an MS successfully registers with the WiMAX network, an Anchor SFA must be assigned to the MS. If the user's QoS has been downloaded from the AAA, the SFA initiates the creation, licensing, and activation of the service flow. There may be times when the service flow cannot be created or activated in the ASN. In this case, the corresponding processing needs to be determined according to the QoS policy in the ASN and the negotiation between the NAP and the NSP.

In the prior art, the QoS final authorization function entity cannot negotiate the QoS service flow profile reduction, and finally determines whether to allow the reduction.

Summary of the invention

The embodiments of the present invention provide a method, a system, and a network entity for negotiating service quality, which are used to solve the problem that the IP CAN and the PCRF entity cannot perform QoS negotiation under the PCC architecture in the prior art.

A method for negotiating quality of service provided by an embodiment of the present invention, where the method includes:

The policy-based charging function is performed by the PCEF entity to report the QoS of the access network to the policy-based charging rule function (PCRF entity), so that the PCRF entity authorizes the reduced QoS.

A system for negotiating quality of service provided by an embodiment of the present invention, where the system includes:

The policy charging execution function is used by the PCEF entity to report the quality of service QoS of the access network to the policy charging rule function PCRF entity.

The PCRF entity is configured to authorize the reduced QoS. In the embodiment of the present invention, the PCEF entity reports the QoS of the access network to the policy charging rule function PCRF entity, and the PCRF entity authorizes the reduced QoS, thereby implementing QoS negotiation under the PCC structure.

The PCEF entity of the policy charging execution function provided by the embodiment of the present invention includes: an obtaining module, configured to obtain a quality of service QoS after the access network is cut;

The reporting module is configured to report the reduced QoS to the policy charging execution function PCRF entity. A policy-based charging rule function, which is provided by the embodiment of the present invention, includes: a processing module, configured to receive a reduced version of a PCEF entity reported from a policy charging execution function

QoS;

An authorization module, configured to authorize the reduced QoS.

In the embodiment of the present invention, the PCEF entity reports the QoS of the access network to the policy charging rule function PCRF entity; the PCRF entity authorizes the reduced QoS, thereby implementing QoS negotiation under the PCC structure.

On the other hand, in order to solve the problem that the QoS final authorization function entity cannot negotiate the QoS service flow attribute reduction in the prior art, and finally determine whether to allow the reduction, the embodiment of the present invention provides a method for service quality negotiation, including:

The QoS final authorization function entity determines the QoS service flow attributes that can be reduced;

The QoS final authorization function entity sends the determined QoS service flow attribute to the SFM; the SFM determines the QoS service flow attribute according to the QoS service flow attribute sent by the QoS final authorization function entity, and finally reduces the negotiation result, and according to the final reduction The result of the negotiation is used to establish a QoS service flow.

The embodiment of the present invention further provides a QoS final authorization function entity device, including: a determining module: configured to determine a QoS service flow attribute that can be reduced;

The sending module is configured to send, to the SFM, a QoS service flow attribute determined by the determining module.

A WiMAX system that includes:

a QoS final authorization function entity, configured to determine a QoS service flow attribute that can be reduced; Determining the QoS service flow attributes that can be reduced;

The SFM is used to determine the QoS service flow attribute according to the QoS service flow attribute and finally reduce the negotiation result; and perform the QoS service flow establishment operation according to the final reduction negotiation result.

It can be seen from the foregoing specific embodiments provided by the embodiments of the present invention that the authorization feedback mechanism for the QoS final authorization function entity and the SFM to reduce and negotiate the QoS service flow attributes is provided, so that when the user's QoS resources need to be reduced, After the SFM negotiates with the QoS final authorization function entity, the negotiated authorization result is fed back to the SFM, and finally determines whether the QoS service flow is processed and processed, thereby ensuring that the QoS final authorization function entity can control whether the cut is allowed or not. Network resource management.

DRAWINGS

Figure 1 is a schematic diagram showing the structure of a PCC architecture introduced in a WiMAX system;

2 is a schematic diagram of a system for service quality negotiation according to an embodiment of the present invention;

3 is a schematic structural diagram 1 of a PCEF entity according to an embodiment of the present invention;

4 is a schematic structural diagram 2 of a PCEF entity according to an embodiment of the present invention;

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

6 is a schematic structural diagram 1 of a PCRF entity according to an embodiment of the present invention;

7 is a schematic flowchart 1 of a method for service quality negotiation according to an embodiment of the present invention;

8 is a schematic flowchart 2 of a method for negotiating service quality according to an embodiment of the present invention;

9 is a schematic flowchart 3 of a method for service quality negotiation according to an embodiment of the present invention;

10 is a schematic flowchart of a method for negotiating service quality in a pull mode according to an embodiment of the present invention; FIG. 11 is a schematic flowchart 1 of a method for negotiating service quality in a push mode according to an embodiment of the present invention; FIG. 12 is a service quality negotiation in a push mode according to an embodiment of the present invention; The schematic diagram of the method flow is two.

FIG. 13 is a flowchart of a method for service quality negotiation according to an embodiment of the present invention;

FIG. 14 is a flowchart of a method for quality of service negotiation according to an embodiment of the present invention;

15, 16 and 17 are structural diagrams of a QoS final authorization function entity device according to an embodiment of the present invention; FIG. 18 is a structural diagram of a system WiMAX according to an embodiment of the present invention.

detailed description

In the embodiment of the present invention, if the access network performs resource reduction on the authorized QoS, the PCEF entity reports to the PCRF entity, and the PCRF entity authorizes the reduced QoS to indicate whether the PCEF entity allows the reduction, and implements the PCC architecture. , Negotiation of QoS reduction.

The embodiments of the present invention are further described in detail below with reference to the accompanying drawings.

As shown in FIG. 2, a schematic diagram 1 of a system for negotiating quality of service according to an embodiment of the present invention includes: a PCEF entity 10 and a PCRF entity 20.

The PCEF entity 10 is configured to report the QoS of the access network to the PCRF entity 20.

The PCRF entity 20 is configured to authorize the received QoS from the PCEF entity 10 entity.

The PCEF entity 10 is further configured to perform corresponding operations according to the received indication after the access network performs the reduction of the authorized QoS.

The PCRF entity 20 is further configured to deliver an indication to the PCEF entity 30 whether to allow the quality of service QoS to be reduced.

If the PCRF entity 20 indicates that the PCEF entity 10 is allowed to cut the QoS, the PCEF entity 10 indicates that the access network bearer is successfully established, or the reduced QoS is reported to the PCRF entity 20 after the access network revise the authorized QoS.

If the PCRF entity 20 indicates that the PCEF entity 10 does not allow the QoS to be cut, the PCEF entity 10 indicates that the access network bearer establishment fails after the access network revise the authorized QoS.

As shown in FIG. 3, a schematic structural diagram 1 of a PCEF entity according to an embodiment of the present invention includes: an obtaining module 100 and an upper module 110.

The obtaining module 100 is configured to obtain the QoS of the access network after the resource is cut by the access network for the authorized QoS.

The reporting module 110 is configured to report the reduced obtained by the obtaining module 100 to the PCRF entity 20

QoS. Optionally, the upper module 110 may include: a sending module 1100.

The sending module 1100 is configured to carry the reduced QoS in the PCC rule response message or the PCC rule request message, and report the QoS to the PCRF entity 20.

The PCEF entity may further include: a first response module 120.

The first response module 120 is configured to: after receiving the indication of the rejection reduction from the PCRF entity 20, indicating that the access network bearer establishment fails.

The PCEF entity may further include: a second response module 130.

The second response module 130 is configured to initiate a bearer modification process or a bearer setup process according to the modified authorized QoS after receiving the modified authorized QoS from the PCRF entity 20.

The PCEF entity may further include: a third response module 140.

The third response module 140 is configured to: after receiving the modified authorization QoS from the PCRF entity 20, if the modified authorization QoS is the same as the reduced QoS, indicating that the access network bearer is successfully established;

If the modified QoS is inconsistent with the QoS of the previous access network, the bearer of the access network is successfully established, and then the bearer modification request message is sent to the access network according to the modified authorized QoS, and the bearer modification process is initiated; or Indicates that the bearer establishment of the access network fails, and then sends a bearer setup request message to the access network according to the modified authorized QoS, and initiates a bearer setup process.

As shown in FIG. 4, the second schematic structural diagram of the PCEF entity in the embodiment of the present invention includes: a receiving module 300 and a processing module 310.

The receiving module 300 is configured to receive an indication from the PCRF entity 40 whether to allow the quality of service QoS to be reduced.

The processing module 310 is configured to perform corresponding operations according to the indication received by the receiving module 300 after the access network reduces the authorized QoS.

The processing module 310 may further include: a first processing module 3100 and/or a second processing module 3110.

The first processing module 3100 is configured to: if the PCRF entity 40 indicates that the QoS is allowed to be cut, After the QoS of the authorized network is cut, the bearer of the access network is successfully established, or the QoS after the QoS is reported to the PCRF entity 40.

The second processing module 3110 is configured to: if the PCRF entity 40 indicates that the QoS is not allowed to be cut, after the access network reduces the authorized QoS, indicating that the access network bearer establishment fails.

As shown in FIG. 5, the third schematic structure of the PCEF entity in the embodiment of the present invention includes:

500, timing module 510 and indicator module 520.

The reporting module 110 is configured to report the QoS of the access network to the PCRF entity.

For example, the reporting module 110 may include: carrying the reduced QoS in a PCC rule response message or a PCC rule request message, and reporting the result to the PCRF entity.

The timing module 510 is configured to start an authorization timer after the reporting module reports to the PCRF entity. The indication module 520 is configured to indicate that the access network bearer establishment fails if the PCEF does not receive the authorization result from the PCRF after the authorization timer expires.

As shown in FIG. 6, the schematic diagram 1 of the PCRF entity of the embodiment of the present invention includes: a processing module 200 and an authorization module 210.

The processing module 200 is configured to receive the reduced QoS reported from the PCEF entity 10.

The authorization module 210 is configured to authorize the reduced QoS received by the processing module 200. The authorization module 210 performs authorization according to the network policy, and if the reduced QoS conforms to the network policy, the authorization is successful;

If the reduced QoS does not comply with the network policy, the authorization fails.

In the embodiment of the present invention, the network policy can be set as needed, for example, whether the cut QoS can ensure the smooth running of the service in the resource network.

The PCRF entity may further include:

The first execution module 220 is configured to instruct the PCEF entity 10 to reject the reduction after the authorization module 210 fails to authorize the reduced QoS.

The PCRF entity may further include: a second execution module 230, configured to modify the authorization QoS after the authorization module 210 successfully authorizes the reduced QoS, and provide the PCEF entity 10 with For modified authorization QoS.

As shown in FIG. 7, a schematic flowchart of a method for quality of service negotiation according to an embodiment of the present invention includes the following steps:

Step 300: The PCEF entity compares the QoS of the access network to the PCRF entity.

For example, the PCEF entity carries the reduced QoS in the PCC rule response message or the PCC rule request message and reports it to the PCRF entity.

Step 301: The PCRF entity authorizes the reduced QoS.

The PCRF entity performs authorization according to the network policy, and if the reduced QoS complies with the network policy, the authorization succeeds;

Wherein, after step 301, the method further includes:

After the authorization fails, the PCRF entity instructs the PCEF entity to reject the reduction;

The PCEF entity indicates that the access network bearer establishment fails; or

The PCRF entity modifies the authorized QoS after the authorization succeeds, and provides the modified authorization QoS to the PCEF entity;

Then, the PCEF entity initiates a bearer modification process or a bearer setup process according to the modified authorization QoS.

After receiving the modified authorization QoS, the PCEF entity sends a bearer modification request message to the access network according to the modified authorized QoS, if the modified authorization QoS is inconsistent with the QoS of the previous access network. Initiating a bearer modification process; or, instructing the access network bearer to be established, and then sending a bearer setup request message to the access network according to the modified authorized QoS, and initiating a bearer setup process;

If the modified QoS is the same as the QoS after the QoS, the PCEF entity indicates that the bearer of the access network is successfully established, or the PCEF entity may initiate the QoS according to the modified QoS. Load modification process or bearer establishment process.

In the embodiment of the present invention, the network policy can be set as needed, for example, whether the cut QoS can ensure the smooth running of the service, and the like.

It can also be further configured that the modified QoS of the modified PCRF entity cannot be higher than the QoS of the access network after the reduction.

In an embodiment of the present invention, the step 300 and the step 301 may further include:

The PCEF entity starts the authorization timer. After the authorization timer expires, if the authorization result from the PCRF is not received, the PCEF entity indicates that the access network bearer establishment fails.

4 The timeout period of the authorized timer shall comply with the corresponding access network to establish a response timeout. For example, in a WiMAX network, it can be set to the maximum value of the Resource Reservation Response (RR_Rsp) message timer.

The PCEF entity selects whether to perform the resource reduction on the authorized QoS of the access network according to the preset setting, and then reports the reduced QoS to the PCRF entity.

Before the step 300, the method may further include: the PCRF entity instructing the PCEF entity to allow the access network to perform the QoS cut.

If the PCRF entity instructs the PCEF entity to allow the access network to perform the cut, the PCEF entity does not need to be configured according to the preset, as long as the access network performs the resource reduction on the authorized QoS, indicating that the access network bearer is successfully established, or will be cut off. The QoS is reported to the PCRF entity.

If the PCRF entity indicates that the PCEF entity does not allow the access network to perform the cut, the PCEF entity indicates that the access network bearer establishment fails after the access network performs resource reduction on the authorized QoS.

As shown in FIG. 8, the schematic flowchart of the method for quality of service negotiation in the embodiment of the present invention includes the following steps:

Step 400: The PCRF entity indicates whether the PCEF entity allows to cut the quality of service QoS.

Step 401: After the PCEF entity cuts the authorized QoS on the access network, performs a corresponding operation according to the received indication from the PCRF entity.

If the PCRF entity instructs the PCEF entity to allow the QoS to be cut, the PCEF entity is in the access network pair After the authorized QoS is cut, the bearer of the access network is successfully established, or the reduced QoS is reported to the PCRF entity.

If the PCRF entity indicates that the PCEF entity does not allow the QoS to be cut, the PCEF entity indicates that the access network bearer establishment fails after the access network revise the authorized QoS.

As shown in FIG. 9, the schematic flowchart of the method for negotiating service quality in the embodiment of the present invention includes the following steps:

Step 500: The PCEF entity compares the QoS of the access network to the PCRF entity.

Step 501: The PCEF entity starts an authorization timer.

Step 502: After the PCEF entity fails to receive the authorization result from the PCRF, the PCEF entity indicates that the access network bearer establishment fails.

As shown in FIG. 10, a schematic flowchart of a method for service quality negotiation in a pull mode according to an embodiment of the present invention includes the following steps:

Steps a600 ~ a601. After detecting the event that triggers the establishment of the preset stream, the PCEF entity sends a PCC rule request message to the PCRF entity through the PDF.

There are many types of events that trigger the establishment of a preset stream, such as: Mobile Station (MS) to obtain an IP address, and so on.

Step a602: After receiving the PCC rule request message, the PCRF entity performs a policy decision according to the preset QoS profile to generate a PCC rule carrying the authorized QoS.

If the PCRF entity needs user/service subscription information and has not obtained the information before, it interacts with the user/service subscription database to obtain the required information;

The PCRF entity generates a PCC rule carrying the authorized QoS according to the preset flow QoS profile, and/or the user/service subscription information.

In steps a603 to a604, the PCRF entity carries the generated PCC rule in the CCA message and sends it to the PCEF entity through the PDF. Step a605: The PCEF entity saves the received PCC rule, and sends a bearer setup request message to the access network according to the PCC rule.

Step a606: The access network establishes a preset flow bearer according to the bearer setup request message. In the process of establishing the bearer, the access network performs resource reduction on the QoS of the bearer because the resource cannot meet the QoS authorized by the PCRF entity.

Step a607: The access network sends a bearer setup response message carrying the reduced QoS to the PCEF entity.

Steps a608 ~ a609: After receiving the reduced QoS, the PCEF entity sends a PCC rule request message carrying the reduced QoS to the PCRF entity through the PDF.

In step a610, the PCRF entity receives the reduced QoS, and makes a policy decision according to the network policy, and authorizes the reduced QoS to determine whether the access network is allowed to be cut. If yes, go to step a611; otherwise, go to step a617. .

Steps a611 ~ a612, the PCRF entity generates a modified PCC rule in the policy decision process, and the PCC rule carries the modified authorization QoS, and carries the modified authorized QoS in the PCC rule to the PCEF entity through the PDF.

Step a613: After receiving the PCC rule, the PCEF entity checks whether the modified authorization QoS is the same as the reduced QoS. If yes, step a614 is performed; otherwise, step a615 is performed.

Step a614: The PCEF entity indicates that the access network bearer is successfully established, and the process ends.

In step a615~a616, the PCEF entity indicates that the bearer of the access network is successfully established. Then, according to the received modified PCC rule, the bearer modification request message is sent to the access network, and the bearer modification process is initiated, and the access network modifies according to the bearer modification request message. The preset stream is carried and the process ends.

Or, the PCEF entity indicates that the bearer establishment of the access network fails; and then sends a bearer setup request message to the access network according to the received modified PCC rule, and initiates a bearer setup process, and the access network establishes a preset flow according to the bearer setup request message. Host, end the process.

Steps a617 ~ a618, the PCRF entity sends a PCC rule deletion message to the PCEF entity through the PDF, indicating that the PCC rule request is rejected. Step a619: After receiving the PCC rule deletion message, the PCEF entity deletes the corresponding PCC rule, and indicates that the access network fails to be established.

Step a620: After the access network receives the bearer establishment failure indication of the PCEF entity, the established bearer is removed.

The PCEF entity in step a608 may also start the authorization timer after sending the PCC rule request message. Then, after the authorization timer expires, the PCEF entity in step a619, if the PCEF does not receive the authorization result from the PCRF, indicates the access network. The bearer establishment fails, the established bearer is removed, and the process ends.

As shown in FIG. 11, a schematic flowchart 1 of a method for negotiating service quality in a push mode according to an embodiment of the present invention includes the following steps:

Step b600: After detecting the event that triggers the PCC decision, the PCRF entity generates a PCC rule carrying the authorized QoS according to the obtained service information and other information.

There are many events that trigger the PCC decision, such as: Receiving an Authentication Authorization Request (AAR) message sent by the AF, indicating the establishment of a service flow, and the like.

If the PCRF entity needs user/service subscription information and has not obtained it before, it interacts with the user/service subscription database to obtain the required information.

Steps b601 ~ b602: The PCRF entity generates a PCC rule according to the obtained information, and the PCC rule is carried in a Re-Auth-Request (RAR) message and sent to the PCEF entity through the PDF.

The information obtained here includes but is not limited to one or more of the following information: service information, subscription information, and access network information.

Step b603: The PCEF entity saves the received PCC rule, and sends a bearer setup request message to the access network according to the PCC rule.

Step b604: The access network establishes an IP CAN bearer according to the bearer setup request message. In the process of establishing the bearer, the access network performs resource reduction on the QoS of the bearer because the resource cannot meet the QoS authorized by the PCRF entity. Step b605: The access network sends a bearer setup response message carrying the reduced QoS to the PCEF entity.

Steps b606 to b607: After receiving the bearer setup response message, the PCEF entity sends a Re-Auth-Agreement (RAA) response message carrying the reduced QoS to the PCRF entity through the PDF.

Step b608: The PCRF entity receives the reduced QoS, makes a policy decision according to the network policy, and authorizes the reduced QoS, and determines whether the access network is allowed to perform the reduction. If yes, step b609 is performed; otherwise, step b618 is performed. .

Steps b609 ~ b610, the PCRF entity generates a modified PCC rule in the policy decision process, and the PCC rule carries the modified authorization QoS, and carries the modified authorized QoS in the PCC rule to the PCEF entity through the PDF.

Step b611: After receiving the PCC rule, the PCEF entity checks whether the modified authorization QoS is the same as the reduced QoS. If yes, step b612 is performed; otherwise, step b614 is performed.

Steps b612 ~ b613, the PCEF entity indicates that the bearer of the access network is successfully established, and simultaneously returns a response message to the PCRF entity through the PDF, and the process ends.

Steps b614-b615, the PCEF entity indicates that the bearer of the access network is successfully established; and then sends a bearer modification request message to the access network according to the received modified PCC rule, and initiates a bearer modification process. The access network modifies the IP CAN bearer according to the bearer setup modification message and returns the bearer modification result to the PCEF entity.

Or, the PCEF entity indicates that the bearer establishment of the access network fails; and then sends a bearer setup request message to the access network according to the received modified PCC rule, and initiates a bearer setup process. The access network establishes an IP CAN bearer according to the bearer setup request message, and returns a bearer setup result to the PCEF entity.

Steps b616 ~ b617, the PCEF entity returns a response message to the PCRF entity through the PDF, and ends the process.

Steps b618 ~ b619, the PCRF entity sends a PCC rule deletion message to the PCEF entity through the PDF. Step b620: The PCEF entity deletes the corresponding PCC rule, indicates that the access network bearer establishment fails, and returns a response message to the PCRF entity through the PDF.

Step b621: After the access network receives the bearer establishment failure indication of the PCEF entity, the access network removes the established bearer.

The PCEF entity in step b606 may also start the authorization timer after sending the PCC rule request message, and the PCEF entity does not receive the authorization result from the PCRF after the authorization timer expires in step b620, indicating that the access network bearer is established. Failed, ending the process.

As shown in FIG. 12, the schematic flowchart of the method for negotiating service quality negotiation in the push mode of the embodiment of the present invention includes the following steps:

The steps c600~c605 are the same as the steps b600~b605 in FIG. 11, and are not described again. Steps c606 ~ c607: After receiving the bearer setup response message, the PCEF entity sends a PCC rule response message to the PCRF entity through the PDF.

Steps c608 ~ c609, the PCEF entity sends a PCC rule request message carrying the reduced QoS to the PCRF entity through the PDF.

Step c610: The PCRF entity receives the reduced QoS, and makes a policy decision according to the network policy, and authorizes the reduced QoS to determine whether the access network is allowed to be cut. If yes, go to step c611; otherwise, go to step c620. .

Steps c611 ~ c612. The PCRF entity generates a modified PCC rule in the policy decision process. The PCC rule carries the modified authorization QoS, and the modified authorization QoS is carried in the PCC rule to the PCEF entity through the PDF.

Step c613: After receiving the PCC rule, the PCEF entity checks whether the modified authorization QoS is the same as the reduced QoS. If yes, step c614 is performed; otherwise, step c616 is performed.

Steps c614 ~ c615, the PCEF entity indicates that the bearer of the access network is successfully established, and simultaneously returns a response message to the PCRF entity through the PDF, and the process ends.

Steps c616~c617: The PCEF entity indicates that the bearer of the access network is successfully established. Then, according to the received modified PCC rule, the bearer modification request message is sent to the access network, and the bearer modification process is initiated. Connect The access network modifies the IP CAN bearer according to the bearer modification request message, and returns the bearer modification result to the PCEF entity.

Steps c618 ~ c619, the PCEF entity returns a response message to the PCRF entity through the PDF, and ends the process.

Steps c620 ~ c621, the PCRF entity sends a PCC rule deletion message to the PCEF entity through the PDF.

Step c622: The PCEF entity deletes the corresponding PCC rule, indicates that the access network bearer establishment fails, and returns a response message to the PCRF entity through the PDF.

Step c623: After the access network receives the bearer setup failure indication of the PCEF entity, the access network removes the established bearer.

The PCEF entity may also start the authorization timer after the PCC rule request message is sent in step c608. After the PCEF entity times out in the step c622, the PCEF does not receive the authorization result from the PCRF, indicating the access network bearer. The establishment fails, indicating that the established bearer is removed, and the process ends.

In the processes described in FIG. 10, FIG. 11 and FIG. 12, in the case that the PCRF entity controls the bearer, the authorized QoS generated in the policy decision process is not carried in the PCC rule, but when the PCRF entity provides the PCC rule to the PCEF entity, Authorized QoS is sent to the PCEF entity along with the PCC rules.

The PCC rules in Figure 10, 11, and 12 are sent in a message on the Gx interface. For example: When the Gx interface uses the DIAMETER protocol, the PCC rules are carried in the CCA message and the RAR message; when the Gx interface uses other protocols. The PCC rules will be sent in the corresponding message specified in the protocol.

The PCEF entity in Figures 10, 11 and 12 determines whether the PCEF entity depends on the policy of the PCEF entity after the QoS is reduced by the access network. So in Figures 10, 11 and 12, the PCRF entity also The indication may be sent to the PCEF entity whether the access network is allowed to perform resource reduction. The indication may be provided to the PCEF entity when the PCRF entity provides the PCC rule to the PCEF entity.

If the PCRF entity indicates that the PCEF entity allows the access network to perform resource reduction and requires PCEF entity feedback, it indicates that the PCEF entity must report to the PCRF entity after the access network reduces the QoS; if the PCRF entity indicates that the PCEF entity does not allow the access network If the QoS is reduced on the access network, the PCEF entity directly indicates that the access network bearer fails to be established, and the previously saved PCC rule is deleted, and the PCC rule failure message is returned to the PCRF entity.

If the PCRF entity indicates that the PCEF entity allows the access network to perform resource reduction and does not require PCEF entity feedback, it indicates that the PCEF entity does not need to report to the PCRF entity after the access network reduces the QoS, and directly indicates that the access network bearer is successfully established.

Resource reduction may occur when the bearer process involves QoS operations. Therefore, the resource reduction may occur during the modification process, and the subsequent QoS negotiation process is similar to the processing in the foregoing embodiments, and details are not described herein again.

It can be seen from the foregoing embodiment that: the PCEF entity in the embodiment of the present invention reports the QoS of the access network to the policy charging rule function PCRF entity; the PCRF entity authorizes the reduced QoS, thereby implementing The QoS negotiation is performed under the PCC structure, and the access network bearer processing flow in the PCC structure is further improved.

On the other hand, an embodiment of the present invention provides a method for service quality negotiation. The method process is as shown in FIG. 13 and includes:

Step 901: First, the Anchor SFA (anchoring service flow authorization function) receives the QoS service flow attribute of the user, and the Anchor SFA sends the corresponding QoS service flow attribute to the RR-Req (Resource Reservation Request) message. Give Serving SFA (Service Service Flow Authorization Function) to request the establishment of a service flow.

Step 902: The Serving SFA parses and obtains the QoS service flow attribute content according to the RR_Req message received from the Anchor SFA, and sends a Path_Reg_Req (Path Registration Request) message to the SFM (Service Flow Management Function) for requesting to establish data. Channel, at the same time The content of the QoS service flow attribute received by the user in the RR-Req is transmitted to the SFM in the Path_Reg_Req.

Step 903: After receiving the Path_Reg_Req message, the SFM determines whether the QoS service flow can be accepted according to the QoS service flow attribute content carried in the Path_Reg_Req message and the air interface resource owned by the SFM. request.

Step 904: If the SFM accepts the QoS service flow request, send a DSA/DSC Request (Dynamic Service Addition/Dynamic Service Change Request) message to the MS to request to establish an air interface connection.

Step 905: After receiving the SFM request, the MS needs to confirm whether the MS has the capability to establish a corresponding QoS service flow for the user. If the MS determines that it has the capability to establish a corresponding QoS service flow for the user and needs resources in the QoS service flow attribute. In the case of the reduction, the resource reduction judgment result is sent to the SFM in the DSA/DSC Response (Dynamic Service Addition/Dynamic Service Change Response).

Step 906: The SFM establishes a QoS service flow attribute reduction negotiation result for the user, including the resource reduction judgment result, and the bearer is sent to the Serving SFA in the Path-Reg-Rsp (Path Registration Response).

Step 907: The Serving SFA carries the QoS service flow attribute reduction negotiation result in an RR Rs (Resource Reservation Response) message and sends the result to the Anchor SFA.

Step 908: When the Anchor SFA is not the QoS final authorization function entity, the Anchor SFA feeds back the QoS service flow attribute reduction result negotiated by the SFM and the air interface MS to other QoS final authorization function entities in the network, and obtains other QoS final authorization function entities. Whether the ruling is authorized or not, Anchor SFA will feedback the feedback to the Serving SFA in the RR-Ack (Resource Reservation Acknowledge). When the Anchor SFA is the QoS final authorization function entity, the Anchor SFA decides whether to accept the QoS service flow attribute reduction result, and the judgment result (that is, whether the authorized feedback result is obtained) Feedback to Serving SFA in RR-Ack. The QoS final authorization function entity may be a Policy Control and Charging Rules Function (PCRF) for: policy control decision and flow rate based control.

Step 909: The Serving SFA receives the result of the reduction in the RR-Ack. If the reduction authorization result is "Success", the Serving SFA sends a Path-Reg-Ack (Path Registration Acknowledge) to agree to the reduction. Sending the SFM, the SFM uses the "Success" as the QoS service flow attribute to finally reduce the negotiation result, and thereby release the reduced resources, and then feed the result back to the MS to establish an air interface data path connection. If the result of the reduction authorization in RR-Ack is "Fail", that is, the reduction is not agreed, the Serving SFA sends a Path-Reg-Ack to send the SFM with the result of the disagreement, and the SFM uses the "Failure" as the QoS service flow attribute to finally negotiate the reduction. As a result, the Data Path resource is released, and the result is fed back to the MS. If the QoS reduction negotiation fails, the air interface data path connection will not be established.

In the above process, if the MS is in a non-roaming state, the Anchor SFA can replace the function performed by the Serving SFA, that is, the Serving SFA does not exist. At this time, the Anchor SFA directly sends the judgment result to the SFM.

In order to implement the solution in the foregoing embodiment, the following modifications may be made on the basis of the prior art: Adding the return value carrying the cut operation in the Path_Reg_Ack and the RR_Ack, that is, whether the QoS final authorization function entity determines whether the authorization is authorized. Feedback results.

Adjusting the order of the two messages Path-Reg-Ack and RR-Ack, the Anchor SFA sends the RR-Ack message to the Serving SFA, and then sends the Path-Reg-Ack to the SFM, so that the MS, The SFM and the SFA can activate or delete the bearer resources according to the result of the authorization of the return value of the cut operation.

The specific plan is as follows:

Add "Result" to (8) RR_Ack as follows: IE M/O Notes (remarks)

( Information ( Mandatory

Element , information /Optional, must

Item) Selected / Optional

of)

MS Info M

(MS

Information, MS

Information)

>SF Info M

( SF

Information , SF

Information)

»SFID M SFID as defined on Rl . (This parameter is defined in (Service WiMAX NWG Version 1 SFID)

Flow Identity, Yueliang

Service flow identification)

> Result 0 This is allowed indicates the results of

(Result) Reduced Resource process if "QoS Parameters" was set at the corresponding RR Req message.

It shall be set to indicate "success" if Anchor

SFA indicated to allow reduce resource.

Otherwise, it should indicate "failure". (This parameter is allowed to indicate the result of the resource clipping operation when the QoS parameter is set in the resource reservation request message. If the anchor service flow authorization function indicates that resource clipping is allowed, the parameter setting "Success"; otherwise, the parameter is set to "Failed.")

Add the "Reduced Resource Result" number in (7) Path_Req_Ack as follows:

> Result 0 This is allowed indicates the results of

Reduced Resource process if "Result" was set at the corresponding RR Ack message. It shall be set to indicate "success" if Anchor SFA indicated to allow reduce resource. Otherwise, it should indicate "failure". This parameter is allowed to indicate the result of the resource clipping operation when the QoS parameter is set. If the anchor service flow authorization function indicates that resource clipping is allowed, the parameter is set to "success"; otherwise, the parameter is set to "failed."

The Result" is defined as follows:

The above table is used to illustrate how the implementation is specifically implemented. However, the embodiment of the present invention does not limit the use of this method. Other definitions may be used as long as one of the RR_Ack and/or Path_Reg_Ack messages is added. It is enough to identify the parameters of the resource cropping result.

In the technical solution provided by the embodiment of the present invention, when the QoS service flow attribute of the user needs to be reduced, the SFM reports the negotiation result of the QoS service flow attribute negotiation negotiated by the user to the Anchor SFA. Determining, by the Anchor SFA or other QoS final authorization function entity that is the QoS final authorization function entity, whether to authorize the QoS service flow attribute reduction negotiation result and feedback the decision condition to the SFM, and the SFM performs the determination according to the judgment situation. Subsequent processing, which avoids the prior art in the case of QoS service flow attribute reduction, the network side QoS final authorization function entity does not participate in the negotiation of the QoS service flow attribute reduction, and cannot determine whether to allow the reduction defect, guarantee The QoS final authorization function entity can control the network resources and facilitate network resource management.

In addition to the above methods, the second embodiment of the present invention provides another method for negotiating quality of service, and the RR-REQ message can be used to carry a scheme for reducing information.

The QoS final authorization function entity (such as Anchor SFA) determines the QoS service flow attribute that it is allowed to cut, and adds one of the QoS parameters carried in the RR-Req message to one or more QoS parameters or all QoS parameters. That is, the QoS information includes, for example, whether to allow the reduction and further including the range of the QoS service flow attribute reduction allowed by the QoS service flow, or directly carrying the allowed reduction range. When a service flow is established in the network, each executing entity refers to the cut range allowed by the received QoS according to its own resource condition, and establishes a service flow within the allowed range.

The QoS information added in the description of each QoS attribute includes not limited to the following information:

1. Whether the QoS attribute allows for reduction;

2. If the reduction is allowed, what is the maximum QoS value allowed by this QoS attribute;

3. If the reduction is allowed, what is the minimum QoS value allowed by this QoS attribute;

4. If the cut is not allowed, what is the value of this QoS attribute.

When the QoS service flow attribute is reduced, the SFM follows the QoS information carried in the RR-Req message to perform the cut judgment, and determines the QoS service flow attribute to finally reduce the negotiation result. After the reduction is completed, the final reduction negotiation results are placed in the Path-Reg-Rsp and RR-Rsp feedback to the Anchor SFA. The method flow of the specific implementation scheme is as shown in FIG. 14 and includes:

Step 1001: First, the Anchor SFA receives the QoS service flow attribute determined by the QoS final authorization function entity, and the Anchor SFA allows the QoS final authorization function entity to allow the reduction. The QoS service flow attribute (ie, the range indicating that the QoS service flow attribute is allowed to be cut) is carried in the RR-Req QoS parameter and sent to the Serving SFA for requesting establishment of the service flow.

In the embodiment of the present invention, the QoS final authorization function entity may be the Anchor SFA, or other network entities, such as a PCRF, an AAA Server, or the like. If the Anchor SFA itself is the QoS final authorization function entity, the Anchor SFA determines which QoS service flow attributes can be reduced and determines the reduction range after receiving the QoS service flow attributes of the user, and the reduced information is carried in the RR-Req. The QoS parameters are sent to the Serving SFA for requesting the establishment of a service flow.

Step 1002: The Serving SFA parses and obtains the QoS service flow attribute content according to the RR_Req message received from the Anchor SFA, and sends a Path_Reg_Req message to the SFM to request to establish a data channel, and at the same time, the QoS final authorization in the RR_Req The functional entity allows the reduced QoS service flow attribute content to be carried in the Path_Reg_Req message and transmitted to the SFM.

Step 1003: After receiving the Path_Reg_Req message, the SFM determines whether to accept the QoS service flow request according to the QoS service flow attribute carried in the Path_Reg_Req message and the air interface resource in the SFM.

Step 1004: If the SFM accepts the QoS service flow request, send a DSA/DSC Request to the MS to request to establish an air interface connection.

Step 1005: After receiving the request of the SFM, the MS needs to confirm whether the MS has the capability to establish a corresponding QoS service flow for the user, and if the QoS service flow attribute needs to be reduced, the reduction judgment result is sent in the DSA/DSC Response. Give SFM.

Step 1006: The SFM will perform the cut judgment according to the QoS information carried in the RR-Req message, and establish a final cut negotiation result of the QoS service flow attribute for the user (that is, the final decision of the QoS service flow attribute is reduced), and the SFM is used. Path—Reg—The Rsp sends the determined QoS service flow attribute final reduction negotiation result to the Serving SFA.

Step 1007: The Serving SFA sends the final QoS negotiation result of the QoS service flow attribute to the Anchor SFA by using the RR Rs.

Step 1008: The Serving SFA returns a Path_Reg_Ack message to the SFM. Step 1009: The Anchor SFA returns an RR_Ack message to the Serving SFA.

Subsequent Path-Reg-Ack messages and RR-Ack messages can be the same as in the prior art, or new return values can be added and sequenced according to other requirements.

The SFM determines the QoS service flow attribute and finally reduces the negotiation result according to the QoS service flow attribute determined by the QoS final authorization function entity. According to such an authorization feedback mechanism, when the QoS resources of the user need to be reduced, after the SFM and the QoS final authorization function entity negotiate, the negotiated authorization result is fed back to the SFM, and finally whether the scope is cut and reduced, and the QoS service flow is determined. Operation processing ensures that the QoS final authorization function entity can control whether to allow the reduction, and facilitate network resource management.

The third embodiment of the present invention is a QoS final authorization function entity device, and the structure thereof is as shown in FIG.

Determining module 200: for determining a QoS service flow attribute that can be reduced;

The sending module 300 is configured to send, to the SFM, the QoS service flow attribute determined by the determining module 200. Further, as shown in FIG. 16, the determining module 200 includes:

The receiving module 210 is configured to receive a QoS service flow attribute reduction negotiation result from the SFM. The first determining submodule 211 is configured to perform a decision operation on the QoS service flow attribute reduction negotiation result received by the receiving module 210.

The sending module 300 includes:

The first sending submodule 310 is configured to send the determination result of the first determining submodule 211 to the SFM.

As shown in FIG. 17, the determining module 200 includes:

The second determining submodule 220 is configured to determine a QoS service flow attribute that is allowed to be cut in the QoS service flow attribute;

The sending module 300 includes:

The second sending submodule 320 is configured to send the QoS service flow attribute determined by the second determining submodule 220 to the SFM. The fourth embodiment of the present invention is a WiMAX system, and its structure is as shown in FIG. 18, including:

a QoS final authorization function entity 1000, configured to determine a QoS service flow attribute that can be reduced; and send the QoS service flow attribute that is determined to be configurable;

The SFM 2000 is configured to determine, according to the QoS service flow attribute, the QoS service flow attribute to finally reduce the negotiation result; and perform the QoS service flow establishment operation according to the final reduction negotiation result.

The step of determining, by the QoS final authorization function entity, the QoS service flow attributes that can be reduced is specifically:

The QoS final authorization function entity 1000 receives the QoS service flow attribute reduction negotiation result from the SFM 2000; the QoS final authorization function entity determines the reduction negotiation result from the SFM; the QoS final authorization function entity 1000 determines the QoS that can be reduced The step of sending the service flow attribute to the SFM 2000 is specifically: the QoS final authorization function entity sends the judgment result to the SFM;

The SFM 2000 determines the QoS service flow attribute based on the QoS service flow attribute sent by the QoS final authorization function entity 1000. The final result of the negotiation is as follows: The SFM uses the decision result of the QoS final authorization function entity as the QoS service flow attribute to finally reduce the negotiation result.

A person skilled in the art can understand that all or part of the process of implementing the above embodiments can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. When executed, the flow of an embodiment of the methods as described above may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

The present invention is not limited to the sequence of steps provided in the foregoing method embodiments, and those skilled in the art can easily realize other steps in the steps provided by the embodiments of the present invention, so that the same objects as the present invention can be achieved.

It should be understood by those skilled in the art that the various functional entities described in the foregoing embodiments may exist in different physical entities or may exist in the same physical entity, and the present invention does not limit the present invention. Set. When any two or more entities are located in the same physical entity, the interaction between them is internally obvious without departing from the spirit of the invention. The spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and the modifications of the invention

Claims

Claim

A method for negotiating quality of service, characterized in that the method comprises:

The policy-based charging function is performed by the PCEF entity to report the QoS of the QoS to the policy-based charging rule function, so that the PCRF entity authorizes the reduced QoS.

2. The method of QoS negotiation according to claim 1, further comprising: when the authorization fails, the PCRF entity instructing the PCEF entity to reject the cut; the PCEF entity instructing the access The network bearer establishment failed.

The method for QoS negotiation according to claim 1, further comprising: when the authorization is successful, the PCRF entity modifies the authorized QoS, and provides the modified authorization QoS to the PCEF entity;

Determining, by the PCEF entity, whether the modified authorized QoS is consistent with the reduced QoS according to the modified authorized QoS;

If they are consistent, the PCEF entity indicates that the access network bearer is successfully established; if not, the PCEF entity initiates an access network bearer modification process or an access network bearer setup process.

The method for QoS negotiation according to claim 1, further comprising: reporting, by the policy charging execution function, the PCEF entity reduces the quality of service QoS of the access network to the policy charging rule function PCRF entity After that, the authorization timer is started;

If the PCEF does not receive the authorization result from the PCRF after the authorization timer expires, the PCEF entity indicates that the access network bearer establishment fails.

The method for QoS negotiation according to claim 1, wherein the policy charging execution function PCEF entity performs the step of reporting the quality of service QoS of the access network to the policy charging rule function PCRF entity. Also includes:

Policy charging rule function The PCRF entity sends a policy to the policy charging execution function. The PCEF entity sends an indication of whether to cut the quality of service QoS.

If the PCRF entity instructs the PCEF entity to allow the QoS to be cut, then the PCEF entity is in the access network After the QoS of the authorized network is reduced, the QoS of the access network is reported to the PCRF entity; if the PCRF entity indicates that the PCEF entity does not allow the QoS to be cut, the PCEF entity reduces the authorized QoS in the access network. Indicates that the access network bearer establishment fails.

6. A system for negotiating quality of service, characterized in that the system comprises:

The policy-based charging execution function, the PCEF entity (10), is configured to report the quality of service QoS of the access network to the policy charging rule function PCRF entity;

The PCRF entity (20) is configured to authorize the reduced QoS.

The system for QoS negotiation according to claim 6, wherein the system comprises: a policy charging rule function PCRF entity (20), and is further configured to send a policy to the policy charging execution function PCEF entity whether to allow the reduction An indication of quality of service QoS;

The PCEF entity (10) is also used to perform corresponding operations according to the indication of the PCRF entity.

8. The system of quality of service negotiation according to claim 6, wherein:

The step of performing the corresponding operation by the PCEF entity (10) according to the indication of the PCRF entity is specifically: if the PCRF entity instructs the PCEF entity to allow the QoS to be cut, the PCEF entity after the access network revise the authorized QoS, The network-reduced QoS is reported to the PCRF entity. If the PCRF entity indicates that the PCEF entity does not allow the QoS to be cut, the PCEF entity indicates that the access network bearer establishment fails after the access network revise the authorized QoS. .

A PCEF entity, wherein the PCEF entity comprises: an obtaining module (100), configured to obtain a quality of service QoS after the access network is cut;

The reporting module (110) is configured to report the reduced version to the policy charging execution function PCRF entity

QoS.

10. The policy charging execution function PCEF entity according to claim 9, wherein the PCEF entity further comprises at least one of the following modules:

The first response module (120) is configured to: after receiving the indication of the rejection of the PCRF entity, indicating that the access network bearer establishment fails;

a second response module (130) for receiving a modified authorization from the PCRF entity After the QoS, if the modified authorization QoS is inconsistent with the reduced QoS, the bearer modification process or the bearer establishment process is initiated;

a third response module (140), configured to: after receiving the modified authorization QoS from the PCRF entity, if the modified authorization QoS is consistent with the reduced QoS, indicating an access network bearer Established successfully.

11. The policy charging execution function PCEF entity of claim 9, wherein the PCEF entity further comprises:

a receiving module (300), configured to receive an indication from the policy charging rule function PCRF entity whether to cut the quality of service QoS;

The indication module (310) is configured to: if the PCRF entity indicates that the QoS is not allowed to be cut, after the access network reduces the authorized QoS, indicating that the access network bearer establishment fails;

The upper module (110) is further configured to: if the PCRF entity indicates that the QoS is allowed to be cut, the PCEF entity reports the QoS of the access network to the PCRF entity after the access network revise the authorized QoS. .

12. The policy charging execution function PCEF entity of claim 9, wherein the PCEF entity further comprises:

a timing module (510), configured to: after the reporting module (110) reports the PCRF entity, start an authorization timer;

The indication module (520) is configured to: after the authorization timer expires, if the PCEF does not receive the authorization result from the PCRF, indicating that the access network bearer establishment fails.

A policy-based charging rule function, the PCRF entity, the PCRF entity, comprising: a processing module (200), configured to receive the reduced QoS reported by the PCEF entity from the policy charging execution function;

The authorization module (210) is configured to authorize the reduced QoS.

14. The policy charging rule function PCRF entity of claim 13, wherein the PCRF entity further comprises: a first execution module (220), configured to: after the authorization fails, instruct the PCEF entity to refuse to cut and/or

The second execution module (230) is configured to: after the authorization is successful, modify the authorized QoS, and provide the modified authorization QoS to the PCEF entity.

15. A method of service quality negotiation, characterized in that:

The QoS final authorization function entity sends the determined QoS service flow attribute to the service flow management entity SFM, so that the SFM determines the QoS service flow attribute according to the QoS service flow attribute, and finally reduces the negotiation result, and according to the final reduction negotiation result Perform QoS service flow establishment operations.

16. The method of quality of service negotiation of claim 15 wherein:

The step of determining, by the QoS final authorization function entity, the QoS service flow attribute that can be reduced is specifically: the QoS final authorization function entity receives the QoS service flow attribute reduction negotiation result from the SFM;

The QoS final authorization function entity determines the result of the reduction negotiation from the SFM, and generates a judgment result;

The step of the QoS final authorization function entity sending the QoS service flow attribute determined to be severable to the SFM is specifically:

The QoS final authorization function entity sends the decision result to the SFM;

The SFM determines the QoS service flow attribute according to the QoS service flow attribute sent by the QoS final authorization function entity. The final reduction negotiation result is specifically:

The SFM uses the decision result of the QoS final authorization function entity as the QoS service flow attribute to finally reduce the negotiation result.

17. The method of quality of service negotiation of claim 16 wherein:

The QoS final authorization function entity sends the decision result to the SFM step as follows:

The QoS final authorization function entity sends the decision result to the SFM through the Anchor SFA;

Or, the QoS final authorization function entity is Anchor SFA, and the Anchor SFA sends the judgment result to the SFM.

The method of claim 15 as claimed in claim 15, further comprising: if the result of the decision is to agree to the cut result sent by the SFM, the SFM releases the cut resource, and then returns the result to the MS. , establishing an air interface data path connection;

If the result of the decision is that the SFM does not agree with the reduction result sent by the SFM, the SFM releases the Data Path resource and feeds the result back to the MS. If the QoS reduction negotiation fails, the air interface data path connection will not be established.

19. A QoS final authorization function entity device, comprising:

Determining module (200)·· for determining a QoS service flow attribute that can be reduced;

The sending module (300) is configured to send the QoS service flow attribute determined by the determining module to the SFM.

The QoS final authorization function entity device according to claim 19, wherein the determining module (200) comprises:

a receiving module (210): configured to receive a QoS service flow attribute reduction negotiation result from the SFM; a first determining sub-module (210): configured to perform a decision operation on the QoS service flow attribute reduction negotiation result received by the receiving module;

The sending module (300) includes:

The first sending submodule (310) is configured to send the determination result of the first determining submodule to the SFM.

21. A WiMAX system, comprising:

a QoS final authorization function entity (1000), configured to determine a QoS service flow attribute that can be reduced; and send the QoS service flow attribute that is determined to be configurable;

The SFM (2000) is configured to determine, according to the QoS service flow attribute, the QoS service flow attribute to finally reduce the negotiation result; and perform the QoS service flow establishment operation according to the final reduction negotiation result.