METHOD AND APPARATUS FOR CONTROLLING BEARERS OF SERVICE DATA FLOWS

• US 20090016344A1
• Filed: 09/24/2008
• Published: 01/15/2009
• Est. Priority Date: 03/27/2006
• Status: Abandoned Application

• Current Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: Sun, Chengzhen, Duan, Xiaoqin, Li, Ming, Hu, Huadong, Liu, Lan
• Application Number:
  US12/236,860
• Publication Number:
  US 20090016344A1
• Time in Patent Office: Days
• US Class Current: 370/389
• CPC Class Codes: H04L 47/41 by acting on aggregated flows or links
• CPC Class Codes: H04W 28/0263 involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
• CPC Class Codes: H04W 28/0268 using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] negotiating SLA or negotiating QoS H04W28/24
• CPC Class Codes: H04W 76/15 Setup of multiple wireless link connections
• CPC Class Codes: H04W 76/22 Manipulation of transport tunnels
• CPC Class Codes: H04W 80/04 Network layer protocols, e.g. mobile IP [Internet Protocol]

Abstract

Embodiments of the present invention provide a method and apparatus for controlling bearers of service data flows, including acquiring a service data flow convergence of service data flows, determining whether the service data flow convergence is able to be multiplexed to an established bearer, and carrying the service data flow convergence in a corresponding bearer according to the determined result. The apparatus of the present invention includes a service data flow convergence acquiring module and a service data flow convergence multiplex handling module for implementing the method of the present invention. In accordance with the method and apparatus of the present invention, it is possible to reduce the bearer information amount necessary to be maintained by various network entities and save the storage and handling resources of system.

Claims

1. A method for controlling bearers of service data flows, comprising:

acquiring, by a policy and charging enforcement function entity, a service data flow convergence; and

determining whether the service data flow convergence is able to be multiplexed to an established bearer, and carrying the service data flow convergence in a bearer according to the determining result.

2. The method of claim 1, wherein the acquiring the service data flow convergence comprises:

performing a convergence operation towards the service data flows with the same user equipment identity in the multiple service data flow corresponding to multiple Policy and Charging Control, PCC, rules according to the related attributes in the multiple PCC rules to acquire the service data flow convergence, upon receiving the multiple PCC rules.

3. The method of claim 2, wherein the related attributes comprise at least one of the three items:

Quality of Service, QoS, class, priority and bandwidth.

4. The method of claim 1, wherein the acquiring the service data flow convergence comprises:

receiving a PCC rule corresponding to the service data flow convergence, wherein the PCC rule is obtained by performing a convergence operation towards the service data flows by a policy and charging rule function entity and sent from the policy and charging rule function entity.

5. The method of claim 1, wherein the bandwidth of the service data flow convergence is the sum of bandwidth of all service data flows converged;

the priority of the service data flow convergence is the priority of the service data flow with the highest priority requirement in all service data flows converged;

the service data flow template of the service data flow convergence is a set of flow filters of all service data flows converged.

6. The method of claim 1, wherein the acquiring the service data flow convergence comprises:

taking, by the policy and charging enforcement function entity, the service data flow corresponding to a PCC rule as a service data flow convergence upon receiving the PCC rule.

7. The method of claim 1, wherein the determining whether the service data flow convergence is able to be multiplexed to the established bearer and carrying the service data flow convergence in the bearer according to the determining result comprises:

determining whether the service data flow convergence is able to be multiplexed to the established bearer;

modifying the established bearer and carrying the service data flow convergence in the modified bearer if the service data flow convergence is able to be multiplexed to the established bearer;

otherwise, initiating a new bearer establishment procedure, and carrying the service data flow convergence in the newly established bearer.

8. The method of claim 2, wherein the determining whether the service data flow convergence is able to be multiplexed to the established bearer and carrying the service data flow convergence in the bearer according to the determining result comprises:

determining whether the service data flow convergence is able to be multiplexed to the established bearer;

modifying the established bearer and carrying the service data flow convergence in the modified bearer if the service data flow convergence is able to be multiplexed to the established bearer;

otherwise, initiating a new bearer establishment procedure, and carrying the service data flow convergence in the newly established bearer.

9. The method of claim 4, wherein the determining whether the service data flow convergence is able to be multiplexed to the established bearer and carrying the service data flow convergence in the bearer according to the determining result comprises:

determining whether the service data flow convergence is able to be multiplexed to the established bearer;

modifying the established bearer and carrying the service data flow convergence in the modified bearer if the service data flow convergence is able to be multiplexed to the established bearer;

otherwise, initiating a new bearer establishment procedure, and carrying the service data flow convergence in the newly established bearer.

10. The method of claim 1, wherein determining whether the service data flow convergence is able to be multiplexed to the established bearer comprises:

determining whether the service data flow convergence corresponding to a PCC rule received is able to be multiplexed to the established bearer according to the related attributes in the PCC rule and/or operator policies.

11. The method of claim 10, wherein the related attributes comprises:

QoS class, priority or the combination of multiple service data flow attributes.

12. The method of claim 7, wherein the modifying the established bearer comprises:

adding service data flow template information of the service flow convergence to the Traffic Flow Template information of the established bearer to form new Traffic Flow Template information of the modified bearer; and

adding the bandwidth requirement of the service flow convergence to the bandwidth attributes of the established bearer to form the bandwidth attributes of the modified bearer.

13. The method of claim 7, wherein the initiating a new bearer establishment procedure comprises:

establishing a new bearer through adapting the new bearer establishment procedure initiated by the network or a user.

14. An apparatus for controlling bearers of service data flows, comprising:

a service data flow convergence acquiring module adapted to acquire the service data flow convergence of service data flows, and transmit the service data flow convergence; and

a service data flow convergence multiplex handling module adapted to determine whether the service data flow convergence transmitted by the service data flow convergence acquiring module is able to multiplexed to an established bearer, and carry the service data flow convergence in a bearer according to the determining result.

15. The apparatus of claim 14, wherein the service data flow convergence acquiring module performs a convergence operation towards the received service data flows according to the related attributes of the service data flows, and acquires the service data flow convergence of the service data flows.

16. The apparatus of claim 14, wherein the service data flow convergence multiplex handling module comprises:

an established bearer multiplex handling module adapted to initiate a modification procedure of the established bearer and carry the service data flow convergence in the modified bearer when the service data flow multiplex handling module determines that the service data flow convergence is able to be multiplexed to the established bearer; and

a newly established bearer multiplex handling module adapted to initiate a procedure for establishing a new bearer and carrying the service data flow convergence in the newly established bearer when the service data flow multiplex handling module determines that the service data flow convergence is unable to be multiplexed to the established bearer.

17. The apparatus of claim 15, wherein the service data flow convergence multiplex handling module comprises:

an established bearer multiplex handling module adapted to initiate a modification procedure of the established bearer and carry the service data flow convergence in the modified bearer when the service data flow multiplex handling module determines that the service data flow convergence is able to be multiplexed to the established bearer; and

a newly established bearer multiplex handling module adapted to initiate a procedure for establishing a new bearer and carrying the service data flow convergence in the newly established bearer when the service data flow multiplex handling module determines that the service data flow convergence is unable to be multiplexed to the established bearer.