L19Q2 Integration of MSMM L2100 With Existing U2100

Ericsson Internal
Operational Description 1 (29)

Prepared (Subject resp) No.
REEJPCU Javier Pesini MELA-19:016949 Uen

Approved (Document resp) Checked Date Rev Reference
MELAIQCA [Manuel Alonso Navarro] 2019-08-08 PA4
L19Q2 Integration of MSMM L2100 with existing U2100
Link to the last version of the document:

https://erilink.ericsson.se/eridoc/erl/objectId/09004cffc2835f45?
docno=MELA-19:016949Uen&action=current&format=msw12
Ericsson Internal

Contents
1 Introduction.............................................................................................3
1.1 Revision History..........................................................................3
1.1 Scope..........................................................................................3
1.2 Responsibilities...........................................................................3
2 Preparation..............................................................................................4
2.1 Check hardware requirements...................................................4
2.2 Check configuration requirements..............................................4
2.3 Licenses......................................................................................4
2.3.1 UMTS..........................................................................................4
2.3.2 LTE.............................................................................................4
3 Configuration Scenarios........................................................................5
3.1 Scenario A: Final configuration with RRUS13............................5
3.1.1 Scenario A with L2100 DUS:......................................................5
3.1.2 Scenario A with L2100 BB and NGS:.........................................6
3.2 Scenario B: Final configuration with RUS02...............................9
3.3 Scenario C: Final configuration with RUS02 SISO...................11
3.4 Radio Building Block MIMO......................................................13
3.5 Radio Building Block SISO.......................................................15
4 Power.....................................................................................................16
5 LTE Integration procedure...................................................................16
5.1 17.Q4 PCI script generation for BB521x eNodeB....................16
5.1.1 SIU reconfiguration...................................................................16
5.2 On site integration....................................................................17
6 3G side configuration...........................................................................17
6.1 Node B reconfiguration.............................................................18
6.1.1 Pre-checks................................................................................18
6.1.2 Procedure.................................................................................21
6.1.3 Post-checks..............................................................................23
6.2 RNC configuration....................................................................23
6.2.1 Configure 3G mobility to L2100................................................23
7.1 Configure 2G mobility to L2100................................................24
8.1 L17Q4 New eNodeB (Baseband 521x) Remote Integration.....24
8.2 DUS - Adding LTE cells to an integrated eNodeB for L19Q2
SW with PCI.............................................................................24
8.3 ENM - BB5216 - Add LTE cells Procedure in L19Q2 with PC&I
Tool...........................................................................................24
9 Synchronization....................................................................................25
9.1 Scenario A: Final configuration with RRUS13..........................25
9.1.1 Scenario A with L2100 DUS:....................................................25
9.1.2 Scenario A with L2100 BB and NGS:.......................................25
9.2 Scenario B: Final configuration with RUS02.............................26
9.3 Scenario C: Final configuration with RUS02 SISO...................26
Ericsson Internal

10 Final Checkings....................................................................................27
11 Troubleshooting...................................................................................27
11.1 Node B Troubleshooting...........................................................27
1 Introduction
The objective of this document is to describe the procedures and steps to
introduce LTE 2100 (or just new L2100 cells) in an existing WCDMA 2100 site
in MSMM configuration. The affected equipment will be the RNC, NodeB,
eNodeB and SIU.
This procedure is defined to OSP for 19Q2 software release.
1.1 Revision History
Date Rev Description Prepared

2019-08-01 PA1 Updated to 19.Q2 REEJPCU
1.1 Scope
This document is intended to show how to integrate an LTE 2100 node in

Mixed Mode with UMTS in Orange’s network. The procedure is applicable for
the described scenarios.
1.2 Responsibilities
Name Function Department

Manuel Alonso Navarro Technical coordinator CU IBM OPT NPI & Indus
Javier Service engineer CU IBM OPT NPI & Indus
Pesini Cuéllar
Francisco Javier Nieto Implementation RAN CU IBM B&O Production
Raul Chamorro TAC RAN CU IBM B&O Technical
Fernandez Office
Oscar Jimenez Alonso ITAC RAN MELA NMSD Build ITAC
Ericsson Internal

2 Preparation
2.1 Check hardware requirements
Before the beginning of the LTE & UMTS configuration, check the following:
1. The RBS cabinet and type has been confirmed and there is sufficient
space and power units for the new hardware.
2. The extra hardware necessary in the RBS has been delivered and is
ready to be installed on site.
2.2 Check configuration requirements
Before the beginning of the LTE & UMTS configuration, check the following:
1. In case MSMM U+G 900 is configured in the same logical NB, 3G

node should be dual DUW.
2. Only U2100 F1 (uarfcnDl=10688) should exist on 3G nodes. It is not

enough if F2 and/or F3 cells are locked in the RNC, Carrier and
RbsLocalCell MOs from U2100 F2 and/or F3 must not exist in the
NB.
Do not continue with procedure if any of conditions above are not met.
2.3 Licenses
The needed licenses, depending on the configuration, are:
2.3.1 UMTS
FAJ 121 1553 Multistandard RBS, Mixed Mode (WCDMA)
2.3.2 LTE
These are some of FAJs related to the MSMM and new L2100 EUtranCells:
Design-specific value
FAJ 121 0485 Connected Users (depending on initial and
final number of bands)
Value depending on final
FAJ 121 0668 Channel Bandwidth 10MHz
number of sectors
FAJ 121 0670 Channel Bandwidth 20MHz
number of sectors
FAJ 121 3071 5 MHz Sector Carrier
number of carriers
FAJ 121 0906 Multistandard RBS, Mixed Mode (LTE)
Ericsson Internal

3 Configuration Scenarios
3.1 Scenario A: Final configuration with RRUS13
3.1.1 Scenario A with L2100 DUS:
Initial status scheme for one sector:
 There might be or not a secondary DUW
 There might be or not U900 either in SM or MSMM
IMPORTANT: In case MSMM U+G 900 is already configured, current

procedure is only valid if 3G node is dual DUW.
Ericsson Internal

Final status scheme for one sector:
Note 1: In L+U 2100 MSMM, 3G will be always connected to RRUS Data 1

and 4G to RRUS Data 2
Note 2: In case of U+G 900 MSMM, DUW U2100 should give synchronization
to DUS41 L2100, and DUW U900 should give synchronization to DUG G900
3.1.2 Scenario A with L2100 BB and NGS:

Ericsson Internal

 There might be or not a secondary DUW
 There might be or not U900 either in SM or MSMM

Ericsson Internal

Note 1: In L+U 2100 MSMM, 3G will be always connected to RRUS Data 1

and 4G to RRUS Data 2. NGS configuration: DUW U2100 is
synchronization provider and BB L2100 is synchronization receiver.
to DUG G900
Ericsson Internal

3.2 Scenario B: Final configuration with RUS02

Ericsson Internal

Note 1: 3G will be always connected to first RUS Data 1 and 4G to second

RUS Data 2
Ericsson Internal

3.3 Scenario C: Final configuration with RUS02 SISO

Ericsson Internal

Note 1: 3G will be always connected to RUS Data 1 and 4G to RUS Data 2
Ericsson Internal

3.4 Radio Building Block MIMO
Scenario A: RRUS
The desired new configuration in scenario A for the W+L 2100 configuration is
one of these:
I. This distribution of elements is characterized as RBB22_1B where

Data 1 is connected to DUW and Data 2 to DUS.
II. This distribution of elements is characterized as RBB44_1D where

Data 1 is connected to DUW and Data 2 to BB.
Scenario B: RUS
The desired new configuration in scenario B for the 3G NodeB is the

following:
Ericsson Internal

This distribution of elements is characterized as RBB11_1A.
For LTE side, the desired configuration is characterized as RBB22_1A:
Complete connectivity as follows:

Ericsson Internal

Pos. Routing: From Routing: To Cable Type

1 RU A – RF A Antenna RF Cable
2 RU B – RF A Antenna RF Cable
3 RU A – Data 1 DUW Digital Signal Cable
4 RU A – Data 2 RU B – Data 1 Digital Signal Cable
5 RU A – RXA I/O RU B – RXB I/O Analog Signal Cable
6 RU A – RXB I/O RU B – RXA I/O Analog Signal Cable
7 RU B – Data 2 DUS Digital Signal Cable
3.5 Radio Building Block SISO
Scenario C: RUS
The desired new configuration in scenario C for the 3G NodeB is the

following:
This distribution of elements is characterized as RBB12_1A.
For LTE side, the desired configuration is SISO (noOfTxAntennas=1 and

noOfRxAntennas=1).
Ericsson Internal

4 Power
The radio design must take into account the possible power limitations
allocating all WCDMA and LTE carriers within the RRUS.
Maximum RRUS13 output power is 2 x 60W (4 x 80W in case of radio 4443)
WCDMA carriers will keep current power configuration, and LTE carriers will
use the remaining power.
5 LTE Integration procedure

In case the LTE node is a new one, follow these procedures.
5.1 17.Q4 PCI script generation for BB521x eNodeB
The scope of script generation procedure is to provide an engineering guide

for the eNB integration using a Baseband 5216 into the network.
The procedure includes different parts or phases for the script generation:
- ARNE definition in OSS
- PCI script generation
- Alarm Supervision off
Link to the latest version of script generation procedure:
https://erilink.ericsson.se/eridoc/erl/objectId/09004cff8d62008d?
5.1.1 SIU reconfiguration
For this configuration of MSMM, SIU must be adapted to the new scenario.
SIU reconfiguration procedure is defined in following document:
https://erilink.ericsson.se/eridoc/erl/objectId/09004cff86642592?
docno=OPER/RMED-13:002662Uen&action=current&format=msw8
Ericsson Internal

5.2 On site integration
After the SIU is properly configured, the LTE integration can start.
For onsite integration procedure, please see eNodeB (Baseband based)

onsite autointegration
6 3G side configuration
The reconfiguration on the WCDMA side has the following goals:
Scenario A:
NodeB:
 Remove the TMA/RUs for B1, if existing
 Define the RRUs for B1
 Activate Mixed Mode
 Configure DUW that handle U2100 cells as synchronization source

for the LTE site. (On a MSMM configuration, the WCDMA site must
provide synchronization to the LTE side)
RNC:
 Configure 3G mobility to L2100 if not done yet.
Scenario B:
Node B:
 Change RBB and AntFeederCable to match desired configuration
 Configure the GPS port of the DUW that handle U2100 cells as
synchronization source for the LTE site. (On a MSMM configuration,
the WCDMA site must provide synchronization to the LTE side)
RNC:

Ericsson Internal

Scenario C:
NodeB:
 Replace RU for B1
 Configure the GPS port of the DUW that handle U2100 cells as
synchronization source for the LTE site. (On a MSMM configuration,
the WCDMA site must provide synchronization to the LTE side)
RNC:
6.1 Node B reconfiguration
Reconfiguration of NodeB should be performed after installation is finished

and can be done while the eNodeB autointegration is ongoing.
6.1.1 Pre-checks
NodeB side
3. Check NodeB alarms:

> alt
4. Check NodeB cell/sector/carrier status:

> st sector
> lst carrier
> st rbslocalcell
5. Check Radio Units status:

> st auxpluginunit.r
6. Check sector number of TX branches and Band:

> hget sector numberOfTxBranches|band
Ericsson Internal

7. Check RUS version used for B1:

> cabx
8. Check maxTotalOutputPower defined in TPA for U2100 sectors:

> get tpa maxTotalOutputPower$
Ericsson Internal

9. Check carrier max DL power capabilities:

> get carrier maxDlPowerCapability
10. Check UtranCell status

Ericsson Internal

6.1.2 Procedure
Scripts will check the number of sectors, sectors used for Band 1 and will
proceed only with the relevant ones.
IMPORTANT: All scripts should be run at once, within the same moshell
session.
1. Lock U2100 Utrancells from RNC side
bl UtranCell=<Node U2100 utrancell>
2. Only Scenario A:
Connect to the NodeB with AMOS and perform:
i. Open EMAS tool and perform “export and delete”.
ii. Open EMAS: Load Cabinet and Site configuration files generated with
Picasso (PICASSO should be feeded with latest Kget and new type of
RRU: RRU13, RRU4443, etc)
 See this example:
iii. Run final settings script generated by Picasso.
 See this example:
iv. In order to activate MSMM for B1 sectors run following script:

Ericsson Internal

v. In case of RRU4443, an upgrade to at least W18.Q4.4 is required to

support the new radio. Perform upgrade at this point, after 3G NodeB
reconfiguration.
3. Only Scenario B: If Radio Units are RUS02, run following script:
i. Note that second RF branch reach first RUS02 through the second
RUS02 internally. There is a LNA which gives a gain of 17 db
inside, and additional delay should also be considered. See table
below:
RU gain RU delay Cosite cable loss Cosite cable delay

R/RUS 17 dB 58,3 ns 0,2 dB/m 3 ns/m
Second AntFeederCable (xB, where x is the number of sector)

values impacted are:
- ulAttenuation: New value= Old Value -17db + 0.2db
- electricalUlDelay: New delay = Old value + 583 + 3*2
Below script is done with following default values. If current ones

should be different, please modify the script before running:
- ulAttenuation -168,-168,-168,-168,-168,-168,-168,-168,-168,-
168,-168,-168,-1,-1,-1
- electricalUlDelay
1321,1321,1321,1321,1321,1321,1321,1321,1321,1321,1321,1
321,-1,-1,-1
In order to change the RBB, AntFeederCable and activate the

MSMM and synchronization run following script:
4. Only Scenario C: If Radio Units are RUS02, run following script:

Ericsson Internal

In order to activate the MSMM and synchronization run following

script:
5. Restart the NodeB
6. Do not unlock the 3G cells until RNC configuration and HW installation is

done
6.1.3 Post-checks
1. Check NodeB alarms:

> alt
2. Check NodeB cell/sector/carrier status:

> st sector
> lst carrier
> st rbslocalcell
3. Check Radio Units status:

> st auxpluginunit.r
4. Check maxTotalOutputPower defined in TPA for U2100 sectors:

> get tpa maxTotalOutputPower$
5. Check carrier max DL power capabilities:

> get carrier maxDlPowerCapability
If sector and rbsLocalCell are disabled, go to Chapter 10. Troubleshooting.
6.2 RNC configuration
6.2.1 Configure 3G mobility to L2100
Modify following script in order to add all cells that need to have mobility
configured to L2100. Only Orange cells (both, U2100 and U900) should have
mobility to LTE new frequency:
Ericsson Internal

7.1 Configure 2G mobility to L2100
Modify following script in order to add all 2G cells that need to have mobility
configured to L2100.
Follow these procedures for remote part of the LTE, depending on if the LTE
node is new or existing, DUS or BaseBand.
8.1 L17Q4 New eNodeB (Baseband 521x) Remote Integration
Remote Integration procedure is normally performed after a successful RBS

on-site integration and is part of the full process of adding RBSs to the
network:
https://erilink.ericsson.se/eridoc/erl/objectId/09004cff8d621183?
8.2 DUS - Adding LTE cells to an integrated eNodeB for L19Q2 SW

with PCI
In case the LTE DUS node already exists, L2100 cells will be added on it,
follow this procedure:
https://erilink.ericsson.se/eridoc/erl/objectId/09004cffc28b0aa8?
8.3 ENM - BB5216 - Add LTE cells Procedure in L19Q2 with PC&I Tool
In case the LTE BaseBand node already exists, L2100 cells will be added on
it, follow this procedure:
https://erilink.ericsson.se/eridoc/erl/objectId/09004cffc287921e?
Ericsson Internal

9 Synchronization
9.1 Scenario A: Final configuration with RRUS13
9.1.1 Scenario A with L2100 DUS:
In a Mixed Mode RBS, the system clocks in the radio standards need to be
synchronized.
1. See below how to configure the WCDMA node synchronization.
In WCDMA DUW U2100 Check:
Subrack=1,Slot=1,PlugInUnit=1,TimingUnit=1 gpsOutEnabled is set to TRUE
Launch Amos session in WCDMA DUW
//Set gpsOutEnabled to TRUE

Lt all
set Subrack=1,Slot=1,PlugInUnit=1,TimingUnit=1 gpsOutEnabled true
2. See below how to configure the LTE node synchronization:
Settings
Synchronization
Method
TimingUnit:: ENodeBFunction:: Synchronization:: Synchronization::
gpsOutEnabled timeAndPhaseSynchCritical fixedPosition syncReference
GPS Receiver FALSE TRUE TRUE GpsSyncRef
Wrong synchronization configuration will prevent users to attach LTE network.
9.1.2 Scenario A with L2100 BB and NGS:
In Mixed Mode U2100/L2100 scenario with NGS (Node Group

synchronization), the system clocks in the radio standards need to be
synchronized.
Follow chapter “Procedure Mixed Mode Node Group Sync WCDMA/LTE” in

procedure “BB521x/BB66xx - Mixed Mode Node Group Synchronization
Configuration Procedure for 19Q2”:
https://erilink.ericsson.se/eridoc/erl/objectId/09004cffc2835f43?
Ericsson Internal

In WCDMA pDUW U2100 Check:
Subrack=1,Slot=1,PlugInUnit=1,TimingUnit=1 gpsOutEnabled is set to FALSE
9.2 Scenario B: Final configuration with RUS02
synchronized.

Lt all
Settings
Synchronization
Method
9.3 Scenario C: Final configuration with RUS02 SISO
synchronized.

Ericsson Internal


Lt all
Settings
Synchronization
Method
10 Final Checkings
1. Check that both 3G and 4G cells are enabled
2. Check that there are no alarms either in 3G or 4G nodes
3. Check that traffic is ongoing in both, 3G and 4G sites
11 Troubleshooting
11.1 Node B Troubleshooting
If AuxPlugInUnit for new RRUs are enabled, but Sector and RbsLocalCell are
disabled:
Ericsson Internal

Follow this procedure (only if NodeB SW level is W14B):
1. Print the PiuType for RRUS:
a. pr PiuType=KRC161
2. Change RRU PiuType to one of previously printed PiuTypes (only B1

RRUs should be changed):
a. set auxpluginunit.rru piutype PiuType=KRC161331/4_*
3. Lock the RRU:
a. bl auxpluginunit.rru
4. Uninitialize the sectors for B1:
a. ma sectb1 sector band 1
b. acc sectb1 unInitSector
5. Change RRU PiuType back to RRUW-preInstalledSW_* (only B1 RRUs

should be changed):
a. set AuxPlugInUnit=RRU piuType PiuType=RRUW-

preInstalledSW_*
6. Unlock the RRU:
a. deb auxpluginunit.rru
7. Initialize sectors for B1:

Ericsson Internal

a. acc sectb1 initSector

1
1
8. Check that RRU, Sector and rbsLocalCell are enabled:
a. st AuxPlugInUnit=RRU
b. st sector
c. st RbsLocalCell

L19Q2 Integration of MSMM L2100 With Existing U2100

Uploaded by

Copyright:

Available Formats

L19Q2 Integration of MSMM L2100 With Existing U2100

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

L19Q2 Integration of MSMM L2100 With Existing U2100

Uploaded by

Copyright:

Available Formats

Ericsson Internal

Operational Description 1 (29)

REEJPCU Javier Pesini MELA-19:016949 Uen

MELAIQCA [Manuel Alonso Navarro] 2019-08-08 PA4