The MME provides an enhanced congestion control and overload control feature set.
This feature builds on the base congestion control functionality provided on the MME. Refer to the Congestion Control and Overload Control sections in the MME Overview chapter for more information about the basic functionality.
To use this feature, you need a valid license key (MME Resiliency) installed. Contact your Cisco Account or Support representative for information on how to obtain a license.
Enhanced Congestion Control and Overload Control
- System CPU usage
- System service CPU usage (Demux-Card CPU usage)
- System Memory usage
- License usage
- Maximum Session per service
- Drop or reject the following S1-AP/NAS messages: S1 Setup, Handover events, TAU request, Service request, PS-Attach request, Combined-attach request, Additional PDN request, or UE initiated bearer resource allocation.
- Allow voice or emergency calls/events.
- Initiate S1AP
overload start to a percentage of eNodeBs with options to signal any of the
following in the Overload Response IE:
- reject non-emergency sessions
- reject new sessions
- permit emergency sessions
- permit high-priority sessions and mobile-terminated services
- reject delay-tolerant access.
Relationships to Other Features
This license-enabled feature builds on the base congestion control functionality provided on the MME.
Refer to the Congestion Control and Overload Control sections in the MME Overview chapter for more information about the basic functionality.
Additional information is also provided in the Congestion Control chapter in the System Administration Guide.
- Port-specific RX and TX utilization
- Port RX and TX utilization
- Message queue utilization
- Message queue wait time
The license-enabled Enhanced Congestion Control funtionality on the MME does not support the monitoring of these resources using three different threshold levels (critical, major and minor). Only a single threshold level (critical) can be monitored for these resources.