You are on page 1of 45

MSC-S Blade Cluster R14.

1
Introduction

Contents
BC main components and hardware
BC Logical Overview
Normal Call flow

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 2

Product Capacity figures


MSC-S BC capacity
MSC R14.0:
MSC R14.1:
MSC R12A:

7 MBHCA
10 MBHCA
12 MBHCA
15 MBHCA

Transit BC capacity
TSC R14.1:
TSC 12A:

20 MBHCA
> 20 MBHCA

10 (9+1) blades is the maximum


(for more exception required)
Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 3

MSC-Server Blade Cluster capacity


Ultra-high capacity

(5,7 M BHCA)

(5,5 M BHCA)

(18 M BHCA)

(18 M BHCA)

(6,0 M Subs)

(5,9 M Subs)

(19 M Subs)

(19 M Subs)

4 x MSC-S
APZ 212 60
8 Subracks

1 x MSC-S BC
6 Blades
3 Subracks

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 4

13 x MSC-S
APZ 212 60
26 Subracks

2 x MSC-S BC
2 x 10 Blades
8 Subracks

MSC-S Blade Cluster, Components


APGAPGCHS
CHS

APG-IO,
APG-IO,
STS
STS

MSC
Blade

Blade
MSC

Blade
MSC

...

SIS
SIS

MSC Blade: Call control,


Trunk control (BICC, ISUP)
SPX: Single point of entry
for signaling in the Blade
Cluster
MXB, EXB: L2 internal
MSC-S BC infrastructure
IPLB: IP Line Board,
provides the host IF
I/O system
- APG43 for the whole
cluster and SPX
- SIS for Integrated Site
Infrastructure

Blade
MSC

MSC
Blade

IS

Infrastructure
IS IS
L2L2
Infrastructure

MXB
, EXB-switch
MXB
, EXB-switch

B
ISER
IPLB

SPX
SPX

SPX
SPX
MSC Server BC

IP
IP

ATM, TDM
ATM, TDM

Color Legend

IS components
MSC/

RAN,
CN CN
RAN,

Blades

Signaling Proxy
APG43

OSS- RC
Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 5

IS O&M

Large Configuration
10 MSC Blades
1 IPLB Pair
2 SPX
2 APG (I/O)
4 Subracks
2 Cabinets

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 6

MSC-S Blade Cluster 2.1, HW layout

Fan

Cabinet 1

Blade
Fan
Fan

SCB
RP/4
XDB
CG
B
IR
AL
B
AL
I
ALI/STE
I
ALI/STE
B
STE
B
STE
B
B P
ET155
ET155 P
CG
B
IR
AL
B
AL
I
ALI/STE
I
ALI/STE
B
STE
B
STE
B
ET155
B
ET155
W
W
XDB
SCB
RP/4

SCB
RP/4
DISC
B
APUB
B

APUB-A
DISC-A
CPUB
B
MAUB
CPUB
A
NTP/ToD

SCB
RP/4

SCB
RP/4
DISC
B
APUB
B
APUBA
DISC-A

EXT MED

Optional
CPUB
B
MAUB
CPUB
A
Alarm board

Charging APG 43

Air Guide

Fan
Fan

Power and Fan module and Air Guide

SCXB
MSC-S blade
MSC-S blade

MSC-S blade

MSC-S
EXBblade
MSC-S blade

All cabinet pictures show examples of one possible HW-configuration,

MSC-S blade

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13the| exact


Pageboard-types
7
and placing of boards in the cabinet are subject to change.

MSC-S
blade
MSC-S
blade
EXB
MSC-S
blade
MSC-S
blade
MSC-S blade
MSC-S blade
SCXB

IP LB
SI
S
SCXB/CMCB

EXB
MSC-S blade or IPLB

MSC-S blade

IP LB
SI
S
MSC-S blade

EXB
MSC-S blade or IPLB

MSC-S blade

MSC-S blade

SCXB/CMCB

Infrastructure
components

Air Guide

MSC-S Blade System


hosted in IS framework

SCB
RP/4
XDB
CG
B
IR
AL
B
AL
I
ALI/STE
I
ALI/STE
B
STE
B
STE
B
B P
ET155
ET155 P
CG
B
IR
AL
B
AL
I
ALI/STE
I
ALI/STE
B
STE
B
STE
B
ET155
B
ET155
W
W
XDB
SCB
RP/4

Option

IO
NTP/ToD

SCB
RP/4

MSC-S Blades
Power and Fan module and Air Guide

TDM
Option
ATM
SPX

Fan
Fan

Cabinet 2

O&M APG 43
2xSPX

Example Optional RP Magazine


ATM

ATM

S
E E
C
T T
B
S
X 1 1
T
D 5 5
R
E
B 5 5
P
B
/
WW
4
0

S
T
E
B

A
L
I
/
S
T
E
B

A
L
I
A A I
/
L L R
S
I I B
T
E
B

C
G
B

A
E
L
T
S S I
1
T T /
5
E E S
5
B B T
E
P P
B
E
T
1
5
5

A
L
I
A A I
/
L L R
S
I I B
T
E
B

C
G
B

S
C
B
X
D
R
B
P
/
4

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

TDM
Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 9

TDM

TDM

Contents
BC main components and hardware
BC R14.1 Overview
Normal Call flow

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 11

MSC-S R14.1 Blade Cluster


Network Overview

Node B

RNC

RANAP Over
ATM

MSC-S BC

M-MGw

SPX 1

BSC

BSSAP Over
TDM

BTS

SPX 2

Virtual M-MGw

ISUP Over TDM

MSC-S
Blade
MSC-S
Blade

MSC-S
Blade

Local PSTN
IP
Network

MSC-S

all nodes see MSC-S BC as one node


n R14.1, MGW has only one vMGW
for MSC-S BC

M-MGw

HSS

IMS

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 12

MSC-S
Blade
MSC-S
Blade

MSC-S R14.1 Blade Cluster


Network Overview

Node B

RNC

Iu Over
IP

MSC-S BC
SPX 1

AOIP

BSC
BTS

SPX 2

M-MGw
MSC-S
Blade
MSC-S
Blade

IP
Network

SIPI

Local PSTN

MSC-S
Blade
MGw

MSC-S

HSS

IMS

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 13

MSC-S
Blade
MSC-S
Blade

MSC in Pool Feature


The MSC in Pool (MiP) feature is strongly recommended.
MIP will make it more smooth to integrate the MSC-S BC.
Example:
1 MSC-S BC has
3 blades and share
network load with
2 MSC-S

MSC

MSC

MSC

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 14

MSC in Pool
(MiP) Feature

MSC-S

MSC-S

Physical Node View (L1/L2):


MSC-S BC with 10 MSC Blades
Optional

Optional

Physical connection to network


Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 15

MSC-S BC is an IP Network
Cluster
Cluster
MSC-S
Blade
Cluster

MSC-S
blade

MSC-S
blade

MSC-S
blade

MSC-S
blade

MSC-S
blade

IP
Signalling Proxy
SPX 1

Signalling Proxy
SPX 2
IPLBA

IPLBB

SIS
SIS

I/O
I/O

Externally accessible IP Subnets


Subnet
Name

IP network behind IPLBs


Host interface on IPLBs

Subnet Size
(/Subnet Mask)

BC-SIG

16 (/28)

BC-OAM

16 (/28)

BC-DNS

8 (/29)

BC-SIP

64 (/26)

The number of required IP addresses


depends on the number of MSC blades. In
order to be future proof it is recommended to
allow for up to 64 addresses unless the
operator can foresee the long-term need to
stay below this number.
In case SIP is not used the BC-SIP and BCDNS subnets should be left undefined.

104

32 in case SIP and DNS are not used.

Traffic separation using


VLANs (subnets)
Internal (Pre-configured)
Externally accessible
Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 16

Reasoning/Scalability Aspects

Total

The number of required IP addresses does


not depend on the number of blades, see
example configuration in Table 3.

VLAN Overview

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 17

IP addressing summary

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 18

Integration of MSC-S BC into IP network


MSC-S BC shares subnet

Dedicated subnet, structured to fit SCTP


requirements for path diversity

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 19

SPX to/from MSCs Blades

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 20

MSC blades to/from the external network

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 21

MSC-S BC is a SCTP Network


Cluster
Cluster
MSC-S
blade

MSC-S
blade

SCTP internal
Signalling Proxy
SPX 1

MSC-S
blade

MSC-S
blade

Signalling Proxy
SPX 2
IPLBB

IPLBA

GCP over SCTP

MSC-S
Blade
Cluster

MSC-S
blade

SIS
SIS

I/O
I/O
CSCF

HLR

Service nodes
e.g. HLRs

SIP/SIP-I
BSC

RNC

RAN

M-MGW
MSC-S
STP

M-MGW

POI
(PSTN/PLMN)

CN

SCTP for SS7 signaling


Internally
Externally
Terminated on SPXs
GCP over SCTP terminated on MSC Blades

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 22

DNS

SCTP Association MSC R14.1

Dedicated SCTP Association for


SUA and M3UA inside MSC-S BC
Client-Server configuration (Blades
are client)
Single-homed on MSC Blades
Multihomed on SPXs

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 23

Signaling MSC 14.1 (incl. GCP/M3ua)

MAP, BSSAP, ISUP


RANAP, GCP

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 24

GCP over SCTP


Cluster SCTP association
Single SCTP association shared by all MSC Blades between M-MGw and
MSC-S Blade Cluster
Configuration
(Virtual) Cluster IP (VIP) addresses configured on all MSC blades
Cluster SCTP end point (Virtual SCTP server) configured on all blades
Cluster SCTP association provisioned on all blades

Only one blade actually terminates a Cluster SCTP association but all blades
can send/receive traffic over it
Cluster SCTP Association is cluster object with master role
Role dynamically assigned to any one MSC blade
Association master roles balanced over all MSC blades
Automatic master re-assignment after blade failure

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 25

Cluster SCTP EP and associations

A cluster End Point for GCP:


IHBII:LIP=193.180.18.1&193.180.18.9,EPID= GCPEP,USER=GCP,MODE=SERVER,SCTPCP;

Cluster SCTP association:


IHADI:SAID=GCPMGW1,EPID=GCPEP,RIP=193.180.14.50& 193.180.14.114,SCTPCP;
IHADI:SAID=GCPMGW2,EPID=GCPEP,RIP=193.180.14.51& 193.180.14.115,SCTPCP;
Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 26

Multihomed association for GCP/SCTP

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 27

Opportunity with GCP over sctp


Node capacity implication (SPX bypassed by GCP)
All IP Network:

BSC

RNC

IP

GCP/SCTP

MSC-S
Blade
Cluster

POI
SIP/SIP-I

M-MGW

No need for SS7 on M-MGW

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 28

INT-SIG
1001

MSC

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 29

SPX2

M3UA

PCG

P USI

CCI B

PASSB

PA NA R

PA CT

SCCP

SCTP
SPX1

GCP
MSC

PA C

PA M
M3UA

SCTP

MSC

PCG

P USI

CCI B

SUA

PASSB

PA NA R

PA C

PA CT

PA M

SPX replaces SCCP with SUA

SCTP
BC-SIG
2001

BC-SIG
2001

IPLB

IPLB

Signaling
Signalling

SPX
roles

IPLB
roles

DNS Server
roles

MSC Blade
address
M3UA level

MSC Blade
address
IP level

MAP/CAP

SUA Gateway

Hosted SPC - MPT

Base IP
(Private IP)

RANAP/BSSAP

SUA Gateway

Hosted SPC - ITU

Base IP
(Private IP)

BICC/ISUP

STP

Non-Hosted SPC

Base IP
(Private IP)

GCP over M3UA

STP

Non-Hosted SPC

Base IP
(Private IP)

GCP over SCTP

Load Balancing

SIP/SIP-I

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 30

Virtual IP
(Public IP)
Load Balancing

Base IP
(Public IP)

MSC-S BC is a SS7 Network


Cluster
Cluster
MSC-S
Blade
Cluster

MSC-S
blade

MSC-S
blade

Signalling Proxy
SPX 1
1

MSC-S
blade

MSC-S
blade

MSC-S
blade

Signalling Proxy
SPX 2
2
IPLBB

IPLBA

SIS
SIS

I/O
I/O
CSCF

HLR

Service nodes
e.g. HLRs

SIP/SIP-I
BSC

M-MGW

RNC

RAN

MSC-S
STP

M-MGW

POI
(PSTN/PLMN)

CN

SPCs for MSC-S BC node (per standard & network (NI) )


1 for HPC for SCCP users
1 for common SPC for M3UA users (trunks, GCP)
2 for SPX, 1 2
1 SCCP GT address for MSC-S BC node

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 31

DNS

#SPCs
MSC-S BC VS Classic MSC-S

3
MSC-S

2
MSC-S

4
MSC-S

1
2
3
4
5

Service nodes
e.g. HLRs

1
5
9

RAN

2
MSC-S
Blade
4 Cluster
3

9
M3UA Users

MSC-S

SCCP Users

POI
(PSTN/PLMN)
CN

MSC-S
MSC-S

M-MGW

10
2
6
10

6
MSC-S
Blade
8 Cluster
7

11 MSC-S

Blade

12 Cluster

3 4
7 8
11 12

#SPCs on network level decreased only if MSC-S BC


replaces high number of classical MSC-Ss
Network environment see different SPCs in MSC-S BC for
SCCP and M3UA users
Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 32

Hiding SPCs of SPX in all IP environment


1

MSC-S
Blade
Cluster

MSC-S
Blade
Cluster

MSC-S
Blade
Cluster

MSC-S
Blade
Cluster

2 4 6 8

M-MGW

M-MGW

SPCs on SPXs can be handled as Dummy SPCs:


Not used by surrounding node for SS7 traffic routing
They can be identical on both SPXs and all MSC-S BCs

Its applicable when only IP signalling is used in MSC-S BC


It shall be used only if #SPCs is really big issue, otherwise standard
solution with dedicated SPCs is preferred as it conforms to SS7 best
practice (SPC shall be unique on network level)
Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 33

Contents
BC main components and hardware
BC R14.1 Overview
Normal Call flow

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 34

Subscriber Distribution
Subscribers are equally distributed to each blade

IMSI

Hash-Function

Hash-Value

Distribution
Table
Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 35

Primary Blade Id
Buddy Blade Id

Primary & Buddy Concept


Each subscriber will be registered in 2 blades
Primary MSC keeps
Buddy MSC updated

The Buddy MSC


is prepared to take
over the traffic
if something happens.

Primary MSC
Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 36

Buddy MSC

MSC-S Blade Cluster Key Mechanisms


in
Hash

g
in
Hash

MSC-S Blade Cluster


Primary

MSC
blade

MSC
blade

Buddy

MSC
blade

MSC
blade

MSC
blade

SCTP/IP
Signaling
SGW
proxy

TDM

RAN

ATM

IO
APG

I/O
SIS
IP

CN

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 37

OSS

Subscriber Distribution
VLR Data Replication

Distribution of Primary and Buddy data


MSC-Server
Blade
Subscriber traffic data is always
available
in Cluster
two MSC-S blades
MSC-S Blade

MSC-S Blade

MSC-S Blade

MSC-S Blade

MSC-S Blade

BUDDY
Subscriber
data

PRIMARY
Subscriber
data

Mobile subscribers, that are registered as Primary on one blade are


distributed with their buddies across all the other blades for redundancy.
Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 38

Example Normal Call Flow 1(7)


2 I will ask
random MSC

AP1

MSC

MSC

MSC

MSC

AP2

SPX1

MSC

IPLB

IPLB

MSC

SPX2

1
Incoming
call => SPX

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 39

Example Normal Call Flow 2(7)


2 Take
care of
this

3 Ok

1 - Round-Robin

AP1

MSC

MSC

MSC

MSC

AP2

SPX1

MSC

IPLB

IPLB

MSC

SPX2

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 40

Example Normal Call Flow 3(7)


1 I will find
right blade

3 Primary,
take care
of this

2 Read LV

TMSI
or
IMSI
Input

4 Ok

2 Read LV
AP1

MSC

MSC

MSC

MSC

AP2

P-HASH

SPX1

MSC

IPLB

IPLB

MSC

SPX2

B-HASH

A-Primary

A-Buddy

Output
Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 41

Example Normal Call Flow 4(7)


1 Where
is B?
2 You
(Cluster)
have B

AP1

MSC

MSC

MSC

MSC

AP2

SPX1

MSC

IPLB

IPLB

MSC

SPX2

A-Primary

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 42

HLR

Example Normal Call Flow 5(7)


3 Ok

1 - Round-Robin

AP1

MSC

MSC

MSC

MSC

AP2

SPX1

MSC

IPLB

IPLB

MSC

SPX2

A-Primary

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 43

2 Take
care of
this

HLR

Example Normal Call Flow 6(7)


2 Read LV

4 Ok

P-HASH

B-HASH

3 Primary,
take care
of this

B-Buddy B-Primary

AP1

MSC

MSC

MSC

MSC

AP2

SPX1

MSC

IPLB

IPLB

MSC

SPX2

A-Primary

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 44

HLR

1 I fill find
right blade
2 Read LV

MSC-S Blade Cluster Resilience


a MSC Blade temporary failure
-

VLR Data Replication: Primary & Buddy Blade

a MSC Blade permanent failure


-

Cluster reconfiguration: Subscriber Redistribution

BC Node failure
- MIP

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 45

Cluster Reconfiguration
Case:
One MSC Blade fails and is completely
out of service (e.g. cyclic restart, upgrade
failure or HW failure).

Active calls of the failed blade are


discontinued.
Subscribers have fully continued
service availability via their Buddy
blades.
The APZ Cluster Handler detects the
(non-) availability of the cluster
members and the distribution algorithm
can be adapted accordingly (automatic
reconfiguration).

Please note: in case of the a transient


failure (restart) of an MSC blade no
reconfiguration is needed!

Blade Cluster Overview Workshop | Ericsson Internal | 2011-11-13 | Page 46

MSC-S Blade Cluster


MSC
blade

MSC
blade

MSC
blade

MSC
blade

MSC
blade

SCTP/IP

I/O
SIS

Signaling
Signaling
SGW
proxy
proxy

TDM

ATM

RAN

IO
APG

IP

CN

lade
B
New
t
c
ne
Con

OSS