Top Banner
Blade Cluster SAS
25

Blade Cluster

Feb 02, 2016

Download

Documents

violetchuwa

msc ericson
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Blade Cluster

Slide titleIn CAPITALS

50 pt

Slide subtitle 32 pt

Blade Cluster

SAS

Page 2: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-082

Motivations

Smooth migration towards IMS by means of HW re-utilization, Integrated Site (IS) structure.

Scale MSC-Server solution (up to 15 blades in MSC SBC).

Seamless upgrade/update.

Page 3: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-083

FAN

MXB

SIS

CER

IMS

IMS

MSC

MSC

MSC

MSC

MSC

MSC

MSC

MSC

CER

SIS

MXB

FAN

Smooth migration towards IMS

As traffic migrates from CS to IMS, HW can be re-configured from an MSC blade system to an IMS blade system.

IMS CSIMS CSIMS CS

FAN

MXB

SIS

CER

IMS

IMS

IMS

IMS

MSC

MSC

MSC

MSC

MSC

MSC

CER

SIS

MXB

FAN

FAN

MXB

SIS

ISER

IMS

IMS

IMS

IMS

IMS

IMS

IMS

MSC

MSC

MSC

ISER

SIS

MXB

FAN

Page 4: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-084

Common concept for scalability and robustness

MSC cluster approach:

distribute load between

members of a cluster of

MSC-S blades

Facilitates seamlessupgrades, zero downtime:Isolate traffic from oneblade (other bladescontinue to run traffic),upgrade it and bring itback into service.

Signaling Proxy/SGW for link aggregation

OSS

CERCERISERISER

SISSIS IOIOSISSIS IOIOSGWSGW

MSC-Sblade

MSC-Sblade

Signalingproxy

Signalingproxy

MSC-Sblade

MSC-Sblade

MSC-Sblade

MSC-Sblade

MSC-Sblade

MSC-Sblade

n+m redundancy

1+1

1:n relation

RAN CN

SAN

MSC-S Cluster

1+1

TDM/ATMi/f

TDM/ATMi/f

SCTP/IP

NW I/F

Page 5: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-085

MGW-1MGW-1 MGW-2MGW-2 MGW-3MGW-3

MSC-in-pool vs. MSC cluster

1. Move the distribution function from the RAN to the MSC cluster

2. Replicate VLR data between cluster members

RNCRNC

MSC-Pool MSC-Cluster

Load control and distribution functionLoad control and

distribution function

HLRHLR

MSC-1MSC-1 MSC-2MSC-2 MSC-3MSC-3

HLRHLR

MSC-1MSC-1 MSC-2MSC-2 MSC-3MSC-3

MGW-1MGW-1 MGW-2MGW-2 MGW-3MGW-3

RNCRNCLoad control

and distribution function

Load control and distribution

function

Note: both concepts can coexist: MSC-in-pool is possible on NW level in the MSC-cluster solution

Page 6: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-086

Signaling Proxy/SGW - motivation

Traditional C7 I/f are expensive compared to IP

The SGW is used as an aggregation node for many C7 interfaces

towards a broadband IP/SCTP interface

The SGW can hide the Application Server node/network topology by

doing an address translation

The SGW acts as the i/f device owner

facilitates the n+m redundant MSC processor blades

A SGW helps to achieve geographic redundancy.

A SGW is a means to change the addressing in the application

servers from point codes to IP addresses, and hence becoming a

vehicle for a more IP centric network approach

Page 7: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-087

I&V Configurations

MSC-S BC Small

4 MSC and 2 TSC blades, 1 ISL testboard, 2 APG43, 1 SPX, IP, ATM, TDM GS, optional extension to 2 SPX possible.

0 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

SC

B-R

P/4

MA

UB

1

SC

B-R

P/4

SC

B-R

P/4

ALA

RM

MA

UB

0

SC

B-R

P/4

MX

B

ISL

ISL2 T

estb

oard

EX

B

EX

B

MX

B

GE

P: C

PU

B 1

A

GE

D: H

DD

1A

GE

P: C

PU

B 0

B

GE

P: A

PU

B 0

A

GE

D: H

DD

0A

Media

SIS

ISE

R

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: A

PU

B 0

B

GE

P: C

PU

B

GE

D: H

DD

0B

slot

GE

P: C

PU

B 1

B

GE

P: A

PU

B 1

A

GE

P: C

PU

B 0

A

GE

D: H

DD

1B

GE

P: A

PU

B 1

B

ISE

R

SIS

MSC-C BC Small Configuration without optional extension

Page 8: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-088

I&V Configurations

MSC-S BC small

0 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

SC

B-R

P/4

XD

B

ET

155-0

ET

155-1

ST

EB

-0

ST

EB

-1

ALIe

-0

ALIe

-1

ALIe

-2

ALIe

-3

IRB

ET

155-0

ET

155-1

ST

EB

-0

ST

EB

-1

ALIe

-4

ALIe

-5

IRB

XD

B

SC

B-R

P/4

SC

B-R

P/4

XD

B

ET

155-0

ET

155-1

ST

EB

-0

ST

EB

-1

ALIe

-0

ALIe

-1

ALIe

-2

ALIe

-3

IRB

ET

155-0

ET

155-1

ST

EB

-0

ST

EB

-1

ALIe

-4

ALIe

-5

IRB

XD

B

SC

B-R

P/4

slot

CG

B

CG

B

CG

B

CG

B

MSC-C BC Small Configuration showing optional extension in second cabinet.

Page 9: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-089

I&V Configurations

MSC-S BC Medium

11 MSC and 2 TSC blades, 2 ISL X-Boards , 2 ISL testboards ,2 APG43, 2 SPX, ATM, TDM, GS.

0 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

SC

B-R

P/4

MA

UB

1

SC

B-R

P/4

SC

B-R

P/4

ALA

RM

MA

UB

0

SC

B-R

P/4

MX

B

ISL

ISL2 T

estb

oard

EX

B

EX

B

MX

B

GE

P: C

PU

B 1

A

GE

D: H

DD

1A

GE

P: C

PU

B 0

B

GE

P: A

PU

B 0

A

GE

D: H

DD

0A

Media

SIS

ISE

R

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: A

PU

B 0

B

GE

P: C

PU

B

GE

D: H

DD

0B

slot

GE

P: C

PU

B 1

B

GE

P: A

PU

B 1

A

GE

P: C

PU

B 0

A

GE

D: H

DD

1B

GE

P: A

PU

B 1

B

ISE

R

SIS

MSC-C BC Medium Configuration – Cabinet 1

Page 10: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-0810

I&V Configurations

MSC-S BC Medium

0 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

SC

B-R

P/4

XD

BE

T155-0

ST

EB

-0S

TE

B-1

ALIe

-0A

LIe

-1A

LIe

-2A

LIe

-3IR

B

ET

155-0

ST

EB

-0S

TE

B-1

ALIe

-4A

LIe

-5A

LIe

-5A

LIe

-5IR

B

XD

BS

CB

-RP

/4

SC

B-R

P/4

XD

BE

T155-0

ST

EB

-0S

TE

B-1

ALIe

-0A

LIe

-1A

LIe

-2A

LIe

-3IR

B

ET

155-0

ST

EB

-0S

TE

B-1

ALIe

-4A

LIe

-5A

LIe

-5A

LIe

-5IR

B

XD

BS

CB

-RP

/4

MX

B

ISL

ISL2 T

estb

oard

MX

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

slot

CG

B

CG

B

CG

B

CG

B

MSC-C BC Medium Configuration – Cabinet 2

Page 11: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-0811

I&V Configurations

MSC-S BC Large

15 MSC and 2 TSC blades, 2 ISL X-Boards , 2 ISL testboards ,2 APG43, 2 SPX, ATM, TDM, GS.

0 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

SC

B-R

P/4

MA

UB

1

SC

B-R

P/4

SC

B-R

P/4

ALA

RM

MA

UB

0

SC

B-R

P/4

MX

B

ISL

ISL2 T

estb

oard

EX

B

EX

B

MX

B

GE

P: C

PU

B 1

A

GE

D: H

DD

1A

GE

P: C

PU

B 0

B

GE

P: A

PU

B 0

A

GE

D: H

DD

0A

Media

SIS

ISE

R

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: A

PU

B 0

B

GE

P: C

PU

B

GE

D: H

DD

0B

slot

GE

P: C

PU

B 1

B

GE

P: A

PU

B 1

A

GE

P: C

PU

B 0

A

GE

D: H

DD

1B

GE

P: A

PU

B 1

B

ISE

R

SIS

MSC-C BC Large Configuration – Cabinet 1

Page 12: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-0812

I&V Configurations

MSC-S BC Large

0 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

SC

B-R

P/4

XD

BE

T15

5-0E

T15

5-1S

TE

B-0

ST

EB

-1A

LIe-0A

LIe-1A

LIe-2A

LIe-3IR

B

ET

155-0

ET

155-1

ST

EB

-0S

TE

B-1

ALIe-4

ALIe-5

ALIe-6

ALIe-7IR

B

XD

BS

CB

-RP

/4

SC

B-R

P/4

XD

BE

T15

5-0E

T15

5-1S

TE

B-0

ST

EB

-1A

LIe-0A

LIe-1A

LIe-2A

LIe-3IR

B

ET

155-0

ET

155-1

ST

EB

-0S

TE

B-1

ALIe-4

ALIe-5

ALIe-6

ALIe-7IR

B

XD

BS

CB

-RP

/4

MX

B

ISL

ISL2 T

estbo

ard

MX

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

GE

P: C

PU

B

CG

B

CG

B

CG

B

CG

B

slot

MSC-C BC Large Configuration – Cabinet 2

Page 13: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-0813

Call setup inside the Cluster

MSC blades The MSC blades are single processing blades. Redundancy is

achieved by allocating a primary and a buddy blade for each subscriber registered in the system. The MSC blades host the complete MSS functionality.

TSC blades The TSC blades are single processing blades. Redundancy is

achieved on network level, by connecting 2 routes (one on each TSC blade) towards other core network nodes. The TSC blades execute only transit functionality, i.e. all ISUP and BICC traffic destined to the MSC is handled by these elements. ISUP and BICC protocols are terminated and converted to an internal protocol, before sending the traffic to the MSC-blades. Optionally, they can also work as a pure transit node, relaying ISUP and BICC traffic towards other network nodes.

Page 14: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-0814

Call to mobile subscriber inside the cluster mobile number

TSC (SPC - 1) TSC (SPC - 2)

MSC/GMSC/SSF MSC/GMSC/SSF MSC/GMSC/SSF MSC/GMSC/SSF MSC/GMSC/SSF…

SGW

TSC (Blade 1) TSC (Blade 2)

MSC/GMSC (Blade 3) MSC/GMSC (Blade 4) MSC/GMSC (Blade 5) MSC/GMSC (Blade 6) MSC/GMSC (Blade n)…

SPX

ISUP/BICC

Internal OIP signalling

1.

2.

3.4.

Traffic distribution

Page 15: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-0815

Call to mobile subscriber inside the cluster mobile number

Step Description 1 The SPX has selected TSC 1 to handle the call via round robin in the M3UA configuration

(detailed chapter x.y.z). The call setup message (IAM) received by the TSC blade includes a mobile subscriber number. TSC blades are not allowed to perform HLR interrogation, because this potentially would lead to an unbalanced load between the TSC blades. On TSC blades just transit calls are allowed. In this call case on the TSC blade and internal trunk shall be seized distributing the traffic to all MSC blades (Error! Reference source not found.. for details). System internally on the TSC blade a round robin mechanism selects one MSC to perform HLR interrogation (Blade 4 in the example). Between TSC and MSC blades an MSC-S BC internal protocol is used for configuration details see chapter Error! Reference source not found..

2 On blade 4 the first traffic analysis instance will seize a GRI route for HLR interrogation. For the addressing of required MAP messages between the MSC-S BC and HLR and HLR and MSC-S BC/VLR see chapter x.y.z SCCP connectivity in MSC-S BC for details. In MSC-S BC each MSC blade owns at least one MSRN series (see chapter Error! Reference source not found.. for details). In the shown case a MSRN that terminates on blades 6 is provided.

3 In the traffic analysis instance after HLR interrogation the MSRN is analyzed (see chapter Error! Reference source not found.. for details). The call is routed via internal protocol to the terminating blade.

4 The Call terminates on blade 6.

Page 16: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-0816

Outgoing Call from mobile subscriber

TSC (SPC - 1) TSC (SPC - 2)

MSC/GMSC/SSF MSC/GMSC/SSF MSC/GMSC/SSF MSC/GMSC/SSF MSC/GMSC/SSF…

SGW

TSC (Blade 1) TSC (Blade 2)

MSC/GMSC (Blade 3) MSC/GMSC (Blade 4) MSC/GMSC (Blade 5) MSC/GMSC (Blade n)…

SPX

ISUP/BICC

Internal OIP signalling

2.

1.

Traffic distribution

MSC/GMSC (Blade 6)

Page 17: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-0817

Outgoing Call from mobile subscriber

Step Description

1 A mobile subscriber located on blade 3 calls a subscriber outside the cluster. Assuming that both TSC blades have connectivity to the destination, an internal trunk shall be seized distributing the traffic to all TSC blades. If a mobile subscriber located inside another node belongs to the same network the HLR interrogation is done directly on the blade 3 as already described in the previous example. All MSC are configured as GMSC.

2 In the traffic analysis instance on the TSC blade an outgoing towards the destination is seized.

Page 18: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-0818

Call to mobile subscriber MSRN received

/Handover in non anchor MSC

TSC (SPC - 1) TSC (SPC - 2)

MSC/GMSC/SSF MSC/GMSC/SSF MSC/GMSC/SSF MSC/GMSC (Blade 6) MSC/GMSC/SSF…

SGW

TSC (Blade 1) TSC (Blade 2)

MSC/GMSC (Blade 3) MSC/GMSC (Blade 4) MSC/GMSC (Blade 5) MSC/GMSC (Blade n)…

SPX

ISUP/BICC

Internal OIP signalling

1.

2.

Traffic distribution

Page 19: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-0819

Call to mobile subscriber MSRN received /Handover in non anchor MSC

Step Description 1 The SPX has selected TSC 1 to handle the call via round robin in the M3UA configuration

(detailed chapter x.y.z). The call setup message (IAM) received by the TSC blade includes an MSRN owned by the MSC-S BC. For efficient routing purposes in MSC-S BC also TSC blades are aware which MSRN series are own by which MSC blades inside the cluster (see chapter Error! Reference source not found.. for details). This information is used to the call is routed via internal protocol to the terminating MSC blade.

2 The Call terminates on Blade 5.

Page 20: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-0820

Mobile originating to mobile terminating call

TSC (SPC - 1) TSC (SPC - 2)

MSC/GMSC/SSF MSC/GMSC/SSF MSC/GMSC/SSF MSC/GMSC (Blade 6) MSC/GMSC/SSF…

SGW

TSC (Blade 1) TSC (Blade 2)

MSC/GMSC (Blade 3) MSC/GMSC (Blade 4) MSC/GMSC (Blade 5) MSC/GMSC (Blade n)…

SPX

ISUP/BICC

Internal OIP signalling

1.

Traffic distribution

Page 21: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-0821

Mobile originating to mobile terminating call

Step Description 1 As all MSC blades are configured as GMSCs and a mobile subscriber of the own network is

called HLR interrogation is done on the MSC blade 3. At HLR interrogation a MSRN owned by blade 6 is received. Finally the call terminates on Blade 6.

Page 22: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-0822

Transit Call

MSC/GMSC/SSF MSC/GMSC/SSF MSC/GMSC/SSF MSC/GMSC/SSF MSC/GMSC/SSF…

SGW

TSC (Blade 1) TSC (Blade 2)

MSC/GMSC (Blade 3) MSC/GMSC (Blade 4) MSC/GMSC (Blade 5) MSC/GMSC (Blade n)…

SPX

ISUP/BICC

Internal OIP signalling

Traffic distribution

MSC/GMSC (Blade 6)

1.

Call handled on own blade

Page 23: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-0823

Transit Call

Step Description 1 The SPX has selected TSC 1 to handle the call via round robin in the M3UA configuration . The

call setup message (IAM) received by the TSC blade includes a B-number which is determined for another node in the network. In the traffic analysis instance on the TSC blade an outgoing towards the destination is seized. If this one is congested an alternative internal trunk route can be selected to route the call via other TSC blade towards the destination. Please note that only complete B-Numbers shall be sent between blades. Overlap sending of digits is not supported between blades.

Page 24: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-0824

References

MSC Server Blade Cluster Configuration User Guide MSC-S BC dimensioning and packaging analysis

Page 25: Blade Cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example.

Slide title 40 pt

Slide subtitle 24 pt

Text 24 pt

Bullets level 2-520 pt

Ericsson Confidential 2007-03-0825