SGSN-MME 16A (Native

& Virtual) Configuration

SGSN-MME Architecture
Objectives
Upon completion of this chapter, the student will be able to :

› Explain the software architecture of Native SGSN-MME using MKVIII

and MkX Hardware
› Understand the hardware architecture of Native SGSN-MME MKVIII
and MkX and its different components
› List the various PIU roles in SGSN-MME
Ericsson SGSN-MME Evolution

IP/Ethernet
based since the year 2000

MkIII
MkV MME 6th NFV
generation
MkII
1st 2nd MkIIIc 3rd 4th MkVI+ 5th
generation generation generation generation generation Cloud

MkI MkIIIb MkIV MkVI MkVIII MkX

2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016

Single Single Single Single Single Single Single Single Dual Dual Dual Multi Multi Multi Multi Multi Multi
core core core core core core core core core core core core core core core core core
Solaris Solaris Solaris Solaris Solaris Solaris Solaris Solaris Linux Linux Linux Linux Linux Linux Linux Linux Linux
VxWorks VxWorks VxWorks VxWorks VxWorks VxWorks VxWorks VxWorks VxWorks VxWorks VxWorks
0.1 0.1 0.1+1 0.1+1 1 1 1 1 1+10 1+10 1+10 1+10+40 1+10+40 1+10+40 1+10+40 Native Native
GbE GbE GbE GbE GbE GbE GbE GbE GbE GbE GbE GbE GbE GbE GbE and and
Virtual Virtual

Evolving with technology leveraging ~15 years of experience

Ericsson SGSN-MME
Multi Access support

2G single
3G single
LTE single

CDMA*
2G/3G dual
WiFi*

Networks3G/LTE
Heterogeneous
dual

2G/3G/LTE triple

Voice M2M / 50B

* Interworking capabilities
Dynamic Resource Allocation between Access types

CP SS7/SCTP UP

2G 2G 2G

3G 3G 3G

LTE LTE Inter a c c e ss

l astic i ty
e
 Ericsson SGSN-MME Evolution

Common Deployment
Physical node
development Native SGSN-MME on EBS
for all access types LTE/3G/2G

Telco Cloud NFV

Virtualized SGSN-MME
for all access types LTE/3G/2G

Smooth evolution
Highest quality – Maintained feature leadership – Pool interworking between Native and Virtual
Pool Interworking between Native
and Virtual
Common OSS-RC/ENM Orchestration
Functional parity and O&M

interworking is required
 During the
transformation
EBS/MkVIII EBS/MkX EBS/MkX COTS COTS
to Cloud (NFV) Native Native Native Virtual Virtual

Pooling of a mix of Native

and Virtual SGSN-MMEs
 Smooth and
secure migration
to Cloud (NFV)
while leveraging Common pool with
previous L2/L3 full interworking
and functional parity
investments
in Native nodes

Full pool interworking between Physical and Virtual SGSN-MME

SGSN MME Software
 SGSN MME Software
The SGSN-MME software is divided into two main parts; the software platform
and the software applications.

Software platform is the lowest and most basic software level, which executes on all
PIUs in the physical SGSN-MME and on all VMs in the virtual SGSN-MME.

Software platform consists of Operating Systems (OSs), SGSN-MME middleware, and

application support.

The SGSN-MME middleware primarily provides distribution of applications over several

different
interacting PIUs or VMs.

On the application level, software is divided into a control system and a transmission
system, interconnected through either the physical or virtual backplane as illustrated
in slide.
Control system
 Control system
The control system is designed to process high-level protocols and to control
payload routing in the transmission system. It handles traffic control activities,
such as mobility and session management and high-level protocol processing;
system-internal control activities, such as recovery, distribution, and Operation and
Maintenance (O&M).

The control system consists of a number of Application Processors (APs),

interconnected through the either physical or virtual backplane, see slide.

The central AP (AP/C) handles the central functions of the control system and runs
on the PIU or the VM that serves as the active Node Controller Board (NCB). The
remaining APs form a generic processing pool to provide shared load handling.
Transmission system
Transmission system
The transmission system enables high-performance payload routing between the
SGSN-MME and other GPRS backbone and radio network nodes. The transmission
system handles signalling and payload between the SGSN-MME and other nodes.

The transmission system consists of a number of payload Device Processors (DPs),

Line Cards (LCs), Routing Processors (RPs), SS7/SCTP DPs as illustrated in slide.
 Software component
SGSN-MME software components are compatible with both physical SGSN-MME
and virtual SGSN-MME. Therefore, they work with both physical HW in site and
virtual HW in cloud environment. The SGSN-MME software is deployed as a
number of either PIUs for physical SGSN-MME or VMs for virtual SGSN-MME. The
SGSN-MME software includes the following roles for PIUs or VMs:

• File Server Board (FSB)

• Node Controller Board (NCB)
• General Processor Board (GPB)
• Routing Processor (RP)
• Line Card (LC)
 File Server Board

The FSB provides disk storage and boot services in the SGSN-MME. The SGSN-MME
has two FSBs, primary FSB and secondary FSB, which mirrors all stored data. If the
primary FSB fails or if it needs to be replaced, the secondary FSB takes over the
operation and becomes the primary FSB.
 Node Controller Board
The NCB performs monitoring, software distribution, and O&M of the SGSN-MME
applications. The SGSN-MME has two NCB , active NCB and passive NCB, which
mirrors all NCB states. If the active NCB fails or if it needs replacement, the passive
NCB becomes active and takes over the operation.

For SGSN-MME MkX and virtual SGSN-MME, the RP role is co-located with
the NCB role.
 General Processor Board

The GPB comprises three co-located roles; Application Processor (AP),Payload

Device Processor (DP) and SS7/SCTP DP. In the SGSN-MME, the GPB PIUs or
GPB VMs are scaled based on the deployed capacity.
 Application Processor

The AP is responsible for traffic control activities, such as mobility and session
management, and high-level protocol processing. Also, it handles internal
system control activities, such as recovery, distribution, and O&M.
Payload Device Processor
For GSM and WCDMA access, the Payload DP is responsible to relay user data
traffic between the radio network and the gateway node (GGSN or SGW),for both
uplink and downlink traffic. The payload related parts of Charging and Lawful
Interception are also executed on the Payload DP.

In a GSM network, payload and signaling are not separated over the Gb
interface. Therefore, payload DP has to separate signaling messages from the
payload, and send signaling messages to the control plane (AP).
SS7/SCTP Device Processor
The SS7/SCTP DP is used for SS7, SCTP, or both SS7 and SCTP signaling.
SCTP associations are terminated and lower layers of SS7 are handled on the
SS7/SCTP DP.

The SS7/SCTP DP consists of the following sub-components:

SS7 Front End The SS7 front end represents the low level protocols of the SS7 stack,
distributing incoming traffic to the SS7 back ends or SS7 NMM. The SS7 front end
is only used
for narrowband including HSL SS7.

SS7 Back End The SS7 back end represents the upper layers in the SS7 stack, and
handles SS7 traffic, registration and deregistration of SS7 users as well as
providing the SS7 user with information on the status of local and remote
subsystems.
SS7/SCTP DP
SS7 NMM The SS7 NMM handles all Message Transfer Part Level3 (MTP-
L3), MTP-L3 User Adaptation Layer (M3UA),and Signaling Connection
Control Part (SCCP) network
management messages. Upon changes in the network with impact on the
stored routing information, the NMM broadcasts the information to all
SS7 back ends in the SGSN-MME.

SS7 Device The SS7 device is a traffic-forwarding device which keeps an

association between established SCCP connections or Transaction
Capabilities Application
Part (TCAP) dialogs and the corresponding MS representations on the
APs. Connectionless messages are also handled and forwarded to
predefined
components on the applicable local AP.
SS7/SCTP DP
SCTP Front End The SCTP front end handles and terminates the SCTP associations.
It also supports the SS7 back end for SS7 over IP, and for an SGSN-MME running
as MME
it supports the SCTP device for the S1-AP, SGsAP,LCS-AP, and Diameter protocols.

SCTP Device The SCTP device handles the SGSN-MME internal distribution of SCTP
messages to and from different SCTP users such as S1-AP, SGsAP, LCS-AP, and
Diameter protocol layers.
Routing Processor (RP)
The RP handles IP routing control plane traffic to and from the SGSN-MME.
The RP handles routing protocols and creates routing tables, depending on
the IP protocol version and routing configuration. The routing tables are
used
to achieve IP connectivity between SGSN-MME and other nodes in external
networks. For information about the location of the RP role,
 Line Card (LC)

The LC has interfaces towards external networks. The LC acts as a load balancer.
It distributes incoming IP traffic over PIUs in a physical SGSN-MME or VMs in a
virtual SGSN-MME. Packet distribution is done based on the packet content. The
LC also distributes outgoing IP traffic over the available IP routes.
For information about the location of the LC role,
Physical SGSN-MME
SGSN-MME MkVIII
The following sections briefly describes the hardware
components of the MkVIII
SGSN-MME. For further information on hardware components
and additional
equipment required to get the MkVIII SGSN-MME up and
running, see MkVIII
Hardware.
Distributed routing in the SGSN-MME MkVIII handles routing of
IP packets for
all internal and external SGSN-MME interfaces. Distributed
routing is managed
by the RPs and is located on the SCXB PIU.
 Physical SGSN-MME
Magazines
The physical SGSN-MME cabinet contains one, two, or three magazines
depending on hardware configuration. Each magazine contains a number of
PIUs that are interconnected through the physical backplane.

Each magazine within one cabinet can be configured as a separate

SGSN-MME. The magazines are then treated as independent 1-magazine
SGSN-MMEs.
Physical SGSN-MME
MkVIII PIUs
The different types of PIUs available in the MkVIII hardware
are described in
the following list.

GEP3 The Generic Ericsson Processor board version 3

(GEP3) without storage media and without E1/T1. The
GEP3 without storage media can take the roles of AP,
Payload DP, SS7/SCTP DP (except for narrowband
SS7) and NCB.

GEP3-E1/T1 The Generic Ericsson Processor board, version 3 -

E1/T1 (GEP3-E1/T1) can take the roles of AP, Payload
DP, and SS7/SCTP DP including narrowband SS7.
Physical SGSN-MME
GEP3-HD or GEP3-SSD
The GEP3 with storage media has the role of an FSB.
For information on FSB
The GEP3 with storage media is available in two
variants, one with a mechanical hard disk (GEP3-HD)
and the other with flash memory based disk
(GEP3-SSD).
Note: The SSD storage media has faster read/writes
speeds, more durable, produces less noise,
no vibration and consumes less power than its
mechanical counter-part.
CMXB3 Component Main Switch Board version 3 (CMXB3)
provides 10 Gigabit Ethernet Layer 2 switching between
PIUs and connection between magazines.
Physical SGSN-MME
SCXB2 The System Control Switch Board version 2 (SCXB2)
has the role of an RP and LC with Layer 3 switching in
hardware. It provides 1 Gigabit Ethernet Layer 2 internal
switching between PIUs and 10 Gigabit interconnect
between magazines. Also, It provides 1 Gigabit and
10 Gigabit Ethernet Layer 2 and Layer 3 connection
towards the APP for external IP connectivity.
APP The Active Patch Panel (APP) is used for connecting 1
Gigabit and 10 Gigabit Ethernet Layer 2 and Layer 3
connections to nodes in external networks.
Physical SGSN-MME
SGSN-MME MkX
MkX PIUs
The different types of PIUs available in the
MkX hardware are described in
the following list.
GEP5 The Generic Ericsson Processor board
version 5
(GEP5) without storage media. The GEP5
without
storage media can take the roles of AP,
Payload DP,
SS7/SCTP DP (except for narrowband SS7), RP
and
NCB. For information on PIU roles
GEP5-400 The GEP5-400 has the role of an FSB.
For information
on FSB, The GEP5-400 with storage media is
available with
flash memory based disk.
SGSN-MME MkX

SMXB The Subrack Main Switch Board (SMXB)

has the role of
an LC. It provides separate 1 and 10 Gigabit
Ethernet
Layer 2 internal switching planes between
PIUs and
100 Gigabit interconnect between magazines
and
100 Gigabit interconnect between SMXBs in
same
magazine. The SMXB also provides 1 Gigabit
and 10
Gigabit Ethernet Layer 2 and Layer 3
connection for
external IP connectivity.
SGSN-MME MkX
Ericsson SGSN-MME-
Physical Offering
MkVIII MkX
(5th generation HW) (6th generation HW)
SGSN-MME 11A/B SGSN-MME 15A

GEP3 GEP5
GEP3-HDD/SDD GEP5-SSD
SCXB2 SMXB
CMXB3
PFM-3200W
APP
GEP3-SS7 (optional)
PFM -2400W
Physical Offering “At a Glance”

Pre-integrated HW/SW offering

Purpose built for Telco Grade operation

Market-Leading Superior Superior Multi

Feature Set In-Service Performance Access
Performance (ISP) & Flexibility
SGSN-MME MkVIII Hardware

Processing blades
(GEP3, cf. ”IBENv5”)
Cabinet (BYB 501)

Ethernet switches
(SCXB2, cf. “PEBv5”,
Subracks (EGEM2)
and CMXB3)

WDH: 60*40*180 cm
 Footprint 0.24 m2
 Volume 0.43 m3

Power & Fan Modules Active Patch Panels

(PFMs) (APPs) for external
Ethernet connectivity
MkVIII Hardware Architecture
MKVIII PIUs
GEP3 GEP3-FSB CMXB3 SCXB2

Intel x86 based multi core processing 10/40 Gbps Ethernet 1 Gbps Ethernet
blade (without / with HDDSSD) switch blade switch blade
MKVIII Hardware Architecture and Component
Overview
PIUs and Roles:
› FSBs
- 2 x GEP3-300

› NCBs
- 2 x GEP3-24GB

› GPBs (AP/DP/SS7/SCTP DP)

- 4 to 32 x GEP3-24GB

› RPs/LCs
- 2 x SCXB2 per magazine

› Switching
- 2 CMXB3s and SCXB2s per magazine CLI: get_eq_role
PIU Roles
• General Processor Board (GPB): GPB comprises three
co-located roles; Application Processor (AP), Payload
Device Processor (DP) and SS7/SCTP DP
• Application Processor (AP)
• used for node management, processing, and signaling

• Device Processor (DP)

• handles payload processing and SS7 signaling

• SS7/SCTP DP
• represents the low-level protocols of the SS7 stack, distributing
incoming traffic to the SS7 back ends or Network Management
Module (NMM)
• narrowband SS7 FE, broadband SS7 FE and SCTP FE
PIU Roles
› Routing Processor (RP)
• Handles IP routing control plane traffic to and from the SGSN-MME

› Node Controller Board (NCB)

• Provides central support and functions, such as O&M, Hardware and
Software monitoring and distribution, Packet Data application and
SGSN-MME supervision
• Active NCB & passive NCB

› File Server Board (FSB)

• Provides disk storage and boot services
• Primary FSB & Secondary FSB

› Line card
• The LC has interfaces towards external networks.
• Acts as a load balancer
EGEM2 Slot Positions

› Slot 1-24 is for use of GEP3

› Slot 9 and 15 has GEP3 used as NCB
› Slot 11 and 13 has a GEP3-HD used as FSB
› Slot positions is the board address defined by the backplane and
shall not be confused with the printed ruler on top of the magazine
 2*10
GbE

GbE
2*10
GbE

GbE

2*1
2*1

2*10
GbE

GbE
2*1

40 GbE
40 GbE

External Ethernet interfaces connected via 2 APPs at the bottom of the cabinet

CMXB3 CMXB3 CMXB3

SCXB2 SCXB2 SCXB2
MkVIII Subrack Configuration

GEP3-SS7 GEP3 GEP3

GEP3-SS7 GEP3 GEP3
GEP3-SS7 GEP3 GEP3
GEP3-SS7 GEP3 GEP3
GEP3 GEP3 GEP3
GEP3-FSB GEP3 GEP3
GEP3-FSB GEP3 GEP3
GEP3 GEP3 GEP3
GEP3-SS7 GEP3 GEP3
GEP3-SS7 GEP3 GEP3
GEP3-SS7 GEP3 GEP3
GEP3-SS7 GEP3 GEP3
CMXB3 CMXB3 CMXB3
SCXB2 SCXB2 SCXB2

40 GbE
40 GbE

2*10
GbE

GbE
2*10

2*10
GbE

GbE

GbE

GbE

2*1
2*1

2*1
Virtual SGSN-MME
 Virtual SGSN-MME Architecture
The virtual SGSN-MME is based on the same architecture as the physical SGSNMME,
including middleware and application software. This provides a common
feature set for both physical and virtual SGSN-MME. The common application
software also assures interworking between virtual SGSN-MME, physical SGSNMME,
and related peer Network Elements.
The software components are distributed and executed on VMs. VMs in the
virtual SGSN-MME correspond to PIUs in the physical SGSN-MME.
VMs can have one of the following roles:
 Virtual SGSN-MME Architecture
File Server Board (FSB)
Provides NFS storage and network boot services for all other VMs in the cluster.
There is one primary FSB and one secondary FSB for redundancy.

Node Controller Board (NCB)

Performs cluster supervision, software distribution, and provides O&M for the virtual SGSN-
MME.There is one active NCB and one passive NCB for redundancy.

General Processor Board (GPB)

Performs SGSN-MME application processing for LTE/WCDMA/GSM control plane and signaling,
and WCDMA/GSM user plane. Optionally includes integrated
vLC functionality.

Virtual Line Card (vLC)

Provides external connectivity, with application aware single IP address load balancing (inbound)
and forwarding (outbound), including support for session
resilience. The vLC VMs are not present when using GPB
VMs with integrated vLC functionality.
Deployment Types

Multi-host virtual SGSN-MME with Standalone vLC:This deployment targets scalability and high
capacity,with full software and hardware redundancy. The vLC role is deployed as vLC VMs separate
from the GPB VMs.

Multi-host virtual SGSN-MME with Integrated vLC:This deployment targets increased scalability and
capacity for payload, with full software and hardware redundancy. The vLC role is integrated in the GPB
VMs.
 Deployment Types
Dual-host virtual SGSN-MME :This deployment targets small footprint with limited capacity. The
deployment has small VM sizes, all collocated on two compute hosts. The deployment
supports full software redundancy and hardware redundancy. The deployment does not support scaling.

Single-host virtual SGSN-MME: This deployment targets small footprint with limited
capacity. The deployment has small VM sizes, all collocated on one compute host. It supports full
software redundancy including VM redundancy. The deployment does not support hardware
redundancy. However, network level redundancy can be achieved through a pair
of virtual SGSN-MME instances configured as an SGSN or
MME pool, possibly with geo-redundancy.
Deployment Guideline
Deployment Guideline
Ericsson SGSN-MME MkX
Tougher
traffic models › Increased performance and scalability
› New GEP5 processing blade
VoLTE,
positioning...
› Significantly increased control plane,
signaling and/or user plane capacity
Heterogeneous
Networks

› Increased functionality and flexibility

M2M/MTC)
› Enhanced routing solution enabling
3GPP
new functionality and improved
evolution characteristics
Network
› Up to 48x10G/1G pluggable Ethernet
evolution I/O
(NFV/SDN)
SGSN-MME MkX Hardware
Ericsson Blade System
(EBS)
Processing and
storage blades
Cabinet (BYB 501) (GEP5)

Ethernet switch blades

Subracks (EGEM2)
(SMXB)

WDH: 60*40*180 cm
 Footprint 0.24 m2
 Volume 0.43 m3

Power & Fan Modules

(PFMs)
MkX Hardware Architecture Evolution
MkVIII MkX

GEP3-24GB GEP5-48GB
EBS
GEP3-SSD GEP5-400

SCXB2

CMXB3 SMXB

APP

PFM 2400 PFM 3200

 MkX Hardware Architecture and component overview

PIUs and Roles:

› FSBs
- 2 x GEP5-400

› NCBs / RPs
- 2 x GEP5-48GB

› GPBs (AP/DP/SCTP DP)

- 4 to 32 x GEP5-48GB

› Line Card and Switching

- 2 SMXBs per magazine

CLI: get_eq_role
MkX GEP5

More ...more
powerful and faster
CPU... memory

MkVIII GEP3  MkVIII GEP3 

Intel Xeon Westmere-EP x86 24 GB DDR3 RAM
(6C/12T, 2.0 GHz, 12 MB L3...) MkX GEP5 
MkX GEP5  48 GB DDR3 RAM
Intel Xeon Ivy Bridge-EP x86
(10C/20T, 2.4 GHz, 25MB L3...)
MkX GEP5-400

More ...more
powerful and faster
CPU... memory

MkVIII
 GEP3-HDD/SSD
300GB HDD/200GB SSD
MkX
 GEP5 – SSD
400GB SSD
MkX SMXB
More 2x
MkVIII SCXB2 
Single core PowerPC powerful multi-fiber
MkX SMXB
CPU and optical
Multi core Intel x86
using DPDK
Ethernet (100G
switch MPO)

8 x pluggable
Ethernet I/O
(1G/10G
SFP/SFP+) 1000BASE-SX/LX/T
10GBASE-SR/LR
SMXB – Internal connectivity (1/2)

› The two 10Gb 10G1 and 10G2

ports marked in RED are used
for signaling and inter-
magazine connectivity

Ports 10G1 & 10G2

100 Ω shielded twisted pair, 10
Gb.
Inter-magazine connectivity
SMXB – Internal connectivity (2/2)
› The two 100Gb B1 and B2 ports
marked in BLUE are used for
payload and traffic between
magazines in the same
magazine and inter connectivity
on the left and right side of the
node.

Ports B1 & B2: Optical MPO/MTP48f

OM3 MTP-MTP Prizm, 100 Gb.
Inter- and intra-magazine connectivity
SMXB – External Connectivity

SFP/SFP+ Transceiver ports

› Integrated into SMXB and providing new
functionality including CLI, Counters and
Alarms.
› Ports A1 to A8 support both 1Gb SFP and 10GB
SFP+ modules
CLI: create_eth_port -as
(activate/deactivate link)

SFP/SFP+ transceivers
› 1000BASE-SX/LX/T
› 10GBASE-SR/LR
CLI: show_piu_transceiver
MkX SMXB
Plug-In Unit:
› CPU: Intel C2758, 2.4 GHz, 8 cores
› 8 GB Flash memory
Internal Connectivity Ports
› 2 x 10Gb, 2 x 100Gb
External Connectivity Ports
› 8 transceiver ports (1Gb/10Gb)
Indicators / LEDs
› 4 status LEDs
› 8 transceiver activity LEDs
SMXB Roles
› Line Card
› Replaces (MkVIII) SCXB, CMXB, APP
 MkX High Level Architectural
Overview 100G

CP CP CP CP CP CP CP CP 8x
8x 10/
LC SS7 SS7 SS7 SS7 SS7 SS7 SS7 SS7 LC
10/1 NCB FSB FSB NCB 1
(FE) SCTP SCTP SCTP SCTP RP RP SCTP SCTP SCTP SCTP (FE)
GbE Gb
UP UP UP UP UP UP UP UP E

100G 100G

8x CP CP CP CP CP CP CP CP CP CP CP CP 8x
10/ 10/
LC SS7 SS7 SS7 SS7 SS7 SS7 SS7 SS7 SS7 SS7 SS7 SS7 LC
1 (FE) (FE) 1
SCTP SCTP SCTP SCTP SCTP SCTP SCTP SCTP SCTP SCTP SCTP SCTP
Gb Gb
E UP UP UP UP UP UP UP UP UP UP UP UP E

100G 100G

8x CP CP CP CP CP CP CP CP CP CP CP CP 8x
10/ 10/
1 LC SS7 SS7 SS7 SS7 SS7 SS7 SS7 SS7 SS7 SS7 SS7 SS7 LC 1
(FE) SCTP SCTP SCTP SCTP SCTP SCTP SCTP SCTP SCTP SCTP SCTP SCTP (FE)
Gb Gb
E UP UP UP UP UP UP UP UP UP UP UP UP
E

100G CP = Control Plane (“AP”)

UP = User Plane (“DP”)
RP = Routing Processor
FE = Forwarding Element
LC = Line Card
 GbE

GbE

GbE
10/1

10/1

10/1
8x

8x

8x
100G

100G

SMXB SMXB SMXB

GEP5 GEP5 GEP5
GEP5 GEP5 GEP5
Hardware Deployment – MkX Scalability on blade level

GEP5 GEP5 GEP5

GEP5 GEP5 GEP5
GEP5 GEP5 GEP5
GEP5-SSD GEP5 GEP5
100G

100G
GEP5-SSD GEP5 GEP5
GEP5 GEP5 GEP5
GEP5 GEP5 GEP5
GEP5 GEP5 GEP5
GEP5 GEP5 GEP5
GEP5 100G GEP5 GEP5

100G
SMXB SMXB SMXB

GbE

GbE
10/1

10/1
GbE
10/1

8x

8x
8x
TMO Levels for a MkVIII SGSN-
MME

TMO Level Number of AP Number of Payload Number of

Cores DP Cores SS7/SCTP DP
Cores
1 1 4 1
2 2 3 1
3 3 2 1
4 4 1 1
0 (Single Access LTE) 5 0 1
TMO Levels for a MkX SGSN-
MME

TMO Level Number of Number of Number of

AP Cores Payload DP Cores SS7/SCTP DP Cores

1 5 4 1
2 6 3 1
3 6 2 2
4 7 1 2
0 (Single Access LTE) 8 0 2
MkX Software Configurable Traffic Mix Optimization
Relative increase in
control plane capacity

MkVIII CP SCTP

/L MkX CP ~1.8x SCTP LTE/3G

signaling
MkVIII CP
SS7
UP optimized
/4 MkX
SCTP

~2.0x
SS7
CP UP
SCTP

SS7
MkVIII CP UP

/3 MkX
SCTP

CP ~2.3x SS7
SCTP
UP

SS7
MkVIII CP UP

/2 MkX
SCTP

CP
~3.4x SS7
SCTP
UP
2G/3G
SS7 throughput
MkVIII CP UP
optimized
/1 MkX
SCTP

CP ~5.7x SS7
SCTP
UP
Summary
After this chapter, the student should now be able to :

› Explain the software architecture of Native SGSN-MME using MKVIII

and MkX virtual SGSN MME Hardware
› Understand the hardware architecture of Native SGSN-MME MKVIII
and MkX and virtual SGSN MME and its different components
› List the various PIU roles in SGSN-MME