Cisco Cisco Packet Data Gateway (PDG)
MME Service Configuration Mode Commands
▀ emm
▄ Command Line Interface Reference, StarOS Release 17
7194
While storing this back-off timer expiry time, the MME shall adjust the mobile reachability timer and/or
implicit detach timer. This is to make sure that the sum of the mobile reachability timer + implicit detach
timer is greater than the back-off timer duration.
The MME will store the DB for at least the EMM back-off timer duration even if the attach is rejected
because of congestion. The MME will not start any timer for EMM back-off. Instead, back-off timer expiry
time will be stored in the DB as the DB is stored for at least back-off timer duration.
If an EMM call is rejected due to congestion control for EMM, the DB created during ULA will not be
cleared and the purge timer will be started for a time period 10% greater than the back-off timer duration.
This is done to make sure that DB is available during back-off timer duration to reject any requests during
this period and also to avoid the HSS signaling again if the UE comes back immediately after the back-off
timer duration.
The MME will not reject any requests related to handovers as part of this feature even if EMM back-off timer
is running.
The MME will drop attach requests received during congestion while EMM back-off timer is running based
on configuration in congestion-action-profile. For example, if configuration is enabled to reject new call only
when low priority indication is set and the UE comes without low priority indication while back off timer is
running, the MME will accept the new call attempt from the UE.
The MME will not reject/drop attach requests received even if EMM back-off timer is running if the
congestion gets cleared.
The MME will forward SGS paging requests received from MSC for a UE attached in MME even if back-off
timer is running.
implicit detach timer. This is to make sure that the sum of the mobile reachability timer + implicit detach
timer is greater than the back-off timer duration.
The MME will store the DB for at least the EMM back-off timer duration even if the attach is rejected
because of congestion. The MME will not start any timer for EMM back-off. Instead, back-off timer expiry
time will be stored in the DB as the DB is stored for at least back-off timer duration.
If an EMM call is rejected due to congestion control for EMM, the DB created during ULA will not be
cleared and the purge timer will be started for a time period 10% greater than the back-off timer duration.
This is done to make sure that DB is available during back-off timer duration to reject any requests during
this period and also to avoid the HSS signaling again if the UE comes back immediately after the back-off
timer duration.
The MME will not reject any requests related to handovers as part of this feature even if EMM back-off timer
is running.
The MME will drop attach requests received during congestion while EMM back-off timer is running based
on configuration in congestion-action-profile. For example, if configuration is enabled to reject new call only
when low priority indication is set and the UE comes without low priority indication while back off timer is
running, the MME will accept the new call attempt from the UE.
The MME will not reject/drop attach requests received even if EMM back-off timer is running if the
congestion gets cleared.
The MME will forward SGS paging requests received from MSC for a UE attached in MME even if back-off
timer is running.
t3412-extended-timeout t3412_ext_dur
Sets the extended periodic TAU timer duration (in seconds), enabling the Operator to configure longer values
for the periodic TAU timer and Mobile Reachable timer. This helps the MME to reduce network load from
periodic TAU signaling and to increase the time until the UE detects a potential need for changing the RAT
or PLMN.
for the periodic TAU timer and Mobile Reachable timer. This helps the MME to reduce network load from
periodic TAU signaling and to increase the time until the UE detects a potential need for changing the RAT
or PLMN.
t3412_ext_dur
is an integer from 0 through 1116000 (0-186 minutes). Default: 3600 seconds (60 minutes).
The UE must include the “MS network feature support” IE in the Attach Request/TAU Request. This IE
indicates to the MME that the UE supports the extended periodic timer T3412, in which case the MME sends
the extended-3412 IE in the attach/TAU response. The MME will not forward the extended-T3412 timer
value to any UE which has not indicated that it supports this extended-t3412 timer.
The MME supports storing the Subscribed-Periodic-RAU-TAU-Timer value if received as part of
subscription data, and deleting this stored value if the corresponding withdrawal flag is received in the DSR
command.
For homers, the MME will send the extended-3412 IE value as received in Subscribed-Periodic-RAU-TAU-
Timer IE in subscription data.
For roamers, the MME takes the presence of Subscribed-Periodic-RAU-TAU-Timer IE in subscription data
as an indication and shall send the extended-3412 IE with the value from the local configuration.
The MME adjusts the configured mobile reachability timer value if the subscribed extended-3412 timer value
received from HSS is greater than the sum of the mobile reachability timer + implicit detach timer such that
the extended-3412 timer value becomes 10% less than the mobile reachability timer + implicit detach timer.
Refer to 3GPP TS 23.401 Section 4.3.17.3 (Version 10.4.0) & 29.272 for more details.
indicates to the MME that the UE supports the extended periodic timer T3412, in which case the MME sends
the extended-3412 IE in the attach/TAU response. The MME will not forward the extended-T3412 timer
value to any UE which has not indicated that it supports this extended-t3412 timer.
The MME supports storing the Subscribed-Periodic-RAU-TAU-Timer value if received as part of
subscription data, and deleting this stored value if the corresponding withdrawal flag is received in the DSR
command.
For homers, the MME will send the extended-3412 IE value as received in Subscribed-Periodic-RAU-TAU-
Timer IE in subscription data.
For roamers, the MME takes the presence of Subscribed-Periodic-RAU-TAU-Timer IE in subscription data
as an indication and shall send the extended-3412 IE with the value from the local configuration.
The MME adjusts the configured mobile reachability timer value if the subscribed extended-3412 timer value
received from HSS is greater than the sum of the mobile reachability timer + implicit detach timer such that
the extended-3412 timer value becomes 10% less than the mobile reachability timer + implicit detach timer.
Refer to 3GPP TS 23.401 Section 4.3.17.3 (Version 10.4.0) & 29.272 for more details.
t3412-timeout t3412_dur
Sets the timeout duration (in seconds) for the T3412 timer. This timer is used for periodic tracking area
update (P-TAU). When this timer expires, the periodic tracking area updating procedure starts and the timer
is set to its initial value for the next start.
This timer starts when the UE goes from EMM-CONNECTED to EMM-IDLE mode and stops when the UE
enters EMM-CONNECTED mode.
update (P-TAU). When this timer expires, the periodic tracking area updating procedure starts and the timer
is set to its initial value for the next start.
This timer starts when the UE goes from EMM-CONNECTED to EMM-IDLE mode and stops when the UE
enters EMM-CONNECTED mode.
t3412_dur
is an integer from 1 through 11160. Default: 3240