ru30 delta optimization m1 intro

24
1 © Nokia Siemens Networks 2011 _Change_Document_Information“ macro. RU30 Delta Optimisation Module 1 - Introduction Finland, Espoo 1-2.12.2011 NPO CMOS Radio Access Confidential NPO CMOS Radio Access/ Dec2011

Upload: bencenk

Post on 04-Oct-2015

158 views

Category:

Documents


15 download

DESCRIPTION

intro ru30

TRANSCRIPT

RU30 Delta Optimization Introduction

RU30 Delta OptimisationModule 1 - Introduction Finland, Espoo 1-2.12.2011NPO CMOS Radio Access

Confidential

NPO CMOS Radio Access/ Dec2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:# Nokia Siemens Networks 2011To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationTitle slideThe title slide serves a prompt to start the presentation.Note that your options are not limited to the standard colored texture on a white background. This template lets you use inverted textures such as the one shown in this slide. You will find all the available options in the master for this presentation.

Insert footnotes as you see fit.Nokia Siemens Networks has four classes of confidentiality governing who may see information: Public, For internal use, Confidential, and Secret.

Public This means the info is deemed suitable for general consumption. Always bear in mind that such public information will be available to everyone.

For internal use This info may be disseminated to anyone employed by or having a business relationship with the company under a valid non-disclosure agreement. If a small amount of this information is disclosed to the public, it will not cause meaningful harm to the company. For internal use is the default class for Nokia Siemens Networks information, and it should appear in all MS Office (master) templates.(Nokia called this class of info Company Confidential, and Siemens labeled it for Internal use.)

Confidential This info may be distributed only to people with a valid business need. Anyone who is authorized to possess this information is entitled to judge the validity of the business need. Unintentional disclosure of this information to the public will cause significant harm to the company. Confidential is the default class for all customer information.(Both Nokia and Siemens previously used the same classifier, Confidential)

Secret This info may be distributed only to people who are specifically authorized to see it by the owner of the information. Its disclosure to the public will cause serious harm to the company.(Nokia called this class of info Secret; Siemens called it Strictly confidential)

All documents in Nokia Siemens Networks shall be labeled according to this confidentiality classification scheme.

Copyright Nokia Siemens Networks. This material, including documentation and any related computer programs, is protected by copyright controlled by Nokia Siemens Networks. All rights are reserved. Copying, including reproducing, storing, adapting or translating, any or all of this material requires the prior written consent of Nokia Siemens Networks. This material also contains confidential information which may not be disclosed to others without the prior written consent of Nokia Siemens Networks

NPO CMOS Radio Access/ Dec2011# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationRU30 Related trainingsCompetence DevelopmentSVU SessionsMobile Radio SessionsRU30 features (SVU, by Chris Johnson )RU30 ON TOP Radio Features (SVU, by Chris Johnson)Training MaterialWCDMARU30 Planning Delta trainingRU30 Delta Optimisation training (this material)

NOTE !! Due the RU30 release roadmap update some early material contains features postponed to RU40

NPO CMOS Radio Access/ Dec2011# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationContentRU30 Delta optimisation training contentRU30 Feature list and RoadmapsRU30 Parameter Overview and OMS

NPO CMOS Radio Access/ Dec2011# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationRU30 delta Optimisation Module 1 IntroductionModule 2 Features (Features, parameter, counters, test results)Part 1 MBLBPart 2 - Uplink Capacity FeaturesPart 3 - HSDPA featuresModule 3 BTS capacity & Monitoring Module 4 Performance MonitoringNPO CMOS Radio Access/ Dec2011# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationRU30 Delta Optimisation Pilot Finland, Espoo 1-2.12.2011Day1Module 1 IntroductionModule 2 Features, Part 1 MBLBDay2Module 2 Features, Part 2 UL CapacityModule 3 BTS capacity & Monitoring (BB changes)

NPO CMOS Radio Access/ Dec2011# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationModule 1 - IntroductionRU30 Delta optimisation training contentRU30 Feature list and RoadmapsRU30 Parameter Overview and OMS

NPO CMOS Radio Access/ Dec2011# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationModule 2 - FeaturesPart1 Layering featuresRAN2172 Multiband Load BalancingPart 2 - Uplink CapacityRAN1702 Frequency Domain Equalizer (FDE)RAN1308 HSUPA Interference Cancellation (IC) ReceiverPart 3 - HSDPA featuresRAN1912 MIMO 42 MbpsRAN1637 High Speed Cell_FACH downlinkRAN2746 Fast HSDPA mobilityRAN2412 Inter Circle RoamingRAN2596 Inter Circle Roaming for HSDPA

NPO CMOS Radio Access/ Dec2011# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationModule 3 BTS Capacity & MonitoringBTS Site Solution Features - Overview RAN1269 4-way RX Diversity RAN2562 AAS Active Antenna System support for Trial RAN1881 RF Chaining RAN2123 Flexi BTS Gigabit BasebandBaseband Capacity & LicensingR99 CapacityHSDPA Schedulers & CapacityHSUPA Schedulers & CapacityLCGMonitoring BTS (new counters, KPIs)

NPO CMOS Radio Access/ Dec2011# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationM4 Performance MonitoringField PerformanceNew Counters & KPIsPerformance after upgrade

New Counters and test results related to RU30 new features are included to feature materialsNPO CMOS Radio Access/ Dec2011# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationContentRU30 Delta optimisation training contentRU30 Feature list and RoadmapsRU30 Parameter Overview and OMS

NPO CMOS Radio Access/ Dec2011# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationRRM and Telecom Features RU30NPO CMOS Radio Access/ Dec2011Feature IDFeature TitleRAS ReleaseLicenseBTS Release (Flexi)UE ReleaseRAN21082X Rake and Centralized TX CoreRU30 EP1NOWBTS7.0 1.0-RAN2352C-Iub Support in RU30RU30 EP1NO--RAN1743Distributed TUPRU30 EP1-WBTS7.0 1.0-RAN2270Extension of HSPA over IurRU30 EP1YES--RAN2054Extension of RNC idsRU30 EP2NO--RAN2746Fast HSPA MobilityRU30 EP1NO3GPP Rel-6RAN1702Frequency Domain EqualizerRU30 EP1-WBTS7.0 1.0RAN1263Generic RAKE for HSPA baseband efficiencyRU30 EP1-WBTS7.0 1.0-RAN1637High Speed Cell_FACH DLRU30 EP2YESWBTS7.0 2.03GPP Rel-7RAN2607HSPA over Iur with AnchoringRU30 EP1YES*--RAN2595HSPA with simultaneous video callRU30 EP1---RAN1308HSUPA Interference Cancellation ReceiverRU30 EP1-WBTS7.0 1.0RAN2412Inter Circle RoamingRU30 EP1YESRAN2596Inter Circle Roaming for HSDPARU30 EP2YESWBTS7.0 2.0RAN1912MIMO 42MbpsRU30 EP1YES**WBTS7.0 1.03GPP Rel-8RAN2172Multi-Band Load BalancingRU30 EP1YESRAN2715Multi-Point Tx DemoRU30 EP2-x-RAN2109RRM/Telecom agreed corrections and additionsRU30 EP1---*No own license, Tied to RAN2270 license (HSPA over Iur extension)** No own license, MIMO and 64QAM license required# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta Optimisation*No own license, Tied to RAN2270 license (HSPA over Iur extension)** No own license, MIMO and 64QAM license required

Removed features - draftFeatures included to earlier version of RU30 roadmap (not confirmed, new roadmap not published yet)

RAN2588 84 Mbps Demo (DC+MIMO) =>RU40RAN2171 Dynamic HSDPA BLER=>RU50RAN2482 Enhanced Virtual Antenna Mapping=>RU40RAN1645 HSUPA 16QAM=>RU40

RAN2394 Extended BTS Site Capacity=>RU40

NPO CMOS Radio Access/ Dec2011Draft # Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationBTS Features RU30NPO CMOS Radio Access/ Dec2011Feature IDFeature TitleRAS ReleaseLicenseBTS Release (Flexi)RAN273615 Cells BTS *RU30 EP2BTS LKWBTS7.0 2.0RAN12694-Way RX DiversityRU30 EP1BTS LKWBTS7.0 1.0RAN2719AAS Active Antenna System - AWS band DEMO and TRIAL SupportRU30 EP2WBTS7.0 2.0RAN2562AAS Active Antenna System support for trialRU30 EP1WBTS7.0 1.0RAN2326Dual-band RF ChainingRU30 EP2WBTS7.0 2.0RAN2123Flexi BTS Gigabit BasebandRU30 EP1BTS LKWBTS7.0 1.0RAN2262Flexi Multiradio System ModulesRU30 EP2-RAN1895Flexi RRH 2TX 900RU30 EP1-WBTS7.0 1.0RAN2560Flexi RRH 2TX 900 30MHzRU30 EP1WBTS7.0 1.0RAN2416MC-HSPA, DB-HSPA, PIC support with several System ModulesRU30 EP2WBTS7.0 2.0RAN2312Radio Interface Harmonization in Rel2.x RF modulesRU30 EP2WBTS7.0 2.0RAN1881RF chainingRU30 EP2BTS LKWBTS7.0 2.0RAN1770RF Sharing WCDMA - GSMRU30 EP1BTS LKWBTS7.0 1.0RAN2126RF Sharing WCDMA - LTERU30 EP2WBTS7.0 2.0RAN2757RF Sharing WCDMA - LTE with Extension SM for WCDMARU30 EP2WBTS7.0 2.0RAN2162RP3 Dynamic allocationRU30 EP1WBTS7.0 1.0*This is a subfeature of RAN2394 Extended BTS site capacity. (moved to RU40)# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationPerformance Features RU30NPO CMOS Radio Access/ Dec2011Feature IDFeature NameRAS ReleaseRAN2290User Management for Online MonitoringRU30RAN2626Baseband Load MonitoringRU30 EP2RAN2526L3 Data Collector for flat-Architectures, I-HSPARU30 EP2# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationContentRU30 Delta optimisation training contentRU30 Feature list and RoadmapsRU30 Parameter Overview and OMS

NPO CMOS Radio Access/ Dec2011# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationOMS Element ManagerNew browser based OMS Element ManagerNPO CMOS Radio Access/ Dec2011

# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationOMS Element ManagerNPO CMOS Radio Access/ Dec2011

# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationOMS Element Manager External ApplicationsNPO CMOS Radio Access/ Dec2011

# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationRAN2163 RNC Object Split to Several ObjectsCurrent RNC object is getting too big, it has to be splitted to several objects. The NetAct Configurator has a technical limitation of parameter amount under one object.

Parameter amount of RNC object in releases: RU10: 726 RU20: 950

RNC object parameters in RU20 are near to limit set by NetAct.

NPO CMOS Radio Access/ Dec2011# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta Optimisation

NEW RNC parameter ObjectsExisting RNC parameters are split under different objectsRNC managed object contains RNC level parameters i.e. commissioning parameters, SysInfo parameters, LCS, TOAWE and TOAWS related parametersRNAC - Object maintains AC parameters, Packet Data Convergence Protocol (PDCP) and power control/balancing/allocation related parameters. This object is not a network topology object. Delete operation is denied. The number of managed objects is 1RNFC - Object maintains all feature control parameters. This object is not a network topology object. Delete operation is denied. The number of managed objects is 1RNHSPA - Object maintains HSPA, CPC, F-DPCH relate parameters. This object is not a network topology object. Delete operation is denied. The number of managed objects is 1.RNMOBI - Object maintains mobility management parameters. i.e. HO, CM and mobile device control related. This object is not a network topology object. Delete operation is denied. The number of Management Object is 1.RNPS - Object maintains mandatory Packet Scheduler parameters and DyLO related parameters. This object is not a network topology object. Delete operation is denied. The number of MO is 1.RNRLC - Object maintains Radio Link Control parameters. This object is not a network topology object. Delete operation is denied. The number of managed objects is 1.RNTRM - Object maintains transmission parameters. This object is not a network topology object. Delete operation is denied. The number of managed objects is 1.

NPO CMOS Radio Access/ Dec2011# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationRNMOBIRNTRMRNPSPFLWSMLCWSGWRABWLCSEWLCSEWANETQMIPQMIPNMIURIUPSIUOIUCSIUCS IPIUPS IPPREBTSRNFCRNRLCRNHSPARNACHOPSHOPLHOPIHOPGFMCSFMCIFMCGCOCOCMOBCBCIWBTSVBTSVCELWCELADJDADJGADJIADJLADJSRNCLogical structure of the RNW management objects

RU30 NewNPO CMOS Radio Access/ Dec2011# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationRU30 parametersLatest version of parameter dump is available in parameter dictionary

RAN parameters - RN6.0 2.0/1.0

BTS Commissioning Parameters WN7.0 2.0/2.0NPO CMOS Radio Access/ Dec2011

# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationEnd of Module 1NPO CMOS Radio Access/ Dec2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:# Nokia Siemens Networks 2011To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.# Nokia Siemens Networks 2011R 255 G 211 B 8R 255 G 175 B 0R 127G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:To change the document information in the footer, press [Alt + F8] and use the Nokia_Siemens_Networks__Change_Document_Information macro.ConfidentialRU30 Delta OptimisationSheet0MS Excel (All parameter fields)Generated: Thu Nov 24 16:41:54 EET 2011Product:RNCRel/ver:RN6.0 2.0/1.0MO ClassParameter IdParameter NameAbbreviated Name3GPP NameData TypeStatusHiddenDescriptionShort DescriptionAdditional informationMultiplicityRelated FunctionsSystem informationRelated ParametersDescription of Parameter RelationshipsGroupClassificationInterfacesRange and StepDefault ValueDefault Value NotesSpecial ValueFormulaRequired on CreationModificationModifiedRelated featuresCalculationReferencesInternal NE TypeADJD19682Change originADJDChangeOriginEnumerationapprovedThe parameter defines the origin of the last configuration action affecting the object.The parameter defines the origin of the last configuration action affecting the object.1Operation and MaintenanceRNC -> RAC, RNC -> EMNot defined (0), Network originated configuration action (1), NetAct RNW plan originated configuration action (2), Element Manager originated configuration action (3), Configuration action by automatic tuning function (4), Element Manager originated mass config action (5), NetAct originated direct RNW change (6)-Value is set by the systemValue set by the systemNot modifiableSoft Handover Based on Detected Set Reportingchange_origin_tADJD19683Identifier of additional intra-frequency adjacencyADJDIdNumberapprovedIdentification of ADJD (Additional Intra-frequency Adjacency) within a WCDMA cell.Identification of ADJD within a WCDMA cell.1IdentificationOperation and MaintenanceRAC RNC, EM RNC, RACApp RAC, RNC -> OMS topology, RNC -> OMS topology UI0...31, step 1-Default value is not possibleinternal_value = gui_valueMandatoryNot modifiableADJD creationSoft Handover Based on Detected Set Reportingadjd_id_tADJD19684Cell IdentifierAdjdCICell Identity; C-IdNumberapprovedAn additional intra-frequency neighbour cell is identified with the UTRAN Cell Identifier, which is composed of the Global RNC Identifier and the Cell Identifier.Identifies the additional intra-frequency neighbour cell within the RNC.1Handover ControlHCConfigurationRadio Resource UtilisationRAC RNC, EM RNC, Planner RAC1...65535, step 1-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJD creation, modification (with restrictions), and deletion. Modification of the parameter is not possible if the cell is controlled by the local RNC; cross-check between RNC, WCEL and, ADJD objects is required.Soft Handover Based on Detected Set Reportingc_id_tADJD19686Primary CPICH powerAdjdCPICHTxPwrPrimary CPICH powerNumberapprovedThe parameter indicates the transmission power level of the Primary CPICH (Common Pilot Channel) of the additional intra-frequency neighbour cell.Parameter indicates the transmission power level of the Primary CPICH of the additional intra-frequency neighbour cell.1Handover ControlPtxPrimaryCPICH of WCEL - If the target cell is in the same RNC, ADJD- Primary CPICH power shall have the same value as WCEL-Transmission power of the primary CPICH channel parameter of the target cell. (public)HCConfigurationRadio Resource UtilisationRAC RNC, EM RNC, Planner RAC-10...50 dBm, step 0.1 dBm-Default value is not possibleinternal_value = gui_value * 10MandatoryOn-lineADJD creation and modification (with restrictions). Modification of the parameter is not possible if the cell is controlled by the local RNC; cross-check between RNC, WCEL, and ADJD objects is required.Soft Handover Based on Detected Set Reportingptx_pri_cpich_tADJD19688Disable Effect on Reporting RangeAdjdDERRCells forbidden to affect Reporting rangeEnumerationapprovedThe parameter indicates whether the additional intra-frequency neighbour cell is forbidden to affect the reporting range (addition/drop window) calculation, if it belongs to the active set.The parameter indicates whether the additional neighbour cell is forbidden to affect the reporting range.1Handover ControlHCMeasurementsRadio Resource UtilisationRNC -> UE, RAC RNC, EM RNC, RACApp RACNo (0), Yes (1)No (0)The additional neighbour cell can affect the reporting range.OptionalOn-lineADJD creation and modificationSoft Handover Based on Detected Set Reportingdisable_eff_rep_range_tADJD19791HSDPA HOPS identifierAdjdHSDPAHopsIdNumberlangCheckedThe parameter identifies the parameter set (HOPS object) which controls the intra-frequency handover to the additional neighbour cell when a user has HS-DSCH allocated.Identifies the HOPS object which controls the intra-frequency handover to the additional neighbour cell when a user has HS-DSCH allocated.1Handover ControlHOPSId of HOPS - Check that the relevant HOPS object exists in the database. (public)HSDPAenabled of WCEL - If HSDPA is enabled in the parent cell of the additional intra-frequency neighbour cell, the special value 'Not defined' is not allowed for AdjdHSDPAHopsId. (public)HCConfigurationRadio Resource UtilisationRAC RNC, EM RNC, RACApp RAC1...100, step 10Not definedNot defined (0)internal_value = gui_valueOptionalOn-lineADJD creation and modificationSoft Handover Based on Detected Set Reporting AND HSDPAhops_id_tADJD19692Location Area CodeAdjdLACLocation Area Code; LACNumberapprovedThe PLMN Identifier and the Location Area Code (LAC) determine the Location Area (LAI) to which the additional intra-frequency neighbour cell belongs to.The PLMN Identifier and the LAC determine the LAI to which the additional intra-frequency neighbour cell belongs to.1Handover ControlLAC of WCEL - If the target cell is in the same RNC, ADJD- Location Area Code shall have the same value as WCEL-Location Area Code parameter of the target cell. (public)HCConfigurationRadio Resource UtilisationRNC MSC, RAC RNC, EM RNC, Planner RAC, RNC -> OMS topology, RNC -> OMS topology UI1...65535, step 1-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJD creation and modification (with restrictions). Modification of the parameter is not possible if the cell is controlled by the local RNC; cross-check between RNC, WCEL, and ADJD objects is required.Soft Handover Based on Detected Set Reportinglac_tADJD19693Mobile Country CodeAdjdMCCMobile Country Code; MCCNumberapprovedAn additional intra-frequency neighbour cell is identified with the UTRAN Cell Identifier, which is composed of the Global RNC Identifier and the Cell Identifier. Furthermore, the Global RNC Identifier is composed of the PLMN Identifier, which consists of the Mobile Country Code (MCC), the Mobile Network Code (MNC), and the RNC Identifier.Unique country identification of the additional intra-frequency neighbour cell.1Handover ControlWCELMCC of WCEL - If the target cell is in the same RNC, ADJD- Mobile Country Code shall have the same value as WCEL-Mobile Country Code parameter of the target cell. (public)HCConfigurationRadio Resource UtilisationRNC MSC, RAC RNC, EM RNC, Planner RAC, RNC -> OMS topology, RNC -> OMS topology UI0...999, step 1-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJD creation and modification (with restrictions). Modification of the parameter is not possible if the cell is controlled by the local RNC; cross-check between RNC, WCEL, and ADJD objects is required.Soft Handover Based on Detected Set Reportingmcc_tADJD19696Mobile Network CodeAdjdMNCMobile Network Code; MNCNumberapprovedAn additional intra-frequency neighbour cell is identified with the UTRAN Cell Identifier, which is composed of the Global RNC Identifier and the Cell Identifier. Furthermore, the Global RNC Identifier is composed of the PLMN Identifier, which consists of the Mobile Country Code (MCC), the Mobile Network Code (MNC), and the RNC Identifier.Unique network identification of the additional intra-frequency neighbour cell within a country.1Handover ControlWCELMNC of WCEL - If the target cell is in the same RNC, ADJD- Mobile Network Code shall have the same value as WCEL-Mobile Network Code parameter of the target cell. (public)HCConfigurationRadio Resource UtilisationRNC MSC, RAC RNC, EM RNC, Planner RAC, RNC -> OMS topology, RNC -> OMS topology UI0...999, step 1-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJD creation and modification (with restrictions). Modification of the parameter is not possible if the cell is controlled by the local RNC; cross-check between RNC, WCEL, and ADJD objects is required.Soft Handover Based on Detected Set Reportingmnc_tADJD19698Mobile Network Code LengthAdjdMNCLengthEnumerationapprovedThe parameter defines whether 2 or 3 digits are used in the mobile network code (MNC) of the additional intra-frequency neighbour cell.Defines whether 2 or 3 digits are used in the MNC.1AdjdMNC of ADJD - When this parameter is modified also the value of the mobile network code is always changed. (public)WCELMNCLength of WCEL - If the target cell is in the same RNC, ADJD- Mobile Network Code Length shall have the same value as WCEL-Mobile Network Code Length parameter of the target cell. (public)HCConfigurationRadio Resource UtilisationRAC RNC, EM RNC2 digits (2), 3 digits (3)2 digits (2)OptionalOn-lineADJD creation and modification (with restrictions). Modification of the parameter is not possible if the cell is controlled by the local RNC; cross-check between RNC, WCEL, and ADJD objects is required.Soft Handover Based on Detected Set Reportingmnc_tADJD19803NRT HOPS IdentifierAdjdNRTHopsIdNumberapprovedThe parameter defines the parameter set (HOPS object) which controls the intra-frequency handover of a non-real time (NRT) radio bearer to the additional neighbour cell.Defines the HOPS object which controls the intra-frequency handover of an NRT radio bearer to the additional neighbour cell.1Handover ControlHOPSId of HOPS - Check that the relevant HOPS object exists in the database. (public)HCConfigurationRadio Resource UtilisationRAC RNC, EM RNC, RACApp RAC1...100, step 1-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJD creation and modificationSoft Handover Based on Detected Set Reportinghops_id_tADJD19784Routing Area CodeAdjdRACRouting Area Code; RACNumberapprovedThe Location Area (LAI) and the Routing Area Code (RAC) determine the Routing Area to which the additional intra-frequency neighbour cell belongs to.The LAI and the RAC determine the Routing Area to which the additional intra-frequency neighbour cell belongs to.1Handover ControlRAC of WCEL - If the target cell is in the same RNC, ADJD- Routing Area Code shall have the same value as WCEL-Routing Area Code parameter of the target cell. (public)HCConfigurationRadio Resource UtilisationRNC MSC, RAC RNC, EM RNC, Planner RAC, RNC -> OMS topology, RNC -> OMS topology UI0...255, step 1-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJD creation and modification (with restrictions). Modification of the parameter is not possible if the cell is controlled by the local RNC; cross-check between RNC, WCEL, and ADJD objects is required.Soft Handover Based on Detected Set Reportingrac_tADJD19785RNC IdentifierAdjdRNCIdRNC Identifier; RNC-IdNumberlangCheckedAn additional intra-frequency neighbor cell is identified with the UTRAN Cell Identifier, which is composed of the Global RNC Identifier and the Cell Identifier. The Global RNC Identifier is composed of the PLMN Identifier and the RNC Identifier.For RAN 2054 feature "Extension of RNC ids" only, extended range of 4096..65534 will be used , otherwise older range 1..4095 will be used as this extended range violates 3GPP specifications.A unique identification for an RNC node within the UTRAN to which an additional intra-frequency neighbor cell belongs.1Handover ControlHCConfigurationRadio Resource UtilisationRNC MSC, RAC RNC, EM RNC, Planner RAC, RNC -> OMS topology, RNC -> OMS topology UI1...65534, step 1-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJD creation, modification (with restrictions), and deletion. Modification of the parameter is not possible if the cell is controlled by the local RNC; cross-check between RNC, WCEL, and ADJD objects is required.Soft Handover Based on Detected Set ReportingNSN reference: RAN2054 Extension of RNC-ids EFS (internal)rnc_id_tADJD19810RT HOPS IdentifierAdjdRTHopsIdNumberapprovedThe parameter defines the parameter set (HOPS object) which controls the intra-frequency handover of a real time (RT) radio bearer to the additional neighbour cell.Defines the HOPS object which controls the intra-frequency handover of an RT radio bearer to the additional neighbour cell.1Handover ControlHOPSId of HOPS - Check that the relevant HOPS object exists in the database. (public)HCConfigurationRadio Resource UtilisationRAC RNC, EM RNC, RACApp RAC1...100, step 1-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJD creation and modificationSoft Handover Based on Detected Set Reportinghops_id_tADJD19804HSDPA HOPS identifier for AMR multi-serviceAdjdRTWithHSDPAHopsIdNumberlangCheckedThe parameter identifies the parameter set (HOPS object) which controls the intra-frequency handover to the additional neighbour cell when a user has HS-DSCH allocated simultaneously with the AMR speech CS RAB.Identifies the HOPS object which controls the intra-frequency handover to the additional neighbour cell when a user has HS-DSCH allocated simultaneously with the AMR speech CS RAB.1Handover ControlHOPSId of HOPS - Check that the relevant HOPS object exists in the database. (public)HSDPAenabled of WCEL - If AMR service can be used with HS-DSCH and HSDPA is enabled in the parent cell of the additional intra-frequency neighbour cell, the special value 'Not defined' is not allowed for AdjdRTWithHSDPAHopsId. (public)AMRWithHSDSCH of RNFC - If AMR service can be used with HS-DSCH and HSDPA is enabled in the parent cell of the additional intra-frequency neighbour cell, the special value 'Not defined' is not allowed for AdjdRTWithHSDPAHopsId. (public)HCConfigurationRadio Resource UtilisationRAC RNC, EM RNC, RACApp RAC1...100, step 10Not definedNot defined (0)internal_value = gui_valueOptionalOn-lineADJD creation and modificationSoft Handover Based on Detected Set Reporting AND HSDPAhops_id_tADJD19786Primary Scrambling CodeAdjdScrCodePrimary scrambling codeNumberapprovedThe downlink scrambling code of the Primary CPICH (Common Pilot Channel) of the additional intra-frequency neighbour cell.

Primary Scrambling Code of an additional intra-frequency neighbour cell must be unique within the basic and additional intra-frequency neighbour cells.The downlink scrambling code of the Primary CPICH of the additional intra-frequency neighbour cell.1Handover ControlPriScrCode of WCEL - If the target cell is in the same RNC, ADJD- Primary Scrambling Code shall have the same value as WCEL-Primary downlink scrambling code parameter of the target cell. (public)HCConfigurationRadio Resource UtilisationRNC UE, RAC RNC, EM RNC, Planner RAC0...511, step 1-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJD creation and modification (with restrictions). Modification of the parameter is not possible if the cell is controlled by the local RNC; cross-check between RNC, WCEL, and ADJD objects is required.Soft Handover Based on Detected Set Reportingdl_pri_scr_code_tADJD19790Tx Diversity IndicatorAdjdTxDivTx diversity indicatorEnumerationapprovedThe parameter indicates whether the Primary CPICH of the additional intra-frequency neighbour cell is broadcast from two antennas. If the Primary CPICH is broadcast from two antennas, the UE measures the received code power from each antenna separately and sums the measurement results together in order to get the total received code power on the Primary CPICH.Indicates whether the Primary CPICH of the additional intra-frequency neighbour cell is broadcast from two antennas.1Handover ControlHCConfigurationRadio Resource UtilisationRNC -> UE, RAC RNC, EM RNC, RACApp RACTx Diversity not used (0), Tx Diversity in use (1)Tx Diversity not used (0)Tx Diversity not usedOptionalOn-lineADJD creation and modification (with restrictions). Modification of the parameter is not possible if the cell is controlled by the local RNC; cross-check between RNC, WCEL, and ADJD objects is required.Soft Handover Based on Detected Set Reportingtx_diversity_ind_tADJG1236Change originADJGChangeOriginEnumerationapprovedThe parameter defines the origin of the last configuration action affecting the object.The parameter defines the origin of the last configuration action affecting the object.1Operation and MaintenanceRNC -> RAC, RNC -> EMNot defined (0), Network originated configuration action (1), NetAct RNW plan originated configuration action (2), Element Manager originated configuration action (3), Configuration action by automatic tuning function (4), Element Manager originated mass config action (5), NetAct originated direct RNW change (6)-Value is set by the systemValue set by the systemNot modifiableNokia reference: Radio Network Configuration Management SFS (internal)change_origin_tADJG1237Inter-system adjacency identifierADJGIdNumberapprovedIdentification of inter-system adjacency (GSM or GAN) within a WCDMA cell. If Wireless Priority Service is enabled, then operator shall specify a unique GSM cell as the target cell of blind handover. When Wireless Priority Service feature is enabled, then value 0 is a special value which indicates that cell is target cell of blind handover. This means that Inter-system adjacency identifier 0 shall be defined by operator if Wireless Priority Service feature is enabled.Identification of inter-system adjacency (GSM or GAN) within a WCDMA cell. When Wireless Priority Service feature is enabled, then value 0 is a special value which indicates that cell is target cell of blind handover.1IdentificationOperation and MaintenanceRAC RNC, EM RNC, RACApp RAC, RNC -> OMS topology, RNC -> OMS topology UI0...31, step 1-Default value is not possibleZero has special meaning only when WPS is enabled. (0)internal_value = gui_valueMandatoryNot modifiableADJG creationWCDMA - GSM Inter-system Handover OR UTRAN-GAN Interworkingadjg_id_tADJG37500Inter-system Neighbour Cell TypeADJGTypeEnumerationlangCheckedThe parameter indicates whether the inter-system neighbour cell is a GSM cell or a GAN cell.The parameter indicates whether the inter-system neighbour cell is a GSM cell or a GAN cell.1Handover ControlHCConfigurationRadio Resource UtilisationRAC RNC, EM RNC, RACApp RACGSM cell (0), GAN cell (1)GSM cell (0)GSM cellMandatoryNot modifiableADJG creationWCDMA - GSM Inter-system Handover AND UTRAN-GAN InterworkingNSN reference: UTRAN - GAN Interworking (RAN1183) EFS (internal)adjg_type_tADJG1238Base Station Colour CodeAdjgBCCBase Station Colour Code (BCC)NumberlangCheckedBase Station Identity Code (BSIC) is composed of Network Colour Code (NCC) and Base Station Colour Code (BCC). The parameter value is set by the system for the GAN neighbour cell.Base Station Identity Code (BSIC) is composed of Network Colour Code (NCC) and Base Station Colour Code (BCC). The parameter value is set by the system for the GAN neighbour cell.1Handover Control, Mobile Device ControlSIB11, SIB12ADJGType of ADJG - Parameter value is always 0 if the value of ADJGType is 'GAN cell'. (public)HCConfigurationRadio Resource UtilisationRNC UE, RAC RNC, EM RNC, Planner RAC0...7, step 1-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJG creation and modificationWCDMA - GSM Inter-system Handover OR UTRAN-GAN Interworking3GPP Reference: TS 25.331, RRC Protocol Specification (public), NSN reference: Handover Control FD (internal)bsic_tADJG1239BCCH ARFCNAdjgBCCHBCCH ARFCNNumberlangCheckedThis parameter contains the absolute RF channel number of the Broadcast Control Channel (BCCH) of the GSM neighbour cell. The parameter value is set by the system for the GAN neighbour cell.This parameter contains the absolute RF channel number of the Broadcast Control Channel (BCCH) of the GSM neighbour cell. The parameter value is set by the system for the GAN neighbour cell.1Handover Control, Mobile Device ControlSIB11, SIB12AdjgBandIndicator of ADJG - Indicates whether the BCCH ARFCN belongs to the GSM 1900 band. (public)ADJGType of ADJG - Parameter value is always 0 if the value of ADJGType is 'GAN cell'. (public)HCConfigurationRadio Resource UtilisationRNC UE, RAC RNC, EM RNC, Planner RAC, RNC -> OMS topology, RNC -> OMS topology UI0...1023, step 1-Default value is not possible.internal_value = gui_valueMandatoryOn-lineADJG creation and modificationWCDMA - GSM Inter-system Handover OR UTRAN-GAN InterworkingNSN reference: Handover Control FD (internal), 3GPP Reference: TS 25.331, RRC Protocol Specification (public)arfcn_tADJG1240Band IndicatorAdjgBandIndicatorBand indicatorEnumerationlangCheckedThis parameter indicates whether the BCCH ARFCN of the neighbour cell belongs to the GSM 1900 band. The parameter value is set by the system for the GAN neighbour cell.Indicates whether the BCCH ARFCN of the neighbour cell belongs to the GSM 1900 band. The parameter value is set by the system for the GAN neighbour cell.1Handover Control, Mobile Device ControlSIB11, SIB12AdjgBCCH of ADJG - Contains the absolute RF channel number of the Broadcast Control Channel (BCCH) of the GSM neighbour cell. (public)ADJGType of ADJG - Parameter value is always 'No' if the value of ADJGType is 'GAN cell'. (public)HCConfigurationRadio Resource UtilisationRNC UE, RAC RNC, EM RNCNo (0), GSM 1900 (1)-Default value is not possible.MandatoryNot modifiableADJG creationWCDMA - GSM Inter-system Handover OR UTRAN-GAN Interworking3GPP Reference: TS 25.331, RRC Protocol Specification (public), NSN reference: Handover Control FD (internal)band_indicator_tADJG1243Cell IdentifierAdjgCICell Identifier; CINumberapprovedGSM and GAN neighbour cells are identified with the Cell Global Identifier (CGI), which is composed of the PLMN Identifier, Location Area Code and Cell Identifier.Cell identifier of the GSM and GAN neighbour cells.1Handover Control, Mobile Device ControlHCConfigurationRadio Resource UtilisationRNC MSC, RAC RNC, EM RNC, Planner RAC, RNC -> OMS topology, RNC -> OMS topology UI1...65535, step 1-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJG creation, modification and deletionWCDMA - GSM Inter-system Handover OR UTRAN-GAN Interworking3GPP Reference: TS 25.413, UTRAN Iu Interface RANAP Signalling (public), Nokia reference: Handover Control SFS v.2.0.2 (internal)c_id_tADJG1244Location Area CodeAdjgLACLocation Area Code; LACNumberapprovedThe PLMN Identifier and Location Area Code (LAC) determine the Location Area (LAI) to which the GSM or GAN neighbour cell belongs to. The PLMN identifier is composed of the Mobile Country Code (MCC) and the Mobile Network Code(MNC).The PLMN Identifier and Location Area Code (LAC) determine the Location Area (LAI) to which the GSM or GAN neighbour cell belongs to1Handover Control, Mobile Device ControlHCConfigurationRadio Resource UtilisationRNC MSC, RAC RNC, EM RNC, Planner RAC, RNC -> OMS topology, RNC -> OMS topology UI1...65535, step 1-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJG creation, modification and deletionWCDMA - GSM Inter-system Handover OR UTRAN-GAN InterworkingNokia reference: Handover Control SFS v.2.0.2 (internal), 3GPP Reference: TS 25.413, UTRAN Iu Interface RANAP Signalling (public)lac_tADJG1245Mobile Country CodeAdjgMCCMobile Country Code; MCCNumberapprovedGSM and GAN neighbour cells are identified with the Cell Global Identifier (CGI), which is composed of the PLMN Identifier, Location Area Code and Cell Identifier. Furthermore, the PLMN Identifier is composed of the Mobile Country Code (MCC) and the Mobile Network Code (MNC).Unique country identification of GSM and GAN neighbour cells.1Handover Control, Mobile Device ControlSIB18HCConfigurationRadio Resource UtilisationRNC MSC, RAC RNC, EM RNC, Planner RAC, RNC -> UE, RNC -> OMS topology, RNC -> OMS topology UI0...999, step 1-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJG creation and modificationWCDMA - GSM Inter-system Handover OR UTRAN-GAN Interworking3GPP Reference: TS 25.413, UTRAN Iu Interface RANAP Signalling (public), Nokia reference: Handover Control SFS v.2.0.2 (internal)mcc_tADJG1246Mobile Network CodeAdjgMNCMobile Network Code; MNCNumberapprovedGSM and GAN neighbour cells are identified with the Cell Global Identifier (CGI), which is composed of the PLMN Identifier, Location Area Code and Cell Identifier. Furthermore, the PLMN Identifier is composed of the Mobile Country Code (MCC) and the Mobile Network Code (MNC).GSM and GAN neighbour cells are identified with the Cell Global Identifier (CGI), which is composed of the PLMN Identifier (MCC + MNC), Location Area Code and Cell Identifier1Handover Control, Mobile Device ControlSIB18AdjgMNCLength of ADJG - Value range depends from the AdjgMNCLength: 00..99 (if AdjgMNCLength is 2) or 000..999 (if AdjgMNCLength is 3). (public)HCConfigurationRadio Resource UtilisationRNC MSC, RAC RNC, EM RNC, Planner RAC, RNC -> UE, RNC -> OMS topology, RNC -> OMS topology UI0...999, step 1-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJG creation and modificationWCDMA - GSM Inter-system Handover OR UTRAN-GAN Interworking3GPP Reference: TS 25.413, UTRAN Iu Interface RANAP Signalling (public), Nokia reference: Handover Control SFS v.2.0.2 (internal)mnc_tADJG1247Mobile Network Code LengthAdjgMNCLengthEnumerationapprovedThis parameter defines whether 2 or 3 digits are used in Mobile Network Code.

When this parameter is modified also the value of MNC used by system is always changed.Defines whether 2 or 3 digits are used in Mobile Network Code1SIB18HCConfigurationRadio Resource UtilisationRAC RNC, EM RNC2 digits (2), 3 digits (3)2 digits (2)MandatoryOn-lineDuring ADJG creation/modification.WCDMA - GSM Inter-system Handover OR UTRAN-GAN Interworking3GPP Reference: TS 25.413, UTRAN Iu Interface RANAP Signalling (public), 3GPP Reference: TS 25.331, RRC Protocol Specification (public)mnc_tADJG1248Network Colour CodeAdjgNCCNetwork Colour Code (NCC)NumberlangCheckedBase Station Identity Code (BSIC) is composed of Network Colour Code (NCC) and Base Station Colour Code (BCC). The parameter value is set by the system for the GAN neighbour cell.Base Station Identity Code (BSIC) is composed of Network Colour Code (NCC) and Base Station Colour Code (BCC). The parameter value is set by the system for the GAN neighbour cell.1Handover Control, Mobile Device ControlSIB11, SIB12ADJGType of ADJG - Parameter value is always 0 if the value of ADJGType is 'GAN cell'. (public)HCConfigurationRadio Resource UtilisationRNC UE, RAC RNC, EM RNC, Planner RAC0...7, step 1-Default value is not possible.internal_value = gui_valueMandatoryOn-lineADJG creation and modificationWCDMA - GSM Inter-system Handover OR UTRAN-GAN InterworkingNSN reference: Handover Control FD (internal), 3GPP Reference: TS 25.331, RRC Protocol Specification (public)bsic_tADJG8073Include in System InformationAdjgSIBEnumerationlangCheckedThe parameter indicates whether the GSM neighbour cell is included in the System Information Block 11&11bis&12&18 for the cell selection and re-selection procedures. The GSM neighbour cell is included in the system information when the value of the parameter is "SIB". The GSM neighbour cell is included in the extended system information when the value of the parameter is "SIBbis". The value of the parameter is set by the system for the GAN neighbour cell.

If the Wireless Priority Service feature is enabled, then the parameter Include in System Information shall be set to have value "SIB" for ADJG-0.

The total number of intra-frequency, inter-frequency and GSM neighbour cells, which can be included in the System Information Block type 11 (SIB11), is 47. When HCS is used, the capacity is limited to 35 cells.

System Information Block type 11bis (SIB11bis) increases the maximum number of adjacencies to 96. SIB11bis can only be decoded by the UEs which support 3GPP R6.

If the total number of intra-frequency, inter-frequency and GSM neighbour cells, which are included in the System Information, exceeds the physical size of SIB data, the NBAP interface is not able to pack the neighbour cell information into the SIB data and the scheduling of the system information blocks fails. The cell is blocked by the system and an alarm 7771 WCDMA CELL OUT OF USE (BCCH scheduling error) is reported for the cell.

Note: The parameter AdjgSIB does not affect GSM measurements in CELL_DCH state of the connected mode. That is, all GSM neighbour cells are monitored for the inter-system handover regardless of the value of the parameter AdjgSIB.The parameter indicates whether the GSM neighbour cell is included in the SIB 11&11bis&12&18. The value of the parameter is set by the system for GAN neighbour cell. The parameter does not affect GSM measurements in CELL_DCH state of the connected mode.1Handover ControlSIB11, SIB12, SIB18, SIB11bisAdjiSIB of ADJI - Parameter indicates whether the inter-frequency neighbour cell is included in the System Information for the cell selection and re-selection procedures. (public)AdjsSIB of ADJS - Parameter indicates whether the intra-frequency neighbour cell is included in the system information for the cell selection and re-selection procedures. (public)ADJGType of ADJG - Parameter value is always "No" if the value of ADJGType is "GAN cell". (public)HCConfigurationRadio Resource UtilisationRAC RNC, EM RNC, RAC RACAppNo (0), SIB (1), SIBbis (2)SIB (1)The GSM neighbour cell is included in the system information.MandatoryOn-lineADJG creation and modification.( WCDMA - GSM Inter-system Handover AND Extension of sib11 ) OR UTRAN-GAN InterworkingNSN reference: Handover Control FD (internal), NSN reference: RAN1323 Extension of Sib11 (internal)gsm_ncell_sib_tADJG1249Maximum UE TX Power on RACHAdjgTxPwrMaxRACHMaximum allowed UL TX power; UE_TXPWR_MAX_RACHNumberlangCheckedThis parameter indicates the maximum transmission power level that a UE can use when accessing the GSM neighbour cell on the RACH. The UE uses the parameter in the cell re-selection procedure. If the maximum output power of the UE is lower than the value of the parameter, the UE adds the power difference (dB value) to the minimum required GSM RSSI level, which the measurement result of the GSM neighbour cell must exceed before the cell re-selection is possible. The parameter value is set by the system for the GAN neighbour cell.Indicates the maximum transmission power level that a UE can use when accessing the GSM neighbour cell on the RACH. The parameter value is set by the system for the GAN neighbour cell.1Mobile Device ControlSIB11, SIB12ADJGType of ADJG - Parameter value is always 0 dBm if the value of ADJGType is 'GAN cell'. (public)HCConfigurationRadio Resource UtilisationRNC UE, RAC RNC, EM RNC0...33 dBm, step 1 dBm-Default value is not possible.internal_value = gui_valueMandatoryOn-lineADJG creation and modificationWCDMA - GSM Inter-system Handover OR UTRAN-GAN InterworkingNSN reference: Handover Control FD (internal), 3GPP Reference: TS 25.331, RRC Protocol Specification (sections 10.3.2.4 and 10.3.6.39) (public), 3GPP Reference: TS 25.304, UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode (public)tx_pwr_max_prach_gsm_tADJG1250Maximum UE TX Power on TCHAdjgTxPwrMaxTCHNumberlangCheckedThis parameter indicates the maximum transmission power level that a UE may use on a TCH in the GSM neighbour cell. The RNC uses the parameter in the decision algorithm of the inter-RAT (GSM) handover. If the maximum output power of the UE is lower than the value of the parameter, the RNC adds the power difference (dB value) to the minimum required GSM RSSI level, which the measurement result of the GSM neighbour cell must exceed before the handover is possible. The parameter value is set by the system for the GAN neighbour cell.Parameter indicates the maximum transmission power level that a UE may use on a TCH in the GSM neighbour cell. The parameter value is set by the system for the GAN neighbour cell.1Handover ControlAdjgRxLevMinHO of HOPG - Determines the minimum required GSM RSSI level which the averaged RSSI value of the GSM neighbour cell must exceed before the coverage (or quality) reason handover to GSM is possible. (public)ADJGType of ADJG - Parameter value is always 0 dBm if the value of ADJGType is 'GAN cell'. (public)HCConfigurationRadio Resource UtilisationRNC UE, RAC RNC, EM RNC0...43 dBm, step 1 dBm-Default value is not possible.internal_value = gui_valueMandatoryOn-lineADJG creation and modificationWCDMA - GSM Inter-system Handover OR UTRAN-GAN InterworkingGSM reference: 05.08 Radio Subsystem Link Control (public), NSN reference: Handover Control FD (internal), GSM reference: 05.05 Radio Transmission and Reception (public)max_tx_pwr_tch_tADJG1251NRT HOPG IdentifierNrtHopgIdentifierNumberlangCheckedDefines the parameter set (HOPG object) which controls the inter-RAT handover of a non-real time (NRT) radio bearer to the GSM neighbour cell. The parameter value is set by the system for the GAN neighbour cell.Defines the parameter set (HOPG object) which controls the inter-RAT handover of a NRT radio bearer to the GSM neighbour cell. The parameter value is set by the system for the GAN neighbour cell.1Handover ControlSIB11, SIB12, SIB18HOPGId of HOPG - Check that the relevant HOPG object exists in the database. (public)ADJGType of ADJG - Special value 'Not defined' is mandatory if the value of the parameter ADJGType is 'GAN cell'. Otherwise, the special value is not allowed. (public)HCConfigurationRadio Resource UtilisationRAC RNC, EM RNC, RACApp RAC, RNC -> OMS topology, RNC -> OMS topology UI1...100, step 1-Default value is not possible.Not defined (0)internal_value = gui_valueMandatoryOn-lineADJG creation and modificationWCDMA - GSM Inter-system Handover OR UTRAN-GAN InterworkingNSN reference: Handover Control FD (internal)hopg_id_tADJG1252RT HOPG IdentifierRtHopgIdentifierNumberlangCheckedDefines the parameter set (HOPG object) which controls the inter-RAT handover of a real time (RT) radio bearer to the GSM neighbour cell. The parameter value is set by the system for the GAN neighbour cell.Defines the parameter set (HOPG object) which controls the inter-RAT handover of a RT radio bearer to the GSM neighbour cell. The parameter value is set by the system for the GAN neighbour cell.1Handover ControlSIB11, SIB12, SIB18HOPGId of HOPG - Check that the relevant HOPG object exists in the database. (public)ADJGType of ADJG - Special value 'Not defined' is mandatory if the value of the parameter ADJGType is 'GAN cell'. Otherwise, the special value is not allowed. (public)HCConfigurationRadio Resource UtilisationRAC RNC, EM RNC, RACApp RAC, RNC -> OMS topology, RNC -> OMS topology UI1...100, step 1-Default value is not possible.Not defined (0)internal_value = gui_valueMandatoryOn-lineADJG creation and modificationWCDMA - GSM Inter-system Handover OR UTRAN-GAN InterworkingNSN reference: Handover Control FD (internal)hopg_id_tADJI1335Change originADJIChangeOriginEnumerationapprovedThe parameter defines the origin of the last configuration action affecting the object.The parameter defines the origin of the last configuration action affecting the object.1Operation and MaintenanceRNC -> RAC, RNC -> EMNot defined (0), Network originated configuration action (1), NetAct RNW plan originated configuration action (2), Element Manager originated configuration action (3), Configuration action by automatic tuning function (4), Element Manager originated mass config action (5), NetAct originated direct RNW change (6)-Value is set by the systemValue set by the systemNot modifiableNokia reference: Radio Network Configuration Management SFS (internal)change_origin_tADJI1336Inter-frequency adjacency identifierADJIIdNumberapprovedIdentification of ADJI (Inter-Frequency Adjacency) within a WCDMA Cell.Identification of ADJI within a WCDMA Cell.1IdentificationOperation and MaintenanceRAC RNC, EM RNC, RACApp RAC, RNC -> OMS topology, RNC -> OMS topology UI0...63, step 1-Default value is not possibleinternal_value = gui_valueMandatoryNot modifiableADJI creation and deletionadji_id_tADJI1337Cell IdentifierAdjiCICell Identity; C-IdNumberlangCheckedAn inter-frequency neighbour cell is identified with the UTRAN Cell Identifier, which is composed of the Global RNC Identifier and the Cell Identifier.

The modification is not possible if the new target cell is under the controlling RNC. Cross-check between RNC, WCEL and ADJI objects is required.This parameter identifies the inter-frequency neighbour cell within a RNC.1Handover Control, Mobile Device ControlHCConfigurationRadio Resource UtilisationRNC UE, RAC RNC, EM RNC, Planner RAC, RNC -> OMS topology, RNC -> OMS topology UI1...65535, step 1-Default value is not possible.internal_value = gui_valueMandatoryOn-line3GPP Reference: TS 25.423, UTRAN Iur interface RNSAP Signalling (public), 3GPP Reference: TS 25.331, RRC Protocol Specification (public), 3GPP Reference: TS 25.401, UTRAN Overall Description (public), Nokia reference: Handover Control SFS, v.2.0.2 (internal)c_id_tADJI1338Primary CPICH powerAdjiCPICHTxPwrPrimary CPICH powerNumberapprovedThis parameter indicates the transmission power level of the Primary CPICH (Common Pilot Channel) of the inter-frequency neighbour cell.Parameter indicates the transmission power level of the Primary CPICH (Common Pilot Channel) of the inter-frequency neighbour cell.1Handover ControlPtxPrimaryCPICH of WCEL - If the target cell is in the same RNC, ADJI- Primary CPICH power shall have the same value as WCEL-Transmission power of the primary CPICH channel parameter of the target cell. (public)The modification is always possible except if the new target cell is existing in local RNC. In this case the modification is done via the WCEL object. Cross-check between RNC, WCEL and ADJI objects is required.HCConfigurationRadio Resource UtilisationRAC RNC, EM RNC, Planner RAC-10...50 dBm, step 0.1 dBm-internal_value = gui_value * 10MandatoryOn-lineADJI creation and modification (with restrictions)Nokia reference: Handover Control SFS v.2.0.2 (internal), 3GPP Reference: TS 25.433 UTRAN Iub Interface NBAP Signalling (public)ptx_pri_cpich_tADJI7130NCHO activity of common load measurement DRNC cellAdjiComLoadMeasDRNCCellNCHOEnumerationlangCheckedThis parameter controls the activity of common load measurement of certain inter-frequency neighbour cell that is controlled by the DRNC. The measurement is controlled over Iur by using RNSAP signalling.

The measurement is used to detect whether non-critical handovers are possible. If common load measurement is activated, the measurement is event based (event A and event B), and the following RNC configuration parameters define the measurement: NCHOThrComLoadMeasDRNCCell, NCHOHystComLoadMeasDRNCCell, and NCHOFilterCoeffComLoadMeasDRNCCell.

Value 1 of the parameter means that the measurement is activated. Note that the DRNC may reject activation due to capacity reasons or if it does not support this measurement.

"Non-critical handovers" are, for example, service and UE capability type handovers. Service and load based handover and Multi-Band Load Balancing make use of this parameter.This parameter controls the activity of common load measurement of certain inter-frequency neighbour cell that is controlled by the DRNC.1Admission Control, Handover ControlNCHOFilterCoeffComLoadMeasDRNCCell of RNMOBI - This parameter defines the filter coefficient for the common load measurements. (public)NCHOHystComLoadMeasDRNCCell of RNMOBI - This parameter defines the hysteresis time for the common load measurements. (public)NCHOThrComLoadMeasDRNCCell of RNMOBI - This parameter defines the load threshold for the common load measurements. (public)HCConfigurationRadio Resource UtilisationEM RNC, RAC RNC, RAC RACAppNot activated (0), Activated (1)Not activated (0)As a default measurement is not activated.MandatoryOn-lineLoad and Service Based Inter-System/Inter-Frequency Handover3GPP Reference: TS 25.423 V4.4.0 (public), Nokia reference: Handover Control SFS: Service and load based IS/IF handover (public), NSN reference: RAN2172 Multi-Band Load Balancing EFS (internal)adji_clm_drnc_cell_slho_tADJI3625CPICH EcNo offset for the non-critical HO procedureAdjiEcNoOffsetNCHONumberapprovedThis parameter defines CPICH EcNo offset for the non-critical inter-frequency handover procedure.

If the measured frequency includes a cell that is blocked in the non-critical handover procedure, the handover to the selected target cell can be done if the blocked cell is not inside the soft handover range of the target cell.

A cell is not inside the soft handover range if the measured EcNo of the best target cell subtracted with the value of this parameter is higher than measured EcNo value of the blocked cell. EcNo offset of the target cell is used in the calculation.

"Non-critical handovers" are, for example, service and UE capability type handovers. Service and load based handover make use of this parameter.This parameter defines CPICH EcNo offset for the load and service based handover procedure.1Handover ControlHCConfigurationRadio Resource UtilisationRAC RNC, EM RNC, RAC RACApp0...20 dB, step 0.5 dB6 dBinternal_value = gui_value * 2MandatoryOn-lineLoad and Service Based Inter-System/Inter-Frequency HandoverNokia reference: RAN2 HC SFS. (internal)adji_ec_no_offset_slho_tADJI3626Handling of blocked IF neighbour cell in SLHO procedureAdjiHandlingBlockedCellSLHOEnumerationapprovedThis parameter defines if an inter-frequency neighbour cell that is blocked from the service- and load-based handover procedure blocks all inter-frequency neighbour cells in that WCDMA frequency from the SLHO procedure.

If the parameter has the value 0 and the cell is blocked from the SLHO procedure, all inter-frequency neighbour cells in the WCDMA frequency are removed from the list of possible handover targets in the SLHO procedure.

If the parameter has the value 1 and the cell is blocked from the SLHO procedure, RNC measures this WCDMA frequency in a normal manner. A handover to the selected target cell can be done if the blocked cell is not inside the soft handover range. The soft handover range for each target cell is defined with the RNP parameter AdjiEcNoOffsetNCHO.This parameter defines whether cell which is blocked from the load and service based handover procedure causes blocking of that whole carrier from the procedure.1Handover ControlAdjiEcNoOffsetNCHO of ADJI - This parameter defines the soft handover range of the target cell. (public)HCMeasurementsRadio Resource UtilisationRAC RNC, EM RNC, RAC RACAppAll cells in that frequency are blocked (0), Frequency is measured (1)All cells in that frequency are blocked (0)As a default all cells in that frequency are blocked if this cell is blocked.MandatoryOn-lineLoad and Service Based Inter-System/Inter-Frequency HandoverNokia reference: Handover control SFS: Service and load based IS/IF handover. (internal)adji_handl_bl_cell_slho_tADJI1339Location Area CodeAdjiLACLocation Area Code; LACNumberapprovedPLMN Identifier and Location Area Code (LAC) determine the Location Area (LAI) to which the inter-frequency neighbour cell belongs to.Parameter contains the Location Area Code (LAC) of inter-frequency neighbour cell.1Handover Control, Mobile Device ControlLAC of WCEL - If the target cell is in the same RNC, ADJI- Location Area Code shall have the same value as WCEL-Location Area Code parameter of the target cell. (public)HCConfigurationRadio Resource UtilisationRNC UE, RNC MSC, RAC RNC, EM RNC, Planner RAC, RNC -> OMS topology, RNC -> OMS topology UI1...65535, step 1-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJI creation and modification (with restrictions). The modification is not possible if the neighbour cell is controlled by the local RNC.3GPP Reference: TS 23.003, Numbering, addressing and identification (public), Nokia reference: Handover Control SFS, v.2.0.2 (internal), 3GPP Reference: TS 25.331, RRC Protocol Specification (public), 3GPP Reference: TS 25.413, UTRAN Iu Interface RANAP Signalling (public), 3GPP Reference: TS 25.423, UTRAN Iur interface RNSAP Signalling (public)lac_tADJI1340Mobile Country CodeAdjiMCCMobile Country Code; MCCNumberlangCheckedAn inter-frequency neighbour cell is identified with UTRAN Cell Identifier which is composed of Global RNC Identifier and Cell Identifier. Furthermore, Global RNC Identifier is composed of RNC Identifier and PLMN Identifier, which in turn consists of Mobile Country Code (MCC) and Mobile Network Code (MNC).

The modification is not possible if the new target cell is under the controlling RNC. Cross-check between RNC, WCEL and ADJI objects is required.Unique country identification of inter-frequency neighbour cell.1Handover Control, Mobile Device ControlSIB18HCConfigurationRadio Resource UtilisationRNC UE, RNC MSC, RAC RNC, EM RNC, Planner RAC, RNC -> OMS topology, RNC -> OMS topology UI0...999, step 1-Default value is not possible.internal_value = gui_valueMandatoryOn-line3GPP Reference: TS 25.413, UTRAN Iu Interface RANAP Signalling (public), 3GPP Reference: TS 25.331, RRC Protocol Specification (public), Nokia reference: Handover Control SFS, v.2.0.2 (internal), 3GPP Reference: TS 23.003, Numbering, addressing and identification (public), 3GPP Reference: TS 25.423, UTRAN Iur interface RNSAP Signalling (public)mcc_tADJI1341Mobile Network CodeAdjiMNCMobile Network Code; MNCNumberlangCheckedAn inter-frequency neighbour cell is identified with UTRAN Cell Identifier, which is composed of Global RNC Identifier and Cell Identifier. Furthermore, Global RNC Identifier is composed of RNC Identifier and PLMN Identifier, which in turn consists of Mobile Country Code (MCC) and Mobile Network Code (MNC).

The modification is not possible if the new target cell is under the controlling RNC. Cross-check between RNC, WCEL and ADJI objects is required.Unique network identification of inter-frequency neighbour cell within country.1Handover Control, Mobile Device ControlSIB18AdjiMNCLength of ADJI - Value range depends from the AdjiMNCLength: 00..99 (if AdjiMNCLength is 2) or 000..999 (if AdjiMNCLength is 3). (public)HCConfigurationRadio Resource UtilisationRNC MSC, RAC RNC, EM RNC, Planner RAC, RNC -> OMS topology, RNC -> OMS topology UI0...999, step 1-Default value is not possible.internal_value = gui_valueMandatoryOn-lineNokia reference: Handover Control SFS, v.2.0.2 (internal), 3GPP Reference: TS 25.413, UTRAN Iu Interface RANAP Signalling (public), 3GPP Reference: TS 23.003, Numbering, addressing and identification (public), 3GPP Reference: TS 25.423, UTRAN Iur interface RNSAP Signalling (public)mnc_tADJI1342Mobile Network Code LengthAdjiMNCLengthEnumerationlangCheckedThe parameter defines whether 2 or 3 digits are used in the Mobile Network Code (MNC).

When this parameter is modified, also the value of the MNC used by the system is always changed.

The modification is not possible if the new target cell is under the controlling RNC. Cross-check between RNC, WCEL and ADJI objects is required.The parameter defines whether 2 or 3 digits are used in the Mobile Network Code.1SIB11, SIB12, SIB18AdjiMNC of ADJI - The value range of Mobile Network Code depends on the value of Mobile Network Code Length (AdjiMNCLenth). (public)HCConfigurationRadio Resource UtilisationRAC RNC, EM RNC2 digits (2), 3 digits (3)2 digits (2)MandatoryOn-line3GPP Reference: TS 25.413, UTRAN Iu Interface RANAP Signalling (public), 3GPP Reference: TS 25.331, RRC Protocol Specification (public)mnc_tADJI28644ADJI HSPA Cell for Non Critical HandoverAdjiNCHOHSPASupportEnumerationlangCheckedThis parameter indicates whether the neighbouring cell provides the HSPA support for non-critical handovers.This parameter indicates whether the neighbouring cell provides the HSPA support for non-critical handovers.1Handover ControlHCConfigurationRadio Resource UtilisationRAC RNC, EM RNC, RAC RACAppNo HSPASupport (0), HSPASupport (1)No HSPASupport (0)The neighbouring cell does not support HSPA.OptionalOn-lineADJI creation, modification (with restrictions) and deletionHSDPA inter-frequency handoverNSN reference: RAN 1596 HSPA Capability Based Handover EFS (internal), NSN reference: RAN1676 EFS (internal)adji_ncho_hspa_sup_tADJI1343Routing Area CodeAdjiRACRouting Area Code; RACNumberapprovedLocation Area (LAI) and Routing Area Code (RAC) determine the Routing Area to which the inter-frequency neighbour cell belongs to.This parameter contains the Routing Area Code (RAC) of the inter-frequency neighbour cell.1Handover Control, Mobile Device ControlRAC of WCEL - If the target cell is in the same RNC, ADJI- Routing Area Code shall have the same value as WCEL-Routing Area Code parameter of the target cell. (public)HCConfigurationRadio Resource UtilisationRNC MSC, RAC RNC, EM RNC, Planner RAC, RNC -> OMS topology, RNC -> OMS topology UI0...255, step 1-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJI creation and modification (with restrictions). The modification is not possible if the neighbour cell is controlled by the local RNC.Nokia reference: Handover Control SFS, v.2.0.2 (internal), 3GPP Reference: TS 25.423, UTRAN Iur interface RNSAP Signalling (public), 3GPP Reference: TS 25.413, UTRAN Iu Interface RANAP Signalling (public)rac_tADJI1344RNC IdentifierAdjiRNCidRNC Identifier; RNC-IdNumberlangCheckedAn inter-frequency neighbor cell is identified with UTRAN Cell Identifier, which is composed of Global RNC Identifier and Cell Identifier. Global RNC Identifier is composed of PLMN Identifier and RNC Identifier.

The modification is not possible if the new target cell is under the controlling RNC. Cross-check between RNC, WCEL, and ADJI objects is required.

For RAN 2054 feature Extension of RNC ids only, extended range of 4096..65534 will be used , otherwise older range 1..4095 will be used as this extended range violates 3GPP specifications.A unique identification for an RNC node within the UTRAN to which the inter-frequency neighbor cell belongs.1Handover Control, Mobile Device ControlHCConfigurationRadio Resource UtilisationRNC MSC, RAC RNC, EM RNC, Planner RAC, RNC -> OMS topology, RNC -> OMS topology UI1...65534, step 1-Default value is not possible.internal_value = gui_valueMandatoryOn-lineNokia reference: Handover Control SFS, v.2.0.2 (internal), 3GPP Reference: TS 25.413, UTRAN Iu Interface RANAP Signalling (public), 3GPP Reference: TS 25.423, UTRAN Iur interface RNSAP Signalling (public), NSN reference: RAN2054 Extension of RNC-ids EFS (internal)rnc_id_tADJI1345Include in System InformationAdjiSIBEnumerationlangCheckedThis parameter indicates whether the inter-frequency neighbour cell is included in the System Information Block 11&12&18 for the cell selection and re-selection procedures. The inter-frequency neighbour cell is included in the system information when the value of the parameter is "SIB". The inter-frequency neighbour cell is included in the extended system information when the value of the parameter is "SIBbis".

The maximum number of inter-frequency neighbour cells that can be included in the System Information Block 11&12&18 is 32. The neighbouring cells can be distributed to up to two FDD carriers (ref. 3GPP TS 25.133).

The total number of intra-frequency, inter-frequency and GSM neighbour cells, which can be included in the System Information Block type 11 (SIB11), is 47. When HCS is used, the capacity is limited to 35 cells.

System Information Block type 11bis (SIB11bis) increases the maximum number of adjacencies to 96. SIB11bis can only be decoded by the UEs which support 3GPP R6.

If the total number of intra-frequency, inter-frequency and GSM neighbour cells, which are included in the System Information, exceeds the physical size of SIB data, the NBAP interface is not able to pack the neighbour cell information into the SIB data and the scheduling of the system information blocks fails. The cell is blocked by the system and an alarm 7771 WCDMA CELL OUT OF USE (BCCH scheduling error) is reported for the cell.

Note: The parameter AdjiSIB does not affect inter-frequency measurements in CELL_DCH state of connected mode. That is, all inter-frequency neighbour cells are monitored for the inter-frequency handover regardless of the value of the parameter AdjiSIB.Parameter indicates whether the inter-frequency neighbour cell is included in the System Information for the cell selection and re-selection procedures.1Handover ControlSIB11, SIB12, SIB18, SIB11bisAdjsSIB of ADJS - The parameter indicates whether the intra-frequency neighbour cell is included in the system information for the cell selection and re-selection procedures. (public)AdjgSIB of ADJG - The parameter indicates whether the GSM neighbour cell is included in the system information for the cell selection and re-selection procedures. (public)HCConfigurationRadio Resource UtilisationRAC RNC, EM RNC, RACApp RACNo (0), SIB (1), SIBbis (2)SIB (1)The inter-frequency neighbour cell is included in the SIB.MandatoryOn-lineADJI creation and modificationExtension of sib11Nokia reference: Handover Control SFS v.2.0.2 (internal), NSN reference: RAN1323: Extension of Sib11 (internal)int_freq_ncell_sib_tADJI1346Primary Scrambling CodeAdjiScrCodePrimary scrambling codeNumberapprovedDefines the downlink scrambling code of the Primary CPICH (Common Pilot Channel) of the inter-frequency neighbour cell.This parameter defines the downlink scrambling code of the Primary CPICH (Common Pilot Channel) of the inter-frequency neighbour cell.1Handover Control, Mobile Device ControlSIB11, SIB12PriScrCode of WCEL - Primary Scrambling Code and UTRA RF Channel Number combination of an inter-frequency neighbour cell must be unique within inter-frequency neighbour cells. The modification is always possible except if the new target cell is existing in the local RNC. In this case the modification is done via the WCEL object. Cross-check between RNC, WCEL and ADJI objects is required. (public)HCConfigurationRadio Resource UtilisationRNC UE, RAC RNC, EM RNC, Planner RAC0...511, step 1-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJI creation and modification (with restrictions)3GPP Reference: TS 25.331, RRC Protocol Specification (public), Nokia reference: Handover Control SFS, v.2.0.2 (internal)dl_pri_scr_code_tADJI1347Tx Diversity IndicatorAdjiTxDivTx Diversity IndicatorEnumerationapprovedIndicates, whether the Primary CPICH of the inter-frequency neighbour cell is broadcast from two antennas. If the Primary CPICH is broadcast from two antennas, the UE measures the received code power from each antenna separately, and sums the measurement results together in order to get the total received code power on the Primary CPICH.Parameter indicates whether the Primary CPICH of the inter-frequency neighbour cell is broadcasted from two antennas1Handover Control, Mobile Device ControlSIB11, SIB12The value must always be 0 (not used) if the inter-frequency neighbour cell is controlled by the local RNC; cross-check between RNC, WCEL and ADJI objects is required.HCConfigurationRadio Resource UtilisationRNC UE, RAC RNC, EM RNC, RACApp RACTx Diversity not used (0), Tx Diversity in use (1)Tx Diversity not used (0)MandatoryOn-lineADJI creation and modification (with restrictions)3GPP Reference: TS 25.331, RRC Protocol Specification (public), Nokia reference: Handover Control SFS, v.2.0.2 (internal)tx_diversity_ind_tADJI1348Maximum UE TX Power on DPCHAdjiTxPwrDPCHMaximum allowed UL TX powerNumberapprovedThis parameter indicates the maximum transmission power level that a UE may use on the DPCH in the neighbouring cell. The RNC uses the parameter in the decision algorithm of the inter-frequency handover. If the maximum output power of the UE is lower than the value of the parameter, the RNC adds the power difference (dB value) to the minimum required CPICH RSCP level, which the measurement result of the neighbour cell must exceed before the handover is possible.This parameter indicates the maximum transmission power level that a UE may use on the DPCH in the neighbouring cell.1Handover ControlAdjiMinRSCP of HOPI - Determines the minimum required CPICH RSCP level which the averaged measurement result of the best inter-frequency neighbour cell must exceed before the quality reason inter-frequency handover is possible. (public)UEtxPowerMaxDPCH of WCEL - Defines the maximum transmission power level a UE can use on DPCH. If the target cell is in the same RNC, ADJI-Maximum UE TX Power on DPCH shall have the same value as WCEL-Maximum UE transmission power on DPCH parameter of the target cell. (public)HCConfigurationRadio Resource UtilisationRAC RNC, EM RNC-50...33 dBm, step 1 dBm-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJI creation and modification (with restrictions). The modification is not possible if the neighbour cell is controlled by the local RNC.3GPP Reference: TS 25.331 RRC Protocol Specification (public), Nokia reference: Handover Control SFS v.2.0.2 (internal), Nokia reference: Admission Control SFS v.2.0.0 (internal)tx_power_dpch_tADJI1349Maximum UE TX Power on RACHAdjiTxPwrRACHMaximum allowed UL TX power; UE_TXPWR_MAX_RACHNumberapprovedThis parameter indicates the maximum transmission power level that a UE can use when accessing the neighbouring cell on the RACH. The UE uses the parameter in the cell re-selection procedure. If the maximum output power of the UE is lower than the value of the parameter, the UE adds the power difference (dB value) to the minimum required CPICH Ec/No level, which the measurement result of the neighbouring cell must exceed before the cell re-selection is possible.Indicates the maximum transmission power level that a UE can use when accessing the neighbouring cell on the RACH.1Mobile Device ControlSIB11, SIB12UEtxPowerMaxPRACH of WCEL - The modification is always possible except if the new target cell is existing in the local RNC. In this case the modification is done via the WCEL object. Cross-check between RNC, WCEL and ADJI objects is required. (public)HCConfigurationRadio Resource UtilisationRNC UE, RAC RNC, EM RNC-50...33 dBm, step 1 dBm-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJI creation and modification (with restrictions)Nokia reference: Handover Control SFS v.2.0.2 (internal), 3GPP Reference: TS 25.331, RRC Protocol Specification (public), 3GPP Reference: TS 25.304, UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode (public)tx_power_prach_tADJI1350UTRA Absolute Radio Frequency Channel NumberAdjiUARFCNUARFCNNumberlangCheckedThis parameter defines the UTRA Absolute Radio Frequency Channel Number of the inter-frequency neighbour cell.

This parameter defines the downlink channel number and the downlink carrier frequency. The RNC calculates the uplink carrier frequency and the uplink channel number from the downlink carrier frequency and the duplex distance used in the RF band.

RF band I: Allowed DL channel numbers are 10562-10838.

RF band II: Allowed DL channel numbers are 9662-9938. In the US allowed DL channel numbers are 9663-9712, 9763-9812, and 9888-9937. Allowed additional DL channel numbers are 412, 437, 462, 487, 512, 537, 562, 587, 612, 637, 662, and 687.

RF band III: Allowed DL channel numbers are 1162-1513.

RF band IV: Allowed DL channel numbers are: 1537-1738. Allowed additional DL channel numbers are 1887, 1912, 1937, 1962, 1987, 2012, 2037, 2062, and 2087.

RF band V : Allowed DL channel numbers are 4357-4458. Allowed additional DL channel numbers are 1007, 1012, 1032, 1037, 1062, and 1087.RF band VI: Allowed DL channel numbers are 4387 - 4413. Allowed additional DL channel numbers are 1037 and 1062.RF band VII: Allowed DL channel numbers are 2237 - 2563. Allowed additional DL channel numbers are 2587, 2612, 2637, 2662, 2687, 2712, 2737, 2762, 2787, 2812, 2837, 2862, 2887 and 2912.

RF band VIII: Allowed DL channel numbers are: 2937-3088.

RF band IX: Allowed DL channel numbers are 9237-9387.RF band X: Allowed DL channel numbers are 3112-3388. Allowed additional DL channel numbers are 3412, 3437, 3462, 3487, 3512, 3537, 3562, 3587, 3612, 3637, 3662 and 3687.RF band XI: Allowed DL channel numbers are 3712-3812.RF band XII: Allowed DL channel numbers are 3837 - 3903. Allowed additional DL channel numbers are 3927, 3932, 3957, 3962, 3987 and 3992.RF band XIII: Allowed DL channel numbers are 4017 - 4043. Allowed additional DL channel numbers are 4067 and 4092.RF band XIV: Allowed DL channel numbers are 4117 - 4143. Allowed additional DL channel numbers are 4167 and 4192. RF band XIX: Allowed DL channel numbers are 712 - 763. Allowed additional DL channel numbers are 787, 812 and 837

Note UEs that support band XIX should also support band VI RF requirements and signalling requirements. Note that if the UE is on a network with MCC set to Japan then it assumes that any DL UARFCN sent by the network from the overlapping region of Band V and Band VI is from Band VI. If the UE is on a network with a MCC other than Japan then it assumes that any DL UARFCN sent by the network from the overlapping region of Band V and Band VI is from Band V.Downlink carrier frequency of the adjacent WCDMA RAN cell.1Handover ControlSIB11, SIB12UARFCN of WCEL - If the target cell is in the same RNC, ADJI- UTRA Absolute Radio Frequency Channel Number shall have the same value as WCEL-UTRA Absolute Radio Frequency Channel Number parameter of the target cell. (public)HCConfigurationRadio Resource UtilisationRNC UE, RAC RNC, EM RNC, Planner RAC0...16383, step 1-Default value is not possible.internal_value = gui_valueMandatoryOn-lineADJI creation and modification (with restrictions). The modification is not possible if the neighbor cell is controlled by the local RNC.WCDMA 1900 OR WCDMA 850 OR WCDMA 1700 & 1800 OR WCDMA 1700/2100 OR WCDMA 900 OR Full WCDMA 1900 UARFCN range3GPP Reference: TS 25.331, RRC Protocol Specification (public), 3GPP Reference: TS 25.423, UTRAN Iur interface RNSAP Signalling (public), NSN reference: Handover Control SFS (internal), 3GPP Reference: TS 25.101, UE Radio Transmission and Reception (FDD) (public)uarfcn_tADJI63513Blind HO target cellBlindHOTargetCellEnumerationlangCheckedThis parameter indicates whether the neighbor cell is defined as a target cell for inter-frequency blind handover. Only one target cell per frequency can be defined.This parameter indicates whether the neighbor cell is defined as a target cell for inter-frequency blind handover.1Handover ControlAdjiRNCid of ADJI - The system checks that the target cell RNC id (AdjiRNCid) is the same as the source cell RNC id (RNCid). (public)HCConfigurationRadio Resource UtilisationRAC RNC, EM RNC, RACApp RACdisabled (0), enabled (1)disabled (0)The target cell of this adjacency is not used as a target for Blind HO.OptionalOn-lineMulti-Band Load BalancingNSN reference: RAN2172 Multi-Band Load Balancing EFS (internal)blho_target_cell_tADJI1352NRT HOPI IdentifierNrtHopiIdentifierNumberapprovedDefines the parameter set (HOPI object) which controls the inter-frequency handover of a non-real time (NRT) radio bearer to the neighbouring cell.Parameter defines the parameter set (HOPI object) which controls the inter-frequency handover of a non-real time (NRT) radio bearer to the neighbouring cell1Handover ControlSIB11, SIB12, SIB18HOPIId of HOPI - Check that the relevant HOPI object exists in the database. (public)HCConfigurationRadio Resource UtilisationRAC RNC, EM RNC, RACApp RAC, RNC -> OMS topology, RNC -> OMS topology UI1...100, step 1-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJI creation and modificationNokia reference: Handover Control SFS v.2.0.2 (internal)hopi_id_tADJI1353RT HOPI IdentifierRtHopiIdentifierNumberapprovedDefines the parameter set (HOPI object) which controls the inter-frequency handover of a real time (RT) radio bearer to the neighbouring cell.Parameter defines the parameter set (HOPI object) which controls the inter-frequency handover of a real time (RT) radio bearer to the neighbouring cell1Handover ControlSIB11, SIB12, SIB18HOPIId of HOPI - Check that the relevant HOPI object exists in the database. (public)HCConfigurationRadio Resource UtilisationRAC RNC, EM RNC, RACApp RAC, RNC -> OMS topology, RNC -> OMS topology UI1...100, step 1-Default value is not possibleinternal_value = gui_valueMandatoryOn-lineADJI creation and modificationNokia reference: Handover Control SFS v.2.0.2 (internal)hopi_id_tADJL49590Change originADJLChangeOriginEnumerationlangCheckedThe parameter defines the origin of the last configuration action affecting the object.The parameter defines the origin of the last configuration action affecting the object.1Operation and MaintenanceRNC -> RAC, RNC -> EMNot defined (0), Network originated configuration action (1), NetAct RNW plan originated configuration action (2), Element Manager originated configuration action (3), Configuration action by automatic tuning function (4), Element Manager originated mass config action (5), NetAct originated direct RNW change (6)-Value is set by the systemValue set by the systemNot modifiableLTE Interworking-Cell Reselection to LTEchange_origin_tADJL49589Identifier of inter- system adjacency to LTEADJLIdNumberlangCheckedThis parameter is an identification of ADJL within a WCDMA cell.This parameter is an identification of ADJL within a WCDMA cell.1IdentificationOperation and MaintenanceRAC RNC, EM RNC, RACApp RAC, RNC -> OMS topology, RNC -> OMS topology UI0...7, step 1-internal_value = gui_valueMandatoryNot modifiableADJL creationLTE Interworking-Cell Reselection to LTEadjl_id_tADJL49591E-UTRA Absolute Radio Frequency Channel NumberAdjLEARFCNEARFCNNumberlangCheckedThis parameter defines the E-UTRA Absolute Radio Frequency Channel Number of the neighboring E-UTRA frequency. This parameter defines the EARFCN of the downlink carrier frequency.This parameter defines the E-UTRA Absolute Radio Frequency Channel Number of the neighboring E-UTRA frequency. This parameter defines the EARFCN of the downlink carrier frequency.1Handover Control, Mobile Device ControlSIB19SystemInfoRadio Resource UtilisationRAC RNC, EM RNC, RACApp RAC, RNC -> OMS topology, RNC -> OMS topology UI0...65535, step 1-internal_value = gui_valueMandatoryOn-lineADJL creation and modificationLTE Interworking-Cell Reselection to LTEeuarfcn_tADJL49592Measurement BandwidthAdjLMeasBwMeasurement BandwidthEnumerationlangCheckedThis parameter indicates the measurement bandwidth information common for all neighboring E-UTRA cells on the carrier frequency. It is defined by the parameter Transmission Bandwidth Configuration, NRB [36.104]. The values indicate the number of resource blocks over which the UE could measure.This parameter indicates the measurement bandwidth information common for all neighboring E-UTRA cells on the carrier frequency.1SIB19SystemInfoTelecomRAC RNC, EM RNC, RACApp RAC6 (6), 15 (15), 25 (25), 50 (50), 75 (75), 100 (100)6 (6)Minimum value.OptionalOn-lineADJL creation and modificationLTE Interworking-Cell Reselection to LTEadjl_meas_bwidth_tADJL49593HOPL IdentifierHopLIdentifierNumberlangCheckedDefines the parameter set (HOPL object) which controls the inter-RAT handover of idle and connected mode UEs to the E-UTRA neighbor cell during cell reselection procedure.Defines the parameter set (HOPL object) which controls the inter-RAT handover of idle and connected mode UEs to the E-UTRA neighbor cell during cell reselection procedure.1Handover ControlHOPLId of HOPL - Check if the relevant HOPL object exists in the database. (internal)HCConfigurationRadio Resource UtilisationRAC RNC, EM RNC, RACApp RAC, RNC -> OMS topology, RNC -> OMS topology UI1...10, step 1-internal_value = gui_valueMandatoryOn-lineLTE Interworking-Cell Reselection to LTEhopl_id_tADJS1354Change originADJSChangeOriginEnumerationapprovedThe parameter defines the origi