# 8 CDMA module

# 8.1 Introduction

SEAMCAT allows the simulation of cellular networks employing Code Division Multiple Access modulation scheme. The specific <span><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke">CDMA</span></span></span> standard (e.g. CDMA2000-1X, or <span><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke">W-CDMA</span></span></span>/<span><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke">UMTS</span></span></span>) can be selected by incorporating the appropriate link level curves into the simulation scenario. Only the interference impact of/on "voice" users can be studied using SEAMCAT. The <span>CDMA</span> examples given in this manual are based on 3GPP <span>UMTS</span> specifications.

<span>CDMA</span> and <span><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke">OFDMA</span></span></span> share common panels and calculation. You are invited to consult Section ‎7.5 for the cellular topology, Reference Cell etc.. Section ‎7.6 for the Pathloss and Effective Pathloss definition etc.

# 8.2 CDMA system tab

# Introduction

Whether you want to simulate <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">UL</span></span></span> (uplink) or <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> DL (downlink), you can import from the system library (Figure 186 – (a)), the cellular system you want (Figure 186 – (b)). You can also export the characteristics of your <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> network to the library for later reuse.

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/QJwvSYaCTyelPOys-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/QJwvSYaCTyelPOys-image.png)

**Figure 186: Selection of a <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> cellular network from the system library**

<div class="inline-extension-renderer css-e2q2ep" id="bkmrk--1"><div data-testid="inline-image"></div></div>

# 8.2.1 System

You can name and write some description of the <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> system you want to simulate. It is the same layout as when a generic system is selected.

# 8.2.2 General

You can enter the frequency. The frequency value is overwritten at the “Scenario” tab level.

<div class="fabric-editor-block-mark fabric-editor-alignment align-center" data-align="center" id="bkmrk-%C2%A0table-26%3A-general-s"> **Table 26: General system panel**</div><div class="pm-table-container with-shadow-observer" data-layout="align-start" data-testid="table-container" id="bkmrk-description-symbol-t"><div class="pm-table-wrapper align-center" data-autosize="false" data-layout="align-start" data-number-column="false" data-table-local-id="" data-vc="table-node-wrapper"><div class="sentinel-left"></div><table class=" align-center" data-layout="align-start" data-number-column="false" data-table-width="760" data-testid="renderer-table"><colgroup></colgroup><tbody><tr><td colspan="1" rowspan="1">**Description**

</td><td colspan="1" rowspan="1">**Symbol**

</td><td colspan="1" rowspan="1">**Type**

</td><td colspan="1" rowspan="1">**Unit**

</td><td colspan="1" rowspan="1">**Comments**

</td></tr><tr><td colspan="1" rowspan="1">**Frequency**

</td><td colspan="1" rowspan="1">f

</td><td colspan="1" rowspan="1">Distribution or Scalar

</td><td colspan="1" rowspan="1">MHz

</td><td colspan="1" rowspan="1">Distribution of the centre frequency of the system

</td></tr></tbody></table>

</div></div>  
It is used to define the necessary parameters for the modelling of <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> systems. The <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> interface has been split into 2 tabs.

# 8.3 General settings

# Introduction

The General settings tabsheet contains a range of <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> system parameters as well as some parameters that depend on the modelled direction of <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> link (uplink vs. downlink). 7 panels characterised the <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> system. The below graphic represent the <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">UL</span></span></span> when a victim.

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/9UIrLjcc0CLEgym3-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/9UIrLjcc0CLEgym3-image.png)

**Figure 187: <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> <span data-highlighted="true" data-vc="highlighted-text">UL</span> general settings**

The only differences with <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> DL are the following 2 panels (<span data-highlighted="true" data-vc="highlighted-text">CDMA</span> Downlink and <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> Capacity).

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/E2njdHZXj3zaxYS6-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/E2njdHZXj3zaxYS6-image.png)

**Figure 188: <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> DL general settings difference with <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> <span data-highlighted="true" data-vc="highlighted-text">UL</span>**

# 8.3.1 CDMA general settings

**Table 27: <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> general settings input parameters**

<div class="pm-table-container with-shadow-observer" data-layout="align-start" data-testid="table-container" id="bkmrk-description-symbol-t"><div class="pm-table-wrapper" data-autosize="false" data-layout="align-start" data-number-column="false" data-table-local-id="" data-vc="table-node-wrapper"><div class="sentinel-left"></div><table data-layout="align-start" data-number-column="false" data-table-width="760" data-testid="renderer-table" style="width: 100%;"><colgroup></colgroup><tbody><tr><td colspan="1" rowspan="1" style="width: 12.2736%;">**Description**

</td><td colspan="1" rowspan="1" style="width: 11.4341%;">**Symbol**

</td><td colspan="1" rowspan="1" style="width: 16.3304%;">**Type**

</td><td colspan="1" rowspan="1" style="width: 10.367%;">**Unit**

</td><td colspan="1" rowspan="1" style="width: 49.571%;">**Comments**

</td></tr><tr><td colspan="1" rowspan="1" style="width: 12.2736%;">Receiver Noise Figure

</td><td colspan="1" rowspan="1" style="width: 11.4341%;"></td><td colspan="1" rowspan="1" style="width: 16.3304%;">Scalar

</td><td colspan="1" rowspan="1" style="width: 10.367%;">dB

</td><td colspan="1" rowspan="1" style="width: 49.571%;">Equipment-specific noise figure of receiver. It is used to calculate the noise floor. See Section‎1.2.2

</td></tr><tr><td colspan="1" rowspan="1" style="width: 12.2736%;">Handover margin

</td><td colspan="1" rowspan="1" style="width: 11.4341%;"></td><td colspan="1" rowspan="1" style="width: 16.3304%;">Scalar

</td><td colspan="1" rowspan="1" style="width: 10.367%;">dB

</td><td colspan="1" rowspan="1" style="width: 49.571%;">Specifies the maximum difference between the links in users active list. The actual active-list selection is based on pathloss calculations.

</td></tr><tr><td colspan="1" rowspan="1" style="width: 12.2736%;">Call drop threshold

</td><td colspan="1" rowspan="1" style="width: 11.4341%;"></td><td colspan="1" rowspan="1" style="width: 16.3304%;">Scalar

</td><td colspan="1" rowspan="1" style="width: 10.367%;">dB

</td><td colspan="1" rowspan="1" style="width: 49.571%;">Threshold to determine call drops. It is used by the power control to determine if a user should be dropped when not meeting exact target requirement.

</td></tr><tr><td colspan="1" rowspan="1" style="width: 12.2736%;">Voice bit rate

</td><td colspan="1" rowspan="1" style="width: 11.4341%;"></td><td colspan="1" rowspan="1" style="width: 16.3304%;">Scalar

</td><td colspan="1" rowspan="1" style="width: 10.367%;">kbps

</td><td colspan="1" rowspan="1" style="width: 49.571%;">it is used to calculate the processing gain. See Section ‎8.7.1.

processingGain = 10\*log10(systemBandwidth (MHz) / voiceBitRate (kbps) \* 1000);

</td></tr><tr><td colspan="1" rowspan="1" style="width: 12.2736%;">Reference bandwith

</td><td colspan="1" rowspan="1" style="width: 11.4341%;"></td><td colspan="1" rowspan="1" style="width: 16.3304%;">Scalar

</td><td colspan="1" rowspan="1" style="width: 10.367%;">MHz

</td><td colspan="1" rowspan="1" style="width: 49.571%;">Bandwidth of the system. It is the same for either <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">UL</span></span></span> or DL.

</td></tr><tr><td colspan="1" rowspan="1" style="width: 12.2736%;">Voice activity factor

</td><td colspan="1" rowspan="1" style="width: 11.4341%;">-

</td><td colspan="1" rowspan="1" style="width: 16.3304%;">-

</td><td colspan="1" rowspan="1" style="width: 10.367%;">-

</td><td colspan="1" rowspan="1" style="width: 49.571%;">It is set to 1, i.e. 100% (all voice users that are generated are active). It is not editable.

</td></tr><tr><td colspan="1" rowspan="1" style="width: 12.2736%;">Minimum Coupling Loss

</td><td colspan="1" rowspan="1" style="width: 11.4341%;"></td><td colspan="1" rowspan="1" style="width: 16.3304%;">Scalar

</td><td colspan="1" rowspan="1" style="width: 10.367%;">dB

</td><td colspan="1" rowspan="1" style="width: 49.571%;">The minimum path loss. It is used in the calculation of the effective path loss depicted in section ‎7.6.1

</td></tr><tr><td colspan="1" rowspan="1" style="width: 12.2736%;">Link Level Data

</td><td colspan="1" rowspan="1" style="width: 11.4341%;"></td><td colspan="1" rowspan="1" style="width: 16.3304%;">Function (X,Y)

</td><td colspan="1" rowspan="1" style="width: 10.367%;"></td><td colspan="1" rowspan="1" style="width: 49.571%;">Drop-down selection of Link level data look-up functions from Library. It is user's responsibility to choose an appropriate set of data. See Section ‎8.5 for further details

</td></tr></tbody></table>

<div class="sentinel-right">  
</div></div><div class="pm-table-sticky-scrollbar-container-view-page" data-vc="table-sticky-scrollbar-container"><div>  
</div></div><div class="pm-table-sticky-scrollbar-sentinel-bottom" data-testid="sticky-scrollbar-sentinel-bottom">  
</div></div>

# 8.3.2 Local environment

You can choose the suitable indoor and outdoor ratio for the mobile station to be used by the propagation model. Further details are presented in Section ‎5.4.3.

# 8.3.3 Receiver settings

This content of this panel depends whether <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> system is a victim or an interfering system. If the <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> is a victim, you will have to set the blocking mask. It is a shared interface with <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">OFDMA</span></span></span>.

![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/KuY35UthFocAVrfe-image.png)

**Figure 192: Cellular panel receiver settings**

**Table 27: Receiver settings of a cellular system**

<div class="pm-table-container with-shadow-observer" data-layout="align-start" data-testid="table-container" id="bkmrk-description-symbol-t"><div class="pm-table-wrapper" data-autosize="false" data-layout="align-start" data-number-column="false" data-table-local-id="" data-vc="table-node-wrapper"><table data-layout="align-start" data-number-column="false" data-table-width="760" data-testid="renderer-table" style="width: 100%;"><colgroup></colgroup><tbody><tr><td colspan="1" rowspan="1" style="width: 21.8065%;">**Description**

</td><td colspan="1" rowspan="1" style="width: 9.41373%;">**Symbol**

</td><td colspan="1" rowspan="1" style="width: 9.89128%;">**Type**

</td><td colspan="1" rowspan="1" style="width: 5.59966%;">**Unit**

</td><td colspan="1" rowspan="1" style="width: 53.265%;">**Comments**

</td></tr><tr><td colspan="1" rowspan="1" style="width: 21.8065%;">**Blocking mask/<span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">ACS</span></span></span>**: Receiver frequency response (receiver blocking performance)

</td><td colspan="1" rowspan="1" style="width: 9.41373%;">*blocking*

</td><td colspan="1" rowspan="1" style="width: 9.89128%;">Function (X,Y)

(MHz)

</td><td colspan="1" rowspan="1" style="width: 5.59966%;">dB

</td><td colspan="1" rowspan="1" style="width: 53.265%;">It is similar to the blocking response depicted in Figure 12 except that it is to be set as user defined mode only.

In case that the blocking mask is defined with negative values, the parameters Standard desensitization and I/N\_target (described below) are used to compute the blocking mask used in the simulations. See section [A9.1](https://wiki.cept.org/display/SH/A9.1+BLOCKING+LEVELS+IN+3GPP+AND+ETSI+SPECIFICATIONS "https://wiki.cept.org/display/SH/A9.1+BLOCKING+LEVELS+IN+3GPP+AND+ETSI+SPECIFICATIONS") (and subsections A9.1.1 to A9.1.3) for the equations

</td></tr><tr><td colspan="1" rowspan="1" style="width: 21.8065%;">**Standard desensitization**

</td><td colspan="1" rowspan="1" style="width: 9.41373%;"></td><td colspan="1" rowspan="1" style="width: 9.89128%;"></td><td colspan="1" rowspan="1" style="width: 5.59966%;">dB

</td><td colspan="1" rowspan="1" style="width: 53.265%;">It is value of desensitization of the receiver as defined in the standards.

</td></tr><tr><td colspan="1" rowspan="1" style="width: 21.8065%;">**Target I/N**

</td><td colspan="1" rowspan="1" style="width: 9.41373%;"></td><td colspan="1" rowspan="1" style="width: 9.89128%;"></td><td colspan="1" rowspan="1" style="width: 5.59966%;">dB

</td><td colspan="1" rowspan="1" style="width: 53.265%;">It is the protection criteria used for the simulation.

</td></tr></tbody></table>

<div class="sentinel-right">  
</div></div><div class="pm-table-sticky-scrollbar-container-view-page" data-vc="table-sticky-scrollbar-container"><div>  
</div></div><div class="pm-table-sticky-scrollbar-sentinel-bottom" data-testid="sticky-scrollbar-sentinel-bottom">  
</div></div>

# 8.3.4 Transmitter settings

This content of this panel depends whether <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> system is a victim or an interfering system. If the <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> is an interferer, you will have to set the spectrum emission mask and the emissions floor. It is a shared interface with <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">OFDMA</span></span></span>.

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/HgwUNPb5KsLn8REr-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/HgwUNPb5KsLn8REr-image.png)**Figure 190: Cellular panel transmitter settings**

When defining the Emission Mask (not as BEM) the units of the user defined mask are: Offset (MHz); Mask Values (dBc); Reference Bandwidth (kHz).

When defining the Emission mask as a Block Edge Mask (BEM), SEAMCAT sets to 0 dBi the peak gain of the transmitter antenna and uses the power entries of the Mask as e.i.r.p (already including the gain of the antenna). So, if the Emission mask is defiend as BEM, the units of the user defined mask are: Offset (MHz); Mask Values (dBm e.i.r.p.); Reference Bandwidth (kHz).

# 8.3.5 CDMA uplink

This is only available if <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">UL</span></span></span> selected.

<div class="_19itglyw _vchhusvi _r06hglyw" data-testid="view-page-main-content-container" data-vc="view-page-main-content-container" id="bkmrk-table-29%3A%C2%A0cdma-ul-in"><div class="highlighter-context page view" data-inline-comments-target="true" data-testid="page-content-only"><div class="_19itglyw _vchhusvi _r06hglyw _19pkidpf _2hwx1wug _otyr1epz _18u01wug _1bsb1osq"><div class="wiki-content css-th923b e5xcnr80" data-test-appearance="max" data-testid="pageContentRendererTestId" data-vc="pageContentRendererTestId"><div class="renderer-overrides"><div class="css-3qfej8"><div class="ak-renderer-wrapper is-max css-pw7jst"><div class="css-1aarbqj" role="none"><div class="ak-renderer-document"><div class="fabric-editor-block-mark fabric-editor-alignment align-center" data-align="center">**Table 29: <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> <span data-highlighted="true" data-vc="highlighted-text">UL</span> input parameters for the power control**</div></div></div></div></div></div></div></div></div></div><div class="_19itglyw _vchhusvi _r06hglyw" data-testid="view-page-main-content-container" data-vc="view-page-main-content-container" id="bkmrk-description-symbol-t"><div class="highlighter-context page view" data-inline-comments-target="true" data-testid="page-content-only"><div class="_19itglyw _vchhusvi _r06hglyw _19pkidpf _2hwx1wug _otyr1epz _18u01wug _1bsb1osq"><div><div class="wiki-content css-th923b e5xcnr80" data-test-appearance="max" data-testid="pageContentRendererTestId" data-vc="pageContentRendererTestId"><div class="renderer-overrides"><div class="css-3qfej8"><div class="ak-renderer-wrapper is-max css-pw7jst"><div class="css-1aarbqj" role="none"><div class="ak-renderer-document"><div class="pm-table-container with-shadow-observer" data-layout="custom" data-testid="table-container"><div class="pm-table-wrapper" data-autosize="false" data-layout="align-start" data-number-column="false" data-table-local-id="" data-table-width="4000" data-vc="table-node-wrapper"><div class="sentinel-left"></div><table data-layout="align-start" data-number-column="false" data-table-width="4000" data-testid="renderer-table" style="width: 100%;"><colgroup><col style="width: 15.3718%;"></col><col style="width: 12.9808%;"></col><col style="width: 14.307%;"></col><col style="width: 10.367%;"></col><col style="width: 46.9495%;"></col></colgroup><tbody><tr><td colspan="1" data-colwidth="333.4" rowspan="1">**Description**

</td><td colspan="1" data-colwidth="197.69" rowspan="1">**Symbol**

</td><td colspan="1" data-colwidth="199.37" rowspan="1">**Type**

</td><td colspan="1" data-colwidth="130.68" rowspan="1">**Unit**

</td><td colspan="1" data-colwidth="3141.3" rowspan="1">**Comments**

</td></tr><tr><td colspan="1" data-colwidth="333.4" rowspan="1">Target network noise rise

</td><td colspan="1" data-colwidth="197.69" rowspan="1"></td><td colspan="1" data-colwidth="199.37" rowspan="1">Scalar

</td><td colspan="1" data-colwidth="130.68" rowspan="1">dB

</td><td colspan="1" data-colwidth="3141.3" rowspan="1">Specific level of noise that the network is willing to handle, when this level is reached it starts removing UEs to reduce its noise level

</td></tr><tr><td colspan="1" data-colwidth="333.4" rowspan="1">cell noise rise selection

</td><td colspan="1" data-colwidth="197.69" rowspan="1"></td><td colspan="1" data-colwidth="199.37" rowspan="1">Boolean

</td><td colspan="1" data-colwidth="130.68" rowspan="1">-

</td><td colspan="1" data-colwidth="3141.3" rowspan="1">Select the algorithm that allow the cell selection based on a noise rise increased. If selected, then the measure of the noise rise per each cell is considered and the algorithm, recursively, tries to identify the number of affected cells due to a single source/cluster of interferers and remove users.

If not selected, then the measure of the noise rise over the whole network is considered

(See Section ‎8.7.6 for details)

</td></tr><tr><td colspan="1" data-colwidth="333.4" rowspan="1">Target cell noise rise

</td><td colspan="1" data-colwidth="197.69" rowspan="1"></td><td colspan="1" data-colwidth="199.37" rowspan="1">Scalar

</td><td colspan="1" data-colwidth="130.68" rowspan="1">dB

</td><td colspan="1" data-colwidth="3141.3" rowspan="1">Only available when Cell noise rise selection is active. It is set to 0.1 dB by default.

The “cell noise rise” algorithm will assess whether to drop users from any cell in which the noise rise exceeds the threshold indicated above. The default value of 0.1 dB has been chosen to ensure that the analysis does not disregard any cases of interfered cells, since users may also be dropped as the consequence of a low noise rise.

</td></tr><tr><td colspan="1" data-colwidth="333.4" rowspan="1">MS maximum transmit power

</td><td colspan="1" data-colwidth="197.69" rowspan="1"></td><td colspan="1" data-colwidth="199.37" rowspan="1">Scalar

</td><td colspan="1" data-colwidth="130.68" rowspan="1">dB

</td><td colspan="1" data-colwidth="3141.3" rowspan="1">Maximum transmit power of the MS (i.e. the <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">UE</span></span></span>)

</td></tr><tr><td colspan="1" data-colwidth="333.4" rowspan="1">MS power control range

</td><td colspan="1" data-colwidth="197.69" rowspan="1"></td><td colspan="1" data-colwidth="199.37" rowspan="1">Scalar

</td><td colspan="1" data-colwidth="130.68" rowspan="1">dB

</td><td colspan="1" data-colwidth="3141.3" rowspan="1">Span of the fluctuation of the power

</td></tr><tr><td colspan="1" data-colwidth="333.4" rowspan="1">PC convergence precision

</td><td colspan="1" data-colwidth="197.69" rowspan="1"></td><td colspan="1" data-colwidth="199.37" rowspan="1">Scalar

</td><td colspan="1" data-colwidth="130.68" rowspan="1">dB

</td><td colspan="1" data-colwidth="3141.3" rowspan="1">In the uplink, each mobile station perfectly achieves the target C/I, Eb/N0\_target, during the power control loop convergence, assuming that the maximum transmit (TX) power, max\_MS\_Tx\_Pw, is not exceeded. Those mobile stations not able to achieve Eb/N0\_target after convergence of the power control loop are considered in outage (i.e. they are dropped). The power control loop is considered to converge when all mobile stations are within the max\_MS\_Tx\_Pw and their Tx power is adjusted by less than the “PC convergence precision” value for the last power balancing iteration.

</td></tr></tbody></table>

</div></div></div></div></div></div></div></div></div></div></div></div>

# 8.3.6 CDMA downlink

This panel is available only if <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> DL selected.

<div class="fabric-editor-block-mark fabric-editor-alignment align-center" data-align="center" id="bkmrk-table-30%3A%C2%A0cdma-dl-in">**Table 30: <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> DL input parameters for the power control**</div><div class="pm-table-container with-shadow-observer" data-layout="align-start" data-testid="table-container" id="bkmrk-description-symbol-t"><div class="pm-table-wrapper" data-autosize="false" data-layout="align-start" data-number-column="false" data-table-local-id="" data-vc="table-node-wrapper"><div class="sentinel-left"></div><table data-layout="align-start" data-number-column="false" data-table-width="760" data-testid="renderer-table" style="width: 100%;"><colgroup></colgroup><tbody><tr><td colspan="1" rowspan="1" style="width: 14.1802%;">**Description**

</td><td colspan="1" rowspan="1" style="width: 15.2464%;">**Symbol**

</td><td colspan="1" rowspan="1" style="width: 11.3265%;">**Type**

</td><td colspan="1" rowspan="1" style="width: 7.62631%;">**Unit**

</td><td colspan="1" rowspan="1" style="width: 51.5968%;">**Comments**

</td></tr><tr><td colspan="1" rowspan="1" style="width: 14.1802%;">Success threshold

</td><td colspan="1" rowspan="1" style="width: 15.2464%;"></td><td colspan="1" rowspan="1" style="width: 11.3265%;">Scalar

</td><td colspan="1" rowspan="1" style="width: 7.62631%;">dB

</td><td colspan="1" rowspan="1" style="width: 51.5968%;">Threshold to determine perfect link quality.

</td></tr><tr><td colspan="1" rowspan="1" style="width: 14.1802%;">Base Station Pilot Channel Fraction

</td><td colspan="1" rowspan="1" style="width: 15.2464%;">*pilot\_frac*

</td><td colspan="1" rowspan="1" style="width: 11.3265%;">Scalar

</td><td colspan="1" rowspan="1" style="width: 7.62631%;">-

</td><td colspan="1" rowspan="1" style="width: 51.5968%;">Fraction of max <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">BS</span></span></span> power allocated to pilot.

</td></tr><tr><td colspan="1" rowspan="1" style="width: 14.1802%;">Base Station Overhead Channel Fraction

</td><td colspan="1" rowspan="1" style="width: 15.2464%;">*Overhead\_frac*

</td><td colspan="1" rowspan="1" style="width: 11.3265%;">Scalar

</td><td colspan="1" rowspan="1" style="width: 7.62631%;">-

</td><td colspan="1" rowspan="1" style="width: 51.5968%;">Fraction of max <span data-highlighted="true" data-vc="highlighted-text">BS</span> power allocated to overhead channels (paging, etc.).

</td></tr><tr><td colspan="1" rowspan="1" style="width: 14.1802%;">Base Station maximum Broadcast Power

</td><td colspan="1" rowspan="1" style="width: 15.2464%;"></td><td colspan="1" rowspan="1" style="width: 11.3265%;">Scalar

</td><td colspan="1" rowspan="1" style="width: 7.62631%;">dBm

</td><td colspan="1" rowspan="1" style="width: 51.5968%;">maximum Broadcast Power

</td></tr><tr><td colspan="1" rowspan="1" style="width: 14.1802%;">Base Station maximum traffic channel fraction

</td><td colspan="1" rowspan="1" style="width: 15.2464%;"></td><td colspan="1" rowspan="1" style="width: 11.3265%;">Scalar

</td><td colspan="1" rowspan="1" style="width: 7.62631%;">-

</td><td colspan="1" rowspan="1" style="width: 51.5968%;">Fraction of the maximum allowable broadcast power (per traff. chan. per <span data-highlighted="true" data-vc="highlighted-text">BS</span>). The maximum allowable traffic channel power is compared to the calculated transmit traffic channel power levels with respect to the Ec/Ior link level data for iterative adjustment in the DL power control.

</td></tr></tbody></table>

<div class="sentinel-right">  
</div></div><div class="pm-table-sticky-scrollbar-container-view-page" data-vc="table-sticky-scrollbar-container"><div>  
</div></div><div class="pm-table-sticky-scrollbar-sentinel-bottom" data-testid="sticky-scrollbar-sentinel-bottom">  
</div></div>

# 8.3.7 CDMA capacity

The capacity of the simulated system (i.e. how many mobiles per cell should be generated in the system) is dependent on all other settings and cannot always be easily deducted from these. Therefore SEAMCAT has a feature that allows for automatic determination of capacity. This is also known as simulation of non interfered capacity and is enabled by default.

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/zD1ahF4x9qbmXvAr-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/zD1ahF4x9qbmXvAr-image.png)

<div class="rich-media-item mediaSingleView-content-wrap image-align-start css-1kosvjs" data-layout="align-start" data-media-vc-wrapper="true" data-node-type="mediaSingle" data-renderer-start-pos="364" data-vc="media-single" data-width="362" data-width-type="pixel" id="bkmrk-figure-191%3A-cdma-ul-"><div class="css-168wdgl"><div data-alt="" data-collection="contentId-493153" data-context-id="493153" data-file-mime-type="" data-file-name="file" data-file-size="1" data-height="176" data-id="db8cf948-04d4-447b-8085-6b4d02d84076" data-node-type="media" data-renderer-start-pos="365" data-type="file" data-width="362"><div class="_2rko18qm _vchhusvi _kqswh2mm _ect4ttxp _p12f1osq _c71l1osq _1bsb1qmm _4t3ine4n _1hlmd0i9 _1rquusvi _eg541i5c _mts3kb7n _1ntskb7n _yfmhtlke _5sb1v00u new-file-experience-wrapper" data-media-vc-wrapper="true" data-testid="media-card-view" id="bkmrk-figure-191%3A-cdma-ul--1"><div class="_1reo15vq _18m915vq _2rko18qm _1e0c1txw _kqswh2mm _p12f1osq _1bsb1osq _4t3i1osq _c71l1osq media-file-card-view" data-cursor="pointer" data-test-media-name="91.png" data-test-progress="1" data-test-source="remote" data-test-status="complete" data-testid="media-file-card-view"><div class="_kqswstnw _1bsb1osq _4t3i1osq _1e0c1txw _2lx21bp4 _1bah1h6o _4cvr1h6o align-center" data-testid="ImageRendererWrapper">![](blob:https://ecowiki.atlassian.net/ba090b70-4b9c-41bb-91f3-958cfceade3b#media-blob-url=true&id=db8cf948-04d4-447b-8085-6b4d02d84076&collection=contentId-493153&contextId=493153&width=362&height=176&alt=&clientId=113268fe-fe5b-4bc3-8ff3-07965dbf1d18)**Figure 191: <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">UL</span></span></span> system - Determination of the optimum number of UEs (<span data-highlighted="true" data-vc="highlighted-text">CDMA</span> capacity)**</div></div></div></div></div></div>In <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> <span data-highlighted="true" data-vc="highlighted-text">UL</span>, the number of optimised users is being re-calculated for each event. It is recommended to run the "simulate non-interfered capacity" so that SEAMCAT can provide a "best" optimised value, this will optimise the computation time afterwards. If you are using another number you risk to create an overhead in your computation time without any change in the output results.

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/2fSVygXti2KT2HbI-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/2fSVygXti2KT2HbI-image.png)

<div class="rich-media-item mediaSingleView-content-wrap image-align-start css-1qmaqo0" data-layout="align-start" data-media-vc-wrapper="true" data-node-type="mediaSingle" data-renderer-start-pos="839" data-vc="media-single" data-width="361" data-width-type="pixel" id="bkmrk-figure-192%3A-cdma-dl-"><div class="css-19kvp28"><div data-alt="" data-collection="contentId-493153" data-context-id="493153" data-file-mime-type="" data-file-name="file" data-file-size="1" data-height="43" data-id="9359e740-f5f6-4c74-8d53-39f20563b493" data-node-type="media" data-renderer-start-pos="840" data-type="file" data-width="361"><div class="_2rko18qm _vchhusvi _kqswh2mm _ect4ttxp _p12f1osq _c71l1osq _1bsb1qmm _4t3ine4n _1hlmd0i9 _1rquusvi _eg541i5c _mts3kb7n _1ntskb7n _yfmhtlke _5sb1v00u new-file-experience-wrapper" data-media-vc-wrapper="true" data-testid="media-card-view" id="bkmrk-figure-192%3A-cdma-dl--1"><div class="_1reo15vq _18m915vq _2rko18qm _1e0c1txw _kqswh2mm _p12f1osq _1bsb1osq _4t3i1osq _c71l1osq media-file-card-view" data-cursor="pointer" data-test-media-name="92.png" data-test-progress="1" data-test-source="remote" data-test-status="complete" data-testid="media-file-card-view"><div class="_kqswstnw _1bsb1osq _4t3i1osq _1e0c1txw _2lx21bp4 _1bah1h6o _4cvr1h6o align-center" data-testid="ImageRendererWrapper">![](blob:https://ecowiki.atlassian.net/6eb65f82-ce82-4d17-921c-bf154de12850#media-blob-url=true&id=9359e740-f5f6-4c74-8d53-39f20563b493&collection=contentId-493153&contextId=493153&width=361&height=43&alt=&clientId=113268fe-fe5b-4bc3-8ff3-07965dbf1d18)**Figure 192: <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> DL system - Determination of the optimum number of UEs (<span data-highlighted="true" data-vc="highlighted-text">CDMA</span> capacity)**</div></div></div></div></div></div><div class="fabric-editor-block-mark fabric-editor-alignment align-center" data-align="center" id="bkmrk-table-31%3A-cdma-capac"><div class="inline-extension-renderer css-e2q2ep"><span class="css-6k4g17">  
</span></div>**Table 31: <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> Capacity settings parameters (<span data-highlighted="true" data-vc="highlighted-text">UL</span> and DL)**</div><table data-layout="align-start" data-number-column="false" data-table-width="2726.52" data-testid="renderer-table" id="bkmrk-description-symbol-t" style="width: 100%;"><tbody><tr><td colspan="1" data-colwidth="269.82" rowspan="1" style="width: 16.4442%;">**Description**

</td><td colspan="1" data-colwidth="197.76" rowspan="1" style="width: 8.69876%;">**Symbol**

</td><td colspan="1" data-colwidth="199.43" rowspan="1" style="width: 11.4395%;">**Type**

</td><td colspan="1" data-colwidth="130.72" rowspan="1" style="width: 6.43924%;">**Unit**

</td><td colspan="1" data-colwidth="1930.64" rowspan="1" style="width: 56.9545%;">**Comments**

</td></tr><tr><td colspan="1" data-colwidth="269.82" rowspan="1" style="width: 16.4442%;">Simulate non interfered capacity

</td><td colspan="1" data-colwidth="197.76" rowspan="1" style="width: 8.69876%;">*-*

</td><td colspan="1" data-colwidth="199.43" rowspan="1" style="width: 11.4395%;">Boolean

</td><td colspan="1" data-colwidth="130.72" rowspan="1" style="width: 6.43924%;">-

</td><td colspan="1" data-colwidth="1930.64" rowspan="1" style="width: 56.9545%;">Toggles automatic capacity finding. If the option **Simulate non-interfered capacity** is checked, then the system will automatically simulate the 'optimal' number of the mobiles for given system configuration (type of system, bandwidth, cell sizes, etc). The optimum finding algorithm is developed to establish the loading that would correspond to approx. 80% of maximum system capacity. If this option is unchecked, you are free to set a constant user-defined average number of mobile users per cell especially if the optimal capacity for the current scenario is known (this is often the case when running consecutive simulations with the same system) there is no need to simulate – as the simulation process can be quite lengthy. When this checkbox is disabled SEAMCAT uses the value entered in 2 – “Users per cell” as the capacity per cell.

</td></tr><tr><td colspan="1" data-colwidth="269.82" rowspan="1" style="width: 16.4442%;">Init users per cell

</td><td colspan="1" data-colwidth="197.76" rowspan="1" style="width: 8.69876%;">*-*

</td><td colspan="1" data-colwidth="199.43" rowspan="1" style="width: 11.4395%;">Scalar

</td><td colspan="1" data-colwidth="130.72" rowspan="1" style="width: 6.43924%;">-

</td><td colspan="1" data-colwidth="1930.64" rowspan="1" style="width: 56.9545%;">If capacity simulation is enabled this indicates the starting point of the simulation. Selecting the right starting point can speed up the capacity finding. If capacity simulation is disabled the value in this field is the actual value used by SEAMCAT.

SEAMCAT does NOT change this input value into the result of the simulation!

Users per cell is equal to <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">UE</span></span></span> per Base Station. SEAMCAT consider each Base station as its own cell.

</td></tr><tr><td colspan="1" data-colwidth="269.82" rowspan="1" style="width: 16.4442%;">Delta users per cell

</td><td colspan="1" data-colwidth="197.76" rowspan="1" style="width: 8.69876%;"></td><td colspan="1" data-colwidth="199.43" rowspan="1" style="width: 11.4395%;">Scalar

</td><td colspan="1" data-colwidth="130.72" rowspan="1" style="width: 6.43924%;">-

</td><td colspan="1" data-colwidth="1930.64" rowspan="1" style="width: 56.9545%;">When SEAMCAT tries to find the optimal capacity it adjust the number of UEs per cell starting with this value. A proper value here can speed up capacity finding.

</td></tr><tr><td colspan="1" data-colwidth="269.82" rowspan="1" style="width: 16.4442%;">Number of trials

</td><td colspan="1" data-colwidth="197.76" rowspan="1" style="width: 8.69876%;"></td><td colspan="1" data-colwidth="199.43" rowspan="1" style="width: 11.4395%;">Scalar

</td><td colspan="1" data-colwidth="130.72" rowspan="1" style="width: 6.43924%;">-

</td><td colspan="1" data-colwidth="1930.64" rowspan="1" style="width: 56.9545%;">When finding the optimal capacity SEAMCAT runs this (i.e. Number of trials) many snapshots of every value of UEs per cell before deciding whether or not the current value is the optimal capacity. Generally larger numbers mean greater precision but also longer time needed by the algorithm.

</td></tr><tr><td colspan="1" data-colwidth="269.82" rowspan="1" style="width: 16.4442%;">Target noise rise precision

</td><td colspan="1" data-colwidth="197.76" rowspan="1" style="width: 8.69876%;"></td><td colspan="1" data-colwidth="199.43" rowspan="1" style="width: 11.4395%;">Scalar

</td><td colspan="1" data-colwidth="130.72" rowspan="1" style="width: 6.43924%;">dB

</td><td colspan="1" data-colwidth="1930.64" rowspan="1" style="width: 56.9545%;">**Uplink only** – the precision used when comparing the noise rise of the filled system with target noise rise set under the “<span data-highlighted="true" data-vc="highlighted-text">CDMA</span> Uplink” panel

</td></tr><tr><td colspan="1" data-colwidth="269.82" rowspan="1" style="width: 16.4442%;">Tolerance of initial outage

</td><td colspan="1" data-colwidth="197.76" rowspan="1" style="width: 8.69876%;"></td><td colspan="1" data-colwidth="199.43" rowspan="1" style="width: 11.4395%;">Scalar

</td><td colspan="1" data-colwidth="130.72" rowspan="1" style="width: 6.43924%;">%

</td><td colspan="1" data-colwidth="1930.64" rowspan="1" style="width: 56.9545%;">**Downlink only** – The tolerance of initial outage is the percentage of UEs that can be dropped before SEAMCAT determines that the tested number of UEs cannot fit into the system (i.e. 20 user\_per\_cell \* 19 <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">BS</span></span></span> = 380 UEs, if 5% or less of 380 UEs are dropped, the system is considered able to handle/service 20 UEs per cell). SEAMCAT will adjust the value of UEs per cell untill a value is found which in 80% of the specified number of trials is able to handle the tested number of UEs per cell.This parameter allows for UEs in “extreme” pathloss situations to be “ignored” from the optimal capacity finding.

</td></tr></tbody></table>

# 8.3.8 Propagation Model

You can choose the suitable propagation model to be applied when calculating signal loss along the transmitter and the receiver path. A choice and settings of propagation models are presented in ‎ANNEX 17:.

# 8.4 Positioning

See section ‎7.5, common to <span><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke">CDMA</span></span></span> and <span><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke">OFDMA</span></span></span> on the positioning of BSs and MSs.

# 8.5 CDMA Link level data

# 8.5.1 CDMA link level system mapping

Power control is a crucial mechanism in <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> mobile radio networks, which needs to be modeled in SEAMCAT. It is a complex process involving various layers of signaling, measurement and modulation/demodulation procedures. It is not feasible to model signaling, link and chip level details of <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> power control in network level simulations performed by SEAMCAT due to the complexity and CPU time constraints. Hence, it is necessary to adopt the two-step approach employed widely in the industry for the simulation of <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> based systems.

The first step utilizes link level simulations that model fast fading channels, power control procedures and actual chip level algorithms to generate outputs that map channel power requirements to link quality (e.g. frame erasure rate, FER). Such simulations involve the knowledge of intricate details of the <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> signaling procedures and modulation/demodulation methods.

Major <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> vendors develop link level simulations and contribute their results to the standard bodies. Since the link level results are independent of most system level variations (cell sizes, amplifier ratings, antenna types, etc.), they are applicable to a wide variety of network configurations. The second step in the simulation of <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> involves system level simulations that actually model the <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> network on a macro scale. Since the required channel power vs. link performance data is available from the link level results, transmit power levels for <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> channels can be calculated and utilized in the system level modelling of a <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> network.

The approach described above enables the reuse of link level data to model various network configurations. Furthermore, through the use of the link level data, an accurate power control model is implicitly included in the system level simulations that run at moderate complexity.

The built-in <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> Link level Data used in DL and <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">UL</span></span></span> can be found in Section ‎13.4.6. SEAMCAT allows you to load your own library too.

# 8.5.2 CDMA DL Power Control Methodology (VOICE ONLY)

Figure 193 presents the dependency between the condition of a user in the network (the so called geometry), mobile speed and soft handover state of the <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">UE</span></span></span> that are needed to map a particular link quality to the channel power requirement.

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/jnFOKHkyatSTdyAf-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/jnFOKHkyatSTdyAf-image.png)

<div class="rich-media-item mediaSingleView-content-wrap image-align-start css-nba9nh" data-layout="align-start" data-media-vc-wrapper="true" data-node-type="mediaSingle" data-renderer-start-pos="241" data-vc="media-single" data-width="730" data-width-type="pixel" id="bkmrk-figure-193%3A-power-co"><div class="css-ej9os6"><div data-alt="" data-collection="contentId-493217" data-context-id="493217" data-file-mime-type="" data-file-name="file" data-file-size="1" data-height="235" data-id="21c3bbf6-e960-49d5-92b5-00ed31f6816f" data-node-type="media" data-renderer-start-pos="242" data-type="file" data-width="730"><div class="_2rko18qm _vchhusvi _kqswh2mm _ect4ttxp _p12f1osq _c71l1osq _1bsb1qmm _4t3ine4n _1hlmd0i9 _1rquusvi _eg541i5c _mts3kb7n _1ntskb7n _yfmhtlke _5sb1v00u new-file-experience-wrapper" data-media-vc-wrapper="true" data-testid="media-card-view" id="bkmrk-figure-193%3A-power-co-1"><div class="_1reo15vq _18m915vq _2rko18qm _1e0c1txw _kqswh2mm _p12f1osq _1bsb1osq _4t3i1osq _c71l1osq media-file-card-view" data-cursor="pointer" data-test-media-name="93.png" data-test-progress="1" data-test-source="remote" data-test-status="complete" data-testid="media-file-card-view"><div class="_kqswstnw _1bsb1osq _4t3i1osq _1e0c1txw _2lx21bp4 _1bah1h6o _4cvr1h6o align-center" data-testid="ImageRendererWrapper">![](blob:https://ecowiki.atlassian.net/9edd11b7-8a7d-4cf2-88dd-47386888d284#media-blob-url=true&id=21c3bbf6-e960-49d5-92b5-00ed31f6816f&collection=contentId-493217&contextId=493217&width=730&height=235&alt=&clientId=113268fe-fe5b-4bc3-8ff3-07965dbf1d18)**Figure 193: Power Control Module (high level)**</div></div></div></div></div></div>All these factors determine the appropriate mapping of a particular link quality to the channel power requirement. For example, stationary users may require less power than moving users to attain the same link quality. Similarly, users connected to several <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">BS</span></span></span>’s at the same time (soft handover) may require less power than users connected to a single <span data-highlighted="true" data-vc="highlighted-text">BS</span> to achieve the same link quality. Furthermore, users in favorable locations (high geometry) may again require less power than users that are in unfavorable locations (low geometry). Hence, link level data includes different mappings (look up tables) between link quality and required power for different mobile speeds, geometries and soft handover states. Furthermore, in order to remove the dependency on the total <span data-highlighted="true" data-vc="highlighted-text">BS</span> power (may vary from system to system), the power requirements are reported as normalized power fractions (fraction of the total <span data-highlighted="true" data-vc="highlighted-text">BS</span> power).

Consequently, the link level data is used in modelling power control in a variety of conditions such as different mobile speeds, geometrical user distributions, soft handover characteristics and amplifier output power ratings. In <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> Downlink, the link level is a function of Ec/Ior.

# 8.5.3 CDMA uplink Power Control Methodology in SEAMCAT (VOICE ONLY)

Performance characteristics of individual links to be used in the power control module of SEAMCAT are generated a priori from link level simulations. This usually includes several mappings between requested link quality (e.g. block error rate, <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">BLER</span></span></span>) and required transmit power of mobile stations/base stations. For generating such mappings in form of “look up tables”, link level simulations involve multipath fading, physical layer transceiver algorithms, e.g. modulation/demodulation and coding/decoding, as well as power control procedures. Different mulipath fading channels (e.g. the <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">ITU</span></span></span> channel models) are used to model various configurations, e.g. indoor, outdoor, pedestrian, vehicular, etc.

In <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">UL</span></span></span>, the sum of received C/I values in two sectors should meet the C/I requirements specified by the link level simulation data. In <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> Uplink, the link level is a function of Eb/No.

# 8.6 CDMA Downlink - simulation algorithm

# 8.6.1 Simulation Methodology

The main goal of the downlink power control in SEAMCAT is to calculate the total <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">BS</span></span></span> output power and the success rate (% of calls with no link quality degradation) for a given snapshot of the system. <span data-highlighted="true" data-vc="highlighted-text">BS</span> output power is a key parameter in the scenarios where <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> is the interferer. Success rate, on the other hand, is crucial in <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> victim scenarios. One possible way to analyze the impact of other system interference on <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> is to compare the success rates in the presence and absence of external interference.

A snapshot of the mutually existing systems is modeled at each event generation in SEAMCAT. Hence, at each event generation the power control algorithm should also be run for the <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> cell, whether it is the victim or the interferer. This is illustrated in Figure 194. The setup block is inherited from the higher layers of SEAMCAT and consists of initializing the system parameters. The next step involves the generation of traffic for power control, calculation of appropriate path losses within the <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> cell layout and determination of soft handover states. Power control is then performed by utilizing the link level data via an iterative process. Finally, necessary outputs are generated and fed into the interference calculation modules in SEAMCAT.

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/YP7nS30VpVbHEcRd-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/YP7nS30VpVbHEcRd-image.png)

**Figure 194: DL Power Control Simulation Methodology – Overview**

For simplicity, the <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> downlink power control methodology is described for omni-cells. However, extension to multi-sector cells is straightforward. In a multi-sector configuration, each sector should be treated in the same way a cell is treated in the omni configuration.

# 8.6.2 Traffic Generation

While the <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">BS</span></span></span> output power and the outage ratio is likely to be calculated for a single <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> cell, accurate modelling of power control requires the consideration of inner-system interference generated by the surrounding tiers of <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> cells. The significance of other cell interference in <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> requires that at least two tiers surrounding the cell of interest be considered. However, <span data-highlighted="true" data-vc="highlighted-text">BS</span> power and outage statistics will only be collected from the center cell, which has the most accurate interference background (two surrounding tiers). Cells surrounding the center cell will not be visible to the higher levels of SEAMCAT and will only be used to generate the inner-system other-cell interference background for the center cell (Figure 195).

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/AVpV5tB0J1kqIROC-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/AVpV5tB0J1kqIROC-image.png)

**Figure 195: Cell layout for power control**

![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/Zb1xgj1tNCeN7JPB-image.png)

The power control simulation time increases with the number of cells for which power control algorithm is run. One way to reduce the simulation time is to simulate only the center cell and the first tier around it with actual power control algorithms and use artificial interference generators for the second tier as shown in Figure 195. More specifically, the <span data-highlighted="true" data-vc="highlighted-text">BS</span>’s in the center cell and the first tier go through the power control algorithms and calculate the precise power they need to transmit. Whereas, the <span data-highlighted="true" data-vc="highlighted-text">BS</span>’s in the second tier are assigned an output power level to generate interference into the center cell and the first tier. If the output power level set for the second tier is reasonable, this approach will speed up the simulation considerably without sacrificing much from accuracy. Possible methods to determine the appropriate artificial interference level will be addressed later in the paper. Nevertheless, if more accurate results are desired, the second tier can also be simulated using actual power control. In that case, a third tier with artificial interference generators would further increase accuracy by presenting the second tier with a more realistic interference background. However, given the considerations on complexity, the layout shown in Figure 195 presents the most appropriate balance between simulation speed and accuracy.

Since higher levels in SEAMCAT consider only a single <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> cell, the cell layout shown in Figure 195 may need to be generated separately in the power control module. It is expected that the <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">UE</span></span></span> placement be done consistently with SEAMCAT’s existing algorithms. However, once the UEs are placed, their mobility assignment should also be done. Actual mobility of the UEs cannot be simulated easily in a static simulation, but the effects of mobility on the channel power can be modeled in a limited sense. While the UEs will be treated at fixed locations within each snapshot, each will be assigned a speed to determine their channel conditions (fast fading), which will be used in the determination of their channel power requirements. This allows the flexibility to simulate various system configurations (fixed, highway, pedestrian, etc.).

# 8.6.3 Soft Handover

A user may simultaneously be connected to multiple <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">BS</span></span></span>’s in <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> based systems (soft handover). Since soft handover affects the amount of power transmitted by each <span data-highlighted="true" data-vc="highlighted-text">BS</span> to a certain user, it is necessary to determine whether the <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">UE</span></span></span> is served by a single <span data-highlighted="true" data-vc="highlighted-text">BS</span> or multiple <span data-highlighted="true" data-vc="highlighted-text">BS</span>’s. The actual determination of the soft handover state of a user and the corresponding channel power requirements may get complicated. Hence, a simplified soft handover algorithm is presented next, which captures the essence of soft handover effects while avoiding implementation of complex algorithms.

Base stations that are connected to a user are included in the “active set” of that user. A base station is initially selected to be in the “active set” based on the strength of its pilot signal versus the interference background. Each base station broadcasts a certain fixed percentage of its maximum power on the pilot channel. The interference background consists of the non-orthogonal energy received on the other channels of the base stations within the active set and the total broadcast power of the base stations that are not in the active set. The <span data-highlighted="true" data-vc="highlighted-text">BS</span> selection criterion, “pilot Ec/Io” is then defined as

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/0aom4TPKs0y7JtbV-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/0aom4TPKs0y7JtbV-image.png) *(Eq. 34)*

with the following definitions:

- *Ec* is the chip energy received from ith <span data-highlighted="true" data-vc="highlighted-text">BS</span>;
- *Io* is the spectral density of total received interference;
- *pilot\_frac* is the fraction of <span data-highlighted="true" data-vc="highlighted-text">BS</span> power allocated to pilot;
- *P*<sub data-renderer-mark="true">max,</sub>*I* is the maximum receivable power from ith <span data-highlighted="true" data-vc="highlighted-text">BS</span> (max <span data-highlighted="true" data-vc="highlighted-text">BS</span> transmit power\*path loss);
- *W* is the system bandwidth;
- *Pj* is the total received power from jth <span data-highlighted="true" data-vc="highlighted-text">BS</span>;
- *F* is the mobile station noise figure;
- *N0* is the thermal noise power density;
- *I<sub data-renderer-mark="true">ext</sub>* is the external interference (out of system).

Based on this selection criterion, the following simplified soft handover algorithm can be employed to assign soft handover states to each user:

For each user:

1. Add the <span data-highlighted="true" data-vc="highlighted-text">BS</span> with the strongest corresponding Ec/Io to the active set;
2. Add the <span data-highlighted="true" data-vc="highlighted-text">BS</span> with the second strongest corresponding Ec/Io to the active set if its Ec/Io is within 4 dB of the strongest Ec/Io.

Then the soft handover state of a user becomes the number of <span data-highlighted="true" data-vc="highlighted-text">BS</span>’s in its active set, which is either one or two. Note that in actual systems, the active set of a user may have more than 2 <span data-highlighted="true" data-vc="highlighted-text">BS</span>’s. However, in order to develop a unified methodology that can simulate various implementations of <span data-highlighted="true" data-vc="highlighted-text">CDMA</span> based systems and to avoid overwhelming complexity, this simplified approach is suggested. Several standards (including <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">UMTS</span></span></span>) present similar methodologies for simulations.

# 8.6.4 Power Control

As far as SEAMCAT is concerned, the actual <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> power control algorithm looks merely like a black box that maps link quality to channel power. However, the mapping is not simply one-to-one. Depending on the conditions of the mobile user, the same link quality can map to different channel power requirements. A key parameter that determines the condition of a user is called the “geometry”. The higher the geometry, the more favorable the <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">UE</span></span></span>’s condition is. The geometry is defined as:

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/cIY8CPNbQy7cqIan-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/cIY8CPNbQy7cqIan-image.png) *(Eq. 35)*

with the following definitions:

- P<sub data-renderer-mark="true">active</sub> is the total power received from <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">BS</span></span></span>’s in the active set;
- *No* is the thermal noise;
- *P*<sub data-renderer-mark="true">other</sub> is the total power received from <span data-highlighted="true" data-vc="highlighted-text">BS</span>’s not in the active set;
- *I*<sub data-renderer-mark="true">ext</sub> is the external Interference (out of system).

The fractional power levels found in the link level data are defined for each user (channel) as:

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/Wi23GOne9Y4buPz1-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/Wi23GOne9Y4buPz1-image.png) *(Eq. 36)*

with the following definitions:

- *P<sub data-renderer-mark="true">traff\_active</sub>* is the total received traffic channel power from <span data-highlighted="true" data-vc="highlighted-text">BS</span>’s in the active set
- *P<sub data-renderer-mark="true">total\_active</sub>* is the total power received from <span data-highlighted="true" data-vc="highlighted-text">BS</span>’s in the active set

P<sub data-renderer-mark="true">total\_active</sub> is the sum of the total received power from the <span data-highlighted="true" data-vc="highlighted-text">BS</span>’s in the active set including their pilot, overhead and all traffic channels. Whereas P<sub data-renderer-mark="true">traff\_active</sub> includes only the traffic channel power that is received from the <span data-highlighted="true" data-vc="highlighted-text">BS</span>’s in the active for the particular user. In other words, a user’s Ec/Ior shows the fraction of the total received power that is used for voice communication with that user. Based on this definition, the amount of traffic channel power received from a <span data-highlighted="true" data-vc="highlighted-text">BS</span> for a particular user can be derived from the Ec/Ior requirements reported in the link level data.

If user has only 1 <span data-highlighted="true" data-vc="highlighted-text">BS</span> in the active set (simplex), the power received from the <span data-highlighted="true" data-vc="highlighted-text">BS</span> is:

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/XywpaHBJvG43gYH6-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/XywpaHBJvG43gYH6-image.png) *(Eq. 37)*

If user has 2 <span data-highlighted="true" data-vc="highlighted-text">BS</span>’s in the active set (2-way soft handover), power received from one of the <span data-highlighted="true" data-vc="highlighted-text">BS</span>’s is then:

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/duZVAGYMskbXPONw-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/duZVAGYMskbXPONw-image.png) *(Eq. 38)*

Note that symmetry between the two soft handover legs (links with <span data-highlighted="true" data-vc="highlighted-text">BS</span>’s in the active set) is assumed. Therefore, when a user is connected to two <span data-highlighted="true" data-vc="highlighted-text">BS</span>’s, it receives equal power from each link. The determination of the traffic channel power levels for each user cannot be done in a single step. The inherent assumption in equations 37 and 38 is that Ptotal\_active is known. However, Ptotal\_active itself is the sum of the pilot, overhead and all traffic channel power levels received from the <span data-highlighted="true" data-vc="highlighted-text">BS</span>’s in the active set. Therefore, an iterative process is required to determine the individual traffic channel received power levels.

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/mspuin7Xdpys7IdM-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/mspuin7Xdpys7IdM-image.png)

<div class="rich-media-item mediaSingleView-content-wrap image-align-start css-11yt8uf" data-layout="align-start" data-media-vc-wrapper="true" data-node-type="mediaSingle" data-renderer-start-pos="2784" data-vc="media-single" data-width="506" data-width-type="pixel" id="bkmrk-figure-196%3A-power-co"><div class="css-1a7buj8"><div data-alt="" data-collection="contentId-493226" data-context-id="493226" data-file-mime-type="" data-file-name="file" data-file-size="1" data-height="678" data-id="f8f25a83-512d-46a4-b367-47bf8d2b80a6" data-node-type="media" data-renderer-start-pos="2785" data-type="file" data-width="859"><div class="_2rko18qm _vchhusvi _kqswh2mm _ect4ttxp _p12f1osq _c71l1osq _1bsb1qmm _4t3ine4n _1hlmd0i9 _1rquusvi _eg541i5c _mts3kb7n _1ntskb7n _yfmhtlke _5sb1v00u new-file-experience-wrapper" data-media-vc-wrapper="true" data-testid="media-card-view" id="bkmrk-figure-196%3A-power-co-1"><div class="_1reo15vq _18m915vq _2rko18qm _1e0c1txw _kqswh2mm _p12f1osq _1bsb1osq _4t3i1osq _c71l1osq media-file-card-view" data-cursor="pointer" data-test-media-name="96.png" data-test-progress="1" data-test-source="remote" data-test-status="complete" data-testid="media-file-card-view"><div class="_kqswstnw _1bsb1osq _4t3i1osq _1e0c1txw _2lx21bp4 _1bah1h6o _4cvr1h6o align-center" data-testid="ImageRendererWrapper">![](blob:https://ecowiki.atlassian.net/4bd933e9-7155-4cc1-96f8-8df60c5108be#media-blob-url=true&id=f8f25a83-512d-46a4-b367-47bf8d2b80a6&collection=contentId-493226&contextId=493226&width=859&height=678&alt=&clientId=113268fe-fe5b-4bc3-8ff3-07965dbf1d18)**Figure 196: Power Control Loop**</div></div></div></div></div></div>Figure 196 shows how the power control loop operates. The initial step is to initialize each <span data-highlighted="true" data-vc="highlighted-text">BS</span> in the cell layout (figure 1) by assigning total broadcast power levels. A figure around 70% of maximum <span data-highlighted="true" data-vc="highlighted-text">BS</span> power is appropriate. Note that for the simulated <span data-highlighted="true" data-vc="highlighted-text">BS</span>’s, the total <span data-highlighted="true" data-vc="highlighted-text">BS</span> power will be updated at each iteration by the power control loop. After enough iterations, the power levels will converge to the correct values.

Once the initialization is complete, geometry and soft handover state for each user can be calculated based on the initial values of the <span data-highlighted="true" data-vc="highlighted-text">BS</span> broadcast levels. Then the Ec/Ior requirement for each active user can be obtained from the link level data using its mobile speed assignment, calculated geometry and soft handover state. Equations 37 and 38 can then be used to get the received traffic channel power levels for each user. Path loss information can then be used to determine the corresponding transmit channel power levels. However, the calculated transmit traffic channel power levels should be checked against the maximum allowable traffic channel power and transmit/receive levels should be adjusted if necessary. As a result of such an adjustment, a user may not meet its Ec/Ior requirement. Based on a “call drop threshold”, such a user may be removed from the system if it meets the following criterion:

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/0hgGMg3DpvxUj7YB-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/0hgGMg3DpvxUj7YB-image.png) *(Eq. 39)*

The call drop threshold is set such that dropping a call is limited to extreme circumstances (thresholds less than 2dB are not recommended) and kept mostly as a safety measure to avoid a single user hogging the <span data-highlighted="true" data-vc="highlighted-text">BS</span> resources. In an actual system, calls are not dropped at the instant they fail to meet their link quality target. The system will tolerate quality degradation up to certain durations and at the same time avoid a single user to sacrifice the overall system performance by consuming all the <span data-highlighted="true" data-vc="highlighted-text">BS</span> resources (max. traff. chan. pow. setting). In fact, for systems that employ sufficient control of maximum traffic channel power, call drops may be avoided completely within the power control loop. Eventually, users not meeting their Ec/Ior target will be evaluated when the success rate of the system is calculated.

Once the transmit traffic channel levels are calculated, the broadcast power of each <span data-highlighted="true" data-vc="highlighted-text">BS</span> should accordingly be updated. If the total broadcast power of a <span data-highlighted="true" data-vc="highlighted-text">BS</span> turns out to be greater than its maximum allowable level, all traffic channels served by that <span data-highlighted="true" data-vc="highlighted-text">BS</span> should be scaled down so that the maximum <span data-highlighted="true" data-vc="highlighted-text">BS</span> power constraint is met. The scaling factor that should be applied to the traffic channel power levels can easily be calculated as:

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/bZbyoKC5yBoxQOF8-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/bZbyoKC5yBoxQOF8-image.png) (Eq. 40)

where:

- *P<sub data-renderer-mark="true">max</sub>* is the maximum allowable <span data-highlighted="true" data-vc="highlighted-text">BS</span> power
- *P<sub data-renderer-mark="true">calculated</sub>* is the actual calculated <span data-highlighted="true" data-vc="highlighted-text">BS</span> broadcast power (including pilot and overhead).

Scaling is only done if P<sub data-renderer-mark="true">calculated</sub> &gt; P<sub data-renderer-mark="true">max</sub> and it is done only on the traffic channels; pilot and overhead power levels remain at a constant percentage of the maximum allowable <span data-highlighted="true" data-vc="highlighted-text">BS</span> power. For channels that go through the scaling, achieved E<sub data-renderer-mark="true">c</sub>/I<sub data-renderer-mark="true">or</sub> levels may not match the required E<sub data-renderer-mark="true">c</sub>/I<sub data-renderer-mark="true">or</sub> levels. Therefore, call drop criterion (if used) shown in equation 6 should also be checked after the scaling. The process is outlined in Figure 199.

This process describes a single iteration of the power control loop. After all the traffic channel power levels are determined and the <span data-highlighted="true" data-vc="highlighted-text">BS</span> levels are updated, the process should be repeated (with the new, more accurate <span data-highlighted="true" data-vc="highlighted-text">BS</span> broadcast levels). Convergence of the traffic channel power levels should be checked at the end of each iteration. The loop can be terminated once the traffic channel power of every simulated user in the network converges to the desired precision.

Signaling and other errors in power control are considered in the link level simulations. System level simulations do not consider additional errors and assume that each user is served with the required power level that is determined from link level data, provided that the <span data-highlighted="true" data-vc="highlighted-text">BS</span> has enough power to do so and the maximum traffic channel limit is not exceeded.

# 8.6.5 Success rate

The power control loop terminates when every <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">BS</span></span></span> broadcast power converges and traffic channel power level for every user is calculated. Therefore, both the <span data-highlighted="true" data-vc="highlighted-text">BS</span> output power and the success rate for the cell of interest (center cell in Figure 198) can be calculated. <span data-highlighted="true" data-vc="highlighted-text">BS</span> output power is the sum of the power in pilot, overhead and all traffic channels. Success rate is the percentage of calls that do not suffer quality degradation. The following process can be used to calculate both output metrics:

i. Power control loop is terminated (traffic power converges for every user)

ii. Final <span data-highlighted="true" data-vc="highlighted-text">BS</span> transmit power levels are calculated (sum of all traffic, pilot and overhead)

iii. Total <span data-highlighted="true" data-vc="highlighted-text">BS</span> broadcast power for the cell of interest is determined

(For each active user in the cell of interest)

iv. Final geometry is calculated based on <span data-highlighted="true" data-vc="highlighted-text">BS</span> power levels calculated in ii.

v. Traffic E<sub data-renderer-mark="true">c</sub>/I<sub data-renderer-mark="true">or</sub> target is determined based on geometries calculated in iv.

vi. Achieved E<sub data-renderer-mark="true">c</sub>/I<sub data-renderer-mark="true">or</sub> is calculated based on <span data-highlighted="true" data-vc="highlighted-text">BS</span> power levels calculated in ii.

vii. Success criterion is checked

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/TYeSD4ZYQyMIZzD7-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/TYeSD4ZYQyMIZzD7-image.png) *(Eq. 41)*

viii. Success rate is determined for the cell of interest

Success Threshold is usually a small figure such as 0.5dB. Users who miss their E<sub data-renderer-mark="true">c</sub>/I<sub data-renderer-mark="true">or</sub> targets by more than the threshold suffer link quality degradation. Note that if call drops occurred within the power control loop, they should also be considered when success rate is determined:

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/zmFbK0YnsH852Flp-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/zmFbK0YnsH852Flp-image.png)  *(Eq. 42)*

# 8.7 CDMA Uplink - simulation algorithm

<span>The center cell site only is used to calculate the effects of interference. In spite of this fact, it is essential to consider the intra-system interference caused by other cells in the cluster for an accurate modelling of power control. The precise transmit power of all active mobile stations in the wrap-around cluster has to be calculated in the uplink power control loop.</span>

# 8.7.1 Power Control

<div class="_n7zlglyw _4t3i8vuz _1pby1ial _p12f18ua _1bsb1osq _1e0c1txw _4cvr1h6o _vchhusvi _1ltv1d4h _1bah1vxp _kqsw1n9t _ca0qidpf _u5f3idpf _n3tdidpf _19bvidpf _2lx21bp4 _bfhkvuon" data-testid="content-header-container" id="bkmrk-"><div class="css-lxgc1w"><div class="_bfhk1j28 _kqswlr7h _lcxv12je _1bsb1osq _1e0c11p5"><div class="css-81kfic"><div class="css-tikxu8" data-testid="object-header-container" id="bkmrk--1"><div class="css-vnc0nh"><div class="css-1cvqcn4" data-testid="breadcrumbs-with-space-name-dropdown"></div></div></div></div></div></div></div><div data-testid="content-container-component" id="bkmrk-in-cdma-networks%2C-cl"><div class="_16jlcs5v _1o9zkb7n _i0dlf1ug _1e0c1ule _1bsb1osq"><article><div class="_19itglyw _vchhusvi _r06hglyw" data-testid="view-page-main-content-container" data-vc="view-page-main-content-container"><div class="_19pkidpf _2hwx1wug _otyridpf _18u01wug _p12f1s5k" data-testid="title-wrapper"><div class="_1e0c1o8l _vchhusvi _1tke68cl _1bsb1osq _p12f1osq" data-test-id="page-content-header" data-testid="page-content-header"><div class="css-6cu6fo" data-testid="content-title-and-byline"><div class="_11c8wadc _18s8t1lt _syazazsu _1e0c1txw _4cvr1h6o _y3gn1kw7 page-metadata-modification-info"><div class="_1bsb1osq _59381r31 _yha2glyw _1nmznqa1 _43ds13af _7hxb1r31 _9m7f1r31 _rfqo1r31 _qfs11r31 _15zv8stv _w7sw8stv _1bgk8stv _s41o8stv _1xvinqa1 _15a9nqa1 _1t0pnqa1 _1k6pnqa1 _p03c12zz _oavv12zz _oxk412zz _1cay12zz _19pkidpf _2hwxidpf _otyridpf _18u0idpf"><div class="_11c8wadc _18s8ze3t _syazazsu _1e0c1txw _4cvr1h6o _y3gn1kw7 _16jlkb7n _1pby1wug _o5721q9c _4t3i1wug _1bsb1osq _kqswh2mm _7yjrt94y _1r3z1n1a"><div class="css-s0cnns" data-testid="byline-single-line"><div role="presentation"></div><div class="css-196bxhx"></div></div></div></div></div></div></div></div><div class="highlighter-context page view" data-inline-comments-target="true" data-testid="page-content-only"><div class="_19itglyw _vchhusvi _r06hglyw _19pkidpf _2hwx1wug _otyr1epz _18u01wug _1bsb1osq"><div><div class="wiki-content css-th923b e5xcnr80" data-test-appearance="max" data-testid="pageContentRendererTestId" data-vc="pageContentRendererTestId"><div class="renderer-overrides"><div class="css-3qfej8"><div class="ak-renderer-wrapper is-max css-pw7jst"><div class="css-1aarbqj" role="none"></div></div></div></div></div></div></div></div></div><div class="_19itglyw _vchhusvi _r06hglyw" data-testid="view-page-main-content-container" data-vc="view-page-main-content-container"><div class="highlighter-context page view" data-inline-comments-target="true" data-testid="page-content-only"><div class="_19itglyw _vchhusvi _r06hglyw _19pkidpf _2hwx1wug _otyr1epz _18u01wug _1bsb1osq"><div class="wiki-content css-th923b e5xcnr80" data-test-appearance="max" data-testid="pageContentRendererTestId" data-vc="pageContentRendererTestId"><div class="renderer-overrides"><div class="css-3qfej8"><div class="ak-renderer-wrapper is-max css-pw7jst"><div class="css-1aarbqj" role="none"><div class="ak-renderer-document"><div class="inline-extension-renderer css-e2q2ep"></div>In <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> networks, closed-loop fast transmit power control (TPC) is supported in uplink. The base station estimates the signal-to-interference ratio (C/I), measured in bit energy-to-noise density ratio *E<sub data-renderer-mark="true">b</sub>/N<sub data-renderer-mark="true">0</sub>*, and compares it to a target value (*E<sub data-renderer-mark="true">b</sub>/N<sub data-renderer-mark="true">0</sub>*_*target*). If the estimated C/I is below *E<sub data-renderer-mark="true">b</sub>/N<sub data-renderer-mark="true">0</sub>*_*target*, the base station commands the mobile station to increase the transmit power; if the measured C/I is above *E<sub data-renderer-mark="true">b</sub>/N<sub data-renderer-mark="true">0</sub>*_*target*, it commands the mobile station to lower its power. The fast transmit power control works at a frequency of f Hz (1500 Hz for <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">WCDMA</span></span></span> and 800 Hz in CDMA2000 1x), thus the TPC commands are transmitted at 1/f s time intervals (0.667 ms for <span data-highlighted="true" data-vc="highlighted-text">WCDMA</span> and 1.25 ms for CDMA2000 1x).</div></div></div></div></div></div></div></div></div>In reality, the fast TPC is not ideal because of issues such as

<div class="_19itglyw _vchhusvi _r06hglyw" data-testid="view-page-main-content-container" data-vc="view-page-main-content-container"><div class="highlighter-context page view" data-inline-comments-target="true" data-testid="page-content-only"><div class="_19itglyw _vchhusvi _r06hglyw _19pkidpf _2hwx1wug _otyr1epz _18u01wug _1bsb1osq"><div><div class="wiki-content css-th923b e5xcnr80" data-test-appearance="max" data-testid="pageContentRendererTestId" data-vc="pageContentRendererTestId"><div class="renderer-overrides"><div class="css-3qfej8"><div class="ak-renderer-wrapper is-max css-pw7jst"><div class="css-1aarbqj" role="none"><div class="ak-renderer-document">- inaccuracies in the C/I estimates;
- transmit power control signaling errors;
- delay in the transmit power control loop.

</div></div></div></div></div></div></div></div></div></div>Links level simulations take these errors into account and reflect their impacts on the link quality figures in the look up tables to be input to the power control module of SEAMCAT. Therefore, we assume a simple C/I based fast closed-loop TPC of traffic channels for uplink in the following.

In the uplink, each mobile station perfectly achieves the target C/I, Eb/N0\_target, during the power control loop convergence, assuming that the maximum transmit (TX) power, max\_MS\_Tx\_Pw, is not exceeded. Those mobile stations not able to achieve Eb/N0\_target after convergence of the power control loop are considered in outage.

The local-mean Signal-to-interference power ratio in the uplink, (C/I)<sub data-renderer-mark="true"><span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">UL</span></span></span></sub>, is calculated by multiplying the received signal power S by the processing gain G, and dividing the result by the total interference power I<sub data-renderer-mark="true">total</sub>

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/S3hZ4UOXC99RNdh6-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/S3hZ4UOXC99RNdh6-image.png) (Eq. 43)

 with

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/50oUdFA2dsc7iMWX-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/50oUdFA2dsc7iMWX-image.png) (Eq. 44)

I<sub data-renderer-mark="true">intra</sub> is the intra-cell interference power, i.e. the interference generated by those mobile stations served by the same base station as the considered mobile station. I<sub data-renderer-mark="true">inter</sub> is the inter-cell interference power from other radio cells. I<sub data-renderer-mark="true">out</sub> is the interference power coming from the interfering system. N<sub data-renderer-mark="true">0</sub> is thermal noise (as well as spurious interference) contained in the receiver bandwidth, *W*, and b is an interference reduction factor due to the use of interference mitigation signal processing techniques in the uplink, e.g. Multi User Detection. No such interference mitigation technique is assumed in these considerations, therefore b = 0.

Assuming a mobile station power control range in the order of *MS\_PC\_Range* dB; the minimum TX power is therefore *max\_MS\_Pw\_Tx – MS\_PC\_Range* dBm.

</article></div></div>

# 8.7.2 Soft and Softer Handover

The handover model proposed is a simplified soft handover. We assume that all base stations transmit with the same pilot power in downlink. Therefore, *P<sub data-renderer-mark="true">L\_fading </sub>*(path loss plus the shadow fading) is the only criterion for selecting the base stations belonging to the active set of a mobile station.

We assume that active set for a mobile station consists of two base stations; the base station with the strongest signal, i.e. the lowest *P<sub data-renderer-mark="true">L\_fading</sub>*, and the base station with the second strongest signal if its signal strength is within *Handover\_Margin* dB of the strongest signal (in other words its *P<sub data-renderer-mark="true">L\_fading </sub>*is within *Handover\_Margin* dB of the lowest *P<sub data-renderer-mark="true">L\_fading</sub>*).

In the case that base stations with omni-antenna are used at the cell sites, selection combining among the base stations in active set is performed and the base station with the strongest signal is selected as the serving base station of the mobile station. In the event of base stations with tri-sector antenna, similar procedure is applied, if the two sectors in the active set belong to different cell sites, else a maximal ratio combining is realized by summing the received signal powers. In the later case, the sum of received C/I values in two sectors should meet the C/I requirements specified by the link level simulation data. Because during softer handover, the mobile station is usually in the overlapping coverage area of two adjacent sectors of the base station, it is reasonable to assume that it has symmetric links to both sectors in the active set. As a consequence, each sector needs to fulfill one half of the C/I requirement.

# 8.7.3 Voice Activity Factor

The voice activity factor is the measure of how long the non-silence period is to the overall time for voice communication as it reflects the fact that speech users are silent or speaking. In SEAMCAT, It is assumed that all connected users are speaking constantly during a simulated event. It is therefore set to 1 (i.e. 100%).

# 8.7.4 System loading

The following procedures can be used for system loading during simulation and preparation of simulation outputs.

**System loading**

To determine the number of active mobile stations *Act\_MS* in the network:

1. Set up:
    
    
    1. Average traffic load in terms of a predefined number of users per cluster: *N\_UL*
    2. standard deviation of log-normal shadowing σ*<sub data-renderer-mark="true">shadowing</sub>*
    3. voice activity factor *Act\_Factor (fixed to 100%)*
    4. target maximum noise rise over the thermal noise in the network η\_*target*
    5. target C/I (*E<sub data-renderer-mark="true">b</sub>/N<sub data-renderer-mark="true">0</sub>*\_*target*) to fulfill service requirement depending on configuration and mobility (provided by link level simulations)
    6. maximum transmit power of mobile station *max\_MS\_Pw\_Tx*
    7. power control range *– MS\_PC\_Rang*:
    8. In the case that the <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> uplink is the victim link, add the received power from the interfering system to the thermal noise power
2. For each event:
    
    
    1. put down uniformly mobile stations at pseudo-random locations across the network and distribute speed among them
    2. Add a new mobile station in the set of active users in the network

<div class="ak-renderer-extension   " data-layout="default" data-node-type="extension" data-testid="extension--wrapper" id="bkmrk-compute-average-path"><div class="ak-renderer-extension-inner-wrapper ak-renderer-extension-overflow-container css-v54qrt"><div class="_1t4wglyw _1syfglyw _1pnoidpf _1gocidpf"><div class="ak-renderer-wrapper is-max css-pw7jst"><div>  
</div><div class="css-9igiaj" role="none"><div class="ak-renderer-document">- - - compute average path-loss from the mobile station to the base station of each cell
        - generate a log-normal pseudo-random value to add to each of the path losses to model shadow fading
        - perform a pseudo-random weighted coin-toss to determine voice activity, where 1 occurs with probability *Act\_Factor*
        - compute required received power at the base station to meet *E<sub data-renderer-mark="true">b</sub>/N<sub data-renderer-mark="true">0</sub>*\_*target*, given interference from pre-existing mobiles and other sources ([![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/z70EdP7czjCOqqhI-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/z70EdP7czjCOqqhI-image.png) and<a class="_ymio1r31 _ypr0glyw _zcxs1o36 _mizu1v1w _1ah3dkaa _ra3xnqa1 _128mdkaa _1cvmnqa1 _4davt94y _4bfu1r31 _1hms8stv _ajmmnqa1 _vchhusvi _kqswh2mm _ect4ttxp _syaz13af _1a3b1r31 _4fpr8stv _5goinqa1 _f8pj13af _9oik1r31 _1bnxglyw _jf4cnqa1 _30l313af _1nrm1r31 _c2waglyw _1iohnqa1 _9h8h12zz _10531ra0 _1ien1ra0 _n0fx1ra0 _1vhv17z1">![](blob:https://ecowiki.atlassian.net/4420a9a7-9611-48e9-a9ad-e564ac0a4df9#media-blob-url=true&id=1d63b543-c75f-468b-b5b7-329b14f81762&clientId=113268fe-fe5b-4bc3-8ff3-07965dbf1d18&contextId=contentId-493204&collection=contentId-493204) </a>[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/dL5ybCP8a9ilJHAy-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/dL5ybCP8a9ilJHAy-image.png) )
        - compute required transmit power of the mobile station
        - adjust the required transmit powers of the all existing mobile stations perturbed by addition of the new mobile station
        - continue the adjustment until the convergence of power control loop is achieved. A convergence criterion could be that the variation of two consecutive transmit powers of each mobile station is within a predefined threshold.
        - compare the number of active mobile stations, *Act\_MS*, with *N\_UL*
            
            
            - if *Act\_MS* ≥ *N\_UL* terminate the addition of a new mobile station in the network
            - else measure the average noise rise over the thermal noise η and compare it with the target noise rise limit η\_target
                
                
                - if η\_target is reached, terminate the addition of a new mobile station in the network
                - else add a new mobile station and go to step 2b

</div></div></div></div></div></div>

# 8.7.5 Outage calculation

Two conditions are counted as outage.

1. A mobile station, which is not able to transmit the required amount of power to meet the received *E<sub data-renderer-mark="true">b</sub>/N<sub data-renderer-mark="true">0</sub>*\_*target* due to maximum power limitations. This mobile is counted as part of the specified traffic load *N\_UL*. However, the mobile is assumed to be transmitting no power.
2. In the case of *Act\_MS* &lt; *N\_UL*, no more mobile stations can be added to the set of active users because of noise rise limits. In this event, *N\_UL* - *Act\_MS* outages are counted.

For each event, the number of optimised users is being re-calculated

# 8.7.6 CDMA UL cell selection

For the <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">UL</span></span></span>, there are two algorithms selectable in SEAMCAT:

Recommended algorithm when the interferer is a cellular network or affecting many cells in a network: the noise rise (which is measured per cell) is averaged over the whole network. This way, the UEs with highest power over the whole victim network are removed in order to compensate the noise rise due to external interference (Section ‎8.7.4).

Recommended algorithm when the interferer affects one or a few cells in a network (e.g. a strong interferer located close to a small part of the victim network): the noise rise is calculated per cell. This algorithm works as follows:

1. The cells with highest noise rise are selected.
2. Recursively, cell per cell, the UEs with highest power in the cell are removed in order to level out the network noise rise (see Annex ‎A15.3 for further details on the algorithm)

 This algorithm allows investigating per event how many cells are being affected (see Section ‎12.5.3).

# 8.8 Capacity for CDMA system

<span>When starting a simulation involving one or more CDMA systems SEAMCAT will begin by checking if any of the CDMA systems have the “Simulate non interfered capacity” feature enabled (this is the default setting). The purpose of the “Simulate non interfered capacity” feature is to find the non interfered capacity system </span><span>(i.e. how many mobiles per cell should be generated in the system before the introduction of an external interference</span>) with the current configuration.

<span>For each CDMA system needing to have its optimal capacity simulated the screen shown in Figure 197 and Figure 198 will appear for uplink and for downlink systems respectively. </span>

# 8.8.1 CDMA Uplink capacity finding

In <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> uplink, the capacity is found by gradually filling system with users until a certain average noise rise with the specified threshold noise rise is reached. The Noise rise is measured as the linear average of dB values – across all 19/57 base-stations. After every trial SEAMCAT calculates the average noise rise over the total number of trials and if this value is above the threshold restarts the simulation with a lower value of users per cell.

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/mwMnjQ2H23lJ63n2-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/mwMnjQ2H23lJ63n2-image.png)

**Figure 197: Uplink non-interfered capacity finding**

**Table 32: Elements of the uplink non-interfered capacity finding screen**

<div class="pm-table-container with-shadow-observer" data-layout="align-start" data-testid="table-container" id="bkmrk-id-description-1-thi"><div class="pm-table-wrapper" data-autosize="false" data-layout="align-start" data-number-column="false" data-table-local-id="" data-vc="table-node-wrapper"><table data-layout="align-start" data-number-column="false" data-table-width="760" data-testid="renderer-table" style="width: 100%;"><colgroup></colgroup><tbody><tr><td colspan="1" rowspan="1" style="width: 10.1353%;">**ID**

</td><td colspan="1" rowspan="1" style="width: 89.8409%;">**Description**

</td></tr><tr><td colspan="1" rowspan="1" style="width: 10.1353%;">**1**

</td><td colspan="1" rowspan="1" style="width: 89.8409%;">This dial indicates the number of trials completed with the current capacity. This dial will range from 0 to the number of trials entered as value “4” on Figure 191.

</td></tr><tr><td colspan="1" rowspan="1" style="width: 10.1353%;">**2**

</td><td colspan="1" rowspan="1" style="width: 89.8409%;">This dial indicates the current number of users being tested. Range is dynamic and the dial is mainly intended as an easy visual indicator of values being tested.

</td></tr><tr><td colspan="1" rowspan="1" style="width: 10.1353%;">**3 <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">UL</span></span></span>**

</td><td colspan="1" rowspan="1" style="width: 89.8409%;">The needle shows the current value of average noise rise across the trials run. The red area indicates the noise rise is too low (too few users in the system) – the green area is the target noise rise (plus/minus) the tolerance specified. The yellow area indicates the average noise rise is too high (too many users in the system).

</td></tr><tr><td colspan="1" rowspan="1" style="width: 10.1353%;">**4 <span data-highlighted="true" data-vc="highlighted-text">UL</span>**

</td><td colspan="1" rowspan="1" style="width: 89.8409%;">The bar chart gives information on previous values tested. The Y axis is the average noise rise and the X axis is the number of users per cell being tested.

</td></tr></tbody></table>

</div></div>

# 8.8.2 CDMA Downlink capacity finding

In <span data-highlighted="true" data-vc="highlighted-text"><span class="_kqswh2mm"><span class="_5pioz8co _189e1dm9 _1il9buyh _19lc184f _d0altlke" data-testid="definition-highlighter">CDMA</span></span></span> downlink, the capacity is found by gradually filling system with users while measuring system outage. For every number of users a certain number of trials are run and then the number of “successful” trials is compared to a predefined success criterion. Only the number of trials is configurable by user – success criterion is fixed at 80%. This means that optimal capacity of a downlink system is defined as the capacity which the system is able serve without any outage in 80% of trials. This step can be quite time consuming. See ‎ANNEX 15: to get a detailed description on how SEAMCAT determines “optimal capacity” for DL <span data-highlighted="true" data-vc="highlighted-text">CDMA</span>– using the values from Figure 192.

SEAMCAT tries to detect when no more trials with a tested value is needed to adjust to the next value. As an example, if 40 users per cell are being tested for 20 trials and the first 5 trials are unsuccessful it is not possible to reach 80% success rate and there is no need to simulate the last 15 trials. Regardless of the result of the last 15 trials SEAMCAT will conclude that fewer users per cell are needed. If more than 80% success rate is reached before all trials are simulated, there is no need to simulate the rest of the trials.

[![image.png](https://wiki.cept.org/uploads/images/gallery/2026-04/scaled-1680-/JzqJt8oJe3f54snT-image.png)](https://wiki.cept.org/uploads/images/gallery/2026-04/JzqJt8oJe3f54snT-image.png)

**Figure 198: Downlink non-interfered capacity finding**

**Table 33: Elements of the downlink non-interfered capacity finding screen**

<div class="pm-table-container with-shadow-observer" data-layout="custom" data-testid="table-container" id="bkmrk-id-description-1-thi"><div class="pm-table-wrapper" data-autosize="false" data-layout="align-start" data-number-column="false" data-table-local-id="" data-table-width="2928.1760000000004" data-vc="table-node-wrapper"><table data-layout="align-start" data-number-column="false" data-table-width="2928.1760000000004" data-testid="renderer-table" style="width: 100%;"><colgroup><col style="width: 12.8719%;"></col><col style="width: 87.1043%;"></col></colgroup><tbody><tr><td colspan="1" data-colwidth="107.25" rowspan="1">**ID**

</td><td colspan="1" data-colwidth="2822.01" rowspan="1">**Description**

</td></tr><tr><td colspan="1" data-colwidth="107.25" rowspan="1">**1**

</td><td colspan="1" data-colwidth="2822.01" rowspan="1">This dial indicates the number of trials completed with the current capacity. This dial will range from 0 to the number of trials entered as value “4” on Figure 194. SEAMCAT does not always simulate all the trials – target is 80% success and if for example 5 out of 20 have already failed – SEAMCAT does not simulate the rest of the trials.

</td></tr><tr><td colspan="1" data-colwidth="107.25" rowspan="1">**2**

</td><td colspan="1" data-colwidth="2822.01" rowspan="1">This dial indicates the current number of users being tested. Range is dynamic and the dial is mainly intended as an easy visual indicator of values being tested.

</td></tr><tr><td colspan="1" data-colwidth="107.25" rowspan="1">**3 DL**

</td><td colspan="1" data-colwidth="2822.01" rowspan="1">The red area indicates that less than 80% has been reached (i.e. too many users in the system – or not all trials yet complete) – the green area is 80% (16 trials with the default settings). The yellow area indicates that more than 80% of the trials are successful (too few users in the system). SEAMCAT stops when this dial stops in the green area after all trials completed.

</td></tr><tr><td colspan="1" data-colwidth="107.25" rowspan="1">**4 DL**

</td><td colspan="1" data-colwidth="2822.01" rowspan="1">The bar chart gives information on previous values tested. The Y axis is the number of successful trials and the X axis is the number of users per cell being tested.

</td></tr></tbody></table>

</div></div>