Cisco Cisco ASR 5700
APN Profile Configuration Mode
▀ qos class
▄ Command Line Interface Reference, StarOS Release 17
1534
Repeat the command as often as needed with different options to define all required QoS criteria. For
example, to configure the maximum bit rate (MBR) for the downlink and uplink directions for a traffic class,
this command must be used twice, specifying
example, to configure the maximum bit rate (MBR) for the downlink and uplink directions for a traffic class,
this command must be used twice, specifying
mbr-down
once and
mbr-up
once.
Advantage for local mapping of MBR: some HLRs cannot be configured with high MBR values. Using the
mbr-map-up
and the
mbr-map-down
parameters allows the SGSN to be configured to treat a specific
HLR value as meaning the desired high MBR value. In a case where the HLR does not support HSPA+ bit
rates, but the handsets and network do, this feature allows the operator to overcome limitations on the HLR
and provide HSPA+ bit rates by overwriting the provisioned HLR-QoS MBR values with SGSN-configured
values. When MBR mapping is configured, if QoS is preferred as the HLR value, then the subscription QoS
MBR received from the HLR is compared with the "from" value in the table. If it matches, then it is
converted to the value specified by the "to" value in the table. QoS negotiation happens based on the
converted value.
Advantage for QoS capping with THP and ARP: Controlling THP and ARP via Operator Policy: This
functionality can differentiate home vs. roaming subscribers, and prevent visiting subscribers from receiving
a high-tiered service. For example, a service provider could offer service differentiation using
Ultra/Super/Standard service levels based upon QoS; this could justify charging a corporate customer more to
use the Internet APN than would be charged to a consumer. This could be accomplished by controlling the
traffic handling priority (THP) over the air interface, i.e. THP 1 = Ultra, THP 2 = Super and THP 3 =
Standard.
rates, but the handsets and network do, this feature allows the operator to overcome limitations on the HLR
and provide HSPA+ bit rates by overwriting the provisioned HLR-QoS MBR values with SGSN-configured
values. When MBR mapping is configured, if QoS is preferred as the HLR value, then the subscription QoS
MBR received from the HLR is compared with the "from" value in the table. If it matches, then it is
converted to the value specified by the "to" value in the table. QoS negotiation happens based on the
converted value.
Advantage for QoS capping with THP and ARP: Controlling THP and ARP via Operator Policy: This
functionality can differentiate home vs. roaming subscribers, and prevent visiting subscribers from receiving
a high-tiered service. For example, a service provider could offer service differentiation using
Ultra/Super/Standard service levels based upon QoS; this could justify charging a corporate customer more to
use the Internet APN than would be charged to a consumer. This could be accomplished by controlling the
traffic handling priority (THP) over the air interface, i.e. THP 1 = Ultra, THP 2 = Super and THP 3 =
Standard.
Example
Use the following command to configure the entire conversational traffic class with predefined QoS options:
qos class conversational all-values
Now change the background class ARP from 3 to 2:
qos class background arp 2
Invalidate the THP parameter, by removing all value from the parameter, for the interactive class:
remove qos class interactive thp