Cisco Cisco Packet Data Gateway (PDG)
MME Changes in Release 17
▀ MME Enhancements for 17.0
▄ Release Change Reference, StarOS Release 17
316
context context_name
egtp-service svc_name
[ no ] gtpc node-feature network-triggered-service-restoration
end
Notes:
When this command is issued, the MME will indicate support for the Network Triggered Service Restoration
procedure in the Node Features IE.
Upon receipt of a Downlink Data Notification (DDN) message including an IMSI, the MME will accept the
request and initiate paging including the IMSI in order to force the UE to re-attach.
IMSI-based DDN requests contain a zero TEID.
Since the UE is not attached, the UE will be paged over the whole MME coverage area.
A different MME may be selected by the eNodeB to service the attach request. Since the MME that serviced the
DDN will not be aware that the UE has responded with the attach request, it will stop paging upon a timeout.
A new disconnect-reason counter has been added:
ue-ctxt-normal-del-ntsr-ddn
. This is incremented
when UE contexts created to handle NTSR DDN's are destroyed when tje UE re-attaches.
network-overload-protection mme-new-connections-per-second
In the event of an MME failure, the surviving MME in the pool may receive a very large number of IMSI requests,
which may overwhelm the IMSI Manager. To avoid congestion, the IMSI Manager can throttle the IMSI-based DDN
requests it receives if the configurable rate is exceeded, as specified using this command.
which may overwhelm the IMSI Manager. To avoid congestion, the IMSI Manager can throttle the IMSI-based DDN
requests it receives if the configurable rate is exceeded, as specified using this command.
This command includes the new
ddn { drop | reject-with-cause { unable-to-page-ue | context-not-
found } }
keywords to drop or reject IMSI-based DDN requests as needed to maintain adequate service performance
for normal procedure processing.
Also included is the ability to configure the default cause code to be sent in the DDN Ack in case the IMSI Manager
cannot send the DDN to a Session Manager.
cannot send the DDN to a Session Manager.
configure
network-overload-protection mme-new-connections-per-second #_new_connections action
attach { drop | reject-with-emm-cause { congestion | network-failure | no-suitable-cell-
in-tracking-area } tau { drop | reject-with-emm-cause { congestion | network-failure |
no-sec-ctxt-in-nw | no-suitable-cell-in-tracking-area } fwd-reloc { drop | reject } ddn {
drop | reject-with-cause { unable-to-page-ue | context-not-found } } } [ queue-size
queue_size ] [ wait-time wait_time ]
attach { drop | reject-with-emm-cause { congestion | network-failure | no-suitable-cell-
in-tracking-area } tau { drop | reject-with-emm-cause { congestion | network-failure |
no-sec-ctxt-in-nw | no-suitable-cell-in-tracking-area } fwd-reloc { drop | reject } ddn {
drop | reject-with-cause { unable-to-page-ue | context-not-found } } } [ queue-size
queue_size ] [ wait-time wait_time ]
default network-overload-protection mme-new-connections-per-second
end
Performance Indicator Changes
System Schema