MME Call Processing

Contents

Introduction
Identities
d ii
Mobility Management
S1-AP Procedures
Basic Call Procedures

2
Introduction

3
 Comparison with 3G Architecture
PDN
PDN

GGSN

P-GW
SGSN

S-GW
MME
RNC

eNodeB
NodeB

• 3G Core • EPC
• 4 nodes in data plane to PDN from UE • 3 nodes in data plane to PDN from UE

4
Comparison with 3G Procedure
3G LTE
Registration 1) Mobility Management  Combined Mobility & Session Management
‐ Attach Procedure ‐ Attach Procedure (establishing a 
2) Session Management
2) Session Management  default EPS bearer)
default EPS bearer)
‐ Primary PDP Context Activation Example) Attach Request NAS Message
NAS Message Type     : Attach Request 
EPS Attach Type      : Initial EPS Attach 
EPS Mobile Identity  : IMSI(450060123400001)
UE Network Capability: E0 E0
UE Network Capability: E0 E0
[ESM Container Contents]
NAS Message Type  : PDN Connectivity Request 
NAS Request Type  : Initial Attach
PDN Type          : IPv4

Multiple bearer UE initiated N/W controlled

‐ Secondary PDP Context Activation ‐ Dedicated Bearer Activation

Location Update  Static Dynamic

‐ RAU Based on a Routing Area
g ‐ TAU Based on TA List per subscriber
p
RA1 TA2
RNC1 TA1

NB2
B2 eNB2
NB2
NB1 SGSN eNB1 MME
RA2 TA3

RNC2

NB4 eNB4
NB3 eNB3 UE2

5
LTE Protocol Stack
App

IP IP
Relay Relay
PDCP PDCP GTP-U GTP-U GTP-U GTP U
GTP-U

RLC RLC UDP/IP UDP/IP UDP/IP UDP/IP

MAC MAC L2 L2 L2 MAC

L1 L1 L1 L1 L1 L1
SGi
LTE-Uu S1-U S5/S8
UE eNB S-GW P-GW

User Plane Protocol Stacks

 NAS : Non Access Stratum
 S1‐AP : S1 Application Protocol
 GTP‐C : GPRS Tunneling Protocol for Control Plane
 GTP‐U : GPRS Tunneling Protocol for User Plane

NAS NAS
Relay GTP-C GTP-C GTP-C GTP-C
RRC RRC S1-AP S1-AP

PDCP PDCP SCTP SCTP UDP UDP UDP UDP

RLC RLC IP IP IP IP IP IP

MAC MAC L2 L2 L2 L2 L2 L2

L1 L1 L1 L1 L1 L1 L1 L1

LTE-Uu S1-MME S11 S5/S8a

UE eNB MME S-GW P-GW

Control Plane Protocol Stacks
6
Identities

7
LTE Network Identities

8
Comparison with 3G TMSI

 TMSI has only local significance (i

(i.e.
e within an SGSN and the area controlled by an SGSN)
 TMSI consists of 4 octets

 GUTI has two main components:

GUMMEI : uniquely identifies the MME which allocated the GUTI shall be constructed from MCC, MNC
and MME Identifier(MMEI)
M-TMSI : uniquely identifies the UE within the MME that allocated the GUTI

 GUTI shall be used to support subscriber identity confidentiality, and, in the shortened S-TMSI form,
to enable more efficient radio signaling procedure (e.g. paging and Service Request)

9
UE IDs (IMSI, GUTI, IMEI)
IMSI

Not more than  15 digits
5~6 digits 9~10 digits

PLMN ID MSIN

3 digits 2~3 digits

MCC MNC

450 08 0123456789
South Korea Olleh

IMEI/SV
MME Group 1 MMEC

MME 1 MME 2

MMEGI

eNB 2

eNB 1
eNB 3

eNB 4

10
eNB ID, ECI
eNB ID • To identify an eNB within a PLMN

Global eNB ID • To identify an eNB in global (Globally Unique)

ECI • To identify a Cell within a PLMN

• To identify a Cell in global (Globally Unique)

ECGI
• EPC can know UE location based of ECGI

PLMN 
ECI

Cell 4 ECGI

Cell 3
Cell 1
eNB 2 Global eNB ID
Cell 0
Cell 2 eNB ID
eNB 1

11
 TA, TA List
TA (Tracking Area)
Minimum unit : cell
possible to make more than one cell in one eNB
The number of cell per one eNB : minimum 1 1, maximum 256
one TA is consisted of n cells.
TA is allocated by operator.
TA List
TA list is allocated by MME considering
current location of UE.
one TA list can be consisted of 16 Tas.

Configuration example
- One eNB is composed of 3 cells MME 1 MME 2
- One TA is composed of 2 eNBs(6 cells)
- One TAL is composed of 1 or 2 TAs City  1
TAC 2 TAC 1

Example) RTRV‐TAL‐INF; TAC 2
TAC 2
TAC 2
TALIST  CNT  TA(MCC/MNC/TAC) TAC 1 TAC 3
TAI List1 = {TAI1, TAI2} TAC 1 eNB 2 TAC 3
1    2    450/08/H'0001  450/08/H'0002
TAC 3
2    2    450/08/H'0003  450/08/H'0004 TAC 1
TAC 3
UE 1 TAC 3
eNB 1
TAI List2 = {TAI3}
eNB 3
TAC 3

TAC 3
City  2
UE 2 eNB 4

12
EPS Bearer

13
EPS Bearer Overview
EPS Bearer
– An EPS bearer is the level of granularity for bearer level QoS control in the
C U
EPC/E-UTRAN

Default bearer & dedicated bearer

– Default bearer
– is established when the UE connects to a PDN, and remains established for
always-on IP connectivity to that PDN
– Non
Non- GBR(Guaranteed Bit
Bit-Rate)
Rate) bearer
– The initial bearer level QoS parameter values of the default bearer are
assigned by the network, based on subscription data
– Dedicated
D di t d bearer
b
– Any additional EPS bearer to the same PDN is referred as a dedicated bearer
: By P-GW which determines bearer level QoS and TFT

– The bearer level QoS parameter value is always assigned by EPC

– UE can send a request for establishing a dedicated bearer, modifying bearers and
deactivating bearers , but a decision is made by EPC
– Bearer Modification/Deactivation by MME/PGW/HSS
14
 EPS Bearer Identity
 uniquely identifies an EPS bearer for a UE accessing via E-UTRAN and is allocated by MME
 eNB stores a mapping between a RB and S1 Bearer to lookup E-RAB ID
 The E-RAB ID maps to an EPS Bearer

Application / Service Layer

UL Service Data Flows DL Service Data Flows

UL--TFT
UL DL-TFT
DL-TFT
UL-TFT
-  RB -ID DL-TFT
-  S5/S8a-TEID
-
RB --ID  S1-TEID
- S1-TEID
-  S5/S8a-TEID

EPS B
Bearer 2
EPS Bearer 1

UE eNodeB
eNB Serving GW PDN GW
Radio Bearer S1 Bearer S5/S8 Bearer

EPS Bearer = E
E-RAB
RAB (Radio Bearer + S1 Bearer) + GTP S5/S8 Bearer
UE uses UL TFT and P-GW uses DL TFT for mapping traffic to an EPS bearer
15
PDN Connection, EPS Bearer and SDF

16
Bearer Level QoS
• The bearer level QoS parameters are QCI, ARP, GBR, MBR, and AMBR
• Each EPS bearer is associated with the following bearer level QoS parameters:
QoS
Q S Class
Cl Identifier
Id tifi (QCI)
– a scalar (index) that represents the QoS characteristics that EPS is
expected to provide for the service data flow
Allocation and Retention Priority (ARP)

Each GBR bearer is additionally associated with the following bearer level QoS
parameters:
Guaranteed Bit Rate (GBR)
Maximum Bit Rate (MBR)

Each APN is associated with an Aggregate Maximum Bit Rate (APN AMBR)
Limit AMBR of all non GBR bearers to a APN
A subscription parameter in HSS

Each UE is associated with UE Aggregate Maximum Bit Rate (UE AMBR)

Limit AMBR of all non GBR bearers to all active APNs
A subscription parameter in HSS

17
QoS Class in Standard

QCI parameter mapping table

QCI Resource Type Priority PDB PELR Example Services

1 2 100 ms 10-2 Conversational Voice

2 4 150 ms 10-3 Conversational Video ((Live Streaming)

g)
GBR
3 3 50 ms 10-3 Real Time Gaming

4 5 300 ms 10-6 Non-Conversational Video (Buffered Streaming)

5 1 100 ms 10-6 IMS Signalling

Video (Buffered Streaming), TCP-based (e.g., www, e-mail,

6 6 300 ms 10-6
p p
chat, ftp, p2p
p file sharing,
g pprogressive
g video, etc.))

Non-GBR
7 7 100 ms 10-3 Voice, Video (Live Streaming), Interactive Gaming

8 8
300 ms
9 9
Video (Buffered Streaming), TCP-based
TCP based (e.g., www, e-mail,
e mail,
10-66
chat, ftp, p2p file sharing, progressive video, etc.)

QCI: QoS Class Identifier PDB: Packet Delay Budget

k Error Loss Rate
PELR: Packet G
GBR: Guaranteed
G d Bit
i Rate

3GPP TS 23.203
18
EPS Bearer & SDF QoS Concept

19
Mobility Management

20
State Model in MME
EMM(EPS Mobility Management) State ECM(EPS Connection Management) State 
Detach,
Attach Reject,
TAU reject,
All bearers deactivated S1 connection
released
EMM-DEREGISTERED EMM-REGISTERED ECM-IDLE ECM-CONNECTED

Attach accept
p
S1 connection
TAU accept for a UE selecting established
E-UTRAN from GERAN/UTRAN

EMM state model in MME ECM state model in MME

21
 UE Mobility Management
• Location of UE is known
• in ECM-Connected mode, on eNodeB Id granularity
• in ECM-Idle mode, on TA list granularity

• UE Connectivity transition
• In order to save radio resource, E-UTRAN releases RRC towards the UE and S1 towards
the SGW.
-> UE changes to ECM
ECM-Idle
Idle mode as a result
• UE changes into ECM-connected mode after initiating the Service Request procedure
when it has a data to send or received

• Reachability Management for UE in idle mode

• MME keeps location information of a UE in ECM-idle mode.
• An ECM-idle UE periodically refreshes its context in the MME via periodic TAU.
• UE may be paged in all cells of the tracking areas (in TAL) in which it is currently
registered
• After expiry of mobile reachable timer, MME may change the EMM state of an attached UE
to EMM-DEREGISTERED.
22
 Life in EPS networks
6. Service
Request
EMM –registered
registered
eNB
ECM-connected
S5/S8
SGW if
5. TAU
PDN PGW necessary
SGi eNB
NB
ECM –connected
MME
HSS eNB
7. Power off-detach
EMM-deregistered
3. Attach 2. RRC
connection ECM-idle
ECM idle
EMM- established 1. Power on
registered
ECM - EMM-deregistered
connected
ECM-idle
4. Inactive during T
RRC connection released
EMM-registered, ECM-idle

23
 Paging
TA2
TA1

TA List 1 = eNB1, eNB2 eNB2 MME

Border TAL List = TA List 2
eNB1
TA3

UE1 TA List 2 = eNB2, eNB3, eNB4

eNB4 Border TAL List = TA List 1
eNB3 UE1

Paging Retransmission
Paging methods 1 st 2 nd 3 rd
Example 1 TA List Border TAI List None
Example 2 TA List None None
Example 3 TA List Border TAI List Broad

24
S1-AP
S1 AP Procedures

25
S1 connection establishment (eNB <-> MME)
Transport Layer
- There shall be only one SCTP association established between one MME and eNB pair.
- The eNB shall establish the SCTP association.
association
- The SCTP Destination Port number value assigned by IANA to be used for S1AP is 36412.

• S1 Setup
S t
- To exchange application level data needed for the eNB and MME on the S1 interface.
S1‐AP Message Type : S1 Setup Request (eNB ‐> MME)
Global eNB
Global eNB ID        : MCC(450) MNC(06) Macro‐eNB(1)
ID : MCC(450) MNC(06) Macro‐eNB(1)
eNB Name             : eNB1
Supported TAs        : Number Of List(1)
TAC(H'0001) PLMN(450 06)
Default Paging DRX    : v256

[MME] RTRV‐MME‐INF;
[MME] RTRV MME INF;
M6000 RETRIEVE MME INFORMATION : COMPLD   
S1‐AP Message Type : S1 Setup Response (eNB <‐ MME)
MME Name             : SamsungMme MCC        = 450
Served GUMMEIs       : Number Of List(1) MNC        = 06
Number of Served PLMNs(1)
MME_GRP    = H'0006
MCC(450) MNC(06)                                                        
Number of Served GroupIDs(1)
p ( ) MME_CODE   = H'F0
MMEGRP(H'0006) MME_NAME   = SamsungMme
Number of Served MMECs(1) HOST       = stpmme.samsung.com
MMEC(H'F0)
Relative MME Capacity   : 100 REALM      = samsung.com

S1‐AP Message Type : S1 Setup Request (eNB ‐> MME)
Global eNB ID        : MCC(450) MNC(06) Macro‐eNB(2)
eNB Name             : eNB2
Supported TAs        : Number Of List(1)
TAC(H'0002) PLMN(450 06)
Default Paging DRX    : v256 26
S1 UE-associated Signaling (eNB <-> MME)

S1 INITIAL UE MESSAGE
- To deliver the first UL NAS message
g transmitted on an RRC connection to be forwarded to an MME
eN B M M E

IN IT IA L U E M E S S A G E

‐ eNB allocates a local unique identifier(28 bits) for the UE over the S1 interface.

• S1 DOWNLINK/UPLINK NAS TRANSPORT

- To transparently deliver NAS message between eNB and MME
e NB M M E

U P L IN K / D O W N L IN K N A S T R A N S P O R T

‐ MME allocates a local unique identifier(32 bits) for the UE over the S1 interface.

27
Basic Call Procedures

28
Initial Attach Procedure Overview
• Attach Request from UE
• Due to Switch On
• After the completion of network initiated detach (re-attach required)

• Attach Procedure
• Authentication / ME Identity Check (i.e. White, Grey or Black List)
• UE location Update & Subscription data download
• Temporary Id allocation (GUTI, TAI List)
• Default Bearer establishment (for always-on IP connectivity)
1) APN & S-GW/P-GW selection, 2) IP address allocation
• Radio Bearer establishment

• After Attach
- UE has access the EPS and UE becomes reachable
• UE state : ECM-Connected & EMM-REGISTERED
• UE has PDN IP address
• UE can secure its data and signal to and from Core Network
29
 Initial Attach Procedure
Diameter Msg
Diameter Msg Type  : Update Location Answer (1.2)
Type : Update Location Answer (1 2)
NAS Msg Type        : Attach Accept (1.6) IMSI              : 450060123400001    MSISDN             : 82060123400001
‐ EPS Attach Result : EPS Only Subscriber Status : SERVICE_GRANTED    Network Access Mode: PACKET_AND_CIRCUIT
‐ T3412             : Unit(Incre DeciHour) Value(9)
UE_AMRB_UL        : 150000000         UE_AMRB_DL         : 150000000
‐ TAI List          : Number Of List(2)
MCC(450) MNC(06) TAC(H'0007) RFSP_ID           : 1                 Access‐Restriction‐Data : None
MCC(450) MNC(06) TAC(H'0008) APN‐Config. Context‐Id List  : Count is 1. Default Context‐Id is 123400001.
‐ [ESM Container Contents]
[ESM Container Contents] APN CONFIGURATION PROFILE INFORMATION 
APN CONFIGURATION PROFILE INFORMATION
‐ NAS Msg Type: Activate Default EPS Bearer Context Request Service‐Selection     : internet     PDN‐Type                  : IPv4   
‐ EPS Bearer Identity  : 5 QoS‐Class‐Identity    : 8            Priority‐Level            : 2
‐ Proc Transaction Id  : H'01 Pre‐emption‐Capability: ENABLED      Pre‐emption‐Vulnerability : ENABLED
‐ EPS QoS : 08 VPLMN‐Dynamic‐Addr‐Allowed: Allowed  PDN‐GW‐Allocation‐Type    : DYNAMIC
‐ APN                  : internet.mnc006.mcc450.gprs
APN_AMRB_UL           : 20000000     APN_AMRB_DL               : 20000000
‐ PDN Address          : IPv4 (92.1.1.2)
‐ APN AMBR             : F4 F4
APN AMBR : F4 F4
‐ EPS Mobile Identity  : GUTI(450 06 H'0003 H'01 H'C011EC6C)
‐ T3402                : Unit(Incre 1 Min) Value(12)
‐ T3423                : Unit(Incre 1 Min) Value(4)
‐ PLMN List            : Number Of List(1)
MCC(450) MNC(06)

NAS Msg Type           : Attach Request (1.1) NAS Msg Type           : Attach Complete (1.7)
‐ EPS Attach Type      : Initial EPS Attach [ESM Container Contents]
‐ EPS Mobile Identity  : IMSI(450060123400001) ‐ NAS Msg Type        : Activate Default EPS Bearer Context Accept
‐ UE Network Capability: 00 40 ‐ EPS Bearer Identity : 5
‐ [ESM Container Contents] ‐ Proc Transaction Id : H'00
‐ NAS Msg Type       : PDN Connectivity Request 
‐ Proc Transaction Id: H'01
‐ NAS Request Type   : Initial Attach
‐ PDN Type           : IPv4 30
Initial Attach Procedure : Acquire UE IMSI

31
Authentication & NAS Security Setup

32
Location Update & IP Session Establishment

33
IP Session Establishment (cont)
MME ‐> eNB/UE

34
Detach Request Overview
• UE initiated Detach
• Device Switch Off or Normal Detach

• Network initiated Detach

• Cancel Location Request
q from HSS or Delete Bearer Request
q from SGW
(explicit detach).
 MME sends Detach Request to Connected UE or
 Pages Idle UE for explicit detach

• Implicit detach after non-communications with UE for a configurable

period (after Mobile Reachability Timer expires).
 MME does not send Detach Request to UE

After Detach : UE Information After Detach : MME Information

35
UE Initiated Detach Request Procedure

NAS Msg Type         : Detach Request
‐ Security Header Type : No Security Protection
‐ Detach Type          : SWOFF(Normal Detach) DETYPE(EPS Detach)
‐ KSIasme : 1
y ( )
‐ EPS Mobile Identity  : GUTI(450 06 H'0003 H'01 H'E812B128)

MSGTYPE  = DELETE_SESSION_REQUEST(H'24)
Linked_EBI (H'49:0) = H'05(5)
INDICATION (H'4D:0) = H'0800(0000 1000 0000 0000)
‐ Operation Indication
ULI        (H'56:0) = H'18(ECGI(1), TAI(1), RAI(0), SAI(0), CGI(0))
‐ TAI  : MCC = 450,  MNC = 06, TAC = H'0003(3)
TAI MCC 450 MNC 06 TAC H'0003(3)
‐ ECGI : MCC = 450,  MNC = 06, ECI = H'0000200(512)

NAS Msg Type         : Detach Accept
‐ Security Header Type : No Security Protection

Message Type    : UE Context Release Command
UE S1AP ID Pair : MME‐UE‐S1AP‐ID(H'100007E) eNB‐UE‐S1AP‐ID(H'73)
Cause           : NAS Cause   Nas_Detach

Message Type    : UE Context Release Complete
MME UE S1AP ID          : H'100007E
eNB UE S1AP ID          : H'73

36
 HSS Initiated Detach Request Procedure
UE eNB MME S-GW P-GW HSS PCRF SPR

DRB S1 Bearer S5 Bearer UE eNB MME

EMM‐Registered EMM‐Registered
RRC Connection S1 Signaling Connection S11 GTP‐C Connection S5 GTP‐C Connection ECM‐Connected ECM‐Connected
ECM Connection RRC‐Connected RRC‐Connected
Message Type      : Paging
UE Identity Index : 00 89 CMD_NAME             = Cancel Location Request (CLR)
UE Paging ID      : S‐TMSI MMEC(H'01) M‐TMSI(H'E812B129) USER_NAME             : 450061044440201
Paging DRX        : v256 Cancel Location Request CANCEL_TYPE           : SUBSCRIPTION_WITHDRAWAL(2)
CN Domain
CN Domain         : PS
: PS IMSI ,, Cancellation Type
yp =Subscription Withdrawn
p
Delete of subscriber’
Delete of subscribers MM context and EPS bearer
s MM context and EPS bearer
TAI List          : MCC(450) MNC(06) TAC(H'0003)
[Optional ] If UE is in ECM ‐Idle state
Paging
NAS Msg Type         : Detach Request
Detach Request ‐ Security Header Type : No Security Protection
GUTI, Detach Type =Reattach Required or not , Cause ‐ Detach Type          : SWOFF(Normal Detach) DETYPE(ReAttach Not Required)
‐ EMM CAUSE            : EPS Service Not Allowed
S
Store current NAS Security Info
NAS S i I f S
Store current NAS Security Info
NAS S i I f
Delete EPS Bearer Context
Delete Session Request
Delete EPS Bearer Context IMSI , EPS Bearer ID , ECGI, TAI
Delete Session Request
NAS Msg Type         : Detach Accept
Delete EPS Bearer Context IMSI, EPS Bearer ID , ECGI, TAI
‐ Security Header Type : No Security Protection
Security Header Type : No Security Protection
Indication of IP‐CAN Session Termination (CCR)
Detach Accept IMSI, UE IP, ECGI , TAI

UE Context Release Command Acknowledge of IP‐CAN Session Termination (CCA)

RRC Release Release Cause=Detach
Delete Session Response Remove PCC Rule
Delete Session Response
Delete UE Context
Delete UE Context Delete EPS Bearer Context
Delete EPS Bearer Context
Cancel Location Ack
IMSI

DRB Released S1 Bearer Released S5 Bearer Released UE eNB MME

EMM‐Deregistered
Deregistered EMM‐Deregistered
Deregistered
RRC  Released S1 Signaling Released S11 GTP‐C Released S5 GTP‐C Released ECM‐Idle ECM‐Idle
ECM Connection Released RRC‐Idle RRC‐Idle

37
S1 Release Overview
• eNodeB can decide whether to release UE’s signaling and all radio
bearers for a UE
• O&M intervention or Unspecified Failure
• User Inactivity
• Repeated RRC signaling Integrity Check Failure
• UE initiated connection release

• MME can decide to release S1 connection

• Authentication failure
• As part of MME initiated detach procedure.
Before S1 Release Procedure After S1 Release Procedure

38
Active Handover Procedures

39
Intra-E-UTRAN Handover Overview
• X2 handover

• If X2 connectivity is available between the source eNB

and the target eNB and the UE would stay in the same PDN
MME pool area, X2 handover is invoked.
SGi
• The source eNodeB directly sends HO request message PGW
HSS
g eNodeB.
to the target S5/S8
S6a
SGW
MME
• S1 handover
h d
S1_c S1_u
• If X2 connectivity is not available or the serving MME eNB X2 eNB
needs to be relocated, S1 handover is invoked. X2 eNB
X2
• The Source eNodeB sends Handover Required
H/O i
H/O signalling path
lli th
message to the serving MME to trigger S1 handover

40
X2 Handover Concept

41
X2 Handover Procedure
Message Type     : Path Switch Request (1.3)
Message Type : Path Switch Request (1 3) Message Type          : MODIFY_BEARER_REQUEST (1.4)
MME UE S1AP ID  : H'100001F ...
eNB UE S1AP ID  : H'E BEARER_CXT (H'5D:0) = 
E‐RAB To Be Sw DL List  : Number Of List(1) EBI            : H'05(5)
E‐RABID(5)  F_TEID(I:0)    : V4(1) V6(0)
TransAddr(10.236.13.230) TEID(H'0000000E) Interface_Type : 0(S1‐U eNB GTP‐U)
Source MME UE S1AP ID  : H'100001F TEID           : H'0000000E
E UTRAN CGI
E‐UTRAN CGI            : MCC(450) MNC(05) CELL(65280)
: MCC(450) MNC(05) CELL(65280) IPv4 Address   : H'0AEC0DE6(10.236.13.230)
TAI                    : MCC(450) MNC(05) TAC(H'0002)
UE Security Capability : EncryptionAlgo(C0 00)
IntegrityProtAlgo(C0 00)

Message Type          : MODIFY_BEARER_RESPONSE (1.4)
...
BEARER CXT (H'5D:0)
BEARER_CXT (H 5D:0) = 
=
EBI            : H'05(5)
Message Type      : Path Switch Request Acknowledge (1.5) Cause          : H'10(Request accepted)
MME UE S1AP ID   : H'100001F F_TEID(I:0)    : V4(1) V6(0)
eNB UE S1AP ID   : H'E Interface_Type : 1(S1‐U SGW GTP‐U)
Security Context : Next Hop Chaining Count(H'02)                                       TEID           : H'00001982
< Next‐Hop NH > IPv4 Address   : H'140101E4(20.1.1.228)

42
X2 Handover Procedure

43
S1 Handover Concept

44
S1 Handover Procedure
Message Type     : Handover Required (1.2) Message Type             : Handover Request (1.3)
g yp q ( )
MME UE S1AP ID  : H'100001F MME UE S1AP ID          : H'100001F
eNB UE S1AP ID  : H'1E Handover Type           : Intra LTE
Handover Type   : Intra LTE Cause                   : Radio Network Layer Cause
Cause           : Radio Network Layer Cause                                       Radio_HandoverDesirableForRadioReason
Radio_HandoverDesirableForRadioReason UE Aggregate Max BR     : MaxDL(100000000) MaxUL(100000000)
Target ID       : Target eNB Id E‐RABs To Be Setup List : Number Of List(1)
MCC(450) MNC(05) Macro‐eNB(38) E‐RABID(5)
( )
MCC(450) MNC(05) TAC(H'0000) TransAddr(20.1.1.228) TEID(H'00001982)
Direct Fwd Path Avail : Direct Path Available QCI(8) Alloc‐Ret‐PRI(1)
SRC to TAR Container  : PreECapa(May trigger Pre‐Emption) PreEVuln(Pre‐Emptable)
SRC to TAR Container    :
UE Security Capability  : EncryptionAlgo(C0 00) IntegrityAlgo(C0 00)
Preparation phase HO Restriction List     : Serving PLMN(450/05)
Security Context        : Next Hop Chaining Count(H'03)  <Next‐Hop NH>
y p g ( ) p
Message Type     : Handover Command (1.4)
d d ( )
MME UE S1AP ID  : H'100001F
eNB UE S1AP ID  : H'1E
Resource Allocation phase
Handover Type   : Intra LTE
Message Type            : Handover Request Acknowledge (1.3)
E‐RABs Subject Fwd List : Number Of List(1)
MME UE S1AP ID         : H'100001F
E‐RABID(5)
eNB UE S1AP ID         : H'44D
DL Transport Addr(10.236.13.38)  DL GTP TEID(H'0008044D)
E‐RABs Admitted List   : Number Of List(1)
s d ed s : u e O s ( )
TAR t SRC C t i
TAR to SRC Container :
E‐RABID(5)
Transport Addr(10.236.13.38)     GTP TEID(H'0000044D)
DL Transport Addr(10.236.13.38)  DL GTP TEID(H'0008044D)
TAR to SRC Container   :

45
S1 Handover Procedure
UE Source
S TTargett MME SAE GW
SAE-GW
eNB eNB
Downlink User Plane Data

Determined that X2 HO cannot be done

1. Handover Required (Target eNB ID)

2. Handover Request (ERABID, QoS, src SGW GTP-U IP+TEID)

3. Handover Request Acknowledge(ERABID, target eNB GTP-

U IP+TEID)
IP TEID)
4. Handover Command (ERABID, target eNB GTP-U IP+TEID)
Handover Command
5. eNB Status Transfer

6. MME Status Transfer

Indirect Forwarding of DL Data

Handover Confirm
Downlink User Plane Data

Uplink User Plane Data

7. Handover Notify 8. Modify Bearer Request
(Bearer Ctxt [target eNB GTP-U IP+TEID])

9. M
9 Modify
dif BBearer R
Response (B
(Bearer Ct
Ctxtt [SGW
GTP-U IP+TEID])
Downlink User Plane Data

Tracking Area Update if TA has changed

10. UE Context Release Command/Complete

RRC Connection Release

46
S1 Handover Procedure – Preparation Phase

47
S1 Handover Procedure – Execution Phase

48
S1 Handover Procedure – Completion Phase

49
S1 Handover Procedure – Completion Phase

50