Congestion is detected based on various threshold-configurable parameters, such as (but not limited to) system CPU utilization, system memory utilization, service CPU utilization. This feature enables the operator to determine the SGSN's response to various congestion scenarios.
The MTC Congestion Control functionality gives the operator control over the congestion threshold settings and the actions taken in response to congestion. The operator defines a set of congestion actions in a congestion-action-profile. The selected actions are executed when congestion is detected.
- General congestion control - applicable only for Mobility Management messages.
- APN-based congestion control for Mobility Management
- APN- based congestion control for Session Management
There are three levels of system-detected congestion: critical, major, and minor. The percentage at which these levels are hit is controlled via threshold configuration.
The operator defines the SGSN's congestion response actions for new calls, active calls, and SM-messages in congestion-action-profiles and association those congestion-action-profiles with the various congestion level.
In addition to system-detected congestion, the SGSN also provides a management option to trigger congestion. This option can be useful when testing system readiness and response.
Other SGSN Features: Low Access Priority Indicator (LAPI) in S-CDRs. The SGSN allows for the use of the LAPI bit in S-CDRs of the custom24 dictionary. Use of this functionality is CLI controlled. For details about this functionality, refer to the GTPP Interface Administration and Reference for StarOS Release 17.
Other Products:While specific operations may vary, MTC Congestion Control functionality is also supported by the MME. For details, refer to the MME Administration Guide for StarOS Release 17