Method, device, and system for controlling quality of service

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Application No. PCT/CN2012/070672, filed on Jan. 20, 2012, which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

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

BACKGROUND

With the rapid popularization of intelligent mobile terminals and the development of the mobile Internet, higher requirements and technical challenges are imposed on a network of an operator, which mainly involve aspects such as bandwidth on demand, assurance of quality of service, and service experience improvement. In this case, it is required that the network of the operator needs to have a service differentiation capability. That is, the network of the operator may differentiate priorities according to subscribers and service demands, treat the subscribers and the service demands in a differentiated manner, and provide the subscribers with services that match subscription of the subscribers.

A quality of service (Quality of Service, QoS) technology is a main means to implement the service differentiation capability of the network currently, and in the field of mobile communication, a QoS model defined by the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) organization is mainly adopted. However, a solution based on the model is limited to a certain extent in actual deployment, and cannot fully meet a requirement of an operator for deploying a QoS differentiated service.

For services within a same bearer, a radio access network node cannot differentiate priorities of the services. As a result, a service with a high priority cannot be forwarded preferentially, disordered packet loss occurs when an air interface is overloaded, and end-to-end differentiated processing of a service flow, namely, differentiated processing of a service flow from a service end to a user equipment end, cannot be implemented, so that differentiated experiences cannot be provided for different levels of subscribers and different types of services.

SUMMARY

In view of this, embodiments of the present invention provide a method, a device, and a system for controlling quality of service, which can implement end-to-end differentiated processing of a service flow, provide differentiated experiences for different levels of subscribers and different types of services, and improve utilization efficiency of radio resources.

To solve the foregoing problems, the embodiments of the present invention provide the following technical solutions:

In one aspect, an embodiment of the present invention provides a method for controlling quality of service, where the method includes:

obtaining, by a policy and charging enforcement function PCEF entity, a service flow priority identifier FPI of a downlink data packet, where the FPI is used to indicate a priority of a service flow to which the downlink data packet belongs;

carrying, by the PCEF, the FPI in the downlink data packet; and

sending, by the PCEF, the downlink data packet to a base station, so that the base station sends the downlink data packet to a user equipment UE according to the FPI.

In another aspect, an embodiment of the present invention provides another method for controlling quality of service, where the method includes:

receiving, by a base station, a downlink data packet, where the downlink data packet includes a service flow priority identifier FPI, and the FPI is used to indicate a priority of a service flow to which the downlink data packet belongs; and

sending, by the base station, the downlink data packet to a user equipment UE according to the FPI.

In still another aspect, an embodiment of the present invention provides a policy and charging enforcement function entity, including: an obtaining unit, a marking unit, and a sending unit, where

the obtaining unit is configured to obtain a service flow priority identifier FPI of a downlink data packet, where the FPI is used to indicate a priority of a service flow to which the downlink data packet belongs;

the marking unit is configured to carry the FPI in the downlink data packet; and

the sending unit is configured to send the downlink data packet to a base station, so that the base station sends the downlink data packet to a user equipment UE according to weight information corresponding to the FPI.

In yet another aspect, an embodiment of the present invention provides a policy and charging rules function entity, including:

an obtaining unit, configured to obtain a service flow priority identifier FPI according to a service type of a service to which a downlink data packet belongs and at least one of the following items: a service priority of the service to which the downlink data packet belongs, a subscriber accumulated usage level of the service to which the downlink data packet belongs, a subscriber level of the service to which the downlink data packet belongs, and a type of a UE receiving the downlink data packet, where the FPI is used to indicate a priority of a service flow to which the downlink data packet belongs; and

a sending unit, configured to send the FPI to a policy and charging enforcement function entity.

In yet another aspect, an embodiment of the present invention provides a base station, including a receiving unit and a sending unit, where

the receiving unit is configured to receive a downlink data packet, where the downlink data packet includes a service flow priority identifier FPI, and the FPI is used to indicate a priority of a service flow to which the downlink data packet belongs; and

the sending unit is configured to send the downlink data packet to a user equipment UE according to the FPI.

In yet another aspect, an embodiment of the present invention provides a system for controlling quality of service, where the system includes the policy and charging enforcement function entity and the base station.

By adopting the method, the device, and the system according to the embodiments of the present invention, a priority of a service flow is indicated by using a one-dimensional scalar FPI, and sending of a downlink data packet of the service flow is performed according to the FPI through a base station; in this way, end-to-end control of quality of service based on service flow granularity is implemented, end-to-end differentiated processing can be performed on the service flow, differentiated service experiences can be provided for different levels of subscribers and different types of services, and utilization efficiency of radio resources can be effectively improved.

BRIEF DESCRIPTION OF THE DRAWINGS

To describe the technical solutions in the embodiments of the present invention more clearly, the following briefly introduces accompanying drawings required for describing the embodiments. Apparently, the accompanying drawings in the following description are merely some embodiments of the present invention, and a person of ordinary skill in the art may further obtain other drawings according to these accompanying drawings without creative efforts.

<figref idref="DRAWINGS">FIG. 1</figref> is a schematic flowchart of a method for controlling quality of service according to an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 2</figref> is a schematic flowchart of another method for controlling quality of service according to an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 3</figref> is a schematic flowchart of still another method for controlling quality of service according to an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 4</figref> is a schematic structural diagram of a policy and charging enforcement function entity according to an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 5</figref> is a schematic structural diagram of an obtaining unit of the policy and charging enforcement function entity according to the embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 6</figref> is a schematic structural diagram of the obtaining unit of the policy and charging enforcement function entity according to the embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 7</figref> is a schematic structural diagram of a marking unit of the policy and charging enforcement function entity according to the embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 8</figref> is a schematic structural diagram of a policy and charging rules function entity according to an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 9</figref> is a schematic structural diagram of a base station according to an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 10</figref> is a schematic structural diagram of a sending unit of the base station according to the embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 11</figref> is a schematic structural diagram of a sending unit of another base station according to an embodiment of the present invention; and

<figref idref="DRAWINGS">FIG. 12</figref> is a schematic structural diagram of a system for controlling quality of service according to an embodiment of the present invention.

DETAILED DESCRIPTION

The following clearly describes the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the embodiments to be described are merely part rather than all of the embodiments of the present invention. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

In the embodiments of the present invention, a service refers to a data service based on a radio network bearer. Exemplarily, the service may be web page browsing, a video service, a voice service, an online game, file downloading, or the like.

In the embodiments of the present invention, a service flow refers to a data flow generated in a process of performing a service. In a same service, there may be different service flows for different subscribers, and there may also be different service flows when a same subscriber uses different services. The service flow is formed by data packets, and the data packets maybe classified into an uplink data packet and a downlink data packet.

In the embodiments of the present invention, a service flow priority identifier (service Flow Priority Identifier, FPI) is a one-dimensional scalar for indicating a priority of a service flow.

In the embodiments of the present invention, a policy and charging enforcement function (Policy and Charging Enforcement Function, PCEF) entity may be a data gateway or an external processing device. The data gateway may be a packet data network gateway (Packet Data Network Gateway, PGW), and may also be a gateway GPRS support node (Gateway GPRS Support Node, GGSN); and the external processing device may generally be a device having capabilities of deep packet inspection (Deep packet inspection, DPI) and obtaining and executing a policy and charging control (Policy and Charging Control, PCC) policy.

In the embodiments of the present invention, a policy and charging rules function (Policy and Charging Rule Function, PCRF) entity has a capability of generating a PCC rule.

In the embodiments of the present invention, a base station is a broad concept. The base station may be a radio network controller (Radio Network Controller, RNC), a base station controller (Base Station Controller, BSC), or an evolved Node B (evolved Node B, eNodeB).

In the embodiments of the present invention, UEs may be distributed in an entire radio network, and each UE may be static or mobile. The UE may be referred to as a terminal (terminal), a mobile station (mobile station), a subscriber unit (subscriber unit), a station (station), or the like. The UE may also be a cellular phone (cellular phone), a personal digital assistant (personal digital assistant, PDA), a wireless modem (modem), a wireless communication device, a handheld (handheld) device, a laptop computer (laptop computer), a cordless phone (cordless phone), a wireless local loop (wireless local loop, WLL) station, or the like.

In the embodiments of the present invention, an intermediate node refers to a node that a service flow passes through and is located between a base station and a PCEF. Exemplarily, the intermediate node may be a serving gateway (Serving Gateway, SGW) or a serving GPRS support node (Serving GPRS Support Node, SGSN).

An embodiment of the present invention provides a method for controlling quality of service. As shown in <figref idref="DRAWINGS">FIG. 1</figref>, the method includes:

<b>101</b>: A PCEF obtains an FPI of a downlink data packet.

Exemplarily, the PCEF may obtain the FPI, that is, obtain the FPI of the downlink data packet, according to a service type of a service to which the downlink data packet belongs and at least one of the following parameters that may be used for quality control: a service priority of the service to which the downlink data packet belongs, a subscriber accumulated usage level of the service to which the downlink data packet belongs, a subscriber level of the service to which the downlink data packet belongs, and a type of a UE receiving the downlink data packet.

Exemplarily, the PCEF may obtain the FPI of the downlink data packet by receiving the FPI of the downlink data packet from a PCRF. The FPI sent by the PCRF is obtained by the PCRF according to a service type of a service to which the downlink data packet belongs and at least one of the following parameters that may be used for quality control: a service priority of the service to which the downlink data packet belongs, a subscriber accumulated usage level of the service to which the downlink data packet belongs, a subscriber level of the service to which the downlink data packet belongs, and a type of a UE receiving the downlink data packet.

<b>102</b>: The PCEF carries the FPI in the downlink data packet.

Exemplarily, the PCEF may carry the FPI in a tunnel encapsulation header of the downlink data packet.

Exemplarily, the PCEF may carry the FPI in an IP packet header of the downlink data packet.

<b>103</b>: The PCEF sends the downlink data packet to a base station, so that the base station sends the downlink data packet to a UE according to the FPI.

Optionally, during a process in which the PCEF sends the data packet to the UE, an intermediate node receiving the data packet may also send, according to the FPI, the downlink data packet to the UE, that is, during the process in which the PCEF sends the data packet to the UE, the intermediate node also participates in control of quality of service.

In the method for controlling quality of service provided in this embodiment, a priority of a service flow is indicated by using a one-dimensional scalar FPI, and a downlink data packet carrying the FPI is sent to a base station, so that the base station sends the downlink data packet of the service flow according to the FPI; in this way, end-to-end control of quality of service based on service flow granularity is implemented, end-to-end differentiated processing can be performed on the service flow, differentiated service experiences can be provided for different levels of subscribers and different types of services, and utilization efficiency of radio resources can be effectively improved.

Based on a same idea, another embodiment of the present invention also provides a method for controlling quality of service. As shown in <figref idref="DRAWINGS">FIG. 2</figref>, the method includes:

<b>201</b>: A base station receives a downlink data packet.

The downlink data packet includes an FPI.

Exemplarily, the downlink data packet may be obtained according to a service type of a service to which the downlink data packet belongs and at least one of the following parameters that may be used for quality control: a service priority of the service to which the downlink data packet belongs, a subscriber accumulated usage level of the service to which the downlink data packet belongs, a subscriber level of the service to which the downlink data packet belongs, and a type of a UE receiving the downlink data packet.

<b>202</b>: The base station sends the downlink data packet to a UE according to the FPI.

Exemplarily, the base station may send the downlink data packet to the UE according to a sequence of service flow priorities indicated by FPIs.

Exemplarily, the base station may send the downlink data packet to the UE according to weight information corresponding to the FPI.

Exemplarily, the base station may send the downlink data packet to the UE according to weight information corresponding to the FPI and weight information corresponding to a bearer to which the downlink data packet belongs.

In the method for controlling quality of service provided in this embodiment, a priority of a service flow is indicated by using a one-dimensional scalar FPI, and sending of a downlink data packet of the service flow is performed according to the FPI through a base station; in this way, end-to-end control of quality of service based on service flow granularity is implemented, end-to-end differentiated processing can be performed on the service flow, differentiated service experiences can be provided for different levels of subscribers and different types of services, and utilization efficiency of radio resources can be effectively improved.

The method for controlling quality of service provided in the embodiment of the present invention is described in detail in the following through a specific example, as shown in <figref idref="DRAWINGS">FIG. 3</figref>.

<b>301</b>: A UE accesses a network to establish a packet data network connection between the UE and a gateway, and a default bearer or a packet data protocol (Packet Data Protocol, PDP) context.

<b>302</b>: A PCEF performs service detection.

When there is a downlink data packet passing, the PCEF performs service detection based on technologies such as IP quintuple or deep packet inspection (Deep packet inspection, DPI). When the PCEF has detected a new service, the PCEF reports a detection result to a PCRF. Exemplarily, the PCEF may report the detection result to the PCRF by adopting a traffic detection function (Traffic Detection Function, TDF) mechanism and a Gx/Sd interface, for example, service information that has been detected may be carried in an Application-Detection-Information information element in a CC-Request message.

Obtaining an FPI of the downlink data packet by the PCEF may be shown in <b>303</b><i>a </i>to <b>303</b><i>b</i>, and may also be shown in <b>303</b><i>c </i>to <b>303</b><i>e. </i>

<b>303</b><i>a</i>: The PCRF obtains an FPI corresponding to the downlink data packet.

Exemplarily, the PCRF may obtain the corresponding FPI according to a service type of a service to which the downlink data packet belongs and at least one of the following items: a service priority of the service to which the downlink data packet belongs, a subscriber accumulated usage level of the service to which the downlink data packet belongs, a subscriber level of the service to which the downlink data packet belongs, and a type of a UE receiving the downlink data packet. For example, the PCRF may pre-configure an FPI subscription table. As shown in the following Table 1, after receiving a service detection result reported by the PCEF, the PCRF queries, according to the service type corresponding to the downlink data packet, the subscriber accumulated usage level, whether the service is subscribed to, and the subscriber level, Table 1 to obtain the corresponding FPI. A. person skilled in the art should know that Table 1 is merely for exemplary description, and specific content may be adjusted according to actual applications, which is not limited in the embodiment of the present invention.

<tables id="TABLE-US-00001" num="00001"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="5"><colspec colname="1" colwidth="49pt" align="left" /><colspec colname="2" colwidth="49pt" align="left" /><colspec colname="3" colwidth="49pt" align="left" /><colspec colname="4" colwidth="42pt" align="left" /><colspec colname="5" colwidth="28pt" align="center" /><thead><row><entry namest="1" nameend="5" rowsep="1">TABLE 1</entry></row><row><entry namest="1" nameend="5" align="center" rowsep="1" /></row><row><entry /><entry>Subscriber</entry><entry>Whether a</entry><entry /><entry /></row><row><entry /><entry>Accumulated</entry><entry>service is</entry><entry>Subscriber</entry></row><row><entry>Service Type</entry><entry>Usage Level</entry><entry>subscribed to</entry><entry>Level</entry><entry>FPI</entry></row><row><entry namest="1" nameend="5" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>Video</entry><entry>Low</entry><entry>Yes</entry><entry>High</entry><entry>1</entry></row><row><entry>Video</entry><entry>Low</entry><entry>No</entry><entry>High</entry><entry>2</entry></row><row><entry>Video</entry><entry>High</entry><entry>No</entry><entry>Intermediate</entry><entry>3</entry></row><row><entry>Web page</entry><entry>Low</entry><entry>No</entry><entry>Intermediate</entry><entry>4</entry></row><row><entry>browsing</entry></row><row><entry>Web page</entry><entry>High</entry><entry>No</entry><entry>Intermediate</entry><entry>5</entry></row><row><entry>browsing</entry></row><row><entry namest="1" nameend="5" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

For another example, the PCRF may also calculate, through a certain specific formula, the FPI according to at least one of the following items: the service priority of the service to which the downlink data packet belongs, the subscriber accumulated usage level of the service to which the downlink data packet belongs, the subscriber level of the service to which the downlink data packet belongs, and the type of the UE receiving the downlink data packet.

The foregoing parameters related to the downlink data packet, such as the service priority of the service to which the downlink data packet belongs, the subscriber accumulated usage level of the service to which the downlink data packet belongs, the subscriber level of the service to which the downlink data packet belongs, and the type of the UE receiving the downlink data packet, are merely exemplary examples. In actual applications, other parameters of quality of service may be adopted, which are not limited in the embodiment of the present invention.

<b>303</b><i>b</i>: The PCRF sends the FPI corresponding to the downlink data packet to the PCEF.

Exemplarily, the PCRF may deliver, through a Gx interface to the PCEF, a policy and charging control (Policy and Charging Control PCC) rule, including the FPI corresponding to the downlink data packet, for example, the PCRF carries the FPI corresponding to the downlink data packet in a Charging-Rule-Install information element of a CC-Answer message.

<b>303</b><i>c</i>: The RCRF generates a PCC rule.

The PCC rule includes at least one of the following items: a service priority of a service to which the downlink data packet belongs, a subscriber accumulated usage level of the service to which the downlink data packet belongs, a subscriber level of the service to which the downlink data packet belongs, and a type of a UE receiving the downlink data packet.

<b>303</b><i>d</i>: The PCRF delivers the PCC rule to the PCEF.

Exemplarily, the PCRF delivers, through a Gx interface, the PCC rule to the PCEF, for example, the PCRF may carries service priority information in a Charging-Rule-Install information element of a CC-Answer message.

<b>303</b><i>e</i>: The PCEF obtains an FPI corresponding to the downlink data packet.

Exemplarily, the PCEF may obtain the corresponding FPI according to a service type of the service to which the downlink data packet belongs and at least one of the following items: the service priority of the service to which the downlink data packet belongs, the subscriber accumulated usage level of the service to which the downlink data packet belongs, the subscriber level of the service to which the downlink data packet belongs, and the type of the UE receiving the downlink data packet. For example, the PCEF may also obtain the corresponding FPI by configuring an FPI subscription table. Reference may be made to the content in <b>303</b><i>a </i>for details, which are not repeatedly described here.

<b>304</b>: The PCEF carries the obtained FPI in the downlink data packet.

Exemplarily, the PCEF may carry the FPI in the downlink data packet by marking a user plane data packet. For example, the FPI may be carried in a tunnel encapsulation header or in an IP packet header of the downlink data packet. The following exemplary description does not constitute a limitation to the embodiment of the present invention.

1) Carry the FPI in the tunnel encapsulation header.

For a GPRS tunneling protocol (GPRS Tunneling Protocol, GTP) interface, such as Gn/Gp, S5/S8, and Iu interfaces, the FPI may be carried by adopting a GTP-U header extension manner. As shown in Table 2 and Table 3, a type of an extension header is 00, so as not to affect another network element.

<tables id="TABLE-US-00002" num="00002"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="offset" colwidth="42pt" align="left" /><colspec colname="1" colwidth="168pt" align="center" /><colspec colname="2" colwidth="7pt" align="center" /><thead><row><entry /><entry namest="offset" nameend="2" rowsep="1">TABLE 2</entry></row></thead><tbody valign="top"><row><entry /><entry namest="offset" nameend="2" align="center" rowsep="1" /></row><row><entry /><entry>Bits</entry><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="9"><colspec colname="1" colwidth="42pt" align="center" /><colspec colname="2" colwidth="28pt" align="center" /><colspec colname="3" colwidth="21pt" align="center" /><colspec colname="4" colwidth="14pt" align="center" /><colspec colname="5" colwidth="28pt" align="center" /><colspec colname="6" colwidth="14pt" align="center" /><colspec colname="7" colwidth="28pt" align="center" /><colspec colname="8" colwidth="14pt" align="center" /><colspec colname="9" colwidth="28pt" align="center" /><tbody valign="top"><row><entry>Octets</entry><entry>8</entry><entry>7</entry><entry>6</entry><entry>5</entry><entry>4</entry><entry>3</entry><entry>2</entry><entry>1</entry></row><row><entry namest="1" nameend="9" align="center" rowsep="1" /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="7"><colspec colname="1" colwidth="42pt" align="char" char="." /><colspec colname="2" colwidth="63pt" align="center" /><colspec colname="3" colwidth="28pt" align="center" /><colspec colname="4" colwidth="14pt" align="center" /><colspec colname="5" colwidth="28pt" align="center" /><colspec colname="6" colwidth="14pt" align="center" /><colspec colname="7" colwidth="28pt" align="center" /><tbody valign="top"><row><entry>1</entry><entry>Version</entry><entry>PT</entry><entry>(*)</entry><entry>E</entry><entry>S</entry><entry>PN</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="42pt" align="char" char="." /><colspec colname="2" colwidth="168pt" align="center" /><colspec colname="3" colwidth="7pt" align="center" /><tbody valign="top"><row><entry>2</entry><entry>Message Type</entry><entry /></row><row><entry>3</entry><entry>Length (1^stOctet)</entry></row><row><entry>4</entry><entry>Length (2^ndOctet)</entry></row><row><entry>5</entry><entry>Tunnel Endpoint Identifier (1^stOctet)</entry></row><row><entry>6</entry><entry>Tunnel Endpoint Identifier (2^ndOctet)</entry></row><row><entry>7</entry><entry>Tunnel Endpoint Identifier (3^rdOctet)</entry></row><row><entry>8</entry><entry>Tunnel Endpoint Identifier (4^thOctet)</entry></row><row><entry>9</entry><entry>Sequence Number (1^stOctet)¹⁾⁴⁾</entry></row><row><entry>10</entry><entry>Sequence Number (2nd Octet)1) 4)</entry></row><row><entry>11</entry><entry>N-PDU Number2) 4)</entry></row><row><entry>12</entry><entry>Next Extension Header Type3) 4)</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

<tables id="TABLE-US-00003" num="00003"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="91pt" align="center" /><colspec colname="2" colwidth="126pt" align="left" /><thead><row><entry namest="1" nameend="2" rowsep="1">TABLE 3</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>Next Extension Header</entry><entry /></row><row><entry>Field Value</entry><entry>Type of Extension Header</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>0000 0000</entry><entry>No more extension headers</entry></row><row><entry>0000 0001</entry><entry>MBMS support indication</entry></row><row><entry>0000 0010</entry><entry>MS Info Change Reporting support</entry></row><row><entry /><entry>indication</entry></row><row><entry>0010 0000</entry><entry>Service Flow Priority Identifier(new)</entry></row><row><entry>1100 0000</entry><entry>PDCP PDU number</entry></row><row><entry>1100 0001</entry><entry>Suspend Request</entry></row><row><entry>1100 0010</entry><entry>Suspend Response</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

For a proxy mobile IP version 6 (PMIPv6) interface, such as S2a and S2b, the FPI may be carried by adding a field in generic routing encapsulation (Generic Routing Encapsulation, GRE), and the FPI may also be carried by using a Reserved0 or Reserved1 cell in existing GRE encapsulation, as shown in Table 4.

<tables id="TABLE-US-00004" num="00004"><table frame="none" colsep="0" rowsep="0" pgwide="1"><tgroup align="left" colsep="0" rowsep="0" cols="32"><colspec colname="1" colwidth="14pt" align="center" /><colspec colname="2" colwidth="7pt" align="center" /><colspec colname="3" colwidth="14pt" align="center" /><colspec colname="4" colwidth="14pt" align="center" /><colspec colname="5" colwidth="7pt" align="center" /><colspec colname="6" colwidth="7pt" align="center" /><colspec colname="7" colwidth="7pt" align="center" /><colspec colname="8" colwidth="7pt" align="center" /><colspec colname="9" colwidth="7pt" align="center" /><colspec colname="10" colwidth="7pt" align="center" /><colspec colname="11" colwidth="7pt" align="center" /><colspec colname="12" colwidth="7pt" align="center" /><colspec colname="13" colwidth="7pt" align="center" /><colspec colname="14" colwidth="7pt" align="center" /><colspec colname="15" colwidth="7pt" align="center" /><colspec colname="16" colwidth="14pt" align="center" /><colspec colname="17" colwidth="7pt" align="center" /><colspec colname="18" colwidth="14pt" align="center" /><colspec colname="19" colwidth="7pt" align="center" /><colspec colname="20" colwidth="7pt" align="center" /><colspec colname="21" colwidth="14pt" align="center" /><colspec colname="22" colwidth="7pt" align="center" /><colspec colname="23" colwidth="14pt" align="center" /><colspec colname="24" colwidth="14pt" align="center" /><colspec colname="25" colwidth="14pt" align="center" /><colspec colname="26" colwidth="14pt" align="center" /><colspec colname="27" colwidth="7pt" align="center" /><colspec colname="28" colwidth="14pt" align="center" /><colspec colname="29" colwidth="14pt" align="center" /><colspec colname="30" colwidth="14pt" align="center" /><colspec colname="31" colwidth="14pt" align="center" /><colspec colname="32" colwidth="14pt" align="center" /><thead><row><entry namest="1" nameend="32" rowsep="1">TABLE 4</entry></row><row><entry namest="1" nameend="32" align="center" rowsep="1" /></row><row><entry>0</entry><entry>1</entry><entry>2</entry><entry>3</entry><entry>4</entry><entry>5</entry><entry>6</entry><entry>7</entry><entry>8</entry><entry>9</entry><entry>0</entry><entry>1</entry><entry>2</entry><entry>3</entry><entry>4</entry><entry>5</entry><entry>6</entry><entry>7</entry><entry>8</entry><entry>9</entry><entry>0</entry><entry>1</entry><entry>2</entry><entry>3</entry><entry>4</entry><entry>5</entry><entry>6</entry><entry>7</entry><entry>8</entry><entry>9</entry><entry>0</entry><entry>1</entry></row><row><entry namest="1" nameend="32" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="7"><colspec colname="1" colwidth="14pt" align="center" /><colspec colname="2" colwidth="7pt" align="center" /><colspec colname="3" colwidth="14pt" align="center" /><colspec colname="4" colwidth="14pt" align="center" /><colspec colname="5" colwidth="63pt" align="center" /><colspec colname="6" colwidth="28pt" align="center" /><colspec colname="7" colwidth="189pt" align="center" /><tbody valign="top"><row><entry>C</entry><entry /><entry>K</entry><entry>S</entry><entry>Reserved0</entry><entry>Ver</entry><entry>Protocol Type</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="140pt" align="center" /><colspec colname="2" colwidth="189pt" align="center" /><tbody valign="top"><row><entry>Checksum (optional)</entry><entry>Reserved1 (Optional)</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="329pt" align="center" /><tbody valign="top"><row><entry>Key (optional)</entry></row><row><entry>Sequence Number (Optional)</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

2) If the FPI is carried in the IP packet header, it is unnecessary to extend tunnel encapsulation.

For example, for an IPv4 packet, a differentiated services code point (Differentiated Services Code Point, DSCP) field may be adopted to identify an FPI, as shown in Table 5. In this embodiment, merely a DSCP in an IP header at an application layer within a tunnel carries the FPI, which does not affect scheduling of an intermediate node and is also not affected by rewriting of a DSCP in an IP header at an external layer of the tunnel by the intermediate node.

<tables id="TABLE-US-00005" num="00005"><table frame="none" colsep="0" rowsep="0" pgwide="1"><tgroup align="left" colsep="0" rowsep="0" cols="32"><colspec colname="1" colwidth="7pt" align="center" /><colspec colname="2" colwidth="7pt" align="center" /><colspec colname="3" colwidth="7pt" align="center" /><colspec colname="4" colwidth="7pt" align="center" /><colspec colname="5" colwidth="7pt" align="center" /><colspec colname="6" colwidth="7pt" align="center" /><colspec colname="7" colwidth="7pt" align="center" /><colspec colname="8" colwidth="7pt" align="center" /><colspec colname="9" colwidth="7pt" align="center" /><colspec colname="10" colwidth="7pt" align="center" /><colspec colname="11" colwidth="7pt" align="center" /><colspec colname="12" colwidth="7pt" align="center" /><colspec colname="13" colwidth="7pt" align="center" /><colspec colname="14" colwidth="7pt" align="center" /><colspec colname="15" colwidth="7pt" align="center" /><colspec colname="16" colwidth="7pt" align="center" /><colspec colname="17" colwidth="14pt" align="center" /><colspec colname="18" colwidth="14pt" align="center" /><colspec colname="19" colwidth="14pt" align="center" /><colspec colname="20" colwidth="14pt" align="center" /><colspec colname="21" colwidth="14pt" align="center" /><colspec colname="22" colwidth="14pt" align="center" /><colspec colname="23" colwidth="14pt" align="center" /><colspec colname="24" colwidth="14pt" align="center" /><colspec colname="25" colwidth="14pt" align="center" /><colspec colname="26" colwidth="14pt" align="center" /><colspec colname="27" colwidth="14pt" align="center" /><colspec colname="28" colwidth="14pt" align="center" /><colspec colname="29" colwidth="14pt" align="center" /><colspec colname="30" colwidth="14pt" align="center" /><colspec colname="31" colwidth="14pt" align="center" /><colspec colname="32" colwidth="14pt" align="center" /><thead><row><entry namest="1" nameend="32" rowsep="1">TABLE 5</entry></row><row><entry namest="1" nameend="32" align="center" rowsep="1" /></row><row><entry>0</entry><entry>1</entry><entry>2</entry><entry>3</entry><entry>4</entry><entry>5</entry><entry>6</entry><entry>7</entry><entry>8</entry><entry>9</entry><entry>0</entry><entry>1</entry><entry>2</entry><entry>3</entry><entry>4</entry><entry>5</entry><entry>6</entry><entry>7</entry><entry>8</entry><entry>9</entry><entry>0</entry><entry>1</entry><entry>2</entry><entry>3</entry><entry>4</entry><entry>5</entry><entry>6</entry><entry>7</entry><entry>8</entry><entry>9</entry><entry>0</entry><entry>1</entry></row><row><entry namest="1" nameend="32" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="28pt" align="center" /><colspec colname="2" colwidth="28pt" align="center" /><colspec colname="3" colwidth="56pt" align="center" /><colspec colname="4" colwidth="224pt" align="center" /><tbody valign="top"><row><entry>Version</entry><entry>IHL</entry><entry>DSCP</entry><entry>Total Length</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="112pt" align="center" /><colspec colname="2" colwidth="42pt" align="center" /><colspec colname="3" colwidth="182pt" align="center" /><tbody valign="top"><row><entry>Identification</entry><entry>Flags</entry><entry>Fragment Offset</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="56pt" align="center" /><colspec colname="2" colwidth="56pt" align="center" /><colspec colname="3" colwidth="224pt" align="center" /><tbody valign="top"><row><entry>Time to Live</entry><entry>Protocol</entry><entry>Header Checksum</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="336pt" align="center" /><tbody valign="top"><row><entry>Source Address</entry></row><row><entry>Destination Address</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="224pt" align="center" /><colspec colname="2" colwidth="112pt" align="center" /><tbody valign="top"><row><entry>Options</entry><entry>Padding</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

For another example, for an IPv6 packet, a FPI may be carried by adopting a Traffic Class field, as shown in <figref idref="DRAWINGS">FIG. 6</figref>.

<tables id="TABLE-US-00006" num="00006"><table frame="none" colsep="0" rowsep="0" pgwide="1"><tgroup align="left" colsep="0" rowsep="0" cols="32"><colspec colname="1" colwidth="7pt" align="center" /><colspec colname="2" colwidth="7pt" align="center" /><colspec colname="3" colwidth="7pt" align="center" /><colspec colname="4" colwidth="7pt" align="center" /><colspec colname="5" colwidth="7pt" align="center" /><colspec colname="6" colwidth="7pt" align="center" /><colspec colname="7" colwidth="7pt" align="center" /><colspec colname="8" colwidth="7pt" align="center" /><colspec colname="9" colwidth="7pt" align="center" /><colspec colname="10" colwidth="7pt" align="center" /><colspec colname="11" colwidth="7pt" align="center" /><colspec colname="12" colwidth="7pt" align="center" /><colspec colname="13" colwidth="7pt" align="center" /><colspec colname="14" colwidth="7pt" align="center" /><colspec colname="15" colwidth="7pt" align="center" /><colspec colname="16" colwidth="7pt" align="center" /><colspec colname="17" colwidth="14pt" align="center" /><colspec colname="18" colwidth="14pt" align="center" /><colspec colname="19" colwidth="14pt" align="center" /><colspec colname="20" colwidth="14pt" align="center" /><colspec colname="21" colwidth="14pt" align="center" /><colspec colname="22" colwidth="14pt" align="center" /><colspec colname="23" colwidth="14pt" align="center" /><colspec colname="24" colwidth="14pt" align="center" /><colspec colname="25" colwidth="14pt" align="center" /><colspec colname="26" colwidth="14pt" align="center" /><colspec colname="27" colwidth="14pt" align="center" /><colspec colname="28" colwidth="14pt" align="center" /><colspec colname="29" colwidth="14pt" align="center" /><colspec colname="30" colwidth="14pt" align="center" /><colspec colname="31" colwidth="14pt" align="center" /><colspec colname="32" colwidth="14pt" align="center" /><thead><row><entry namest="1" nameend="32" rowsep="1">TABLE 6</entry></row><row><entry namest="1" nameend="32" align="center" rowsep="1" /></row><row><entry>0</entry><entry>1</entry><entry>2</entry><entry>3</entry><entry>4</entry><entry>5</entry><entry>6</entry><entry>7</entry><entry>8</entry><entry>9</entry><entry>0</entry><entry>1</entry><entry>2</entry><entry>3</entry><entry>4</entry><entry>5</entry><entry>6</entry><entry>7</entry><entry>8</entry><entry>9</entry><entry>0</entry><entry>1</entry><entry>2</entry><entry>3</entry><entry>4</entry><entry>5</entry><entry>6</entry><entry>7</entry><entry>8</entry><entry>9</entry><entry>0</entry><entry>1</entry></row><row><entry namest="1" nameend="32" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="28pt" align="center" /><colspec colname="2" colwidth="56pt" align="center" /><colspec colname="3" colwidth="252pt" align="center" /><tbody valign="top"><row><entry>Version</entry><entry>Traffic Class</entry><entry>Flow Label</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="112pt" align="center" /><colspec colname="2" colwidth="112pt" align="center" /><colspec colname="3" colwidth="112pt" align="center" /><tbody valign="top"><row><entry>Payload Length</entry><entry>Next Header</entry><entry>Hop Limit</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="336pt" align="center" /><tbody valign="top"><row><entry>Source Address</entry></row><row><entry>Destination Address</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

It should be noted that the foregoing manners for carrying the FPI are merely several common instances, to which specific applications are not limited, and the details are not described in detail here.

<b>305</b>: The PCEF sends the downlink data packet to a base station.

Optionally, the PCEF may send the downlink data packet according to the FPI of the downlink data packet. Exemplarily, the PCEF may prioritize and schedule downlink data packets based on FPIs, and preferentially send a downlink data packet of a service flow with a high priority.

Optionally, when the downlink data packet passes through the intermediate node, the intermediate node may also forward the downlink data packet according to the FPI of the downlink data packet. Exemplarily, the intermediate node may prioritize and schedule downlink data packets based on FPIs, and preferentially send a downlink data packet of a service flow with a high priority.

<b>306</b>: The base station sends the downlink data packet to the UE according to the FPI of the downlink data packet.

In this embodiment, sending of the downlink data packet based on the FPI may be implemented in multiple manners, and this embodiment is merely described in the following manners, to which this embodiment is not limited. For example, the downlink data packet may be sent to the UE according to a sequence of service flow priorities indicated by FPIs, and the downlink data packet may also be sent to the UE according to weight information corresponding to the FPI, or the downlink data packet may be sent to the UE according to weight information corresponding to the FPI and weight information corresponding to a bearer to which the downlink data packet belongs.

That the downlink data packet is sent according to the weight information corresponding to the FPI and the weight information of the bearer corresponding to the downlink data packet is taken as an example for description in the following.

For example, as shown in Table 7, a certain cell has three subscribers, each subscriber has a bearer with a weight of 100, 50, and 50; each bear has three queues with a weight of 60, 30, and 10, and each queue may correspond to two different FPIs. When there is a downlink data packet passing, the downlink data packet may be inserted to a corresponding queue according to a bearer to which the downlink data packet belongs and an FPI of the downlink data packet. When a base station sends a downlink data packet, the base station first allocates scheduling opportunities (2:1:1) to bearers according to weights of the bearers. After the bearers are scheduled, the base station allocates scheduling opportunities (6:3:1) to queues according to weights of the queues of the bearers, so as to choose and send a downlink data packet in a corresponding queue. Based on this, a downlink data packet of a service flow with a high priority may be sent preferentially, and a downlink data packet of a service flow with a low priority may be sent after a delay. In this manner, end-to-end control of quality of service based on service flow granularity is implemented, end-to-end differentiated processing can be performed on the service flow, differentiated service experiences can be provided for different levels of subscribers and different types of services, and utilization efficiency of radio resources may be effectively improved.

<tables id="TABLE-US-00007" num="00007"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="6"><colspec colname="1" colwidth="28pt" align="center" /><colspec colname="2" colwidth="35pt" align="center" /><colspec colname="3" colwidth="21pt" align="center" /><colspec colname="4" colwidth="28pt" align="center" /><colspec colname="5" colwidth="28pt" align="center" /><colspec colname="6" colwidth="77pt" align="left" /><thead><row><entry namest="1" nameend="6" rowsep="1">TABLE 7</entry></row><row><entry namest="1" nameend="6" align="center" rowsep="1" /></row><row><entry /><entry>Quality of</entry><entry /><entry /><entry /><entry /></row><row><entry /><entry>Service</entry></row><row><entry>Sub-</entry><entry>Class</entry><entry /><entry>Bearer</entry><entry>Queue</entry></row><row><entry>scriber</entry><entry>Identifier</entry><entry>FPI</entry><entry>Weight</entry><entry>Weight</entry><entry>Examples of Services</entry></row><row><entry namest="1" nameend="6" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="6"><colspec colname="1" colwidth="28pt" align="center" /><colspec colname="2" colwidth="35pt" align="center" /><colspec colname="3" colwidth="21pt" align="center" /><colspec colname="4" colwidth="28pt" align="char" char="." /><colspec colname="5" colwidth="28pt" align="center" /><colspec colname="6" colwidth="77pt" align="left" /><tbody valign="top"><row><entry>A</entry><entry>7</entry><entry>1~2</entry><entry>100</entry><entry>60</entry><entry>Services that may be</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>controlled by operators,</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>such as videos and</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>multimedia messages</entry></row><row><entry /><entry /><entry>3~4</entry><entry /><entry>30</entry><entry>Services with a high</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>priority, such as instant</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>messages and web page</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>browsing</entry></row><row><entry /><entry /><entry>5~6</entry><entry /><entry>10</entry><entry>Services with a low</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>priority, such as</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>point-to-point</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>transmission</entry></row><row><entry>B</entry><entry>8</entry><entry>1~2</entry><entry>50</entry><entry>60</entry><entry>Services that may be</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>controlled by operators,</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>such as videos and</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>multimedia messages</entry></row><row><entry /><entry /><entry>3~4</entry><entry /><entry>30</entry><entry>Services with a high</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>priority, such as instant</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>messages and web page</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>browsing</entry></row><row><entry /><entry /><entry>5~6</entry><entry /><entry>10</entry><entry>Services with a low</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>priority, such as</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>point-to-point</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>transmission</entry></row><row><entry>C</entry><entry>8</entry><entry>1~2</entry><entry>50</entry><entry>60</entry><entry>Services that may be</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>controlled by operators,</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>such as videos and</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>multimedia messages</entry></row><row><entry /><entry /><entry>3~4</entry><entry /><entry>30</entry><entry>Services with a high</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>priority, such as instant</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>messages and web page</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>browsing</entry></row><row><entry /><entry /><entry>5~6</entry><entry /><entry>10</entry><entry>Services with a low</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>priority, such as</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>point-to-point</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>transmission</entry></row><row><entry namest="1" nameend="6" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

It should be noted that, for a working mechanism for the PCEF and the intermediate node to send the downlink data packet according to the FPI, reference may be made to a working mechanism for the base station to send the downlink data packet according to the FPI, and details are not repeatedly described here.

In the method for controlling quality of service provided in this embodiment, a priority of a service flow is indicated by using a one-dimensional scalar FPI, a downlink data packet including the FPI is sent to a base station through a policy and charging enforcement function entity, and then the base station sends the downlink data packet of the service flow according to the FPI; in this way, end-to-end control of quality of service based on service flow granularity is implemented, end-to-end differentiated processing can be performed on the service flow, differentiated service experiences can be provided for different levels of subscribers and different types of services, and utilization efficiency of radio resources can be effectively improved.

Based on a same idea, still another embodiment of the present invention provides a policy and charging enforcement function entity. As shown in <figref idref="DRAWINGS">FIG. 4</figref>, the policy and charging enforcement function entity includes an obtaining unit <b>401</b>, a marking unit <b>402</b>, and a sending unit <b>403</b>, where

the obtaining unit <b>401</b> is configured to obtain an FPI of a downlink data packet;

the marking unit <b>402</b> is configured to carry the FPI in the downlink data packet; and

the sending unit <b>403</b> is configured to send the downlink data packet to a base station, so that the base station sends the downlink data packet to a UE according to the FPI.

Furthermore, as shown in <figref idref="DRAWINGS">FIG. 5</figref>, the obtaining unit <b>401</b> includes a receiving unit <b>4011</b> or a matching unit <b>4012</b>. The receiving unit <b>4011</b> is configured to receive an FPI sent by a PCRF, where the FPI is obtained by the PCRF according to a service type of a service to which the downlink data packet belongs and at least one of the following items: a service priority of the service to which the downlink data packet belongs, a subscriber accumulated usage level of the service to which the downlink data packet belongs, a subscriber level of the service to which the downlink data packet belongs, and a type of the UE receiving the downlink data packet. The matching unit <b>4012</b> is configured to obtain the FPI according to a service type of a service to which the downlink data packet belongs and at least one of the following items: a service priority of the service to which the downlink data packet belongs, a subscriber accumulated usage level of the service to which the downlink data packet belongs, a subscriber level of the service to which the downlink data packet belongs, and a type of the UE receiving the downlink data packet.

Furthermore, as shown in <figref idref="DRAWINGS">FIG. 6</figref>, the obtaining unit <b>401</b> further includes a rule receiving unit <b>4013</b> and an extracting unit <b>4014</b>. The rule receiving unit <b>4013</b> is configured to receive a policy and charging control PCC rule delivered by the PCRF. The extracting unit <b>4014</b> is configured to obtain, from the PCC rule, at least one of the following items: the service priority of the service to which the downlink data packet belongs, the subscriber accumulated usage level of the service to which the downlink data packet belongs, the subscriber level of the service to which the downlink data packet belongs, and the type of the UE receiving the downlink data packet.

Furthermore, as shown in <figref idref="DRAWINGS">FIG. 7</figref>, the marking unit <b>402</b> includes a first processing unit <b>4021</b> or a second processing unit <b>4022</b>. The first processing unit <b>4021</b> is configured to carry the FPI in a tunnel encapsulation header of the downlink data packet; and the second processing unit <b>4022</b> is configured to carry the FPI in an IP packet header of the downlink data packet.

Furthermore, the sending unit <b>403</b> is specifically configured to send, through an intermediate node, the downlink data packet to a base station, so that the base station sends the downlink data packet to the UE according to the FPI, where the downlink data packet is sent by the intermediate node to the base station according to the FPI.

A working mechanism for the policy and charging enforcement function entity provided in this embodiment to implement the method for controlling quality of service is the same as a working mechanism in the embodiments shown in <figref idref="DRAWINGS">FIG. 1</figref> and <figref idref="DRAWINGS">FIG. 3</figref>, and details are not repeatedly described here. The policy and charging enforcement function entity shown in <figref idref="DRAWINGS">FIG. 1</figref> and <figref idref="DRAWINGS">FIG. 3</figref> may be implemented by the policy and charging enforcement function entity provided in this embodiment.

In the policy and charging enforcement function entity provided in this embodiment, a priority of a service flow is indicated by using a one-dimensional scalar FPI, and a downlink data packet carrying the FPI is sent to a base station, so that the base station sends the downlink data packet of the service flow according to the FPI; in this way, end-to-end control of quality of service based on service flow granularity is implemented, end-to-end differentiated processing can be performed on the service flow, differentiated service experiences can be provided for different levels of subscribers and different types of services, and utilization efficiency of radio resources can be effectively improved.

Based on a same idea, yet another embodiment of the present invention provides a policy and charging rules function entity. As shown in <figref idref="DRAWINGS">FIG. 8</figref>, the policy and charging rules function entity includes an obtaining unit <b>501</b> and a sending unit <b>502</b>, where <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0121">the obtaining unit <b>501</b> is configured to obtain an FPI according to a service type of a service to which a downlink data packet belongs and at least one of the following items: a service priority of the service to which the downlink data packet belongs, a subscriber accumulated usage level of the service to which the downlink data packet belongs, a subscriber level of the service to which the downlink data packet belongs, and a type of a UE receiving the downlink data packet; and</li><li id="ul0002-0002" num="0122">the sending unit <b>502</b> is configured to send the FPI to a policy and charging enforcement function entity.</li></ul></li></ul>

The policy and charging rules function entity provided in the embodiment of the present invention may implement the policy and charging rules function entity in the embodiments shown in <figref idref="DRAWINGS">FIG. 1</figref> and <figref idref="DRAWINGS">FIG. 3</figref>.

In the policy and charging rules function entity provided in the embodiment of the present invention, a priority of a service flow is indicated by using a one-dimensional scalar FPI, and the FPI is sent to a policy and charging enforcement function entity; in this way, end-to-end control of quality of service based on service flow granularity can be implemented, end-to-end differentiated processing can be performed on the service flow, differentiated service experiences can be provided for different levels of subscribers and different types of services, and utilization efficiency of radio resources can be effectively improved.

Based on a same idea, yet another embodiment of the present invention provides a base station. As shown in <figref idref="DRAWINGS">FIG. 9</figref>, the base station includes a receiving unit <b>601</b> and a sending unit <b>602</b>, where <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0000"><ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0126">the receiving unit <b>601</b> is configured to receive a downlink data packet, where the downlink data packet includes an FPI; and</li><li id="ul0004-0002" num="0127">the sending unit <b>602</b> is configured to send the downlink data packet to a UE according to the FPI.</li></ul></li></ul>

Furthermore, as shown in <figref idref="DRAWINGS">FIG. 10</figref>, the sending unit <b>602</b> includes a first obtaining unit <b>6021</b> and a first sending unit <b>6022</b>. The first obtaining unit <b>6021</b> is configured to obtain weight information corresponding to the FPI; and the first sending unit <b>6022</b> is configured to send the downlink data packet to the UE according to the weight information corresponding to the FPI.

Furthermore, as shown in <figref idref="DRAWINGS">FIG. 11</figref>, the sending unit <b>602</b> includes a second obtaining unit <b>6023</b>, a third obtaining unit <b>6024</b>, and a second sending unit <b>6025</b>. The second obtaining unit <b>6023</b> is configured to obtain weight information corresponding to the FPI; the third obtaining unit <b>6024</b> is configured to obtain weight information corresponding to a bearer of the downlink data packet; and the second sending unit <b>6025</b> is configured to send the downlink data packet to the UE according to the weight information corresponding to the FPI and the weight information corresponding to the bearer to which the downlink data packet belongs.

A working mechanism for the base station provided in the embodiment of the present invention to implement control of quality of service is the same as that in the embodiments shown in <figref idref="DRAWINGS">FIG. 2</figref> and <figref idref="DRAWINGS">FIG. 3</figref>, and details are not repeatedly described here. The base station in <figref idref="DRAWINGS">FIG. 2</figref> and <figref idref="DRAWINGS">FIG. 3</figref> may be implemented by the base station provided in this embodiment.

In the base station provided in the embodiment of the present invention, a priority of a service flow is indicated by using a one-dimensional scalar FPI, and sending of a downlink data packet of the service flow is performed according to the FPI through a base station; in this way, end-to-end control of quality of service based on service flow granularity is implemented, end-to-end differentiated processing can be performed on the service flow, differentiated service experiences can be provided for different levels of subscribers and different types of services, and utilization efficiency of radio resources can be effectively improved.

Based on a same idea, yet another embodiment of the present invention provides a system for controlling quality of service. As shown in <figref idref="DRAWINGS">FIG. 12</figref>, the system for controlling quality of service includes a policy and charging enforcement function entity <b>701</b> and a base station <b>702</b>, where:

the policy and charging enforcement function entity <b>701</b> may be the policy and charging enforcement function entity shown in <figref idref="DRAWINGS">FIG. 4</figref>; and

the base station <b>702</b> may be the base station shown in <figref idref="DRAWINGS">FIG. 9</figref>.

A working mechanism for the system for controlling quality of service provided in this embodiment to implement control of quality of service is the same as working mechanism(s) in the embodiments shown in <figref idref="DRAWINGS">FIG. 1</figref> to <figref idref="DRAWINGS">FIG. 3</figref>, and details are not repeatedly described here.

In the system for controlling quality of service provided in this embodiment, a priority of a service flow is indicated by using a one-dimensional scalar FPI, a downlink data packet including the FPI is sent to a base station through a policy and charging enforcement function entity, and then the base station sends the downlink data packet of the service flow according to the FPI; in this way, end-to-end control of quality of service based on service flow granularity is implemented, end-to-end differentiated processing can be performed on the service flow, differentiated service experiences can be provided for different levels of subscribers and different types of services, and utilization efficiency of radio resources can be effectively improved.

It should be noted that, a person skilled in the art may easily understand that the device for implementing control of quality of service described in the foregoing embodiments may also exist as part of another system, and the method for implementing control of quality of service in the system is consistent with that described in the foregoing embodiments. Therefore, the another system including the device for implementing control of quality of service provided in the foregoing embodiments should also fall within the protection scope of the application, and details are not repeatedly described here.

A person skilled in the art may further be aware that, units and algorithm steps of each example described in combination with the embodiments disclosed here may be implemented by electronic hardware, computer software, or a combination of the two. In order to clearly describe interchangeability between the hardware and the software, compositions and steps of each example have been generally described according to functions in the foregoing description. Whether the functions are executed by hardware or software depends on particular applications and design constraint conditions of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each specific application. However, it should not be considered that this implementation goes beyond the scope of the embodiments of the present invention.

The methods or algorithm steps described in combination with the embodiments disclosed here may be directly implemented by using hardware, a software module executed by a processor, or a combination of the two. The software module may be located in a random access memory (RAM), a memory, a read only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any storage medium that is in another form and is well-known in the art.

The foregoing description of the disclosed embodiments enables a person skilled in the art to implement or use the embodiments of the present invention. Multiple kinds of modifications to the embodiments are obvious to a person skilled in the art, and general principles defined here may be implemented in other embodiments without departing from the spirit or scope of the embodiments of the present invention. Therefore, the embodiments of the present invention are not limited to the embodiments described here but fall within the broadest scope in line with the principle and novel features disclosed here.

The foregoing description is merely exemplary embodiments of the embodiments of the present invention, but is not intended to limit the embodiments of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principles of the embodiments of the present invention shall fall within the protection scope of the embodiments of the present invention.