Patent Description:
A policy and charging rules function (Policy and Charging Rule Function, PCRF) device generates and authorizes a policy and charging control (Policy and Charging Control, PCC) rule for a data flow according to factors such as an operator policy, user network access constraints, user subscription data, and service information of a data flow of an application service that is currently being performed by the user, and the PCC rule usually includes a data flow identifier (flow template) and QoS (Quality of Service, QoS) information corresponding to a data flow corresponding to the data flow identifier. After generating the PCC rule, the PCRF device installs the PCC rule on a policy and charging enforcement function (Policy and Charging Enforcement Function, PCEF) device. The PCEF device binds the data flow to a bearer according to quality of service in the PCC rule, and this type of PCC rule is referred to as a dynamic rule. In addition, there is another type of PCC rule referred to as a non-dynamic rule (also referred to as a predefined PCC rule), the PCRF knows authorized QoS information and identifier of authorized rule, and the PCRF can activate this type of rule. The PCRF adds the identifier of the rule to an activation message sent to the PCEF device, but the PCRF cannot change the QoS information in the rule.

Generally, one bearer includes one or more service data flows. The PCEF needs to perform an operation for binding the data flow to a bearer according to a PCC rule, that is, to determine a bearer at which the service data flow is located. A basic binding rule is to bind service data flows whose QoS parameters (QCI/ARP) in the PCC rule are the same to a same bearer. Otherwise, service data flows corresponding to different QoS parameters cannot be bound to a same bearer. In this way, when a data flow corresponding to a dynamic PCC rule and a data flow corresponding to a non-dynamic PCC rule are bound to a same bearer, if the PCRF performs an operation for changing a QoS parameter (QCI\ARP) on the dynamic PCC rule, a changed QoS parameter is different from the original QoS parameter. Therefore, the QoS parameter in the dynamic PCC rule is different from that in the non-dynamic PCC rule. In this way, two data flows that separately correspond to the original dynamic PCC rule and the non-dynamic PCC rule need to be bound to two different bearers. In this case, a quantity of bearers in a system is increased.

However, in some cases, the PCRF may temporarily change the QoS parameter in the dynamic PCC rule or a QoS parameter of a default bearer, and after a period of time, a current QoS parameter may be restored to the original QoS parameter. For example, in a service that provides prior access to a network for some government officials or emergency management officials when a natural disaster such as an earthquake causes network congestion, the system improves QoS of a bearer of a specific user according to a priority of the user, and further provides a high-priority service for the user. In this case, an increment of the quantity of bearers in the system because of a change of QoS in the dynamic PCC rule is unnecessary. In the transient process, bearers are increased in the system, and system maintenance costs are increased.

3GPP Document TS <NUM>, V12. <NUM>, specifies the overall stage <NUM> level functionality for Policy and Charging Control that encompasses the following high level functions for IP CANs (e.g. GPRS, I WLAN, Fixed Broadband, etc.): Flow Based Charging for network usage, including charging control and online credit control, for service data flows and application traffic; and Policy control (e.g. gating control, QoS control, QoS signalling, etc.). It specifies the Policy and Charging Control functionality for Evolved 3GPP Packet Switched domain, including both 3GPP accesses (GERAN/UTRAN/E-UTRAN) and Non-3GPP accesses, according to TS <NUM> and TS <NUM>. It specifies functionality for unicast bearers. Broadcast and multicast bearers, such as MBMS contexts for GPRS, are out of scope of 3GPP Document TS <NUM> V12.

<CIT> discloses a service processing method, a service processing system, and a PCRF entity to overcome the defect that its prior art is unable to handle services discriminatively according to the policy context information when different services require the same QoS level. The method includes: receiving bearer priority information from a PCRF entity, where the bearer priority information includes: bearer priority information of a service data stream, bearer priority information of an IP-CAN session, and/or bearer priority information of an IP-CAN bearer; and handling services according to the bearer priority information. The policy context information is converted into bearer priority information so that the PCEF handles services according to the bearer priority information. In this way, different services that require the same QoS level are handled discriminatively according to the policy context information.

3GPP Document TS <NUM>, V12. <NUM>, adds detailed flows of Policy and Charging Control (PCC) over the Rx, Gx, Gxx, Sd, Sy and S9 reference points and their relationship with the bearer level signalling flows over the Gn/Gp, S4, S5/S8, S2a and S2c interfaces. It also describes the binding and the mapping of QoS parameters among SDP, UMTS QoS parameters, and QoS authorization parameters; the PCRF addressing using DRA; and Diameter race condition handling for Gx based applications, i.e. Gx, Gxx, Sd and S9.

Embodiments of the present invention provide a method and a device for controlling binding of a data flow to a bearer as defined in the attached claims, so as to decrease system maintenance costs. In this way, a case in which a new bearer is added can be avoided, and system maintenance costs can be further decreased.

The following clearly and completely describes the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are a 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.

It should be understood that, the technical solutions of the embodiments of the present invention may be applied to various communications systems, such as: a Global System for Mobile Communications (English: Global System of Mobile communication, GSM for short) system, a Code Division Multiple Access (English: Code Division Multiple Access, CDMA for short) system, a Wideband Code Division Multiple Access (English: Wideband Code Division Multiple Access, WCDMA for short) system, a general packet radio service (English: General Packet Radio Service, GPRS for short), a Long Term Evolution (English: Long Term Evolution, LTE for short) system, an LTE frequency division duplex (English: Frequency Division Duplex, FDD for short) system, an LTE time division duplex (English: Time Division Duplex, TDD for short), a Universal Mobile Telecommunications System (English: Universal Mobile Telecommunication System, UMTS for short), a Worldwide Interoperability for Microwave Access (English: Worldwide Interoperability for Microwave Access, WiMAX for short) communications system or the like.

<FIG> is a schematic flowchart of a method for controlling binding of a data flow to a bearer according to an embodiment of the present invention. The method in <FIG> may be performed by a PCEF device.

The policy and charging enforcement function PCEF device receives indication information and an identifier of a policy and charging control PCC rule from a policy and charging rules function PCRF device.

For example, the PCEF device receives a re-authentication request (Re-Auth-Request, RAR) message from the PCRF device, and the RAR message carries the indication information and the identifier of the PCC rule. It should be understood that, the RAR message is only one implementation manner of embodiments of the present invention, and an implementation manner for implementing the embodiments of the present invention by using another message to carry the indication information and the identifier of the PCC rule shall fall within the protection scope of the embodiments of the present invention.

The PCEF device binds, to a target bearer according to the indication information, a data flow indicated by an identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule.

For example, when binding, to the target bearer, the data flow indicated by the identifier of the data flow in the PCC rule corresponding to the identifier of the PCC rule, the PCEF device performs bearer binding according to the indication information, instead of performing bearer binding by using the PCC rule directly according to a bearer binding rule.

In the method according to this embodiment of the present invention, when a QoS parameter of a dynamic PCC rule is changed, a PCRF device sends indication information and an identifier of the PCC rule to a PCEF device. Then, the PCEF device performs, according to the indication information, bearer binding of a data flow indicated by an identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule. In this way, a case in which a new bearer is added can be avoided, and system maintenance costs can be further decreased.

Optionally, in one embodiment, the indication information includes a target QoS parameter, service information, or an identifier of the target bearer. For example, the service information may be priority service information.

In an embodiment, when binding, to the target bearer according to the indication information, the data flow indicated by the identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule, the PCEF device first changes a QoS parameter in the PCC rule corresponding to the identifier of the PCC rule to the target QoS parameter in the indication information. In this case, the PCEF device binds, to the target bearer according to a changed PCC rule, the data flow indicated by the identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule.

For example, the indication information includes the target QoS parameter. After receiving the indication information, the PCEF device first changes a QoS parameter of a corresponding PCC rule to the target QoS parameter; and then binds, to a bearer that has a same QoS (QCI\ARP) parameter according to a changed PCC rule, the data flow indicated by the identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule.

Optionally, in another embodiment, when the PCEF device binds, to the target bearer according to the indication information, the data flow corresponding to the identifier of the PCC rule, the PCEF device changes a QoS parameter in the PCC rule indicated by the identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule to a QoS parameter corresponding to the service information in the indication information. Then, the PCEF device binds, to the target bearer according to a changed PCC rule, the data flow corresponding to the identifier of the PCC rule.

For example, the indication information includes the service information. After receiving the indication information, the PCEF device first changes a QoS parameter of a corresponding PCC rule to the QoS parameter corresponding to the service information; and then binds, to a bearer that has a same QoS (QCI\ARP) parameter according to a changed PCC rule, the data flow indicated by the identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule.

Optionally, in another embodiment, when the PCEF device binds, to the target bearer according to the indication information, the data flow indicated by the identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule, the PCEF device binds the data flow corresponding to the identifier of the PCC rule to the bearer corresponding to the identifier of the target bearer in the indication information.

For example, the indication information includes the identifier of the target bearer. After receiving the indication information, the PCEF device directly binds, to the target bearer, the data flow indicated by the identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule, without changing the QoS parameter of the PCC rule. Optionally, in another embodiment, the identifier of the target bearer includes an identifier of a default bearer.

Optionally, in another embodiment, when binding, to the target bearer according to the indication information, the data flow indicated by the identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule, the PCEF device first changes a QoS parameter in the PCC rule corresponding to the identifier of the PCC rule to the target QoS parameter in the indication information. In this case, the PCEF device binds, to the target bearer according to a changed PCC rule, the data flow indicated by the identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule.

For example, the indication information includes the identifier of the target bearer. After receiving the indication information, the PCEF device directly binds, to the target bearer, the data flow indicated by the identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule, without changing the QoS parameter of the PCC rule.

Optionally, in another embodiment, the identifier of the target bearer includes an identifier of a default bearer.

There are two types of bearers in a system: the default bearer and a dedicated bearer. The default bearer is the first bearer when a user establishes a PDN connection. The dedicated bearer is another bearer different from the default bearer. The default bearer always exists during the PDN connection, and after the default bearer is deactivated, the PDN connection is also deactivated at the same time. If there is only one PDN connection in the system, after the PDN connection is deactivated, the user is detached.

Therefore, the PCEF device directly binds the data flow corresponding to the identifier of the PCC rule to the default bearer, so as to avoid adding a new bearer.

<FIG> is a schematic flowchart of a method for controlling binding of a data flow to a bearer according to another embodiment of the present invention. The method in <FIG> may be performed by a PCRF device.

The policy and charging rules function PCRF device generates indication information, where the indication information includes a target QoS parameter, service information, or an identifier of a target bearer.

For example, when a QoS parameter of a dynamic PCC rule is changed, the PCRF device generates indication information according to a changed dynamic rule, so as to instruct bearer binding of a data flow corresponding to a predefined PCC rule whose QoS parameter is the same as that of the dynamic PCC rule before the change. The service information may be priority service information.

For another example, the changed QoS parameter of the dynamic PCC rule is used as the target QoS parameter, and a PCEF device is instructed to change the QoS parameter of the corresponding predefined PCC rule to the target QoS parameter. Alternatively, if a priority service causes the change of the QoS parameter of the dynamic PCC rule, the service information (for example, an identifier of the priority service or corresponding QoS parameter information) is directly used as the indication information. Alternatively, a bearer identifier corresponding to the changed dynamic PCC rule is directly used as the identifier of the target bearer, and the PCEF device is instructed to directly bind the data flow to the target bearer.

The PCRF device sends an identifier of a PCC rule and the indication information to a policy and charging enforcement function PCEF device, so that the PCEF device binds, to the target bearer according to the indication information, a data flow indicated by an identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule.

For example, the PCRF device sends an RAR message to the PCEF device, and the RAR message carries the indication information and the identifier of the PCC rule. It should be understood that, the RAR message is only one implementation manner of embodiments of the present invention, and an implementation manner for implementing the embodiments of the present invention by using another message to carry the indication information and the identifier of the PCC rule shall fall within the protection scope of the embodiments of the present invention.

In the method according to this embodiment of the present invention, when a QoS parameter of a dynamic PCC rule is changed, a PCRF device sends indication information and an identifier of the PCC rule to a PCEF device. Then, the PCEF device performs, according to the indication information, bearer binding of a data flow corresponding to the identifier of the PCC rule. In this way, a case in which a new bearer is added can be avoided, and system maintenance costs can be further decreased.

Optionally, in one embodiment, the identifier of the PCC rule includes an identifier of a predefined PCC rule.

<FIG> is a schematic flowchart of a method for controlling binding of a data flow to a bearer according to another embodiment of the present invention. The method in <FIG> may be performed by a PCEF device.

The policy and charging enforcement function PCEF device receives, from a policy and charging rules function PCRF device, indication information for changing a QoS parameter of a default bearer.

If there is a data flow (for example, in the default bearer, there is one or more data flows that use a predefined PCC rule) corresponding to the predefined PCC rule in the default bearer before the QoS parameter of the default bearer is changed, the PCEF device binds the data flow corresponding to the predefined PCC rule to the default bearer.

For example, if there is a data flow corresponding to the predefined PCC rule in the default bearer before the QoS parameter of the default bearer is changed, when the data flow corresponding to the predefined PCC rule is subsequently bound, the data flow is still bound to the default bearer, instead of a new bearer established for the data flow.

Optionally, the PCEF may notify the PCRF of a QoS parameter in a PCC rule indicated by an identifier of the current PCC rule, and/or identifier information of a bearer in which a data flow is located, where the data flow is indicated by an identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule. For example, the identifier of the PCC rule and/or a bearer identifier and/or QoS parameter information or the like is included in a re-authentication answer message.

In the method according to this embodiment of the present invention, when a QoS parameter of a default bearer is changed, a PCEF device still binds a data flow corresponding to a predefined PCC rule to the default bearer. In this way, a case in which a new bearer is added can be avoided, and system maintenance costs can be further decreased. Optionally, in one embodiment, when binding the data flow corresponding to the predefined PCC rule to the default bearer, the PCEF device first determines whether a changed QoS parameter of the default bearer belongs to a preset specific parameter range.

When the PCEF device determines that the changed QoS parameter of the default bearer belongs to the specific QoS parameter range, the PCEF device binds the data flow corresponding to the predefined PCC rule to the default bearer.

<FIG> is a schematic block diagram of a policy and charging enforcement function device according to an embodiment of the present invention. A PCEF device <NUM> includes a receiving unit <NUM> and a processing unit <NUM>.

The receiving unit <NUM> is configured to receive indication information and an identifier of a policy and charging control PCC rule from a policy and charging rules function PCRF device.

For example, the PCEF device receives an RAR message from the PCRF device, and the RAR message carries the indication information and the identifier of the PCC rule. It should be understood that, the RAR message is only one implementation manner of embodiments of the present invention, and an implementation manner for implementing the embodiments of the present invention by using another message to carry the indication information and the identifier of the PCC rule shall fall within the protection scope of the embodiments of the present invention.

The processing unit <NUM> is configured to bind, to a target bearer according to the indication information, a data flow indicated by an identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule.

Optionally, in another embodiment, the processing unit <NUM> is specifically configured to: change a QoS parameter in the PCC rule corresponding to the identifier of the PCC rule to the target QoS parameter in the indication information; and bind, to the target bearer according to a changed PCC rule, the data flow indicated by the identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule.

Optionally, in another embodiment, the processing unit <NUM> is specifically configured to: change a QoS parameter in the PCC rule corresponding to the identifier of the PCC rule to a QoS parameter corresponding to the service information in the indication information; and bind, to the target bearer according to a changed PCC rule, the data flow indicated by the identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule.

Optionally, in another embodiment, the processing unit <NUM> is specifically configured to bind the data flow indicated by the identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule to the bearer corresponding to the identifier of the target bearer in the indication information.

<FIG> is a schematic block diagram of a policy and charging rules function device according to an embodiment of the present invention. A PCRF device <NUM> includes a generation unit <NUM> and a sending unit <NUM>.

The generation unit <NUM> is configured to generate indication information, where the indication information includes a target QoS parameter, service information, or an identifier of a target bearer.

For example, when a QoS parameter of a dynamic PCC rule is changed, the PCRF device generates indication information according to a changed dynamic rule, so as to instruct bearer binding of a data flow corresponding to a predefined PCC rule whose QoS parameter is the same as that of the dynamic PCC rule before the change.

The sending unit <NUM> is configured to send an identifier of a PCC rule and the indication information to the policy and charging enforcement function PCEF device, so that the PCEF device binds, to the target bearer according to the indication information, a data flow indicated by an identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule.

<FIG> is a schematic block diagram of a policy and charging enforcement function device according to another embodiment of the present invention. A PCEF device <NUM> includes a receiving unit <NUM> and a processing unit <NUM>.

The receiving unit <NUM> is configured to receive, from a policy and charging rules function PCRF device, indication information for changing a QoS parameter of a default bearer.

The processing unit <NUM> is configured to: if there is a data flow (for example, in the default bearer, there is one or more data flows that use a predefined PCC rule) corresponding to the predefined PCC rule in the default bearer before the QoS parameter of the default bearer is changed, bind the data flow corresponding to the predefined PCC rule to the default bearer.

For example, if there is a data flow corresponding to the predefined PCC rule in the default bearer before the QoS parameter of the default bearer is changed, when subsequently binding the data flow corresponding to the predefined PCC rule, the processing unit <NUM> still binds the data flow to the default bearer, instead of a new bearer established for the data flow.

In the method according to this embodiment of the present invention, when a QoS parameter of a default bearer is temporarily changed, a processing unit <NUM> still binds a data flow corresponding to a predefined PCC rule to the default bearer. In this way, a case in which a new bearer is added can be avoided, and system maintenance costs can be further decreased.

Optionally, in one embodiment, the processing unit <NUM> is specifically configured to: when the PCEF device determines that a changed QoS parameter of the default bearer belongs to a specific QoS parameter range, bind the data flow corresponding to the predefined PCC rule to the default bearer.

For example, when binding the data flow corresponding to the predefined PCC rule to the default bearer, the PCEF device first determines whether the changed QoS parameter of the default bearer belongs to a preset specific parameter range. When the PCEF device determines that the changed QoS parameter of the default bearer belongs to the specific QoS parameter range, the processing unit <NUM> binds the data flow corresponding to the predefined PCC rule to the default bearer.

<FIG> is a schematic block diagram of a policy and charging enforcement function according to another embodiment of the present invention.

A policy and charging enforcement function device <NUM> in <FIG> may be configured to implement steps and methods in the foregoing method embodiments. In this embodiment of <FIG>, the policy and charging enforcement function device <NUM> includes a processor <NUM>, a memory <NUM>, and an interface <NUM>. The processor <NUM> controls an operation of the device <NUM>, and may be configured to process a signal. The processor <NUM> may be referred to as a CPU (Central Processing Unit, central processing unit). The memory <NUM> may include a read-only memory and a random access memory, and provide an instruction and data for the processor <NUM>. A part of the memory <NUM> may further include a nonvolatile random access memory (NVRAM). A transmitter circuit <NUM> and a receiver circuit <NUM> may be coupled to the interface <NUM>. Components of the device <NUM> for controlling wear leveling of a storage device group are coupled together by using a bus system <NUM>, and in addition to a data bus, the bus system <NUM> includes a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are marked as the bus system <NUM> in the figure.

Specifically, the memory <NUM> may store an instruction for enabling the processor <NUM> to perform the following operations:
receiving indication information and an identifier of a policy and charging control PCC rule from a policy and charging rules function PCRF device; and binding, to a target bearer according to the indication information, a data flow indicated by an identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule.

Optionally, in one embodiment, the memory <NUM> may further store an instruction for enabling the processor <NUM> to perform the following operation.

The indication information includes a target QoS parameter, service information, or an identifier of the target bearer. Optionally, in another embodiment, the memory <NUM> may further store an instruction for enabling the processor <NUM> to perform the following operations:
when the data flow indicated by the identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule is bound to the target bearer according to the indication information, changing a QoS parameter in the PCC rule corresponding to the identifier of the PCC rule to the target QoS parameter in the indication information; and binding, to the target bearer according to a changed PCC rule, the data flow indicated by the identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule.

Optionally, in another embodiment, the memory <NUM> may further store an instruction for enabling the processor <NUM> to perform the following operations:.

Optionally, in another embodiment, the memory <NUM> may further store an instruction for enabling the processor <NUM> to perform the following operation.

The identifier of the target bearer includes an identifier of a default bearer.

<FIG> is a schematic block diagram of a policy and charging rules function device according to another embodiment of the present invention.

A policy and charging rules function device <NUM> in <FIG> may be configured to implement steps and methods in the foregoing method embodiments. In this embodiment of <FIG>, the policy and charging rules function device <NUM> includes a processor <NUM>, a memory <NUM>, and an interface <NUM>. The processor <NUM> controls an operation of the device <NUM>, and may be configured to process a signal. The processor <NUM> may be referred to as a CPU (Central Processing Unit, central processing unit). The memory <NUM> may include a read-only memory and a random access memory, and provide an instruction and data for the processor <NUM>. A part of the memory <NUM> may further include a nonvolatile random access memory (NVRAM). A transmitter circuit <NUM> and a receiver circuit <NUM> may be coupled to the interface <NUM>. Components of the device <NUM> for controlling wear leveling of a storage device group are coupled together by using a bus system <NUM>, and in addition to a data bus, the bus system <NUM> includes a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are marked as the bus system <NUM> in the figure.

Specifically, the memory <NUM> may store an instruction for enabling the processor <NUM> to perform the following operations:
generating indication information, where the indication information includes a target QoS parameter, service information, or an identifier of a target bearer; and sending an identifier of a PCC rule and the indication information to a policy and charging enforcement function PCEF device, so that the PCEF device binds, to the target bearer according to the indication information, a data flow indicated by an identifier of the data flow in the PCC rule indicated by the identifier of the PCC rule.

The identifier of the PCC rule includes an identifier of a predefined PCC rule.

<FIG> is a schematic block diagram of a policy and charging enforcement function device according to another embodiment of the present invention.

Specifically, the memory <NUM> may store an instruction for enabling the processor <NUM> to perform the following operations:
receiving, from a policy and charging rules function PCRF device, indication information for changing a QoS parameter of a default bearer; and if there is a data flow corresponding to a predefined PCC rule in the default bearer before the QoS parameter of the default bearer is changed, binding the data flow corresponding to the predefined PCC rule to the default bearer.

In the method according to this embodiment of the present invention, when a QoS parameter of a default bearer is changed, a PCEF device still binds a data flow corresponding to a predefined PCC rule to the default bearer. In this way, a case in which a new bearer is added can be avoided, and system maintenance costs can be further decreased. Optionally, in one embodiment, the memory <NUM> may further store an instruction for enabling the processor <NUM> to perform the following operation:
when the data flow corresponding to the predefined PCC rule is bound to the default bearer and the PCEF device determines that a changed QoS parameter of the default bearer belongs to a specific QoS parameter range, binding the data flow corresponding to the predefined PCC rule to the default bearer.

It should be understood that sequence numbers of the foregoing processes do not mean execution sequences in various embodiments of the present invention. The execution sequences of the processes should be determined according to functions and internal logic of the processes, and should not be construed as any limitation on the implementation processes of the embodiments of the present invention.

A person of ordinary skill in the art may be aware that, in combination with the examples described in the embodiments disclosed in this specification, units and algorithm steps may be implemented by electronic hardware, computer software, or a combination thereof. To clearly describe the interchangeability between the hardware and the software, the foregoing has generally described compositions and steps of each example according to functions.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented through some interfaces.

A part or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments of the present invention.

When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of the present invention essentially, or the part contributing to the prior art, or all or a part of the technical solutions may be implemented in the form of a software product. The software product is stored in a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, a server, or a network device) to perform all or a part of the steps of the methods described in the embodiments of the present invention. The foregoing storage medium includes: any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (Read-Only Memory, ROM for short), a random access memory (Random Access Memory, RAM for short), a magnetic disk, or an optical disc.

Claim 1:
A method for controlling binding of a data flow to a bearer, comprising:
sending, by a
policy and charging rules function device, a target Quality of Service ,QoS, parameter, and a identifier of a policy and charging control, PCC, rule to a policy and charging enforcement function,
receiving (<NUM>), by the policy and charging enforcement function device (<NUM>), indication information and the identifier of the PCC rule from the policy and charging rules function device (<NUM>), wherein the indication information comprises the target QoS parameter and the PCC rule is indicated by the received identifier of the PCC rule;
changing, by the policy and charging enforcement function device (<NUM>), a QoS parameter in the PCC rule to the target QoS parameter,
binding, by the policy and charging enforcement function device (<NUM>), to a target bearer according to the changed PCC rule, a data flow indicated by the identifier of the data flow in the PCC rule.