CISCO-GGSN-QOS-MIB Table View

This table represents the mapping for different 
QoS classes to TOS precedence classes in the IP 
header. 
          
If cggsnQosMappingMethod is set to delay(3),
the length of the table is 4 with the following 
default mapping: delay1 = 3 (flash), delay2 = 2 (immediate),
delay3 = 1 (priority), delay_besteffort = 0 (routine).
          
If cggsnQosMappingMethod is set to canonical(2),
the length of the table is 3 with the following 
default mapping: premium = 2 (immediate), normal
= 1 (priority), best_effort = 0 (routine).
           
If cggsnQosMappingMethod is set to umts(4) or none(1),
the table will be empty.

This table represents the mapping between a given traffic 
class and the corresponding DS PHB group. 
          
The table has one entry for each possible traffic class type.
          
The table will be empty if the cggsnQosMappingMethod is not 
set to 'umts'.

This table represents the DiffServ Code Point (DSCP) 
mappings for different types of DiffServ PHB groups. 
          
The table has one entry for each possible DS PHB.

Call Admission Control (CAC) is to ensure that network 
resources are not oversubscribed to protect real-time traffic 
such as voice (conversational) and video (streaming), etc. 
Therefore before admitting a new PDP create, call admission 
control will be performed to ensure there is sufficient 
resource for the new PDP create request.
          
This table contains policy profiles (containing all the QOS
parameter needed for the PDP activation) which can be attached 
to the one or more APN.
          
The SNMP entity adds a conceptual row to this table when
the user configures a policy profile.
          
The SNMP entity deletes a conceptual row from this table when
the user removes the policy profile. However, if there is
an APN associated with this policy, the conceptual row cannot
be deleted.
          
The SNMP entity modifies the conceptual row when the user
changes any QOS parameters of the profile. However, if there 
are existing PDP contexts in the APN which is using this 
policy, the maximum QOS parameter can only be changed to 
greater or higher than previous configuration.

This table defines Maximum Bit Rate and/or Guaranteed Bit rate
that can be allowed for each traffic class in both uplink and
downlink directions. For the IMS PDP context, this parameter is
taken from authorized QoS obtained from PDF.
          
The SNMP entity creates a conceptual row when the user
configures the MBR/GBR for a particular traffic class with
either uplink or downlink traffic type and there must be a 
corresponding conceptual row existing in 
cggsnUmtsQosCacPolicyTable.
          
The SNMP entity deletes the conceptual row(s), when the user
deletes the MBR/GBR configuration or the corresponding 
conceptual row is deleted from cggsnUmtsQosCacPolicyTable. 
However, if some PDP context is active in the APN using this 
policy, then the conceptual row(s) cannot be deleted.
          
The SNMP entity modifies the conceptual row, when the user
changes the MBR/GBR value or the optional reject parameter. 
However, if any PDP context is active in the APN using this
policy, then the MBR/GBR value can be changed to higher than
the previously configured.

This table defines allocation of virtual bandwidth pool for
the traffic classes. Basically there are two types of bandwidth
pool, Physical & Virtual. Physical bandwidth is the egress
interface bandwidth. It is not supported and will not be 
explained more.
          
Virtual bandwidth is user defined bandwidth. Virtual bandwidth 
provides an easy and flexible way to implement bandwidth pool 
for call admission control to avoid physical bandwidth 
limitations. In contrast to per-interface based physical 
bandwidth management, Virtual bandwidth management is per-APN 
based, that is, each APN has its own pool to admit request.  
To use this type of bandwidth, user needs to make assumption of 
what interface type and total bandwidth of Gi and Gn in both 
directions to allocate bandwidth for each class.
          
The SNMP entity creates a conceptual row when the user
configures the bandwidth pool with some bandwidth value in the
range described in cggsnUmtsQosCacBWPoolBWVal.
          
The SNMP entity deletes the conceptual row, when the user
deletes the bandwidth pool. However, if the bandwidth pool is 
associated with an APN or if bandwidth is currently been
utilized, then the conceptual row cannot be deleted.
          
The SNMP entity modifies the conceptual row, when the user
changes the bandwidth value. However, if any PDP context is 
active in the APN using this pool, then the bandwidth value 
can be changed to higher than the previously configured.

This table is the sub table of cggsnUmtsQosCacBWPoolTable.
This contains all the traffic class bandwidth allocation in
percentage or absolute value. The total value of the 
bandwidth allocated for different traffic class per pool
must not exceed 100 percent or the absolute 
value (4294967295).
          
The SNMP entity creates a conceptual row when the user 
configures the bandwidth allocation for the traffic class 
defined in cggsnQosBWPoolTrafClass and if the corresponding 
conceptual row is present in cggsnUmtsQosCacBWPoolTable.
          
The SNMP entity deletes the conceptual row(s) when the user
unconfigures the bandwidth allocation for the traffic class
or the corresponding conceptual row is deleted from
cggsnUmtsQosCacBWPoolTable. However, if there are active PDP
in the APN using this pool, then the conceptual row cannot
be deleted.
          
The SNMP entity modifies the conceptual row when the user
changes the bandwidth allocation for a traffic class. However,
if there are active PDPs in the APN using this pool, then only
value greater than previous allocation is accepted.