Cisco Cisco Packet Data Gateway (PDG)
MME Changes in Release 17
▀ MME Enhancements for 17.0
▄ Release Change Reference, StarOS Release 17
310
If some PDNs of a UE are impacted, a UE in ECM-Connected will be sent NAS Deactivate Bearer Request with
cause “regular deactivation”, and a UE in ECM-IDLE will not be paged and will be locally deactivated in a
paced manner.
paced manner.
PDN Deactivation Rate
By default, the MME will perform deactivations at the rate of 100 PDNs ( 50 Idle + 50 Connected) per session manager
per second. This rate will be applied to MME specific pacing queues ( Idle & Connected).
per second. This rate will be applied to MME specific pacing queues ( Idle & Connected).
This default pacing rate can be altered using the MME Messaging Rate Control feature.
Refer to the MME Administration Guide and to the
network-overload-protection mme-tx-msg-rate
command
in the Global Configuration Mode Commands chapter of the Command Line Interface Reference for more information
about this feature.
about this feature.
Note: Configuration of this deactivation rate should be based on appropriate dimensioning exercise to arrive at the
appropriate rate.
appropriate rate.
PDN Reactivation Behavior
After the affected subscribers have been deactivated, the MME will prioritize the re-activation of impacted PDN
connections based on subscribed APN restoration priority, if received from the HSS. If an APN restoration priority is
not received from the HSS, then this locally configured value is used. If there is no local configuration then by default
such PDNs will be assigned the lowest restoration priority.
connections based on subscribed APN restoration priority, if received from the HSS. If an APN restoration priority is
not received from the HSS, then this locally configured value is used. If there is no local configuration then by default
such PDNs will be assigned the lowest restoration priority.
Limitations
In this release, the MME will not deactivate a PDN connection upon receiving P-GW Restart Notification when the P-
GW serving the PDN is dual IP stack.
GW serving the PDN is dual IP stack.
The PGW Restart Notification is received with cause PGW-NOT-RESPONDING, however the MME is not able to find
the matching P-GW entry as the MME stores either IPv4 or IPv6 PGW address.
the matching P-GW entry as the MME stores either IPv4 or IPv6 PGW address.
This occurs when the PGW Restart Notification does not contain the P-GW IP address stored by MME.
Command Changes
gtpc node-feature pgw-restart-notification
The MME now supports P-GW Restart Notification functionality through the existing
pgw-restart-notification
keyword per EGTP service.
configure
context context_name
egtp-service svc_name
[ no ] gtpc node-feature pgw-restart-notification
end
Notes:
This command enables the MME to advertise the PGW restart notification in EGTPC echo request/response
messages.
apn-restoration priority