BSS R10 Network Impact Report

BSS R10 Network Impact Report
REPORT
E
Copyright
©Ericsson AB 2002, All Rights Reserved.
Disclaimer
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 damages of any kind resulting from the
use of this document.
2/10948-HSC 103 12/4 Uen M 2004-09-17

Contents
1 Introduction 1
2 Revision Information 1
3 General Impact 6
3.1 Capacity and Performance 6
3.2 Hardware 7
3.3 Implementation 11
3.4 Interface 13
3.5 Memory 13
3.6 Operations 15
3.7 Other Features 15
3.8 Other Network Elements 15
4 Summary of Impacts 16
4.1 BSS Features 16
4.2 BTS Features 19
4.3 OSS Features 19
5 Impacting BSS Features 20

5.1 Multi Band Cell 20
5.2 Intracell Handover 22
5.3 Dynamic MS Power Control 23
5.4 AMR Power Control 24
5.5 Network Assisted Cell Change (NACC) 25
5.6 Quality of Service Streaming 27
5.7 GPRS/EGPRS End-user Performance 28
5.8 Flexible SDCCH Allocation 31
5.9 Dynamic FR/HR Mode Adaptation 34
5.10 Call Queuing 36
5.11 Synchronised Radio Networks 37
5.12 Self Configuring Transcoder Pools 39
5.13 AMR HR 41
5.14 Real Time Event Data 42
5.15 EGPRS 44
2/10948-HSC 103 12/4 Uen M 2004-09-17

5.16 Dynamic Overlaid / Underlaid Subcells 45

5.17 Dynamic HR Allocation 47
5.18 AMR 48
5.19 Speech Quality Supervision 50
5.20 Active BA-list Recording 51
5.21 Reduction of BSC Restart Time 52
5.22 Advanced Single Slot Allocation 53
5.23 Support of APZ 212 33C 55
5.24 BSS R10 GPRS/EGPRS System Improvements 56
5.25 BSS R10 System Improvements 58
5.26 Advanced Frequency Handling 60
5.27 Re-Use of Frequencies within a cell 61
5.28 Increased SDCCH Capacity 62
5.29 Locating 63
5.30 Paging 65
5.31 GPRS Quality of Service and Scheduling 66
5.32 High Speed Signalling Links (HSL) 67
5.33 Antenna Hopping 68
5.34 Statistics Based on Measurement Results 69
5.35 Support of AXE 810 — APG40 71
5.36 Support of AXE 810 — APT 1.5 72
5.37 Extended Call Release Reporting 73
5.38 Flexible Positioning Support 74
5.39 Frequency Allocation Support 75
6 Impacting BTS Features 76

6.1 Interference Rejection Combining (IRC) 76
6.2 Battery Test 77
7 Impacting OSS Features 79

7.1 GSM Real–time Performance Monitoring 79
8 Summary of Operator Interface Changes 80

8.1 Parameters Changes 80
8.2 STS Counter Changes 96
9 Glossary 120
10 References 123
2/10948-HSC 103 12/4 Uen M 2004-09-17

1 Introduction
This document describes the impacts the new release, BSS R10 will have
on the BSS Product. BSS R10 contains the following; OSS-RC 1.1, BSC
R10 , BTS 10.1A, BTS 10.1B (RBS 2106/2206/2207/2308), BTS 10A
(RBS2101/2102/2202/2301/2302/2401), BTS 10A (RBS 200) and SMPC 6.0.
Note that a seperate NIR covering R10 NAED (North American Early Delivery)
covers the network impact from R9.1 to R10 NAED. This document covers the
network impact from BSS R9.1 to BSS R10.
The OSS-RC 1.1 consist of the GSM OSS and the CN-OSS. This is the first
merged product covering the Operation and Maintenance both for the Radio
Access Network and the Core Network. For the OSS user this involves some
changes and additions to the OSS GUIs. There are also changes in how to
handle the Network Elements in the OSS.
2 Revision Information
Table 1
Revi- Date Prepared Description
sion
A 2002-11-20 ENEILOR First version of BSS R10 NIR.
Approved by SYG.
B 2003–01–20 ENEILOR Updated with changed counters,

OMT, AXE 810/NNRP-4,
Extended Call release reporting
added. Other general updates.
2/10948-HSC 103 12/4 Uen M 2004-09-17 1

Table 1
sion
C 2003–03–22 EPKHASP Updated due to:
New SGSN version 5.5. Flexible
Positioning Support added. TRH
Capacity drop estimated to 5%.
Features delivered in BTS SW
10.1B clarified. OSS-RC 1.1
added. OSS Configurations
updated. Double DXU EDGE
described in more details.
Improved BTS alarms added.
Editorial changes
D 2003–05–23 EPKHASP The main changes are:

LMU is removed. BSC support
for RBS 200 R7 SW is removed
(chap. 3.7). RNO description
is replaced by applicable
description of BSS features.
Frequency Allocation Support is
added. BSC and OSS capacity
impact changed for Real Time
Event Data. Impact on PLLDP
POD added for BSS R10
System Improvements. BSC CP
memory requirement is updated.
Flexible Positioning Support is
updated. BTS SW 9.1D added.
The BSC CP capacity estimation
is updated
2 2/10948-HSC 103 12/4 Uen M 2004-09-17

Table 1
sion
E 2003–07–09 EPKHASP The main changes are:
RBS 2207 is added.
Compatibility with older BTS
R9 SW is changed (chapter
3.3). Parameter NOR5AINBSC
added (chapter 8.1.1). Note
added for GPRS/EGPRS in OL
subcell (chapter 5.7). Antenna
Hopping on Double DXU EDGE
solution is not supported. OMT
improvements are changed
(chapter 5.25).
2/10948-HSC 103 12/4 Uen M 2004-09-17 3

Table 1
sion
F 2003–10–17 EPKHASP The main changes are:
Compatibility with CGSN
2.1 changed to CGSN 3.0.
Chapter 8.2 (STS counter
changes) updated. Chapter 5.7
(Re-reservation of an existing
TBF) is clarified. Parameter
TN corrected in chapter 8.1.2.
Removal of results on SDCCH
in MRR is added in chapter
5.34. OMT Support for RBS
2x06 dual band configurations
added in chapter 5.25. Memory
requirements for APZ 212 20
and APZ 212 25 are clarified
(chapter 3.5). Mixed HW
configurations added in chapter
3.2.2. Recovery of EGPRS
Channels added in chapter
5.24. HW restriction added for
Self Configuring Transcoder
Pools (chapter 5.12.2). Chapter
3.3 updated regarding BTS
compatibility.
G 2003–10–24 EPKHASP The changes are:

Capacity and Performance for
the BSC is updated (chapter
3.1.1). Memory requirements for
NNRP-4 added (chapter 5.36.5)
4 2/10948-HSC 103 12/4 Uen M 2004-09-17

Table 1
sion
H 2003–10–28 EPKHASP Description of the feature
Flexible SDCCH Allocation
updated (chapter 5.8)
J 2003–12–12 EPKHASP Information added in chapter 3.6

that OSS-RC does not support
the same character set as in
GSM OSS.
Note added in chapter
3.2.2 regarding Mixed HW
Configuration.
Chapter 3.2.2 updated with
information regarding increased
SW support for RBS 2308.
Minor updates in chapter Flexible
Positioning Support (5.38)
K 2004–03–12 EPKATRO Information on changed
counters added in chapter
8.2. Information added in
tables in chapter 8.2.2–8.2.4.
New chapter 8.2.5 added with
non-functional counter changes.
L 2004–04–29 EPKATRO Corrections of typing errors in
chapter 8.2.2.
M 2004–09–17 EPKATRO Corrected chapter 8.1.2
according to TR HE85556 (no
new bit in GPRSPrio)
2/10948-HSC 103 12/4 Uen M 2004-09-17 5

3 General Impact
3.1 Capacity and Performance
3.1.1 BSC
The CP capacity drop compared to BSC R9.1 with the BAS2 traffic model is
roughly 8% for APZ 212 20/25 and 3% for APZ 212 30. The higher impact
for APZ 212 25 and APZ 212 20 is due to the limited PS cache memory in
those processors. Note that the capacity drop depends on the traffic mix in
the network.
The TRH traffic capacity drop compared to BSC R9.1 is estimated to be 5% for
the BAS2 traffic model.
The PCU processor capacity is slightly decrased but the dimensioning rule that
the RPP can handle traffic on all supported GSL channels is not changed.
However since we so far have very limited experience from heavy live GPRS
traffic with R10 features like QoS Streaming the dimensioning rule may be
changed for the case with heavy traffic per GSL channel.
3.1.2 OSS
The OSS capacity and performance are not yet estimated.
3.1.2.1 Configuration A
This configuration consists of a single master server. It is designed to manage

small networks.
Table 2 Supported maximum network configuration for configuration A

Description Value
Number of MSCs 5
Number of xGSNs 2
Number of SMPCs 2
Number of BSCs 10
Total number of cells 1 000
Total number of neighboring cell relations 25 000
Total number of TRXs 3000
6 2/10948-HSC 103 12/4 Uen M 2004-09-17

3.1.2.2 Configuration B

medium sized networks.
Table 3 Supported maximum network configuration for configuration B

Description Value
Number of MSCs 40
Number of xGSNs 13
Number of SMPCs 16
Number of BSCs 80
Total number of TRXs 24 000
3.1.2.3 Configuration C

large networks.
Table 4 Supported maximum network configuration for configuration C

Description Value
Number of MSCs 75
Number of xGSNs 23
Number of SMPCs 30
Number of BSCs 150
Total number of TRXs 45 000
3.2 Hardware
3.2.1 BSC HW
Supported HW combinations are:
• APZ 212 20 in combination with IOG 20C (Both BYB 202 and BYB 501).
2/10948-HSC 103 12/4 Uen M 2004-09-17 7

• APZ 212 25 in combination with IOG 20M, only for the one cabinet BSC
and BSC/TRC configurations (BYB 501 only).
• APZ 212 30 in combination with APG40.
• APZ 212 33C in combination with APG40.
• TRA R4, R5A and R5B in BYB 202.
• TRA R5A and R5B in BYB 501.
• TRA R6 in AXE 810
• RPD and RPG1 in BYB 202.
• RPP 202 and RPP 501 in BYB 202.
• RPP 501 in BYB 501.
• ETC4 in BYB 202.
• ETC5, ETC T1-H in BYB 501 and BYB 202
• ET155-7 in BYB 501.
• ET155-1 in AXE 810
• RPG3 in AXE 810 and BYB501
• RPG2 in BYB501
Note in BSS R10, support for NNRP4 is introduced. This process allows the
upgrade of BYB501 group switch to GS890(AXE810) group switch.
3.2.2 BTS HW
The RBS 2000 platforms are supported (RBS 2106, RBS 2206, RBS 2207,
RBS 2308 and older RBS 2000 platforms).
The RBS 200 platform is also supported.
A new RBS 2207 is introduced in BSS R10 and is based mainly on the RBS
2206 platform. A maximum of 3 dTRUs will be supported. The software support
for RBS 2207 is introduced in BTS 10.1B.
The RBS 2308 is the new micro base station and is introduced in BSS R10 for
800, 900, 1800 and 1900 frequencies. The software support for RBS 2308 is
introduced in BTS 10.1B. For GSM 800 and GSM 1900, it is also possible to
run RBS 2308 with BTS SW 9.1C and 10.1A but in this case without support for
the feature Synchronised Radio Networks.
EDGE double TRU for 1800 MHz and 900 MHz are introduced (RBS 2106
and RBS 2206/2207).
A new internal Hybrid Combiner Unit (HCU) is introduced in RBS 2106 and
2206. The purpose is to be able to build large configurations with less number
of antennas and still support synthesised frequency hopping.
A new RBS configuration, Double DXU EDGE (for 1900 MHz only) is also
supported in BTS SW 9.1D. This allows DXU-21 + sTRU to be added to RBS
2202 and RBS 2102 to co-exist with the existing DXU-11 and non EDGE
TRUs in the same cabinet. These are considered 2 TGs by the BSC and are
connected via TG-SYNC. Note that the needed number of TGs per BSC will
8 2/10948-HSC 103 12/4 Uen M 2004-09-17

increase due to the fact that each BTS where the mix configuration is introduced
need to have an extra TG to handle the new HW (i.e. DXU-21 with s-TRUs).
The maximum number of TGs that can be connected to a BSC is still 512.
The following features are impacted by the Double DXU EDGE configuration:
1) The feature AMR requires that all TRUs in a cell are capable of handling
AMR. When using the Double DXU EDGE configuration, the existing TRU’s
needs to be able to support AMR in order for the subcell to support AMR.
2) If a cell is served by a TG cluster and is configured to use either base band or

synthesized frequency hopping, then the hopping sequence cannot extend over
more than one TG. This follows from the fact that a given hopping sequence
can only be defined for one channel group and a given channel group can
only be defined for one TG.
3) The feature Software Power Boost require an even number of TRXs to work.
The cTRU and sTRU can not be combined for this purpose. This means that an
even number of sTRUs/cell and an even number of cTRUs/cell are required.
See table 5 for further information regarding support for new R10 features.
A new RBS configuration, Mixed HW Configuration, is supported in BTS SW

10.2A. This configuration enables a cost effective introduction of EDGE in
existing networks by making it possible to deploy RBS 2000 configurations
containing a mixture of pre-core units (TRU, ECU) as well as core based units
(DXU-21, sTRU). With this feature, it will be possible to introduce EDGE support
in RBS 2202/2102 cabinets by exchange non-EDGE capable TRU with new core
based EDGE capable sTRU. In addition to adding sTRU, the old DXU-01/03/11
will also have to be replaced with a new DXU-21. The frequencies 900, 1800,
1900 MHZ will be supported. For impact on other features, see table 5 below.
Note that Mixed HW Configuration does not include any changes in the
operational documents in BSS R10.
2/10948-HSC 103 12/4 Uen M 2004-09-17 9

Table 5 New Feature support on various RBS platforms.

Feature RBS 200 RBS RBS RBS RBS
200 2000 2000 2000 2000
203 2101 2301 2102 2106
204 2102 2302 2202 2206
205 2202 2401 DDE or 2207
SPU+ DXU-01 Mixed 2308
SPU++ DXU-03 HW Con-
SPE DXU-11 figuration
TRU with
EDGE
sTRU
(non
EDGE
TRU can
be con-
nected
but only
support-
ing func-
tionality
as per
column
2)
Flexible SDCCH X X X X X
Allocation
Increased X X X X X
SDCCH
Capacity
AMR / AMR HR — X X1 X X2
IRC — — — X X
Antenna — — — — X
Hopping
IDB and HW — — — — X
Consistency
Check
Battery Test — X — X X3
Synchronised — — — X X
Radio Networks
EDGE (UL) — — — X X
Paging X X X X X
1:RBS 2301 supported only if revision R6A or higher.
10 2/10948-HSC 103 12/4 Uen M 2004-09-17

2:AMR FR is already supported in BSS R9.1
3:Battery test not supported on RBS 2308
3.2.3 OSS HW
The following Sun Enterprise and Sun Fire servers/products are supported in
OSS-RC 1.1 provided that the network load is lower or the same as in R9.1.
• E4500, E5500 and E6500 (CPU model 400MHz)
• SF V880, SF 4800 and SF 6800 (CPU model 1.05GHz)
• Sun StorEdge D1000/A1000 and A5200 disk system with disk capacity from
18/36 GB per disk and T3 disk system with 36 GB per disk
• Workstations of three models, Ultra 5, Ultra 10 and Blade 150
Old OSS HW may also be used. Please see Sales Configuration Guide for
OSS RC 1.1 for details.
3.3 Implementation
The following upgrade paths to BSS R10 are supported:
For BSS R9.1 to BSS R10
1 OSS R9.1 to OSS-RC 1.1
2 BSC R9.1 to BSC R10
The order of TRC, BSC/TRC and BSC is independent.
3 If BSC is upgraded to R10 before upgrading BTS SW:
BTS 9C to BTS 10A (valid for RBS 2101/2102/2202/2301/2302/2401)
BTS 9.1B/9.1C/9.1D to BTS 10.1A/10.1B (valid for RBS

2106/2206/2207/2308 HW).
BTS 9C/10A or 9.1D/10.1A/10.1B to 10.2A (valid for Mixed HW

Configuration (RBS2102/2202))
BTS 9B to BTS 10A (valid for RBS 200)
If BTS is upgraded before BSC:
BTS 9A/9B/9C to BTS 10A (valid for RBS 2101/2102/2202/2301/2302/2401)
BTS 9.1A/9.1B/9.1C/9.1D to BTS 10.1A/10.1B (valid for RBS

2106/2206/2207/2308 HW).
2/10948-HSC 103 12/4 Uen M 2004-09-17 11

BTS 9A/9B/9C/10A or 9.1D/10.1A/10.1B to 10.2A (valid for Mixed HW

Configuration (RBS2102/2202))
To upgrade RBS200 SW before the BSC is not supported.
4 SMPC 5.0 to SMPC 6.0
SMPC can be upgraded independent of the other nodes.
For BSS R10 NA ED to BSS R10
1 OSS R10 NA ED to OSS-RC 1.1
2 BSC R10 NA ED to BSC R10
The order of TRC, BSC/TRC and BSC is independent.
3 If BSC is upgraded to R10 before upgrading BTS SW:
BTS 9C to BTS 10A (valid for RBS 2101/2102/2202/2301/2302/2401)
BTS 9.1B/9.1C/9.1D to BTS 10.1A/10.1B (valid for RBS

2106/2206/2207/2308 HW).
BTS 9C/10A or 9.1D/10.1A/10.1B to 10.2A (valid for Mixed HW

Configuration (RBS2102/2202)
If BTS is upgraded before BSC:
BTS 9A/9B/9C to BTS 10A (valid for RBS 2101/2102/2202/2301/2302/2401)
BTS 9.1A/9.1B/9.1C/9.1D to BTS 10.1A/10.1B (valid for RBS

2106/2206/2207/2308 HW).
BTS 9A/9B/9C/10A or 9.1D/10.1A/10.1B to 10.2A (valid for Mixed HW

Configuration (RBS2102/2202)
4 SMPC 5.0 to SMPC 6.0
SMPC can be upgraded independent of the other nodes.
BSS R10 is compatible with the following non-BSS nodes
• MSC R9.1
• MSC R10/R3
• SGSN G 3.0
• SGSN 5.0 (G)
• SGSN R5.5
• CGSN G 3.0
12 2/10948-HSC 103 12/4 Uen M 2004-09-17

3.4 Interface
All BSS interfaces have been updated to comply to 3GPP/GSM Release
4/December 2001. See Statement of Compliance (SoC) documents for more
information.
3.5 Memory
3.5.1 General
The memory estimate is based on BSS R9.1 with estimate on BSS R10
functionality added. The CP memory impact is estimated to an increase of
approx. 6–10 MW16.
The APZ memory limits are according to the table below. The maximum values
are specified and possible reduction steps within parenthesis.
Table 6 Memory Limits

APZ PS DS RS
type
212 25 64 MW16 (fixed) 252 MW16 (fixed) 2 MW32 (fixed)
212 20 64 MW16 (fixed) 380 MW16 (64 MW 2 MW32 (fixed)

steps)
212 30 96 MW16 (fixed) 4 GW16 (512 MW 32MW16 (fixed)

Steps) *
212 1 or 2 GW16
33C configurable for PS,
DS and RS.
*512 MW16 steps are valid for DRAM based boards, 32 MW steps are valid for
SRAM based boards (BSC only uses DRAM boards)
3.5.2 Stand-alone TRC Node
3.5.2.1 APZ 212 25
The processor is always equipped with 64 MW16 PS and 252 MW16 DS which
is enough to handle the largest TRC.
3.5.2.2 APZ 212 20
The processor is always equipped with 64 MW16 PS which is enough to handle

the largest TRC.
2/10948-HSC 103 12/4 Uen M 2004-09-17 13

The minimum memory requirement for DS when using fixed SAE settings is
252MW16.
3.5.2.3 APZ 212 30
The processor is always equipped with 96 MW16 PS and minimum of 512

MW16 DS which is enough to handle the largest TRC.
3.5.2.4 APZ 212 33C
The processor is always equipped 1024 MW16 DS which is enough to handle

the largest TRC.
3.5.3 Stand-alone BSC or combined BSC/TRC Node
3.5.3.1 APZ 212 25
is enough to handle the largest BSC/TRC. See also chapter 3.5.4 for further
information regarding upgrade to BSC R10.
3.5.3.2 APZ 212 20
The processor is always equipped with 64 MW16 PS which is enough to handle

the largest BSC/TRC.
The recommended DS memory when using fixed SAE settings is

316MW16/508MW16 (the memory size differs depending on if 64 MW or 256
MW memory boards are used). In some cases 252 MW16 might be enough,
see chapter 3.5.4 for further information regarding upgrade to BSC R10.
3.5.3.3 APZ 212 30
is enough to handle the largest BSC/TRC.
3.5.3.4 APZ 212 33C
The processor is always equipped with 1024 MW16 DS which is enough to

handle the largest BSC/TRC.
3.5.4 Memory Requirements during Upgrade

In order to be able to upgrade to R10 MD, 58 MW16 free DS memory is required.
This may not be available in BSCs with APZ 212 25 with Beamon switch or APZ
212 20 with 252 MW DS and Beamon switch. The amount of free memory
will be checked in the upgrade scripts for APZ 212 20 and APZ 212 25 and if
necessary, a reduction of SAE 538 will be performed during upgrade. However,
14 2/10948-HSC 103 12/4 Uen M 2004-09-17

for APZ 212 20, this SAE reduction may not be enough for large switches and
further actions may be required. This has to be investigated for each case.
3.6 Operations
See each specific feature for a detailed description.
The Information Model Handler (IMH) in GSM OSS is restricted to use the US
ASCII character set with the following limitations: """, "*", ",", ";", "\", "<", ">",
".", "’", "%", "~", "(", ")", "&", "|", "?", "^”, ´“”, “‘” In OSS-RC only the following
characters are allowed: "A-Z", “a-z”, “0-9”, "-", “#”, "[]", "_" .
The consequence of this for the migration in OSS-RC is that if any characters
are used that are not allowed in OSS-RC, they will be substituted by "_". It is
therefore strongly recommended to change those characters before starting
the migration to OSS-RC since those characters are not allowed in OSS-RC
and consequently it’s impossible to import Network Elements and Sites into
OSS-RC containing those characters. If not done in advance it will for example
not be possible to reconnect the FM specific data (for example heart beat and
management groups) to the Managed element.
3.7 Other Features

The SPP/Extended Range requirement on the BSC to support RBS 200 R7 SW

is not included in BSS R10.
3.8 Other Network Elements

Table 7 Inter-node dependencies for BSS R10 Features

BSS R10 Feature MSC SGSN MS
Network Assisted — SGSN 3.0 Rel 4 MS required
Cell Change for full NACC
support.
EGPRS — SGSN 3.0 R99
(EGPRS EGPRS MS
supporting)
GPRS/EGPRS — SGSN 3.0 Rel 4 MS required
End-user High (Supporting to support
Performance GPRS/EGPRS) Extended UL TBF
Mode
2/10948-HSC 103 12/4 Uen M 2004-09-17 15

Table 7 Inter-node dependencies for BSS R10 Features

Quality of Service — SGSN 5.0 (R99 MS supporting
Streaming QoS) R99 QoS
GPRS Quality — SGSN 3.0 (R97 MS supporting
of Service and QoS) or SGSN R97 QoS or R99
Scheduling 5.0 (R99 QoS) QoS
Call Queuing MSC R10 — —
HSL (ANSI) MSC R10 — —
Extended MSC R10 — —
Call Release
Reporting
4 Summary of Impacts
This section is an overview of the impact the features have on the system. If
a feature is classified as ’major’ it means that new hardware is needed before
the feature can be used. Major can also mean that the feature affects other
features or has impact in other ways on the system. For details of the impact,
see each feature description.
4.1 BSS Features

Table 8 Summary of Impacts BSS
Feature Major Minor No Feature New (N)
Impact Impact Impact number or En-
hanced
(E)
Multi Band Cell X FAJ 122 N
085
Intra-cell Handover X FAJ 122 E
290
Dynamic MS Power X FAJ 122 E
Control 260
AMR Power Control X FAJ 121 N
353
16 2/10948-HSC 103 12/4 Uen M 2004-09-17


hanced
(E)
Network Assisted X FAJ 121 N
Cell Change 359
(NACC)
Quality of Service X FAJ 121 N
Streaming 360
GPRS/EGPRS X FAJ 121 N
End-user 375
Performance
Increased SDCCH X FAJ 121 N
Capacity 355
Dynamic FR/HR X FAJ 121 N
Adaptation 361
Call Queuing X FAJ 121 N
362
Self Configuring X FAJ 121 N
Transcoder Pools 356
AMR HR X FAJ 121 N
358
Real Time Event X FAJ 121 E
Data 50
EGPRS X FAJ 121 E
31
Dynamic X FAJ 122 E
Overlaid/Underlaid 430
Subcells
Dynamic HR X FAJ 122 E
Allocation 852
AMR X FAJ 121 E
055
Speech Quality X FAJ 122 E
Supervision 583
High Speed X FAJ 121 E
Signalling Links 30
Advanced Single X FAJ 121 N
Slot Allocation 363
2/10948-HSC 103 12/4 Uen M 2004-09-17 17


hanced
(E)
GPRS/EGPRS X FAJ 121 N
System 366
Improvements
BSS System X FAJ 121 N
Improvements 376
Active BA-list X FAJ 122 E
Recording 396
Advanced X FAJ 121 N
Frequency Handling 372
RE-use of X FAJ 121 N
frequencies within a 374
cell
Reduction of BSC X FAJ 121 E
Restart Time 357
APZ 212 33C X FAJ 121 N
354
Locating X FAJ 122 E
259
Flexible SDCCH X FAJ 121 N
Allocation 367
Paging X FAJ 122 E
210
Synchronised X FAJ 122 N
Radio Networks 081
GPRS Quality X FAJ 121 E
of Service and 32
Scheduling
Antenna Hopping X FAJ 122 N
082
Statistics based X FAJ 122 E
on Measurement 399
Results
Extended Call X FAJ 121 N
Release Reporting 432
Support of AXE 810 X FAJ 121 E
— APG 40 22
18 2/10948-HSC 103 12/4 Uen M 2004-09-17


hanced
(E)
Support of AXE 810 X FAJ 121 E
— APT 1.5 23
Flexible Positioning X FAJ 121 E
Support 51/1
Frequency X FAJ 122 E
Allocation Support 395
4.2 BTS Features

Table 9 Summary of Impacts BTS
Feature Major Minor No Impact Feature
Impact Impact number
Interference Rejection X FAJ 122
(1)
Combining 083
Battery Test X FAJ 122
084
(1)
IRC also includes minor impacts to the BSC
4.3 OSS Features

Table 10
Feature Major Minor No Impact Feature
Impact Impact number
GSM Real Time X FAJ 121 46
Performance
Monitoring
2/10948-HSC 103 12/4 Uen M 2004-09-17 19

5 Impacting BSS Features
5.1 Multi Band Cell

The feature Multi Band Cell introduces the possibility of supporting more than
one frequency band in the same cell, e.g. 900MHz and 1800 MHz. This feature
allows one BCCH to serve all the frequency bands within the cell.
By combing the frequency bands within the same cell it is possible to achieve
further network integration. The traffic can be increased in the frequency
band without BCCH (one extra TCH) and there will be less neighbouring cell
relations. The radio interference in the non-BCCH band will be less (the BCCH
always transmits with maximum output power) and the reuse of frequencies
can be tighter.
The Multi Band Cell solution in BSS R10 allows different frequency bands in
different subcells. A maximum of two bands per cell is supported. Subcell
load distribution is utilised to distribute circuit switched traffic between the
frequency bands.
GPRS/EGPRS support in either band is supported and strategies for PDCH

allocation for dedicated and on-demand channels are introduced.
5.1.1 Capacity and Performance

No CP Impact.
The number of cell relations will be reduced in a Multi Band Cell network
compared to a traditional ’dual-band site’ network with multiple frequency
bands. The amount of inter cell handovers are expected to be reduced since
the same cell can handle more than one frequency band. The amount of intra
cell handovers are expected to be increased.
Less number of cells in an area will result in larger cells with respect to the
number of TRX per cell. Less paging load is expected due to this and also
higher traffic levels can be achieved at the same congestion level.
5.1.2 Hardware
No impact.
5.1.3 Implementation
No impact.
20 2/10948-HSC 103 12/4 Uen M 2004-09-17

5.1.4 Interface
The following OSS External Interfaces are impacted,
CNA Interface (Import/Export)
PMR Export of CTR/MTR/CER Recording Results
5.1.5 Memory
No impact.
5.1.6 Operations
The following new OPIs are introduced,’ BSC Multi Band Cell, Initiate’ and
’BSC Multi Band Cell, End’.
The following OPIs are updated, ’BSC Cell System Information Data Change’
and ’BSC, Internal Cell Data, Change’.
The following commands are modified following the introduction of this feature,
RARDC, RLCFI, RLDGE, RLDGI, RLDEC, RLDGC, RLOLC, RLLOC, RLHPC
and RLHPP.
The following printout descriptions are modified, ’ Cell Channel Group Data’,
’Cell Locating Data’,’Cell Resources’,’CERFIL’, ’CTRFILE’, ’MTRFILE’.
The following Adaptation Directions are modified, ’ RCCDA, Mobile Telephony

Data: Addition of a Cell to the BSC’, ’RCCDA, Mobile Telephony Data:Deletion
of a Cell from the BSC’.
The following Application Information is modified, ’RCCD’, ’ RCCGD’, ’RMCC’,

’RNLCT’, ’ RNSDCCH’, ’RNTCH’, ’RQCD’, ’ROPEC’.
PMR, BSM, CNA and CNAI in OSS are modified to support Multi Band Cell.
5.1.7 Other Features

The features Advanced Frequency Handling and GPRS/EGPRS End-user
Performance are required for GPRS/EGPRS in both bands in the cell.
5.1.8 Other Network Elements

No impact.
2/10948-HSC 103 12/4 Uen M 2004-09-17 21

5.2 Intracell Handover

The existing feature Intracell handover and function Bad Quality Urgency
allow the operator to set thresholds/parameters which reduce unnecessary
handovers within the network for the FR, EFR and HR codecs. The AMR
codec adapts to the radio environment and is therefore more robust than the
FR, EFR or HR codecs. In order to utilise this benefit of AMR, this feature
introduces the possibility to set separate quality thresholds specific for AMR FR
from the other codecs.
No Impact.
5.2.2 Hardware
No impact.
No impact.
5.2.4 Interface
5.2.5 Memory
No impact
5.2.6 Operations
Operator must specify the new thresholds for AMR FR.
The following OPI are updated due to this feature, ’BSC, Cell Locating Data,
Change’.
The following command descriptions are updated, ’RLHIC’, ’RLLIP’.
The following printout description are updated, ’Cell Locating Intracell Handover
Data’
The following Application information is updated, ’RQCD’ and ’RMHBI’.
22 2/10948-HSC 103 12/4 Uen M 2004-09-17

CNA and CNAI in OSS are modified to support this feature.
AMR is required.
No impact.
5.3 Dynamic MS Power Control

The feature Dynamic MS Power Control in enhanced by replacing the algorithm
to one which performs the same way as the dynamic BTS power control which
was introduced in BSS R7.1. The new Dynamic MS Power Control Algorithm
has better overall general performance.

No CP impact.
Minor impact on TRH capacity.
5.3.2 Hardware
No Impact.
No Impact.
5.3.4 Interface
5.3.5 Memory
No impact
2/10948-HSC 103 12/4 Uen M 2004-09-17 23

5.3.6 Operations
The Dynamic MS Power Control Parameters will require tuning to achieve

optimal performance of the new algorithm.
The following OPIs are updated, ’BSC, Dynamic MS Power Control Cell Data,
Change’, ’BSC, Dynamic Mobile Subscriber Power Control, Activate’ and ’BSC,
Dynamic Mobile Subscriber Power Control, Deactivate’.
The following command descriptions are updated, ’RLPCC’, ’RLPCI’, ’RLPCE’,

’RLPCP’.
The following printout description is updated ’ Dynamic MS Power Control Cell

Data’.
The following Application information is updated, ’RQCD’.

No impact

No impact.
5.4 AMR Power Control

The feature introduces separate parameter settings for AMR for the features,
Dynamic BTS Power Control and Dynamic MS Power Control. This allows
the improved robustness gained via the AMR codec to be utilised to achieve
capacity gain in networks that have a mixture of AMR and non-AMR traffic.

No CP impact.
5.4.2 Hardware
No impact.
No impact.
24 2/10948-HSC 103 12/4 Uen M 2004-09-17

5.4.4 Interface
5.4.5 Memory
No impact
5.4.6 Operations
A new OPI, ’BSC, AMR Power Control Cell Data, Change’ is introduced and the
OPI ’ BSC, Internal Cell Data, Change’ is updated.
The following new commands are introduced, ’RLAPC’, ’RLAPI’, ’RLAPE’,

’RLAPP’.
A new printout description is introduced, ’AMR Power Control Cell Data’.
The application information for ’RQCD’ is updated.
The operator must purchase the optional features, Dynamic BTS Power Control
and Dynamic MS Power Control before using this feature.

No impact.
5.5 Network Assisted Cell Change (NACC)

The feature Network Assisted Cell Change (NACC) allows the BSS to assist a
GPRS/EGPRS MS upon cell reselection while in Packet Transfer Mode. NACC
will significantly reduce the service outage time for Intra-BSC cell reselection.
NACC is only used for cell reselection between GSM cells.

No CP Impact.
NACC will reduce the service outage time on Intra-BSC cell change from
1–5seconds down to 0.3–1 seconds for Release 4 compliant mobiles. This
2/10948-HSC 103 12/4 Uen M 2004-09-17 25

will significantly improve performance by increasing throughput and releasing

bandwidth.
For non-release 4 GPRS mobiles that support the message PACKET PSI
STATUS (3GPP 44.060) the NACC feature will reduce the service outage
time at cell change although the reduction will not be as high as for NACC
supporting Release 4 mobiles.
5.5.2 Hardware
No Impact.
No Impact
5.5.4 Interface
The Um interface is affected.
5.5.5 Memory
No Impact.
5.5.6 Operations
The following application information is updated, ’ROEPC’.
NWS CNA and CNAI in OSS are updated to support this feature.
The feature GPRS is required.
Release 4 MS is required to obtain full benefits of NACC.
26 2/10948-HSC 103 12/4 Uen M 2004-09-17

5.6 Quality of Service Streaming

The feature Quality of Service (QoS) Streaming provides support of the QoS
traffic class ’Streaming’ making it possible to fulfill Guaranteed Bit Rate (GBR)
requirements necessary for streaming applications in cells with high traffic load.
The GSM R99 standard describes four QoS classes, background, interactive,
streaming and conversational. In BSS R9.1, the first two. background and
interactive are introduced as part of the QoS feature. In BSS R10 support
for the streaming class is introduced.
New attributes are introduced in the standard for the QoS streaming class,
Transfer delay, Guaranteed Bit Rate (GBR) and SDU format. GBR is the
requested bitrate on LLC level and is the only new supported attribute in BSS
R10. GBR is only supported in the downlink direction. Although a streaming
application may run on an interactive bearer, it is this new attributes which
enables the QoS Streaming user to secure resources with the necessary bitrate
for a streaming application.
It is assumed the user has already activated a PDP context when wanting to
initiate a streaming application. A secondary PDP context is activated and
PDCHs are reserved for the streaming application. These PDCHs are marked
for streaming and may not be used by any other streaming user. However
interactive and background users may be multiplexed on these PDCHs. The
number of actual reserved PDCHs will be determined by GBR, CS load, number
of channels occupied already by other streaming users and by a bitrate/PDCH
parameter, settable by the operator to control coverage of streaming services in
the cell. If the streaming user does not get the requested resources, attempts
are made to upgrade the number of PDCHs to the user. If this is successful
then a re-negotiation of GBR is performed. If the MS moves to a cell with higher
capabilities than the old one, the BSS shall request the SGSN to make a
download of the original ABQP to re-negotiate the PFC to ensure the highest
possible bitrate for each cell is achieved.
The operator can choose if PDCHs allocated by a streaming user are allowed
to be pre-empted by circuit switched traffic or not.

No CP Impact.
5.6.2 Hardware
No Impact
No Impact
2/10948-HSC 103 12/4 Uen M 2004-09-17 27

5.6.4 Interface
Gb and Um interfaces are impacted.
The following external interfaces in OSS are updated,
CNAI, NWS Universe and NWS Reports.
5.6.5 Memory
No Impact
5.6.6 Operations
The following OPIs are updated due to this feature, ’BSC, General Packet Radio
Service Quality of Service, Change’, ’BSC, General Packet Radio Service
Quality of Service, Activate’ and ’BSC, General Packet Radio Service Quality of
Service, Deactivate’.
The following new commands are introduced, ’RLGQC’, ’RLGQI’, ’RLGQE’

and ’RLGQP’.
The following new printout descriptions are introduced, ’CELL GPRS Quality
of Service Data’.
The following Application information is updated, ’RCS GRC Radio Link Control
Changeable Exchange Adaptation’.
CNA, CNAI, SDM and NWS in OSS are updated to support this feature.
The features, GPRS and GPRS Quality of Service and Scheduling, are required
in order to use this feature.

SGSN supporting Quality of Service Streaming and terminals compliant to R99
are required to use QoS Streaming.
5.7 GPRS/EGPRS End-user Performance

The feature GPRS/EGPRS End-user Performance provides enhancements to
the features GPRS and EGPRS which increase the end-user performance.
These include;
Delayed TBF release of Downlink TBFs:
28 2/10948-HSC 103 12/4 Uen M 2004-09-17

This is a mechanism to keep a TBF alive when expecting more downlink data to
arrive that will reduce frequent TBF setup / releases. With this, the throughput
is improved, especially for ’bursty’ traffic such as web browsing and E-mail etc.
Dynamic UL/DL Resource Handling :
With this enhancement the TBFs are changed in accordance with the
applications needs. If the main direction of application transfer is in uplink then
the downlink TBF is downgraded and the uplink TBF is upgraded.
TBF Upgrading:
For TBFs running on fewer than requested PDCHs, PDCHs are added to the
reservation without moving the TBF.
Re-reservation of an existing TBF:
This feature enables an existing TBF to be moved from channels that don’t
fulfill the requirements of the TBF to channels that better correspond to the
requirements. This will result in better utilisation of the PDCHs as the traffic
load will be more evenly distributed within the cell. Note that re-reservation of
an existing TBF is only supported within a certain TBF mode.This means that
the TBF mode will not be changed at re-reservation.
Early Set-up of Downlink TBFs:
A faster set-up on the downlink is triggered by information in the uplink TBF.

This will reduce the latency.
Extended Uplink TBF Mode:
This is a mechanism to keep an UL TBF alive longer enabling more data to

be sent without setting up new TBFs.
GPRS/EGPRS in Overlaid Subcell:
Prior to BSS R10 GPRS/EGPRS was only supported in the underlaid subcell.
With this feature the possibility to utilise GPRS/EGPRS in an overlaid subcell is
introduced. This is important for configurations where limited number of TRUs
are used within an underlaid subcell. Used together with the feature Multi Band
Cell, GPRS/EGPRS shall be supported no matter which subcell or frequency
band the BCCH is allocated. Similarly when used together with the feature
BCCH in Overlaid Subcell, GPRS/EGPRS can be supported in an overlaid
subcell in which a BCCH is allocated.
Note: If GPRS/EGPRS is configured in OL subcell and the UL subcell is

configured as an extended range cell, the PCU will treat the entire cell as an
extended range cell. For packet data, this means that only half of the channels
can be used and that only single slot channels can be configured in the cell.
Packet Specific Cell Plan:
2/10948-HSC 103 12/4 Uen M 2004-09-17 29

A number of improvements are introduced enabling GPRS/EGPRS specific cell

planning to adapt to GPRS/EGPRS specific conditions. A cell border offset for
GPRS/EGPRS services and a separate HCS (Hierarchical Cell Structures)
feature for GPRS/EGPRS is introduced.

No CP Impact.
GPRS/EGPRS end-user throughput in DL will be improved (e.g. estimated of

up to 20–30% for web browsing) due to the decreased frequent TBF set-ups
resulting in a decreased delay on application level.
GPRS/EGPRS end-user throughput in UL will be improved (up to 100%) due

to the dynamic uplink/downlink resource handling.
By introducing specific cell reselection parameters for GPRS/EGPRS specific

conditions, the number of cell reselections can be reduced without impacting
circuit switched speech quality resulting in decreased interruptions in packet
flow.
5.7.2 Hardware
No Impact.
Radio Network planning should consider that the overlaid subcell coverage
should be at least the same as the underlaid subcell coverage when
GPRS/EGPRS in Overlaid Subcell is utilised. Radio Network planning is
required to tune the cell reselection parameters.
5.7.4 Interface
The UM interface is impacted.
NWS Universe and NWS Reports.
5.7.5 Memory
No Impact.
30 2/10948-HSC 103 12/4 Uen M 2004-09-17

5.7.6 Operations
The following application information is updated due to this feature, ’ROEPC’,

’RCCD’, ’RQCD’.
The following new OPIs are introduced due to this feature, ’BSC, Packet
Specific Cell Plan Data, Change’,
The following new command descriptions are introduced, ’RLPSC’, ’RLPSP’,

’RLGNC’, RLGNP’,’RLNSC’,
The following printout descriptions are introduced to support this feature ’Packet
Neighbour Relation Data’ and ’Packet Specific Cell Plan Data’
CNA, CNAI and NWS in OSS are modified to support this feature.

The feature GPRS is required. The feature EGPRS is enhanced by this feature.
If Hierarchical Cell Structures are to used for GPRS/EGPRS then the feature
Multi Layered HCS is required.
If this is used together with the feature Multiband Cell, GPRS/EGPRS will be
supported no matter in which subcell or frequency band the BCCH is allocated.
Also with this feature, it shall be possible to use GPRS/EGPRS together with
the feature BCCH in Overlaid Subcell.

SGSN and mobiles supporting GPRS (EGPRS for EGPRS enhancements) are
required. Mobile supporting more than 1 TS in UL are required to avail of the
dynamic UL/DL resource handling. Release 4 mobiles are required to utilise
Extended Uplink TBF Mode.
5.8 Flexible SDCCH Allocation

Flexible SDCCH Allocation provides flexibility when allocating SDCCH in a cell,
allowing configuration of SDCCH on the most suitable carrier. Therefore up to
eight SDCCH/8 timeslots can be allocated on any carrier in the air-interface and
not just on the BCCH carrier.
The load generated by a SDCCH/8 timeslot is much higher than a traffic

channel, and allocating multiple SDCCH/8 on a transceiver, can impact the
BSC hardware dimensioning. In order to control the impact and even avoid it
when the additional flexibility is not needed, it is possible to set the number of
SDCCH/8 timeslots that a transceiver is allowed to handle. The maximum
number of SDCCH/8 that can be configured on a transceiver is four.
2/10948-HSC 103 12/4 Uen M 2004-09-17 31

In the radio base station there is not a one-to-one relation between a transceiver
and what is transmitted on the air-interface (carrier). In order to optimize
the hardware and A-bis link utilization, the BSC will automatically spread
the SDCCH/8 between all possible transceivers to distribute the load. The
inter-transceiver bus (also used for baseband frequency hopping) is used to put
the information onto the correct carrier. The consequence of this is that if, for
example eight SDCCH/8 timeslots are required on a carrier, then at least two
transceivers carrying four SDCCH/8 each are needed.
Note that Flexible SDCCH Allocation does not increase the total number of
SDCCH that can be configured in a cell, instead it enhances the flexibility of
where to put them. If additional SDCCH capacity is required then the feature
FAJ 121 355 Increased SDCCH Capacity should be used.
One example when multiple SDCCH on a transceiver is needed is when EDGE

and/or CS3/CS4 is introduced. Since it is not desired to allocate SDCCH
on EDGE or CS3/CS4 enabled transceivers, other transceivers might have
to handle multiple SDCCH/8 instead in order to maintain SDCCH capacity.
Another example is when the feature FAJ 122 085 Multi Band Cell is used. If
support for single band terminals is required, then SDCCH cannot be allocated
to the non-BCCH frequency band. For similar reasons the possibility to forbid
allocation of SDCCH in certain channel groups is also introduced.
Multiple SDCCH/8 per transceiver is also needed when the feature FAJ 121
355 Increased SDCCH Capacity is used.

No CP Impact.
The possibility for the operator to allocate SDCCH capacity per cell is introduced
as follows,
The amount of SDCCHs possible to define in a cell is equal to the number

of TRXs defined in that cell.
Maximum number of SDCCH/8s per TRX is increased from 1 to 4.
The number of TRX per RPG3, RPG1/2 and RPD (TRH capacity) is reduced
due to the increase of the number of SDCCH/8s per TRX.
The operator will be able to set, with an exchange property, the number of
SDCCH/8s per TRX possible to configure in the BSC. The following table
describes the impact.
32 2/10948-HSC 103 12/4 Uen M 2004-09-17

Table 11 Maximum number of TRX per TRH

TRH/RP TYPE Number of Allowed number of TRX
SDCCH/8s/TRX per TRH
possible to configure
RPD 1 7
2 6
3 not supported
4 not supported
RPG 1/2 1 24
2 20
3 18
4 16
RPG 3 1 32
2 32
3 28
4 24
5.8.2 Hardware
No Impact.
No Impact.
5.8.4 Interface
CNAI, CNA Interface (Import/Export)
5.8.5 Memory
No Impact.
5.8.6 Operations
The following OPIs are updated due to this feature; ’ BSC, Adaptive
Configuration of Logical Channels, Change’, ’BSC, Cell Description Data’.
2/10948-HSC 103 12/4 Uen M 2004-09-17 33

The following command descriptions are updated, ’RLACC’, ’RLBDC’, ’RLCCC’,

’RLCFE’, ’RLCHC’, ’RLDEC’.
The following printout descriptions are updated, ’Cell Adaptive Logical Channel
Configuration’, ’Cell Configuration Frequency Data’, ’Cell Configuration
Frequency Hopping Data’.
The following application data is updated, ’RCCGD’, ’ROEPC’.
CNA, CNAI and BSM in OSS are modified to support this feature.

This feature replaces the feature Flexible SDCCH Handling.
This feature can be extended with more signalling capacity in a cell with the
optional feature, Increased SDCCH Capacity.

No Impact.
5.9 Dynamic FR/HR Mode Adaptation

The feature Dynamic FR/HR Mode Adaptation allows the operator to direct
ongoing traffic for each cell towards FR or HR calls, which will give better
flexibility to control the traffic resources. By setting separate FR/HR Mode
adaptation thresholds for AMR and non-AMR mobiles it shall be possible to
steer AMR capable mobiles to AMR-HR during high traffic load, increasing
capacity while utilising improved speech quality of AMR-HR over HR. Speech
quality thresholds are introduced for both non-AMR and AMR calls to determine
if the speech quality is acceptable for adapting FR calls to HR.
The channel quality for HR calls shall be continuously supervised. Two new
quality thresholds are introduced, one for AMR and one for non-AMR calls to
determine when a change of channel rate HR to FR is preferred in order to
obtain better speech quality.

No CP Impact.
This feature allows the operator the possibility to improve the call capacity per
cell by efficient use of HR and AMR-HR.
34 2/10948-HSC 103 12/4 Uen M 2004-09-17

5.9.2 Hardware
No Impact.
No Impact.
5.9.4 Interface
The following OSS External Interfaces are impacted;
CNA Interface (Import/Export).
5.9.5 Memory
No Impact.
5.9.6 Operations
The following new OPI is introduced, ’BSC Cell Dynamic FR/HR Mode
Adaptation Data Change’.
The following new command descriptions are introduced, ’RLDMI’, ’RLDMC’,

’ RLDMP’, ’RLDME’.
The following printout descriptions are updated, ’Cell Dynamic FR/HR Mode
Adapation Data’, ’CTRFILE’, ’ MTRFIL’, ’CERFIL’.
The following application information is updated, ’RCCD’, ’ROEPC’.
NWS, PMR, CNA and CNAI in OSS are updated to support this feature.
The features AMR and AMR-HR are required in order to utilise the AMR
parameters/thresholds.

No Impact.
2/10948-HSC 103 12/4 Uen M 2004-09-17 35

5.10 Call Queuing

The feature Call Queuing allows priority defined user’s call attempts to be
queued when there is congestion in the cell. This results in networks that
are nearing congestion to take account of priority of the connection when
distributing resources.
Queuing is a softer way to prioritize certain connections over others than

pre-emption. The advantage of queuing is that there are no resources reserved
for high-priority connections, which results in higher capacity for channel
reservation. Queuing shall be used for TCHs at assignment and intra-BSC
handover. It shall not be supported for immediate assignment on TCH or
SDCCH. There shall be only one queue defined per cell.

By allowing queuing of priority calls at cell congestion, the capacity for channel
reservation increases.
As queuing causes signalling resources to be held while the call is queued

(upto 60s depending on operator setting) this could cause SDCCH congestion
in the cell.
5.10.2 Hardware
No Impact.
No Impact.
5.10.4 Interface
The A-interface is updated.
5.10.5 Memory
No Impact.
5.10.6 Operations
The following new OPI is introduced, ’BSC, MS Queuing, Change’.
36 2/10948-HSC 103 12/4 Uen M 2004-09-17

The following new command descriptions are introduced, ’RLMQC’ and

’RLMQP’.
The following new printout description is introduced, ’Cell MS Queuing Data’.
The following Application Information are updated, ’RMQ’, ’RCCD’. ’RNLCT’,

’ROEPC’.
CNA and CNAI in OSS are updated to support this feature.

This feature requires the enhanced Multi-Level Precedence and Pre-emption
Level (eMLPP) GSM feature.
This feature can be combined with Differential Channel Allocation (DCA) . This
allows operators to reserve part of the cell for priority users, resulting in these
users gaining access to the cell even though ordinary users will experience
congestion. When all channels in the best cell are occupied then incoming calls
will be handled according to the rules of Call Queuing.
Similarly this feature can be used together with eMLPP. In this case a priority
user shall attempt to pre-empt other users to gain access to the cell. If this is
not possible (no other active calls are of type permitting pre-emption) then
incoming calls will be handled according to the rules of Call Queuing.

Requires that MSC supports Queuing. Note that the sending of priority
elements from the HLR to the MSC/VLR requires that MAP V2 is used in the
MSC/VLR and the signalling is the standard version.
5.11 Synchronised Radio Networks

The feature Synchronised Radio Networks offers possibilities to minimize the
interference for a GSM network while maximising frequency hopping gain at
tight frequency reuse, extending spectrum limited capacity with estimated
15–20%. Synchronised radio networks also improves the uplink and the
downlink interference suppression of the feature Interference Rejection
Combining (IRC) and the feature Single Antenna Interference Rejection (SAIR)
with 2–3dB.
This feature is valuable for operators with a limited set of frequencies as well
as for operators with high traffic load.
In the synchronised radio network, the base stations are frame synchronised
to a nominal position so that bursts are aligned and transmitted at the same
time in different cells. The nominal position is calculated by the base station
with the aid of a synchronisation reference. The alignment of bursts introduces
2/10948-HSC 103 12/4 Uen M 2004-09-17 37

the possibility to tighten the frequency reuse. The performance and capacity of
such a network are limited by interference between cells, so mechanisms such
as planning of MAIO and TSC should be utilised to reduce the interference.
The sychronised radio network is fault tolerant and has built in recovery
mechanisms. The base station is able to maintain frame synchronisation even
when synchronisation information is temporarily unavailable, e.g. due to GPS
satellite shadow. For longer interruptions in synchronisation information the
BTS shall still provide service by choosing a back up synchronisation source.
Note that this combination of a primary synchronisation source and backup
synchronisation source shall lead to improved ISP compared to base stations
with a single synchronisation source.
Note that the support for Synchronised Radio Networks on the RBS PPC
platform is provided in BTS software 10.1B.

No CP Impact.
Increased spectrum limited capacity with estimated 15–20% while maintaining

the quality of today.
Increased interference suppression of (estimated) 2–3dB (uplink and downlink)

if combined with the features IRC and SAIR.
5.11.2 Hardware
RBSs must be connected with a GPS synchronisation source. RBS 2308 and
RBSs in the RBS 2000 family equipped with DXU-21 are supported.
No Impact.
5.11.4 Interface
Updates are made to the Abis Interface.
5.11.5 Memory
No Impact.
38 2/10948-HSC 103 12/4 Uen M 2004-09-17

5.11.6 Operations
The following new OPIs are introduced to support this feature, ’Radio X-Ceiver
Administration, Transceiver Group Frame Synchronisation using GPS’, ’Radio
X-Ceiver Administration, Transceiver Group Frame Synchronisation using
GPS Fault, Repair’ and the following OPIs are updated, ’Radio X-Ceiver
Administration, Transceiver Group Synchronisation Fault, Repair’ and ’Radio
X-Ceiver Administration, Transceiver Group Synchronisation’.
The following command descriptions are updated, ’RXMOI’, ’RXMOC’,

’RXMOC’, ’RXMSC’ and ’RXMOP’..
The following printout descriptions are updated, ’Radio X-Ceiver Administration

Managed Object Data’ and ’BCDCFILE ASN.1 Result’.
Application Information for ’RXCMOO’ and ’ROEPC’.
CNAI, BSM and CNA in OSS are updated to support this feature.

This feature can be used in conjunction with the feature ’RBS 2000
Synchronisation’ making it possible to synchronise a RBS without a connected
GPS synchronisation source. This is possible if the RBS is part of a TG
Synchronised cluster with a master TG realised by a RBS with a connected
GPS synchronisation source.
This feature can be used in conjunction with the feature IRC to improve
downlink interference suppression by 2–3dB.
This feature can be used in conjunction with the feature SAIR to improve uplink
interference suppression by 2–3dB.
The feature supports synchronisation towards a non-Ericsson synchronised

BSS within the GSM network.
5.12 Self Configuring Transcoder Pools

The feature Self Configuring Transcoder Pools introduces support for automatic
configuration of the transcoder pools in BSS. This is achieved by analysing
statistics on transcoder pool usage and re-allocating transcoder hardware
between pools to meet the traffic demand.
Thresholds are specified by the operator to determine when and what

percentage of the pool is permitted to be moved. The pools can be reconfigured
daily, e.g. off-peak or triggered immediately by command. The BSC shall
inform FM in OSS that reconfiguration is necessary and FM shall issue the
2/10948-HSC 103 12/4 Uen M 2004-09-17 39

commands to, re-define, load with new codec SW, and move to new pool, the
required transcoder resources. Only ’free’ transcoder resources within the
pool shall be moved.
By utilising this feature the operator will experience simplified O&M of the
Transcoder Pools, have automatic pool redimensioning to match the subscriber
profile, handling situations such as the phased introduction of AMR mobiles in
the market and the possibility to order re-configuration to handle cases where
one pool has reached congestion, eg more HR required during peak busy hour.

No CP Impact.
5.12.2 Hardware
TRA R6, TRA R5A and TRA R5B are supported.
Note that the feature do not support a mix of TRA R5A and TRA R5B equipment
if AMR is activated in the BSC. This is due to that the TRA R5A equipment
do not support AMR.
No Impact.
5.12.4 Interface
No Impact.
5.12.5 Memory
No Impact.
5.12.6 Operations
The following new OPIs are introduced, ’ Radio Transmission Transcoder
Pool Self-Configuration Timeout’, ’Radio Transmission Transcoder Pool Self
Configuration, Initiate’, ’Radio Transmission Transcoder Pool Self Configuration,
END’. The following OPIs are updated, ’Radio Transmission Transcoder Pool,
Change’, ’Radio Transmission Transcoder Pool, Initiate’, ’Radio Transmission
Transcoder Pool, End’, ’Radio Transmission Transcoder Pool Idle Level
Superivision, Initiate’.
The following new command descriptions are introduced, ’RRPSC’, ’RRPSE’,

’RRPSI’, ’RRPSP’, ’RRPLP’, ’RRPAR’.
40 2/10948-HSC 103 12/4 Uen M 2004-09-17

The following new print out descriptions are introduced, ’Radio Transmission
Transcoder Pool Self Configuration’, ’Radio Transmission Transcoder Pool Self
Configuration Data’, ’Radio Transmission Transcoder Pool Self Configuration
Timeout’, ’Radio Transmission Transcoder Pool Change Log’.
The following application information is updated, ’RTTPH’, ’ROEPC’.
A new alarm is added that will be send from the BSC and checked by OSS,
which shall trigger the OPS scripts to be executed.

The features FM (and FMX), OPS and Selfconfiguration transcoder in pool
management (SCTP) (FAJ 121 449) in OSS-RC 1.1 are required.

No Impact.
5.13 AMR HR
The feature Adaptive Multi Rate Half Rate (AMR HR)introduces a new speech
codec type (AMR HR) which adapts the speech codec rate and channel coding
according to the radio environment. AMR HR allows the operator to enhance
capacity at retained speech quality in the radio network i.e. a speech quality
better or equal to FR. By combining AMR HR with features such as AMR Power
Control, Dynamic FR/HR Adaptation and Dynamic HR Allocation, the operator
can fully utilise the capacity benefit of using the HR channel.

No CP Impact.
AMR HR gives twice the capacity as FR with the same or better speech quality.
Similarly use of HR also reduces the transmission costs on Abis.
5.13.2 Hardware
TRA R5B or TRA R6 (part of AXE 810) are required to be able to use AMR HR.
See Table 5 for RBS support.
No Impact.
2/10948-HSC 103 12/4 Uen M 2004-09-17 41

5.13.4 Interface
Updates are made to the A-Interface, A-ter, Abis, Um and TRA-BTS Interface.
5.13.5 Memory
No Impact.
5.13.6 Operations
See feature AMR. New optional feature parameter specific for AMR-HR added,
application information ’ROEPC’ updated to reflect this.

The features Half Rate and Adaptive Multi Rate (AMR) are required to use
AMR HR.

AMR Mobiles and AMR Support in MSC are required.
5.14 Real Time Event Data

The feature Real Time Event Data provides access to radio network events
on a real time basis. This feature together with the OSS feature , Real Time
Performance Monitoring (R-PMO) provides an effective method of monitoring
network performance in real time from the OMC site. The operator can choose
events to be monitored in relation to e.g. traffic load, speech quality, call and
handover performance, and event data is sent to OSS via the signaling terminal
for Open communication (STOC) HW in the BSC on TCP/IP to OSS, where it is
displayed via R-PMO.
In BSS R10 this feature is updated to support monitoring of packet switched

traffic performance, in the areas of, GPRS/EGPRS data throughput, Cell
Reselection performance and Packet Data radio link quality.
Monitoring of Circuit switched traffic is also enhanced by introducing, monitoring

of Handover cause values, monitoring of dropped call values and improved
TCH and SDCCH traffic performance monitoring.
Support for mobile station HW specific monitoring is also introduced.
Real Time Event Data is also updated to support Multi Band Cells (by
monitoring of the Frequency Band Offset for Multiband Cells).
42 2/10948-HSC 103 12/4 Uen M 2004-09-17

This feature impacts CP load. Depending on the number of events and number
of cells that are to be monitored, the CP capacity drop will vary.
All event handling in the BSC are treated with lower priority than than traffic
handling to minimize disturbances to CS and PS traffic capacity. The additional
BSC CP load is estimated to 12% relative load increase with all events active.
This is a relative load increase of approx. 3% compared to BSS R9.1. When
events are dropped due to high load in the BSC, OSS is informed.
This feature also impacts OSS load. Approx 11–12% of the CPU capacity is
used by the R-PMO application when running 3000 cells (à 3 erlang). The
memory consumption is maximum 1.5Gb when running all reports for the whole
network.
The load on the TCP/IP link between BSC and OSS is estimated to maximum
220kbit/s.
The overall performance monitoring is improved by the addition of packet

switched traffic and improvements to the circuit switched monitoring.
5.14.2 Hardware
No new hardware needed in BSS R10. Same hardware requirements as
per R9.1 are still valid for this feature, i.e. additional hardware in the BSC
called STOC is required. STOC is regional processor based, running on
RPG-2E/RPG3 for BYB501 BSCs and RPG3 for AXE810 BSCs. It allows the
BSC to be connected to a TCP/IP channel.
This feature is not supported on BYB202 or mixed BYB202/BYB501 BSC

configurations.
No Impact.
5.14.4 Interface
The OSS-BSC (RNX-BSC) interface is updated to support the new monitors.
5.14.5 Memory
No Impact.
2/10948-HSC 103 12/4 Uen M 2004-09-17 43

5.14.6 Operations
The following command descriptions are updated due to this feature, ’RAPMI’
and ’RAPME’.
This feature should be used in conjunction with the OSS feature, GSM
Real-time Performance Monitoring (R-PMO).

No Impact.
5.15 EGPRS
The feature EGPRS is enhanced to provide support for all MCSs in uplink. Link
Adaptation support in uplink is also introduced.
Functionality is introduced to monitor the Radio Link Bitrate Distribution on

the EGPRS uplink channels.
Support for 900/1800Mhz frequency bands is also introduced for the EDGE
double TRU.

No CP Impact.
By supporting all MCSs in uplink together with link adaptation higher throughput
is achieved in UL. Overall better performance is achieved as the data throughput
in UL is adapted to the quality of the radio environment.
5.15.2 Hardware
DXU-21 with EDGE sTRU or EDGE dTRU is required (see table 5).
The new RBS configurations, Double DXU EDGE and Mixed HW Configuration
are supported. This configuration allows EDGE to be supported on the RBS
2202 / RBS 2102.
EDGE double TRU for 1800 Mhz and 900 Mhz is introduced.
No Impact.
44 2/10948-HSC 103 12/4 Uen M 2004-09-17

5.15.4 Interface
5.15.5 Memory
No Impact.
5.15.6 Operations
The following application information is updated to support the enhancements,
’ROEPC’.
CNAI, CNA and NWS in OSS are updated to support the enhancements.

SGSN and mobiles supporting EGPRS are required.
5.16 Dynamic Overlaid / Underlaid Subcells

The feature Dynamic Overlaid / Underlaid Subcells in enhanced by the addition
of a new threshold called Distance to Cell Border (DTCB). The new threshold
shall co-exist with the existing path loss and timing advance thresholds. DTCB
is calculated as the signal strength difference between the serving cell and the
surrounding neighbour cells in the same frequency band.
Path Loss and Timing Advance thresholds only take the serving BTS into
consideration to ensure the MS does not get too far away from the BTS. In a
high capacity area this is not sufficient as interference is the biggest problem
in these areas and not signal strength. BTSs are usually transmitting at high
power to ensure indoor coverage, resulting in high signal strength at the cell
borders. Due to high frequency utilisation in high capacity areas the MSs at the
cell borders can remain using the wrong channel in the wrong place generating
and receiving interference. The DTCB threshold ensures that an MS shall not
become too close to a neighbour cell, avoiding this interference. The DTCB
and path loss thresholds are configured for each cell. When a threshold is
exceeded for an MS, a handover is initiated to a subcell fulfilling all thresholds.
This enables the operator to optimise the frequency reuse of each subcell ,
insuring maximum capacity while maintaining good speech quality in the area
covered by that subcell.
2/10948-HSC 103 12/4 Uen M 2004-09-17 45

No CP Impact.
DTCB will increase the efficiency of Dynamic Overlaid / Underlaid Subcells

and as a consequence both higher capacity and a significant reduction in
optimization cost can be achieved.
5.16.2 Hardware
No Impact.
No Impact.
5.16.4 Interface
5.16.5 Memory
No Impact.
5.16.6 Operations
The application information ’ROEPC’ is updated to support this feature.
The following command description is updated, ’ RLOLC’.
The following printout descriptions are updated, ’Cell Locating Overlaid Subcell
Data’, ’CTRFILE’, ’MTRFIL’, ’Mobile Traffic Recording Event Report’.
The following application informations are updated, ’RCS Cell Load Sharing
Changeable Exchange Adaptation’ and ’ RCS, RCQS Cell Data Changeable
Exchange Adaptation’.
CNA, CNAI, PMR and NWS in OSS is updated to support this feature.

When the enhanced Dynamic Overlaid / Underlaid Subcells feature is used
as part of the Fractional Load Planning concept, significant capacity gains
can be achieved.
46 2/10948-HSC 103 12/4 Uen M 2004-09-17

No Impact.
5.17 Dynamic HR Allocation

The feature Dynamic HR Allocation is enhanced by adding the possibility to set
the cell load thresholds differently for an AMR capable and non AMR capable
mobiles. This will allow the operator to avail of the improved speech quality
of AMR HR over HR by steering a larger percentage of the AMR capable
mobiles to AMR HR during high traffic load while still maintaining good speech
quality. These thresholds shall now be settable on a per cell level giving the
operator more flexibility to set the thresholds according to the characteristics
of the particular cell.

No CP Impact.
By steering AMR traffic separately, increased capacity can be achieved while

still maintaining good speech quality.
5.17.2 Hardware
No Impact.
No Impact.
5.17.4 Interface
5.17.5 Memory
No Impact.
5.17.6 Operations
The following new OPI is introduced, ’BSC Cell Dynamic HR Allocation Data
Change’.
2/10948-HSC 103 12/4 Uen M 2004-09-17 47

The following new command descriptions are introduced, ’RLDHC’ and

’RLDHP’.
The following new printout description is introduced. ’Cell Dynamic HR

Allocation Data’.
The application information for ’RCCD’, ’RNLCT’ and ’ROEPC’ are updated
due to this feature.
CNAI and CNA in OSS is updated to support the enhancements to this feature.

AMR and AMR HR are required to utilise separate handling for AMR traffic.
No Impact.
5.18 AMR
The feature AMR is enhanced to provide the operator with improved AMR
counters, together with OSS support which allow the operator to fine tune the
AMR feature to their particular radio environment. Codec Mode Utilisation
counters provide information on usage of the different codec modes within the
codec set. As the modes are adapted according to the radio conditions (C/I) a
picture of the cell performance can be made. Erased frame and total number
of frame counters are introduced for all codec modes within the HR and FR
defined Active Codec Sets (ACS). These counters are also introduced for FR
SPV1, FR SPV2 and HR SPV1. These counters can be used by the operator
to calculate the Frame Erasure Rate (FER) which gives an indication of the
speech quality in the cell. Separate drop call counters are introduced for AMR
FR and AMR HR calls, to distinguish them from existing FR/HR dropped calls.
Using the above counters the operator can fine tune the AMR parameters for
the BSC. To facilitate this new operator settable parameters are introduced for
setting the codec modes within the active codec set together with the thresholds
and hysteresis values to determine when to change codec mode. The two
predefined ACSs for AMR-FR and two for AMR-HR introduced in BSS R9.1 will
remain unchanged. These will be joined by two new user defined ACSs for
AMR-FR and two new ACSs for AMR-HR.
The AMR feature is introduced on new hardware platforms in BSS R10, with
support for RBS 2000 (except RBS2301<R6A) and TRA R5B.

No CP Impact.
48 2/10948-HSC 103 12/4 Uen M 2004-09-17

The enhancements allow the operator to fine tune the AMR performance. Using
AMR in combination with features such as AMR Power Control, Dynamic FR/HR
Mode Adaptation and Dynamic HR Allocation provide increased capacity while
maintaining good speech quality.
5.18.2 Hardware
AMR is supported on the following TRA platforms,
TRA R6
TRA R5B
See Table 5 for RBS support.
Note that all TRUs in the same subcell must be AMR capable in order to
support AMR in that subcell.
No Impact.
5.18.4 Interface
Updates are made to the Abis interface.
5.18.5 Memory
No Impact.
5.18.6 Operations
The following new OPI is introduced, ’BSC, AMR data, Change’.
The following new command descriptions are introduced, ’RLADC’, ’RLADP’.

The following command descriptions are updated, ’RRTPI’ and ’RRTCC’.
The following new printout description is introduced, ’AMR Data’.
CNA, CNAI and NWS in OSS are updated to support the enhancements to
the AMR feature.
2/10948-HSC 103 12/4 Uen M 2004-09-17 49

AMR HR is required to utilise the described enhancements for AMR HR traffic.

AMR support in MSC and AMR mobiles are required.
5.19 Speech Quality Supervision

The feature Speech Quality Supervision (SQS) is enhanced to support AMR FR
and AMR HR calls. By monitoring the SQS values for AMR calls the operator
can use this as input to fine tuning the AMR parameters to optimise speech
quality and capacity.

No CP Impact.
5.19.2 Hardware
No Impact.
No Impact
5.19.4 Interface
The Abis interface is updated to support this feature.
5.19.5 Memory
No Impact.
5.19.6 Operations
The following Speech Quality Reports are modified to include AMR FR and
AMR HR.
Speech Quality Cell, BSC
Speech Quality Chart, BSC
50 2/10948-HSC 103 12/4 Uen M 2004-09-17

Speech Quality Chart, Cell

AMR and AMR HR are required to utilise the enhancements to Speech Quality
Supervision.

No Impact.
5.20 Active BA-list Recording

The feature Active BA-List Recording provides the operator with support in
finding the most appropriate set of neighbour cell relations when adding new
cells or optimising the neighbour cell relations in the radio network. The feature
Active BA-List Recording is also used for the creation of the ICDM (Inter Cell
Dependency Matrix), that is used to estimate the downlink Percent Interfered
Traffic (PIT) in the OSS (by the RNO features FAS and FOX) . In BSS R10 this
feature is updated with the following enhancements:
Three additional thresholds for relative signal strength are introduced.
A new counter for the number of measurement reports from Half Rate
connections.
Measurement results are now available on a per channel group basis.

The maximum BARFIL size will grow from 2300 kB/BSC to 5700 kB/BSC.
5.20.2 Hardware
No Impact.
No Impact.
5.20.4 Interface
No Impact.
2/10948-HSC 103 12/4 Uen M 2004-09-17 51

5.20.5 Memory
No Impact.
5.20.6 Operations
The following OPI is updated to support this feature, ’BSC, Active BA-List
Recording Definition, Initiate’.
The following command description is updated, ’RABDC’.
The following printout descriptions are updated, ’BSC, Active BA-List Recording
Definition Data’, ’Active BA-List Recording Result’, ’BARFIL’.
The following application information is updated, ’ROBAR’.

The OSS features Neighbouring Cell Support FAJ 122 477, Neighbouring cell
list Optimization eXpert FAJ 122 630, Frequency Allocation Support FAJ 122
474 and Frequency Optimisation Expert (FOX) FAJ 122 629 will increase the
value of this feature. The improvements in OSS are:
- Support for Multi Band Cell
- Support for FAS ICDM on subcell level
- Improved PIT estimation: Consideration of GPRS traffic in the cells and

setting of CHALLOC is added to the calculation of the PIT estimate. Secondly
when STS data is not available the CS traffic level will be estimated based on
the number of reports in the BARFIL and an improvement is the new counter
that keeps track of the Half Rate usage.

No Impact.
5.21 Reduction of BSC Restart Time

The feature Reduction of BSC Restart Time introduces improvements which
reduce the time for Small Restart with complete RP Restart and Large Restart
with and without Radio Network Reconfiguration significantly. The reduction is
achieved by updating RPs in parallel, restarting CCS-7 links immediately after
Large Restart and other system improvements.
52 2/10948-HSC 103 12/4 Uen M 2004-09-17

Traffic downtime for a large restart in the BSC is reduced by on average of 25s
(dependent on APZ type and size of BSC Node).
Note that System Start and Large Restart with Reload are not impacted by
this feature.
5.21.2 Hardware
No Impact.
No Impact.
5.21.4 Interface
No Impact.
5.21.5 Memory
No Impact.
5.21.6 Operations
No Impact.

No Impact.

No Impact.
5.22 Advanced Single Slot Allocation

In BSS R9.1 there is only one singleslot TCH allocation strategy that chooses
the best TCH taking into consideration mainly the channel quality. In BSS R10
single slot allocation has been enhanced to include 3 different TCH allocation
strategies, for channel quality, MAIO consideration or Multislot configuration.
2/10948-HSC 103 12/4 Uen M 2004-09-17 53

The single slot TCH allocation strategy with quality consideration is based on
the R9.1 allocation strategy but also taking MAIO into consideration. Operators
should select this when channel quality is the most important criteria.
The single slot TCH allocation strategy with MAIO consideration is aimed at tight
frequency reuse networks (especially 1/1) where the most important criteria is
to minimise interference from co-channels and adjacent channels within and
between cells. MAIO offsets the synthesizer hopping sequences to obtain the
least amount of interference. For this strategy the MAIO is considered before
quality for single slot TCH allocation.
The single slot TCH allocation strategy with multislot consideration leaves as
many idle channels free as possible for multislot calls, increasing the probability
for consecutive channels being available for multislot traffic. For this strategy
multislot is considered ahead of quality.
The TCH allocation strategy is chosen on channel group level. The channel
allocation algorithm shall choose channel groups with the strategy ’TCH
Allocation with Multislot consideration’ as a last option in the cell when allocation
single slot connections. This results in more TCHs available in the channel
groups with multislot consideration strategy for mulitslot connections. Also
this enables the operator to have different frequency planning for that channel
group that shall mostly carry PS traffic.
The strategies are selectable by the operator by command. The default strategy
is Single Slot TCH Allocation with Quality Consideration.

No CP Impact.
5.22.2 Hardware
No Impact.
No Impact.
5.22.4 Interface
The following OSS External Interfaces are impacted;
CNA Interface (Import/Export).
54 2/10948-HSC 103 12/4 Uen M 2004-09-17

5.22.5 Memory
No Impact.
5.22.6 Operations
The following new OPI is introduced to support this feature, ’BSC, Cell Channel
Group Allocation Data, Change’.
The following new commands are introduced to support this feature, ’RLGAC’
and ’RLGAP’.
The following new printout is introduced, ’Cell Channel Group Allocation Data’.
The application information ’RCCGD’ is updated.

No Impact.

No Impact.
5.23 Support of APZ 212 33C

The feature Support of APZ 212 33C introduces a new APZ in BSS for use in
BYB501 based BSC/TRC nodes as well as BSC nodes. APZ 212 33C is a
small, compact and powerful CP housed in one subrack.

The APZ 212 33C is 1.5–2 times the capacity of APZ 212 30. Inter Platform
Network (IPN, 100Mbit/s) is supported for connection to APG40.
5.23.2 Hardware
The APZ 212 33C substitutes APZ 212 25 and APZ 212 30 for new node
deliveries.
The APZ 212 33C can also be used for APZ upgrade of APZ 212 25/IOG 20 to
APZ 212 33C/APG40 in the installed base of BYB 501.
2/10948-HSC 103 12/4 Uen M 2004-09-17 55

No Impact.
5.23.4 Interface
No Impact.
5.23.5 Memory
See chapter 3.5.
5.23.6 Operations
No Impact.

The feature Support of AXE 810 — APG40 is required for using APZ 212 33C.

No Impact.
5.24 BSS R10 GPRS/EGPRS System Improvements

The feature BSS R10 GPRS/EGPRS System Improvements contains the
following enhancements to GPRS/EGPRS.
Detect and Release of Hanging PDCHs and TBFs in PCU — If a TBF is

occupied without any ongoing activity for a while it is classified a ’hanging TBF’.
This results in PDCHs that remain busy and cannot be returned to CS Traffic.
This feature provides a mechanisim to detect and release hanging TBFs.
GB Link Recovery — The current implementation of GB recovery is improved

so that recovery of a lost Gb link (an NSVC) is attempted immediately.
PCU Configuration (Single/Multiple RP Environment) — In BSS R9.1 the

method to select Single or Multiple RP environments is automatic which can
result in problems determining if the PCU environment is Single or Multiple. In
BSS R10 this automatic detection is replaced with a more direct and secure
method by introducing two new commands to manually configure/print the
PCU Configuration.
RRGBP Improvements — The command RRGBP is improved by the addition of

an optional parameter to exclude the cell information.
56 2/10948-HSC 103 12/4 Uen M 2004-09-17

Recovery of EGPRS Channels — This improvement introduces a mechanism

to detect the appearance of EGPRS capable equipment and trigger a
reconfiguration of the appropriate Non-EGPRS equipment. This is to allow the
new equipment to be used to fullfill the EGPRS requirements on the cell. It
includes downgrade and upgrade of E-TCHs when EGPRS capable equipment
is lost and then comes back again.

Minor Impact on CP load.
5.24.2 Hardware
No Impact.
No Impact.
5.24.4 Interface
No Impact.
5.24.5 Memory
No Impact.
5.24.6 Operations
The following OPIs are introduced to support this feature ’Radio Transmission,
PCU Configurations, Change’, ’Radio Transmission, Packet Control Unit,
Connect’.
The following new command descriptions are introduced ’RRPCC’, ’RRPCP’,

’RRGBP’.
The following new printout description is introduced ’Radio Transmission, PCU

Configuration Data’.

2/10948-HSC 103 12/4 Uen M 2004-09-17 57

No Impact.
5.25 BSS R10 System Improvements

The feature BSS R10 System Improvements introduces the following new
functions which shall improve the BSS system characteristics,
Improved Load Regulation of Circuit Switched Paging. — A paging message

sent out in the network usually generates a Channel Required message in the
BSC as a response. The set-up and assignment of new channels generates
CP load. To avoid overloading the CP this feature load regulates the amount
of Channel Required messages due to circuit switched paging. Both paging
messages received over the A and Gb interfaces are controlled in this way.
Adapt default value to recommended value for T3105 — The Timer T3105
indicates the time between repetition of physical information messages
during the handover procedure. The default value is changed to match the
recommended value (from 6 to 8).
Improved Emergency Call Handling — In order to increase the possibility

for emergency calls to be setup in congested cells the last SDCCH in a cell
shall be reserved under certain circumstances. When a random access with
establishment cause ’emergency call’ is received then the last SDCCH channel
is reserved for 1 minute. This ’reserved’ SDCCH shall only be available for
emergency calls, meaning that non-emergency access shall be discarded if
only the reserved SDCCH is left in the cell. The SDCCH shall be reserved in
the BCCH band to ensure compatibility with the feature Multi Band Cell.
Increased Receiver Performance — By using new receiver algorithms the RX

performance is improved by approximately 1dB for 8–PSK (EDGE).
Extended Fault Reporting — Extended Fault reporting support is added for

RBS 2202/2102/2101/2302/2301/2401.
OMT/IDB Hardware Consistancy Check — A consistancy check is introduced

in OMT between the IDB configuration file and the actual RBS Hardware.
OMT will issue a warning upon detection of an inconsistancy which the field
technician can act upon during RBS installation.
OMT Improvements — It will be possible to retrieve interpretation of RBS2000

faults via OMT. The OMT will also provide a new function called RBS
configuration wizard. The wizard will guide the OMT user on site through every
configuration step that is needed to have an IDB describing an RBS installed
in the RBS.
Improved RX diversity alarms — To improve the fault localisation possibilities

for RX diversity faults, two new alarms have been added. One alarm for faults in
the RXA dependency way and one alarm for faults in the RXB dependency way.
58 2/10948-HSC 103 12/4 Uen M 2004-09-17

DC undervoltage alarm — DC undervoltage alarms has been improved for

RBS 2202/2102/2101/2302/2301/2401. Both “Battery Mode on” and “DC
undervoltage” alarms will be possible to receive.
OMT Support for RBS 2x06 dual band configurations — Support for 900/1900
dual band RBS 2106 and RBS 2206 configurations will be implemented in the
OMT. The support will be delivered in BTS SW 10.1B.

No Impact.
5.25.2 Hardware
See Table 5 for RBS HW support for RBS impacting improvements.
No Impact.
5.25.4 Interface
No Impact.
5.25.5 Memory
No Impact.
5.25.6 Operations
The application information for ’ROEPC’ is updated with the new T3105 default
timer value.
The printout PLLDP is affected by the Improved Load Regulation of Circuit

Switched Paging. This is due to that the load regulation of incoming paging
messages is replaced by load regulation of Channel Required as answer to
paging from the mobiles.

No Impact.
2/10948-HSC 103 12/4 Uen M 2004-09-17 59

No Impact.
5.26 Advanced Frequency Handling

The feature Advanced Frequency Handling increases the maximum number
of frequencies per cell from 32 to 128. (note that the maximum number per
channel group is limited to 32). This makes it possible to use 1/1 frequency
reuse in large spectrums. The feature also enables more than 16 frequencies
to be used in frequency hopping multi band cells.
To be consistent with the increased number of frequencies per cell, new

frequency formats for allocation of GPRS/EGPRS channels are also introduced.
No Impact.
5.26.2 Hardware
No Impact.
No Impact.
5.26.4 Interface
5.26.5 Memory
No Impact.
5.26.6 Operations
The following command descriptions are updated to support this feature,
’RLCHC’, ’RLSLC’, ’RLDEC’.
The following printout description are updated, ’Cell Supervision of Logical

Channel Availability Data’.
60 2/10948-HSC 103 12/4 Uen M 2004-09-17

The following application information is updated, ’ RCCGD’.
CNA and CNAI in OSS is updated to support this feature.

Prior to R10 all frequencies in the cell were available for Immediate Assignment.
The 3GPP standards limit the Range/number of hopping frequencies that
can be available for Immediate Assignment. In Ericsson BSS this limits the
number of frequencies per cell. Due to the high Range (difference between the
lowest ARFCN and highest ARFCN) in a Multi Band cell, prior to R10 only 16
frequencies could be used in a multi band cell. In BSS R10 this limitation is
removed and it is possible to allocate upto 128 frequencies in a Multi Band cell.
No Impact.
5.27 Re-Use of Frequencies within a cell

The feature Re-Use of Frequencies within a Cell allows the operator to use
the same frequencies in more than one channel group within a cell when
synthesised frequency hopping is used. By setting different MAIO values to
the TRU in the same way as is done within a channel group, a frequency is
not used for more than one connection at any instant in time. This makes it
possible to expand a network with new hardware using the FLP concept. E.g.
it shall be able to synchronise EDGE (synthesised hopping RBS2000) with
TCH channels (synthesised hopping RBS 200) within one cell when upgrading
RBS200 cells with EDGE. (Note that the BCCH frequency cannot be re-used
and must remain unique).

No Impact.
5.27.2 Hardware
No Impact.
No Impact.
2/10948-HSC 103 12/4 Uen M 2004-09-17 61

5.27.4 Interface
5.27.5 Memory
No Impact.
5.27.6 Operations
’RLCFI’, ’RLCFE’.
The following printout description is updated, ’Cell Configuration Frequency

Hopping Data’.

The features Flexible MAIO management, RBS2000 Synchronisation and RBS
200 and 2000 in the same Cell (where applicable) are required.

No Impact.
5.28 Increased SDCCH Capacity

The feature Increased SDCCH Capacity enables increased SDCCH signalling
capacity per cell providing the operator a means to dimension the network to
manage the increasing signalling needs due to higher SMS traffic, increased in
normal location updating, periodic registration, IMSI attach/detach, call set up
etc.
This feature increases the number of SDCCHs it shall be possible to define in a

cell to be equal to twice the number of TRXs for that cell upto a maximum of
32 SDCCHs per cell.
Number of SDCCHs possible to define in a cell is equal to the number of TRXs

in the cell times two, upto a maximum of 32 SDCCHs per cell.
62 2/10948-HSC 103 12/4 Uen M 2004-09-17

The increase in SDCCH/8s defined per cell require more SDCCH/8s on each
TRX. This will reduce the capacity of the RPD/RPG. This shall be configurable
by the operator. See feature Flexible SDCCH Allocation for more details.
5.28.2 Hardware
No Impact.
No Impact.
5.28.4 Interface
5.28.5 Memory
See feature Flexible SDCCH Allocation.
5.28.6 Operations
CNA, CNAI and BSM in OSS are updated to support this feature.
The feature Flexible SDCCH Allocation is required.

No Impact.
5.29 Locating
The feature, Locating, provides the basis for handover decisions in BSS. It is
controlled via parameters and works out the cell selection for active MSs. In
BSS R10 this feature is enhanced to include new bad quality parameters for
AMR mobiles. This allows the operator to benefit from the increased robustness
associated with AMR-FR by setting separate bad quality thresholds and higher
2/10948-HSC 103 12/4 Uen M 2004-09-17 63

Rxqual values before a bad quality urgency handover is performed for these
mobiles.

No Impact.
5.29.2 Hardware
No Impact.
No Impact.
5.29.4 Interface
5.29.5 Memory
No Impact.
5.29.6 Operations
The following OPI is updated due to this feature ’BSC Cell Neighbour Relation
Data, Change’.
The following command descriptions are updated, ’RLLUC’, ’RLLUP’, ’RLNRC’,

’RLNRP’.
The following printout descriptions are updated, ’Cell Locating Urgency Data’
and ’Neighbour Relation Data’.
The following Application information is updated, ’RQCD’ and ’RMHBI’

AMR is required to utilise the new parameters for AMR mobiles.
64 2/10948-HSC 103 12/4 Uen M 2004-09-17

No Impact.
5.30 Paging
The feature Paging is used when a mobile terminated call is to be set up to
search for the mobile within the Paging Area, and to order the MS to initiate
the connection. In BSS R10 this feature is enhanced by introducing two new
counters for detecting PCH congestion. The first counter, counts, per cell,
the number of discarded pages due to full Paging Queue in the BTS. The
second counter, counts, per cell, the number of discarded pages due to age.
These two counters provide the operator with a truer representation of paging
congestion situations. By providing the operator with a proper information of
paging congestion situations the operator can take actions to improve paging
performance.

No CP Impact.
5.30.2 Hardware
No Impact.
No Impact.
5.30.4 Interface
The Abis interface is updated to support this feature.
NWS Universe and NWS Reports.
5.30.5 Memory
No Impact.
5.30.6 Operations
NWS in OSS are updated to support this feature.
2/10948-HSC 103 12/4 Uen M 2004-09-17 65

No Impact.
No Impact.
5.31 GPRS Quality of Service and Scheduling

The feature GPRS Quality of Service and Scheduling enables the operator
to differentiate between users by giving them different profiles in terms of
throughput and priority. Prior to BSS R10 this feature required full R99 QoS
support in the mobile and SGSN. Mobiles not supporting R99 QoS were treated
as background users i.e. best effort. In BSS R10 the feature is enhanced by
providing support for R97/98 mobiles and SGSNs not supporting PFM (Packet
Flow Management). In these cases the QoS profile as specified in the release
97 3GPP TS will be used for differentiation. The precendence class and the
Peak Thoughput class are mapped to Interactive/Background classes and the
Maximum Bitrate respectively.

No Impact.
5.31.2 Hardware
No Impact.
No Impact.
5.31.4 Interface
No Impact.
5.31.5 Memory
No Impact.
66 2/10948-HSC 103 12/4 Uen M 2004-09-17

5.31.6 Operations
The following OPIs are updated to reflect the enhancements to the feature,
’BSC, General Packet Radio Service Quality of Service, Change’, ’BSC,
General Packet Radio Service Quality of Service, Activate’, ’BSC, General
Packet Radio Service Quality of Service, Deactivate’.
The following Application Information is updated, ’ROEPC’.


SGSN, HLR and Mobile compliant to the R97 QoS or R99 QoS standard are
required.
5.32 High Speed Signalling Links (HSL)

The feature High Speed Signalling Links was introduced in BSS R9.1 for both
CCITT No7 signalling towards the MSC on A-interface and HDLC based
(China) high speed signalling. In BSS R10 this feature is enhanced to support
also ANSI SS7 signalling.
The Capacity of one 1.5 Mb/s ANSI HSL link using ATM will be approximately
equal to the capacity of 13 56 kb/s signalling links.
No Impact on CP load.
5.32.2 Hardware
RPP is required to support the HSL feature. Each RPP can administrate one
high speed signalling link. APZ 212 20 with serial RP bus, APZ 212 25 , APZ
212 30 and APZ 212 33C support HSL.
One serial RP-Bus branch can handle upto 3 HSLs when no other RPs are
connected to it.
Co-existance of conventional 56 kb/s links on the same link set as HSLs is

supported to facilitate upgrading to HSL without traffic loss.
2/10948-HSC 103 12/4 Uen M 2004-09-17 67

It is recommended to have at least two HSLs in the BSC working side by side
for redundancy reasons.
5.32.4 Interface
HSL impacts the A-Interface.
5.32.5 Memory
No Impact.
5.32.6 Operations
All devices within the HSL need to be defined to obtain HSL.
No Impact.

MSC must also support ANSI HSL.
5.33 Antenna Hopping

The feature Antenna Hopping provides benefits for operators having limited
spectral bandwidth. It is achieved by alternating the transmission of down link
bursts between two or more antennas.
Antenna hopping is seen as particularly beneficial for cells where the non-BCCH
channel group is using synthesizer hopping (and FLP). The BCCH carrier also
benefits from antenna hopping in this configuration.

No CP impact.
5.33.2 Hardware
RBS 2106/2308 and RBS 2206/2207 are supported. A hybrid combiner is

required. Antenna hopping is not possible to use together with a filter combiner.
68 2/10948-HSC 103 12/4 Uen M 2004-09-17

No impact.
5.33.4 Interface
No Impact.
5.33.5 Memory
No Impact.
5.33.6 Operations
’RXMOC’, ’RXMSC’.
The following printout descriptions are updated, ’Radio X-Ceiver Administration,

Managed Object Data Owner’, ’Radio X-Ceiver Administration, Managed Object
Configuration Data’, ’BCDCFILE ASN.1Result’.
The following application information is updated ’RXCMOO’.
BSM in OSS is updated to support this feature.
No impact

None.
5.34 Statistics Based on Measurement Results

The feature Statistics Based on Measurement Results extracts information
from the measurement reports sent from the mobiles and BTS’s and creates
histogram reports of signal strength, quality, timing advance, etc. In BSS R10
this feature has been enhanced so that measurement results are available on
channel group level instead of subcell level, allowing optimisation for different
quality needs in different channel groups. Also, counters are introduced in the
recording for the Pathloss difference (Pathloss DL - Pathloss UL).
The measurement results collected while the connection is on the SDCCH are
completely removed from the Measurement Result Recording (MRR). This
means that only connections on TCH is recorded and counted by the counters
2/10948-HSC 103 12/4 Uen M 2004-09-17 69

in MRR. Note that this may have an impact on the MRR statistics. For example,
a sudden change of measured RxQual might be seen when upgrading to BSS
R10. This is due to that counters are based on measurements on TCH and
SDCCH before the upgrade while after the upgrade, only TCH measurements
are considered.

The maximum MRRFIL size will grow from 1600 kB/BSC to 1900 kB/BSC.
5.34.2 Hardware
No Impact.
No Impact.
5.34.4 Interface
No Impact.
5.34.5 Memory
No Impact.
5.34.6 Operations
The following OPI is updated to support this feature, ’BSC, Measurement Result
Recording Definition, Initiate’.
The following command description is updated, ’RAMDC’.
The following printout descriptions are updated, ’Measurement Result

Recording Definition Data’, ’MRRFIL’.

OSS is required to make full use of this feature. The improvements in OSS are:
— A histogram for the Path Loss difference is introduced.
— Filtering of AMR and non-AMR mobiles in MRR is introduced to aid the

operator in tuning AMR Power Control.
70 2/10948-HSC 103 12/4 Uen M 2004-09-17

— The total number of collected measurement reports in a cell will be presented

when filtering is used to present data only for the filtered out fraction of reports.

No Impact.
5.35 Support of AXE 810 — APG40

The feature Support of AXE 810 — APG40 enables use of the compact and
powerful IO platform for BSC and BSC/TRC nodes, APG40.
In BSS R10 this feature is enhanced by supporting the following,
All commands now stored in the security log,
Faster function change of AP software,
All counters including the new counters introduced in BSS R10 can be
supported.

All counters including the new counters introduced in BSS R10 can be
supported.
5.35.2 Hardware
No Impact.
No Impact.
5.35.4 Interface
No Impact.
5.35.5 Memory
No Impact.
2/10948-HSC 103 12/4 Uen M 2004-09-17 71

5.35.6 Operations
No Impact.

No Impact.

No Impact.
5.36 Support of AXE 810 — APT 1.5

The feature Support of AXE 810 — APT 1.5, the compact and high capacity
component in the AXE 810 HW platform used for BSC and BSC/TRC nodes
has been enhanced by adding support for the NNRP-4 process. This allows the
possibility to expand existing BYB 501 based nodes with AXE 810.
Improved capacity and performance associated with APT1.5 can be achieved

in existing BYB 501 nodes.
The capacity limit of the Subrate Switch (SRS) in the GS12 will be removed.
For ET155–7 connected to GS12 there are restrictions not to use all devices
in order to avoid group switch congestion. The GS890 is a congestion-free
group switch. This means that increased capacity will be obtained for ET155–7
after group switch upgrade. The capacity will be increased from 1736 to 1953
circuits per ET155.
5.36.2 Hardware
GS890 is added to the group switch in BYB 501. The BYB 501 group switch
remains connected to existing hardware, eg. TRA R5B, RPG2. The GSS 890
can then have APT 1.5 hardware connected to it, eg TRA R6, RPG3, ET155–1.
NNRP-4 process is used for GS conversion.
5.36.4 Interface
No Impact.
72 2/10948-HSC 103 12/4 Uen M 2004-09-17

5.36.5 Memory
The GS890 requires more CP DS memory than the GS12 group switch. An
additional 7 MW16 per GEM magazine is required. This has to be considered for
APZ 212 25 and 212 20 processors where DS memory may be a limiting factor.
5.36.6 Operations
No Impact.

No Impact.

No Impact.
5.37 Extended Call Release Reporting

With the feature Extended Call Release Reporting the BSC can report detailed
information on why a call has been dropped to the MSC. Before BSS R10 this
information is only available from the BSC for statistical purposes. By reporting
this information to the MSC, it is possible for the MSC to provide more detailed
information to the billing system which can then be connected to individual
subscribers.

No Impact.
5.37.2 Hardware
No Impact.
No Impact.
5.37.4 Interface
No Impact.
2/10948-HSC 103 12/4 Uen M 2004-09-17 73

5.37.5 Memory
No Impact.
5.37.6 Operations

No Impact.

MSC/VLR feature FAJ 122 899 BSSMAP Call Release Reason in Call Data
Records, is required to benefit from this feature in the MSC.
5.38 Flexible Positioning Support

The feature Flexible Positioning Support has been improved by support of MS
assisted A-GPS. At MS assisted A-GPS, the positioning calculation is done in
the SMPC node based on measurements provided by the MS.
A Sanity Check of every A-GPS positioning estimate is done in the SMPC

before using it in a location response. The Sanity check is supported both for
MS based and MS assisted A-GPS.

No impact.
5.38.2 Hardware
No Impact.
No Impact.
5.38.4 Interface
The following interfaces have been updated: SMPC-OSS, SMPC-BSC,

SMPC-MS.
74 2/10948-HSC 103 12/4 Uen M 2004-09-17

5.38.5 Memory
No Impact.
5.38.6 Operations
The SMPC tool is updated with a new graphical user interface and it will also be
supported using any Netscape browser.

No impact.
Mobile station that supports A-GPS.
5.39 Frequency Allocation Support

The feature Frequency Allocation Support facilitates the frequency planning for
the operator by measuring uplink interference levels for frequencies in cells
specified by the operator. The uplink interference measurements for a cell
are saved on a file for further evaluation in OSS. In BSS R10, FAS has been
adapted to work with the feature Multi Band Cell. This is achieved by allowing
measurements in all cells supporting a frequency band, regardless of the
configured BCCH frequency band.

No Impact.
5.39.2 Hardware
No Impact.
No Impact.
5.39.4 Interface
No impact.
2/10948-HSC 103 12/4 Uen M 2004-09-17 75

5.39.5 Memory
No Impact.
5.39.6 Operations
No impact.

The feature is updated to support the feature Multi Band Cell.
The OSS features Frequency Allocation Support FAJ 122 474 and Frequency
Optimisation Expert (FOX) FAJ 122 629 will increase the value of this feature.
The improvement in OSS is that support for Multi Band Cell has been added.

No impact.
6 Impacting BTS Features
6.1 Interference Rejection Combining (IRC)

The feature Interference Rejection Combining is used to improve the receiver
performance when the interference is high.
No CP impact.
6.1.2 Hardware
RBS 2102 and RBS 2202 together with DXU-21 and sTRU are supported. RBS
2308, 2106 and RBS 2206/2207 are also supported.
76 2/10948-HSC 103 12/4 Uen M 2004-09-17

No Impact.
6.1.4 Interface
BTS-BSC interface updated to support enabling/disabling IRC.
The following OSS External Interface is also impacted, CNA Interface

(Import/Export)
6.1.5 Memory
No impact.
6.1.6 Operations
The BSC command, RLDEC is modified to include the IRC parameter.
The following printout descriptions are modified, ’Cell Description Data’ and
’Radio X-Ceiver Administration Managed Object Configuration Data.
The following Application Information is modified, ’RXCMOO’.
Support for IRC in BSM, CNA and CNAI in OSS is also added.

Feature RX Diversity must be enabled before enabling IRC.

No impact.
6.2 Battery Test

The feature Battery Test reduces maintenance cost and environmental impact
and can possibly give improved in-service performance. This is achieved by
introducing , battery backup time test and optimised charging.
Battery backup time is tested (on cyclic basis) and if the measured time is
less than an operator configured expected time, an alarm is generated. This
reduces maintenance costs and avoids unnecessary replacement of batteries.
It allows the operator to replace batteries before a situation occurs where bad
batteries lead to a RBS out of service.
2/10948-HSC 103 12/4 Uen M 2004-09-17 77

Optimised charging improves the charging to support FVLA, VRLA, Na/MeCL

and NIMeH battery types. Charging algorithms are improved to optimise
charging according to the battery type.
Note that the software support for Battery Test on the RBS PPC platform
is supported in BTS 10.1B.

No CP Impact.
6.2.2 Hardware
This feature is available for the Macro RBS 2000 with following site solution:
single cabinet, master + extension with separated or shared batteries and sites
with many RBS 2000 and shared batteries. The power supply unit has to be
either a PSU 230 or a PSU AC and the batteries have to support more than
0.2 hours backup time.
No Impact.
6.2.4 Interface
Abis interface is updated to support this feature.
6.2.5 Memory
No Impact.
6.2.6 Operations
No Impact.

No Impact.

No Impact.
78 2/10948-HSC 103 12/4 Uen M 2004-09-17

7 Impacting OSS Features
7.1 GSM Real–time Performance Monitoring

The feature GSM Real-time Performance Monitoring is enhanced in BSS R10
to provide support for GPRS. The following functionality is added,
— Throughput can be monitored per cell and combination of class, RLC-mode,

MBR, direction and GPRS type.
— Cell reselection data can be output on individual neighbour relations.
— Drops monitoring with user defined filtering on cause values.
— GPRS/EGPRS radio link performance based on the GPRS/EGPRS

measurement reports (at downlink data traffic)
All new monitors can be viewed in real-time using the new improved R-PMO
user interface. The events as well as the monitors can also be stored in
tab-seperated text files for post processing in other tools.

The disk storage requirement on the OSS server is increased with 1Gb. The
event dumper uses this storage space.
7.1.2 Hardware
No Impact.
No Impact.
7.1.4 Interface
The OSS-BSC (RNX-BSC) interface is updated to support the new monitors.
7.1.5 Memory
See capacity and performance.
2/10948-HSC 103 12/4 Uen M 2004-09-17 79

7.1.6 Operations
No Impact.
The feature Real Time Event Data is required.

No Impact.
8 Summary of Operator Interface Changes
In case of discrepancy between this document and any Operation and

Maintenance documentation, O&M document should be considered valid.
8.1 Parameters Changes
8.1.1 New Parameters
Table 12 New BSC Parameters

Parameter Description Com- Level Feature
mand
AMRPC- Indication of RLAPI Cell FAJ 121 353
STATE state of AMR
Power Control
(active/inactive)
SSDESD- Desired Signal RLAPC Internal FAJ 121 353
LAFR Strength for Cell/Over-
AMR FR DL laid subcell
QDESD- Desired Quality RLAPC Internal FAJ 121 353
LAFR for AMR FR DL Cell/Over-
laid subcell
SSDESU- Desired Signal RLAPC Internal FAJ 121 353
LAFR Strength for Cell/Over-
AMR FR UL laid subcell
80 2/10948-HSC 103 12/4 Uen M 2004-09-17


mand
QDESU- Desired Quality RLAPC Internal FAJ 121 353
LAFR for AMR FR UL Cell/Over-
laid subcell
UPDWNRA- New BSC RAEPC BSC FAJ 122 260
TIO exchange
property
SSDESUL Desired Signal RLPCC Internal FAJ 122 260
Strength UL Cell/Over-
laid subcell
REGINTUL Regulation RLPCC Internal FAJ 122 260
Interval UL Cell/Over-
laid subcell
QLENUL Length of RLPCC Internal FAJ 122 260
QualityFilter Cell/Over-
UL laid subcell
SSLENUL Length of RLPCC Internal FAJ 122 260
Signal Strength Cell/Over-
Filter UL laid subcell
BAND Define the RLDGI CHGR FAJ 122 085
frequency band
used.
FBOFFS Define RLLOC CELL FAJ 122 085
frequency band
offset for MB
Cells. (single
parameter
in CNA but
handled as
2 separate
parameters —
FBOFFSN and
FBOFFSP in all
user interfaces
and to BSC)
2/10948-HSC 103 12/4 Uen M 2004-09-17 81


mand
MBCRAC Defines if all RAEPC BSC FAJ 122 085
frequency
bands are
available or
if frequency
bands as per
MS Frequency
Band
parameter are
available.
DLDELAY BSC exchange RAEPC BSC FAJ 121 375
property for
specifing of
delay release
of inactive DL
TBF.
ESDELAY BSC exchange RAEPC BSC FAJ 121 375
property for
specification
of delay of
release due to
inactivity of DL
TBF following
’early set-up’ of
DL TBF.
TFILIMIT BSC exchange RAEPC BSC FAJ 121 375
property for
specification
of lower limit
for control of
when a TBF
will no longer
be allowed to
enter ’Delayed
Release of DL
TBF’-mode
as defined by
DLDELAY.
ULDELAY BSC exchange RAEPC BSC FAJ 121 375
property for the
specification of
delay of release
of inactive
uplink TBF.
82 2/10948-HSC 103 12/4 Uen M 2004-09-17


mand
USFLIMIT BSC exchange RAEPC BSC FAJ 121 375
property for the
specification
of the lower
limit for the
number of
available USFs
below which
inactive uplink
TBFs must be
released.
PROFFSET Reselection off RLGNC CELL FAJ 121 375
set used during (neighbour
GPRS/EGPRS relation)
cell reselection.
PSVALID Defines the RLNSC CELL FAJ 121 375
possiblity of (neighbour
performing cell relation)
reselection
from serving
cell to
neighbouring
cell.
PLAYER Defines the RLPSC CELL FAJ 121 375
hierarchical
structure
priority used
during cell
reselection.
PHCSTHR Defines the RLPSC CELL FAJ 121 375
hierarchical
structure
threshold used
during cell
reselection
PS- BSC Exchange RAEPC BSC FAJ 121 375
CELLPLAN property to
enable Packet
Specific Cell
Plan
2/10948-HSC 103 12/4 Uen M 2004-09-17 83


mand
SCALLOC Specifies how RLGSC CELL FAJ 121 375
PDCHs shall
be allocated
when GPRS is
activated for the
CELL, ie in UL,
OL, Both-UL
Preferred,
Both-OL
Preferred..
IRC Add IRC RLDEC CELL FAJ 122 083
parameter
EXCHGR Indicates RLACC Channel FAJ 121 355
if adaptive Group
SDCCHs are
allowed to
be added to
CHGR.
MAXNOSD- BSC Exchange RAEPC/P BSC FAJ 121 367
CCHTRX property to
specify the
max number
of SDCCHs
allowed per
TRX.
DM Indicate state RLDMI Internal FAJ 121 361
of Dynamic CELL
FR/HR mode
adaptation
DMTHAMR AMR threshold RLDMC Internal FAJ 121 361
CELL
DMTHNAMR Non-AMR RLDMC Internal FAJ 121 361
threshold CELL
DMQG Switch RLDMI Internal FAJ 121 361
on/off quality CELL
threshold
FR/HR
DMQGAMR AMR Quality RLDMI Internal FAJ 121 361
Threshold CELL
FR/HR
84 2/10948-HSC 103 12/4 Uen M 2004-09-17


mand
DMQG- Non-AMR RLDMI Internal FAJ 121 361
NAMR Quality CELL
Threshold
FR/HR
DMQB Switch RLDMI Internal FAJ 121 361
on/off quality CELL
threshold
HR/FR
DMQBAMR AMR Quality RLDMI Internal FAJ 121 361
Threshold CELL
HR/FR
DBQBNAMR Non-AMR RLDMI Internal FAJ 121 361
Quality CELL
Threshold
HR/FR
QLENGTH Max queue RLMQC CELL FAJ 121 362
length
RESLIMIT % of channel RLMQC CELL FAJ 121 362
resources
allocated
to priority
connections
(PC) before
starting to give
channels to
non priority
connections.
MSQHO- Queuing RAEPC BSC FAJ 121 362
PRIO Ranking
strategy
MSQUEU- Switch MS Q RAEPC BSC FAJ 121 362
ING on/off
MSQASSTIME Max time a RAEPC BSC FAJ 121 362
PC can stay in
queue.
DHA Switch RLDHP CELL FAJ 122 852
Dynamic HR
Allocation
on/off per cell
2/10948-HSC 103 12/4 Uen M 2004-09-17 85


mand
DTHAMR Percentage RLDHP CELL FAJ 122 852
of free TCHs
releative to
the amount
of deblocked
TCHs in the
cell. Below
this AMR HR is
allocated. Valid
for AMR MS
only.
DTHNAMR Percentage RLDHP CELL FAJ 122 852
of free TCHs
releative to
the amount
of deblocked
TCHs in the
cell. Below this
HR is allocated.
Valid for non
AMR MS.
AMRFRSUP- BSC exchange RAEPC BSC FAJ 121 055
PORT property, for
AMR FR on/off
AM- BSC exchange RAEPC BSC FAJ 121 358
RHRSUP- property for
PORT AMR HR on/off
AMR- BSC exchange RAEPC BSC FAJ 121 055
SPEECHVER- property
USED for AMR
callsspecifing
if userd speech
coder after the
first assignment
should be
prioritised at
change of
channel or not
MODE1 Lowest codec RLADC BSC FAJ 121 055
mode in Codec
Set
86 2/10948-HSC 103 12/4 Uen M 2004-09-17


mand
MODE2 2nd codec RLADC BSC FAJ 121 055
mode in Codec
Set
MODE3 3rd codec RLADC BSC FAJ 121 055
mode in Codec
Set
MODE4 Highest codec RLADC BSC FAJ 121 055
mode in Codec
Set
THR1 Threshold RLADC BSC FAJ 121 055
between
MODE1 and
MODE2
between
MODE2 and
MODE3
between
MODE3 and
MODE4
HYST1 Hysteresis for RLADC BSC FAJ 121 055
THR1 between
MODE1 and
MODE2
THR2 between
MODE2 and
MODE3
THR3 between
MODE3 and
MODE4
DTCBSC Activation of RAEPC BSC FAJ 122 430
Distance to Cell
Border
DTCB Distance to RLOLC CELL FAJ 122 430
Cell Border
threshold
2/10948-HSC 103 12/4 Uen M 2004-09-17 87


mand
DTCBHYST Hysteresis RLOLC CELL FAJ 122 430
value for DTCB
NNCELLS Number of RLOLC CELL FAJ 122 430
neighbouring
cells required
for DTCB
criteria
NDIST Signal strength RLOLC CELL FAJ 122 430
range of
neighbouring
cells for DTCB
criteria.
QUALITY Strategy for RLGAC Channel FAJ 121 363
single slot Group
allocation
MAIO Strategy for RLGAC Channel FAJ 121 363
single slot Group
allocation
MULTI Strategy for RLGAC Channel FAJ 121 363
single slot Group
allocation
SAS Single Slot RLGAC Channel FAJ 121 363
Allocation Group
Strategy
SSOFFSE- Signal strength RLHIC CELL FAJ 122 290
TULAFR parameter
for AMR FR
mobiles
SSOFF- Signal strength RLHIC CELL FAJ 122 290
SETDLAFR parameter
for AMR FR
mobiles
QOFFSETU- Quality offset RLHIC CELL FAJ 122 290
LAFR parameters
for AMR FR
mobiles
QOFFSETD- Quality offset RLHIC CELL FAJ 122 290
LAFR parameters
for AMR FR
mobiles
88 2/10948-HSC 103 12/4 Uen M 2004-09-17


mand
QLIMULAFR Bad quality RLLUC CELL FAJ 122 259
urgency offset
for AMR-FR
mobiles
QLIMDLAFR Bad quality RLLUC CELL FAJ 122 259
urgency offset
for AMR-FR
mobiles
BQOFF- Bad quality RLNRC Neighbour FAJ 122 259
SETAFR urgency offset CELL
for AMR-FR
mobiles
(neighbour cell)
BCCD Specifies if a RLCHC Channel FAJ 121 372
channel group Group
is capable
of handling
immediate
assignment
or packet
assignment
(when not using
MPDCH) or
not.
QOSMAP- Acti- RAEPC BSC FAJ 121 32
PING vates/Deacti-
vates/Changes
QoS Sup-
port based
on ABQPs
mapped from
R97 QoS Pro-
file.
RELSS3P Positive relative RABDC CELL FAJ 122 396
signal strength
treshold 3
RELSS3N Negative RABDC CELL FAJ 122 396
relative signal
strength
treshold 3
signal strength
treshold 4
2/10948-HSC 103 12/4 Uen M 2004-09-17 89


mand
relative signal
strength
treshold 4
signal strength
treshold 5
relative signal
strength
treshold 5
MEASLIMN Path Loss RAMDC CELL FAJ 122 399
Difference
between
UL and DL
(negative)
CONTYPE Type of RAMDC CELL FAJ 122 399
connection
for which
measurement
results shall be
collected
FCOFFSET Specifies if RXMOC, Per TF FAJ 122 081
TG should be RXMSC
synchronised
to nominal
position with
defined offset
or should not be
synchronised
to the nominal
position
BSCFSOFF- Specifies the RAEPC BSC FAJ 122 081
SETMSW high part of the
base offset for
TGs that are
sychronised
to the nominal
position.
90 2/10948-HSC 103 12/4 Uen M 2004-09-17


mand
BSCFSOFF- Specifies the RAEPC BSC FAJ 122 081
SETLSW low part of the
base offset for
TGs that are
sychronised
to the nominal
position.
PDCHPRE- Packet Data RAEPC BSC FAJ 121 360
EMT Channels
(PDCHs)
pre-emptability
CALL- Reporting of RAEPC BSC FAJ 121 432
DROPMSC Dropped Call
Reason to the
MSC
NOR5AINBSC Controls RAEPC BSC FAJ 121 356
reconfiguration
of TRA R5
equipment
DYNULD- Controls RAEPC BSC FAJ 121 375
LACT activation of
Dynamic UL/DL
Resource
Handling
2/10948-HSC 103 12/4 Uen M 2004-09-17 91

8.1.2 Changed Parameters
Table 13 Changed BSC Parameters

mand
QCOMPUL Extended Value RLPCC Internal FAJ 122 260
Range (for BSC Cell /
of version R10 Overlaid
NA ED) and Subcell
only possible
to set when
MSPWRCTRL
is ON (for BSC
of version BSC
NAED)
CHAP extended value RLHPC CELL FAJ 122 085
range
LOL extended value RLOLC CELL FAJ 122 085
range
CSYSTYPE In Multi Band RABDC CELL FAJ 122 085
Cell this defines RAMDC
the frequency RARDC
band used for RLDEI
the BCCH.
MSTXPWR Valid frequency RLCPC internal FAJ 122 085
band must cell,
now be derived overlaid
from the BAND subcell,
parameter. external
cell, foreign
cell
TN Changed from RLCCC / Channel FAJ 121 367
integer to range RLCFP Group
of 0–7. For
extended range
cells only even
timeslots can
be used.
SDCCH Extended RLCCC / Channel FAJ 121 367
from 16 to 32 RLCFP Group
and removed
connection to
CCHPOS
HOP Value TCH RLCHC / Channel FAJ 121 367
removed RLCHP Group
92 2/10948-HSC 103 12/4 Uen M 2004-09-17

Table 13 Changed BSC Parameters

mand
EBANDIN- Add RAEPC BSC FAJ 121 362
CLUDED MSQUEUING
LQCACT Activation of RAEPC BSC FAJ 121 31
LQC updated
to include UL.
LQCDE- Default MCS for RAEPC BSC FAJ 121 31
FAULTMC- UL when LQC
SUL is not active.
EID New events RAPMI BSC FAJ 121 50
added RAPME
8.1.3 Removed Parameters

Table 14 Removed BSC Parameters
mand
SSDES Removed RLPCC Internal FAJ 122 260
Cell/Over-
laid subcell
REGINT Removed RLPCC Internal FAJ 122 260
Cell/Over-
laid subcell
QLEN Removed RLPCC Internal FAJ 122 260
Cell/Over-
laid subcell
SSLEN Removed RLPCC Internal FAJ 122 260
Cell/Over-
laid subcell
PMARG Removed RLPCC Internal FAJ 122 260l
Cell/Over-
laid subcell
INIDES Removed RLPCC Internal FAJ 122 260
Cell/Over-
laid subcell
INILEN Removed RLPCC Internal FAJ 122 260
Cell/Over-
laid subcell
CCHPOS Removed RLCCC Channel FAJ 121 367
Group
2/10948-HSC 103 12/4 Uen M 2004-09-17 93

Table 14 Removed BSC Parameters

mand
TLDTH Removed RAEPC BSC FAJ 122 582
AMRSUP- Removed RAEPC BSC FAJ 121 055
PORT
8.1.4 New Commands
Table 15 New BSC Commands

Command Description Level Feature
RLAPC AMR power CELL Subcell FAJ 121 353
control cell data,
Change
RLAPI AMR power CELL FAJ 121 353
control cell data,
Initiate
RLAPE AMR power CELL FAJ 121 353
control cell data,
End
RLAPP AMR power CELL FAJ 121 353
control cell data,
Print
RLMQP Cell Queuing CELL FAJ 121 362
Settings, Print
RLMQC Change Cell CELL FAJ 121 362
Queuing
settings
RRPSC Selfconfiguring BSC FAJ 121 356
TRA Pool data ,
change
RRPSE Selfconfiguring BSC FAJ 121 356
TRA Pool data ,
End
RRPSI Selfconfiguring BSC FAJ 121 356
TRA Pool data ,
Initiate
RRPSP Selfconfiguring BSC FAJ 121 356
TRA Pool data ,
Print
94 2/10948-HSC 103 12/4 Uen M 2004-09-17

Table 15 New BSC Commands

Command Description Level Feature
RRPLP Selfconfiguring BSC FAJ 121 356
TRA Pool
Change Log
Print
RRPAR Selfconfiguring BSC FAJ 121 356
TRA Pool
Timeout alarm,
Reset
RLDHC Dynamic HR CELL FAJ 122 582
Allocation Data,
Change
RLDHP Dynamic HR CELL FAJ 122 582
Allocation Data,
Print
RLADC Re-definition BSC FAJ 121 055
of AMR Codec
Sets
RLADP Printing AMR BSC FAJ 121 055
Data
RLGNC GPRS CELL FAJ 121 375
Neighbour
Relation Data,
Change
RLGNP GPRS CELL FAJ 121 375
Neighbour
Relation Data,
Print
RLPSC Packet Specific CELL FAJ 121 375
Cell Data Plan,
Change
RLPSP Packet Specific CELL FAJ 121 375
Cell Data Plan,
Print
RLGAC Single slot Channel Group FAJ 121 363
TCH allocation
strategy,
Change
RLGAP Single slot Channel Group FAJ 121 363
TCH allocation
strategy,
Change
2/10948-HSC 103 12/4 Uen M 2004-09-17 95

8.2 STS Counter Changes
8.2.1 New Object Types

These new object types and counters are described in detail in 62/1553–HSC
103 12/4 User Description, Radio Network Statistics.
Table 16
Object Type Counter Description Level
CELLMSQ NQPCCNT Number of PC requests CELL
CELLMSQ RQHIGHCNT Number of PC that have been CELL
removed due to higher PC
request
CELLMSQ NIQLOWCNT number of PCs not allowed in CELL
queue due to PC has lower
priority-queue is full
CELLMSQ RQT11CNT Number of PCs that have been CELL
removed from queue due to
time out
CELLMSQ NPCALLOC- MS queuing counter CELL
CNT
CELLMSQ RQLOSSCNT MS queuing counter CELL
CELLPAG PAGCHCONG Number of discarded pages CELL
due to full Page queue in the
BTS
CELLPAG PAGTOOOLD Number of discarded pages CELL
due to age
CLRATECHG HOAT- Number of intra cell handover CELL
FRHRAMR attempts due to FR to HR
channel rate change made by
an AMR capable mobile
CLRATECHG HOAT- Number of intra cell handover CELL
FRHRNAMR attempts due to FR to HR
a mobile not capable of AMR
CLRATECHG HO- Number of succesful intra cell CELL
SUCFRHRAMR handovers due to FR to HR
CLRATECHG HO- Number of successful intra cell CELL
SUCFRHRNAMR handovers due to FR to HR
96 2/10948-HSC 103 12/4 Uen M 2004-09-17

Table 16
CLRATECHG HOATHRFRAMR Number of intra cell handover CELL
attempts due to HR to FR
CLRATECHG HOATHRFR- Number of intra cell handover CELL
NAMR attempts due to HR to FR
CLRATECHG HO- Number of successful intra cell CELL
SUCHRFRAMR handovers due to HR to FR
CLRATECHG HOSUCHRFR- Number of successful intra cell CELL
NAMR handovers due to HR to FR
CELEVENTSC SCLDCOMUL Subcell change attempts and CELL
successful subcell change
CELEVENTSC SCLDSUCUL Subcell change attempts and CELL
CELEVENTSC DTCBCOMUL Subcell change attempts and CELL
CELEVENTSC DTCBSUCUL Subcell change attempts and CELL
CELEVENTSC LOLCOMUL Subcell change attempts and CELL
CELEVENTSC LOLSUCUL Subcell change attempts and CELL
CELEVENTSC TAOLCOMUL Subcell change attempts and CELL
CELEVENTSC TAOLSUCUL Subcell change attempts and CELL
BSCGPRS2 RPP0040 Number of scans where RPP BSC
load was between 0 and 40%
2/10948-HSC 103 12/4 Uen M 2004-09-17 97

Table 16
load was between 91 and
100%
CELLGPRS2 LDISTFI Number of times the entire CELL
contents of DL LLC PDU
buffer were discarded due to
the reason No available PDCH
or TFI
CELLGPRS2 LDISOTH Number of times the entire CELL
the reason ’Other’
CELLGPRS2 PSCHREQ Number of successful received CELL
access requests in the PCU
on any channel
CELLGPRS2 PREJTFI Number of rejected access CELL
requests for the reason No
PDCH, USF or TFI
CELLGPRS2 PREJOTH Number of rejected access CELL
requests due to reason ’Other’
CELLGPRS2 IAULREL Number of times an UL TBF CELL
is closed down because radio
contact has been lost with
the MS after PS immediate
Assignment or the Packet UL
Assignment has been sent
CELLGPRS2 FLUDISC Number of flush messages CELL
from SGSN that resulted in
one or more LLC PDUs in the
buffer being discarded.
CELLGPRS2 FLUMOVE Number of flush messages CELL
from SGSN that resulted in
one or more LLC PDUs in the
buffer being moved to another
queue
CELLGPRS2 LDISRR Number of times the entire CELL
the radio reasons
CELLGPRSO ALLPDCH- Number of accumulations CELL
SCANSUB of alloacated PDCHs in OL
subcell
98 2/10948-HSC 103 12/4 Uen M 2004-09-17

Table 16
CELLGPRSO PREEMTPD- Number of preemted used CELL
CHSUB PDCHs in OL subcell
CELLGPRSO ALLPD- Number of allocated PDCHs CELL
CHACCSUB accumulator for OL subcell
CELLGPRSO ALLPDCHAC- Number of used PDCHs CELL
TACCSUB accumulator for OL subcells
CELLGPRSO MC19DLSCHED- Number of RLC data blocks CELL
SUB scheduled by the MAC
protocol in the OL subcell only
for MCS 1–9
CELLGPRSO MC19DLACK- Total amount of RLC data CELL
SUB successfully acknowledged
from the total RLC data blocks
scheduled on the DL in the OL
subcell only for MCS 1–9
CELLGPRSO MC19ULSCHED- Number of RLC data blocks CELL
for MCS 1–9
CELLGPRSO MC19ULACK- Total amount of RLC data CELL
scheduled on the UL in the OL
subcell only for MCS 1–9
CELLGPRSO CS14DLSCHED- Number of RLC data blocks CELL
for CS 1–4
CELLGPRSO CS14DLACK- Total amount of RLC data CELL
subcell only for CS 1–4
CELLGPRSO CS12DLSCHED- Number of RLC data blocks CELL
for CS 1–2
CELLGPRSO CS12DLACK- Total amount of RLC data CELL
scheduled on the DL in the OL
2/10948-HSC 103 12/4 Uen M 2004-09-17 99

Table 16
CELLGPRSO CS12ULSCHED- Number of RLC data blocks CELL
for CS 1–2
CELLGPRSO CS12ULACK- Total amount of RLC data CELL
CELLGPRSO LDISRRSUB Number of tiems the entire CELL
contents of the DL LLC PDU
radio reasons
CELLGPRSO IAULRELSUB Number of times an UL TBF CELL
is closed down because radio
contact has been lost with the
MS after the PS Immediate
Assignment message or
the Packet UL Assignment
message has been sent in the
OL subcell only
CELLQOSS VOLUL- Accumulated UL TBF volume CELL
STRACC over one measurement period
CELLQOSS WTHP10STRACCDL weighted throughput over CELL
one measurement period in
the GBR interval 10–19
100 2/10948-HSC 103 12/4 Uen M 2004-09-17

Table 16
CELLQOSS WTHP120STRACC
DL weighted throughput over CELL
CELLQOSS WTHP160STRACC
DL weighted throughput over CELL
the GBR interval 160 and over
CELLQOSS VOL10STRACC Accumulated DL TBF volume CELL
over one measurement period
in the GBR interval 10–19
in the GBR interval 160 and
over
CLQOSSCON CELLPPRS QoS Streaming Congestion CELL
counter
CLQOSSCON GBR10REQ QoS Streaming Congestion CELL
counter
counter
counter
counter
2/10948-HSC 103 12/4 Uen M 2004-09-17 101

Table 16
counter
counter
counter
counter
CLQOSSCON GBR10LOW QoS Streaming Congestion CELL
counter
counter
counter
counter
counter
counter
counter
counter
CLQOSSCON2 GBR10FAIL QoS Streaming Congestion CELL
counter
counter
counter
counter
counter
counter
counter
102 2/10948-HSC 103 12/4 Uen M 2004-09-17

Table 16
counter
CLQOSSCON2 TBFUPS QoS Streaming Congestion CELL
counter
DELSTRTBF START- QoS Streaming Counter BSC
STRTBF
DELSTRTBF STARTCON- QoS Streaming Counter BSC
TSTRTBF
DELSTRTBF PENDSTRTBF QoS Streaming Counter BSC
DELSTRTBF PENDCON- QoS Streaming Counter BSC
TSTRTBF
TRAFFDLGPRS TRAFFDL- GPRS DL Traffic load counter CELL
GPRSSCAN
TRAFFDLGPRS TBFDLGPRS GPRS DL Traffic load counter CELL
TRAFFDLGPRS TBFDLEGPRS GPRS DL Traffic load counter CELL
TRAFFDLGPRS DLBPDCH GPRS DL Traffic load counter CELL
TRAFFDLGPRS DLGPDCH GPRS DL Traffic load counter CELL
TRAFFDLGPRS DLEPDCH GPRS DL Traffic load counter CELL
TRAFFDLGPRS DLTBFPBDCH GPRS DL Traffic load counter CELL
TRAFFDLGPRS DLTBFGPDCH GPRS DL Traffic load counter CELL
TRAFFDLGPRS DLTBFEPDCH GPRS DL Traffic load counter CELL
TRAFFDLGPRS STRBPDCH GPRS DL Traffic load counter CELL
TRAFFDLGPRS STRGPDCH GPRS DL Traffic load counter CELL
TRAFFDLGPRS STREPDCH GPRS DL Traffic load counter CELL
TRAFFDLGPRS QOSWDLBA- GPRS DL Traffic load counter CELL
SIC
TRAFFDLGPRS QOSWDL- GPRS DL Traffic load counter CELL
GPRS
TRAFFDLGPRS QOSWDLEG- GPRS DL Traffic load counter CELL
PRS
TRAFFULGPRS TRAFFUL- GPRS UL Traffic load counter CELL
GPRSSCAN
TRAFFULGPRS TBFULGPRS GPRS UL Traffic load counter CELL
TRAFFULGPRS TBFULEGPRS GPRS UL Traffic load counter CELL
TRAFFULGPRS ULBPDCH GPRS UL Traffic load counter CELL
TRAFFULGPRS ULGPDCH GPRS UL Traffic load counter CELL
2/10948-HSC 103 12/4 Uen M 2004-09-17 103

Table 16
TRAFFULGPRS ULEPDCH GPRS UL Traffic load counter CELL
TRAFFULGPRS ULTBFPBDCH GPRS UL Traffic load counter CELL
TRAFFULGPRS ULTBFGPDCH GPRS UL Traffic load counter CELL
TRAFFULGPRS DLTBFEPDCH GPRS UL Traffic load counter CELL
TRAFFULGPRS QOSWULBA- GPRS UL Traffic load counter CELL
SIC
TRAFFULGPRS QOSWUL- GPRS UL Traffic load counter CELL
GPRS
TRAFFULGPRS QOSWULEG- GPRS UL Traffic load counter CELL
PRS
TRAFFGPRS2 TRAFF2BTBF- GPRS traffic load counter CELL
SCAN
TRAFFGPRS2 TRAFF2GTBF- GPRS traffic load counter CELL
SCAN
TRAFFGPRS2 TRAFF2ETBF- GPRS traffic load counter CELL
SCAN
TRAFFGPRS2 MUTILBASIC GPRS traffic load counter CELL
TRAFFGPRS2 MULTIGPRS GPRS traffic load counter CELL
TRAFFGPRS2 MULTIEGPRS GPRS traffic load counter CELL
TRAFFGPRS2 MAXTSDL GPRS traffic load counter CELL
TRAFFGPRS2 MUTIL24 GPRS traffic load counter CELL
CELLFERF TFV3FERCM1 FR Frame Erasure Rate (FER) CELL
counter
counter
counter
104 2/10948-HSC 103 12/4 Uen M 2004-09-17

Table 16
counter
CELLFERF TFV1FER FR Frame Erasure Rate (FER) CELL
counter
CELLFERF TFV2FER FR Frame Erasure Rate (FER) CELL
counter
CELLFERF TFV3TFCM1 FR Frame Erasure Rate (FER) CELL
counter
counter
counter
counter
CELLFERF TFV1FERTF FR Frame Erasure Rate (FER) CELL
counter
CELLFERF TFV2FERTF FR Frame Erasure Rate (FER) CELL
counter
CELLFERH THV3FERCM1 HR Frame Erasure Rate (FER) CELL
counter
counter
counter
counter
CELLFERH THV1FER HR Frame Erasure Rate (FER) CELL
counter
CELLFERH THV1FERTF HR Frame Erasure Rate (FER) CELL
counter
CELLFERH THV3TFCM1 HR Frame Erasure Rate (FER) CELL
counter
counter
counter
counter
2/10948-HSC 103 12/4 Uen M 2004-09-17 105

Table 16
CLTCHFV3C TFV3CM1UL Codec mode utilisation (AMR CELL
FR) counter
FR) counter
FR) counter
FR) counter
CLTCHFV3C TFV3CM1DL Codec mode utilisation (AMR CELL
FR) counter
FR) counter
FR) counter
FR) counter
CLTCHHV3C THV3CM1UL Codec mode utilisation (AMR CELL
HR) counter
HR) counter
HR) counter
HR) counter
CLTCHHV3C THV3CM1DL Codec mode utilisation (AMR CELL
HR) counter
HR) counter
HR) counter
HR) counter
CLTCHDRAF TFDISTAA Dropped connections for CELL
TCH/F
CLTCHDRAF TFSUDLOSA Dropped connections for CELL
TCH/F
CLTCHDRAF TFSUDLOS- Dropped connections for CELL
SUBA TCH/F
106 2/10948-HSC 103 12/4 Uen M 2004-09-17

Table 16
CLTCHDRAF TFDISSDLA Dropped connections for CELL
TCH/F
CLTCHDRAF TFDISSDL- Dropped connections for CELL
SUBA TCH/F
CLTCHDRAF TFDISSULA Dropped connections for CELL
TCH/F
CLTCHDRAF TFDISSUL- Dropped connections for CELL
SUBA TCH/F
CLTCHDRAF TFDISSBLA Dropped connections for CELL
TCH/F
CLTCHDRAF TFDISS- Dropped connections for CELL
BLSUBA TCH/F
CLTCHDRAF TFDISQADLA Dropped connections for CELL
TCH/F
CLTCHDRAF TFDISQADL- Dropped connections for CELL
SUBA TCH/F
CLTCHDRAF TFDISQAULA Dropped connections for CELL
TCH/F
CLTCHDRAF TFDIS- Dropped connections for CELL
QAULSUBA TCH/F
CLTCHDRAF TFDISQABLA Dropped connections for CELL
TCH/F
CLTCHDRAF TFDIS- Dropped connections for CELL
QABLSUBA TCH/F
CLTCHDRAH THDISTAA Dropped connections for CELL
TCH/H
CLTCHDRAH THSUDLOSA Dropped connections for CELL
TCH/H
CLTCHDRAH THSUDLOS- Dropped connections for CELL
SUBA TCH/H
CLTCHDRAH THDISSDLA Dropped connections for CELL
TCH/H
CLTCHDRAH THDISSDL- Dropped connections for CELL
SUBA TCH/H
CLTCHDRAH THDISSULA Dropped connections for CELL
TCH/H
CLTCHDRAH THDISSUL- Dropped connections for CELL
SUBA TCH/H
2/10948-HSC 103 12/4 Uen M 2004-09-17 107

Table 16
CLTCHDRAH THDISSBLA Dropped connections for CELL
TCH/H
CLTCHDRAH THDISS- Dropped connections for CELL
BLSUBA TCH/H
CLTCHDRAH THDISQADLA Dropped connections for CELL
TCH/H
CLTCHDRAH THDISQADL- Dropped connections for CELL
SUBA TCH/H
CLTCHDRAH THDISQAULA Dropped connections for CELL
TCH/H
CLTCHDRAH THDIS- Dropped connections for CELL
QAULSUBA TCH/H
CLTCHDRAH THDISQABLA Dropped connections for CELL
TCH/H
CLTCHDRAH THDIS- Dropped connections for CELL
QABLSUBA TCH/H
8.2.2 Changed Object Types

These object types have been changed. A more thorough explanation of the
changes and the new behavior can be found in 62/1553–HSC 103 12/4 User
Description, Radio Network Statistics.
Table 17
CELLSQI TSQIGOODAF SQS for AMR. New counter CELL
for monitoring speech quality
for AMR FR and HR codecs
for overlaid and underlaid
subcells.
CELLSQI TSQIGOODAH SQS for AMR. New counter CELL
subcells.
CELLSQI TSQIGOOD- SQS for AMR. New counter CELL
SUBAF for monitoring speech quality
subcells.
108 2/10948-HSC 103 12/4 Uen M 2004-09-17

Table 17
CELLSQI TSQIGOOD- SQS for AMR. New counter CELL
SUBAH for monitoring speech quality
subcells.
CELLSQI TSQIACCPTAF SQS for AMR. New counter CELL
subcells.
CELLSQI TSQIACCPTAH SQS for AMR. New counter CELL
subcells.
CELLSQI TSQIACCPT- SQS for AMR. New counter CELL
SUBAF for monitoring speech quality
subcells.
CELLSQI TSQIACCPTS- SQS for AMR. New counter CELL
BAH for monitoring speech quality
subcells.
CELLSQI TSQIBADAF SQS for AMR. New counter CELL
subcells.
CELLSQI TSQIBADAH SQS for AMR. New counter CELL
subcells.
CELLSQI TSQIBADSUBAF SQS for AMR. New counter CELL
subcells.
CELLSQI TSQIBADSUBAH SQS for AMR. New counter CELL
subcells.
2/10948-HSC 103 12/4 Uen M 2004-09-17 109

Table 17
BSC BSCCUMMS MS Session counter. Changed BSC
from 16 bits to 32 bits due to
overflow.
BSC GSM900CUMMS MS Session counter. Changed BSC
from 16 bits to 32 bits due to
overflow.
RANDOMACC RA- Random Access Counter. CELL
TRHFAOTHER Changed behavior due to
new counter in object type.
RATRHFAOTHER(new)=RA-
TRHFAOTHER(old)-RA-
TRHFAANPAG.
RANDOMACC RATRHFAAN- New Random Access Counter. CELL
PAG The counter will be stepped
for every rejected “CHANNEL
REQUIRED” in TRH with
establishment cause “Answer
to paging”
BSCGPRS NACCPCO Number of PCCP messages BSC
sent per BSC. New counter.
BSCGPRS ESUTONRM Number of TBF set up in ’Early BSC
Set-up of DL TBF mode’ that
resume normal operation.
New counter.
BSCGPRS ESUDLTBF Number of TBF set up in ’Early BSC
Set-up of DL TBF mode’. New
counter.
BSCGPRS DELRELTONRM Number of DL TBFs for which BSC
the release is delayed in
’Delayed Release of a DL TBF
mode’ that resume normal
operation. New counter.
BSCGPRS DELRELDLTBF Number of DL TBFs for which BSC
the release is delayed in
’Delayed Release of a DL TBF
mode’. New counter.
BSCGPRS EXULTIP Number of UL TBFs entering BSC
the ’Temporary Inactive
Period’. New counter.
BSCGPRS EXULNRM Number of UL TBFs entering BSC
the ’Temporary Inactive Period’
that resume normal operation.
New counter.
110 2/10948-HSC 103 12/4 Uen M 2004-09-17

Table 17
BSCGPRS GSL0040 Total number of scans where BSC
fraction is between 0 and 40%.
New counter.
fraction is between 41 and
60%. New counter.
80%. New counter.
90%. New counter.
100%. New counter.
BSCGPRS GSLMAX Accumulated number of BSC
maximum GSL 16 kbit/s
devices possible to use. New
counter.
BSCGPRS GSLUTIL Accumulated number of BSC
maximum GSL devices
possible to use, fractions
calculated for each scan. New
counter.
BSCGPRS GSLSCAN Number of scans of PCU BSC
taken in relation to GSL device
utilization. New counter.
CELLGPRS CS12ULSCHED Main GPRS events in BSC. CELL
New counter to monitor the
average radio link bitrate.
CELLGPRS CS12DLSCHED Main GPRS events in BSC. CELL
CELLGPRS CS12ULACK Main GPRS events in BSC. CELL
CELLGPRS CS12DLACK Main GPRS events in BSC. CELL
CELLGPRS MC19ULSCHED Main GPRS events in BSC. CELL
2/10948-HSC 103 12/4 Uen M 2004-09-17 111

Table 17
CELLGPRS MC19ULACK Main GPRS events in BSC. CELL
LOADREG NREJIEX Load Regulation counter. New BSC
counter for the number of
terminating calls rejected by
the process load control.
CELLQOSG ULTHP1GTHR GPRS QoS throughput CELL
counter. Counter
weighted by data volume.
ULTHP1GTHR(new) =
ULTHP1GTHR(old) * LLC
data volume.
CELLQOSG DLTHP1GTHR GPRS QoS throughput CELL
counter. Counter
DLTHP1GTHR(new) =
DLTHP1GTHR(old) * LLC
data volume.
counter. Counter
ULTHP2GTHR(new) =
data volume.
counter. Counter
DLTHP2GTHR(new) =
data volume.
counter. Counter
ULTHP3GTHR(new) =
data volume.
counter. Counter
DLTHP3GTHR(new) =
data volume.
112 2/10948-HSC 103 12/4 Uen M 2004-09-17

Table 17
CELLQOSG ULBGGTHR GPRS QoS throughput CELL
counter. Counter
ULBGGTHR(new)
=ULBGGTHR(old) * LLC
data volume.
CELLQOSG DLBGGTHR GPRS QoS throughput CELL
counter. Counter
DLBGGTHR(new)
=DLBGGTHR(old) * LLC
data volume.
CELLQOSEG ULTHP1EGTHR EGPRS QoS throughput CELL
counter. Counter
ULTHP1EGTHR(new) =
ULTHP1EGTHR(old) * LLC
data volume.
CELLQOSEG DLTHP1EGTHR EGPRS QoS throughput CELL
counter. Counter
DLTHP1EGTHR(new) =
DLTHP1EGTHR(old) * LLC
data volume.
counter. Counter
ULTHP2EGTHR(new) =
data volume.
counter. Counter
DLTHP2EGTHR(new) =
data volume.
counter. Counter
ULTHP3EGTHR(new) =
data volume.
2/10948-HSC 103 12/4 Uen M 2004-09-17 113

Table 17
counter. Counter
DLTHP3EGTHR(new) =
data volume.
CELLQOSEG ULBGEGTHR EGPRS QoS throughput CELL
counter. Counter
ULBGEGTHR(new) =
ULBGEGTHR(old) * LLC
data volume.
CELLQOSEG DLBGEGTHR EGPRS QoS throughput CELL
counter. Counter
DLBGEGTHR(new) =
DLBGEGTHR(old) * LLC
data volume.
RLINKBITR INT8BRG- GPRS Radio Link Quality CELL
PRSTBF counter. Measures “volume
of successfully received RLC
data” instead of “number of
TBFs”.
TBFs”.
TBFs”.
TBFs”.
TBFs”.
114 2/10948-HSC 103 12/4 Uen M 2004-09-17

Table 17
TBFs”.
RLINKBITR INT10BREG- GPRS Radio Link Quality CELL
TBFs”.
TBFs”.
TBFs”.
TBFs”.
TBFs”.
TBFs”.
TBFs”.
TBFs”.
2/10948-HSC 103 12/4 Uen M 2004-09-17 115

Table 17
TBFs”.
TBFs”.
8.2.3 Removed Counters
Table 18
CELLGPRS RBCDL Main GPRS events in BSC. CELL
Replaced by CS12DLSCHED
(only acknowledged mode)
CELLGPRS RBCUL Main GPRS events in BSC. CELL
Replaced by CS12ULSCHED
CELLGPRS ERBCUL Main GPRS events in BSC. CELL
Replaced by MC19ULSCHED
CELLGPRS RETRANSDL Main GPRS events in BSC. CELL
Replaced by CS12DLACK
(different usage)
CELLGPRS RETRANSUL Main GPRS events in BSC. CELL
Replaced by CS12ULACK
(different usage)
CELLGPRS ERETRANSUL Main GPRS events in BSC. CELL
Replaced by MC19ULACK
(different usage)
TRAFFGPRS TBFPULGPRS GPRS Traffic load counter. CELL
Object type TRAFFGPRS
is replaced by object
types TRAFDLGPRS and
TRAFULGPRS.
116 2/10948-HSC 103 12/4 Uen M 2004-09-17

Table 18
TRAFFGPRS TBFPDLGPRS GPRS Traffic Load counter. CELL
TRAFULGPRS.
TRAFFGPRS TBFPDLEGPRS GPRS Traffic Load counter. CELL
TRAFULGPRS.
TRAFFGPRS TBFPULEGPRS GPRS Traffic Load counter. CELL
TRAFULGPRS.
TRAFFGPRS PDCHULGPRS GPRS Traffic Load counter. CELL
TRAFULGPRS.
TRAFFGPRS PDCHDLGPRS GPRS Traffic Load counter. CELL
TRAFULGPRS.
TRAFFGPRS PDCHULEGPRS GPRS Traffic Load counter. CELL
TRAFULGPRS.
TRAFFGPRS PDCHDLEGPRS GPRS Traffic Load counter. CELL
TRAFULGPRS.
TRAFFGPRS TBFPULBASIC GPRS Traffic Load counter. CELL
TRAFULGPRS.
TRAFFGPRS TBFPDLBASIC GPRS Traffic Load counter. CELL
TRAFULGPRS.
2/10948-HSC 103 12/4 Uen M 2004-09-17 117

Table 18
TRAFFGPRS PDCHULBASIC GPRS Traffic Load counter. CELL
TRAFULGPRS.
TRAFFGPRS PDCHDLBASIC GPRS Traffic Load counter. CELL
TRAFULGPRS.
8.2.4 Changed Counter Names
Table 19
Object Old New Description Level
Type Counter Counter
CLCTCH TASSMS5 TCASSALL Assignment complete for all CELL
MSs. Name changed with
kept functionality (all MS
classes).
8.2.5 Non functional changes of counters

The following changes in the system has affected the counter behavior.
How much that you can see of these changes is dependent on traffic mix
and compared AC-A levels on the BSC releases. The list of changes is not
complete since the requirement for this information came late in the project.
The information shown below is mainly concerning GPRS counters.
Table 20
Object type Counter Change
BSCQOS PFCLIFETIME The removed threshold
MIN_PFC_OCTET=0 will make
counter increase.
BSCQOS NUMBERTBF The removed threshold
MIN_PFC_OCTET=0 will make
counter increase.
118 2/10948-HSC 103 12/4 Uen M 2004-09-17

Table 20
BSCQOS NUMBERLL- This quota is the average throughput
CPDU / PFCLIFE- and it might decrease because
TIME of the removed threshold
MIN_PFC_OCTET=0 but might
also increase because of the Delayed
release of TBFs and Early setup of
TBFs.
CELLQOSEG all Same changes as for CELLQOSG.
CELLQOSG xxxxDATA Counters might increase because
of the removed threshold
MIN_PFC_OCTET=0.
CELLQOSG xxxxPFC Counters might increase because
of the removed threshold
MIN_PFC_OCTET=0, but might
decrease because of the delayed
release of TBF and early setup of TBF.
CELLQOSG average Observe that the method of calculating
throughput the average throughput is changed but
the value should be about the same
(see explanation on BSCQOS average
throughput above):
R9.1: xxxxTHR/xxxxPFC = average
throughput
R10: xxxxTHR/xxxxDATA = average
throughput
BSCGPRS ALLPDCH Counter might increase due to early
set-up of DL TBFs (number of PDCH
allocation has increased)
CELLGPRS ALLPDCA, Counters might increase due to early
ALLPDCS, setup of DL TBFs (number of PDCH
PCHALLA, allocations has increased)
PCHALLF
CELLGPRS FAILDLT Counters might have increased
depending on that the counterin early
R10 releases counted also the failed
early setups of DL TBFs. This is now
changed and behaviour should be
approximately the same as in R9.1.
2/10948-HSC 103 12/4 Uen M 2004-09-17 119

9 Glossary
ABQP Aggregate BSS Quality of Service Profile
ACS Active Codec Set
AMR Adaptive Multi Rate
BAR active BCCH Allocation list Recording
BCCH Broadcast Control Channel
BSC Base Station Controller
BSM Base Station Manager
BSS Base Station System
BTS Base Transceiver Station
CCS Common Channel Signalling
CER Channel Event Recording
CTR Cell Traffic Recording
CNA Cellular Network Administration
CNAI CNA Interface
CP Central Processor
CGSN Combined SGSN-GGSN
DS Data Store
DT Data Transcript
EDGE Enhanced Data rate for GSM Evolution
EFR Enhanced Full Rate
FAS Frequency Allocation Support
FLP Fractional Load Planning
FM Fault Manager
FR Full Rate
120 2/10948-HSC 103 12/4 Uen M 2004-09-17

GGSN Gateway GPRS Support Node
GPRS General Packet Radio Services
GSL GPRS Signalling Link
GMPC Gateway Serving Mobile Positioning Centre
HLR Home Location Register
ICDM Inter Cell Dependency Matrix
IOG Input Output Group
MAIO Mobile Allocation Index Offset
MBC Multi Band Cell
MML Man-Machine Language
MPDCH Master Packet Data Channel
MS Mobile Station
MSC Mobile Switching Service Centre
MW16 Mega 16-bit word
MRR Measurement Result Recording
MTR Mobile Traffic Recording
NCS Neighbour Cell Support
NOX Neighbour Cell Optimisation Expert
NNRP4 Network Node Renewal Process 4
NWS Network Statistics
NSVC Network Services Virtural Connection
NE Network Element
OML Operation&Maintenace Link
OMC Operation adn Maintenance Centre
OMT Operation and Maintenance Terminal
2/10948-HSC 103 12/4 Uen M 2004-09-17 121

OSS Operation Support System
PACCH Packet Associated Control Channel
PC Personal Computer
PCM Pulse Code Modulation
PCU Packet Control Unit
PCH Paging Channel
PDP Packet Data Protocol
PFC Packet Flow Context
PIT Percentage Interfered Traffic
PDCH Packet Data Channel
PMR Performance Management Recording
RNO Radio Network Optimiser
RNX Radio Network eXpert
PS Program Store
RP Regional Processor
RPP Regional Processor with PCI interface
RPI Regional Processor Integrated
RPG Regional Processor with Group Switch Interface
R-PMO Realtime Performance Monitoring
RS Reference Store
RSL Radio Signalling Link
RX Reciever
SAE Size Alteration Event
SDCCH Standalone Dedicated Control Channel
SGSN-G Serving GPRS Support Node(GSM)
SL Signalling Link
SP Support Processor
122 2/10948-HSC 103 12/4 Uen M 2004-09-17

SMPC Serving Mobile Positioning Centre
SQS Speech Quality Supervision
STOC Signalling Terminal for Open Communications
STS Statistical Subsystem
TBF Temporary Block Flow
TCH Traffic Channel
TCP Transmission Control Protocol
TF Timing Function
TG Transceiver Group
TRA Transcoder and Rate Adaptor
TRC Transcoder Controller
TRH Transceiver Handler
TRU Tranceiver Unit
TRX Transceiver
10 References
10/109 21–APT 210 09/207–1 Changes to the Operator Interface from APT 210
09/203 R1A to APT 210 09/207 R1A
62/1553–HSC 103 12/4 User Description, Radio network Statistics
2/10948-HSC 103 12/4 Uen M 2004-09-17 123

BSS R10 Network Impact Report

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

BSS R10 Network Impact Report

Uploaded by

Copyright:

Available Formats

BSS R10 Network Impact Report

©Ericsson AB 2002, All Rights Reserved.

2/10948-HSC 103 12/4 Uen M 2004-09-17

5 Impacting BSS Features 20

2/10948-HSC 103 12/4 Uen M 2004-09-17

5.16 Dynamic Overlaid / Underlaid Subcells 45

6 Impacting BTS Features 76

7 Impacting OSS Features 79

8 Summary of Operator Interface Changes 80

2/10948-HSC 103 12/4 Uen M 2004-09-17

B 2003–01–20 ENEILOR Updated with changed counters,

2/10948-HSC 103 12/4 Uen M 2004-09-17 1

D 2003–05–23 EPKHASP The main changes are:

2 2/10948-HSC 103 12/4 Uen M 2004-09-17

2/10948-HSC 103 12/4 Uen M 2004-09-17 3

G 2003–10–24 EPKHASP The changes are:

4 2/10948-HSC 103 12/4 Uen M 2004-09-17

J 2003–12–12 EPKHASP Information added in chapter 3.6

2/10948-HSC 103 12/4 Uen M 2004-09-17 5

3.1 Capacity and Performance

The OSS capacity and performance are not yet estimated.

This configuration consists of a single master server. It is designed to manage

Table 2 Supported maximum network configuration for configuration A

6 2/10948-HSC 103 12/4 Uen M 2004-09-17

This configuration consists of a single master server. It is designed to manage

Table 3 Supported maximum network configuration for configuration B

This configuration consists of a single master server. It is designed to manage

Table 4 Supported maximum network configuration for configuration C

2/10948-HSC 103 12/4 Uen M 2004-09-17 7

The RBS 200 platform is also supported.

8 2/10948-HSC 103 12/4 Uen M 2004-09-17

2) If a cell is served by a TG cluster and is configured to use either base band or

A new RBS configuration, Mixed HW Configuration, is supported in BTS SW

2/10948-HSC 103 12/4 Uen M 2004-09-17 9

Table 5 New Feature support on various RBS platforms.

1:RBS 2301 supported only if revision R6A or higher.

10 2/10948-HSC 103 12/4 Uen M 2004-09-17

2:AMR FR is already supported in BSS R9.1

3:Battery test not supported on RBS 2308

• E4500, E5500 and E6500 (CPU model 400MHz)

• SF V880, SF 4800 and SF 6800 (CPU model 1.05GHz)

• Workstations of three models, Ultra 5, Ultra 10 and Blade 150

For BSS R9.1 to BSS R10

1 OSS R9.1 to OSS-RC 1.1

2 BSC R9.1 to BSC R10

The order of TRC, BSC/TRC and BSC is independent.

3 If BSC is upgraded to R10 before upgrading BTS SW:

BTS 9C to BTS 10A (valid for RBS 2101/2102/2202/2301/2302/2401)

BTS 9.1B/9.1C/9.1D to BTS 10.1A/10.1B (valid for RBS

BTS 9C/10A or 9.1D/10.1A/10.1B to 10.2A (valid for Mixed HW

BTS 9B to BTS 10A (valid for RBS 200)

If BTS is upgraded before BSC:

BTS 9A/9B/9C to BTS 10A (valid for RBS 2101/2102/2202/2301/2302/2401)

BTS 9.1A/9.1B/9.1C/9.1D to BTS 10.1A/10.1B (valid for RBS

2/10948-HSC 103 12/4 Uen M 2004-09-17 11

BTS 9A/9B/9C/10A or 9.1D/10.1A/10.1B to 10.2A (valid for Mixed HW

To upgrade RBS200 SW before the BSC is not supported.

4 SMPC 5.0 to SMPC 6.0

SMPC can be upgraded independent of the other nodes.

For BSS R10 NA ED to BSS R10

1 OSS R10 NA ED to OSS-RC 1.1

2 BSC R10 NA ED to BSC R10

The order of TRC, BSC/TRC and BSC is independent.