<?xml version="1.0" encoding="utf-8" standalone="yes"?><html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Capacity Planning</title>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
<meta content="text/css" http-equiv="Content-Style-Type" />
<script src="NED?action=retrieve&amp;identifier=dn00188761&amp;edition=1&amp;language=none&amp;coverage=global&amp;encoding=javascript&amp;component=data&amp;item=data" type="text/javascript" xml:space="preserve">
</script>
<?conversion name="Pub2XHTML" version="2.0" source="urn:mars:dn04111589:1:en:global:publishing_online_1_0:data:data:*:*:*" date="2005-02-15T11:49:27Z"?>
<link href="NED?action=retrieve&amp;identifier=dn01158124&amp;edition=1&amp;language=en&amp;coverage=global&amp;encoding=css&amp;component=data&amp;item=data" rel="stylesheet" title="Nokia Networks default online style" type="text/css" />
<meta content="draft" name="status" />
<?conversion name="SplitHTML" version="1.9" source="urn:mars:dn04111589:1:en:global:publishing_online_1_0:data:data:46:*:*" date="2005-02-15T11:49:27Z"?>
</head>
<body lang="en" xml:lang="en">
<p><a name="feb151134419" shape="rect"></a>
<a name="ned_21" shape="rect"></a></p>

<div class="div">
<div class="div">
<table width="100%">
<tr>
<td align="center" colspan="1" rowspan="1" width="20%"><?NED5 annotation?>
<br clear="none" /><?NED5 printview?>
</td>
<td align="center" colspan="1" rowspan="1" width="20%"></td>
<td align="center" colspan="1" rowspan="1" width="20%"></td>
<td align="center" colspan="1" rowspan="1" width="20%"><a href="NED?action=retrieve&amp;identifier=dn04111589&amp;edition=1&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=ned_20#ned_20" onclick="sync(this);return true" shape="rect">Impact on planning</a></td>
<td align="center" colspan="1" rowspan="1" width="20%"><a href="NED?action=retrieve&amp;identifier=dn04111589_about&amp;edition=1&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=ned_top#ned_top" onclick="openSmallPopup(event,'NED?action=retrieve&amp;identifier=dn04111589_about&amp;edition=1&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=ned_top#ned_top');return false" shape="rect" target="_blank"><img alt="Document information" border="0" class="Metainfo" src="NED?action=retrieve&amp;identifier=dn01158003&amp;edition=1&amp;language=en&amp;coverage=global&amp;encoding=gif&amp;component=data&amp;item=data" /></a></td>
</tr>
</table>


<div class="div">
<h3>Capacity Planning</h3>

<p>The scope of capacity planning process is initially to understand the
variety of users and services (for example, HTTP, WAP, PoC, Streaming and
so on) in the network and its requirements (TRECs). An estimation of the actual
user traffic profile (service mix) will determine the needed BSS resources
to support each user and their service with different TREC.</p>


<p>Therefore every network element in the chain must be investigated and
all the possible capacity bottlenecks should be eliminated.</p>


<p>The following BSS network elements can be analyzed and replanned from
capacity point of view for having the required EQoS functionality:</p>


<ul>
<li><p>Radio (Air interface)</p>
</li>
<li><p>EDAP</p>
</li>
<li><p>PCU</p>
</li>
</ul>


<p>The capacity planning of BSS resources above for EQoS differs from actual
dimensioning process in the increasing importance of knowing the type of services,
user traffic profile and its requirements in terms of throughput, delay, etc
that the network will support.</p>


<p>The following conditions are required, in order to dimension accordingly:</p>


<ol class="type-odd">
<li type="1"><p>Estimation and preparation of traffic profile (the service types
and mix). That includes types of Real Time traffic: audio/video streaming
supported by 3GPP Streaming Class, PoC, and so on as well as Non Real Time
traffic: WAP, web browsing, email, and so on. </p>
</li>
<li type="1"><p>Understand Service requirements: throughput, delay, maximum BLER,
and in general QoS attributes (TRECS) attached to each service/APN.</p>
</li>
<li type="1"><p>Estimate the number of users and their TRECs in a given area</p>
</li>
<li type="1"><p>Understand radio technology available, for example GPRS and EGPRS
and multiplexing effects. If GPRS and EGPRS PSW territories are combined performance
restrictions should be taken into account.</p>
</li>
<li type="1"><p>EQoS capable PCU2 and MS distribution, average MS multislot capability
and type of applications marketed and its penetration in the network. Low
penetration of PCU2 and QoS-aware terminals can reduce the importance of EQoS
planning (the streaming Traffic Class TRECs (TRECs 4-6) can be used only with
QoS-aware terminals, for example Nokia 5140).</p>
</li>
<li type="1"><p>Estimate radio, EDAP and PCU capacity needed to support each
service.</p>
</li>
<li type="1"><p>Reserve enough Default or Dedicated PSW Territory to enable the
service.</p>
</li>
<li type="1"><p>Ensure enough Capacity for CS, since Blocking can be increased
due to PSW services.</p>
</li>
</ol>
</div>
</div>
</div>
</body>
</html>