Why Multi-sector solution is

needed?
Network load is heavy, new sites acquisition is not feasible, and the frequency resources
of the operator are limited.
6-sector solution can be adopted in these cases to make expansion and address the
capacity requirement.

Operators who are interested in 6-sector solution: Argentina Movistar , Personnel (1

Page 1
 Site Scenario
WRFU/RRU Cascade CPRI
The logical port of the WRFU/RRU can only
be configured in Slot 2 and Slot 3
Therefore WRFU/RRU cascading is required
when there are no available CPRI ports on
the existing WBBP board slot 3
Cascading is normally applied if the site is
configured as a co-BBU (Sharing along with
2G) where slot 2 is occupied by a UBRI board

Page 2
 Site Scenario

WBBPb could only support up to 3 logical WRFU/RRU connection

Example: The above Slot 2 of the BBU is occupied by a UBRI (GSM) board thus additional sectors
are required to be cascaded

Page 3
 WRFU/RRU Cascade
CPRI Connection
CPRI_0 (WRFU) / CPRI_W(RRU) of the Existing
WRFU/RRU S1 connects to the WBBP board.

CPRI_1 (WRFU) / CPRI_E(RRU) connects to CPRI_0

Page 4
Page 5
 BTS3900 with New Cabinet
For sites which was proposed in the DRM with
a new cabinet, the exisiting WRFU slot 0, 2,
and 4 in Cabinet_0 needs to be relocated to
Cabinet_2

Page 6
 Site Scenario
WRFU/RRU Direct Connection
If the BBU is pre-installed with WBBPd board (with 6
CPRI Ports) in Slot_3, connect the CPRI of the new
WRFU/RRU to the unoccupied ports in ascending
order
If the DRM proposes additional WBBP, replace the
existing WBBP in slot_3 (WBBPb) with the new
WBBPd and move the existing to other empty slots
For BBU with WBBP boards installed in both Slot_2
and Slot_3, the new WRFU/RRU should be connected
to the WBBP in Slot_2
CPRI_0 S1 CPRI_1 S4 CPRI_2 S3 CPRI_3 S5 CPRI_4 S4 CPRI_5 S6

WBBP board CPRI Port Assignments

Page 7
If the BBU is pre-installed with
WBBPd board (with 6 CPRI
Ports) in Slot_3, connect the
CPRI of the new WRFU/RRU to
the unoccupied ports in
ascending order

If the DRM proposes additional

Page 8
 For BBU with WBBP boards
installed in both Slot_2 and
Slot_3, the new
WRFU/RRU should be
connected to the WBBP in
Slot_2

Page 9
 Configuration Steps
RNC:
ADD USAC RNC:
ADD ULOCELL DEA UCELL
ADD UCELLQUICKSETUP (Existing)
ADD UCELLHSDPA
ADD UCELLHSUPA

NodeB:
ADD NodeB:
RRUCHAIN ADD BRD (WBBP if any)
ADD SEC RMV LOCELL (Existing)
RNC: ADD RRU
ACT UCELL (ALL) MOD UL/DL GROUP
ADD LOCELL ADD UL/DL GROUP
(New) ADD LOCELL (Existing)

RNC:
M2000:
MOD UCELLNAME (Existing cell add N_))
Update
MOD UNODEBNAME (Add N_)
License
MOD ADJNODE (Add N_)

Page 10
 New Cell Configuration
Below are the command for the new 6 sector cells
ADD USAC
Add SAC for the new sectors
SAC = Cell ID
ADD ULOCELL
Add Local Cell for the new sectors
Ensure the LOCELL ID correspond with the correct CELL ID
ADD UCELLQUICKSETUP
Cell ID to be added according to the NODIN
The Cell Name must have N_
Max Transmit Power must match the existing cell in order to
balance between the new and existing and new cells
The CPICH is 10% of the Max Transmit Power
ADD UCELLHSDPA
ADD UCELLHSUPA

Page 11
 LOCELL SECTOR UL UARFCN DL UARFCN T_Cell UL/DL
Group
1 1 9688 10638 CHIP0 0
2 2 9688 10638 CHIP768 0
3 3 9688 10638 CHIP1536 0
4 1 9713 10663 CHIP0 1
5 2 9713 10663 CHIP768 1
6 3 9713 10663 CHIP1536 1
7 4 9688 10638 CHIP256 0
8 5 9688 10638 CHIP1024 0
9 6 9688 10638 CHIP1792 0
10 4 9713 10663 CHIP256 1
11 5 9713 10663 CHIP1024 1
12 6 9713 10663 CHIP1792 1

Cell Uplink Assignment

Page 12
 List Local Cell
---------------
Local Cell ID Cell ID Site No. Sector No. UL BB Resource Group No. DL BB Resource Group No.

1 45081 4508 0 0 0
2 45082 4508 1 0 0
3 45083 4508 2 0 0
4 45084 4508 0 1 1
5 45085 4508 1 1 1
6 45086 4508 2 1 1
7 25081 4508 3 0 0
8 25082 4508 4 0 0
9 25083 4508 5 0 0
10 25084 4508 3 1 1
11 25085 4508 4 1 1
12 25086 4508 5 1 1
(Number of results = 12)

Page 13
 Modify UL/DL Resource Group
The existing UL/DL is only grouped into a single group
(Group 0)
Because a single uplink resource group can only process
services borne on six cells, when the NodeB has more than
6 cells, the uplink resource must be grouped into 2 groups
A single uplink resource group only processes services
borne on six cells.
Softer handover may occur to cells within the same uplink
resource group. It is recommended to put intra-frequency
cells into the same group
The same frequency cells must be in the same uplink
resource group otherwise SHO cannot be performed
between adjacent cells with the sane frequency

Page 14
 Modify UL/DL Resource Group
DEA UCELL (Existing localcells)
Deactivate the existing cells of the site on the RNC
ADD BRD
If the DRM proposes new WBBP, configure the new WBBP
RMV LOCELL (Existing)
Remove the existing local cell in order to group the new and existing cells
based on the frequency
MOD UL/DL GROUP
divide the UL/DL slot unit from Group 0
ADD UL/DL GROUP
Add the new UL/DL group
ADD LOCELL (Existing local cells)
Add the existing local cells with the newly grouped uplink resources

Page 15
 Configure New RRU
ADD RRUCHAIN

ADD SEC

ADD RRU

ADD LOCELL

Page 16
 Activate Cell & Modify Cell/NodeB
Name
Activate the cells including the HSDPA/HSUPA
Customer requests to change the NodeB and
existing cell names as a new site thus require
to add N_ to the names
Upon completion inform PLO team to proceed
with DT

Page 17
 UMPT Upgrade
To increase the CNBAP
Reduce CNBAP congestion on the IUB

Page 18
Page 19
 If the existing NodeB transmission type is IP
transport, the WMPT can be deteled and replace
with UMPT by using CME
Should the transport type is ATM/Hybrid, need to
export the IUB Interface (including the Physical
NodeB), delete the ATM transport data then only
make the modification on the NodeB Device
Pane;l thus re-import the same IUB Interface
sheet (to re-import the ATM configuration of the
NodeB)
No changes required on the data configuration

Page 20
Page 21
 Risk Factor
Faulty CPRI/SFP
High rate of faulty CPRI and SFP are faced during installation
Each subcon team must carry a spare set of 10M CPRI and 2 850nm MM SFP
Low optical transmit/receive power
The SFP installed does not match. Both ends require the same SFP type, wavelength,
mode, and distance
CPRI bending radius >90
SFP type mismatch. For cascade RRU, SFP type is 850nm MM
Internal Cross Feeder
The feeder are normally crossed within the sector
UMPT Upgrade
The UMPT is normally pre-installed with the R013 software version. Thus the UMPT
most be upgraded to the R014 together with the commissioning
Wait ~15 minutes before loading the NodeB XML script after inserting the board into
the BBU
Azimuth and Tilting
The azimuth and tilting must follow the new RNP report regardless of the existing
setting on site

Page 22
 Risk Factor
IUB/CE Congestion

Page 23
 Implementation Flow
Prerequisites Prior to Implantation
MOS
Ensure there are no shortage of materials
CRQ
Ensure CRQ has been approved by Telkomsel
To check the latest status of the CRQ contact Telkomsel
OSS hotline 085218882773

DRM Report
Approved RNP Report
Approved NODIN

Page 24
 Implementation Flow
Inform NSA Area
Login to TSEL NOC Owner Installation
(Refer attachment)

Contact Huawei Swap / Relocate

Alarm handling Drive test

Page 25
 Attachment
Site Scenarion + RRU Topology

NSA Area Owner Contact Details

Page 26
 Split Antennas
Frequency band 2100MHz

Page 27