alex0675 (1).pdf

109 48-HSC 103 12/7 Uen Rev F

BSS R12 Network Impact Report

NETW. IMPACT REPORT


109 48-HSC 103 12/7 Uen Rev F 2007-01-26 © Ericsson AB 2005-2006 � All Rights Reserved Ericsson Internal

2 (175)

Copyright

© Ericsson AB 2005-2006 � All Rights Reserved

Disclaimer

No part of this document may be reproduced in any form without the written permission of the copyright owner.

The contents of this document are subject to revision without notice due to continued progress in methodology, design, and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.



3 (175)

Contents

1 Introduction............................................................................................ 5

2 Revision Information............................................................................. 5

3 General BSS Impact .............................................................................. 8 3.1 Capacity and Performance ...................................................................... 8 3.2 Hardware ............................................................................................... 11 3.3 Implementation ...................................................................................... 15 3.4 Interface................................................................................................. 17 3.5 Memory.................................................................................................. 17 3.6 Dimensioning / System Limits ............................................................... 19 3.7 Overload Performance .......................................................................... 19 3.8 Operations ............................................................................................. 20 3.9 Other Features ...................................................................................... 20 3.10 Other Network Elements ....................................................................... 20

4 Summary of Impacts ........................................................................... 22 4.1 BSS Features ........................................................................................ 22 4.2 OSS-RC Features ................................................................................. 24

5 Impacting BSS Features ..................................................................... 25 5.1 Abis Triggered HR Allocation ................................................................ 25 5.2 Active Queue Management (AQM)........................................................ 27 5.3 Adaptive Configuration of SDCCHs....................................................... 30 5.4 Adaptive Multi Rate (AMR) .................................................................... 31 5.5 Admission Control for Push to Talk ....................................................... 32 5.6 AMR Power Control ............................................................................... 35 5.7 AMR Radio Link Timers......................................................................... 36 5.8 Application Aware Timeslot Allocation................................................... 38 5.9 BSC IP Connectivity .............................................................................. 40 5.10 BSS R12 GPRS/EGPRS Improvements ............................................... 42 5.11 BSS R12 System Improvements ........................................................... 45 5.12 BSS R12 System Improvements, BTS .................................................. 47 5.13 BSS R12 System Improvements, OSS-RC ........................................... 49 5.14 Channel Repacking ............................................................................... 50 5.15 Combined Cell re-selection triggering GSM to WCDMA ....................... 53 5.16 Dual Transfer Mode............................................................................... 54 5.17 Dynamic BTS Power Control ................................................................. 56 5.18 Dynamic MS Power Control .................................................................. 57 5.19 Dynamic Overlaid/underlaid Subcell...................................................... 58 5.20 Enhanced Measurement Reporting (EMR)............................................ 59 5.21 Five Downlink Timeslots ........................................................................ 61 5.22 Flexible Abis .......................................................................................... 64 5.23 Flexible Channel Allocation ................................................................... 66 5.24 Flexible Priority Handling of Packet Data Channels .............................. 69 5.25 Full Rate AMR on 8 kbps Abis............................................................... 70 5.26 Gb over IP ............................................................................................. 71



4 (175)

5.27 GPRS/EGPRS Load Optimisation......................................................... 75 5.28 GPRS/EGPRS Mobile Logging ............................................................. 78 5.29 GSM-UMTS Cell Reselection and Handover......................................... 79 5.30 GSM-WCDMA Active BA List Recording............................................... 80 5.31 Handover with Usage of Service Indicator ............................................ 82 5.32 Immediate Assignment on TCH............................................................. 85 5.33 Incremental Redundancy in Uplink........................................................ 86 5.34 Interference Rejection Combining ......................................................... 88 5.35 Inter System Consistency Reports ........................................................ 89 5.36 Mixed Micro Configurations ................................................................... 90 5.37 Multi Band Cell ...................................................................................... 91 5.38 Multi-Layered HCS ................................................................................ 92 5.39 Operation Maintenance Terminal .......................................................... 94 5.40 PCU Load Control ................................................................................. 96 5.41 Predefined Configuration Profiles.......................................................... 98 5.42 Radio Network Optimisation (RNO)..................................................... 100 5.43 RBS 2000 Synchronization.................................................................. 101 5.44 Real-Time Event Data and Real-Time Performance Monitoring ......... 104 5.45 Remote OMT ....................................................................................... 106 5.46 Remote OMT over IP........................................................................... 108 5.47 Self Configuring Transcoder Pools...................................................... 109 5.48 SGSN in Pool Support in BSC............................................................. 110 5.49 Single Phase Access for EGPRS ........................................................ 114 5.50 Smooth GSM to WCDMA Unloading................................................... 116 5.51 Speech Quality Supervision ................................................................ 117 5.52 Support for 1024 Cells in BSC............................................................. 120 5.53 Support for 8000 EGPRS Time Slots .................................................. 121 5.54 Support of AXE 810 � APT 1.5............................................................ 122 5.55 Tandem Free Operation ...................................................................... 123 5.56 Tight BCCH Frequency Reuse ............................................................ 128 5.57 Traffic Level Measurement Data.......................................................... 129 5.58 Voice Group Call Services................................................................... 130

6 Parameters Changes......................................................................... 134

7 STS Counter Changes....................................................................... 134 7.1 Modified Counters ............................................................................... 134 7.2 New Counters in Existing Object Types .............................................. 137 7.3 New Object Types ............................................................................... 144 7.4 Removed Counters.............................................................................. 154 7.5 Non Functional Changes of Counters ................................................. 154

8 Glossary ............................................................................................. 169

9 References ......................................................................................... 174



5 (175)

1 Introduction This document describes the impacts the new BSS R12 features will have on the BSS Product.

As long as this document is in preliminary state all information herein shall be treated as preliminary and not officially approved.

BSS R12 contains the following nodes:

• BSC R12

• BTS 12A, 12A_1 and 12B: RBS 2000 12A RBS 2000 12A_1 (is a post GA release, see ref [11]) RBS 2000 12B (is a post GA release) RBS 200 10A

• OSS-RC R3

2 Revision Information

Rev Date Description

A 2005-08-22 First Approved version

B 2005-10-07 CP capacity change updated for all APZ in table Table 2.

Added ref to BSC STS spreadsheet in chapter 3.1.1 (STS capacity)

Restart down times updated for APZ 212 33 in Table 3.

Added RBS 2112, 2103 in Table 4.

AQM: clarification about dependencies towards other network elements added in chapter Other Network Elements for the feature.

RTED, R-PMO feature characteristic chapter updated with BSC load information and operations chapter is updated with COD/POD/OPI/AI info.

Single Phase Access for EGPRS updated feature description due to changes for parameter EACPREF.



6 (175)

TFO updated feature implementation chapter with information about LSL.

Traffic Level Measurement Data updated with BSC name for interface.

Prepare TRU for removal, RBS information Log and LAPD multiplexing queuing alarm removed from BTS 12B scope. This changes leads to updates of Table 4 and feature descriptions for BSS R12 System Improvement, BTS and the OMT features in chapter 5.

New BTS configurations for 2107 and 2106 are removed from BTS 12B see chapter 3.2.2.1.

Linguistic updates.

C 2005-11-23 Feature Adaptive Configuration of Logical Channels is enhanced in R12 and added in this revision. This also impacts chapter 7.5

Feature Dynamic Overlaid/underlaid subcell is updated due to improved sub-cell load distribution. This also impacts chapter 7.5.

Feature GB over IP updated with information in interface chapter for the feature.

Feature Flexible Abis updated with information about interaction with other features.

Chapter 7.5 updated with impact on CELLGPRS from BSS R12 GPRS/EGPRS Improvements.

D 2006-03-23 Feature BSS R12 GPRS/EGPRS Improvements is updated since Single mode PCU is not supported in BSS R12, see 5.10. Command RRPCC also removed in R12, chapter 5.26.3

7.5.5 Non functional changes of counters due to Adaptive Configuration of SDCCHs is updated with more specific information.

Clarification of Gb failure detection when using IP network (replaces Gb Link Break) in 3.1.1.

BTS 12A_1 SW release included in 1.

OSS-RC R3, AOM 901 017/3 R1K updates: Feature Inter System Consistency Reports to support WCDMA P4 see 5.35.



7 (175)

Ch 3.1.1 and 5.52.4: Number of supported counters in APG40 increased to 1 900 000 for15-min BRP (verified together with ACA1). (BRP added in glossary).

Ch 3.10 and 5.57.1. Footnote about supported GMPC version added.

New chapter 7.5.6 added with non-functional changes of counters due to correction packages. Updated with info from packages up to ACA1.

Ch 3.2.1 Clarification that NNRP4 also supports TFO.

Minor editorial changes.

E 2006-07-17 Changes in chapter 7.5.6 due to changes in correction packages up to ACA2.

F 2007-01-26 Changed document number of reference [2].

Ch 5.51.2 clearified. EMR is not a strict requirement.

CH 5.16.2 corrected. Parameter DTMBTSPOWREG removed due to that was decided to not be implemented.

Ch 5.1.2 corrected. Parameter DFRAABISTHR should be DFRMAABISTHR. New parameter ATHABIS added.

Ch 5.49.3 corrected. Misspelled parameters: ARACPCCCH -> MSRACREQPCCCH and ARACCCCH -> MSRACREQCCCH.

Ch 5.17.1. corrected. Misspelled parameter: LCOMDL -> LCOMPDL

Changes in chapter 7.5.6 due to changes in correction packages up to ACA3.

Table 1 Revision Information



8 (175)

3 General BSS Impact

3.1 Capacity and Performance

3.1.1 BSC

Central Processor Performance:

With the BAS1 (traffic model used without GPRS traffic) and BAS2 (traffic model used with GPRS traffic) traffic models, the CP capacity loss compared to R11 is given in the table below.

Group Switch CP Capacity Change

APZ 212 20/25 GS12 - 4% to -5%

APZ 212 20/25 GS 890 - 6% to -7%

APZ 212 30/33 All types -1% to -2%

Table 2 CP Traffic Capacity change, BSC/TRC

The CP traffic capacity loss compared to R11 for a stand-alone BSC is expected to be in the same area as for BSC/TRC.

TRH Capacity:

For RPG1/2 and 3 the capacity is roughly equal to R11. For RPD the capacity drop is estimated to 20%, when the processor is limiting, compared to R11.

GPH Capacity:

The traffic handling capacity for the GPRS Packet Handler (GPH) processor is reduced in R12. This does not have any effect on dimensioning of GPH when the GPRS traffic per cell is low. In high traffic scenarios more RPPs may be required in the BSC.

APG40:

See ref [4] for changes to the APG40.

Maximum Traffic Capacity, CS:

For APZ 212 25 and APZ 212 20 the capacity is reduced compared to R11 as the CP capacity see Table 2.



9 (175)

For APZ 212 30/33 the maximum CS capacity is unchanged compared to R11 but limited by:

• for GS12 limited by the sub-rate switch (maximum 6 400 Erlang)

• for GS890 by the maximum amount of TRA HW in the product packages (maximum 12 000 Erlang).

TRA Capacity:

When TFO is configured number of transcoder resources per MUX group will be reduced (from 24 to 16). This is valid for TRA R6 that belongs to TFO capable EFR, AMR HR and AMR FR pools. This leads to a maximum reduction of channels per board from 192 to 128, if all MUX groups for that board are configured for TFO (EFR, AMR FR or AMR HR).

The new version of TRA hardware, TRA R6B, will not have this limitation and 192 channels per board will be supported for speech codecs with TFO.

Maximum Traffic Capacity, PS:

The maximum number of RPPs in the PCU is increased from 64 to 128 that give roughly the double capacity for GPRS traffic (requires feature ��Support for 8000 EGPRS Time Slots�) compared to R11.

At high GPRS traffic, Frame Relay traffic above 40 Mbit/s, the Ethernet cascade may become a bottleneck and the BSC LAN switch shall be used in that case.

STS Capacity:

With IOG20, up to a total number of 300 000 STS counters can be supported, unchanged from R11.

With APG40, the maximum valid configuration (1.941.200 counters) can used for a 15-minute Basic Recording Period (BRP) on an APG40 platform. When using a 5-minute BRP, the maximum number of supported counters is still 1 300 000.

In case the limit has been reached and not all counters were possible to fetch from STS an alarm will be raised.

For assistance to calculate number of STS counters the following document can be used, BSC STS Configuration Spreadsheet [10].

Restart Downtimes:

With restart downtime is meant the time until first call can be set up after a system restart.

Small restart Large restart without BTS reconf

Large restart with BTS reconf.

APZ 212 20 40 90 120



10 (175)

APZ 212 25 60 110 180

APZ 212 30 20 70 80

APZ 212 33 15 60 80

Table 3 Restart downtime (seconds)

Small restart is similar to R11, large restart has somewhat deteriorated compared to R11.

Radio Network Recovery:

The time for radio network recovery after system restart is similar to R11.

CP Downtime during Function Change:

CP downtime during upgrade is in the range 60-120 seconds for all APZ types.

RPP

RPP restart time will remain the same, but there will take some extra time to set-up the connections with the rest of the IP network depending on number of SGSNs. However, as soon as the first connection is set up to an SGSN, traffic can start.

Gb failure detection when using IP network

The detection time for one NSE failure will be between 30s - 60s depending on the number of remote IP access points in the peer NSE. The usage of IP network will improve the reliability and flexibility of transmission, compared to using T1/E1 and Frame Relay.

The detection time of a total Gb failure for a pool of SGSNs will slightly increase compared to when one SGSN is connected to the BSC.

3.1.2 BTS

There are no capacity or performance impacts to consider in this release.

3.1.3 OSS-RC

The increased number of supported counters will increase network traffic and processor load in OSS-RC. Extended support of Real time Performance monitoring (R-PMO) also increases the load and for large configurations it is required to deploy R-PMO on a separate server. For other parts of OSS-RC the capacity and performance is maintained in comparison to the base version of OSS RC.



11 (175)

3.2 Hardware No phased out HW in this release.

New HW in the BSC is TRA R6B and the possibility to expand the BYB 501 group switch with GEM-based devices using NNRP5.

No new BTS version is introduced.

3.2.1 BSC

Supported configurations:

• APZ 212 20 in combination with IOG 20C (Both BYB 202 and BYB 501).



• 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 33/ APZ 212 33C in combination with APG40.

Note: APG40 C/2 last time to buy 2006-06-30 and will be replaced by APG40 C/4.

• TRA R4, R5A and R5B in BYB 202.

• TRA R5A and R5B in BYB 501.

• TRA R6 in AXE 810 and in BYB501 (with NNRP5).

• TRA R6B in AXE 810 and in BYB501 (with NNRP5).

• RPD and RPG1 in BYB 202.

• RPP 202 and RPP 501 in BYB 202.

• RPP 501 in BYB 501 and AXE810.

• ETC4 in BYB 202.

• ETC5, ETC T1-H in BYB 501 and BYB 202.

• ET155-7 in BYB 501.

• ET155-1 in AXE 810 and in BYB501 (with NNRP5).



12 (175)

• ET4-1 in AXE 810 and in BYB501.

• RPG3 in AXE 810 and BYB501.

• RPG2 and RPG2-E in BYB501 (final order 2003-12-31).

• RPG2 in BYB202 , with TSM64C (final order 2003-12-31).

• BSC LAN switch for IP Connectivity in AXE 810 and BYB 501.

Note that in BSS R10, support for NNRP4 is introduced. This allows the upgrade of BYB501 group switch to GS890 (AXE810) group switch.

Notice that the BYB 202 cabinet is not supported or supported with limitations by the following new or enhanced R12 features:

• BSC IP Connectivity

• GPRS/EGPRS Mobile Logging

• Real-Time Performance Monitoring (R-PMO)

• Remote OMT over IP

See each feature description for more details about cabinet support.

The features using TCP/IP; BSC IP Connectivity, Real Time Event Data (used by R-PMO) and GPRS/EGPRS Mobile Logging can be run on a BYB 202 build set in combination with a BYB 501 for the RPPs. It is necessary to have all the RPPs in the BYB 501.

TFO requires TRA R6 or R6B and this is supported in AXE 810 and BYB 501 together with NNRP4 or NNRP5.

EPS, ROJ 204 50/1, is required in all RPP magazines running GB over IP (EPSB, ROJ 204 23/1, is not supported).



13 (175)

3.2.2 BTS

Below is a list of different RBSs and their support of new features with BTS impact. Only RBSs released at GA of R12 are listed. For information on later released RBS versions, see the release note for respective RBS release.

RBS 200 RBS2000 RBS2000 RBS2000 RBS2000 RBS2000 203 2101 2301 2101 2106 2308204 2102 2302 2102 2107 2309205 2103 2401 2202 2112 2109

2202 2206 SPU+ DXU-01 DXU-21 2207

SPU++ DXU-03 EDGE sTRU

SPE DXU-11 cTRU

BSS R12 Features

cTRU Adaptive Multi Rate (AMR) X X(1) X X X AMR Power Control X X(1) X X X AMR Radio Link timers X X(1) X X X Abis Triggered HR Allocation X(4) X X BSS R12 System Improvements X(6) X X X X X BSS R12 System Improvements, BTS

Faster Function Change Automatic restart after very long link breaks Improved LED handling Fault Filtering

X X

X X

X X

X X

X X

X X

X X

X X

Enhanced Measurement Reporting X(3) X(1)(3) X(3) X X Flexible Abis X(4) X X Full Rate AMR on 8 kbps Abis X(4) X X Incremental Redundancy in Uplink X(4)(5) X X Interference Rejection Combining X(4) X X Mixed Micro Configurations X X New Configurations 2x06 X(9) Operation Maintenance Terminal

Increased Transmission Speed Improved Bandwidth Usage Check IDB Impr. Desc.of define parameters

X(8) X(7) X(7)

X(8) X(7) X(7)

X

X(8) X(7) X(7)

X

X(8) X(7) X(7)

X

X(8) X(7) X(7)

RBS 2000 Synchronisation X(2)(7) X X Single Phase Access for EGPRS X(4) X X Remote OMT

Improved Bandwidth Usage Check IDB Impr. Desc.of define parameters

X(8) X(7) X(7)

X(8) X(7) X(7)

X(8) X(7) X(7)

X(8) X(7) X(7)

X(8) X(7) X(7)

Remote OMT over IP Improved Bandwidth Usage Check IDB Impr. Desc.of define parameters

X(8) X(7) X(7)

X(8) X(7) X(7)

X(8) X(7) X(7)

X(8) X(7) X(7)

X(8) X(7) X(7)



14 (175)

Speech Quality Supervision X X(1) X X X Tandem Free Operation X X(1) X X X Voice Group Call Service X X X X X

Table 4 RBS feature support

Note:

1. The feature is not supported on 2301 of versions before R6A.

2. DXU-11 is required.

3. BEP (MEAN_BEP & CV_BEP) and RxLev_VAL is not supported on the cTRU, RBS 2301, RBS 2302 and RBS 2401.

4. sTRU is required.

5. Support not guaranteed for sTRU KRC 131 139/01 revision R1G or earlier.

6. The new counter for Immediate Assignment messages discarded by BTS due to congestion on AGCH (includes Immediate Assignments both for CS and PS) is not supported on RBS 200.

7. BTS 12B is required.

8. BTS 12B is required for some parts, see feature description in chapter 5.

9. For 2206 some configurations require BTS 12B, see below.

3.2.2.1 New RBS configurations with BSS R12 SW support:

RBS 2000 12A:

RBS 2106/2206 has support for the following configurations: - 4 TRXs combined + 4 TRXs uncombined - 4 TRXs uncombined + 4 TRXs combined - 2 TRXs uncombined + 4 TRXs uncombined - 3 TRXs uncombined + 3 TRXs uncombined - 4 TRXs, with HCU and ASU + 8 TRXs, with HCU (800/900) - 8 TRXs, with HCU + 4 TRXs, with HCU and ASU (800/900) - 8 TRXs, with HCU + 4 TRXs combined (800/900) - 4 TRXs combined + 8 TRXs, with HCU (800/900) - 8 TRXs, with HCU + 2 TRXs combined (800/900) - 2 TRXs combined + 8 TRXs, with HCU (800/900) - 8 TRXs, with HCU (800/900) - 1x8 with 4-way receiver diversity (1800/1900) - 1x12 with 4-way receiver diversity (1800/1900) Note: With 4-way receiver diversity enabled only one TRX per dTRU is possible to use.



15 (175)

RBS 2106 has also support for the following configuration: - 3x4 with 4-way receiver diversity (1800/1900) Note: With 4-way receiver diversity enabled only one TRX per dTRU is possible to use.

RBS 2000 12B:

RBS 2206 ha support for the following two cabinet configuration: - 3x8 with 4-way receiver diversity. Note: With 4-way receiver diversity enabled only one TRX per dTRU is possible to use.

3.2.3 OSS

The following Sun Enterprise and Sun Fire servers planned to be used in OSS-RC R3:

• SFV240, SFV440, SFV890, SFE2900, SFE4900, SFE6900

• StorEdge 3310, 3510 disk systems.

• Workstation: Sun Blade 150

The following Sun Enterprise and Sun Fire servers/products are supported in OSS-RC R3 provided that the network load is lower or the same as in R12

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

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

• Sun StorEdge D1000/A1000 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

For detailed information see Sales Configuration Guide for OSS-RC R3.

3.3 Implementation The following upgrade paths to BSS R12 are supported.

Notice that the upgrade normally must be performed in the numbered order.

For BSS R11 to BSS R12

1. OSS-RC 2.1 (or 2.2) to OSS-RC 3

2. BSC R11 to BSC R12

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



16 (175)

3. BTS 11A/11B/11C to 12A/12B

RBS 200 10A has no upgrade path.

BTS can be upgraded either before or after the BSC.

If RBS 2000 Synchronization is used the slaves must be upgraded before the master.

BTS 12B is a post GA release.

Note:

MSC in Pool: Before activating new features in BSS that have an impact on the A-interface it is recommended to upgrade all MSCs connected to the same BSC (to achieve same level of functional support in all MSCs within the Pool). In R12 the following features introduce changes to the A-interface (and will be supported by Ericsson MSC R12):

• Handover with Usage of Service Indicator

• Smooth GSM to WCDMA unloading

APG40: HW baseline for the upgrade must be APG40C/2 R3B or later for BSC equipped with APG40. A HW update kit for R2 versions will be available, thus making it possible to upgrade also on those, see ref [4].

For BSS R11.1 to BSS R12

1. OSS-RC 2.1 (or 2.2) to OSS-RC 3

2. BSC R11.1 to BSC R12

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

3. BTS 11A/11B/11C to 12A/12B

RBS 200 10A has no upgrade path.

BTS can be upgraded either before or after the BSC.

If RBS 2000 Synchronization is used the slaves must be upgraded before the master.

BTS 12B is a post GA release.

Note

MSC in Pool and APG40, see above.



17 (175)

SGSN in Pool: The BSC and first SGSN that establish Gb contact after BSC restart will set the support level for optional Gb features and only SGSNs with the same level of support or higher will be possible to include in the pool. During the upgrade it is recommended to have the same level of support for optional Gb features in all SGSNs. If the BSC has the lowest level of support for optional Gb features it will automatically be the limiting factor. For more detailed information about the handling of optional Gb features see User Description: GB over IP and SGSN in Pool, ref [5].

BSS R12 is compatible with the following non-BSS nodes:

• MSC R11 (CN R4)

• MSC R12 (CN R5)

• SGSN 5.5, 6.0 and 7.0

• CGSN 3.0 and 4.0

• SMPC 7.0 and 8.0

3.4 Interface All BSS interfaces have been updated to comply with 3GPP/GSM Release 6/June 2004. See Statement of Compliance (SoC) documents for more information ref [1].

3.5 Memory

3.5.1 General

The APZ memory limits are according to the table below. The maximum values are specified and possible reduction steps within parenthesis.

Upgrade to BSC R12 will be possible on APZ 212 25 without any expected inconveniences for the operator, however, SAE settings must follow the recommendations in document �Size Alteration Events in BSC/TRC, 2/155 18-AXE 105 07 Uen� before and after the upgrade.

APZ type PS DS RS

212 25 64 MW 16 (fixed) 252 MW 16 (fixed) 2 MW 32 (fixed)

212 20 64 MW 16 (fixed) 380 MW 16 (64 MW steps) 2 MW 32 (fixed)

212 20 64 MW 16 (fixed) 1536 MW 16 (256 MW steps)

2 MW 32 (fixed)



18 (175)

212 30 96 MW 16 (fixed) 4 GW 16 (512 MW steps) * 32 MW 16 (fixed)

212 33C /212 33

96 MW 16 (fixed) 4 GW 16 (512 MW steps) * 32 MW 16 (fixed)

Table 5 APZ 212 nn memory limits

* 512 MW 16 steps are valid for DRAM based boards, the only type used in the BSC

3.5.2 Stand-alone TRC Node

APZ 212 25

The processor is always equipped with 64 MW16 PS and 252 MW16 DS which is enough to handle the largest TRC.

APZ 212 20

The processor is always equipped with 64 MW16 PS, which is enough to handle the largest TRC.

The minimum memory requirement for DS when using fixed SAE settings is 252MW16.

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.

APZ 212 33C/ APZ 212 33

The processor is always equipped 96 MW16 PS and minimum of 512 MW 16 DS, which is enough to handle the largest TRC.

3.5.3 Stand-alone BSC or Combined BSC/TRC Node

APZ 212 25

The processor is always equipped with 64 MW16 PS and 252 MW16 DS which is enough to handle a BSC/TRC equipped with up to 1020 TRX and maximum 512 cells.

APZ 212 20

The processor is always equipped with 64 MW16 PS. The memory requiremen for DS when using fixed SAE settings is 316MW 316MW16/508MW16 (the memory size differs depending on if 64 MW or 256 MW memory boards are used).

This is enough to handle a BSC/TRC equipped with up to 1020 TRX and maximum 512 cells.



19 (175)

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 BSC/TRC.

APZ 212 33C/ APZ 212 33

The processor is always equipped 96 MW16 PS and minimum of 512 MW 16 DS, which is enough to handle the largest BSC/TRC. The memory requirement for DS when using fixed SAE settings is 1024 MW 16.

3.6 Dimensioning / System Limits

3.6.1 Gb Interface/ Number of SGSNs

The SGSN in Pool Support in BSC feature makes it possible to connect the BSC/TRC to between 1 and 16 SGSNs.

3.6.2 PCU Dimensioning

Dimensioning guidelines are updated for:

• GB over IP (the RPP will get increased GSL capacity since no GPH devices are needed for Gb)

• Reduced processor capacity for high traffic scenarios (PS traffic per cell).

3.6.3 TRH Dimensioning

Minor change for RPG1/2 and 3 but around 20% reduced capacity for RPD, when the processor is limiting, compared to R11.

3.7 Overload Performance

3.7.1 CP Overload Performance

No change compared to R11.

3.7.2 RPP Overload Performance

This is improved with the new feature PCU Load Control, see chapter 5.40 for detailed information.



20 (175)

3.7.3 TRH Overloaded Performance

No change compared to R11.

3.8 Operations See each specific feature chapter below for descriptions of impact for the features.

For general impact on OSS-RC R3, see ref [9].

3.8.1 APG40

See ref [4] for changes to the APG40.

Note:

The new APG OS detects Ethernet link break within 10 seconds after that the physical link from APG to first network element is broken, see chapter 4.1.2.1 in ref [4] for details. An upgrade of BSC LAN switch SW is detected as a link break causing fail over. This has no impact with the current upgrade order since the LAN switch is upgraded before APG 40.

APG 40 backup of both nodes with one single command described in chapter 4.1.2.3 in ref [4] is not included in BSS R12 GA release.

In chapter 4.1.2.6 in ref [4] it is stated that default setting for new nodes from factory will be that only SSH/SFTP is allowed, this is not included in BSS R12 GA release.

3.9 Other Features See each specific feature for a detailed description.

3.10 Other Network Elements Feature Dependencies to other Network elements are shown in table below, see each specific feature for a detailed description of dependencies.

BSS R12 Features MSC MGW SGSN UTRAN MS Other

Admission Control for Push To Talk

Rel 99 QoS, Secondary PDP context

Rel 99 QoS, Secondary PDP context, �EIT settings for QoS�

IPMM Servers 2.0



21 (175)

Active Queue Management

5.5 R97

Combined Cell re-selection triggering GSM to WCDMA

Multi RAT R5

Dual Transfer Mode R5

Enhanced Measurement Reporting

R99

Five Down link Timeslots

R5 Multislot class 30-33, 40-45

Gb over IP R6

GSM-WCDMA BA List Recording

Multi RAT

RNO (GSM-WCDMA NCS)

Multi RAT

Handover with Usage of Service Indicator

R12 Multi RAT

Incremental Redundancy in Uplink

R99

SGSN in Pool R6

Single Phase Access for EGPRS

R99 (EGPRS)

Smooth GSM to WCDMA unloading

R12 P3 Multi RAT

Tandem Free Operation

R4.1 NNRP5

Traffic Level Measurement Data

GMPC 9.01

Voice Group Call Services

Anchor R4

Table 6 Inter-node dependencies for BSS R12 Features

1 The support for this feature might be added in GMPC version 8.0, but it is currently not decided.



22 (175)

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

BSS R12 Feature Major Impact

Minor Impact

Feature Number FAJ

New (N) Enhanced (E) Basic (B) Optional (O)

Abis Triggered HR Allocation X 121 846 N/O

Active Queue Management X 121 822 N/O

Adaptive Configuration of SDCCHs X 121 381 E/O

Adaptive Multi Rate X 121 055 E/O

Admission Control for Push to Talk X 121 823 N/O

AMR Power Control X 121 353 E/O

AMR Radio Link Timers X 121 826 N/O

Application Aware Timeslot Allocation X 121 824 N/O

BSC IP Connectivity X 121 665 E/B

BSS R12 GPRS/EGPRS Improvements X 121 828 N/B

BSS R12 System Improvements X 121 848 N/B

Channel Repacking X 121 843 N/O

Combined Cell re-selection triggering GSM to WCDMA X 121 933 N/O

Dual Transfer Mode X 121 611 E/O

Dynamic BTS Power Control X 122 910 E/O

Dynamic MS Power Control X 122 260 E/O

Dynamic Overlaid/Underlaid Subcell X 122 430 E/O

Enhanced Measurement Reporting X 121 821 N/O



23 (175)

Five Downlink Timeslots X 121 814 N/O

Flexible Abis X 122 450 E/O

Flexible Channel Allocation X 122 117 E/B

Flexible Priority Handling of Packet Data Channels X 121 060 E/O

Full Rate AMR on 8 kbps Abis X 121 827 N/O

GB over IP X 121 786 N/O

GPRS/EGPRS Load Optimisation X 121 825 N/O

GPRS/EGPRS Mobile Logging X 121 587 E/O

GSM-UMTS Cell Reselection and Handover X 121 57 E/O

GSM-WCDMA Active BA List Recording X 121 815 N/O

Handover with Usage of Service Indicator X 121 835 N/O

Immediate Assignment on TCH X 122 913 E/B

Incremental Redundancy in Uplink X 121 816 N/O

Interference Rejection Combining X 122 083 E/O

Mixed Micro Configurations X -

Multi Band Cell X 122 085 E/O

Multi-Layered HCS X 122 573 E/O

Operation Maintenance Terminal X 122 072 E/O

PCU Load Control X 121 819 N/B

RBS 2000 Synchronization X 122 854 E/O

Real Time Event Data X 121 50 E/O

Remote OMT X 122 345 E/O

Remote OMT over IP X 121 618 E/O

Self Configuring Transcoder Pools X 121 356 E/O

SGSN in Pool Support in BSC X 121 787 N/O

Single Phase Access for EGPRS X 121 820 N/O



24 (175)

Smooth GSM to WCDMA Unloading X 121 840 N/O

Speech Quality Supervision X 122 583 E/O

Support for 1024 Cells in BSC X 121 817 N/O

Support for 8000 EGPRS Time Slots X 121 818 N/B

Support of AXE 810 � APT1.5 X 121 23 E/B

Tandem Free Operation X 121 25 N/O

Tight BCCH Frequency Reuse X 121 813 N/O

Traffic Level Measurement Data X 121 844 N/O

Voice Group Call Services X LA N/O

Table 7 Summary of BSS impacting features

4.2 OSS-RC Features

BSS R12 Feature Major Impact

Minor Impact

Feature Number FAJ

New (N) Enhanced (E) Basic (B) Optional (O)

BSS R12 System Improvements, OSS Cellular Network Administration (CNA) BTS Configuration Management (BSM)

X X

122 405 122 476

E/B E/B

Inter System Consistency Reports Cellular Network Administration (CNA)

X 122 405 N/B

GPRS/EGPRS Mobile Logging Client (GMLC) X 121 603 E/O

Predefined Configuration Profiles X 121 841 N/O

Radio Network Optimization (RNO) GSM�WCDMA Neighboring Cell Support (GWNCS) Neighboring Cell Support (NCS Frequency Allocation Support (FAS) Frequency Optimization eXpert (FOX) Neighboring Cell Optimization eXpert (NOX) Measurement Result Recording (MRR) Synchronized Radio Network Optimization eXpert (SYROX)

X X X X X X X

121 886 122 477 122 474 122 629 122 630 122 522 121 612

N/O E/O E/O E/O E/O E/O E/O

Real Time Performance Monitoring (R-PMO) X 121 46 E/O



25 (175)

Table 8 Summary of OSS-RC impacting features

5 Impacting BSS Features In subchapters each feature is described separately.

The feature impact and dependency table is intended as quick overview of the feature. If an impact area or dependencies to other than nodes are marked with �X� in the table then there is specific information to follow for this subject.

5.1 Abis Triggered HR Allocation

Implementation Operations Characteristics Interface CompatibilityImpacts

- X X - X

BSC BTS OSS SMPC Other Network elements

Other features Dependencies

X - X - - X

Table 9 Feature impact and dependency quick chart

5.1.1 Description

To reduce the need of Abis bandwidth near Abis congestion the following is introduced:

Dynamic HR Allocation from Abis

The design base feature �Dynamic Halfrate Allocation� allocates AMR HR and HR channels when there is a lack of AMR FR and FR channels in a cell. In R12 the same functionality will be triggered also if there is a shortage of 16 kbps paths in the non-64RES Abis pool. (Note however that this feature is not dependant on �Dynamic Halfrate Allocation�).

Dynamic FR/HR Mode Adaptation from Abis

The design base features �HR Packing� and �Dynamic FR/HR Mode Adaptation� pack AMR HR and HR channels respectively move AMR FR and FR channels to AMR HR and HR channels when there is a lack AMR FR and FR channels in a cell. In R12 the same functionality will be triggered also if there is a shortage of 16 kbps paths in the non-64RES Abis pool. (Note however that this feature is not dependant on �HR Packing� or �Dynamic FR/HR Mode Adaptation�).



26 (175)

5.1.2 Operations

The command RXMOI is extended with threshold parameter DHRAABISTHR for when to start allocating half rate channels due to Abis.

The command RXMOI is extended with threshold parameter DFRMAABISTHR for when to start packing of HR and AMR HR channels and for when to start move from FR to HR channels, including AMR, due to Abis.

The command RXMOC is extended with the same parameters as RXMOI.

The command RXMSC is extended with the same parameters as RXMOI.

The command RXMOP produces a printout of the new parameters mentioned above.

New command RLDAC is introduced to enable/disable each of the features on cell level.

New command RLDAP is introduced to print the parameters set in RLDAC.

Commands RLDAC and RLDAP uses new parameter ATHABIS, which activates and deactivates Abis triggered HR allocation in a cell.

The following cell counters are introduced:

• one cell counter for number of successful intra cell handovers due to FR to HR channel rate change due to Abis congestion made by AMR capable mobiles

• one cell counter for number of successful intra cell handovers due to FR to HR channel rate change due to Abis congestion made by non-AMR capable mobiles.

The Assignment Command event is updated with the new reasons (Traffic load and Abis load) for the traffic cases �Intra Cell Handover due to half rate packing� and �Intra Cell Handover due to channel rate change�.

5.1.3 Characteristics

This feature will reduce the level of congestion from lack of Abis resources. This will enable an even slimmer dimensioning of Abis with a preserved congestion level or conversely, the level of congestion can be reduced without adding Abis resources.

5.1.4 Compatibility

RBSs with sTRUs, dTRU, dTRUe or RRU is required.



27 (175)

5.1.5 Other Features

The features FAJ 122 450 Flexible Abis and FAJ 122 315 Half Rate Channels are required. The features FAJ 121 055 Adaptive Multi Rate (AMR) and FAJ 121 358 AMR Half Rate is required in order to use it together with AMR.

5.2 Active Queue Management (AQM)


- X X X -



X - X - X X


5.2.1 Description

Active Queue Management (AQM) is a queue management feature for the downlink. For applications using TCP/IP as transmission (e.g. FTP, web browsing, email), it is important with a rapid feedback of the radio link data rate to the TCP/IP protocol. Feedback of the radio link data rate is reported to TCP/IP by discarding IP-packets. In this way the TCP/IP protocol will faster adjust its send rate according to the radio link capacity and TCP slow-starts are avoided.

If the feature �QoS and Scheduling� in BSC is active (R97 QoS and/or R99 QoS), the queue management feature is applied to Interactive class and Background class data. The queue management feature is not applied to signalling messages, SMS, LLC acknowledged mode data, EIT data or Streaming class data when QoS is active. For SMS, signalling messages, LLC acknowledged mode data, EIT data and Streaming class data a maximum buffer is set and when the buffer is overflowed packets are discarded starting from front of the buffer.

If the feature �QoS and Scheduling� in BSC is passive, the queue management feature is applied to all payload data but not to signalling messages, SMS or LLC acknowledged mode data. For LLC acknowledged mode data and data not handled by AQM a maximum buffer is set and when the buffer is overflowed packets are discarded starting from front of the buffer.



28 (175)

The queue management feature starts to discard data in the buffers in the BSC at certain thresholds of buffer fullness. Data is discarded starting from front of the buffers. The feature also attempts to identify complete IP-packets, such that one complete IP-packet is discarded and not parts of one or two IP-packets. The thresholds of when to start discarding data is set to lower than the actual buffer size to get a smooth slow down in the data rate from the server.

The BSSGP Flow Control function is made passive for the MSs using this feature. The rate of the data flow is not regulated towards the BSC, and all buffering is made in the BSC.

5.2.2 Operations

There are five new BSC exchange properties for this feature, which can be set by operator command:

• AQMSUPPORT

• AQMMINBUFF

• AQMRTTCONST

• AQMMINIPSIZE

• AQMMAXIPSIZE

The exchange parameter AQMSUPPORT switch on/off the AQM feature for data of R97 and R99 QoS per BSC.

The operator shall be able to set the value of AQMMINBUFF per BSC. The AQMMINBUFF exchange property gives the value of MinTmin which ensures that at least a few IP-packets are buffered at very low leak rate. The default value is 104 Kbytes and the value range is 1 to 200 Kbytes.

The end to end roundtrip time can be divided in to one constant part and one varying part. The end to end roundtrip time is then used for calculation of the estimated pipe capacity. The RTTconst is the constant part of the roundtrip time. The constant part includes delays in server, core network, BSC, MS and laptop as well as transmission delays on the interface such as Gn, Gb and Abis. The operator shall be able to set the value of AQMRTTCONST per BSC. The default value is 850 ms and the value range is 100 to 4000 ms in steps of 10ms.

It shall also be possible for the operator to set the upper limit, AQMMAXIPSIZE, and lower limit, AQMMINIPSIZE, per BSC. The limits represent the total size of a number of LLC PDU�s constituting the largest and the smallest IP-Packet sizes respectively. The default values shall be AQMMAXIPSIZE = 1700 bytes and AQMMINIPSIZE = 300 bytes and the value ranges 100 to 2000 bytes.



29 (175)


The total time for downloading data is reduced with up to 25% (GPRS and EGPRS) when jumping between web pages before they are completely downloaded (or downloading from multiple sources).

The end-to-end throughput for downlink transfers will increase up to 20% (GPRS) for applications using TCP/IP. Large downloads and sessions with low radio link bit rate will experience the largest improvement.

5.2.4 Interface

Gb Interface

When discarding data due to the AQM feature, it is beneficial if the BSC can report the amount of discarded data per PFC and per MS to the SGSN. The SGSN may then compensate the charging records accordingly, such that discarded data is not charged for. In order to be able to report discarded data per PFC the Flow Control per PFC feature needs to be negotiated between the BSC and the SGSN. The negation procedure is supported both for the GB frame relay solution and the GB IP solution.

When the optional feature GPRSAQM is available in the BSC and the exchange property AQMSUPPORT is not equal to 0, the BSC negotiate the Flow Control per PFC feature with the SGSN. The BSC shall indicate support for �PFC Flow Control� in the feature bitmap sent in the signalling BVC-reset procedure.

If a SGSN pool is used all SGSNs must support the Flow Control per PFC feature in order for AQM to use it.

The 3GPP TS 48.018 messages FLOW-CONTROL-PFC and FLOW-CONTROL-PFC-ACK are not used by the BSC. The BSC only reports Flow Control per MS and per BVC for MSs subject to AQM, even though the Flow Control per PFC is negotiated.

When the SGSN also supports the PFC Flow Control the BSC indicates for which PFC the LLC data has been discarded when sending the 3GPP TS 48.018 message LLC-DISCARDED to the SGSN. This is done by setting the current PFI for discarded LLC-PDUs in the LLC-DISCARDED message. The LLC-DISCARDED message is sent every time LLC data is discarded.

5.2.5 Other Network Elements

In order to apply AQM per traffic class SGSN 5.5, that provides support for different traffic classes, or later is needed together with MS supporting R97 or R99 QoS.



30 (175)

To be able to compensate the CDRs in SGSN for data discarded by AQM it is mandatory that mobile provides support for QoS R'99 as specified in 3GPPP TS 23.107 and PFC as specified in 3GPP TS 24.008 and that the SGSN must provide support for QoS R'99 as specified in 3GPPP TS 23.107, Packet Flow Management procedures and Flow Control for PFC as specified in 3GPP TS 48.018.

However none of this above is a pre-requisite for the usage of AQM.


See description for dependencies towards the feature FAJ 121 32, Quality of Service (QoS) and Scheduling.

Two new monitors in R-PMO are introduced:

• Total IP data received by AQM

• Total IP data delivered by AQM

5.3 Adaptive Configuration of SDCCHs


X X - - -



X - - - - -


5.3.1 Description

Adaptive configuration of logical channels will dynamically dimension the cell with more (or less) SDCCH/8s on demand. This prevents SDCCH congestion to occur.

In R12 this feature is enhanced to also allow adaptive configuration of SDCCH in overlaid subcells. At allocation of an SDCCH subchannel the total number of idle SDCCH subchannels in the cell (overlaid and underlaid) will be compared with the SDCCH level parameter. If number of idle SDCCH subchannels is as low as the SDCCH level the system selects an active channel group with less SDCCHs than the system allows. The evaluation always starts with channel group 0 (if not configured to be excluded).



31 (175)

5.3.2 Implementation

This feature is activated on cell level and by default are all channel groups included. If this is not a wanted configuration it is possible to exclude channel groups in which no adaptive SDCCHs will be added.

5.3.3 Operations

Command RLACC has been updated. The limitation to only allow SDCCH/8 in underlaid subcell is removed. This command is also used to include or exclude channel groups available for adaptive configuration of SDCCH.

5.4 Adaptive Multi Rate (AMR)


- X - - X



X - - - - -


5.4.1 Description

A new pre-defined full rate codec set has been defined for AMR. This codec set contain the following codec modes: 12.2, 7.4, 5.9 and 4.75 kbps.

This codec set, together with the pre-defined half rate codec set 2, containing the modes 7.4, 5.9 and 4.75, satisifes the AMR FR and AMR HR interoperation in an optimal way when TFO is introduced.

The new AMR FR codec set is also used by the feature Full Rate AMR on 8 kbps Abis.

The AMR algorithm has been updated to be compliant with 3GPP TS 26.073 CR 19 (Correction of AMR DTX functionality). The correction is included in the TRA software for TRA R6 and R6B in the R12 release.



32 (175)

5.4.2 Operations

New full rate codec sets possible to use is described in the Application Information ROS Operation And Maintenance Exchange Property, Changeable Exchange Adaptation.

5.4.3 Compatibility

AMR is supported on all RBS 2000 except for RBS 2301 < R6A.

TRA R6 and R6B support the 3GPP correction of AMR DTX functionality. TRA R5B will be handled in ordinary maintenance procedures.

5.5 Admission Control for Push to Talk


- X - - -



X - X - - X


5.5.1 Description

BSS R12 introduces Admission control for EIT in order to guarantee that Quality�of-service (QoS) requirements are fulfilled for as many users as possible. Admission Control checks that the resources reserved for a user is enough to fulfill the QoS agreement. Also, the admittance of a new user shall not affect already admitted users so that their QoS agreement is broken. Admission Control for EIT works on cell level and considers both uplink and downlink resources. Admission control is applied at all channel reservations/re-reservations for TBFs that are identified as EIT. Admission Control is applied at cell re-selection.

The basic Admission Control algorithm follows the rule:

• A new user shall only be admitted if requested GBR and Transfer Delay can be achieved in both UL and DL.

• A new user shall only be admitted if existing EIT users still achieve their GBR and Transfer Delay after admitting the new user.



33 (175)

If the admission control algorithm has detected that a new user cannot be admitted, action has to be taken. The action is defined by a new parameter, EITQOSPRIO, which defines the actions when an EIT TBF will not get the necessary resources. The new parameter defines the following actions:

• Reject

• Re-negotiate with SGSN (Downgrade to interactive)

• Admit (make temporary BSC internal downgrade to interactive with QoS priority THP1)

Since EIT is based on traffic class streaming, there is a risk that interactive and background users will get poor performance if the percentage of EIT users in a cell is high. This since streaming has higher priority than interactive and background. Since the current Channel Reservation algorithm tries to spread the reservations over the existing PDCHs before multiplexing begins, there is a risk that there will be EIT TBF on most PDCHs, even at moderate load.

To reduce this risk a new configurable parameter EITEXCLUDED is introduced, defining the number of PDCHs that are excluded from EIT usage.


EIT aims to keep TBFs up and running as long as possible by the use of Delayed release in DL or Extended UL mode, this in order to avoid delays for TBF setup and release during EIT sessions. This will result in that a large amount of EIT TBFs will be inactive in either direction for a large part of a session. This has to be taken into consideration when configuring the parameters below.

5.5.3 Operations

Admission Control is controlled by settings of parameters limiting EIT usage per PDCH. Since the choice of DL CS for EIT is limited by parameter EITHIGHCS which has an upper limit at CS2, there will be no difference between BPDCH and GPDCH.

The following new BSC exchange properties are introduced:

EITADMCTRL Turn on/off admission control for EIT per BSC

EITGMAXUSEDL Maximum channel usage for EIT TBFs DL for B- and G-TBF mode

EITEMAXUSEDL Maximum channel usage for EIT TBFs DL for E-TBF mode

EITGMAXUSEUL Maximum channel usage for EIT TBFs UL for B- and G-TBF mode

EITEMAXUSEUL Maximum channel usage for EIT TBFs UL for E-TBF mode



34 (175)

EITQOSPRIO Parameter defining actions to take when EIT reservations fails due to Admission Control

STRFACTOR Weight factor for streaming TBFs

STRFORGET Filter weight for bandwidth reports

The following command RLGQC and printout �Cell GPRS Quality of Service Data� is updated with the following parameter:

EITEXCLUDED Number of PDCHs not allowed for EIT TBFs

The parameters defining the maximum channel usage of EIT per TBF mode and direction are defined as how much of the defined maximum channel capacity can be used by EIT, if only EIT TBFs are reserved on the PDCHs. If ordinary streaming TBFs (with higher QoS priority) are reserved on the same PDCHs (ESPs) as used by the EIT TBF, EIT can only use the remaining PDCH capacity up to the maximum EIT usage. The PDCH capacity not used by EIT (as in silent periods) or by ordinary streaming may be used for lower QoS priority traffic (i.e. Background and Interactive).

The STS counters are meant to give the basic support needed to observe the behaviour of Admission Control. The following cell level counters are introduced in STS object type CELLEIT2:

• Total number of Admission Control requests for EIT

• Total number of times EIT service was denied due to Admission Control

• This counter is incremented each time the parameter EITQOSPRIO is used by the Admission Control.


Requires that the optional feature FAJ 121 591 Instant Talk Performance is active.

The R-PMO feature includes a new monitor for the following observable entities that are handled per cell:

1. Number of requests made to Admission Control

2. Number of times Admission Control denied an EIT user access

3. Requested transfer delay

4. Achieved transfer delay

5. BLER DL for EIT TBFs

6. BLER UL for EIT TBFs



35 (175)

The monitor is based on the new R-PMO Event:

• Admission Control with event data

EIT TBF admitted or EIT TBF not admitted indicating the result of Admission control (successful or unseccesful) In case unsuccessful the action parameter EITGPRSPRIO is used and the cause value is used to specify the reason for reject.

And the following existing R_PMO Event:

• TBF Endswith event data:

BLER DL for EIT TBFs

BLER UL for EIT TBFs

• Data Activity Ends with event data:

Requested transfer delay

Achieved transfer delay (average delay over TBF lifetime)

5.6 AMR Power Control


- X - - X



X - X - - X


5.6.1 Description

Signal strength and quality target values for circuit switched Power Control is possible to set separately for AMR HR.

New default values when new cells are created for the following parameters:, QDESDLAFR, SSDESDLAFR, QDESULAFR and SSDESULAFR.



36 (175)

5.6.2 Operations

The command, RLAPC, Radio Control Cell, AMR Power Control Cell Data, the printout AMR Power Control Cell Data and the application Information RCS, RCQS Cell Data, Changeable Exchange Adaptation is updated to reflect the changes.

5.6.3 Compatibility



The features FAJ 122 260 Dynamic MS Power Control and/or FAJ 122 910 Dynamic BTS Power Control are required for power regulation on the up and downlink respectively.

The feature FAJ 121 055 Adaptive Multi Rate (AMR) is required in order to use the AMR full rate codec.

The feature FAJ 121 358 AMR Half Rate is required in order to use the AMR half rate codec.

5.7 AMR Radio Link Timers


- X - - X



X - X - - -


5.7.1 Description

Separate values for the downlink and uplink radio link timeout timers for the Full Rate AMR and Half Rate AMR speech codecs are provided.



37 (175)

Since Full Rate AMR is more robust than the SACCH signalling a higher value for the radio link timeout timer is needed otherwise there is a high chance that a call with good speech quality is disconnected due to failing signalling. If the timer value is increased for all speech codecs the consequence would be that for calls using less robust codecs, the channels would be held onto long after the call is terminated by the callers due to too poor speech quality, which would decrease channel utilization.

In BSS R11 the existing parameters RLINKT and RLINKUP are used for both non-AMR and AMR connections to decide when to disconnect a call due to a failure in decoding the SACCH messages. In order to prolong the lifetime for an AMR connection, when a failure in decoding the SACCH messages occurs, four new AMR specific radio link timeout parameters are introduced for AMR/FR and AMR/HR:

RLINKTAFR - AMR/FR on DL

RLINKTAHR - AMR/HR on DL

RLINKUPAFR - AMR/FR on UL

RLINKUPAHR - AMR/HR on UL

5.7.2 Operations

The existing parameter RLINKT is set (as before) by command RLSSC and sent out to all mobiles on the BCCH in SI3 and also to a specific MS on the SACCH in SI6.

The new parameters, RLINKTAFR - for AMR FR and RLINKTAHR - for AMR HR, will be introduced in command RLSSC and supported by OSS. When SI6 is to be sent out, the chosen speech version will be checked and if it indicates AMR, one of the new parameters will be sent out on SI6 instead of RLINKT. At change of channel or channel mode change, the radio link timeout value has to be checked and if needed, the new value will be sent on the SACCH. If the operator decides to change the value of either the parameter RLINKTAFR or RLINKTAHR, it will not be distributed to an already active MS in the cell.

The existing parameter RLINKUP is set (as before) by command RLLDC and is used in the RP-unit RQRCQSR.

Two new parameters, RLINKUPAFR - for AMR FR and RLINKUPAHR for AMR HR, will be introduced in command RLLDC and supported by OSS. These parameters will be distributed to the function �Supervision of Radio Connections� (RQRCQSR unit), in the same way as parameter RLINKUP. RQRCQSR unit will check the channel rate and channel speech version to decide which parameter to use. When CHANNEL MODE CHANGE occurs, the new channel mode data is received in �Update of RCQS Data� function and the new channel mode parameters are stored in RQRCQSR.



38 (175)

Command RLSSC and PrintOut �Cell System Information SACCH and BCCH Data� will be changed to handle the new parameters RLINKTAFR and RLINKTAHR.

Command RLLDC and PrintOut �Cell Locating Disconnect Data� will be updated to handle the new parameters RLINKUPAFR and RLINKUPAHR.

5.7.3 Compatibility


5.8 Application Aware Timeslot Allocation


- X - - -



X - X - - X


5.8.1 Description

This feature improves the dynamic balancing of downlink and uplink timeslots allocated to an (E)GPRS terminal depending on the amount of buffered data in up- and downlink. This improves the performance of applications where there are streams of uplink data and downlink data in parallel.

Depending on the MS multislot class and how long the MS stays in the Neutral UL/DL state the PDCH saving can be up to 20-25%.

The feature is working for PS traffic of QoS Background and Interactive (Streaming is not affected).

A new UL/DL state, Neutral, is introduced which:

a. Maximizes the total number of timeslots reserved and

b. Minimizes the difference in number of reserved UL timeslots and number of reserved DL timeslots. This difference shall be as small as possible.

c. If there is a difference in number of timeslots that can be reserved for UL and DL then DL shall be prioritised.



39 (175)

The UL/DL State may change on the following occasions:

• As a result of adding an opposite TBF

• When an opposite TBF is removed (opposite data buffer level should be set to �Empty�)

• When a data buffer level report is received.

The changing of UL/DL state is shown in Figure 1 and Table 14 below.

UL Biased

DL Biased

Neutral

EDA

EDA

5 6

2

1

4

3

Initial TBF set up

Figure 1 UL/DL state transition

Nr Current UL/DL State

Next UL/DL State

Transition Criteria

1 Neutral UL Biased Large UL and small, empty or medium DL

2 UL Biased Neutral Small or empty UL and medium DL

or

Large UL and large DL

3 Neutral DL Biased Large DL and small, empty or medium UL

4 DL Biased Neutral Small or empty DL and medium UL

or

Large UL and large DL

5 UL Biased DL Biased Small or empty UL and large DL

6 DL Biased UL Biased Small or empty DL and large UL

Table 17 UL/DL state transition criteria



40 (175)

5.8.2 Operations

There is one new BSC Exchange Property for this feature:

• GPRSNEUTRALACT to switch the neutral state for dynamic UL/DL handling on and off.


The feature Dynamic UL/DL Handling must be active in the system.

The feature FAJ 121 606 Extended Dynamic Allocation (EDA) that was introduced in BSS R11 must be used when the number of TS in uplink is greater than number of TS in downlink.

5.9 BSC IP Connectivity


X X - - X



X - X - X X


5.9.1 Description

The purpose of the BSC IP-connectivity feature as such is to consolidate all TCP/IP communication activities within the BSS. The IP connectivity feature was introduced in R11 providing the BSC with an IP infrastructure, the BSC local area network (LAN).

The following enhancements are included in R12:

• IP security enhancements

• O&M improvements BSC LAN

Default use of encryption for IP transport using SSH2 where it is applicable, support for logging of IP-based communication as well as password replacement at first login are examples of IP security enhancements.



41 (175)

BSC documentation will be updated including a node hardening guideline and an IP address management description.

Remote BSC LAN configuration and software upgrade of the BSC LAN switches will be supported by OSS.


Enhanced IP security requires support in the OMC environment for SSH2 as well as Syslog and NTP servers.

The IP connectivity feature put requirement on Ethernet bandwidth utilization IP addressing, and support for IP traffic prioritization if needed.

5.9.3 Operations

There will be changes on existing configuration parameters.

OSS should be used for BSC LAN switch configuration and supervision.

5.9.4 Compatibility

BYB501 or later will be supported. No support for a BYB202.


The IP connectivity feature supports site integration using static routes and VLAN for traffic separation.


The feature �BSC IP Connectivity� is a prerequisite to the features:

• GPRS/EGPRS Mobile Logging

• Real Time Performance Monitoring (R-PMO)

• GB over IP / SGSN in Pool

The applications listed above reside in the GPH/PCU. It is also a recommendation to install the BSC LAN switches for other reasons than giving IP connectivity to these applications. The BSC LAN switches also provide perimeter protection to the BSC. IP-hosts like APG40, IOG20 or STOC are, if the IP connectivity feature is installed, controlled by the BSC LAN switches using access control lists and separate VLANs. Denial-of-service protection is also part of the implementation.



42 (175)

5.10 BSS R12 GPRS/EGPRS Improvements


- X - - -



X - X - - -


5.10.1 Description

Procedure to change TBF Mode between GPRS/EGPRS

In the earlier releases of GPRS there is no procedure to change the TBF mode for an ongoing TBF, the specifications does not either support any procedures. BSS R12 provides a solution to change a TBF mode by releasing all TBFs connected to an MS and set up new ones using new TBF mode. Release of uplink TBF and downlink TBF is done in controlled manner and coordinated in time.

Change of TBF mode may be triggered by:

• Change of QoS to traffic class streaming is requested but only possible by changing TBF mode

• The requested GBR for a streaming TBF is only possible to reach by changing TBF mode

• Higher bandwidth for TBFs of QoS traffic classes Interactive or Background is only possible to reach by changing TBF mode

Faster TBF setup

In the current implementation Early Setup of Downlink TBF (ESU) is triggered when the Countdown Value (CV) reaches 0. In BSS R12 ESU is triggered as soon as the MS initiates the countdown procedure.

TBFLIMIT

By allocating new PDCHs only when the number of TBFs on existing PDCHs exceeds the operator set limit, new PDCHs allocated in vain is avoided. The granularity of the configuration parameter is improved making it possible for the operator to have more exact control of the TBF sharing factor.

PILTIMER



43 (175)

When on-demand or semi-dedicated PDCHs no longer carry any traffic, the PIL timer is started in order to delay the release of the PDCH in case any new traffic will arrive. Three changes are introduced in BSS R12:

• The default value for the PIL timer is to be changed to 10 seconds. The recommended value was changed to 10 seconds already in R11.

• In case TBF is setup just for signalling the PILTIMER shall not be restarted.

• The timer is no longer restarted for idle PDCHs every time an existing TBF on some of the PDCHs available (PSET) is upgraded with more timeslots.

PS channel allocation/reservation

The parameter MBCRAC is used by the BSC to decide which frequency bands shall be considered at PS channel allocation/reservation when the MS capability is unknown. This parameter is extended with one additional value, which shall indicate that not only the BCCH band but also the corresponding sub-frequency band shall be considered, for example:

In GSM 900 system, the new value will indicate that channels from both P and G1 frequency band are included in the calculations. This lead to that BCCH do not need to be moved from P-band when operators starts to use Extended GSM 900 (P + G1) band.

Performance monitoring

General improvements of STS counters and R-PMO that are not related to any of the new R12 feature:

• Existing QoS counters and R-PMO monitors modified to exclude PFCs with lower schduling priority for users running several paralell PFCs

• New throughput counters that are based on MS GPRS/EGPRS capability, in total 8 new counters.

• Measurements for GPRS downlink IP buffer discards introduced in R-PMO.

• Multi slot class introduced as parameter for the R-PMO IP throughput monitors

• Number of accesses per MS Multi Slot class introduced in R-PMO

• Improvements of the timeslots utillisation measurement in R-PMO

• MS 3GPP R97/R99 or R4 capability introduced as a parameter in the R-PMO IP latency monitors

• Counters for number of UL TBFs where the MS turned up on the PDCH, separate for DTM and non DTM connections



44 (175)

• Improvements to the GPRS availability measure, a new peg counter for five minute periods the cell is suspected to be unavailable

• Traffic load counters reflecting active TBF time (when data is transferred or in the downlink buffer), counters for number PDCHs and number TBFs per PDCH separately for E-, G- and B-PDCHs, uplink and downlink

• Counters for total number vs used RLC blocks Uplink and Downlink

PCU Configuration

From BSS R12 it is not possible by command to force the PCU to Single Mode. However it is still possible to run the PCU with only one RP for a very small system. The command used, RRPCC, is not longer supported.

5.10.2 Operations

Procedure to change TBF Mode between GPRS/EGPRS

The sub-feature will be controlled with new BSC exchange property, TBFMODEACT included in the commands RAEPC and RAEPP.

Sub-feature �Procedure to change TBF Mode between GPRS/EGPRS� can be monitored with R-PMO. The event �TBF Data Ends� is updated with new cause value �TBF release due to TBF mode procedure�.

TBFLIMIT

The following BSC Exchange Properties have a changed format:

• TBFULLIMIT

• TBFDLLIMIT

Both parameters can now be set on a decimal level.

PILTIMER

The default value of the BSC Exchange Property PILT is changed from 20 to 10 seconds.

PS channel allocation/reservation

The exchange property MBCRAC is extended with one additional value which shall indicate that not only the BCCH band but also the corresponding sub-frequency band shall be considered.

Performance monitoring

New R-PMO monitors are added for timeslot utilisation and IP buffer discards.



45 (175)

New parameters are added in R-PMO monitors for number of TBFs, IP throughput and IP latency.

A new sheet showing IP throughput based on MS GPRS and EGPRS capability has been added in the NWSA report �GPRS IP Throughput Cell, BSC�.

The counters are available in NWSA universe for customer report creation.

PCU Configuration

The command RRPCC, Radio Transmission, PCU Environment, Change is not longer supported.


Faster TBF setup

The �first Ping� time is reduced with up to 120 ms.

5.11 BSS R12 System Improvements


- X - - -



X X X - - -


5.11.1 Description

General Improvements of STS counters and R-PMO that are not related to any of the new feature:

• New hard time congestion counters for halfrate, separate for OL and UL subcell.

• A new counter for Immediate Assignment messages discarded by BTS due to congestion on AGCH (includes Immediate Assignments both for CS and PS).



46 (175)

• New signalling time congestion counters, considering both SDCCH and signalling on TCH, separate for call set-ups and other procedures that can be completed on a SDCCH.

• Two new counters for SDCCH establishment failures.

• Dropped call counters for calls with established call connection, separate for halfrate/fullrate and OL/UL subcell.

• Improvements to the TCH drop monitor in R-PMO, introduction of parameters for subcell, channel group, speech version, urgency condition and underlying cause.

• Speech Quality Measurement (SQI, FER and RXQUAL) to be collected only when there is an established speech path in STS, R-PMO and MRR.

Other improvements within the BSC:

• The architecture and blocks in BG-GRC are reconstructed in order to reduce the block size and complexity.

• The interface between the PPC and the DSP within the RPP is reworked and the code in DSPSUP is optimised to speed up the execution time.

5.11.2 Operations

New parameters are added in R-PMO monitor for TCH drops.

The counters are available in NWSA universe fro customer report creation.

A number of printouts and files have been changed to get a uniform syntax for parameters related to CELL, BSC, MSC and TRAPOOL name to make the parsing of incoming data in OSS-RC more consistent. The following file formats are changed:

• BARFIL

• BCDCFILE ASN.1 RESULT This file is also updated with information about which TRXs that are connected to Channel groups and cells. BSM Adjust in OSS-RC is updated to handle this new information.

• MRRFIL

• RIRFIL

The following printout formats are changed:

• CELL CHANNEL GROUP DATA

• CELL CONFIGURATION DTX DOWNLINK DATA



47 (175)

• CELL CONFIGURATION POWER DATA

• CELL IDLE CHANNEL MEASUREMENT DATA

• CELL LOCATING FILTER DATA

• CELL LOCATING PENALTY DATA

• CELL MS QUEUING DATA

• CELL STATE CHANGE RESULT

• CELL STATUS

• NEIGHBOUR TO CELLS

• NEIGHBOUR RELATION DATA

• NEIGHBOUR RELATION DELETED

• RADIO TRANSMISSION GB INTERFACE CONFIGURATION DATA

5.12 BSS R12 System Improvements, BTS


- X -



X X X - -


5.12.1 Description

RBS Fault Filtering

To reduce the number of fault reports generated by the RBS the Remote Transcoder Lost fault is abstracted from TS to TRX level. This reduces the number of reports sent over Abis as well as the number of entities written in BSC/OSS logs.

Automatic Restart after very Long Link Break



48 (175)

It has been observed that an RBS can be unreachable from the BSC, despite the fact that the RBS is in remote mode. Examples of causes are: Large BSC Restart (not all RBSs recover,), function change software or hardware malfunction.

The purpose is to detect when the RBS communication to the BSC is malfunctioning and force the RBS to restart on its own to try to recover the situation. This new restart will have its own Start Cause and the restart will be a slow restart.

This will reduce the number of site visits to do just a Push-Button Reset and reduce the risk for NFF by having a DXU/IXU suspected of being faulty or replaced for �just in case�.

The introduction of a new Start Cause will increase usefulness of statistical data logging in the BSC to detect what sites that �stand out� and in need of a more thorough investigation as to why they experience link breaks.

Improved LED handling

The improvement is to introduce unique LED behaviour when software download is ongoing to avoid that site personnel press the reset button on RUs for the wrong reason and too often. For example, pressing the reset button of a unit doing FC will lead to corruption of software on the RUs flash memory.

The unique LED behaviour is needed to help the site personnel to understand that an internal function change or external function change is ongoing. The behaviour shall be identical on TRS-2 and TRS-3 for consistency reason and to avoid confusion.

This unique LED behaviour will help the technician on site to understand which state the RBS is in and will reduce the risk of NFF. Once the SW download is completed and there is consistency between SW on flash and RAM, the RBS will stop to indicate function change.

Faster Function Change

To reduce software download time, only files supported by the current BTS configuration shall be downloaded. This together with improved File Relation Request/Response when SO CF is in state reset will reduce the software download time with up to 16 minutes.

Also the internal SW of sTRU, dTRU, dTRUe and RRU from DXU/IXU in the BTS are improved.

5.12.2 Operations

RBS Fault Filtering

Remote Transcoder Lost is now reported on TRX level (instead on TS).

New statistics counters are introduced regarding remote transcoder lost faults.



49 (175)

Improved LED handling

New unique LED behaviour during function change is introduced.

5.13 BSS R12 System Improvements, OSS-RC


- X - - -



- - X - - -


5.13.1 Description

BSS R12 System Improvements for BSS specific applications.

TG State Overview Report in BSM

BSM now provides a report that presents state information on Transceiver Groups and all subordinate Managed Objects. Users indicate the targeted transceiver group or groups through a selection made in the MO-browser of the application main window followed by an order to the BSM to generate the report. The selection may contain one or more Transceiver Groups, one or more Site-objects or a combination of either. The report presents the same information as returned by the MML-command RXMSP.

CNA Job Queuing

As a measure to avoid inconsistencies in the application information model the CNA application allows only one Adjust or Update job at a time to operate on the data stored for an individual network element. This sometimes causes a system resource conflict between jobs that want to access data for the same network element simultaneously. Up until now the solution has been that the job that comes first puts a �write-lock� on the data for the network element which has resulted in termination of subsequent Adjust or Update jobs that try to access the same network element data.



50 (175)

Besides an improved error message CNA Job Queuing introduces an option at preparation of Adjust and Update jobs where users can request that the job is queued rather than terminated. The number of retries and time between retries are configurable. Unless queuing is actively selected at definition of Adjust and Update jobs the application defaults back to the old behaviour where a resource conflict with another job causes termination of the job with a subsequent �now more clear- system message to the effect.

BSM Configuration Check for BCDC-file Handling

This feature is packaged as a command line script that allows for quick checks of the configuration of both the OSS and BSC nodes with regard to BCDC-file transfer.

Enhanced Support in CNA BSC Exchange Properties

Support for configuration management of BSC exchange properties is extended to encompass also parameters that don�t have any direct relevance for configuration of cell parameters but are of general relevance to the configuration of a network of cells.

Support in BSM for BSC Exchange Properties

BSM introduces management �including configuration change- support for a number of BSC exchange properties that need to be considered at configuration of radio base stations.

Configuration of Multiple DIPs

A new work order is introduced in the BSM Planning Wizard for simultaneous configuration of up to and including ten DIPs on the BSC side of A-bis links.

Enhanced Support in BSM for DIP Configuration

The work order offered in the BSM Planning Wizard under the name New RBS is enhanced with regard to configuration of DIPs on the BTS side of A-bis links by giving operators the possibility to edit all parameter values recommended by the Wizard.

5.13.2 Operations

The operation of the improvements referred to as System Improvements for OSS in BSS R12 is described in the OSS System Administrator and OSS User Guide for the CNA and BSM applications respectively.

5.14 Channel Repacking


- X - - -



51 (175)



X - X - - X


5.14.1 Description

This feature consists of Packing improvements and Optimization of TCH usage. The current implementation of TCH packing functions does not take into account which resources packed connections are occupying. Secondly, there are situations where channel packing is not necessary but a movement of a single slot CS connection would increase probability for a better DTM/GPRS throughput.

In this feature a new selection algorithm based on strategy �PS consecutiveness� is introduced. Whenever connections are chosen for packing this strategy decides in which order they will be packed.

This feature also introduces a new function that will optimize usage of TCHs. Whenever one of the following events occurs, MS leaves DTM, PS upgrading fails or at channel release, the group with TCHs is evaluated according to the new selection algorithm and a decision is made if any of the connections shall be moved from the group by means of intra cell handover.

Packing Improvements

This part introduces an enhanced packing algorithm for existing packing functions. Both existing functions �HR Packing� and �Dynamic FR/HR Mode Adaptation (note: just the FR to HR part) are adapted to the new optimization strategy.

In case when two connections are equally good from the optimization strategy point of view the �oldest� connection in the cell is to be moved.

Secondly, when connections are chosen for FR to HR packing and speech quality will decide which connection to pack, the channel allocation algorithm will propose candidates that are suitable for packing based on the optimization strategy.

The packing candidates sent for the quality evolutions are sent in prioritized order. First of the candidates that meet quality criteria shall be returned and packing shall be initiated on it. In case when none of the proposed candidates meet quality criteria the quality function shall choose suitable candidate.

Optimisation of TCH usage

This part introduces new TCH optimization functionality, which shall move single slot CS connections within a sub-cell without changing their channel rate and according to the new optimization strategy.



52 (175)

In order to move a connection the new traffic case �intra cell handover due to TCH optimization� is initiated.

The operator has the possibility turn this functionality on or off per BSC.

This function is event controlled i.e. when one of the following events occurs the optimization shall be initiated:

• A connection is released in a TCHGRP where resources are shared between CS and PS domain

• An MS leaves DTM

• PS domain wants to upgrade a P-set and finds out that a consecutive TN is missing in the PS domain, initiate movement of CS connection if possible.

When moving of connection is initiated it should be regarded only as another way of starting the channel allocation process but it is important that the same channel rate and speech version is kept so the end-user experiences as little disturbance as possible. The existing channel allocation profiles (CHAPs) shall be adapted in such way that this is fulfilled.

To increase probability of a successful movement of a CS connection and in order to not disturb normal traffic one moving attempt per cell at the same time shall be allowed. Whenever a suitable candidate for moving have been found the request for a new channel will follow the same selection process as a normal channel request but in case when function MS Queuing have active queue in the cell moving of connections shall be prohibited. When the cell is congested and the re-allocation of a connection leads to pre-emption the attempt shall be aborted. The optimization functionality shall however override capacity locks (AMRFRMAXTRAFFIC, AMRHRMAXTRAFFIC) in case when an AMR channel is already in use.

TCH optimisation strategy

Both improvements above uses the same selection strategy to decide which connection shall be chosen for packing/moving.

Note that an optimisation strategy shall only be used if the channel algorithm decides by it self what to move/pack.

The strategy, �PSPRIO�, shall be based on following selection criteria.

Move out CS traffic from PSPRIO marked TCHGRPs in order to increase probability for consecutive TNs.

TN 0 1 2 3 4 5 6 7 Idle TCH

PS

CS

DTM

TCHGRP

TCHGRP

IHO (1) IHO (2)



53 (175)

In the example above there are two connections that shall be moved according to the chosen strategy. In order get a priority between the candidates a ranking-value shall be used:

TCH Capability | Trigging Event | Number of PS Allocated Channels | Timeslot Number

Where TCH Capability have highest priority.

5.14.2 Operations

The operator can turn the feature on/off per BSC.

One new STS counter counts the number of intra cell handovers due to TCH optimization.


Cell Traffic Recording (CTR) and Mobile Traffic Recording (MTR) are updated with new cause value for intra cell handover i.e. �intra cell handover due to TCH optimization�

Events sent to R-PMO are updated with new cause value for intra cell handover i.e. �intra cell handover due to TCH optimization�.

5.15 Combined Cell re-selection triggering GSM to WCDMA


- X - X -



X - X - X X




54 (175)

5.15.1 Description

In the design base, GSM to UTRAN FDD cell reselection by the MS is only triggered by CPICH Ec/No exceeding a minimum threshold (FDDQMIN). CPICH Ec/No is a good measure on the FDD downlink quality. However, CPICH RSCP is a good measure (estimate) on the FDD uplink quality.

By also using CPICH RSCP, cell reselection to an UTRAN FDD cell will only be performed by the MS if both these measures exceed the indicated thresholds. A new offset (FDDQMINOFF) is also introduced and shall be used by the MS in the cell reselection algorithm.

5.15.2 Operations

The new parameters FDDRSCPMIN and FDDQMINOFF are possible to set from CNA in OSS on cell level.

It is also possible to use the command RLSUC to set these parameters and they are visible in the printout CELL SYSTEM INFORMATION UTRAN DATA.

The application information of ROEPC is updated due to the new value (2) for BSC exchange property COEXUMTS. COEXUMTS = 2 triggers that the new parameters above are included in SI and PSI.

The Application information RCS, CC Cell Data Handler, RCCD is updated.

5.15.3 Interface

System Information and Packet System Information sent to the MS includes the new parameters values.


Multi RAT MS release 5 or later is required to gain from this feature.

5.15.5 Other features

The feature FAJ 121 57, GSM-UMTS Cell Reselection and Handover is required.

5.16 Dual Transfer Mode


- X - - -



55 (175)



X - X - X X


5.16.1 Description

DTM is a way to achieve simultaneous speech and data transfer to one MS, as standardized by 3GPP. Improvements in R12 are mainly in the areas of showing DTM channel allocation success rate, increased support DTM set-up in all CS modes and to improve performance.

The following enhancements are included in BSS R12:

• Improved algorithm to choose TN for DTM calls

! The algorithm to choose TN for DTM connections is upgraded to consider the possibilities and limitations involved with the feature Flexible Abis.

! The algorithm to choose TN for DTM connections is upgraded to consider the limitations for the MPDCH to carry data traffic.

! If the PS alternatives are considered equal then the algorithm to choose TN for DTM connections is improved to consider current sub-cell as a better choice instead of following the SCALLOC parameter (i.e. let the CS locating functionality be considered more important).

• Improved DTM surveillance in R-PMO

• A filter for DTM is introduced in MRR to separate measurements from pure circuit switched calls

• New STS counter: DTM requests per cell that leads to an allocation attempt.

5.16.2 Operations

The command RAMDC and printouts MEASUREMENT RESULT RECORDING DEFINITION DATA and MRRFIL is updated with the new parameter DTMFILTER.

New STS counter: DTM requests per cell that leads to an allocation attempt.

R-PMO, NWS and RNO in OSS are updated to support the changes.



56 (175)


R-PMO and RNO is updated with information in events and MRR.


MS rel-5 supporting DTM is required.

5.17 Dynamic BTS Power Control


X X - - -



X - X - - -


5.17.1 Description

The parameters SSLENDL, QLENDL and REGINTDL are moved to BSC level.

The parameters SDCCHREG (ON) and STEPLIMDL (OFF) will no longer be configurable and are removed from commands and signals.

New default values when new cells are created for the following parameters: QDESDL, SSDESDL, QCOMPDL and LCOMPDL.


Due to that parameters are moved to BSC level these parameters will be assigned the default value. In case of differences between the default value and existing settings in customer network the behaviour can be affected.

5.17.3 Operations

The following commands and printouts are introduced/updated:

• New COD for RLBAC, RL, Dynamic BTS Power Control Additional BSC Data, Change



57 (175)

• New COD for RLBAP, RL, Dynamic BTS Power Control Additional BSC Data, Print

• Changed COD for RLBCC, Radio Control Cell, Dynamic BTS Power Control Cell Data, Change

• New POD for RLBAP, Dynamic BTS Power Control Additional BSC Data

• Changed POD for RLBCC, Dynamic BTS Power Control Cell Data

The following Application Information�s are updated:

• ROS Operation and Maintenance Exchange Property Changeable Exchange Adaptation (remove STEPLIMDL )

• RCS, RCQS Cell Data Changeable Exchange Adaptation (Power control parameters)

5.18 Dynamic MS Power Control


X X - - -



X - X - - -


5.18.1 Description

The parameters DTXFUL, REGINTUL, SSLENUL and QLENUL are moved to BSC level.

New default values when new cells are created for the following parameters: QDESUL, SSDESUL, QCOMPUL and LCOMPUL.


Due to that parameters are moved to BSC level these parameters will be assigned the default value. In case of differences between the default value and existing settings in customer network the behaviour can be affected.



58 (175)

5.18.3 Operations

The following commands and printout are introduced/updated:

• New COD for RLMAC, RL, Dynamic MS Power Control Additional BSC Data, Change

• New COD for RLMAP, RL, Dynamic MS Power Control Additional BSC Data, Print

• Changed COD for RLPCC, Radio Control Cell, Dynamic MS Power Control Cell Data, Change

• New POD for RLMAP, Dynamic MS Power Control Additional BSC Data

• Changed POD for RLPCP, Dynamic MS Power Control Cell Data

The following Application Information�s are updated:

• RCS, RCQS Cell Data Changeable Exchange Adaptation (Power control parameters)

5.19 Dynamic Overlaid/underlaid Subcell


- X - - -



X - X - - X


5.19.1 Description

With Two-way SCLD the traffic load in both subcells are evaluated at subcell load distribution. This is particularly beneficial in multi band cells since by allowing traffic allocation first to the OL subcell, the operators are given the possibility to prioritise any frequency band until some certain traffic level, and not only the "stronger" frequency band, normally set in the UL subcell.



59 (175)

Before R12, the cell evaluations for SCLD were done at every subcell load distribution time interval and a maximum of 16 active cells were evaluated for SCLD at each time interval in the BSC. In BSS R12 this time interval is removed and the evaluations for SCLD in a cell are now done at each TCH allocation and TCH release in the cell, and subcell changes can then be initiated directly if required.

5.19.2 Operations

The existing cell parameters SCLDLL and SCLDUL are replaced with the parameters SCLDLUL (SCLD Lower Limit UL) and SCLDLOL (SCLD Lower Limit OL). There is also a new cell parameter, SCLDSC, that is used by locating to determine which subcell that shall be preferred.

The exchange property SCLDTIMEINT is removed.

The following command is modified following the introduction of this feature RLLLC.

The following printout description is modified, � SUBCELL LOAD DISTRIBUTION DATA�.

The following Application Information is modified, �RCS CC Cell Data Handler�.

Two new STS counters, OLSCLDCOM and OLSCLDSUC added to existing DID CELEVENTSCCNT (Object type CELEVENTSC).

NCM (CNA, CNAI) in OSS is modified to support the changes.

5.20 Enhanced Measurement Reporting (EMR)


- X X X X



X X X - MS X




60 (175)

5.20.1 Description

The Enhanced Measurement Reporting feature (a.k.a. EMR), introduces a new measurement report, replacing the existing MR for EMR capable mobiles. The EMR message itself provides improved downlink transmission quality information for a specific MS can be used as basic input to statistics, power control and enhanced drop call handling.

Improved transmission quality information can also be provided for the uplink even without the use of EMR capable mobiles (as basic input to the existing MS Power Control feature algorithm).

Basic information for the decoding of speech blocks is provided using EMR, enabling FER data to be retrieved for the downlink.

5.20.2 Operations

The following new commands are introduced:

• RLEMI, RL, Enhanced Measurement Reporting, Initiate

• RLEME, RL, Enhanced Measurement Reporting, End

• RLEMP, RL, Enhanced Measurement Reporting, Print

The following commands are changed:

• RLDEC, Radio Control Cell, Description data, Change

• RLNRI, Radio Control Cell, Neighbour Relation, Initiate

• RLNRE, Radio Control Cell, Neighbour Relation, End

• RABRI, Radio Control Administration Active BA-list Recording, Initiate (General improvement of description of access control, including new EMR commands)

The following new printout is introduced:

• New POD for RLEMP, Enhanced Measurement Reporting

The following printout is updated:

• MTRFIL, record MEASUREMENT DATA updated with new EMR data

The following Application Information is updated for EMR:

• RXCMOO, Radio X-ciever Administration, Managed Object Data Handling, Changeable Exchange Adaptation



61 (175)


A minor increase of O&M load due to 3 signals instead of 2 being sent at Mobile Traffic Recording (MTR).

Increased size of new measurement report (EMR) has minor impact on LAPD.

5.20.4 Interface

Beside the changed format of the Measurement Result message, as described above, the EMR feature requires a changed management the following messages between BTS & BSC:

• CHANNEL ACTIVATION

• MODE MODIFY

• MEASUREMENT INFORMATION

5.20.5 Compatibility

The BTS activates EMR reporting for capable hardware platforms after the feature has been activated in the BSC. BTS performs UL measurements for Improved transmission quality information.

The use of BEP (MEAN_BEP & CV_BEP) and RxLev_VAL is not supported on the cTRU, RBS 2301, RBS 2302 and RBS 2401.


EMR capable mobiles (R99) are needed for this feature.


• The EMR message as such (including NBR_RCVD_BLOCKS) is provided in the mobile traffic recording function (MTR) and PMR in OSS.

• Basic transmission quality information is provided for further handling in MRR (RNO).

• EMR related event data (NBR_RCVD_BLOCKS and DTX_Used) is made available to the event application RTED in the BSC.

5.21 Five Downlink Timeslots

Impacts Implementation Operations Characteristics Interface Compatibility



62 (175)

- X X - -



X - X - X X


5.21.1 Description

Full support for MS multislot classes 30 to 33 are implemented. MSs supporting one or more of Multislot class 30 to 33 are capable of supporting up to five Time Slots (TS) in downlink. Depending on the multislot class, the MS can have one to four TS in uplink.

There is also a new mapping of MS multislot classes 34 to 45 when the feature is activated.

Multislot Class Max Rx Max Tx Sum

30 5 1 6

31 5 2 6

32 5 3 6

33 5 4 6

Table 31 MS Multislot Class 30 to 33

Mapped to Multislot Class Multislot Class

Feature On Feature Off

34 33 12

35 8 8

36 10 10

37 11 11

38 12 12



63 (175)

39 12 12

40 30 8

41 31 10

42 32 11

43 33 12

44 33 12

45 33 12

Table 32 New mapping of MS Multislot Classes 34 to 45

5.21.2 Operations

New STS counters introduced:

• MUTIL15

• MUTIL25

• MUTIL35

• MUTIL45

• MUTIL55

There is one new BSC Exchange Property for this feature:

• GPRS5TSDLACT to swich the feature on/off


Five instead of four TS could be supported in downlink, which increases throughput to a user with 25%.

The sum of simultaneous up- and downlink TS is increased from five to six, which enables 20% higher aggregated up- and downlink throughput to/from a user.


Rel 5 mobiles with MS multi-slot class 30-34 or 40-45 for 5 TS DL.



64 (175)


One new monitor is introduced in R-PMO, TS for DL 5-slot MS.

The NWS-A report GPRS BSC Traffic Load Cell is updated to reflect the utilization of 5 TS.

5.22 Flexible Abis


X X X - X



X - X - - X


5.22.1 Description

Flexible Abis was introduced in R11 as an optional feature. In R12 this feature has been enhanced in the following of aspects:

• 16k Abis paths, which have been allocated from the RES64K pool for circuit switched calls, are packed to counteract fragmentation of 64k Abis paths in the pool. The packing is done by intra cell handover.

• Improved initial allocation of GSL devices to counteract fragmentation of the RPP pool. GSL devices for on-demand and semi-dedicated PDCHs are seized from one end of the device file while devices for dedicated PDChs are seized from the other end. When the PDCH type is changed the old GSL device is released and a new GSL device is seized in accordance with this strategy.

• Extended pre-emption at Abis congestion. The pre-emption is extended to all cells supported by the same Abis pool. Also, pre-emption of a non-vital PDCH in one cell can be made to set up a vital PDCH in another cell.

• Improved downgrading of Abis path. A downgrade of a 64k Abis path will always succeed since no free 16k Abis path is needed to perform the downgrade.

• Move of cell enhancements. Dedicated PDCHs are not released when a cell is moved from one RPP to another. The allocation of new GSL devices in the target RPP will be faster so the time for a cell re-location will be reduced.



65 (175)

• Upgrade from B-PDCH to E-PDCH will trigger a change of TBF mode from GPRS to EGPRS to be able to benefit from the new PDCH capability.


The exchange property FLEX64KABIS is replaced by the cell parameter FLEXHIGHGPRS.

5.22.3 Operations

The command RXMOI is extended with a threshold parameter, ABIS64KTHR, for when to start packing of 16k paths in the 64k pool.

The command RXMOC is extended with the same parameter as RXMOI.

The command RXMSC is extended with the same parameter as RXMOI.

The command RXMOP produces a printout of the new parameter mentioned above.


• one cell counter for number of attempts to allocate a 16k Abis path for a circuit switched channel

• one cell counter for successful allocations from these attempts

• one cell counter for the number of pre-emptions of PDCHs due to Abis congestion

The following counters on TG level are introduced:

• Min, max and average number of idle devices in the 64k pool

• Fragmentation level in the 64K pool

• Min, max and average number of idle devices in the 16k pool

The Assignment Command event shall be updated with the new traffic case Intra Cell Handover due to Resource Optimisation and with the new reason 16k Abis Packing.

The TBF Changes Event is updated with the channel release cause values �PDCH pre-emption from CS due to Abis congestion� and �PDCH pre-emption from PS due to Abis congestion�

The new GPRS Ends event is updated with the channel release cause values �PDCH pre-emption from CS due to Abis congestion� and �PDCH pre-emption from PS due to Abis congestion�.



66 (175)


The level of congestion from lack of Abis or RPP resources will be reduced by the enhancements presented above. This will enable an even slimmer dimensioning of these resources with a preserved congestion level or conversely, the level of congestion can be reduced without adding Abis or RPP resources.

5.22.5 Hardware

The same dependency on hardware as the design base feature Flexible Abis.


The exchange property FLEX64KABIS is replaced by the cell parameter FLEXHIGHGPRS.

In the RBS dTRU, dTRUe, RRU or sTRU is required.


The enhancements of Flexible Abis utilize the procedure to change TBF Mode, which is part of the basic feature BSS R12 GPRS/EGPRS Improvements.

Since this feature adds delay to the activation time it would make things worse when having this in a long delay scenario, such as Abis over Satellite. Flexible Abis is therefore not possible with Abis over Satellite.

When Adaptive Configuration of SDCCHs is used together with Flexible Abis, the system assumes that all cells within the TG use this. The system then reserves an Abis path for being able to reconfigure an SDCCH/8 back to a TCH.

5.23 Flexible Channel Allocation


X X - - X



X - X - - X




67 (175)

The following enhancements are introduced.

PDCH Preemption Improvements

This part improves steering of PDCH preemption. Existing BSC parameter GPRSPRIO is moved to the cell level in order to improve interaction between this parameter and the parameter PDCHPREEMT.

Steerable Allocation

Selection algorithm used for circuit switched calls at channel allocation might sometime override preference parameters and result in random behavior. This is caused by certain order of CS/PS traffic and certain settings of parameters CHALLOC and PDCHALLOC. Secondly, previously named parameters can most likely be set in such way that that they will interfere with each other.

BSS R12 introduces a new selection strategy based on a cell parameter that will enable operators to choose if preference parameter shall decide where to park the calls or if PS traffic shall be prioritized. In order to avoid parameter conflicts, parameters CHALLOC and PDCHALLOC are combined into one cell parameter, CSPSALLOC.

The possible values for CSPSALLOC are:

• ĆS first, PS last´,

• ĆS first, PS no preference´,

• ĆS last, PS first´,

• ĆS last, PS no preference´,

• ĆS last, PS last´,

• ĆS no preference, PS last´,

• ĆS no preference, PS first´ or

• Ńo preference´.

A new cell parameter called CSPSPRIO is also introduced which steers how channels shall be allocated when there could be conflict between PSPRIO and the new parameter CSPSALLOC. The parameter shall have the values ĆS steers´ or ´PS steers´. The default value is ´PS steers´. The allocation algorithm shall treat the default value as no change in the algorithm compared to the design base.

The CS allocation algorithm is updated to handle the new parameter CSPSPRIO. This means that if the parameter has the value ĆS steers´ the algorithm shall follow that i.e. CSPSALLOC must be considered before PSPRIO.

On-Demand PDCH Limit



68 (175)

A new channel group parameter ODPDCHLIMIT that makes it possible to limit number of On-Demand PDCHs in a channel group at channel allocation is introduced. The parameter will be expressed as a percentage value of the total number of available traffic channels that can be used as On-Demand PDCHs.


�Steerable Allocation� merges two parameters into one new cell parameter. At function change the PS part value of the new parameter CSPSALLOC inherits the value of the parameter PDCHALLOC and the CS part inherits the value of parameter CHALLOC in all cases except when PDCHALLOC is set to �FIRST� and CHALLOC is set to �FIRST�. In that case the CSPSALLOC is set to �CSNOPRFPSFIRST�.

5.23.2 Operations

PDCH Preemption Improvements

The BSC exchange property, GPRSPRIO will be moved to the cell level and included in new commands RLCLC and RLCLP.

New POD �CELL CHANNEL ALLOCTION DATA� issued when command RLCLP is entered will include the new cell parameter.

The new OPI �BSC, Cell Channel Allocation Data, Change� will describe procedure how to change the new parameter.

Steerable Allocation

The existing parameters, BSC exchange property CHALLOC and cell parameter PDCHALLOC will be combined into one cell parameter CSPSALLOC and included in new commands RLCLC and RLCLP.

RNO (FAS/FOX algorithms) in OSS is updated due to the new parameter CSPSALLOC.

The new cell parameter CSPSPRIO is included in new commands RLCLC and RLCLP.

New POD �CELL CHANNEL ALLOCTION DATA� issued when command RLCLP is entered will include all these new cell parameters.

The new OPI �BSC, Cell Channel Allocation Data, Change� will describe procedure how to change the new parameters.

On-Demand PDCH Limit

New parameter ODPDCHLIMIT on channel group level will be included in the existing commands RLGAC and RLGAP.



69 (175)

Existing POD �CELL CHANNEL GROUP ALLOCTION DATA� issued when command RLGAP is entered will include this new cell parameter.

The existing OPI �BSC, Cell Channel Group Allocation Data, Change� will describe procedure how to change the new parameter.


The feature will introduce some operational incompatibility compared to the earlier BSS releases.

• The parameter GPRSPRIO is removed and replaced by a cell parameter with the same name.

• The parameter CHALLOC is removed and replaced by a combined cell parameter CSPSALLOC.

• The parameter PDCHALLOC is removed and replaced by a combined cell parameter CSPSALLOC.


See also the feature Flexible Priority Handling of Packet Data Channels for information about changes in initiation of PDCH pre-emption.

5.24 Flexible Priority Handling of Packet Data Channels


- - - - -



X - - -


5.24.1 Description

The initiation of load balancing features is in R12 based on average sampled value of preemptable On-Demand PDCH instead of the total number of On-Demand PDCHs in the cell.



70 (175)

5.25 Full Rate AMR on 8 kbps Abis


X X - X



X X X - - X


5.25.1 Description

This feature will allocate an AMR FR channel with AMR speech codec restricted to a maximum of 7.4 kbps when there is a shortage of 16 kbps paths in the non-64RES Abis pool. The reduced codec enables use of half a 16 kbps Abis path for the AMR FR connection. Compared to using AMR HR on the air interface the AMR FR channel will give a better coverage from the higher degree of channel coding provided.

5.25.2 Operations

The command RXMOI is extended with a threshold parameter DAMRREDABISTHR for when to start allocating AMR FR channels with reduce codec set, due to Abis.

The command RXMOI is extended with a switch, DAMRCR, for activating/deactivating Dynamic AMR FR Codec Reduction on TG level.

The command RXMOC is extended with the same parameters as RXMOI.

The command RXMSC is extended with the same parameters as RXMOI.

The command RXMOP produces a printout of the new parameters mentioned above.

New command RLDAC is introduced to enable/disable the features on cell level.

New command RLDAP is introduced to print the parameters set in RLDAC.


• one cell counter for number of successful allocations for an AMR FR channel using an 8 kbps Abis path.



71 (175)

The Channel Busy and Channel Busy extended events shall be updated with the new Abis rate.


The feature will reduce the level of congestion from lack of Abis resources. This will enable an even slimmer dimensioning of Abis with a preserved congestion level or conversely, the level of congestion can be reduced without adding Abis resources.


In the RBS dTRU, dTRUe, RRU or sTRU is required.


This feature requires the features FAJ 122 450 Flexible Abis, FAJ 121 055 Adaptive Multi Rate (AMR) and FAJ 121 358 AMR HR (which require FAJ 122 315 Half Rate Channels).

5.26 Gb over IP


X X - X X



X - X - X X


5.26.1 Description

This function gives the operator the possibility to use an IP transport network for the Gb interface according to 3GPP technical specification 48.016 and 48.018.

The speed at which data is transferred over the Gb Interface is also expected to be higher in an IP transport network while queuing and re-routing of packets is expected to decrease.

If the operator chooses to implement Gb over IP, the opportunity of pooling the SGSN resources will also arise (enable SGSN in Pool Support in BSC).



72 (175)


For HW dependencies see compatibility section below.

5.26.3 Operations

In general the described commands are used also for the SGSN in Pool Support in BSC feature.

Administration of IP Network Service and BSSGP Data

A new command family will be introduced to administer NS Entities and the parameters associated with the peer NS Entity (SGSN). With this family of commands it shall be possible to Initiate, Change, End and Print all parameters related to a specific NS Entity. The commands will support establishment and disconnection of the network service towards the peer NS Entity.

The behaviour of these commands is controlled by an optional feature parameter, (GBIP). The Gb over IP feature has to be supported by the PCU for any of the commands to be allowed.

There is also an exchange property for controlling if Frame Relay or IP is the active transport protocol for the Gb interface. The NSSTATE parameter of the RRINC command is only allowed if IP is set as being the active transport protocol for the Gb interface.

RRINI:NSEI=nsei,PRIP=prip,PORT=port;

This command makes it possible to create a new NS Entity and to initiate all Network Service parameters associated to the peer NS Entity. After this the NS Entity will be created and STATE will be MBL.

RRINC:NSEI=nsei,[[PRIP=prip][,PORT=port][,NSSTATE=nsstate]];

This command makes it possible to Change all Network Service parameters associated to a specific NS Entity.

The command initiates the sending of the SNS-SIZE procedure towards the Primary Remote IP Address specified in the command if the NSSTATE is changed to ACTIVE and there is at least one Local IP Address specified in the PCU. In this case the STATE can be either ACTIVE or ABL.

If NSSTATE is set to PASSIVE the NS layer communication towards the peer NS Entity will be interrupted. The command initiates the SNS-DELETE procedure for all Local IP end-points associated to the peer NS Entity. In this case the STATE will be MBL.

RRINE:NSEI=nsei;



73 (175)

This command makes it possible to End the Network Service for a specific NS Entity. It is not allowed to End the Network Service for an NS Entity that has an NSSTATE set to ACTIVE.

RRINP;

This command makes it possible to Print all Network Service parameters associated to all NS Entities.

RRBVP:NSEI=nsei[,NCBD];

This command makes it possible to print the BSSGP layer information for one several or all NS Entities. The parameter NCBD (no cell BVC data) makes it possible to print only signalling BVC data.

GPRS Cell Administration and Management

When IP is the active transport protocol for Gb traffic, one Cell could correspond to a number of BVCIs (one BVCI for each created NS Entity).

The possibility to change that reference when changing active transport protocol is added.

An exchange property GBTRANSPORT will control which transport protocol is active.

Administration of Gb Interface

It is not possible to activate Frame Relay as well as IP as transport protocol for Gb traffic at the same time in the one and the same PCU.

While only one transport protocol can be used at the same time in one PCU, the commands RRNSI, RRNSE, RRNEI, RRNEE, RRVBI, RRVBE, RRGBP and RRPCP are updated with an error code stating that the commands are not valid when Gb over IP transport is active.

Priority Handling

It is possible to priorities Gb over IP traffic over other IP applications in the BSC. There is an optional field in the IPv4 and IPv6 header which allows the IP packets to be treated differently by any receiving router/node, so different packets can be prioritised and consequently forwarded ahead of other packets. This IP functionality for differentiated services is called �DiffServ�.

It is possible to set a priority for uplink Gb traffic, but the IP layer in the BSC will not use the priority for incoming traffic since the air interface is the limiting resource and there exist flow control on that level.

Manual Configuration

To be able to recognise an SGSN, the BSS shall have knowledge of at least one of the SGSN IP endpoint(s). This SGSN endpoint is configured within the BSC before a communication path can be established.



74 (175)

The BSS internal IP endpoints and one UDP port shall be configured in the BSC used for an SGSN. An arbitrary UDP port value within a defined value range shall be given.

The BSS internal IP endpoints and the UDP port shall be configured before a communication path towards an SGSN can be established.

Before the switch from FR to IP can take place the IP network has to be configured and verified. This is a pre-requisite to the feature Gb over IP.

Dynamic Configuration

The auto-configuration procedures are used to exchange the configuration information between BSS and SGSN.

The client/server principle applies: the SGSN is the server, while the BSS is a client. The BSS shall have knowledge of at least one of the SGSN IP endpoint(s) to initiate the auto-configuration procedures.

Resource Distribution

The Resource Distribution function is used in the BSC to direct data traffic for a particular cell into the RPP who holds this cells BSSGP entity. This function allows BSS (or SGSN) to explicitly change the IP endpoint at which it receives NS SDUs.

The Resource Distribution function provides a means for the BSC (or SGSN) to control the IP endpoints at which the NS user traffic for a mobile is received.

5.26.4 Influenced Operations

The Operator must configure the Gb interface with IP.

Normally operators are using private IP addresses. That means that there will be no limitation of the number of IP addresses. An assumption is made that the operators can handle the relative high number of IP addresses.

The operator must choose an UDP port within a value range to be configured for the BSC.

Command RRPPI, Radio Transmission, IP Port, Initiate, was already introduced in R11.

RRPPI:PORT=port,APL=apl[,DSCP=dscp][,RIP1=rip1][,RIP2=rip2] [,RIP3=rip3][,RIP4=rip4];

This command opens an IP port for a specified IP application. The command also optionally initiates the port parameters, which are:

• Diffserv code point for the IP port

• Remote IP addresses assigned to the IP port



75 (175)

With this command the operator can map different applications, in this case Gb over IP to a certain Diffserv code point value. Note that the values shall be coordinated with the rest of the IP network.

Command RRAPI, Radio Transmission IP Application, introduced in BSS R11, associates an application with a previously defined IP address.

RRAPI:APL=apl,IPADDR=ipaddr;

In this case the application is Gb over IP.

When the IP configuration is ready, the operator can activate the IP transmission for Gb.

5.26.5 Interfaces

Gb over IP is compliant with Release 6 of the 3GPP Technical Specification 48.016 and the 3GPP Technical Specification 48.018.

Each RPP in the BSC is addressed with one IP v4 endpoint over the Gb interface.


EPS, ROJ 204 50/1, is required in all RPP magazines running GB over IP (EPSB, ROJ 204 23/1, is not supported).


The GB/IP feature in the BSS requires SGSN R6.


FAJ 121 665 BSC IP Connectivity is a prerequisite for Gb over IP.

5.27 GPRS/EGPRS Load Optimisation


- x X - -



X - X - - -



76 (175)


5.27.1 Description

In cases where two or more TBFs share the same radio resources and there is a TBF with low throughput due to bad radio conditions, that TBF is scheduled more seldom. In that way the TBFs with better radio conditions, and thus better throughput, will be scheduled more often. This leads to that the users with good throughput in the system can increase their throughput at high load situations.

Indirect this also means that the operator is able to prioritize between GPRS and EGPRS users, see parameters described below.

To determine if a TBF should be put in low scheduling, the radio conditions is evaluated against the radio link bitrate of the TBF. For a downlink TBF the radio link bitrate depends on the coding scheme used and the ratio of retransmissions. For an uplink TBF the radio link bitrate depends on the combination of coding scheme and ratio of failed USF schedules.

In order to put a TBF in low scheduling mode, the TBF shall fulfill the following conditions:

• Quality of Service (QoS) classes Interactive and/or Background

• The data volume level for the TBF is Medium or Large

• MAC mode is Dynamic Allocation (uplink)

The priorities between the different QoS classes are not affected. GPRS Load Optimization is however function even if the QoS feature is not activated.

5.27.2 Operations

The feature is controlled by the following parameters available in OSS (CNA/CNAI):

• LOADOPT � Support for GPRS Load Optimization

Off, On for Background or on for Background and Interactive.

• LOPTGTHR � Radio link bit rate threshold for GPRS TBFs

The threshold defines when a GPRS TBF is considered to be in a bad radio environment. The radio link bitrate is measured per PDCH. Valid for both downlink and uplink.

• LOPTETHR � Radio link bitrate threshold for EGPRS TBFs



77 (175)

The threshold defines when an EGPRS TBF is considered to be in a bad radio environment. The radio link bitrate is measured per PDCH. Valid for both downlink and uplink.

The setting of parameters LOPTGTHR and LOPTETHR can be used to differentiate GPRS users from EGPRS users.

An R-PMO monitor shows how much time the TBF has been in low scheduling mode.


The throughput for a TBF in good radio conditions will be improved with this feature. The graph below is based on measurement during verification and shows average DL throughput per timeslot, GPRS MS faded, EGPRS not faded.

The plot shows that the GPRS MS is sent to Low Scheduling Mode for RXQual 4 or bigger. At the same time it is possible to see that the EGPRS MS that have perfect radio environment all the time is scheduled more often and therefore get better throughput for RXQual 4 and above.



78 (175)

5.28 GPRS/EGPRS Mobile Logging


X X - X -



X - - - - X


5.28.1 Description

GPRS/EGPRS Mobile Logging (GML) feature was introduced in BSS R11 and it makes it possible to log data from (E)GPRS mobiles. In BSS R12 following enhancements are added to this feature:

• New Radio Signalling Link related event notifications would be available to subscribe to per cell basis. This is valid for DTM terminals.

• Missing Channel Allocation data will be added.

• It will be possible to add expire date to files that includes IMSI according to EU Directive 95/46/EC.

5.28.2 Operations

The COD/POD/OPI/AI will be updated.


There is an overload protection securing that the RPP is not overloaded. As high GPRS/EGPRS traffic will increase the logging volume, there might be capacity problems at traffic peaks if the RPP capacity is a scarce resource in the network. GPRS/EGPRS traffic will be served in favour of logging the GPRS/EGPRS Mobile Logging feature, causing some of the logging data to be lost at high load.


The features FAJ 121 665 BSC IP Connectivity and FAJ 121 603 GPRS/EGPRS Mobile Logging Client are required when using GPRS/EGPRS Mobile Logging.



79 (175)

5.29 GSM-UMTS Cell Reselection and Handover


- X X - -



X - X - - -


5.29.1 Description

In R12 urgency handover is introduced as an improvement to the existing feature �GSM-UMTS Cell reselection and handover�. Furthermore, R-PMO events are introduced to improve the observability.

In case quality- or timing advance problems in the serving GSM cell, it shall be possible to trigger a handover to UTRAN without considering the load in the GSM cell. Quality and timing advance measurements are compared to configurable thresholds to judge if an urgency condition is fulfilled, see �User Description, Locating�.

The table below summarises the priority order for handovers with the R12 feature �GSM-UMTS Cell reselection and Handover�.

Non-urgency Urgency

Not High Load High Load Not High Load High Load

G UG GU UG

Table 41 Handovers priority order

In case the load criterion in �GSM-UMTS Cell reselection and Handover� is not fulfilled (�Not high load�), GSM candidates are prioritised. But when the load criterion is fulfilled (�high load�), UTMS cells are prioritised.

In all cases, the radio criteria, CPICH Ec/N0 >= MRSL, for the UMTS cell must still be fulfilled before a GSM to UTRAN handover can be triggered.



80 (175)

5.29.2 Operations

New STS counters are introduced to be able to monitor the number of urgency handover attempts and the number of successful urgency handovers.

The observability for GSM to UMTS handover is improved by the introduction of a new R-PMO report with the following monitors:

• HO attempts (Number of)

• HO success (%)

• Quality at HO Success (UMTS cell)

• HO Reversion (%)

• Quality at HO Reversion (UMTS cell)

• HO Lost (%)

• Quality at HO Lost (UMTS cell)

The monitors can be used to tune the parameter setting of the quality threshold MRSL (described in �User Description, GSM-UMTS Cell reselection and Handover�). MRSL defines the minimum quality of a UMTS handover candidate.

R-PMO is also updated with a new report for monitors related to the results at inter-system handover resource allocation.

It should be noted that in some situation handover to UMTS might not be successful even when the measured quality is good. The reason might be the path-loss on the UL between the mobile station and the UMTS cell.

The PODs CTRFILE and MTRFILE have been updated with urgency handover related cause values for GSM to UMTS handover.

The AI2 has been updated with the new urgency handover counters URGHOVERUTRAN and SUCURGHOUTRAN.


In cases where the coverage of GSM is poor but the UMTS coverage is good, urgency handover will decrease the number of dropped calls.

5.30 GSM-WCDMA Active BA List Recording


- X - - -



81 (175)



X - X - X X


5.30.1 Description

In BSS R12 two new optional features are introduced: GSM-WCDMA NCS (GWNCS) in the OSS and GSM-WCDMA Active BA-list Recording (GWBAR) in the BSC.

The optional feature GSM-WCDMA Active BA-list Recording is a functional enhancement of the basic feature Active BA-list Recording. It enables data collection from WCMA neighbouring cells via the measurement reports sent by multi-RAT mobiles. The data can be used to optimize the WCDMA neighbouring cell lists for GSM cells.

The existing MML-commands and file printout for the BSC recording function Active BA-list Recording are extended with parameters and data for WCDMA cells, when the optional BSS feature GSM-WCDMA Active BA-list Recording is enabled.

The optional OSS feature GSM-WCDMA Neighbouring Cell Support includes functionality for recording scheduling and data presentation of the WCDMA neighbouring cell data.

The alphanumeric printout from Active BA-list recording in the BSC has been removed in this release. GSM-WCDMA Active BA-list Recording does not support alphanumeric printout.

5.30.2 Operations

The following commands related to the recording function Active BA-list Recording are modified following the introduction of the new feature: RABDC, RABDE, RABDP, RABTI

The following commands related to UTRAN Measurement Frequency data are modified following the introduction of the new feature: RLUMC, RLUMP

The following command related to System information, UTRAN data is modified following the introduction of the new feature: RLSUC

The following OPI is modified: BSC, Active BA-list Recording Report, Initiate (removal of alphanumeric printout)

The following printout descriptions are modified:



82 (175)

• �ACTIVE BA-LIST RECORDING DEFINITION DATA�

• �ACTIVE BA-LIST RECORDING RESULT�

• �CELL UTRAN MEASUREMENT FREQUENCY DATA�

• �CELL SYSTEM INFORMATION UTRAN DATA�

• �BARFIL�

The following Application Information is modified:

• �ROS O&M Active BA-list Recording Changeable Exchange Adaptation (ROBAR)�


Minor impact on CP-load and memory in BSC is foreseen.


RNO optional feature GSM-WCDMA NCS in OSS is needed to fully utilize the functions provided.


Multi-RAT mobiles are required.

5.31 Handover with Usage of Service Indicator


X X - X X



X - X - X X




83 (175)

5.31.1 Description

The BSS feature �Handover with Usage of Service Indicator� gives support for service based handovers, which means that the MSC can control in which system, GSM or UMTS, different Circuit Switched call types preferably shall be served.

The MSC can use the service indicators �should�, �should not� and �shall not� to indicate how potential handovers to UMTS shall be treated for a connection. It is also possible for the MSC to omit the service indicator. Regardless of the service indicator, any UMTS cell handover candidate must still fulfil the radio criteria described in the existing feature �GSM-UMTS Cell reselection and Handover�.

The table below summarises the priority order for handovers when the feature �Handover with Usage of Service Indicator� is activated. Urgency handover to UMTS is introduced in R12 and is described in the chapter �GSM-UMTS Cell reselection and Handover� in this document.

Non- urgency Urgency Case

No Load Load No Load Load

�Missing IE� G UG GU UG

�Should not� G G GU GU

�Should� UG UG UG UG

�Shall not� G G G G

Table 44 Handovers priority order

In case the MSC does not provide a service indicator (�Missing IE�), the connection is subject to load sharing. That is, in case of high load in GSM, handover to UMTS is prioritized before handover to GSM.

In case the MSC indicates that a handover to UMTS should not be performed (�should not�), handover to UMTS is only triggered in case of urgency and after all GSM cell candidates have been tried

In case the MSC indicates that a handover to UMTS should be performed (�should�), handover to UMTS is always prioritized before handover to GSM.

In case the MSC indicates that a handover to UMTS shall not be performed (�shall not�), handover to UMTS is never triggered.


The optional feature �GSM-UMTS cell reselection and handover� needs to be activated in BSS. The feature �Service Based Handover� needs to be activated in the Ericsson MSC.



84 (175)

5.31.3 Operations

The PODs MTRFILE and CTRFILE are updated with the new cause value: Service Indicator set to �should�.

The RQUCD AI is updated with the new STS counter HOATTSHOULDUTRAN, introduced to count the number of times a handover to UMTS is triggered because the service indicator is set to �should�.

ROEPC AI is updated with the new BSC exchange property SBHOACTIVE.

5.31.4 Interface

In the BSSMAP protocol the information element (IE) �Service Handover� in the messages �Handover Request� and �Assignment Request� is used.


An R12 BSC shall be compatible with an MSC which does not use the IE �Service Handover� (such MSC R11).

An R11 BSC shall be compatible with an MSC which uses the IE �Service Handover� (such MSC R12).


Support in the MSC for IE �Service Handover� is required.


The R12 version of the feature FAJ 121 57 �GSM-UMTS cell reselection and handover� is needed. As described above, the handover criteria according to the feature �GSM-UMTS Cell Reselection and Handover� is changed by the introduction of �Handover with usage of service indicator�.

The feature �Smooth GSM to WCDMA unloading�, does not limit the number of handovers for calls with the service indicator set to �should�.



85 (175)

5.32 Immediate Assignment on TCH

5.32.1 Description

Three new values for the existing cell parameter CHAP are introduced. They give the possibility to combine Immediate Assignment on TCH with BCCH in OL in a multi band cell as well as additional flexibilities.

5.32.2 Operations

The following commands are modified following the introduction of this feature RLHPC and RLHPP.

The following printout description is modified �CERFIL�.

The following Application Information is modified, �RCS CH Logical Channel Traffic Handler�.

PMR, NCM (CNA, CNAI) are modified to support the changes.

5.32.3 Interface

The external interface PMR Export of CTR/MTR/CER Recording Results in OSS is updated.


PMR in OSS are updated due to CERFIL changes.


- X - X -



X - X - - X




86 (175)

5.33 Incremental Redundancy in Uplink


X X - X X



X X X - X X


5.33.1 Description

Incremental Redundancy (IR) on the Uplink is a feature that will increase the throughput on the uplink for EGPRS TBFs. The feature can be divided in three parts:

The IR algorithm and storing of IR information

Incremental Redundancy (IR) is a type-II hybrid Automatic Repeat request (ARQ) scheme. This means that the receiver not only requests retransmission of erroneous radio blocks it also store soft values of these blocks. The soft values are combined with the information from the retransmitted block to increase the probability of successful decoding.

LQC improvements

Prior to R12 only Link Adaptation (LA) has been used on the uplink for EGPRS TBFs. To take full advantage of IR new MCS selection tables is introduced and these are more aggressive than the ones for LA.

Activation and deactivation of IR per uplink EGPRS TBF

If IR is activated the BSC will send IR activation messages to the BTS for each new uplink EGPRS TBF that is established. The IR activation message contains the TFI and the used TSs for the TBF. If the TBF is served by several TRXs a separate IR activation message is sent to each one of them.

When a TBF that is using IR in uplink is ending a IR stop message is sent from the BSC to the BTS. When the BTS receives this message it will delete all stored IR data connected to this TBF/TFI combination.



87 (175)

If the TFI is changed at upgrade of a TBF an IR stop message will be sent for the old message and a new IR activation message is sent for the new TFI. The same procedure is applied at re-reservation of a TBF. If the TFI is not changed at upgrade of a TBF an IR update message will be sent, when the BTS receives an IR update message the already stored IR data will not be deleted.

Figure 3 gives an overview of how the IRU feature affects different nodes and functions.

RBS BSC

Um:-Possible to set resegment bit in Packet uplink ACK/NACK, Packet uplink assignment and Packet timeslot reconfigure

BSC:-Optional feature- LQC is update-Activation/deactivationof IR per TBF

Abis:-The PCU-Data-IND IE is updatedwith IR information per TBF.

-BTS reports IR capability to BSC.

RBS:-IR algorithm (joint decoding and soft combining) - Storing of unacknowledged RLC data blocks- Send IR capability to BSC

MS:-Support for IR onthe uplink has been mandatorysince R99


In order to create logical naming and usage of the LQC exchange properties UL and DL, the exchange property called LQCIR has changed name to LQCMODEDL.

5.33.3 Operations

Two new BSC exchange properties are introduced:

• EGPRSIRUL used to turn this feature on and off

• LQCMODEUL used to control the aggressiveness of the LQC algorithm in the uplink. This parameter also controls if re-segmentation of the re-transmitted RLC data block is allowed



88 (175)

5.33.4 Hardware

IR in the uplink requires EGPRS capable TRXs.

5.33.5 Interface

The RESEGMENT bit sent to the MS indicates if it is allowed to re-segment a retransmitted RLC block or not. Prior to R12 this has been fixed to 1 but with IR in uplink it will be now dependent of the parameter LQCMODEUL.

The RESEGMENT bit is included within each PACKET UPLINK ACK/NACK, PACKET UPLINK ASSIGNMENT and PACKET TIMESLOT RECONFIGURE messages.

0 = Resegmentaion not allowed

1 = Resegmentaion is allowed


Support is not guaranteed for sTRU KRC 131 139/01 revision R1G or earlier.


Rel 99 MS with support for IR in the UL is required.


Link Quality Control is updated with enhanced support for UL EGPRS TBFs.

5.34 Interference Rejection Combining


- - X - -



- X - - - -




89 (175)

5.34.1 Description

IRC Enhancements improves the IRC algorithm for GMSK modulated carriers in frame-synchronized networks. The enhancement will provide better uplink interference suppression of the strongest GMSK modulated interfering signal with different training sequence than the carrier.


Improved uplink performance (RxQual) in frame-synchronized radio networks.

5.35 Inter System Consistency Reports


X X X - -



- - X - - X


5.35.1 Description

To avoid ping-pong effects between GSM and UMTS, the following parameter settings are recommended for inter-system handover and reselection.

• Cell reselection; FDDQMIN � FDDQMINOFF > qQualmin + sRatSearch

(1)

• Handover; MRSL > utranFreqThresh2dEcno (2)

Note: This formula is valid from OSS-RC R3, AOM 901 017/3 R1K. For older version of OSS-RC please use revision C or older of the BSS R12 NIR

The parameters qQualmin and sRatSearch are set on cell level and utranThres3aEcno is set on RNC level in UTRAN. The values of these parameters can either be entered manually in CNA or, if the function IRATHOM is activated, automatically fetched from the UTRAN network.

FDDQMIN and FDDQMINOFF is set per GSM cell and is valid for all its UTRAN neighbours and MRSL is set per UTRAN cell in GSM.



90 (175)

In the �Inter System Consistency Report�, generated via OSS RC, all the inconsistencies for cell reselection and handover will be presented, that is when rules 1 and 2 are not fulfilled.

5.35.2 Operations

The consistency check report can be generated from the CNA GUI

Parameters can be viewed and entered in the new GUIs �RNC Properties � GSM � UMTS Cell Reselection/Handover� and UTRAN External Cell Properties � GSM-UMTS Cell Reselection/Handover�.


Minor increase of CPU load in the OSS during the time consistency check rules is executed.


FDDQMINOFF is only included in the Consistency rules if the feature FAJ 121 933, Combined Cell re-selection triggering GSM to WCDMA is activated.

If automatic synchronisation of GSM - and UMTS data shall be performed, the function IRATHOM needs to be activated.

5.36 Mixed Micro Configurations


X X - - -



X X X - - -


5.36.1 Description

Mixed configurations between RBS 2308/RBS 2302 and RBS 2309/RBS 2302 are supported.



91 (175)

The RBS 2308 or RBS 2309 shall always be configured as the master cabinet. From the master cabinet a TXL bus is connected to each RBS 2302 cabinet and a Y-link to an eventually RBS 2308 or RBS 2309.

Following configurations are supported:

• One RBS 2308 and one RBS 2302

• One RBS 2308 and two RBS 2302

• Two RBS 2308 and one RBS 2302

• Two RBS 2308 and two RBS 2302

• One RBS 2309 and one RBS 2302

• One RBS 2309 and two RBS 2302

• Two RBS 2309 and one RBS 2302

• Two RBS 2309 and two RBS 2302

Both single and dual band configurations are supported.


Due to HW differences, there are no bus connection routing bursts between RBS 2308/9 and RBS 2302. Consequently, a TS controlled by a TRX in an RBS 2308/2309 cannot be transmitted by a TX located in an RBS 2302, and vice versa. To overcome this limitation, it is essential that the TRXs in an RBS 2308/2309 and the RBS 2302 are dedicated to different CHGRs. The TXs in the different cabinet types must also be dedicated to different CHGRs.

5.36.3 Operations

TX recovery is disabled when these configurations are used.

Antenna Hopping is not supported for these configurations

5.37 Multi Band Cell


- X - - -



92 (175)



X - X - - X


5.37.1 Description

In a multi band cell, it will be possible to use the downlink measurements on the BCCH carrier of the serving cell instead of the downlink measurements on the active channel and this will improve the Locating accuracy and make the tuning of multi band cells easier. For this to work the BCCHNO of the serving cell need to be included in the cell�s Active BA-list.

5.37.2 Operations

There are two new parameters in CNA in OSS, �Serving cells BCCH in Active list� and �Serving cells BCCH in Idle list�, to control whether or not the BCCH frequency of the cell is included or not included in the Active BA-list and Idle BA-list.

The following printout description is modified �CELL LOCATING DATA�.


The Active BA-List Recording now adds measurements collected on the own BCCH as an undefined neighbour. This need to be known by post-processing tools in order to not make faulty assumptions when associating measured ARFCNs, BSICs for undefined neighbours to probable cell names. The RNO applications RNO (FAS, NCS, NOX) in OSS have been modified to handle this.

5.38 Multi-Layered HCS


X X X - -



X - X - - X



93 (175)


5.38.1 Description

The R12 HCS (Hierarchical Cell Structures) Enhancements give additional functions to the existing optional feature �Multi Layered HCS� set with �HCS with 8 layers and 8 HCS bands�.

Extended number of prioritised cells per layer

The HCS algorithm is modified to prioritise more than one cell in the same layer in the candidate list. This will solve the problem with unwanted handover to cells in lower prioritised (higher) layers when handover to the (only one) higher prioritized target cell candidate is not possible due to that it is congested.

There are two new exchange properties introduced for this enhancement, MAXCELLSINLAYER and MAXDBDEVINLAYER.

HCS handover in or out possible depending on channel availability

HCS is given the ability to even out the traffic load differences between the different layers and HCS bands. This is achieved through a new HCS traffic distribution functionality in Locating that can prevent cells in higher prioritised layers from becoming congested, while cells in lower prioritised layers have free capacity. It is possible to set channel availability limits for a cell, so that the possibility to do HCS handover in to, and HCS handover out from, a cell depends on the current traffic load. At low traffic load in a cell, HCS handover out cannot be done, and at high load in a cell, it is not possible to do HCS handover into this cell. At the same time as the risk of congestion situations for speech traffic is reduced it will be possible to prioritise packet data traffic (HCS now uses the same bit as CLS in the GPRSPRIO parameter).

The new HCS traffic distribution parameters are two on cell level, HCSOUT and HCSIN. In addition there are two new exchange properties, HCSCHAVAILTIMER and HCSTRAFDISSTATE.


Function change can be performed with DCI. Default values shall be loaded into new cell parameters at function change to avoid disturbances (the default values aims at disabling the new traffic distribution functionality, so that it can be gradually introduced to the network at a later stage).

Note that prioritising more cells per layer will reduce some of the ping-pong handovers that could occur with the previous HCS functionality.



94 (175)

5.38.3 Operations

The following OPI is modified, �BSC, Hierarchical Cell Structure Data, Change�.

The following commands are modified, RLLHC and RLLHP.

The following printout description is modified, �CELL LOCATING HIERARCHICAL DATA�.

The Application Information is modified for the following blocks, ROEPC, RQCD and RQRCQS.

One new STS counter per cell, TIMEHCSOUT, added to existing object type CELLHCS.


Impact on CP processor load is expected to be maximum 1.4% (APZ 212 25) for CS Traffic at handover and only if HCSTRAFDISSTATE is set on and HCSCHAVAILTIMER is set to minimum value. Using higher value on HCSCHAVAILTIMER can reduce this impact.


The NWS-A report �Handover Performance per Cell, BSC� is updated with �HCS Handover out Availability (%)�.

5.39 Operation Maintenance Terminal


- X X - X



- X - - - X


5.39.1 Description

Increased Transmission Speed



95 (175)

The transmission speed between an OMT and an RBS containing DXU-21 or IXU-21 is increased compared to R11.

The execution time for the OMT functions �Read IDB�, �Install IDB� and �Display RBS log� will be reduced significantly due to the increased speed.

This will make it easier for site personnel to get RBS SW logs from problem sites.

Improved Bandwidth Usage

OMT offers a lot of functions for the user. Some of these OMT functions take long time. Display log, Install IDB and Read IDB are examples of such functions. To make Install IDB, Read IDB and Display log faster the bandwidth used in the OMT-RBS communication is reduced and optimised.

Check IDB (requires BTS 12B)

This new OMT function checks the IDB in the RBS and gives the OMT user information about the IDB. The information that is given to the user is:

• IDB type ("Standard IDB", "Expert IDB" or "Not Supported IDB")

• IDB fault status ("Faulty" or "Not Faulty")

Check IDB will be useful when performing RBS trouble shooting or when planning IDB replacement.

Improved description of define parameters (requires BTS 12B)

In the OMT users manual, the OMT online help and RBS 2000 CPI the following is described for each configuration parameter that is entered in the OMT:

• What the parameter is used for

• When the parameter must be defined

• How to find out which parameter value to set

• What happens if wrong parameter value is used

Improved description of define parameters means that:

• The information needed when creating an IDB is always available.

• If the operator has forgotten to define a parameter in an IDB the operator will have information enough to determine if the parameter value must be changed.

5.39.2 Operations

See description.



96 (175)


See description of Increased Transmission Speed.


Increased Transmission Speed requires an RBS with DXU-21 or IXU-21.

The �Improved Bandwidth Usage� functionality is supported for all RBS 2000 configurations.

BTS 12B is required for some parts, see description above.

5.40 PCU Load Control


- X X - -



X - X - - -


5.40.1 Description

Utilizing the CPU capacity of each RPP as much as possible can increase the capacity of the PCU. By introducing mechanisms in the RPP, which avoid disturbances in traffic throughput, or even restart of the RPP, at high CPU load the PCU can be dimensioned to handle more traffic. This is achieved by prioritizing between activities that are performed on the CPU, and by introducing several load thresholds at which different actions shall be performed in order to limit the load.

The PCU Load Control feature is divided into three major tasks:

Load Regulation

The load regulation within GPH is based on credits provided by a new load regulation function that shall insure that important traffic functions have enough CPU time.

Overload Protection



97 (175)

The Overload Protection mechanisms will handle all fast changes in CPU load or memory usage and make sure that the RPP will not restart due to high load. Examples on measures to be taken at rapid increases of load is:

High Load actions

1st � Stop RPEF events and prevent addition of new GSL channels

2nd � Decrease the PILT timeout in the overloaded RP

3rd � Remove PDCH�s step-by step until load is secured

Low memory actions

1st � Reduce MS Flow Control buffer sizes

2nd � Prevent new TBF�s from being established

When the overload peak is gone, the restrictions shall be released slowly step-by step to prevent large fluctuations.

RPP Load Distribution between PCU HW Resources

RPP Load Distribution handles all long-term changes in CPU load by monitoring and comparing the load of each RPP within the whole PCU. If a certain RPP is extremely loaded, and at the same time there are RPPs with much less load, then a �Move of Cell� shall be triggered in order the even out the load between the RPPs.

5.40.2 Operations

To monitor the distribution of cells between RPPs, two new STS counters on BSC level are introduced in a new STS object type GPHLOADREG:

• Number of succeeded cell move attempts for PCU Load Distribution

• Number of failed cell move attempts for PCU Load Distribution due to lack of RPP candidates with enough low load

To monitor the actions taken by the GPH Overload Protection mechanism, the following BSC level STS counters are introduced in the new STS object type GPHLOADREG:

• A counter that increases at every 500ms interval when an RPP is considered to be in high load mode.

• Number of rejected Packet Access Request per BSC due to lack of RPP memory.

• A counter that increases every 20th second when MS Flow Control has been suppressed due to lack of memory.



98 (175)

• Number of active PDCHs released due to high load in an RPP.

• Number of idle PDCHs released due to high load in an RPP.

On cell level the following is added to the existing STS object type CELLGPRS3:

• Number of active PDCHs released due to high load in RPP.

A new OPI that describes how to detect an under dimensioned PCU is introduced 'PCU LOAD DISTRIBUTION FAULT' and 'PCU OVERLOAD PROTECTION FAULT' which shall be followed if a corresponding alarm is raised by the BSC. By following these OPI's it gives an indication whether the PCU is under dimensioned (when it comes to RP hardware) or not.


The capacity of the PCU is increased since the RPPs in a PCU can be running closer to CPU limit.

5.41 Predefined Configuration Profiles


- X - X X



- - X - - -


5.41.1 Description

Predefined Configuration Profiles (PCP) offers a way to create predefined parameter configurations in so called Configuration Profiles. A profile may define a specific configuration for anything from a single parameter, several or all parameters of one or more features to a subset or all of the parameters for configuration of a specific type of MO, e.g. an Internal Cell.

Configuration Profiles that are intended for a common configuration purpose are grouped under a common identity referred to as the Profile Group.



99 (175)

5.41.2 Operations

PCP may be operated through the CNA GUI or alternatively from the command line interface (CLI) of the new CNAI introduced in BSS release R11.

Configuration Profiles are applied to individual MOs by linking the MO to the Configuration Profile, in PCP called �associating�. At parameter configuration entire groups of parameters can be assigned values by means of the Configuration Profiles to which MOs have been associated.

To enable for example network optimisers to keep track of unwanted changes PCP offers a number of ways to generate a report on deviations between the parameter values that are specified by Configuration Profiles associated to different MOs (the wanted configuration) and the corresponding active values in the live network (the actual configuration).

Checks of active parameter configuration versus configuration profile specifications are performed on the CNA Valid Area. The same type of check can also be executed on CNA Planned Areas. It�s also possible to restore a parameter value that deviates from an applied Configuration Profile.

To help users to become familiar with this feature it comes with four predefined Profile Groups and Configuration Profiles that support configuration of BTS- and MS- Dynamic Power Control as well as Intra-Cell Handover characteristics.

5.41.3 Interface

Import and export of MO-Configuration Profile associations is only supported by the new CNA interface (CNAI) that was introduced in BSS R11.

A feature-specific flag has been added to the new interface. The flag is used to request generation of a CNAI export file containing corrections needed to restore all parameter values according to the wanted parameter configurations as expressed by user specified MO-Configuration Profile associations that are stored in the CNA database.

The interface is fully backwards compatible.


The function for checking of deviations between wanted and the active network configuration is supported only by the new (R11) CNA interface.

5.41.5 Other Functions

The feature is built on and requires the OSS-RC applications CNA and CNAI.



100 (175)

5.42 Radio Network Optimisation (RNO)


X X - X -



X - X - X X


5.42.1 Description

The Radio Network Optimization (RNO) features consist of several OSS and BSS features. In BSS R12 two new features are introduced: GSM-WCDMA Neighbouring Cell Support in the OSS and GSM-WCDMA Active BA-list Recording in the BSC.

GSM-WCDMA NCS is used to find which WCDMA cells that should be defined neighbours to the GSM cells. This functionality is based on measurement reports from multi-RAT mobiles and handover statistics. Data from the measurement reports is collected in the BSC with the BSS feature GSM-WCDMA Active BA-list Recording (GWBAR). The feature GWBAR is described more in detail in another chapter in this document.

In addition there are some other enhancements in RNO:

• Import of ICDM in FAS. It is also possible to delete rows in the ICDM.

• Possibility to include number of times an undefined neighbour was reported as strongest as a criterion in the NOX algorithm

• Enhanced TSC allocation in the SYROX algorithm

• Only BCCH frequencies in the reallocation search in FOX

• Make a CNA planned area in FOX and NOX without scheduling an update job

There are also some enhancements in RNO related to the features Multi Band Cell, Speech Quality Supervision and Dual Transfer Mode. For more information see the description of each of the mentioned features.



101 (175)


In order for GWNCS to work properly, coordinates, antenna direction, antenna type and output power for WCDMA cells need to be included in CNA, preferably done by importing the data via CNAI.

5.42.3 Operations

FAS, FOX, MRR, NCS, NOX, RNDBI, SYROX, CNA and CNAI in the OSS are modified by the new functionality.


Minor impact on processor-load and memory usage in OSS is foreseen.

5.42.5 Interface

The following OSS External interface are affected:

• The export of RNO results in tab-separated format is updated

• The format of the RNDBI database is updated


The optional OSS feature GSM-WCDMA NCS is dependent of the optional BSS feature FAJ 121 815 GSM-WCDMA Active BA-list Recording and the optional OSS feature Neighbouring Cell Support (NCS).


Multi-RAT mobiles are required.

5.43 RBS 2000 Synchronization


X X - - X



X X X - - X



102 (175)


5.43.1 Description

This feature enhances the optional feature �RBS 2000 Synchronization� by introducing:

• Automatic calculation of TF compensation values and measurement of ESB delays.

• Automatic master reselection in TG clusters. This means that a new master is selected automatically if the former master is unable to provide timing information to the slaves in the TG cluster. The slaves automatically recalculate their TF compensation values according to the new master. The operator does not need to intervene.

The automatic master reselection is performed within a logical TG cluster, i.e. TGs connected to the same physical ESB and configured with the same defined TG cluster identifier.


The customer needs to group existing TGs, i.e. connected to each other through the ESB and configured with TFMODE set to master or slave, into logical TG cluster to take advantage of the enhancements introduced for RBS 2000 Synchronization. Physical TGs not belonging to a logical TG cluster will not take advantage of the new enhancements.

A logical TG cluster is defined by configuring the new parameter CLUSTERID with the same defined identifier to all TGs that should belong to the same logical cluster.

The parameter TFCOMPPOS needs to have the default value OMT to allow the TGs to perform automatic calculation of TF compensation value when belonging to a logical TG cluster.

It�s recommended to activate Supervision of Logical Channels Availability for BCCH to get an alarm when BCCH (channel group 0) is not available after an automatic master reselection has occurred.

5.43.3 Operations

OPI Cell Logical Channel Availability Supervision is updated and a new OPI Radio X-ceiver Administration, Channel Group Allocation, Change is created to describe the movement of channel group 0 between 2 TGs within a logical TG cluster after an automatic master reselection has occurred.

OPI Radio X-ceiver Administration, Transceiver Group Synchronization, Active, is updated due to introduction of TG clusters.



103 (175)

OPI Radio X-ceiver Administration, Transceiver Group Cluster, Define, is introduced due to TG clusters.

OPI Radio X-ceiver Administration, Transceiver Group Cluster, Remove, is introduced due to TG clusters.

OPI Radio X-ceiver Administration, Transceiver Group Cluster, Change, is introduced due to TG clusters.

COD RXMOI, is updated with new parameter and fault codes.

COD RXMOC, is updated with new parameter and fault codes.

COD RXMSC, is updated with new fault codes.

COD RXMOP, is updated with new parameter and fault codes.

COD RXCDP, is updated with new function description.

POD Radio X-ceiver Administration Managed Object Data, is updated with a new printout indicating if a timing function belongs to a TG cluster for which automatic master reselection is active.

POD Radio X-ceiver Administration Managed Capability Information, is updated with new parameters.

POD Radio X-ceiver Administration Managed Object Configuration Data Information, is updated with new parameters.

POD BCDCFILE ASN.1 RESULT, is updated with new parameters.

AI RXCMOO, Changeable Exchange Adaptation, is updated with a new bit, f7, description in OMLF1 function map.

AI RXCMSD, Changeable Exchange Adaptation, is updated with a new parameter, CLUSTERID, description.

AI ROEPC, Changeable Exchange Adaptation, is updated with a new exchange property EXMASTERRES that activate the automatic master reselection functionality.


The feature is supported by TGs realized by RBS 2000 and supporting the feature �RBS 2000 Synchronization�.

The enhancements to �RBS 2000 Synchronization� are not compatible with physical TG clusters containing RBS 200. Such TG clusters are still supported as before and requires manual calculation of TF compensation values.

BTS 12B is required to support RBSs with DXU-11.



104 (175)

5.44 Real-Time Event Data and Real-Time Performance Monitoring


X X X - -



X - X - - X


5.44.1 Description

The R-PMO application has been used for trouble shooting purposes as well as radio network optimisation presenting network data as traffic and quality monitors in real time on cell level. In BSS R12 the R-PMO application will be used as a complement to STS as well as continuing to be a trouble shooting tool and optimisation tool. The R12 feature R-PMO introduces the following enhancements:

• Measurement Result Event reporting rate is changed to a more even regulation at low, normal and high situations.

• Better overload regulations for all Events in the BSC and between BSC and OSS.

• The Measurement Result Event is split in

o Medium: to be used in R-PMO monitors

o Large: to be used in Raw Event Data Export (REDE, implemented in R11)

• The GPRS Data Transfer Ends Event is split in three events to be able to include more information

• Possibility to dedicate processor usage in OSS for R-PMO

• A new database in R-PMO application to be used for statistics

• Since larger amounts of data will arrive to the R-PMO application a number of enhancements are made to help the user to view the data in a comprehensible and well-arranged way

• The average row can be displayed in a graph



105 (175)

• TRX data in monitors

• More cause values for dropped calls

• Multi-select of filters when more than two filters are available

• It will be possible to add expire date to files that includes IMSI according to EU Directive 95/46/EC

Support for a number of other R12 features are also provided, see each feature for a description.

The BSC adds new events and does some changes to existing events. The OSS adds 30-35 new monitors and 3 reports.


A dedicated RPP index 6 shall be situated on a 100 Mbps slot in the RPP magazine.

For large configurations a dedicated server in OSS might be needed (dependent of how much event data that will be subscribed for).

5.44.3 Operations

OPI: Radio Transmission IP Services Configuration, Change is updated with new parameters to the RRIPI command.

OPI: BSC, Dedicated RP Resource for Event Handling, Change is updated to describe how to dedicate two RPP for MES.

COD: RRIPI is updated due to new parameters.

POD: Radio Transmission IP Parameter Data is updated due to new parameters

AI: ROS; RP Application Support and Event Handling Changeable Exchange Adaptation is updated due to new EID and AID.


Event Data Enhancements

The load on the OSS will increase in R12 compared to R11 due to the fact that R-PMO shall work as a complement to STS (Statistics). More (E)GPRS events will be sent, more and longer CP events, and more MR events will also be sent. The processor usage will be dedicated in the OSS for R-PMO and the BSC RPP shall be situated on a 100 Mbps slot in the RPP magazine.



106 (175)

The load in BSC CP will increase in R12 compared to R11. In R11 the expected relative CP traffic load increase when activating R-PMO in the whole BSC for all CS event types was estimated to about 6% (for example traffic load increase from 50 to 1,06*50 = 53% CP load). In R12 the relative load increase when activating R-PMO for all CS traffic events including medium MR event differs depending on the CS traffic level in the cells and is estimated to:

• relative CP load increase 10%

• absolute CP load increase of maximum 10 % for APZ 212 20/25 and 3-4% for APZ 212 30/33. This is for a assumed network size of 250 cells for APZ 212 25, 500 cells for APZ 212 20, 500 cells for APZ 212 30 and 1000 cells for APZ 212 33."

5.44.5 Hardware

It is strongly recommended that the dedicated RPP index 6 for event handling is situated on a 100Mbps slot in the RPP magazine in large configurations. Redundancy by using a hot stand-by RPP is possible.

The disk storage requirements on the OSS server will increase due to the new statistics database.


The feature FAJ 121 665, BSC IP Connectivity, is required when using Real-Time Event Data and Real-Time Performance Monitoring.

5.45 Remote OMT


- X - - -



- X - - - X


5.45.1 Description

Improved Bandwidth Usage



107 (175)

OMT offers a lot of functions for the user. Some of these OMT functions take long time. Display log, Install IDB and Read IDB are examples of such functions. To make Install IDB, Read IDB and Display log faster the bandwidth used in the OMT-RBS communication is reduced and optimised.















5.45.2 Operations

See description.


The �Improved Bandwidth Usage� functionality is supported for all RBS 2000 configurations.




108 (175)

5.46 Remote OMT over IP


- X - - -



- X - - - X


5.46.1 Description

Improved Bandwidth Usage (requires BTS 12B for some parts)

OMT offers a lot of functions for the user. Some of these OMT functions take long time. Display log, Install IDB and Read IDB are examples of such functions. To make Install IDB, Read IDB and Display log faster the bandwidth used in the OMT-RBS communication is reduced and optimised. This is supported in BTS 12A

OML and RSL signalling can be disturbed if Remote OMT over IP signalling is performed on the same timeslot. To make Display Faulty RUs and monitor functions to use less bandwidth and to reduce the risk that Remote OMT over IP signalling can disturb OML and RSL signalling the OMT-RBS communication is reduced and optimised. This enhancement requires BTS 12B












109 (175)






5.46.2 Operations

See description.


The �Improved Bandwidth Usage�� functionality is supported for all RBS 2000 configurations.


5.47 Self Configuring Transcoder Pools


- X - - -



X - X - X


5.47.1 Description

This feature allows the BSC to issue an observation alarm indicating an under-utilized pool, called �surrendering pool�, where it is possible to �steal� resources from and a congested pool, called �receiving/destination pool�, that needs more resources. The OSS is then triggered to perform the reconfiguration of the hardware and the change in configuration of the pools in an automated way.



110 (175)

The introduction of TFO will have an impact on this feature. When TFO is activated number of transcoder resources per MUX group will be reduced (from 24 to 16) for TRA R6 that belongs to EFR, AMR HR and AMR FR pools. For TRA R6B the capability is still 24 per MUX group independent of TFO is activated or not.

5.47.2 Operations

When an observation alarm is issued a one MUX group reconfiguration is ordered by indicating the surrendering pool, the receiving pool and the current number of transcoder resources for both pools.

Then the OSS starts its script by considering 24 or 16, indicated in the observation alarm, to reconfigure the involved pools and after a successful reconfiguration BSC reports that the number of transcoder resources for the surrendering/receiving pool has been decremented/incremented by 24 or 16.

Impacted Printouts

• Radio Transmission Transcoder Pool Details; add in the printout the new information about TFO.

• Radio Transmission Transcoder Pool Self Configuration Log, new format for the result printout of command RRPLP

• Radio Transmission Transcoder Pool Self Configuration. The SCTRAP observation alarm printout shall be updated to print parameters CHRATE and SPV also for the surrendering pool. The SNT variant shall be added as well.

• Radio Transmission Transcoder Pool Self Configuration Timeout. The SCTRAP timeout alarm printout shall be updated to print parameters CHRATE and SPV also for the surrendering pool. The SNT variant shall be added as well.

When the operator assign transcoder resources to a transcoder pool the capability for the TRA (TFO or not TFO capable) is considered. The TRA is then assigned to the correct sub-pool depending of the capability.


The impact on this feature is due to the introduction of TFO.

5.48 SGSN in Pool Support in BSC


- X - - X



111 (175)



X - X - X X


5.48.1 Description

SGSN in Pool Support in BSC introduces the possibility to connect a number of NSEs to one BSC. Up to 16 NSEs can be connected to one BSC and each NSE can serve mobile stations in the whole BSC radio coverage area. This feature is supported when the Gb interface, between BSS and SGSN, is implemented over IP.

An identifier defines each connected NSE. Each connected NSE has a number of remote IP endpoints where signalling and data can be transmitted. Up to 32 remote IP endpoints per NSE can be supported.

Each cell with GPRS service is configured in all connected NSEs. For each defined NSE, there is one BVC, representing the cell with GPRS service. Each NSE has also one signalling BVC defined (BVC0).

SGSN Selection Function in BSS

The BSC node selects the specific NSE node to which LLC frames are routed. To be able to select an NSE in a pool of SGSNs, the NRI is used for PDUs with a TLLI field.

The number of bits out of the TLLI, which is significant for the NRI, is configured in the BSC.

The SGSN Selection Function should find an available NSE either by manually configured NRI values defined in a routing table or by a load balancing. If no NSE is configured for a received NRI or if the first pointed out NSE is not available the load balancing is used to find an available NSE. The load balancing will spread the traffic load over the available NSEs.

Routing Table

A routing table controls the uplink PDUs. The routing table is always used for all TBFs as a first step. The routing table can select an NSE, normally for all MSs that are already registered in the pool.

If an available NSE is found in the routing table for the corresponding NRI, the PDU is directed to that NSE. If not an available NSE is found, an NSE is selected by load balancing as a second step.

Load Balancing



112 (175)

The BSC node distributes the load between the available CN nodes for all MSs that are not already registered in the pool or in exceptional cases, the pointed out NSE, is not available. E.g. new mobile stations coming into the pool area or blocking of communication to one NSE connected to the BSC. That is, an available NSE cannot be found for the received TLLI, and the BSC has to find an available NSE for that MS.

The NSEs capacity is not considered from BSS. The load balancing will consider the number of NRI values representing an NSE. BSS will not support any re-distribution for already registered MSs, e.g. if the traffic level will become unequal between the NSEs.

5.48.2 Operations

In general the commands described in Gb over IP are also needed for the SGSN in Pool Support in BSC.

Administration of Core Network Routing Data

The existing command family for Administration of Core Network Routing Data, used for MSC in Pool will be used to administer NS Entity routing parameters. With this family of commands it shall be possible to Initiate, Change, End and Print all parameters related to the routing of traffic to a specific peer NS Entity (SGSN).

RRNRI:NSEI=nsei,NRI=nri�.;

This command makes it possible to connect an NS Entity to one or several NRI values.

RRNRE:NSEI=nsei,NRI=nri...;

This command removes the connection between one, several or all NRI values and one NS Entity.

RRNRP:[NSEI=nsei];

This command makes it possible to Print all NS Entity routing parameters associated to one or all NS Entities.

RRNLC:[SGSNNRILENGTH=sgsnnrilength];

This command makes it possible to change the NRI length used by all SGSNs and BSCs in the SGSN pool area.

RRNLP;

This command prints the SGSN NRI length and the MSC NRI length.



113 (175)

The operator must configure the SGSNs connected to BSS. The network planner will need to plan the introduction and expansion of SGSN pools in the network. This includes planning of the NRI values so that no NRI is re-used in neighbouring pools. He also needs to be able to use the statistics for SGSN Pool for monitoring of SGSN selection and P-TMSI based routing. This statistics is provided by the SGSN and can be retrieved from OSS.

When the SGSNs are configured in BSS, the operator can activate the SGSN in Pool Support in BSC.

Alarms are generated from the BSC and transferred to OSS when the BSC has lost contact with any IP endpoint, when any NSE is lost and when the whole pool is lost.

The transmission planner will need to plan the Gb interface and changes within an IP network.

OSS Support of Use Cases

OSS will support the following use cases with respect to procedures for configurations, consistency checks etc:

• Maintenance of SGSN pool member

• Load balancing within SGSN pool � by moving active mobiles

• Remove SGSN node from SGSN pool

• Remove BSC from SGSN pool

• Add new BSC node to SGSN pool members

• Add SGSN node to SGSN pool

• Check SGSN pool consistency

• Export pool configuration

The support is implemented in ARNE, ONE and mainly in GPRS-CM.


All nodes in the SGSN pool need to be updated with software to support SGSN Pool before the pool can be activated.

SGSN in Pool Support in BSC is compliant with Release 5 of the 3GPP Technical Specification 23.236 and Release 6 of 48.016.



114 (175)

If some nodes in a pool are not consistently configured regarding NRIs or not taken into operation at the same time, the traffic distribution will not work as planned. The BSC will start using P-TMSI based routing as soon as the feature is activated but if the P-TMSI is not received as intended (wrong NRI or wrong format of NRI) the BSC will either choose a new SGSN according to SGSN selection or chose the wrong SGSN. Both cases lead to unnecessary signalling and shuffling of subscribers between SGSNs.

However, OSS supports consistency check for NRI settings between the nodes.


The SGSN Pool feature is designed in SGSN R6.


FAJ 121 665 BSC IP Connectivity and FAJ 121 786 Gb over IP are prerequisites for SGSN in Pool Support in BSC.

5.49 Single Phase Access for EGPRS


X X - X -



X X X - - X


5.49.1 Description

This feature aims to improve the latency characteristics of BSS to be better suited to the requirements of delay sensitive services like EIT. Improvements are made in the following areas:

• Decreased TBF establishment time for EGPRS MSs

• Quicker acquisition of MS capabilities

The feature is divided in the following two sub-features.

EGPRS Access on CCCH



115 (175)

Currently EGPRS capable mobiles are not allowed to use one-phase access in cells where PBCCH is not present. This sub-feature introduces support of the message EGPRS Packet Channel Request on CCCH. With use of this message an EGPRS MS may indicate one-phase access and be assigned an uplink TBF directly in EGPRS mode.

The EGPRS access time on CCCH will be reduced with up to 300 ms compared to doing a two-phase access.

Improved acquisition of MS Radio Access Capabilities

In the case where a mobile establishes an UL TBF using 1-phase access it is quite likely that the MS Radio Access Capabilities (MS RAC) are not known in the BSS.

If the Radio Access Capabilities are not known when the UL TBF is to be released it is not possible to enter extended UL TBF mode. Extended UL TBF mode would be beneficial for EIT since the establishment of an EIT session includes extensive signalling followed by a media stream. If the UL TBF is maintained during the establishment phase the overall delay would be significantly improved.

For EGPRS capable mobiles, making a 1-phase access, it is possible to request the MS RAC from the MS. This is done with the Access Technologies Request IE set in the either Packet Uplink Assignment or Immediate Assignment depending on whether MPDCH is used or not.

Note that when an uplink TBF is set-up with 2-phase access the MS RAC will be known before BSS has to take the decision whether to let the MS enter Extended UL mode or not.



The support of EGPRS Packet Channel Request on CCCH requires that the BCCH/CCCH is configured on a Power PC-based TRU, i.e. dTRU, dTRUe, RRU and sTRU.

To activate this sub-feature, a TRU capable of EGPRS Packet Channel Request shall be chosen for configuration of BCCH/CCCH (if such a TRU is available).

If no TRU capable of EGPRS Packet Channel Request is available or when the feature is turned off, a TRU with least GPRS/EGPRS capabilities will be chosen for configuration of BCCH/CCCH.

The configuration is done automatically when the new cell parameter EACPREF is set to ON.

5.49.3 Operations

Improved acquisition of MS Radio Access Capabilities



116 (175)

The following new BSC exchange parameters are introduced for this subfeature.

MSRACREQPCCCH Turn on/off per BSC when PBCCH is used

MSRACREQCCCH Turn on/off per BSC when CCCH is used


The feature is controlled via parameter EACPREF in command RLBDC. This parameter activates/de-activates the feature on cell level from the BSC and OSS-RC. Changing the parameter is only allowed in a halted cell.

The parameter is also included in the corresponding printout RLBDP.

5.49.4 Interface

With the introduction of sub-feature EGPRS Access on CCCH the message EGPRS Packet Channel Request will now be possible to use also on CCCH.


FAJ 121 31 EGPRS is required.

5.50 Smooth GSM to WCDMA Unloading


X X X - -



X - X - X X


5.50.1 Description

With the feature �Smooth GSM to WCDMA unloading�, the number of handovers to trigger per second can be limited. Hence the GSM network is unloaded smoothly preventing all multi-RAT mobiles to be handed over to WCDMA when the load criterion in �GSM-UMTS cell reselection and handover� is fulfilled.

This feature does not limit the number of urgency handovers to WCDMA.



117 (175)

Incoming handovers due to load in WCDMA (indicated by cause Directed Retry or Reduce Load in Serving Cell) are only accepted when the load is low in the GSM cell (criterion in �GSM-UMTS cell reselection and handover� is not fulfilled).

5.50.2 Operations

The COD RLLOC and POD RLLOP has been updated with the new parameter MAXISHO

The AI for ROEPC shall be updated with the new exchange property COEXUMTSLSH.

A new R-PMO event is added; the event indicates when the maximum number of handovers to UTRAN, given by MAXISHO, has been reached


Since this feature might reject incoming handovers from UTRAN, the handover statistics in the UTRAN system might be affected negatively.

Since this feature limits the number handovers, the number of handovers to UTRAN might decrease.


MSC R12 needed to map cause values between BSSMAP and RANAP correctly (according to TS 29.010).

UTRAN P3 needed to trigger handovers due to load (cause Directed Retry sent by UTRAN).


The feature FAJ 121 57, GSM-UMTS cell reselection and handover, should be activated.

If feature FAJ 121 835, Handover with Usage of Service Indicator, is used and Service Handover IE is set to any value the incoming handover is accepted without considering load (ISHOLEV) in the GSM cell.

5.51 Speech Quality Supervision


X - X - -



118 (175)



X X X - - X


5.51.1 Description

New quality measures will be introduced based on a new type of measurement report from the mobile, Enhanced Measurement Report, which is introduced by the BSS R12 feature EMR.

The new quality measures are:

• FER (introduced in MRR/MRR, STS/NWS, and RTED/R-PMO)

• Drops due to FER (introduced in STS/NWS and RTED/R-PMO)

• SQI DL (introduced in STS/NWS, RTED/R-PMO, and MTR/MTR)

The introduction of FER will be done as to resemble RXQUAL implementation, Drops due to FER will be fitted together with the existing Drops due to cause, and SQI DL will be introduced in the same way as existing SQI UL.

The SQI thresholds are revised for Good (to 22.5 dBQ) and Unacceptable (to 13.5 dbQ) categories also the punishment of the SQI value at handover is removed.


When this feature is introduced, the feature EMR must be switched on and the exchange property SPEQINDCOLLECT activated in order to get any FER data for the DL, drop statistics due to FER or SQI DL data. It is also necessary with mobiles that can provide Enhanced Measurement Reports.

SQS will be supported on all RBS 2000 except for RBS 2301 < R6A.

5.51.3 Operations

The following OPIs are changed:

• BSC, Speech Quality Supervision, Initiate

• BSC, Speech Quality Supervision, End

The following OPI is new:



119 (175)

• BSC, Speech Quality Supervision Data, Change

The following CODs are changed:

• RAMDC, Radio Control Administration, Measurement Result Recording, Change

• RLLFC, Radio Control Cell Locating Filter Data, Change

The following CODs are new:

• RLSQC, Radio Control Cell, Speech Quality Supervision, Change

• RLSQP, Radio Control Cell, Speech Quality Supervision, Print

The following PODs are changed:

• Cell Locating Filter Data

• MTRFIL

• Measurement Result Recording Definition Data

• MRRFIL

The following POD is new:

• RLSQP, Speech Quality Supervision Data


157 new STS counters per cell are introduced.

194 new MRR counters per channel group are introduced.


SQS will be supported on all RBS 2000 except for RBS 2301 < R6A.


Requires the feature FAJ 121 821 Enhanced Measurement Reporting.

PMR, RNO, R-PMO, and NWS in OSS-RC are affected by this feature.



120 (175)

5.52 Support for 1024 Cells in BSC


X X X - X



X - X - - X


5.52.1 Description

This feature increases the BSC/TRC system limit for maximum number of supported internal cells from 512 to 1024. In addition, the BSC/TRC system limit for external cells has been increased from 512 to 2048 and the system limit for neighbouring cell relations have been increased from 8192 to 32768. OSS is adapted to support the increase of cell and cell relation objects.

The system limits for external UTRAN cells and UTRAN cell relations were already increased in BSS R11 and are therefore not impacted.

The main advantage of this feature is that it makes operators less restricted in their cell planning. While 512 cells are thought to give enough flexibility for the average operator, BSC nodes that can handle more cells have definite benefits in situations where the number of TRXs grows above 1020.

BSC nodes that handle more cells than the current 512 are likely to also be of advantage in network scenarios where multiple core networks share a common BSS.


APG40 is recommended to use when supporting large number of cells and cell relations due to the increased number of STS counters.

5.52.3 Operations

The following Operational Instructions are updated

• BSC, GPRS Statistics Data Measurements, Administer

• BSC, Speech Quality Supervision, End



121 (175)

• BSC, Speech Quality Supervision, Initiate

The following Command Descriptions are updated:

• RLNRI: Radio Control Cell, Neighbouring Relation, Initiate

• RLDEC: Radio Control Cell, Description Data, Change

• RAPTI: Radio Control Administration, Call Path Tracing in BSC/TRC, Initiate

The following Printout Descriptions are updated:

• CERFIL

• CTRFILE

• MTRFIL

The following Adaptation Directions is updated:

• Mobile Telephony Data: Addition of a Cell to the BSC


Since many statistical counters are available on a per cell basis, there is a large impact on the total number of counters in the system. For a BSC/TRC supporting 1024 internal cells and 32768 neighboring cell relations, the counters related to internal cells are increased by approx. 400 000 and the counters related to neighboring cell relations are increased by approx. 450 000 compared to BSS R11. The total maximum number of STS counters supported is 1 900 000 from one BSC with APG40 (IOG limitation is unchanged in R12) (see explanation in chapter 3.1.1). In case the limit has been reached and not all counters were possible to fetch from STS an alarm will be raised.


This feature is only supported for the following platforms: APZ 212 30, APZ 212 33 and APZ 212 33C. APZ 212 20 and APZ 212 25 are not supported for this feature.

5.53 Support for 8000 EGPRS Time Slots


- - X - -



122 (175)



X - X - - X


5.53.1 Description

With the introduction of the feature �Mega BSC � Support for 2000 TRXs� in R11 the number of TRXs, and thereby also the number of BPCs, that a BSC supports was doubled compared to R10. The share of BPCs that can be used for GPRS/EGPRS traffic was thus decreased with 50% in R11. To be able to use the same share of BPCs for GPRS/EGPRS traffic as in R10, the maximum number of PDCHs that the PCU can handle is doubled. This is done by extending the system limit from 64 RPPs to 128 RPPs.

The upgrade to 128 RPPs is only valid for HWM501 cabinets.


The capacity of the BSC to handle GPRS/EGPRS traffic is doubled.

If there is one dedicated master RPP for R-PMO there might be limitations in handling events from all RPPs when there are 128 RPPs in the PCU.

5.54 Support of AXE 810 � APT 1.5


X - - - X



X - - - - -


5.54.1 Description

NNRP5 consist of a multiplexer (EMUX unit) between DL3 and DL34 interfaces in order to connect GEM-based devices to AXE10 nodes built upon the BYB501 group switch (GS10/GS12).



123 (175)

For the customer this solution will appear as a new GEM magazine connected to the old group switch.

Each EMUX unit can handle either

• combinations of ET155-1 ETSI and TRA R6/R6B or

• only ET155-1 ANSI

To connect both ET155-1 ANSI and TRA R6/R6B to the same node separate EMUX units (software) and cabinets are needed.

Max two GEM�s per cabinet gives a TRA R6/R6B capacity of maximum 3072*2 channels.


See description.

5.54.3 Hardware

A new multiplexer (EMUX unit) between DL3 and DL34 interfaces in order to connect GEM-based devices to AXE10 nodes built upon the BYB501 group switch is introduced.


NNRP5 should not be used together with NNRP4. The difference between the two processes is that NNRP4 converts the AXE10 BYB501 node to an AXE810 node. Using NNRP5 the node will remain an AXE10 BYB501 node.

5.55 Tandem Free Operation


X X X - X



X X X - X X




124 (175)

5.55.1 Description

Tandem Free Operation (TFO), as specified by 3GPP, is intended to avoid the traditional double speech encoding/decoding in MS to MS call configurations in GSM (or MS to UE for GSM/WCDMA or UE to UE for WCDMA networks).

In a normal MS to MS call configuration the speech signal is first encoded in the originating MS, sent over the air interface, coded into G.711 PCM format, carried over the fixed network, transcoded again in the distant transcoder, sent over the distant air interface and finally decoded in the terminating MS. In this configuration, the two speech codec are in �Tandem Operation�. The major drawback of a tandem configuration is the speech quality degradation introduced by the double transcoding.

Both encoding functions can be bypassed if the originating and terminating connections are using the same speech codec. Then it is possible to transmit transparently the speech frames received from the originating MS to the terminating MS without activating the transcoding functions in the originating and terminating networks. In this configuration, �Tandem Free Operation� is ongoing.

Figure 4 below provides a reference model for the functional entities handling TFO in a GSM network.

IPE

IPE

PCM Samples

TFO_Messages

TFO_Frames

64 kBit/s

64 kBit/s

TFO_Protocol

DL_TFO

UL_TFO

Decoder

Encoder

TFO_Protocol

DL_TFO

UL_TFO

Decoder

Encoder

TRAU B TRAU A

UL_TRAU Frames

DL_TRAU Frames

DL_TRAU Frames

UL_TRAU Frames

BTS B

Mobile B

BTS A

Mobile A

Encoder

Decoder Encoder

Decoder

Digital Network

BSC A MSC A BSC B MSC B

1st Radio Interface 2nd Radio Interface

Figure 4 Tandem Free Oeration in GSM (3GPP 28.062)



125 (175)

The TFO solution supports 64kbit/s PCM TS on the A interface. During the negotiation phase a number of different TFO messages is sent over the A interface between the local and distant transcoder. All TFO messages are transferred within the LSB of PCM samples, by replacing the LSB of every 16th consecutive PCM sample with the TFO message. That small in-band signalling channel causes a slight distortion, which is de facto inaudible.

Once TFO is negotiated, TFO frames are exchanged between the transcoders. The TFO negotiation reserved the necessary transport channel inside the 64 kbit/s PCM channel, 8 or 16 kbit/s sub-multiplexing, which are mapped on the LSBs (one for 8 kbit/s, two for 16 kbit/s) of the PCM signal. The TFO frames, that contains compressed speech, uses this transport channel inside the PCM channel. The other bits of the PCM samples remain unaltered and contain the traditional narrowband version of the speech signal that shall be used when a TFO break happens.

For MS to MS calls TFO provides optimal speech quality due to less transcoding within the end-to-end speech path. The speech quality gain will be most noticeable for the lower codec rates of AMR codec type as long as the TFO session remains established, i.e. as long as the end-to-end TFO transparency between the local and distant transcoder is maintained.

TFO alone does not provide any transmission bandwidth saving because the TFO frames, compressed speech, are still encapsulated into 64 kbit/s PCM signal. TFO will give substantial transmission gains in a Ericsson Mobile Softswitch Solution (MSS) with IP transmission in the core network implementing TrFO or similar.


TFO will only be supported on TRA R6 and R6B.

MCC (Mobile Cross-talk Control) is only supported for EFR (not for AMR HR or AMR FR). If used together with AMR HR or AMR FR the TFO session will not break but acoustic echo from MS (if present) will not be removed.

When TFO is configured number of transcoder resources per MUX group will be reduced (from 24 to 16) for TRA R6 that belongs to EFR, AMR HR and AMR FR pools.

TFO will be supported on all RBS 2000 except for RBS 2301 < R6A.

Transcoder pools must be configured for TFO capable devices.



126 (175)

The Line Speech Level (LSL) shifter function allows adapting the incoming/outgoing PCM samples to a desired volume level. The LSL is transparent to TFO, meaning that the LSL acts on the 6 most significant bits of each PCM sample leaving unaltered the 2 LSB carrying the TFO frames. So in principle it is possible to use the LSL together with TFO because it does not destroy TFO frames. However the usage of the LSL with TFO could affect the speech quality because the speech volume is modified only on the PCM stream and not on the TFO frames. So, during a TFO break or when TFO synchronization is lost (i.e. when the PCM is used) the user may notice a sudden change of the received speech volume, depending on the value of the LSL. For this reason it is preferable not to use LSL when TFO is activated

5.55.3 Operations

New exchange properties

The operator can turn on/off the feature per BSC. A new BSC exchange property, TFOSTATUS, shall be introduced to activate TFO support in a BSC for EFR, AMR-FR and AMR-HR codec types for transcoders based on R6 HW platform (TRA R6 and R6B).

Another BSC exchange property, PCMLAW, shall be introduced to set the proper PCM law type, A-Law or µ-Law, on the A-interface.

A third BSC exchange property, TFOCONFIGTRA, shall be used to indicate if TRA R6 shall be configured to handle TFO or not (R6B does not need this extra configuration due to no capacity reduction when TFO is activated).

A fourth exchange property, TFOPRIO, is used to prioritise TFO before a number of handover cases for AMR HR and FR. These handover cases are:

• DYMA (FR to HR Adaptations)

• HR Packing

• Cell Load Sharing

• Sub-cell Load distribution

TFO for AMR HR and FR is also prioritised before new handover cases introduced by other features in R12:

• Intra cell handover due to TCH optimization (Channel Repacking)

• Dynamic HR Allocation from Abis (Abis triggered HR Allocation)

• Dynamic FR/HR Mode Adaptation from Abis (Abis triggered HR Allocation)

Impacted Command



127 (175)

• RRTPP, add new optional parameter DETAIL. This parameter specifies the TFO capability and PCM law usage for the devices in the transcoder pool.

Impacted Printouts

• Radio Transmission Transcoder Pool Details; add in the printout the new information about TFO and PCM law.

• Radio Transmission Transcoder Pool Self Configuration Log, new format for the result printout of command RRPLP

• Radio Transmission Transcoder Pool Self Configuration. The SCTRAP observation alarm printout shall be updated to print parameters CHRATE and SPV also for the surrendering pool. The SNT variant shall be added as well.

• Radio Transmission Transcoder Pool Self Configuration Timeout. The SCTRAP timeout alarm printout shall be updated to print parameters CHRATE and SPV also for the surrendering pool. The SNT variant shall be added as well.

Impacted Operational Instructions

• BSC, Tandem Free Operation, Activate, describes the procedure to activate TFO in the BSC.

• BSC, Tandem Free Operation, Deactivate, describes the procedure to deactivate TFO in the BSC.

• BSC Tandem Free Operation, Change describes the procedure to change TFOPRIO exchange property in the BSC.

New STS counters

2 new STS counters are defined:

• Number of TFO establishment attempts

• Number of TFO successful establishment attempts


TFO messages are transferred within the LSB of the PCM samples by replacing the LSB of every 16th consecutive PCM sample with the TFO message. This small inband signalling causes a slight distortion, which is de facto inaudible.

When TFO is configured number of transcoder resources per MUX group will be reduced (from 24 to 16). This is valid for TRA R6 that belongs to TFO capable EFR, AMR HR and AMR FR pools. This leads to a maximum reduction of channels per board from 192 to 128, if all MUX groups for that board are configured for TFO (EFR, AMR FR or AMR HR).



128 (175)

5.55.5 Hardware

This feature is possible to use on old BYB501 nodes. This requires that the NNRP5 solution is used be to connect TRA R6 and R6B to the BYB501 Group Switch.


TFO will only be supported on TRA R6 and R6B.

TFO will be supported on all RBS 2000 except for RBS 2301 < R6A.

In Path Equipment in the Core Network must be TFO compliant.


In the MSC the ECP must be of version 5 or later.

If MSS is used MSS 4.1 (MSC Server 12.1, MGw 4.1) is the first version that is TFO compliant.


For MSS the CN feature TrFO is also needed to gain transmission bandwidth saving.

The introduction of TFO will have an impact on the SCTRAP feature FAJ 121 356.

The features FAJ 121 329 EFR, FAJ 121 055 AMR and FAJ 122 358 AMR HR is required to be able to use TFO for respective speech codec.

5.56 Tight BCCH Frequency Reuse


- X - X -



X - X - - X




129 (175)

5.56.1 Description

Tight BCCH Frequency Reuse is a new, optional feature that replaces �BCCH in Overlaid Subcell�. It will be possible to separately apply the pathloss and DTCB criteria to the channel group 0 and by doing this traffic channels could be restricted on the BCCH frequency and the BCCH frequency plan could be tightened, regardless of the subcell structure, i.e. even within a multi band cell. If the calculated pathloss exceeds the new cell parameter BCCHLOSS, the channel group 0 is evaluated as not suitable for this call and moved to another channel group. The DTCB criterion and the new parameter BCCHDTCB will work in a similar way. There are new additional parameters, BCCHREUSE, BCCHLOSS, BCCHLOSSHYST, BCCHDTCBN, BCCHDTCBP, BCCHDTCBHYST.

5.56.2 Operations

The following command is modified following the introduction of this feature RLLOC.

The following printout descriptions are modified �CELL LOCATING DATA�, �CTRFILE�, �MTRFIL�.

The following Application Information is modified, �RCS, RCQS Cell Data�.

PMR and NCM (CNA, CNAI) in OSS are modified to support the feature.

Four new STS counters, BCDTCBCOM, BCLOSSCOM, BCDTCBSUC and BCLOSSSUC added to existing DID CELEVENTICNT (Object type CELEVENTI).

5.56.3 Interface

PMR Export of CTR/MTR/CER Recording Results external interface in OSS is updated.


PMR in OSS is updated.

5.57 Traffic Level Measurement Data


- X - X -

Dependencies BSC BTS OSS SMPC Other Network elements

Other features



130 (175)

X - - X X


5.57.1 Description

This is a new interface, also called Open Event Notification (OEN), to be used together with GMPC 9.02. The interface provides a basic measurement report containing cell id and TA (Timing Advance) in real time for all active CS connections in a BSC to GMPC.

5.57.2 Operations

The new interface is possible to turn on/off per BSC by an exchange property.

5.57.3 Interface

Through an IP interface in the BSC, GMPC 9.0 can be feed with simplified measurement reports.


The e2e solution requires GMPC 9.0 that provides the external interface to be used by the operator.


The feature FAJ 121 50, Real Time Event Data (requires FAJ 121 665 BSC IP Connectivity) is required in BSS. In MPS (Mobile Positioning System) the feature INF 901 2472, Anonymous Bulk Location Data Support is required.

5.58 Voice Group Call Services


- X X X -

Dependencies BSC BTS OSS SMPC Other Network elements

Other features

2 The support for this feature might be added in GMPC version 8.0, but it is currently not decided.



131 (175)

X X X - X -


5.58.1 Description

A voice group call in VGCS is a multi-party call where only one subscriber is allowed to talk at a time, while the rest is only listening. Circuit switched (CS) channels are used. A voice group call can be spread over several BSCs and MSCs. A BSC is typically connected via a relay MSC to the anchor MSC. The speech from the talker is through connected in the anchor MSC to all other MSCs and BSCs involved in the group call.

The subscribers participating in a group call are located in a specified group call area (GCA).

If there are several participants in the same cell, all are listening to the same downlink (DL) VGCS channel. One participant in the call is allowed to talk at a time and then gets access to an uplink (UL) channel. Access to the uplink is requested with a kind of push-to-talk button.

A group call can be initiated by any one of the participants in the group. A group call is normally terminated by the initial caller but can also be terminated by the network in case an abnormal situation occurs.

When a group call is initiated information of the started group call is broadcast on the notification channel (NCH) on the BCCH timeslot in all cells of the group call area. Notification of the new call is also sent on the FACCH of all ongoing group calls in these cells. MSs capable of VGCS but currently involved in a dedicated call will be notified on the FACCH of that call. The MSs thus notified of the new call can then choose to join the group call or not.

In addition to normal participants, there may be dispatchers connected to the call via normal duplex connections, mobile or fixed. The dispatchers may talk, and be heard, at the same time as the currently talking subscriber.

The feature is marketed as the optional feature Professional Mobile Radio. The implementation of Professional Mobile Radio follows the VGCS/VBS standard quite closely. In the Ericsson implementation the option to have the talker on a separate channel has been selected. (The standard also allows the talker on the uplink of the VGCS channel.)

(ASCI as defined in 3GPP consist of VGCS, VBS and eMLPP. Only VGCS is considered in this document.)

5.58.2 Operations

The operator can activate the feature per BSC (new command RLVGI).



132 (175)

The operator can deactivate the feature per BSC (new command RLVGE).

With the new command RLVGC the operator can set, per BSC, the repetition period for notifications into ongoing group calls, the lowest priority for notification into ongoing group calls and p-t-p calls and the lowest priority of p-t-p calls for paging into ongoing group calls.

In another format for the same command the repetition period for notifications on the NCH, the preferred frequency band and preference for the BCCH frequency for the VGCS channel can be set per cell.

The operator can print all parameters above with command RLVGP.

The following new events on cell level are introduced:

• VGCS Notification (for new VGCS calls)

• VGCS Call Release

• VGCS Channel Setup

The following new cell counters are introduced:

• TASSATTVGCS � number of attempts to set up a VGCS call

• TASSSUCVGC - number of successful VGCS call set-ups


The main impact comes from the pagings for point-to-point calls sent on the FACCH of the VGCS channels. If many VGCS calls are ongoing in the BSC the paging load could be increased considerably. It is therefore important the parameter defining the minimum eMLPP priority level for the pagings to be sent on these channels is set well above the priority level for normal calls.

5.58.4 Interface

New messages on the A-interface

VGCS/VBS SETUP

VGCS/VBS SETUP ACK

VGCS/VBS SETUP REFUSE

VGCS/VBS ASSIGNMENT REQUEST

VGCS/VBS ASSIGNMENT RESULT

VGCS/VBS ASSIGNMENT FAILURE



133 (175)

VGCS/VBS QUEUING INDICATION

UPLINK REQUEST

UPLINK REQUEST ACKNOWLEDGE

UPLINK REQUEST CONFIRMATION

UPLINK RELEASE INDICATION

UPLINK REJECT COMMAND

UPLINK RELEASE COMMAND

UPLINK SEIZED COMMAND

Updated messages on the A-interface

ASSIGNMENT REQUEST

COMPLETE LAYER 3 INFORMATION

HANDOVER COMMAND

HANDOVER REQUEST

HANDOVER REQUIRED

New messages on the BSS-MS interface

IMMEDIATE SETUP

IMMEDIATE SETUP 2

NOTIFICATION/FACCH

NOTIFICATION/NCH

SYSTEM INFORMATION TYPE 10

TALKER INDICATION

UPLINK ACCESS

UPLINK BUSY

UPLINK FREE

UPLINK RELEASE

VGCS UPLINK GRANT

Updated messages on the BSS-MS interface



134 (175)

ASSIGNMENT COMMAND

CHANNEL RELEASE


The BSS must be connected to an MSC supporting VGCS. The relay and anchor functionality can be hosted in one and the same MSC.

MS supporting VGCS (R4) with a dedicated TCH for the talker is needed.

6 Parameters Changes Parameter changes are described in the following documents:

• User Description, Radio Network Parameters & Cell Design Data For Ericsson's GSM [2]

• Changes to the Operator Interface for the BSC [3]

• Changes on BSC SAE settings are listed in Application Information, Size Alteration events in BSC/TRC [6]

• Changes on BSC Exchange Properties are listed in Application Information (AI2), ROS, Exchange property Commands Changeable Exchange Adaptation [7].

• Changes on BSC AXE parameters due to new features are listed in Ordering Information for the BSC [8] (Ericsson personal only).

7 STS Counter Changes

7.1 Modified Counters

7.1.1 Object Types with Some Modified Counters

The following object types have some modified counters and the modifications are highlighted by bold face (where applicable).

Object Type CELLFLXAB

Function Flexible Abis connections per cell.

Counter Name Level Size Type Description

FLX16ATT Cell 16 Peg Number of attempts to allocate a 16k flexible Abis paths for PS



135 (175)

FLX16SUCC Cell 16 Peg Number of successful allocations of a 16k flexible Abis path for PS

Object Type CELLGPRS

Function GPRS counters per cell


TBFPREEMPEST Cell 32 Peg

Accumulated time between a TBF release due to PDCH preemption either due to CS channel congestion or Abis congestion (for CS only) or PCU overload protection, and a successful TBF establishment.

PREEMPTTBF Cell 32 Peg

Number of released TBFs due to PDCH preemption either due to CS channel congestion or Abis congestion (for CS only) or PCU overload protection.

Object Type CELLGPRS2

Function GPRS counters per cell.


PREEMPTULREL Cell 16 Peg

Total number of UL TBFs abnormally relased due to preemption either due to CS channel congestion or Abis congestion (for CS only) or PCU overload protection.

Object Type LOADREG

Function Load regulation counters per BSC.


NREJEMC BSC 16 Peg Number of mobile originating emergency calls rejected by the Processor Load Control in BSC/TRC function or MSC Overload.

NREJPRIO BSC 16 Peg Number of normal originating connections rejected by the Processor Load Control in BSC/TRC function or MSC Overload.

NREJNPRIO BSC 16 Peg Number of location updates rejected by the Processor Load Control in BSC/TRC function or MSC Overload.

NREJIEX BSC 16 Peg

Number of terminating calls and number of VGCS channel allocation attempts rejected by the Process Load Control in BSC/TRC function or MSC Overload

Object Type LOAS

Function Traffic and load counters



136 (175)


NOFFIEX BSC 16 Peg Number of offered incoming call attempts and number of offered setup of VGCS channel attempts

Object Type Counter Impact Due to Feature

or Enhancement

CHGRP0F

TSQ0GOOD TSQ0AFGOOD TSQ0ACCPT TSQ0AFACCPT TSQ0BAD TSQ0AFBAD

These counters are expected to decrease since they are incremented only if there is an established speech path.

BSS R12 System

Improvements (Basic Feature)

CHGRP0H TSQ0AHGOOD TSQ0AHACCPT TSQ0AHBAD


BSS R12 System


Table 72 Object Types with some modified counters

7.1.2 Object Types with All Counters Modified

The following object types have all their counters modified.

Object Type Counter Impact Due to Feature

or Enhancement

CELLQOSG

CELLQOSEG

CLDTMQOS

All counters in the object types

All counters in these object types are expected to decrease since they are modified so that for periods where one user has an active PFC on top of another PFC with lower priority, the PFC with lower priority does not contribute to the accumulated LLC data volume and the PFC activity time.

If two PFCs with same priority exist both shall be excluded.

BSS R12 GPRS/EGPRS Improvements (Basic Feature)



137 (175)

CLRXQUAL

CELLSQI

CELLFERF

CELLFERH

All counters in the object type


BSS R12 System


Table 73 Object Types with all counters modified

7.2 New Counters in Existing Object Types The following object types have been changed by addition of new counters. A more thorough explanation of the changes and the new behaviour can be found in User Description, Radio Network Statistics, 216/1553-HSC 103 12.

Object Type BSCGPRS

Function GPRS counters per BSC


AQMDELIVDATA BSC 32 Peg Total amount of data delivered by AQM in Kbit. This is generated per BSC.

AQMRECDATA BSC 32 Peg Total amount of data received by AQM in Kbit. This is generated per BSC.

Object Type CCCHLOAD

Function CCCH Load counters per cell


DISCIMMASS Cell 16 Peg Number of discarded Immediate Assignments (for CS and PS) in the BTS.

Object Type CELEVENTI

Function Intra cell Channel Change registrations per cell.


BCDTCBCOM Cell 16 Peg Number of intra-cell handover attempt out of BCCH channel group, BCCHDTCB criteria.

BCLOSSCOM Cell 16 Peg Number of intra-cell handover attempt out of BCCH channel group, BCCHLOSS criteria.

BCDTCBSUC Cell 16 Peg Number of successful intra-cell handover out of BCCH channel group, BCCHDTCB criteria.

BCLOSSSUC Cell 16 Peg Number of successful intra-cell handover out of BCCH channel group, BCCHLOSS criteria.

HOSUCTCHOPT Cell 16 Peg Number of successful Intra Cell Handover due to TCH optimization.



138 (175)

Object Type CELEVENTSC

Function Subcell change attempts and successful subcell changes per cell.


OLSCLDCOM Cell 16 Peg Number of subcell change attempts to overlaid subcell due to subcell load distribution

OLSCLDSUC Cell 16 Peg Number of successful subcell change to overlaid subcell due to subcell load distribution.

Object Type CELLEIT2

Function Counters for measure of the performance of EIT with respect to the Push-To-TalkTM service.


ACREQEIT Cell 32 Peg Total number of Admission Control requests for EIT.

ACREJEIT Cell 32 Peg

Number of times channel resources could not be reserved for EIT service as requested due to Admission Control and the action according to the parameter EITQOSPRIO was performed.

Object Type CELLFLXAB

Function Flexible Abis connections per cell.


FLXCS16ATT Cell 16 Peg Number of attempts to allocate a 16k flexible Abis paths for CS

FLXCS16SUCC Cell 16 Peg Number of successful allocations of a 16k flexible Abis path for CS

FLX8SUCC Cell 16 Peg Number of successful allocations for an AMR FR using a 8 kbit/s Abis path




MSESTULTBF Cell 32 Peg Number of UL TBFs where the mobile has started to send data UL in the TBF.




PMTCSABCONG Cell 16 Peg Number of CS initiated preemptions of Abis



139 (175)

path done either by preemption of an idle PDCH or by downgrading of a E-PDCH not carrying any EGPRS traffic from E-PDCH to B-PDCH.

PMTPSABCONG Cell 16 Peg

Number of PS initiated preemptions of Abis path done either by preemption of an idle PDCH or by downgrading of a E-PDCH not carrying any EGPRS traffic from E-PDCH to B-PDCH.

GPRSCELLAVA Cell 16 Peg Number of five-minute intervals a cell is unavailable for GPRS

AVAILRBLKS Cell 32 Peg Number of available 20 ms RLC blocks on all allocated PDCHs (DL and UL).

USEDDLRBLKS Cell 32 Peg Number of occupied radio blocks DL

USEDULRBLKS Cell 32 Peg Number of occupied (scheduled) radio blocks UL.

LCCLRELBUSYHI3 Cell 16 Peg Number of active PDCHs released due to entering High Load Mode

Object Type CELLHCS

Function HCS counters per cell.


TIMEHCSOUT Cell 16 Peg Accumulated time in seconds when the serving cell's channel availability is below or equal to HCSOUT.

Object Type CELTCHF

Function TCH/F connections per cell.


TFNCEDROP Cell 16 Peg

Number of dropped connections that occur in underlaid subcell when a subscriber to subscriber connection is established. This is between the DTAP messages Connect Acknowledge and Release or Disconnect.

TFNCEDROPSUB Cell 16 Peg

Number of dropped connections that occur in overlaid subcell when a subscriber to subscriber connection is established. This is between the DTAP messages Connect Acknowledge and Release or Disconnect.

Object Type CELTCHH

Function TCH/H connections per cell.


THTHARDCONGS Cell 16 Peg Counts the time when all radio resources are



140 (175)

occupied (hard congestion) and an allocation attempt is made in the underlaid subcell

THTHARDCONSUB Cell 16 Peg Counts the time when all radio resources are occupied (hard congestion) and an allocation attempt is made in the overlaid subcell

THNCEDROP Cell 16 Peg

Number of dropped connections that occur in underlaid subcell when a subscriber to subscriber connection is established. This is between the DTAP messages Connect Acknowledge and Release or Disconnect.

THNCEDROPSUB Cell 16 Peg

Number of dropped connections that occur in overlaid subcell when a subscriber to subscriber connection is established. This is between the DTAP messages Connect Acknowledge and Release or Disconnect.

Object Type CHGRP0F

Function Monitor selected performance indicators separately for channel group zero.


TFFERULDIS0 Cell 16 Peg FER drop calls, FR uplink, for CHGRP0.

TFFERDLDIS0 Cell 16 Peg FER drop calls, FR downlink, for CHGRP0.

TFFERBLDIS0 Cell 16 Peg FER drop calls, FR bothlink, for CHGRP0.

Object Type CHGRP0H

Function Monitor selected performance indicators separately for channel group zero.


THFERULDIS0 Cell 16 Peg FER drop calls, HR uplink, for CHGRP0.

THFERDLDIS0 Cell 16 Peg FER drop calls, HR downlink, for CHGRP0.

THFERBLDIS0 Cell 16 Peg FER drop calls, HR bothlink, for CHGRP0.

Object Type CLDTMEST

Function Counters for DTM connection set-up attempts and successful establishments per channel service.


TDTMALLOCATT Cell 16 Peg Number of channel allocation attempt.

Object Type CLDTMPER

Function Counters for the average number of reserved PDCHs for DTM TBFs




141 (175)

MSESTULDTMTBF Cell 32 Peg Number of UL DTM TBFs where the mobile has stated to send data UL in the TBF.

Object Type CLRATECHG

Function Dynamic FR/HR Mode Adaptation connections per Cell


AMRABHOSUCFRHR Cell 32 Peg Number of successful intra cell handovers due to FR to HR channel rate change at Abis congestion made by an AMR capable mobile.

NAMRABHOSUCFRHR Cell 32 Peg Number of successful intra cell handovers due to FR to HR channel rate change made at Abis congestion by a mobile not capable of AMR.

Object Type CLSDCCH

Function Counters for SDCCHs per cell.


CSCSTCONG Cell 16 Peg Signalling Connection setup time congestion for procedures requiring a TCH.

CSCSOPTCONG Cell 16 Peg Signalling Connection setup time congestion for other procedures that can be completed on a SDCCH.

CESTCHACTIV Cell 16 Peg Number of SDDCH establishment failure that occurs under Channel Allocation and Channel Activation.

CESTIMMASS Cell 16 Peg Number of SDCCH establishment failure due to timeout after sending Immediate Assignment.

Object Type CLTCHDRAF

Function Dropped connections per cell for TCH/F


TFDISFERULA Cell 16 Peg Dropped FR AMR connections, FER uplink.

TFDISFERDLA Cell 16 Peg Dropped FR AMR connections, FER downlink.

TFDISFERBLA Cell 16 Peg Dropped FR AMR connections, FER bothlink.

TFDISFERULSUBA Cell 16 Peg Dropped FR AMR connections, FER uplink, overlaid subcell.

TFDISFERDLSUBA Cell 16 Peg Dropped FR AMR connections, FER downlink, overlaid subcell.

TFDISFERBLSUBA Cell 16 Peg Dropped FR AMR connections, FER bothlink, overlaid subcell.

Object Type CLTCHDRAH



142 (175)

Function Dropped connections per cell for TCH/H


THDISFERULA Cell 16 Peg Dropped HR AMR connections, FER uplink.

THDISFERDLA Cell 16 Peg Dropped HR AMR connections, FER downlink.

THDISFERBLA Cell 16 Peg Dropped HR AMR connections, FER bothlink.

THDISFERULSUBA Cell 16 Peg Dropped HR AMR connections, FER uplink, overlaid subcell.

THDISFERDLSUBA Cell 16 Peg Dropped HR AMR connections, FER downlink, overlaid subcell.

THDISFERBLSUBA Cell 16 Peg Dropped HR AMR connections, FER bothlink, overlaid subcell.

Object Type CLTCHDRF

Function Dropped connections per cell for TCH/F


TFDISFERUL Cell 16 Peg Dropped FR connections, FER uplink.

TFDISFERDL Cell 16 Peg Dropped FR connections, FER downlink.

TFDISFERBL Cell 16 Peg Dropped FR connections, FER bothlink.

TFDISFERULSUB Cell 16 Peg Dropped FR connections, FER uplink, overlaid subcell

TFDISFERDLSUB Cell 16 Peg Dropped FR connections, FER downlink, overlaid subcell.

TFDISFERBLSUB Cell 16 Peg Dropped FR connections, FER bothlink, overlaid subcell.

Object Type CLTCHDRH

Function Dropped connections per cell for TCH/H


THDISFERUL Cell 16 Peg Dropped HR connections, FER uplink.

THDISFERDL Cell 16 Peg Dropped HR connections, FER downlink.

THDISFERBL Cell 16 Peg Dropped HR connections, FER bothlink.

THDISFERULSUB Cell 16 Peg Dropped HR connections, FER uplink, overlaid subcell.

THDISFERDLSUB Cell 16 Peg Dropped HR connections, FER downlink, overlaid subcell.

THDISFERBLSUB Cell 16 Peg Dropped HR connections, FER bothlink, overlaid subcell.

Object Type NUCELLREL



143 (175)

Function Inter System GSM (to UTRAN) Handover per cell relation.


HOATTSHOULDUTRAN UTRAN

Cell Relati.

16 Peg Number of handover attempts to a neighbouring UTRAN FDD cell due to the Service Handover value is 'should'.

URGHOVERUTRAN UTRAN

Cell Relati.

16 Peg Number of handover attempts to the neighbour UTRAN FDD cell in case of urgency conditions.

SUCURGHOUTRAN UTRAN

Cell Relati.

16 Peg Number of successful handover attempts to the neighbour UTRAN FDD cell in case of urgency conditions.

Object Type TRAFDLGPRS

Function GPRS DL Traffic Load Counters per Cell


DLACTBPDCH Cell 16 Peg Number of B-PDCHs that carried one or more active TBFs of any mode, DL.

DLACTGPDCH Cell 16 Peg Number of G-PDCHs that carried one or more active TBFs of any mode, DL.

DLACTEPDCH Cell 16 Peg Number of E-PDCHs that carried one or more active TBFs of any mode, DL.

DLACTTBFPBPDCH Cell 16 Peg Sum of simultaneous active TBFs (all TBF modes) on each and every B-PDCH, DL.

DLACTTBFPGPDCH Cell 16 Peg Sum of simultaneous active TBFs (all TBF modes) on each and every G-PDCH, DL.

DLACTTBFPEPDCH Cell 16 Peg Sum of simultaneous active TBFs (all TBF modes) on each and every E-PDCH, DL.

Object Type TRAFGPRS2

Function GPRS Traffic Load counters Per Cell. The counters shall not be stepped for DTM connections. The counters shall exclude contribution from TBFs carrying EIT.


MUTIL15 Cell 32 Peg Number of DL TBFs scanned where 1 out of 5 PDCHs are reserved.







144 (175)

Object Type TRAFULGPRS

Function GPRS UL Traffic Load Counters per Cell


ULACTBPDCH Cell 16 Peg Number of B-PDCHs that carried one or more active TBFs of any mode, UL.

ULACTGPDC Cell 16 Peg Number of G-PDCHs that carried one or more active TBFs of any mode, UL.

ULACTEPDCH Cell 16 Peg Number of E-PDCHs that carried one or more active TBFs of any mode, UL.

ULACTTBFPBPDCH Cell 16 Peg Sum of simultaneous active TBFs (all TBF modes) on each and every B-PDCH, UL.

ULACTTBFPGPDCH Cell 16 Peg Sum of simultaneous active TBFs (all TBF modes) on each and every G-PDCH, UL.

ULACTTBFPEPDCH Cell 16 Peg Sum of simultaneous active TBFs (all TBF modes) on each and every E-PDCH, UL.

Object Type TRAPEVENT

Function Transcoder resource registrations per pool


TPTFOESTATT Trans. pool 32 Peg Number of TFO establishment attempts

TPTFOEST Trans. pool 32 Peg Number of successful TFO establishment

Table 74 New counters in existing Object Types

7.3 New Object Types These new object types and counters are described in detail in User Description, Radio Network Statistics, 216/1553-HSC 103 12.

Object Type RES64K

Function Status of the 64KRES pool of Abis paths per TG


MIN64K TG 8 ST Minimum number of idle 64 kbps Abis paths in 64KRES pool during last 15 minutes, calculated from samples taken every minute

MAX64K TG 8 ST Maximum number of idle 64 kbps Abis paths in 64KRES pool during last 15 minutes, calculated from samples taken every minute

AVG64K TG 8 ST Average number of idle 64 kbps Abis paths in 64KRES pool during last 15 minutes,



145 (175)

calculated from samples taken every minute

FRAG64K TG 8 ST Fragmentation level of the 64KRES pool, i.e. the number of fragmented (partly used) 64 kbps Abis paths in the 64KRES pool

Object Type CELLAFFER

Function FER intervals in SQS data Collection for codec type AMR FR per cell.


TAF1ULFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type AMR FR, UL.

TAF2ULFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type AMR FR, UL.



TAF5ULFER Cell 16 Peg Number of FER occurrences in the range FERTHR4-96, for codec type AMR FR, UL.

TAF1ULSUBFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type AMR FR, overlaid subcell UL.

TAF2ULSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type AMR FR, overlaid subcell UL.



TAF5ULSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR4-96, for codec type AMR FR, overlaid subcell UL.

TAF1DLFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type AMR FR, DL.

TAF2DLFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type AMR FR, DL.

TAF3DLFER Cell 16 Peg Number of FER occurrences in the range FERTHR2-FERTHR3, for codec type AMR FR, DL.

TAF4DLFER Cell 16 Peg Number of FER occurrences in the range FERTHR3-FERTHR4, for codec type AMR FR,



146 (175)

DL.

TAF5DLFER Cell 16 Peg Number of FER occurrences in the range FERTHR4-96, for codec type AMR FR, DL.

TAF1DLSUBFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type AMR FR, overlaid subcell DL.

TAF2DLSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type AMR FR, overlaid subcell DL.



TAF5DLSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR4-96, for codec type AMR FR, overlaid subcell DL.

Object Type CELLAHFER

Function FER intervals in SQS data Collection for codec type AMR HR per cell.


TAH1ULFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type AMR HR, UL.

TAH2ULFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type AMR HR, UL.



TAH5ULFER Cell 16 Peg Number of FER occurrences in the range FERTHR4-96, for codec type AMR HR, UL.

TAH1ULSUBFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type AMR HR, overlaid subcell UL.

TAH2ULSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type AMR HR, overlaid subcell UL.

TAH3ULSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR2-FERTHR3, for codec type AMR HR, overlaid subcell UL.

TAH4ULSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR3-FERTHR4, for codec type AMR



147 (175)

HR, overlaid subcell UL.

TAH5ULSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR4-96, for codec type AMR HR, overlaid subcell UL.

TAH1DLFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type AMR HR, DL.

TAH2DLFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type AMR HR, DL.



TAH5DLFER Cell 16 Peg Number of FER occurrences in the range FERTHR4-96, for codec type AMR HR, DL.

TAH1DLSUBFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type AMR HR, overlaid subcell DL.

TAH2DLSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type AMR HR, overlaid subcell DL.



TAH5DLSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR4-96, for codec type AMR HR, overlaid subcell DL.

Object Type CELLEFFER

Function FER intervals in SQS data Collection for codec type EFR


TEF1ULFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type EFR, UL.

TEF2ULFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type EFR, UL.



TEF5ULFER Cell 16 Peg Number of FER occurrences in the range



148 (175)

FERTHR4-96, for codec type EFR, UL.

TEF1ULSUBFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type EFR, overlaid subcell UL.

TEF2ULSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type EFR, overlaid subcell UL.



TEF5ULSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR4-96, for codec type EFR, overlaid subcell UL.

TEF1DLFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type EFR, DL.

TEF2DLFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type EFR, DL.



TEF5DLFER Cell 16 Peg Number of FER occurrences in the range FERTHR4-96, for codec type EFR, DL.

TEF1DLSUBFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type EFR, overlaid subcell DL.

TEF2DLSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type EFR, overlaid subcell DL.



TEF5DLSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR4-96, for codec type EFR, overlaid subcell DL.

Object Type CELLFFER

Function FER intervals in SQS data Collection for codec type FR




149 (175)

TF1ULFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type FR, UL.

TF2ULFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type FR, UL.



TF5ULFER Cell 16 Peg Number of FER occurrences in the range FERTHR4-96, for codec type FR, UL.

TF1ULSUBFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type FR, overlaid subcell UL.

TF2ULSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type FR, overlaid subcell UL.



TF5ULSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR4-96, for codec type FR, overlaid subcell UL.

TF1DLFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type FR, DL.

TF2DLFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type FR, DL.



TF5DLFER Cell 16 Peg Number of FER occurrences in the range FERTHR4-96, for codec type FR, DL.

TF1DLSUBFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type FR, overlaid subcell DL.

TF2DLSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type FR, overlaid subcell DL.

TF3DLSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR2-FERTHR3, for codec type FR, overlaid subcell DL.

TF4DLSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR3-FERTHR4, for codec type FR,



150 (175)

overlaid subcell DL.

TF5DLSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR4-96, for codec type FR, overlaid subcell DL.


Function GPRS cell counters


DLMSGTHR Cell 32 Peg Accumulated weighted LLC throughput for interactive/background, GPRS capable MSs, DL.

ULMSGTHR Cell 32 Peg Accumulated weighted LLC throughput for interactive/background, GPRS capable MSs, UL.

DLMSEGTHR Cell 32 Peg Accumulated weighted LLC throughput for interactive/background, EGPRS capable MSs, DL.

ULMSEGTHR Cell 32 Peg Accumulated weighted LLC throughput for interactive/background, EGPRS capable MSs, UL.

DLMSGDATA Cell 32 Peg Accumulated LLC data volume for interactive/background, GPRS capable MSs, DL.

ULMSGDATA Cell 32 Peg Accumulated LLC data volume for interactive/background, GPRS capable MSs, UL.

DLMSEGDATA Cell 32 Peg Accumulated LLC data volume for interactive/background, EGPRS capable MSs, DL.

ULMSEGDATA Cell 32 Peg Accumulated LLC data volume for interactive/background, EGPRS capable MSs, UL.

Object Type CELLHFER

Function FER intervals in SQS data Collection for codec type HR


TH1ULFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type HR, UL.

TH2ULFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type HR, UL.

TH3ULFER Cell 16 Peg Number of FER occurrences in the range FERTHR2-FERTHR3, for codec type HR, UL.

TH4ULFER Cell 16 Peg Number of FER occurrences in the range



151 (175)

FERTHR3-FERTHR4, for codec type HR, UL.

TH5ULFER Cell 16 Peg Number of FER occurrences in the range FERTHR4-96, for codec type HR, UL.

TH1ULSUBFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type HR, overlaid subcell UL.

TH2ULSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type HR, overlaid subcell UL.



TH5ULSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR4-96, for codec type HR, overlaid subcell UL.

TH1DLFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type HR, DL.

TH2DLFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type HR, DL.



TH5DLFER Cell 16 Peg Number of FER occurrences in the range FERTHR4-96, for codec type HR, DL.

TH1DLSUBFER Cell 16 Peg Number of FER occurrences in the range 0-FERTHR1, for codec type HR, overlaid subcell DL.

TH2DLSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR1-FERTHR2, for codec type HR, overlaid subcell DL.



TH5DLSUBFER Cell 16 Peg Number of FER occurrences in the range FERTHR4-96, for codec type HR, overlaid subcell DL.

Object Type CELLSQIDL

Function Speech quality supervision downlink per cell.



152 (175)


TSQIGOODDL Cell 16 Peg Number of measurements with good speech quality.

TSQIGOODSUBDL Cell 16 Peg Number of measurements with good speech quality in overlaid subcell.

TSQIACCPTDL Cell 16 Peg Number of measurements with acceptable speech quality.

TSQIACCPTSUBDL Cell 16 Peg Number of measurements with acceptable speech quality in overlaid subcell.

TSQIBADDL Cell 16 Peg Number of measurements with unsatisfactory speech quality.

TSQIBADSUBDL Cell 16 Peg Number of measurements with unsatisfactory speech quality in overlaid subcell.

TSQIGOODAFDL Cell 16 Peg Number of measurements with good speech quality, AMR FR.

TSQIGOODAHDL Cell 16 Peg Number of measurements with good speech quality, AMR HR.

TSQIGOODSUBAFDL Cell 16 Peg Number of measurements with good speech quality in overlaid subcell, AMR FR.

TSQIGOODSUBAHDL Cell 16 Peg Number of measurements with good speech quality in overlaid subcell, AMR HR.

TSQIACCPTAFDL Cell 16 Peg Number of measurements with acceptable speech quality, AMR FR.

TSQIACCPTAHDL Cell 16 Peg Number of measurements with acceptable speech quality, AMR HR.

TSQIACCPTSUBAFDL Cell 16 Peg Number of measurements with acceptable speech quality in overlaid subcell, AMR FR.

TSQIACCPTSUBAHDL Cell 16 Peg Number of measurements with acceptable speech quality in overlaid subcell, AMR HR.

TSQIBADAFDL Cell 16 Peg Number of measurements with unsatisfactory speech quality, AMR FR.

TSQIBADAHDL Cell 16 Peg Number of measurements with unsatisfactory speech quality, AMR HR.

TSQIBADSUBAFDL Cell 16 Peg Number of measurements with unsatisfactory speech quality in overlaid subcell, AMR FR.

TSQIBADSUBAHDL Cell 16 Peg Number of measurements with unsatisfactory speech quality in overlaid subcell, AMR HR.

Object Type CHGRP0SQI

Function Speech quality supervision downlink for channel group zero per cell.


TSQ0GOODDL Cell 16 Peg Number of measurements with good speech quality.



153 (175)

TSQ0ACCPTDL Cell 16 Peg Number of measurements with acceptable speech quality.

TSQ0BADDL Cell 16 Peg Number of measurements with unsatisfactory speech quality.

TSQ0AHGOODDL Cell 16 Peg Number of measurements with good speech quality, AMR HR.

TSQ0AHACCPTDL Cell 16 Peg Number of measurements with acceptable speech quality, AMR HR.

TSQ0AHBADDL Cell 16 Peg Number of measurements with unsatisfactory speech quality, AMR HR.

TSQ0AFGOODDL Cell 16 Peg Number of measurements with good speech quality, AMR FR.

TSQ0AFACCPTDL Cell 16 Peg Number of measurements with acceptable speech quality, AMR FR.

TSQ0AFBADDL Cell 16 Peg Number of measurements with unsatisfactory speech quality, AMR FR.

Object Type CLVGCSEST

Function Statistics about attempted and successful VGCS call set-ups per cell


TASSATTVGCS Cell 16 Peg Number of attempts for VGCS call set-ups in the cell

TASSSUCVGCS Cell 16 Peg Number of successful VGCS call set-ups in the cell

Object Type GPHLOADREG

Function GPH Overload Protection and RPP Load Distribution function counters per BSC


LCCELLMOV BSC 32 Peg Number of succeeded cell move attempt by PCU Load Control

LCCELLMOVREJ BSC 32 Peg Number of failed cell move attempts by PCU Load Control due to lack of RPP candidates with low load (only valid for force move of cell).

LCHIRPPLOAD BSC 32 Peg Increased at every 500ms interval when in any of the High Load Modes for an RPP.

LCPARREJ BSC 32 Peg Number of rejected Packet Access Request per BSC due to lack of RPP memory.

LCMSSUPRFC BSC 32 Peg The time when MS Flow Control has been sent with a reduced bucket size, due to lack of PCU-RP memory. The counter is increased by one every 20th second as long as this action is in use.

LCRELBUSYHI3 BSC 32 Peg Number of active PDCHs released due to



154 (175)

entering High Load Mode.

LCRELIDLEHI3 BSC 32 Peg Number of idle PDCHs released due to entering High Load Mode 3.

Object Type NONRES64K

Function Status of the non-64KRES pool of Abis paths per TG


MIN16K TG 16 ST

Minimum number of idle 16 kbps Abis paths in non-64KRES pool during last 15 minutes, calculated from samples taken every minute

MAX16K TG 16 ST

Maximum number of idle 16 kbps Abis paths in non-64KRES pool during last 15 minutes, calculated from samples taken every minute

AVG16K TG 16 ST

Average number of idle 16 kbps Abis paths in non-64KRES pool during last 15 minutes, calculated from samples taken every minute

Object Type TRALOST

Function Remote Transcoder Lost fault counters per BSC.


TSMODEIDLE BSC 32 Peg Number of 'Remote Transcoder Lost' fault reports for Idle TS Mode.

TSMODECS BSC 32 Peg Number of 'Remote Transcoder Lost' fault reports for Circuit Switched TS Mode.

TSMODEPS BSC 32 Peg Number of 'Remote Transcoder Lost' fault reports for Packet Switched TS Mode.

Table 75 New Object Types

7.4 Removed Counters No counters are removed.

7.5 Non Functional Changes of Counters The R12 dynamic legacy counters (i.e. old unmodified counters with changed behaviour) are specified in the table below.



155 (175)

In case there are several impacts on the same counter, the impacts are specified individually but with numbering, e.g. PSCHREQ imp-1 and PSCHREQ imp-2 etc.

Object Type Counter Impact Due to Feature or Enhancement

CELLGPRS ALLPDCHACC PDCHALLAT

There will be a decreased value of allocated PDCH since on-demand and semi-dedicated PDCHs are de-activated quicker due to changes of PILTIMER. Due to this also allocation attempts will increase.

BSS R12 GPRS/EGPRS Improvements (Basic feature)

CELLQOSEG

ULTHP1EGTHR ULTHP2EGTHR ULTHP3EGTHR ULBGEGTHR

CELLGPRS MC19ULSCHED MC19ULACK

CELLGPRSO MC19ULSCHEDSUB MC19ULACKSUB

There will be an increased UL throughput for most radio network environments when the optional feature Incremental Redundancy in Uplink is introduced. Valid if the optional feature EGPRSIRU is available (set to 1) and if the the BSC exchange property EGPRSIRUL is set to 1 (i.e. IRU activated).

Incremental Redundancy in Uplink

TRAFGPRS2

MUTIL14 MUTIL24 MUTIL34 MUTIL44

A decreased value is expected since the maximum number of reserved timeslots downlink becomes 5 (instead of 4 in the previous release) for the MS multislot classes 30-34 and 40-45. Valid if the optional feature Five Downlink Timeslots is on (GPRS5TSDL is available, i.e. set to 1 and the BSC Exchange Property GPRS5TSDLACT is set to 1)

Five Downlink Timeslots

TRAFGPRS2 MUTILBASIC MUTILGPRS MUTILEGPRS

A decreased value is expected since 2 of 5 timeslots reserve (instead of 2 of 4 in the previous release) for the MS multislot classes 30-34 and 40-45. Valid if the optional feature Five Downlink Timeslots is on (GPRS5TSDL is available, i.e. set to 1 and the BSC Exchange Property GPRS5TSDLACT is set to 1)


TRAFGPRS2 MAXGTSDL An increased value is expected Five Downlink Timeslots



156 (175)

MAXEGTSDL since the maximum number of reserved timeslots Downlink becomes 5 (instead of 4 in the previous release) for the MS multislot classes 30-34 and 40-45. Valid if the optional feature Five Downlink Timeslots is on (GPRS5TSDL is available, i.e. set to 1 and the BSC Exchange Property GPRS5TSDLACT is set to 1)

TRAFDLGPRS

DLBPDCH DLGPDCH DLEPDCH DLTBFPBPDCH DLTBFPGPDCH DLTBFPEPDCH

An increased value is expected since the maximum number of reserved timeslots Downlink becomes 5 (instead of 4 in the previous release) for the MS multislot classes 30-34 and 40-45. Valid if the optional feature Five Downlink Timeslots is on (GPRS5TSDL is available, i.e. set to 1 and the BSC Exchange Property GPRS5TSDLACT is set to 1)


CELLGPRS2 PSCHREQ imp-1 PREJOTH imp-1 PREJTFI

An increased value is expected since the counters are Incremented for EGPRS Packet Channel Requests on CCCH also. Valid if the optional feature parameter REDPACLAT is available and if the command (RLBDC) parameter EACPREF is set to YES.

Single Phase Access for EGPRS

CELLEIT

EITDLBPDCH EITULBPDCH EITDLGPDCH EITULGPDCH EITDLEPDCH EITULEPDCH

These counters might show decreased values due to this feature if the cell parameter EITEXCLUDED is set to a value greater than 0. Valid if the optional feature parameter ADMCTRL is available and if the value of the BSC exchange parameter EITADMCTRL is set to 1.

Admission Control for Push to Talk

CELLGPRS2 PSCHREQ imp-2 PREJOTH imp-2

A decreased value is expected since the counters will not incremented for ignored access requests during change of TBF mode. Valid if the value of the BSC exchange parameter TBFMODEACT is different from 0

Flexible Channel Allocation



157 (175)

(OFF).

CHGRP0F TFQADLDIS0 TFQAULDIS0 TFQABLDIS0

These counters will be stepped less than before since the corresponding FER counters (TFFERULDIS0, TFFERDLDIS0 and TFFERBLDIS0) will be stepped for drops due FER instead. Valid if the optional feature SQSSUPPORT is available.

Speech Quality Supervision

CHGRP0H THQADLDIS0 THQAULDIS0 THQABLDIS0

These counters will be stepped less than before since the corresponding FER counters (THFERULDIS0, THFERDLDIS0 and THFERBLDIS0) will be stepped for drops due FER instead. Valid if the optional feature SQSSUPPORT is available.


CLTCHDRAF

TFDISQADLA TFDISQADLSUBA TFDISQAULA TFDISQAULSUBA TFDISQABLA TFDISQABLSUBA

These counters will be stepped less than before since the corresponding FER counters (TFDISFERULA, TFDISFERDLA, TFDISFERBLA, TFDISFERULSUBA, TFDISFERDLSUBA and TFDISFERBLSUBA) will be stepped for drops due FER instead. Valid if the optional feature SQSSUPPORT is available.


CLTCHDRAH

THDISQADLA THDISQADLSUBA THDISQAULA THDISQAULSUBA THDISQABLA THDISQABLSUBA

These counters will be stepped less than before since the corresponding FER counters (THDISFERULA, THDISFERDLA, THDISFERBLA, THDISFERULSUBA, THDISFERDLSUBA and THDISFERBLSUBA) will be stepped for drops due FER instead. Valid if the optional feature SQSSUPPORT is available.




158 (175)

CLTCHDRF TFDISQADL TFDISQADLSUB TFDISQAUL TFDISQAULSUB TFDISQABL TFDISQABLSUB

These counters will be stepped less than before since the corresponding FER counters (TFDISFERUL, TFDISFERDL, TFDISFERBL, TFDISFERULSUB, TFDISFERDLSUB and TFDISFERBLSUB) will be stepped for drops due FER instead. Valid if the optional feature SQSSUPPORT is available.


CLTCHDRH THDISQADL THDISQADLSUB THDISQAUL THDISQAULSUB THDISQABL THDISQABLSUB

These counters will be stepped less than before since the corresponding FER counters (THDISFERUL, THDISFERDL, THDISFERBL, THDISFERULSUB, THDISFERDLSUB and THDISFERBLSUB) will be stepped for drops due FER instead. Valid if the optional feature SQSSUPPORT is available.


RLINKBITR All counters in the object type

All or some of the counters (dependent on the values of the parameters LOPTGTHR and LOPTETHR) are expected to have an increased value of data volume on higher bitrate levels. Valid if the optional feature parameter GPRSLOADOPT is available and the BSC exchange property LOADOPT is set to 1 or 2.

GPRS/EGPRS Load Optimization

CELEVENTSC SCLDCOMUL SCLDSUCUL

These counters are expected to have an increased value. Valid if the optional feature parameter DYNOLULSC is available, SCLD is ON and SCLDSC is set to OL.

Dynamic Overlaid/Underlaid Subcell

CELEVENTS HOAATUL HOSUCUL

These counters are expected to have an increased value. Valid if the optional feature parameter DYNOLULSC is available, SCLD is ON and SCLDSC is set to OL.




159 (175)

CELEVENTS HOAATOL HOSUCOL

These counters are expected to have a decreased value. Valid if the optional feature parameter DYNOLULSC is available, SCLD is ON and SCLDSC is set to OL.


CELLQOSG

DLTHP1GTHR DLTHP2GTHR DLTHP3GTHR DLBGGTHR

These counters are expected to have an increased value. Valid if the optional feature parameter GPRSAQM is activated (set to 1) and the BSC exchange property AQMSUPPORT is set to 1, 2 or 3.


CELLQOSEG

DLTHP1EGTHR DLTHP2EGTHR DLTHP3ETHR DLBGEGTHR

These counters are expected to have an increased value. Valid if the optional feature parameter GPRSAQM is activated (set to 1) and the BSC exchange property AQMSUPPORT is set to 1, 2 or 3.


CLRATECHG

HOATFRHRAMR HOATFRHRNAMR HOSUCFRHRAMR HOSUCFRHRNAMR

These counters are expected to have an increased value since they will also count the number of attempts and successful intra cell handovers initiated by the Abis Triggered HR Allocation optional feature. Valid if the optional feature parameter ATHAABIS is available (set to 1) and if the optional feature parameter ABISALLOC has value FLEXIBLE.

Abis Triggered HR Allocation

CELTCHH

CELTCHF

(60*PERLEN*THTRALACC)/ (THNSCAN*THMESTAB)

(60*PERLEN*TFTRALACC)/ (TFNSCAN*TFMESTAB)

It is expected that the TCH/FR mean holding time will decrease due to increased number of successful Intra Cell handovers triggered by Channel Repacking

This is valid if the parameter TCHOPTIMIZATION is set to 1

Channel Repacking



160 (175)

CELTCHH CELTCHF

CHGRP0H CHGRP0F CLTCHHV1,3 CLTCHFV1,2,3 CLTCHHV1,3 CLTCHFV1,2,3

THTRALACC / (THTRALACC + TFTRALACC)

THTRALACC0 /

(THTRALACC0 + TFTRALACC0)

THVxTRALACC / (THVxTRALACC+TFVxTRALACC)

THVxTRALSUB /

(THVxTRALSUB+TFVxTRALSUB)

The proportion of the the seized half rate traffic channels in the cell and in the channel group zero is expected to increase in case of Abis congestion due to the number of successful intra cell handovers initiated by the Abis Triggered HR Allocation optional feature. Valid if the optional feature parameter ATHAABIS is available (set to 1) and if the optional feature parameter ABISALLOC has value FLEXIBLE.

Abis Triggered HR Allocation

CELLGPRS TBFPREEMPEST PREEMPTTBF

These counters are expected to have an increased value since they shall be stepped due to released TBFs due to PDCH preemption or Abis congestion (both CS and PS). Valid if the optional feature parameter ABISALLOC has value FLEXIBLE.

Flexible Abis

CELLGPRS2 PREEMPTULREL

CELLFLXAB FLX16SUCC

This existing counter will count less number of successful attempts than in R11 since the new counter FLX8SUCC will in R12 register these attempts instead. Valid if the optional feature parameter DAMRREDUCE is available (set to 1) and if the optional feature parameter ABISALLOC has value FLEXIBLE.

Full Rate AMR on 8 kbps Abis

CLTCH TASSALL TCASSALL TASSATT

An increased value in these counters is expected in case there are frequent change of talkers during a voice group call. Valid if the optional feature parameter PMR for Voice Group Call Service is available (set to 1) and the feature is activated by the command RLVGI.


PREEMP HOATTPH FAILPH DISPH

An increased value in these counters is expected in case there are many Voice Group Call Voice Group Call



161 (175)

CLTCHHV1 THV1CONGSAS THV1CONGSASSUB

Service channels setup and/or frequent change of talkers during a voice group call. Valid if the optional feature parameter PMR for Voice Group Call Service is available (set to 1) and the feature is activated by the command RLVGI.

Services

CELTCHH

THCASSALL THCASSALLSUB THCONGSAS THCONGSASSUB

CELLDUALT TFDUALCASSALL TFDUALASSALL



CELTCHF

TFCASSALL TFCASSALLSUB TFCONGSAS TFCONGSASSUB

CLTCHFV1 TFV1CONGSAS TFV1CONGSASSUB

CELEVENTD

DISNORM DISBQA DISBSS DISETA

An increased value in these counters is expected in case there are frequent changes of talkers during a voice group call. Valid if the optional feature parameter PMR for Voice Group Call Service is available (set to 1) and the feature is activated by the command RLVGI.


NECELASS

HOASBCL HOASWCL HOSUCBCL HOSUCWCL



NICELASS

HOASBCL HOASWCL HOSUCBCL HOSUCWCL

CELTCHF TFNDROP TFNDROPSUB

If a voice group talker leaves its group call area (GCA), the call will be dropped leading to an increase in the dropped call counters. Valid if the optional feature parameter PMR for Voice Group Call Service is available (set to 1) and the feature is activated by the command RLVGI.


CELTCHFP TFDROPPGSM TFDROPPGSMSUB

If a voice group talker leaves its group call area (GCA), the call will be dropped leading to an Voice Group Call



162 (175)

CELTCHH THNDROP THNDROPSUB

CELLDUALT TFDUALNDROP

increase in the dropped call counters. Valid if the optional feature parameter PMR for Voice Group Call Service is available (set to 1) and the feature is activated by the command RLVGI.

Services

CLTCHDRF All counters in the object type

CLTCHDRH All counters in the object type



CHGRP0F

TFNDROP0 TFQADLDIS0 TFQAULDIS0 TFQABLDIS0 TFSSDLDIS0 TFSSULDIS0 TFSSBLDIS0 TFTADIS0



CHGRP0H

THNDROP0 THQADLDIS0 THQAULDIS0 THQABLDIS0 THSSDLDIS0 THSSULDIS0 THSSBLDIS0 THTADIS0



CELLMSQ All counters in the object type

An increased value in these counters is expected due to VGCH allocations. Valid if the optional feature parameter PMR for Voice Group Call Service is available (set to 1) and the feature is activated by the command RLVGI.


Table 76 R12 dynamic legacy counters



163 (175)

7.5.1 Non Functional Changes of Counters During PCU Load Control

During overload in PCU or due to lack of memory in PCU, the following legacy impacts will be seen:

1. The existing counters MOVECELLTBF (in the object type CELLGPRS), CELLMOVED (in the object type CELLGPRS), and FAILMOVECELL (in the object type BSCGPRS) will have increased value due to cell move by PCU load Control, i.e. when the new counter LCCELLMOV (in the object type GPHLOADREG) is stepped.

2. The existing counter PREJOTH (in the object type CELLGPRS2) will have increased value due to the rejected Packed Access Request at lack of RPP memory, i.e. when the new counter LCPARREJ (in the object type GPHLOADREG) is stepped.

3. The existing counters PREEMPTTBF, PREEMPTULREL an LDISTFI (all in the object type CELLGPRS2) will have increased value due to the entrance to the High Load Mode 3 will cause more idle or active PDCHs will be released, i.e. when the new counters LCCLRELBUSYHI3 (in the object type CELLGPRS3), LCRELBUSYHI3 and LCRELIDLEHI3 (both in the object type GPHLOADREG) are stepped.

4. The throughput counters will have decreased value during the time when the �MS Flow Control� has been suppressed due to lack of memory, i.e. when the new counter LCMSSUPRFC (in the object type GPHLOADREG) is stepped.

7.5.2 Non Functional Changes of Counters due to Speech Quality Supervision

Besides the impacts given in chapter 7.5, the following impacts need to be mentioned:

• The SQI thresholds are adjusted for Good and Unacceptable categories, which will lead to the SQI statistics to get lower values than before.

• The punishment of the SQI value at handover is removed which will lead to the SQI statistics to get better values.

As a summary, calculations and comparisons between R11 and R12 show, that the amount of Good samples will decrease, and the amount of Satisfactory samples will increase. The combined values for Good and Satisfactory in total can be expected to decrease with typically a couple of percent. The magnitude of the change may vary between networks



164 (175)

7.5.3 Non Functional Changes of Counters due to Admission Control for Push to Talk

In case of EIT traffic admission control rejects EIT traffic (which is visible in the counter value of ACREJEIT in the object type CELLEIT2), the following EIT counters will show different values compared to if the feature Admission Control for EIT was deactivated (which is equivalent to the R11 functionality of EIT):


CELLEIT

Q3TDDLEIT / (Q1TDDLEIT + Q2TDDLEIT + Q3TDDLEIT)

Q3TDULEIT / (Q1TDULEIT + Q2TDULEIT + Q3TDULEIT)

Transfer Delay Success both DL and UL (the given formulas) will show an increased values due to this feature. Valid if the optional feature parameter ADMCTRL is available and if the value of the BSC exchange parameter EITADMCTRL is set to 1.


CELLEIT

EITDLGTBF EITULGTBF EITDLETBF EITULETBF

RLCGDLEITSCHED RLCGULEITSCHED RLCEDLEITSCHED RLCEULEITSCHED

These counters will show decreased values due to this feature. Valid if the optional feature parameter ADMCTRL is available and if the value of the BSC exchange parameter EITADMCTRL is set to 1.


CELLEIT2

RLCGDLVOLEIT RLCGULVOLEIT RLCEDLVOLEIT RLCEULVOLEIT

LLCVOLDLEIT LLCVOLULEIT

These counters will show decreased values due to this feature. Valid if the optional feature parameter ADMCTRL is available and if the value of the BSC exchange parameter EITADMCTRL is set to 1.


Table 77 Non Functional changes of counters due to Admission Control for Push to Talk

In case of EIT traffic admission control rejects EIT traffic (which is visible in the counter value of ACREJEIT in the object type CELLEIT2) and the parameter EITQOSPRIO has value 2 or 3 then the EIT requests will be accepted at quality of service class interactive (instead of streaming). This will lead to some related counters for the quality of service class interactive and some throughput counters for the class interactive will have increased values compared to if the feature Admission Control for EIT was deactivated (which is equivalent to the R11 functionality of EIT). The related object types are CELLGPRS, CELLGPRS3, CELLQOSG, CELLQOSEG.



165 (175)

7.5.4 Non Functional Changes of Counters due Dynamic Overlaid/underlaid Subcell

In addition to the impacts given in chapter 7.5, the following impact is expected in case SCLD is activated for more than 16 cells in a BSC since the evaluations for SCLD in a cell in R12 are done at each TCH allocation and TCH release in the cell, and subcell changes can then be initiated directly if required.

The enhanced SCLD will also exist in AC-A packages available for BSC R10 and R11. The below indicated non functional counter changes are valid for R12 if those AC-A packages has not been installed in R10 or R11.

As a result of the enhancement mentioned above, the following counters will show increased values in case SCLD is activated for more than 16 cells in the BSC:


CELEVENTSC

SCLDCOMUL SCLDSUCUL OLSCLDCOM OLSCLDSUC

The counters for Subcell change attempts and successful subcell changes will show increased values due this improvement. Valid if SCLD is activated in more than 16 cells in the BSC.

Dynamic Overlaid/underlaid Subcell

CELEVENTS

HOAATOL HOSUCOL HOAATUL HOSUCUL

The counters for handover attempts and successful handovers between the subcells will show increased values due this improvement. Valid if SCLD is activated in more than 16 cells in the BSC.


CELTCHF TFMSESTB TFMSESTBSUB TFCALLS TFCALLSSUB TFCONGSHO TFCONGSHOSUB

Full Rate and Half Rate TCH allocation related counters will show increased values due this improvement. Valid if SCLD is activated in more than 16 cells in the BSC.


CELTCHH THMSESTB THMSESTBSUB THCALLS THCALLSSUB THCONGSHO THCONGSHOSUB

Full Rate and Half Rate TCH allocation related counters will show increased values due this improvement. Valid if SCLD is activated in more than 16 cells in the BSC.




166 (175)

CLTCHFV1 CLTCHFV2 CLTCHFV3 CLTCHHV1 CLTCHHV3

TrVxCALLS TrVxCALLSSUB TrVxCONGSHO TrVxCONGSHOSUB (r stands for F or H and x stands for 1, 2 or 3)

Full Rate and Half Rate Speech Version 1, 2 and 3 TCH allocation related counters will show increased values due this improvement. Valid if SCLD is activated in more than 16 cells in the BSC.


Table 78 Non Functional changes of counters due to Improved Subcell Load Distribution

7.5.5 Non Functional Changes of Counters due to Adaptive Configuration of SDCCHs

Since it is possible to use adaptive configuration of SDCCHs also in the overlaid subcell, TCHs in overlaid subcell may be adaptively configured to SDCCHs if the channel group that belongs to overlaid is not excluded.

Since the number of TCHs will decrease in the overlaid subcell, some traffic may be moved from the overlaid to underlaid subcell, but the total traffic handled in the cell (overlaid and underlaid together) will not be changed.

As a result of this enhancement, the following general non functional counter changes are expected in case adaptive configuration of SDCCHs is activated and the channel group located in overlaid subcell is not excluded:

• SDCCH related counters are expected to increase in the overlaid subcell while the same amount of decrease is expected in the corresponding UL subcell counters. Example: The counter CCALLSSUB in the object type CLSDCCHO is expected to increase while the counter CCALLS in the object type CLSDCCH is expected to decrease.

• TCH related counters (e.g. TCH allocation counters, assignment and handovers counters) are expected to increase in the UL subcell while the same amount of decrease is expected in the corresponding overlaid subcell counters. Example: The counter TFCASSALL in the object type CELTCHF is expected to increase while the counter TFCASSALLSUB in the same object type expected to decrease.

A related overlaid and underlaid subcell counter pair is called to be disjoint if stepping of an overlaid subcell counter does not affect the underlaid subcell counter. Contrarily, an overlaid and underlaid subcell counter pair is called to be dependent if stepping of an overlaid subcell counter means stepping the corresponding underlaid subcell counter at the same time. So, dependent underlaid counters will not be affected by the adaptive configuration of SDCCHs.

Object Type Counter Impact



167 (175)

CELLCCHDR CDISQA CDISSS

These disjoint underlaid cell SDCCH counters will show decreased values as explained above.

CELLCCHDR CDISQASUB CDISSSSUB

These overlaid cell SDCCH counters will show increased values as explained above.

CLSDCCHO CCALLSSUB CCONGSSUB CTCONSUB CTRALSUB CAVASUB CMSESTABSUB CNRELCONGSUB

These overlaid cell SDCCH counters will show increased values as explained above.

CLSDCCH CCONGS CTCONGS CNDROP

These disjoint underlaid cell SDCCH counters will show decreased values as explained above.

CELLSQI TSQIxSUBy All overlaid cell TCH speech quality will show decreased values as explained above.

CELLSQI TSQIxy All underlaid cell TCH speech quality will show increased values as explained above.

CELTCHF CELTCHH

TxySUB All overlaid cell TCH counters will show decreased values as explained above.

CELTCHF CELTCHH

Txy Txy

All disjoint underlaid cell TCH counters (associated with overlaid counters) will show increased values as explained above.

CELTCHFP TFDROPPGSM TFCONGPGSM

These disjoint underlaid cell TCH counters will show increased values as explained above.

CELTCHFP TFESTPGSMSUB TFDROPPGSMSUB TFCONGPGSMSUB

These overlaid cell TCH counters will show decreased values as explained above.

CLTCH TAVASUB TAVASCANSUB

These overlaid cell TCH counters will show decreased values as explained above.

CLTCHDRF CLTCHDRH CLTCHDRAF CLTCHDRAH

TxySUB TxySUBA

All overlaid cell dropped TCH connection counters will show decreased values as explained above.

CLTCHDRF CLTCHDRH CLTCHDRAF CLTCHDRAH

Txy TxyA

All underlaid cell dropped TCH connection counters (associated with overlaid counters) will show increased values as explained above.



168 (175)


TxVySUB All overlaid cell dropped TCH connection counters will show decreased values as explained above.


TxVy All disjoint underlaid cell TCH counters (associated with overlaid counters) will show increased values as explained above.

7.5.6 Non Functional Changes of Counters due to Correction Packages

This chapter will be updated at every ACA package with counters that might get modified behaviour due to the released correction packages.

Object Type Counter Correction Package

Impact

DTDSUBS TOTDTDDTMF DR1DTMF ACA1

10922-APT21009/211-1370:

This CNI corrects a fault where counters in the object type DTDSUBS have correct values, but on wrong positions: the counter TOTDTDDTMF at position of the counter DR1DTMF, the counter DR1DTMF at position of the counter DR2DTMF, etc.

TRUNKROUTE

NSCAN NTRALACCI NTRALACCO NBLOCACC NBBLOCACC

ACA1

10922-APT21009/211-1370:

This CNI also corrects a fault where accumulation counters NSCAN, NTRALACCI, NTRALACCO, NBLOCACC and NBBLOCACC in the object type TRUNKROUTE could have too low values when an SP restart has occurred.

CELLGPRS2 PMTREF PMTATT

IP-A11 (AC-A2)

10922-APT21009/211-1401:

This CN-I corrects a fault where the counter PMTREF is stepped too often. The counter is supposed to count the number of pre-emption attempts that are refused due to the cell parameter PDCHPREEMPT. The fault was that the counter could step for other reasons and even when PDCHPREEMT is set to all on-demand PDCHs are possible to pre-empt.

This CN-I also corrects a fault where the counter PMTATT was stepped to often. PMTATT is supposed to count the number of pre-emption attempts when there is at least one PDCH possible to preempt. The fault is that the counter was stepped for every preemtion attempt, even though there is no PDCH possible to preempt.

CELLFLXAB FLX16ATT IPA14 In the situation described below FLX16SUCC (BAN=H�28A) and MNAHG-3229:



169 (175)

FLX64ATT (ACA3) FLX16ATT counters will increase due to that they will also be

stepped for successful 16K allocation result upon request of 64K preferred, but not mandatory path. Also, when a Flexible Abis allocation request for 64K Abis path is made and 64K path is preferred, but not mandatory, counter FLX64ATT in the block RNLCT is stepped. As the result of the request 16K Abis path may be received instead of 64K path due to lack of recourses. This situation may occur for allocation of abis paths for On Demand or Semi PDCH and allocation of PS part of DTM connection. In that case no other counters are stepped and successful 16K answer is not recorded.

All CLRATECHG IPA14 (ACA3)

MNAHG-3240: If feature DYMA (Dynamic FR/HR Mode Adaptation) is used, a difference in FR/HR counters might be seen.

CELTCHF

TFNCEDROP TFNCEDROPSUB THNCEDROP THNCEDROPSUB

IPA14 (ACA3)

MWAHG-3236: The drop counters: TFNCEDROP, TFNCEDROPSUB, THNCEDROP, THNCEDROPSUB are modified. Instead of DTAP message 24.008 Connect Acknowledge, the 44.018 messages Assignment Complete, Handover Complete and Channel Mode Modify Acknowledge will define the start point of the counting interval. The end point will remain intact, i.e. DTAP message 24.008 Disconnect or 24.008 Release.

APPLATFORM

CONTSWITCH PAGEFAULT CACHEFAULT NIRECEIVED NISENT

ACA3 10922-APZ21230/5-783: Overflow problem for counters CONTSWITCH, PAGEFAULT, CACHEFAULT, NIRECEIVED and NISENT of APPLATFORM Object Type is corrected.

All CLTCHDRH

ACA3 10922-APT21009/211-1620: -Problem with objtype CLTCHDRH is corrected.

8 Glossary

Abis Interface between BSC � BTS

ACS Active Codec Set

AMR Adaptive Multi Rate

BAR active BCCH Allocation list Recording

BCCH Broadcast Control Channel

BRP Basic Recording Period

BSC Base Station Controller

BSM Base Station Manager

BSS Base Station System

BSSGP BSS GPRS Protocol



170 (175)

BTS Base Transceiver Station

CCS Common Channel Signalling

CER Channel Event Recording

CGI Cell Global identity

CTR Cell Traffic Recording

CNA Cellular Network Administration

CNAI CNA Interface

CP Central Processor

CGSN Combined SGSN-GGSN

DS Data Store

DT Data Transcript

E-CGI Enhanced Cell Global Identity

EDGE Enhance Data rate for GSM Evolution

EFR Enhanced Full Rate

EGPRS Enhanced General Packet Radio Service

EIT Ericsson Instant Talk

EMR Enhanced Measurement Report

FAS Frequency Allocation Support

FOA First Office Application

FR Full Rate

Gb Interface between BSC - SGSN

GERAN GSM/EDGE Radio Access Network

GGSN Gateway GPRS Support Node

GPH GPRS Protocol Handler

GPRS General Packet Radio Service

GSL GPRS Signaling Link



171 (175)

GML GPRS/EGPRS Mobile Logging

GMPC Gateway Serving Mobile Positioning Centre

GWBAR GSM-WCDMA BA List Recording

GWNCS GSM-WCDMA neighbouring Cell List Support

HLR Home Location Register

IDB Installation Data Base

ICDM Inter Cell Dependency Matrix

IMSI International Mobile Subscriber Identity

IOG Input Output Group

IPE In Path Equipment

ISHO Inter System Handover

ISP In Service Performance

LA Ericsson Layered Architecture

LCS Location Service

LSL Line Speech Level

MAC Medium Access Control

MBC Multi Band Cell

MML Man-Machine Language

MPDCH Master Packet Data Channel

MRR Measurement Result Recording

MS Mobile Station

MSC Mobile Switching Centre

MSS Ericsson Mobile Softswitch Solution (MSC-S and M-MGw)

MTR Mobile Traffic Recording

MW16 Mega 16-bit word




172 (175)


NCS Neighbour Cell Support

NE Network Element

NFF No Fault Found

NNRP4 Network Node Renewal Process 4

NNRP5 Network Node Renewal Process 5

NOX Neighbour Cell Optimisation Expert

NSE Network Service Entity

NSVC Network Services Virtual Connection

NWS Network Statistics

O&M Operation and Maintenance

OMC O&M Centre

OML O&M Link

OMT O&M Terminal

OSS Operation and Support System

PACCH Packet Associated Control Channel

PCH Paging Channel

PCM Pulse Code Modulation

PCU Packet Control Unit

PDCH Packet Data Channel

PDP Packet Data Protocol

PFC Packet Flow Context

PLMN Public Land Mobile Network

PMR Performance Management

PS Program Store

RLC Radio Link Control



173 (175)

RNO Radio Network Optimization

RNX Radio Network eXpert

RP Regional Processor

RPP Regional Processor with PCI interface

RPI Regional Processor Integrated

RPG Regional Processor with Group Switch Interface

R-PMO Real Time Performance Monitoring

RS Reference Store

RSL Radio Signalling Link

RX Receiver

SAE Size Alteration Event

SDCCH Standalone Dedicated Control Channel

SGSN-G Serving GPRS Support Node (GSM)

SL Signalling Link

SP Support Processor

SMPC Serving Mobile Positioning Centre

SQS Speech Quality Supervision

STOC Signalling Terminal for Open Communications

STS Statistical Subsystem

SYROX Synchronized Radio Network Optimization Expert

TBF Temporary Block Flow

TCH Traffic Channel

TCP Transmission Control Protocol

TF Timing Function

TFO Tandem Free Operation

TrFo Transcoder Free operation



174 (175)

TG Transceiver Group

TLLI Temporary Location Link Identity

TMA Tower Mounted Amplifier

TN Timeslot Number

TRA Transcoder and Rate Adaptor

TRC Transcoder Controller

TRH Transceiver Handler

TRU Transceiver Unit

TRX Transceiver

TSC Training Sequence Code

USF Uplink State Flag

UTRAN Universal Terrestrial Radio Network Access

VGCS Voice Group Call Service

9 References [1] BSS R12 GSM Statement of compliance document list,

http://www.lmera.ericsson.se/~kigran/projects/BSSR12/BSSR12_System/Execution/GSM SoC/BSS R12/

[2] User Description, Radio Network Parameters & Cell Design Data For Ericsson's GSM Systems, 222/1553-HSC 103 12/7

[3] Changes to the Operator Interface for the BSC, 10/10921-APT 210 09/211-1

[4] APG40 APZ 12.0 Network Impact Report, 1/109 48-FAM 101 30/2

[5] User Description, Gb over IP and SGSN in Pool, 241/1553-HSC 103 12

[6] Application Information, Size Alteration events in BSC/TRC, 2/155 18-AXE 105 07

[7] Application Information, ROS, Exchange Property Commands Changeable Exchange Adaptation, 2/155 18-CNT 248 1115

[8] Ordering info, SOURCE SYSTEM ISSUE APT 210 09/211 R1A, 131 62-APT 210 09/211 (Ericsson personnel only).



175 (175)

[9] Network Impact Report for OSS-RC R3, 1/190 48-AOM 901 017/3

[10] BSC STS Configuration Spreadsheet, 2/198 17-APT 210 09

[11] RBS 2000 12A_1/11D_1 SW Release Note, LZY 213 1440/2 R9V, 109 47-LZY 213 1440/2-2

alex0675 (1).pdf

Documents

Transcript of alex0675 (1).pdf