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 ▄
331
3. The S-GW candidate list from DNS is exhausted
4. The procedure guard timer times out.
This functionality ensures that the calls are not disconnected due to S-GW failure or maintenance.
S-GW Relocation Information Displayed in mme-service session Output
Previous Behavior: Show commands did not show some information related to S-GW relocation procedures.
New Behavior:
show mme-service session full all
now shows S-GW control TEID, MSC_2, MSC_3,
supported codecs and bearer deletion status.
S1-AP Initial Context Setup Failure Handling Enhancements
Previous Behavior: In previous releases, if the eNodeB returns an Initial Context Setup failure during service request
procedure, the MME would detach the UE without signaling to the eNodeB and UE.
procedure, the MME would detach the UE without signaling to the eNodeB and UE.
If the eNodeB returned an Initial Context Setup failure during a TAU procedure, the MME would move the UE to IDLE
MODE without signaling to the eNodeB and UE.
MODE without signaling to the eNodeB and UE.
New Behavior: The behavior of the MME for this scenario is now configurable.
For Initial Context Setup failure during a service request or extended service request, the MME can now move the UE
to idle mode (instead of detaching the UE), as well as configure a list of cause codes that would move the UE to
ECM_IDLE.
to idle mode (instead of detaching the UE), as well as configure a list of cause codes that would move the UE to
ECM_IDLE.
For Initial Context Setup failure during a TAU procedure, the MME can now detach the UE (instead moving the UE to
idle mode), as well as configure a list of cause codes that would detach the UE.
idle mode), as well as configure a list of cause codes that would detach the UE.
SCTP Template - SCTP Max In Streams and Max Out Streams
Previous Behavior: Max in-streams and max out-streams in MME service can be configured 1-16 by associating an
SCTP parameter template.
SCTP parameter template.
New Behavior: Max in-streams and max out-streams in MME service is restricted to 2-16. When the SCTP parameter
template is associated to MME service with in-streams or out-streams configured as 1, value 2 will be applied.
template is associated to MME service with in-streams or out-streams configured as 1, value 2 will be applied.
SGs Architecture Enhancements: Intelligent EMM Information Delivery
Previous Behavior: Currently the MME provides the EMM Network Identity and Time Zone (NITZ) information twice
in the case where SGs is present. This occurs because the MME delivers the EMM information (based on its own
settings) early in the attach cycle, immediately following the security procedures and prior to initiation of LU towards
the MSS over SGs. Since the MSS also delivers EMM information shortly (~200-300ms) following delivery of the
attach accept, the MME subsequently passes the new EMM information to the UE.
in the case where SGs is present. This occurs because the MME delivers the EMM information (based on its own
settings) early in the attach cycle, immediately following the security procedures and prior to initiation of LU towards
the MSS over SGs. Since the MSS also delivers EMM information shortly (~200-300ms) following delivery of the
attach accept, the MME subsequently passes the new EMM information to the UE.
New Behavior: In cases when the UE performs combined registration, the MME now can be configured to give a
preference to the NITZ information as configured on the MME, or give preference to the information received from the
MSC.
preference to the NITZ information as configured on the MME, or give preference to the information received from the
MSC.
If no preference is indicated, the MME performs as indicated in the Previous Behavior section.
If MME information is given preference, the MME shall always send its information, and ignore any MM
Information messages send by the MSC.
If the MSC information is given preference, in cases where a successful Location Update is performed to a MSC,
the MME shall NOT send MME configured information to the UE, and shall transmit only MSC send
information. In cases where a Location Update procedure is not required (for example, for UE that are
information. In cases where a Location Update procedure is not required (for example, for UE that are