MENU

Summary of Corrections
and Enhancements
Release Delivery: EX3.1 MP1.0
Product Family: Base Stations
Product: Flexi Multiradio BTS, GSM/EDGE
Release: EX3.1

DN0974364
Issue 2-0 en
24/03/11

©© Nokia Siemens Networks Company Confidential 1 (10)

Nokia Siemens Networks 1 (10)
MENU

Table of Contents
1. Purpose......................................................................................................................................................... 3
2. Corrections.................................................................................................................................................... 3
2.1 EGPRS Downlink throughput degraded (23111ESPE07) ........................................................................................ 3
2.2 Sometimes the site is not able to process calls (NA04846791, NA04854601 and NA04850140)............................ 3
2.3 Updates to CL are not taken into use from an MP release of a older EM if a later main release is already
installed (47041ESPE03) ......................................................................................................................................... 4
2.4 Misleading TRX Test result with antenna optimised configuration (82582ESPE02) ................................................ 4
2.5 BTS Manager allows user to enter illegal characters into SCF (80488ESPE02) ..................................................... 5
2.6 RX diversity does not work after re-commissioning at BTS manager (80980ESPE02)............................................ 5
2.7 BCCH reconfiguration does not work if TRX’s are split on two branches due to frequency budget
(69756ESPE02) ....................................................................................................................................................... 5
2.8 Cannot send SCF if BCF is locked at the BSC when the BTS power is turned on (26799ESPE05) ........................ 5
2.9 Alarm 7606 “ESMx internal SRIO Link is Faulty” reported after BCF reset (19553ESPE06) ................................... 6
2.10 Unnecessary alarms are raised during runtime (20436ESPE06) ............................................................................. 6
2.11 GCS Connection tool does not populate connection fields (67491ESPE04)............................................................ 6
2.12 BTS Alarm window not refreshing properly in 2G Flexi BTS Manager (66343ESPE04) .......................................... 7
2.13 Test Pattern Transmission is shown as ONGOING on the BTS Manager, even after completion and
reports not cleared when deleted (6770ESPE04) .................................................................................................... 7
2.14 Missing 7606-'ESMx System Module has lost connection to FXxx RF Module' alarm (75595ESPE02) .................. 7
2.15 Timing Advance offset of 2-3 observed in KPI testing when compared to Flexi EDGE (19810ESPE07) ................. 7
2.16 No alarm when no RF power coming out from any of the branches and TRX objects in WO state
(18937ESPE06) ....................................................................................................................................................... 8
2.17 Unexpected 7607 - RF module detected too high TX power alarm (49758ESPE01) ............................................... 8
3. New functionality........................................................................................................................................... 8
4. 3rd party corrections ..................................................................................................................................... 9
5. Restrictions ................................................................................................................................................... 9
6. Release objects ............................................................................................................................................ 9
7. Piloting .......................................................................................................................................................... 9
8. Appendices / References.............................................................................................................................. 9

Contact
Contact your local Nokia Siemens Networks support or GSM/EDGE BTS Technical
Support: [email protected]

Summary of changes
24-Mar-2011 Version 2.0 Approved for EX3.1 MP1.0

DN0974364
Issue 2-0 en
24/03/11
2 (10)
© Nokia Siemens Networks Company Confidential
MENU

1. PURPOSE

The purpose of this document is to give a brief summary on the Flexi Multiradio EDGE
BTS SW EX3.1 MP1.0 delivery content.

2. CORRECTIONS

Flexi EDGE BTS SW EP3 MP4.0 has been used as a baseline for Flexi Multiradio
EDGE BTS SW EX3.1 MP1.0. This means that all corrections included in EP3 MP4.0
are also included in EX3.1 MP1.0.

More details about all EP3 MP4.0 corrections can be found from the latest Flexi EDGE
BTS List of Generic Faults report /4/.

EX3.1 MP1.0 BTS SW release contains Flexi Multiradio EDGE BTS specific
corrections for the following problems. For further details, please see Flexi Multiradio
EDGE BTS List of Generic Faults-report /3/

2.1 EGPRS Downlink throughput degraded (23111ESPE07)

Description:
EGPRS downlink throughput degradation has been observed with low (below -95dBm)
DL RX levels compared to EX3.1 BTS SW release.

2.2 Sometimes the site is not able to process calls (NA04846791, NA04854601 and
NA04850140)

Description
It has been observed that after BSC upgrade, BCF reset or RFM HW reset, the BCF is
not able to process calls or handovers. The problem is activated when the System
module has been running continuously for approx. 50 days without a HW reset (e.g.
following a power break).

When the problem is active, the following alarms can been seen on BSC and NetAct:
- 7738 BTS WITH NO TRANSACTIONS
- 7743 MEAN HOLDING TIME BELOW DEFINED THRESHOLD
- 7745 CHANNEL FAILURE RATE ABOVE DEFINED THRESHOLD
- 7746 CH CONGESTION IN CELL ABOVE DEFINED THRESHOLD

Also, when the problem is active, TRX Tests in all TRX objects will fail as follows:
o TRX Test run from BSC (ZUBS, ZUBP):
TEST RESULT: INCONCLUSIVE
REASON: HARDWARE FAILURE
o TRX Test run from BTS Manager:
Fail with very high reported BER value.

Root cause of the problem:

BTS SW is responsible for detecting and compensating for the delay between BTS
internal frame clocks and the GSM Frame clocks in order for the UL decoding to work
as expected. The formula to calculate these delays from internal clocks required 64 bit
accuracy to be use throughout the calculation to achieve the required accuracy.

However, the SW compiler incorrectly uses a 32 bit data types to save a temporary
calculation result. This results in truncation errors in the calculation. After approx. 50
days of continuous ESMx System Module operation, there is an overflow in the delay

DN0974364
Issue 2-0 en
24/03/11
3 (10)
© Nokia Siemens Networks Company Confidential
MENU

value which results in an error in the delay calculation caused by the use of 32bit
temporary variable.

The problem is only triggered when this incorrect delay value is sent to the RF module.
This happens after BCF reset (caused by e.g. BCF lock/unlock, BSC SW upgrade) or
after RF module HW reset (caused by user action or due to unexpected HW reset).
From this point onwards, decoding in the UL will fail.

In addition to the root cause correction, a new alarm is implemented to ease the
troubleshooting if similar problems are seen in the future. Alarm 7601 - BCF
OPERATION DEGRADED - “Rx Uplink path not working in ESMx System module" is
triggered if UL of all TRXs in Supervisory state are not working indicating GSM UL
failure.

If new alarm is seen with EX3.1 MP1.0 or newer SW version, log files for
troubleshooting purpose can be collected with snapshot feature via remote BTS
Manager, even after BCF reset.

2.3 Updates to CL are not taken into use from an MP release of a older EM if a later
main release is already installed (47041ESPE03)

Description:
BTS Manager application includes Compatibility Launcher (CL). Main task of CL is to
select most compatible BTS Manager from laptop hard disk when BTS Manager is
launched from CL.

It has been noticed that a correction delivered to CL after EX3.1 are not taken in use if
EX3.1 BTS Manager with CL has been already installed to the laptop. In latest BTS
Manager’s versioning scheme is updated so that also CL is upgraded when newer
BTS Manager is installed.

Note: Installing EX3.1 BTS Manager will downgrade CL parts of the BTS Manager
functionality. Thus recommended course of action is that if EX3.1 BTS Manager needs
to be installed, first remove all other BTS Manager installations, then install EX3.1 BTS
Manager, then reinstall any other EX3.1 MPx.x BTS Managers.

2.4 Misleading TRX Test result with antenna optimised configuration (82582ESPE02)

Description:
In antenna optimized configuration two or more pipes are used (associated) in the
same sector which minimises the number of needed antenna ports and antenna lines:
no dedicated antenna is needed for Rx diversity signal. The RX signals are
automatically cross-connected between the pipes if RX diversity is enabled on BSC
and all TRX objects in the same sector are within the RX bandwidth (20 MHz @ 900
and 30 MHz @ 1800 band). The cross-connection works even if the pipes belong to
two different RF modules connected to same ESMx.

Antenna optimised sector is split on Ant1 and Ant3 due to power budget and TCH
TRX-4 is allocated on Ant1. When the TRX Test is run on TRX-4, Main Rx BER and
it’s Rx Result are reported. Div Rx BER and it’s Rx Result can not be tested as the
diversity is coming from Ant3.

The problem, however, is that the Div Rx BER and it’s Rx Result are reported as
‘NOT_TESTED’ which is misleading. After Pre4, Div Rx BER and Rx Result are
reported as ‘N/A’ indicating that test is not applicable to the tested TRX.

DN0974364
Issue 2-0 en
24/03/11
4 (10)
© Nokia Siemens Networks Company Confidential
MENU

2.5 BTS Manager allows user to enter illegal characters into SCF (80488ESPE02)

Description:
Currently the BTS Manager allows user to enter illegal characters into SCF, for
example in the Site location field.

2.6 RX diversity does not work after re-commissioning at BTS manager

(80980ESPE02)

Description:
BTS is commissioned with one RFM but no RX diversity antennas (Ant2, Ant4 or Ant
6) are taken in use, although RX diversity is activated in BSC (RDIV=Y). - Alarm 7607
TRX OPERATION DEGRADED 'Too few antennas available for Rx diversity is raised
as expected.

Then BTS is re-commissioned and RX diversity are taken in use in antenna settings
(Ant2, Ant4 or Ant6) and SCF is sent to BTS.
After one hour, RSSI alarm (put exact alarm name + number) is unexpectedly raised
and RSSI Comparison Values' in BTS manager shows values:
EX3.1: Ant1: -76, Ant2: -128
Ant2 value -128 dBm indicates that diversity is not working at all.

After BCF reset ' RSSI Comparison Values' in BTS manager shows expected values:
EX3.1: Ant1: -77, Ant2: -78
The results indicate that BTS was not using RX diversity antennas until BCF reset was
given.

2.7 BCCH reconfiguration does not work if TRX’s are split on two branches due to
frequency budget (69756ESPE02)

Description:
Two branches are needed for one Local Sector for one of two reasons:

• Power budget: The maximum output power of one branch is 60 W which can
be divided evenly across TRX objects assigned to that branch (e.g. 1 x 60 W or 3 x 20
W). If the power capability of one branch is exceeded (e.g. need to have 4 x 20 W
TRX’s on one Local Sector), two branches needs to be allocated for the configuration.
• Frequency budget: All TRX’s in a certain branch for FXDA units must be within
20 MHz window. If their frequencies are spread over a wider span (>20 MHz), then two
branches will be allocated for the configuration.

BCCH reconfiguration works if the TRX objects are spread across two branches due to
power budget. However, it fails if they are spread across two branches due to
frequency budget.

This correction requires also BSC SW S14 MP9.0 to work correctly.

2.8 Cannot send SCF if BCF is locked at the BSC when the BTS power is turned on
(26799ESPE05)

Description:
The scenario is a commissioned BTS is powered down and the BCF object is locked
at the BSC.

DN0974364
Issue 2-0 en
24/03/11
5 (10)
© Nokia Siemens Networks Company Confidential
MENU

When the BTS power is switched on, the BCF operational state stays in SW
downloading - even though there is no software download activity. It then becomes
impossible to send a new SCF if append commissioning is made.

To ease troubleshooting, in EX3.1 MP1.0 there will be a text change to the pop-up
window after unsuccessful SCF downloading saying that either SW downloading is on-
going or the BCF is in a locked state at the BSC.

Note: This problem does not happen when brand new HW is used at the site as the
ESMB/C modules are delivered in uncommissioned state.

2.9 Alarm 7606 “ESMx internal SRIO Link is Faulty” reported after BCF reset
(19553ESPE06)

Description:
During lab testing with the Site is in the commissioned state used configuration is
2+2+2+2+2+2 the RFM is connected to port 1 & Port 3 of ESMx the RFM is given a
Power reset by toggle of the power using the BTS control – Power control menu in 2G
Flexi BTS Site Manager.

When the RFM is detected the site resets and RFM becomes non functional. To
recover functionality a BCF reset is needed.
After the site reaches supervisory state the, Alarm 7606 “ESMx internal SRIO Link is
Faulty” is sometimes raised.

This problem is occasional.

2.10 Unnecessary alarms are raised during runtime (20436ESPE06)

Description:
A problem has been observed where any one of the following alarms could be
activated during runtime:
• 7606 TRX Faulty "ESMx internal SRIO Link is faulty"
• 7600 BCF FAULTY "ESMx System Module has lost connection to all modules
on optical ports"
• 7606 TRX FAULTY "ESMx System Module has lost connection to FXxx RF
Module"
• 7607 TRX OPERATION DEGRADED "Baseband bus major operation error
occurred in ESMx System Module"
• 7602 BCF NOTIFICATION "Baseband bus minor operation error occurred in
ESMx System Module"
• 7606 TRX FAULTY "ESMx System Module detected internal baseband bus
failure"

Note that problem is rare and visible only in some sites.

2.11 GCS Connection tool does not populate connection fields (67491ESPE04)

Description:
When the operator opens the database and selects node or connection properties, all
information exists.

Operator has to use fetch command using GCS node, manually typing in the name will
populate all the fields.

DN0974364
Issue 2-0 en
24/03/11
6 (10)
© Nokia Siemens Networks Company Confidential
MENU

If the operator goes in to fetch using GCS node, and types the required BCF and
selects fetch, and then goes to connection tool and chooses another node and selects
connect, the fields are not updated.

2.12 BTS Alarm window not refreshing properly in 2G Flexi BTS Manager
(66343ESPE04)

Description:
Occasionally when alarms are generated and then cancelled, user has to refresh the
alarm history to properly display the active alarm status.

This has been observed during testing, a maintenance alarm is generated on the
FPMA at the TRX level, and other multiple alarms were generated at the same time
and then immediately cancelled.

Not all alarms are shown as cancelled on screen as expected

2.13 Test Pattern Transmission is shown as ONGOING on the BTS Manager, even after
completion and reports not cleared when deleted (6770ESPE04)

Description:
With the BTS in supervisory mode and running Test Pattern Transmission the BTS
Manager is indicating that the test pattern is still transmitting after the request is made
to stop the test pattern.

This is a cosmetic problem with 2G Flexi BTS Site Manager as the Test Pattern
Transmission is stopped when the user executes the stop command.

2.14 Missing 7606-'ESMx System Module has lost connection to FXxx RF Module'
alarm (75595ESPE02)

Description:
Configuration: 2+2, 60 W per TRX (two RF modules used, one TRX per RFM).

During testing of the configuration, the RFM optical cable was removed from OPT-2
port on the ESMB generating alarm 7606 - 'ESMx System module has lost connection'
is raised as expected on both TRX’s allocated on the RFM.
A BCF lock/unlock was executed and after recovery 7606-'ESMx System module has
lost connection' alarm was not activated but instead, 7606 - 'TRX object allocation
failed' alarm activated.

The optical cable was re-connected to OPT-2 port and after a short time the site
recovered.

2.15 Timing Advance offset of 2-3 observed in KPI testing when compared to Flexi
EDGE (19810ESPE07)

Description:
During NSN internal lab testing small (1…3 steps) differences on the reported Timing
Advance (TA) values have been observed when comparing Flexi Multiradio and Flexi
EDGE BTS in same conditions, especially when mobiles are moving away from BTS.
However, the difference is negligible when comparing the reported TA values for static
mobiles or when mobiles are coming towards the BTS

DN0974364
Issue 2-0 en
24/03/11
7 (10)
© Nokia Siemens Networks Company Confidential
MENU

2.16 No alarm when no RF power coming out from any of the branches and TRX
objects in WO state (18937ESPE06)

Description:
A site was commissioned successfully, then the RF module was replaced with a new
one,
and this new RFM was taken in use (via ESM power cycle).

After power on, the site recovered and all objects reached WO state, with no
unexpected alarms, however, there was NO RF power coming out from any of the
branches.
There were no alarms raised to indicate the status.

The reason for the problem was a HW defect with the new RF module, however with
this defect there should have been an alarm to block the affected TRX from use.

2.17 Unexpected 7607 - RF module detected too high TX power alarm (49758ESPE01)

Description:
Following commissioning of the site the BCF comes to the supervisory state and the
alarm "7604 BTS OPERATION DEGRADED RF module detected too high TX power"
is raised for some of the TRX’s. PMAX parameter was set to minimum.

PMAX (PMAX1, PMAX2) parameter is used on BSC to reduce the maximum

transmitted power of the BTS from the peak power output of the TRX. The parameter
range on BSC is 0…30 with 2 dB steps (default value is 0 -> no attenuation applied).

Note that if TRX test is executed from BTS Site Manager with unsupported power
levels, TRX test failure 'High Power in Abis1-Air3 Loop' might be reported.

3. NEW FUNCTIONALITY

Major new features in EX3.1 MP1.0 are:

 GSM1800 RFM support
 PWE support (FIQA/FIYA in PDH mode only)
 FIQB/FIYB support
 Dynamic Power sharing
 Highlight support for the RF module in BTS Manager
 Rx-diversity sharing with other BTS
 GSM900J RFM support
 RET support
 Extended BCCH and Extended BCCH
 Hot insertion of RFM Module
 Longer than 200m optical cable between RF Module and System module
 RF Sharing with WCDMA (concurrent mode)

For details of supported features, please see the Feature Description document /1/ in
EX3.1 MP1.0 SW binder.

The following functionalities are excluded from the EX3.1 SW MP1.0:

 RRH support
 RFM Chaining
 4-way diversity
 Intelligent Downlink Diversity

DN0974364
Issue 2-0 en
24/03/11
8 (10)
© Nokia Siemens Networks Company Confidential
MENU

 DFCA
 LMU sync
 RFM block/unblock
 Antenna Hopping

4. 3RD PARTY CORRECTIONS

None

5. RESTRICTIONS

Full compatibility of Flexi Multiradio EDGE BTS /2/ can be found from EX3.1 MP1.0
SW binder.

6. RELEASE OBJECTS

BTS SW EX3.1 BTS SW EX3.1 MP1.0

Release Date 20-Oct-2010 24-Mar-2011

BTS Software BTSM3100.218 BTSM3110.069

A5/0 Build 118 Build 69
Version 3.16-0 Version 3.17-0
BTS Software BTSM3103.218 BTSM3113.069
A5/3 Build 118 Build 69
Version 3.16-3 Version 3.17-3
BTS Site BTS Site Manager BTS Site Manager
Manager Build 216 Build 67
Application Version 3.1 Version 3.1 MP1.0

SiteWizard - -
FIFA FIFA SW 1.3 FIFA SW 1.3
Code: P59303.01--D0 Code: P59303.01--D0
Build: FIF_1.3-02 Build: FIF_1.3-02
FlexiHub FHM4.0 FHM4.0
Manager Code: P38207.02--06 Code: P38207.02--06
Build: FHM_4.0-80 Build: FHM_4.0-80

7. PILOTING

EX3.1 MP1.0 has been piloted in several customer networks. Found problems have
been fixed in final EX3.1 MP1.0 SW, case details can be found from LGF /3/.

8. APPENDICES / REFERENCES

/1/ Flexi Multiradio BTS GSM/EDGE Feature Descriptions, DN0967559

/2/ Software Compatibility of Flexi Multiradio BTS GSM/EDGE, DN0947091
/3/ Flexi Multiradio EDGE BTS, List of Generic Faults, LGF-2GBTSmr-2011-w12
/4/ Flexi EDGE BTS, List of Generic Faults, LGF-2GBTSf-2011-w05, available in Nokia
Siemens Networks Online Services (NOLS).

Flexi Multiradio EDGE BTS Operating documentation is available at RG10 and RG20
level libraries:
GSM/EDGE BSS, rel. RG10(BSS), Operating Documentation, issue 06
GSM/EDGE BSS, rel. RG20(BSS), Operating Documentation, Issue 03

Check Siemens Networks Online Services for newer version of documentation sets.

DN0974364
Issue 2-0 en
24/03/11
9 (10)
© Nokia Siemens Networks Company Confidential
MENU

Disclaimer
The information in this document is subject to change without notice and describes
only the product defined in the introduction of this documentation. This documentation
is intended for the use of Nokia Siemens Networks customers only for the purposes of
the agreement under which the document is submitted, and no part of it may be used,
reproduced, modified or transmitted in any form or means without the prior written
permission of Nokia Siemens Networks. The documentation has been prepared to be
used by professional and properly trained personnel, and the customer assumes full
responsibility when using it. Nokia Siemens Networks welcomes customer comments
as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability,
capacity, or performance of the mentioned hardware or software products are given
“as is” and all liability arising in connection with such hardware or software products
shall be defined conclusively and finally in a separate agreement between Nokia
Siemens Networks and the customer. However, Nokia Siemens Networks has made
all reasonable efforts to ensure that the instructions contained in the document are
adequate and free of material errors and omissions. Nokia Siemens Networks will, if
deemed necessary by Nokia Siemens Networks, explain issues which may not be
covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible.
IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN
THIS DOCUMENTATION OR 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.
This documentation and the product it describes are considered protected by
copyrights and other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered
trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their
respective owners, and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2011. All rights reserved.

DN0974364
Issue 2-0 en
24/03/11
10 (10)
© Nokia Siemens Networks Company Confidential