Cisco Cisco Packet Data Gateway (PDG)
MME Changes in Release 17
▀ MME Enhancements for 17.0
▄ Release Change Reference, StarOS Release 17
298
operator-policy policy_name
[ no ] apn network-identifier apn_net_id congestion-control
end
Notes:
During an Attach, all subscribed APNs will be checked to determine if any of them is configured for congestion.
Attach request would be rejected if any of the subscribed APN is configured for congestion.
During an Additional PDN, the requested APN will be checked to determine if it is configured for congestion.
This congestion control enhancement also supports the APN remap table functionality. The APN to which it is
remapped will be checked for the congestion-control configuration. For example, if APN abc.com is remapped
to xyz.com and xyz.com has been configured for congestion-control, the MME can drop/reject these
connection attempts.
remapped will be checked for the congestion-control configuration. For example, if APN abc.com is remapped
to xyz.com and xyz.com has been configured for congestion-control, the MME can drop/reject these
connection attempts.
diameter-result-code-mapping s6a
This command now includes a new keyword to map EMM NAS cause code #42, “Severe Network Failure” with s6a
diameter result codes.
diameter result codes.
configure
call-control-profile profile_name
diameter-result-code-mapping s6a diameter_result_code mme-emm-cause severe-network-
failure
failure
remove diameter-result-code-mapping s6a diameter_result_code }
end
Notes:
NAS cause code #42 (Severe Network Failure) can now be applied to any diameter result code using the new
severe-network-failure
keyword. For example:
diameter-result-code-mapping s6a diameter-
unable-to-comply mme-emm-cause severe-network-failure
Performance Indicator Changes
MME Schema
The following new MME Schema bulk statistics have been added to track congestion-related EMM reject causes. No
new ESM statistics were introduced as the cause “insufficient resources” already existed.
new ESM statistics were introduced as the cause “insufficient resources” already existed.
emm-msgtx-attach-reject-congestion
emm-msgtx-attach-reject-severe-network-failure
emm-msgtx-service-reject-congestion
emm-msgtx-tau-congestion
emm-msgtx-tau-severe-network-failure
emm-msgtx-tau-intra-congestion