Core Network Dimensioning

07/08/2016
Core network and

transmission
dimensioning
Sami TABBANE
CONTENTS
I. Introduction
II. Evolved Packet Core
III. Core network Dimensioning
IV. Summary
1
07/08/2016
CONTENTS
I. Introduction
Introduction
 LTE Commercialization
• 351 Operators in 104 Countries are investing in LTE

• 105 LTE Commercial LTE Networks Launched in 48 Countries
2
07/08/2016
Introduction
 LTE: Fast Market Growth
• 100 LTE Commercial Launches within 3 years of the first launch

• WCDMA took longer than 4 year for 100 commercial launches
• 100M LTE Subscribers within 3.3 year expected
Introduction
 World evolution of mobile data traffic
3
07/08/2016
Introduction
 3GPP technologies are based on CDMA and OFDMA

technologies
• WCDMA and HDPA are based on CDMA

• LTE is based on OFDMA
Introduction
Advantages
 Provide low latency

 Higher network throughput
 Increased data transfer speed
 More cost effectiveness
 Improvements over 3G network
4
07/08/2016
CONTENTS
II. Evolved Packet Core
Evolved Packet Core
 3GPP Core Network Evolution
 3GPP Network has evolved from 4 tier architecture to 3 tier architecture
2G /3G PTSN
CDMA/EV-DO Circuit swirched
Voice core voice
GSM/GPRS channels Other
EDGE Mobile
networks
UMTS BSC/RNC
HSPA IP channel BTS Packet swirched Internet
NodeB core data
VPN
LTE
eNodeB
Evolved packet core
IP channel (all–IP)
eNodeB Transport (backhaul and backbone)
10
5
07/08/2016
Evolved Packet Core
Evolved core network
IP channel
S-GW MME P-GW PCRF

eNodeB
Service delivery platforms
IP communications Advanced location based services

(VoiP, video) • Mobile Tv, IP mULimedia
• Messaging SMS/MMS • Mobile office
• Internet, Web 2.0
11
Evolved Packet Core
 Radical changes in the network
 End of circuit-switched voice:

• LTE uses a new paradigm for voice traffic — VoIP.
 Evolved wireless broadband
 Mobility as a part of the core network:

• In LTE, all mobility management is moved into the mobile
core and becomes the responsibility of the MME.
12
6
07/08/2016
Evolved Packet Core
 Radical changes in the network
 End-to-end QoS becomes essential:

• LTE must provide superior end-to-end QoS management and
enforcement in order to deliver new media-rich, low-latency and
real-time services.
 Policy management and enforcement:

• Service control is provided via the Policy and Charging Rules
Function (PCRF)
• PCRF dynamically controls and manages all data sessions and

provides appropriate interfaces towards charging and billing
systems.
• LTE requires significantly more capacity in both the data plane and
control plane.
13
Evolved Packet Core
 4G (LTE) architecture
2G RNC SGSN
SAE GW S5/S8
3G
SGW P-GW
S1-U
S11
S7 (Gx)
MME PCRF
S1-C
S6a
eNode B
HSS
X2
eNode B
14
7
07/08/2016
Evolved Packet Core
 The EPC is realized through four new elements:
• Serving Gateway (SG-W)

• Packet Data Network (PDN) Gateway (P-GW)
• Mobility Management Entity (MME)
• Policy and Charging Rules Function (PCRF)
 SGW, PGW and MME are introduced in 3GPP Release 8,

 PCRF was introduced in 3GPP Release 7
15
Evolved Packet Core
Serving Gateway (S-GW)
Manage user-plane mobility  acts as an interface between the RAN and

core networks.
Maintains data paths between eNodeBs and the PDN Gateway (PGW).
Evolved core network
IP channel
S-GW MME P-GW PCRF

eNodeB
eNodeB
 SGW is the termination point of the packet data network interface towards
E-UTRAN.
16
8
07/08/2016
Evolved Packet Core
 Packet Data Network (PDN) Gateway (P-GW)

The termination point of the packet data interface towards the Packet Data Network(s).
the PDN GW supports:
• Policy enforcement features

• Packet filtering (for example, deep packet inspection for application type detection)
• Charging support (for example, per-URL charging)
In LTE, data plane traffic is carried over virtual connections called service data flows
(SDFs).
One or more SDFs are aggregated and carried over one bearer.
17
Evolved Packet Core
 Mobility Management Entity (MME)
• It performs the signaling and control functions to manage the User

Equipment (UE) access to network connections, the assignment of network
resources, and the management of the mobility states to support tracking,
paging, roaming and handovers
The MME supports:
• Security procedures: End-user authentication as well as initiation and

negotiation of ciphering and integrity protection algorithms.
• Terminal-to-network session handling
• Idle terminal location management
18
9
07/08/2016
Evolved Packet Core
 Policy and charging rules function (PCRF)
• A concatenation of Policy Decision Function (PDF) and Charging Rules Function

(CRF)
• A control plane element that is not strictly speaking, an EPC element, but is
required to give dynamic control over bandwidth, charging, and network usage
AF
 Policy and Charging Enforcement Function (PCEF):
PCRF
supports service data flow detection, policy
enforcement and flow-based charging. Online
 Application Function (AF): SGW PGW charging
supports applications that require
dynamic policy and/or charging Offline
control. charging
 shows how PCRF interfaces with other EPC elements..

19
Evolved Packet Core
EPC deployment model
Deployment architecture Centralised Function Distributed Function
SGSN+GGSN+MME+SGW
Completely centralised
+PGW
MME+SGSN+GGSN+SGW
Completely distributed
+PGW
Centralised bearer/
SGW+PGW+GGSN MME+SGSN
Distributed control
Centralised control/
MME PGW+SGW
Distributed bearer
20
10
07/08/2016
CONTENTS
III. Core network Dimensioning
21
Core network Dimensioning
 General wireless network planning process
Pre-planning • Collect area parameters .

• Detailed information of EPC core
network
• Superficies
Dimensioning: • Subscribers information
Coverage and capacity constraints
Requirements and  Minimize exploited resources
Strategy for coverage, Output
capacity and quality • Equipment capacity
Output:
• Offered services
• Necessary capacity
• Number of subscribers
• User Traffic rate
Coverage planning • Signaling traffic
Capacity equipment
Parameters planning
Geographical site position

Optimization  Maximize the coverage
Performance analysis in
terms of quality and
interference KPI (Key performance indicator)
 QoS requirements
22
11
07/08/2016
CORE NETWORK DIMENSIONING
1. Dimensioning Phases
23
Dimensioning Phases
 Traffic Dimensioning
Subscribers
Equipment demands
dimensioning
Dimensioning Traffic
Number of
Signaling Traffic
equipment needed
Data Traffic
24
12
07/08/2016
Dimensioning Phases
 Dimensioning preliminary phases

Initial parameters • Number of subscribers, N
configuration • Number of smartphone

• Number of data card
Handsets profiles
configuration
• Session size
• Number of sessions during the busy hour
Traffic at Busy hour • Traffic percentage in DL
• Data traffic carried in VPNs or for Internet services
Signaling Traffic • Network attach and detach

• Bearer activation
• HO procedures
• Tracking area update 25
2. Traffic dimensioning at BH
26
13
07/08/2016
Traffic dimensioning at BH
 Initial parameters (Number of smartphones and data cards)
Nc= NA* PC
NS =NA* Ps
Where:
Nc: Number of data cards

NA: Total subscribers number
PC: Data card percentage
NS: Total smartphones number
Ps: Smartphones percentage
27
 Smartphone profile in Busy hour
With smartphones we can access to:

• Streaming
• Interactive video games
• Download
• Internet Service characteristics:
• Session size
• Number of possible sessions at
busy hour
 Traffic at busy hour:
ρS BH-DL/UL = (Tsession*Nsession)
Where
ρS BH-DL/UL: Traffic volume in UL/ DL at Busy hour
Tsession : Exchanged data volume per session
Nsession: Number of sessions at BH
28
14
07/08/2016
 Traffic on DL:
ρS BH-DL = (ρS BH-DL/UL ) * ρ DL

Where:
• ρS BH-DL/UL: Traffic volume at Busy hour
• ρS BH-DL: Traffic volume on the DL
• ρ DL : Percentage of DL traffic
29
 Traffic during BH
 Smartphones Total traffic

ρS DL/UL= ρS BH-DL/UL *Ns
ρS DL/UL: Smartphone total traffic at Busy hour
 Data card total traffic
ρCD DL/UL= ρCD Internet-BH-DL/UL *NCD
ρS DL/UL: Smartphone total traffic at Busy hour
30
15
07/08/2016
 Internet services Throughput at BH
 Total traffic Internet services
ρInternet DL/UL = ρS DL/UL + ρCD DL/UL
 Throughput of Internet services
THInternet BH-DL/UL = (ρInternet DL/UL *8) / 3600
Where
THInternet BH-DL/UL: Internet services throughput at busy hour
31
 VPN services Throughput during BH
Number of cards supporting this services:

NCD_VPN = NCD*PCD_VPN
NCD_VPN: Number of cards using VPN

PCD_VPN: Percentage of cards using VPN
ρ VPN DL/UL = (ρ CDVPN BH-DL/UL ) * NCD_VPN
THVPN DL/UL = (ρVPN DL/UL *8) / 3600
Where
THVPN DL/UL: Throughput VPN services at busy hour
32
16
07/08/2016
 Traffic in DL
ρS DL = (ρS BH-DL) * Ns
ρS DL = Smartphones total traffic in DL
ρCD DL = (ρCDInternet BH-DL) * NCD
ρCD DL = Data cards total traffic in DL
(ρInternet BH-DL)= ρS DL + ρCD DL
(ρInternet BH-DL)T: Total traffic in DL ( Internet services)
THInternet BH-DL = ((ρInternet DL) *8/3600)
33
 Number of active users at Busy hour
NAU= NA*P AU
NAU: Number of active user at busy hour

PAU: Percentage of active user at busy hour
 Number of operations made at busy hour
NAttach= NAttach/sub/BH*N AU
Nattach: Total number attachment

NAttach/sub/BH: Number of attachment at busy hour
NDetach= NDetach/sub/BH*N AU
NDetach: Total number of detach

NDetach/sub/BH: Number of detach at busy hour
34
17
07/08/2016
NIDLE/ACTIVE= NIDLE/ACTIVE/sub/BH*N AU
• NIDLE/ACTIVE: Total number of transitions idle to active

• NIDLE/ACTIVE/sub/BH: Number of transitions idle to active at busy hour
NPDN= NPDN/sub/BH*N AU
• NPDN: Total number of PDN connections

• NPDN/sub/BH: Number of PDN connections at busy hour
35
NBEARERS= NBEARERS/sub/BH*N AU
NBEARERS: Total number of bearer activation and deactivation

NBEARERS/sub/BH: Number of bearer activation and deactivation per user at busy hour
NTAU_INTER_MME = NTAU_INTER_MME/sub/BH*N AU
NTAU_INTER_MME: Total number of tracking area update inter MME

NTAU_INTER_MME/sub/BH: Number of tracking area update inter MME per user
at busy hour
NTAU_INTER_MME_SGW = NTAU_INTER_MME_SGW/sub/BH*N AU
NTAU_INTER_MME_SGW: Total number of tracking area update inter MME /SGW

NTAU_INTER_MME_SGW/sub/BH: Number of tracking area update inter MME/SGW per user
at busy hour
36
18
07/08/2016
NX2_HO= NX2_HO/sub/BH*N AU
NX2_HO: Total number of handover via X2 interface

NX2_HO/sub/BH: Number of handover via X2 interface per user at busy hour
NS1_HO = NS1_HO /sub/BH*N AU
NS1_HO: Total number of handover via S1 interface

NS1_HO/sub/BH:Number of handover via S1 interface per user at busy hour
NHO_INTER_MME = NHO_INTER_MME/sub/BH*N AU
NHO_INTER_MME: Total number of handover inter MME

NHO_INTER_MME/sub/BH: Number of handover inter MME per user at busy hour
37
 Total number of procedures at busy hour
N proc = NAttach+ NDetach + NIDLE/ACTIVE + NPDN + NBEARERS + NTAU_INTER_MME + NX2_HO

+ NS1_HO + NHO_INTER_MME
N proc: Total Number of procedures
38
19
07/08/2016
3. Equipment dimensioning
39
Equipment dimensioning
a) MME dimensioning
40
20
07/08/2016
MME dimensioning
N MME = E[ Nattach / OC SAU]
N MME: Required number of MME

OC SAU: Capacity MME in simultaneous users attached
N MME= E[NIDLE/ACTIVE /3600)/ OC IDLE/ACTIVE]
OC IDLE/ACTIVE: Capacity MME in Idle to active transactions (in seconds)
N MME= E[NPROC /3600)/ OC TRANS_MME]
OC TRANS_MME: Capacity MME in transactions (in seconds)
41
b) SGW dimensioning
42
21
07/08/2016
SGW dimensioning
N SGW = E[ NBEARERS / OC BEARERS]
N SGW: Required number of SGW

OC BEARERS: Capacity MME in bearers activation and deactivation
N MME= E[NIDLE/ACTIVE /3600)/ OC IDLE/ACTIVE]
 For internet and VPN services:
N SGW = E[ THBH-DL-INTERNET / OC DATA-PROCESSING]
N SGW = E[ THBH-DL-VPN/ OC DATA-PROCESSING]
OC DATA-PROCESSING: Capacity data treatment

43
c) PGW dimensioning
44
22
07/08/2016
PGW dimensioning
N PGW = E[ NBEARERS / OC BEARERS]
N PGW: Required number of PGW
N PGW = E[ THBh-DL-INTERNET / OC DATA-PROCESSING]
N PGW = E[ THBh-DL-VPN/ OC DATA-PROCESSING]
45
d) HSS dimensioning
46
23
07/08/2016
HSS dimensioning
N HSS = E[ NA / OC A]
N HSS: Required number of HSS
OC A: Maximum capacity of HSS in term of subscribers
47
d) PCRF dimensioning
48
24
07/08/2016
PCRF dimensioning
N PCRF = E[ NPROC/3600) / OC TANS_PCRF]
N PCRF: Required number of PCRF
OC TANS_PCRF: Capacity of PCRF in term of transactions ( in seconds)
49
e) Dimensioning of signaling procedures
50
25
07/08/2016
Dimensioning of signaling procedures
0.2 T ≤ NMSG*Duration= Tsignal = TMSG /Throughput ≤ 0.4T
• TMSG: Request signaling size ( in bit)

• Throughput: Transmission throughput
• Tsignal: Time transmission
• NMSG: Number of signaling messages between network elements
TH INT_C = [TMSG * NMSG * NPROC/3600]
• C INT_C= ∑ TH INT_C
• NPROC_x: Number of operations
• TH INT_C: Throughput per interface in the control plane
• C INT_C: Capacity per interface
51
CONTENTS
IV. Case Study
52
26
07/08/2016
Subscribers Information
 Area Information
Population 1 003 700

Market Evaluation 52,6 %
Data Card Percentage 42 %
Smartphones (% ) 27 %
Total Subscribers Data cards Number Smartphones Number
527 947 142 546

221 738
53
Subscribers Information
 Smart-Phone Configuration Profile UL/DL
Number of DL Percentage
Traffic Session size
session at BH (%)
topology
Service Active subscribers
Web
1 2 85
Internet access ALL Browsing
Email 4 0.5 80
VPN 30% of data cards
Video
1 10 95
streaming
VPN 0.25 1 60
Gaming 1 0.04 60
54
27
07/08/2016
CASE STUDY
1. Traffic dimensioning at BH
55
Traffic Volume UL-

UL-DL
 Data session profile for a Smartphone
Traffic Volume at
Traffic Volume at busy
Traffic Number of Session busy hour DL
hour UL/DL
topology session Size(Mb) (Mb)
(Mb)
Web
1 2 2 1.7
Browsing
1.6
Email 4 0.5 2
Video
streamin 1 10 10 9.5
g
VPN 0.25 1 0.25 0.15
Gaming 1 0.04 0.04 0.02

Total Traffic Volume (Internet) 14.04 12.82
56
28
07/08/2016
Traffic Volume UL-

UL-DL
 Data session profile for a Data card
Traffic Volume at
Traffic Volume at busy
Traffic Number of Session busy hour DL
hour UL/DL
topology session Size(Mb) (Mb)
(Mb)
Internet 1 2 2 1.7
3.2
Internet 2 2 4
Internet 1 10 10 9.5
VPN 0.5 2 1 0.6
Internet 1 0.04 0.04 0.02

Total Traffic Volume (Internet) 16.04 14.42
Total Traffic Volume (VPN) 1 0.6
57
Traffic Volume UL-

UL-DL
 Total traffic for office VPN and internet at BH (DL and UL)
Total traffic at BH for Internet

Item
(Mb)
Total traffic volume for all smartphones 1.99
Total traffic volume for all data cards 3.54
Total traffic (Mb) 5.54
BH throughput for intent DL&UL (Gb) 12.31

Data cards using VPN 30%
Total traffic VPN (MB) 0.06
BH throughput for office VPN (GB) 0.14
58
29
07/08/2016
Traffic Volume UL-

UL-DL
 Total traffic for office VPN and internet at BH (DL)
Total traffic at BH for

Item
Internet(Mb)
Total traffic volume for all smartphones 1.827.439
Total traffic volume for all data cards 2.005.513

Total traffic ( Mb) 3.882.952
BH throughput for internet DL&UL ( Gb) 8.62

Data cards using VPN 30%
Total traffic VPN (MB) 39 913
BH throughput for office VPN 0.08
59
CASE STUDY
2. Dimensioning of signaling procedures
60
30
07/08/2016
Dimensioning of signaling procedures
Procedure
Number
Subscriber/BH
Active user at BH 90%
N attach 1 475153
N detach 1 475153
• Busy Hour Active Subscriber N Idle to active 50 23 757 600
N PDN 0,5 237 576

= 527 947 x 90%
= 475 153 N Bearers activ/deactiv 0.5 237 576
N TAUs inter MME 0,01 4752
N TAUs 0,1 47 516
N X2- HO 0,25 118788
N S1- HO 0,25 118788
N HO inter MME 0,01 4752
N Procedure 25 477 654
61
CASE STUDY
3. Equipment dimensioning
62
31
07/08/2016
Components Metrics Unit Value Percentage Operating capacity
SimULaneous attached users

Subscribers 400 000 85% 340000
(SAU)
Idle to active
MME Trans/sec 2600 85% 2210
transition/second
Transactions/second Trans/sec 3000 85% 2550
Number of active bearers bearers 1000000 85% 850000

SGW
Data processing capacity Gbps 10 85% 8.5

PGW
Data processing capacity Gbps 10 85% 8.5

Combines
GW/P-GW
Data c processing capacity Gbps 5 85% 4.25
Subscribers
HSS Number of users supported 3000000 85% 2550000
Trans/sec
PCRF Transactions/second 1600 85% 1360
63
 Required nodes
Component Required number
N MME-OC SAU 1
N MME-IDLE/ACTIVE 3
N MME-Proc 3
N SGW-Bearers 1
N SGW-Data Proc 2
N SGW-VPN 1
N PDNGW-Bearers 1
N PDNGW-DL Internet 2
N PDNGW-VPN 1
N SGW-PDNGW Bearers 1
N SGW-PDNGW DL Internet 3
N SGW-PDNGW DL VPN 1
N HSS 1
N PCRF 5
64
32
07/08/2016
CONTENTS
VI. Summary
65
Summary
 Main Challenges for the Future
• User QoE decrease and operator cost increase due to mobile traffic growth
• Operator revenue growth slows
66
33
07/08/2016
Summary
• Many promising technologies have been identified in 3GPP

• Operator and consumer benefit should be carefully considered when
new technologies are introduced for beyond 4G
67
Thank you
68
34

Core Network Dimensioning

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Core Network Dimensioning

Uploaded by

Copyright:

Available Formats

07/08/2016

Core network and

• 351 Operators in 104 Countries are investing in LTE

 LTE: Fast Market Growth

• 100 LTE Commercial Launches within 3 years of the first launch

 World evolution of mobile data traffic

 3GPP technologies are based on CDMA and OFDMA

• WCDMA and HDPA are based on CDMA

 Provide low latency

II. Evolved Packet Core

Evolved Packet Core

 3GPP Core Network Evolution

 3GPP Network has evolved from 4 tier architecture to 3 tier architecture

Evolved Packet Core

Evolved core network

S-GW MME P-GW PCRF

Service delivery platforms

IP communications Advanced location based services

Evolved Packet Core

 Radical changes in the network

 End of circuit-switched voice:

 Evolved wireless broadband

 Mobility as a part of the core network:

Evolved Packet Core

 Radical changes in the network

 End-to-end QoS becomes essential:

 Policy management and enforcement:

• PCRF dynamically controls and manages all data sessions and

Evolved Packet Core

Evolved Packet Core

 The EPC is realized through four new elements:

• Serving Gateway (SG-W)

 SGW, PGW and MME are introduced in 3GPP Release 8,

Evolved Packet Core

Serving Gateway (S-GW)

Manage user-plane mobility  acts as an interface between the RAN and

S-GW MME P-GW PCRF

Evolved Packet Core

 Packet Data Network (PDN) Gateway (P-GW)

the PDN GW supports:

• Policy enforcement features

Evolved Packet Core

 Mobility Management Entity (MME)

• It performs the signaling and control functions to manage the User

The MME supports:

• Security procedures: End-user authentication as well as initiation and

Evolved Packet Core

 Policy and charging rules function (PCRF)

• A concatenation of Policy Decision Function (PDF) and Charging Rules Function

 shows how PCRF interfaces with other EPC elements..

Evolved Packet Core

EPC deployment model

Deployment architecture Centralised Function Distributed Function

III. Core network Dimensioning

Core network Dimensioning

 General wireless network planning process

Pre-planning • Collect area parameters .

Geographical site position

CORE NETWORK DIMENSIONING

 Dimensioning preliminary phases

configuration • Number of smartphone

Signaling Traffic • Network attach and detach

CORE NETWORK DIMENSIONING

 Initial parameters (Number of smartphones and data cards)