LTE Overview

Alcatel-Lucent Proprietary
1 11/07/2008
LTE Overview
4/30/2009
Scott Olmstead
MME Architecture

2 11/07/2008
What Does LTE Mean to End Users & Service Providers?
Performance
Improvement
Impact to End User Impact to Service Provider
INCREASED SPECTRAL
EFFICIENCY
Uplink: 2.00-2.25x vs. 3G
Downlink: 1.25x vs. 3G
Lower costs flat fee
pricing
Can buy the same amount of spectrum and pump
more data to users, or less spectrum to maintain
the same level of data usage
Reduced cost per bit
FASTER SPEEDS
Uplink: 2.00-2.25x vs. 3G
Downlink: 3x vs. 3G
Peak rate = 100 Mbps
Faster downloads of
multi-media
Better experience with
blended services
More ways to splice bandwidth:
Same # of users with more bandwidth/user or more
users with same bandwidth per user
INCREASED VOICE
CAPACITY
10 MHz: 2x vs. 3G
Better voice quality Support more voice users
REDUCED LATENCY
< 50 ms
Faster reactions when
gaming
Better voice, video
telephony
Can reuse applications across wireless and
wireline
More capacity for VoIP and TCP-based
applications
Comparisons based on average aggregate performance
3 11/07/2008
3GPP Requirements For LTE
Spectrum efficiency
DL : 3-4 times HSDPA for MIMO(2,2)
UL : 2-3 times E-DCH for MIMO(1,2)
Frequency Spectrum :
Scalable bandwidth : 1.4, 3, 5, 10, 15, 20MHz
To cover all frequencies of IMT-2000: 450 MHz to 2.6 GHz
Peak data rate (scaling linearly with the spectrum allocation)
DL : > 100Mb/s for 20MHz spectrum allocation
UL : > 50Mb/s for 20MHz spectrum allocation
Capacity
200 users for 5MHz, 400 users in larger spectrum allocations (active
state)
Latency
C-plane : < 100ms to establish U-plane
U-plane : < 10ms from UE to server
Coverage
Performance targets up to 5km, slight degradation up to 30km
Mobility
LTE is optimized for low speeds 0-15km/h but
connection maintained for speeds up to 350 or 500km/h
Handover between 3G & 3G LTE
Real-time < 300ms
Non-real-time < 500ms

4 11/07/2008
LTE Network Architecture (Non Roaming Case)

SGi
S4
S3
S1-MME
PCRF
S7
S6a
HSS
Operator s IP Services
(e.g. IMS, PSS etc.)
Rx+
S10
UE
GERAN
UTRAN
SGSN
LTE - Uu
EUTRAN
MME
S11
S5 Serving
Gateway
PDN
Gateway
S1-U
5 11/07/2008
LTE End to End Architecture
Network simplification
User Plane : 3 functional entities : eNode B, Serving Gateway and PDN
Gateway (the gateways can be combined into a single physical entity)
GGSN S/P-GW
Control plane :
SGSN MME (Mobility Management Entity)
RNC eNode B
eNode B
LTE S/P GW
IP transport
backbone
Multi-standard
User Database
Application
servers
Service IP
backbone
MD
S
S1
X2
eNode B
GGSN
SGSN
RNC
NodeB
C-plane U-plane
eNode B
EPC - Network Simplification
C-plane U-plane
S-GW
P-GW
MME
E-UTRAN
EPC
MME
6 11/07/2008 6 | Technical Sales Forum | May 2008
LTE Transforms Wireless Access and Core Networks to All-IP
6 |
7 11/07/2008
eNB, MME and SGW Pools
eNB
1

MME
eNB
2
eNB
3
eNB
4
eNB
5
eNB
6
eNB
7
eNB
8
eNB
9

MME
MME
MME
MME Pool
A
MME Pool
B
Pool Area
X
Pool Area Y
SGW
SGW
SGW Pool 2
MME
MME
MME
SGW
SGW
SGW
SGW Pool 1
8 11/07/2008
Functional Mapping (from TR 25.813)
LTE functions in eNode-B
Selection of MME at UE attachment
Routing towards SGW at UE initial access
NAS messaging encapsulated by RRC for tx over radio
Scheduling and transmission of paging messages
Scheduling and transmission of System Information
Dynamic allocation of resources to UEs in both UL
and DL
Configuration and provision of eNB measurements
Radio Bearer Control
Radio Admission Control
Access restrictions in Active state
Connection Mobility Control in LTE_ACTIVE state
Active mode Handover handling
RRC, header compression, encryption, RLC, MAC,
PHY
Security of User plane and RRC
Encryption of both in PDCP, integrity check of RRC
Scheduling and associated QoS handling
internet
eNB
RB Control
Connection Mobility Cont.
eNB Measurement
Configuration & Provision
Dynamic Resource
Allocation (Scheduler)
PDCP
PHY
MME
Serving Gateway
S1
MAC
Inter Cell RRM
Radio Admission Control
RLC
E-UTRAN EPC
RRC
Mobility Anchoring
SAE Bearer Control
Idle State Mobility
Handling
NAS Security
9 11/07/2008
MME Functions
NAS signalling
NAS signalling security
S101 Interface between MME and eRNC for inter-RAT handoffs
Inter CN node signalling for mobility between 3GPP access networks
(terminating S3)
UE Reachability in ECM-IDLE state (including control and execution of paging
retransmission)
Tracking Area list management
PDN GW and Serving GW selection
MME selection for handovers with MME change
SGSN selection for handovers to 2G or 3G 3GPP access networks
Roaming (S6a towards home HSS)
Authentication
Bearer management functions including dedicated bearer establishment.
Lawful Interception of signalling traffic.
10 11/07/2008
SGW Functions
For each UE associated with the EPS, at a given point of time, there is a
single Serving GW.
The functions of the Serving GW, for both the GTP-based and the PMIP-based
S5/S8, include:
the local Mobility Anchor point for inter-eNodeB handover;
assist the eNodeB reordering function during inter-eNodeB handover by sending one
or more "end marker" packets to the source eNodeB immediately after switching
the path.
Mobility anchoring for inter-3GPP mobility (terminating S4 and relaying the traffic
between 2G/3G system and PDN GW);
ECM-IDLE mode downlink packet buffering and initiation of network triggered
service request procedure;
Lawful Interception;
Packet routeing and forwarding;
Transport level packet marking in the uplink and the downlink, e.g. setting the
DiffServ Code Point, based on the QCI of the associated EPS bearer;
Accounting on user and QCI granularity for inter-operator charging;
UL and DL charging per UE, PDN, and QCI
(e.g. for roaming with home routed traffic)
11 11/07/2008
PDN GW Functions
If a UE is accessing multiple PDNs, there may be more than one PDN GW for that UE,
however a mix of S5/S8 connectivity and Gn/Gp connectivity is not supported for that
UE simultaneously.
PDN GW functions include for both the GTP-based and the PMIP-based S5/S8:
Per-user based packet filtering (by e.g. deep packet inspection);
Lawful Interception;
UE IP address allocation;
Transport level packet marking in the uplink and downlink, e.g. setting the DiffServ Code Point,
based on the QCI of the associated EPS bearer;
UL and DL service level charging as defined in TS 23.203 [6]
(e.g. based on SDFs defined by the PCRF, or based on deep packet inspection defined by local
policy);
UL and DL service level gating control as defined in TS 23.203 [6];
UL and DL service level rate enforcement as defined in TS 23.203 [6]
(e.g. by rate policing/shaping per SDF);
UL and DL rate enforcement based on APN-AMBR
(e.g. by rate policing/shaping per aggregate of traffic of all SDFs of the same APN that are
associated with Non-GBR QCIs);
DL rate enforcement based on the accumulated MBRs of the aggregate of SDFs with the same
GBR QCI(e.g. by rate policing/shaping);
DHCPv4 (server and client) and DHCPv6 (client, relay and server) functions;
12 11/07/2008
MME HW and SW Architecture
13 11/07/2008
MME LM0.4 (Trial Phase 4 Load 3) Hardware Configuration
O
A
M

S
e
r
v
e
r

(
R
o
u
z
i
c
)

M
I
F

(
R
o
u
z
i
c
)

M
A
F

(
R
o
u
z
i
c
)

H
u
b

(
M
a
l
b
a
n
1
)

S
h
M
C

S
h
M
C

Single ATCAv2 (200W per slot) chassis
Equipage consists of
1 pair of Shelf Management Cards (ShMCs)
1 Ethernet Hub (Malban1)
1 OAM Server blade (Rouzic Diskful)
1 MME Interface Function blade (Rouzic Diskless)
1 MME Application Function blade (Rouzic Diskless)
All external interfaces (signaling and OAM) via the
Ethernet Hub (Malban1) faceplate
14 11/07/2008
MME LM1.x Hardware Configuration
Single 44U enclosed Cabinet
Redundancy configured horizontally
1 pair of Ethernet Hubs (Malban1)
1 pair of OAM Server blades (Rouzic Diskful)
1 pair of MME Interface Function blades (Rouzic Diskless)
1 pair of MME Application Function blades (Rouzic Diskless)
Malban faceplate
May equip one additional pair of MAF servers, if needed
PDU
O
A
M

S
e
r
v
e
r

(
R
o
u
z
i
c
)

M
I
F

(
R
o
u
z
i
c
)

M
A
F

(
R
o
u
z
i
c
)

M
A
F

(
R
o
u
z
i
c
)

M
I
F

(
R
o
u
z
i
c
)

H
u
b

(
M
a
l
b
a
n
1
)

H
u
b

(
M
a
l
b
a
n
1
)

O
A
M

S
e
r
v
e
r

(
R
o
u
z
i
c
)

S
h
M
C

S
h
M
C

15 11/07/2008
MME LM2.0 Hardware Configuration
1 pair of Ethernet Hubs (Malban1)
1 pair of HSPP4 AMCs on Malban cards
1 pair of MME Application Function blades (Molene Diskless)
Malban and HSPP4 faceplate
PDU
O
A
M

S
e
r
v
e
r

(
R
o
u
z
i
c
)

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

H
u
b

(
M
a
l
b
a
n
1
)

H
u
b

(
M
a
l
b
a
n
1
)

O
A
M

S
e
r
v
e
r

(
R
o
u
z
i
c
)

S
h
M
C

S
h
M
C

16 11/07/2008
1 -
MME LM2.1 Hardware Configuration(s)
Single or Dual shelf solution
One or Two ATCAv2 (300W per slot) chasses
Shelf 1 (bottom) equipage consists of
1 pair of Hub/MIF Combos (Malban1 w/ HSPP4)
1 to 5 pair of MME Application Function blades (Molene Diskless)
Shelf 2 (if needed) equipage consists of
1 pair of Hubs (Malban1s)
1 to 6 pair of MME Application Function blades (Molene Diskless)
OAM Signaling via the Malban Hub faceplate ports or RTM
Transport signaling via the Malban HSPP4 ports
Shelf to shelf cabling via the Hub & Hub/MIF Combo faceplate (both base and
fabric) (10 Gb)
PDU
M
A
F

(
M
o
l
e
n
e
)

O
A
M

S
e
r
v
e
r

(
R
o
u
z
i
c
)

O
A
M

S
e
r
v
e
r

(
R
o
u
z
i
c
)

S
h
M
C

S
h
M
C

M
I
F
/
H
u
b

M
I
F
/
H
u
b

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

S
h
M
C

S
h
M
C

H
u
b

H
u
b

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

M
A
F

(
M
o
l
e
n
e
)

17 11/07/2008
MME Internal Architecture
EPC & 2G/3G
Core Network
SGW
SGSN
HSS
MME
R3
R4
S11,S10,S6a,S13
eNB
eNB
eNB
R1
R2
LTE
RAN
S1-MME
R5
R6
NML
OAM Network
User MAF
Registry
MME Interface Function
L
D
A
C
Dia
met
er
Paging
(broadcast)
S1-AP Intfc
S6a Intfc
S10 Intfc
IPv4
IPv6
IPsec
NAT
S
C
T
P
U
D
P
S13 Intfc
G
T
P
S11 Intfc
S101 Intfc
Link
Mgmt
I
P
M
MWare
MWare
MidWare
MME
Hub
Base Host
MWare
MWare
MidWare
Ethernet
Switch
MME Pilot /
OAM Server
MWare
MWare
MidWare
Paging
Logger
PCMD
Perf Mon
-
MME Application Function
VLR+
I
P
M
MWare
MWare
MidWare
2
nd

Tier
LD
SGW
Selector
UE Session Context
Mobil
Mgmt
Bearer
Mgmt
Paging
Handoff
Intfc
Proxy

eHRPD
RAN
S-101
18 11/07/2008
MME LM0.4/LM1.x IP Configuration Architecture
MME OAM
MAF
MME Hub (Malban)
Base
Switch
Fabric
Switch
MME Hub (Malban)
Base
Switch
Fabric
Switch
L2 L2
OAM
OAM
S1,S6,S10,
S11,S101
S1,S6,S10,
S11,S101
.
.
.
MAF
MME OAM
MAF
.
.
.
MAF
Shelf 0
MIF MIF
19 11/07/2008
MME LM2.0/LM2.1 IP Configuration Architecture
MME OAM
MAF
MME Hub (Malban)
Base
Switch
Fabric
Switch
MME Interface
Function (HSPP)
MME Hub (Malban)
Base
Switch
Fabric
Switch
MME Interface
Function (HSPP)
10Gb
L2 L2
OAM OAM
S1,S6,S10,
S11,S101
S1,S6,S10,
S11,S101
.
.
.
MAF
MME OAM
MAF
.
.
.
MAF
MME Hub (Malban)
Base
Switch
Fabric
Switch
MME Hub (Malban)
Base
Switch
Fabric
Switch
MAF
MAF
.
.
.
MAF
MAF
.
.
.
Shelf 0
Shelf 1
20 11/07/2008
Optical Interface RTM for MIF

Malban/MIF
AMC 1:
HSPP4
AMC 2:
HSPP4
Zone 3
connector

10 GE optical
1 GE optical
1 GE optical
1 GE optical
1 GE optical
1 GE optical
1 GE optical
1 GE optical
1 GE optical
Base to Other
shelves
External links
HSPP4 # 1
External links
HSPP4 # 2
RTM
10 GE optical
Fabric to Other
shelves
1 GE optical
1 GE optical
Base links
OAM
10 GE optical
RTM used to support
external 1GE to network
SFP support
Single mode
Multi mode
PDN GW SGW MME PCRF
Base
Switch
Fabric
Switch
21 11/07/2008
MME 3-Year Major Software Release Feature
Roadmap
M0.4 LTE Trials

Functionality:
Enables Friendly User Trial
of Commercial Foundation
for MME HW and SW
Basic Mobility
Management &
Authentication
End to End
Signalling/Authentication
(eNB, SGW & HSS)

Interfaces:
S1-MME MME/eNB
S11 MME/SGW (external)
S6a MME/HSS
M2.0 Commercial
Launch Data
Interworking
Functionality:
Enable commercial scaled
deployments
Increased capacity
Pooling
Lawful Intercept
IPV6 Transport
Non Optimized 3GPP HO
(NAC)

Trial Support for:
- Pre-Rel8 Data Hand-Off
- SGs base CS Fallback UMTS,
GSM
- SMS over LTE via SGs

Interfaces:
SGs MME/MSC (3GPP)
S13 MME I/F to EIR
S10 MME/MME

M3.0/4.0 Full SGSN
Function

Functionality:
SR-VCC (3G1x)
SR-VCC (GSM, UMTS)
-CDMA Data Hand-Off
SGSN User Plane
Gn mobility for inter
SGSN HO
SGSN legacy features
LTE-WiMax Hand-Off
Location Based Services
EWTS/CMAS

Interfaces:
Gr MME/HLR
Iu-CP MME(SGSN)/RNC
Iu-UP MME(SGSN)/RNC
Slg MME/VGMLC
Sls MME/SMLC
SBc MME/CBC
S1-AP MME/eNodeB

M1.0/1.1 Ltd
Commercial Deployment

Functionality:
Enable Limited Commercial
Deployments
Enhanced Mobility
Management &
Authentication

Trials Support of:
- 3G1x CDMA Dual
Transceiver
- Pre-Rel8 Data Hand-Off
- CS over LTE Voice

Interfaces:
Gn MME/Pre-Rel8 SGSN
Sv MME/MSC (trial)
4Q 3Q 4Q 3Q 2Q 1Q
2009 2011
2Q 1Q 2Q 1Q
2010 2011 2009
M0.4
POI
M1.1
POI
M2.0
POI
M2.1
POI
4Q 3Q
M2.1 CS Interworking

Functionality:
CDMA CS Fall Back
SMS over LTE via S102
CDMA Data Hand-Off
SGs base CS Fallback UMTS,
GSM
CDMA CS Fall Back
SMS over LTE via SGs
Idle Mode Signaling
reduction
IP Sec all Interfaces

Trials Support of:
Rel8 Data Hand-Off

Interfaces:
S101 MME/eHRPD
S3 2G/3G Rel8 SGSN
S102 MME/3G-1X

M3.0
POI
M4.0
POI
M1.0
POI
22 11/07/2008
CS voice services over LTE
Using dedicated Interworking
Function

23 11/07/2008
Voice over LTE options
No voice over LTE
LTE used as a data only service with data only terminals

IMS based voice services over LTE
Direct application of IMS standards using EPC based procedures for handovers
Requires definition of voice application support in UE (IMS profile based on RCS?)
Two cases depending upon legacy voice support: CS only or IMS (VoIP) over 3G
Requires Single Radio Virtual Call Continuity (SRVCC)

CS Fallback (CSFB)
Page in eUTRAN, call in GSM/WCDMA approach
Defined in 3GPP rel. 8 under 23.272

CS over PS
TMO driven variant of evolved MSC alternative from TR 23.879
Using a normal MSC plus a dedicated interworking function to handled interface with MME

Note: Other solutions exist and are discussed in CS over EPS study item (23.879)
24 11/07/2008
Environment and Assumptions
T-Mobil is primary driver for CSoPS
Support Voice on LTE ASAP
TMO considers it is impossible to offer voice service with CS Fallback on 2G
because of poor services and performances
Solution to be based on Circuit Switched (CS) voice bearer
TMO considers it is impossible for them to deploy IMS, TAS, ICS, SR-VCC in addition
to modifications to charging network, subscriber management and customer care
by 2012
Leverage existing base of MSC
Implies inserting and IWF between EPC and MSC, where the IWF would be
perceived as a RNC/BSC by the MSC
Proposed approach
Minimise changes to LTE and EPC
Add dedicated Interworking Function between EPC and legacy MSC
Exploit SRVCC mechanisms in MME to trigger handover
Standards to be developed in VOLGA forum and transferred to 3GPP
25 11/07/2008
CSoPS Architecture
IWF perceived as a BSC/RNC for the MSC(s)
Iu over IP (and/or A over TDM) interface to MSC
IWF perceived as an Application Server by the EPS
Rx interface to PCRF to manage EPS resources
Sv interface as defined for SR-VCC to handle co-ordination with MME
New protocol, Z1, to carry CS layer 3 signaling between UE and IWF
Z1
UE
BTS/
BSC
NodeB
/RNC
eNodeB
S-GW/
PDN-GW
S1-UP
IWF
SGi
MSC/
VLR
A
Iu/A
HSS D
PCRF
Rx
Gx
Iu
MME
Sv
S1-MME
26 11/07/2008
Short description
Approach
2/3G call setup signalling and CS voice streams over IP pipe transported over LTE data bearer
(messages will depend on choice of Iu and A interface)
Connects to MSC via existing Iu-cs using dedicated gateway, Sv to MME (handover) and Rx to PCRF
(QoS)
Solution based on dedicated IWF
Handover
Based on re-use of SRVCC signalling interface (Sv) to trigger Iu-cs based CS handover in parallel with
PS LTE<>2/3G
Key elements and interfaces
CSoPS IWF (NAS and RANAP handling, UE CS services attachment)
CSoPS MGW (User plane handling)
CSoPS client in terminal
Iucs (and/or A) CSoPS IWF+MGW and MSC (same as 2/3G RAN)
Sv interface MME and CSoPS IWF (same as SRVCC)
Rx interface PCRF and CSoPS (same as IMS PCRF control)
27 11/07/2008
Main elements for ALU solution
PDN
GW
CSoLTE
MGW
SGW
eNB
RNC
Node B
SGSN-C
Rel8
UTRAN
E-UTRAN
S5/S8
S1u
S1-mme
S12
MGW
S11
S3

Iu ps
Iu cs-u
SGW
megaco
IMS voice and PS data
CS Voice and PS data
SGi
PCRF
ISUP
Rx
Gx
Sv

BSC
BTS
GERAN
S4
Gb
A
MSC-S
Rel8
MME
CSoLTE
IWF
H.248?

DHCP/
DNS
Iu cs-u
Iu cs-c
9474 IWF (tbc)
CSoLTE IWF control plane
element
Based on 9471 MME platform
7510 IWF MGW (tbc)
CSoLTE IWF user plane
element
Based on 7510 MGW platform
9471 MME
Minor or zero changes for
CSoPS
MUST support SRVCC
DHCP/DNS server
Based on IMS solution
Required Tracking Area
mapping table
5750 SCC
Zero changes for CSoPS
MUST support Rx
9326 eNodeB
Zero changes for CSoPS
MUST support 2/3G
handover initiation
HSS
S6a

8650 SDM HSS
Minor or zero changes for CSoPS
MUST support SRVCC
28 11/07/2008
Iu cs-u
PDN
GW
Main elements and streams (user plane and control)
CSoLTE
MGW
SGW
eNB
RNC
Node B
UTRAN
E-UTRAN
S5/S8
S1u
S1-mme
S12
Iu cs-c
S11
Iu cs-u
VoIP and PS data
SGi
PCRF
Rx
Gx
Sv

BSC
BTS
GERAN
S4
A
ISUP
V
S
V
CSoLTE
IWF
1. EPC Attach 2. CSoLTE Attach 3. CSoLTE Call 4. Handover 5. Call end
H.248?

DHCP/
DNS
HSS
MME
S6a

MSC
29 11/07/2008
Single 44U ONLY enclosed
Cabinet
Single ATCAv2 (300W per slot)
chassis
Redundancy configured
horizontally
1 pair of Shelf Management
Cards (ShMCs)
1 pair of Ethernet Hubs
(Malban1)
1 pair of Rouzic (LAF)
1 pari of Rouzic (LIF)

PDU
S
h
M
C

S
h
M
C

Product Overview
LVI-C LV1.1 Hardware Configuration
LVI Packaged in
separate MME type
44U frame
AdvancedTCA (PICMG3.x)
D
i
s
k

O
A
M

S
e
r
v
e
r

I
P

S
w
i
t
c
h

S
h
M
C

S
h
M
C

Rouzic Malban1
L
A
F

S
e
r
v
i
c
e

L
A
F

S
e
r
v
i
c
e

D
i
s
k

O
A
M

S
e
r
v
e
r

I
P

S
w
i
t
c
h

L
I
F

S
e
r
v
i
c
e

L
I
F

S
e
r
v
i
c
e

Red Hat Linux 5
Rouzic or
Molene pair
per faux-RNC
30 11/07/2008
LVI Internal Architecture
2G/3G
Core Network
A or IuCS
2G MSC
3GMSC
R3
R4
R5
R6
NML
OAM Network
User LAF
Registry
LVI Interface Function
L
D
A
C
Diam
eter
Sv Intfc
Rx Intfc
H.248 Intfc
S
C
T
P
S
i
g
t
r
a
n

IuCS Intfc
Link/CIC
Mgmt
I
P
M
MWare
MWare
MidWare
LVI
Hub
Base Host
MWare
MWare
MidWare
Ethernet
Switch
LVI
OAM Server
MWare
MWare
MidWare
Perf Mon
-
LVI Application Function
I
P
M
MWare
MWare
MidWare
2
nd

Tier
LD
CXN
Manager
LVI Connection Context
UEl
Mgmt
Bearer
Mgmt
Intfc
Proxy
LVI Application Function
Last LAF

A Intfc
Z1 Intfc
PDN
GW
R1
R2
LTE
RAN
LTE Z1
Rx
PCRF
MME
Sv
IPv4
IPv6
IPsec
NAT
SC
CP
TCP
UDP
GTP
H.248
7510
Link
Mgmt
UE Data
Registry
H.248 DS
31 11/07/2008
LVI LV1.1 IP Configuration Architecture
LVI OAM
LAF
LVI Hub (Malban)
Base
Switch
Fabric
Switch
LVI Hub (Malban)
Base
Switch
Fabric
Switch
L2 L2
OAM
Z1, Rx, A/Iu
H.248, Sv
.
.
.
LAF
LVI OAM
LAF
.
.
.
LAF
Shelf 0
LIF LIF
Z1, Rx, A/Iu
H.248, Sv
32 11/07/2008
LVI-C Major Software Release Feature Roadmap
M2.0 Trial Phase 2
Functionality:
Active VoLGA call
Handover from LTE to GSM
IPv4 and IPv6
Support for multiple
simultaneous addresses for
different APNs
1 dedicated bearer for
signaling and voice
PS mobility from
GSM/UMTS to LTE (no PS
HO)
Cell Site Reselection
between LTE & GSM/UMTS
PS mobility from LTE to
GSM Redirection & NACC (no
PS HO)
PS mobility from LTE to
UMTS Redirection & PS HO

M3.0 Commercial
Release

Functionality:
Many to Many element
relationships
IPSec support for Z1
Signaling
Semi-Persistent
Scheduling for Voice
Traffic
Multiple VANC
including HOSF

Interfaces:
Iu
Secure Interfaces
Lawful Intercept
Interfaces for online,
offline charging
M1.1 Trial Phase 1

Functionality:
Single VANC
Centralized deployment

Trials Support of:
Active VoLGA call
UE IP Address
IPv4
Single IP address

Interfaces:
A interface to 2G MSC
Pre-Release-8 with Gn
interface
4Q 3Q 4Q 3Q 2Q 1Q
2009 2011
2Q 1Q 2Q 1Q
2010 2011 2009
LV1.1 LV2.0 LV2.1
4Q 3Q
M2.1 Place Holder

Functionality:

Interfaces:

LV3.0
33 11/07/2008
Backup
34 11/07/2008
LTE, EPS, E-UTRAN and EPC
3GPP LTE (Long Term Evolution), an evolution of GSM/UMTS, specifies
the next generation 3GPP mobile broadband network
The mobile broadband network is called Evolved Packet System (EPS)
The EPS consists of Evolved UTRAN (E-UTRAN) and Evolved Packet
Core (EPC)
For 3GPP high level requirements on UTRA-UTRAN Long Term
Evolution (LTE) and 3GPP System Architecture Evolution (SAE), read
http://www.3gpp.org/Highlights/LTE/lte.htm
Phase 4 Chalk talks, EPC FDD links:
http://mobility.ih.lucent.com/~jlic/lte.htm
EPC FDD 7090: http://mobility.ih.lucent.com/~slaha/LTE/
MME sites:
https://sps.ndc.lucent.com/sites/wireless.mme/default.aspx - App Arch
https://sps.ndc.lucent.com/sites/wireless.mme_sae/default.aspx - SAE

35 11/07/2008
Resources - external
VOLGA

3GPP
23.009: Handover procedures
Existing Iu-cs procedures
23.216: Single Radio Voice Call Continuity (SRVCC)
Mechanism to combine IMS to CS transfer with LTE to 2/3G handover
23.228: IP Multimedia Subsystem (IMS)
Based standard for IMS calls
23.272: CS Fallback
UE forced to handover to 2/3G on call establishment or voice paging - proposed Rel8 approach for Voice
services over LTE
23.292: IMS Centralised Services (ICS)
Offers IMS based applications (in CSCF and AS) via MSC and CS bearers
23.237: IMS Service Continuity (ISC)
Service continuity for cases PS-CS using ICS, PS-PS and PS-PS in conjunction with PS-CS
23.401/402:
EPC procedures including handover between LTE and 2/3G coverage
23.879: CS services over evolved PS access (CSoPS)
Study offering 5 alternatives for CS voice services - applicable if IMS over LTE not supported

36 11/07/2008
LTE Standard Reference Points (1 of 2)
S1-MME: Reference point for the control plane protocol between E-UTRAN and MME.
S1-U: Reference point between E-UTRAN and Serving GW for the per bearer user plane
tunnelling and inter eNodeB path switching during handover.
S2a: It provides the user plane with related control and mobility support between
trusted non 3GPP IP access and the Gateway.
S3: It enables user and bearer information exchange for inter 3GPP access network
mobility in idle and/or active state. It is based on Gn reference point as defined
between SGSNs.
S4: It provides related control and mobility support between GPRS Core and the 3GPP
Anchor function of Serving GW and is based on Gn reference point as defined between
SGSN and GGSN. In addition, if Direct Tunnel is not established, it provides the user
plane tunnelling.
S5-PMIP: It provides user plane tunneling and tunnel management between Serving GW
and PDN GW. It is used for Serving GW relocation due to UE mobility and in case the
Serving GW needs to connect to a non collocated PDN GW for the required PDN
connectivity.
S6a: This interface is defined between MME and HSS for authentication and
authorization.
S6c: It is the reference point between PDN Gateway and 3GPP AAA server/proxy for
mobility related authentication if needed. This reference point may also be used to
retrieve and request storage of mobility parameters. This reference point may also be
used to retrieve static QoS profile for a UE for non-3GPP access in case dynamic PCC is
not supported.
37 11/07/2008
LTE Standard Reference Points (2 of 2)
S7: It provides transfer of (QoS) policy and charging rules from PCRF to Policy and
Charging Enforcement Point (PCEF) ) in the PDN GW.
S7a: It provides transfer of (QoS) policy information from PCRF to the Trusted Non-
3GPP accesses.
S7b: This interface is not specified within this release of the specification.
S7c: It provides transfer of (QoS) policy information from PCRF to the Serving Gateway
S8: It is the roaming interface in case of roaming with home routed traffic. It provides
the user plane with related control between Gateways in the VPLMN and HPLMN.
S9: It provides transfer of (QoS) policy and charging control information between the
Home PCRF and the Visited PCRF in order to support local breakout function. In all
other roaming scenarios, S9 has functionality to provide dynamic QoS control policies
from the HPLMN.
S10: This interface is reference point between MMEs for MME relocation and MME to
MME information transfer.
S11: This interface is reference point between MME and Serving GW.
S103-U: This interface is the bearer interface between the EPC Serving Gateway and
the HSGW,
S101: This interface is the signaling interface between the EPC MME and the evolved
HRPD Access Network (eAN/PCF).
X2: This interface is for eNodeB to eNodeB handoff.

38 11/07/2008
Resources - internal
E2E LTE-GSM SAE team
Web site: http://mobility.ih.lucent.com/~slaha/CSoPS/
Team meetings: Tuesdays, 9:30-11:00AM CT US
Former CTO/NTS web site
LTE-MME Sharepoint site
https://sps.na.alcatel-
lucent.com/sites/wireless.mme_sae/Shared%20Documents/Forms/AllItems.a
spx
CSoverPS Sharepoint site
https://sps.na.alcatel-
lucent.com/personal/robinthompson/CSoPS/default.aspx
39 11/07/2008
Iu-cs Control plane protocol stack (DRAFT Under definition within
VOLGA)
Key features
UE-MSC signalling transparently relayed by IWF
RANAP terminated in IWF which generates corresponding Rx messages for
radio bearers
PDCP
IP
MM
CC/SS/SMS
Ethernet
IP
New Protocol RANAP RANAP
MM
CC/SS/SMS
Z1 Iu_CS
UE IWF MSC/VLR
Signalling
Transport
Layers
(TS 25.412)
TCP/SCTP TCP/SCTP
Signalling
Transport
Layers
(TS 25.412)
New Protocol
RLC
MAC
PHY
EPS
IP
Ethernet
PDCP
RLC
MAC
PHY
SGi
IPSec functions
(see Note 1)
IPSec functions
(see Note 1)
NOTE 1: It is FFS whether IPsec security is required between the UE and IWF
40 11/07/2008
A Interface Control plane protocol stack (DRAFT Under definition within
VOLGA)
Key features
UE-MSC signalling transparently relayed by IWF
BSSMAP terminated in IWF which generates corresponding Rx messages for radio
bearers
NOTE 1: It is FFS whether IPsec security is required between the UE and IWF
PDCP
IP
MM
CC/SS/SMS
Ethernet
IP
New Protocol BSSAP BSSAP
MM
CC/SS/SMS
Z1 A
UE IWF MSC/VLR
Signalling
Transport
Layers
TCP/SCTP TCP/SCTP
Signalling
Transport
Layers
New Protocol
SCCP SCCP
RLC
MAC
PHY
IPSec functions
(see Note 1)
IPSec functions
(see Note 1)
EPS
IP
Ethernet
PDCP
RLC
MAC
PHY
SGi
41 11/07/2008
Evolved Mobility Management
42 11/07/2008
MME Mobility & Connection Management
MME maintains two types of state information to manage UE mobility &
UE/EPC connectivity
EPS Mobility Management (EMM) states describe the mobility status of
UEs resulted from mobility management procedures
EPS Connection Management (ECM) states describe the signaling
connectivity between the UE & the EPC
43 11/07/2008
EPS Mobility Management (EMM) States
EMM context holds no valid
location or routing info for
the UE
UE is not reachable by the UE
as the UE location is not
known
EMM-DEREGISTERED
EMM-REGISTERED
Attach
Detach
UE successfully registers with
UE with Attach procedure
UE position is known in
within tracking area
MME can send page to UE
44 11/07/2008
EPS Connection Management (ECM) States
No signaling connection
between UE and core
network (S1-U, S1-MME)
No RRC connection
UE performs cell reselection
and tracking area updates
ECM-IDLE
ECM-CONNECTED
Signaling Connection
Established
Signaling Connection
Released
Signaling connection is
established between the UE
and MME
UE location is known to the
accuracy of the cell ID
45 11/07/2008
EPS Identities
IMSI
The International Mobile Subscriber Number is assigned to each mobile subscriber in
GSM/UMTS/EPS systems. The maximum number of digits used for IMSI is 15. The IMSI is made
up of Mobile Country Code (MCC) (3 digits) + Mobile Network Code (MNC) (2-3 digits) + Mobile
Subscriber Identification Number (MSIN) (9 or 10 digits). In EPS, S-TMSI is used to page a
mobile. Refer to GUTI definition for the definition of S-TMSI.
TMSI
The Temporary Mobile Subscriber Number (TMSI) is assigned to support subscriber identity
confidentiality service. The 3GPP documents use the following notation to identify which entity
assigned a TMSI: simple TMSI is used if it is assigned by MSC, P-TMSI is used if assigned by SGSN
and M-TMSI is used if assigned by MME. M-TMSI is part of the GUTI. Refer to 23.003 for details on
TMSI.
GUTI
The Globally Unique Temporary Identity purpose is to provide an unambiguous identity of the UE
that does not reveal the UE or the users identity. The GUTI has two components:
Globally Unique MME Identifier (GUMMEI) that uniquely identifies MME that assigned the GUTI
and M-TMSI which identifies a UE uniquely within the MME that allocated the GUTI. The
GUMMEI consist of MCC, MNC and MMEI (MME Identifier). The MMEI has 16 bits of MME group ID
and 8 bits of MME code. The M-TMSI is 32 bits long.
46 11/07/2008
EPS Identities
TAI
The Tracking Area Identity is used to identify tracking areas. A tracking are
is defined in EPS as a geographical area in which a mobile subscriber can
freely roam without informing its location (tracking area updates). A
tracking area may consist of one more cells. The TAI consists of MNC, MCC
and TAC (Tracking Area Code).
eNB S1AP UE ID
The eNB S1AP UE Identifier is a temporary identifier to identify a UE on S1
reference point within the eNB. It is unique within the eNB.
MME S1AP UE ID
The MME S1AP UE Identifier is a temporary identifier to identify a UE on S1
reference point within the MME. It is unique within the eNB.
47 11/07/2008
EPS Identities Bearer ID
EPS Bearer ID
An EPS bearer identity uniquely identifies an EPS bearer for one UE accessing via E-
UTRAN (eNB). The EPS Bearer Identity is allocated by the MME. There is one to one
mapping between EPS RB and EPS Bearer, and the mapping between EPS RB Identity
and EPS Bearer Identity is made by E-UTRAN. The following diagram is used to
illustrate the definition of EPS bearer and its components: Radio Bearer, S1 Bearer
and S5/S8 Bearer.
P-GW S-GW Peer
Entity
UE eNB
EPS Bearer
Radio Bearer S1 Bearer
End-to-end Service
External Bearer
Radio S5/S8
Internet
S1
E-UTRAN EPC
Gi
S5/S8 Bearer
48 11/07/2008
Default & Dedicated Bearers
UE
eNB
S-GW
PGW1
A
P
N
_
1

A
P
N
_
2

PGW0
Default Bearer Context 1[PDN-Addr-1, QoS-1, Bearer-ID-1]
Default Bearer Context 2[PDN-Addr-2, QoS-2, Bearer-ID-2]
Dedicated Bearer Context31[PDN-Addr-3, QoS-3, Bearer-ID-3, LBI]
GTP-Tunnel-1
GTP-Tunnel-2
GTP-Tunnel-3 GTP-Tunnel-6
GTP-Tunnel-5
GTP-Tunnel-4
RB-2
RB-3
RB-1
PDN-2
PDN-1
49 11/07/2008
Evolved Mobility Management Procedures
Attach Procedure: To receive any service from the network, the UE needs to
register with the network. This is referred to as network attachment. During this
procedure, default bearers are assigned along with possible allocation of the IP
address to the UE.
Tracking Area Update: The UE performs this procedure periodically as well as upon
its entry to an unregistered new tracking area to notify its availability/location to
the network and/or to obtain the new local identity (S-TMSI).
Service Request: This procedure changes the EMM mode of the UE/MME from ECM-
IDLE to ECM-CONNECTED and establish the radio and S1 bearers when uplink user
data is to be sent or downlink data/signaling from the network is to be receive
S1 Release Procedure: This procedure is used for the release of all S1 bearers for a
UE, including all S1-U bearers and the S1-MME signaling connection for the UE.
Detach Procedure: This procedure has the opposite effect of the Attach procedure
and terminates the access of the UE to the EPS. It may be initiated either by the UE
or the network.
Intra-EUTRAN Handover: This procedure involves handover of the UE from a source
eNB to a target eNB with/without MME change, with/without S-GW change.
50 11/07/2008
Ranga Tota 1 Initial Attach with IMSI No UE context in MME 23.401 V8.3.0 & 24.301 V1.0.0
UE eNB MME
SGW/
PGW HSS
Nov 6, 2008
(M1) Attach Request with
PDN Connectivity
Request
(M2) S1AP Initial UE Message
with the Attach Request
(M3) Authentication Request
(M4) Authentication Response
(M5) Authentication Request
(M6) Authentication Response
(M7) Security Mode Command
(M8) Security Mode Complete
Identity Request/Response if required
(M9) PCO/APN Request
(M10) PCO /APN Response
(M11) Update-Location-Request
(M12) Update-Location-Answer
(M13) Create Session Request
(29.274 7.2.1)
51 11/07/2008
Ranga Tota 2 Initial Attach with IMSI No UE context in MME 23.401 V8.3.0 & 24.301 V1.0.0
UE eNB MME
SGW/
PGW HSS
Nov 6, 2008
Alcatel-Lucent Technologies Proprietary
(M14) Create Session Response
((29.274 7.2.2)
(M15) S1AP Initial Context Setup
with Attach Accept &
Activate Def EPS Bearer Context
Request
RRC Connection Reconfiguration
(M16) S1 Initial Context Setup Response
(M17) Attach Complete with
Accept Def EPS Bearer
Context Accept
(M18) First Uplink Data
(M19) Modify Bearer Request
(29.274 7.2.7)
(M20) Modify Bearer Response
Notify Request/Response if needed
(M21) First Downlink Data
52 11/07/2008
1 LTE X2 Based Handover without SGW Relocation - 23.401 V8.3.0 29.274 V1.3.0
UE
Source
eNB
Target
eNB MME
SGW/
PGW
Nov 6, 2008
Downlink/Uplink Data
Downlink/Uplink Data
Handover Preparation
Handover Execution
(M1) Forwarding of Data
(M2) Uplink Data
(M3) Uplink Data
(M4) S1AP Path Switch Request
(M5) User Plane Update Request Message
(M6) User Plane Update Request Response
Downlink Data
(M7) Deactivate Bearer Request
(Deactivates bearers that target eNB
did not set up. The message need to be defined
in IOS and 29.274)
(M8) Delete Bearer Request
(M9) S1AP SAE Bearer Release Request
(M10) Deactivate EPS Bearer
Context Response
53 11/07/2008
2 LTE X2 Based Handover without SGW Relocation - 23.401 V8.3.0 29.274 V1.3.0
UE
Source
eNB
Target
eNB MME
SGW/
PGW
Radio Bearer Release Request/Response
(M11) SAE Bearer Release Response
(M12) Deactivate EPS Bearer
Context Request
(M13) Deactivate Bearer Response
(M14) End marker
(M15) End marker
(M16) S1AP Path Switch Request Ack
(M17) Release Resources
Tracking Area Update Procedure
if required
54 11/07/2008
1 Service Request 23.401 V8.3.0 & 24.301 V1.0.0
UE eNB MME
SGW/
PGW HSS
Nov 6, 2008
(M1) Service Request
(M2) S1AP Initial UE Message
with the Service Request
Authentication if needed.
Is Update Location Needed?
(M3) S1AP Initial Context Setup
Activate Def EPS Bearer Context
Request
RRC Connection Reconfiguration
(M4) S1 Initial Context Setup Response
(M5) Activate Def EPS Bearer
Context Accept
(M6) First Uplink Data
(M7) Modify Bearer Request
(29.274 7.2.7)
(M8) Modify Bearer Response
(M9) First Downlink Data
55 11/07/2008
Paging
DDN Ack
UE eNB MME S-GW PDN GW
Downlink Data Notification
Downlink Data Notification
Paging
Paging
Service Request
continue with Service Request procedure
56 11/07/2008
1 UE Initiated Detach
UE eNB MME
SGW/
PGW HSS
Nov 6, 2008
(M1) Detach Request
A1: If there is S1
connection then eNB
forwards message in
S1AP Uplink NAS
transfer message. If
S1 does not exist
then eNB sends
using S1AP UE
initial message.
(M2) Uplink NAS Transfer or
Initial UE Message
Delete Session Request/Response
(M3) Detach Accept
MME uses the downlink NAS Transport.
No need to use Initial Context Setup.
(M4) S1AP UE Context Release Command
(M5) S1AP UE Context Release Response
57 11/07/2008
2 UE Initiated Detach
UE eNB MME
SGW/
PGW HSS
Nov 6, 2008
A2: MME deletes all
eNB related
information but
keeps all UE related
bearer information
in the UE context.
SGW also keeps this
information.

LTE Overview

Caricato da

Informazioni sul documento

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

LTE Overview

Caricato da

Copyright:

Formati disponibili

Alcatel-Lucent Proprietary

Potrebbero piacerti anche