external] rnc capacity roadmap 1

8/2/2019 External] RNC Capacity Roadmap 1

1/23

Copyright 2006 Nortel, All Rights Reserved

Printed in France

NORTEL CONFIDENTIAL:

The information contained in this document is the property of Nortel. Except as specifically authorized in writing

by Nortel, the holder of this document shall keep the information contained herein confidential and shall protect

same in whole or in part from disclosure and dissemination to third parties and use same for evaluation, operation

and maintenance purposes only.

The content of this document is provided for information purposes only and is subject to modification. It does not

constitute any representation or warranty from Nortel as to the content or accuracy of the information contained

herein, including but not limited to the suitability and performances of the product or its intended application.

The following are trademarks of Nortel: *NORTEL, the NORTEL corporate logo, the NORTEL Globemark,

UNIFIED NETWORKS. The information in this document is subject to change without notice. Nortel assumes no

responsibility for errors that might appear in this document.

All other brand and product names are trademarks or registered trademarks of their respective holders.

Nortel UMTS RNC Capacity Roadmap

Document number: UMT/PLM/INF/004862Document issue: V01.08/ENDocument status: StandardDate: May 29th, 2006


2/23


3/23


UMT/PLM/INF/004862 V01.08/EN Standard Page 3/23

PUBLICATION HISTORY

21/OCT/2002

Issue 01.01 / EN. Creation of Document (previously called V01)08/NOV/2002

Issue 01.02 / EN. Approved version for account distribution after internal review.

(Previously called V02)

19/NOV/2002

Issue 01.03 / EN. Editorial and minor changes.

29/AUG/2003

Issue 01.04 / EN. Editorial and minor changes. Additional details provided on UA02

capacity validation and RNC 2500. Change to Video Telephony AF.

12/JAN/2004

Issue 01.05 / EN. Revised UA03 capacity. Incorporated new connectivity options.

9/JULY/2004

Issue 01.06 / EN. UA04 capacity baseline. Introduce Nortel UMTS RNC 1500,

Enhanced RNC 2500 Market Models, Minor Corrections.

20/May/2005

Issue 01.07 / EN. UA04.1 capacity baseline. Capacity improvements, Introduce Nortel

UMTS RNC 1500 Multi-shelf, Mixed capacity Profile, Minor Corrections.

07/Nov/2005

Issue 01.07b / EN. UA04.1 capacity baseline. RNC 2500 in UA05.

06/Feb/2006

Issue 01.08 / EN. UA04.2 capacity baseline.

29th/May/2006

Issue 01.08b / EN. UA04.2 capacity baseline. Update to reflect UA05 PoR. Minor

corrections.


4/23



CONTENTS

TABLES................................................................................................................................................5

1. INTRODUCTION .........................................................................................................................6

1.1. OBJECTIVE ............................................................................................................................6

1.2. SCOPE OF THIS DOCUMENT .....................................................................................................6

1.3. RNC1500OVERVIEW............................................................................................................7

2. ASSUMPTIONS AND METRICS.................................................................................................8

2.1. CALL PROFILE ASSUMPTIONS ..................................................................................................8

2.2. METRICS .............................................................................................................................10

2.2.1 Traffic Metrics .............................................................................................................11

2.2.2 Coverage Metrics........................................................................................................112.2.3 Connectivity Metrics....................................................................................................11

3. CAPACITY PER SOFTWARE RELEASE.................................................................................12

3.1. UA04.0 CAPACITY................................................................................................................12

3.2. UA04.1 CAPACITY................................................................................................................13

3.3. UA04.2 CAPACITY................................................................................................................13

3.3.1 UA04.2 RNC release BorDEr limits.............................................................................14

4. RNC PHYSICAL CONNECTIVITY OPTIONS ...........................................................................16

4.1. RNCCONNECTIVITY BY UARELEASE ....................................................................................17

5. RNC SCALABILITY ..................................................................................................................18

6. UA04.2 FEATURES IMPACT....................................................................................................20

7. RNC CAPACITY EVOLUTION..................................................................................................21

7.1. RNC1500 AND 2500CAPACITY ...........................................................................................21

ABBREVIATIONS...............................................................................................................................23


5/23



TABLES

Table 1: Traffic parameters per Uni-service.......................................................................................... 8

Table 2 Traffic parameters for RNC service-mix profile ........................................................................ 9

Table 3 Traffic parameters for RNC service-mix profile Cont. from Table 2 ....................................... 9

Table 4 Signalling parameters Common to all call profiles............................................................... 10

Table 5 Signalling parameters RNC service-mix profile only........................................................... 10

Table 6: RNC 1000 Capacity with UA04 software.............................................................................. 12

Table 7: RNC 1000 and 1500 Capacity with UA04.1 software ........................................................... 13

Table 8: RNC 1000 and 1500 Capacity with UA04.2 software ........................................................... 14

Table 9 RNC PCM Connectivity Options for All Market regions except North America....................... 16

Table 10 RNC MSS PoC Connectivity Options for All Market regions except North America ............. 16

Table 11 Connectivity Options for North American Market Regions ................................................... 16

Table 12: Summary of RNC 1000 Scalability...................................................................................... 18

Table 13: Summary of RNC 1500 Scalability...................................................................................... 18

Table 14 RNC 1000 and 1500 Optional Features Capacity Impacts ................................................... 20

Table 15: Summary of RNC 2500 Capacity per configuration............................................................. 22


6/23



1. INTRODUCTION

1.1. OBJECTIVE

Nortel UMTS RNC Capacity Roadmap provides product capacity commitments on a

per release basis, based on a set of capacity metrics for Nortel defined Speech,

Mobile Office Internet (i.e. PS 64/128 I/B), an R99 service-mix and HSDPA service-

mix capacity profiles only. Capacity figures for the other service profiles are provided

for example purposes only and are subject to change. A capacity commitments

validation report is available for every UMTS Access release comparing the RNC

capacity commitments with the actual measured capacity. The UA04.2 validation

report is available now and shows that Nortel RNC meets capacity commitments.

Nortel uses the following criteria to formulate the capacity commitment of the RNC

1000 & 1500:

Scenarios must be verifiable either in a lab or in the field

Capacity metrics chosen based on their suitability for network engineering

The Capacity Commitments Validation report provides the following benefits:

Full and Comprehensive visibility of RNC capacity:

The test report gives a comprehensive view of Nortels RNC capacity in

loaded conditions for a given release.

A transparent commitment from Nortel:

The capacity committed is directly comparable to the actual measured

capacity in Nortels labs. This ensures that Operators can hold Nortel

accountable for the capacity we commit to on the RNC.

Continuity of capacity commitment:

Each release of the capacity test report will contain the same capacity metrics,

guaranteed to be verified in identical conditions and formatted to allow simple

comparisons against capacity commitments for this release and results from

previous release(s).

Capacity Achievements in live networks

Each release Nortel will share the major capacity achievements obtained in

live network deployments.

1.2. SCOPE OF THIS DOCUMENT

Nortel RNC Capacity Roadmap provides RNC product capacity commitments on a per

release basis. The baseline release for this document is UA04.2 release. This

document describes the assumptions and environment under which the Nortel RNC

achieves a specific capacity. It also highlights which tests will be executed to ensure

that capacity commitments are achieved once the relevant software release is

available.


7/23



1.3. RNC 1500 OVERVIEW

The RNC 1500 is based on the Multi-Service Switch (MSS) platform and is available

from UA04.1. The RNC 1500 is functionally equivalent to the RNC 1000 i.e. same

feature content, capacity, performance and reliability; but occupies 50% less cabinet

space than the RNC 1000 SDH & SONET models. The RNC 1000 will bemanufactured discontinued in June 2006.


8/23



2. ASSUMPTIONS AND METRICS

2.1. CALL PROFILE ASSUMPTIONS

Nortel are introducing an RNC service-mix profile to provide a view of RNC capacity

with a mix of different CS and PS services. In particular, the RNC service-mix profile is

designed to stimulate current and future RRM features, which can be verified in

Nortels test environment. It is not intended to model real network call profiles that

evolve continuously over time. The RNC service-mix profile definition will remain

stable release over release for comparison purposes, like the Speech and Mobile

Office Internet Uni-service profiles. In UA04.2, Nortel provides a commitment and

issues a capacity validation report for the RNC R99 and HSDPA service-mix profiles

also. In both call profiles the PS services are the same, but an HSDPA bearer is used

instead of dedicated RB in the downlink.

Nortel RNC capacity commitments are based on a set of call profile assumptions perservice. Call profiles are described by traffic parameters per service and service

independent signalling parameters. However, in order to trigger different RRM

features additional signalling parameters are defined for the RNC service-mix profile.

The following tables describe the Uni-service and RNC service-mix profile

assumptions:

Uni-Service Call Profile assumptions Traffic parameters

RAB

DownlinkActivityFactor

UplinkActivityFactor

Mean Callduration(second) BHCA

MobileTerminated

Calls Typical Service

CS Conv. 12,2 AMR 50% 50% 90 1 44% Speech

CS Conv. 64 100% 100% 180 0.3 50% Video Telephony

PS I/B 64/64 50% 5% 85 0.3 0% Basic browsingPS I/B 64/128 50% 10% 75 0.3 0% Mobile office Internet

PS I/B 64/128 90% 20% 200 0.3 0% Video streaming

PS I/B 64/64 90% 10% 220 0.3 0% Audio streaming

PS I/B 64/384 50% 10% 75 0.3 0% Mobile office Premium

Table 1: Traffic parameters per Uni-service

Table 1 Notes:

Each service assumes that 100% of the traffic is generated using only this

service. Note that in reality, there will be a mixture of services.

BHCA per attached Subscriber is 1 for speech, the same as the NUSCM.

However, NUSCM considers a low BHCA for each data service (CS or PS)since all services are running in parallel in a service-mix profile. In the Uni-

service profiles, data services are run in isolation. Therefore, BHCA for each

data service has been set to 0.3 in order to make each all data scenario

significant and comparable.


9/23



RNC Service-mix Call Profile assumptions Traffic parameters

RAB

DownlinkActivityFactor

UplinkActivityFactor

Sessionduration(second)

Iu Conn.Duration(second) BHCA Typical Service

CS Conv. 12,2 AMR 50% 50% 90 90 1 Speech

CS Conv. 64 100% 100% 240 240 0.11 Video Telephony

PS I/B 64/6440% R992.4% HS 10% 232 272 0.43 Basic browsing

PS I/B 64/12830% R993.8% HS 10% 90 130 0.43 Mobile office Internet

PS I/B 64/38420% R997.5% HS 10% 100 140 0.29 Mobile office Premium

CS Conv. 12,2 AMR 50% 50% 120 120 0.002 Emergency Calls

Table 2 Traffic parameters for RNC service-mix profile

Table 2 Specific Notes:

Session Duration is the time from the first to last user packet transmission.

Iu connection duration time = Session duration + AlwaysOn TimerT1 (downsize

timer) + AlwaysOn TimerT2 (Iu release timer). PS I/B calls are assumed to end

due to T2 timeout and RNC initiated release.

HSDPA RNC service-mix profile uses HSDPA in the Downlink for PS services,

rather than R99 dedicated bearers. e.g. R99 PS I/B 64/64 is HSDPA PS I/B

64/HSDPA.

Note as HSDPA bearers have higher peak rates than R99 DCH bearers, the AFs

for HSDPA are different (in DL only). HSDPA AFs are denoted as HS in Table 2.

Corrected session duration error (250s to 240s) for CS Conv. 64Kbps RAB.

RNC Service-mix Call Profile assumptions Traffic parameters Cont.

RAB CompressedMode

Mobile

TerminatingCalls

#Pauses /Pause

Duration(second)

Bad Radio

Events persession Typical Service

CS Conv. 12,2 AMR 10% 44% 0 0 Speech

CS Conv. 64 0% 50% 0 0 Video Telephony

PS I/B 64/64 0% 0% 4/38s 0.1 Basic browsing

PS I/B 64/128 0% 0% 4/5s 0.1 Mobile office Internet

PS I/B 64/384 0% 0% 2/15s 0.1 Mobile office Premium

CS Conv. 12,2 AMR 0% 0% 0 0 Emergency Calls

Table 3 Traffic parameters for RNC service-mix profile Cont. from Table 2

Table 3 Specific Notes:

Compressed mode represents the % of 3G calls per busy hour that terminate with

a Hard Handover to 2G.

Number of pauses per session and the average pause duration simulates long

intra session periods of inactivity in data applications. These pauses may result in

a change to/from the downsized/nominal state.


10/23



Call Profile assumptions (common to all services) Signalling parameters

Parameter Value Comments

IMSI attach0.17 (CS)0.27 (PS)

Per attached subscriber during busy hour

IMSI detach

0.14 (CS)

0.08 (PS)

Per attached subscriber during busy hour

This includes UE and network initiatedLocation Area Update 1.25 (CS) Per attached subscriber during busy hour

Routing Area Update 0.65 (PS) Per attached subscriber during busy hour

% attached subscribers70% (CS)80% (PS)

Percentage of reference subscribers attached to thenetwork

1.3 Average Sector per User in Cell DCH stateMacro Diversity (R99only)

0.1Active Set Update rate. This means 1 radio link additionOR one radio link deletion every 10 seconds

6 UMTS Cells per RRC Measurement ReportRRC Measurements

0.75 MR/sec per subscriber in cell-DCH state

1.5 CN paging request repetition factorPaging Repetition

1 UTRAN Paging repetition factor (means 1 transmission)

RLC Retransmission 10% Due to Block Error Rate

Table 4 Signalling parameters Common to all call profiles.

Call Profile assumptions (common to all services) Signalling parameters

Parameter Value Comments

Cell Update (R99 only) 0.03 (PS) Per second in Cell FACH state

NBAP MR rate (R99Only)

1 Dedicated MR per iRM upgrade

Compressed Mode Cellsper RRC MR

6+6 UMTS+GSM

iRM scheduling events(R99 only)

Assume 10% of PS sessions experience badRadio conditions once per session

PS Session termination RNC always terminates due to T2 Always-On time-out

Table 5 Signalling parameters RNC service-mix profile only

The assumptions proposed in these tables are realistic assumptions based on Nortels

extensive field experience in live GSM, CDMA and IP networks:

The signalling parameter values are taken from Nortel UMTS Standard Call Model

(NUSCM), which is an average of the call profiles observed or anticipated on

various networks.

All traffic and signalling values are for attached subscribers.

These signalling parameters apply to both R99 and HSDPA mixed profiles, unless

stated otherwise e.g. Macro diversity (in DL) does not apply to HSDPA PS

services.

2.2. METRICS

The RNC capacity is defined in three dimensions:

- traffic

- coverage

- connectivity


11/23



These dimensions are independent, thus the RNC capacity is determined by the most

constraining limit. Nortel uses the following Metrics to quantify the capacity of the

RNC:

2.2.1 TRAFFIC METRICS

Iu Mbit/s UL+DL at application layer

oThis metric is defined as the sum of UL and DL traffic on Iu-CS and Iu-PS

interfaces, at the application layer.

Iu Mbit/s UL+DL at physical layer

oThis metric is defined as the sum of UL and DL traffic on Iu-CS and Iu-PS

interfaces, at the physical layer. This figure is always greater than the

application layer throughput.

Reference Subscriber

oThis metric is the total number of subscribers located under the coverage of

that RNC.

Simultaneous TRB subscribers (or Erlangs for CS domain)

oThis metric represents the amount of simultaneous subscribers with a Traffic

Radio Bearer assigned. Note that in case of CS Services, this is

equivalent to the Erlang metric.

2.2.2 COVERAGE METRICS

Number of Node B

oThis is the number of Node Bs that can be under a single serving RNC.

Number of Cells

oThis is the number of cells that one serving RNC can support. A cell is

defined as one carrier in one sector; for instance, a S222 contains 6 cells.

2.2.3 CONNECTIVITY METRICS

Number of E1/DS1

oThis is the number of E1/DS1 links that the RNC can terminate.

Number of STM1/OC3

oThis is the number of STM1 or OC3 links that the RNC can terminate.


12/23



3. CAPACITY PER SOFTWARE RELEASE

This section provides the capacity per UMTS Access (UA) software release. These

capacity commitments are based on: A maximum RNC Configuration i.e.

o RNC 1000: 14 TMU-Rs and 12 Packet Servers

o RNC 1500: 12 Packet Servers

Apply to all physical RNC connectivity options e.g. E1, STM1, OC3

Capacity commitments, shaded in green are for Speech and Mobile office

internet (PS 64/128 I/B RB) service profiles only for UA04.1 and prior

releases. From UA04.2, Nortel also supports capacity commitments for an

RNC R99 and HSDPA service-mix profiles.

Capacity figures for the other service profiles are provided as examples.These are not commitments from Nortel and are subject to change.

3.1. UA04.0 CAPACITY

The capacity commitments for Nortel UMTS RNC 1000 for UA04.0 release are

provided in Table 6.

Service & Bearer Capacity of RNC 1000

Iu Mbit/s Reference

RAB Typical Service

Iu Mbit/sApplication Layer

PhysicalLayer Subscribers

SimultaneousTRB

subscribers

CS Conv.12,2AMR Speech 49 83 220 000 3900

CS Conv. 64 Video Telephony 170 205 130 000 1300

PS I/B 64/64 Basic browsing 85 105 400 000 2200

PS I/B 64/128 Mobile office Internet 140 170 400 000 2000

PS I/B 64/128 Video streaming 240 300 140 000 1900

PS I/B 64/64 Audio streaming 200 240 210 000 3100

PS I/B 64/384 Mobile office Premium 225 270 230 000 1100

Table 6: RNC 1000 Capacity with UA04 software

Notes:

These are the capacity figures for RNC 1000 UA04.0 General Availability

(GA).

Capacity commitments of Speech and Mobile Office profiles are unchanged.

UA04.0 Capacity Validation notes:

The capacity figures in green coloured cells have been measured during

capacity tests and included in the UA04.0 capacity commitments validation

report.

RNC capacity validation improvements :

o Increased call model coverage i.e. new signalling procedures

implemented.


13/23



o Model more closely reflects typical Node B deployment

o Improved accuracy in the U-plane traffic generation.


The capacity commitments for UA04.1 release are provided in

Table 7.

Service & Bearer Capacity of RNC 1500 & RNC 1000

Iu Mbit/s Reference

RAB Typical Service

Iu Mbit/sApplication Layer

PhysicalLayer Subscribers

SimultaneousTRB

subscribers








Table 7: RNC 1000 and 1500 Capacity with UA04.1 software

Notes:

These are the capacity figures for UA04.1 General Availability (GA).

RNC 1500 was introduced in UA04.1.

Capacity commitment for the Mobile Office profile was increased in UA04.1

i.e. new commitment is 176 vs original 140 Mbps.

Capacity commitment of Speech profile is unchanged at 3900 Erlangs.

RNC service-mix profile is a capacity commitment from UA04.2.




report, which is available.


The capacity commitments for UA04.2 release are provided in Table 8.


14/23



Service & Bearer Capacity of RNC 1500 & RNC 1000

Iu Mbit/s Reference

RAB Typical Service

IuMbit/s

Application

Layer

Physical

Layer Subscribers

SimultaneousTRB

subscribers








R99 RABs R99 Service-mix 88 120 49 000 2500

R99 & HSDPA RABs HSDPA Service-mix 88 120 49 000 2500

Table 8: RNC 1000 and 1500 Capacity with UA04.2 software

Notes:

These are the capacity figures for UA04.2 General Availability (GA).

RNC HSDPA and R99 service-mix profiles are capacity commitments from

UA04.2.




report, which is now available.

3.3.1 UA04.2 RNC RELEASE BORDER LIMITS

Border limits define the maximum operating range of the RNC for a given release i.e.

the maximum capacity figures that cannot be exceeded irrespective of call profile.

The following border limits exist on the RNC:

310Mbps Iu DL throughput on the current 16pOC3/STM1 (PQC based) Card.

o A new version of the 16pOC3/STM1 (MS3 based) is being introduced

in UA05 that supports line rate (upto 2.5Gbps) IP forwarding.

o Nortel are increasing this border limit from 220Mbps to 310Mbps and

aligns with the MSS engineering recommended IP forwarding limit for

this card.

A fully configured UA04.2 RNC 1000 and 1500 can support a maximum of

9600 (UA04.1 = 7200) RRC contexts. The following is a breakdown of the

different RRC contexts pools:

o Max number of CS RRC contexts: 6048 (UA04.1 = 4320)

o Max number of PS RRC contexts: 8640 (UA04.1 = 3600)

o Max number of UE RRC contexts: 9600 (UA04.1 = 4620)


15/23



o Max number of FACH RRC contexts: 6720 (UA04.1 = 2400)

In UA05.0, Nortel plan to introduce CELL_PCH and URA_PCH RRC context

states. Nortel plan to support

o Max number of CELL_PCH RRC contexts: 7020

o Max number of total CELL_PCH and URA_PCH RRC contexts:

32,040.

o Max number of FACH RRC contexts: 7020 (UA04.2 = 6720).

o All other UA04.2 RRC context pools remain unchanged.


16/23



4. RNC PHYSICAL CONNECTIVITY OPTIONS

The RNC is based on the industry leading MSS Platform. The MSS portfolio supports

numerous different interface options, not all of which are applicable to a UTRANsystem. Nortel adds new connectivity options to our RNC product every release.

This section provides the capacity in terms of links & ports for each available

connectivity option. Each connectivity option supports the same processing capacity in

terms of Erlangs, Subscribers, and Mbps etc. as per section 3.

w/o IMA IMA

MSA32 DS 32 Electrical 6+1 7K210

(30 * 7 FP)

Upto UA04.1

154 (22 * 7 FP)

from UA04.2

196 (28 * 7 FP)

8+8 (RNC 1000)

9+9 (RNC 1500)UA01

MSA32 SS 32 Electrical 6+1 7K 210(30 * 7 FP)

Upto UA04.1

154 (22 * 7 FP)UA04.2

196 (28 * 7 FP)

8+8 (RNC 1000)9+9 (RNC 1500) avail 2005

Clear Channel SS 16 Optical 1+1 None _ _

In SDH config

15+15 (RNC 1000)

16+16 (RNC 1500)

UA01

Channelized DS 2 Electrical 2+2 7K 228 2528+8 (RNC 1000)

9+9 (RNC 1500)UA04.1

Connectivity Option Max. RNC Configuration RNC Connectivity Capacity

E1

STM1E1s

Interface VariantSingle Slot/

Double Slot# ports

MSS7K

(if required)

Optical/

Electrical# FPs

Interface

Availability

STM1

Table 9 RNC PCM Connectivity Options for All Market regions except NA

w/o IMA IMA

MSA32 DS 32 Electrical 6+1 7K 210(30 * 7 FP)

Upto UA04.0

154 (22 * 7 FP)from UA04.1

196 (28 * 7 FP)

8+8 (RNC 1000)9+9 (RNC 1500)

UA01

MSA32 SS 32 Electrical 9+2 7KFrom UA04.1

330 (30 * 11 FP)

From UA04.1

308 (28 * 11 FP)

8+8 (RNC 1000)

9+9 (RNC 1500)avail 2005

Clear Channel SS 16 Optical 1+1 None _ _

In SDH config

15+15 (RNC 1000)

16+16 (RNC 1500)

UA01

Clear Channel SS 4 Optical 6+6 15K _ _ 24+24PCR 5.2

(Min)

Channelized DS 2 Electrical 2+2 7K 228 2528+8 (RNC 1000)

9+9 (RNC 1500)UA04.1

Channelized SS 2 Optical 5+5 7K 570 6308+8 (RNC 1000)

9+9 (RNC 1500)

PCR 7.1

(min)

STM1

PoC

(if required)

E1sSTM1

E1

Connectivity Option Max. RNC Configuration RNC Connectivity Capacity

Interface

AvailabilityInterface Variant

Single Slot/

Double Slot# ports

Optical/

Electrical# FPs

Table 10 RNC MSS PoC Connectivity Options for All Market regions except NA

w/o IMA IMA

DS3 Channelized SS 4 Electrical 8 + 2 15K896

(112 * FP)

896

(112 * FP)

8+8 (RNC 1000)

9+9 (RNC 1500)UA03

OC3 Clear Channel SS 16 Optical1+1 (RNC)

4 (PoC)15K _ _

15+15 (RNC 1000)

16+16 (RNC 1500)

64 (AN)

UA01

RNC Connectivity Capacity

Interface

AvailabilityInterface Variant

Single Slot/

Double Slot

PoC

(if required)# ports

Connectivity Option Max. RNC Configuration

Optical/

ElectricalOC3

DS1s# FPs

Table 11 Connectivity Options for North American Market Regions


17/23



Notes

The maximum number of interfaces a single connectivity option can support is

provided. Nortels RNC is very scalable and allows for smaller configurations.

Connectivity options are segregated, i.e. North America and all other regions.

MSS7K can be deployed as part of the RNC 1500 PCM configuration or as a

Point of Concentration in UA04.1 or UA04.2.

In #FP column the redundancy scheme is provided e.g. 6+1 implies 6 active

cards and 1 spare card.

Max number of E1s with MSA32 card are for unspared MSS7K configurations

4.1. RNC CONNECTIVITY BY UA RELEASE

The new connectivity options introduced in UA04.1 are

o

The single slot MSA32 card available from year end 2005o This is the same card as the current double slot MSA32, but occupies

a single card slot only.

o The STM1 electrical Channelised card is a 2 port card and supports ATM and

IMA services.

o RNC 1500 has an additional port over RNC 1000 because a port is no longer

required for the CNode platform.

o Support for a 2pSTM1/OC3 card in the MSS7K PoC and Access Nodes;

MSA32-STM1 card is being MDd in June 2006 as this will not be made RoHS

compliant.

The new connectivity options that introduced in UA04.2 are

o Support for 28E1s with IMA per MSA32 card on the RNC PCM configuration

o 2ptSTM1o ch card in the MSS7K PoC (min PCR 7.1 release)

o Support for Y-splitter functionality on the 16ptOC3/STM1 card, which enables

equipment (not line) protection even though there is only a single fiber.

The new connectivity options planned for UA05 are

o Nortel plan to MD the RNC 1500 PCM configuration from UA05 and only

support PoCs.


18/23



5. RNC SCALABILITY

In previous sections, Nortel RNC capacity was quoted based on the maximum

configuration. However, Nortel RNC is a very scalable platform, and can be configuredto meet different network capacity needs.

Table 12 and Table 13 show the main dimensioning metrics for the RNC scalability

models. The new connectivity options being introduced in UA04 and beyond will

provide similar scalability.

RNC 1000 Market ModelsUA

ReleaseS4-4-0P4-4-3

PCM OnlyP6-6-5

S7-7-0P9-7-5

S11-10-0P12-10-7

S14-12-0P14-12-7

Node B 80 120 140 200 200

Cells 360 600 7201080 (S)

1200 (P) 1200

Speech (RB CSConv.12,2AMR)Erlangs orSimultaneous TRBs

UA04.x 980 16002000 (S)2300 (P)

2900 (S)3300 (P)

3900

UA04.0 36 6072 (S)84 (P)

108 (S)120 (P)

140Mobile Office Internet(RB = PS I/B 64/128)Iu App. Throughput (Mbit/s) UA04.x

(x= 1 or 2)44 73

88 (S)103 (P)

132 (S)147 (P)

176

RNC R99 & HSDPAService Mixed ProfileSimultaneous TRBs

UA04.2 625 10401250 (S)1460 (P)

1880 (S)2080 (P)

2500

Table 12: Summary of RNC 1000 Scalability

RNC 1500 Market Models1504 1506 1507 1510 1512

Node B 80 120 140 200 200

Cells 360 600 720 1200 1200

Speech(Erlangs)

980 1600 2000 3300 3900

Mobile Office InternetIu App. Throughput (Mbit/s)

44 73 88 147 176

RNC R99 & HSDPAService Mixed Profile

Simultaneous TRBs

625 1040 1250 2080 2500

Table 13: Summary of RNC 1500 Scalability

Notes:

For more details about the definition of the metrics and assumptions used to

compute these figures please refer to previous section 3 Capacity per

software Release

S refers to RNC SONET configuration in North America, whereas S refers to

SDH for all other market regions. P stands for PCM in the table.


19/23



- This notation only refers to RNC 1000. The RNC 1500 also supports

SONET, SDH and PCM configurations but does not include this

notation in the naming;

The available RNC 1500 Market Models are provided below. The model

naming uses the last 2 digits (i.e. RNC 15XX) to refer to the number of Packet

Servers. MSA32 cards are required for RNC 1500 PCM models only.

RNC 1500 Market Models1504 1506 1507 1510 1512

PS 4 6 7 10 12

MSA32 3 5 5 7 7


20/23



6. UA04.2 FEATURES IMPACT

In general, Nortel includes most of the base and optional features in the capacity

calculation. This means that the capacity given in this document assumes that most ofthe features are enabled in the network. However, the following exceptions should be

noted:

1- Nortel assumes that the parameter setting is within a reasonable range. For

instance, setting always-on timers or handover threshold outside of this range can

cause additional procedures and degrade RNC Capacity.

2- When implementing new features in future software releases, there is always the

possibility that a feature(s) may degrade the RNC capacity. While every effort will

be made to ensure there is no degradation in capacity over a previous release,

Nortel will notify operators before the customer readiness milestone and quantify

the capacity degradation.

3- The capacity communicated in this document assumes that features that are

specifically designed to optimize or commission a network are turned-off. This is

the case for call trace and OCNS.

In UA04.2, there are two optional features that have an impact on RNC capacity i.e.

Silent Mode (SM) and Full Event Triggered Measurement Reports (fETMR), which

replaces Partial Event Triggered Measurement Reports. The following table highlights

the impact of these optional features on RNC 1000 and 1500 capacity.

RNC 1000 14-12 RNC 1512Feature Impact

Erlangs Mbps Erlangs Mbps

RNC Base Capacity (No SM, no ETMR) 2630 153 2730 158

Silent Mode Only Enabled 2630 153 2730 158

Full ETMR Only Enabled 3900 176 3390 172

Silent Mode and Full ETMR Enabled 3900 176 3900 176

Table 14 RNC 1000 and 1500 Optional Features Capacity Impacts


21/23



7. RNC CAPACITY EVOLUTION

Nortel Networks RNC 2500 is the next generation RNC and is planned in UA06

release.

Figure 1 RNC capacity roadmap

The key benefits of this product for a customer are:

Increased number of Node B per RNC

This will allow the expected network expansion and densification without

additional RNCs.

Increased number of Mbit/s per RNC

The added Mbit/s will absorb traffic growth without having to install new RNCs.

Increased number of subscribers per RNC

The 3G-subscriber base will grow and the RNC can absorb this growth without

having to install new RNCs.

Reduced operational costs thanks to a smooth upgrade policy

The evolution from Nortel Networks RNC to Nortel Networks RNC 2500 is

achieved through a software upgrade and (optionally) simple upgrade of FRU

(Field Replaceable Units). No forklift is required.

The current platform also allows a second step upgrade by addition of NextGeneration PSFPs, without requiring a forklift of the cabinet. This is a candidate

feature for UA06.

7.1. RNC 1500 AND 2500 CAPACITY

The capacity of RNC 2500 and NGPS is presented in the table below:

UA04.1UA04.1

RNC 1500 RNC 2500

ORBiT

Optional

NGPS3

2X2X

UA06UA06

RNC 2500

+

UA06UA06

Hitless Patching

Single PlatformIncreased Density

2X Capacity Increase

OPEX reduction

2X capacity

PS Mixity

Highlights

Optional Optional


22/23



Node B 200 160 240 280 400 400 800 720

Cells 1200 720 1200 1440 2400 2400 4800 3600

STM1/OC3 16 16 16 16 16 16 16 16

Speech

(Erlangs)

3,900 2,000 3,200 4,000 6,600 8,000 16000 9600

Mobile Office Internet

Iu App. Throughput (Mbit/s)176 88 146 176 294 352 704 438

RNC 2512

6 NGPS

+ 6 PS1

RNC 1512

Max Config.RNC2504 RNC 2506 RNC 2510

RNC 2512

Max Config.

RNC 2512

with NGPSRNC 2507

Table 15: Summary of RNC 2500 Capacity per configuration

Notes:

RNC 2500 supports the same Market Models as RNC 1500

RNC 2500 uses same model naming convention as RNC 1500

o The RNC 2512 is a fully populated RNC with 12 Packet Servers.

Given that we are only at the early stage of the project, the capacity of these

models are guidelines only and subject to change as development

progresses.

RNC 2500 with Next Generation PSFP doubles RNC 2500 capacity.

RNC 2500 shall support a single mixity configuration of 6 current PSs and 6

next generation PSs.


23/23


ABBREVIATIONS

2.5G 2.5 Generation Wireless Network

2G 2nd Generation Wireless Network

3G 3rd

Generation Wireless Network

AF Activity Factor

AN Access Node

BHCA Busy Hour Call Attempts

DL Downlink

DS Refers to an interface card that occupies a double slot in the shelf

FRU Field Replaceable Units

NGPS Next Generation Packet Server

NUSCM Nortel UMTS Call Model

RNC Radio Network Controller

SR Strategic Readiness

SS Refers to an interface card that occupies a single slot in the shelf

UA UMTS Access release.

UL Uplink

TRB Traffic Radio Bearer

END OF DOCUMENT

external] rnc capacity roadmap 1

Documents