Cisco Cisco Packet Data Gateway (PDG)
MME Changes in Release 16
▀ MME Enhancements for 16.4
▄ Release Change Reference, StarOS Release 16
218
CSCur97956, CSCun97512 - paging event causing failures (PSC3 only, DPC is
not)
Feature Changes
Enabling Paging Optimization
Previous Behavior: The MME’s paging cache functionality was disabled.
New Behavior: It is now possible for the operator to use CLI commands to enable and control the MME’s paging
cache functionality.
cache functionality.
Command Changes
mme paging cache
The new
mme paging cache
keyword ranges for this command, in the LTE Policy configuration mode, enable the
operator to more easily enable or disable caching of the MME’s paging.
configure
lte-policy
mme paging cache { size cache_size | timeout time }
default mme paging cache { size | timeout }
end
Notes:
size cache_size
: Enter an integer from 0 to 10000 to specify the maximum number of TAC entries to be
cached. Entering the ‘0’ value disables caching and should be followed by use of the
mme paging cache
clear
command (see CSCus14148).
timeout time
: Enter an integer from 1 to 1440 to specify the number of minutes that each TAC entry remains
valid. A lower cache timeout helps to refresh the cache frequently and enables this functionality to quickly
adapt to changes in the network. We recommend the
adapt to changes in the network. We recommend the
timeout
value be less than the expected eNodeB flap
frequency; for example, if the eNodeBs connected to the MME are expected to disconnect and reconnect every
10 minutes (due to network issues), then the timeout configuration should be less than 10 minutes.
10 minutes (due to network issues), then the timeout configuration should be less than 10 minutes.
Defaults: cache size = 5000 TAC entries per SessMgr; timeout time = 5 minutes.
Both size and timeout must be configured to enable paging caching optimization.
CSCus14148 - Dynamic Paging cache size allocation through CLI
Feature Changes
Configuring Paging Cache Functionality