CISCO-GGSN-QOS-MIB: View SNMP OID List / Download MIB

This MIB module manages the Quality of Service parameters of GGSN in a GPRS system. GGSN is the Gateway GPRS Support Node in the GPRS architecture. It provides interworking of GPRS network with external packet-switched networks - PDNs or other data networks. The following diagram illustrates a simplified GPRS logical architecture with the name of inter-node interface: +---------------------------------------------+ | +======+ a PLMN | | | SGSN | | | +======+ | | | | | Gn | | | | |+====+ +====+ +=====+ +======+ +======+ | +===+ || TE |-R-| MT |-| BSS |-| SGSN |-Gn-| GGSN |-|-Gi-|PDN| |+====+ +====+ +=====+ +======+ +======+ | +===+ | | | | | | +----------------------------------------|----+ Gp | +-----------------------------+ | +====+ +=====+ +======+ | | | MS |---| BSS |---| SGSN | | | +====+ +=====+ +======+ | | | | other PLMN | +-----------------------------+ A PDP Context is an information set maintained by MS and GSNs which describes the mobile wireless service call or session. Three types of QoS mapping method are supported on GGSN: canonical, delay and UMTS. Canonical QoS mapping consists of Best Effort, Normal and Premium QoS classes. Delay QoS mapping consists of four classes: delay1, delay2, delay3 and delay-besteffort. UMTS QoS has the following traffic classes: signalling, conversational, streaming, interactive and background. UMTS QoS is based on differentiated services network model. A QoS Profile is associated with each PDP context which defines multiple attributes like precedence, delay, reliability, peak throughput, mean throughput and traffic class. Based on the precedence, delay and mean throughput an user is classified into different canonical and delay QoS classes . Based on delay, jitter, bandwidth and reliability user is classified into the UMTS traffic classes. In GGSN, the QoS remapping mechanism is that, for uplink traffic, the GGSN remaps the TOS in the user traffic before forwarding the packet to the Gi interface and for downlink traffic, the GGSN will only setup the TOS for the IP header for the Tunnel, not the IP header for user traffic. Traffic from MS to PDN is considered as uplink and the reverse is considered as downlink traffic. Acronyms and terms: APN Access Point Name BSS Base Station System ETSI European Telecommunications Standards Institute DS Differentiated Service DSCP DS Code Point GGSN Gateway GPRS Support Node GPRS General Packet Radio Service GSM Global System for Mobile communication GSN GPRS Support Node G-PDU GTP PDU MS Mobile Station MT Mobile Terminal PDN Packet Data Network PDP Packet Data Protocol PDU Protocol Data Unit PHB Per-hop Behavior PLMN Public Land Mobile Network SGSN Serving GPRS support Node TE Terminal Equipment T-PDU the payload of G-PDU UMTS Universal Mobile Telecommunication System IMS IP Multimedia Subsystem GBR Guaranteed Bit Rate MBR Maximum Bit Rate CAC Call Admission Control QOS Quality Of Service REFERENCE [1] GSM 03.60: Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service description; Stage 2. V7.1.0 [2] GSM 09.60: Digital cellular telecommunication system (Phase 2+); General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across Gn and Gp Interface. V7.3.0 [3] 3GPP; Technical Specification Group Services and System Aspects; QoS Concept and Architecture. 3G TS 23.107 v3.2.0. [4] 3GPP; Technical Specification Group Core Network; General Packet Radio Service(GPRS); GPRS Tunnelling Protocol (GTP) across Gn and Gp Interface (Release 1999). 3G TS 29.060 v3.5.0. [5] 3GPP; Technical Specification Group Services and System Aspects; General Packet Radio Service(GPRS); Service description; Stage 2 (Release 1999) 3G TS 23.060 v3.3.1.

This object specifies the type of QoS method (canonical or delay or none (best-effort) or umts) mapped to GPRS QoS. Enumeration: 'delay': 3, 'umts': 4, 'none': 1, 'canonical': 2.

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.

Entry which denotes mapping of different QoS classes to TOS precedence class and also the number of PDP contexts associated with each QoS Class.

This object specifies different QoS Classes of either 'canonical' or 'delay' QoS based on the value set to cggsnQosMappingMethod. The following is how the value needs to be interpreted. If cggsnQosMappingMethod is set to delay(3), 1 - delay1, 2 - delay2, 3 - delay3, 4 - delay_best_effort. If cggsnQosMappingMethod is set to canonical(2), 1 - premium, 2 - normal, 3 - best_effort.

This object specifies the IP TOS precedence to which cggsnQosClass is mapped. Higher TOS precedence value indicates a higher service priority. The values '6 (internetwork_control)' and '7 (network_control)' of TOS are not used in mapping.

This object specifies the current number of PDP contexts that have cggsnQosClass.

The total amount of bandwidth resource on the GGSN, this total depends on various factors like system throughput, memory size, maximum number of PDP contexts supported. A portion of the total resources will be allocated to a user at the PDP context activation time based on the QoS class the user is assigned to. This object can only be retrieved if cggsnQosMappingMethod is set to canonical(2).

The current amount of bandwidth resource used on the GGSN. This object can only be retrieved if cggsnQosMappingMethod is set to canonical(2).

This object specifies the mean throughput deviation factor that the GGSN uses to calculate the allowable data throughput for Premium QoS. This object can only be retrieved if cggsnQosMappingMethod is set to canonical(2).

This object specifies the bandwidth factor to be applied to canonical best-effort QoS class. This object can only be retrieved if cggsnQosMappingMethod is set to canonical(2).

The sum of the mean throughput of premium class QOS users on the GSN. This object can only be retrieved if cggsnQosMappingMethod is set to canonical(2).

The sum of the mean throughput of normal class QOS users on the GSN. This object can only be retrieved if cggsnQosMappingMethod is set to canonical(2).

The sum of the mean throughput of best-effort class QOS users on the GSN. This object can only be retrieved if cggsnQosMappingMethod is set to canonical(2).

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'.

Entry which denotes mapping between a given traffic class and the corresponding DS PHB group and the number of PDP contexts associated with each traffic class.

This object denotes the UMTS QoS traffic class. UMTS QoS uses this parameter to make assumptions about the traffic source, and determine the maximum bitrate, and guaranteed bitrate for the traffic class when performing admission control. The signalling traffic class only applies to the UMTS signalling messages. Enumeration: 'conversational': 2, 'streaming': 3, 'signalling': 1, 'background': 5, 'interactive': 4.

This object denotes the PHB which is mapped to the traffic class given by cggsnQosUmtsTrafficClass. DS architecture is based on number of functional elements, one of which is PHB. PHBs specify queuing, queue management and scheduling characteristics that allow a means of allocating buffer and bandwidth resources at each node among the competing traffic streams. The various DS PHBs include: signalling - signallingClass(1) The signalling class PHB is only used for the UMTS signalling messages. This DS PHB does not apply to any other IP data packets. expedited forwarding - efClass(2) The expedited forwarding PHB is used for providing a low loss, low latency, low jitter, assured bandwidth, end-to-end service through the DS domains. Such a service appears to the endpoints like a point-to-point connection, or a virtual leased line. assured forwarding - afClass(3-6) The assured forwarding PHB provides a means for a provider DS domain to offer different levels of delivery assurances for packets received from a customer DS domain. Four assured forwarding classes: afClass1, afClass2, afClass3 and afClass4 are defined, where each AF class is in each DS node allocated a certain amouont of forwarding resoources(buffer space and bandwidth). IP packets are assigned into one or more of these classes, according to the subscribed service. Within each class the packets are marked by a mobile subscriber, or by the provider DS domain, with one of the three possible drop precedence values. In case of congestion, the drop precedence of a packet determines the relative importance of a packet within the class. Packets in one class are forwarded independently of the packets in another class. best effort - bestEffort(7) This is the default PHB. The packets of this aggregate are forwarded on an output link whenever the link is not required to satisfy any other PHB. Enumeration: 'signallingClass': 1, 'efClass': 2, 'afClass3': 5, 'afClass2': 4, 'afClass4': 6, 'bestEffort': 7, 'afClass1': 3.

This object specifies the current number of PDP contexts associated with each traffic class identified by cggsnQosUmtsTrafficClass.

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.

Entry which denotes mapping of different DS PHBs to the DSCP.

This object denotes the various possible values of PHB. It can take up one of the following values: signallingClass(1) - Signalling class efClass(2) - expedited forwarding class afClass1Low(3) - assured forwarding class 1 low drop precedence afClass1Medium(4) - assured forwarding class 1 medium drop precedence afClass1High(5) - assured forwarding class 1 high drop precedence afClass2Low(6) - assured forwarding class 2 low drop precedence afClass2Medium(7) - assured forwarding class 2 medium drop precedence afClass2High(8) - assured forwarding class 2 high drop precedence afClass3Low(9) - assured forwarding class 3 low drop precedence afClass3Medium(10) - assured forwarding class 3 medium drop precedence afClass3High(11) - assured forwarding class 3 high drop precedence afClass4Low(12) - assured forwarding class 4 low drop precedence afClass4Medium(13) - assured forwarding class 4 medium drop precedence afClass4High(14) - assured forwarding class 4 high drop precedence bestEffort(15) - best effort class Enumeration: 'signallingClass': 1, 'efClass': 2, 'afClass1Medium': 4, 'afClass3High': 11, 'afClass2High': 8, 'afClass2Medium': 7, 'bestEffort': 15, 'afClass4Low': 12, 'afClass4High': 14, 'afClass1High': 5, 'afClass4Medium': 13, 'afClass3Low': 9, 'afClass2Low': 6, 'afClass1Low': 3, 'afClass3Medium': 10.

This object denotes the DSCP for the corresponding PHB defined by cggsnQosDiffServPhb. The values recommended for the various values of cggsnQosDiffServPhb are: signallingClass - '101000' efClass - '101110' afClass1Low - '001010' afClass1Medium - '001100' afClass1High - '001110' afClass2Low - '010010' afClass2Medium - '010100' afClass2High - '010110' afClass3Low - '011010' afClass3Medium - '011100' afClass3High - '011110' afClass4Low - '100010' afClass4Medium - '100100' afClass4High - '100110' bestEffort - '000000'

This object defines if the DSCP in the subscriber datagram will be forwarded in the uplink/downlink path with or without modification. The various values that this object can take up are: up(1) - DSCP will not be modified in the uplink path alone down(2) - DSCP will not be modified in downlink path alone all(3) - DSCP will not be modified in both uplink/downlink path none(4) - DSCP will be modified both in uplink and in downlink path Enumeration: 'down': 2, 'all': 3, 'up': 1, 'none': 4.

This object is to map the IP Multimedia Subsystem (IMS) signaling traffic to one of UMTS traffic class. Only 'interactive' or 'background' traffic class can be set to this object. If the traffic class is set to 'interactive', then the priority has to be set in cggsnUmtsQosMapImsSigTrafHandPri. This object is deprecated as the IMS is not supported from GGSN release 5.0 onwards.

This object is to set the priority of traffic handling for interactive class. This object can be set only if the traffic class is set to 'interactive' in cggsnUmtsQosMapImsSigTrafClass. This object is deprecated as the IMS is not supported from GGSN release 5.0 onwards. Enumeration: 'priority1': 1, 'priority3': 3, 'priority2': 2.

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.

Each entry in this table contains a set of QOS parameter needed for the PDP activation (policy profile).

This object is the CAC policy name which will be attached to one or more APN's.

This object is used to create a new row or delete an existing row in this table. To create a row, set this object to 'createAndGo'. To delete a row, set this object to 'destroy'.

This object defines maximum number of PDPs that can be created. If total number of activated PDPs exceeds the maximum number, the PDP context will be rejected. Value '0' means there is no limit on PDP context creation.

This object defines the threshold value to accept only PDP context with allocation/retention priority 1 when the threshold is reached. This object can be set only when cggsnUmtsQosCacMaxPdp is set to some value and also the this object should have lesser value that cggsnUmtsQosCacMaxPdp. Value '0' means PDP context creation with allocation/retention will not be checked.

This object defines the highest traffic class that can be accepted. If the requested traffic class is higher than configured one, the PDP context create request will be rejected. Traffic class can not be downgraded.

This object defines the priority for the traffic class set in cggsnUmtsQosCacMaxTrafficClass, but this priority is applicable only for traffic class type 'interactive'. If not set, then any priority will be accepted. Enumeration: 'priority1': 1, 'none': 0, 'priority2': 2, 'priority3': 3.

This object defines highest peak throughput class for R97/98 QoS can be accepted in a particular APN. This is used only for GTP v0 PDP or GTP v1 PDP containing R97/98 QoS. If the requested Peak throughput class is higher than highest number, the request will be either downgrade to the value set, or rejected. If this object is not set, it will be mapped to R99 maximum bit rate rules for determining R99 attributes from R97/98 attributes that is defined in 23.107. The Maximum Bit Rate parameter will be applied. If the value is set to '0', then any throughput will be accepted.

This object is used for downgrading or PDP to be rejected when cggsnUmtsQosCacMaxThruPut is set. 'true' - Reject the exceeding max throughput traffic. 'false' - Downgrade to the max throughput value set in cggsnUmtsQosCacMaxThruPut This object can be set to 'true', only when cggsnUmtsQosCacMaxThruPut is set to a non-zero value.

This object defines highest delay class for R97/98 QoS can be accepted in a particular APN. This object is used only for GTP v0 PDP, or GTP v1 PDP containing R97/98 QoS. If Delay class is higher than highest number, the request will be either downgraded to the configured number, or rejected. If this object is not set, the request will be mapped to R99 Interactive or Background traffic class based on the rules for determining R99 attributes from R97/98 attributes that is defined in 23.107. The Highest Traffic Handling Priority will be applied if the class is mapped Interactive traffic class. Enumeration: 'delayClass2': 2, 'delayClass3': 3, 'none': 0, 'delayClass1': 1, 'delayClass4': 4.

This object is used for downgrading or PDP to be rejected when cggsnUmtsQosCacMaxDelayClass is set. 'true' - Reject the exceeding max delay class. 'false' - Downgrade to the max delay class value set in cggsnUmtsQosCacMaxDelayClass This object can be set to 'true', only when cggsnUmtsQosCacMaxDelayClass is set to a delay class.

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.

Entry which has all the details of each traffic class with their MBR/GBR values for uplink/downlink traffic and also the condition for rejecting or downgrading if the requested MBR/GBR exceeds.

This object specifies the UMTS traffic class for which MBR/GBR in uplink/downlink has to be set. When cggsnUmtsQosCacTcBitRateType is set to 'guaranteed', the values 'conversational' and 'streaming' can only be set to this object.

This object specifies the type of bit rate applicable for traffic class denoted by cggsnUmtsQosCacTcTrafClass. Enumeration: 'guaranteed': 2, 'maximum': 1.

This object specifies the direction of traffic. Enumeration: 'downlink': 2, 'uplink': 1.

This object is used to create a new row or delete an existing row in this table. To create a row, set this object to 'createAndGo'. cggsnUmtsQosCacTcBitRate is mandatory object for creating a row. To delete a row, set this object to 'destroy'.

This object specifies the MBR/GBR allowed for the traffic class defined by cggsnUmtsQosCacTcTrafClass. This object is deprecated and replaced by cggsnUmtsQosCacTcRevBitRate. While retrieving the the value of cggsnUmtsQosCacTcBitRate, the maximum value of 16000 will be returned if the value of cggsnUmtsQosCacTcRevBitRate for the same instance exceeds 16000.

This object is to specify whether the requested MBR/GBR be downgraded or PDP to be rejected if the requested MBR/GBR exceeds the value set in cggsnUmtsQosCacTcBitRate. 'true' - The request will be rejected if exceeded. 'false' - The requested MBR will be downgraded if exceeded.

This object specifies the MBR/GBR allowed for the traffic class defined by cggsnUmtsQosCacTcTrafClass.

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.

Each entry in this table holds the total bandwidth that this pool provides and the corresponding allocation to the traffic classes.

This object is the name of the virtual bandwidth pool which will be attached to the APN.

This object is used to create a new row or delete an existing row in this table. To create a row, set this object to 'createAndGo'. To delete a row, set this object to 'destroy'.

This object defines the total bandwidth for this pool. This object is a must while creating a row in this table.

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.

Each entry in this table holds the allocation of bandwidth for a traffic class in percentage or absolute value.

This object defines the traffic class for which the allocation of bandwidth is needed.

This object is used to create a new row or delete an existing row in this table. To create a row, set this object to 'createAndGo'. To delete a row, set this object to 'destroy'.

This object is to specify whether the bandwidth allocation should be considered as percentage or absolute value. If this object is set to 'true', then the bandwidth reserved will be in percentage, given by cggsnQosBWPoolTrafClassPerVal. If this object is set to 'false', then the bandwidth reserved will be in absolute value given by cggsnQosBWPoolTrafClassAbsVal. All the entries can either have the unit as percent or absolute but not both.

This object denotes the percent of bandwidth allocated for the traffic class set in cggsnQosBWPoolTrafClass. This object will be valid and can be set only if cggsnQosBWPoolTrafClassPercent is set to 'true'.

This object denotes the absolute value of bandwidth allocated for the traffic class set in cggsnQosBWPoolTrafClass. This object will be valid and can be set only if cggsnQosBWPoolTrafClassPercent is set to 'false'.

This object denotes the absolute available bandwidth left unused for traffic class set in cggsnQosBWPoolTrafClass.

The compliance statements for entities which implement the CISCO-GGSN-QOS-MIB. This compliance has been deprecated by cggsnQosMIBComplianceRev1.

The compliance statements for entities which implement the CISCO-GGSN-QOS-MIB.

The compliance statements for entities which implement the CISCO-GGSN-QOS-MIB.

The compliance statements for entities which implement the CISCO-GGSN-QOS-MIB. This is deprecated by cggsnQosMIBComplianceRev4.

The compliance statements for entities which implement the CISCO-GGSN-QOS-MIB.

A collection of objects providing general QoS configurations.

A collection of objects specific to Canonical QoS on GGSN.

A collection of objects pertaining to the UMTS QoS on GGSN.

A collection of objects pertaining to the CAC on GGSN. This group is deprecated by cggsnQosUmtsCacGroupRev1.

A collection of objects pertaining to the CAC on GGSN. This is deprecated by cggsnQosUmtsCacGroupRev2.

A collection of objects pertaining to the CAC on GGSN.