Mme Support For Offloading Overloaded Mafs and Support For T3346 Timer

MME support for Offloading Overloaded MAFs
and support for T3346 timer

9471 WMM Release 8.0.0
Aaron Lugo-Alvarez
March 2014
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
AGENDA
1. Support for T3346 timer

1. Overview
2. Provisioning
3. Capture Files
4. PCMD / PM
2. Support for offloading of overloaded MAF
1. Feature description
2. Provisioning
3. PM counters
3. References
Introduction to Offloading Overloaded MAFs and
support for T3346 timer

ALCATEL-LUCENT — CONFIDENTIAL — SOLELY FOR AUTHORIZED PERSONS HAVING A NEED TO KNOW — PROPRIETARY — USE PURSUANT TO COMPANY
INSTRUCTION
T3346 3GPP
T3346 backoff timer is defined in 3gpp 24.008, This timer is sent to the UE
when the network is experiencing congestion. The specific handling of the
T3346 is described in 3GPP 24.301.
In summary, this timer provides a mechanism to the UE so that it delays

procedures and wait for an specified amount of time before retrying. For
instance, If the UE is attempting to attach and the procedure is rejected with
cause code 22 (congestion), the UE should wait until the T3346 time expires
before retrying to attach.
MME provides the ability to provision separate minimum and maximum timer
value for Attach, TAU and SR procedures. MME randomly selects a timer
value between the minimum and maximum timer values. This random
selection is used so that UEs subsequent requests are not all triggered at the
same time.
If timer values are not provisioned then MME sets the T3346 to 0.

Provisioning

INSTRUCTION
MAF overload backoff timer
1:lm69# configure system parameters mobility

1:lm69>config>system>params>mobility# info detail
----------------------------------------------
mobility
no maf-offload
no mme-overload-backoff-timer
exit
----------------------------------------------
MAF offload and backoff timer
1:lm69# configure system timers mobility

1:lm69>config>system>timers>mobility# info detail
----------------------------------------------
mobility
t3346-timers
no max-attach-timer
no max-sr-timer
no max-tau-timer Default values:
no min-attach-timer Min = 15 seconds
no min-sr-timer
no min-tau-timer Max = 60 seconds
exit
exit
----------------------------------------------
1:lm69>config>system>timers>mobility#
1) MME Overload MM Rejection NAS CC
2) Enable MME overload back off timer

SAM

Capture PCAP files

INSTRUCTION
IMSI / GUTI attach rejection CC 22 and T3346
Rejection cause 22 congestion.

T3346 timer, random value Between Min and Max settings for Attach

TAU attach rejection CC 22 and T3346

T3346 timer, random value Between Min and Max settings for TAU

SR rejection CC 22 and T3346

T3346 timer, random value Between Min and Max settings for SR

PCMD sample
The sample file decodes as follow:
# gzip -c -d 2014-03-02.21:24.-0600.MMEpcmd.gz |cut -d ";" -f 7,12-14

11;1;101;139
16;2;245;418
Procedure 16: Service Request

CFCQ 245 : MM
SCFCQ 418 : Congestion. Sent to the UE because of congestion in the network
(e.g. no channel, facility busy/congested etc.) Maps to EMM cause 22

Support for offloading of overloaded MAFs

INSTRUCTION
Overview
Currently, when MPH, MIF or MAF goes into CPU overload, MME responds by
rejecting of fractions of mobility management and session management
procedures. As the CPU overload increases or decreases, MME progressively
increases or decreases the fraction of procedures it rejects. As part of this
rejection mechanism. IMSI and GUTI attaches are candidates for rejection.
This feature provides a capability for offloading UEs from MAFs in CPU overload to
lightly loaded MAFs when available in MME. A MAF with CPU load of 85% or more
can offload UEs if there are MAFs in the MME with CPU load of 70% or less.
The MME support for offloading overloaded MAFs builds upon this mechanism of
rejection of IMSI and GUTI attaches during MAF CPU overload to relocate UEs to
lightly loaded MAFs in the MME. Only enough UEs are offloaded so that the MAF
are brought out of CPU overload.

Feature highlights
This feature builds upon existing MME overload control mechanisms:
1. Offload all IMSI and GUTI attaches targeted for rejection from MAFs in CPU overload to
less loaded MAFs
2. Only enough UEs are offloaded until the overloaded MAF is brought out of CPU overload.
The UE offloading activity is performed until the source MAF’s alarm state goes from
major to minor
3. MIF will target a percentage of IMSI and GUTI attaches towards MAFs in CPU overload
and instruct the MAF to reject these attaches and then to delete the UE context (VLR
entry).
4. The deletion of the UE context is only performed when there is/are lightly loaded MAFs
within the MME
5. When MME rejects an Attach Request, MME includes in the Attach Reject message a
T3346 timer and sets the NAS cause code to #22 (Congestion)
6. When the UE subsequently retries the IMSI or GUTI attach, MME will not find UE context,
forcing MME to assign a MAF that is not in CPU overload and that has room in the UE
context (VLR entry)
7. The UE offload rate depends on attach rate experienced by the MME and also by the
procedure rejection rate applied to the MAF in CPU overload

Conditions to trigger MAF offload
1. One or more MAFs are in CPU overload (CPU load 85% or more and an alarm
critical or major)
2. At least other active MAFs is NOT in CPU overload CPU load less than 70%
3. VLR occupancy in the target MAF is 95 % or less of the target occupancy
Number reg + de-reg UEs
Target Occ =
Number of MAF pairs
For example, in an MME with 100000 UEs and 4 MAFspairs, each MAF should have 25000 entries in its VLR. The
MME will start offloading when the target MAF is 70% or less of that VLR occupancy. That would be 70% of
25000, 17500 entries or less.
MME will stop off loading if the target MAF reaches 95% of that VLR occupancy, That would be 95% of 25000,
2375 entries
Without these 3 conditions, offload will NOT be triggered.
Additionally, T3346 will only be sent if “MME overload MM rejection NAS CC” is set
to 22 (congestion)
Can anyone provide an example when this situation may happen?

Prior to WM800
Active
MAF Load
<=70% Resources are sufficient
MPHocc
VLR
MAF accepts the procedure
less than
MIF re-directs
MIF re-directs the
the UE
UE to
to 70% target
the MAF
the MAF where
where the UE
the UE
Same UE performs context is
context is allocated
allocated
Attach
Attach IMSI
IMSI /GUTI
/GUTI MAF
Active
MAF In MAF in
in OVERLOAD
OVERLOAD
Active Active OverLoad % of the procedures are
% of the procedures are
eNB MPH
Load >= Rejected
Rejected
MPH
MPH MPH
MIF 85% UE
UE context
context is
is kept
kept in
in MAF
MAF
UE may be rejected again
Overload condition is not
improved
Active
MAF Load
<=70%
MPHocc
VLR
less than
70% target

WM800
Target VLR occupancy = Total num UE’s (Reg + de-Reg) / numb of MAF pairs
MIF re-directs the UE to Active

MAF Load
<= 70%, Resources are sufficient
the MAF where the UE
MIF has no reference to allocated
the UE and MPH
VLR occ
MAF accepts the procedure
context is less than
selects a random
And MAF.
instructsthe
MIF re-directs MAF UEtoto 70% target
Less loaded MAFs have
Reject
the MAF thehigher preference.
procedure
where the UE
When timer expires
Same UE will And remove
context UE context
is allocated
Attach IMSI /GUTI MAF in OVERLOAD
Overloaded MAF hasare
Active
MAF In % of the procedures
Active Active OverLoad Offloaded
Rejected the UE.
eNB MPH
Load >=
MPH
MPH MPH
MIF 85%
UE context is Removed
Inand
time, MAF overload
all references to UE
will cease
If UE supports T3346 Procedure

Procedure is rejected successfully
completes
UE will wait until If T3346 is enabled,
timer expires before IE T3346 will be included Active
MAF Load
<=70%
Attempting procedure
retransmission MPHocc,
VLR
less than
70% target

Provisioning

INSTRUCTION
1) Allow UE Offload on MME During MAF CPU overload
Feature is off by default

MAF overload backoff timer
1:lm69# configure system parameters mobility

1:lm69>config>system>params>mobility# info detail
----------------------------------------------
mobility
no maf-offload
no mme-overload-backoff-timer
exit
----------------------------------------------

PM counters
Counter Name 3GPP Description
Number of service request messages VS.ServiceReqThrottledDropped Counts the number Service Request
that are dropped due to excessive messages that are dropped due to
service request rate exceeding the service request storm
threshold
Number of extended service request VS.ExtServiceReqThrottledDropped Counts the number Extended Service
messages that are dropped due to Request messages that are dropped
excessive extended service request due to exceeding the service request
rate storm threshold.
Number of TAU request messages that VS.TAUThrottledDropped Counts the number TAU Request
are dropped due to excessive TAU messages that are dropped due to
request rate exceeding the TAU request storm
threshold.
Number of delete bearer request VS.DeleteBearerThrottledDropped Counts the number Delete Bearer
messages that are dropped due to Request messages that are dropped
excessive delete bearer request due to exceeding the Delete Bearer
message rate Request storm threshold.
Number of DDN messages that are VS.DDNThrottledDropped Counts the number DDN messages that
dropped due to excessive DDN are dropped due to exceeding the DDN
message rate message storm threshold.
This counters are not directly related to MAF offload but were included as
part of the feature development
Q&A
1) Are emergency calls rejected / offloaded to other MAF’s?
Emergency calls are not touched offloaded, emergency procedures are not
targeted for rejection
2) What is the behavior when all MAF’s are overloaded, procedures will be rejected
but shouldn’t delete the VLR to avoid offloading to other MAF’s, shouldn’t it ?
FMAF Offload feature will not be triggered because the conditions to have at least
another MAF with less load is not met
1) When a Service Request or TAU are rejected, VLR will not be removed, will the
UE re-attach or reattempt the Service Request /TAU ?
Normal handling by the UE will be used, generally UE will retry the procedure
1) Was this feature trigger by tier-4 or customer ?
T3346 was requested by customer, MAF offload was a tier-4 /development
initiative
1) Is the NAS CC 22 new ?
NO, this CC was introduced with feature m10108-04
2) Are the CC indicated in the SCFCQ in PCMD new ?
SCFCQ CC22 is new

References
1. 9471 WMM PM SEI Requirements in WM8.0.0

2. PRD MME Support for Offloading 3 MAFs and Support for T3346 Timer
3. 9471WMM WM800 Command Line Interface SEI Document
4. Technical Description
5. Command Line Interface Reference Guide
6. 3GPP 23.401
7. 3GPP 24.301
8. 3GPP 008


Mme Support For Offloading Overloaded Mafs and Support For T3346 Timer

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Mme Support For Offloading Overloaded Mafs and Support For T3346 Timer

Caricato da

Copyright:

Formati disponibili

MME support for Offloading Overloaded MAFs

and support for T3346 timer

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

1. Support for T3346 timer

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

In summary, this timer provides a mechanism to the UE so that it delays

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

1:lm69# configure system parameters mobility

MAF offload and backoff timer

1:lm69# configure system timers mobility

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

Rejection cause 22 congestion.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

Rejection cause 22 congestion.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

Rejection cause 22 congestion.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

The sample file decodes as follow:

# gzip -c -d 2014-03-02.21:24.-0600.MMEpcmd.gz |cut -d ";" -f 7,12-14

Procedure 16: Service Request

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

Without these 3 conditions, offload will NOT be triggered.

Can anyone provide an example when this situation may happen?

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

MIF re-directs the UE to Active

If UE supports T3346 Procedure

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

1:lm69# configure system parameters mobility

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

1. 9471 WMM PM SEI Requirements in WM8.0.0

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

Potrebbero piacerti anche