Cisco Cisco Packet Data Gateway (PDG)
MME Changes in Release 17
MME Enhancements for 17.4 ▀
Release Change Reference, StarOS Release 17 ▄
263
CSCuu88343 - Emergency PDN Connectivity Request Rejected by MME
Feature Changes
Emergency PDN connectivity Requests After Emergency PDN Connection De-activation
Previous Behavior: For every emergency pdn-connection from the UE, the MME maintains the state of the emergency
session. Once an emergency pdn-connection gets de-activated, any subsequent pdn-connectivity request towards same
APN are rejected by the MME with the cause “Multiple PDN connections not allowed”.
session. Once an emergency pdn-connection gets de-activated, any subsequent pdn-connectivity request towards same
APN are rejected by the MME with the cause “Multiple PDN connections not allowed”.
New Behavior: Once the emergency pdn-connection is de-activated, the session state is accordingly updated at the
MME. PDN connectivity requests that arrive after emergency pdn-connection de-activation are validated and honored
by the MME.
MME. PDN connectivity requests that arrive after emergency pdn-connection de-activation are validated and honored
by the MME.
Customer Impact: The UE is not affected by recurrent emergency pdn-context creation and deletion towards same
APN.
APN.
CSCuv02890 - Enforce license for MTC functionality
Feature Changes
License Control for MTC Functionality
Previous Behavior: The feature specific license was not enforced to use the commands and functionality related to the
optional MTC feature functionality on the SGSN.
optional MTC feature functionality on the SGSN.
New Behavior: With Release 17.4, the MTC Feature license is now enforced to use MTC functions and related
commands. Please speak with your Cisco Customer Representative if you have questions about the MTC Feature
license.
commands. Please speak with your Cisco Customer Representative if you have questions about the MTC Feature
license.
For an idea of the MTC functionality supported by the SGSN, refer to the sections covering CSCum47774,
CSCum50056 in the SGSN Enhancements for 17.1 in this document. For detailed information about the SGSN’s MTC
feature support, refer to the MTC Congestion Control chapter of the SGSN Administration Guide.
CSCum50056 in the SGSN Enhancements for 17.1 in this document. For detailed information about the SGSN’s MTC
feature support, refer to the MTC Congestion Control chapter of the SGSN Administration Guide.
CSCuv21929 - Incorrect Feature-List Bit Set for S6a - ODB-all-OG
Feature Changes
3GPP TS 29.272 Version Compliance for Operator Determined Barring
Previous Behavior: The Operator Determined Barring for all outgoing calls (ODB-all-OG) bit is always set in the
ULR from the MME to the HSS. This behavior is not expected from MME that is compliant with 3GPP TS 29.272
version 10.5.0 . The HSS does not expect the ODB-all-OG bit to be present in the ULR from the MME which is 3GPP
TS 29.272 version 10.5.0 compliant, as a result excess signaling is observed on the s6A interface from the HSS.
ULR from the MME to the HSS. This behavior is not expected from MME that is compliant with 3GPP TS 29.272
version 10.5.0 . The HSS does not expect the ODB-all-OG bit to be present in the ULR from the MME which is 3GPP
TS 29.272 version 10.5.0 compliant, as a result excess signaling is observed on the s6A interface from the HSS.
New Behavior: The Operator Determined Barring of all outgoing calls (ODB-all-OG) bit will not be present in the
ULR from MME. This is a 3GPP TS 29.272 version 10.5.0 compliance change.
ULR from MME. This is a 3GPP TS 29.272 version 10.5.0 compliance change.
Customer Impact: Excess signaling on the s6a interface from HSS is reduced.