Configuring RF Sharing

Nokia Networks

LTE Radio Access, Rel. RL60, Operating Documentation, Issue 04 Configuring RF Sharing DN09172017 Issue 01 Approval Date 2014-06-13

Configuring RF Sharing

The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein. This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia Solutions and Networks (“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 Solutions and Networks. 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 Solutions and Networks 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 Solutions and Networks welcome 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 Solutions and Networks reserves the right to change any such information and statements without notice. Nokia Solutions and Networks has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But, Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia Solutions and Networks 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 SOLUTIONS AND NETWORKS 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 Solutions and Networks’ proprietary and confidential information, which may not be distributed or disclosed to any third parties without the prior written consent of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright © 2014 Nokia Solutions and Networks. All rights reserved.

f

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 Solutions and Networks 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 Solutions and Networks for any additional information.

2

DN09172017

Issue: 01


Table of Contents This document has 43 pages

Issue: 01

1 1.1 1.2

Concepts and terminology............................................................. 6 Concept of RP3-blocking SW.........................................................6 Differences between RF Sharing and RX diversity sharing........... 7

2 2.1 2.2 2.3 2.4 2.5

RF Sharing deployment scenarios................................................. 8 Installing a new RF Sharing site.....................................................8 Adding RF Sharing to the existing site and activating locally.........9 Adding RF Sharing with RP3-blocking SW case 1.......................12 Adding RF Sharing with RP3-blocking SW case 2.......................15 Adding RF Sharing with locked WCDMA cells.............................17

3 3.1 3.2 3.3

Commissioning RF Sharing......................................................... 23 Commissioning WCDMA to RF Sharing...................................... 23 Commissioning LTE to RF Sharing.............................................. 26 Commissioning GSM to RF Sharing............................................ 29

4 4.1 4.2 4.3

RX diversity sharing..................................................................... 32 Rx diversity sharing requirements................................................32 Configuring RX diversity sharing WCDMA/LTE............................34 Configuring RX diversity sharing GSM.........................................39

5 5.1 5.2 5.3 5.4 5.5

Troubleshooting RF Sharing........................................................ 42 Missing RF Sharing license..........................................................42 Incorrect RP3 cabling...................................................................42 Incorrect filter shift in RX diversity sharing................................... 43 TRX Object allocation failed - GSM alarms..................................43 Remote connection to the Slave BTS is lost................................ 43

DN09172017

3


List of Figures

4

Figure 1

RP3-blocking SW concept....................................................................6

Figure 2

Main differences between RF Sharing and RX diversity sharing concepts............................................................................................... 7

Figure 3

Downloading SW without activation................................................... 13

Figure 4

RF Sharing with locked WCDMA cells concept..................................17

Figure 5

Commissioning - reconfiguration, target: BTS....................................19

Figure 6

GSM BTS - alarms at startup............................................................. 20

Figure 7

GSM BTS - selecting shared/dedicated modules...............................21

Figure 8

WCDMA - Concurrent Mode Settings.................................................24

Figure 9

WCDMA - Local Cell Resources........................................................ 25

Figure 10

WCDMA - Send Parameters.............................................................. 26

Figure 11

LTE - Enable EIF2 as RP3-01 interface............................................. 27

Figure 12

LTE - Concurrent Mode Settings........................................................ 28

Figure 13

GSM - Local Sector Settings.............................................................. 31

Figure 14

Rx diversity sharing requirements...................................................... 32

Figure 15

Additional Rx diversity cables connection.......................................... 33

Figure 16

Rx diversity signal paths.....................................................................34

Figure 17

RX diversity sharing: WCDMA - Local Cell Resources...................... 35

Figure 18

RX diversity sharing: WCDMA - Carrier settings................................ 36

Figure 19

RX diversity sharing: WCDMA - Antenna Line Management............. 37

Figure 20

RX diversity sharing: WCDMA - AISG MHA Settings: LNA1..............37

Figure 21

RX diversity sharing: WCDMA - AISG MHA Settings: LNA2..............38

Figure 22

RX diversity sharing: WCDMA - Antenna Line Settings - RX antenna modifications.......................................................................................38

Figure 23

WCDMA - Send Parameters.............................................................. 39

Figure 24

RX diversity sharing: GSM - Antenna Line Settings - TX (example).. 40

Figure 25

RX diversity sharing: GSM - Antenna Line Settings - RX...................41

Figure 26

RX diversity sharing: GSM - Antenna Line Settings - RX - in legacy SW......................................................................................................41

DN09172017

Issue: 01


List of Tables

Issue: 01

Table 1

WCDMA/LTE settings forcing the GSM recommissioning.................. 23

Table 2


Table 3


Table 4

Example of manual filter tuning (FXDA)............................................. 36

Table 5

Missing RF Sharing license................................................................ 42

Table 6

RFM/RRH cables cross-connected before GSM commissioning....... 42

Table 7

Incorrect filter shift.............................................................................. 43

Table 8

TRX Object allocation failed - GSM alarms........................................ 43

Table 9

Remote connection to the Slave BTS is lost...................................... 43

DN09172017

5

Concepts and terminology


1 Concepts and terminology 1.1 Concept of RP3-blocking SW The RP3-blocking software is a non-standard WCDMA or LTE build. The SW disables all the external RP3-01 links, so the System Module (SM) does not detect any RF Modules (RFMs), Remote Radio Heads (RRHs), Antenna Line Devices (ALDs), nor the other technology's SM. The SW is designed to prepare the site for RF Sharing when the user has, for example, no legal license to transmit on the added technology's bands. It prevents the new SM from automatically detecting the connected modules and taking over the Sync and Radio Master roles. RF Sharing is activated later, remotely. The SW allows for transmission commissioning, which enables a remote connection. The autoconnection feature can be used then. Figure 1: RP3-blocking SW concept presents the RP3-blocking SW usage in RF Sharing cases. Note that the presented configurations are exemplary, for supported configurations, see Flexi Multiradio BTS RF Sharing Released Configurations. To order the RP3-blocking SW, refer to Technical Support. Figure 1

RP3-blocking SW concept

WCDMA-GSM LTE-GSM WCDMA/LTESM with RP3-blockingSW

WCDMA-LTE

DedicatedRFM (nottransmitting)

SyncMaster

RadioMaster

WCDMASM DedicatedRFM LTESMwith RP3-blockingSW

DedicatedRFM

GSMSM SyncMaster RadioMaster

RemoteRFSharingactivation


RadioMaster RadioMaster

RadioMaster

GSMSM

6

WCDMASM

DedicatedRFM

SharedRFM

DN09172017

SyncMaster

SyncMaster

WCDMA/LTESM

SharedRFM LTESM

Issue: 01


Concepts and terminology

1.2 Differences between RF Sharing and RX diversity sharing There are two ways of deploying two technologies at one site with shared resources: RF Sharing and RX diversity sharing (also called antenna sharing). The main difference is that in RF Sharing the technologies work in Master-Slave mode and the same RFMs/RRHs are used by both technologies, while in RX diversity sharing both technologies are transmitting independently, using dedicated RFMs. Figure 2: Main differences between RF Sharing and RX diversity sharing concepts presents the main differences between those deployment cases. Note that the figure is only an example. Figure 2

Main differences between RF Sharing and RX diversity sharing concepts

RFSharing SyncMaster

RadioMaster Technology1 SystemModule

SharedRFM

MHAs

Antennas

MHAs

Antennas

Technology2 SystemModule

RXdiversitysharing RadioMaster Technology1 SystemModule

Technology1 dedicatedRFM RadioMaster

Technology2 SystemModule

Issue: 01

Technology2 dedicatedRFM

DN09172017

7

RF Sharing deployment scenarios


2 RF Sharing deployment scenarios The section contains the most typical deployment scenarios: • • • •

installing a new RF Sharing site adding RF Sharing to the existing site and activating locally adding RF Sharing with RP3-blocking SW adding RF Sharing with locked WCDMA cells

2.1 Installing a new RF Sharing site Purpose The purpose of this scenario is to prepare a new RF Sharing site. Both technologies' HW is installed and activated locally during the site visit. After the site visit both technologies are on air. Ensure that you have all the respective instructions to prepare the desired site.

Before the site visit 1

Prepare the configurations, depending on which technologies are used: a) For GSM: create the site on BSC. b) For WCDMA: create the site on RNC. Optional: Prepare Site Configuration Files (SCFs) for both technologies to save the site visiting time.

2

Install the correct GSM/WCDMA/LTE BTS Site Manager version on your computer(s). In case of RF Sharing with WCDMA, ensure you have all the required licenses downloaded on your computer.

g

It is recommended that you have two computers, which allows simultaneous connection to both technologies' Site Managers. 3

Check the supported SW for both technologies in RF Sharing Compatibility Matrix.

4

Optional: Update the SMs' SW. It is recommended that you update the new SMs' SW before the site visit (if possible) to reduce the site visit time.

During the site visit

8

DN09172017

Issue: 01



5

Install the HW, do the cabling, and connect to SMs via Local Management Ports (LMPs). To connect the modules for RF Sharing configurations, see the appropriate Creating RF Sharing Configurations (WCDMA-GSM, LTE-GSM, or WCDMA-LTE). For details, see the respective Installing and Cabling Flexi Multiradio documentation. Ensure that the RFM/RRH has the same SFP type as the SM - 3 Gbps or 6 Gbps. In case of LTE, always use 6 Gbps SFPs and optical links, when supported by the used HW.

6

g

Power up the Master technology SM (WCDMA or LTE) and ensure all the RFMs/RRHs and ALDs are detected and shown properly. FSMF is delivered with factory LTE SW. WCDMA Site Manager does not detect any RFMs/RRHs and ALDs until the SM is updated with WCDMA SW. For the update procedure instructions, see the Delivery Note, provided in the HW delivery box.

7

If not done before, update the SM SW to the desired version. If Incompatible SW version detected (0023) alarm is raised, update the SW again. Result The HW is now ready for commissioning.

8

Commission the Master technology for RF Sharing.

9

Repeat steps 5 and 6 for the Slave technology.

10 Commission the Slave technology for RF Sharing. In case GSM is the Slave technology, fetch the SCF from the Master technology's BTS and use it as a template in Hardware Configuration. Result The site is ready and both technologies are on air. Post requisites Before leaving the site ensure that: • • •

Both technologies are working properly without any unexpected alarms. Test calls (both voice and data) are successful in each cell/sector. All unused ports (for example LMP) are secured with IP caps.

2.2 Adding RF Sharing to the existing site and activating locally Purpose Typical initial status:

Issue: 01

DN09172017

9


• •


GSM is already on air, WCDMA or LTE is now added as a Master technology. WCDMA is already on air, LTE is now added as a Slave technology.

The purpose of this scenario is to add RF Sharing to the site. The other technology's HW is installed and RF Sharing is activated locally during the site visit. After the site visit both technologies are on air. Ensure that you have all the respective instructions to prepare the desired site.


Prepare the configurations, depending on which technologies are used: a) For GSM: create the site on BSC. b) For WCDMA: create the site on RNC. Optional: Prepare Site Configuration Files (SCFs) for both technologies to save the site visiting time.

2


g



4

Optional: Update the already deployed technology's SM SW. If the SW update is needed for the already deployed technology, update it remotely to save the site visit time.

5

Optional: Update the new technology's SM SW. It is recommended that you update the new technology's SM SW before the site visit (if possible). This reduces the site visit time and the eventual downtime of the already deployed technology's transmission. In case of a WCDMA use download the needed licenses to the WCDMA SM.

g

FSMF is delivered with factory LTE SW. WCDMA Site Manager does not detect any RFMs/RRHs and ALDs until the SM is updated with WCDMA SW. For the update procedure instructions, see the Delivery Note, provided in the HW delivery box. During the site visit

10

DN09172017

Issue: 01



6

Install the new HW. Do not connect the new SM to the already deployed SM and RFMs/RRHs.

7

Power up the new technology's SM. Update the SW, if not done before.

8

Power off the already deployed and the new SMs and connect cables. To connect the modules for RF Sharing configurations, see the appropriate Creating RF Sharing Configurations (WCDMA-GSM, LTE-GSM, or WCDMA-LTE). For details, see the respective Installing and Cabling Flexi Multiradio documentation. Ensure that the RFM/RRH has the same SFP type as the SM - 3 Gbps or 6 Gbps. In case of LTE, always use 6 Gbps SFPs and optical links, when supported by the used HW. Result The already deployed technology's traffic goes down.

9

Recommended (Optional): Switch the RFM/RRH power cables to the Master SM. The Shared RFMs/RRHs can be powered from either Master SM, Slave SM, or an external power supply, depending on the site environment. If the RFMs/RRHs are powered from the Slave SM and the Slave SM gets reset or a failure occurs, both technologies' traffic goes down.

g

Exception: in WCDMA-LTE case, if the Slave (LTE) SM is FSMF with Power Distribution Sub-module (FPFD), then the SM reset does not affect the power supply provided by FPFD. If the RFMs/RRHs are powered from the Master SM (as recommended) and the Slave SM gets reset or failure occurs, only the Slave technology traffic goes down. 10 Power up the Master technology SM and ensure all the RFMs/RRHs and ALDs are detected and shown properly. If Incompatible SW version detected (0023) alarm is raised, update the SW again. Result The HW is now ready for commissioning. 11 Commission the Master technology (WCDMA or LTE) for RF Sharing. If the SCF was not created before the site visit, save the Master technology's SCF for later use in the GSM (Slave) technology commissioning. Result The Master technology cells go on air (in both shared and dedicated RFMs/RRHs).

Issue: 01

DN09172017

11



12 Power up the Slave technology (LTE or GSM) and commission it for RF Sharing. In case of GSM, the commissioning can be conducted with Undo Commissioning (removes both Hardware Configuration and Transmission Parameters) or Change Settings Manually procedures. Before performing Undo Commissioning save the current SCF. It contains the transmission settings and can be used as a back-up. To commission GSM, fetch the SCF from the Master technology's BTS and use it as a template in Hardware Configuration. Result The site is ready and both technologies are on air. Post requisites Before leaving the site ensure that: • • •

Neither of the technologies' Site Managers shows any unexpected alarms. Both technologies are transmitting properly (make test calls). All unused ports (for example LMP) are secured with IP caps.

2.3 Adding RF Sharing with RP3-blocking SW case 1 Case 1: The GSM site is already active. WCDMA or LTE is now added as a Master technology. Purpose The purpose of this scenario is to add RF Sharing with RP3-blocking SW to the site. The WCDMA or LTE HW is installed, RF Sharing is set locally, and the RP3-blocking SW is downloaded during the site visit. After the site visit the new technology is off air. GSM is transmitting in dedicated mode with full power and frequency budgets. RF Sharing is activated later, remotely. Ensure that you have all the respective instructions to prepare the desired site. Use case The case is deployed, for example, when the user has not yet got a legal license to transmit on WCDMA or LTE band. The scenario is adopted when there is no WCDMA or LTE transmission in dedicated mode due to RP3-blocking SW. For details on RP3blocking SW, see Concept of RP3-blocking SW.



12

DN09172017

Issue: 01


g




3

Optional: Update the new technology's SM SW. It is recommended that you update the new technology's SM SW before the site visit (if possible). This reduces the site visit time and the eventual downtime of the already active GSM transmission. a) Connect to the SM locally via Local Management Port (LMP) and update the SW to the desired version (not the RP3-blocking SW). b) Download the RP3-blocking SW to the SM; do not activate it. Untick the Activate SW after update tick-box as in Figure 3: Downloading SW without activation.

g

FSMF is delivered with factory LTE SW. WCDMA Site Manager does not detect any RFMs/RRHs and ALDs until the SM is updated with WCDMA SW. For the update procedure instructions, see the Delivery Note, provided in the HW delivery box. Figure 3

Downloading SW without activation

c) In case of a WCDMA use download the needed licenses to the WCDMA SM. d) Commission TRS. On Commissioning page select Target: TRS. During the site visit 4

Install the new HW, do the cabling, and connect to SMs via LMPs. To connect the modules for RF Sharing configurations, see the appropriate Creating RF Sharing Configurations (WCDMA-GSM or LTE-GSM). For details, see the respective Installing and Cabling Flexi Multiradio documentation.

Issue: 01

DN09172017

13



Ensure that the RFM/RRH has the same SFP type as the SM - 3 Gbps or 6 Gbps. In case of LTE, always use 6 Gbps SFPs and optical links, when supported by the used HW. 5

Power off GSM SM. Result GSM goes off air.

6

Recommended (Optional): Switch the RFM/RRH power cables to the Master SM. The Shared RFMs/RRHs can be powered from either Master SM, Slave SM, or an external power supply, depending on the site environment. If the RFMs/RRHs are powered from the Slave SM and the Slave SM gets reset or a failure occurs, both technologies' traffic goes down. If the RFMs/RRHs are powered from the Master SM (as recommended) and the Slave SM gets reset or failure occurs, only the Slave technology traffic goes down.

7

Power up the Master technology SM and ensure all the RFMs/RRHs and ALDs are detected and shown properly. Update the new technology's SM SW, if not done before. If Incompatible SW version detected (0023) alarm is raised, update the SW again. Result The Master technology's HW is now ready for commissioning.

8

Commission the Master technology (WCDMA or LTE) for RF Sharing. Important: In case of WCDMA, keep the WCELs locked at RNC. Save the Master technology's SCF for later use in the GSM commissioning.

9

Update the Master technology's SM with RP3-blocking SW. Result Expected alarm is raised: "Failure in optical RP3 interface (0010)".

10 Power up the GSM SM. Result GSM is back on air in dedicated mode. WCDMA or LTE is ready for remote activation. Before leaving the site ensure that: • • •

14

All the cables are working properly (checked in Step 8) Neither of the technologies' Site Managers shows any unexpected alarms. GSM is transmitting properly (make test calls).

DN09172017

Issue: 01


•


All unused ports (for example LMP) are secured with IP caps.

After the site visit When the legal license to transmit the Master technology is acquired. 11 WCDMA-specific step: Create the 3G configuration plan at RNC. 12 Connect remotely to the Master technology's SM and update the SW to the active one (not RP3-blocking). Master technology's SM detects the Shared RFMs/RRHs. If Incompatible SW version detected (0023) alarm is raised, update the SW again. 13 Connect remotely to GSM (Slave) SM. a) Optional: update the GSM SM's SW, if needed. b) Commission GSM to RF Sharing. Fetch the SCF from the Master technology's BTS and use it as a template in Hardware Configuration. Result GSM gets reset and OMUSIG connection may be lost, including loss of the remote Site Manager connection. 14 Give a reset to the Master technlogy SM. The action resets also the GSM SM. After the reset the OMUSIG and remote Site Manager connection are restored.

2.4 Adding RF Sharing with RP3-blocking SW case 2 Case 2: The WCDMA site is already active. LTE is now added as a Slave technology. Purpose The purpose of this scenario is to add LTE with RP3-blocking SW to the site, for later RF Sharing activation. The LTE HW is installed and the RP3-blocking SW is downloaded during the site visit. After the site visit LTE is off air. WCDMA is transmitting in dedicated mode with full power and frequency budgets. RF Sharing is activated later, remotely. Ensure that you have all the respective instructions to prepare the desired site. For details on RP3-blocking SW, see Concept of RP3-blocking SW.

Prerequisites

Issue: 01

DN09172017

15



1

Install the correct LTE BTS Site Manager version on your computer.

2

Optional: Update the LTE SM with RP3-blocking SW. It is recommended that you update the LTE SM's SW before the site visit (if possible). This reduces the site visit time. a) Connect to the SM locally via Local Management Port (LMP) and update the SW to the RP3-blocking SW. b) Commission TRS. On the Commissioning page, select Target: TRS.

During the site visit 3

Install the LTE HW and do the cabling. To connect the modules for RF Sharing configurations, see Creating RF Sharing WCDMA-LTE Configurations. For details, see the respective Installing and Cabling Flexi Multiradio documentation. Ensure that the RFM/RRH has the same SFP type as the SM - 3 Gbps or 6 Gbps. In case of LTE, always use 6 Gbps SFPs and optical links, when supported by the used HW.

4

If not done before, update the LTE SM with RP3-blocking SW as described in Optional: Update the LTE SM with RP3-blocking SW. Result LTE is ready for remote activation. Before leaving the site ensure that: • • •

Neither of the technologies' Site Managers shows any unexpected alarms. WCDMA is transmitting properly (make test calls). All unused ports (for example LMP) are secured with IP caps.

After the site visit

16

DN09172017

Issue: 01



5

Create the 3G configuration plan at RNC and prepare all the required WCDMA licenses.

6

Connect remotely to WCDMA SM, commission the RF Sharing, and save the backup commissioning file.

7

Connect remotely to the LTE SM, update the SW to the active one (not RP3blocking), and commission the RF Sharing.

2.5 Adding RF Sharing with locked WCDMA cells Purpose Initial status: WCDMA (on Band A, for example 2100 MHz) and GSM (on Band B, for example 900 MHz) are already on air, both in dedicated mode. WCDMA Band B WCEL(s) are created in RNC and kept in locked state. Figure 4

RF Sharing with locked WCDMA cells concept

SyncMaster

WCDMASM

DedicatedRFM

BandA

RadioMaster

SharedRFM transmitting onlyGSM

GSMSM

BandB

RadioMaster


SyncMaster

WCDMASM

DedicatedRFM

BandA

RadioMaster

GSMSM

SharedRFM transmitting WCDMA+GSM

BandB

RadioMaster

The purpose of this scenario is to add RF Sharing, in which WCDMA and GSM share the Band B (currently used by GSM). The new optical cabling is done, RF Sharing is prepared locally during the site visit. After the site visit the shared RFMs/RRHs transmit only the GSM traffic with limited power budget (due to RF Sharing), overlapping the

Issue: 01

DN09172017

17



planned WCDMA carrier bandwidth (BW). Later, the overlapping GSM TRXs are removed and WCDMA cells for RF Sharing are activated remotely. Figure 4: RF Sharing with locked WCDMA cells concept presents the deployment case. Ensure that you have all the respective instructions to prepare the desired site. Use case This scenario is deployed in cases where the user, for example, has not yet got a legal license to transmit WCDMA on Band B. The scenario is used when WCDMA transmission in dedicated mode (on Band A) is needed (RP3-blocking SW cannot be used).

Prerequisites 1

Install the correct GSM/WCDMA BTS Site Manager version on your computer(s). Ensure you have all the required WCDMA licenses downloaded on your computer.

g


Optional: Update the SMs' SW. If the SW update is needed for the WCDMA and GSM SMs, update them remotely to save the site visit time.

3

Back up the GSM commissioning file.

During the site visit 4

Switch off the WCDMA and GSM SMs. Result The WCDMA and GSM traffic goes down.

5

Install the new optical cables for RF Sharing. To connect the modules for RF Sharing configurations, see Creating RF Sharing WCDMA-GSM Configurations . For details, see the respective Installing and Cabling Flexi Multiradio documentation. Ensure that the RFM/RRH has the same SFP type as the SM - 3 Gbps or 6 Gbps. In case of LTE, always use 6 Gbps SFPs and optical links, when supported by the used HW.

6

Commission WCDMA to RF Sharing. a) Switch on the WCDMA SM. Connect to the SM locally and run the BTS Site Manager. If Incompatible SW version detected (0023) alarm is raised, download the SW again.

18

DN09172017

Issue: 01



Result Band B RFM/RRH is detected. If the FSMx's optical port for Band A RFM/RRH has not been changed, the dedicated cells go back on air. b) In BTS Site Manager, select reconfiguration, as shown in Figure 5: Commissioning - reconfiguration, target: BTS, and update the information regarding the shared Band B RFM(s)/RRH. Figure 5

Commissioning - reconfiguration, target: BTS

c) Save the commissioning parameters and send them to BTS. BTS gets reset and is recommissioned to RF Sharing mode. Result Band A cells are active, Band B cells are inactive (locked in RNC). 7

Commission GSM to RF Sharing. a) Power up the GSM SM. Connect to the SM locally and run the BTS Site Manager. Two alarms are activated: • •

Issue: 01

BCF NOTIFICATION: Shared RF module detected two synchronization master sources. TRX FAULTY: TRX object allocation failed in RF module.

DN09172017

19


Figure 6


GSM BTS - alarms at startup

b) In BTS Site Manager select "Commissioning/Change settings manually". Proceed to Hardware Configuration page, select Specify from file and use the WCDMA BTS SCF. Choose RFMs to be shared/dedicated in a pop-up window, as in Figure 7: GSM BTS - selecting shared/dedicated modules. If the shared RFMs'/RRHs' climate-control has not been set in WCDMA commissioning, a window pops up, press Close to ignore it.

20

DN09172017

Issue: 01



Figure 7

GSM BTS - selecting shared/dedicated modules

c) Proceed to Local Sector Settings page and create the GSM configurations again. Important: make sure that BCCH is outside the planned WCDMA carrier BW. The other TRXs can overlap the WCDMA carrier BW. d) Proceed to Transmission Parameters and select "Do not change settings". e) On the last page, press Send SCF. Result All TRXs are in working state. At this point, non-blocking alarms for the TRXs which overlap with WCDMA carrier BW: "TRX OPERATION DEGRADED: TRX object allocation failed in RF module" (7607) are expected. Before leaving the site ensure that: • • •

Neither of the technologies' Site Managers shows any unexpected alarms. Both technologies transmit properly (make test calls). All unused ports (for example LMP) are secured with IP caps.

After the site visit Perform the steps only when the legal license to transmit WCDMA on band B is acquired.

Issue: 01

DN09172017

21


8


Connect remotely to the BSC and perform the TRX removal procedure: a) Lock the BCF - command ZEFS b) Lock the BTSs (sectors) on BSC - command ZEQS c) Lock all the TCH-TRXs overlapping the WCDMA carrier BW - command ZERS

g

Note that TCH-TRXs have to be allocated at least 2 MHz away from the WCDMA cell's center frequency. Thus overlapping the edges of WCDMA cell bandwidth is allowed. d) Delete the locked TCH-TRXs - command ZERP e) Unlock the GSM BTS (sector) - command ZEQS f)

Unlock the BCF - command ZEFS

Result The GSM TRXs go on air. 9

Unlock the WCDMA Band B WCELs on RNC. Result The WCDMA Band B cells go on air.

22

DN09172017

Issue: 01


Commissioning RF Sharing

3 Commissioning RF Sharing 3.1 Commissioning WCDMA to RF Sharing Purpose Follow these steps to commission WCDMA (the Master technology) for: • •

RF Sharing WCDMA-GSM RF Sharing WCDMA-LTE

Make sure that all the appropriate steps in Deployment scenarios have been completed.

g g

Note that the RF Sharing is a part of the commissioning procedure. The commissioning procedures are described in detail in the technology-specific documents. The RF Sharing commissioning steps have to be taken in addition to the technology-specific steps. Note that GSM/EDGE System Module needs to be recommissioned (using new SCF fetched from WCDMA or LTE) when the following settings (if related to RF Sharing) are changed in the Master technology BTS: Table 1

WCDMA/LTE settings forcing the GSM recommissioning WCDMA

LTE Concurrent Mode Settings

Local Cell Resources - Antenna settings Local Cell Resources - Carrier Power settings Local Cell Resources - MIMO settings WCDMA Carrier Candidates and Local Cell Group Settings - WCDMA carrier frequency (UARFCN)

LTE Carriers - Downlink (Tx) Carriers and LTE Bandwidth

Antenna Line Management (AISG communication, DC voltage) Antenna Line Settings RET settings Radio Module External Fault and Control Settings

Always be sure that the Slave technology's SCF is up-to-date with the Master's SCF. The preconditions are: • • • •

Issue: 01

The BTS Site Manager is running and connection to the BTS is established. Appropriate SW and licenses are downloaded to the BTS. The RFMs/RRHs and ALDs are correctly detected. There are no unexpected alarms.

DN09172017

23


1


Start the commissioning. Select Commissioning, Target: BTS, Commissioning type: • •

if the WCDMA BTS has not been commissioned at all: Template/Planned/Manual if the WCDMA BTS has already been commissioned: Reconfiguration

Result The BTS Settings page appears. Note that the Slave technology (GSM or LTE) System Module is not detected yet. 2

Proceed to Concurrent Mode Settings. Tick the RF sharing enabled check box, choose the shared technologies (3G-2G or 3G-LTE), enter the product code and serial number of the Slave SM, and choose the shared RFMs/RRHs. Figure 8: WCDMA - Concurrent Mode Settings shows exemplary settings for 3G-2G RF Sharing.

g

At least one RFM/RRH must be selected as shared. Figure 8

3

WCDMA - Concurrent Mode Settings

Proceed to Local Cell Resources. Remember the settings on this page, as they affect the later Slave technology settings. Figure 9: WCDMA - Local Cell Resources shows exemplary settings for 3G2G RF Sharing

24

DN09172017

Issue: 01


g


Make sure that the sum of both WCDMA and LTE/GSM carriers power does not exceed the RFM's/RRHs' maximum output power. (Except when BSS21507: Flexible MCPA TX Power Pooling is activated in GSM.) Figure 9

4

WCDMA - Local Cell Resources

Proceed to WCDMA Carrier Candidates and Local Cell Group Settings. Enter the UARFCN channel value for each Local Cell (use the same value as defined in the RNC). These UARFCN values are stored in the SCF and they are later used for the Slave technology commissioning. Thus incorrect values may cause TRX object allocation issues in GSM.

Issue: 01

DN09172017

25


g


Make sure that all the WCDMA carriers along with the GSM TRXs/LTE carriers are within the RFMs'/RRHs' bandwidths. Note that TCH-TRXs have to be allocated at least 2 MHz away from the WCDMA cell's center frequency. Thus overlapping the edges of WCDMA cell bandwidth is allowed. 5

Proceed to Radio Module External Fault and Control Settings. Every Radio Module external alarm can be commissioned for either or both of the two technologies. For example, if an alarm is commissioned for WCDMA, it is visible only from the WCDMA side.

6

Proceed to the last page - Send Parameters. Select the appropriate Send option: • •

if the WCDMA BTS has not been commissioned: All parameters if the WCDMA BTS has been already commissioned: Only changes

Click Send Parameters. Figure 10

WCDMA - Send Parameters

Result The WCDMA SM gets reset and the RF Sharing is activated.

3.2 Commissioning LTE to RF Sharing Purpose Follow these steps to commission LTE for: • •

RF Sharing LTE-GSM RF Sharing WCDMA-LTE


g

26

Note that the RF Sharing is a part of the commissioning procedure. The commissioning procedures are described in detail in the technology-specific documents. The RF Sharing commissioning steps have to be taken in addition to the technology-specific steps.

DN09172017

Issue: 01


g


Note that GSM/EDGE System Module needs to be recommissioned (using new SCF fetched from WCDMA or LTE) when the following settings (if related to RF Sharing) are changed in the Master technology BTS: WCDMA/LTE settings forcing the GSM recommissioning

Table 2

WCDMA





Always be sure that the Slave technology's SCF is up-to-date with the Master's SCF. The preconditions are:

•

The BTS Site Manager is running and connection to the BTS is established. Appropriate SW is downloaded. The RFMs/RRHs and ALDs are correctly detected. There are no unexpected alarms.

1

Start the commissioning.

• • •

In case of FSMF go through the TRS commissioning first and check the "Enable EIF2 as RP3-01 interface". Figure 11

LTE - Enable EIF2 as RP3-01 interface

Select Commissioning, Target: BTS, Commissioning type: • •

Issue: 01

when the SCF has been prepared before: Template when there is no SCF file: Manual

DN09172017

27



Result The BTS Settings page appears. Note that the other technology (GSM or WCDMA) System Module is not detected yet. 2

Proceed to Concurrent Mode Settings. Tick the RF sharing enabled check box, choose the shared technologies (LTE-2G or LTE-3G), enter the product code and serial number of the other technology SM, and choose the shared RFMs/RRHs. Figure 12: LTE - Concurrent Mode Settings shows exemplary settings for LTE-3G RF Sharing.

g

At least one RFM/RRH must be selected as shared. Figure 12

3

LTE - Concurrent Mode Settings

Proceed to Cell Resources. In case of RF Sharing LTE-GSM, remember the settings on this page, as they affect the later settings in GSM. In case of RF Sharing WCDMA-LTE, calculate the available power, taking into account the values already commissioned to WCDMA.

g

Make sure that the sum of both LTE and WCDMA carriers/GSM TRXs power does not exceed the RFM's/RRH's maximum output power. (Except when BSS21507: Flexible MCPA TX Power Pooling is activated in GSM.) 4

Proceed to LTE Carriers. Enter the EARFCN channel value for each Local Cell. These EARFCN values are stored in the SCF and is later used for the GSM commissioning. Select the appropriate Bandwidth. Ensure the Bandwidth is supported by the used HW configuration. For details see Flexi Multiradio BTS RF Sharing Released Configurations.

28

DN09172017

Issue: 01


g


Make sure that all the LTE carriers along with the GSM TRXs/WCDMA carriers are within the RFM's/RRH's UL/DL instantaneous bandwidth, and that they are not overlapping. 5

Proceed to Radio Module External Fault and Control Settings. Every Radio Module alarm can be commissioned for either or both of the two technologies. For example, if an alarm is commissioned for LTE, it is visible only from the LTE side.

6

Proceed to the last page - Send Parameters. Select Send: All parameters. Save Parameters, if the SCF is needed for later GSM commissioning, then Send Parameters Result The LTE SM resets and the RF Sharing is activated.

3.3 Commissioning GSM to RF Sharing Purpose Follow these steps to commission GSM (the Slave technology) to: • •

RF Sharing WCDMA-GSM RF Sharing LTE-GSM


g

Issue: 01

Note that the RF Sharing is a part of the commissioning procedure. The commissioning procedures are described in detail in the technology-specific documents. The RF Sharing commissioning steps have to be taken in addition to the technology-specific steps.

DN09172017

29


g


Note that GSM/EDGE System Module needs to be recommissioned (using new SCF fetched from WCDMA or LTE) when the following settings (if related to RF Sharing) are changed in the Master technology BTS: Table 3

WCDMA/LTE settings forcing the GSM recommissioning WCDMA





Always be sure that the Slave technology's SCF is up-to-date with the Master's SCF. The preconditions are:

•

The BTS Site Manager is running and connection to the BTS is established. Appropriate SW is downloaded. The RFMs/RRHs and ALDs are correctly detected. There are no unexpected alarms.

1

Start the commissioning.

• • •

Select Commissioning Wizard, Change settings manually 2

Proceed to Hardware Configuration. Select Specify from file and browse for WCDMA/LTE SCF. If the shared RFMs'/RRHs' climate-control has not been set in WCDMA or LTE commissioning, a window pops up, press Close to ignore it.

3

Proceed to Module Configuration. The shared modules are shown (taken from the Master technology's SCF). If needed, add the GSM-dedicated RFMs/RRHs.

30

DN09172017

Issue: 01


4

g


Proceed to Local Sectors Settings. Note that the “Total max. Capacity” shows a value for both shared technologies. Figure 13: GSM - Local Sector Settings shows exemplary settings for LTE-2G RF Sharing. In the example LTE uses 8 W per pipe out of available 60 W - the power left for GSM is 52 W, which allows for five TRXs, 10 W each. Figure 13

5

GSM - Local Sector Settings

Proceed to FRM External Alarm and Control Settings. Every Radio Module alarm can be commissioned for either or both of the two technologies. For example, if an alarm is commissioned for GSM, it is visible only from the GSM side.

6

Proceed to the last page - Site Commissioning File. Select Send SCF. Result The GSM SM gets reset and the RF Sharing is activated.

Issue: 01

DN09172017

31

RX diversity sharing


4 RX diversity sharing 4.1 Rx diversity sharing requirements Requirements and detailed information regarding Rx diversity sharing. The following requirements have to be fulfilled to configure RX diversity sharing: • • • •

Only RF Modules (RFMs) with "Rx Out" port can be used. Both RFMs operate in the same frequency band. Both GSM and WCDMA/LTE carriers are within the RFM's instantaneous BW. The Rx (UL) filters in both pipes cover the same instantaneous part of the UL band.

Figure 14

Rx diversity sharing requirements 3GPP DLBW

RFMinstantaneousDLBW

WCDMA/ LTEBTS RFM1

DLfiltercenterfrequency

WCDMA/LTE carrier

Frequency

2GBTS RFM2 GSMTRXs

Frequency

Filter Tuning In case the RFM's instantaneous BW is narrower than the 3GPP band BW, the RF Module's filter may need a manual shift to meet the Rx diversity sharing requirements. In WCDMA and LTE BTS Site Manager it is possible to shift the DL filter and in 2G BTS Site Manager it is possible to shift the UL filter. The DL and UL band filters are coupled, so they are both shifted simultaneously.

Calculating GSM frequencies In a typical scenario, a GSM-dedicated BTS already exists on a site. WCDMA or LTE, with predefined carrier frequencies, is brought to the same site and existing antenna lines are used for both technologies with Rx diversity sharing. The GSM TRX frequencies are usually changed to accommodate the WCDMA/LTE carriers in the same band. Thus the available GSM ARFCNs have to be calculated. Example: calculating available ARFCNs, when FXDA RF Module (20 MHz Rx filter pass band BW) is used and the WCDMA uplink (Rx) center frequency is set to 905 MHz. 1. Calculate the lower and the higher Rx filter cutoff frequencies: [Rx center frequency] -/+ [Rx filter pass band BW]/2 • •

32

lower frequency [MHz]: 905 - 20/2 = 895 higher frequency [MHz]: 905 + 20/2 = 915

DN09172017

Issue: 01



2. The available ARFCN channel frequencies have to be greater than 895 MHz and lower than 915 MHz: • •

the lowest ARFCN: 26 (895.2 MHz) the highest ARFCN: 124 (914.8 MHz)

In case of WCDMA, the GSM TRXs (except for BCCH) can overlap the edges of the WCDMA carrier BW - the TRXs have to be allocated at least 2 MHz away from the WCDMA carrier's center frequency. In case of LTE, the GSM TRXs have to be allocated outside the LTE carrier BW. For example, when LTE carrier BW is 10 MHZ, the GSM TRXs have to be allocated at least 5.1 MHz away from the LTE carrier's center frequency.

Rx diversity cabling Rx diversity sharing requires two additional RF cables for each sector. Those cables connect the Rx Out port of the first RFM and Ant2/4/6 (Rx) port of the second RFM. A set of six cables (allowing for three sectors) is delivered in "RDSA Rx Diversity Sharing Kit 2m", sales code 472454A. Figure 15

Additional Rx diversity cables connection PWRIN

ANT 6 Rx

ANT 5 Tx/Rx

ANT 4 Rx

ANT 3 Tx/Rx

ANT 2 Rx

ANT 1 Tx/Rx

ANT 1 RxOut

ANT 3 RxOut

ANT 5 RxOut

OPT 1

EAC

OPT 2 OPT 3

Additional RXdiversity cables

Sector3

PWRIN

ANT 6 Rx

ANT 5 RxOut

ANT 5 Tx/Rx

Sector2

ANT 4 Rx

ANT 3 Tx/Rx

ANT 2 Rx

ANT 1 Tx/Rx

ANT 1 RxOut

ANT 3 RxOut

EAC

Sector1

OPT 1

OPT 2 OPT 3

Total uplink gain The BTS receiver expects a certain fixed total gain in the uplink (UL) path, regardless the configuration. The total gain at RX Diversity and RX Main have to be approximately equal (the difference have to be less than few dB). The internal LNA gain at both RX Main and RX Diversity paths is adjusted by the BTS, depending on the parameters set during the commissioning. In Rx diversity sharing, both paths have to be commissioned separately. •

LNA in the Rx Main path: – –

Issue: 01

When there is no MHA nor other additional gain in the feeder lines: the LNA gain is set to high, to optimize the Rx sensitivity. When there is an MHA or other additional gain in the feeder lines: the LNA gain is adjusted by the BTS SW according to the values set during the commissioning.

DN09172017

33



•

LNA in the Rx Diversity path: The LNA gain is set to low as the signal is already amplified by the other RFM. The eventual gain of an MHA is also taken into account by the other RFM.

The additional gain seen by the receiving RFM equals +28 dB (+29 dB from Rx Out port - 1 dB for Rx diversity cable loss). Figure 16

Rx diversity signal paths Antenna

Lowgain setbyBTS

TotalgainatRXDiversity andRXMain isapproximatelythesame

Bias-T

LNA

ANT2 Rx

RX filter

RXDiversity

ANT1 RxOut

LNA

RF block

RX filter

RXMain

Bias-T

VSWR Det

TXRX

TX filter

PA

Optional MHA MHA MHA LNA1 LNA2

ANT1 Tx/Rx

RFM1 Rxdiversitycables 1dBcableloss NoMHA:HighgainsetbyBTS MHA:gainadjustedbyBTS

GainatRxOut is+29dB

Bias-T

LNA

ANT2 Rx

RX filter

RXDiversity

ANT1 RxOut

LNA

RF block

RX filter

RXMain

Bias-T

VSWR Det

TXRX

PA

TX filter

ANT1 Tx/Rx

RFM2

4.2 Configuring RX diversity sharing WCDMA/LTE Follow these steps to configure RX diversity sharing in WCDMA or LTE Initial status The site is prepared for RX diversity sharing - the cabling is done and BTS Site Manager connection to the SMs is established. The commissioning procedure is the same as in the dedicated mode, except for the additional steps described in this section. The pictures in this section show the WCDMA Site Manager, but the same steps are applicable for LTE as well.

34

DN09172017

Issue: 01


1


Start the commissioning. Select Commissioning, Target: BTS, Commissioning type: • •

2

if the BTS has not been commissioned: Template/Manual if the BTS has been already commissioned: Reconfiguration

Proceed to Local Cell Resources (WCDMA) or Cell Resources (LTE). Set three 1TX/2RX sectors. Figure 17

3

RX diversity sharing: WCDMA - Local Cell Resources

Proceed to WCDMA Carrier Candidates and Local Cell Group Settings (WCDMA) or LTE Carriers (LTE). Select the appropriate UARFCN/EARFCN value and Bandwidth (for LTE). The RFM's filter position is set automatically. If the manual shift is needed, tick the Override nominal frequency check box and set the center frequency.

Issue: 01

DN09172017

35



g

The allowed values are calculated (in MHz) as follows: • •

The lowest value: 3GPP Band start frequency + 1/2*RFM's UL filter BW The highest value: 3GPP Band stop frequency - 1/2*RFM's UL filter BW

Example: FXDA (900 MHz) RFM has 20 MHz UL filter BW, the center frequency tuning range is shown in Table 4: Example of manual filter tuning (FXDA). Table 4

Example of manual filter tuning (FXDA) DL start frequency [MHz]

UL start frequency [MHz]

DL stop frequency [MHz]

UL stop frequency [MHz]

900 MHz band frequency 925 range

880

960

915

Manual tuning range of FXDA 935 (925 + 10) UL filter center frequency

890 (880 + 10)

950 (960 - 10)

905 (915 - 10)

Figure 18

g

RX diversity sharing: WCDMA - Carrier settings

Steps Proceed to Antenna Line Management. and Proceed to AISG MHA Settings. are required only when WCDMA or LTE provides power to MHAs and controls them. 4

Proceed to Antenna Line Management. Tick the DC voltage check box for the antenna ports in which the MHAs are used.

36

DN09172017

Issue: 01



Figure 19

5

RX diversity sharing: WCDMA - Antenna Line Management

Proceed to AISG MHA Settings. Assign the first LNA to This BTS and the second LNA to Other BTS as it is used by GSM. Figure 20

Issue: 01

RX diversity sharing: WCDMA - AISG MHA Settings: LNA1

DN09172017

37



Figure 21

6

RX diversity sharing: WCDMA - AISG MHA Settings: LNA2

Proceed to Antenna Line Settings. Use regular, site-specific values and settings on TX antenna ports (ANT1, ANT3, and ANT 5). For RX antenna ports (ANT2, ANT4, and ANT6) use the following modifications when using NSN RDSA cables: • • • •

Set Feeder loss to "0" Set Additional RX gain to "28" Set Uplink delay to "10" RTT measurements are done as usual, based on the site-specific conditions. There are no special requirements because of RX diversity sharing.

Figure 22

38

RX diversity sharing: WCDMA - Antenna Line Settings - RX antenna modifications

DN09172017

Issue: 01


7


Proceed to the last page - Send Parameters. Select the appropriate Send option: • •

if the WCDMA/LTE BTS has not been commissioned: All parameters if the WCDMA/LTE BTS has been already commissioned: Only changes

Click Save Parameters, if needed, then Send Parameters. Figure 23

WCDMA - Send Parameters

In the commissioning report check if the parameters are set correctly. This can also be checked in Site Information, after the commissioning. Result The SM gets reset and the RX diversity sharing is ready from WCDMA/LTE side. 8

Check the BTS Hardware view (the main Site Manager view) Ensure there are no unexpected alarms.

4.3 Configuring RX diversity sharing GSM Follow these steps to configure RX diversity sharing in GSM Initial status The site is prepared for RX diversity sharing - the cabling is done and BTS Site Manager connection to the SMs is established. The commissioning procedure is the same as in the dedicated mode, except for the additional steps described in this section.

1

Start the commissioning. Select Commissioning Wizard, Change settings manually

2

Proceed to Antenna Settings. a) For TX antenna ports (ANT1, ANT3, and ANT5) Use regular, site-specific values and settings.

Issue: 01

DN09172017

39



If the UL (Rx) bandwidth (BW) of the used RF Module is narrower than 3GPP BW, the manual filter tuning may be needed. The filter tuning is done by setting the "Distance of beginning of filter band from lower frequency" parameter (in MHz, granularity 0.1) as in Figure 24: RX diversity sharing: GSM - Antenna Line Settings - TX (example).

g

The UL and DL filters are coupled, thus setting UL filter also shifts the DL filter. The allowed values (in MHz) are calculated as follows: • •

The lowest value: "0.0" The highest value: 3GPP band UL BW - RFM UL filter BW

Example: FXDA (900 MHz) RFM has 20 MHz UL filter BW, the 900 MHz band's BW is 35 MHz. The highest allowed parameter value: 15 MHz (35 MHz - 20 MHz). If an MHA is used (and controlled by the other technology), set the parameters as listed: • • • • • •

Feeder voltage - set to "0". Feeder loss - use site-specific value. MHA type - select "Non-AISG 2.0 MHA". Product type - select the correct MHA type, or choose "Other" if your MHA is not on the list. Serial number - optional field for entering the MHA's serial number manually. Alarm threshold - enter the MHA's alarm threshold manually.

Figure 24

RX diversity sharing: GSM - Antenna Line Settings - TX (example)

b) For RX antenna ports (ANT2, ANT4, and ANT6) Tick the Additional Rx Gain check box and set the value to "28", when using NSN RDSA cables.

40

DN09172017

Issue: 01



Figure 25

RX diversity sharing: GSM - Antenna Line Settings - RX

c) In case the legacy SW is used (EX4.2) Additional RX gain has to be set as a "fake" MHA. When using NSN RDSA cables, set the parameters as listed: • • • • • •

Feeder voltage - set to "0". Feeder loss - set to "0". MHA type - select "AISG 2.0 MHA". Product type - select Other". Gain - set to "28". Product code - mandatory field, though you can fill in any value.

Figure 26

3

RX diversity sharing: GSM - Antenna Line Settings - RX - in legacy SW

Proceed to the last page - Site Commissioning File. Click Send SCF. Result The SM gets reset and the RX diversity sharing is ready from GSM side.

Issue: 01

DN09172017

41

Troubleshooting RF Sharing


5 Troubleshooting RF Sharing 5.1 Missing RF Sharing license Table 5

Missing RF Sharing license

Effect on WCDMA

Effect on GSM

Solution

Result

WCDMA carriers are operational; minor fault is reported: "License missing... (1885)"

Shared RFMs are blocked; the "Operational state" indicates "Blocked: dedicated to peer"

Install the WCDMA RF GSM TRXs in the Sharing license. shared RFMs/RRHs go on air; site reset is not required

The fault: "TRX object allocation failed in RF module" (diagnostic info "05") is reported.

5.2 Incorrect RP3 cabling WCDMA is commissioned to RF Sharing, GSM is not commissioned yet. RFM/RRH cables are connected incorrectly to the GSM System Module. • •

WCDMA (correct connection): The first shared RFM is connected to OPT1, the second shared RFM to OPT2. GSM (incorrect connection): The first shared RFM is connected to OPT2, the second shared RFM to OPT1.

Table 6

RFM/RRH cables cross-connected before GSM commissioning

Effect on WCDMA

Effect on GSM

Solution

Result

Cells in the shared RFM stay on air.

1. Reported fault:

1. Correct the cable connections - the first RFM to OPT1, the second RFM to OPT2.

1. The alarm is cleared, GSM is ready for commissioning.

2. Commission the GSM.

2. Alarm is cleared, GSM TRXs go on air.

Reported fault: "Failure in RP3 optical interface (4039)"

"TRX/BTS FAULTY: ESMx System Module has lost connection to RF Modules" 2. Reported fault: "BCF NOTIFICATION: Invalid or uncommissioned shared RF module HW configuration detected"

42

DN09172017

Issue: 01


Troubleshooting RF Sharing

5.3 Incorrect filter shift in RX diversity sharing The problem happens when the filter frequency has been shifted manually and the filter exceeds the RFM BW or channel BW. Table 7

Incorrect filter shift

Effect on WCDMA/LTE

Effect on GSM

Solution

Result

"Reported fault: RF module failure (1840)"

Reported fault: "BTS/TRX FAULTY: TRX object allocation failed in RF module", diagnostic info: "06"

Recommission the BTS, setting the correct filter shift value.

After recommissioning the alarms are cleared and cells/TRXs go on air.

5.4 TRX Object allocation failed - GSM alarms Table 8

TRX Object allocation failed - GSM alarms

Effect on WCDMA

Effect on GSM

Solution

Cells in the shared RFMs/RRHs stay on air.

Fault is reported: 7606 See Trouble - TRX FAULTY - "TRX Management of Flexi object allocation failed" Multiradio BTS GSM/EDGE. There may be various root causes, the Diagnostic info in 2G BTS Site Manager indicates the possible root cause.

Result Alarms are cleared, GSM TRXs go back on air.

5.5 Remote connection to the Slave BTS is lost Table 9

Issue: 01

Remote connection to the Slave BTS is lost

Effect on the Master technology

Effect on the Slave technology

Solution

Result

No effect.

Remote connection is not possible.

Reset the Master technology BTS. It resets also the Slave technology BTS.

Remote connection is restored.

DN09172017

Note: when GSM is the Slave technology and runs in Temporary Sync mode, the recovery method may not succeed.

43

Configuring RF Sharing

Recommend Documents