SON Usage and Implementation in StarHub

1 © Nokia Siemens Networks 2012

For internal use

LTE CLT Sharing Session_Indonesia / Ver. 1.0 / Rudi Wijaya

SON Usage and Implementation in StarHub LTE Project (Singapore)

By: Rudi Wijaya

Dept. / Author / Date


For internal use


AGENDA

StarHub LTE Network

Optimizer Overview

ANR Management by Optimizer

PCI Analysis


For internal use


AGENDA

StarHub LTE Network

Optimizer Overview


PCI Analysis


For internal use


NSN SON Suite Features in Radio and OSS

Self-

Healing

Self-

Optimization

Self-

Configuration

Mobility Load Balancing

Power Saving

Plug & Play

Cell Outage Detection, Reset

and Compensation

Mobility Robustness (MRO)

Automated Neighbor Relat.

Interference Optimization

Drive Test Minimization (MDT)

Alarm Correlation, Root Cause Analysis

PRACH Management

Nokia Siemens Networks E2E SON Suite

LTE SON

2G/3G SON

Open northbound interfaces

SON

Other vendor’s network

Énhanced Packet core

Distributed SON

Centralised SON


For internal use


StarHub LTE Network

• LTE 1800 with 2G RF Sharing

• Not using SON Plug and Play hence there is no DHCP server

• Implement and Using Nokia Siemens Networks’ LTE ANR strategy


For internal use


StarHub LTE Network

• NetAct

OSS5.3 MP1

• Optimizer

Optimizer 3.0 MP2 CD’s 4772 & 4773


For internal use


Optimizer Functionalities in StarHub LTE Network

• PCI-IP Mapping Creation

• Physical Cell ID management

• Analyze PCI collisions and violations

• Reallocate PCI

• Visualize PCI reuse on map

• Forbidden Code Set

• Antenna Editor

• Distance-based adjacency creation (LTE->GSM)


For internal use


AGENDA

StarHub LTE Network

Optimizer Overview ANR

Management by Optimizer

PCI Analysis


For internal use


Optimizer



For internal use


Foreign cluster CM data

Other vendor CM data

Local cluster CM data

Provisioning

Foreign cluster CM data

Other vendor CM data

Local cluster CM data

Local NetAct cluster xml

CM DB

Plan

OPT DB

Foreign NetAct cluster

Vendor X cluster

Plan


For internal use


Provisioning process using CM applications

Export CM Plan from Optimizer

Check Plan CM Analyser

Transfer plan to NW CM Operations Mgr End

Prepare Plan (automatic) CM Operations Mgr

Modify Plan (optional) CM Editor


For internal use


NetAct tools used in the ANR operation

• CM Editor

• CM Operations Manager

• Optimizer

• SON Scheduler


For internal use


RL 25TDD, RL 30

SITE

BTS(eNB)

CELL

Intra LTE Adjacency (pointer

to target eNB)

ADJLL, LNREL

X2

Mobile triggers LNREL creation.

eNB creates it automatically for all

the neigbors that are reported.


For internal use


LTE Network Elements (RL 25TDD, RL 30)

LNADJ

LNADJ 1..6

0..64

LNCEL

ADJLL

0..389

LNBTS

LNREL

0..389

Present in CM and in Optimizer

Present only in Optimizer

Optimizer creates an ADJLL for

each LNADJ that doesn’t have

the corresponding LNREL.


For internal use


AGENDA

StarHub LTE Network

Optimizer Overview


PCI Analysis


For internal use


Optimizer 3.0 CD3 for LTE

Use cases for Optimizer in LTE network:

1. New planned eNBs in the network

2. Handover in LTE network : case of an unknown cell


For internal use


Automated Neighbor Relation (ANR) Features



For internal use


Architecture of Automated Neighbor Relation (ANR)



For internal use


LTE 782 – ANR UE Fully Based 1/2


eNB1 eNB2 MME

1.) S1AP: ENB CONFIGURATION TRANSFER

to eNB2-ID (SON Information Request)

3.) S1AP: ENB CONFIGURATION TRANSFER

to eNB1-ID (SON Information Response with IP@)

2.) S1AP: MME CONFIGURATION TRANSFER

to eNB2-ID (SON Information Request)

4.) S1AP: MME CONFIGURATION TRANSFER

to eNB1-ID (SON Information Response with IP@)

X2 Establishment

3GPP TS36.300 section 22.3.6.1


For internal use


LTE 782 – ANR UE Fully Based 2/2



For internal use


Not Implementing LTE 782 - ANR UE Fully Based

• Current NSN MME has been upgraded to NS2.1

• ANR UE Fully Based is supported only in NS2.2.

• Radio part is OK and Tested!

• Where CGI resolution of Target eNB can be seen and transfer to Source eNB. Afterward, it should get X2 CP IP Addr given by MME. Unfortunately MME is not transferring the needed information to Target eNB.


For internal use


Optimizer 3.0 CD3 for LTE LTE492 Automated Neighbor Relation (ANR)

In autoconfiguration the neighbor eNBs’ IPs are stored in ADIPNO object or in LNADJs and the eNBs get this data from Configurator.

Based on this the X2 connection to neighbor relations can be established.

PCI = 3

PCI = 4 PCI = 5

IP@ = 1

PCI = 0

PCI = 1 PCI = 2

IP@ = 2

PCI 4

ADIPNO

IP@1

IP@2

IP@3

IP@4

…..

IP@32


For internal use


LTE492: Automated Neighbor Relation (ANR)



For internal use


Preparation for Optimizer

• In optimizer, sites can be listed by using browser

• Site list can be exported and check the consistency with on-air sites from MR-Status


For internal use



• Add the new sites and updated the sites with changed antenna information

• Prepared the Outdoor and Indoor Antenna Import Files


For internal use



• When importing the antenna data files in Antenna Data Editor (Optimizer), you may have a message in problem window

• Recommended to check the same line number in your imported excel file

• Probably because of wrong cell name, missing antenna data, 2-sector and indoor misconfiguration


For internal use



• Antenna Data now fully integrated to NetAct OSS and sites are ready to be used in Optimizer


For internal use



• “Refresh Actual” and ready to go for PCI-IP mapping


For internal use


Creating PCI-IP Mapping Table

• Create a New Plan for your job


For internal use



• Check site to site distance to know the range to define the neighbor


For internal use



• After planning site to site distance to define the range, you can now put the search distance


For internal use



• Now you can create PCI-IP mapping table for your selected sites


For internal use



• According to your search distance, the mapping table creation done for neighbour sites.


For internal use



• In order to export optimizer plan, click on CM Data Exchange


For internal use



• Launch CM Operation Manager and Refresh to see your plan


For internal use



• Provision your plan


For internal use



• If there is no error and finished the provision, PCI-IP mapping tables are now successfully created in NetAct OSS


For internal use



• Check the sites with PCI-IP mapping table in NetAct


For internal use



• Now ready to go out for drive testing and you will see the successful hand over in the field

• You can also see the LNADJ after coming back from drive testing


For internal use


StarHub LTE Network

• Downlink Throughput


For internal use


LTE784: ANR InterRAT GERAN



For internal use


Creating LNRELG

• As the project is LTE-2G RF sharing, distance-based adjancy creation can be used.

• For creation of LTE=> GSM adjancies

• Save the result into the plan and continue results verification in Browser and on the Map

LNRELG


For internal use


Creating LNRELG

• Click on LNRELG and define the search distance according to network topology

• Run and check the result for numbers of LNRELG created

• Listing the results in Browser and also can remove unwanted one


For internal use


Example of Inter-RAT LTE to GERAN initial neighbor allocation



For internal use


AGENDA

StarHub LTE Network

Optimizer Overview


PCI Analysis


For internal use


Physical-layer Cell Identities (PCIs)

PCI group

0

1

2

165

166

…

167

0 1 2

3 4 5

6 7 8

495 496 497

498 499 500

… … …

501 502 503

PCI offset

0 1 2

23

14

1

66

412

502

234

322

98


For internal use


PCI Collisions and Confusions

• 3GPP defines collision-free as “the PCI is unique in the area that the cell covers”

• 3GPP defines confusion-free as “a cell shall not have neighboring cells with identical PCIs”

ideally only initial PCI values

need to be assigned

PCI values of ACTUAL cells

need to be changed


For internal use


PCI Management


For internal use


Analyze PCI collisions and violations 1/5



For internal use





For internal use


Forbidden Codes

• Customer want to reserve some PCI group for future Femto Cells

• In this case, there are some codes that cannot be used in the allocation

• Create a new Forbidden Code Set and assign to the cells


For internal use


Summary

• Efficient, Easy and User Friendly

• Geographical visualization and Analysis

• Powerful CM parameters management with Browser

• Effective parameters changes

• Speed up the rollout project with accurate neighbor creation and parameters managements

• Good Customer’s Impression on Optimizer for NSN ANR method giving a quick successful handover in the field during the drive test


For internal use


Nokia Siemens Networks Nokia Siemens Networks

Jakarta – INDONESIA

+62 812 1083902

[email protected]

Rudi Wijaya LTE eNB CLT APAC

Thank You…

SON Usage and Implementation in StarHub

Documents

Transcript of SON Usage and Implementation in StarHub