Problem
Performance Management (PM) data is not reflected in the database.
Possible Cause
•
PM pipe is not running.•
Some ETLOAD processes stopped working.•
Invalid OMeS files are received.•
OMeS file is inaccessible.1. Check PM pipe status.
a) To check the status of the PM pipe, refer to Checking the status of PM Pipe service. b) If the PM pipe service is not started, restart the service by following the succeeding steps:
Note: These steps are intended only for the system administrator with root privileges.
1. Log in to the VM where the rep service is running as root user.
2. To restart the rep service, enter the following command:
$ smanager.pl start service rep-<VM or node name>
Expected outcome
An output like the one below appears:
Service rep-<VM or node name> started on node <VM or node name>
2. For ETLOAD-related issues, refer to ETLOAD processes failures.
3. For invalid OMeS, refer to Invalid semantic error in etlpslmx.
4. For OMeS accessibility problems, refer to Troubleshooting "Cannot access file. Can't gunzip" error
LTE Radio Access, Rel. FDD-
LTE 15A, Operating
Documentation, Issue 02
Configuring RF Sharing
DN09172017
Issue 06
Approval Date 2015-09-23
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 © 2015 Nokia Solutions and Networks. 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 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.
Table of Contents
This document has 62 pages
1 2 2.1 2.2 2.3 3 3.1 3.2 3.3 3.3.1 3.4 4 4.1 5 5.1 5.2 5.3 5.4 5.4.1 5.4.2 Summary of changes... 7 Concepts of RF sharing and RX diversity sharing... 10 RF Sharing deployment scenarios... 11 Installing a new RF sharing site...11 Adding RF Sharing to existing site and activating locally...13 Adding RF Sharing with locked WCDMA cells...16 Commissioning RF sharing... 22 Commissioning WCDMA for 2-RAT RF Sharing... 22 Commissioning LTE for 2-RAT RF Sharing...27 Commissioning GSM for 2-RAT RF Sharing... 32 Sync Hub related BSC MML commands to set right Sync Mode for GSM BTS... 37 Recommissioning RF Sharing to change particular settings in Master technology...38 Reverting RF sharing site to dedicated site... 41 Reverting RF sharing site to dedicated GSM site... 41 Rx diversity sharing...43 Rx diversity sharing requirements...43 Commissioning WCDMA or LTE to RX diversity sharing... 46 Commissioning GSM to RX diversity sharing... 51 LTE-GSM RF sharing with Rx diversity sharing (P-type
configuration)... 53 Commissioning type P configuration in LTE...55 Commissioning type P configuration in GSM...59
Configuring RF Sharing
List of Figures
Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 20 Figure 21 Figure 22 Figure 23 Figure 24 Figure 25 Figure 26 Figure 27 Figure 28 Figure 29 Figure 30 Figure 31 Figure 32 Figure 33 Figure 34 Figure 35 Figure 36Main differences between RF sharing and RX diversity sharing concepts... 10 RF Sharing with locked WCDMA cells concept...16 Commissioning - reconfiguration, target: BTS...18 GSM BTS - alarms at startup... 19 GSM BTS - selecting shared/dedicated modules...20 WCDMA - Enable EIF2 as RP3-01 interface...23 BTS Synchronization settings...24 WCDMA - Concurrent Mode Settings...25 WCDMA - Local Cell Resources... 26 WCDMA - Send Parameters... 27 LTE - Enable EIF2 as RP3-01 interface... 28 BTS Synchronization settings...30 LTE - Concurrent Mode Settings for LTE-2G...31 LTE - Concurrent Mode Settings for LTE-3G...31 GSM - Site Specific Information... 35 GSM - Module Configuration for Sync Hub Master... 36 GSM - Module Configuration for Sync Hub Slave... 36 GSM - Local Sector Settings... 37 Rx diversity sharing requirements... 43 Carrier-TRX spacing rules (pictures not in scale)...44 Additional Rx diversity cables connection... 45 Rx diversity signal paths...46 RX diversity sharing: WCDMA - Local Cell Resources... 47 RX diversity sharing: WCDMA - Carrier settings... 48 RX diversity sharing: WCDMA - Antenna Line Management... 48 RX diversity sharing: WCDMA - AISG MHA Settings: LNA1...49 RX diversity sharing: WCDMA - AISG MHA Settings: LNA2...49 RX diversity sharing: WCDMA - Antenna Line Settings - RX antenna modifications...50 WCDMA - Send Parameters... 50 RX diversity sharing: GSM - Antenna Line Settings - TX (example)... 52
RX diversity sharing: GSM - Antenna Line Settings - RX...52 RX diversity sharing: GSM - Antenna Line Settings - RX - for Flexi Compact... 53 P-type configuration for LTE FSME with resource allocation... 54 P- type configuration for LTE FSMF with resource allocation...55 P- type LTE - LTE Concurrent Mode Settings...56 P- type LTE - Cell Resources... 57
Figure 37 Figure 38 Figure 39 Figure 40 Figure 41 Figure 42
P-type LTE - LTE Carriers...58 P-type LTE - Antenna Line Settings... 58 P- type GSM - Local sector 1... 60 P- type GSM - Local sector 2... 60 P- type GSM - Local sector 3... 61 P- type GSM - Antenna line settings... 62
Configuring RF Sharing
List of Tables
Table 1 Table 2 Table 3 Table 4 Table 5RAT releases covered by the document...7 Clock source (CS) parameter values...38 SENA parameter values... 38 WCDMA/LTE settings forcing the GSM recommissioning... 39 Example of manual filter tuning (FXDA)... 48
Configuring RF Sharing Summary of changes
Summary of changes
Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.
This document is common for Radio Access Technologies (RATs) listed in Table 1: RAT releases covered by the document.
Table 1 RAT releases covered by the document
Radio Access Technology (RAT)
GSM/EDGE (BSS) WCDMA RAN Long Term Evolution
Product release
RG30 (BSS), RG40 (BSS), GSM16 (BSS) RU40, RU50, RU50 EP1, WCDMA16 RL50, RL60, RL70, FDD-LTE 15A
Changes between issues 05 (2015-06-16) and 06 (2015-09-23)
Installing a new RF sharing site•
Information on WCDMA licenses has been removed.•
Information on storage of SCF files in NetAct has been added.•
Steps 3, 6, 7 and 9 have been updated.•
Information of FDSW has been removed.Adding RF Sharing to existing site and activating locally
•
Information on licenses has been updated.•
Information on storage of SCF files in NetAct has been added.•
Steps 3, 5 and 12 have been updated.Adding RF Sharing with locked WCDMA cells
•
Information on licenses has been updated.•
Steps 4, 6 and 8 have been updated.Commissioning WCDMA for 2-RAT RF Sharing
•
Information on licenses has been removed.•
Information on Enable FSM EIF2 as RP3-01 interface option has been added to step 1.•
Note about secondary sync source for SyncHyb Slaves has been added.Commissioning LTE for 2-RAT RF Sharing
•
Information on licenses has been removed.•
Note about secondary sync source for SyncHyb Slaves has been added.•
Note about the power sums has been removed.Commissioning GSM for 2-RAT RF Sharing
•
Step Proceed to Site Specific Information has been updated.Sync Hub related BSC MML commands to set right Sync Mode for GSM BTS
•
Section has been added.Summary of changes Configuring RF Sharing
•
Section has been updated.Reverting RF sharing site to dedicated GSM site
•
Section has been added.LTE-GSM RF sharing with Rx diversity sharing (P-type configuration)
•
Note about MHA restriction has been added.•
Figure P-type configuration for LTE FSMF with resource allocation has been added.Concept of RP3-blocking SW
•
Section has been removed.Adding RF Sharing with RP3-blocking SW case 1
•
Section has been removed.Adding RF Sharing with RP3-blocking SW case 2
•
Section has been removed.Changes between issues 04 (2015-05-25) and 05 (2015-06-16)
Commissioning WCDMA for 2-RAT RF Sharing
•
Step Proceed to BTS Synchronization settings has been added.•
Step Proceed to Concurrent Mode Settings has been updated.•
Post requisite has been added.Commissioning LTE for 2-RAT RF Sharing
•
Step Proceed to BTS Synchronization settings has been added.•
Step Proceed to Concurrent Mode Settings has been updated.•
Post requisite has been added.Commissioning GSM for 2-RAT RF Sharing
•
Note regarding GSM as Sync Hub Master has been added.•
Step Proceed to Site Specific Information has been added.•
Step Proceed to Module Configuration has been updated. Troubleshooting RF sharing•
Section has been moved to Troubleshooting RF Sharing document.Changes between issues 03 (2015-02-27) and 04 (2015-05-25)
Commissioning WCDMA for 2-RAT RF Sharing
•
Note regarding GSM recommission has been removed. Commissioning LTE for 2-RAT RF Sharing•
Note regarding GSM recommission has been removed. Commissioning GSM for 2-RAT RF SharingConfiguring RF Sharing Summary of changes
•
Note regarding GSM recommission has been removed.Recommissioning RF Sharing to change particular settings in Master technology
•
Section has been added.Commissioning WCDMA or LTE to RX diversity sharing
•
Minor changes in center frequency tuning have been made. Commissioning GSM to RX diversity sharingConcepts of RF sharing and RX diversity sharing Configuring RF Sharing
1 Concepts of RF sharing and RX diversity
sharing
A description and a picture showing the basic 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 1: 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 1 Main differences between RF sharing and RX diversity sharing concepts
RF Sharing
Radio Master Technology 1 System Module Technology 2 System Module Technology 1 System Module Technology 2 System Module Shared RFM/RRHRX diversity sharing
Radio Master Technology 1 dedicated RFM Radio Master Technology 2 dedicated RFM ALD s ALD s Antennas Antennas Sy n c M a sConfiguring RF Sharing RF Sharing deployment scenarios
2 RF Sharing deployment scenarios
A list the most typical RF sharing deployment scenarios.
For the supported and recommended HW combinations, the latest SW release
combinations, and the recommended SW upgrade paths, see the following documents:
•
RF-Sharing Regular Maintenance NewsletterThis RF Sharing Newsletter is published internally and updated monthly. For details, contact Technical Support.
•
Flexi Multiradio BTS RF Sharing Released ConfigurationsAvailable in NOLS at the following directory: NOLS ► Product Information Center ► Documentation finder ► Radio Network ► Base Stations ► Flexi Multiradio
10 BTS EDGE / Flexi Multiradio BTS EDGE / Flexi Multiradio BTS WCDMA / Flexi Multiradio BTS LTE ► Operating documentation ► Flexi Multiradio BTS
RF Sharing Released Configurations (XLS format)
•
Compatibility MatrixAvailable in NOLS at the following directory: NOLS ► Product Information Center ► Compatibility Matrix ► Compatibility Matrix - Access Networks
2.1 Installing a new RF sharing site
Steps to install a new site with RF sharing: WCDMA-GSM, LTE-GSM, or WCDMA-LTE.
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.
It is recommended that you store the backup of SCFs for both technologies in NetAct as soon as the RF Sharing site is accepted. This would serve as a reference in the future troubleshooting and help in faster recovery of sites in HW replacement scenarios.
RF Sharing deployment scenarios Configuring RF Sharing
2 Install the correct GSM/WCDMA/LTE BTS Site Manager version on your computer(s).
g
34
It is recommended that you have two computers, which allows simultaneous connection to both technologies' Site Managers.
Check the supported SW for both technologies in Compatibility Matrix, in Flexi Multiradio BTS RF Sharing Released Configurations, or in RF-sharing Regular Maintenance Newsletter.
For details on these documents, see RF Sharing deployment scenarios section.
Optional: Update the System Module SW.
It is recommended that you update the new System Module SW before the site visit (if possible) to reduce the site visit time.
During the site visit
5 Install the HW, do the cabling, and connect your computer(s) to System Modules via Local Management Ports (LMPs).
To connect the modules for RF sharing configurations, see Flexi Multiradio BTS RF Sharing Released Configurations.
For details, see the respective Installing and Cabling Flexi Multiradio documentation. Ensure that the RFM/RRH has the same SFP type as the System Module - 3 Gbps or 6 Gbps. In case of LTE, always use 6 Gbps SFPs and optical links, when supported by the used HW.
6 Power up the Master technology's System Module (WCDMA or LTE).
7 If not done before, update the System Module SW to the desired version.
If Incompatible SW version detected (0023) alarm is raised, update the SW again.
Ensure that all the installed RFMs/RRHs and ALDs are detected and shown properly in the BTS Site Manager.
Result
The HW is now ready for commissioning.
8 Commission the Master technology for RF sharing.
9 Power up the Slave technology's System Module and update the System Module SW to the desired version, if not done before.
10 Commission the Slave technology for RF sharing.
In case GSM is the Slave technology, select "Manual commissioning", then fetch the SCF from the Master technology's BTS (as a Backup Commissioning File) and use it as a template in Hardware Configuration.
Configuring RF Sharing RF Sharing deployment scenarios
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 existing site and activating
locally
Steps to add one technology HW to an already existing site and create an RF sharing site: WCDMA-GSM, LTE-GSM, or WCDMA-LTE.
Purpose
Typical initial status:
•
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.
Before the site visit
1 If possible, prepare the shared 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.
It is recommended that you store the backup of SCFs for both technologies in NetAct as soon as the RF Sharing site is accepted. This would serve as a reference in the future troubleshooting and help in faster recovery of sites in HW replacement scenarios.
2 Install the correct GSM/WCDMA/LTE BTS Site Manager version on your computer(s).
When activating RF Sharing in an existing WCDMA site, ensure you have the new required licences downloaded to your computer.
RF Sharing deployment scenarios Configuring RF Sharing
g
34
5
It is recommended that you have two computers, which allows simultaneous connection to both technologies' Site Managers.
Check the supported SW for both technologies in Compatibility Matrix, in Flexi Multiradio BTS RF Sharing Released Configurations, or in RF-sharing Regular Maintenance Newsletter.
For details on these documents, see RF Sharing deployment scenarios section.
Optional: Update and activate the already deployed technology's System Module SW.
If the SW update is needed for the already deployed technology, update it remotely to save the site visit time.