Cisco Cisco Packet Data Gateway (PDG)
This release includes enhancements that are applicable to multiple products. The following lists the various
multi-product enhancements sections, some of which might include content applicable to your MME.
multi-product enhancements sections, some of which might include content applicable to your MME.
Important
• AAA Enhancements
• CF Enhancements
• ECS Enhancements
• Firewall Enhancements
• GTPP Enhancements
• Lawful Intercept Enhancements
• MVG Enhancements
• NAT Enhancements
• SNMP MIB Enhancements
• System and Platform Enhancements
Cause Code Mapping for UE-CONTEXT-RELEASE Sent from MME
CSCux13166 - MME releases UE context with Category NAS Unspecified for non-TAU
Feature Changes
Previous Behavior: By default, an MME initiated the UE-CONTEXT-RELEASE with cause
NAS-Normal-Release whenever the MME received a TAU Request over Initial-UE if the UE was in the
connected state.
NAS-Normal-Release whenever the MME received a TAU Request over Initial-UE if the UE was in the
connected state.
CLI was available which allowed the operator to specify the cause code mapping for MME-initiated
S1-UE-CONTEXT-RELEASE whenever the MME received a TAU over Initial-UE message from the eNodeB.
For all non TAU scenarios, MME initiated the UE-CONTEXT-RELEASE with cause NAS/Unspecified by
default whenever it receives any message other than TAU over Initial-UE if its in connected state.
S1-UE-CONTEXT-RELEASE whenever the MME received a TAU over Initial-UE message from the eNodeB.
For all non TAU scenarios, MME initiated the UE-CONTEXT-RELEASE with cause NAS/Unspecified by
default whenever it receives any message other than TAU over Initial-UE if its in connected state.
New Behavior: Now by default, the MME initiates the UE-CONTEXT-RELEASE with cause
NAS-Normal-Release whenever the MME receives a request over Initial-UE (for all TAU and non-TAU
scenarios such as Service Request, Attach, and Extended-Service-Request), if the UE is in the connected state.
NAS-Normal-Release whenever the MME receives a request over Initial-UE (for all TAU and non-TAU
scenarios such as Service Request, Attach, and Extended-Service-Request), if the UE is in the connected state.
The existing CLI has been modified to enable the operator to specify the cause code mapping for the
MME-initiated S1-UE-CONTEXT-RELEASE whenever the MME receives an Initial-UE request message
from the eNodeB, irrespective of the procedure if the UE is in the connected state. CLI changes are explained
in the following section.
MME-initiated S1-UE-CONTEXT-RELEASE whenever the MME receives an Initial-UE request message
from the eNodeB, irrespective of the procedure if the UE is in the connected state. CLI changes are explained
in the following section.
Release Change Reference, StarOS Release 19
183
MME Changes in Release 19
Cause Code Mapping for UE-CONTEXT-RELEASE Sent from MME