MME Pool Principle
www.huawei.com
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.
Objectives
Upon completion of this course, you will be able to:
Describe key technique of MME pool
Outline the key parameters of MME pool
Describe the Main signaling procedure
Describe the principle of capacity management.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page2
Contents
1. MME Pool Network Overview
2. Signaling Procedure of MME Pool
3. MME Pool Capacity Management
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page3
Contents
1. MME Pool Network Overview
2. Signaling Procedure of MME Pool
3. MME Pool Capacity Management
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page4
MME Pool Networking
MME
SGW
SGW Serving Area
MME POOL Area
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page5
NNSF
NNSF: NAS node selection MME1 MME2 MME3
function
For the first attach of subscriber:
find a suitable MME regarding
the load balancing. eNodeB NNSF
For the subsequence service of
the subscriber: try to find the
same MME.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page6
MMEC
How to try to find the same MME for the same subscriber ?
Every MME in the Pool have it’s MME code value.
The MME allocates an MMEC to the UE. The subsequent services of
the UE are all routed through the NNSF function to the MME to which
the MMEC belongs.
MMEC information is carried by GUTI.
MCC MNC MME Group ID MME Code M-TMSI
Unique UE Identity
in MME
Unique UE Identity in
S-TMSI MME POOL
Globally Unique
MME Identifier
GUMMEI
Globally Unique
UE Identity
GUTI
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page7
MMEC Allocation and Usage
MME1 MME2 MME3
MMEC=1 MMEC=2 MMEC=3
GUMMEI( With MMEC)
eNB MME
eNodeB NNSF
GUTI (with GUMMEI)
UE MME MME Group ID MMEC
MME1 0x8000 1
S-TMSI （with MMEC） MME2 0x8000 2
UE eNB MME3 0x8000 3
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 8
S1-Flex Load Balancing Algorithm
MME1 MME2 MME3 MME Weight Distribution rate
MME1 1 25%
MME2 1 25%
MME3 2 50%
UE ID UE ID
NNSF Load Sharing Proportion is configured on MME and
eNodeB MME will sent to eNodeB.
During the initial access, UEID carried in the RRC
CONNECT message is invalid, eNodeB selects
MME based on the load sharing proportion received.
Initial Access UE roams from When UE roams from outside the pool area, UEID
Outside pool area parameter carried in the RRC CONNECT message
has GUMMEI information. GUMMEI indicates that
MMC MNC MME Group ID MME Code
UE roams from outside the pool and eNodeB will
selects MME based on load sharing proportion.
GUMMEI
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page9
Disaster Tolerance Principle
MME 1 MME 2 MME 3
MME State Weight Distribution rate
MME1 Normal 1 25%
MME2 Normal 1 25%
MME3 Normal 2 50%
MME3 faulty
SGW 1 SGW 2 MME State Weight Distribution rate
MME1 Normal 1 50%
eNB MME2 Normal 1 50%
MME3 Faulty 2 0%
eNodeB will judge whether MME is available through S1 link detection
mechanism.
MME will judge whether SGW is available through GTP path detection.
If an MME becomes faulty, eNodeB select other available MMEs; if an
SGW becomes faulty, MME select other available SGWs.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 10
Contents
1. MME Pool Network Overview
2. Signaling Procedure of MME Pool
3. MME Pool Capacity Management
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page11
eNodeB Registration
MME2 MME3
MME1 MMEC=4
MMEC=1 MMEC=2/3
Capacity= 20 Capacity= 10
Capacity= 10
2. S1AP message: S1
1. S1AP message: S1 setup response (Served
setup request MMECs= 2/3, Relative
MME Capacity=20)
eNodeB 1
MME Group ID MMEC Relative Capacity
MME1 0x8000 1 10
MME2 0x8000 2/3 20
MME3 0x8000 4 10
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page12
Initial Attach
MME2 MME3
MME1 MMEC=4
MMEC=1 MMEC=2/3
Capacity= 20 Capacity= 10
Capacity= 10
4. S1AP: Initial UE Message
( EMM: Attach request (IMSI) ) 5. Attach accept : new GUTI ( MMEC=2 )
2. eNodeB1 select a MME
(MME2) according to the
load balancing algorithm eNodeB 1
CN Capacit Load Sharing
Node y Proportion 1. RRC Connection
3 3. RRC message: UL
MME1 10 25% Request ( UE ID = Information Transfer
MME2 20 50%
random value ) ( attach request( IMSI) )
MME3 10 25%
Initial Access
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page13
Intra MME Attach
MME2 MME3
MME1 MMEC=4
MMEC=1 MMEC=2/3
Capacity= 20 Capacity= 10
Capacity= 10
4. S1AP: Initial UE Message ( EMM:
Attach request (GUTI(MMEC=2)) ) 5. Attach accept : new GUTI ( MMEC=2 )
2. eNodeB1 select a MME
(MME2) according to the
MMEC value eNodeB 1
CN Node MMEC
1. RRC Connection 3. RRC message: UL
MME1 1 3
Request ( UE ID = Information Transfer ( attach
MME2 2/3 S-TMSI (MMEC=2) ) request( GUTI (MMEC=2)) )
MME3 4
Intra MME2 attach
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page14
Periodic TAU
MME2 MME3
MME1 MMEC=4
MMEC=1 MMEC=2/3
Capacity= 20 Capacity= 10
Capacity= 10
4. S1AP: Initial UE Message ( EMM:
TAU request (GUTI(MMEC=2)) ) 5. TAU accept : new GUTI ( MMEC=2 )
2. eNodeB1 select a MME
(MME2) according to the
MMEC value eNodeB 1
CN Node MMEC
1. RRC Connection 3. RRC message: UL
MME1 1 3
Request ( UE ID = Information Transfer ( TAU
MME2 2/3 S-TMSI (MMEC=2) ) request( GUTI (MMEC=2)) )
MME3 4
Periodic TAU
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page15
TAU in the MME Pool
MME2 MME3
MME1 MMEC=4
MMEC=1 MMEC=2/3
Capacity= 20 Capacity= 10
Capacity= 10
4. S1AP: Initial UE Message ( EMM:
5. TAU accept : new GUTI ( MMEC=2 ) TAU request (GUTI(MMEC=2)) )
5
2. eNodeB2 select a MME
(MME2) according to the
eNodeB 1 eNodeB 2 MMEC value
MME1 1
3. RRC message: UL MME2 2/3
3 1
Information Transfer ( TAU
request( GUTI (MMEC=2)) ) MME3 4
1. RRC Connection Request
( UE ID = S-TMSI (MMEC=2) )
TAU
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page16
TAU in the Pool when the Link Fault
MME2 MME3
MME1 MMEC=4
MMEC=1 MMEC=2/3
Capacity= 20 Capacity= 10
Capacity= 10 5. MME3 find MME2 by the
5 GUMMEI(MMEC=2) of the GUTI.
X
6 4. S1AP: Initial UE Message ( EMM:
6. TAU accept :
TAU request (GUTI(MMEC=2)) )
new GUTI
( MMEC=4 )
2. eNodeB2 select a new MME (MME3)
according to the load balancing algorithm.
eNodeB 1 eNodeB 2
MME MMEC State CAP %
3. RRC message: UL
3 1 MME1 1 Normal 10 50%
Information Transfer ( TAU
request( GUTI (MMEC=2)) ) MME2 2/3 Faulty 20 0%
MME3 4 Normal 10 50%
1. RRC Connection Request ( UE ID = S-TMSI
TAU (MMEC=2) )
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page17
Roaming Between the Pool 5. MME5 find
MMEC MME IP MME3 by the
4 MME3 GUMMEI(MMEC=4)
DNS of the GUTI.
... ...
MME2 MME3
MME1 MMEC=4 MME5 MME6
MMEC=1 MMEC=2/3 5 MMEC=7 MMEC=8
Capacity= 20 Capacity= 10
Capacity= 10 Capacity= 10 Capacity= 10
6
6. Context request:
old GUTI
7 4. S1AP: Initial UE Message ( EMM:
( MMEC=4 )
TAU request (GUTI(MMEC=4)) )
7. TAU accept : new
GUTI ( MMEC=7 ) 2. eNodeB3 select a new MME (MME5)
according to the load balancing algorithm.
eNodeB 2 eNodeB 3
MME MMEC CAP %
CN Node MMEC 3. RRC message: UL
3 1 MME5 7 10 50%
Information Transfer ( TAU
MME1 1
request( GUTI (MMEC=4)) ) MME6 8 10 50%
MME2 2/3
1. RRC Connection Request
MME3 4
( UE ID = S-TMSI (MMEC=4) )
TAU
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page18
Contents
1. MME Pool Network Overview
2. Signaling Procedure of MME Pool
3. MME Pool Capacity Management
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page19
MME Capacity Modification
eNodeB MME OM
1. Modify the MME
relative capacity value
2. MME
CONFIGURATION
UPDATE ( Relative MME
capacity)
3. Update the Relative
MME capacity
4. MME CONFIGURATION
UPDATE ACKNOWLEDGE
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page20
MME Overload Control
When the MME is overloaded, the MME sends the eNodeB
an Overload Start message, which instructs the eNodeB to
prohibit UEs from establishing new connections to the
eNodeB. This step reduces the signaling impact on the
network.
When the MME is no longer overloaded, the MME sends
the eNodeB an Overload Stop message, which instructs the
eNodeB to enable UEs to access the MME. Then, the MME
can provide services for UEs.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page21
MME Overload Control: Start
eNodeB MME1 OM
Or 2. enable
1. CPU overload the overload
control by
OAM.
3. OVERLOAD START
4. eNodeB may:
REJECT_ALL_NON_EMERGENCY;
REJECT_ALL_SIGNALLING;
PERMIT_EMERGENCY_AND_MT.
MME2
5. Attach request
5. Attach request
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page22
MME Overload Control: Stop
eNodeB MME1 OM
1. CPU load
recover to
normal status.
Or 2. Disable the
overload control by
OAM.
3. OVERLOAD STOP
4. Service request from UE
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page23
Load Redistribution of MME Pool
Load redistribution scenario:
MME is overloaded,
MME to be relocated,
MME to be upgraded,
when the loads on MMEs are unbalanced.
The purpose is to promptly adjust the network based on
running status, increase resource usage, decrease access-
related resource consumption, and reduce service
interruption.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page24
Load Redistribution Mode
There are four subscriber migration modes:
Migrating all subscribers (ALL)
Migrating a specified number of subscribers (PART)
Migrating a specified percentage of subscribers (RATE)
Migrating a single subscriber based on its IMSI (IMSI)
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page25
Load Redistribution General Procedure
eNodeB MME2 MME1 OM
1. Modify the MME1 Relative
2. MME CONFIGURATION UPDATE capacity value to “0”.
( Relative MME capacity= 0)
3. New subscriber : 5. Start Subscriber migration
Attach request command
4. Attach request
6. MME/eNodeB migrate the subscribers.
7. Migration finish.
7. Or Stop Subscriber
migration command
8. Modify the MME1 Relative
9. MME CONFIGURATION capacity value to suitable value.
UPDATE ( Relative MME capacity)
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page26
Subscriber Migration Procedure
A subscriber migration procedure needs to be performed in
two phases :
Phase 1 : After an access procedure initiated by a subscriber is
successful, MME migrates this subscriber.
Phase 2 : After the timer of phase 1 expires, the MME migrates
subscribers that are still online by initiating connection release
procedures.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page27
Migration Phase 1
eNodeB MME2 MME1 OM
1. Start Subscriber migration
command.
ECM
connected
state UE
2. UE Context Release Request
( cause: User Inactivity, etc)
3. UE Context Release Command
4. RRC Connection Release (Load Balancing TAU Required)
(Load Balancing TAU Required)
5. TAU request
5. TAU request
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page28
Migration Phase 1
eNodeB MME2 MME1 OM
1. Start Subscriber migration
ECM idle command.
state UE 2. TAU request
3. TAU accept
4. UE Context Release Command
(Load Balancing TAU Required)
5. RRC Connection Release
(Load Balancing TAU Required)
6. TAU request
6. TAU request
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page29
Migration Phase 1
eNodeB MME2 MME1 OM
EMM 1. Start Subscriber migration
Deregistered command.
state UE 2. Attach request
3. Attach accept
4. UE Context Release Command
(Load Balancing TAU Required)
5. RRC Connection Release
(Load Balancing TAU Required)
6. TAU request
6. TAU request
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page30
Migration Phase 2
eNodeB MME2 MME1 OM
1. Start Subscriber migration
command.
ECM
connected Phase 1 timer expired
state UE
2. UE Context Release Command
(Load Balancing TAU Required)
3. RRC Connection Release
(Load Balancing TAU Required)
4. TAU request
4. TAU request
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page31
Migration Phase 2
eNodeB MME2 MME1 OM
1. Start Subscriber migration
command.
ECM idle Phase 1 timer expired
state UE
2. Paging
3. Service request
4. UE Context Release Command
(Load Balancing TAU Required)
5. RRC Connection Release
(Load Balancing TAU Required)
6. TAU request
6. TAU request
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page32
Thank you
www.huawei.com
