UGW9811

Security Level : Internal Use
UGW9811
Bandwidth Management
www.huawei.com
Copyright © 2012 Huawei Technologies Co., Ltd. All rights reserved.

Contents
1. Requirement So urces
2. Implementation Principles
3. Application Scenarios
4. Flow Chart
5. Configuration Examples
6. Commissioning Location
7. Troubleshooting
8. FAQ
Copyright © 2012 Huawei Technologies Co., Ltd. All rights reserved. Page2
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.
The preceding
requirements are
divided into the
following:
 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
Copyright © 2012 Huawei Technologies Co., Ltd. All rights reserved. Page 3
Contents
1. Requirement Sources
4. Flow Chart
7. Troubleshooting
8. FAQ
Implementation Principle 1: Division of Subscribers
into User Groups
User-group
global User-group
User-profile
default
XX
User-group User-group
APN
A
APN A
B XXX
APN B
APN B User-profile
N
 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.
 Related commands:
user-group { user-group-name [priority priority-value] | default }
binding { apn apn-name | user-profile user-profile-name }
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 processed
based 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
} { {uplinkbwm-controller | downlinkbwm-controller }* | bwm-controller } } | {bwm-rule-name
bwm-servicebwm-service-name {subscriber | group} { { uplinkbwm-controller | downlinkbwm-controller }* | bwm-controller } [ rat { utran |
geran | wlan | gan } | roaming { home | roaming | visiting } | time-range-service
time-range-service-name ]* prioritypriority-value }}
Implementation Principle 3: Flow Control
Based on ToS or Non-ToS
BWM
ToS (Type of Service) BWM-rule
ToS is a standard field in IP packet headers. The BWM

bandwidth management module executes different flow group-default |
subscriber- BWM- bwm- Group|subscr Time-
Up|down priority
control actions based on the value of the TOS field in default service controller iber range
the header of received IP packets processed by the tos | Category- car | shaping |
Priority is
defined
property | L 7- remark based on
DPI 
module.
ToS value: The IP packet header contains eight RAT Roaming
bits. IP precedence uses
protocol | protocol-
bit 0 to the user
group group
bit 2, and ToS uses bit 3 to bit 6. Bit 7 is reserved. The meanings of bits of the ToS
 Remark
Non-ToS
value are as follows:
Non-TOS refers to services that are defined according
 Bits 0-2: Precedence Action-List
to layer 3/4
and
Bit layer 7 information
3: 0=Normal of packets,
Delay, 1=Lowl7-Delay
protocol, and l7-protocol-group.
 Bit These services1=High
4: 0=Normal Throughput, are Throughput
Action- Category-
Property Property
classified intoBit

Related category-property, l7-protocol,1=High
5: 0=Normal Reliability,
commands: and l7- Reliability
 Bits
protocol-group
bwm-rule { {6-7:
on the ExplicitCategory-property
GGSN. Congestion
{ group-default Notification
is the} { {uplink
| subscriber-default bwm-controller | downlinkbwm-controller }* | bwm-
Category-Group
Category-group is flexibly bound to
label that the DPI
controller } } module of the GGSN
| {bwm-rule-name attaches
bwm-service to
bwm-service-name {subscriber | group
the layer}3/4
{ or
{ layer
uplink
7 bwm-controller
configuration |
flows. downlink
L7-protocol and l7-protocol-group
bwm-controller are directly
}* | bwm-controller } [ rat { utran | geran Rule| wlan | gan }of |theroaming
DPI module. { home | roaming | visiting
User-Profile
configured and not relatedtime-range-service-name
} | time-range-service to the configuration of the ]* prioritypriority-value } }
DPI module.
bwm-rule-globalbwm-rule-name bwm-servicebwm-service-name { { uplinkbwm-controller | downlinkbwm-

Copyright
controller © 2012 Huawei Technologies
}* | bwm-controller Co., Ltd. All rights
} time-range-service reserved.
time-range-service-name Page 7
prioritypriority-value
Implementation Principle 4: Time Range,
Location, and Other Control Conditions
 Control conditions such as time range, RAT, roaming, uplink/downlink, and priority
are defined in bwm-rule. Control policies are switched when the time range or
location is changed.
BWM-rule
group-default |
subscriber- BWM- Group|subscr Up|down Time- bwm- priority
default service iber range controller
tos | Category- car | shaping |

property | L7- remark
protocol | protocol- RAT Roaming
group
Related commands: Matching Matching Matching

conditions results priority
bwm-rule { { { group-default | subscriber-defaultuplink
} { { bwm-controller | downlinkbwm-controller }* | bwm-controller } } | {bwm-
rule-name bwm-servicebwm-service-name {subscriber | group } {uplink
{ bwm-controller | downlinkbwm-controller }* | bwm-
controller } [ rat { utran | geran | wlan | gan } | roaming { home | roaming | visiting } | time-range-service
time-range-service-name ]*
prioritypriority-value }}
Implementation Principle 5: Control
Actions
 Control actions are classified into car, shaping, and remark.
BWM-rule
group-default |
subscriber- BWM- Group|subscr Time- bwm-
Up|down priority
default service iber range controller
tos | Category- car | shaping|

group
Matching Matching Matching

conditions results priority
Related commands:
bwm-controllerbwmc-name { { car cir cir-value [ cbs cbs-value ] [ pirpir-value [ pbs pbs-value ] ] [ green { pass | dropremark
| dscp-
name | dscp-value } | yellow { pass | drop | remark
dscp-name | dscp-value } | red { pass | drop | remark
dscp-name | dscp-value }]*}|
{ shapingrate rate-value [ queue-depthqueue-depth-value ]}}
Full Flow Principle
1. 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 and Rule Subscriber-level User group-level

classification by means of DPI matching bandwidth control bandwidth control
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 subscribers
Global User group Subscriber
Services
Contents
4. Flow Chart
7. Troubleshooting
8. FAQ
Typical Scenario 1: Combined Application
of DPI + BWM on the UGW9811
BWM-rule
BWM module
group-default |
Up|down priority
default service controller iber range

group
Remark
Action-List
Action- Category-
Property Property
DPI module
Category-Group
Rule
Typical Scenario 2: Separate
Application of BWM on the UGW9811
BWM-rule
BWM module
group-default |
Up|down priority

group
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 (TOS or 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. PCC combined solution
A typical application scenario of

the UGW + PCRF bandwidth
management solution is FUP
Contents
4. Flow Chart
7. Troubleshooting
8. FAQ
Flow Chart for BWM Bandwidth
Management The data packet arrives
Is the no-ToS service

No type (determining whether Yes
the packet is f orwarded)
conf igured f or
bwm-service-type?
The ToS value in the packet is The packet is resolved to obtain
Is bandwidth control
matched with the ToS value in Yes based on the subscriber category-id and 7-protocol.
bwm-service. level and of ToS type?
The packet is matched with

Subscriber-levelbandwidth bwm-rule of subscriber type
control is perf ormed based on No under user group.
the bwm-controller subscriber
packet with the corresponding
TOS value.
Whether to match
No Yes No
Is bandwidth control based bwm-rule?
on the subscriber level
and of ToS type?
Is the drop action Bwm-controller is obtained Is subscriber-def ault
specif ied f or the packet in Yes
and attached to a quintuple conf igured f or the user
bwm-controller?
Yes node of the subscriber. group?
No
The ToS value in the packet
is matched with the ToS
value in bwm-service. Subscriber-levelbandwidth
control is perf ormed based Subscriber-levelbandwidth
on the CAR or shaping action control is not perf ormed f or the
in bwm-controller. subscriber.
Subscriber-levelbandwidth
control is perf ormed based on
the bwm-controller subscriber
packet with the
corresponding TOS value.
No Is the drop action specif ied
No f or the packet in Yes
bwm-controller?
Is the drop action specif ied
f or the packet in
bwm-controller?
The packet is matched with
Yes Is subscriber-def ault
bwm-rule of subscriber type in conf igured f or the
the user group. user group?
No
No
Subscriber-levelbandwidth
control is perf ormed based on
the CAR or shaping action in Subscriber-level
bwm-controller. bandwidth control is not
Yes
perf ormed f or the
Is global bandwidth control subscriber.
Yes
available?
No
The ToS value in the packet is

matched with the ToS value Is the drop action specif ied
in bwm-service. f or the packet in
Yes bwm-controller?
Subscriber-level bandwidth control is

perf ormed based on the bwm- No
controller subscriber packet under
the corresponding ToS value.
Is the drop action specif ied f or

No
the packet in bwm-controller?
The packet is f orwarded.
Yes
The packet is discarded. Yes
End
Contents
4. Flow Chart
7. Troubleshooting
8. FAQ
Configuration Logic for Bandwidth Management
TOS services are configured by running bwm-related commands.
Service-view BWM-rule
Max = 50
group-default |
Group|subscr BWM- Time-
priority User-Group Max = 50 iber
subscriber-
service priority Up|down bwm-
default range controller
tos | Category- Priority is Controllers

property | L7- defined in four time car |
protocol | protocol- RAT Roaming based on ranges can shaping |
APN User- group the user be bound to remark
profile group. bwm-rule.
Association of Bandwidth Management
Configuration
BWM
BWM-rule
group-default |
Up|down priority
Priority is
tos | Category- car | shaping | defined
property | L7- remark based on
the user
group group.
Remark
Action-List
Action- Category-
Property Property
Category-Group
Rule
User-Profile
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).
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.
Service Planning
User Group
User group name ug-bwm
User group priority 1
Subscriber under APN

huawei
bound to the user group
Subscriber level; non -ToS
Service type
services
Service Planning (Continued)
bwm-service
Service name my-bwm-service1
Type of l7-protocol p2p
time-range-service
Time-range service name trs-idle
Periodic time range 01:00-06:00
Absolute time range daily
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
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 bc-up-max

specified time range
Downlink bwm-controller in the bc-dn-max

specified time range
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 2 Configure 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
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 an
absolute 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
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
Contents
4. Flow Chart
7. Troubleshooting
8. FAQ
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
License Are Enabled
 Support of bandwidth control
PDP context numbers of supporting service control and bandwidth management = 1000000
 Support of DPI fu nctional 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
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
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
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
Contents
4. Flow Chart
7. Troubleshooting
8. FAQ
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 tos be
[UGW-service-user-group-ug_test] bwm-service-typesubscriber tos
[UGW-service-user-group-ug_test] bwm-service-typegroup non-tos
[UGW-service-user-group-ug_test] bwm-rule br_test bwm-service bs_test
group uplink bc-up downlink bc-
down priority 1
 The CAR action does not take effect because the values of cbs and pbs
in the configured bwm-controller are too small. The cbs and pbs
parameters are not used to control bandwidth but control the token
bucket size. The default value (100000) is recommended. Parameter
configuration is not required.
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 srcinal 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.
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.
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 T OS services.
Contents
4. Flow Chart
7. Troubleshooting
8. FAQ
FAQ
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.
Current activated bandwidth management PDP contexts (APN) 134840235
Average 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
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.
Thank you
www.huawei.com

UGW9811

Uploaded by

Copyright:

Available Formats

UGW9811

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

UGW9811

Uploaded by

Copyright:

Available Formats

What are the implementation principles of bandwidth management?

What are the implementation principles of bandwidth management?

What are some application scenarios of bandwidth management?

What are some application scenarios of bandwidth management?

Security Level : Internal Use

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

 Three types of user groups

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

bwm-rule-globalbwm-rule-name bwm-servicebwm-service-name { { uplinkbwm-controller | downlinkbwm-

tos | Category- car | shaping |

Related commands: Matching Matching Matching

tos | Category- car | shaping|

Matching Matching Matching

Service identification and Rule Subscriber-level User group-level

tos | Category- car | shaping |

tos | Category- car | shaping |

A typical application scenario of

Is the no-ToS service

The packet is matched with

The ToS value in the packet is

Subscriber-level bandwidth control is

Is the drop action specif ied f or

The packet is f orwarded.

The packet is discarded. Yes

TOS services are configured by running bwm-related commands.

tos | Category- Priority is Controllers

1. Confirm that the license supports the bandwidth management

User group name ug-bwm

User group priority 1

Subscriber under APN

Service name my-bwm-service1

Type of l7-protocol p2p

Time-range service name trs-idle

Periodic time range 01:00-06:00

Absolute time range daily

Uplink bwm-controller name bc-up-p2p

cir-value 100 kbit/s

pir-value 700 kbit/s

Uplink bwm-controller name bc-up-max

cir-value 300 kbit/s

pir-value 1000 kbit/s

Downlink bwm-controller name bc-dn-p2p

cir-value 100 kbit/s

pir-value 600 kbit/s

Downlink bwm-controller name bc-dn-max

cir-value 300 kbit/s

pir-value 5000 kbit/s

bwm service my-bwm-service1

Uplink bwm-controller bc-up-p2p

Uplink bwm-controller in the bc-up-max

Downlink bwm-controller in the bc-dn-max

 Step 4 Configure a user group.

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

 Step 6 Configure a service type.

 Step 7 Configure the subscriber-based bandwidth control rule.

1. Check bandwidth-related items in the license.

 Support of DPI fu nctional items required by services for which bandwidth

 Support of the shaping bandwidth control method (not recommended for

 Support of sending of bandwidth control policies from the PCRF

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