Uploaded byRathnaKumar47
7,108 views

Radio Network Design & Roll Out

This document provides an overview of radio network design for rollouts, including configuration of parameter structures, site configuration, mobility configuration, and neighbors configuration. It discusses organizing parameters into managed object classes with a hierarchical structure. Major sections cover defining radio modules and cells, antenna line configuration, frequency configuration, and adding new objects. Configuration of idle and connected mode mobility parameters and system information blocks is also addressed.

Embed presentation

Downloaded 368 times
Soc Classification level 1 © Nokia Siemens Networks Presentation / Author / Date Radio Network Design for Roll Outs Configuration Management
Soc Classification level 2 © Nokia Siemens Networks Contents • Parameter structure (MOC) and Site Configuration • Idle Mode Mobility Configuration • Connected Mode Mobility Configuration • Neighbours Configuration • S1 Handover Configuration • Blacklisting • Exercise • Plan Creation Methods • Exercise Presentation / Author / Date
Soc Classification level 3 © Nokia Siemens Networks Parameter structure (Managed Object Classes) and Site Configuration Presentation / Author / Date
Soc Classification level 4 © Nokia Siemens Networks Introduction • Parameters are organised into Managed Object Classes (MOC) that follow a hierarchical structure containing three main areas : – Radio Network Parameters (RNW) – Site Configuration Parameters (HW) – LTE BTS Transport Parameters (FTM) • Majority of MOCs are stable between releases but some of them can be added/removed between releases. Same applies for the parameters under each MOC. They can be found in NOLS Operating Documentation • Not all MOCs are mandatory (i.e. they don’t need to be configured) • This section is about configuring different MOCs based on the network characteristics needed when creating a site configuration file (also can be used as site template) Presentation / Author / Date Focus of the training
Soc Classification level 5 © Nokia Siemens Networks Managed Object Hierarchy (RL30) PLMN MRBTS ANTL BTSSCL LCELL LNBTS MHA RET RMOD SMOD FTM ADIPNO CTRLTS MTRACE GTPU MODRED LNADJ LNADJG LNADJW LNADLP LNCEL LNMME MODPR MOPR PRMNL SCTP LNADJL CDFIM GFIM IAFIM IRFIM LNHOG LNHOIF LNHOW LNREL REDRT UFFIM GNFL MORED AMRG CERTH ETHLK IPNO IPSECC SYNC UNIT TAC LTAC STPG PPTT OAMPRF IEIF IVIF QOS IPRT INTP IPRM IHCP BFD BFDGRP TOPIK TWAMP RNW Parameters FTM Parameters Site Configurati on Parameters
Soc Classification level 8 © Nokia Siemens Networks Parameter Configuration Parameter configuration can be divided into: • Site specific parameters: Those that need to be planned/allocated separately for each site • ‘Site template’ parameters: Those that can be assigned a value that is pre-defined in a template as they don’t vary across the sites of a network. They can be: • Operator specific: E.g. mnc, mcc, plmnId • ‘Default’ parameters • References for parameter configuration are: • PDDB: http://pddb.inside.nokiasiemensnetworks.com/pddb/ • PKDB: http://pkdb1.emea.nsn-net.net:8080/pkdbWebToolLTE/ • SCF: System Configuration File • Configuration Management IMS Folder: • https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/436539771 • As part of PKDB (link above) scenarios Presentation / Author / Date
Soc Classification level 9 © Nokia Siemens Networks System Configuration Files (SCF) Overview • Golden System Configuration Files (SCF) are xml files containing the basic MOCs and related parameters to create a commissioning file or a template for a site • Vendor specific (i.e. hidden parameters) are not part of the SCF • Contents of the SCF vary depending on the LTE variant (FDD or TDD) and on the different releases • Even within the same release, there are different versions of SCF with newer versions containing more features implemented in the meantime • Once P8 milestone for a Release has been reached the contents of the SCF are frozen. Recommendation is always to use the latest SCF available Presentation / Author / Date MOC: Managed Object Classes
Soc Classification level 10 © Nokia Siemens Networks System Configuration Files (SCF) Structure SCF can not be used directly as a template file for an eNB due to: • MOCs and instances need to be adapted for each case • Only 1 LNCEL object (normally, 3 LNCEL objects are required) • Only ANTL-1 to ANTL-6 are defined (normally, up to ANTL- 12 is required) • Some parameters, operator specific, haven’t got any value assigned: • They may not contain all MOCs required or MOCs that are not required (LNADJG, IRFIM…) Presentation / Author / Date MOCs defined in SCF for RL30
Soc Classification level 11 © Nokia Siemens Networks System Configuration Files Parameter values (SCF vs. PDDB) • Most default parameter values in PDDB should be aligned with SCF values after P8 milestone • Reasons why parameter values can be different: • SCF is focused on lab testing, low loaded trials and customer networks whereas PDDB values should be more generic. E.g. cell load dependent parameters • Other parameter values in SCF are the result of a workaround for some issue (network or UE) that may be removed in future release/SW-version • All cases of differences between PDDB default values and Golden SCF should be documented in the corresponding GMC scenario within the Parameter Knowledge Database (PKDB): Presentation / Author / Date RL30 RL20 RL25
Soc Classification level 12 © Nokia Siemens Networks Site Configuration RMOD and SMOD MOCs An starting point when creating a template or configuring a site is to define how many and which type of RF modules (RMOD) and System Modules (SMOD) will be used • RMOD object: • Type of RF module is specific to the frequency used • Amount of RF modules per site depends on the site configuration. E.g. 3 cells site with 2Tx MIMO 2 • Distributed case : 3 RF modules (1 RF module per cell) • ‘Normal configuration’: 2 RF modules ( to cover for the 3 cells) • SMOD object: • To define the type of system module (FSME) and the technology used (EUTRA) Presentation / Author / Date
Soc Classification level 13 © Nokia Siemens Networks Site Configuration Cells configuration and ANTL MOC • After RF module definition is necessary to define the cells per site: – How many cells – RF modules and antenna Lines used per cell – MIMO settings – Power of the RF module • Relation between antenna ports used and antenna lines may not be so intuitive • Parameters involved: • lcrId: ID of the Local Cell Resource ( i.e. cell/sector ID). Unique value in the eNB for each cell • antId: Identifies the specific antenna port in the Radio Module for the antenna line. Range and step: ANT1 (0), ANT2 (1), ANT3 (2), ANT4 (3), ANT5 (4), ANT6 (5) • antlId: Identifies the specific antenna line • rModId: Identifies the Radio Module Presentation / Author / Date
Soc Classification level 14 © Nokia Siemens Networks ANTL object 3 sector site • Common configuration where the 2 RF modules are situated next to the system module Presentation / Author / Date antId=0 (ANT1 in BTS SM) antId=2 (ANT3 in BTS SM) antId=4 (ANT5 in BTS SM)
Soc Classification level 15 © Nokia Siemens Networks ANTL object 3 sector site: BTS SM definition • For each Local cell (lcrId) it is required to define the antId used in each Radio Module, the MIMO settings and the carrier power Presentation / Author / Date
Soc Classification level 16 © Nokia Siemens Networks Defining ANTL object 3 sector site: xml file • In the xml file, there is a total of 12 ANTL objects Presentation / Author / Date • Parameter structure for the ANTL used (i.e. ANTL1,3,5,7,9,11) is the same as per ANTL-1 • Parameter structure for the ANTL not used (i.e. ANT2,4,6,8,10,12) is the same as per ANTL-2
Soc Classification level 17 © Nokia Siemens Networks Defining ANTL object 3 sector distributed site • 1RF module required per sector in order to have the 2x2 MIMO Presentation / Author / Date antId=0 (ANT1 in BTS SM) antId=2 (ANT3 in BTS SM)
Soc Classification level 18 © Nokia Siemens Networks ANTL object 3 sector distributed site: BTS SM definition • For each Local cell (lcrId) it is required to define the antId used in each Radio Module, the MIMO settings and the carrier power Presentation / Author / Date
Soc Classification level 19 © Nokia Siemens Networks Defining ARFCN Frequency Included in LNCEL MOC • It is enough to define the DL ARFCN frequency for each cell and the bandwidth. UL ARFCN is automatically calculated Presentation / Author / Date Downlink Uplink
Soc Classification level 20 © Nokia Siemens Networks Addition of New Objects not in SCF MHA, RET MOCs • It is possible to define new objects not in the original SCF like MHA, RET (Remote Electrical Tilt)… as BTS SM asks for the parameters required Presentation / Author / Date
Soc Classification level 21 © Nokia Siemens Networks Radio Network Configuration Parameters MRBTS, LNBTS MOCs • All radio related parameters are under MRBTS object Presentation / Author / Date Multiradio flexi BTS site Identifier ( MRBTS-ID) must be the same as the LNBTS-ID
Soc Classification level 22 © Nokia Siemens Networks Radio Network Configuration Parameters Errors • If working directly with SCF, LNBTS parameters give many errors (indicated by a ‘yellow triangle’) • Errors indicate missing mandatory parameters or parameters that cannot be validated as they are not recognised (i.e. those with ‘e.g.xxxx’ values in SCF) • 2 ways of solving it: • Open each MOC with an error and complete the mandatory parameters indicated by the yellow asterisk • Go through the list of errors (below). By clicking each of the errors BTS SM points the user to where the error is Presentation / Author / Date
Soc Classification level 23 © Nokia Siemens Networks LNBTS and LNCEL children objects • Which objects to add depend on each operator case • LNCEL child objects related to idle mode (cell reselection): IAFIM, IRFIM, UFFIM, GFIM • LNCEL child objects related to connected mode mobility: LNHOIF,LNHOW,LNHOG,LNREL,REDRT • LNBTS child objects related to connected mode mobility: ADIPNO, LNADJ, LNADJG, LNADJW Presentation / Author / Date
Soc Classification level 24 © Nokia Siemens Networks Idle Mode Mobility Configuration Presentation / Author / Date
Soc Classification level 25 © Nokia Siemens Networks System Information Blocks (SIBs) • UE reads the system information within Idle mode to acquire parameters needed to complete cell selection and reselection • System information is broadcast using a Master Information Block (MIB) and a series or System Information Blocks(SIB) • SIB1..3 are mandatory • SIB 4,5,6,7,8 are optional and are defined within LNCEL Presentation / Author / Date More info: TS36.331
Soc Classification level 26 © Nokia Siemens Networks siXMappingInfo Parameter LNCEL • LNCEL/siXMappingInfo parameter indicates which System Information Block is contained in the SI-X message. Values: SIB4(2), SIB5(3), SIB6(4), SIB7(5), SIB8 (6), notUsed (18) Presentation / Author / Date SI: System Information MOC: Managed Object Class • If ‘SIB4’ is defined in any LNCEL/siXMappingInfo where X={4,5,6,7,8} then the MOC IAFIM (iafimId) object must be defined • If 'SIB5' is defined in LNCEL, then MOC IRFIM (irfimId) needs to be created • If 'SIB6' is defined in LNCEL, then MOC UFFIM (uffimId) needs to be created • If 'SIB7‘ is defined in LNCEL, then MOC GFIM (gfimId) needs to be created • If 'SIB8‘ is defined in LNCEL, them MOC CDFIM (cdfimId) needs to be created • Example where only si4MappingInfo is configured indicating that SI-4 carries the SIB4 information:
Soc Classification level 27 © Nokia Siemens Networks SIB3 LNCEL • SIB3 carries the cell reselection parameters (serving cell information) Presentation / Author / Date • All these parameters are part of LNCEL object
Soc Classification level 28 © Nokia Siemens Networks SIB4 and IAFIM (1/2) • IAFIM parameters are broadcasted in SIB4 (neighbour cell information) Presentation / Author / Date • SIB4 contents are optional! • Intra Frequency Neighbours plus offsets • Intra Frequency Blacklisted Cells • CSG reserved cells i.e. for Home eNB -> not implemented CSG: Closed Subscribed Group
Soc Classification level 29 © Nokia Siemens Networks SIB4 and IAFIM (2/2) • IAFIM only needs to be created to give some special cell reselection offset (other than 0) to certain neighbour cells or to blacklist cells Practice: • Recommendation is to create a ‘dummy’ SIB4 as it is required for certain terminals e.g. Huawei LTE-USB sticks otherwise they crash • If IAFIM object is created them either blacklisted cells OR neighbour cells need to be defined – It is enough to configure a ‘dummy’ PCI in IAFIM – SIB4 periodicity in this case can also be longer • Presentation / Author / Date Theory: • All parameters in IAFIM are optional i.e. – No need to define intra-frequency idle mode neighbours – UE does not need SIB4 as it evaluates the available found neighbour cells + any additional cells defined in SIB4 if configured
Soc Classification level 30 © Nokia Siemens Networks Intra frequency cell reselection Practical Experience • qOffsetCell (the offset for the neighbouring cells) is in the IAFIM object and has to be defined separately for each neighbour relation (defined by the neighbours’ PCI). • Issue: It is not convenient to maintain. E.g. If creating a new PCI plan it is also necessary to change the PCIs in all the IAFIM objects • Solution: To ”move” all the offset to the qHyst (the offset for the serving cell) • E.g. instead of defining qHyst = 1dB and qOffsetCell = 2 dB to change qHyst to 3 dB and qOffsetCell to 0 (or don’t define the IAFIM at all)
Soc Classification level 31 © Nokia Siemens Networks Intra frequency cell reselection Practical Experience: Example • In the Telia Denmark network: – LNCEL:qHyst was set to 1 dB – IAFIM:qOffsetCell was set to 2dB, only defined for intra-site neighbours • This meant: – when reselecting to intra-site neighbours: total hysteresis was 3 dB (2+1) – When reselecting to non intra-site neighbours: total hysteresis was 1 dB (as no qOffsetCell was defined for the other neighbours) – 1 dB of hysteresis is too little leading to many cell reselections List only contains offset for the two intra site neighbours
Soc Classification level 32 © Nokia Siemens Networks Intra frequency cell reselection Idle mode PCI plot Before parameter change, cell reselections happening too often After parameter change, less ping pong between cells
Soc Classification level 33 © Nokia Siemens Networks IRFIM object SIB5: Inter frequency cell reselection • Idle mode mobility between two different LTE frequency layers, e.g. LTE 2600MHz for capacity sites and LTE 800MHz for coverage sites • IRFIM parameters are broadcasted in the SIB5 IRFIM object
Soc Classification level 34 © Nokia Siemens Networks UFFIM object SIB6: Inter RAT cell reselection • SIB6 and UFFIM with priorities and reselection thresholds towards 3 different WCDMA carriers Presentation / Author / Date
Soc Classification level 35 © Nokia Siemens Networks Inter RAT cell reselection Settings on WCDMA side (1/2) • ‘RAN2067 LTE interworking feature’ needs to be activated • Software needs to be appropriate e.g. WBTS SW BTS WN6.0 PP2.03 and activated on all WCDMA sites • ‘LTE Cell Reselection in WCEL needs to be enabled • RNC setting for SIB19 Presentation / Author / Date
Soc Classification level 36 © Nokia Siemens Networks17 May 201636 • ADJL configuration Inter RAT cell reselection Settings on WCDMA Side (2/2)
Soc Classification level 37 © Nokia Siemens Networks GFIM object LTE to GSM reselection • SIB7 needs to be activated • Mandatory parameter: GNFL/bandInd • It distinguishes between GERAN frequency bands if ARFCN values are associated with either GSM1800 or GSM1900. Values: gsm1800 (0) or gsm1900 (1) • If other ARFCN bands then the parameter although mandatory is not relevant • E.g. GNFL/gerArfcnVal = 1-124 (i.e. GSM900 frequencies) then bandInd can be either 0 or 1 Presentation / Author / Date
Soc Classification level 38 © Nokia Siemens Networks Connected Mode Mobility Configuration Presentation / Author / Date
Soc Classification level 39 © Nokia Siemens Networks Intra-Frequency Handovers • All parameters related with intra-frequency handover are under the LNCEL object: – These are the A3 and A5 (offsets, report intervals, time to trigger) – Parameters to enable the A3 and A5 handovers: enableBetterCellHo and enableCovHo – All thresholds referred to the serving cell: Threshold1, Threshold2/2a, Threshold3/3a, Threshold4 • Intra cell reselection parameters are also under LNCEL Presentation / Author / Date
Soc Classification level 40 © Nokia Siemens Networks LNHOIF Inter-Frequency HO • LNBTS:actIfHo must be enabled • Inter-frequency HO is activated on site level • Need to create a LNHOIF object per cell defining the parameters that will be used in the Measurement Configuration message and all the thresholds for A3/A5 event • Need to define the LNCEL parameters regarding threshold2/2a to activate/deactivate inter- frequency measurements • Inter-frequency HO parameters: Presentation / Author / Date Inter-Frequency Parameters
Soc Classification level 41 © Nokia Siemens Networks LNHOW, LNAJDW (RL30) IRAT HO to WCDMA Presentation / Author / Date • LNADJW [LNBTS]: Defines WCDMA neighboring cell(s) • LNHOW [LNCEL]: For each predefined EUTRA (utraCarrierFreq) defines event B2 related parameters • New parameters in already existing objects LNCEL and LNBTS are introduced
Soc Classification level 42 © Nokia Siemens Networks IRAT to WCDMA (RL30) LNBTS Configuration • LNBTS/LNADJW to define candidate 3G neighbor cell information for handover • Identifier 0 originally a bug • LNCEL/Related LNADJW instance list needs to be created with “WCDMA Cell Index ID” according to 3G neighbor lists need for that LTE cell. Create per 3G neighbor cells • actHOtoWcdma enables the feature Handover from LTE to WCDMA LNADJW-x = LNADJW: lnAdjWIndex
Soc Classification level 43 © Nokia Siemens Networks IRAT to WCDMA LNCEL • LNCEL/LNHOW needs to be created per 3G neighbor frequency • One LNHOW needed per frequency • LNCEL/UFFIM needs to be created per 3G neighbor frequency for cell reselection
Soc Classification level 44 © Nokia Siemens Networks LNHOG, LNADJG (RL30) eNACC to GSM • LNHOG: Information about NACC thresholds and timers for predefined set of ARFCNs defined by the parameter arfcnValueListGERAN • LNADJG:GSM cell considered as neighbouring GSM cell by LNCEL when its lnAdjGId parameter is listed on GSM Neighbouring Cell Information LNCEL:adjGInf parameter • New parameters in already existing objects LNBTS, LNCEL are introduced Presentation / Author / Date
Soc Classification level 45 © Nokia Siemens Networks CS Fallback to UTRAN (1/2) LNBTS, LNCEL, UFFIM, GFIM • CS fallback needs to be enabled via LNBTS:actCSFBRedir • Redirection technologies (WCDMA or GSM) need to be configured: UFFIM for WCDMA and GFIM for GSM • Activation of SIB6 for WCDMA and SIB7 for GSM (within LNCEL) Screenshots for WCDMA case
Soc Classification level 46 © Nokia Siemens Networks CS Fallback to UTRAN (2/2) REDRT • Necessary to create the REDRT object indicating the RAT for redirection and the priority for CS fallback with redirection • REDRT object also needs to be created for RRC Connection Release with Redirect (Threshold4) • One RDRT object is created per RAT frequency/band indicator
Soc Classification level 47 © Nokia Siemens Networks Presentation / Author / Date S1 Handover Configuration
Soc Classification level 48 © Nokia Siemens Networks Intra-LTE handover via S1 Parameter settings up to RL 20 1/2 • S1 handover doesn’t seem to be enabled in live networks but it is normally tested to ensure the proper configuration and functioning • Following MOC have to be adapted/created for setting up S1-based HOs: 1. The S1 handover feature needs to be enabled in LNBTS by: <p name="actLTES1Ho">true</p> 2. If the target eNB is able to perform X2-based handovers the target cell has to be blacklisted for X2 handover. For functionality testing of S1 HO, the X2 neighbour cell needs to be blacklisted: LNCEL object: <list name="blacklistHoL"> <item> <p name="blacklistTopo">onlyX2</p> <p name="freqEutra">65536</p> <p name="phyCellIdRange">n8</p> <p name="phyCellIdStart">pci</p> </item> </list>
Soc Classification level 49 © Nokia Siemens Networks Intra-LTE handover via S1 Parameter settings up to RL20 2/2 3. LNADLP (Target cell for S1 Handover) needs to be created per S1 neighbour cell LNBTS object: <managedObject class="LNADLP" distName="LNBTS-1001/LNADLP-1" operation="create“ <list name="adjBcPlmnIdOp"> <item> <p name="adjBcMccOp">MCC</p> <p name="adjBcMncOp">MNC</p> <p name="adjBcMncLenOp">length</p> <…> <p name="adjEarfcnOp">ARFCN</p> <p name="adjPhyCellIdOp">pci</p> <p name="adjTacOp">tac</p> <p name="lnAdlpId">0</p> </managedObject> • Note: On RL30, LNADLP object has been removed.
Soc Classification level 50 © Nokia Siemens Networks Intra-LTE handover via S1 Parameter settings RL30 • In RL30 the object LNADLP is removed • With feature LTE782 (ANR Fully UE based) in place there is not need for the object LNADLP:  A part of the procedure for LTE782 is the configuration of the X2 interface. After X2 successfully established source and target eNBs exchange configuration information necessary to fill in MOCs LNADJ and LNADJL  Until X2 link is successfully setup, cells being already defined in LNADJL can be regarded as targets for S1 HO (if feature is enabled) • To configure a pure S1 HO target cell: – Parameter LNADJ/cPlaneIpAddr must be left empty and… – LNADJ/cPlaneIpAddrCtrl must be set to: enbControlled • To prohibit X2 connection establishment, the neighbour eNB needs to be blacklisted via LNBTS/glbNbEnbIdX2LinkBlacklist Presentation / Author / Date
Soc Classification level 51 © Nokia Siemens Networks Summary of blacklisting parameters Connected Mode: • Blacklisting for (X2 or X2&S1) HO between an LTE cell and intra/inter- frequency list of cells • LNCEL: blackListTopo (part of blackListHoL) • Blacklisting between an LTE cell and a WCDMA/GSM cell • LNCEL: cellblacklisted (WCDMA/GSM) • X2 blacklisted eNB Id: related to (RL30) ANR fully UE based • LNBTS: glbNbEnbIdX2LinkBlacklist • (RL30) LTE cell blacklisted to be HO target of another LTE cell. Applies in addition to blackListTopo • LNREL: handoverAllowed Presentation / Author / Date
Soc Classification level 52 © Nokia Siemens Networks Neighbours Configuration
Soc Classification level 53 © Nokia Siemens Networks Contents • Neighbours configuration in RL20/RL15TD • Manual Definition • SON (ANR) • Summary • Neighbours configuration in RL30/RL25TD • Manual definition • SON (ANR) • Summary • Differences in neighbour definitions between RL20 and RL30 Presentation / Author / Date
Soc Classification level 54 © Nokia Siemens Networks Neighbours configuration in RL20/RL15TD Manual definition (no ANR) • Neighbours are manually defined via the C-plane IP@ of the adjacent eNodeB(s) • Defined in MOC ADIPNO within the adjEnbIpAddressMap via parameter adjEnbCPlaneIpAddress • Once the source eNB knows the IP@ of the target eNBs it establishes the X2 connections that allow for: • Automatic derivation of all necessary neighbour site (MOC LNADJ) and neighbour cells (MOC LNADJL) information • Automatic creation and population of neighbour cell information list (in MOC LNCEL) with all cells of the parent eNB and all cells for which the parent eNB has received configuration information from neighbour eNB Presentation / Author / Date
Soc Classification level 55 © Nokia Siemens Networks ADIPNO MOC (RL20) ADjacent IP NOde • It is enough to define the neighbour IP@ (AdjEnbCPlaneIpAddress) • Additional parameters in the ADIPNO object and existing values of adjMacroEnbId, adjMcc, adjMnc and adjMncLenght will be updated once that file is uploaded into the eNB (i.e. during the X2 setup) Presentation / Author / Date SCF original ADIPNO object… ADIPNO object after site integration
Soc Classification level 56 © Nokia Siemens Networks ADIPNO object (RL20) Presentation / Author / Date Defines the list of neighbours (enough to configure the AdjEnbCPlaneIpAddress) After site integration objects LNADJ and LNADJL are automatically created:
Soc Classification level 57 © Nokia Siemens Networks Neighbours configuration in RL20/RL15TD ANR definition • Feature LTE492: ANR support for LTE with OAM • No need for manual pre-planning of eNB adjacencies for X2 connection setup • NetAct generated PCI/RF/IP@ mapping tables for neighbour site relations are downloaded to eNB during auto-configuration • For each unknown adjacent cell, eNB searches the PCI/RF/IP@ look up table (stored in MOC LNBTS under pciIpAdrMap) to determine the IP@ needed for the X2 establishment towards eNB being a parent of unknown cell • After X2 connection is successfully established, source and target eNBs exchange configuration information necessary to fill in MOCs LNADJ and LNADJL and to add adjacent cells to neighbour cell information list in MOC LNCEL (attribute adjCellInfoL) same as in the previous case Presentation / Author / Date pciIpAdrMap only exists when neighbours are created with NetAct
Soc Classification level 58 © Nokia Siemens Networks Common information RL20 • MOCs LNADJ and LNADJL as well as parameter adjCellInfoL (in MOC LNCEL) are not modifiable for operator – that are just read only (in NetAct and BTS SM) Presentation / Author / Date • MOC LNADLP: (ADjacent LTE cell Plan based) • Contains target cells for S1-based HO that must be created by operator as they can’t automatically be created by eNB • A cell may be target cell for S1- and X2-HO. In that case the represented by two objects: • one LNADJL object for the X2-HO target • one LNADLP object for the S1-HO target • parameter lnAdlpInf provides a reference to the LNADLP object if the cell is configured to be a S1-HO target too
Soc Classification level 59 © Nokia Siemens Networks Summary RL20 • Difference between using SON ANR features or not only affects how the neighbour are defined: • SON (LTE 492:ANR with OAM extension) neighbours are defined with NetAct • Manual: neighbours are defined as a list of IP addresses adjEnbCPlaneIpAddress in the ADIPNO:adjEnbIpAddressMap • Once the IP@ of the neighbour site is available the updates in the involved MOC are automatic ( LNADJ, LNADJL, LNREL) after X2 setup Presentation / Author / Date
Soc Classification level 60 © Nokia Siemens Networks Neighbours configuration in RL30/RL25TD LTE782: ANR Fully UE based (3GPP) • eNB requests UE to report the ECGI of unknown cells reported in the measurement report • UE must support decoding and delivery of ECGI on request coming from eNB • Derived ECGI is used as input to an IP@ resolution procedure over S1 IF • eNB retrieves, with the help of MME, the C-plane IP@ needed to setup X2 connection towards the neighbour eNB parenting the UE-reported cells • Once IP@ is known then X2 connection to eNB hosting the neighbour cell can be established Presentation / Author / Date • No need for pre-defined PCI/RF/IP@ mapping tables (no need for NetAct)
Soc Classification level 61 © Nokia Siemens Networks Neighbours configuration in RL30/RL25TD LTE782: ANR Fully UE based (3GPP) • When X2 connection is established, source and target eNBs exchange configuration information necessary to fill in MOCs LNADJ and LNADJL • Bidirectional neighbour cells configuration data exchange • eNB knows all cells of the neighbouring eNB by PCI and IP address • LNADJL is created for all cells belonging to the peer eNB (not only for the unknown cell that triggered the procedure) • ANR is not triggered again when UE reports PCI of those not yet discovered cells • eNB creates the LNREL for the newly discovered cell (if this LNREL has not been created manually yet) • MOC LNREL (neighbour relations) is created by the eNB only for those cells that have been included in the UE measurement report received in given cell
Soc Classification level 62 © Nokia Siemens Networks Neighbours configuration in RL30/RL25TD LTE782: ANR Fully UE based (3GPP) • ANR feature implies the definition of new parameters in LNBTS and LNCEL MOCs necessary for the ECGI derivation and for the detection of unknown cells (active detection) • Parameters involved an additional information of the feature can be found in: • https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D437011923 Presentation / Author / Date
Soc Classification level 63 © Nokia Siemens Networks Neighbours configuration in RL30/RL25TD Manual definition (no ANR) • Neighbours are defined with the parameter cPlanIpAddr (MOC LNADJ) • As in the ANR case, once the eNB has the IP@ of the eNB’s hosting the neighbour cells, it automatically attempts the setup of the X2 connection and if successful, it automatically creates the corresponding LNADJL and complements the information in LNADJ • The creation of corresponding LNREL is triggered automatically after reception of a measurement report from the UE containing that cell
Soc Classification level 64 © Nokia Siemens Networks RL30 Summary (1/2) • In RL30 neighbours can be created manually via LNADJ: cPlanIpAddr or automatically by the eNB • Once IP address of neighbour site is detected and X2 connection is successful the eNB automatically creates the corresponding LNADJL and complements the information in LNADJ • LNADJ and LNADJL can be created also manually (in RL20 only automatic creation). Cases: • To blacklist cells, configure cells for pure S1 HO (via LNREL) • If LNADJ, LNADJL are created manually (via plan) the lowest available IDs should be used ( 0, 1…) to avoid ID conflicts in case with the automatic case as eNB uses the highest free LNADJ/LNADJL/LNREL instance ID in automatic creation procedure • LNADJ and LNADJL: can be modified or deleted via plan file Presentation / Author / Date
Soc Classification level 65 © Nokia Siemens Networks RL30 Summary (2/2)  LNREL object can also be created manually for blacklisting, define S1-HO or define cell specific offsets  LNREL objects are created by eNB if corresponding LNADJL object already exist and certain PCI is reported by UE as a result of A3 or A5 event • LNREL objects remain after deleting the LNADJL. The relation becomes invalid for HO but still is considered for blacklisting LNBTS LNCELLNADJ LNADJL LNREL LNREL: Relation between the parent cell LNCEL and one LNADJL cell
Soc Classification level 66 © Nokia Siemens Networks LNADJ, LNADJL and LNREL Relations LNREL: • New MOC in RL30 mainly related with ANR and Optimization of neigh relations • LNREL: cell to cell neighbour relationship between parent LNCEL and another LTE cell identified in LNADJL with ecgiAdjEnbId and ecgiLcrId • LNREL provides additional information on the neighbour relationship defined in LNADJL: • Definition of cell individual offsets • Blacklisting Presentation / Author / Date LNBTS LNCELLNADJ LNADJL LNREL LNADJ: neighbour site of parent LNBTS • Site identified by cplanIpAddr and adjEnbId that is the lnBtsId of the neighbour site LNADJL: specifies the cells belonging to LNADJ site that have a neighbour relationship with the parent eNB cells (LNCEL-x) • Cells identified via: – ecgiLcrId – ecgiAdjEnbId – phyCellId (not the EutraCelId)
Soc Classification level 67 © Nokia Siemens Networks Differences in neighbour definitions Between RL20/RL30 • In RL30 neighbour site IP@ are not defined anymore in ADIPNO MOC but in LNADJ MOC • LNADPL MOC (to define S1-HO relations) disappears • Until X2 link is successfully setup, cells being already defined in LNADJL can be regarded as targets for S1 HO (if feature is enabled) • New MOC: LNCEL/LNREL for neighbour relations containing information previously part of LNCEL (adjacent cell info List) • ANR feature in RL20 supports also intra and inter frequency neighbours. ANR feature in RL30 only supports intra frequency neighbours
Soc Classification level 68 © Nokia Siemens Networks LNADJL (1..LNADJL (1..66):):  lnAdjlIdlnAdjlId  lnAdlpInflnAdlpInf  phyCellIdphyCellId  adjEutraCelIdadjEutraCelId  ecgiPlmnIdecgiPlmnId  ecgiAdjEnbIdecgiAdjEnbId  ecgiLcrIdecgiLcrId  sourceOfDatasourceOfData  validityOfDatavalidityOfData  …… ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) Feature details Neighbour relations database structure in RL30Neighbour relations database structure in RL30 LNBTS (1..1) lnBtsId, …, actUeBasedAnrIntraFreqLteactUeBasedAnrIntraFreqLte,, glbNbEnbIdX2LinkBlacklistglbNbEnbIdX2LinkBlacklist, pciIpAdrMap (dlEarfcn, ipAdr, pci, eNbId)*pciIpAdrMap (dlEarfcn, ipAdr, pci, eNbId)*, … … LNADJG(0..32)LNADJG(0..32) LNADJW(0..32)LNADJW(0..32) LNADJ (0..LNADJ (0..6464):):  lnAdjIdlnAdjId  adjEnbIdadjEnbId  plmnIdplmnId  ……  cPlaneIpAddrcPlaneIpAddr  cPlaneIpAddCtrlcPlaneIpAddCtrl  x2LinkStatusx2LinkStatus LNADLP (0..32):LNADLP (0..32):  lnAdlpIdlnAdlpId  adjPhyCellIdOpadjPhyCellIdOp  adjEgciOpadjEgciOp …… * LTE492 specific* LTE492 specific LNRELLNREL (0..389):(0..389):  lnRelIdlnRelId  ecgiAdjEnbIdecgiAdjEnbId  ecgiLcrIdecgiLcrId  ecgiPlmnIdecgiPlmnId  …… LNCEL:LNCEL:  lnCelIdlnCelId  adjCelInfoLadjCelInfoL eutraCelId_1eutraCelId_1 …… eutraCelId_130eutraCelId_130  phyCellIdphyCellId  eutraCelIdeutraCelId  lcrIdlcrId  adjWInfListadjWInfList  adjGInfListadjGInfList  anrThresNbCellanrThresNbCell  drxProfile101drxProfile101  nLTEIntraNeighbnLTEIntraNeighb oursours  …… LNCEL:LNCEL:  lnCelIdlnCelId  adjCelInfoLadjCelInfoL eutraCelId_1eutraCelId_1 …… eutraCelId_130eutraCelId_130  phyCellIdphyCellId  eutraCelIdeutraCelId  lcrIdlcrId  adjGInfListadjGInfList  adjWInfListadjWInfList  anrThresNbCellanrThresNbCell  drxProfile101drxProfile101  nLTEIntraNeighbnLTEIntraNeighb oursours  …… 1…66 LNRELLNREL (0..389):(0..389):  lnRelIdlnRelId  ecgiAdjEnbIdecgiAdjEnbId  ecgiLcrIdecgiLcrId  ecgiPlmnIdecgiPlmnId  …… Presentation m ode only!!! Presentation m ode only!!! ADIPNO (1..1):ADIPNO (1..1):  AdIpNoIdAdIpNoId  adjEnbIpAddressMapadjEnbIpAddressMap  ……
Soc Classification level 69 © Nokia Siemens Networks Parameters for Blacklisting
Soc Classification level 70 © Nokia Siemens Networks Blacklisting: IAFIM Intra-Frequency cells • If an operator wants to prohibit UEs to camp on certain cells, these cells can be blacklisted • The blacklisted PCIs are defined by the parameters IAFIM:startIntraPci and IAFIM:rangeIntraPci • Together, these two parameters define the blacklisted PCIs – startIntraPci defines the lowest PCI in the range – rangeIntraPci defines the number of PCIs in the range • There can be 16 ranges in total PCI 1-4 are black listed
Soc Classification level 71 © Nokia Siemens Networks Blacklisting: IRFIM Inter-Frequency Cells • In the same way as for intra frequency cells , inter frequency cells can be blacklisted • The blacklisted PCIs are defined by the parameters IRFIM:startInterPci and IRFIM:rangeInterPci • Together, these two parameters define the blacklisted PCIs – startInterPci defines the lowest PCI in the range – rangeInterPci defines the number of PCIs in the range • There can be 16 ranges in total Presentation / Author / Date
Soc Classification level 72 © Nokia Siemens Networks Blacklisting for X2 or X2 and S1 HO Intra frequency and inter frequency • Intra frequency and inter frequency cells can be blacklisted for X2 or X2 and S1 HO under LNCEL object • Parameters involved: – blacklistTopo: • allEqual means only X2 and S1 HO are forbidden to that cell(s) • onlyX2 means cells are only blacklisted for X2 HO – freqEutra: 65536 means same frequency (i.e. intra frequency) – phyCellIdRange: how many PCIs – phyCellIdStart: first PCI in range Presentation / Author / Date
Soc Classification level 73 © Nokia Siemens Networks Blacklisting between an LTE cell and a WCDMA/GSM cell (RL30) • It is possible to blacklist a WCDMA neighbour cell (defined under LNADJW ) with LNCEL parameter cellblacklisted (under Related LNADJW instance list) Presentation / Author / Date • It is possible to blacklist a GSMC neighbour cell (defined under LNADJG) with LNCEL parameter cellblacklisted (under List of pointer to LNADJG instance)
Soc Classification level 74 © Nokia Siemens Networks Blacklisting X2 Handover towards another eNB RL30 • LNBTS: glbNbEnbIdX2LinkBlacklist is used to blacklist X2 handovers between eNBs in the list • The eNodeB does not establish or accept X2 connections to/from eNodeBs contained in the list • It is possible to have 64 lists (i.e. to blacklist relations between 64 eNodeBs from one eNodeB) Presentation / Author / Date
Soc Classification level 75 © Nokia Siemens Networks Blacklisting for HO between two LTE cells RL30 • LTE cell blacklisted to be HO target of another LTE cell • Related to ANR procedure and Optimization of neighbour relations. However operator can also manually blacklist a cell with LNREL: handoverAllowed if LNREL: nrcontrol is set to manual • Applies in addition to blackListTopo • If a cell is blacklisted for HO with blackListTopo (blacklistHoL in MOC LNCEL) then automatically is blacklisted for ANR procedure (LNREL: handoverAllowed is not considered) Presentation / Author / Date nrcontrol: neighbour relation control
Soc Classification level 76 © Nokia Siemens Networks Summary of blacklisting parameters Idle Mode: • Blacklisting from one LTE cell to a list of intra or inter frequency cells – IAFIM: intrFrBCList (intra frequency) – IRFIM: intFrBCList (inter frequency) Connected Mode: • Blacklisting for (X2 or X2&S1) HO between an LTE cell and intra/inter- frequency list of cells – LNCEL: blackListTopo (part of blackListHoL) • Blacklisting between an LTE cell and a WCDMA/GSM cell – LNCEL: cellblacklisted (WCDMA/GSM) • X2 blacklisted eNB Id: related to (RL30) ANR fully UE based – LNBTS: glbNbEnbIdX2LinkBlacklist • (RL30) LTE cell blacklisted to be HO target of another LTE cell. Applies in addition to blackListTopo – LNREL: handoverAllowed Presentation / Author / Date
Soc Classification level 77 © Nokia Siemens Networks Exercise • Scope: Familiarize with Site Manager, xml files and understand configuration aspects using real commissioning files: • In the following example of RL20 commissioning file: – Indicate to which frequencies /technologies we will have reselection and which one has the highest priority • In the following example of RL30 commissioning file: – Identify the sector configuration and RF module configuration (ANTL parameters) – Have neighbours been created manually or with ANR? Why? – Maybe create some UFFIM or IRFIM for certain frequency (if parameters defined before). A REDR is easier (parameter wise but file already has some) -> if UFFIM created now it could be reused (parameter values) for the KISS macro (list object) Presentation / Author / Date RL30_comm_file RL20_Comm_File It needs to be refined
Soc Classification level 78 © Nokia Siemens Networks Plan Creation Methods Roll outs Presentation / Author / Date
Soc Classification level 79 © Nokia Siemens Networks Plan Creation for Rollouts Introduction • Configuration Management (CM) deals with the creation of plans/configuration files (xml) required for the integration of the sites within a network • There are multiple methods to create such plan/configuration file. Each method is based on a different tool. Preferred method is base on the project characteristics: • Method 1: NetAct Configurator • Method 2: Daisy - LACE • Method 3: Plan Editor • Method 4: Databuild Creation Macro (internal macro) • Three areas need to be configured when creating a plan: – Radio Network Parameters (RNW) – Site Configuration Parameters (HW) – LTE BTS Transport Parameters (FTM) • Focus within this training is on the RNW and site configuration areas Presentation / Author / Date
Soc Classification level 80 © Nokia Siemens Networks Method 1: NetAct Configurator Overview • Tool: NetAct Configurator • Inputs: • Site Data file (XML or CSV input file) • It contains ‘site specific’ parameters i.e. those that need to planned/allocated separately for each site • One site specific parameter per column, parameters for one site per row • Import Profile (XML) • Only necessary if Site Data file is in CSV format • Maps the columns information of the CSV file into XML • Site Template • Output: • Plan to be provisioned to the network • Benefit: • Simple and fast • Drawback: • It is necessary to have on-line connection to NetAct Presentation / Author / Date
Soc Classification level 81 © Nokia Siemens Networks Method 1: NetAct OSS and NetAct Configurator • Plan is created with a combination of CM Operations Manager and CM Editor • CM Operations Manager: Import site data (start of plan creation), import of site templates and CM workflow • CM Editor: Edit site templates and site(s)/plan inputs Presentation / Author / Date • RL30 and RL25TD are supported from OSS 5.3 CD set 3 NetAct –NE Element Compatibility Matrix
Soc Classification level 82 © Nokia Siemens Networks Method 1: NetAct Configurator Process 1. Import in CM Operations Manager (part of NetAct Configurator) the input file i.e. the site data file • Planner decides which parameters to include in the input file. Those parameters should be the ones that need to be specific for each site and for which it is not possible to use a template. • Within the input file it is necessary to include the identifier to the site template to be used 2. Assign an import profile to the csv input file • Only required if the input file is in csv format. Not needed if the input file is already in xml format • The import profile is needed to create and xml file from the csv input file. 3. Apply a site template to our plan (or input file) • For those parameters not included in the input file, the values of the site template are used 4. Validate the plan and provision it. NOTE: Provisioning the plans is not part of Radio planning Presentation / Author / Date
Soc Classification level 83 © Nokia Siemens Networks Method 1: NetAct Configurator Input File • Example input file for RL20 (csv) with minimal set of parameters needed: • Each column contains one site-specific parameter and each row contains the site- specific parameters for one site • User Interface (UI) or Internal parameter values can be used • A unique Distinguished Name (dn) is needed for every object created in the CSV file. It uniquely identifies a Managed Object in the database. – The only site-specific id in the DN is the MRBTS/mrBtsId which must be equal to LNBTS/lnBtsId  Example DN for LNCEL of sector #1: PLMN-PLMN/MRBTS-9876/LNBTS- 9876/LNCEL-1 • More information in Plan Creation with NetAct CM.ppt: – https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D437258745 Presentation / Author / Date 3cells_site_Input file
Soc Classification level 84 © Nokia Siemens Networks Method 1: NetAct Configurator Import Profile and Site Template (RL20) Import Profile • Example import profile for the previous input file example: • Import profile is created manually in a text editor. It must contain the same inputs (MOC and site-specific parameters) defined in the site input file Site Template • It contains the parameters that don’t need to be planned for every site and can be assigned a pre-defined value • Two ways to create the site template: – Importing an existing template using CMO Manager (NetAct Configurator) – Create a site template from an existing site in the OSS database using CM Editor (part of Configurator) • Site template values can be browsed and modified with any text editor or in CM Editor • More information in Plan Creation with NetAct CM.ppt: – https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D437258745 Presentation / Author / Date 3cells_import profile MOC: Managed Object Class
Soc Classification level 85 © Nokia Siemens Networks Method 2: Daisy-LACE Overview • Tool: – Daisy (NSN internal tool) with HW license (free) – Plan Editor with SW license (.lf file) • Inputs: – CIQ (Customer Information Questionnaire) excel • Output: – XML file for each eNB or unique xml containing the actual plan • Benefit: – Off-line • Drawback: – Not always available in time: It depends on availability of PE database, CIQ creation/verification – It doesn’t support SITE object creation (needed for Optimizer and Auto configuration) Presentation / Author / Date
Soc Classification level 86 © Nokia Siemens Networks Method 2: Daisy-LACE Process (1/4) Preparation phase: • Download and install the latest Daisy: – https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/432861101 – An empty Plan Editor (PE) database and the valid CIQ file for that Daisy version is part of the package, within folder LACE/Input E.g. C:Program FilesNSNDAISYProjectsLTE_LACE_RL20WorkDirLACEInput • Request CIQ HW license by filling the form: – https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D434761332 • Fill the required parameters within the CIQ – https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D433717329 • RL30 CIQ preparation is ongoing. No CIQ support for LTE TDD Presentation / Author / Date Example CIQ RL20
Soc Classification level 87 © Nokia Siemens Networks Method 2: Daisy-LACE Process (2/4) Daisy Handling • As Daisy works for several technologies it is necessary to select the correct one with the Data Generation button Presentation / Author / Date • Daisy works in three simple steps: – Data generation: Generation of xml files from the CIQ excel – Data Upload into Plan Editor: upload of xml files into PE – Data export (generation of the xml plan): combination of CIQ and PE parameters
Soc Classification level 88 © Nokia Siemens Networks Method 2: Daisy-LACE Process (3/4) Daisy Handling (cont) •Data Generation : Uploading the CIQ • Validates the CIQ • Note: CIQ must be closed (not opened in excel) when importing it in Daisy •Data Upload: Import in Plan Editor -> Straight forward after uploading the CIQ • Input: xml files generated in the previous step. It is enough to point to the folder •Data Export: Export to xml using either Default LTE LNx.0 or Default OSS Presentation / Author / Date
Soc Classification level 89 © Nokia Siemens Networks Method 2: Daisy-LACE Process (4/4) Plan Validation • Once Daisy provides the plan it is recommended to validate it before provisioning • Two possible DAISY outputs depending on the export profile – 1) Default LTE LNx.0 – 2) Default OSS Default LTE LNx.0 • It generates an xml file for each eNB -> validation for each site can be done individually with BTS site Manager Default OSS • It generates one xml for NetAct Configurator containing all sites (i.e. the whole plan) Presentation / Author / Date
Soc Classification level 90 © Nokia Siemens Networks Method 3: Plan Editor Overview • Tool: – Plan Editor with SW license (.lf file) • Inputs: – Site Data file (csv) – Plan Editor templates • Output: – Either a Commissioning file per site (suitable for BTS SM) or OSS plan multiple sites depending on the export profile selected • Benefit: – Off-line tool and official NSN tool – For some people it is the best method to generate plans and track changes • Drawback: • Generation of templates and template sets may not be straight forward Presentation / Author / Date If time add something else….
Soc Classification level 91 © Nokia Siemens Networks Method 4: KISS Databuild Creation Macro Overview • Tool: – Excel macro • Inputs: – Excel with radio and transport parameters that need to be planned (those different for each site) – Template for certain release – BTS SM for file validation (optional) • Output: – Commissioning file to be provisioned Presentation / Author / Date • Benefit: – Flexibility to adapt the macro for different releases and different inputs – Mass validation of sites in BTS SM with just one click • Drawback: – None so far KISS: Keep it short and simple
Soc Classification level 92 © Nokia Siemens Networks Method 4: KISS Databuild Creation Macro Overview • The off-line excel macro can be used for rollouts (simultaneously creation of multiple commissioning files) • It is valid for any release (FDD and TDD) providing the right template is used • Idea behind the tool: • Macro works by replacing $parameter tags in the template for parameters defined in the input sheets • Tool and instructions can be downloaded from: • https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/437564713 Presentation / Author / Date
Soc Classification level 93 © Nokia Siemens Networks Presentation / Author / Date Method 4: KISS Databuild Creation Macro Generic Process • Overall procedure: 1. Template creation: Create a template file using Site Manager (from Golden SCF), or use an existing site as a template file 2. Template adaptation: In the template file, replace site-specific parameter with $parameter tags, such as ‘$pci1’ 3. KISS handling: Define $parameter tags in the KISS excel and the parameter values that should replace them, one site per excel row 4. Run macro: KISS replaces tags with the parameter values and produces a commissioning file per site 5. Run validation
Soc Classification level 94 © Nokia Siemens Networks Comparison of plan creation methods (1/2) Attribute Method 1: NetAct with LTE site templates Method 2: DAISY-LACE Input data format CSV or XML Excel: Customer Information Questionnaire (CIQ) Output data Site CM data in OSS database. Can be exported in XML format using CMO Manager eNB commissioning files (xml) or OSS database (xml) SW required NetAct OSS DAISY-LACE + Plan Editor Licensing Basic NetAct functionality License for DAISY-LACE (hw dongle), Plan Editor soft license (.lf file) On-line / Off-line On-line: connection to NetAct required to import data with CMO Manager and to apply site template Off-line Optimizer SITE object creation readiness in import Yes, allows creation of SITE object in the CSV import No, SITE object must be created afterwards in NetAct Site template data parameter customizability Yes, site template parameters can be freely customized No, input data is according to fixed input data format (CIQ), empty parameters replaced with PDDB defaults CIQ = Customer Information Questionnaire
Soc Classification level 95 © Nokia Siemens Networks Comparison of plan creation methods (2/2) Attribute Method 3: Plan Editor using template sets Method 4: KISS Databuild Creation Macro Tool Input data format CSV Excel Output data eNB commissioning files (xml) or OSS database (xml) eNB commissioning files (xml) SW required Plan Editor None specific. Excel Licensing Plan Editor soft license (.lf file) None. On-line / Off-line Off-line Off-lines Optimizer SITE object creation readiness in import No, SITE object must be created afterwards in NetAct No, SITE object must be created afterwards in NetAct Site template data parameter customizability Yes, site template parameters can be freely customized using PE template sets Yes, site template parameters can be freely customized CIQ = Customer Information Questionnaire
Soc Classification level 96 © Nokia Siemens Networks Plan Creation with KISS Macro Exercise INPUTS: • Excel file provides input data (CIQ) based on real project(s) for 5 sites • Template has been created with BTS Site Manager and modified to work with KISS • Basic KISS macro: https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D437598496 EXERCISE: Create and validate commissioning files for the sites included in the plan. Consider: • Site 1 and Site 3 cells must be barred (using the macro, cellbarred parameter) – Scope: Addition of new parameters in the basic macro • Commissioning files must contain the neighbours defined in CIQ_RL30 excel (AdjSites) – Scope: Addition of List objects in KISS Presentation / Author / Date CIQ_RL30 T_ln30_exercise_basic.xml Still to be refined:
Soc Classification level 97 © Nokia Siemens Networks Plan Creation with KISS Macro Exercise • Current exercise is more about tool handling than configuration (parameter decision) • It can complement the other exercises: 1. identifying Configuration details as MOC with BTS site manager and 2. configuring a bit of idle mode or connected mode parameters (optimization training exercises) • Necessary to find a balance between not giving too much processing already done to the people or too little. • If too much: exercise can be very simple • If too little: they can spend hours in ‘manual’ handling (i.e. modifying the template, input data into the KISS macro) • Giving CIQ is good in the sense they have an example for real network. On the other hand, it is unnecessary complicated (if follows Daisy format) and it will be difficult for people to locate parameters. Probably easier just to provide an excel with some parameters • Maybe we could add that people create and UFFIM previously defined (maybe in another exercise). -> Need to check parameter values for that exercise and test it with the tool. Presentation / Author / Date Still to be refined:
Soc Classification level 98 © Nokia Siemens Networks Useful Links
Soc Classification level 99 © Nokia Siemens Networks Useful Links (1/2) • Main Configuration Management (CM) and data fills folder in IMS: • https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/433416226 • NetAct Plan Editor can be downloaded from IMS (software folder) together with additional documentation (documentation folder): – https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/390002169 • BTS SM can be downloaded: • NOLS: https://online.portal.nokiasiemensnetworks.com/nolshome/homepage ( access required to NOLS and to download software) : Radio Network -> Base Stations -> Flexi Multiradio BTS LTE and Flexi Multiradio BTS TD-LTE • IMS: https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/433488673 Presentation / Author / Date
Soc Classification level 100 © Nokia Siemens Networks Useful Links (2/2) • Commissioning parameters and parameter changes per different releases from NOLS: • https://online.portal.nokiasiemensnetworks.com/pic/com/nsn/extranet/pic/controller/productinf oview/pivdocumentation.do?productId=urn:nsn.com:mxpdm:133-047488 • Useful for ‘troubleshooting’ errors in the plan validation due to parameter relations that can be found in that excel Presentation / Author / Date
Soc Classification level 101 © Nokia Siemens Networks Terminology and Databuild types Golden System Configuration File (SCF): • xml file with all parameters necessary to configure the system • Excluding the parameters that are ’vendor’ specific Vendor File: • NSN specific parameters: The ones that can not be modified/ hardcoded. E.g ulSeqHop Commissioning File: • File containing all the parameters in the SCF. It doesn’t show the vendor file parameters Databuilds (types): • CIQ: Customer Information Questionaire – Theoretically, minimum set of information, easy to fill by/with customer – Input for Daisy ( LACE Tool) – It can be used as the excel databuild • Excel databuild: Similar to RNC/MSS/MGW data builds – Should include all parameters that may require planning intervention (i.e. default value might need to be changed under certain circumstances) • Plan Editor full databuild: the full PE database, including all eNB parameters Presentation / Author / Date

More Related Content

PPT
06a_LTE mobility management v1_0.ppt
byssuser022794
 
PPT
01 lte radio_parameters_lte_overview_rl1
byMd.Akm Sahansha
 
PDF
Nokia LTE IP Planning Guide
byTarun Sharma - CCNA®, ITIL®, ETCP
 
PPT
305090798 04-basic-parameter-planning-rules-v1-1
byNitin George Thomas
 
PPT
63077585 idle-mode-parameter-optimization
byRanto Narivo Solofo RAFARALAHY
 
PDF
Chap 4. call processing and handover.eng
bysivakumar D
 
PDF
02_LTE_KPI architecture.pdf
byVahidZibakalam3
 
PDF
3GPP SON Series: Mobility Load Balancing (MLB)
by3G4G
 
06a_LTE mobility management v1_0.ppt
byssuser022794
 
01 lte radio_parameters_lte_overview_rl1
byMd.Akm Sahansha
 
Nokia LTE IP Planning Guide
byTarun Sharma - CCNA®, ITIL®, ETCP
 
305090798 04-basic-parameter-planning-rules-v1-1
byNitin George Thomas
 
63077585 idle-mode-parameter-optimization
byRanto Narivo Solofo RAFARALAHY
 
Chap 4. call processing and handover.eng
bysivakumar D
 
02_LTE_KPI architecture.pdf
byVahidZibakalam3
 
3GPP SON Series: Mobility Load Balancing (MLB)
by3G4G
 

What's hot

PPTX
422738668-LTE-Downlink-Throughput-Optimization-Based-on-Performance-Data [Rep...
bySudheeraIndrajith
 
PDF
LTE KPI and PI Formula_NOKIA.pdf
byVahidZibakalam3
 
PPT
3 g huawei-wcdma-rno-parameters-optimization
byshagahod
 
PDF
UMTS/LTE/EPC Call Flows for CSFB
byJustin MA (馬嘉昌)
 
PDF
2G Handover Details (Huawei)
byMd Mustafizur Rahman
 
PPTX
Volte troubleshooting
byJamil Awan
 
PDF
LTE Call Processing and Handover
bySitha Sok
 
PDF
Ericsson important optimization parameters
byPagla Knight
 
PPTX
395317358-LTE-Resource-Usage-Optimization.pptx
bySudheeraIndrajith
 
PPT
Lte irat-troubleshooting-guide
byDenmark Wilson
 
PDF
Hw lte rf-optimization-guide
bytharinduwije
 
PDF
Events in tems products
byTo Anh
 
PDF
LTE Air Interface
bySpiros Louvros
 
PPT
Huawei parameter strategy v1.4 1st dec
byKetut Widya
 
PDF
Kpi 2g troubleshootin
byAbd Yehia
 
PDF
224698998 moshell-commands
byAchmad Salsabil
 
PDF
GSM Channel Concept
byMd Mustafizur Rahman
 
PPT
GSM fundamentals (Huawei)
byShopnomoy Prantor
 
PPT
WCDMA Tems Parameters Investigation and Drive Testing
byS Mohib Naqvi
 
PDF
Cluster optimization procedure v1
byTerra Sacrifice
 
422738668-LTE-Downlink-Throughput-Optimization-Based-on-Performance-Data [Rep...
bySudheeraIndrajith
 
LTE KPI and PI Formula_NOKIA.pdf
byVahidZibakalam3
 
3 g huawei-wcdma-rno-parameters-optimization
byshagahod
 
UMTS/LTE/EPC Call Flows for CSFB
byJustin MA (馬嘉昌)
 
2G Handover Details (Huawei)
byMd Mustafizur Rahman
 
Volte troubleshooting
byJamil Awan
 
LTE Call Processing and Handover
bySitha Sok
 
Ericsson important optimization parameters
byPagla Knight
 
395317358-LTE-Resource-Usage-Optimization.pptx
bySudheeraIndrajith
 
Lte irat-troubleshooting-guide
byDenmark Wilson
 
Hw lte rf-optimization-guide
bytharinduwije
 
Events in tems products
byTo Anh
 
LTE Air Interface
bySpiros Louvros
 
Huawei parameter strategy v1.4 1st dec
byKetut Widya
 
Kpi 2g troubleshootin
byAbd Yehia
 
224698998 moshell-commands
byAchmad Salsabil
 
GSM Channel Concept
byMd Mustafizur Rahman
 
GSM fundamentals (Huawei)
byShopnomoy Prantor
 
WCDMA Tems Parameters Investigation and Drive Testing
byS Mohib Naqvi
 
Cluster optimization procedure v1
byTerra Sacrifice
 

Similar to Radio Network Design & Roll Out

PDF
Radio network overview
byMd Mustafizur Rahman
 
PPT
3 g rf_opt_process_ppt
byHatim100
 
PDF
3G Radio Network Planning
bytoha ardi nugraha
 
PPTX
3 g drive-test
byAniekhan
 
PPT
Concepts of 3GPP LTE.ppt
byStefan Oprea
 
PPT
3 g rf-opt-process.ppt
byMd.Akm Sahansha
 
PPTX
Drive test using tems investation 16.1
byMd Joynal Abaden
 
PPT
03 umts radio path and transmissionnew
bysivakumar D
 
PPTX
Drive Test Using Tems Investation 16
byMd Joynal Abaden
 
PPTX
04_SRAN17A_Commissioning and integration
byShammiPerera2
 
PPT
3G network planning overview radio network 2002
byjockestraphe
 
PDF
LTE-Training-With Basic Parameters and tecgnology
byPrakash226236
 
PDF
Iscit2007 keynote juergenschindler
byMuhammad Ali Basra
 
PDF
98780537 gsm-fundamentals
byAdzadogo Louis
 
PPTX
CMC notes Unit 5.pptx
byDRKSHASHIDHAR
 
DOCX
Parameters for drive test
byJakoba Fetindrainibe
 
PDF
3g tutorial
by9876012345
 
PPTX
46640814 3 g-drive-test
byAndri Wahyudi
 
PPS
3 g
byroopeshkkuttikol
 
PPT
Frequency_Planning.ppt
bymohammedalgmaty
 
Radio network overview
byMd Mustafizur Rahman
 
3 g rf_opt_process_ppt
byHatim100
 
3G Radio Network Planning
bytoha ardi nugraha
 
3 g drive-test
byAniekhan
 
Concepts of 3GPP LTE.ppt
byStefan Oprea
 
3 g rf-opt-process.ppt
byMd.Akm Sahansha
 
Drive test using tems investation 16.1
byMd Joynal Abaden
 
03 umts radio path and transmissionnew
bysivakumar D
 
Drive Test Using Tems Investation 16
byMd Joynal Abaden
 
04_SRAN17A_Commissioning and integration
byShammiPerera2
 
3G network planning overview radio network 2002
byjockestraphe
 
LTE-Training-With Basic Parameters and tecgnology
byPrakash226236
 
Iscit2007 keynote juergenschindler
byMuhammad Ali Basra
 
98780537 gsm-fundamentals
byAdzadogo Louis
 
CMC notes Unit 5.pptx
byDRKSHASHIDHAR
 
Parameters for drive test
byJakoba Fetindrainibe
 
3g tutorial
by9876012345
 
46640814 3 g-drive-test
byAndri Wahyudi
 
3 g
byroopeshkkuttikol
 
Frequency_Planning.ppt
bymohammedalgmaty
 

Recently uploaded

PDF
Internet_of_Things_IoT_for_Next_Generation_Smart_Systems_Utilizing.pdf
byRoshanSyed12
 
DOCX
Introduction to the World of Computers (Hardware & Software)
byALIABBAS ABASOV
 
PDF
Security Technologys: Access Control, Firewall, VPN
byShielaLasala
 
PDF
The year in review - MarvelClient in 2025
bypanagenda
 
PDF
Unlocking the Power of Salesforce Architecture: Frameworks for Effective Solu...
byvarsha30tiwari
 
PDF
Day 3 - Data and Application Security - 2nd Sight Lab Cloud Security Class
by2nd Sight Lab
 
PDF
Vibe Coding vs. Spec-Driven Development [Free Meetup]
byHaim Michael
 
PDF
Security Forum Sessions from Houston 2025 Event
byMark Simos
 
PDF
Unser Jahresrückblick – MarvelClient in 2025
bypanagenda
 
PDF
Day 5 - Red Team + Blue Team in the Cloud - 2nd Sight Lab Cloud Security Class
by2nd Sight Lab
 
PDF
Usage Control for Process Discovery through a Trusted Execution Environment
byValerioGoretti
 
PPTX
THIS IS CYBER SECURITY NOTES USED IN CLASS ON VARIOUS TOPICS USED IN CYBERSEC...
byMelissaGblinwon
 
PDF
Digit Expo 2025 - EICC Edinburgh 27th November
byRay Bugg
 
PDF
Our Digital Tribe_ Cultivating Connection and Growth in Our Slack Community 🌿...
bysanjeetmishra30
 
PPTX
Building Cyber Resilience for 2026: Best Practices for a Secure, AI-Driven Bu...
byYasir Naveed Riaz
 
PPTX
cybercrime in Information security .pptx
byismaeelsahib032
 
PPTX
AI's Impact on Cybersecurity - Challenges and Opportunities
byYasir Naveed Riaz
 
PDF
Six Shifts For 2026 (And The Next Six Years)
byDavid Armano
 
PPTX
Kanban India 2025 | Daksh Gupta | Modeling the Models, Generative AI & Kanban
byLeanKanbanIndia
 
PPTX
Data Privacy and Protection: Safeguarding Information in a Connected World
byYasir Naveed Riaz
 
Internet_of_Things_IoT_for_Next_Generation_Smart_Systems_Utilizing.pdf
byRoshanSyed12
 
Introduction to the World of Computers (Hardware & Software)
byALIABBAS ABASOV
 
Security Technologys: Access Control, Firewall, VPN
byShielaLasala
 
The year in review - MarvelClient in 2025
bypanagenda
 
Unlocking the Power of Salesforce Architecture: Frameworks for Effective Solu...
byvarsha30tiwari
 
Day 3 - Data and Application Security - 2nd Sight Lab Cloud Security Class
by2nd Sight Lab
 
Vibe Coding vs. Spec-Driven Development [Free Meetup]
byHaim Michael
 
Security Forum Sessions from Houston 2025 Event
byMark Simos
 
Unser Jahresrückblick – MarvelClient in 2025
bypanagenda
 
Day 5 - Red Team + Blue Team in the Cloud - 2nd Sight Lab Cloud Security Class
by2nd Sight Lab
 
Usage Control for Process Discovery through a Trusted Execution Environment
byValerioGoretti
 
THIS IS CYBER SECURITY NOTES USED IN CLASS ON VARIOUS TOPICS USED IN CYBERSEC...
byMelissaGblinwon
 
Digit Expo 2025 - EICC Edinburgh 27th November
byRay Bugg
 
Our Digital Tribe_ Cultivating Connection and Growth in Our Slack Community 🌿...
bysanjeetmishra30
 
Building Cyber Resilience for 2026: Best Practices for a Secure, AI-Driven Bu...
byYasir Naveed Riaz
 
cybercrime in Information security .pptx
byismaeelsahib032
 
AI's Impact on Cybersecurity - Challenges and Opportunities
byYasir Naveed Riaz
 
Six Shifts For 2026 (And The Next Six Years)
byDavid Armano
 
Kanban India 2025 | Daksh Gupta | Modeling the Models, Generative AI & Kanban
byLeanKanbanIndia
 
Data Privacy and Protection: Safeguarding Information in a Connected World
byYasir Naveed Riaz
 

Radio Network Design & Roll Out

  • 1.
    Soc Classification level 1© Nokia Siemens Networks Presentation / Author / Date Radio Network Design for Roll Outs Configuration Management
  • 2.
    Soc Classification level 2© Nokia Siemens Networks Contents • Parameter structure (MOC) and Site Configuration • Idle Mode Mobility Configuration • Connected Mode Mobility Configuration • Neighbours Configuration • S1 Handover Configuration • Blacklisting • Exercise • Plan Creation Methods • Exercise Presentation / Author / Date
  • 3.
    Soc Classification level 3© Nokia Siemens Networks Parameter structure (Managed Object Classes) and Site Configuration Presentation / Author / Date
  • 4.
    Soc Classification level 4© Nokia Siemens Networks Introduction • Parameters are organised into Managed Object Classes (MOC) that follow a hierarchical structure containing three main areas : – Radio Network Parameters (RNW) – Site Configuration Parameters (HW) – LTE BTS Transport Parameters (FTM) • Majority of MOCs are stable between releases but some of them can be added/removed between releases. Same applies for the parameters under each MOC. They can be found in NOLS Operating Documentation • Not all MOCs are mandatory (i.e. they don’t need to be configured) • This section is about configuring different MOCs based on the network characteristics needed when creating a site configuration file (also can be used as site template) Presentation / Author / Date Focus of the training
  • 5.
    Soc Classification level 5© Nokia Siemens Networks Managed Object Hierarchy (RL30) PLMN MRBTS ANTL BTSSCL LCELL LNBTS MHA RET RMOD SMOD FTM ADIPNO CTRLTS MTRACE GTPU MODRED LNADJ LNADJG LNADJW LNADLP LNCEL LNMME MODPR MOPR PRMNL SCTP LNADJL CDFIM GFIM IAFIM IRFIM LNHOG LNHOIF LNHOW LNREL REDRT UFFIM GNFL MORED AMRG CERTH ETHLK IPNO IPSECC SYNC UNIT TAC LTAC STPG PPTT OAMPRF IEIF IVIF QOS IPRT INTP IPRM IHCP BFD BFDGRP TOPIK TWAMP RNW Parameters FTM Parameters Site Configurati on Parameters
  • 6.
    Soc Classification level 8© Nokia Siemens Networks Parameter Configuration Parameter configuration can be divided into: • Site specific parameters: Those that need to be planned/allocated separately for each site • ‘Site template’ parameters: Those that can be assigned a value that is pre-defined in a template as they don’t vary across the sites of a network. They can be: • Operator specific: E.g. mnc, mcc, plmnId • ‘Default’ parameters • References for parameter configuration are: • PDDB: http://pddb.inside.nokiasiemensnetworks.com/pddb/ • PKDB: http://pkdb1.emea.nsn-net.net:8080/pkdbWebToolLTE/ • SCF: System Configuration File • Configuration Management IMS Folder: • https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/436539771 • As part of PKDB (link above) scenarios Presentation / Author / Date
  • 7.
    Soc Classification level 9© Nokia Siemens Networks System Configuration Files (SCF) Overview • Golden System Configuration Files (SCF) are xml files containing the basic MOCs and related parameters to create a commissioning file or a template for a site • Vendor specific (i.e. hidden parameters) are not part of the SCF • Contents of the SCF vary depending on the LTE variant (FDD or TDD) and on the different releases • Even within the same release, there are different versions of SCF with newer versions containing more features implemented in the meantime • Once P8 milestone for a Release has been reached the contents of the SCF are frozen. Recommendation is always to use the latest SCF available Presentation / Author / Date MOC: Managed Object Classes
  • 8.
    Soc Classification level 10© Nokia Siemens Networks System Configuration Files (SCF) Structure SCF can not be used directly as a template file for an eNB due to: • MOCs and instances need to be adapted for each case • Only 1 LNCEL object (normally, 3 LNCEL objects are required) • Only ANTL-1 to ANTL-6 are defined (normally, up to ANTL- 12 is required) • Some parameters, operator specific, haven’t got any value assigned: • They may not contain all MOCs required or MOCs that are not required (LNADJG, IRFIM…) Presentation / Author / Date MOCs defined in SCF for RL30
  • 9.
    Soc Classification level 11© Nokia Siemens Networks System Configuration Files Parameter values (SCF vs. PDDB) • Most default parameter values in PDDB should be aligned with SCF values after P8 milestone • Reasons why parameter values can be different: • SCF is focused on lab testing, low loaded trials and customer networks whereas PDDB values should be more generic. E.g. cell load dependent parameters • Other parameter values in SCF are the result of a workaround for some issue (network or UE) that may be removed in future release/SW-version • All cases of differences between PDDB default values and Golden SCF should be documented in the corresponding GMC scenario within the Parameter Knowledge Database (PKDB): Presentation / Author / Date RL30 RL20 RL25
  • 10.
    Soc Classification level 12© Nokia Siemens Networks Site Configuration RMOD and SMOD MOCs An starting point when creating a template or configuring a site is to define how many and which type of RF modules (RMOD) and System Modules (SMOD) will be used • RMOD object: • Type of RF module is specific to the frequency used • Amount of RF modules per site depends on the site configuration. E.g. 3 cells site with 2Tx MIMO 2 • Distributed case : 3 RF modules (1 RF module per cell) • ‘Normal configuration’: 2 RF modules ( to cover for the 3 cells) • SMOD object: • To define the type of system module (FSME) and the technology used (EUTRA) Presentation / Author / Date
  • 11.
    Soc Classification level 13© Nokia Siemens Networks Site Configuration Cells configuration and ANTL MOC • After RF module definition is necessary to define the cells per site: – How many cells – RF modules and antenna Lines used per cell – MIMO settings – Power of the RF module • Relation between antenna ports used and antenna lines may not be so intuitive • Parameters involved: • lcrId: ID of the Local Cell Resource ( i.e. cell/sector ID). Unique value in the eNB for each cell • antId: Identifies the specific antenna port in the Radio Module for the antenna line. Range and step: ANT1 (0), ANT2 (1), ANT3 (2), ANT4 (3), ANT5 (4), ANT6 (5) • antlId: Identifies the specific antenna line • rModId: Identifies the Radio Module Presentation / Author / Date
  • 12.
    Soc Classification level 14© Nokia Siemens Networks ANTL object 3 sector site • Common configuration where the 2 RF modules are situated next to the system module Presentation / Author / Date antId=0 (ANT1 in BTS SM) antId=2 (ANT3 in BTS SM) antId=4 (ANT5 in BTS SM)
  • 13.
    Soc Classification level 15© Nokia Siemens Networks ANTL object 3 sector site: BTS SM definition • For each Local cell (lcrId) it is required to define the antId used in each Radio Module, the MIMO settings and the carrier power Presentation / Author / Date
  • 14.
    Soc Classification level 16© Nokia Siemens Networks Defining ANTL object 3 sector site: xml file • In the xml file, there is a total of 12 ANTL objects Presentation / Author / Date • Parameter structure for the ANTL used (i.e. ANTL1,3,5,7,9,11) is the same as per ANTL-1 • Parameter structure for the ANTL not used (i.e. ANT2,4,6,8,10,12) is the same as per ANTL-2
  • 15.
    Soc Classification level 17© Nokia Siemens Networks Defining ANTL object 3 sector distributed site • 1RF module required per sector in order to have the 2x2 MIMO Presentation / Author / Date antId=0 (ANT1 in BTS SM) antId=2 (ANT3 in BTS SM)
  • 16.
    Soc Classification level 18© Nokia Siemens Networks ANTL object 3 sector distributed site: BTS SM definition • For each Local cell (lcrId) it is required to define the antId used in each Radio Module, the MIMO settings and the carrier power Presentation / Author / Date
  • 17.
    Soc Classification level 19© Nokia Siemens Networks Defining ARFCN Frequency Included in LNCEL MOC • It is enough to define the DL ARFCN frequency for each cell and the bandwidth. UL ARFCN is automatically calculated Presentation / Author / Date Downlink Uplink
  • 18.
    Soc Classification level 20© Nokia Siemens Networks Addition of New Objects not in SCF MHA, RET MOCs • It is possible to define new objects not in the original SCF like MHA, RET (Remote Electrical Tilt)… as BTS SM asks for the parameters required Presentation / Author / Date
  • 19.
    Soc Classification level 21© Nokia Siemens Networks Radio Network Configuration Parameters MRBTS, LNBTS MOCs • All radio related parameters are under MRBTS object Presentation / Author / Date Multiradio flexi BTS site Identifier ( MRBTS-ID) must be the same as the LNBTS-ID
  • 20.
    Soc Classification level 22© Nokia Siemens Networks Radio Network Configuration Parameters Errors • If working directly with SCF, LNBTS parameters give many errors (indicated by a ‘yellow triangle’) • Errors indicate missing mandatory parameters or parameters that cannot be validated as they are not recognised (i.e. those with ‘e.g.xxxx’ values in SCF) • 2 ways of solving it: • Open each MOC with an error and complete the mandatory parameters indicated by the yellow asterisk • Go through the list of errors (below). By clicking each of the errors BTS SM points the user to where the error is Presentation / Author / Date
  • 21.
    Soc Classification level 23© Nokia Siemens Networks LNBTS and LNCEL children objects • Which objects to add depend on each operator case • LNCEL child objects related to idle mode (cell reselection): IAFIM, IRFIM, UFFIM, GFIM • LNCEL child objects related to connected mode mobility: LNHOIF,LNHOW,LNHOG,LNREL,REDRT • LNBTS child objects related to connected mode mobility: ADIPNO, LNADJ, LNADJG, LNADJW Presentation / Author / Date
  • 22.
    Soc Classification level 24© Nokia Siemens Networks Idle Mode Mobility Configuration Presentation / Author / Date
  • 23.
    Soc Classification level 25© Nokia Siemens Networks System Information Blocks (SIBs) • UE reads the system information within Idle mode to acquire parameters needed to complete cell selection and reselection • System information is broadcast using a Master Information Block (MIB) and a series or System Information Blocks(SIB) • SIB1..3 are mandatory • SIB 4,5,6,7,8 are optional and are defined within LNCEL Presentation / Author / Date More info: TS36.331
  • 24.
    Soc Classification level 26© Nokia Siemens Networks siXMappingInfo Parameter LNCEL • LNCEL/siXMappingInfo parameter indicates which System Information Block is contained in the SI-X message. Values: SIB4(2), SIB5(3), SIB6(4), SIB7(5), SIB8 (6), notUsed (18) Presentation / Author / Date SI: System Information MOC: Managed Object Class • If ‘SIB4’ is defined in any LNCEL/siXMappingInfo where X={4,5,6,7,8} then the MOC IAFIM (iafimId) object must be defined • If 'SIB5' is defined in LNCEL, then MOC IRFIM (irfimId) needs to be created • If 'SIB6' is defined in LNCEL, then MOC UFFIM (uffimId) needs to be created • If 'SIB7‘ is defined in LNCEL, then MOC GFIM (gfimId) needs to be created • If 'SIB8‘ is defined in LNCEL, them MOC CDFIM (cdfimId) needs to be created • Example where only si4MappingInfo is configured indicating that SI-4 carries the SIB4 information:
  • 25.
    Soc Classification level 27© Nokia Siemens Networks SIB3 LNCEL • SIB3 carries the cell reselection parameters (serving cell information) Presentation / Author / Date • All these parameters are part of LNCEL object
  • 26.
    Soc Classification level 28© Nokia Siemens Networks SIB4 and IAFIM (1/2) • IAFIM parameters are broadcasted in SIB4 (neighbour cell information) Presentation / Author / Date • SIB4 contents are optional! • Intra Frequency Neighbours plus offsets • Intra Frequency Blacklisted Cells • CSG reserved cells i.e. for Home eNB -> not implemented CSG: Closed Subscribed Group
  • 27.
    Soc Classification level 29© Nokia Siemens Networks SIB4 and IAFIM (2/2) • IAFIM only needs to be created to give some special cell reselection offset (other than 0) to certain neighbour cells or to blacklist cells Practice: • Recommendation is to create a ‘dummy’ SIB4 as it is required for certain terminals e.g. Huawei LTE-USB sticks otherwise they crash • If IAFIM object is created them either blacklisted cells OR neighbour cells need to be defined – It is enough to configure a ‘dummy’ PCI in IAFIM – SIB4 periodicity in this case can also be longer • Presentation / Author / Date Theory: • All parameters in IAFIM are optional i.e. – No need to define intra-frequency idle mode neighbours – UE does not need SIB4 as it evaluates the available found neighbour cells + any additional cells defined in SIB4 if configured
  • 28.
    Soc Classification level 30© Nokia Siemens Networks Intra frequency cell reselection Practical Experience • qOffsetCell (the offset for the neighbouring cells) is in the IAFIM object and has to be defined separately for each neighbour relation (defined by the neighbours’ PCI). • Issue: It is not convenient to maintain. E.g. If creating a new PCI plan it is also necessary to change the PCIs in all the IAFIM objects • Solution: To ”move” all the offset to the qHyst (the offset for the serving cell) • E.g. instead of defining qHyst = 1dB and qOffsetCell = 2 dB to change qHyst to 3 dB and qOffsetCell to 0 (or don’t define the IAFIM at all)
  • 29.
    Soc Classification level 31© Nokia Siemens Networks Intra frequency cell reselection Practical Experience: Example • In the Telia Denmark network: – LNCEL:qHyst was set to 1 dB – IAFIM:qOffsetCell was set to 2dB, only defined for intra-site neighbours • This meant: – when reselecting to intra-site neighbours: total hysteresis was 3 dB (2+1) – When reselecting to non intra-site neighbours: total hysteresis was 1 dB (as no qOffsetCell was defined for the other neighbours) – 1 dB of hysteresis is too little leading to many cell reselections List only contains offset for the two intra site neighbours
  • 30.
    Soc Classification level 32© Nokia Siemens Networks Intra frequency cell reselection Idle mode PCI plot Before parameter change, cell reselections happening too often After parameter change, less ping pong between cells
  • 31.
    Soc Classification level 33© Nokia Siemens Networks IRFIM object SIB5: Inter frequency cell reselection • Idle mode mobility between two different LTE frequency layers, e.g. LTE 2600MHz for capacity sites and LTE 800MHz for coverage sites • IRFIM parameters are broadcasted in the SIB5 IRFIM object
  • 32.
    Soc Classification level 34© Nokia Siemens Networks UFFIM object SIB6: Inter RAT cell reselection • SIB6 and UFFIM with priorities and reselection thresholds towards 3 different WCDMA carriers Presentation / Author / Date
  • 33.
    Soc Classification level 35© Nokia Siemens Networks Inter RAT cell reselection Settings on WCDMA side (1/2) • ‘RAN2067 LTE interworking feature’ needs to be activated • Software needs to be appropriate e.g. WBTS SW BTS WN6.0 PP2.03 and activated on all WCDMA sites • ‘LTE Cell Reselection in WCEL needs to be enabled • RNC setting for SIB19 Presentation / Author / Date
  • 34.
    Soc Classification level 36© Nokia Siemens Networks17 May 201636 • ADJL configuration Inter RAT cell reselection Settings on WCDMA Side (2/2)
  • 35.
    Soc Classification level 37© Nokia Siemens Networks GFIM object LTE to GSM reselection • SIB7 needs to be activated • Mandatory parameter: GNFL/bandInd • It distinguishes between GERAN frequency bands if ARFCN values are associated with either GSM1800 or GSM1900. Values: gsm1800 (0) or gsm1900 (1) • If other ARFCN bands then the parameter although mandatory is not relevant • E.g. GNFL/gerArfcnVal = 1-124 (i.e. GSM900 frequencies) then bandInd can be either 0 or 1 Presentation / Author / Date
  • 36.
    Soc Classification level 38© Nokia Siemens Networks Connected Mode Mobility Configuration Presentation / Author / Date
  • 37.
    Soc Classification level 39© Nokia Siemens Networks Intra-Frequency Handovers • All parameters related with intra-frequency handover are under the LNCEL object: – These are the A3 and A5 (offsets, report intervals, time to trigger) – Parameters to enable the A3 and A5 handovers: enableBetterCellHo and enableCovHo – All thresholds referred to the serving cell: Threshold1, Threshold2/2a, Threshold3/3a, Threshold4 • Intra cell reselection parameters are also under LNCEL Presentation / Author / Date
  • 38.
    Soc Classification level 40© Nokia Siemens Networks LNHOIF Inter-Frequency HO • LNBTS:actIfHo must be enabled • Inter-frequency HO is activated on site level • Need to create a LNHOIF object per cell defining the parameters that will be used in the Measurement Configuration message and all the thresholds for A3/A5 event • Need to define the LNCEL parameters regarding threshold2/2a to activate/deactivate inter- frequency measurements • Inter-frequency HO parameters: Presentation / Author / Date Inter-Frequency Parameters
  • 39.
    Soc Classification level 41© Nokia Siemens Networks LNHOW, LNAJDW (RL30) IRAT HO to WCDMA Presentation / Author / Date • LNADJW [LNBTS]: Defines WCDMA neighboring cell(s) • LNHOW [LNCEL]: For each predefined EUTRA (utraCarrierFreq) defines event B2 related parameters • New parameters in already existing objects LNCEL and LNBTS are introduced
  • 40.
    Soc Classification level 42© Nokia Siemens Networks IRAT to WCDMA (RL30) LNBTS Configuration • LNBTS/LNADJW to define candidate 3G neighbor cell information for handover • Identifier 0 originally a bug • LNCEL/Related LNADJW instance list needs to be created with “WCDMA Cell Index ID” according to 3G neighbor lists need for that LTE cell. Create per 3G neighbor cells • actHOtoWcdma enables the feature Handover from LTE to WCDMA LNADJW-x = LNADJW: lnAdjWIndex
  • 41.
    Soc Classification level 43© Nokia Siemens Networks IRAT to WCDMA LNCEL • LNCEL/LNHOW needs to be created per 3G neighbor frequency • One LNHOW needed per frequency • LNCEL/UFFIM needs to be created per 3G neighbor frequency for cell reselection
  • 42.
    Soc Classification level 44© Nokia Siemens Networks LNHOG, LNADJG (RL30) eNACC to GSM • LNHOG: Information about NACC thresholds and timers for predefined set of ARFCNs defined by the parameter arfcnValueListGERAN • LNADJG:GSM cell considered as neighbouring GSM cell by LNCEL when its lnAdjGId parameter is listed on GSM Neighbouring Cell Information LNCEL:adjGInf parameter • New parameters in already existing objects LNBTS, LNCEL are introduced Presentation / Author / Date
  • 43.
    Soc Classification level 45© Nokia Siemens Networks CS Fallback to UTRAN (1/2) LNBTS, LNCEL, UFFIM, GFIM • CS fallback needs to be enabled via LNBTS:actCSFBRedir • Redirection technologies (WCDMA or GSM) need to be configured: UFFIM for WCDMA and GFIM for GSM • Activation of SIB6 for WCDMA and SIB7 for GSM (within LNCEL) Screenshots for WCDMA case
  • 44.
    Soc Classification level 46© Nokia Siemens Networks CS Fallback to UTRAN (2/2) REDRT • Necessary to create the REDRT object indicating the RAT for redirection and the priority for CS fallback with redirection • REDRT object also needs to be created for RRC Connection Release with Redirect (Threshold4) • One RDRT object is created per RAT frequency/band indicator
  • 45.
    Soc Classification level 47© Nokia Siemens Networks Presentation / Author / Date S1 Handover Configuration
  • 46.
    Soc Classification level 48© Nokia Siemens Networks Intra-LTE handover via S1 Parameter settings up to RL 20 1/2 • S1 handover doesn’t seem to be enabled in live networks but it is normally tested to ensure the proper configuration and functioning • Following MOC have to be adapted/created for setting up S1-based HOs: 1. The S1 handover feature needs to be enabled in LNBTS by: <p name="actLTES1Ho">true</p> 2. If the target eNB is able to perform X2-based handovers the target cell has to be blacklisted for X2 handover. For functionality testing of S1 HO, the X2 neighbour cell needs to be blacklisted: LNCEL object: <list name="blacklistHoL"> <item> <p name="blacklistTopo">onlyX2</p> <p name="freqEutra">65536</p> <p name="phyCellIdRange">n8</p> <p name="phyCellIdStart">pci</p> </item> </list>
  • 47.
    Soc Classification level 49© Nokia Siemens Networks Intra-LTE handover via S1 Parameter settings up to RL20 2/2 3. LNADLP (Target cell for S1 Handover) needs to be created per S1 neighbour cell LNBTS object: <managedObject class="LNADLP" distName="LNBTS-1001/LNADLP-1" operation="create“ <list name="adjBcPlmnIdOp"> <item> <p name="adjBcMccOp">MCC</p> <p name="adjBcMncOp">MNC</p> <p name="adjBcMncLenOp">length</p> <…> <p name="adjEarfcnOp">ARFCN</p> <p name="adjPhyCellIdOp">pci</p> <p name="adjTacOp">tac</p> <p name="lnAdlpId">0</p> </managedObject> • Note: On RL30, LNADLP object has been removed.
  • 48.
    Soc Classification level 50© Nokia Siemens Networks Intra-LTE handover via S1 Parameter settings RL30 • In RL30 the object LNADLP is removed • With feature LTE782 (ANR Fully UE based) in place there is not need for the object LNADLP:  A part of the procedure for LTE782 is the configuration of the X2 interface. After X2 successfully established source and target eNBs exchange configuration information necessary to fill in MOCs LNADJ and LNADJL  Until X2 link is successfully setup, cells being already defined in LNADJL can be regarded as targets for S1 HO (if feature is enabled) • To configure a pure S1 HO target cell: – Parameter LNADJ/cPlaneIpAddr must be left empty and… – LNADJ/cPlaneIpAddrCtrl must be set to: enbControlled • To prohibit X2 connection establishment, the neighbour eNB needs to be blacklisted via LNBTS/glbNbEnbIdX2LinkBlacklist Presentation / Author / Date
  • 49.
    Soc Classification level 51© Nokia Siemens Networks Summary of blacklisting parameters Connected Mode: • Blacklisting for (X2 or X2&S1) HO between an LTE cell and intra/inter- frequency list of cells • LNCEL: blackListTopo (part of blackListHoL) • Blacklisting between an LTE cell and a WCDMA/GSM cell • LNCEL: cellblacklisted (WCDMA/GSM) • X2 blacklisted eNB Id: related to (RL30) ANR fully UE based • LNBTS: glbNbEnbIdX2LinkBlacklist • (RL30) LTE cell blacklisted to be HO target of another LTE cell. Applies in addition to blackListTopo • LNREL: handoverAllowed Presentation / Author / Date
  • 50.
    Soc Classification level 52© Nokia Siemens Networks Neighbours Configuration
  • 51.
    Soc Classification level 53© Nokia Siemens Networks Contents • Neighbours configuration in RL20/RL15TD • Manual Definition • SON (ANR) • Summary • Neighbours configuration in RL30/RL25TD • Manual definition • SON (ANR) • Summary • Differences in neighbour definitions between RL20 and RL30 Presentation / Author / Date
  • 52.
    Soc Classification level 54© Nokia Siemens Networks Neighbours configuration in RL20/RL15TD Manual definition (no ANR) • Neighbours are manually defined via the C-plane IP@ of the adjacent eNodeB(s) • Defined in MOC ADIPNO within the adjEnbIpAddressMap via parameter adjEnbCPlaneIpAddress • Once the source eNB knows the IP@ of the target eNBs it establishes the X2 connections that allow for: • Automatic derivation of all necessary neighbour site (MOC LNADJ) and neighbour cells (MOC LNADJL) information • Automatic creation and population of neighbour cell information list (in MOC LNCEL) with all cells of the parent eNB and all cells for which the parent eNB has received configuration information from neighbour eNB Presentation / Author / Date
  • 53.
    Soc Classification level 55© Nokia Siemens Networks ADIPNO MOC (RL20) ADjacent IP NOde • It is enough to define the neighbour IP@ (AdjEnbCPlaneIpAddress) • Additional parameters in the ADIPNO object and existing values of adjMacroEnbId, adjMcc, adjMnc and adjMncLenght will be updated once that file is uploaded into the eNB (i.e. during the X2 setup) Presentation / Author / Date SCF original ADIPNO object… ADIPNO object after site integration
  • 54.
    Soc Classification level 56© Nokia Siemens Networks ADIPNO object (RL20) Presentation / Author / Date Defines the list of neighbours (enough to configure the AdjEnbCPlaneIpAddress) After site integration objects LNADJ and LNADJL are automatically created:
  • 55.
    Soc Classification level 57© Nokia Siemens Networks Neighbours configuration in RL20/RL15TD ANR definition • Feature LTE492: ANR support for LTE with OAM • No need for manual pre-planning of eNB adjacencies for X2 connection setup • NetAct generated PCI/RF/IP@ mapping tables for neighbour site relations are downloaded to eNB during auto-configuration • For each unknown adjacent cell, eNB searches the PCI/RF/IP@ look up table (stored in MOC LNBTS under pciIpAdrMap) to determine the IP@ needed for the X2 establishment towards eNB being a parent of unknown cell • After X2 connection is successfully established, source and target eNBs exchange configuration information necessary to fill in MOCs LNADJ and LNADJL and to add adjacent cells to neighbour cell information list in MOC LNCEL (attribute adjCellInfoL) same as in the previous case Presentation / Author / Date pciIpAdrMap only exists when neighbours are created with NetAct
  • 56.
    Soc Classification level 58© Nokia Siemens Networks Common information RL20 • MOCs LNADJ and LNADJL as well as parameter adjCellInfoL (in MOC LNCEL) are not modifiable for operator – that are just read only (in NetAct and BTS SM) Presentation / Author / Date • MOC LNADLP: (ADjacent LTE cell Plan based) • Contains target cells for S1-based HO that must be created by operator as they can’t automatically be created by eNB • A cell may be target cell for S1- and X2-HO. In that case the represented by two objects: • one LNADJL object for the X2-HO target • one LNADLP object for the S1-HO target • parameter lnAdlpInf provides a reference to the LNADLP object if the cell is configured to be a S1-HO target too
  • 57.
    Soc Classification level 59© Nokia Siemens Networks Summary RL20 • Difference between using SON ANR features or not only affects how the neighbour are defined: • SON (LTE 492:ANR with OAM extension) neighbours are defined with NetAct • Manual: neighbours are defined as a list of IP addresses adjEnbCPlaneIpAddress in the ADIPNO:adjEnbIpAddressMap • Once the IP@ of the neighbour site is available the updates in the involved MOC are automatic ( LNADJ, LNADJL, LNREL) after X2 setup Presentation / Author / Date
  • 58.
    Soc Classification level 60© Nokia Siemens Networks Neighbours configuration in RL30/RL25TD LTE782: ANR Fully UE based (3GPP) • eNB requests UE to report the ECGI of unknown cells reported in the measurement report • UE must support decoding and delivery of ECGI on request coming from eNB • Derived ECGI is used as input to an IP@ resolution procedure over S1 IF • eNB retrieves, with the help of MME, the C-plane IP@ needed to setup X2 connection towards the neighbour eNB parenting the UE-reported cells • Once IP@ is known then X2 connection to eNB hosting the neighbour cell can be established Presentation / Author / Date • No need for pre-defined PCI/RF/IP@ mapping tables (no need for NetAct)
  • 59.
    Soc Classification level 61© Nokia Siemens Networks Neighbours configuration in RL30/RL25TD LTE782: ANR Fully UE based (3GPP) • When X2 connection is established, source and target eNBs exchange configuration information necessary to fill in MOCs LNADJ and LNADJL • Bidirectional neighbour cells configuration data exchange • eNB knows all cells of the neighbouring eNB by PCI and IP address • LNADJL is created for all cells belonging to the peer eNB (not only for the unknown cell that triggered the procedure) • ANR is not triggered again when UE reports PCI of those not yet discovered cells • eNB creates the LNREL for the newly discovered cell (if this LNREL has not been created manually yet) • MOC LNREL (neighbour relations) is created by the eNB only for those cells that have been included in the UE measurement report received in given cell
  • 60.
    Soc Classification level 62© Nokia Siemens Networks Neighbours configuration in RL30/RL25TD LTE782: ANR Fully UE based (3GPP) • ANR feature implies the definition of new parameters in LNBTS and LNCEL MOCs necessary for the ECGI derivation and for the detection of unknown cells (active detection) • Parameters involved an additional information of the feature can be found in: • https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D437011923 Presentation / Author / Date
  • 61.
    Soc Classification level 63© Nokia Siemens Networks Neighbours configuration in RL30/RL25TD Manual definition (no ANR) • Neighbours are defined with the parameter cPlanIpAddr (MOC LNADJ) • As in the ANR case, once the eNB has the IP@ of the eNB’s hosting the neighbour cells, it automatically attempts the setup of the X2 connection and if successful, it automatically creates the corresponding LNADJL and complements the information in LNADJ • The creation of corresponding LNREL is triggered automatically after reception of a measurement report from the UE containing that cell
  • 62.
    Soc Classification level 64© Nokia Siemens Networks RL30 Summary (1/2) • In RL30 neighbours can be created manually via LNADJ: cPlanIpAddr or automatically by the eNB • Once IP address of neighbour site is detected and X2 connection is successful the eNB automatically creates the corresponding LNADJL and complements the information in LNADJ • LNADJ and LNADJL can be created also manually (in RL20 only automatic creation). Cases: • To blacklist cells, configure cells for pure S1 HO (via LNREL) • If LNADJ, LNADJL are created manually (via plan) the lowest available IDs should be used ( 0, 1…) to avoid ID conflicts in case with the automatic case as eNB uses the highest free LNADJ/LNADJL/LNREL instance ID in automatic creation procedure • LNADJ and LNADJL: can be modified or deleted via plan file Presentation / Author / Date
  • 63.
    Soc Classification level 65© Nokia Siemens Networks RL30 Summary (2/2)  LNREL object can also be created manually for blacklisting, define S1-HO or define cell specific offsets  LNREL objects are created by eNB if corresponding LNADJL object already exist and certain PCI is reported by UE as a result of A3 or A5 event • LNREL objects remain after deleting the LNADJL. The relation becomes invalid for HO but still is considered for blacklisting LNBTS LNCELLNADJ LNADJL LNREL LNREL: Relation between the parent cell LNCEL and one LNADJL cell
  • 64.
    Soc Classification level 66© Nokia Siemens Networks LNADJ, LNADJL and LNREL Relations LNREL: • New MOC in RL30 mainly related with ANR and Optimization of neigh relations • LNREL: cell to cell neighbour relationship between parent LNCEL and another LTE cell identified in LNADJL with ecgiAdjEnbId and ecgiLcrId • LNREL provides additional information on the neighbour relationship defined in LNADJL: • Definition of cell individual offsets • Blacklisting Presentation / Author / Date LNBTS LNCELLNADJ LNADJL LNREL LNADJ: neighbour site of parent LNBTS • Site identified by cplanIpAddr and adjEnbId that is the lnBtsId of the neighbour site LNADJL: specifies the cells belonging to LNADJ site that have a neighbour relationship with the parent eNB cells (LNCEL-x) • Cells identified via: – ecgiLcrId – ecgiAdjEnbId – phyCellId (not the EutraCelId)
  • 65.
    Soc Classification level 67© Nokia Siemens Networks Differences in neighbour definitions Between RL20/RL30 • In RL30 neighbour site IP@ are not defined anymore in ADIPNO MOC but in LNADJ MOC • LNADPL MOC (to define S1-HO relations) disappears • Until X2 link is successfully setup, cells being already defined in LNADJL can be regarded as targets for S1 HO (if feature is enabled) • New MOC: LNCEL/LNREL for neighbour relations containing information previously part of LNCEL (adjacent cell info List) • ANR feature in RL20 supports also intra and inter frequency neighbours. ANR feature in RL30 only supports intra frequency neighbours
  • 66.
    Soc Classification level 68© Nokia Siemens Networks LNADJL (1..LNADJL (1..66):):  lnAdjlIdlnAdjlId  lnAdlpInflnAdlpInf  phyCellIdphyCellId  adjEutraCelIdadjEutraCelId  ecgiPlmnIdecgiPlmnId  ecgiAdjEnbIdecgiAdjEnbId  ecgiLcrIdecgiLcrId  sourceOfDatasourceOfData  validityOfDatavalidityOfData  …… ANR – Intra-LTE, Intra-frequency – Fully UE based (LTE782) Feature details Neighbour relations database structure in RL30Neighbour relations database structure in RL30 LNBTS (1..1) lnBtsId, …, actUeBasedAnrIntraFreqLteactUeBasedAnrIntraFreqLte,, glbNbEnbIdX2LinkBlacklistglbNbEnbIdX2LinkBlacklist, pciIpAdrMap (dlEarfcn, ipAdr, pci, eNbId)*pciIpAdrMap (dlEarfcn, ipAdr, pci, eNbId)*, … … LNADJG(0..32)LNADJG(0..32) LNADJW(0..32)LNADJW(0..32) LNADJ (0..LNADJ (0..6464):):  lnAdjIdlnAdjId  adjEnbIdadjEnbId  plmnIdplmnId  ……  cPlaneIpAddrcPlaneIpAddr  cPlaneIpAddCtrlcPlaneIpAddCtrl  x2LinkStatusx2LinkStatus LNADLP (0..32):LNADLP (0..32):  lnAdlpIdlnAdlpId  adjPhyCellIdOpadjPhyCellIdOp  adjEgciOpadjEgciOp …… * LTE492 specific* LTE492 specific LNRELLNREL (0..389):(0..389):  lnRelIdlnRelId  ecgiAdjEnbIdecgiAdjEnbId  ecgiLcrIdecgiLcrId  ecgiPlmnIdecgiPlmnId  …… LNCEL:LNCEL:  lnCelIdlnCelId  adjCelInfoLadjCelInfoL eutraCelId_1eutraCelId_1 …… eutraCelId_130eutraCelId_130  phyCellIdphyCellId  eutraCelIdeutraCelId  lcrIdlcrId  adjWInfListadjWInfList  adjGInfListadjGInfList  anrThresNbCellanrThresNbCell  drxProfile101drxProfile101  nLTEIntraNeighbnLTEIntraNeighb oursours  …… LNCEL:LNCEL:  lnCelIdlnCelId  adjCelInfoLadjCelInfoL eutraCelId_1eutraCelId_1 …… eutraCelId_130eutraCelId_130  phyCellIdphyCellId  eutraCelIdeutraCelId  lcrIdlcrId  adjGInfListadjGInfList  adjWInfListadjWInfList  anrThresNbCellanrThresNbCell  drxProfile101drxProfile101  nLTEIntraNeighbnLTEIntraNeighb oursours  …… 1…66 LNRELLNREL (0..389):(0..389):  lnRelIdlnRelId  ecgiAdjEnbIdecgiAdjEnbId  ecgiLcrIdecgiLcrId  ecgiPlmnIdecgiPlmnId  …… Presentation m ode only!!! Presentation m ode only!!! ADIPNO (1..1):ADIPNO (1..1):  AdIpNoIdAdIpNoId  adjEnbIpAddressMapadjEnbIpAddressMap  ……
  • 67.
    Soc Classification level 69© Nokia Siemens Networks Parameters for Blacklisting
  • 68.
    Soc Classification level 70© Nokia Siemens Networks Blacklisting: IAFIM Intra-Frequency cells • If an operator wants to prohibit UEs to camp on certain cells, these cells can be blacklisted • The blacklisted PCIs are defined by the parameters IAFIM:startIntraPci and IAFIM:rangeIntraPci • Together, these two parameters define the blacklisted PCIs – startIntraPci defines the lowest PCI in the range – rangeIntraPci defines the number of PCIs in the range • There can be 16 ranges in total PCI 1-4 are black listed
  • 69.
    Soc Classification level 71© Nokia Siemens Networks Blacklisting: IRFIM Inter-Frequency Cells • In the same way as for intra frequency cells , inter frequency cells can be blacklisted • The blacklisted PCIs are defined by the parameters IRFIM:startInterPci and IRFIM:rangeInterPci • Together, these two parameters define the blacklisted PCIs – startInterPci defines the lowest PCI in the range – rangeInterPci defines the number of PCIs in the range • There can be 16 ranges in total Presentation / Author / Date
  • 70.
    Soc Classification level 72© Nokia Siemens Networks Blacklisting for X2 or X2 and S1 HO Intra frequency and inter frequency • Intra frequency and inter frequency cells can be blacklisted for X2 or X2 and S1 HO under LNCEL object • Parameters involved: – blacklistTopo: • allEqual means only X2 and S1 HO are forbidden to that cell(s) • onlyX2 means cells are only blacklisted for X2 HO – freqEutra: 65536 means same frequency (i.e. intra frequency) – phyCellIdRange: how many PCIs – phyCellIdStart: first PCI in range Presentation / Author / Date
  • 71.
    Soc Classification level 73© Nokia Siemens Networks Blacklisting between an LTE cell and a WCDMA/GSM cell (RL30) • It is possible to blacklist a WCDMA neighbour cell (defined under LNADJW ) with LNCEL parameter cellblacklisted (under Related LNADJW instance list) Presentation / Author / Date • It is possible to blacklist a GSMC neighbour cell (defined under LNADJG) with LNCEL parameter cellblacklisted (under List of pointer to LNADJG instance)
  • 72.
    Soc Classification level 74© Nokia Siemens Networks Blacklisting X2 Handover towards another eNB RL30 • LNBTS: glbNbEnbIdX2LinkBlacklist is used to blacklist X2 handovers between eNBs in the list • The eNodeB does not establish or accept X2 connections to/from eNodeBs contained in the list • It is possible to have 64 lists (i.e. to blacklist relations between 64 eNodeBs from one eNodeB) Presentation / Author / Date
  • 73.
    Soc Classification level 75© Nokia Siemens Networks Blacklisting for HO between two LTE cells RL30 • LTE cell blacklisted to be HO target of another LTE cell • Related to ANR procedure and Optimization of neighbour relations. However operator can also manually blacklist a cell with LNREL: handoverAllowed if LNREL: nrcontrol is set to manual • Applies in addition to blackListTopo • If a cell is blacklisted for HO with blackListTopo (blacklistHoL in MOC LNCEL) then automatically is blacklisted for ANR procedure (LNREL: handoverAllowed is not considered) Presentation / Author / Date nrcontrol: neighbour relation control
  • 74.
    Soc Classification level 76© Nokia Siemens Networks Summary of blacklisting parameters Idle Mode: • Blacklisting from one LTE cell to a list of intra or inter frequency cells – IAFIM: intrFrBCList (intra frequency) – IRFIM: intFrBCList (inter frequency) Connected Mode: • Blacklisting for (X2 or X2&S1) HO between an LTE cell and intra/inter- frequency list of cells – LNCEL: blackListTopo (part of blackListHoL) • Blacklisting between an LTE cell and a WCDMA/GSM cell – LNCEL: cellblacklisted (WCDMA/GSM) • X2 blacklisted eNB Id: related to (RL30) ANR fully UE based – LNBTS: glbNbEnbIdX2LinkBlacklist • (RL30) LTE cell blacklisted to be HO target of another LTE cell. Applies in addition to blackListTopo – LNREL: handoverAllowed Presentation / Author / Date
  • 75.
    Soc Classification level 77© Nokia Siemens Networks Exercise • Scope: Familiarize with Site Manager, xml files and understand configuration aspects using real commissioning files: • In the following example of RL20 commissioning file: – Indicate to which frequencies /technologies we will have reselection and which one has the highest priority • In the following example of RL30 commissioning file: – Identify the sector configuration and RF module configuration (ANTL parameters) – Have neighbours been created manually or with ANR? Why? – Maybe create some UFFIM or IRFIM for certain frequency (if parameters defined before). A REDR is easier (parameter wise but file already has some) -> if UFFIM created now it could be reused (parameter values) for the KISS macro (list object) Presentation / Author / Date RL30_comm_file RL20_Comm_File It needs to be refined
  • 76.
    Soc Classification level 78© Nokia Siemens Networks Plan Creation Methods Roll outs Presentation / Author / Date
  • 77.
    Soc Classification level 79© Nokia Siemens Networks Plan Creation for Rollouts Introduction • Configuration Management (CM) deals with the creation of plans/configuration files (xml) required for the integration of the sites within a network • There are multiple methods to create such plan/configuration file. Each method is based on a different tool. Preferred method is base on the project characteristics: • Method 1: NetAct Configurator • Method 2: Daisy - LACE • Method 3: Plan Editor • Method 4: Databuild Creation Macro (internal macro) • Three areas need to be configured when creating a plan: – Radio Network Parameters (RNW) – Site Configuration Parameters (HW) – LTE BTS Transport Parameters (FTM) • Focus within this training is on the RNW and site configuration areas Presentation / Author / Date
  • 78.
    Soc Classification level 80© Nokia Siemens Networks Method 1: NetAct Configurator Overview • Tool: NetAct Configurator • Inputs: • Site Data file (XML or CSV input file) • It contains ‘site specific’ parameters i.e. those that need to planned/allocated separately for each site • One site specific parameter per column, parameters for one site per row • Import Profile (XML) • Only necessary if Site Data file is in CSV format • Maps the columns information of the CSV file into XML • Site Template • Output: • Plan to be provisioned to the network • Benefit: • Simple and fast • Drawback: • It is necessary to have on-line connection to NetAct Presentation / Author / Date
  • 79.
    Soc Classification level 81© Nokia Siemens Networks Method 1: NetAct OSS and NetAct Configurator • Plan is created with a combination of CM Operations Manager and CM Editor • CM Operations Manager: Import site data (start of plan creation), import of site templates and CM workflow • CM Editor: Edit site templates and site(s)/plan inputs Presentation / Author / Date • RL30 and RL25TD are supported from OSS 5.3 CD set 3 NetAct –NE Element Compatibility Matrix
  • 80.
    Soc Classification level 82© Nokia Siemens Networks Method 1: NetAct Configurator Process 1. Import in CM Operations Manager (part of NetAct Configurator) the input file i.e. the site data file • Planner decides which parameters to include in the input file. Those parameters should be the ones that need to be specific for each site and for which it is not possible to use a template. • Within the input file it is necessary to include the identifier to the site template to be used 2. Assign an import profile to the csv input file • Only required if the input file is in csv format. Not needed if the input file is already in xml format • The import profile is needed to create and xml file from the csv input file. 3. Apply a site template to our plan (or input file) • For those parameters not included in the input file, the values of the site template are used 4. Validate the plan and provision it. NOTE: Provisioning the plans is not part of Radio planning Presentation / Author / Date
  • 81.
    Soc Classification level 83© Nokia Siemens Networks Method 1: NetAct Configurator Input File • Example input file for RL20 (csv) with minimal set of parameters needed: • Each column contains one site-specific parameter and each row contains the site- specific parameters for one site • User Interface (UI) or Internal parameter values can be used • A unique Distinguished Name (dn) is needed for every object created in the CSV file. It uniquely identifies a Managed Object in the database. – The only site-specific id in the DN is the MRBTS/mrBtsId which must be equal to LNBTS/lnBtsId  Example DN for LNCEL of sector #1: PLMN-PLMN/MRBTS-9876/LNBTS- 9876/LNCEL-1 • More information in Plan Creation with NetAct CM.ppt: – https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D437258745 Presentation / Author / Date 3cells_site_Input file
  • 82.
    Soc Classification level 84© Nokia Siemens Networks Method 1: NetAct Configurator Import Profile and Site Template (RL20) Import Profile • Example import profile for the previous input file example: • Import profile is created manually in a text editor. It must contain the same inputs (MOC and site-specific parameters) defined in the site input file Site Template • It contains the parameters that don’t need to be planned for every site and can be assigned a pre-defined value • Two ways to create the site template: – Importing an existing template using CMO Manager (NetAct Configurator) – Create a site template from an existing site in the OSS database using CM Editor (part of Configurator) • Site template values can be browsed and modified with any text editor or in CM Editor • More information in Plan Creation with NetAct CM.ppt: – https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D437258745 Presentation / Author / Date 3cells_import profile MOC: Managed Object Class
  • 83.
    Soc Classification level 85© Nokia Siemens Networks Method 2: Daisy-LACE Overview • Tool: – Daisy (NSN internal tool) with HW license (free) – Plan Editor with SW license (.lf file) • Inputs: – CIQ (Customer Information Questionnaire) excel • Output: – XML file for each eNB or unique xml containing the actual plan • Benefit: – Off-line • Drawback: – Not always available in time: It depends on availability of PE database, CIQ creation/verification – It doesn’t support SITE object creation (needed for Optimizer and Auto configuration) Presentation / Author / Date
  • 84.
    Soc Classification level 86© Nokia Siemens Networks Method 2: Daisy-LACE Process (1/4) Preparation phase: • Download and install the latest Daisy: – https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/432861101 – An empty Plan Editor (PE) database and the valid CIQ file for that Daisy version is part of the package, within folder LACE/Input E.g. C:Program FilesNSNDAISYProjectsLTE_LACE_RL20WorkDirLACEInput • Request CIQ HW license by filling the form: – https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D434761332 • Fill the required parameters within the CIQ – https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D433717329 • RL30 CIQ preparation is ongoing. No CIQ support for LTE TDD Presentation / Author / Date Example CIQ RL20
  • 85.
    Soc Classification level 87© Nokia Siemens Networks Method 2: Daisy-LACE Process (2/4) Daisy Handling • As Daisy works for several technologies it is necessary to select the correct one with the Data Generation button Presentation / Author / Date • Daisy works in three simple steps: – Data generation: Generation of xml files from the CIQ excel – Data Upload into Plan Editor: upload of xml files into PE – Data export (generation of the xml plan): combination of CIQ and PE parameters
  • 86.
    Soc Classification level 88© Nokia Siemens Networks Method 2: Daisy-LACE Process (3/4) Daisy Handling (cont) •Data Generation : Uploading the CIQ • Validates the CIQ • Note: CIQ must be closed (not opened in excel) when importing it in Daisy •Data Upload: Import in Plan Editor -> Straight forward after uploading the CIQ • Input: xml files generated in the previous step. It is enough to point to the folder •Data Export: Export to xml using either Default LTE LNx.0 or Default OSS Presentation / Author / Date
  • 87.
    Soc Classification level 89© Nokia Siemens Networks Method 2: Daisy-LACE Process (4/4) Plan Validation • Once Daisy provides the plan it is recommended to validate it before provisioning • Two possible DAISY outputs depending on the export profile – 1) Default LTE LNx.0 – 2) Default OSS Default LTE LNx.0 • It generates an xml file for each eNB -> validation for each site can be done individually with BTS site Manager Default OSS • It generates one xml for NetAct Configurator containing all sites (i.e. the whole plan) Presentation / Author / Date
  • 88.
    Soc Classification level 90© Nokia Siemens Networks Method 3: Plan Editor Overview • Tool: – Plan Editor with SW license (.lf file) • Inputs: – Site Data file (csv) – Plan Editor templates • Output: – Either a Commissioning file per site (suitable for BTS SM) or OSS plan multiple sites depending on the export profile selected • Benefit: – Off-line tool and official NSN tool – For some people it is the best method to generate plans and track changes • Drawback: • Generation of templates and template sets may not be straight forward Presentation / Author / Date If time add something else….
  • 89.
    Soc Classification level 91© Nokia Siemens Networks Method 4: KISS Databuild Creation Macro Overview • Tool: – Excel macro • Inputs: – Excel with radio and transport parameters that need to be planned (those different for each site) – Template for certain release – BTS SM for file validation (optional) • Output: – Commissioning file to be provisioned Presentation / Author / Date • Benefit: – Flexibility to adapt the macro for different releases and different inputs – Mass validation of sites in BTS SM with just one click • Drawback: – None so far KISS: Keep it short and simple
  • 90.
    Soc Classification level 92© Nokia Siemens Networks Method 4: KISS Databuild Creation Macro Overview • The off-line excel macro can be used for rollouts (simultaneously creation of multiple commissioning files) • It is valid for any release (FDD and TDD) providing the right template is used • Idea behind the tool: • Macro works by replacing $parameter tags in the template for parameters defined in the input sheets • Tool and instructions can be downloaded from: • https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/437564713 Presentation / Author / Date
  • 91.
    Soc Classification level 93© Nokia Siemens Networks Presentation / Author / Date Method 4: KISS Databuild Creation Macro Generic Process • Overall procedure: 1. Template creation: Create a template file using Site Manager (from Golden SCF), or use an existing site as a template file 2. Template adaptation: In the template file, replace site-specific parameter with $parameter tags, such as ‘$pci1’ 3. KISS handling: Define $parameter tags in the KISS excel and the parameter values that should replace them, one site per excel row 4. Run macro: KISS replaces tags with the parameter values and produces a commissioning file per site 5. Run validation
  • 92.
    Soc Classification level 94© Nokia Siemens Networks Comparison of plan creation methods (1/2) Attribute Method 1: NetAct with LTE site templates Method 2: DAISY-LACE Input data format CSV or XML Excel: Customer Information Questionnaire (CIQ) Output data Site CM data in OSS database. Can be exported in XML format using CMO Manager eNB commissioning files (xml) or OSS database (xml) SW required NetAct OSS DAISY-LACE + Plan Editor Licensing Basic NetAct functionality License for DAISY-LACE (hw dongle), Plan Editor soft license (.lf file) On-line / Off-line On-line: connection to NetAct required to import data with CMO Manager and to apply site template Off-line Optimizer SITE object creation readiness in import Yes, allows creation of SITE object in the CSV import No, SITE object must be created afterwards in NetAct Site template data parameter customizability Yes, site template parameters can be freely customized No, input data is according to fixed input data format (CIQ), empty parameters replaced with PDDB defaults CIQ = Customer Information Questionnaire
  • 93.
    Soc Classification level 95© Nokia Siemens Networks Comparison of plan creation methods (2/2) Attribute Method 3: Plan Editor using template sets Method 4: KISS Databuild Creation Macro Tool Input data format CSV Excel Output data eNB commissioning files (xml) or OSS database (xml) eNB commissioning files (xml) SW required Plan Editor None specific. Excel Licensing Plan Editor soft license (.lf file) None. On-line / Off-line Off-line Off-lines Optimizer SITE object creation readiness in import No, SITE object must be created afterwards in NetAct No, SITE object must be created afterwards in NetAct Site template data parameter customizability Yes, site template parameters can be freely customized using PE template sets Yes, site template parameters can be freely customized CIQ = Customer Information Questionnaire
  • 94.
    Soc Classification level 96© Nokia Siemens Networks Plan Creation with KISS Macro Exercise INPUTS: • Excel file provides input data (CIQ) based on real project(s) for 5 sites • Template has been created with BTS Site Manager and modified to work with KISS • Basic KISS macro: https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D437598496 EXERCISE: Create and validate commissioning files for the sites included in the plan. Consider: • Site 1 and Site 3 cells must be barred (using the macro, cellbarred parameter) – Scope: Addition of new parameters in the basic macro • Commissioning files must contain the neighbours defined in CIQ_RL30 excel (AdjSites) – Scope: Addition of List objects in KISS Presentation / Author / Date CIQ_RL30 T_ln30_exercise_basic.xml Still to be refined:
  • 95.
    Soc Classification level 97© Nokia Siemens Networks Plan Creation with KISS Macro Exercise • Current exercise is more about tool handling than configuration (parameter decision) • It can complement the other exercises: 1. identifying Configuration details as MOC with BTS site manager and 2. configuring a bit of idle mode or connected mode parameters (optimization training exercises) • Necessary to find a balance between not giving too much processing already done to the people or too little. • If too much: exercise can be very simple • If too little: they can spend hours in ‘manual’ handling (i.e. modifying the template, input data into the KISS macro) • Giving CIQ is good in the sense they have an example for real network. On the other hand, it is unnecessary complicated (if follows Daisy format) and it will be difficult for people to locate parameters. Probably easier just to provide an excel with some parameters • Maybe we could add that people create and UFFIM previously defined (maybe in another exercise). -> Need to check parameter values for that exercise and test it with the tool. Presentation / Author / Date Still to be refined:
  • 96.
    Soc Classification level 98© Nokia Siemens Networks Useful Links
  • 97.
    Soc Classification level 99© Nokia Siemens Networks Useful Links (1/2) • Main Configuration Management (CM) and data fills folder in IMS: • https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/433416226 • NetAct Plan Editor can be downloaded from IMS (software folder) together with additional documentation (documentation folder): – https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/390002169 • BTS SM can be downloaded: • NOLS: https://online.portal.nokiasiemensnetworks.com/nolshome/homepage ( access required to NOLS and to download software) : Radio Network -> Base Stations -> Flexi Multiradio BTS LTE and Flexi Multiradio BTS TD-LTE • IMS: https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/433488673 Presentation / Author / Date
  • 98.
    Soc Classification level 100© Nokia Siemens Networks Useful Links (2/2) • Commissioning parameters and parameter changes per different releases from NOLS: • https://online.portal.nokiasiemensnetworks.com/pic/com/nsn/extranet/pic/controller/productinf oview/pivdocumentation.do?productId=urn:nsn.com:mxpdm:133-047488 • Useful for ‘troubleshooting’ errors in the plan validation due to parameter relations that can be found in that excel Presentation / Author / Date
  • 99.
    Soc Classification level 101© Nokia Siemens Networks Terminology and Databuild types Golden System Configuration File (SCF): • xml file with all parameters necessary to configure the system • Excluding the parameters that are ’vendor’ specific Vendor File: • NSN specific parameters: The ones that can not be modified/ hardcoded. E.g ulSeqHop Commissioning File: • File containing all the parameters in the SCF. It doesn’t show the vendor file parameters Databuilds (types): • CIQ: Customer Information Questionaire – Theoretically, minimum set of information, easy to fill by/with customer – Input for Daisy ( LACE Tool) – It can be used as the excel databuild • Excel databuild: Similar to RNC/MSS/MGW data builds – Should include all parameters that may require planning intervention (i.e. default value might need to be changed under certain circumstances) • Plan Editor full databuild: the full PE database, including all eNB parameters Presentation / Author / Date