Documente Academic
Documente Profesional
Documente Cultură
RX Diversity sharing
between Flexi EDGE BTS
and Flexi WCDMA BTS
Information is classified as
Internal
Public X
Customer Specific
1. Validity......................................................................................................................................... 3
2. Compatibility / Dependencies to other products ........................................................................... 3
3. Keywords .................................................................................................................................... 3
4. Summary ..................................................................................................................................... 3
5. HW / SW requirements ................................................................................................................ 3
6. supported configurations ............................................................................................................. 5
7. cabling Instructions ...................................................................................................................... 6
8. 3G commissioning ....................................................................................................................... 7
9. 2G commissioning ..................................................................................................................... 12
Contact:
Summary of changes:
1. VALIDITY
Product Category 1
Flexi WCDMA BTS software X
EUBB UltraSite
UltraSite
N.A
3. KEYWORDS
4. SUMMARY
This document describes how to configure RAN2514 RX Diversity Sharing into use when
using 3G BTS SW WN6.0 MP4 and 2G BTS SW EX3.1 MP1.0. This feature allows Rx
diversity over two RF-Modules in the same frequency band, WCDMA - GSM. Both
technologies are using dedicated RF-Modules. This function requires new Rel2 RF-
modules which includes RX out port (located at the front panel of the Radio Module).
This feature enables operators to reduce site complexity, site upgrade costs and to reuse
existing antenna system inside operating bandwidth.
• 2 antenna feeder lines instead of 4
• Only one x-pol antenna per sector
• No need for multiradio combiner (MRC)
• Enables high capacity per technology
5. HW / SW REQUIREMENTS
SW REQUIREMENTS:
HW REQUIREMENTS:
ADDITIONAL INFORMATION:
• No NEW BTS licences are needed in 3G because of the RX diversity sharing. Normal
licences according to the used configuration are needed like before.
• In 3G RNC, 900MHz support needs to be enabled.
• In 2G BSC, Flexi Multiradio TRX HW Activation is needed to be activated (BSC00311)
In RX diversity sharing both technologies are using dedicated Radio Modules with normal
RP3 optical connection. Both technologies need to have connection to upper network (3G
to RNC / 2G to BSC) as well. In RX diversity sharing both RX branches needs to be in the
same RX window, which is 20 MHz for 900 MR FXDA, this needs to be taken into account
when planning used frequencies.
Note! Same configuration rules applies also with RX diversity sharing than with normal A-
type configuration.
Antenna Sharing X
1
Abis RFM 900
System module
2
ESM
1+1+1@60W 3
3+3+3@20W
6+6+6@10W
1+1+1 @40W
2+2+2@20W
3+3+3@20W
1 RFM 900
System Module
Iub 2
FSM
3
How to proceed:
RF cabling for the RX diversity sharing is cross-fed from Radio Modules Rx out port to the
other Radio Modules Rx port, like in the picture below. Main antennas are cabled normally
and also optical cables between system module and radio module are connected
normally.
One cable kit is needed for triple radio pair, include 6 cables (2 per sector).
472454A RDSA Rx Diversity Sharing Kit 2m
Define Additional RX Gain parameter (value 28dB) for each diversity antennas where
RX diversity sharing is used.
Note: When MHAs are not commissioned, feeder loss is not included to calculation, so
this has to be taken into account when setting value to Additional RX Gain. If virtual MHA
would be defined instead of Additional RX gain, then MHA gain would need to set to 29dB
and feeder loss to -1dB.
To ensure optimal performance the Uplink delay parameter should also be set to
compensate additional delay in diversity branch according to existing HW and cables. For
example FXDA from antenna to ext out connector xx ns and the sharing cable [prod code]
xx ns.
First LNA1 should be commissioned to be used in This BTS and second LNA2 should be
commissioned to be used in Other BTS.
NOTE! In this release, it is recommended that when MHAs are used, they are controlled
by 3G.
After commissioning has been completed, the 3G BTS Site Manager view should look like
in the following picture. AISG MHA (MDGA) is used in Main antenna and RX diversity
sharing is not visible in 3G BTS Site Manager.
Following parameters should be used for defining virtual MHA in diversity antenna.
Note! MHA serial number and product code needs to be unique inside one BTS.
2G BTS commissioning is otherwise normal according to the used cabling and configuration, except in
the MHA settings page. There virtual MHAs must be defined for the diversity antenna lines when RX
diversity sharing between two RF modules is used.
Following parameters should be used for defining virtual MHA in diversity antenna.
Note! MHA serial number and product code needs to be unique inside one BTS.
Note! In future builds (EX3.1 MP3 =>) virtual MHA is not needed to be commissioned anymore.
Additional RX Gain parameter will be implemented also to 2G side and that should be used from EX3.1
MP3 onwards when commissioning RX diversity sharing in 2G side
.
If MHAs are really used in configuration Main branches, (One MHA e.g. MDGA where LNA1 is
connected to 3G RF Ant1 and LNA2 is connected to 2G RF Ant1), they need to be commissioned
normally.
Following parameters should be used for defining AISG MHA in Main antenna.
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.