Cisco Cisco Packet Data Gateway (PDG) Veröffentlichungshinweis
MME Changes in Release 15.0
MME Enhancements for September 30, 2013 ▀
Cisco ASR 5x00 Release Change Reference ▄
327
The MME now supports MSC pools for load balancing and intelligent selection of MSC servers based on PLMN
and/or IMSI hash values. Up to 24 MSC servers can now be defined per MME service.
The MME now allows an administrator to place one or more MSC server in maintenance mode. This action
removes the MSC server as a possible selection target.
Support for IMS Centralized Service call handling as specified in 3GPP TS 29.280, enabling call flow handling
for advanced scenarios.
Support for GTP echo path management messages as defined in 3GPP TS 29.280.
Support for Emergency call support.
Modified MME Features
This section identifies MME features modified in release 15.0.
Configurable Cause Code Mapping Enhancements
For the errors that are encountered during EMM procedures, the cause codes sent by the MME dictate actions on the
UE. This feature provides improved flexibility and finer control of UE behavior during error conditions
UE. This feature provides improved flexibility and finer control of UE behavior during error conditions
Previous Behavior: The MME allowed configuration of EMM cause codes for the following conditions:
APN mismatch
Congestion
New call policy restriction
Restricted zone code.
New Behavior: The following additional conditions can now be mapped to specific cause codes at the Call Control
Profile level and the MME Service level:
Profile level and the MME Service level:
Authentication failure
Context transfer from MME failure
Context transfer from SGSN failure
HSS unavailable
GW not reachable
No active bearers
Peer node resolution failure
P-GW selection failure
S-GW selection failure
VLR down and VLR unreachable condition cause codes are also now configurable in at the MME Service level in this
release.
release.
Deactivate Bearer Request During Additional PDN Disconnect
Previous Behavior: When a target eNodeB sends a path switch request, the MME did not send a deactivate bearer
request to the new eNodeB even though the PDN disconnect request is sent to the MME.
request to the new eNodeB even though the PDN disconnect request is sent to the MME.
New Behavior: In this scenario, the MME will not send a Deactivate Bearer Request.