Architecture

TECHNICAL PRODUCT DESCRIPTION

35/221 02-AXB 250 05/8-V2 Uen BS

Copyright

© Ericsson AB 2009–2016. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design, and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use
of this document.

Trademark List

All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.

35/221 02-AXB 250 05/8-V2 Uen BS | 2016-03-17

 Contents

Contents

1 Introduction 1
1.1 Scope 1
1.2 Target Groups 1

2 SGSN-MME Software 1
2.1 Control System 2
2.2 Transmission System 3
2.3 Software Components 4
2.4 Software Redundancy 8

3 SGSN-MME Deployments and Supported

Configurations 8
3.1 Physical SGSN-MME 8
3.2 Virtual SGSN-MME 13
3.3 Traffic Mix Optimization 13

35/221 02-AXB 250 05/8-V2 Uen BS | 2016-03-17

Architecture

35/221 02-AXB 250 05/8-V2 Uen BS | 2016-03-17

 SGSN-MME Software

1 Introduction

This document describes the architecture of the SGSN-MME for GSM,

WCDMA, and LTE radio access.

It describes physical SGSN-MME deployed with Plug-In Units (PIUs), virtual

SGSN-MME deployed with Virtual Machines (VMs), and the SGSN-MME
software structure.

Note: The term Board refers to a PIU in a physical SGSN-MME and a VM

in a virtual SGSN-MME.

1.1 Scope
This document covers the following topics:

• Description of the SGSN-MME software structure and software components

• Overview of the different types of PIUs for the physical SGSN-MME

• Overview of the different types of VMs for the virtual SGSN-MME

• SGSN-MME Deployments and Supported Configurations

• Different Traffic Mix Optimization (TMO) deployments

1.2 Target Groups

This document is an introduction to the architecture of the SGSN-MME
for network operation and network optimizing personnel as well as system
administrators. It assumes a basic knowledge of datacom, telecom, and cloud.

2 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

35/221 02-AXB 250 05/8-V2 Uen BS | 2016-03-17 1

 Architecture

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 Figure 1.

SGSN-MME

Control System

Backplane

Transmission System

Signaling
Resource management
Payload

Figure 1 SGSN-MME Software Architecture on Application Level

The control system, the transmission system, and the software components in
the SGSN-MME are further described in the following sections.

2.1 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 Figure 2.

2 35/221 02-AXB 250 05/8-V2 Uen BS | 2016-03-17

 SGSN-MME Software

SGSN-MME
Control System
AP/C

Backplane

AP AP AP AP

Transmission System

Signaling
Resource management
Payload

Figure 2 SGSN-MME Control System Architecture

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.

2.2 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 Figure 3.

35/221 02-AXB 250 05/8-V2 Uen BS | 2016-03-17 3

 Architecture

SGSN-MME

Control System

Transmission System
Payload SS7/SCTP
DP DP

Backplane

Payload
DP RP LC

Signaling
Payload

Figure 3 SGSN-MME Transmission System Architecture

2.3 Software Components

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)

2.3.1 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.

4 35/221 02-AXB 250 05/8-V2 Uen BS | 2016-03-17

 SGSN-MME Software

2.3.2 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.

2.3.3 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.

2.3.3.1 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.

2.3.3.2 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).

The payload DP consists of the following sub-components:

BVC Device Each Base Station Subsystem GPRS Protocol (BSSGP)

Virtual Connection (BVC) device represents a number
of Network Service Entities (NSEs).

The BVC device handles the NS control layer and

BSSGP concerning radio and cell management over
the Gb interface. Furthermore, the BVC device handles
Gb over IP.

35/221 02-AXB 250 05/8-V2 Uen BS | 2016-03-17 5

 Architecture

Charging Device The charging device collects charging information for

CDR based charging and CAMEL based charging. The
generated SGSN - Charging Data Records (S-CDRs)
are forwarded to the NCB for persistent storing and
to the local AP for transport by GTP prime. Charging
information for CAMEL is sent to the local AP to be
used by the CAMEL GPRS Service Switching Function
(SSF).

GTU Device Each GPRS Tunneling User Plane device type (GTU)
handles the GTP protocol over the Gn/Gp and Iu-U
interfaces for a number of MSs. For GSM, the GTU
device supports exactly the same selection of MSs as
the collocated MS device. For WCDMA Systems, the
GTP protocol is completely handled by the GTU device
in a symmetrical way over Gn/Gp and Iu-U.

LI Device The Lawful Interception (LI) device supports the LI

function.

MS Device Each MS device represents a number of MSs. When

a new MS enters the SGSN, the MS device for the
connection is selected based on the MS identity. This
allows an evenly distributed load.

The MS device handles the connection-oriented part

of BSSGP, the LLC protocol, and the Subnetwork
Dependent Convergence Protocol (SNDCP) over the
Gb interface. In addition, Mobility Management services
are partly allocated to the MS device.

2.3.3.3 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.

6 35/221 02-AXB 250 05/8-V2 Uen BS | 2016-03-17

 SGSN-MME Software

SS7 NMM The SS7 NMM handles all Message Transfer Part Level
3 (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.

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.

2.3.4 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, see Page 7.

Table 1 RP Role Location

SGSN-MME RP Role Location
MkVIII Co-located with the LC on a SCXB
PIU.
MkX Co-located with the NCB on a GEP5
PIU.
Virtual SGSN-MME Co-located with the NCB on a VM.

2.3.5 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

35/221 02-AXB 250 05/8-V2 Uen BS | 2016-03-17 7

 Architecture

content. The LC also distributes outgoing IP traffic over the available IP routes.
For information about the location of the LC role, see Page 8.

Table 2 LC Role Location

SGSN-MME LC Role Location
MkVIII Co-located with the RP on a SCXB
PIU.
MkX Located on a SMXB PIU.
Virtual SGSN-MME Located on dedicated VMs.

2.4 Software Redundancy

Software components are distributed over the SGSN-MME to achieve load
sharing and redundancy on the software level. If a software component fails,
another software component of the same role takes over the operation until
the failing software component is back to service. For more information, see
Resilience.

3 SGSN-MME Deployments and Supported

Configurations

Software deployment describes which software components are executing

and where they are executing, thereby it describes the roles of the PIUs in a
physical SGSN-MME or VMs in a virtual SGSN-MME. Software deployments of
both physical and virtual SGSN-MME are described in Section 3.1 on page 8
and Section 3.2 on page 13 respectively.

For more information about the software deployment parameters, see Software
Configuration (CLI).

3.1 Physical SGSN-MME

Physical SGSN-MME supports MkVIII described in Section 3.1.1 on page 8,
and MkX described in Section 3.1.2 on page 11.

8 35/221 02-AXB 250 05/8-V2 Uen BS | 2016-03-17

 SGSN-MME Deployments and Supported Configurations

3.1.1 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.

For more information on distributed routing, see Distributed Routing.

3.1.1.1 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. For an overview of the cabinet hardware configuration for the
multi SGSN-MME, see MkVIII Hardware.

3.1.1.2 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. For information on PIU roles, see
Section 2.3 on page 4.

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. For
information on PIU roles, see Section 2.3 on page 4.

35/221 02-AXB 250 05/8-V2 Uen BS | 2016-03-17 9

 Architecture

GEP3-HD or GEP3-SSD
The GEP3 with storage media has the role of an FSB.
For information on FSB, see Section 2.3.1 on page 4

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.

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.

3.1.1.3 Deployments for MkVIII SGSN-MME

Hardware can be expanded PIU by PIU from a partly equipped magazine

minimum configuration, up to 3 fully equipped magazines. For more information,
see Increasing SAU Capacity (MkVIII). The deployment for MkVIII SGSN-MME
is shown in Figure 4.

10 35/221 02-AXB 250 05/8-V2 Uen BS | 2016-03-17

 SGSN-MME Deployments and Supported Configurations

25 26 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 27 28

S C G G G G G G G G G G G G G G G G G G G G G G S C
C M E E E E E E E E E E E E E E E E E E E E E E C M
X X P P P P P P P P P P P P P P P P P P P P P P X X
B B 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 B B
2 3 3 3 3 3 2 3
/ - / - / - / - / - / - / - / -
Magazine 1
- - - -
E E E E H S H S E E E E
1 1 1 1 D S D S 1 1 1 1
/ / / / / D / D / / / /
LC / RP

LC / RP
T T T T T T T T
1 1 1 1 1 1 1 1

GPB GPB GPB GPB NCB FSB FSB NCB GPB GPB GPB GPB

S C G G G G G G G G G G G G S C
C M E E E E E E E E E E E E C M
X X P P P P P P P P P P P P X X
B B 3 3 3 3 3 3 3 3 3 3 3 3 B B
2 3 2 3
Magazine 2

LC / RP

LC / RP
GPB GPB GPB GPB GPB GPB GPB GPB GPB GPB GPB GPB

S C G G G G G G G G G G G G S C
C M E E E E E E E E E E E E C M
X X P P P P P P P P P P P P X X
B B 3 3 3 3 3 3 3 3 3 3 3 3 B B
2 3 2 3
Magazine 3

LC / RP

LC / RP
GPB GPB GPB GPB GPB GPB GPB GPB GPB GPB GPB GPB

Figure 4 SGSN-MME, MkVIII

For a description of the software components, see Section 2.3 on page 4.

3.1.2 SGSN-MME MkX

The following sections briefly describes the hardware components of the MkX
SGSN-MME, involved in packet processing and signaling and deployments of
physical SGSN-MME. For further information on hardware components and
additional equipment required to get the MkX SGSN-MME up and running, see
MkX Hardware.

Centralized routing in the SGSN-MME MkX handles routing of IP packets for all
internal and external SGSN-MME interfaces. Centralized routing is managed
by the RP and is co-located with the NCB.

For more information on centralized routing, see Centralized Routing.

3.1.2.1 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. For an overview of the cabinet hardware configuration for the
multi SGSN-MME, see MkX Hardware.

35/221 02-AXB 250 05/8-V2 Uen BS | 2016-03-17 11

 Architecture

3.1.2.2 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, see Section 2.3 on
page 4.

GEP5-400 The GEP5-400 has the role of an FSB. For information

on FSB, see Section 2.3.1 on page 4

The GEP5-400 with storage media is available with

flash memory based disk.

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.

3.1.2.3 Deployments for MkX SGSN-MME

Hardware can be expanded PIU by PIU from a partly equipped magazine

minimum configuration, up to 3 fully equipped magazines. For more information,
see Increasing SAU Capacity (MkX). The deployment for MkX SGSN-MME
is shown in Figure 4.

12 35/221 02-AXB 250 05/8-V2 Uen BS | 2016-03-17

 SGSN-MME Deployments and Supported Configurations

25 26 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 27 28

S G G G G G G G G G G G G S
M E E E E E E E E E E E E M
X P P P P P P P P P P P P X
B 5 5 5 5 5 5 5 5 5 5 5 5 B
- -
Magazine 1 4
0
4
0
0 0

RP

RP

LC
LC

GPB GPB GPB GPB NCB FSB FSB NCB GPB GPB GPB GPB

S G G G G G G G G G G G G S
M E E E E E E E E E E E E M
X P P P P P P P P P P P P X
B 5 5 5 5 5 5 5 5 5 5 5 5 B
Magazine 2

LC
LC

GPB GPB GPB GPB GPB GPB GPB GPB GPB GPB GPB GPB

S G G G G G G G G G G G G S
M E E E E E E E E E E E E M
X P P P P P P P P P P P P X
B 5 5 5 5 5 5 5 5 5 5 5 5 B
Magazine 3

LC
LC

GPB GPB GPB GPB GPB GPB GPB GPB GPB GPB GPB GPB

Figure 5 SGSN-MME, MkX

For a description of the software components, see Section 2.3 on page 4.

3.2 Virtual SGSN-MME

The virtual SGSN-MME supports flexible deployments, with different number
of VMs and different VM sizes. The number of VMs and the VM sizes can be
scaled depending on the required capacity.

For information about deployment types and scaling of the virtual SGSN-MME,
see Virtual SGSN-MME Technical Product Description.

3.3 Traffic Mix Optimization

It is possible to optimize the utilization of physical SGSN-MME HW and virtual
SGSN-MME VM by moving capacity either from the control plane (AP) to the
user plane (DP), or from the user plane (DP) to the control plane (AP), using
Traffic Mix Optimization (TMO). For example, when enabling 3GDT, TMO can
be used to increase signaling capacity and to decrease user plane capacity.

For detailed information about TMO, See Characteristics. For description of the
software components, see Section 2.3 on page 4.

35/221 02-AXB 250 05/8-V2 Uen BS | 2016-03-17 13