RAN - HWI - Guidelines - 4G - LTE Huawei - Telkomsel - v6

You might also like

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 34

RAN Operation Standardization

4G Huawei
Network Operation Management Group
RADIO ACCESS NETWORK OPERATON
Juni 2015
Background & Objective
Background
1. There aren’t guidance standard for parameter, configuration, resilience, alarm, and
surveillance.

Objective
1. RAN Readiness & Resiliance.

Radio Access Network Operation 2018


eNodeB GuideLines

NE Naming • eNodeB and Cell Naming Standardization

• Site Solution
Hardware • Transmission Configuration
• BBU & UPEU Configuration

• Backup Configuration
Configuration • Input Regional, Location, Longlat Data
Standardization

Software • Equal latest Software Version

Severity Alarm • Cell Unavailable Alarm Severity

Radio Access Network Operation 2018


eNodeB and Cell ID Planning
SITE ID NE ID

AAA xxx AAA xxx CC y

Numerical number of
Numerical site ID of DATI II Prefix code of Equipment type
Site ID
Equipment type
Alphabetical code of
DATI II
•AAAxxx = Prefix code of Site ID
- the LTE site ID is the same as the site ID at •CC = Equipment type
the existing co-located site * ML = Macro LTE 1800
* IL = INDOOR LTE 1800
• AAA = Alphabetical code of DATI II * HL = BTS HOTEL LTE 1800
(Refer to KD FAR No: 027/FN.01/PD-00/IV/2010) * OL = Micro Outdoor LTE 1800
• xxx = Numerical site ID of DATI II * MT = Macro LTE 900
(001 ~ 999) * IT = INDOOR LTE 900
* HT = BTS HOTEL LTE900
* OT = Micro Outdoor LTE900
Sample :
y = numerical number of equipment type
JKS123 (1 ~ 9)

Sample :
JKS123ML1
Radio Access Network Operation 2018
eNodeB and Cell ID Planning
Notes :
- LTE Cell ID includes 20 bit ENodeB ID and 8 bit cell ID - If there is 2 NE in one location, the other NE will have to
- ENodeB ID range : -1….1048575 use the DATI II ID for spare.
- Each ENodeB should have a unique ENodeB ID Example :
- If there is more than one ENodeB in one site location, use a different site Site ID : JKS123
ID number for each ENodeB NE ID : JKS123MT & JKS123IT
- Cell ID range : 0….255 EnodeID : - JKS123MT : 133123
- EnodeB cell ID : MCC – MNC – ENodeB ID – Cell ID - JKS123IT : 612123

eNodeB ID Numbering Cell ID Numbering


SITE ID
2 5 5
MWR123 1 = LTE 1800
2 = LTE 900
3 – 5 = LTE future band
DATI II ID Cell Number
Site ID Number
From 1-25
MEULABOH= MBO = 1 001 Cell ID
LTE 900 Sector 1
012
BANDA ACEH = NAD = 9 ….

MANOKWARI = MWR = 403 123 LTE ENODEB CELL ID

AAA – BBB – CCCDDD - EEE

DATI II ID Site ID Number ENodeB ID MCC MNC Dati II ID Cell ID


Site ID Number
403 123 403123

510 10 403123 012


Radio Access Network Operation 2018
eNodeB and Cell ID Planning
LTE eNodeB Name (<=64bytes) LTE eNodeB Name (<=99bytes)

ENodeB Name ENodeB Cell Name


A_ BBBxxxCC_DDDDDD A_ BBBxxxCC_DDDDDDCCn

Site ID BTS Name Site ID BTS Name

Equipment type Equipment type Sector ID


Site information Site information
•A = Site information •A = Site information
- N = New site N = New site
• BBB xxx = SITE ID • BBB xxx = Site ID
• CC = Equipment Type • CC = Equipment Type
(See Table Summary – NE ID) (See Table Summary – NE ID)
• DDDDDD = BTS Name • DDDDDD = BTS Name
•_ = Separator •_ = Separator
•n = Sector ID
(0 ~ 9)
Sample :
N_JKS123ML_Merdeka Sample :
JKS123ML_Merdeka After passing lock value JKS123ML_MerdekaML1
Site LTE Merdeka Sector 1
Radio Access Network Operation 2018
Site Solution

Part Before After


RF Board Type MRFU MRFU
MRFU/ MRRU Board Number 3 6
RF Cascading No RF Cascading RF Cascading
CPRI Cascading No CPRI Cascading CPRI Cascading
GSM TRX Configuration 4/4/4 1/1/1
Power per RTX 20W 20W
CPRI Connection To GTMU To UBBP
CPRI Connection Type Single CPRI CPRI Mux

WBBP
LBBP
GTMU
UMPT WBBP
UBBP GTMU
Notes :
Move 1 jumper RXB to TXRXA in new MRFU
LBBP UMPT

Move CPRI GSM from GTMU/UBRI to UBBP

G G G G G G G G G
9 9 9 L L L L L L
0 0 0
0 0 0 9 9 9 9 9 9
0 0 0 0 0 0
0 0 0 0 0 0

Radio Access Network Operation 2018


Site Solution
SCENARIO 1b
(Change MRFUv2 to RRU3959)

Part Before After


RF Board Type MRFU MRRU
MRFU/ MRRU Board Number 3 3
RF Cascading No RF Cascading No RF Cascading
CPRI Cascading No CPRI Cascading No CPRI Cascading
GSM TRX Configuration 4/4/4 1/1/1
Power per RTX 20W 20W
CPRI Connection To GTMU To UBBP
CPRI Connection Type Single CPRI CPRI Mux

WBBP GTMU
LBBP UMPT WBBP
UBBP GTMU
LBBP UMPT

Notes :
Dismantle MRFUv2, as MRFU donorto site with scenario
1a (add MRFUv2 from Donor)
Move CPRI GSM from GTMU/UBRI to UBBP
G G G
9 9 9
0 0 0
0 0 0

Radio Access Network Operation 2018


Site Solution
SCENARIO 2
(SW Upgrade - MRFUd)

Part Before After


RF Board Type MRFU MRFU
MRFU/ MRRU Board Number 3 3
RF Cascading No RF Cascading No RF Cascading
CPRI Cascading No CPRI Cascading No CPRI Cascading
GSM TRX Configuration 4/4/4 1/1/1
Power per RTX 20W 20W
CPRI Connection To GTMU To UBBP
CPRI Connection Type Single CPRI CPRI Mux

WBBP
LBBP
GTMU
UMPT WBBP
UBBP GTMU
Notes :
Move CPRI GSM from GTMU/UBRI to UBBP
LBBP UMPT

G G G G G G
9 9 9 L
L L
0 0 0
0 0 0 9 9 9
0 0 0
0 0 0

Radio Access Network Operation 2018


Site Solution

Part Before After


RF Board Type MRRU MRRU
MRFU/ MRRU Board Number 3 3
RF Cascading No RF Cascading No RF Cascading
CPRI Cascading No CPRI Cascading No CPRI Cascading
GSM TRX Configuration 4/4/4 1/1/1
Power per RTX 20W 20W
WBBP UTRP CPRI Connection To GTMU To UBBP
UPEU
WBBP CPRI Connection Type Single CPRI CPRI Mux
F GTMUb
AN UBRI
UPEU
WBBPf WMPT
Notes :
Move CPRI GSM from GTMU/UBRI to UBBP

WBBP
UPEU
WBBP
F GTMUb
AN UBBPd
UPEU
WBBPf UMPT_UL

Radio Access Network Operation 2018


Site Solution
SCENARIO 4a
(Add MRRU 3926 Cascading from Donor)

Part Before After


RF Board Type MRRU MRRU
MRFU/ MRRU Board Number 3 6
RF Cascading No RF Cascading RF Cascading
CPRI Cascading No CPRI Cascading CPRI Cascading
GSM TRX Configuration 4/4/4 1/1/1
Power per RTX 20W 20W
CPRI Connection To GTMU To UBBP
CPRI Connection Type Single CPRI CPRI Mux

WBBP UTRP
UPEU
WBBP
GTMUb
Notes :
F
AN UBRI
UPEU
WBBPf WMPT
Move CPRI GSM from GTMU/UBRI to UBBP
Add CPRI cable for cascading
Add RF diversity cable for cascading
WBBP
UPEU
WBBPf
F GTMUb
AN UBBPd
UPEU
WBBPf UMPT_UL

Radio Access Network Operation 2018


Site Solution
SCENARIO 4b
(Change MRRU 3926 to MRRU 3959)

Part Before After


RF Board Type MRRU MRRU
MRFU/ MRRU Board Number 3 3
RF Cascading No RF Cascading No RF Cascading
CPRI Cascading No CPRI Cascading No CPRI Cascading
GSM TRX Configuration 4/4/4 1/1/1
Power per RTX 20W 20W
CPRI Connection To GTMU To UBBP
CPRI Connection Type Single CPRI CPRI Mux
WBBP UTRP
UPEU
WBBP
F GTMUb
AN UBRI
UPEU
WBBPf WMPT Notes :
Move CPRI GSM from GTMU/UBRI to UBBP

WBBP
UPEU
WBBPf
F GTMUb
AN UBBP
UPEU
WBBPf UMPT_UL

Radio Access Network Operation 2018


Transmission Configuration
Scenario1
WBBP UTRP  WBBP LBBP LTE and UMTS share one UMPT,
 WBBP
GTMU
 WBBP 2 IPs are required for LTE, 1 for
PWR GTMU PWR
Fan UBRI Fan UBBP control plane, 1 for user plane.
UPEU UPEU
WBBP UMPT WBBP UMPT

Scenario2
WBBP LBBP
 WBBP  WBBP
GTMU PWR GTMU PWR
Fan UBRI Fan UBBP
UPEU UPEU
WBBP UMPT

atau
UTRP UCIU WBBP LBBP
 WBBP  WBBP  WBBP
PWR GTMU PWR PWR
Fan WBBP Fan UBRI Fan UBBP
UPEU UPEU UPEU
WBBP UMPT WBBP UMPT

Radio Access Network Operation 2018


Transmission Configuration

Scenario3 (More than 2 UBBP) BBU Interconnection (CLK, Control signal)

WBBP UTRP  WBBP UCIU  WBBP UTRP 


 WBBP  WBBP  UBBP GTMU
GTMU PWR GTMU PWR PWR
Fan UBRI Fan UBRI Fan UBBP
UPEU UPEU UPEU
WBBP UMPT WBBP UMPT UBBP UMPT

In case there are UMPT boards in both main & secondary BBU,
UMPT in main BBU provide co-transmission port
Use UCIU port M0 to connect to UMPT CI Port

Radio Access Network Operation 2018


BBU Configuration
BBU CONFIGURATION
Before
Notes :
WBBP UTRP
UPEU 1. UBBPd only can be configured in slot 2 and 3
WBBP
F
UBRI
GTMUb 2. Dismantle UBRI
AN
UPEU 3. Re-connect DCS CPRI from UBRI to GTMU (need to
WBBPf WMPT
change DCS configuration)
4. Installed UBBPd in slot 2
5. Move GSM CPRI from GTMU to UBBP (need to
change GSM configuration)
After 6. LTE CPRI is same CPRI with GSM CPRI (CPRI Mux)
7. Port 03 – 05 UBBP will be use as plan for LTE1800
WBBP
UPEU (plan CA next)
WBBP
F GTMUb
AN UBBPd
UPEU
WBBPf UMPT_UL

If have CPRI in WBBP for 3G, move the CPRI and make
CPRI cascade with 3G WRFU or 3G RRU

Radio Access Network Operation 2018


UPEU Configuration
Before Before
WBBP UTRP WBBP UTRP
WBBP WBBP
F GTMUb F GTMUb
AN UBRI AN UBRI
UPEUa UPEUc
WBBPf WMPT WBBPf WMPT
After After
WBBP WBBP
F
WBBP
GTMUb
UPEUc
F
WBBP
GTMUb
UPEUc To ensure BBU DC power supply
UBBPd
AN
UPEUc
AN
UBBPd
UPEUc
capacity,
WBBPf UMPT_UL WBBPf UMPT_UL
It is necessary to install 2 UPEUc
board.
Before Before This 2 UPEUc configuration will
WBBP UTRP WBBP UTRP supply
UPEUa UPEUa
F
WBBP
UBRI
GTMUb F
WBBP
UBRI
GTMUb maximum capacity (650 watt) to
AN AN
WBBPf WMPT
UPEUa
WBBPf WMPT
UPEUc BBU without risk of lack power in
the future due to additional board.
After After
WBBP WBBP
UPEUc UPEUc
WBBP WBBP
F GTMUb F GTMUb
UBBPd UBBPd
AN AN
UPEUc UPEUc
WBBPf UMPT_UL WBBPf UMPT_UL

Radio Access Network Operation 2018


Backup Configuration
In case of hardware failure or corrupt database, it is necessary to back up the configuration files of all NEs
managed by the U2000 and the files changing dynamically during the operation

Menu :
Software > NE Backup

Radio Access Network Operation 2018


Input Regional Name
1. Input data Regional Name must be filled in “User Label” with command MML: ADD ENODEBFUNCTION:; and fill based
on Regional Name.
2. Regional Name in “User Label” must fill like this:
a. REGIONAL1  North Sumatera g. REGIONAL7  Bali NusRA
b. REGIONAL2  South Sumatera h. REGIONAL8  Kalimantan
c. REGIONAL3  Jabotabek i. REGIONAL9  Sulawesi
d. REGIONAL4  West Java j. REGIONAL10  Central Sumatera
e. REGIONAL5  Central Java k. REGIONAL11  Maluku & Papua
f. REGIONAL6  East Java
3. Example :
ADD
ENODEBFUNCTION:ENODEBFUNCTIONNAME="N_JKB005MT_FARIACARGO",APPLICATIONREF=1,ENODEBID=131005,
USERLABEL="REGIONAL3";

Radio Access Network Operation 2018


Input Location, Longitude & Latitude
1. Longitude & Latitude data follow the NODIN from RAE.
2. Fill longitude & latitude data in MML Command “ADD LOCATION:GCDF=Degree;”.
Here for the Rule:
 Location Name = eNodeB ID
 For Latitude and Longitude data before you fill in the field the value must be multiply by 1.000.000.
Example:
Longitude Latitude Latitude = -6.249083 x 1.000.000 = -6249083
106.122944 -6.249083 Longitude = 106.122944 x 1.000.000 = 106122944
So, in the MML Command you fill:
Latitude = -6249083
Longitude = 106122944
 City = City of eNodeB, Region = Region of City, Address = Address of eNodeB
 User Label = NEID
 Office = RTPO Name each Region

Radio Access Network Operation 2018


Software Version
All NE Using Latest Software
Description : To avoid different rule and problem isolation in software version, all NE should be upgrade to the equal latest
software version.
Procedure : We can query NE software version from U2000 by menu
Configuration > Report > NE Report
Checklist BTS3900 & BTS3900 LTE

Radio Access Network Operation 2018


Cell Unavailable Alarm Severity
- Cell Unavailable alarm report that cell cannot provide services. This alarm is related to physical
resources such as baseband resources, RF resources, CPRI resources, clock resources,
transmission resources, and also license resources. Some correlative alarm to Cell Unavailable :
- RF Maintenance Failure
- BBU Board Maintenance Link Failure
- Board Powered Off (RXU or BBP)
- Board Hardware Fault
- S1 Interface Fault
- SCTP Link Fault
- By default Cell Unavailable severity is
configured as Major on eNodeB.
Alarm Name : Cell Unavailable
Alarm ID : ALM-29240
- To raise awareness of Cell Unavailable alarm,
it is necessary to promote alarm severity
from Major to Critical.
Radio Access Network Operation 2018
Cell Unavailable Alarm Severity
- Severity configuration can be done in U2000 based on Alarm Name
Monitor  Alarm Settings  Redefine  Add

2. Choose Cell Unavailable

Radio Access Network Operation 2018


Alarm Masking for SCTP Link Alarm Related S1 & X2
Description
If signaling fault in eNodeB the SCTP Link Alarm will occure that make We confuse belong to
which interface because the alarm name similar with other interfaces (over IP). So, We can
masking this alarm to specifically alarm related S1 & X2 interface.
Note:
This function for software SRAN10 above.
Procedure:
Run MML Command in eNodeB:
MOD ENODEBALMCFG:SRVINTFALMCFGSW=X2-1;
If S1-1 & X2-1 is be selected, so ALM-29201 S1 Interface Fault and ALM-29204 X2 Interface
Fault is reported then ALM-25888 SCTP Link Fault is masked.

Radio Access Network Operation 2018


OMCH Interruption Automatically Recover
Description
If the OMCH Auto-Establishment Switch parameter is set to DISABLE, The eNodeB attempts
to recover the faulty remote maintenance channel based on the current transmission
configurations. If the remote maintenance channel fails due to modification of the
transmission configurations of the peer end, the remote maintenance channel cannot be
reestablished. So, We need set to ENABLE to activate Auto-Establishment.
Procedure:
Run MML Command in eNodeB:
SET DHCPSW:SWITCH=ENABLE;
And
SET TLFRSWITCH:;  Choose Enable

Radio Access Network Operation 2018


Dynamic Adjusment of Number OFDM Symbol
Description
Indicates the switch used to enable or disable dynamic adjustment on the number of orthogonal frequency
division multiplexing (OFDM) symbols occupied by the physical downlink control channel (PDCCH). If this
parameter is set to OFF, the number of OFDM symbols occupied by the PDCCH is fixed and cannot be
dynamically adjusted. If this parameter is set to ON, the number of OFDM symbols occupied by the PDCCH is
dynamically adjusted based on the required number of PDCCH control channel elements (CCEs). If this
parameter is set to ECFIADAPTIONON, the number of OFDM symbols occupied by the PDCCH is dynamically
adjusted based on the cell downlink throughput, and the adjustment performance is the best among the
three methods.
ECFIADAPTIONON, the dynamic adjustment of the number of OFDM symbols occupied by the PDCCH
considers cell downlink throughput, and therefore can reach higher throughput when downlink frequency
selective scheduling is enabled
Procedure:
Run MML Command in eNodeB:
MOD CELLPDCCHALGO:LOCALCELLID=1,PDCCHSYMNUMSWITCH=ECFIADAPTIONON;
Do to all Cell ID.
Radio Access Network Operation 2018
Script & Mechanism on eNodeB for Sleeping Cell
Background
• As a result of common network issues, a cell that cannot provide radio access services is displayed as normal due to
inappropriate parameter settings, environmental changes, transmission device faults, and hardware or software faults. For
such a cell, no alarm is generated to inform customers that this cell is abnormal. This type of cell is called a sleeping cell.

Description
• If a TRX/cell is not accessed by UEs for 4 hours, it is a sleeping TRX/cell. With the Sleeping Cell Detection and Recovery
feature, the BTS/NodeB provided by Huawei can automatically detect sleeping cells and report alarms then do recover by
automatically reset cell.
Benefit
• To Improve Network Reliability
• To Improve Operation & Maintenance Efficiency

Script for eNodeB:


MOD CELLNOACCESSALMPARA: LocalCellId=XXX, NoAccessStartDetectTime=06&00&00,
NoAccessStopDetectTime=22&00&00, NoAccessDetectTimer=4;
*XXX = Please fill the Local Cell ID
The Mechanism:
NoAccessStartDetectTime=06&00&00  This feature active start on 06:00
NoAccessStopDetectTime=22&00&00  This feature deactive on 22:00
NoAccessDetectTimer=4  If no traffic for 4 hours and ALM-29242 No Traffic Volume in the Cell alarm reported.
Radio Access Network Operation 2018
X2 Son Setup
Description
The Switch of X2 setup by SON is indicates whether to enable or disable X2 setup by SON.
The method of X2 setup by SON is indicates the method of X2 setup by SON, that is, the method of
automatically setting up X2 interfaces. The value X2_OVER_OSS can be set only for Huawei eNodeBs, and the
value X2_OVER_S1 can be set for eNodeBs of any vendor.
Those parameter applies only to LTE FDD and LTE TDD.

Procedure:
Run MML Command in eNodeB:
MOD GLOBALPROCSWITCH:X2SONSETUPSWITCH=ON,X2SONLINKSETUPTYPE=X2_OVER_S1;

Radio Access Network Operation 2018


NTP Client for Clock Time Synch with OSS
Description
This function is to lock the clock source and synch with OSS.

Procedure:
Run MML Command in eNodeB:
ADD NTPC:MODE=IPV4,IP="10.52.204.81",SYNCCYCLE=10,AUTHMODE=PLAIN;
IP = using U2000 IP
Sync cyle = 10 minute

Radio Access Network Operation 2018


Feature Flash CSFB
Description
This feature is an enhancement to the optional feature LOFD-001033 CS Fallback to UTRAN. The eNodeB
obtains UTRAN cell information through the RIM procedure and then sends the LTE-to-UMTS redirection
message including the obtained cell information to the UE. In this case, the UE can access a UTRAN cell
without obtaining UTRAN cell information. This reduces the access delay. For details about how the UTRAN
cell information is delivered to the eNodeB through the RIM procedure
Procedure:
Run MML Command in eNodeB:
MOD ENODEBALGOSWITCH:; then choose:
UtranCsfbSwitch:1 (On)  Compulsary
UtranFlashCsfbSwitch:1 (On)  the feature of flash CSFB
UTRAN RIM Switch:1 (On)  the feature of flash CSFB
Note:
The UTRAN RIM Switch must be On, then the UtranFlashCsfbSwitch recommend to ON
because if the UTRAN RIM Switch “Off” then the UtranFlashCsfbSwitch “ON” will make
abnormal CSFB.
Radio Access Network Operation 2018
Alarm GPS Antenna Fault impact Cell Faulty in LTE TDD
Description Alarm GPS Antenna Fault
Alarm GPS Antenna Fault causing the base station fails to synchronize to the satellite card
clock. Impact : the quality of services carried on the base station deteriorates. In certain cases,
the base station cannot provide services.
After GPS Antenna Fault, eNodeb have 24 hour holdover condition. After that, clock status
become Free Running & cell become faulty.
Alarm Name : GPS Antenna Fault (26121)
Impact : Cell Unavailable due to Clock not usable
Part Number Antenna GPS : 27010596

Alarm Cell Unavailable

Redefine
Change severity for alarm GPS
Antenna Fault from Minor to Critical

Radio Access Network Operation 2018


ADD LONGLAT AUTO with GPS Antenna at LTE TDD
Description
GPS Antenna can be used to define Location (Longitude & Latitude) by automatic with command ADD LOCATION.

Command  ADD LOCATION:MODE=AUTO;

Radio Access Network Operation 2018


Parameter
VSWR Alarm Parameter Threshold
Description
VSWR is a counter for measuring impedance match of the antenna feeder system. In this case, the ratio
of the reflected power to the transmit power can be measured as VSWR.
BTS3900 Type (New Integration) GBTS Type (New Integration & Modify Existing)
MML Command: MML Command:
ADD RRU:CN=*,SRN=**,SN=*,TP=TRUNK,RT=***,ALMPROCTHRHLD=18, SET BTSRXUBP:IDTYPE=BYID,BTSID=**,RXUIDTYPE=SRNSN,CN=*,SRN=*,SN=*,
ALMTHRHLD=14,MNTMODE=NORMAL,RFDCPWROFFALMDETECTSW=OFF RXUTYPE=***,LVL1VSWR=14,LVL2VSWR=18;

SET ALMLVL:AID=26529,ALVL=MAJOR; SET ALMLVL:AID=12830,ALVL=MAJOR;


SET ALMLVL:AID=5326,ALVL=MAJOR;
BTS3900 Type (Modify Existing)
SET ALMLVL:AID=12832,ALVL=CRITICAL;
MML Command: SET ALMLVL:AID=5328,ALVL=CRITICAL;
MOD RRU:CN=*,SRN=*,ALMPROCSW=OFF,ALMPROCTHRHLD=18,
ALMTHRHLD=14; Checking Data
MML Command:
SET ALMLVL:AID=26529,ALVL=MAJOR;
LST BTSRXUBP:IDTYPE=BYID,BTSID=***;
Checking Data
MML Command:
LST RRU;

Radio Access Network Operation 2018


Parameter
VSWR Testing on Live Network
BTS Manual Test VSWR Operation BTS Real Time VSWR Operation
MML Command For NodeB, eGBTS, and eNodeB: MML Command For NodeB, eGBTS, and eNodeB:
STR VSWRTEST DSP VSWR

MML Command For GBTS and run the command in BSC: MML Command For GBTS and run the command in BSC:
STR BTSVSWRTST DSP BTSBRD: INFOTYPE=RUNPARA, IDTYPE=BYID, BTSID=**, BRDTYPE=RXU,
RXUIDTYPE=SRNSN, RXUCN=*, RXUSRN=**, RXUSN=*;

Radio Access Network Operation 2018

You might also like