RANCP51 Release Note Build 136

7/27/2019 RANCP51 Release Note Build 136

http://slidepdf.com/reader/full/rancp51-release-note-build-136 1/10

© Nokia CorporationNokia Proprietary and Confidential

1 (10)

Nokia WCDMA RAN Capacity Planner

Release Note

RANCP 5.1, Version 1.1 Build 136



Generic Failure Reports

2 (10) © Nokia CorporationNokia Proprietary and Confidential

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is intended for theuse of Nokia's customers only for the purposes of the agreement under which the document issubmitted, and no part of it may be reproduced or transmitted in any form or means withoutthe prior written permission of Nokia. The document has been prepared to be used by

professional and properly trained personnel, and the customer assumes full responsibilitywhen using it. Nokia welcomes customer comments as part of the process of continuousdevelopment and improvement of the documentation.

The information or statements given in this document concerning the suitability, capacity, orperformance of the mentioned hardware or software products cannot be considered bindingbut shall be defined in the agreement made between Nokia and the customer. However,Nokia has made all reasonable efforts to ensure that the instructions contained in thedocument are adequate and free of material errors and omissions. Nokia will, if necessary,explain issues which may not be covered by the document.

Nokia's liability for any errors in the document is limited to the documentary correction oferrors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDINGMONETARY LOSSES), that might arise from the use of this document or the information in it.

This document and the product it describes are considered protected by copyright accordingto the applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

Other product names mentioned in this document may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright © Nokia Corporation 2007. All rights reserved.



Contents


3 (10)

Contents

1 About this document ........................................................................... 4

1.1 Overview................................................................................................ 4





1 About this document This document describes the functionality of the Nokia RAN Capacity Planner

(RANCP) software build 136.

1.1 Overview

1.2 Flexi BTS model

Flexi BTS model for RANCP consist of WSM configuration, carriers, sectors

and signalling link configuration. Channel Element capacity licensing, CEusage for Common Channels and HSDPA are included in the model. The

supported Flexi configurations are included in the installation package.

1.3 RN 2.2 RNC models

The RNC's of RNC 196 family use the concept of DMPG pooling for allocating

resources for HSDPA. This feature applies only to RNC's of RNC 196 family

and release RAS05. Starting from release RAS05.1, support for this feature is

not needed in the RAN Capacity Planner.

The supported RNC configurations and capacity limits included in the

installation package.





5 (10)

1.4 Multiple VCC handling

Multiple U-plane VCC’s connections were not handled correctly with the first

version of the RANCP tool. Multiple VCC’s are needed, when there aremultiple WAM’s in the BTS configurations and optional AAL2 multiplexing

feature is not used. Multiple U-plane VCC’s may be needed with AAL2

multiplexing feature, when there is AAL2 connection ID limitation.

Common channel allocation in BTS capacity planning with multiple VCC was

implemented based on simplified BTS RRM algorithms. The type of the VCC

and it's free capacity may be taken into account in the algorithm, since the tool

does not have a BTS HW model, which would contain the information needed

for detailed CCH allocation algorithm. However, the user is able to reallocate

the CCH's based on other information, like product descriptions or BTS

dimensioning guidelines.

Allocation of the user services on multiple U-planes VCC's shall be based on

simplified allocation algorithm, where the allocation is based on available U-

plane capacity only.

The allocation of Common Channels and user services based on U-plane

capacity is not an issue, since the configuration of the BTS should be such, that

the WSP capacity behind each U-plane VCC is corresponding to the U-plane

VCC size.

1.5 Route selection supported at Iub

The Route Selection feature allows dedicating a separate VCC for HSDPA at

the Iub interface.

The tool shall allow user to define multiple VCC's and select on which VCC’s

the HSDPA is allocated. When the route is selected for HSDPA, the tool does

not allocate any other traffic, like Common Channels, or other user services on

this VCC. Signalling bearers or uplink data channels related to HSDPA userservice are not allocated to this VCC, either.

Statistical multiplexing gains in the intermediate transport network (between the

RNC and the BTS) are realized using external ATM equipment. The tool does

not model this functionality, since the network elements, which might realize

the multiplexing gain, are out of the scope of the RANCP.





1.6 AMR Codec Sets (12.2, 7.95, 5.90, 4.75) and (5.90,4.75)

New bearers supporting AMR Codec sets (12.2, 7.95, 5.90, and 4.75) and (5.90,

4.75) are introduced in RAS05.1. These services are included in the installation

package of the tool.

1.7 Wideband AMR Codec Set (12.65, 8.85, 6.6)

New bearers supporting Wideband AMR Codec Set (12.65, 8.85, and 6.6) are

introduced in RAS05.1. These services are included in the installation package

of the tool.

1.8 Interactive & Background PS Data 256 kbpsUplink&Downlink

New bearers supporting Interactive & Background PS Data 256 kbps Uplink

Downlink are introduced in RAS05.1. These services are included in the

installation package of the tool.

1.9 HSDPA with Simultaneous AMR Voice Call

New service consisting of HSDPA with Simultaneous AMR Voice Call is

introduced in RAS05.1. These services are included in the installation package

of the tool.

1.10 RNC196 support

The purpose of the 300 Mbits/s and 450Mbit/s capacity upgrades is to increase

Iub capacity for e.g. HSDPA services. This upgrade can be done to 196Mbits/s

RNC's (or from 300Mbit/s) to make installed base RNC's more suitable to

increased Iub traffic.





7 (10)

Two new capacity steps are introduced to RNC196:

RNC196/300M:

The capacity of RNC196/196M is increased to 300Mbit/s (Iub) by removingsome units and replacing those with other functional units.

The main capacity figures for RNC196/300M are:

• Iub throughput: 300 Mbits/s

• AMR capacity: 6800 Erl

• AAL2UP connectivity: 1.3 Gbits/s with AL2S-B, 3.594 Gbits/s with

AL2S-D

RNC196/450M:

RNC196/450M includes the same number of units as RNC196/300 but the

minimum HW requirements for the units are different.

The main capacity figures for RNC196/450M are:


• AMR capacity: 8000 Erl

• AAL2UP connectivity: 3.594 Gbits/s





These new RNC configurations and capacity limits are included in the


1.11 RNC450 support

New RNC450 with enhanced mechanics and new capacity steps is introduced.

RNC450 includes three different capacity steps with Iub throughput figures 150

Mbits/s, 300 Mbits/s and 450 Mbits/s as described in the figure below.

The cabinet and the mechanics including the power distribution and cooling

system are enhanced to support the future capacity increase towards the gigabit

capacity.





9 (10)

The main capacity figures for the maximum 450 Mbits/s configuration are:


•

AMR capacity: 8000 Erl• AAL2UP connectivity: 3.594 Gbits/s

These new RNC configurations and capacity limits are included in the


1.12 Multiple RNC handling improvement

If the number of BTS, or load or some other limit exceeds the capacity of RNC,

then user is able to add more RNC's in order to support the required number of

BTS's or load instead of reducing the load, which was the earlier

implementation.





The Traffic Mix rule in RAS05.1 is reverting back to the original rule used in

RAS04. The high level process of RNC dimensioning stays the same (see

diagram below). RAS05.1 does not require static HSDPA pool for HSDPA

anymore.

!

!

"

"!

"

! "

!

!

!

"

"!

"

! "

!

1.13 Fixing the problems found in earlier releases

The “Carriers" from BTS is used and compared against the corresponding limit

of RNC. The intention was to compare the number of cells in the BTS against

the maximum number of cells in the RNC.

.

Documents

RANCP51 Release Note Build 136