Anda di halaman 1dari 6

Project Clearwater - IMS in the Cloud

Sizing / Costing Model

A Clearwater deployment comprises four software-based elements, as follows:


Bono - edge proxy (P-CSCF)
Sprout - core proxy (I/S-CSCF an d BGCF) plus TAS
Homestead - subscriber profile database / HSS cache
Homer - XML Document Management Server

Each of these has a certain upper limit of capacity in terms of subscriber population and calli
depending on virtual machine size. For any given virtual machine size, the upper limit of cap
given type of node may be determined by population limit or by call load limit, depending on
assumed calling profile.

The model is based on deployment of Clearwater on Amazon AWS. We have tested upper lim
subscriber population and call load for the various software elements on a selection of differe
machine types (and we have done some extrapolations across VM types). By plugging in the
subscriber population and the call load profile in BHCA per subscriber, and by selecting a virt
type for each of the different software elements, we can estimate the total number of virtual
instances of each type that will be needed , and the cost per year to obtain this capacity.

We also plug in estimates of the signaling bandwidth needed per subscriber per hour since t
bandwidth is into and out of the AWS Cloud (via Bono) and attracts bandwidth charges. Note
estimate of 10kB per hour per subscriber for registration traffic is based on the use of TCP tra
SIP, since this needs much less bandwidth to keep NAT pinholes open than UDP transport an
preferred transport type for Clearwater.

as follows:

riber population and calling load,


ze, the upper limit of capacity of any
load limit, depending on the

We have tested upper limits of


s on a selection of different virtual
ypes). By plugging in the total
er, and by selecting a virtual machine
e total number of virtual machine
obtain this capacity.

bscriber per hour since this


bandwidth charges. Note that the
sed on the use of TCP transport for
n than UDP transport and is the

kSubs total
BHCA/sub
kBHCA total

EC2 instance type


kSubs/instance
kBHCA/instance
instances
reserved upfront cost (3 year)
reserved cost/hour
amortized reserved cost/year
instances cost/year
static bandwidth/sub/hour
call bandwidth/CA
bandwidth/sub/hour
bandwidth/hour
bandwidth/year
amortized bandwidth cost/GB
bandwidth cost/year
total/year
total/sub/year
Node scalability
kSubs/instance
m1.large
m1.medium
m1.small
m1.xlarge
kBHCA/instance
m1.large
m1.medium
m1.small
m1.xlarge

25000
2
50000
bono
m1.medium
110
350
227
$514
$0.02
$372.95
$84,660
10 KB
5 KB
20 KB
500 GB
4.4 PB
$0.062
$270,749
$355,409
$0.0142

sprout
m1.medium
551
500
100
$514
$0.02
$372.95
$37,295

homestead
m1.small
5000
850
59
$257
$0.01
$190.86
$11,261

0 KB
0 GB
0 GB
$0.062
$0
$37,295
$0.0015

0 KB
0 GB
0 GB
$0.062
$0
$11,261
$0.0005

bono

sprout
1103
551
250

homestead
22059
11029
5000
44118
homestead
3400
1700
850
6800

110
50
bono
350
175

sprout
1000
500
250

m1.large
$1,028
$0.046

m1.medium
$514
$0.023

EC2 instance pricing


reserved upfront cost (3 year)
reserved cost/hour
EC2 bandwidth pricing
First/month
Up to/month
Next/month
Next/month
Next/month

1 GB
10.0 TB
40.0 TB
100.0 TB
350.0 TB

cost/GB
$0.00
$0.12
$0.09
$0.07
$0.05

m1.small
$257
$0.012

Drop-down list options

m1.small
m1.medium
m1.large
m1.xlarge

Key:
Model parameters
Node scalability
EC2 costs
homer
m1.small
1250
1150
44
$257
$0.01
$190.86
$8,398

0 KB
0 GB
0 GB
$0.062
$0
$8,398
$0.0003

homer
5515
2757
1250
11029
homer
4600
2300
1150
9200

m1.xlarge
$2,056
$0.092

total

430

$141,614
10 KB
5 KB
20 KB
500 GB
4.4 PB
$270,749
$412,363
$0.016

RAM/GB
7.5
3.75
1.7
15
ECU
4
2
1
8