msc-s blade cluster introduction

Slide titleIn CAPITALS

50 pt

Slide subtitle 32 pt

MSC Server Blade Cluster Roadmap and Introduction

MUINLK

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

Slide title 40 pt


Text 24 pt

Bullets level 2-520 pt

Commercial in confidence MSC-S Blade Cluster Introduction 2009-11-122

Contents

Roadmap and Release Overview Why MSC Blade Cluster & Architectural change Blade Cluster Hardware and Architecture

Integrated Site ( IS)

Blade Cluster Components Blade Cluster Key Mechanism Basic Signalling View Key features & differences in various release Protocol Stacks


Slide title 40 pt


Text 24 pt



Contents





Slide title 40 pt


Text 24 pt



Mobile switching, roadmap overviewQ2 2009 update

General availability datesPhase 1 is MSS 5.2Phase 2 Drop 1 is MSS 6.0Phase 2 Drop 2 is MSS 6.1

General availability datesPhase 1 is MSS 5.2Phase 2 Drop 1 is MSS 6.0Phase 2 Drop 2 is MSS 6.1

MSC

IP-STP

MSS

GSM WCDMA

2008 2009 2010

ReleasedReady for Contract

IndicativeCandidate

2011

R13.2Oct

R14.1Q3

R5.2Feb

R6.1Q3

R6.0Q4

R14.1Q3

R13.2Oct

R5.1Oct

R7Q3

R15Q3

R15Q3


Slide title 40 pt


Text 24 pt



Extract of the CN/MSS MPP Roadmap

13.0

5.0 5.1

GAdates

2008Nov.

2009

CNCS7.0MSS R5.0

13.1

MSC BC ph1MSS R5.2

Mar

CNCS7.1MSS R5.1

14.0

CNCS8.0MSS R6.0

( incl BC ph2 drop1)

AugJuly

MSS R6.0: - MGw R6.0.1 + MSC R14.0 (BC ph2 drop1, ETSI/ANSI) - MGw R6.0 + MSC R13.2 (LA - non BC, ETSI/ANSI)

MSS R6.1: - MGw R6.1 + MSC R14.1 (NLA, LA & BC ph2)

13.2

Timeline MSS 6.0: TG0: 01/08 TG1: 05/08 TG2: Q3’08 start of Int.: Q4’08 LFD: Q1’09 PRA I: 05/09 (MGw R6.0 / MSC R13.2) PRA II: 05/09 (MGw R6.0/MSC R14.0) GA: 08/09

design base line: MSC R13.1 (BC ph1) MGw R5.1

6.0 6.1

14.1

CNCS8.0MSS R6.1

( incl BC ph2 drop2)

Nov

Timeline MSS 6.1: TG0: 05/08 TG1: Q3’08 TG2: Q4’08 start of Int.: Q1’09 LFD: Q3’09 PRA: 09/09 GA: 11/09

CNCS 8 release:MSS R6.0 MSS R6.1

6.0.1


Slide title 40 pt


Text 24 pt



Contents





Slide title 40 pt


Text 24 pt



Architecture OverviewArchitectural change

Robustness, better ISP, basically the system shall have 0 downtime. Software upgrade with 0 downtime. Scalability up to 4 million subscribers (approx. 400000- 500000

subscribers per MSC blade). Lower manufacturing costs than traditional APZ hardware. Migration towards IMS (How secure are investments in Ericsson CS

CN?) Footprint reduction State of the art system Ericsson has to stay competitive against competitors:

– Huawei already has a server for 1.8 Msub– Nokia already has a server for 1.2 Msub– Ericsson has 0.8 Msub server with (APZ 212 50)


Slide title 40 pt


Text 24 pt



Why Blade Cluster ?AXE MSC-S

Standard(APZ 212 50)

MSC-S

Blade Cluster(APZ 214 01)

Benefit

Capacity 1 M Ultra High

(up to 4 M)

4 times higher

Network efficiency

- higher 75% less MSC Nodes

Footprint

/4M subscribers

4,8 sqm(4 cabinets)

0,48 sqm(1 cabinet )

90% less space

Power consumption /subscriber

- lower 60% less

Green product

Scalable no easy 500.000 subscribers(per blade)

O&M costs - lower reduced to 45%

More For Less


Slide title 40 pt


Text 24 pt



“Classical” MSC-S versus Blade Cluster

MSC-S :

– High available node offering maximum flexibility for optimum network design

– Connecting to outside world via all possible signaling bearers– Freedom in physical location– Flexible pool design, geographical redundancy

MSC-S Blade Cluster

– The ones above +…– Highly scalable node– Optimal for high traffic concentration– Fits all operator capacity needs (from small to very large subscriber

capacity)– Improved redundancy scheme (n+1 on MSC blades)– Make use of the newest HW (common also for other modern platforms,

i.e. IMS)– Less manufacturing Costs


Slide title 40 pt


Text 24 pt



Contents





Slide title 40 pt


Text 24 pt



What is MSC-Server Blade Cluster? Based on a New HW Concept

MSC Server is based on a new HW concept

– Integrated Site infrastructure

– Traffic load on MSC-S blades

Same SW and HW features as in current MSC-S

Fig 1. Conceptual view of MSC Server Blade Cluster cabinet

Integrated Site infrastructure

MSC-S blades for traffic load

Integrated Site (IS) shared resources on blades for routing, ethernet

switching, network management etc

Current MSC-S HW technology

Single external interface (Signalling Proxy) to other network nodes

O&M and charging support (I/O)

MSC-S on blades for easy scalability and ultra-high capacity on small footprint

Signalling Proxy and I/O

Signalling Proxy and I/O

MS

C-S

bladeM

SC

-S blade

MS

C-S

blade

MS

C-S

bladeM

SC

-S blade

IS-blades

Blade Cluster


Slide title 40 pt


Text 24 pt



MSC-S Blade Cluster HW Layout Cabinet 1 and Cabinet 2

MS

C-S

blade

MS

C-S

blade

MX

B

MS

C-S

blade

MX

BM

SC

-S blade

MS

C-S

bladeM

SC

-S blade

MS

C-S

blade

MS

C-S

blade

MS

C-S

blade

MS

C-S

blade

Fan

Fan

Fan

SC

B – R

P/4

XD

BE

T155 W

ET

155 WS

TE

BS

TE

BA

LI/ST

EB

ALI/S

TE

BA

LIA

LIIR

BC

GB

ET

155 PE

T155 P

ST

EB

ST

EB

ALI/S

TE

BA

LI/ST

EB

ALI

ALI

IRB

CG

BX

DB

SC

B – R

P/4

Fan

SC

B – R

P/4

XD

BE

T155 W

ET

155 WS

TE

BS

TE

BA

LI/ST

EB

ALI/S

TE

BA

LIA

LIIR

BC

GB

ET

155 PE

T155 P

ST

EB

ST

EB

ALI/S

TE

BA

LI/ST

EB

ALI

ALI

IRB

CG

BX

DB

SC

B – R

P/4

Fan

Cabinet 2

MS

C-S

blade

Fan

Fan

Fan

MX

BE

XB

MS

C-S

bladeM

SC

-S blade

EX

BIS

ER

SIS

MS

C-S

bladeM

SC

-S blade

MS

C-S

blade

MS

C-S

blade

ISE

R

MX

BS

IS

Fan

NT

P/T

oDS

CB

– RP

/4

CP

UB

– AM

AU

B

DIS

C – A

AP

UB

– A

EX

T – M

ED

AP

UB

– BD

ISC

– BA

LAR

MS

CB

– RP

/4

CP

UB

– B

Fan

SC

B – R

P/4

CP

UB

– A

MA

UB

DIS

C-A

AP

UB

– B

CP

UB

– B

NT

P/T

oD

AP

UB

-A

DIS

C – B

SC

B – R

P/4

Alarm

boardA

larm board

Cabinet 1

SPX

IO

IS Infrastructure

MSC-S Blades

TDM Option

ATM Option


Slide title 40 pt


Text 24 pt



MSC-S Blade Cluster Node viewFunctional Components and General Concept

MSC Server Blade Cluster

MSC-Sblade

MSC-Sblade

MSC-Sblade

MSC-Sblade

MSC-Sblade

1+1

Cluster

1+1 1+1

CNRAN

M-MGW

Signaling proxySignaling Proxy (SPX)

hides the blade structure from

outside networks

MSC-S application on Generic Processor

Blades for traffic handling

I/OSIS

OSS

Input/output (I/O) is the O&M interface for

MSC blades and Signaling Proxy

Site Infrastructure Support (SIS) is the

O&M interface for the site infrastructure


Slide title 40 pt


Text 24 pt



Architecture Overview High level overview

OSS

CERCERISERISER SISSIS

IOIO

SISSIS

APG43APG43SGWSGW

MSC-Sblade

MSC-Sblade

SPXSPX

MSC-Sblade

MSC-Sblade

MSC-Sblade

MSC-Sblade

MSC-Sblade

MSC-Sblade

n+1 redundancy

1+1

1:n relation

RAN CN

MSC-S-Blade Cluster

1+1

TDM/ATMi/f

TDM/ATMi/f

SCTP/IP

TSC-Sblade

TSC-Sblade

TSC-Sblade

TSC-Sblade

1+1

1+1 redundancy


Slide title 40 pt


Text 24 pt



Architecture Overview MSC-S-BC components with L2 infrastructure


Slide title 40 pt


Text24 pt


MSC-Blade MSC-Blade TSC-Blade TSC-Blade

SIS

MXB-, EXB-switchIS L2 infrastructure

AP

G-IO, S

TS

AP

G-CH

S

SCB SCB

SPX

RP

RP

RP

SC

B

SC

B

SPX

RP

RP

RP

SC

B

SC

B

IS components

MSC/TSC Blades

Signaling Proxy

APG43, OSS-RC

ISER

…

……

Color Legend

ATM, TDM

IP

OSS-RC

MSC Server BC

…

IS O&M

IP ATM/TDM

O&M


Slide title 40 pt


Text 24 pt



Contents





Slide title 40 pt


Text 24 pt



Integrated Site consists of

a framework of rules for hosting of multiple applicationsrunning on various platforms in a scalable site solutionwith Telco grade characteristicsenabling unified O&M

a set of site infrastructure products using technology based on open standards and common HW bladesfor all applications

CorporateNetworks

PSTN

PSTN

IP backbone

Internet

3PP or Legacy system

O&M

Architecture OverviewIS Overview


Slide title 40 pt


Text 24 pt



FAN

OTHER

. . .

IS Infrastructure provides:• A physical shelf infrastructure

including power and cooling

TSP server basedBlade

Systeme.g. IMS

APZserverbased Blade

Systeme.g. MSC

IS Applications implemented• as SB Blade Systems, E.g.:

•HSN for Mobile@Home

•APZ based servers (E.g. HLR, MSC server, BSC…)

• Optional Customer Edge Router with LAN or WAN I/Fs and secure tunnels

• Secure SW & data storage, Equipment management andan O&M framework for Site O&M

• Resilient L2 Connectivity

• Optional Site LAN I/Fs (GE or FE)

FAN

ISER

MXB

EXB M

XB

SIS

SIS

EXB

ISER

Skipanimation

SGCmatedPair

BladeSystem

MPmatedpair

BladeSystem

HSN

NC

2* Dual Ethernet star

Management Bus

Backplane

IS Framework provides:• Specification of design rules and

guidelines (much like IETF-specs)

• or HA Blade Systems, E.g.:•SGC, MP, eML Multimedia

MGW•TSP based servers (E.g. MRFC,

CSCF, TAS)

Architecture OverviewIS Framework


Slide title 40 pt


Text 24 pt



Contents





Slide title 40 pt


Text 24 pt



Architecture OverviewBasic components MSC and TSC blades

– MSC traffic handling and service execution (no need for RPs)– Single sided CPs based on GEP board family

SPX nodes (including traditional APT equipment)– Signaling aggregation of C7 traffic and conversion to IP based

signaling towards the blades– Double sided CPs based on GEP board family

APG43 IOs– IO, collection of charging and statistical data for the MSC-, TSC-

blades and the SPX nodes, Alarm boards, Media– Double sided CPs based on GEP board family, Generic Disk board

and Generic Alarm board SIS blades

– O&M of the IS-L2 infrastructure– O&M for ISER

IS-L2 Ethernet switches (MXB,EXB)– Redundant L2 connectivity between the components

ISER– IP signaling traffic connectivity and routing

IS infrastructure


Slide title 40 pt


Text 24 pt



Architecture OverviewBlade Cluster Software (Highlights)

Consistent view on blade states via Cluster Handler (via the Cluster Handler, each blade will know the availability of the other blades)

IP Stack on CP and GCP on CP SUA for inter blade APT communication SUA/M3UA for blade-SPX communication Subscriber-based distribution of calls Two types of blades: MSC and TSC blades Identical SW/HW on MSC&TSC blades IP signaling traffic

connectivity and routing


Slide title 40 pt


Text 24 pt



Blade Architecture Overview

APZ 21401 on Single Sided Blades, IS adapted Consistent view on blade states via Cluster Handler RP free blade system: IP Stack on CP and GCP on CP SUA for inter blade APT communication

– INTROIP/SUA (OIP between blades)– MACIC/SUA (MAGAM inter blade communication)

SUA/M3UA for blade-SPX communication Subscriber based distribution of calls


Slide title 40 pt


Text 24 pt



Architecture Overview TSC Blades Task Overview

Handles BICCs, ISUP, China TUP external protocols Two TSC blades exists per cluster Each TSC blade has its own SPC Signalling traffic between SPX and TSC blade is handle

via M3UA GCP is either based on SCTP directly or M3UA


Slide title 40 pt


Text 24 pt



Architecture Overview MSC Blades Task Overview

Handles RANAP, BSSAP, MAP …. Node Functions are: O-MSC, GMSC, T-MSC, SSF SUA is used between SPX and MSC blades Only one SPC for all MSC blades together, except for GCP where

a M-MGW sees each blade Initial incoming messages are distributed on weighted round robin

to the MSC blade– Distribution function on the MSC Blade transfers the message to

the right blade

Subsequent message will stick to the used SCCP connection reference or TCAP transaction id

GCP is either based on SCTP directly or M3UA


Slide title 40 pt


Text 24 pt



Architecture Overview SPX Software (Highlights)

APZ 212 60 Double Side IP Stack on CP Uses SUA for internal connection to MSC Blades Uses M3UA for connection to TSC blades M3UA relay Two double sided SPX are used for redundancy reason


Slide title 40 pt


Text 24 pt



Architecture OverviewSPX Task overview

Signaling proxy “hides” the cluster from the network Terminates ATM and TDM and acts as Signalling

gateway to IP (applies to protocols using SCCP and also for direct MTP3 users)

M3UA relay for ISUP/BICC and GCP Acts as SCCP/SUA signalling gateway for RAN traffic Acts as Signalling gateway to M3UA for MTP3(b) traffic


Slide title 40 pt


Text 24 pt



MSC-S Blade Cluster ResilienceHighly Resilient Node

SPX 2 x (1+1) protection

MSC-blades n+1 protection TSC-blades 1+1 protection

APG43 1+1 protection (OAM & STS)

APG43 1+1 protection (Charging)

IS 1+1 protection


Slide title 40 pt


Text 24 pt



Contents





Slide title 40 pt


Text 24 pt



MSC-S Blade Cluster ConceptKey Mechanisms

Three key mechanisms provide the outstanding node availability of the MSC-S Blade Cluster

– Key mechanism 1 Load distribution

– Key mechanism 2 VLR data replication

– Key mechanism 3 Cluster reconfiguration

The 1+1 redundancy of all vital components (SPX, SIS, I/O) provides overall server redundancy


Slide title 40 pt


Text 24 pt



Key mechanism 1:

Load distribution

Distribution of subscriber data to

PRIMARY blade via hashing

Key mechanism 2:

VLR data replication

To BUDDY blade

CNRAN

1+1

Cluster

1+1

MSC-Sblade

MSC-Sblade

1+1

I/OSIS

OSS

MSC-S Blade Cluster Node ViewKey Mechanisms 1 and 2

Hashing

Hashing

Hashing

Hashing

Primary Buddy

M-MGW

Signalling proxy

MSC-Sblade

MSC-Sblade

MSC-Sblade

MSC-Sblade

MSC-Sblade

Round robin


Slide title 40 pt


Text 24 pt



MSC-S Blade Cluster Node ViewSubscriber Traffic Data is always Available in Two MSC-S Blades

MSC-S Blade Cluster

CNRAN

1+1

Cluster

M-MGW

1+1

MSC-Sblade

MSC-Sblade

MSC-Sblade

MSC-Sblade

MSC-Sblade

1+1

I/OSIS

OSS

Signalling proxy

AB C

A buddyA primary

B buddy

B primary

C primaryC buddy

Subscriber traffic datais always available

ín two MSC-S bladesfor redundancy

Primary bladeBuddy blade


Slide title 40 pt


Text 24 pt



Distribution of “Primary” and “Buddy” Data Subscriber traffic data is always available in two MSC-S blades

Mobile subscribers, that are registered as ‘primary’ on one blade are distributed with their ‘buddies’ across all the other blades for redundancy.

… … … … …

MSC-S Blade MSC-S Blade MSC-S BladeMSC-S BladeMSC-S Blade

BUDDYSubscriber

data

PRIMARYSubscriber

data

MSC-S Blade Cluster

…


Slide title 40 pt


Text 24 pt



Contents





Slide title 40 pt


Text 24 pt



Signaling View of an Example Network – With MSC-Server Blade Cluster MSS R5.2

RAN

M-MGW

HLR

ISUPBICC

RNCBSC

M-MGWM-MGW

Virtual M-MGw’s

Local PSTN

MSC-S TSC

e.g. MAPGCP

RANAPBSSAP

Service nodes

HLR

GCP

Cluster

MSC-Sblade

MSC-Sblade

MSC-Sblade

Signalling proxy

TSC-Sblade

TSC-Sblade

M-MGw is ”cluster aware”

(same relation of MSC-S and M-MGw as today)

ISUP and BICC are connected to TSC-S blades


Slide title 40 pt


Text 24 pt



Signaling View of an Example Network – With MSC-Server Blade Cluster , MSS R6.0

RAN

HLR

ISUP

BICC

RNCBSC

M-MGW

Virtual M-MGw

Local PSTN

MSC-S TSC

e.g. MAPGCP

RANAPBSSAP

Service nodes

HLR

GCP

Cluster

MSC-Sblade

MSC-Sblade

MSC-Sblade

Signalling proxy

TDM devices pooled

2 TSC-S bladesAre present forBICC and ISUP

TSCblade

TSCblade


Slide title 40 pt


Text 24 pt



Signaling View of an Example Network – With MSC-Server Blade Cluster, MSS R6.1

RAN

HLR

ISUP

BICC

RNCBSC

M-MGW

Virtual M-MGw

Local PSTN

MSC-S TSC

e.g. MAPGCP

RANAPBSSAP

Service nodes

HLR

GCP

Cluster

MSC-Sblade

MSC-Sblade

MSC-Sblade

Signalling proxy

TDM devices pooled

TSC-S bladesare removed

(and exchanged with additionalMSC-S blades)

MSC-Sblade

MSC-Sblade


Slide title 40 pt


Text 24 pt



MSC-S Blade Cluster Phase ISystem Architecture, MSS 6.0

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

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

POIs and other PLMNs

MSC-Server-Cluster

BICC and ISUP, H.248

SPX

RAN, SGSNs,ServiceNodes

RANAP, BSSAP,BSSAP+, INAP,MAP, H.248

BICC and ISUP, MAP, INAP, H.248

Control of all payload circuits

towards POIs and other

PLMNsControl of all payload circuits towards the RAN


Slide title 40 pt


Text 24 pt



MSC-S Blade Cluster Phase ISystem Architecture, MSS 6.1

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

POIs and other PLMNs

MSC-Server-Cluster

BICC and ISUP, RANAP, BSSAP,BSSAP+, INAP,MAP, H.248

SPX

RAN, SGSNs,ServiceNodes

Control of all payload circuits towards POIs and other PLMNsControl of all payload circuits towards the RAN


Slide title 40 pt


Text 24 pt



MSC-S Blade Cluster Phase IConnectivity Between MSC-S and M-MGw in BC 5.2


Slide title 40 pt


Text 24 pt





Slide title 40 pt


Text 24 pt



Contents





Slide title 40 pt


Text 24 pt



MSC-S Blade Cluster Phase IWhat would this change?

MSC and TSC blades

Tight relation between blades and V-MGws

1+1 TSC redundancy

3 M Subscriber Max

3 ”bottlenecks” (APG, TSC, SPX)

Only MSC blades

Single node view

N+1 MSC blade redundancy

8 M Subscriber

2 ”bottlenecks” (APG, SPX)

No fixed access Primary Rate Access (PRA)*

MSC-S Blade Cluster ph1

*) Not in current scope

MSC-S Blade Cluster ph2


Slide title 40 pt


Text 24 pt



MSC-S Blade Cluster Phase IIMSC-S R14.0 – BC 6.0

IUPCH (part 1) (Improved User-plane Circuit Handling)

– One virtual MGw for all MSC blades– Adaptation of the A-interface– Trunks remain on TSC blades as in Phase 1

Minimum O&M to support the other changes Support for “smooth” MSC blade expansion List of MSC-S R13.2 features:

– Iu/IP – Encryption of LI – Non-resilient/scalable SIP/SIP-I (including G.729 and RTCP)– AMR-WB


Slide title 40 pt


Text 24 pt



MSC-S Blade Cluster Phase IIMSC-S R14.1 – BC 6.1

IUPCH (part 2) – Trunk adaptation to IUPCH– Removal of TSC blades

BC Adaptation of existing Features– ATM-IP migration on interlink– Signaling enhancements: IETF+

M3UA– (PRA support for BC (incl.

adaptation to IUPCH))*– (AMMS support for BC)*– Resilient/Scalable SIP *

IP Load Balancer (on ISER): – SCTP Server LB (for GCP/SCTP)– SCTP Client LB (for IUA) *, – TCP&UDP Server and Client (for

SIP enhancements) **) Not in current scope

BC Ph 2 O&M Enhancements:– Configuration Management: – Fault Management– Performance Management– Software management– Test and Fault Localization– Network Management

New Features: – CCBS, – A-i/f over IP, – Virtual MSC, …

Capacity– 8 M subscribers– APZ 21260 as SPX


Slide title 40 pt


Text 24 pt



Contents





Slide title 40 pt


Text 24 pt



Signalling Stack for TCAP and SCCP Users TCAP and SCCP Users

termination, conversion and distribution

IP

TDM*

ATM* IP

Preceding node MSC blade with protocol termination

SPX

MTP2

SUA

SCTP

MTP1 IP

MTP3

SSCF-NNI

SCCP-CO, SCCP-CL

AAL5

SCCOP

MTP2

MTP1

MTP3/b

SSCF-NNI

SCCP-CO, SCCP-CL

AAL5

SCCOP

RANAP/ BSSAP

SUA

SCTP

IP

SCTP

IP

M3UA

TCAP

TCAP user

TCAP

TCAP user

SCTP

IP

MSC Server BC internal MSC Server BC external

M3UA

RANAP/ BSSAP

Note: * In addition, high speed links can be used between external node and SPX, depending on the market.


Slide title 40 pt


Text 24 pt



Signalling Stacks for Direct MTP3 Users

Direct MTP3 Users

ATM*

TDM*

termination, conversion and relay

IP

SPX (optional for IP bearer)


IP

TSC blade with application proto col termination

POI in core network

MTP3

MTP2

M3UA

SCTP

MTP1

IP

MTP3 /b

MTP2

MTP1

M3UA

SCTP

IP

ISUP, BICC, TUP

ISUP, BICC, TUP *

SCTP

IP

M3UA

IP

SUA

SCTP

IP

Internal**

Internal**

SUA

SCTP

IP

IP

termination, conversion and distribution

SSCF -NNI

AAL5

SCCOP

SSCF -NNI

AAL5

SCCOP

Notes: * In addition, high speed links can be used between external node and SPX. ** Internal Call Control Protocol

MSC bl ade with protocol termination


Slide title 40 pt


Text 24 pt



Signalling Stacks GCP

IP

GCP

ATM

IP

IP

GCP

IP

MSC or TSC blade with application protocol

termination

preceding node: M-MGw SPX (optional for IP bearer)

SCTP

M3UA

IP

MTP3b

SSCF-NNI

AAL5

SCCOP

SCTP

IP

MTP3b

SSCF-NNI

AAL5

SCCOP

SCTP

IP

M3UA

termination, conversion and relay

M3UA

SCTP

IP

SCTP

IP



Slide title 40 pt


Text 24 pt



msc-s blade cluster introduction

Documents