Technical Support Note

TS-BSC-SW-0763-I12.0

Adding a TRX to a (E)GPRS enabled cell

Radio Controllers
BSC
SR20, SR40, S16_2, BSC16, BSC17, SRAN16.2,
SRAN16.10

Approval date: (06-Feb-2002)

This document contains following

type of information
Informative X
Preventive
Corrective
Additional categorization
Urgent
Security
Release Upgrade
SW Update
Parameterization
Information is classified as
Internal
Public X
Customer Specific

TS-BSC-0763-I12.0- Page 1/8 © Nokia 2016

Version 12.0
Confidential
Table of Contents

1. Validity .....................................................................................................................................3
2. Compatibility / Dependencies to other products ......................................................................3
3. Keywords.................................................................................................................................3
4. Executive Summary ................................................................................................................3
5. Detailed description .................................................................................................................3
6. SOLUTION / INSTRUCTIONS ................................................................................................4
7. NOTE¤ ....................................................................................................................................7
8. REFERENCE ..........................................................................................................................7

Contact:

Contact your local Nokia Solutions and Networks support

Summary of changes:

06-02-2002 1.0 First version

13-02-2002 1.1 Instructions for manual checking
05-07-2002 1.2 Correction to locked BTS info
29-07-2002 1.3 Correction to conflicting information about he
timeslots of the locked BTS
18-06-2007 1.4 TN is validated for S11, S11.5 and S12 level
21-07-2008 2.0 Update to S13 level
19-03-2009 3.0 Update to S14 level
21-10-2009 3.1 EGPRS update
16-02-2010 4.0 S15 validation
19-12-2011 5.0 SR10, S15mcBSC validation
15-11-2012 6.0 SR20 and S16 validation
12-04-2013 7.0 SR10 removed add S16.1
11-Sep-2014 8.0 S16_2 validation
11-May-2015 9.0 SR40 & BSC16 validation
17-Aug-2015 10.0 Content Modified
10-Nov-2015 11.0 SRAN16.2 validation, Removing S16 & S16.1
03-Aug-2016 12.0 SRAN16.10 & BSC17 validation

TS-BSC-0763-I12.0- Page 2/8 © Nokia 2016

Version 12.0
Confidential
Purpose
This document contains generic information about products. These can be instructions that
explain problem situations in the field, instructions on how to prevent or how to recover from
problem situations, announcements about changes or preliminary information as requirements
for new features or releases.

1. VALIDITY

Product SR20 S16_2 SR40 BSC16 SRAN16.2/ BSC17

SRAN16.10
BSC3i X X X
Flexi BSC X X X X X
TCSM2A/E
TCSM3i
mcBSC X X X
mcTC
Single RAN X

2. COMPATIBILITY / DEPENDENCIES TO OTHER PRODUCTS

None.

3. KEYWORDS

GTRX, GENA, CDEF, CDED, GPRS, EGPRS, adding TRX

4. EXECUTIVE SUMMARY

Adding a TRX to a (E)GPRS enabled cell may cause PCU capacity (max 1024 Abis channels)
to be exceeded, if the addition is not done properly. Maximum channel capacity contains
GPRS channels, EGPRS master channels and EGPRS slave channels (EDAP).

5. DETAILED DESCRIPTION

A TRX addition to a (E)GPRS enabled cell must be done, taking the following aspect into
consideration:
When a (E)GPRS enabled (GTRX=Y) TRX is added to a (E)GPRS enabled cell (GENA=Y)
and territory definitions remain unaltered (CDEF, CDED), the amount of (E)GPRS channels in
the cell increases. If this is not taken into account in the dimensioning, the PCU maximum Abis
channel capacity may be exceeded. This causes the PCU to be unable to grant all the
channels that are requested and some cells will have reduced (E)GPRS capacity available.

Example:
A TRX (with GTRX=Y) is added to a (E)GPRS enabled cell (BTS1) and PCU capacity is
exceeded. Because of this, (E)GPRS channels cannot be fully granted to BTS1. Now, when
the circuit switched traffic increases in another cell (BTS2) so that the (E)GPRS territory will be
downgraded, these freed channels will be granted to BTS1. Then, when traffic decreases in
BTS2, the territory cannot be upgraded to its original size anymore as the channels are not
available in the PCU. In the worst case, BTS2 will loose its GPRS capacity totally.

TS-BSC-0763-I12.0- Page 3/8 © Nokia 2016

Version 12.0
Confidential
6. SOLUTION / INSTRUCTIONS

After adding a TRX (with GTRX=Y) to a (E)GPRS enabled cell, choose one of the
following actions:

 Decrease the territory size (definitions of CDEF,CDED) to keep the amount of

(E)GPRS channels the same as before.

 Optimize the EDAP sizes in PCU.

 In case cell is not EGPRS cell toggle the GPRS activation status (GENA=N/Y). This
attaches BTS to NSEI, where there is enough capacity available.

 Verify manually that the PCU capacity is not exceeded. And if it is exceeded, allocate
some of the BTS to another PCU.

The amount of timeslots requested to (E)GPRS territory can be found with E00_BXSX service
terminal extension. Note that this printout includes the default timeslots of the locked BTSs if
they are GPRS enabled.

Go to the service terminal of OMU (ZDDS;)

Load extension E00_BXSX (ZLE:<char>,E00_BXSX)
Print out BSC information (Z<char>A:6,1,0)
Find out the amount of timeslots requested to (E)GPRS from the printout. It is the column
furthest on the left of the last list. If any of the values in the first column exceeds value in third
column (MAX CONN), then too many timeslots have been requested from that PCU. MAX
CONN is the channel capacity that there is available in PCU after EDAP channels.
Note that this printout includes the default timeslots of the locked BTSs if they are GPRS
enabled.

Example 1 (GPRS configuration without EDAP):

04-MAN>ZMA:6,1,0

2009-03-19 15:09:32.74
BSC SPECIFIC DATA (0107 bytes)

OCCU TCH CNT REAL TIME, MEAS PRD: 007C 07AB

OCCU TCH CNT LAST, THIS PERIOD : 0072 007C
OCCU TCH COUNT PEAK : 0072
OCCU TCH COUNT PEAK TIME : 12:05:33.13 19/03/2009
OCCU TCH DENOMINATOR : 0013
TCH SEIZ CNT THIS, LAST PERIOD : 0371 0894
TCH SEIZ COUNT PEAK : 08CD
TCH SEIZ COUNT PEAK TIME : 12:20:33.14 19/03/2009
SDCCH SEIZ CNT THIS, LAST PERIOD: 02AF 0696
SDCCH SEIZ COUNT PEAK : 06FA
SDCCH SEIZ COUNT PEAK TIME : 12:20:33.14 19/03/2009
TIME STAMP UNIT STATE TO WO : 10:05:33.05 19/03/2009
AMH MAX LOAD OF TGTC : 46
NUMBER OF PCU:S IN THE LIST : 12
TSL---CONN--MAX---BCSU--PCU---SWITCH
CNT---CNT---CONN--UNIT--INDEX-OVER

TS-BSC-0763-I12.0- Page 4/8 © Nokia 2016

Version 12.0
Confidential
 0000 0000 0100 415A 0007 00
00A4 00A2 0100 415A 0009 00
0000 0000 0100 415B 0007 00
00AC 00AA 0100 415B 0009 00
0000 0000 0100 415C 0007 00
0000 0000 0100 415C 0009 00
0000 0000 0100 415D 0007 00
00A8 00A5 0100 415D 0009 00
0000 0000 0100 415E 0007 00
0124 0100 0100 415E 0009 00
0000 0000 0100 415F 0007 00
0000 0000 0100 415F 0009 00
0000 0000 0100 4160 0007 00
0000 0000 0100 4160 0009 00
0000 0000 0100 4161 0007 00
0000 0000 0100 4161 0009 00
0000 0000 0100 4162 0007 00
0000 0000 0100 4162 0009 00

In this example, too many timeslots have been requested from a PCU in a BCSU whose
logical address is 415E and index 9.

If there are too many timeslots requested from some BCSU, find the BCSU index with
RCBUGGGX service terminal extension:

Load extension RCBUGGGX (ZLE:<char>,RCBUGGGX)

Print out BCSU addresses (Z<char>SI:BCSU)
Find out the BCSU index from the printout.

Example continues:
00-MAN>ZUSI:BCSU

UNIT MB LGA STATE INFO 2009-03-19 09:53:22

BCSU-0 30 415B SP-EX
BCSU-1 31 415A WO-EX
BCSU-2 32 415C WO-EX
BCSU-3 33 4161 WO-EX
BCSU-4 34 415D WO-EX
BCSU-5 35 415E WO-EX
BCSU-6 36 4162 WO-EX
BCSU-7 37 415F WO-EX
BCSU-8 38 4160 WO-EX

009 Unit(s)

In this example, too many timeslots have been requested from PCU in BCSU-5.

TS-BSC-0763-I12.0- Page 5/8 © Nokia 2016

Version 12.0
Confidential
 Example 2 (EGPRS configuration with EDAP)

2009-10-21 10:42:30.69
BSC SPECIFIC DATA (0954 bytes)

OCCU TCH CNT REAL TIME, MEAS PRD: 0000 0000

OCCU TCH CNT LAST, THIS PERIOD : 0000 0000
OCCU TCH COUNT PEAK : 0000
OCCU TCH COUNT PEAK TIME : 00:00:00.00 00/00/0000
OCCU TCH DENOMINATOR : 002D
TCH SEIZ CNT THIS, LAST PERIOD : 0000 0000
TCH SEIZ COUNT PEAK : 000A
TCH SEIZ COUNT PEAK TIME : 14:12:22.46 06/10/2009
SDCCH SEIZ CNT THIS, LAST PERIOD: 0000 0000
SDCCH SEIZ COUNT PEAK : 0009
SDCCH SEIZ COUNT PEAK TIME : 13:12:22.42 06/10/2009
TIME STAMP UNIT STATE TO WO : 10:42:16.56 30/09/2009
AMH MAX LOAD OF TGTC : 46
LICENCING FEATURES
AMR FEATURE DATA PRIMARY_STATE : 02
DFCA FEATURE DATA PRIMARY_STATE : 02
SCC FEATURE DATA PRIMARY_STATE : 02
WPS FEATURE DATA PRIMARY_STATE : 00
SAIC FEATURE DATA PRIMARY_STATE : 02
INCREASED SDCCH CAPACITY FEATURE DATA PRIMARY_STATE : 00
LBAP FEATURE DATA PRIMARY_STATE : 02
NUMBER OF PCU:S IN THE LIST : 9A
TSL---CONN--MAX---BCSU--PCU---SWITCH
CNT---CNT---CONN--UNIT--INDEX-OVER
0012 0003 0080 415A 0004 00
0004 0000 0100 415B 0003 00
000F 0000 0100 415E 0003 00

In this example, in PCU in a BCSU whose logical address is 415A and index 4 maximum
connection is 128 (80h). This is because there is 128 EDAP channels configured for the same
PCU. Despite of this PCU’s maximum capacity is not exceeded since TSL CNT is 12.

To define correct PCU load extension RCBUGGGX (ZLE:<char>,RCBUGGGX)

Print out BCSU addresses (Z<char>SI:BCSU)
Find out the BCSU index from the printout.

00-MAN>ZUSI:BCSU

UNIT PHYS LGA STATE INFO 2009-10-21 10:44:15

BCSU-0 0030 415A WO-EX
BCSU-1 0031 415D WO-EX
BCSU-2 0032 4160 SP-EX

In this example PCU with EDAP is PCU 4 in BCSU 0.

TS-BSC-0763-I12.0- Page 6/8 © Nokia 2016

Version 12.0
Confidential
 In PCU capacity EDAP’s channels are counted in 16k slots. Use ZESI; MML command to
check EDAP’s configured to the PCU. ZESI prinout presents EDAP channels in 64k slots as
they are defined.

DAP CTRL
ID ETPCM-TSLS BCSU PCU
---- ------------ --------
6 265- 9&&-19 0 4
2 475-10&&-19 0 4
99 268- 1&&-11 0 4

DAP 6 is 11*4 = 44, DAP 2 is 10 * 4 = 40 and DAP 99 is 11 * 4 = 44. Totally there is 44+40+44
= 128 16k EDAP channels in PCU wich is reduced from the PCU’s total channel capacity.

7. NOTE¤

None.

8. REFERENCE

BSC EDGE Dimensioning (DN7032469), operation documentation (NED).

TS-BSC-0763-I12.0- Page 7/8 © Nokia 2016

Version 12.0
Confidential
Disclaimer
The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified
herein. Reference to “Nokia” later in this document shall mean the respective company within Nokia Group of Companies with whom
you have entered into the Agreement (as defined below).

This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the purposes defined in the
agreement between You and Nokia (“Agreement”) under which this document is distributed. No part of this document may be used,
copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia. If You have not
entered into an Agreement applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this
document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof.

The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility
when using it. Nokia welcomes your comments as part of the process of continuous development and improvement of the
documentation.

This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability,
capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document,
and Nokia reserves the right to change any such information and statements without notice. Nokia has made all reasonable efforts to
ensure that the content of this document is adequate and free of material errors and omissions, and Nokia will correct errors that You
identify in this document. Nokia's total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia
does not warrant that the use of the software in the Product will be uninterrupted or error-free.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF
AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE
LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR
CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE
INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

This document is Nokia proprietary and confidential information, which may not be distributed or disclosed to any third parties without
the prior written consent of Nokia.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their
respective owners.

Copyright © 2016 Nokia. All rights reserved.

Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having
carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information”
part of this document or documentation set.

Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you
as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow
the recommendations for power use and proper disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at
Nokia for any additional information.

TS-BSC-0763-I12.0- Page 8/8 © Nokia 2016

Version 12.0
Confidential