- About this Guide
- Mobility Management Entity Overview
- Mobility Management Entity Configuration
- 128K eNodeB Connections
- A-MSISDN Functionality
- Access Restriction based on Regional Zone Code
- APN Override
- Backup and Recovery of Key KPI Statistics
- Cause Code #66
- Cell Broadcast Center - SBc Interface
- Cell Traffic Trace
- Closed Subscriber Groups
- CSFB and SMS over SGs Interface
- CSFB for 1xRTT
- DDN Throttling
- Default APN for DNS Failure
- eDRX Support on the MME
- Emergency Bearer Services
- Enhanced Congestion Control and Overload Control
- Enhanced Multimedia Priority Service (eMPS)
- Enhanced Event Logging
- Foreign PLMN GUTI Management
- GTP-C Load and Overload Control on MME
- GUTI Re-allocation
- Heuristic and Intelligent Paging
- HSS-based P-CSCF Restoration
- Idle-mode Signaling Reduction
- IMSI Manager Overload Control
- IMSI Manager Scaling on the MME
- Integrity and Confidentiality Algorithms for UE
- IPNE Service
- Limiting the Number of SGWs Tried
- Load Balancing and Rebalancing and VoLTE Offloading
- Local Emergency Numbers List
- Location Services
- MBMS for MME (eMBMS)
- Operator Policy
- Operator Specific QCI
- Operator Policy Selection Based on IMEI-TAC
- Overcharging Protection
- Paging Priority IE Support
- Power Saving Mode (PSM) in UEs
- QoS Profile Support
- S13 Additional IMEI Check
- Selective Authentication
- Session Tracing
- SGW Blacklisting on the MME
- SGSN-MME Combo Optimization
- Single Radio Voice Call Continuity
- SRVCC for 1xRTT
- State-Location Information Retrieval Flag
- TAI-based Routing for 20-bit and 28-bit eNB ID
- Timer-based GBR Bearer Deactivation
- UDPC2 Support for MME/SGSN
- UE Relocation
- VLR Management
- Troubleshooting the MME Service
- Monitor the MME Service
- Engineering Rules
128K eNodeB
Connections
The MME supports 128K eNodeB connections for VPC-DI and ASR5500-DPC2 platforms, previously only 64k eNodeB connections were supported.
- Feature Description
- Configuring Rate Limit for S1 SCTP Connections from eNodeB
- Monitoring and Troubleshooting
Feature Description
128K eNodeB Connection Support
The MME now supports 128K eNodeB connections for VPC-DI and ASR5500-DPC2 platforms; it has been enhanced from 64K eNodeB connections. A MME manager instance supports 4K eNodeBs, a minimum of 32 MME managers are required to support 128K eNodeB's. If the network has more than 32 MME managers, 128k eNodeB connections limit is not enforced. The support for 128K eNodeB connections is per chassis and not per MME service.
The maximum number of MME managers that can be configured per chassis for the VPC-DI platform has been enhanced from "24" to "48".
Distribution of Multiple SCTP Association - VLR
The SCTP associations of a VLR are now distributed across MME managers. In previous releases multiple SCTP connections from a VLR were hosted on the same MME manager. Distribution of VLR SCTP associations across MME managers helps in achieving better load distribution at the MME managers.
There is no change for load balancing of SGs messages sent by MME across multiple SCTP associations of a VLR.
S1-SCTP Rate Limiting
The operator can now configure a rate limit for incoming S1 SCTP connections from the eNodeB. This prevents an overload at the MME in case there is a surge of S1 SCTP connections from the eNodeBs. New command keywords s1-sctp rate limit are introduced in the task facility mmedemux command, they can be used to specify the rate limit value of connections per second for the chassis. New MME Demux subsystem statistics are introduced to display the number of packets that are dropped due to the configured rate limit.
Configuring Rate Limit for S1 SCTP Connections from eNodeB
The task facility mmedemux command is updated to include option to configure a rate limit for incoming S1 SCTP connections in MME per chassis.
configure task facility mmedemux { mmemgr-startup-percentage percent_value [ mmemgr-startup-wait-time wait_time ] | s1-sctp rate-limit value } default task facility mmedemux mmemgr-startup-percentage mmemgr-startup-wait-time no task facility mmedemux { mmemgr-startup-percentage mmemgr-startup-wait-time | s1-sctp rate-limit} exit
- By default rate limiting is not imposed on incoming SCTP connections at the MME. Configuring the rate limit is an optional configuration, to prevent overload of MME from surge/burst of S1 SCTP connections from eNodeBs.
- The keyword s1-sctp identifies the MME SCTP interface type.
- The keyword rate-limit is used to configure the rate limit for incoming S1 SCTP connections from eNodeB. The value of the rate limit that can be configured is an integer from 1 up to 65535. Once the rate of incoming S1 SCTP connections exceed the configured value, the SCTP cookie echo packets are dropped by the MME on exceeding the rate limit. The SCTP connection with eNodeB is eventually be established after retries/retransmission by the eNodeB. The statistics of the dropped S1 SCTP packets are collected and displayed as part of MME Demux subsystem statistics.
Example:
The following CLI command configures rate-limit of 100 S1 SCTP connections per second for a chassis:
task facility mmedemux s1-sctp rate-limit 100
Verifying the Configuration
The configuration of this feature can be verified using the following show commands. Execute the show configuration command to verify the configuration, the output displays the following parameters based on the configuration:
Monitoring and Troubleshooting
This section provides information on the show commands available to support this feature.
Show Command(s) and/or Outputs
The following parameter is added to the output generated by the show session subsystem facility mmedemux all command to display statistics for this feature.
Feedback