P7.0 Network Impact Report PDF

WCDMA RAN P7.
0 Network Impact Report
NETWORK IMPACT REPORT

Copyright
© Copyright Ericsson AB 2008-2009. All rights reserved.
Disclaimer
No part of this document may be reproduced in any form without the written
permission of the copyright owner.
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use
of this document.
1/109 48-HSD 101 02/7 Uen D 2009-02-19

Contents
Contents
1 Introduction 1
1.1 Purpose 1
1.2 Revision Information 1
2 General Impact 2
2.1 Capacity and Performance 2
2.2 Upgrade Procedures 3
2.3 Interface 5
2.4 Operation 6
2.5 Other Features 6
2.6 User Equipment 6
2.7 Other Network Elements 6
3 Hardware Impact 7
3.1 RNC 3820 7
3.2 RNC 3810 9
3.3 RBS 6000 10
3.4 RBS 3000 11
3.5 RXI 12
3.6 OSS-RC 12
4 Summary of Impacts Per Feature 12

4.1 Introduction 12
4.2 System Improvements 12
4.3 Services and Radio Access Bearers 13
4.4 Radio Network Functionality 16
4.5 HSDPA 18
4.6 Enhanced Uplink 20
4.7 Transport Network Functionality 21
4.8 RAN Management 23
4.9 Licensing Principles 24
4.10 Capacity Licenses 25
5 Impact on WCDMA RAN 6.1 - System Improvements 26

5.1 System Improvements in WCDMA RAN 7 26
1/109 48-HSD 101 02/7 Uen D 2009-02-19

WCDMA RAN P7.0 Network Impact Report
6 Impact on WCDMA RAN 6.1 Services and Radio Access

Bearers 28
6.1 Conversational RAB for Multimode AMR Speech 28
6.2 Stand Alone SRB 3.4 kbps 32
6.3 Multiple HSPA PS Interactive RAB Combination 34
7 Impact on WCDMA RAN P6.1 Radio Network

Functionality 35
7.1 MBMS Iub Efficiency 35
7.2 Statistical Observability 36
7.3 Enhanced Layer 2 39
7.4 IF/IRAT Mobility on HSPA 41
7.5 Support for 64QAM 45
7.6 Cell Broadcast Service 47
8 Impact on WCDMA RAN P6.1 HSDPA 49
9 Impact on WCDMA RAN P6.1 Enhanced Uplink 50

9.1 Downlink Power Control for Enhanced Uplink 50
9.2 Enhanced Uplink 2 ms TTI 51
9.3 Advanced Receivers, GRAKE in RBS 54
9.4 Improved CE ladder for E-DCH for RAX R2e 55
10 Impacts on WCDMA RAN P6.1 Transport Network

Functionality 57
10.1 IuCS User Traffic over IP 57
10.2 Common Iub IP host in RBS 59
10.3 Mub Port Integration 61
10.4 Robust Reconfiguration using Rollback 63
11 Impact on WCDMA RAN P6.1 RAN Management 65

11.1 RBS Auto Provisioning 65
11.2 Accessibility 67
12 Impact on WCDMA RAN P6.1 Licensing Principles 71
13 Impact on WCDMA RAN P6.1 Capacity Licenses 71

13.1 HSDPA Users per Cell 71
13.2 Number of Carriers in RRUW/RUW based RBS 73
13.3 Number of 60W power amplifiers in RRUW/RUW based
RBS 74
1/109 48-HSD 101 02/7 Uen D 2009-02-19

13.4 Number of 40W power amplifiers in RRUW/RUW based

RBS 76
13.5 RNC HW R5 Iub Throughput Enhancement 77
14 Summary of Operator Interface Changes 78

14.1 Removed and New/Changed Events 78
14.2 Removed and New/Changed Alarms 78
14.3 Removed and New / Changed Parameters 79
14.4 Removed and New / Changed Counters 79
Glossary 81
Reference List 83
1/109 48-HSD 101 02/7 Uen D 2009-02-19

1/109 48-HSD 101 02/7 Uen D 2009-02-19

Introduction
1 Introduction
1.1 Purpose
The Network Impact Report (NIR) describes how the current release of WCDMA
RAN (WCDMA RAN P7.0) affects the previous release (WCDMA RAN P6.1).
The purpose of the NIR is to provide early information to operators to help

plan the upgrade to the latest system release by describing its affects on
their installed base through the introduction of new functionality, features or
products. As this is a general guideline, there can be network topology issues
or equipment or tools not supplied by Ericsson that must be taken into account
when using this document to assist in planning the network upgrade.
For customers upgrading from WCDMA RAN P6.0 to WCDMA RAN P7.0, the
WCDMA RAN P6.1 Network Impact Report, 2/109 48 HSD101 02/6 shall also
be taken into consideration.
Note: There are separate documents covering OSS-RC features, see

Reference [1] and Reference [6].
Note: Unless specifically stated, WCDMA RAN P7.0 refers to WCDMA RAN
P7.0.X releases, where X determines a specific maintenance release.
1.2 Revision Information

Apart from editorial changes this document has been revised as follows:
Table 1 Revision History

Rev Description
A This is the first preliminary release of this document.
B Updated after review at RFA.
C Updated Accessibility chapter. System Improvements changed to
basic feature.
D Updated to align with WCDMA RAN P7.0.1 release. I.e. include
multivendor aspect to 64QAM and HLR provisioning, updated
accessibility chapter, updated Upgrade chapter, RNC/RBS General
Capacity/Performance, Conversational RAN for MultiMode Speech
operation. 7.0.2 features also added.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 1

2 General Impact
2.1 Capacity and Performance
2.1.1 RNC
In P7 new system improvements are introduced in RNC, for spreading the

load more evenly on the Module MP and DcSP processors and reducing the
need for remoduling RBSs. This has changed the distribution of the load on
the processors in WCDMA RAN P7 compared to WCDMA RAN P6.0/P6.1, and
some customers may notice a slightly higher average load in WCDMA RAN
P7.0 on Module MP, DcSP, CcSP and RANAP MP. The overall effect is an
automatically better tuned system, with evenly distributed load on Module MP,
which gets overall improved characteristics of the RNC.
On highly loaded systems it might be necessary to increase the capacity of the

system before upgrading. This can be done by replacing HW to a later release
or expanding the node.
It is recommended to measure the load on Module MP, DcSP, CcSP and

RANAP MP before upgrading to WCDMA RAN P7.0. To have margins it
is advised to verify that the Busy Hour processing load in WCDMA RAN
P6.0/P6.1, prior to upgrade to P7MD, is below:
• Module MP: 65%
• RANAP MP: 55%
• DC-SP: 55%
• CC-SP: 55%
All cases above refer to the node-average value. If the load is higher than the
above figures a HW upgrade or node expansion should be considered before
upgrading the P7.
2.1.2 RBS
RACH configuration - Due to an error in WCDMA RBS 6.1 and earlier it has
previously been possible to configure up to 4 RACH on certain RAX boards.
The maximum supported number of RACH per RAX board is however 3. From
WCDMA RBS 7.0 it is only possible to configure up to 3 RACH per RAX board.
This release supports the configuration of up to 6 Resource_id on a HS-TX60

board. Up to 3 Resource_id can be configured for HSDPA. Up to 3 Resource_id
can be configured for DCU. 1 Resource_id can be configured for EUL.
2 1/109 48-HSD 101 02/7 Uen D 2009-02-19

General Impact
2.1.3 RXI
None.
2.1.4 OSS-RC
For OSS-RC, see Reference [1]. and Reference [6]
2.1.5 Subscriber Capacity

For subscriber capacity, see impact per feature.
2.1.6 Network Performance

For network performance, see impact per feature.
2.2 Upgrade Procedures

This section describes the prerequisites and upgrade paths for WCDMA RAN.
2.2.1 Prerequisites
To ensure the success of the chosen upgrade path, the following prerequisites
apply:
• The Core Network can be upgraded either before or after WCDMA RAN
for all upgrade paths.
• New hardware must be installed in affected nodes, and old hardware

removed.
Note: All necessary field change orders must have been performed prior
to upgrade.
• The old WCDMA RAN P6.x LKF (Licence Key File) will not work in a
WCDMA RAN P7.0 node. The WCDMA RAN P7.0 product must be
correctly ordered to receive the P7.0 LKFs. Those P7.0 LKFs must be
pre-installed in the from-state before upgrading. Note that before
installing the licences it is important that the system clock for the
node is set correctly. Failure to install the licences shall result in lost
functionality or capacity after the upgrade. An alarm is issued when the
LKF is missing. Concerning license controlled features which were active in
the from-state, the AUE will handle the activation. For new features, the
operator has to activate them, when they are to be used.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 3

Note: It is not possible to run WCDMA RAN P7.0 SW without the LKFs
installed. There is a License Validation Script within the RNC
Upgrade Package that can be used in the upgrade step to check
that nodes have the proper LKF before starting the actual upgrade.
• Capacity licenses in both RBS and RNC must be ordered and installed with
enough capacity in order to retain existing capacity.
2.2.2 Upgrade Paths

When upgrading WCDMA RAN nodes the following order applies:
From WCDMA RAN 6.0 to WCDMA RAN P7.0.
1. Upgrade OSS-RC 5.3/OSS-RC 6.1 to OSS-RC 6.2.
2. Upgrade WCDMA RAN P6.0 RNC to WCDMA RAN P7.0 RNC.
3. Upgrade WCDMA RAN P6.0 RXI to WCDMA RAN P7.0 RXI.
4. Upgrade WCDMA RAN P6.0 RBS to WCDMA RAN P7.0 RBS.
From WCDMA RAN 6.1 to WCDMA RAN P7.0.
1. Upgrade OSS-RC 5.3/OSS-RC 6.1 to OSS-RC 6.2.
2. Upgrade WCDMA RAN P6.1 RNC to WCDMA RAN P7.0 RNC.
3. Upgrade WCDMA RAN P6.1 RXI to WCDMA RAN P7.0 RXI.
4. Upgrade WCDMA RAN P6.1 RBS to WCDMA RAN P7.0 RBS.
Note: In previous RNC releases, each SP device is administrated by a

module MP in the same subrack. This has been changed so that some
SP devices are allocated to module MPs in other subracks, when this
creates better match between module MP capacity and SP capacity.
This change reduces the need to match HW resources within individual
subracks. A secondary effect is more spread in DC load at moderate
overall loads. Due to the introduction of this improvement, the operator
may experience changed behavior (that is, uneven distribution of DC
load) after the upgrade to WCDMA RAN P7.0. This is normal/expected
behavior and no further action is required should it occur.
In preparation for upgrade of RNC to WCDMA RAN P7.0, load and

HW dimensioning aspects should be considered, see RNC Capacity
and Performance.
If upgrading to WCDMA RAN P7.0.2, step 1 should be replaced by,

Upgrade the OSS-RC 5.3/OSS-RC 6.1/OSS-RC 6.2 to OSS-RC 6.3.
The Network Impact Report for OSS-RC 6.3 should also be considered,
see Reference [6].
4 1/109 48-HSD 101 02/7 Uen D 2009-02-19

General Impact
2.3 Interface
2.3.1 Inter-Node Interface

The following interfaces are compliant with the associated 3GPP release:
• Iu, Iub, Iur - 3GPP Release 7
• Iuant - 3GPP Release 7
• Iubc - 3GPP Release 6
Note: In 3GPP release 7 new functionality is introduced in both RAN,

and CN PS and CS to support MBR DL greater than 16 MBs. This
involves the support of IE Maximum Bitrate For Downlink
Extension used in the QoS negotiation between the UE and the
CN PS. It has been observed that some non-Rel-7 UEs fail QoS
negotiation if they receive the Maximum Bitrate For Downlink
Extension. This can occur if the UE requests, Max Bitrate For
Downlink=Subscribed Maximum Bitrate For Downlink and
the subscriber has been allocated an MBR DL >16 MBs in the HLR.
In this scenario Ericsson WCDMA RAN P7.0.1 RNC has implemented

support for the optional IE, Alternative RAB Parameter Values
required for RAB QoS negotiation, as specified in 3GPP 25.413. Upon
receiving a request for MBR DL > 16MBs from the SGSN, the WCDMA
RAN P7.0.1 RNC shall check the UE capabilities and for non Rel-7
UEs, request an alternative RAB configuration. The SGSN includes
this new information in determining the QoS and does not use the
Maximum Bitrate For Downlink Extension. This functionality
is supported by Ericsson SGSN 2008B.
For earlier Ericsson SGSN versions or other vendor SGSN not

supporting Alternative RAB Parameter Values/ QoS Negotation in
RANAP, care must be taken in provisioning subscribers in the
HLR, to ensure only users with Rel-7 compatible UEs are allocated
MBR DL > 16 MBs.
2.3.2 Man-Machine Interface

For impact on man-machine interfaces, see impact per feature.
2.3.3 Open External Interface

For impact on open external interfaces, see Published Management Interface,
Mu.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 5

2.4 Operation
The parameter maxNumEulUsers, which sets the number of EUL users per
cell, is used for licensing per number of EUL users (FAJ 121 1129, Enhanced
Uplink Users per Cell). After upgrade from WCDMA RAN 6.0, this parameter
is set to its default value of 4 irrespective of the licensed capacity. Therefore,
maxNumEulUsers must be set to the desired value after the upgrade,
otherwise the EUL accessibility may be degraded.
For impact concerning operation, see impact per feature.
2.5 Other Features

For impact on other features, see impact per feature.
2.6 User Equipment

For impact on user equipment, see impact per feature.
2.7 Other Network Elements

For impact on other network elements, see impact per feature.
The following Ericsson Core Network Versions are recommended for use with
WCDMA RAN P7.0. These shall be considered as a guideline and exact CN
versions should always be confirmed by the CN CS / CN PS.
6 1/109 48-HSD 101 02/7 Uen D 2009-02-19

Hardware Impact
Table 2 Core Network Versions

Core Network Release Reason
CN CS MSS 5.1 Includes support for feature 'Iu
CS User Traffic over IP' and HLR
support for definition of high bit
rate users for feature 'Support
for 64 QAM'
Note:
For the feature 'Support for 64
QAM' the HLR feature FAJ 122
508/3High Speed Downlink
Packet Access (HSDPA) is
required.
CN PS SGSN 2008B Feature support for High bit
and GGSN R5 rate users, required for feature
FP01 'Support for 64 QAM'
Note:
For the feature ' Support for 64
QAM' it is possible to us GGSN
R4 with the feature '- FAJ
121 0395/1 HSDPA Support
Expansion 3, 16-32Mbps .
For SGSN 2008B the feature,
- FAJ 121 0429, HSDPA
Support, Expansion 3 -
HSDPA , is required for the RAN
feature, 'Support for 64QAM'.
3 Hardware Impact
3.1 RNC 3820
3.1.1 Description
This system release introduces the new RNC 3820 product, a high capacity
radio network controller with a node throughput capacity of 2 Gbit/s (dependent
1/109 48-HSD 101 02/7 Uen D 2009-02-19 7

on applied traffic model) and a radio network control capacity of 768 RBSs
and 2 304 cells.
3.1.2 Impact
3.1.2.1 Capacity and Performance
3.1.2.1.1 Subscriber Capacity
Node throughput capacity increased to 2 Gbit/s.
3.1.2.1.2 Network Performance
None.
3.1.2.2 Hardware
The RNC 3820 is built with 1-3 high performance subracks housed in one
BYB 501 cabinet.
The following hardware units are introduced in RNC 3820:
• High Performance Subrack (HPS) BFD 742 2019
• Fan Unit BKV 106 056/1
• Active Patch Panel (APP)
• Misc. cable kits
• SCB-DF ROJ 119 2334/2
• C-MXB ROJ 208 504/1
• TUB2 ROJ 119 2104/4
• ET-IPG ROJ 119 2345/1
• ET-MF4 ROJ 119 2294/1
• ET-MF41 ROJ 119 504/1
• ET-MC1 ROJ 119 2163/1
• GPB65 ROJ 119 2106/65
• SPB3 ROJ 119 2103/5
3.1.2.3 Implementation
None.
8 1/109 48-HSD 101 02/7 Uen D 2009-02-19

Hardware Impact
3.1.2.4 Interface
3.1.2.4.1 Inter-Node Interface
RNC 3820 introduce 10 Gigabit Ethernet as node external physical interface

(used for Iu, Iur, Iub and Mur). Following interface types are supported:
• 10G BaseT
• Optical (via SFP modules)
RNC 3820 introduces free allocation of Iu, Iur and Iub user plane terminations
(ATM VCC) over subracks.
In RNC 3810, Iu and Iur user plane terminations must still be allocated to the
main subrack only.
3.1.2.4.2 Man-Machine Interface
New Element Manager is introduced for WCDMA RAN P7.0 nodes.
3.1.2.5 Operation
RNC 3820 introduces a new RNC Module Identity (MOC: rncModule, based
on subrack and slot position. RNC 3820 introduces black box configuration
when adding a new IP based RBS, that is, the operator does not need to supply
a preferred subrack.
3.1.2.6 Other Features
None.
3.1.2.7 Other Network Elements
None.
3.2 RNC 3810
3.2.1 Hardware
The following new HW is supported by RNC 3810.
• ET-MF41 ROJ 119 504/1
• SPB3 ROJ 119 2103/5
1/109 48-HSD 101 02/7 Uen D 2009-02-19 9

3.3 RBS 6000
3.3.1 Description
WCDMA RAN P7.0 introduces software support for a new family of
multi-standard RBSs, the RBS 6000 family.
Note: Only WCDMA RBS equipment is described here.
A new remote unit for main remote cabinets is introduced.
3.3.2 Impact
None.
None.
None.
3.3.2.2 Hardware
The following RBS 6000 WCDMA cabinets are supported by WCDMA RAN
P7.0:
• RBS 6102
The RBS 6102 is an outdoor macro RBS which can be equipped with
WCDMA RBS equipment.
• RBS 6201
The RBS 6201 is an indoor macro RBS which can be equipped with
WCDMA RBS equipment.
The RBS 6102 and RBS 6201 can be equipped with the following new hardware
units introduced for RBS 6000 WCDMA:
• RUW 01 0860 KRC 118 51/2
• RUW 01 1960 KRC 118 52/2
• RUW 01 0960 KRC 118 53/2
• RUW 01 2140 KRC 118 40/1
10 1/109 48-HSD 101 02/7 Uen D 2009-02-19

Hardware Impact
• RUW 01 2160 KRC 118 40/2
• RUW 01 21IV 60 KRC 118 54/2
The RUW is a combined radio and filter unit containing a TRX board, Power
Amplifier and Filter Unit. It supports the following frequency bands 850,
900, 1700, 1900, and 2100 MHz, all with 60 W maximum output power.
Note: RBSs equipped with RUWs are subject to capacity licensing of output
power and number of carriers.
• SCU BGM 136 1006/1
The SCU (Support Climate Unit) contains internal and external fans groups
and external alarms.
• SAU ZHY 601 17/1
The SAU (Support Alarm Unit) is a common external alarm unit that is
part of the site equipment.
3.4 RBS 3000

The following main remote RBSs have a new remote hardware unit supported
by WCDMA RAN P7.0:
• RBS 3018
• RBS 3412
• RBS 3418
• RBS 3518
The new hardware units are;
• RRUW 01 0860 KRC 118 46/2
• RRUW 01 0840 KRC 118 46/1
• RRUW 01 1960 KRC 118 47/2
• RRUW 01 1940 KRC 118 47/1
• RRUW 01 0960 KRC 118 48/2
• RRUW 01 0940 KRC 118 48/1
• RRUW 01 18IX 60 KRC 118 49/2
• RRUW 01 18IX 40 KRC 118 49/1
• RRUW 01 21IV 60 KRC 118 50/2
1/109 48-HSD 101 02/7 Uen D 2009-02-19 11

• RRUW 01 21IV 40 KRC 118 50/1
The RRUW is a remote combined radio and filter unit containing a TRX
board, Power Amplifier and Filter Unit. It supports the following frequency
bands 850, 900, 1700, 1900, and 2100 MHz, all with either 40 W or 60
W maximum output power.
Note: RBSs equipped with RRUW are subject to capacity licensing of output
power and number of carriers.
The following RBS 3000 hardware units are now obsolete and not supported
by the RBS WCDMA RAN P7.0 SW:
• RAX R1 ROJ 119 2071/2
• RAX R1 ROJ 119 2071/3
3.5 RXI
None.
3.6 OSS-RC
Concerning OSS-RC HW, see Reference [1].
4 Summary of Impacts Per Feature
4.1 Introduction
This section describes the impact changes to specific features have on the
WCDMA RAN system.
4.2 System Improvements

Table 3 Summary of Impact of System Improvements
Feature Major Minor No Feature Number Comments
Impact Impact Impact
System Improvements X FAJ 121 850
in WCDMA RAN P3
Release
12 1/109 48-HSD 101 02/7 Uen D 2009-02-19

Summary of Impacts Per Feature

in WCDMA RAN P4
Release
in WCDMA RAN P5
Release
in WCDMA RAN P6
Release
in WCDMA RAN P7
Release
4.3 Services and Radio Access Bearers

Table 4 Summary of Impact on Services and Radio Access Bearers
Conversational RAB for X FAJ 121 146
AMR Speech
64 kbps multimedia
Interactive RAB up to X FAJ 121 148
384 kbps Packet Data
Speech and Packet data X FAJ 121 150
RAB combination
Streaming RAB for NT X FAJ 121 153
CS data, 57.6 kbps
Positioning Service, Cell X FAJ 121 244
Accuracy
PS Streaming RAB, 64 X FAJ 121 411
kbps Downlink
Two Times PS X FAJ 121 413
Interactive RAB
Combination
Max Bit Rate Capability X FAJ 121 425
for QoS Profiling
RTT Positioning X FAJ 121 436
1/109 48-HSD 101 02/7 Uen D 2009-02-19 13


Speech and Two Times X FAJ 121 553
PS Interactive RAB
Combination
Speech and 0 kbps X FAJ 121 754
Packet Data Rate
64 kbps CS Multimedia
and 8 kbps Packet Data
RAB Combination
Streaming RAB for up to X FAJ 121 856
128 kbps Packet Data
Flexible Initial Rate X FAJ 121 977
Selection, PS Interactive
Interactive RAB for up to X FAJ 121 980
128 kbps, Uplink
Interactive RAB for up to X FAJ 121 981
384 kbps, Uplink
Speech 12.2 kbps, X FAJ 121 984
Interactive 8 kbps, and
PS Streaming 128 kbps
Speech 12.2 kbps and X FAJ 121 1012
PS Interactive RAB for
up to 384 kbps Downlink
PS Interactive RAB for
up to 128 kbps Uplink
MBMS Broadcast Mode X FAJ 121 1026
with 64 kbps
MBMS Traffic Channel X FAJ 121 1027
128 kbps
MBMS Traffic Channel X FAJ 121 1028
256 kbps
A-GPS Positioning for X FAJ 121 1046
Commercial Services
AMR WB Speech X FAJ 121 1059
AMR WB Speech and X FAJ 121 1060
PS Interactive RAB
Combination
14 1/109 48-HSD 101 02/7 Uen D 2009-02-19


AMR WB Speech and X FAJ 121 1061
HSDPA Interactive RAB
Combination
AMR WB Speech X FAJ 121 1062
and Two Times
PS Interactive RAB
Combination
AMR WB Speech, PS X FAJ 121 1066
Streaming 128 kbps,
and PS Interactive 8
kbps
Conversational RAB for X FAJ 121 985 Impacted
Multimode AMR speech
Stand alone SRB 3.4 X FAJ 121 1158 NEW
kbps
Two Times HSDPA X FAJ 121 1069
Interactive RAB
Combination
Three Times PS X FAJ 121 1071
Interactive RAB
Combination
Three Times HSDPA X FAJ 121 1072
Interactive RAB
Combination
Two Times HSDPA PS
Interactive RAB
Speech 12.2 kbps, PS X FAJ 121 1081
Streaming on HSDPA,
and PS Interactive 8
kbps
PS Streaming and PS X FAJ 121 1083
Interactive on HSDPA
TrFO Support for X FAJ 121 1084
Speech 12.2 kbps
Speech and Multiple X FAJ 121 1103
PS Interactive RAB
Combinations
1/109 48-HSD 101 02/7 Uen D 2009-02-19 15

4.4 Radio Network Functionality

Table 5 Summary of Impact on Radio Network Functionality
Emergency Call X FAJ 121 112
SAI Based (Cell) X FAJ 121 113
Positioning
Admission Control X FAJ 121 114
Cell Update X FAJ 121 116
Channel Switching X FAJ 121 117
Ciphering Mode Control X FAJ 121 118
Congestion Control X FAJ 121 119
Connection Setup and X FAJ 121 120
Release
Downlink Power X FAJ 121 121
Allocation
Downlink Power Drift X FAJ 121 122
Prevention
Enhanced Layer 2 X FAJ 121 1328 NEW
IF/IRAT Mobility on X FAJ 121 1106 NEW
HSPA
Integrity Protection X FAJ 121 123
Paging X FAJ 121 124
Power Control X FAJ 121 125
Radio Connection X FAJ 121 126
Supervision
Soft/Softer Handover X FAJ 121 127
and Cell Reselection
System Information X FAJ 121 128
Distribution
Transparent Message X FAJ 121 129
Transfer
GSM Handover and Cell X FAJ 121 154
Reselection
Shared Network Support X FAJ 121 246
Inter Frequency X FAJ 121 405
Handover & Cell
Reselection
16 1/109 48-HSD 101 02/7 Uen D 2009-02-19


Directed Retry to GSM X FAJ 121 406
UTRAN Registration X FAJ 121 407
Area Handling
Active Queue X FAJ 121 408
Management
Inter Frequency Load X FAJ 121 435
Sharing
Service Differentiated X FAJ 121 550
Congestion Handling
Emergency Call X FAJ 121 748
Re-Direct to GSM
Service Based X FAJ 121 799
Handover
Core Network Hard X FAJ 121 800
Handover
Dynamic PS I/B RAB X FAJ 121 845
Establishment
Inter-Frequency Load X FAJ 121 902
Distribution
Multi-Band Support X FAJ 121 928
Support for MSC in pool X FAJ 121 971
Support for SGSN in X FAJ 121 972
pool
Shared RAN (MOCN) X FAJ 121 974
Channel Switching, X FAJ 121 978
Uplink
Throughput Based X FAJ 121 979
Downswitch
Channel Element X FAJ 121 1007 Obsolete due to
Capacity Ladder for phase out of RAX
DCH with RAX R1 R1.
Domain Specific Access X FAJ 121 1022
Class Barring
Extended Range up to X FAJ 121 1030
80 km
Extended Range up to X FAJ 121 1036
160/200 km
1/109 48-HSD 101 02/7 Uen D 2009-02-19 17


Improved Downlink X FAJ 121 1047
Coverage
Hierarchical Cell X FAJ 121 1055
Structures
Flexible QoS and X FAJ 121 1093
Allocation/Retention
Handling
Traffic Handling Priority X FAJ 121 1094
Fast Power Congestion X FAJ 121 1095
Control
Active TX Chain Gain X FAJ 121 1096
Calibration
SIB 18, Enhanced Inter X FAJ 121 1124
PLMN Mobility
One PLMN ID per X FAJ 121 1301
Frequency
MBMS Iub Efficiency X FAJ 121 1029 NEW
Cell Broadcast Service X FAJ 121 1326 NEW
Support for 64QAM X FAJ 121 1331 NEW
Load Triggered Access X FAJ 121 1332
Class Barring
4.5 HSDPA
Table 6 Summary of Impact on HSDPA
HSDPA Mobility X FAJ 121 801
HSDPA Introduction X FAJ 121 842
HSDPA Mobility, Phase X FAJ 121 860
2
HSDPA TN Optimization X FAJ 121 895
HSDPA 16 QAM X FAJ 121 903
HSDPA Proportional Fair X FAJ 121 904
Scheduler
HSDPA Interactive up to X FAJ 121 905
384/HS
18 1/109 48-HSD 101 02/7 Uen D 2009-02-19


HSDPA Interactive X FAJ 121 906
64/HS RAB
HSDPA Dynamic Code X FAJ 121 967
Allocation
HSDPA Flexible X FAJ 121 968
Scheduler
HSDPA Code X FAJ 121 969
Multiplexing and
HS-SCCH Power Control
HSDPA Interactive
64/HS RAB combination
HSDPA Interactive
384/HS RAB
combination
CQI Adjustment X FAJ 121 1004
HSDPA Introduction X FAJ 121 1033
Package
HSDPA Incremental X FAJ 121 1058
Redundancy
Multiple HSPA PS X FAJ 121 1070 Impacted
Interactive RAB
Combination
HSDPA Max Bit Rate X FAJ 121 1091
for Quality of Service
Profiling
Fast HSDPA Dynamic X FAJ 121 1097
Power Allocation
HSDPA & Enhanced X FAJ 121 1114
Uplink Service Indicator
HSDPA QoS Scheduler X FAJ 121 1115
HSDPA PS Streaming X FAJ 121 1303
and Multiple PS
Interactive RAB
Combinations
1/109 48-HSD 101 02/7 Uen D 2009-02-19 19


Speech and Multiple X FAJ 121 1304
HSDPA PS Interactive
RAB Combinations
Speech 12.2 kbps, X FAJ 121 1305
HSDPA PS Streaming
and Multiple PS
Interactive RAB
Combinations
4.6 Enhanced Uplink

Table 7 Summary of Impact on Enhanced Uplink
Downlink Power Control X FAJ 121 1345 NEW
for Enhanced Uplink
EUL Introduction X FAJ 121 970
Enhanced UL Mobility X FAJ 121 1002
Enhanced Uplink Start X FAJ 121 1023
Package
Enhanced Uplink, TN X FAJ 121 1054
Optimization
EUL QoS Scheduler X FAJ 121 1111
EUL up to 6 Cell Carriers X FAJ 121 1112
EUL Scheduler X FAJ 121 1135
Enhancements
Channel Element Ladder X FAJ 121 1157
for E-DCH with RAX R2
Enhanced Uplink, 2 ms X FAJ 121 1317 Enhanced
TTI
Enhanced Uplink X FAJ 121 990
Interactive RAB
Advanced Receivers, X FAJ 121 1333 NEW
GRAKE in RBS
Improved CE ladder for X FAJ 121 1334 NEW
E-DCH on RAX R2e
20 1/109 48-HSD 101 02/7 Uen D 2009-02-19

4.7 Transport Network Functionality

Table 8 Summary of Impact on Transport Network Functionality
Built in 16 Gbps Packet X FAJ 121 130
Switch in RNC, RBS,
and RXI Nodes
ATM PVC/PVP X FAJ 121 131
Support including
Cross-Connect
Dynamic AAL2 X FAJ 121 132
Connections
Permanent AAL5 X FAJ 131 133
Connections for Control
Plane Traffic
ATM on Fractional X FAJ 121 134
for 2G Transmission
Sharing
Circuit Emulation X FAJ 121 135
over ATM for 2G
Transmission Sharing
Transport Redundancy X FAJ 121 136
Network Synchronizati X FAJ 121 137
on
Node Synchronization X FAJ 121 138
RAN Topologies X FAJ 121 364
ATM Interfaces in RAN X FAJ 121 368
Inverse Multiplexing X FAJ 121 369
over ATM, IMA
System Integrated X FAJ 121 440
GPS Network
Synchronization
ATM RAN Transport X FAJ 121 734
Aggregation
AAL2 Switching for X FAJ 121 735
Transport Aggregation
AAL2 Switching X FAJ 121 736
Capacity Expansion
RAN Transport Quality X FAJ 121 737
of Service Separation
1/109 48-HSD 101 02/7 Uen D 2009-02-19 21


Transmission Power X FAJ 121 836
Priority
Mub Routing in RXI X FAJ 121 931
AAL2 Path with UBR X FAJ 121 940
Robust Transport X FAJ 121 962
Configuration
DL Flow Control for PS X FAJ 121 963
Interactive/Background
on DCH
IP Interfaces in RAN X FAJ 121 964
Configurable Transport X FAJ 121 966
Bearer QoS Class
SS7 over IP X FAJ 121 973
Iu-PS User Plane over X FAJ 121 976
IP
IMA Bandwidth X FAJ 121 1086
Adaptation
Iub Optimization X FAJ 121 1098
Iub Transport Split for X FAJ 121 1101
Best Effort Data
System Integrated X FAJ 121 1109
Ethernet Switch
Iub over IP/Ethernet in X FAJ 121 1118
RNC
Iur User Plane over IP X FAJ 121 1120
Iub over IP/Ethernet in X FAJ 121 1132
RBS
Network Synch Server X FAJ 121 1154
for IP Transport
Network Synch Client X FAJ 121 1155
for IP Transport
Iub over IP/Ethernet X FAJ 121 1167
Using Pseudo Wire
ATM and IP Dual Stack X FAJ 121 1221
Support in RNC
ATM & IP dual stack in X FAJ 121 1311
RBS
22 1/109 48-HSD 101 02/7 Uen D 2009-02-19


IuCS User Traffic over X FAJ 121 1119 NEW
IP
Mub Port Integration X FAJ 121 1408 NEW in WCDMA
RAN P7.0.2
Common Iub IP host in X FAJ 121 1461 NEW in WCDMA
RBS RAN P7.0.2
Robust Reconfiguration X FAJ 121 1463 NEW in WCDMA
using Rollback RAN P7.0.2
4.8 RAN Management

Table 9 Summary of Impact on RAN Management
Feature Major Minor No Feature number Comments
Accessibility X FAJ 121 101 Enhanced
Backup X FAJ 121 102
Configuration X FAJ 121 103
Management
Fault Management X FAJ 121 104
Performance X FAJ 121 105
Management
Product Inventory X FAJ 121 106
Security Management X FAJ 121 107
Software Management X FAJ 121 108
Site LAN X FAJ 121 110
Documentation X FAJ 121 111 See Library Revision
Information
Statistical Observability X FAJ 121 409 Enhanced
Measurement Function X FAJ 121 514
Radio Environment
Statistics
Recording Observability X FAJ 121 1001
for General
Performance Event
Handling
1/109 48-HSD 101 02/7 Uen D 2009-02-19 23


Configurable Priority X FAJ 121 1003
of Neighbour Cell
Relations
Drifting RNC X FAJ 121 1089
Observability
RBS Soft Lock X FAJ 121 1123
Release Locked X FAJ 121 1156
Mobiles when Iu-CS
Is Down
Support for 3GPP X FAJ 121 1173
Compatible RET
Antennas
RBS Auto Provisioning X FAJ 121 1369 NEW
Support for 3GPP X FAJ 121 1142
Compatible TMAs
4.9 Licensing Principles

Table 10 Summary of Impact on Licensing Principles
License Control X FAJ 121 437 Enhanced
Emergency Unlock X FAJ 121 961
Reset
Administrative X FAJ 121 1006
Correction for Licensing
Delayed Activation of X FAJ 121 1009
Capacity Control
License Control for X FAJ 121 1051
Features
Emergency Unlock X FAJ 121 1226
RNC Capacity License X FAJ 121 1321
Control
24 1/109 48-HSD 101 02/7 Uen D 2009-02-19

4.10 Capacity Licenses

Table 11 Summary of Impact on Capacity Licenses
RBS Channel Elements X FAJ 121 072
in Uplink
RBS Channel Elements X FAJ 121 073
in Downlink
HSDPA Codes Per Cell X FAJ 121 0332
RNC Throughput X FAJ 121 1008
Capacity
HSDPA Cell Carriers X FAJ 121 1010
HSDPA Users per Cell X FAJ 121 1011 Enhanced
RNC User Capacity X FAJ 121 1049
Enhanced Uplink, 1.4 X FAJ 121 1050
Mbps Capacity
Enhanced Uplink Users X FAJ 121 1129
per Cell
RNC HW R5 Capacity X FAJ 121 1322
Enhancement
RNC HW R4 Capacity X FAJ 121 1323
Enhancement
RNC R4-R5 Upgrade X FAJ 121 1324
Capacity Enhancement
Number of carriers in X FAJ 121 1344 NEW
RUW/RRUW based
RBS
40W Output power in X FAJ 121 1347 NEW
RUW/RRUW based
RBS
60W Output power in X FAJ 121 1348 NEW
RUW/RRUW based
RBS
Output Power Basic X FAJ 121 1343
(Default 20W),
RNC HW R5 X FAJ 121 1391 NEW
Iub Throughput
Enhancement
1/109 48-HSD 101 02/7 Uen D 2009-02-19 25

5 Impact on WCDMA RAN 6.1 - System

Improvements
5.1 System Improvements in WCDMA RAN 7
5.1.1 Description
This is new basic feature in the in WCDMA RAN P7.0.
This feature contains all enhancements and improvements that are not covered
by other features for the WCDMA RAN 7 release and are of commercial value.
Following enhancements and improvements are added:
• Compliance with 3GPP Release 7, for functions that are implemented
• Reduced downtime at RNC restart
• ISL Load Control
• Improved In-Service Performance
• Node-level load balancing in the RNC
5.1.2 Impact
None.
Improvements to streamline the RNC-internal procedures during restart,

resulting in shorter restart times have been introduced.
In RNC a new load control for the Inter-Subrack Links has been introduced
to provide a reliable protection from ISL overload. The mechanism regularly
measures the load on each ISL. When the load is approaching the link capacity,
the Packet Data Router will reduce the user plane traffic to avoid overload. This
ensures robust behavior also in very high traffic situations and allows for a
Maximum Iub throughput of up to 1200 Mbps.
In-Service Performance for the RNC is improved by introduction of memory pool

protection of USAAL. This is done by flow control of NBAP-C/D messages sent
26 1/109 48-HSD 101 02/7 Uen D 2009-02-19

Impact on WCDMA RAN 6.1 - System Improvements
from RBS to RNC. This features ensures that the USAAL server will not fill up
its pool memory and cause a module restart in RNC. Traffic overload protection
involves a flow control mechanism allowing USAAL to check if NBAP-D
and NBAP-C are ready to receive more messages. The USAAL, server in
communication with NBAP, will add and receive flow control information
(sequence numbers) in the signal flow, such that it can protect against buffer
overruns and prevent restart during heavy traffic.
The Module MP processor load balancing mechanism is introduced in P7 which

will balance the load within the complete RNC, essentially removing the need
for frequent remoduling (moving RBSs between subracks). This will increase
the utilization of the RNC HW. After upgrade to WCDMA RAN P7.0 distribution
of load across Main and Extension subracks may change. This is normal
behaviour due to that the load is now balanced across all subracks.
5.1.2.2 Hardware
None.
None.
5.1.2.4 Interface
3GPP Release 7 is introduced and supported for Iub, Iu and Iur interfaces.
See 3GPP SoC.
None.
5.1.2.5 Operation
The WCDMA RAN P7.0 CPI introduces a new concept, a library collection.
The change presents all the documentation for all WCDMA RAN nodes in one
view providing the end user with better navigation between the related CPI
products for the WCDMA RAN release. It also provides support for multi-library
download and searching multi-libraries and removes the need for having
several browsers open with various node libraries in parallel. The change does
not impact the end user, in that no actions need to be taken. The enhancement
is graphical and presents a coherent view of all WCDMA RAN CPI.
None.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 27

None.
6 Impact on WCDMA RAN 6.1 Services and

Radio Access Bearers
6.1 Conversational RAB for Multimode AMR Speech
6.1.1 Description
This optional feature, Conversational RAB for Multimode AMR Speech, is
enhanced in WCDMA P7.0.
This feature provides the possibility to increase the capacity for the speech
service by making it possible to use lower codec rates for speech when there
is a high load in the radio network. The feature also allows for increasing the
speech coverage by using the lower speech codec rates.
The feature provides a conversational Radio Access Bearer (RAB) for multi
mode AMR speech with the following rates:
• 12.2 kbps
• 7.95 kbps
• 5.9 kbps
• 4.75 kbps
The operator can choose between two different realization alternatives for this
RAB, that is, either single rate or multi-rate .
The multi-mode AMR speech RAB, with single rate radio bearer, is enabled
over the radio interface with separate radio bearers for the different rates,
providing a higher spreading factor for the two lower rates. The 12.2 and 7.95
kbps rates use the downlink spreading factor of 128, while the 5.9 and 4.75
kbps rates a spreading factor of 256. The higher spreading factor for the two
lower codec rates also gives improved code utilization.
The multi mode AMR speech RAB with multi-rate radio bearer is enabled
over the radio interface with a radio bearer combination that has a downlink
spreading factor of 128 and that can change rate by just changing the transport
28 1/109 48-HSD 101 02/7 Uen D 2009-02-19

Impact on WCDMA RAN 6.1 Services and Radio Access Bearers
format combination. It also allows both the core network and the mobile to
instantaneously change to any of the allowed rates. This allows the mobile to
autonomously change to a lower speech codec rate due to uplink coverage.
The core network assigns this multi-mode AMR RAB by making a RAB
assignment with these 4 rates. The selection between the two alternatives
(that is, single or multi rate radio bearer) is controlled by the operator on a cell
level. The selection is done at RAB assignment and the selected alternative will
not change due to mobility.
Rate selection is done at the assignment of the RAB by checking the radio
network load (both uplink and downlink) of the cells in the active set in the
SRNC with operator configurable thresholds (as per existing functionality).
These thresholds provide the possibility to select at which load in the radio
network the different rates shall be selected and also the possibility to have
some rates excluded from the selection. The selected rates are the same in
uplink and downlink. In order to limit the lowest rate to be selected, the core
network may also set one of the rates as the Guaranteed Bit Rate (GBR) value
in the RAB assignment (Note that this is only valid for single-rate, in multi-rate
UE can always select all rates as long as the maximum rate is not exceeded).
For the multi-mode AMR speech RAB with single rate radio bearer, the selected
rate is what is then set up to the mobile, while for the multi-mode AMR speech
RAB with multi rate radio bearer, the selected rate is the maximum rate and
both the core network and the UE can use one of the lower rates at any time. In
case the multi-rate radio bearer alternative is selected this feature also gives the
AMR speech multi rate radio bearer for most of the speech RAB combinations
in the WCDMA RAN P7.0 release. The exceptions here are those that would
exceed the 64 or 128 transport format combinations in uplink or downlink
respectively, which is more than the normal UEs can handle. This means that
in WCDMA RAN P7.0 release, the following RAB combinations will have the
AMR multi rate radio bearer 12.2, 7.95, 5.9, 4.75) in the RB combinations:
• Speech + (1-3)x PS interactive on both rel 99 and HSDPA
• Speech + PS streaming on rel 99
• Speech + PS streaming on HSDPA except for the 32/HS and 128/HS

streaming cases and the combinations with multiple interactive bearers
In order to have the possibility to select a particular rate, the support mode
version 1 of the Iu framing protocol is used.
See CPI Connection handling for more information.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 29

6.1.2 Impact
When compared to the single rate radio bearer alternative, multi-mode multi
rate can lead to decreased Accessibility in speech capacity limited cells due to
that SF256 can not be used in DL for the two lowest rates.
In high load situations there will be an improved speech capacity in the radio
network by reducing the speech codec rate. The feature enables the higher
speech codec rates when the radio network load allows for that.
Improved code utilization is introduced due to the higher spreading factor for
the two lower AMR rates (applicable for the single rate radio bearer alternative).
Improved coverage is possible for the speech service with the lower speech
codec rates.
Introduces possibility for the UEs to adapt between the different uplink codec
rates due to uplink coverage (applicable for the multi- rate radio bearer
alternative).
6.1.2.2 Hardware
None.
In WCDMA RAN P6.x the recommended value for maxSduSize was

increased from 600 octets to 1024 octets to handle larger NBAP-D messages.
This maxSduSize(1024) for NBAP-D is valid for WCDMA RAN P6.x and
onwards releases. This recommendation can be found in CPI "Transport
Network Configuration" 1/1553-HSD 101 02/7, chapter SAAL-UNI for Iub .
The recommended value (1024) should be implemented before activating
AmrNbMultiMode on ATM sites.
6.1.2.4 Interface
Iu UP version 1 must be used
None.
30 1/109 48-HSD 101 02/7 Uen D 2009-02-19

6.1.2.5 Operation
The feature is under license control.
The following parameter can be set on cell level by the operator,

amrNbSelector, to enable AMR NB MM. Single-rate is the default
configuration.
New Erlang and traffic volume counters for AMR MM are introduced;
• pmSumAmrNbMmRabEstablish
• pmSamplesAmrNbMmRabEstablish
• pmSumBestAmrNbMmRabEstablish
• pmSamplesBestAmrNbMmRabEstablish
• pmUlTrafficVolumeAmrNbMm
• pmDlTrafficVolumeAmrNbMm
Following GPEH Parameter is updated to include speech configuration:
• EVENT_PARAM_SOURCE_CONNECTION_PROPERTIES
• EVENT_PARAM_TARGET_CONNECTION_PROPERTIES
For the multirate case existing parameters are used to configure at which load
in the radio network the different rates shall be selected as maximum rate and
thereby having the higher rates excluded from the selection.
Note also that the behaviour of existing counters, pmSumBestAmr12200R

abEstablish, pmSamplesBestAmr12200RabEstablish is impacted
by the introduction of this feature. The stepping of these counters is now
dependent on both the request from the core network and the settings of
the following parameter in the RNC, amrNbSelector and the feature state,
AmrNbMultiMode.
E.g. if the Core Network requests a Single-Mode speech (i.e.

Requests only one speech rate), then 12.2 is setup and the counter
pmSumBestCs12Establishis stepped. However if the CN requests a
Multi-Mode multi-rate speech (i.e. Requests multiple speech rates), then the
parameter amrNbSelectoris checked. If amrNbSelector=Single-Rate
then the speech call can be setup - in theory - in one of the following, 12.2,
7.95, 5.9, 4.75. If 7.95, 5.9, 4.75 are not licensed, the speech call is setup
on 12.2, and this time the counter pmSumBestAmr12200RabEstablish
is stepped. It is therefore recommended, in order to monitor the
average number of speech users in the network, to use both
the "amr12200" counters (pmSumBestAmr12200RabEstablish,
pmSamplesBestAmr12200RabEstablish) and the Cs12 counters
(pmSumBestCs12Establish, pmSamplesBestCs12Establish). The formulas can
be found in the CPI Radio Network KPI, 120/1553-HSD10102/7.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 31

This feature requires the feature Conversational RAB for AMR Speech
FAJ 121 146.
The value of this feature is increased if paired with the feature Stand Alone
SRB 3.4 kbps that adds possibility to use lower signalling rates and extend
the SRB coverage in a cell to match the coverage area of speech calls when
the low rate speech codec is used.
When this feature is activated and the parameter amrNbSelector is set to

AMR NB MM and the feature Measurement Function Radio Environment
StatisticsFAJ 121 514 (RES) is used, there is a limitation in that RES will not
support the recording of AMR NB MM (there will be fewer samples for the
RES service speech).
This feature requires support in the Core Network. Support for AMR MM is
required in the UE.
6.2 Stand Alone SRB 3.4 kbps
6.2.1 Description
The optional feature Stand Alone SRB 3.4 kbps is new in WCDMA RAN P7.0.
The possibility to have a stand alone SRB with the rate 3.4 kbps instead of
the default SRB rate of 13.6 kbps is introduced. SRB 3.4 kbps requires less
resources than SRB 13.6 kbps, which means the coverage and capacity can be
improved. In particular, if SRB 3.4 kbps is combined with using a lower rate
speech codec of AMR NB or AMR WB, the coverage of the speech service
can be improved.
For more information, see Connection Handling.
6.2.2 Impact
None.
32 1/109 48-HSD 101 02/7 Uen D 2009-02-19

When the SRB 3.4 kbps is used this will increase the SRB stand alone coverage
and the number of simultaneous users of the SRB in a cell (consumes less
resources/lower data speed). The increase in coverage area can lead to an
increase in Accessibility.
Since the SRB 3.4 kbps has a lower signalling rate, the call setup signalling will
take longer (estimated 1-1.5s increase) than when SRB 13.6 kbps is used. The
choice to use SRB 3.4 or SRB 13.6 kbps is operator configurable on cell level.
The increased time on SRB could result in decreased retainability.
6.2.2.2 Hardware
None.
None.
6.2.2.4 Interface
None.
None.
6.2.2.5 Operation
The feature is under license control.
A cell parameter, standAloneSrbSelector, is used to select if SRB 3.4 or

SRB 13.6 kbps will be used in the cell.
New PM counters are introduced;
New Retainability counters for SRB
• pmNoNormalReleaseSrbOnly34
• pmNoSystemReleaseSrbOnly34
• pmNoNormalReleaseSrbOnly136
• pmNoSystemReleaseSrbOnly136
1/109 48-HSD 101 02/7 Uen D 2009-02-19 33

New Erlang counters for SRB
• pmSumSrbOnly34
• pmSamplesSrbOnly34
• pmSumBestSrbOnly34
• pmSamplesBestSrbOnly34
• pmSumBestRrcOnlyEstablish
• pmSamplesBestRrcOnlyEstablish
New Traffic volume counters for SRB
• pmDlTrafficVolumeSrb34
• pmUlTrafficVolumeSrb34
• pmDlTrafficVolumeSrb136
• pmUlTrafficVolumeSrb136
This feature is not dependent on any other feature, but the value of this feature
is increased if paired with the feature Conversational RAB for AMR Speech
that adds possibility to use lower speech coding rates and extend the speech
service coverage in a cell to match the low rate SRB.
UEs supporting the feature are required.
6.3 Multiple HSPA PS Interactive RAB Combination
6.3.1 Description
The optional feature Multiple HSPA PS Interactive RAB Combination is

impacted in WCDMA RAN P7.0 with the introduction of support for Enhanced
Uplink , 2 ms TTI. See also Enhanced Uplink , 2ms TTI.
34 1/109 48-HSD 101 02/7 Uen D 2009-02-19

Impact on WCDMA RAN P6.1 Radio Network Functionality
7 Impact on WCDMA RAN P6.1 Radio

Network Functionality
7.1 MBMS Iub Efficiency
7.1.1 Description
The new optional feature MBMS Iub Efficiency, is introduced in WCDMA P7.0.
For one MBMS Session and for cells on the same frequency, one Iub transport
bearer can be used for MBMS user plane transmission from RNC to RBS in
which the distribution to affected cells is done.
When the feature is not used, separate Iub Transport bearers are set up for
each cell and MTCH, either on AAL2 or IP transport. When the feature is used,
a common Iub transport bearer is used for all cells in the RBS belonging to the
same MBMS session. This solution is based on 3GPP release 7 NBAP.
For more information see MBMS.
7.1.2 Impact
None.
The feature uses less Iub capacity when broadcasting the same session to more
than one cell within an RBS. This frees up capacity for other usage. For a 3-cell
site, when using Iub Transport bearers on AAL2, up to 1.6 Mbit/s can be saved.
7.1.2.2 Hardware
HW requirements are the same as for MBMS in general.
This feature only works in conjunction with MBMS. As soon as the feature is
active, the RBS tries to set up only one transport bearer per session. The use
of a common Iub connection is restricted to within one frequency bearer.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 35

7.1.2.4 Interface
When MBMS is activated in the network the use or non use of the feature
impacts Iub dimensioning.
None.
7.1.2.5 Operation
Iub efficiency is activated in RBS. Activation and deactivation

of MBMS Iub Efficiency is made using the RBS parameter
featureStateMbmsIubEfficiency.
This feature only works in conjunction with MBMS.
None.
7.2 Statistical Observability
7.2.1 Description
The optional feature Statistical Observability, is enhanced in WCDMA RAN
P7.0.
Counters for new and enhanced optional features, for example 64 QAM and
Cell Broadcast Service have been added.
In RBS the possibility to view the blocked calls caused by shortage of licensed
resources have been added. It will also be possible to observe the level
of statistical utilization of the licensed resources in an enhanced way. The
licensed resources in RBS covered are the following:
• Channel elements
• HS-DSCH users
• HS-PDSCH codes
• E-DCH users
36 1/109 48-HSD 101 02/7 Uen D 2009-02-19

RBS capacity status can be monitored and resources managed accordingly.

Taking necessary action will ensure that subscribers experience less access
blocking and dropped calls.
7.2.2 Impact
The operator will be able to predict shortage of licensed capacity and thereby
prepare the system for higher subscriber capacity.
The experienced quality of the network will improve as fewer calls will be
blocked caused by shortage of RBS and RNC resources.
7.2.2.2 Hardware
The enhanced observability will predict need for investment in more licenses of
channel elements, but also hardware if all available capacity is already utilized.
None.
7.2.2.4 Interface
None.
Maintenance personnel will be informed when licensed resources are scarce

and can act accordingly to offset the shortfall.
7.2.2.5 Operation
The observability is supplied with the licenses it monitors. In addition the

following new RBS counters are introduced monitoring the RBS capacity status:
• pmCapacityDlCe
• pmCapacityAllocAttDlCe
• pmCapacityAllocRejDlCe
1/109 48-HSD 101 02/7 Uen D 2009-02-19 37

• pmSumCapacityDlCe
• pmSumSqrCapacityDlCe
• pmSamplesCapacityDlCe
• pmCapacityUlCe
• pmCapacityAllocAttUlCe
• pmCapacityAllocRejUlCe
• pmSumCapacityUlCe
• pmSumSqrCapacityUlCe
• pmSamplesCapacityUlCe
• pmCapacityHsDschUsers
• pmCapacityAllocAttHsDschUsers
• pmCapacityAllocRejHsDschUsers
• pmSumCapacityHsDschUsers
• pmSumSqrCapacityHsDschUsers
• pmSamplesCapacityHsDschUsers
• pmCapacityHsPdschCodes
• pmCapacityAllocAttHsPdschCodes
• pmCapacityAllocRejHsPdschCodes
• pmSumCapacityHsPdschCodes
• pmSumSqrCapacityHsPdschCodes
• pmSamplesCapacityHsPdschCodes
• pmCapacityEDchUsers
• pmCapacityAllocAttServEDchUsers
• pmCapacityAllocRejServEDchUsers
• pmSumCapacityServEDchUsers
• pmSumSqrCapacityServEDchUsers
• pmSamplesCapacityServEDchUsers
• pmCapacityNodeBDlCe
38 1/109 48-HSD 101 02/7 Uen D 2009-02-19

• pmCapacityNodeBUlCe
• pmUsedHsPdschCodes
None.
None
7.3 Enhanced Layer 2
7.3.1 Description
This optional feature Enhanced Layer 2 is new in WCDMA RAN P7.0.
Enhanced layer 2 (EL2), is the collective name for the following RLC and MAC
level functionality that have been introduced in the 3GPP release 7:
• Flexible RLC - Permits transmission of RLC AM PDUs with varying size as

opposed to legacy RLC where PDUs are of fixed predetermined size
• Enhanced MAC-hs (abbreviated MAC-ehs) - Differs from legacy MAC-hs

by allowing segmentation of SDUs and multiplexing of data from multiple
Priority Queues (PQs).
To support EL2 data transport in the transport network, a new Iub frame
protocol (type 2) is also introduced. In WCDMA RAN P7 EL2 is supported for
interactive PS RABs on HS-DSCH in conjunction with EUL.
See HSDPA User Plane for more information.
7.3.2 Impact
None.
Improved Iub bandwidth utilization.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 39

Removes throughput limitations which otherwise would have posed a

throughput bottleneck for services such as 64 QAM (feature 'Support for
64QAM').
In situations where the feature is not rolled out in all cells in the network there
will be scenarios where there will be a reconfiguration between EL2 and legacy
L2 (fixed size RLC and MAC-hs) which will have a performance impact for an
EL2 user since the data lost during the reconfiguration will have to be re-sent by
higher layers (for example TCP). There is no impact on Legacy Layer 2 traffic.
Note: Only some RAB combinations support EL2 and during transition to or
from these there will be a similar impact on performance due to the
need to re-configure L2.
7.3.2.2 Hardware
None.
Enhanced layer 2 results in a lower TN overhead due to the higher RLC window
size. Therefore TN dimensioning aspects should be considered.
7.3.2.4 Interface
For multivendor scenarios, there may be a need to configure parameter

maxMacdPduSizeExtended for the Iur link to comply to limitations in other
vendors network if these do not support RLC PDU sizes as large as in Ericsson
network.
None.
7.3.2.5 Operation
EL2 is an optional feature that is handled with a license key. There is one
license per RBS. Provided that the there is a valid license key installed for EL2,
EL2 may be activated/deactivated on cell level by the operator with a new
parameter, featureStateEnhancedLayer2. OSS and scripts are used to
enable feature on RNS level or for individual cells. It is also possible to turn
the feature on/off using the RBS Element Manager.
None.
40 1/109 48-HSD 101 02/7 Uen D 2009-02-19

UEs supporting EL2 are required.
7.4 IF/IRAT Mobility on HSPA
7.4.1 Description
The IF/IRAT Mobility on HSPA feature is a new optional feature introduced
in WCDMA RAN P7.0.
The feature improves end-user throughput in case of mobility between

EUL/HSDPA cells on different frequencies or to GSM, as no need to down
switch to DCH/DCH is required.
Support is introduced for Inter-frequency and Inter-RAT mobility for RAB

combinations mapped on HSPA channels, that is:
• IRAT and IF handover evaluation using compressed mode measurements
• IRAT handover to GSM, IRAT Cell Change to GSM
• IF handover execution
For IFHO the target cell must have the same HS and EUL capabilities as used
in the source configuration. A RAB combination mapped on EUL/HS can for
example only be handed over to a target cell that is both HS and EUL capable.
If the capabilities of the target cell do not match the current configuration in
the source cell a downswitch to either HS/DCH or DCH/DCH is performed
prior to the IFHO execution
IF and IRAT compressed mode measurements are only supported for E-DCH
10 ms TTI (and not for E-DCH 2 ms TTI). Compressed mode on HSDPA and
E-DCH is implemented according to 3GPP 25.212 and 25.214.
See Handover for more information.
7.4.2 Impact
None.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 41

The feature improves end-user throughput in case of mobility between

EUL/HSDPA cells on different frequencies or to GSM, as no need to down
switch to DCH/DCH is required.
When compressed mode is activated a lower data throughput (in comparison to

normal HS / EUL throughput) can be expected for PS Interactive RBs mapped
on HS-DSCH and E-DCH. For transmission on HS-DSCH an additional delay
of 12-14 ms can be expected whenever a CM gap is scheduled on DPCH.
Due to that more users shall remain on HS/EUL longer (instead of switching
down to DCH) and will have lower throughput when in compressed mode, the
average EUL/HS throughput in the cell may decrease.
7.4.2.2 Hardware
None.
When this feature is activated the down switch to DCH due to poor quality
is no longer triggered for RAB combinations mapped on HSPA channels.
Instead existing algorithms to start compressed mode measurements are
applied. This behavior is valid for all settings (ON/OFF) of the parameter
hsToDchTrigger.poorQualityDetected.
Furthermore, if poor quality has been detected on DCH all state transitions to
HSPA channels are allowed when this feature is activated.
Note: If HS/EUL over Iur is activated on the IurLink, RNSs (both RNCs and
RBSs) on either side of the IurLInk , should be upgraded to WCDMA
RAN 7.0 before activation of this feature.
7.4.2.4 Interface
The feature is supported over Iur.
None.
7.4.2.5 Operation
The feature is under license control. One single license on RNC is used for
activation of the feature for both HS and EUL.
42 1/109 48-HSD 101 02/7 Uen D 2009-02-19

The following (existing) parameter settings can be set for RAB Combinations
containing HSDPA and/or EUL to decide which measurements are started:
• FddGsmHoSupp
• FddIfHoSupp
• hoType
The following new mobility counters are defined for the RAB types HSDPA
and EUL.
• pmNoOutIratCcAttHs : Number of PS IRAT Cell Change attempts for a

UE on dedicated channels with RB/RBs mapped on HSDPA in downlink.
• pmNoOutIratCcReturnOldChHs : Number of PS Inter-RAT Cell Change

attempts for a UE on dedicated channels with RB/RBs mapped on HSDPA
in downlink where the UE returns to old channel.
• pmNoOutIratCcSuccessHs : Number of successful PS Inter-RAT Cell

Change attempts for a UE on dedicated channels with RB/RBs mapped on
HSDPA in downlink.
• pmNoOutIratCcAttEul : Number of PS IRAT Cell Change attempts for a

UE on dedicated channels with RB/RBs mapped on EUL in uplink.
• pmNoOutIratCcReturnOldChEul : Number of PS Inter-RAT Cell

Change attempts for a UE on dedicated channels with RB/RBs mapped on
EUL in uplink where the UE returns to old channel.
• pmNoOutIratCcSuccessEul : Number of successful PS Inter-RAT Cell

Change attempts for a UE on dedicated channels with RB/RBs mapped
on EUL in uplink.
• pmAttNonBlindIfhoPsIntHs : Number of attempted non-blind outgoing

Inter-frequency handovers for RAB = PS Interactive mapped on HSDPA
in downlink.
• pmAttNonBlindIfhoPsIntEul : Number of attempted non-blind

outgoing Inter-frequency handovers for RAB = PS Interactive mapped on
EUL in uplink.
• pmAttNonBlindIfhoPsStrHs : Number of attempted non-blind outgoing

Inter-frequency handovers for RAB = PS Streaming mapped on HSDPA
in downlink.
• pmSuccNonBlindIfhoPsIntHs : Number of successful non-blind

HSDPA in downlink.
• pmSuccNonBlindIfhoPsIntEul :Number of successful non-blind

EUL in uplink.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 43

• pmSuccNonBlindIfhoPsStrHs : Number of successful non-blind

outgoing Inter-frequency handovers for RAB = PS Streaming mapped on
HSDPA in downlink.
• pmFailNonBlindIfhoFailRevPsIntHs : Number of failed non-blind

outgoing Inter-frequency handovers, where the UE fails to return to the
present active set, for RAB = PS Interactive mapped on HSDPA in downlink.
• pmFailNonBlindIfhoFailRevPsIntEul : Number of failed non-blind

present active set, for RAB = PS Interactive mapped on EUL in uplink.
• pmFailNonBlindIfhoFailRevPsStrHs : Number of failed non-blind

present active set, for RAB = PS Streaming mapped on HSDPA in downlink.
• pmFailNonBlindIfhoRevPsIntHs : Number of failed non-blind

outgoing Inter-frequency handovers, where the UE returns to the present
active set, for RAB = PS Interactive mapped on HSDPA in downlink.
• pmFailNonBlindIfhoRevPsIntEul : Number of failed non-blind

outgoing Inter-frequency handovers, where the UE returns to the present
active set, for RAB = PS Interactive mapped on EUL in uplink.
• pmFailNonBlindIfhoRevPsStrHs : Number of failed non-blind

present active set, for RAB = PS Streaming mapped on HSDPA in downlink.
Retainability KPIs may be impacted upon activating the feature if non fully
3GPP compliant UEs exist in the network, which do not support compressed
mode on EUL.
This feature requires the optional RAN features:
• GSM Handover and Cell Reselection FAJ 121 154
• Inter Frequency Handover & Cell Reselection FAJ 121 405
• Relevant HSPA features
UEs supporting IF/IRAT on HSPA are required.
44 1/109 48-HSD 101 02/7 Uen D 2009-02-19

7.5 Support for 64QAM
7.5.1 Description
This optional feature Support for 64QAM is introduced in WCDMA RAN P7.0.
Support for 64QAM introduces an additional modulation method, 64QAM,

on the HS-PDSCH. The purpose of 64QAM is to increase the peak bit rate.
64QAM carries 6 data bits/symbol compared with 4 data bits/symbol for
16QAM. This means that there is potential to increase the peak bit rate by
50% when 64QAM is used.
Higher bit rates, up to 21 Mbps (Layer 1) are obtainable. The function will
also increase the cell capacity.
64QAM requires high SNR so the bit rate that can be attained will depend on
the radio conditions. 64QAM is an optional feature for the network and the
UE. The RBS and the UE report to the RNC if they are capable of 64QAM.
When a connection is established, the RNC indicates to the RBS whether it is
allowed to use 64QAM in downlink and also to the UE whether the downlink
is configured for 64QAM. If the UE is capable of 64QAM and if the RBS uses
64QAM, the feature will be enabled.
Every 2 ms TTI, the RBS determines the modulation method to be used on

the HS-PDSCH:
• QPSK
• 16QAM
• 64QAM
For more information see HSDPA User Plane.
7.5.2 Impact
None.
Introduces the possibility to achieve higher bit rates, up to 21 Mbps on layer 1.

Overall HS cell throughput is improved. The function also increases the cell
capacity, as the improved efficiency of 64QAM modulation in some conditions
makes it possible to achieve similar performance to 16QAM with less code
usage.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 45

7.5.2.2 Hardware
The following RBSs configurations, that are equipped to support HSDPA, will
support 64QAM:
1. RBS R1
2. RBS R2
3. RBS R3
4. RBS 6000
SPB21 or SPB3 HW is required in the RNC, dimensioned according network

requirements. See Dimensioning Description RNC 3810.
Network dimensioning aspects (e.g. TN Iu/Iub capacity) should be considered

when introducing 64 QAM.
7.5.2.4 Interface
RANAP Rel-7 is needed to achieve bit rates higher than 16 Mbps over Iu. Care
must be taken when provisioning 64 QAM users (with DL MBR set > 16 MB) in
the HLR, see Interface.
None.
7.5.2.5 Operation
The feature 64QAM is license controlled and the license is located on the RBS
node. Licenses for Enhanced Layer 2 and HSDPA 16QAM are required to
enable the feature 64QAM.
The feature can be activated/deactivated by the parameter NodeBFunctio

nfeatureState64Qam. The parameter Hsdsch.qam64Support indicates
whether or not the cell supports 64QAM.
The following licenses are required to activate this feature, HSDPA 16QAM
FAJ 121 903 , Enhanced Layer 2 FAJ 121 1328.
46 1/109 48-HSD 101 02/7 Uen D 2009-02-19

Core network support required for the higher bit rates. UEs supporting 64QAM
are required.
Care must be taken when provisioning 64 QAM users (with DL MBR set > 16
MB) in the HLR, see Interface.
7.6 Cell Broadcast Service
7.6.1 Description
The optional feature Cell Broadcast Service (CBS) is a new in WCDMA RAN
P7.0.
The service permits a number of unacknowledged messages to be broadcast

in defined geographical areas known as cell broadcast areas. The CBS
messages are broadcast cyclically at a frequency and for a duration agreed by
the content provider. CBS messages are sent to UTRAN from a Cell Broadcast
Center (CBC) via the Iu-BC interface. One CBC can serve several RNCs, but
each RNC can only be connected to one CBC node.
A new user-plane protocol, BMC, is introduced above RLC. The functionality of

the BMC protocol is to store message orders received from CBC and schedule
and broadcast the messages over the air interface. The messages are sent on
a new logical channel, CTCH, using RLC unacknowledged mode. The CTCH is
multiplexed on a FACH transport channel carried by a Secondary CCPCH.
CBS messages are received by UEs in idle mode and in state URA_PCH. The
UE will monitor the FACH during predefined CTCH occasions.
The CBS feature introduces a new area concept called Cell Broadcast Service
Area. One Cell Broadcast Service Area contains only one UTRAN cell.
See Cell Broadcast Service for more information.
7.6.2 Impact
None.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 47

The CTCH will share existing FACH and Secondary CCPCH resources
allocated for RRC signalling and PS Interactive data. During the CTCH
occasions CBS traffic will have the highest priority.
The Iu-BC interface will share the INET IP-stack with the Mur interface. Since
there is no possibility to separate the QoS characteristics for the two interfaces,
the Iu-BC traffic will compete for bandwidth with the O&M traffic on Mur.
7.6.2.2 Hardware
The feature requires R4 HW or later for the RANAP/RNSAP MP in RNC.
None.
7.6.2.4 Interface
A new interface, Iu-BC, is introduced between the RNC and the external node
CBC. The Iu-BC interface is connected to the same IP network as used for
Mur and the same data link layer (IP or ATM transport) must be used for both
interfaces. Compliance to the interfaces are covered by the following 3GPP
SoCs; BMC (25.324), 44/17402 - HSD10102/7, SABP (25.419), 45/17402 –
HSD 10202/7, Iu interface data transport & signalling (25.414), 02/17402 –
HSD 10102/7.
RNC EM and OSS GUIs are updated to support this feature.
7.6.2.5 Operation
The following parameters can be set by the operator:
• ctchOccasionPeriod – the period of CTCH allocations on S-CCPCH
• cellBroadcastSac – Cell Broadcast Service Area Code within a

Location Area
• cbcIpAdress – IP address of the CBC node
• sourceIpAdressValidation – indicates if the source IP address shall

be validated when the CBC establishes a TCP connection. If so, only a
source IP address equal to cbcIpAdress is accepted
48 1/109 48-HSD 101 02/7 Uen D 2009-02-19

Impact on WCDMA RAN P6.1 HSDPA
The following new performance management counters are defined for this
feature.
• pmNoReceivedSABPMsgs: Number of received SABP messages over

Iu-Bc.
• pmNoSentSABPMsgs: Number of sent SABP messages over Iu-Bc.
• pmNoRejectedTcpConnections: Number of rejected TCP connections

because of disallowed source IP address.
• pmNoDiscardedCbsMsgOrders:Number of discarded CBS message

orders per cell.
• pmNoDiscardedBmcMsgs: Number of discarded BMC PDU’s per cell.

Each BMC PDU contains one BMC CBS Message.
• pmBmcTrafficVolume: Accumulated BMC payload (bytes) per cell.
A new GPEH event is also introduced: CBS_MESSAGE_ORDER_DISCARDED.
The following should be considered when activating the feature:
• SW license for FAJ 121 1326 installed and activated in RNC
• MO IuBcLink created and unlocked
• Cell Broadcast Service Area defined per UtranCell (parameter

cellBroadcastSac)
None.
In order to receive and broadcast CBS messages the RNC must be connected
to an external CBC node via the Iu-BC interface. UEs supporting CBS are
required and the CBS application must be activated in the UE in order to
receive and display cell broadcast messages.
8 Impact on WCDMA RAN P6.1 HSDPA
None.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 49

9 Impact on WCDMA RAN P6.1 Enhanced

Uplink
9.1 Downlink Power Control for Enhanced Uplink
9.1.1 Description
The optional feature, Downlink power control for Enhanced Uplink, is
new in WCDMA RAN P7.0. The feature introduces power control for the
Enhanced Uplink related downlink control channel E-HICH. The E-HICH will
be transmitted with enough, but not excessive power, individually adjusted per
user connection. This results in remaining power which is available for HS,
enabling increase in HS throughput in the cell.
The power level decision is based on CQI measurements, and the algorithm is
based on the same principle as the existing HS-SCCH power control algorithm.
For more information see, Power Control.
9.1.2 Impact
The feature results in an increase in the HS throughput in the cell.
Downlink interference will be reduced since up to now the ACK/NACK for EUL
has been transmitted with constant power.
9.1.2.2 Hardware
None.
None.
50 1/109 48-HSD 101 02/7 Uen D 2009-02-19

Impact on WCDMA RAN P6.1 Enhanced Uplink
9.1.2.4 Interface
None.
None.
9.1.2.5 Operation
This feature is licence controlled.
Parameters introduced by the E-HICH Power Control:
• eHichMinCodePowerE-HICH ACK minimum code power relative to

PCPICH power. (default -22 dB 10 ms)
• qualityCheckPowerEHich Configurable offset to adjust the E-HICH

power. (default 0 dB)
After upgrade to WCDMA RAN P7 the old system behavior is

maintained. By configuring the parameter eHichMinCodePower
relative to the maxUserErgchEHichPowerDl (10 ms EUL) and
maxUserEHichPowerDlTti2 (2 ms EUL) downlink power control for
enhanced uplink is introduced.
This feature requires the optional RAN feature: Enhanced Uplink Introduction
Package FAJ 121 1023.
None.
9.2 Enhanced Uplink 2 ms TTI
9.2.1 Description
This optional feature Enhanced Uplink 2 ms TTI is enhanced in WCDMA RAN
P7.0 by the introduction of a switch between 2 ms and 10 ms TTI and the
support for the 2 times PS interactive RAB on 2 ms TTI.
The switch from 2 ms to 10 ms TTI occurs when:
• Entering a cell with 10 ms TTI support only
1/109 48-HSD 101 02/7 Uen D 2009-02-19 51

• There is a lack of Channel Elements in target cell at soft handover
• At change of Serving cell when maximum numbers of 2 ms TTI users is

exceeded
• Coverage based switch, based on event 6d
Scheduler observability is improved for enhanced uplink users.
For more information see, Enhanced ULScheduler, EUL User Plane, EUL Flow
Control and EUL Overview.
9.2.2 Impact
None.
The 2 to 10 ms switch enables improved EUL coverage and the capability to

maintain a high bit rate EUL connection when switching to a 10 ms TTI-only
EUL RAB combination, and thus avoid a DCH down-switch.
9.2.2.2 Hardware
RAX R2e is required in the RBS.
Recommended values for all parameters should be used.
Due to that Eul 2 ms operates on high rates in uplink there can be higher noise
rise in the system when there is a lot of Eul traffic. Monitor accessibility and
retainability KPIs. There may be some increase in these due to the increased
load. Scheduler and load estimator parameters such as the maximum allowed
noise rise can be tuned to trade-off Eul load vs KPI impact.
9.2.2.4 Interface
None.
None.
52 1/109 48-HSD 101 02/7 Uen D 2009-02-19

9.2.2.5 Operation
A new parameter is introduced eulMaxAllowedSchRate : used to tune peak

rate vs stability per cell.
The following new counters are introduced,
• pmSumNackedBitsCellEulTti10: Recording of the total amount of

NACKed data received in kbits after HARQ process on MAC-e level for all
10 ms TTI users in a cell. Note that k = 1000.
• pmSumAckedBitsCellEulTti10: Recording of the total amount of

ACKed data received in kbits after HARQ process on MAC-e level for all 10
ms TTI users in a cell. Note that k = 1000.
• pmNoActive10msIntervalsEulTti10: A cell-level RBS counter that

records the number of 10-ms intervals in which the transmission of one or
more E-DCH frames has been detected.
• pmSumNackedBitsCellEulTti2: Recording of the total amount of

NACKed data received in kbits after HARQ process on MAC-e level for all
2 ms TTI users in a cell. Note that k = 1000.
• pmSumAckedBitsCellEulTti2: Recording of the total amount of ACKed

data received in kbits after HARQ process on MAC-e level for all 2 ms TTI
users in a cell. Note that k = 1000.
• pmNoActive2msIntervalsEulTti2: A cell-level RBS counter that

records the number of 2-ms intervals in which the transmission of one or
more E-DCH frames has been detected.
• pmNoActive2msIntervalsEul: A cell-level RBS counter that records

the number of 2-ms intervals in which the transmission of one or more
E-DCH frames has been detected.
• pmEulRlcUserPacketThp : (Updated) Change the range of the existing

counter to give better granularity for the higher rates needed with 2 ms TTI.
• pmLedchTot : Cell level Scheduled E-DCH Uu load estimate Includes

component from E-DPDCH and E-DPCCH for E-DCH users in the cell.
• pmLmaxedch : Total cell level estimate of the Uu component of scheduling

headroom available for EUL ‘schedulable’ traffic in a cell.
• pmHwCePoolEul : (updated) The existing counter shall always apply HW

cost according to the current E-DCH licensed ladder in the RBS when
reporting CE consumption for Eul.
Note that activation of this feature is cover in CPI EUL Migration and Activation.
This feature requires the features
1/109 48-HSD 101 02/7 Uen D 2009-02-19 53

• Enhanced Uplink Introduction Package FAJ 121 1023
This feature can be further enhanced by:
• Advanced Receivers, Generalized RAKE in RBS FAJ 121 1333
• Improved CE ladder for Enhanced Uplink FAJ 121 1334
Rel 6 UEs are required supporting 2 ms. Support in the CN for higher bit rates
in UL is required.
9.3 Advanced Receivers, GRAKE in RBS
9.3.1 Description
The optional feature Advanced Receivers, GRAKE in RBS is a new feature
introduced in WCDMA RAN P7.0.
A generalized RAKE (G-RAKE) receiver is introduced in the RBS to improve

achievable bit rates for Enhanced Uplink in multi-path radio environments. The
functionality is supported for configurations with and without receiver diversity.
G-RAKE is a receiver technique that uses the correlation matrix of the

received signals in the different delay taps (called fingers) to estimate the
self-interference and the receiver noise. The estimates are then used to
suppress the self-interference. The G-RAKE is applied for E-DCH users with 2
ms TTI for the spreading factor combinations 2xSF2 and 2xSF2 + 2xSF4
For more information see EUL User Plane.
9.3.2 Impact
None.
G-RAKE provides improved peak rate in multi-path conditions, and improves

the bit rate coverage for high bit rates (above 2 Mbps).
54 1/109 48-HSD 101 02/7 Uen D 2009-02-19

9.3.2.2 Hardware
The CE cost per rate is the same for G-RAKE as RAKE.
Tune the eulMaxScheduledRate to allow higher peak rates.
9.3.2.4 Interface
None.
None.
9.3.2.5 Operation
The feature is licence controlled in the RBS.
Operator configurable on/off parameter featureStateGrake is introduced.
This optional feature has been introduced in WCDMA RAN P7.0 and requires
the optional RAN features:
• EUL 2 ms TTI FAJ 121 1317
• Improved CE ladder for Enhanced Uplink FAJ 121 1334
None.
9.4 Improved CE ladder for E-DCH for RAX R2e
9.4.1 Description
The optional feature Improved CE ladder for E-DCH for RAX R2e is a new
feature introduced in WCDMA RAN P7.0.
This feature provides double Channel Element (CE) efficiency for EUL users
through a software capacity license. The improvement is valid for both low rate,
and high rate, Enhanced Uplink users on 2 ms TTI and 10 ms TTI.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 55

With the RAX R2e hardware it is possible to have twice as efficient CE ladder
for EUL users. The new ladder called E-DCH ladder E is controlled by a
software capacity license.
The CE usage for ladder E and the previous ladders is noted in the table below.
Table 12 Channel element usage in relation to Spreading Factor (SF)

SF E-DCH E-DCH E-DCH
Ladder C Ladder D Ladder E
256 3 2 1
128 3 2 1
64 3 2 1
32 3 2 1
16 4 4 2
8 8 8 4
4 16 16 8
2x4 32 32 16
2x2 64 64 32
2x2+2x4 96 96 48
For more information see Configuring HSDPA and EUL and RBS License
Control.
9.4.2 Impact
More EUL subscribers possible per RAX R2e board.
The basic cost for an EUL user can be reduced to 1 CE (10 ms TTI). For 2 ms
TTI it is reduced to 8 CEs. Double Channel Element efficiency for all Enhanced
uplink users processed by the RAX R2e.
9.4.2.2 Hardware
This feature requires an RBS configuration including RAX R2e hardware.
56 1/109 48-HSD 101 02/7 Uen D 2009-02-19

Impacts on WCDMA RAN P6.1 Transport Network Functionality
None.
9.4.2.4 Interface
None.
None.
9.4.2.5 Operation
The feature is license controlled in the RBS.
This optional feature requires the optional RAN features: Enhanced Uplink
Introduction Package FAJ 121 1023.
None.
10 Impacts on WCDMA RAN P6.1 Transport

Network Functionality
10.1 IuCS User Traffic over IP
10.1.1 Description
The IuCS User Traffic over IP feature is a new optional feature introduced
in WCDMA RAN P7.0.
Introducing the IuCS User Plane over IP feature allows for transporting the
Iu-CS user plane over IP using an Ethernet interface. The Iu-CS control plane
over IP is described in the "SS7 over IP" feature introduced in WCDMA RAN
5. This feature provides the Iu-CS interface specific functionality to establish
1/109 48-HSD 101 02/7 Uen D 2009-02-19 57

and release Iur user plane transport bearers using IPv4 transport option and
to transport Iu-CS data streams over RTP/UDP/IP.
Diffserv marking in accordance with default settings is supported and can be

used in the IP network for QoS prioritization. Diffserv mapping to Ethernet
quality bits in accordance with 802.1p will also be performed. For operator
configurable Diffserv settings and Diffserv mapping, see feature Configurable
Transport Bearer QoS Classes, introduced in WCDMA RAN 6.
It is possible to have both ATM-based and IP-based Iu-CS in the same RNC.
10.1.2 Impact
None.
None.
10.1.2.2 Hardware
The feature requires ET-MFGs to connect to an IP network. ATM ET boards in

the RNC main subrack may need to be removed depending on availability of
empty slots.
IP interfaces must be available and configured before activating this feature.
10.1.2.4 Interface
An IP network must be provided connecting the RNC and MSC/MGW.
Note in the multi-vendor case RANAP IEs “Transport Layer Address” and
“Binding ID” are used for the CS domain for coding IP address and UDP port
number to set up IP transport bearers.
None.
58 1/109 48-HSD 101 02/7 Uen D 2009-02-19

10.1.2.5 Operation
The feature is activated by attribute userPlaneTransportOption in the MO

Class IuLink, see IP Transport Network Configuration. IP hosts must be
configured and referenced with attribute userPlaneIpResourceRef in the
MO Class IuLink before activating the feature.
Activation of the feature enables the RNC to use IP transport if selected by the
MSC. The MSC is the node selecting the transport option to use. Performance
management counters in the IP layer replace performance management
counters in the ATM layer.
This feature requires the optional RAN feature IP interfaces in WCDMA RAN
FAJ 121 964
MSC/MGW must support IP transport for Iu-CS user plane.
10.2 Common Iub IP host in RBS
10.2.1 Description
This new basic feature, Common Iub IP host in RBS is introduced in WCDMA
RAN P7.0.2 and makes it possible to use the same IP host for Iub control plane
and Iub user plane in RBS. The same functionality is also available in RNC. An
RBS will only need one IP address for Iub when this feature is introduced.
Note: This does not affect the IP address used for O&M (Mub).
The number of IP addresses in the RNC for use with Iub interface can be
reduced since no specific IP Hosts are required for Iub control plane. The
existing IP hosts on ET-MFX used for Iub user plane can be reused also for
Iub control plane. When Iub control plane and user plane share IP addresses,
the operator may want to revise the IP address plan to take advantage of the
reduced number of IP addresses used by RBS and RNC.
Migration paths are supported from WRAN P7: ATM RBS, Dual stack RBS,
IP RBS.
For further information see CPI: IP Transport Network Configuration.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 59

10.2.2 Impact
None.
None.
10.2.2.2 Hardware
Supported in RBS.
This feature can be activated separately in RBS and RNC. In RBS, this feature
will be activated as an automatic reconfiguration during upgrade. The IP
address used for Iub control plane (in existing IpAccessHostGpb) will be
moved to the ET host. This move is performed to avoid the need to reconfigure
the RNC since the IP address used for Iub control plane is defined in the
controlling RNC. In RNC this feature is optional to configure, but recommended
for new RNC installation. It is also possible to reconfigure an existing RNC
node, see below (Operation).
10.2.2.4 Interface
None.
None.
10.2.2.5 Operation
In RNC, the feature is activated by re-configuring the IP layer below SCTP used
for Iub control plane. The IP host MO IpAccessHostGpb is deleted and a
new MO IpAccessSctp is created, which contains references to the IP host
MO IpAccessHostEt used for Iub user plane. See RAN CPI "IP Transport
Network Configuration" for an example.
When activated the feature changes the behavior of PM counters for IP in MOC
IpAccessHostEt because counters will include IP packets for SCTP for Iub
control plane, while previously only including IP packets for Iub user plane. The
relevant counters are:
60 1/109 48-HSD 101 02/7 Uen D 2009-02-19

• pmIcmpInDestUnreachs
• pmIcmpInMsgs
• pmIpInDelivers
• pmIpInReceives
• pmIpInDiscards
• pmIpInHdrErrors
• pmIpOutDiscards
• pmIpOutRequests
None.
None
10.3 Mub Port Integration
10.3.1 Description
The new basic feature Mub Port Integration, introduced in WCDMA RAN
P7.0.2, removes the need for the O&M Cable used in IP RBS for Mub traffic.
The O&M cable is an Ethernet front cable (Emily – RJ45) carrying Mub traffic
between the FE port on CBU/GPB and the ET MFX board. When this feature
is introduced, O&M traffic will be carried via backplane directly to ET-MFX
board instead. RBS nodes from factory will be delivered without O&M cable
when this feature is introduced.
The feature will give the following benefits for an IP RBS: - Remove the need
for the O&M front cable - Free ports on ET MFX and GPU (will make ET-MFX14
possible to use in RBS) - Local Management PC can be connected directly
to FE port on CBU/GPB using a well known IP Address 169.254.1.1 (APIPA
Address) - Mub traffic can be configured with redundant routers supervised
by RPS functionality
Support in OSS-RC will also be updated to handle the new configuration of IP

RBS and to support remote migration between Dual Stack RBS and IP RBS.
RBS with dual stack Iub is not directly impacted by this feature since Mub use
IP over ATM for dual stack RBS. There are however some considerations
related to site-LAN configuration if remote migation from dual stack RBS to
1/109 48-HSD 101 02/7 Uen D 2009-02-19 61

IP RBS shall be possible. In this case connectivity to both IP over ATM and
Ethernet backhaul must be provided from site-LAN.
10.3.2 Impact
None.
With the Mub port integration, only one port on the IP/Ethernet interface board
in the RBS is required for connecting both Iub and Mub. Operators that have
the feature “System Integrated Ethernet switch” will have one more port
available for Site LAN or Iub aggregation.
Migrating RBS to IP requires less effort since no external cabling and no

configuration of specific Mub port on ET-MFX is required.
10.3.2.2 Hardware
O&M cable is no longer required for IP RBS.
Before introducing this feature all required Site LAN connectivity has to be
provided through the ET-MFX and not through the FE port on the CBU/GPB.
The reconfiguration of Mub to use backplane link instead of O&M Cable will be
performed automatically during upgrade of IP RBS. After upgrade, the O&M
cable will no longer be used, and can be removed at next site visit. The Node
IP Address including subnet and VLAN configuration will be kept, but it will be
moved to a new MAC Address (on ET-MFX). The O&M Host will be set to run
in host mode. The IP address at the FE port will be set to the APIPA address
169.254.1.1 with subnet mask 255.255.0.0.
If the O&M cable is connected to another port than the default port on ET-MFX
(Port 2), some preparation of RBS node must be performed before upgrade
to indicate the port where O&M cable is located, see details in RBS upgrade
instructions.
With the introduction of Mub Port Integration, the O&M IP host in IP RBS will
be configured in “host mode”. As a consequence the functionality for “DHCP
Relay Agent” is no longer supported. This service was used by site-LAN
equipment (including local terminal attached to the Site-LAN) to relay a request
for dynamic IP address assignment to the DHCP Server in COMINF. To keep
62 1/109 48-HSD 101 02/7 Uen D 2009-02-19

the same functionality after introduction of Mub , a DHCP Relay Agent must be
configured in the closest Router attached to the LAN instead.
10.3.2.4 Interface
None.
None.
10.3.2.5 Operation
The Mub related counters previously found on EthernetLink MO will be available

on IpHostLink MO.
This feature is only relevant for RBS with IP transmission.
None
10.4 Robust Reconfiguration using Rollback
10.4.1 Description
This new basic feature, Robust Reconfiguration is introduced in WCDMA RAN
P7.0.2 and provides the possibility to protect a node (typically an RBS) from
errors leading to lost O&M communication. The protection using rollback is
mainly relevant for remote reconfiguration related to transmission links carrying
O&M traffic. This type of protection is relevant both for ATM based and IP
based transmission. Without this feature, a site visit is in many cases the only
way to recover from a situation with lost O&M contact. With this feature, it is
now possible to set up a rollback protection for any reconfiguration activity
similar to the existing support during SW upgrade or security activation.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 63

10.4.2 Impact
None.
None.
10.4.2.2 Hardware
None.
This functionality will not be active unless explicitly configured.
10.4.2.4 Interface
None.
None.
10.4.2.5 Operation
The protection can be activated before a reconfiguration impacting O&M

connectivity by setting attribute configCountdownActivatedin MO
ConfigurationVersion. After the (successful) reconfiguration the O&M
connectivity must be confirmed by resetting the same attribute within the time
limit specified by configAdmCountdown. If O&M contact is lost, a fallback to
the previous configuration will be made.
None.
None.
64 1/109 48-HSD 101 02/7 Uen D 2009-02-19

Impact on WCDMA RAN P6.1 RAN Management
11 Impact on WCDMA RAN P6.1 RAN

Management
11.1 RBS Auto Provisioning
11.1.1 Description
The new basic feature, RBS Auto Provisioning is new in WCDMA RAN P7.0.
The feature simplifies the integration of RBS into the network and shortens
the site integration time. The feature makes it possible for a site technician to
easily and rapidly integrate an RBS into the network, without any support from
the OMC personnel.
Immediately after the integration, test calls can be made to verify the integration,
before the technician leaves the site. The steps in the automated integration
process are displayed on the LCT (Local Craft Terminal) and can thus be
monitored by the site technician. When the automated process is finalized an
integration report is produced. A semi automated integration procedure is also
possible. In this procedure the RBS configuration files (Site Basic Configuration
file and External HW Configuration file) are stored (instead of in the network
repository) on the LCT that the technician brings to the site.
Note: For ATM-RBSs the semi automated procedure has to be used (as
ATM-RBSs initially cannot access the DHCP server).
The amount of information needed at the site visit is minimized, as the

preparations are made in advance. During the integration the RBS configuration
is automatically downloaded from network repositories (FTP (SMRS) and
DHCP servers respectively). IP connectivity to the site is required for taking
advantage of the Auto-Integration of RBS feature. This means IP connectivity
over Ethernet or over ATM for IP- or ATM RBSs respectively.
For more information see Add RBS.
11.1.2 Impact
None.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 65

None.
11.1.2.2 Hardware
In order to utilize this feature to its full extent the following servers are in
operation in the O&M infrastructure (COMInf) are required:
• Bi-SMRS server (used as a repository for the RBS configuration files)
• DHCP server (based on IP Works)
The Bi-SMRS server requires the hardware servers NESS and NEDSS.
However, the semi-automated process (see Section 11.1.1 Description on page
65) can always be used independently if the Bi-SMRS or the DHCP servers.
The site technician launches the Auto-Integration of RBS application GUI

and enters the needed information (RBS logical name and so on). The
Auto-Integration process then starts and it consists of a number of steps, all
performed automatically without any operator intervention.
11.1.2.4 Interface
None.
A new GUI for Auto-Integration is introduced in the RBS EM.
11.1.2.5 Operation
To be able to utilize the Auto-Integration of RBS feature preparations have to

be made in advance. The amount of preparation data differs depending on the
type Auto-Integration procedure (semi automated or not). Not all preparations
are needed in semi automated procedure as the RBS configuration files are
stored in the LCT and not in the network repositories. As comparison, the
preparation activities for a totally manual integration procedure (Manual) are
also shown in the table below.
Table 13 Overview of Preparation Data

Item Preparation activity Semi Manual
1 Produce Site Basic Configuration file y y
(3)
66 1/109 48-HSD 101 02/7 Uen D 2009-02-19

Item Preparation activity Semi Manual

2 Produce External HW Configuration y y
file
3 Produce Site Specific Configuration y y
file
4 Produce RBS Summary file n N/A
(1)
5 Load data in DHCP server n N/A
(2)
6 Store RBS configuration files in n N/A
Repository (SMRS)
7 Import Site Specific Configuration file y y
to Planned Area
8 Configure Auto-Integration in OSS y N/A
(1) When semi automated procedure is used the Basic IP data is included in the Site Basic
configuration file (same as for manual integration of RBS).
(2) When semi automated procedure is used the Site Basic and External HW configuration files
need to be stored on the site technician LCT before travelling to the site (same as for manual
integration of RBS).
Dependent on that the Bi-SMRS product is used in the O&M Infrastructure

(COMInf).
None.
11.2 Accessibility
11.2.1 Description
The feature Accessibility is updated in WCDMA RAN P7.0 to include the new
Element Managers (EM) for P7 nodes and onwards, thus replacing the former
Element Managers and Object Explorer. When launching the Element Manger
towards P7 nodes and onwards, the new Element Manager will be launched.
When launching towards P6 nodes and older, the P6 Element Manger (EMAS)
together with Object Explorer (OE) will be launched.
Existing basic EM functionality from P6 EM is to a large extent preserved in P7

EM but there are differences in the user interface;
The new Element Managers have been built on a new GUI platform where the
main difference is that the GUIs now are model-driven, i.e. the GUIs adapt
to the content of the actual Managed Object Model (MOM). This means that
1/109 48-HSD 101 02/7 Uen D 2009-02-19 67

step-by-step procedures for some use cases will be performed differently as

the content and structure of the pre-defined views will differ from the P6 EMs.
The menu bar is different and new tabs for the right pane are introduced. A
containment view of the MOs on the node, the MO Tree, is displayed graphically
in the left pane, looking very much as the Object Explorer.
The pre-defined views are the views recognized from P6 EMs, but the view
element concept is replaced by folders where related MOs are arranged. A
License view is added as well as Relations views which contain stack views
with configuration and status information for resources on the node. As the
views now are specified in XML file format, the users can in an easy way specify
their own user-defined views to facilitate fault-finding and troubleshooting.
The primary and recommended way to launch the configuration tools will now
be from the start menu for easy and fast access. A basic MOM knowledge is an
advantage when working with the new Element Managers.
The EMs are described in following CPI: Element Manager User Guide
RBS 3000 16/1553-HRB 105 102/1, Element Manager User Guide RNC
29/1553-AXD 105 03/1, Element Manager User Guide RXI 3/1553-CNX 901 280
, Specifying User-Defined Views 2/1553-CXA 110 3559.
For examples of user interface delta information, see Element Manager, RAN
P6.1 - RAN P7.0 Delta Information, 1/00651-HSD 101 02/7, Installing an
Element Management Application, RNC, 25/1553-AXD 105 03/1, Installing an
Element Management Application, RXI, 2/1553-CNX 901 280, Installing an
Element Management Application, RBS, 18/1553-HRB 105 102/1.
11.2.2 Impact
None.
None.
11.2.2.2 Hardware
None.
The EM installation package has to be downloaded from the WCDMA RAN

P7 node and installed on the PC the first time it is used, when the EM is
68 1/109 48-HSD 101 02/7 Uen D 2009-02-19

started towards a WCDMA RAN P7 node. When EM is started from OSS-RC,

no special activity has to be done as software upgrade of the EM is done
automatically, so there is no impact on the end-user. The client only needs to
retrieve the EM application the first time it launches the application and when
there are new versions of the EM/OE applications. After this initial installation,
the launcher mechanism will verify, and if needed update, the version of the
application in the client PC, as in P6.1.
Note: To have all WCDMA RAN P6 and WCDMA RAN P7 EM applications

startable from the client machine, the EM for an older system version must
be installed before an EM for a newer system version. If there is a need to
re-install the EM of an earlier node version due to, for example, an error
correction delivery, the EM for a newer system version must also be re-installed,
afterwards, in order to be able to launch towards both old and new nodes.
Java 5 or later, needs to be installed on the client.
11.2.2.4 Interface
In cases where the EM is launched from a non-Ericsson application designed

by the operator, the operator launching scripts may have to be rewritten for new
EM to start properly.
A new EM GUI is introduced.
11.2.2.5 Operation
When launching the Element Manager towards P7 nodes and onwards, the
new Element Manager will be launched. When launching towards P6 nodes
and older, the P6 Element Manager (EMAS) together with Object Explorer
(OE) will be launched.
The EM Object Explorer is removed from all WCDMA RAN P7.0 nodes and
replaced by the new Element Manager. (The OSS-RC Object Explorer will
continue to support WCDMA RAN P7 Nodes.)
Configuration tools - started from Windows start menu The primary, and
recommended way, to start the configuration tools is from the Windows start
menu, under Start/Programs EM applications and RNC/RXI/RBS configurations
tools. However, all node specific tools, including these configuration tools can
still be launched from the actual EM.
New Main window- changed menu bar and new tabs - There are new GUIs
in the new Element Manager but with similarities to P6 Element Manager. The
menu bar is different and now shows File, View, MO, Alarm, Tools, Options,
Help whereas the old EM showed Network Element, Fetch, Configuration,
Maintenance, Supervision, Tools and Window.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 69

A containment view of the MOs on the node, the MO Tree, is displayed in the
left pane, in a similar way to Object Explorer. The Containment view shows the
relations between all MOs, parent to child, as defined in the Managed Object
Model (MOM), and provides an overview of the MO structure of the whole node.
Several tabs are new in the right pane.
• The Table tab gives an overview over important attributes that belong to an
MO selected in the MO tree.
• The MO Properties tab which is a convenient new alternative to the MO

Properties windows, showing attributes and actions for a specific MO. Many
right-click functions in the old EM are now performed in MO Properties.
• The CV and UP tab in the Software view replaces the folders Configuration
Versions, Rollback List, Upgrade Packages.
Model-driven GUIs - changed user interface - The new Element Managers

are model driven, that is the GUI adapts to the content of the Managed Object
Model (MOM). This provides a GUI that is consistent with the MOM, as in
Object Explorer, and an alignment in naming and behavior throughout the
system. Therefore good MOM knowledge is an advantage when working with
the New Element Manager.
As a result of the model-driven GUIs, some use cases will be performed

differently. Right-click functionality is now often performed in the MO Properties
window. More clicks sometimes are needed to expand the MO tree to the level
where the action is performed. For example, right-click functionality Lock/Unlock
and manual restart of a board on a View Element Slot in previous products, is
now performed by expanding Subrack MO, expanding Slot MO, expanding MO
PlugInUnit, and right-clicking on the Lock/Unlock or manual restart.
IP ping and traceRoute right-click functionality in previous products is now

performed in the MO Properties tab.
Activities like Add/Delete MO, which in previous product releases were

performed by right-clicking, are now performed through the menu bar / MO /
Add… or Delete.
Attributes grouped under different tabs in the RNC EM are now all found in
alphabetical order in the MO Properties tab.
Some MOs are no longer viewed/configured in the pre-defined views, but can
be seen in the containment view.
Manual refresh- now always needed after configuration changes - Manual

refresh is needed after configuration changes. In P6 Element Manager the left
pane MO tree was updated automatically when nodes were configured from
EM configuration tools. This does not happen in new EM and Manual refresh
is needed or, going in/out from a GUI updates the tree. This saves bandwidth
and processing capacity on the node and gives consistency between the way
information is updated in the GUIs.
70 1/109 48-HSD 101 02/7 Uen D 2009-02-19

Impact on WCDMA RAN P6.1 Capacity Licenses
None.
None.
12 Impact on WCDMA RAN P6.1 Licensing

Principles
The feature License Control, FAJ 121 437, is enhanced in WCDMA RAN P7.0.
These changes result in new handling procedures for Licenses in P7.0 in
particular in relation to upgrade. This is documented in the Upgrade Chapter.
13 Impact on WCDMA RAN P6.1 Capacity

Licenses
13.1 HSDPA Users per Cell
13.1.1 Description
This optional feature HSDPA Users per Cell is enhanced in WCDMA RAN
P7.0. with support for upto 64 HSDPA users per cell in RBS. The feature
also introduces the possibility for the operator to configure A-DCH processing
capacity. Note that the total number of users in the cells served by one HSDPA
resource cannot exceed 96.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 71

13.1.2 Impact
The feature increases the peak level of subscribers that can be handled in a
cell from 32 to 64.
For more information see Configuring HSDPA and EUL and RBS License
Control.
None.
13.1.2.2 Hardware
None.
HW capacity (number of HSDPA processing resources and configured A-DCH

capacity) should be matched to the licensed or configured level or users. In
RNC, there are cell admission control parameters that need to be tuned to
the correct value, dependent on what license level there is in the RBS, or
how the parameters maxNumHsdpaUsers and maxNumADchReservation
are set. Amount of A-DCH to allow in RBS shall also be tuned via parameter
numAdchReservation
13.1.2.4 Interface
None.
None.
13.1.2.5 Operation
The existing license FAJ 121 1011 is extended to have the following 2 more
license levels allowing up to 64 users:
• 33..48
• 49..64
72 1/109 48-HSD 101 02/7 Uen D 2009-02-19

The new parameter numAdchCeReservation to allow the operator to control

the resources for A-DCH.
Following new counters are introduced,
• pmUsedADch : A-DCH resource utilization
• pmAllocRejADch : A-DCH blocking
• pmAllocRejHwHsDschUsers : number of users blocking
None.
None.
13.2 Number of Carriers in RRUW/RUW based RBS
13.2.1 Description
This license Number of Carriers in RRU/RRUW based RBS is new in WCDMA
RAN P7.0. Support for up to 12 carriers per RBS is introduced.
13.2.2 Impact
None.
None.
13.2.2.2 Hardware
This license applies to RBS equipped with RUW or RRUW radio units. See 3.2
for further details. In case of an RBS configuration with a mix of, for example
RRUW and RRU22 the license will only apply to the RRUW subset of the
configuration.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 73

The licensed level must be equal to, or exceed, the number of carriers in the
RBS.
13.2.2.4 Interface
None.
None.
13.2.2.5 Operation
None.
None.
None.
13.3 Number of 60W power amplifiers in RRUW/RUW

based RBS
13.3.1 Description
This license Number of 60W power amplifiers in RRU/RRUW based RBS is
new in WCDMA RAN P7.0. With support for up to 12 power amplifiers per RBS.
13.3.2 Impact
None.
74 1/109 48-HSD 101 02/7 Uen D 2009-02-19

None.
13.3.2.2 Hardware
for further details. In case of an RBS configuration with a mix of, for example
configuration.
The licensed level must be equal to, or exceed, the number of power amplifiers
configured to 60W nominal output power in the RBS.
13.3.2.4 Interface
None.
None.
13.3.2.5 Operation
The parameter maxTotalOutputPower is introduced to set the nominal

output power of each RRU/RRUW. Each time a power amplifier is configured
with a certain nominal output power the setting is compared with the licensed
level. Configuring 60W requires licenses for both 60W and 40W. Configuring
40W requires only a 40W license. Configuring 20W requires no license.
This license is closely related to the licenses NumberOf40WPowerAmplifie

rsFAJ 121 1347, and Number of Carriers in RUW and RRUW based RBS,
FAJ 121 1344.
None.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 75

13.4 Number of 40W power amplifiers in RRUW/RUW

based RBS
13.4.1 Description
This license Number of 40W power amplifiers in RRU/RRUW based RBS is
new in WCDMA RAN P7.0. With support for up to 12 power amplifiers per RBS.
13.4.2 Impact
None.
None.
13.4.2.2 Hardware
for further details. In case of an RBS configuration with a mix of , for example
configuration.
The licensed level must be equal to, or exceed, the number of power amplifiers
configured to 40W nominal output power in the RBS.
13.4.2.4 Interface
None.
None.
13.4.2.5 Operation
The parameter maxTotalOutputPower is introduced to set the nominal

output power of each RRU/RRUW. Each time a power amplifier is configured
with a certain nominal output power the setting is compared with the licensed
76 1/109 48-HSD 101 02/7 Uen D 2009-02-19

level. Configuring 60W requires licenses for both 60W and 40W. Configuring
40W requires only a 40W license. Configuring 20W requires no license.
This license is closely related to the licenses NumberOf60WPowerAmplifiers

FAJ 121 1348, and Number of Carriers in RUW and RRUW based RBS,
FAJ 121 1344.
None.
13.5 RNC HW R5 Iub Throughput Enhancement
13.5.1 Description
The feature RNC HW R5 Iub Throughput Enhancement provides the Iub

throughput enhancement of 25 Mbps for RNC HW R5. The value in the
Throughput Capacity license key will increase with 25000 kbps. This feature
can be applied several times on one RNC node, up to the maximum Iub
throughput as specified in the Product Package Description.
13.5.2 Impact
None.
None.
13.5.2.2 Hardware
Valid only for RNC R5 HW.
None.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 77

13.5.2.4 Interface
None.
None.
13.5.2.5 Operation
None.
The feature for RNC HW Capacity Enhancement, FAJ 121 1322, is needed for
the whole node before this feature is used.
None.
14 Summary of Operator Interface Changes
14.1 Removed and New/Changed Events

For new, changed or removed events, see General Performance
Event Handling, RNC, RAN P6.1- RAN P7.0 Delta Information,
130/1553-HSD10102/7or General Performance Event Handling, RNC, RAN
P6.0 - RAN P7.0 Delta Information, 230/1553-HSD10102/7.
14.2 Removed and New/Changed Alarms

For new, removed, or changed alarms, see:
• Radio Network Alarms, RNC, RAN P6 - RAN P7 Delta Information,

25/006 51-AXD 105 03/1
• Radio Network Alarms, RBS, RAN P6 - RAN P7 Delta Information,

19/006 51-HRB 105 102/1
78 1/109 48-HSD 101 02/7 Uen D 2009-02-19

Summary of Operator Interface Changes
• Radio Network Alarms, RXI, RAN P6 to RAN P7 Delta Information,

6/006 51-AXI 101 02
14.3 Removed and New / Changed Parameters

For new, removed, or changed parameters, see:
• Radio Network Parameters, RAN P6 - RAN P7 Delta Information,

96/1553-HSD 101 02/7
• Transport Network Parameters, RAN P6 - RAN P7 Delta Information,

97/1553-HSD 101 02/7
14.4 Removed and New / Changed Counters

For new, removed, or changed counters, see:
• Radio Network Performance Monitoring Counters, RNC, RAN P6 - RAN

P7 Delta Information, 105/1553-HSD 101 02/7
• Transport Network Performance Monitoring Counters, RAN P6 - RAN P7

Delta Information, 99/1553-HSD 101 02/7
• Radio Network Performance Monitoring Counters, RBS, RAN P6 - RAN P7

Delta Information, 17/1553-HRB105102/1
1/109 48-HSD 101 02/7 Uen D 2009-02-19 79

80 1/109 48-HSD 101 02/7 Uen D 2009-02-19

Glossary
Glossary
For glossary, see Glossary of Terms and

Acronyms.
1/109 48-HSD 101 02/7 Uen D 2009-02-19 81

82 1/109 48-HSD 101 02/7 Uen D 2009-02-19

Reference List
Reference List
[1] Network Impact Report for OSS RC R6 (6.2), 3/109 48-AOM 901 046.
[2] 3GPP Statement of Compliance, 37/174 02-HSD 101 02/7 Uen
[3] Configuring HSDPA and EUL , RBS 3000, 5/1553-HRB105102/1 Uen
[4] RBS License Control, RBS 3000, 7/1553-HRB105102/1 Uen
[5] Dimensioning Description, RNC 3810, 106/1551- AXD 105 03/1
[6] Network Impact Report for OSS RC R6 (6.3), 4//109 48-AOM 901 046
1/109 48-HSD 101 02/7 Uen D 2009-02-19 83

P7.0 Network Impact Report PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

P7.0 Network Impact Report PDF

Uploaded by

Copyright:

Available Formats

WCDMA RAN P7.

0 Network Impact Report

NETWORK IMPACT REPORT

© Copyright Ericsson AB 2008-2009. All rights reserved.

1/109 48-HSD 101 02/7 Uen D 2009-02-19

4 Summary of Impacts Per Feature 12

5 Impact on WCDMA RAN 6.1 - System Improvements 26

1/109 48-HSD 101 02/7 Uen D 2009-02-19

6 Impact on WCDMA RAN 6.1 Services and Radio Access

7 Impact on WCDMA RAN P6.1 Radio Network

8 Impact on WCDMA RAN P6.1 HSDPA 49

9 Impact on WCDMA RAN P6.1 Enhanced Uplink 50

10 Impacts on WCDMA RAN P6.1 Transport Network

11 Impact on WCDMA RAN P6.1 RAN Management 65

12 Impact on WCDMA RAN P6.1 Licensing Principles 71

13 Impact on WCDMA RAN P6.1 Capacity Licenses 71

1/109 48-HSD 101 02/7 Uen D 2009-02-19

13.4 Number of 40W power amplifiers in RRUW/RUW based

14 Summary of Operator Interface Changes 78

1/109 48-HSD 101 02/7 Uen D 2009-02-19

1/109 48-HSD 101 02/7 Uen D 2009-02-19

The purpose of the NIR is to provide early information to operators to help

Note: There are separate documents covering OSS-RC features, see

1.2 Revision Information

Table 1 Revision History

1/109 48-HSD 101 02/7 Uen D 2009-02-19 1

2.1 Capacity and Performance

In P7 new system improvements are introduced in RNC, for spreading the

On highly loaded systems it might be necessary to increase the capacity of the

It is recommended to measure the load on Module MP, DcSP, CcSP and

• Module MP: 65%

• RANAP MP: 55%

This release supports the configuration of up to 6 Resource_id on a HS-TX60

2 1/109 48-HSD 101 02/7 Uen D 2009-02-19

For OSS-RC, see Reference [1]. and Reference [6]

2.1.5 Subscriber Capacity

2.1.6 Network Performance

2.2 Upgrade Procedures

• New hardware must be installed in affected nodes, and old hardware

1/109 48-HSD 101 02/7 Uen D 2009-02-19 3

2.2.2 Upgrade Paths

From WCDMA RAN 6.0 to WCDMA RAN P7.0.

1. Upgrade OSS-RC 5.3/OSS-RC 6.1 to OSS-RC 6.2.

2. Upgrade WCDMA RAN P6.0 RNC to WCDMA RAN P7.0 RNC.

3. Upgrade WCDMA RAN P6.0 RXI to WCDMA RAN P7.0 RXI.

4. Upgrade WCDMA RAN P6.0 RBS to WCDMA RAN P7.0 RBS.

From WCDMA RAN 6.1 to WCDMA RAN P7.0.

1. Upgrade OSS-RC 5.3/OSS-RC 6.1 to OSS-RC 6.2.

2. Upgrade WCDMA RAN P6.1 RNC to WCDMA RAN P7.0 RNC.

3. Upgrade WCDMA RAN P6.1 RXI to WCDMA RAN P7.0 RXI.

4. Upgrade WCDMA RAN P6.1 RBS to WCDMA RAN P7.0 RBS.

Note: In previous RNC releases, each SP device is administrated by a

In preparation for upgrade of RNC to WCDMA RAN P7.0, load and

If upgrading to WCDMA RAN P7.0.2, step 1 should be replaced by,

4 1/109 48-HSD 101 02/7 Uen D 2009-02-19

2.3.1 Inter-Node Interface

• Iu, Iub, Iur - 3GPP Release 7

• Iuant - 3GPP Release 7

• Iubc - 3GPP Release 6

Note: In 3GPP release 7 new functionality is introduced in both RAN,

In this scenario Ericsson WCDMA RAN P7.0.1 RNC has implemented

For earlier Ericsson SGSN versions or other vendor SGSN not

2.3.2 Man-Machine Interface