hosting – different approaches

IMS On Cloud & Voice On Cloud

Tu Jason

VP of Core Network

© ZTE Corporation. All rights reserved.

High CAPEX

Core Network Equipment Transmission Equipment Cost of Accessories

Why we need cloud?

1 Headquarter + 4 OpCos = 5 IMS Systems TCO for IMS network deployment is high！

MTOHeadquarter

OpCo A

OpCo B

OpCo C

OpCo D

High OPEX

Network Maintenance Rental Cost of Space Cost of Power Employee Training Cost Spares

Low Resource Utilization

Hard for resource allocation and scheduling amongsystems in different areas

http://www.iconpng.com/icon/16278






What kind of Cloud ?

CARRIER-GRADE

Optimized Telecom-Signal & Telecom-Session Control

Optimized Content & Media Resources

Optimized Real-time Processing

SLA

Super UDC

TDM & IP Compatibility

Multiple HW & OS adaptation for IT services

High Scalability

N+K Redundancy

Hitless Upgrade

Large Capacity

99.9999% Reliability

OPTIMIZATION

Differentiators

What Kind of Cloud?


Architecture of The Cloud

Hosts/Blades

Hardware Layer

Hyperviosr

Iaas Layer: Tecs

Cluster Controller

Tecs Center

Host Controller

Host Controller

Host Controller

Software Layer

OS:

CGEL

APP:C

SCF

OS:

CGEL

APP

OS:

CGEL

APP

OS:

SUSE

APP:

DNS

Serve

r

OS:

Win

APP

OS

APP

OS

APP

Middl

eWare

VM VM VM VM VM VM VM

Application

Hardware

Abstraction


Hardware of the Cloud

Enhanced TCA Platform Unified All IP ETCA platform

High performance, perfect

reliability and flexible evolution &

expansion

Several elements can run on one

board

Each board could act as one

element

Support consolidated IMS – “IMS

in a Box” deployment for multi-

branches

CS

IMS

UDC

CDN

AS

SBC

CG

EMS

99.9999% Reliability, Unified ETCA, Shared Boards and Hardware, Lower OPEX


TECS of the Cloud -- Virtual Machine Technique

TECS Clusters

Cluster is the effective function area

Cluster Controllers are in duty to configure and manage clusters

Host Controllers executes directives from Cluster Controller

A unique TECS Center manages total system

TECS Features

Multi-platform and Multi-OS capabilities

Automatic Deployment Function

Adaptive Resource dispatcher

Fault isolation and self-heal

Hardware

NE1

APP

TULIP

OS

APP APP

TULIP TULIP

OS OS

VM VM VM

TECS(TULIP Elastic Computing System)

NE2

APP

TULIP

OS

APP APP

TULIP TULIP

OS OS

VM VM VM


TULIP Middleware of the Cloud

Features

•Advanced software

architecture with middleware

•Distributed and centralized

adaptability

•Multi-process independence

for fault isolation and

independent upgrade

•Support for multi-CPU/multi-

core

•Perfect Fault detection and

recovery

•……Ethernet Switching Channel

Distributed Applications

…

TULIP(Telecom Universal Integrated Platform)

APP Dispatching

TimerTime

Management

Message Distribution

Memory Management

VOS

Exception Logging/analysis

Main Control

…Blade Blade Blade

APP1 APP2 APPn

System Monitoring

Userland Shell

File Management

Resources Configurable

OS OS OS


Hosting – Different Approaches

CSCF1

Middleware

OS

CSCF 2 CSCF 3

CSCF1

Middleware

OS

CSCF2 CSCF3

Middleware

Middleware

OS OS

VM1 VM2 VM3

Middleware based multi-instance Virtual machine based

MMTEL AS

Middleware

OS

Multi domain


Multi domain Features in China Telecom (Fujian)

Fu Zhou

MMTEL AS

CSCF

HSS

CG

EMS

Fu Zhou

AGCF

SBCMGW

Ning De

SBCMGW

Nan Ping

SBCMGW

CS CS CS

BOSSBOSSBOSS

MGCF

Partial resource managed byOperator A in City A

Partial resource managed byOperator B in City B

AG AG AG


Element

Region A

Region B

Resource type 1

Resource type 2

Resource type 3

Resource type 4

Resource scope

setting

Resource scope

setting

Resource scope

setting

Resource scope

setting

Resource Management Model And Authority Management Model

Operator role

Element A

Element B

Region A

Region B

Region C

Region D

Operation set 1

Operation set 2

Operation set 3

Operation set 4


Hosting – Different approaches

CSCF1

Middleware

OS

CSCF 2 CSCF 3

CSCF1

Middleware

OS

CSCF2 CSCF3

Middleware

Middleware

OS OS

VM1 VM2 VM3

Middleware based Virtual machine based

MMTEL AS

Middleware

OS

Multi domain


Multi Instance Deployment

Hosted city

AS2

HSS

CG

EMS

Hosted city

AGCF

SBCMGW

Country A

SBCMGW

Country B

SBCMGW

CS CS CS

BOSSBOSSBOSS

MGCFMGCFMGCF

AS2AS2

AGCF AGCF

CSCF, AS,MGCF, AGCF in the hosted premises

Access and interworking NEs are deployed in local OpCo;

Secure Communication

No media detour

CSCFCSCF CSCF

AG AG AG


Multi-instance Maintenance

Operations Authorization

NEs Authorization

OpCo A

OpCo B

OpCo C

Role A

Role B

Role C

…

CSCF

MMTel AS Add ModifyDelete Show …

Add ModifyDelete Show …

CSCF


…

Add ModifyDelete Show…

CSCF


…

Add ModifyDelete Show …

Operating staff of each OpCo maintains all the instances belonging to their domain

Authorization and authentication ensures each OpCo can only manage its own NEs


Hosting – Different approaches

CSCF1

Middleware

OS

CSCF 2 CSCF 3

CSCF1

Middleware

OS

CSCF2 CSCF3

Middleware

Middleware

OS OS

VM1 VM2 VM3

Middleware based Virtual machine based

MMTEL AS

Middleware

OS

Multi domain


Hosting Approaches ComparisonItems Multi domain Multi instance Virtual machine

Technology adopted Implemented through the network management

Based on the same Middleware

Based on Virtual machine/TECS

Instance no. only one instance Multiple instances run on one board or one shelf

Multiple instance could run on one on one board or one shelf

Integration of multiple instances

NA Good Best, application with different OS can also be integrated in one board

Decoupling of each Opco

Not fully decoupled Fully decoupled Fully decoupled

Hardware dependence

On ATCA hardware On ATCA hardware ATCA and other general x86 based hardware

ZTE product Availability

Available Available for test (sharing on one board) /commercial

In process of validation

Limitation Not all resources can be managed by different Opcos

Software platform version alignment for each element (sharing one board).

Performance

Suitable scenario Suitable for fast delivery and branches of same Operator sharing similar requirement

Suitable for Opco who would like to fully control his instance, e,g, VNO

Suitable for Opco, VNO, resellers, enterprise and other parties.


Performance Cost Analysis – TULIP vs. TECS

CPU 30% CPU 50% CPU 70% CPU 80%

Cap. Lat. Cap. Lat. Cap. Lat. Cap. Lat.

NoVM

240 450 320 488 390 500 420 512

noVT-X

35 539 150 576 275 583 320 610

with VT-X

45 530 180 543 290 575 350 578

P-CSCF

S-CSCF

I-CSCF

SUSE Linux

Blade 1

HSS

OM

C

SUSE Linux

Blade 2

TULIP TULIP

P-CSCF

S

SUSE Linux

Blade 1

I

VM

I-CSCF

S

SUSE Linux

P

VM

S-CSCF

P

SUSE Linux

I

VM

HSS

OM

C

SUSE Linux

Blade 2

TULIP TULIPTULIP TULIP

ConfigurationHW: ZTE ATCA Platform, Model J Blade, Dual Xeon 5500 Processors, 24GB DDR3 Mem, Smart Ethernet Card support SR-IOVVMM: Xen 4.0, kernel 2.6.32Domain0 OS: SUSE 11.1 Enterprise VersionSW:, SUSE 10.2 , kernel 2.6.21 ZTE IMS Debug Version


Performance Cost Analysis – TULIP vs. TECS

0

50

100

150

200

250

300

350

400

450

CPU 30% CPU 50% CPU 70% CPU 80%

No VM

No VT-X

with VT-X

0

100

200

300

400

500

600

700

CPU 30% CPU 50% CPU 70% CPU 80%

No VM

No VT-X

with VT-X

1. On average, VM cost 48% performance without VT-X 2. On average, VM cost 42% performance with VT-X3. On average, using VT-X improving 11%performance

1. On average, 18% deterioration in latency without VT-X 2. On average, 14% deterioration in latency with VT-X3. On average, using VT-X improving 22% latency


Integration with Other Hypervisor

CSC

F

SSS

EMS

MM

TEL A

S

HC Hypervisor(Vmware)

HSS

CG

MG

CF

ENU

M

HC Hypervisor(XEN)

TECS platform (CC+TC)

Applications

ZTE TECS platform plans to support multiple hypervisors


Service Application

OSS&BSS Applications

Immigration of 3rd APPs

What’s on the Cloud?

HD VideoConference

IPTV

EMS Charging Provision

PORTAL

SELF-CARE

Multimedia Telephony

Enhanced Phone Book

Web Call

Multi-Tenancy


Typical IMSCloud Scenarios


Integrated Switch By Virtualization

Integrated Controller‘iCX’

Integrated Media Gateway‘iMG’

BOSSSCPUDC

GSM/UMTSLTE

Wi-Fi XDSL PON

IMSCS

MSCS

MGW

MRFP

IM-MGW A-BGF

VIG

I-BGF

CSCF

xAGCF MRFC

MGCF PSS

iCX (intelligent Controller eXtensive)

iMG (integrative Media Gateway)

• Unified network architecture ensures smooth

evolution

• Unified OMC improves efficiency

• Unified user number enhances user loyalty

iCX

iMG(ZTE Voice&video over Anyaccess)

SIP AS

Typical Scenario: zVOA


http://www.easyicon.cn/icondetail/4629/






CS IMS CS IMS

Evolve

IMSCSEvolve

Innovation & Convergence: Convergent CS&IMS products, iCX and iMG, integrate all the NEs of CS and

IMS (iCX=MSCS/e+CSCF+AGCF+MMTel AS+MGCF+MRFC+…, iMG=MGW+IM-

MGW+MRFP+VIG+BGF+…), ensures smooth evolution from CS to IMS

Pool Resource Management: Hardware resources (CPU, memory, interface, etc.) form a pool

shared by CS and IMS, to improve system resource utilization rate

Dynamic Resource Adjustment: With the evolution from CS to IMS and users' migration, the

system processing capability is dynamically adjusted between CS and IMS, to protect operator's

investment and reduce TCO effectively

70%

35%

0%

70%

35%

0%

70%

35%

0%

zVOA: Ensure Smooth Evolution from CS to IMS


Rack 1

Typical Scenario: Multi-tenancy

Blade 1

CSC

F

1

CSC

F

2

CSC

F

3

Opco A Opco B Opco C

Blade 2

CSC

F

3

Blad

e

3

Blad

e

14

… •One IMS system serving for multiple OpCos with the same HW, SW and OS

•High scalability

•Multiple logical instances in one blade

•One logical instance distributed in several blades & racks

Rack 3

Blade 1

MG

CF

1

MG

CF

2

MG

CF

3

Blade 2

CSC

F3

Blad

e

3

Blad

e

14

…

Multi-tenancy sharing one set of IMS coreLower CAPEX, Lower OPEX, Higher Utilization


Typical Scenario: All IMS NEs in one box

E

M

S

/

C

T

S

/

C

G

H

S

S

E

M

S

/

C

T

S

/

C

G

H

S

S

O

M

M

O

M

M

M

G

W

/

M

R

F

P

/

V

I

G

M

G

W

/

M

R

F

P

/

V

I

G

M

G

C

F

/

V

I

G

M

G

C

F

/

V

I

G

M

G

W

/

M

R

F

P

/

V

I

G

S

S

S

/

C

S

C

F

/

A

G

C

F

M

G

W

/

M

R

F

P

/

V

I

G

S

S

S

/

C

S

C

F

/

A

G

C

F

E

T

C

A

Session and Service Control

User Profile

Media Process

O&MCharging

Compact Solution with one frame for all IMS network elements with 50,000 IMS subscribers


Typical Scenario: IMS Pool

P-CSCF1 P-CSCFn

SBC1 SBC2

MGCF1 MGCFn

…

AGCF1 AGCFn

…

HSS/SLF1 HSS/SLF2

…

…

MMTELMMTEL

…

I-CSCF1 I-CSCFn

…

S-CSCF1 S-CSCFn

…

Distributed Architecture

Backup and geographical

Redundancy

High reliability

High scalability

Business continuity

hosting – different approaches

Documents