owd090922(slide) ugw9811 v900r009c01 bandwidth management-20120319-b-v1 1

5/23/2018 OWD090922(Slide) UGW9811 V900R009C01 Bandwidth Management-20120319-B-V1 1

1/44

www.huawei.com

Copyright 2012 Huawei Technologies Co., Ltd. All rights reserved.

UGW9811

Bandwidth Management

Security Level : Internal Use


2/44Copyright 2012 Huawei Technologies Co., Ltd. All rights reserved. Page2

Contents

1. Requirement Sources

2. Implementation Principles

3. Application Scenarios

4. Flow Chart

5. Configuration Examples

6. Commissioning Location

7. Troubleshooting

8. FAQ


3/44

Copyright 2012 Huawei Technologies Co., Ltd. All rights reserved. Page 3

Requirement Sources P2P services occupy too much bandwidth and therefore affect the QoS of other services.

Operators hope that service control and bandwidth management can be performed for

the traffic of P2P and VoIP services to prevent the services from occupying too much

bandwidth resources. In this way, bandwidth resources are shared among applications in

a fair way, and user experience is improved.

Support of service control and bandwidth management for P2P and VoIP services at the granularities of

integrated equipment, APN, user group, and subscriber

Support of service control and bandwidth management for P2P and VoIP services based on time range,

traffic direction, RAT, Location, and Roaming Support of change in service control and bandwidth management for P2P and VoIP services with

change in RAT

The preceding

requirements are

divided into thefollowing:


4/44

Copyright 2012 Huawei Technologies Co., Ltd. All rights reserved. Page4

Contents




4. Flow Chart



7. Troubleshooting

8. FAQ


5/44


Implementation Principle 1: Division of Subscribers

into User Groups

Three types of user groups

user-group XXX: It is a self-defined user group. It must be manually added and bound to

the APN or user profile. The homing user group of a subscriber is determined based on

user group priority when a subscriber belongs to two self-defined user groups.

user-group default: It must be manually added. The subscribers that are contained in the

user-group default group are fixed; they are the subscribers that are not included in the

self-defined user groups of the GGSN.

user-group global: It is created by the system and contains all subscribers on the GGSN,

or GGSN integrated equipment.

User-group

A

User-group

B

User-group

default

User-group

global

APN AAPN B

APN BUser-profile

N

APN

XXX

User-profileXX

Related commands:

user-group { user-group-name[priority priority-value] | default }

binding { apn apn-name| user-profile user-profile-name}


6/44


Implementation Principle 2: Three-Level Control

Based on Subscriber -> User Group -> Integrated

Equipment

There is an "and" control relationship among the levels of subscriber, user group,and integrated equipment.

For example, the upper limit of the bandwidth is 10 Mbit/s which is defined for user group A.

The user group A contains only one APN: cmwap. The upper limit of the bandwidth for each

subscriber in user group A is 1 Mbit/s. Subscriber-based control is performed when the

number of subscribers that use the cmwap APN to log in a network reaches 20. A maximum

of 1 Mbit/s bandwidth is allocated to each subscriber (excessive packets are processedbased on the defined car and shaping actions). Group-based control is then performed.

Certain subscribers preempt 1 Mbit/s bandwidth, whereas other subscribers preempt less

than 1 Mbit/s bandwidth. The total bandwidth for the 20 subscribers does not exceed 10

Mbit/s. The preemption result indicates the bandwidth that is allocated to each subscriber.

Related commands:

bwm-rule { { { group-default | subscriber-default } { {uplink bwm-contro l le r | downlink bwm-contro l le r }* | bwm-contro l le r } } | { bwm-rule-name

bwm-service bwm-service-name{subscriber | group } { { uplink bwm-contro l le r | downlink bwm-contro l le r }* | bwm-contro l le r } [ rat { utran |

geran | wlan | gan } | roaming { home | roaming | visiting } | time-range-service t ime-range-service-name]* priority priority-value} }


7/44


Implementation Principle 3: Flow Control

Based on ToS or Non-ToS

ToS (Type of Service)

ToS is a standard field in IP packet headers. The BWM

bandwidth management module executes different flow

control actions based on the value of the TOS field in

the header of received IP packets processed by the

DPI module.

Non-ToSNon-TOS refers to services that are defined according

to layer 3/4 and layer 7 information of packets, l7-

protocol, and l7-protocol-group. These services are

classified into category-property, l7-protocol, and l7-

protocol-group on the GGSN. Category-property is the

label that the DPI module of the GGSN attaches to

flows. L7-protocol and l7-protocol-group are directly

configured and not related to the configuration of the

DPI module.

BWM-service

RoamingRAT

bwm-controller Up|down

Group|subscriber

Priority isdefinedbased onthe usergroup

tos | Category-property | L7-

protocol | protocol-group

BWM-rule

priorityTime-range

group-default |subscriber-

default

car | shaping |remark

Rule

Category-Property

Action-Property

Category-Group

Remark

Action-List

BWM

User-Profile

Category-group is flexibly bound to

the layer 3/4 or layer 7 configuration

of the DPI module.

ToS value: The IP packet header contains eight bits. IP precedence uses bit 0 to

bit 2, and ToS uses bit 3 to bit 6. Bit 7 is reserved. The meanings of bits of the ToS

value are as follows:

Bits 0-2: Precedence

Bit 3: 0=Normal Delay, 1=Low Delay

Bit 4: 0=Normal Throughput, 1=High Throughput

Bit 5: 0=Normal Reliability, 1=High Reliability

Bits 6-7: Explicit Congestion NotificationRelated commands:

bwm-rule { { { group-default | subscriber-default } { {uplink bwm-contro l ler | downlink bwm-contro l ler }* | bwm-

contro l ler } } | { bwm-rule-namebwm-service bwm-service-name{subscriber | group } { { uplink bwm-contro l ler |

downlink bwm-contro l ler }* | bwm-contro l ler } [ rat { utran | geran | wlan | gan } | roaming { home | roaming | visiting

} | time-range-service t ime-range-service-name]* priority prior i ty-value } }

bwm-rule-global bwm-rule-namebwm-service bwm-service-name{ { uplink bwm-contro l ler | downlink bwm-

contro l ler }* | bwm-contro l ler } time-range-service t ime-range-service-namepriority prior i ty-value


8/44


Implementation Principle 4: Time Range,

Location, and Other Control Conditions

Control conditions such as time range, RAT, roaming, uplink/downlink, and priorityare defined in bwm-rule. Control policies are switched when the time range or

location is changed.

BWM-service

RoamingRAT

bwm-controllerUp|down

Group|subscriber



BWM-rule

priorityTime-range


default


Matchingconditions

Matchingresults

Matchingpriority

Related commands:

bwm-rule { { { group-default | subscriber-default } { {uplinkbwm-contro l ler | downlinkbwm-contro l ler }* | bwm-contro l ler } } | { bwm-

rule-namebwm-service bwm-service-name{subscriber | group } { { uplinkbwm-contro l ler | downlinkbwm-contro l ler }* | bwm-

contro l ler } [ rat { utran | geran | wlan | gan } | roaming { home | roaming | visiting } | time-range-service t ime-range-service-name]*

priority prior i ty-value }}


9/44


Implementation Principle 5: Control

ActionsControl actions are classified into car, shaping, and remark.

BWM-service

RoamingRAT

bwm-controllerUp|down

Group|subscriber



BWM-rule

priorityTime-range


default

car | shaping|remark

Matchingconditions

Matchingresults

Matchingpriority

Related commands:

bwm-controller bwmc-name{ { carcir cir-value[ cbs cbs-value ] [ pir pir-value[ pbs pbs-value ] ] [ green { pass | drop | remarkdscp-

name| dscp-value } | yellow { pass | drop | remark dscp-name| dscp-value } | red { pass | drop | remark dscp-name| dscp-value } ] * } |

{ shapingrate rate-value[ queue-depth queue-depth-value] } }


10/44


Full Flow Principle1. Services are identified and classified on the DPI module (including layer

3/4 and layer 7).

2. Service matching is implemented based on the user profile, service type,

and traffic property to generate service control policies.

3. Service control is implemented on the user level, user-group level, and

integrated-equipment level.

Service identification andclassification by means of DPI

Rulematching

Subscriber-levelbandwidth control

User group-levelbandwidth control


11/44


Levels of the Service Control Functional

Domain

Bandwidth control and management based on integrated

equipment

Bandwidth control and management based on user groups

Bandwidth control and management based on subscribersSubscriberUser groupGlobal

Services


12/44


Contents




4. Flow Chart



7. Troubleshooting

8. FAQ


13/44


Typical Scenario 1: Combined Application

of DPI + BWM on the UGW9811

BWM-service

RoamingRAT


Group|subscriber

tos| Category-property | L7-

protocol | protocol-

group

BWM-rule

priorityTime-range


default


Rule

Category-Property

Action-Property

Category-Group

Remark

Action-List

BWM module

DPI module


14/44


Typical Scenario 2: Separate

Application of BWM on the UGW9811

BWM-service

RoamingRAT


Group|subscriber



BWM-rule

priorityTime-range


default


BWM module


15/44


Typical Scenario 3: UGW + PCRF

Bandwidth Management Solution UGW9811:

1. The UGW9811 parses data packets of

subscribers.

2. The UGW9811 obtains bandwidth control

polices (rules or user profiles) from the

PCRF over the Gx interface.

3. The BWM module performs bandwidth

(QoS) control for services based on the

parameters (TOSor category-property)input by the DPI module.

PCRF:

1. The PCRF provides the policy management

function.

2. The PCRF sends bandwidth control policies

to the UGW9811 over the Gx interface.

A typical application scenario of

the UGW + PCRF bandwidth

management solution is FUP

PCC combined solution


16/44


Contents




4. Flow Chart



7. Troubleshooting

8. FAQ

Flo Chart for BWM Band idth


17/44


Flow Chart for BWM Bandwidth

Management The data packet arrivesIs the no-ToS service

type (determining whetherthe packet is forwarded)

configured forbwm-service-type?

Yes

The ToS value in the packet is

matched with the ToS value inbwm-service.

Subscriber-level bandwidthcontrol is performed based onthe bwm-controller subscriberpacket with the corresponding

TOS value.

The packet is matched withbwm-rule of subscriber type

under user group.

Whether to matchbwm-rule?

Bwm-controller is obtainedand attached to a quintuple

node of the subscriber.

Yes

Is subscriber-defaultconfigured for the user

group?

No

Yes

No

Subscriber-level bandwidthcontrol is not performed for the

subscriber.

Subscriber-level bandwidthcontrol is performed based

on the CAR or shaping actionin bwm-controller.

Is bandwidth control

based on the subscriberlevel and of ToS type?

No

Yes

The packet is resolved to obtaincategory-id and 7-protocol.

Is the drop action specifiedfor the packet inbwm-controller?

The packet is matched withbwm-rule of subscriber type in

the user group.

Subscriber-level bandwidthcontrol is performed based onthe CAR or shaping action in

bwm-controller.

The ToS value in the packetis matched with the ToSvalue in bwm-service.

Subscriber-level bandwidthcontrol is performed based onthe bwm-controller subscriber

packet with the

corresponding TOS value.

Is bandwidth control basedon the subscriber level

and of ToS type?

Yes

Is the drop actionspecified for the packet in

bwm-controller?

No

No



The ToS value in the packet ismatched with the ToS value

in bwm-service.

Subscriber-level bandwidth control isperformed based on the bwm-

controller subscriber packet underthe corresponding ToS value.

Is global bandwidth controlavailable?

Yes

Is the drop action specified forthe packet in bwm-controller?

No

No

The packet is forwarded.

The packet is discarded.

Yes

Yes

Yes

No

Yes

End

No

No

Is subscriber-defaultconfigured for the

user group?

No

Subscriber-levelbandwidth control is not

performed for thesubscriber.

Yes

No Yes


18/44


Contents




4. Flow Chart



7. Troubleshooting

8. FAQ


19/44


Configuration Logic for Bandwidth Management

TOS services are configured by running bwm-related commands.

User-Group

APN User-profile

BWM-service

Service-view

Max = 50

Max = 50

RoamingRAT

bwm-controller

Up|downGroup|subscr

iber

Priority isdefinedbased onthe usergroup.



BWM-rule

priorityTime-range

prioritygroup-default |

subscriber-default

car |shaping |remark

Controllersin four timeranges canbe bound tobwm-rule.

A i ti f B d idth M t


20/44


Association of Bandwidth Management

Configuration

BWM-service

RoamingRAT


Group|subscriber

Priority isdefinedbased onthe usergroup.



BWM-rule

priorityTime-range


default


Rule

Category-Property

Action-Property

Category-Group

Remark

Action-List

BWM

User-Profile


21/44


Research on Live-Network Deployment

1.Confirm that the license supports the bandwidth management

function.

2.Confirm that the license supports the protocol types for

bandwidth control.

3.Confirm that SIG is correctly loaded for identification of non-

ToS services.

4.Determine the subscriber range of bandwidth control.

5.Determine the services for which bandwidth control is

performed.

6.Determine bandwidth control levels (subscriber, user group,integrated equipment, and PCC control).

7.Determine control policies (time, RAT, and home/roaming).


22/44


Live-Network Deployment: Application

Examples

Application scenario:

Uplink access rate is limited to less than 700 kbit/s and downlink access rate is

limited to 600 kbit/s when subscribers access P2P services. Uplink access rate is

limited to 1000 kbit/s and downlink access rate is limited to 5000 kbit/s at 01:00-06:00 every day.


23/44


Service Planning

User Group

User group name ug-bwm

User group priority 1

Subscriber under APN

bound to the user grouphuawei

Service type

Subscriber level; non-ToS

services


24/44


Service Planning (Continued)

bwm-service

Service name my-bwm-service1

Type of l7-protocol p2p


25/44



time-range-service

Time-range service name trs-idle

Periodic time range 01:00-06:00

Absolute time range daily


26/44


Service Planning (Continued)bwm-controller

Uplink bwm-controller name bc-up-p2p

cir-value 100 kbit/s

pir-value 700 kbit/s

Uplink bwm-controller name bc-up-max



Downlink bwm-controller name bc-dn-p2p



Downlink bwm-controller name bc-dn-max




27/44



bwm-rule

Name of the bandwidth control rule br-p2p

Priority 1

bwm service my-bwm-service1

Uplink bwm-controller bc-up-p2p

Downlink bwm-controller bc-dn-p2p

Uplink bwm-controller in the

specified time range

bc-up-max

Downlink bwm-controller in the

specified time range

bc-dn-max


28/44


Configuration Procedure Step 1 Configure a bwm service.

Define the bwm service by means of l7-protocol.

[UGW-service] bwm-service my-bwm-service1 l7-protocol P2P

Step 2Configure four bwm controllers, which contain the parameter setting of the

CAR action.

# Configure the bwm controller name as bc-up-p2p, with a 100 kbit/s promised rate and 700 kbit/s peak rate.

[UGW-service]bwm-controller bc-up-p2p car cir 100 pir 700 green pass yellow pass red drop

# Configure the bwm controller name as bc-dn-p2p, with a 100 kbit/s promised rate and 700 kbit/s peak rate.

[UGW-service]bwm-controller bc-dn-p2p car cir 100 pir 600 green pass yellow pass red drop

# Configure the bwm controller name as bc-up-max, with a 300 kbit/s promised rate and 1000 kbit/s peak rate.

[UGW-service]bwm-controller bc-up-max car cir 300 pir 1000 green pass yellow pass red drop

# Configure the bwm controller name as bc-dn-max, with a 300 kbit/s promised rate and 1000 kbit/s peak rate.

[UGW-service]bwm-controller bc-dn-max car cir 300 pir 5000 green pass yellow pass red drop


29/44


Configuration Procedure (Continued)

Step 3 Configure a time range.

# Configure the time-range service name as trs-idle, with a periodic time range 01:00-06:00 and anabsolute time range daily.

[UGW-service]time-range-service trs-idle 01:00 to 06:00 daily

Step 4 Configure a user group.

# Configure the user group name as ug-bwm, with a priority 1.

[UGW-service]user-group ug-bwm priority 1

Step 5 Configure subscribers under the APN in the ug-bwm user group.

# Configure subscribers under apn huawei.com in the ug-bwm user group.

[UGW-service-user-group-ug-bwm]binding apn huawei.com

Step 6 Configure a service type.

# Configure a user level and non-ToS services.

[UGW-service-user-group-ug-bwm]bwm-service-type subscriber non-ToS


30/44


Configuration Procedure (Continued)

Step 7 Configure the subscriber-based bandwidth control rule.

# In the ug-bwm user group, create the br-p2p bwm-rule, with the priority 1. Configure uplink and

downlink bwm-controllers for subscribers.

[UGW-service-user-group-ug-bwm]bwm-rule br-p2p bwm-service my-bwm-service1 subscriber uplink

bc-up-p2p downlink bc-dn-p2p priority 1

# Configure the bandwidth control policy of bwm-rule br-p2p for the trs-idle time-range service.

[UGW-service-user-group-ug-bwm]bwm-controller-binding bwm-rule br-p2p time-range-service trs-idle

uplink bc-up-max downlink bc-dn-max


31/44


Contents

1. Requirement Sources2. Implementation Principles


4. Flow Chart



7. Troubleshooting

8. FAQ


32/44


Commissioning Location Procedure

1. Check bandwidth-related items in the license.

2. Check whether the SIG knowledge base is correctly loaded.

3. Check whether bandwidth management is correctly

configured.

Check Whether Related Items in the


33/44


Check Whether Related Items in the

License Are Enabled

Support of bandwidth controlPDP context numbers of supporting service control and bandwidth management = 1000000

Support of DPI functional items required by services for which bandwidth

control is performed (View DPI control items of specified protocols. An

example is provided.)

PDP context numbers of supporting DPI-P2P = 1000000

PDP context numbers of supporting DPI-VOIP = 1000000

Support of the shaping bandwidth control method (not recommended for

commercial operations)

Supporting for shaping = 1000000

Support of sending of bandwidth control policies from the PCRF

PDP context numbers of supporting Gx = 1000000

Check Whether the SIG Knowledge


34/44


Check Whether the SIG Knowledge

Base Is Correctly Loaded

Check whether the SIG knowledge base is correctly loaded.The result for correct loading is as follows:

[UGW-service] display signature-database

Signature database information

------------------------------

signature database version = 1.0.0.105

engine version = SIG-Module V100R001C02SPC006

(Number of results = 1)

The result for loading failure or not loading is as follows:

[UGW-service] display signature-database

Signature database information

------------------------------

None version can be displayed, please first load correct signature database

Check Whether Bandwidth


35/44


Check Whether Bandwidth

Management Is Correctly Configured

Check whether bandwidth management is correctly configured.Display user-group

Display user-group-global

Display bwm-service

Display bwm-rule

Display bwm-rule-global

Display bwm-controller

Check Whether the Configuration


36/44


Check Whether the Configuration

Violates Usage Limits The group-level bwm-rule cannot be bound to the bwm-controller with

the shaping action. The group-level bwm-rule does not take effect

even when the binding is successful. Therefore, the shaping action

cannot be used by group-level control.

Switch between the CAR action and shaping action cannot be

performed for a bwm-controller. Switch between actions takes effect

only by deleting the bwm-controller and adding another one. For

example, the following configuration of directly modifying the control

action of bc1 does not take effect.

bwm-controller bc1 car cir 1000 bwm-controller bc1 shaping rate 128 queue-depth 256


37/44


Contents




4. Flow Chart



7. Troubleshooting

8. FAQ


38/44


Common Configuration Faults

The APN or user profile of subscribers is not bound to a user group.

In a user group, the subscriber/group type specified in bwm-service-type

is not consistent with the subscriber/group type configured in bwm-

service. For example, the following configuration is incorrect.[UGW-service] bwm-service bs_test tosbe

[UGW-service-user-group-ug_test] bwm-service-type subscribertos

[UGW-service-user-group-ug_test] bwm-service-type group non-tos

[UGW-service-user-group-ug_test] bwm-rule br_test bwm-service bs_test groupuplink bc-up downlink bc-

down priority 1

The CAR action does not take effect because the values of cbsand pbs

in the configured bwm-controller are too small. The cbsand pbs

parameters are not used to control bandwidth but control the tokenbucket size. The default value (100000) is recommended. Parameter

configuration is not required.


39/44


Example of Problem Location Problem description:

An FTP bandwidth control test detects that bandwidth control suddenly becomes invalid in FTP services.

Cause analysis:

Bandwidth control takes effect in the beginning and later becomes invalid. Based on control effect analysis,

bandwidth control does not recover after becoming invalid, indicating that bandwidth control becomes invalid

permanently.

The preceding analysis result shows that the problem is not caused by the basic functions of bandwidth control.

The possible causes are: 1. Bandwidth control becomes invalid because of limit to the effective time of

bandwidth control rules. 2. The original bandwidth control rules become invalid because of re-matching of new

services or rules.

Further analysis shows that time range is not configured in all bandwidth control rules. It is suspected that service

re-matching causes the rules to become invalid because only one service type is involved in the test.

Based on packet analysis, the interval between two FTP packets is 32 seconds, which is equal to the deterioration

time for 5-tuple. This causes service re-matching. Service re-matching fails because the SIG cannot identify FTP

services based on FTP data-layer packets. As a result, bandwidth control becomes invalid.


40/44


Constraints and Limits Maximum number of supported user groups: 50 (each user group contains a maximum of 16

APNs or user profiles)

Maximum number of supported services: 500

Maximum number of supported protocol groups: 100 (each protocol group contains a maximum

of 32 protocols)

Maximum number of supported service controllers: 1000

Maximum number of supported rules: 50 rules per user group

Maximum number of supported time ranges: four time ranges per rule (the smallest time

granularity for a time range is 30 minutes) Average number of user-level service controllers: 8; maximum number of user-level service

controllers: 16

Maximal percentage of subscribers for whom bandwidth control is performed: 25%

Protocol identification rate: less than 100%

The group-level bwm-rule cannot be bound to the bwm-controller with the shaping action. The

group-level bwm-rule does not take effect even when the binding is successful.

Switch between the CAR action and shaping action cannot be performed for a bwm-controller.

Switch between actions takes effect only by deleting the bwm-controller and adding another one.


41/44


Constraints and Limits (Continued)

Service control is performed in the subscriber level, user-group level, and

global level. Service control rules for ToS services and non-ToS services

cannot take effect simultaneously in a certain level. The bwm-service-type

command is used to determine which type of service control rules (of ToS

services or non-ToS services) takes effect. Service control rules do not take

effect for online subscribers if the value of bwm-service-type is changed.

Same service controller parameter names map same service controller

instances in a certain level. When multiple bwm-rules use a service

controller parameter template, the traffic that complies with these bwm-rules

shares a service controller instance. Unified service control is performed.

User profile cannot be configured in the service control rules of group-level

or global level TOS services.

C t t


42/44


Contents




4. Flow Chart



7. Troubleshooting

8. FAQ

FAQ


43/44


1. What versions of the UGW9811 support the bandwidth management function?

UGW9811 V900R001C03 and later versions support the bandwidth management function.

2. In what sites the bandwidth management function of the UGW9811 is put to commercial operation?

The bandwidth management function of the UGW9811 has been put to commercial operation in DigiTel(Philippines), M1 (Singapore), and NII (Peru). Sites that enable the FUP function of the PCC also

enable the bandwidth management function of the UGW9811.

3. Are there any alarms related to the bandwidth management function of the UGW9811?

No.

4. Is performance statistics available for the bandwidth management function of the UGW9811?

The following performance counters are available.

5. Are there any precautions for bandwidth management?

The shaping algorithm provides a better result but has a great impact on UGW9811 performance.Therefore, the shaping algorithm is recommended in demonstrating BWM whereas the CAR

algorithm is recommended in deploying BWM on live networks.

Current activated bandwidth management PDP contexts (APN) 134840235Average activated bandwidth management PDP contexts (APN) 134840236

Maximum activated bandwidth management PDP contexts (APN) 134840237

Dropped uplink packets with BWM 134686754

Dropped downlink packets with BWM 134686755

Dropped uplink traffic in KB with BWM 134686756

Dropped downlink traffic in KB with BWM 134686757


44/44

Thank youwww.huawei.com

owd090922(slide) ugw9811 v900r009c01 bandwidth management-20120319-b-v1 1

Documents

user profile

userprofile userprofile

usergroup global

homing user group

user experience

types of user groupsusergroup

theusergroup default

theselfdefined user