UTRAN Release Operational Impacts (Features, Counters... )

NN-20500-044
UTRAN Release UMTS5.0

UMTS5.0 01.02/ EN
Operational
March 2006
Impacts
Preliminary
UTRAN RELEASE OPERATIONAL IMPACTS UMTS5.0

Document number: Document issue: Document status: Product Release: Date: NN-20500-044 01.02/ EN Preliminary UMTS5.0 March 2006
Copyright 2003-2005 Nortel Networks, All Rights Reserved Originated in France NORTEL CONFIDENTIAL The information contained in this document is the property of Nortel Networks. Except as specifically authorized in writing by Nortel Networks, the holder of this document shall keep the information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties and use same for evaluation, operation and maintenance purposes only. The content of this document is provided for information purposes only and is subject to modification. It does not constitute any representation or warranty from Nortel Networks as to the content or accuracy of the information contained herein, including but not limited to the suitability and performances of the product or its intended application. This is the Way. This is Nortel, Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks. All other trademarks are the property of their owners.
Nortel Confidential
Publication history
PUBLICATION HISTORY
MARCH 2006
Issue 01.02 / EN, Preliminary Update after review
FEBRUARY 2006
Issue 01.01 / EN, Draft Document creation
Copyright 2003-2005 Nortel Networks
UTRAN Release Operational Impacts - UMTS5.0
Nortel Confidential
Publication history
ii
NN-20500-044
01.02/EN
Preliminary
March 2006
Copyright 2004 Nortel Networks
Nortel Confidential
Table of contents
iii
TABLE OF CONTENTS
1. INTRODUCTION .........................................................................................................................1 1.1. 1.2. 1.3. 2. OBJECT .................................................................................................................................1 APPLICABILITY .......................................................................................................................1 AUDIENCE .............................................................................................................................1
RELATED DOCUMENTS............................................................................................................1 2.1. 2.2. APPLICABLE DOCUMENTS........................................................................................................1 REFERENCE DOCUMENTS .......................................................................................................1
3.
UA04.2 FEATURES ....................................................................................................................3 3.1. 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5 3.1.6 3.1.7 3.2. 3.3. UA04.2 FEATURE IMPACT LIST ...............................................................................................3 PERFORMANCE AND CAPACITY FEATURE IMPACT LIST .......................................................4 TRANSMISSION AND TRANSPORT CAPABILITY FEATURE IMPACT LIST ..................................5 SECURITY FEATURE IMPACT LIST .....................................................................................5 RADIO MOBILITY FEATURE IMPACT LIST ...........................................................................6 RESOURCE MANAGEMENT AND OPTIMIZATION / SERVICES FEATURE IMPACT LIST................7 OPERATIONAL EFFECTIVENESS FEATURE IMPACT LIST ......................................................8 COMPLIANCE FEATURE IMPACT LIST ................................................................................8 FEATURE 13451 - 3G TO 2G REDIRECTION FOR SPEECH CALLS ................................................9 FEATURE 24082 - MSA32 ENHANCEMENT TO SUSTAIN 28E1 WITH IMA ...................................10
3.4. FEATURE 25100 - UTRAN CALL TRACE: ADDITIONAL MEASUREMENT REPORTING (NBAP COMMON MEASUREMENT, RRC BLER, ETC..).....................................................................................10 3.5. 3.6. 3.7. 3.8. 3.9. 3.10. 3.11. 3.12. 3.13. 3.14. 3.15. 3.16. 3.17. 3.18. 3.19. 3.20. FEATURE 26234 - NODE B SUPPORT OF 2 OAM IP ADDRESSES ..............................................10 FEATURE 26407 - IPSEC SUPPORT VALIDATION ON RNC.........................................................11 FEATURE 26409 - SUPPORT OF RADIUS CLIENT ON RNC........................................................14 FEATURE 26521 - RNC SUPPORTS QAAL2 ALTERNATE ROUTING ...........................................15 FEATURE 26614 - RNC SUPPORTS QAAL2 ALTERNATE ROUTING ...........................................18 FEATURE 27219 - INTRA-FREQUENCY EVENT-TRIGGERED MEASUREMENTS ..............................19 FEATURE 27330 - RB ADAPTATION BASED ON TRAFFIC: DL AND UL WITH START @64KBIT/S .....19 FEATURE 27597 - SERVICE-BASED INTER-FREQ/INTER-RAT SELECTION FOR HHO ...................23 FEATURE 27639 - PP7K OPTICAL STM-1 CHANNELIZED CARD IN POC ....................................23 FEATURE 27729 - UA04.2 COUNTERS EVOLUTION .................................................................25 FEATURE 27740 - IUB LOAD IN IRM .......................................................................................25 FEATURE 27901 - UA04.2 PARAMETER EVOLUTION ...............................................................26 FEATURE 27930 - HSDPA SERVICE .....................................................................................26 FEATURE 27931 - HSDPA FLEXIBLE RESOURCE MANAGEMENT ..............................................27 FEATURE 27932 - HSDPA STEP 1........................................................................................27 FEATURE 27935 - MULTI-CARRIER HSDPA TRAFFIC SEGMENTATION .......................................28
Nortel Networks Confidential
iv
3.21. 3.22. 3.23. 3.24. 3.25. 3.26. 3.27. 3.28. 3.29. 3.30. 3.31. 3.32. 3.33. 3.34. 3.35. 3.36. 3.37. 3.38. 3.39. 3.40. 3.41. 3.42. 4.
FEATURE 27936 - HSDPA INTRA-FREQUENCY MOBILITY ........................................................29 FEATURE 27937 - HSDPA ALARM MOBILITY..........................................................................30 FEATURE 27939 - HS-SCCH POWER CONTROL ....................................................................31 FEATURE 27940 - H-BBU POOL ACROSS SECTORS ...............................................................32 FEATURE 27941 - NODE B MODULE OPERATION FOR HSDPA ................................................33 FEATURE 27942 - ALWAYS-ON ON HSDPA ...........................................................................34 FEATURE 27943 - IUB BANDWIDTH LIMITATION HANDLING .......................................................35 FEATURE 27945 - HSDPA RADIO BEARERS ..........................................................................36 FEATURE 27947 - PS I/B UL:384 .........................................................................................36 FEATURE 28036 - MOBILITY PERFORMANCE IMPROVEMENTS ..................................................38 FEATURE 28040 - POWER CONTROL AND RATE MATCHING ENHANCEMENTS ............................38 FEATURE 28047 - CALL ESTABLISHMENT KPI IMPROVEMENTS ................................................39 FEATURE 28109 - UA04.2 - 3GPP BASELINE & ADDITIONAL CRS ............................................40 FEATURE 28144 - IRM SCHEDULING DOWNGRADING BASED ON TXCP .....................................41 FEATURE 28302 - Y-SPLITTER AT THE RNC ...........................................................................42 FEATURE 28330 - PS STREAMING UP TO 128KBIT/S ...............................................................43 FEATURE 28331 - PS STREAMING UP TO 128KBIT/S + PS I/B 8KBIT/S ......................................43 FEATURE 28847 - CHANGE OF SAI REPORTING ......................................................................43 FEATURE 28900 - STSR1+1 NODE B ...................................................................................44 FEATURE 29361 - HANDOVER AND RRM CONFCLASS RANGE EXTENSION ................................45 FEATURE 30038 - NODE B CAC: MAX HSDPA USERS PER NODE B ........................................45 FEATURE 30311 - RAB BASED CAC .....................................................................................46
ACCESS OAM05.0 FEATURES ...............................................................................................47 4.1. 4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 4.2. 4.3. 4.4. 4.5. 4.6. 4.7. 4.8. 4.9. 4.10. 4.11. ACCESS OAM05.0 FEATURE IMPACT LIST .............................................................................47 ACCESS OAM FAULT MANAGEMENT ..............................................................................47 ACCESS OAM CONFIGURATION MANAGEMENT ...............................................................48 ACCESS OAM PERFORMANCE MANAGEMENT .................................................................48 ACCESS OAM ADMINISTRATION AND SECURITY MANAGEMENT ........................................49 ACCESS OAM FEATURE ACTIVATION AND NETWORK RECONFIGURATION PROCEDURES ....49 FEATURE 26444 - RRM INSTANCES EXPLICIT NAMING............................................................50 FEATURE 27233 - SMART ACTIVATION ENHANCEMENTS...........................................................50 FEATURE 27360 - RNC AUDIT REPORT FILE NAMING EVOLUTION ..........................................50 FEATURE 27514 - CONTINUED CM/FM/PM FOR ACCESS ........................................................51 FEATURE 27517 - CALL TRACE CONFIGURATION WIZARD ENHANCEMENTS..............................52 FEATURE 27520 - UTRAN PERFORMANCE METRICS AND REPORTS ........................................53 FEATURE 27809 - W-NMS SUPPORT OF IPSEC TO RNC ........................................................53 FEATURE 27811 - W-NMS SUPPORT OF RADIUS AUTHENTICATION FOR RNC...........................54 FEATURE 28142 - UPGRADE PATH: UA4.0 UA4.2..............................................................54 FEATURE 28143 - UPGRADE PATH: UA4.1 UA4.2..............................................................55
NN-20500-044
01.02/EN
Preliminary
March 2006
Nortel Confidential
Table of contents
4.12. 4.13. 4.14. 4.15. 4.16. 4.17. 5.
FEATURE 28377 - MIGRATION RNC 1000 RNC 1500 UA4.2..............................................55 FEATURE 28536 - RECONFIGURATION PROCEDURES ..............................................................56 FEATURE 28538 - UTRAN CALL TRACE KPIS........................................................................56 FEATURE 28718 HSDPA ACTIVATION PROCEDURE .............................................................56 FEATURE 29109 - WPS CHECKS ..........................................................................................57 FEATURE 30266 - SHELF-LEVEL DISPLAY ZOOM IN / ZOOM OUT ..............................................58
PLATFORM...............................................................................................................................59 5.1. 5.2. 5.3. 5.4. 5.4.1 5.4.2 5.5. UA04.2 PLATFORM FEATURES ..............................................................................................59 OBSOLETE HARDWARE .........................................................................................................59 NEW HARDWARE ..................................................................................................................59 MODIFIED HARDWARE ...........................................................................................................60 HSDPA IMPACT ...........................................................................................................60 STSR1+1 IMPACT ........................................................................................................61 HARDWARE BASELINE ..........................................................................................................62
6.
COMPATIBILITY TABLE / UPGRADE PATH...........................................................................63 6.1. 6.2. UA04.2 COMPATIBILITY / UPGRADE PATH FEATURES ..............................................................63 SYSTEM UPGRADE PATHS & COMPATIBILITY MATRIX ...............................................................63
7. 8.
TOOLS ......................................................................................................................................64 FAULT MANAGEMENT ............................................................................................................65 8.1. 8.2. 8.3. 8.4. UA04.2 FAULT FEATURES ....................................................................................................65 OAM05.0 FAULT FEATURES .................................................................................................65 UA04.2 NEW/DELETED/MODIFIED ALARMS ............................................................................65 ALARM MANAGER WINDOW ...................................................................................................66
9.
CONFIGURATION MANAGEMENT..........................................................................................67 9.1. 9.2. 9.3. 9.4. UA04.2 CONFIGURATION FEATURES .....................................................................................67 OAM05.0 CONFIGURATION FEATURES ..................................................................................69 UA04.2 NEW/DELETED/MODIFIED PARAMETERS ....................................................................69 SMART ACTIVATION ..............................................................................................................69
10.
PERFORMANCE MANAGEMENT............................................................................................70 10.1. 10.2. 10.3. UA04.2 PERFORMANCE FEATURES .......................................................................................70 OAM05.0 PERFORMANCE FEATURES ....................................................................................70 UA04.2 NEW/DELETED/MODIFIED COUNTERS........................................................................71
11.
SYSTEM AND SECURITY MANAGEMENT .............................................................................72 11.1. 11.2. 11.3. UA04.2 SYSTEM AND SECURITY MANAGEMENT FEATURES .......................................................72 RNC SECURITY ...................................................................................................................72 NODE B AVAILABILITY ...........................................................................................................73
vi
12.
UPGRADE, PATCH AND MIGRATION MANAGEMENT..........................................................74 12.1. 12.2. 12.3. 12.4. 12.5. UA04.2 UPGRADE, PATCH AND MIGRATION MANAGEMENT FEATURES .......................................74 OAM05.0 UPGRADE, PATCH AND MIGRATION MANAGEMENT FEATURES ....................................74 GENERAL OPERATIONAL CONSTRAINTS .................................................................................74 OBSOLETE UPGRADE PROCEDURES.......................................................................................74 NEW UPGRADE PROCEDURES ...............................................................................................75
12.5.1 12.6.
411-8111-241: RNC 1500 SOFTWARE UPGRADE PROCEDURE USING OAM 5.0 (INTER RELEASE NEW MIB) .....................................................................................................................75 MODIFIED UPGRADE PROCEDURES ........................................................................................78
12.6.1 411-8111-240: NODE-B SOFTWARE UPGRADE PROCEDURE USING OAM 5.0 (INTRA UPGRADE)...................................................................................................................................78 12.6.2 411-8111-239: NODE-B SOFTWARE UPGRADE PROCEDURE USING OAM 5.0 (INTER UPGRADE)...................................................................................................................................80 12.6.3 411-8111-238: RNC 1000 SOFTWARE UPGRADE PROCEDURE USING OAM 5.0 TYPE 7 INTRA RELEASE ............................................................................................................................83 12.6.4 411-8111-237: RNC 1000 SOFTWARE UPGRADE PROCEDURE USING OAM 5.0 TYPE 6 INTRA RELEASE ............................................................................................................................86 12.6.5 411-8111-236: RNC 1000 SOFTWARE UPGRADE PROCEDURE USING OAM 5.0 TYPE 6 INTER RELEASE ..........................................................................................................................89 12.6.6 12.6.7 12.6.8 12.6.9 12.7. 13. 411-8111-243: RNC 1000 TO RNC 1500 MIGRATION PROCEDURE USING OAM 5.0 ........93 411-8111-232: RNC 1500 PATCHING PROCEDURES ......................................................96
411-8111-244: RNC 1500 SOFTWARE UPGRADE PROCEDURE USING OAM 5.0 (INTRA RELEASE CURRENT MIB)..............................................................................................................97 411-8111-242: RNC 1500 SOFTWARE UPGRADE PROCEDURE USING OAM 5.0 (INTRA RELEASE NEW MIB) .....................................................................................................................99 FEATURE ACTIVATION STATE AFTER AN UTRAN UPGRADE ......................................................101
INTERFACE CHANGES .........................................................................................................103 13.1. 13.2. 13.3. UA04.2 INTERFACE FEATURES ............................................................................................103 OAM05.0 INTERFACE FEATURES.........................................................................................104 ACCESS GUI INTERFACE ....................................................................................................105 SCOPE ......................................................................................................................105 W-NMS GUI EVOLUTIONS ..........................................................................................105
13.3.1 13.3.2 13.4. 13.5. 13.6.
UA04.2 COMPLIANCE TO 3GPP SPECIFICATIONS .................................................................111 IUB INTERFACE...................................................................................................................112 IUB TRANSPORT .........................................................................................................112 IUR WHEN SRNC AND DRNC RUN DIFFERENT RELEASES ..............................................116 IUR TRANSPORT .........................................................................................................124 IUR INTEROPERABILITY ................................................................................................126 IU TRANSPORT............................................................................................................127 IUR INTERFACE ..................................................................................................................116
13.5.1 13.6.1 13.6.2 13.6.3 13.7. 13.7.1 14.
IU INTERFACE ....................................................................................................................127
NETWORK ARCHITECTURE .................................................................................................130

01.02/EN Preliminary March 2006 Copyright 2004 Nortel Networks
NN-20500-044
Nortel Confidential
Table vii
of
contents
15.
NETWORK RECONFIGURATION PROCEDURES (NRPS) ...................................................131 15.1. 15.2. OAM05.0 NETWORK RECONFIGURATION FEATURES .............................................................131 NRP PROCEDURES ............................................................................................................131 OBSOLETE PROCEDURES ............................................................................................131 NEW PROCEDURES .....................................................................................................131 MODIFIED PROCEDURES..............................................................................................132 AN OVERVIEW OF THE PROCEDURE IS PRESENTED IN THE FOLLOWING FIGURE: ................146
15.2.1 15.2.2 15.2.3 15.2.4 16.
FEATURE ACTIVATION PROCEDURES (FAPS) ..................................................................149 16.1. 16.2. OAM05.0 FEATURE ACTIVATION FEATURES ........................................................................149 FAP PROCEDURES ............................................................................................................149 OBSOLETE PROCEDURES ............................................................................................149 NEW PROCEDURES .....................................................................................................150 MODIFIED PROCEDURES..............................................................................................152
16.2.1 16.2.2 16.2.3 17. 18. 19. 20.
NTP REFERENCE LIST..........................................................................................................165 NRP REFERENCE LIST .........................................................................................................167 FAP REFERENCE LIST..........................................................................................................168 ABBREVIATIONS AND DEFINITIONS ...................................................................................169 20.1. 20.2. ABREVIATIONS ...................................................................................................................169 DEFINITIONS ......................................................................................................................169
ANNEX A: NEW/DELETED/MODIFIED ALARMS ............................................................................170 1. UA04.2/OAM05.0 NEW ALARMS...........................................................................................170 1.1. 1.1.1 1.1.2 1.2. 1.2.1 1.2.2 2. BTS NEW ALARMS .............................................................................................................170 BTS NEW ALARMS .....................................................................................................170 BTS OAM NEW ALARMS ............................................................................................171 RNC ALARMS ....................................................................................................................172 RNC NEW ALARMS ....................................................................................................172 RNC NEW OAM ALARMS ...........................................................................................172
UA04.2/OAM05.0 DELETED ALARMS...................................................................................173 2.1. 2.1.1 2.1.2 2.2. 2.2.1 2.2.2 BTS DELETED ALARMS ......................................................................................................173 BTS DELETED ALARMS ...............................................................................................173 BTS DELETED OAM ALARMS ......................................................................................173 RNC DELETED ALARMS .....................................................................................................173 RNC DELETED ALARMS ..............................................................................................173 RNC DELETED OAMALARMS ......................................................................................173
viii
3.
UA04.2/OAM05.0 DELETED ALARMS...................................................................................174 3.1. 3.1.1 3.1.2 3.2. 3.2.1 3.2.2 BTS MODIFIED ALARMS .....................................................................................................174 BTS MODIFIED ALARMS ..............................................................................................174 BTS MODIFIED OAM ALARMS .....................................................................................174 RNC MODIFIED ALARMS .....................................................................................................174 RNC MODIFIED ALARMS .............................................................................................174 RNC MODIFIED OAM ALARMS ....................................................................................174
ANNEX B: NEW/DELETED/MODIFIED PARAMETERS ..................................................................175 1. UA04.2/OAM05.0 NEW PARAMETERS .................................................................................175 1.1. 1.2. 1.3. 1.4. 1.5. 1.6. 2. CNODE NEW PARAMETERS .................................................................................................175 ANODE NEW PARAMETERS .................................................................................................185 INODE NEW PARAMETERS...................................................................................................186 BTS NEW PARAMETERS .....................................................................................................188 OAM NEW PARAMETERS ....................................................................................................188 POC NEW PARAMETERS.....................................................................................................188
UA04.2/OAM05.0 DELETED PARAMETERS .........................................................................189 2.1. 2.2. 2.3. 2.4. 2.5. 2.6. CNODE DELETED PARAMETERS...........................................................................................189 ANODE DELETED PARAMETERS ...........................................................................................190 INODE DELETED PARAMETERS ............................................................................................190 BTS DELETED PARAMETERS ...............................................................................................191 OAM DELETED PARAMETERS ..............................................................................................191 POC DELETED PARAMETERS ..............................................................................................191
3.
UA04.2/OAM05.0 MODIFIED PARAMETERS ........................................................................192 3.1. 3.1.1 CNODE MODIFIED PARAMETERS ..........................................................................................192 ACCESSSESSION (ACCESSSESSION) ...........................................................................192
3.1.2 AGPSUEBASEDLOCATIONTECHNOLOGYEXTENDEDPARAMS (AGPSUEBASEDLOCATIONTECHNOLOGYEXTENDEDPARAMS) ......................................................192 3.1.3 3.1.4 3.1.5 3.1.6 3.1.7 3.1.8 3.1.9 3.1.10 3.1.11 3.1.12 3.1.13
NN-20500-044
ALARMHARDHOCONF (ALARMHARDHOCONF) .............................................................193 ALWAYSONCONF (ALWAYSONCONF) ..........................................................................193 ALWAYSONTIMER (ALWAYSONTIMER) .........................................................................193 ANODE (ANODE)........................................................................................................194 ANODESOFTWARE (ANODESOFTWARE) ......................................................................194 AOONFACHPARAM (AOONFACHPARAM)......................................................................194 ARPRIORITYLEVEL (ARPRIORITYLEVEL)......................................................................194 CACCONFCLASS (CACCONFCLASS) ............................................................................195 CALLACCESSPERFORMANCECONF (CALLACCESSPERFORMANCECONF) ........................195 CALLTRACE (CALLTRACE) ..........................................................................................196 CC1 (CC1) ...............................................................................................................196
01.02/EN Preliminary March 2006 Copyright 2004 Nortel Networks
Nortel Confidential
Table of contents
ix
3.1.14 3.1.15 3.1.16 3.1.17 3.1.18 3.1.19 3.1.20 3.1.21 3.1.22 3.1.23 3.1.24 3.1.25 3.1.26 3.1.27 3.1.28 3.1.29 3.1.30 3.1.31 3.1.32 3.1.33 3.1.34 3.1.35 3.1.36 3.1.37 3.1.38 3.1.39 3.1.40 3.1.41 3.1.42 3.1.43 3.1.44 3.1.45 3.1.46 3.1.47 3.1.48 3.1.49 3.1.50 3.1.51 3.1.52 3.1.53
CELLCOLORS (CELLCOLORS) .....................................................................................196 CELLSESSION (CELLSESSION) ....................................................................................196 CMODEPATTERNSEQINFO (CMODEPATTERNSEQINFO) ................................................196 CNODESOFTWARE (CNODESOFTWARE) ......................................................................197 COMPUTEDGAINFACTORS (COMPUTEDGAINFACTORS) .................................................197 CONTROLPORT (CONTROLPORT) ................................................................................197 CORESESSION (CORESESSION) ..................................................................................197 CSCORENETWORKACCESS (CSCORENETWORKACCESS) .............................................197 DEDICATEDCONF (DEDICATEDCONF)...........................................................................198 DELTASIR2ANDAFTER2 (DELTASIR2ANDAFTER2)........................................................198 DHIGHRBB1 (DHIGHRBB1)........................................................................................198 DLDYNAMICPARAMETERPERDCH (DLDYNAMICPARAMETERPERDCH) ............................198 DLRBSETCONF (DLRBSETCONF) ...............................................................................199 DLRLCACKMODE (DLRLCACKMODE) ..........................................................................199 DLRLCTMODE (DLRLCTMODE)...................................................................................200 DLRLCUMODE (DLRLCUMODE)..................................................................................200 DLUSERSERVICE (DLUSERSERVICE)...........................................................................200 DLUSPOWERCONF (DLUSPOWERCONF) .....................................................................201 DXCHCONF (DXCHCONF) ..........................................................................................201 DYNAMICPARAMETERPERDCH (DYNAMICPARAMETERPERDCH) ....................................201 EVENT1A (EVENT1A) ..................................................................................................202 EVENT1F (EVENT1F) ..................................................................................................202 FACH (FACH) ..........................................................................................................203 FACHCLASS (FACHCLASS)..........................................................................................203 FACHPOWERADJUSTMENTPARAMS (FACHPOWERADJUSTMENTPARAMS) .......................204 FASTALARMHARDHOCONF (FASTALARMHARDHOCONF) ..............................................204 FDDCELL (FDDCELL) ................................................................................................205 GEOGRAPHICALSESSION (GEOGRAPHICALSESSION) .....................................................206 GSMCELL (GSMCELL) ..............................................................................................206 GSMNEIGHBOURINGCELL (GSMNEIGHBOURINGCELL) ...................................................206 HOCONFCLASS (HOCONFCLASS) ...............................................................................207 INODE (INODE) ..........................................................................................................207 INODESOFTWARE (INODESOFTWARE) .........................................................................207 INTERFREQHHOFDDCELL (INTERFREQHHOFDDCELL) ..................................................207 IRMONRLCONDITIONPARAMETERS (IRMONRLCONDITIONPARAMETERS) ........................207 IRMPREEMPTIONEXTENDEDPARAMS (IRMPREEMPTIONEXTENDEDPARAMS)....................208 IUCSTIMINGALIGNMENT (IUCSTIMINGALIGNMENT) ........................................................208 LOCATIONSERVICES (LOCATIONSERVICES) ..................................................................208 MEASUREMENTCONFCLASS (MEASUREMENTCONFCLASS)............................................208 MEDIUMRBB2 (MEDIUMRBB2) ....................................................................................208
3.1.54 3.1.55 3.1.56 3.1.57 3.1.58 3.1.59 3.1.60 3.1.61 3.1.62 3.1.63 3.1.64 3.1.65
MLPTOOLS (MLPTOOLS)............................................................................................209 MMS (MMS) .............................................................................................................209 MTPSIGNPOINT (MTPSIGNPOINT) ...............................................................................209 NBAPMEASUREMENT (NBAPMEASUREMENT) .............................................................209 NEIGHBOURINGRNC (NEIGHBOURINGRNC).................................................................210 NODEB (NODEB)........................................................................................................210 NODEBCONFCLASS (NODEBCONFCLASS)...................................................................211 NODEBSAALUNIPARAMS (NODEBSAALUNIPARAMS) ....................................................211 OBJECTTRACE (OBJECTTRACE) ..................................................................................211 OMU (OMU) .............................................................................................................211 PCH (PCH)...............................................................................................................211 PERFSCANNER (PERFSCANNER) .................................................................................212
3.1.66 POWERBALANCINGADJUSTMENTPARAMETERS (POWERBALANCINGADJUSTMENTPARAMETERS) ..........................................................................212 3.1.67 3.1.68 3.1.69 3.1.70 3.1.71 3.1.72 3.1.73 3.1.74 3.1.75 3.1.76 3.1.77 3.1.78 3.1.79 3.1.80 3.1.81 3.1.82 3.1.83 3.1.84 3.1.85 3.1.86 3.1.87 3.1.88 3.1.89 3.1.90 3.1.91 3.1.92 POWERCONFCLASS (POWERCONFCLASS)...................................................................212 POWERCTRLCONFCLASS (POWERCTRLCONFCLASS)...................................................213 POWERPARTCONFCLASS (POWERPARTCONFCLASS) ..................................................213 PSCORENETWORKACCESS (PSCORENETWORKACCESS) .............................................213 RADIOACCESSSERVICE (RADIOACCESSSERVICE).........................................................214 RLCCONFCLASS (RLCCONFCLASS).............................................................................214 RLCONDITION (RLCONDITION).....................................................................................215 RNC (RNC) ..............................................................................................................215 RNCMIB (RNCMIB)....................................................................................................215 RRCMEASUREMENT (RRCMEASUREMENT) .................................................................215 SCCPCH (SCCPCH)................................................................................................216 SERVICEINIT (SERVICEINIT).........................................................................................216 SHOLINKADDITIONPARAMS (SHOLINKADDITIONPARAMS) ..............................................216 SHOLINKDELETIONPARAMS (SHOLINKDELETIONPARAMS).............................................216 SIGNALLEDGAINFACTORS (SIGNALLEDGAINFACTORS) ..................................................216 SOFTHOCONF (SOFTHOCONF) ...................................................................................217 TMU (TMU) ..............................................................................................................217 UETIMERCSTCONNECTEDMODE (UETIMERCSTCONNECTEDMODE)...............................217 ULOUTERLOOPPOWERCTRL (ULOUTERLOOPPOWERCTRL)..........................................217 ULRBSETCONF (ULRBSETCONF) ...............................................................................218 ULRLCACKMODE (ULRLCACKMODE) ..........................................................................218 ULRLCTMODE (ULRLCTMODE)...................................................................................219 ULRLCUMODE (ULRLCUMODE)..................................................................................219 ULUSERSERVICE (ULUSERSERVICE)...........................................................................219 ULUSPOWERCONF (ULUSPOWERCONF) .....................................................................220 UMTSFDDNEIGHBOURINGCELL (UMTSFDDNEIGHBOURINGCELL) ................................220
NN-20500-044
01.02/EN
Preliminary
March 2006
Nortel Confidential
Table of contents
xi
3.1.93 3.1.94 3.2. 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.2.6 3.2.7 3.2.8 3.2.9 3.2.10 3.2.11 3.2.12 3.2.13 3.2.14 3.3. 3.3.1 3.3.2 3.3.3 3.3.4 3.3.5 3.3.6 3.3.7 3.3.8 3.3.9 3.3.10 3.3.11 3.3.12 3.3.13 3.3.14 3.3.15 3.3.16 3.3.17 3.3.18 3.3.19 3.3.20 3.3.21 3.3.22
USERSERVICES (USERSERVICES) ...............................................................................220 USHOCONF (USHOCONF) ..........................................................................................221 ATMINTERFACE (ATMIF)..............................................................................................222 ATMCONSTANTBITRATE (CBR)....................................................................................222 ATMNONREALTIMEVARIABLEBITRATE (NRTVBR) .........................................................222 ATMREALTIMEVARIABLEBITRATE (RTVBR) ..................................................................222 ATMUNSPECIFIEDBITRATE (UBR) ................................................................................223 ATMTRAFFICMANAGEMENTPROV(TM)..........................................................................223 INWATMCONNECTION (AC)..........................................................................................223 APMVC4 (VC4) ..........................................................................................................223 SHELF (SHELF) ..........................................................................................................223 CARD (CARD).............................................................................................................224 INWIP (IP) ..................................................................................................................225 INWIPSTATIC (STATIC) ................................................................................................225 INWIPSTATICROUTEENTRY (ROUTE)............................................................................225 INWIPPORT (IPPORT)..................................................................................................225 PSSS7ROUTE (RO) ....................................................................................................226 SIGNALLINGBEARER (SIG)...........................................................................................226 NAILEDUPACCESSPOINT (NAP) ...................................................................................226 SAALUNI (SAALUNI) ...................................................................................................226 INWATMCONNECTION (AC)..........................................................................................226 INWOSPFAREAENTRY (AREA) .....................................................................................227 ATMINTERFACE (ATMIF)..............................................................................................227 CARD (CARD).............................................................................................................228 ATMCONSTANTBITRATE (CBR)....................................................................................229 INWLOCALMEDIAINTERFACE (IF)..................................................................................229 INWIP (IP) ..................................................................................................................229 INWIPPORT (IPPORT)..................................................................................................229 LINEAUTOMATICPROTECTIONSWITCHING (LAPS) ..........................................................229 INWIPLOGICALIF (LOGICALIF) ......................................................................................230 ATMNONREALTIMEVARIABLEBITRATE (NRTVBR) .........................................................230 INWIPOSPF (OSPF).....................................................................................................230 INWOSPFIF (OSPFIF) ..................................................................................................230 ATMCONNECTIONMAPPINGOVERRIDE (OV) ..................................................................230 IUXIFPATH (PATH) ......................................................................................................231 INWIPSTATICROUTEENTRY (ROUTE)............................................................................231 ATMREALTIMEVARIABLEBITRATE (RTVBR) ..................................................................231 SHELF (SHELF) ..........................................................................................................231
ANODE MODIFIED PARAMETERS ..........................................................................................222
INODE MODIFIED PARAMETERS ...........................................................................................226
xii
3.3.23 3.3.24 3.3.25 3.3.26 3.3.27 3.3.28 3.4. 3.4.1 3.4.2 3.4.3 3.4.4 3.4.5 3.4.6 3.4.7 3.4.8 3.4.9 3.4.10 3.4.11 3.4.12 3.4.13 3.4.14 3.4.15 3.4.16 3.4.17 3.4.18 3.4.19 3.4.20 3.5. 3.5.1 3.5.2 3.5.3 3.5.4 3.5.5 3.5.6 3.5.7 3.5.8 3.5.9 3.5.10 3.6. 3.6.1
INWIPSTATIC (STATIC) ................................................................................................231 ATMTRAFFICMANAGEMENTPROV (TM).........................................................................231 INWOSPFIFTYPEOFSERVICE (TOS) ............................................................................232 ATMUNSPECIFIEDBITRATE (UBR) ................................................................................232 INWOSPFVIRTIFENTRY (VIRTIF) ..................................................................................232 PSSS7SERVICEINDICATOR (SERVIND) .........................................................................232 AAL2BEARER (AAL2BEARER) ....................................................................................233 ANTENNAACCESS (ANTENNAACCESS) .........................................................................233 BOARD (BOARD).........................................................................................................233 BTSCELL (BTSCELL).................................................................................................233 BTSEQUIPMENT (BTSEQUIPMENT) .............................................................................234 BTSEQUIPMENTMIB (BTSEQUIPMENTMIB).................................................................235 BTSEQUIPMENTSOFTWARE (BTSEQUIPMENTSOFTWARE) ............................................235 CCP (CCP)...............................................................................................................235 COOLINGSYSTEM (COOLINGSYSTEM) ..........................................................................235 COUNTERFAMILY (COUNTERFAMILY) ...........................................................................235 DEVICETABLE (DEVICETABLE).....................................................................................236 IMAGROUP (IMAGROUP) .............................................................................................236 NODEBCP (NODEBCP)..............................................................................................236 OMCBCONNECTION (OMCBCONNECTION) .................................................................236 PASSIVECOMPONENT (PASSIVECOMPONENT)...............................................................237 POWERSYSTEM (POWERSYSTEM) ...............................................................................237 ROUTECES (ROUTECES) ............................................................................................237 RTOBSSESSION (RTOBSSESSION)..............................................................................238 SITELAN (SITELAN) ....................................................................................................238 VCC (VCC)...............................................................................................................238 EXTERNALALARMMAPPINGTABLE (EXTERNALALARMMAPPINGTABLE) ............................239 EXTERNALALARMMAPPINGTABLEENTRY (EXTERNALALARMMAPPINGTABLEENTRY) ........239 SCOPE (SCOPE).........................................................................................................239 TRACEFILTER (TRACEFILTER) .....................................................................................239 TRACERECORD (TRACERECORD) ................................................................................240 TRACESESSION (TRACESESSION) ...............................................................................240 TRACESESSIONTEMPLATE (TRACESESSIONTEMPLATE).................................................240 USEREQUIPMENTID (USEREQUIPMENTID) ....................................................................240 PMCLUSTER (PMCLUSTER)........................................................................................241 CLUSTER (CLUSTER) ..................................................................................................241 AAL1ACTIVEENDPOINT (AEP) .....................................................................................242
BTS MODIFIED PARAMETERS ..............................................................................................233
OAM MODIFIED PARAMETERS .............................................................................................239
POC MODIFIED PARAMETERS .............................................................................................242
NN-20500-044
01.02/EN
Preliminary
March 2006
Nortel Confidential
Table xiii
of
contents
3.6.2 3.6.3 3.6.4 3.6.5 3.6.6 3.6.7 3.6.8 3.6.9 3.6.10
ATMCELL (CELL) ........................................................................................................242 ATMPNNI (PNNI).........................................................................................................242

CASROOT (EM)..........................................................................................................242
DCSSPOOLER (SP).....................................................................................................242 E1 (E1) .....................................................................................................................243 E1CHAN (CHAN) ........................................................................................................243 INWHOSTENTRYCOS (HOST) ......................................................................................243 INWIPLOGICALIF (LOGICALIF) ......................................................................................243 PMSTC (TC)...............................................................................................................243
ANNEX C: NEW/DELETED/MODIFIED COUNTERS .......................................................................244 1. UA04.2/OAM05.0 NEW COUNTERS ......................................................................................244 1.1. 1.2. 2. RNC NEW COUNTERS ........................................................................................................244 BTS COUNTERS ................................................................................................................265
UA04.2/OAM05.0 DELETED COUNTERS..............................................................................267 2.1. 2.2. RNC DELETED COUNTERS ..................................................................................................267 BTS DELETED COUNTERS...................................................................................................267
3.
UA04.2/OAM05.0 MODIFIED COUNTERS .............................................................................268 3.1. 3.2. RNC MODIFIED COUNTERS .................................................................................................268 BTS MODIFIED COUNTERS ..................................................................................................268
xiv
NN-20500-044
01.02/EN
Preliminary
March 2006
Nortel Confidential
1.
1.1.
INTRODUCTION
OBJECT
This document lists the impacts of the UA04.2 UMTS access release on operational activities compared to the UA04.1 release. It is intended to assist operational teams in preparing to receive a new release by clearly explaining the changes which affect operational activities due to the upgrade.
1.2.
APPLICABILITY
This document is produced as a part of the Release Documentation program and, as such, it refers to the all documents listed in the section Applicable Document. The reader has to enquire into the documents mentioned above. This document deals with the UA04.2 system release. It is based on the features planned in the UA04.2 Customer Readiness version. The UA04.2 Access release is part of the UMTS5.0 solution line-up.
1.3.
AUDIENCE
It is the input document for Customers and Nortel people who want to know the operational impacts of the UA04.2 Release.
2.
2.1.
RELATED DOCUMENTS
APPLICABLE DOCUMENTS
None
2.2.
REFERENCE DOCUMENTS
[R1] [R2] Matrix UMT/COM/INF/00018 UMT/SYS/DD/09476 UMTS Continuity UMTS05 System Upgrade Paths and Compatibility UA04.2 Access Network Feature Planning Guide UMTS Access Network Parameters 06.05/EN
[R3] UMT/SYS/INF/07906 V01.07/EN [R4] 411-8111-813 (P1 to P6)
NN-20500-044 01.02/EN Preliminary March 2006
Nortel Confidential
[R5] 411-8111-822 (P1 to P3) V04.12/EN [R6] UMT/DCL/APP/12535 (UODP05.0) V01.08/EN [R7] [R8] [R9] [R10] [R11] [R12] [R13] [R14] [R15] [R16] [R17] [R18] [R19] [R20] [R21] [R22] [R23] [R24] [R25] [R26] UMT/UTR/DD/09488 411-8111-813 411-8111-822 411-8111-554 411-8111-556 UMT/SYS/DD/09157 UMT/SYS/DD/00034 UMT/SYS/DD/00054 UMT/SYS/DD/00077 UMT/SYS/DD/00086 UMT/SYS/DD/00128 UMT/SYS/DD/00140 UMT/SYS/DD/00143 UMT/SYS/DD/00158 UMT/SYS/DD/04666 UMT/SYS/DD/08326 UMT/SYS/DD/10421 UMT/SYS/DD/10672
UMTS Access Network Observation Counters UMTS Overall Documentation Plan for UMTS05.0 Access Network Parameters Access Network Observation Counters RNC 1000 & RNC 15000 Fault Analysis UMTS BTS Fault Analysis UMTS Call Trace Events Dictionary V02.02/EN PS Call Management UMTS Radio Mobility UTRAN Call Trace Specification Power Management iRM-intelligent RAB mapping RNC upgrade RNC AN MSA32 Sparing Panel Location Services GPS based UE positioning SPVCs on Iu/Iur/Iub interfaces Radio Bearers configuration parameters PP7k 2pSTM1Ch FP on RNC AN iRM pre-emption
UTRAN Neighbor List UTRAN and Core Network releases compliance Feature Activation Procedure Wireless Network Management System Feature
[R27] UMT/SYS/DD/15313 with respect to 3GPP [R28] HSDPA 411-8111-575
[R29] UMT/OAM/INF/11587 Planning Guide OAM05.0
Nortel Confidential
3.
UA04.2 FEATURES
This chapter covers the whole UA04.2 portfolio. This chapter gives: in 3.1: the list of all the UA04.2 features per category as defined in [R3] from 3.2 to 3.42: the description of all the features as defined in [R3] and in [R29]
3.1.
UA04.2 FEATURE IMPACT LIST

The following tables give the list of the whole new UA04.2 features and their impacts.
Nortel Confidential
3.1.1 PERFORMANCE AND CAPACITY FEATURE IMPACT LIST

Compatibility Table/Upgrade path System & Security Management Upgrade, patch & migration Configuration Management Performance Management
Network Architecture
Interfaces changes
Fault Management
Hardware
Feature ID
Feature Title
27930 27931 27932 27935 27936 27937 27939 27940 27941 27942 27943 27945 27947 28047 28900
HSDPA Service HSDPA Flexible Resource Management HSDPA Step1 Multi-carrier HSDPA traffic segmentation HSDPA Intrafrequency Mobility HSDPA Alarm Mobility HS-SCCH Power Control H-BBU Pool Across Sectors Node-B Module Operation For HSDPA Always-On on HSDPA Iub Bandwidth Limitation Handling HSDPA Radio Bearers PS I/B UL:384 Call Establishment KPI Improvements STSR1+1 NodeB x
x x
x x x x x x x x x x x
x x x x x x x x x x x x x
x x x x x x x x
x x x x x x x x x x x x
NRP/FAP
Tools
Nortel Confidential
3.1.2 TRANSMISSION AND TRANSPORT CAPABILITY FEATURE IMPACT LIST

Network Architecture x Network Architecture
Interfaces changes
Fault Management
Hardware
Feature ID
Feature Title
24082
26521 26614
MSA32 enhancement to sustain 28E1 with IMA RNC supports QAAL2 Alternate Routing RNC supports QAAL2 Address Translation PP7K optical STM1 channelized card in POC Y Splitter at the RNC
x x x
27639 28302
Transmission is out of the scope of this document even though this document deals with the POC parameters/alarms/counters. x
3.1.3 SECURITY FEATURE IMPACT LIST

Interfaces changes
Fault Management
Hardware
Feature ID
Feature Title
26407 26409
IPsec support validation on RNC Support of Radius Client on RNC
x x
x x
x x
x x
NRP/FAP
Tools
NRP/FAP
Tools
Nortel Confidential
3.1.4 RADIO MOBILITY FEATURE IMPACT LIST

Interfaces changes
Fault Management
Hardware
Feature ID
Feature Title
13451 27597
3G to 2G Redirection for Speech calls Service-based inter-freq/inter-RAT selection for HHO
x x
x x
x x
NRP/FAP
Tools
Nortel Confidential
3.1.5 RESOURCE MANAGEMENT AND OPTIMIZATION / SERVICES FEATURE IMPACT LIST

Interfaces changes
Fault Management
Hardware
Feature ID
Feature Title
28144
25100
27219
27330 27740 28036 28040 28330 28331 28847 30038 30311
iRM Scheduling downgrading based on TxCP UTRAN Call Trace :Additional Measurement Reporting (NBAP Common measurement, RRC BLER, etc..) Intra-frequency Event-triggered Measurements RB adaptation based on traffic: DL and UL with start @64kbit/s Iub load in iRM Mobility Performance Improvements Power Control and Rate Matching enhancements PS Streaming up to 128kbit/s PS Streaming up to 128kbit/s + PS I/B 8kbit/s Change of SAI reporting Node-B CAC: Max HSDPA users per Node-B RAB based CAC
x x x
x x
No operational impact x x x x x x x x x x
NRP/FAP
Tools
Nortel Confidential
3.1.6 OPERATIONAL EFFECTIVENESS FEATURE IMPACT LIST

Network Architecture Network Architecture
Interfaces changes
Fault Management
Hardware
Feature ID
Feature Title
26234 27729 27901 29361
NodeB support of 2 OAM IP adresses UA04.2 Counters evolution UA04.2 Parameters evolution Handover and RRM ConfClass range extension
x x x x
3.1.7 COMPLIANCE FEATURE IMPACT LIST

Interfaces changes
Fault Management
Hardware
Feature ID
Feature Title
28109
UA04.2 - 3GPP baseline & additional CRs
NRP/FAP
Tools
NRP/FAP
Tools
Nortel Confidential
3.2.
FEATURE 13451 - 3G TO 2G REDIRECTION FOR SPEECH CALLS

The feature redirects speech calls from 3G to 2G at call establishment when no resources are available to establish the call on the current 3G cell. This situation can occur during the SRB (Signaling Radio Bearer) establishment or during the TRB (Traffic Radio Bearer) establishment The SRB is established as a result of the first Access Stratum (AS) message being received by the RNC, and is used to allow the UE and CN to exchange subsequent Non Access Stratum (NAS) messages to allow the call to progress. The TRB is established upon reception of the RAB Assignment Request from the CN. As a result, the existing SRB is transitioned to a SRB+TRB RB. This RB combination may also cause CAC to fail on the RNC for the same resource constraint reasons as can occur during SRB processing.
Handling CAC failure during SRB establishment: Once the RNC receives the RRC Connection Request for an Originating Conversational Call, if no resources are available to establish the SRB, the RNC will reply to the UE with RRC Connection Reject indicating that Redirection to GSM shall be performed. Handling CAC failure during TRB establishment: The speech call progresses normally to the point where the CN sends the RAB Assignment Request. If the RNC does not identify any form of capacity exhaust, the call is completed on 3G using existing normal procedures. If the RNC identifies a capacity exhaust situation, using existing CAC mechanisms, prior to the RAB Assignment Response, the RNC responds with a RAB Assignment failure, with a Directed Retry (DR) indication. This prevents the CN from terminating the call. The RNC then sends the CN a Relocation Required indication, including the provisioned 2G designated target cell (Blind HO target). The 3G-2G HO is completed as per existing 3G-2G UTRAN/CN Handover procedures. The different resources that could trigger the Directed Retry in case of shortage are: Power Codes Iub (i.e. AAL2 CAC) CEM (i.e. RL Reconf Failure from NodeB) Iu (i.e. AAL2 CAC) RNC Internal Resource (i.e. PMC CPU, load )
Nortel Confidential
10
3.3.
FEATURE 24082 - MSA32 ENHANCEMENT TO SUSTAIN 28E1 WITH IMA

Without this feature a maximum of 22 E1 links per MSA32 card can be provisioned on the Iub interface when IMA is used. Therefore, the overall E1/IMA capacity of an RNC (i.e. when 7MSA32 cards are plugged into the PP7K) was 154E1. Thanks to this feature a maximum of 28 E1 links per MSA32 card can be provisioned on the Iub interface when IMA is used. Therefore, the overall E1/IMA capacity of the RNC becomes 196 E1/IMA.
3.4.
FEATURE 25100 - UTRAN CALL TRACE: ADDITIONAL MEASUREMENT REPORTING (NBAP COMMON MEASUREMENT, RRC BLER, ETC..)
NBAP measurements are performed at Node B level. The results are then reported to the RNC in NBAP (Node B measurements) measurement report messages. This is defined in recommendations 3GPP 25.434. The required feature consists of including NBAP Common Measurements in the CTa, CTb and CTg session outputs. The collection and mediation layer APM.ADI shall decode all the NBAP common and RRC messages as per the CT template definition. Without this feature, the NBAP Common Measurements sub-function comes from: Iub function OTCell Call Trace sessions LightTroubleShooting Trace Filter Event or ASN1 mode for XDR interface Event or ASN1 for XML interface.
With this feature, the NBAP Common Measurements sub-function comes from: Iub function CTa, CTb, CTg and OTCell Call Trace sessions LightTroubleShooting Trace Filter Event or ASN1 mode for XDR interface Event or full decoded and ASN1 for XML interface.
3.5.
FEATURE 26234 - NODE B SUPPORT OF 2 OAM IP ADDRESSES

NodeB supports 2 IP addresses in order to support a second OAM server.
Nortel Confidential
11
3.6.
FEATURE 26407 - IPSEC SUPPORT VALIDATION ON RNC

IPSec is a framework of open standards developed by the Internet Engineering Task Force (IETF). IPSec provides security for transmission of sensitive information over unprotected networks such as the Internet. IPSec acts at the network layer, protecting and authenticating IP packets between participating IPSec devices ("peers"). IPSec provides the following network security services. These services are optional. In general, local security policy will dictate the use of one or more of these services: Data Confidentiality - The IPSec sender can encrypt packets before transmitting them across a network. Data Integrity - The IPSec receiver can authenticate packets sent by the IPSec sender to ensure that the data has not been altered during transmission. Data Origin Authentication - The IPSec receiver can authenticate the source of the IPSec packets sent. This service is dependent upon the data integrity service. Anti-Replay - The IPSec receiver can detect and reject replayed packets
IPSec provides IP network-layer encryption and consists in the addition of authentication, encryption, compression, and public key exchange. The standards define several new packet formats: the authentication header (AH) to provide data integrity and the encapsulating security payload (ESP) to provide confidentiality and data integrity. Key management and security associations, the IPSec parameters between two devices, are negotiated with the Internet Key Exchange (IKE, formerly known as the Internet Security Association Key Management Protocol or ISAKMP (Oakley). IKE can use digital certificates for device authentication to enable the creation of large encryption networks. IPSec according to the standards consists of separate protocols, listed below:
Nortel Confidential
12
Application
IKE
Application protocols Sockets Transport (TCP, UDP)

IP
IPsec
(AH, ESP)
Link & Physical layers
IPsec protocol stack
Authentication Header (AH): provides authenticity guarantee for packets, by attaching strong crypto checksum to packets. If you receive a packet with AH and the checksum operation was successful, you can be sure about two things if you and the peer share a secret key, and no other party knows the key: The packet was originated by the expected peer. The packet was not generated by impersonator. The packet was not modified in transit. Unlike other protocols, AH covers the whole packet, from the IP header to the end of the packet. Encapsulating Security Payload (ESP): provides confidentiality guarantee for packets, by encrypting packets with encryption algorithms. If you receive a packet with ESP and successfully decrypted it, you can be sure that the packet was not wiretapped in the middle, if you and the peer share a secret key, and no other party knows the key. IP payload compression (IPcomp): ESP provides encryption service to the packets. However, encryption tends to give negative impact to compression on the wire (such as ppp compression). IPcomp provides a way to compress packet before encryption by ESP (Of course, you can use IPcomp alone if you wish to). An orthogonal (mostly) division of IPSec functionality is applied depending on whether the endpoint doing the IPSec encapsulation is the original source of the data or a gateway: Transport mode: is used by a host that generates the packets. In transport mode, the security headers are added before the transport layer (e.g.. TCP, UDP) headers, before the IP header is prepended to the packet. In other words an AH added to the packet will cover the hashing of the TCP header and some fields of the end-to-end IP header, and an ESP header will cover the encryption of the TCP header and the data, but not the end-to-end IP header. Tunnel mode: is used when the end-to-end IP header is already attached to the packet, and one of the ends of the secure connection is only a gateway. In this mode, the AH and ESP headers are used to cover the entire packet
Nortel Confidential
13
including the end-to-end header, and a new IP header is prepended to the packet that covers just the hop to the other end of the secure connection (though that may of course be several IP hops away). IKE is optional; it is possible to configure secret keys manually for AH/ESP. Nevertheless manual key configuration introduces drawbacks and security gaps, as one secret key cannot be used forever. If a same secret key has been used for a long period of time, the traffic become more and more likely to get compromised. So that, security of IPSec protocols depends on the secrecy of secret keys. If secret keys are compromised, IPSec protocols can no longer be secure. RFC suites starting from RFC1825 describe IPSec, and most recent IPSec RFC suite starts from RFC2401.
Nortel Confidential
14
3.7.
FEATURE 26409 - SUPPORT OF RADIUS CLIENT ON RNC

This feature allows the RNC to access to a RADIUS server.
User account management & policies (strong passwords, aging)
Log alarms for Security audits Accounting
RNC
Radius Server Radius Client PAM IPsec Authenticate both sites, data integrity LDAP server
Users profiles Real time alarms
RNC
OMC
User accounts Support of Radius Client on RNC
Nortel Confidential
15
3.8.
FEATURE 26521 - RNC SUPPORTS QAAL2 ALTERNATE ROUTING

Terminology - MGW : Media Gateway The Media Gateway terminates the signaling over the Mc interface from the (G)MSC servers. The Media Gateway terminates the Iu transport network control plane signaling with its transport bearer (see 3GPP TS 25.410 and 3GPP TS 25.414). The Media Gateway also terminates the Iu user plane protocol (see 3GPP TS 25.415). It also terminates the bearer control signaling and the transport bearer over the Nb interface (see 3GPP TS 29.414 and 3GPP TS 29.415). The Media Gateway contains bearer terminations and media manipulation equipment (e.g. transcoders, echo cancellers, or tone senders). It may perform media conversion and framing protocol conversion.
UTRAN
Iu MGW A A Mc Nc MSC server Nb
MGW Mc GMSC server
PSTN/ Legacy/External
Iu
GERAN
Signalling Interface Signalling and Data Transfer Interface
MGW in 3 GPP (figure 10)
Reference Documents [R6] ITU-T Q.2630.1 AAL type 2 signaling protocol (Capability Set 1), ITU Recommendation Technical requirement description This feature provides the ability to reach a given A2EA address through several routes (SS7 PCs for instance) so that if one becomes unavailable another can be used.
Nortel Confidential
16
The Iu (or Iur) ALCAP will pass through two different AAL2 switching equipment.
AAL2
PC1
Other Node (MGW, RNC)
AAL2 RNC
PC2
A2EA1
In case of failure of one AAL2 switch, it will be possible to continue establishing AAL2 connections on Iu/Iur
Routing Possibilities (figure 11) For a given Q.AAL2 destination identified by an address (A2EA) more than one route needs to be provisioned to reach that address so that in case of failure of one route another route to that address can still be used. The need for this would appear typically in a AAL2 switched network: This function chooses a route for the QAAL2 establishment request based on the destination address (A2EA). The route is in fact the next-hop or the next adjacent AAL2 switch identified by its SS7 PC for Iu and Iur (identified by its SSCOP connection for Iub).
PC5 MGW1 PC2 A2EA1 SS7 SS7 SS7 RNC1 PC3 SS7 AAL2 switch SS7 SS7 PC4
PC6 MGW2 A2EA2 PC7 RNC2 A2EA3
PC1 A2EA0
RNC in AAL2 switched environment (Iub out of scope of UA04.2) (figure 12a) This means that routing/provisioning tables would look like this (table 5):
NN-20500-044 01.02/EN Preliminary March 2006 Copyright 2003-2005 Nortel Networks
Nortel Confidential
17
A2EA1 A2EA1 A2EA2 A2EA3
PC2 PC3 PC3 PC3 Table
PC5 PC2
MGW1 A2EA1
PC6
MGW2 A2EA2
SS7 SS7 SS7 PC3 RNC1 SS7 PC4 SS7 RNC2 A2EA3
PC1 A2EA0
AAL2 switch (not an SS7 STP)
UA03 Supported configuration only one route for a given A2EA (figure 12b) This means that routing/provisioning tables would look like this (table 6): A2EA1 A2EA2 A2EA3 PC2 PC3 PC4 Table
Nortel Confidential
18
3.9.
FEATURE 26614 - RNC SUPPORTS QAAL2 ALTERNATE ROUTING

This function chooses a route for the QAAL2 establishment request based on the destination address (A2EA). In previous releases, all A2EAs are provisioned in the RNC one by one (the whole address) and there is a static mapping to an SS7 PC (Point Code). Also when standard address format types are defined, address translation can be performed using address prefix instead of the whole address. This is very important as it means we need only to provision prefixes, its easier for the operator and it allows a nearly unlimited amount of A2EAs. Originally the 3GPP didnt mandate or list a particular A2EA format so that implementing prefix translation was risky (no way of knowing what format the customer would like to use). Now the 3GPP references an updated version of E.191 with a limited list of A2EA formats. This means that for a given AAL2 switch (identified by its point code on Iu/Iur or SSCOP connection in Iub) instead of provisioning a list of up to 32 20-bytes A2EAs, the operator can provision a given number of variable length entries (prefixes) that can be reached through this adjacent AAL2 node.
DPC1 RNC1 A2EA1 4700798 NB1 4700798001xxxxxxxxxx NB2 4700798002xxxxxxxxxx NB3 4700798103xxxxxxxxxx A2EA2 4700798 2 NB4 47007982004xxxxxxxxxx DPC3 A2EA3 47007 NB5 4700700011xxxxxxxxxx
DPC2 A2EA1 (4700798) A2EA2 (47007982) DPC1 DPC2 DPC1 DPC2 A2EA3 (47007) DPC3
prefix -> DPC routing table
Best match prefix In coming A2EA: 4700700011xxxxxxxxxx
QAAL2 Address Translation In the example above, 3 prefixes are provisioned: A2EA1, A2EA2, A2EA3. A dedicated A2EA would be matched against each prefix: the best match would be used for routing purpose, in order to find the associated Destination Point Code. Reference Documents [R6] ITU-T Q.2630.1 AAL type 2 signaling protocol Capability set 1 [R7] ITU-T E.191 - B-ISDN addressing, ITU Recommendation 3GPP 25.414 / UTRAN Iu interface data transport and transport signaling, 3GPP Standard Document
Nortel Confidential
19
3.10. FEATURE 27219 - INTRA-FREQUENCY EVENT-TRIGGERED MEASUREMENTS

Prior to UA04.2 the product allows the operator to choose between Periodic intra-frequency RRC measurement reporting, or Hybrid periodic / event-based intra-frequency RRC measurements reporting This feature implements the support of Event-triggered intra-frequency RRC measurements reporting as an evolution to the hybrid mode. Intra-frequency measurements are used for Soft Handover mobility, Alarm Handover detection, and RRM algorithms. Inter-frequency and inter-RAT (GSM) measurements are still reported in periodic mode.
3.11. FEATURE 27330 - RB ADAPTATION BASED ON TRAFFIC: DL AND UL WITH START @64KBIT/S
When a service is initiated, the Radio Bearer (RB) that is setup results from the computation of the RAB request attributes and the UTRAN admission rules. For instance, PS services, which are tolerant to delay, can be admitted with a lower bit rate when the available system resources do not allow to admit it at the requested maximum bit rate. Nevertheless, once the RB is established, there can be some situations where the allocated RB bit rate is too high (or too low) compared to the real traffic carried over the RAB. This can for example be the case for: FTP or Streaming like applications for which the throughput may be constrained by a server limitation or a congestion at the IP level Allocation policy for which the CN always requests the subscribed maximum bit rate (e.g. 384kbit/s), irrespective of the service requirement.
Nortel already provides the Always-On feature to handle inactive or low active applications (e.g. polling mechanism, mailbox checking, etc) by downsizing the RB to low rate DCH (i.e. UL:8/DL:8) or CELL_FACH. Thanks to this feature further capacity is saved as the RNC is able to dynamically adapt the RB bit rate as close as possible to the real traffic for those services requiring more than the Always-On downsized configuration but less than the current RB. The feature supports RB bit rate adaptation in both downlink (DL) and uplink (UL) independently. To achieve this, the RNC monitors the traffic of all established PS RAB and periodically determines if the current RB needs to be reconfigured to match the actual traffic. This mechanism works in parallel of the existing Always-On feature as illustrated in the picture below.
Nortel Confidential
20
eMail Web browsing 128 Streaming 256 384
64
Radio Bearer adaptation
AO
Always-On process (AO = 8/8 or CELL_FACH)
idle
RB adaptation principles (figure 19)
The RB adaptation process has two main procedures: A Traffic monitoring process: procedure by which the RNC estimates the average throughput of the service A RB resizing process: this is the mechanism responsible for determining if the current RB bit rate needs to be adapted and for triggering the corresponding RB reconfiguration
RB bit rate adaptation can lead to downsize or to upsize the current RB bit rate. Although performed independently, DL and UL bit rate adaptation processes are quite similar the only difference being that: o In DL, user is initially admitted at a bit rate determined based on the RAB Matching and iRM rules. Then, during the call, the RB bit rate can be downsized or upsized to match the estimated user average throughput. The RAB Matching provides a reference RB bit rate that is selected among the RB configuration, which are enabled to RAB Matching, as the bit rate that is immediately lower or equal to the Requested Maximum Bit Rate (i.e. received in the RAB assignment request) iRM can replace the reference DL RB bit rate by a lower one according to radio conditions (Radio link colour) and cell loading (Cell colour).
In UL, user is initially admitted at a pre-configured low bit rate (default is 64kbit/s), and the RNC relies on the traffic monitoring function to determine if the bit rate needs to be upsized or downsized.
The rationale behind this choice is that UL traffic profile is expected to be made of few packets followed by large idle period in most cases. Hence allocating a low bit rate at admission reduces the risk of blocking, while the traffic monitoring function ensures that if the user actually needs more it can be upsized to a higher rate. Such management also ensures that allocated base band resources in the Node B are used to carry revenue generating traffic.
Nortel Confidential
21
RB adaptation downsizing When the RB bit rate needs to be downsized, the RNC selects the bit rate according to ranges of average throughput as shown in the picture below. For example, if a user is currently allocated UL:64kbit/s / DL:384kbit/s but the estimated DL average throughput is lower than Tdown(N), then the RB is reconfigured to UL:64kbit/s / DL:N kbit/s where N {32, 64, 128, 256, 384}.
Average throughput
384 In this range of rate, no RB downsizing is triggered 256
Tdown(256)
In this range of rate, a RB is downsized to 256kbit/s 128

Tdown(128)
In this range of rate, a RB is downsized to 128kbit/s In this range of rate, a RB is downsized to 64kbit/s In this range of rate, a RB is downsized to 32kbit/s
64
Tdown(64)
32
Tdown(32)
Example of RB downsizing when current RB bit rate is 384kbit/s (figure 20)
RB adaptation downsizing in DL
DL384
DL256
DL128
DL64
DL32
RB adaptation downsizing in UL
UL384
UL128
UL64
UL32
RB adaptation downsizing (figure 21)
Nortel Confidential
22
RB adaptation upsizing 1. Uplink

When the RB bit rate needs to be upsized, the RNC selects the bit rate that is immediately higher than the current RB (i.e. step-by-step upsize), since the traffic monitoring function can only indicate that the current bit rate is not sufficient (i.e. estimated throughput higher than an absolute threshold), but cannot provide information on what would be the most suitable higher rate. For example, if a user is currently allocated UL:64kbit/s / DL:128kbit/s but the estimated average throughput in UL is above an absolute threshold, i.e. Tup(64), then the RB is reconfigured to UL:128kbit/s / DL:128kbit/s.
2. Downlink
When the RB bit rate needs to be upsized, the RNC can target any rate (i.e. multi-step upsize), based on user throughput and RLC buffer.
RB adaptation upsizing in DL
DL384
DL256
DL128
DL64
DL32
RB adaptation upsizing in UL
UL384
UL128
UL64
UL32
RB adaptation upsizing (figure 22) In case of an upsize, the bit rate cannot exceed the bit rate provided by iRM in DL, while in UL the bit rate cannot exceed the reference bit rate.
Nortel Confidential
23
3.12. FEATURE 27597 - SERVICE-BASED INTER-FREQ/INTER-RAT SELECTION FOR HHO

Without this feature the alarm Handover triggers either inter-frequency measurements or inter-RAT (GSM) measurements depending on the configuration of the primary cell: Inter-frequency in case of inter-frequency neighbors only Inter-RAT in case of inter-RAT or mixed cells
This feature introduces the ability to choose between inter-frequency or inter-RAT measurements in case of Alarm handover, on a per service type (AsConf) basis. The RNC will thus request the measurements corresponding to the chosen type. In case no valid measurements have been reported (either type), and if a Blind GSM is configured, then it is triggered.
3.13. FEATURE 27639 - PP7K OPTICAL STM-1 CHANNELIZED CARD IN POC

This feature introduces the 2 Ports Channelized optical STM1 card in the PP7K POC. Typical network topology with this feature is as follows:
1/ E1
N*/ E1 IMA
N*/ E1 multi-pcm
RNC
1/ E1
Node-B 1
Optical Channelized STM1
A/D Mux
SDH protected ring
A/D Mux
N* E1 / IMA
PP7K (POC) 2 ports Channelized STM1 card inserted into the PP7K
Node-B 2
N* E1 / multi pcm
Network Topology
Interface Node connectivity is achieved by either: STM1/VC4 port of an MSA32 card within the same PP7K Dedicated 2 ports STM1/VC4 single mode card in the PP7K
Note: This feature requires the addition of 2 new card types in the Access Node as compared to previous Utran sw releases: 2p STM1/VC12 optical card and 2 ports STM1/VC4 optical card.
Nortel Confidential
24
The 2pSTM1/VC12 card is a single slot card
Description of the feature (2/2)

RNC
PP7K (POC
10
11
12
13
14
15
CP Eth
2pSTM1ch
CP Eth
2pSTM1ch
2pOC3
2pOC3
2pOC3
POC card configuration (figure 16) POCs equipped with this card provide the same functionalities as POCs equipped with MSA32 card (with the exception of ATM/Fractional E1 which is not supported by this card). In particular: It is possible to configure SPVC/PNNI between the I-Node and the PP7K in order to manage PP7K link/card failures. IMA is supported This card is inter-card APS capable, card redundancy is provisionable. It is possible to mix this card with MSA32 cards (eventually with MSA32 sparing panel), which can be linked : either to a GSM BSC if CES is in use or to Node-bs connected through MicroWave links
The 2pChannelized card is supported by PCR 7.1.
ATM Connections to be supported are: PVC, SPVC/PNNI
Nortel Confidential
25
3.14. FEATURE 27729 - UA04.2 COUNTERS EVOLUTION

This feature describes the counter evolutions in UA04.2. These counters will allow for KPI metrics building and complete the existing metrics. This feature does not include the HSDPA counters, see the feature 27930 HSDPA service for the HSDPA specific counters.
3.15. FEATURE 27740 - IUB LOAD IN IRM

This feature consists in integrating the Iub load in the existing cell colour that is used as an input of DL iRM and iRM pre-emption features. As such, DL iRM and iRM preemption remains unchanged but takes the Iub load into account. The feature works as follow: RNC measures the load on the Iub Based on configurable thresholds the RNC determines an Iub link colour The Iub link colour is integrated to the existing radio cell colour Since the Iub bandwidth is shared between all the cells of the same Node B the Iub link colour is per Node B (more details below) Cell colour integrating Iub link colour is applied to: DL iRM iRM pre-emption, i.e. possibility to trigger pre-emption based on Iub congestion
Iub link colour determination

3 colours: Green when Iub is not loaded Yellow when Iub is moderately loaded Red when Iub is highly loaded Calculated at each allocation/release/reconfiguration of Iub resources on a given Iub interface Determined by comparing Iub load to configurable thresholds Green2Yellow_th (resp. Yellow2Green_th for hysteresis) Yellow2Red_th (resp. Red2Yellow_th for hysteresis)
Iub load 100% Yellow2Red_th Red2Yellow_th Green2Yellow_th Yellow2Green_th 0%
Iub link colour determination
Nortel Confidential
26
Integration of Iub link colour in radio cell colour Radio cell colour can be Green < Yellow < Red Iub link colour can be Green < Yellow < Red Cell colour = Max(Radio cell colour, Iub link colour)
Radio cell colour With Iub load
Iub link = Red
Iub link = Green
Example of cell colour integrating Iub link colour
3.16. FEATURE 27901 - UA04.2 PARAMETER EVOLUTION

This feature is used to enhance the operational effectiveness of the Access solution. It is used to ease day to day operations and reduce loss of service.
3.17. FEATURE 27930 - HSDPA SERVICE

Nortel UA04.2 HSDPA feature is an integrated E2E solution for the 2100MHz and 1900MHz spectrum. As far as HSDPA-capable UE solutions are concerned, the feature consists in handling all Rel5 UE Interactive/Background packet data flow by HS-DSCH as a no guaranteed traffic (no GBR) while ensuring SRB traffic on the associated HSDPA user DCH. The feature specifies Cell_DCH as the preferred RRC state for connection call setup. It also specifies the RRM features that optimize the UTRAN resource usage on HSDPA cells. UTRAN system parameters and counters are also defined in this document.
Nortel Confidential
27
3.18. FEATURE 27931 - HSDPA FLEXIBLE RESOURCE MANAGEMENT

The feature introduces a dynamic sharing of the Node-B PA power between HSPDA and R99 traffic. As far as the CCH channels and the power margin (SHO, ) are concerned, the UA04.1 Node-B PA power partitioning is not impacted. Concerning the PA resource availability, the Nortel CAC algorithm has been enhanced with respect to previous releases in order to take into account MAC-hs power management for HSDPA. To do so, the Node-B sends back to the RNC the Total_PW_On_None_HSDPA_Channels parameter for a dynamic update of the RNC CAC.
Power Margin (SHO ) Min PW for non data on DCH
PTraffic
Min PW for HS-DSCH & HS-SCCH
PW for CCH(s)
Flexible power management (figure 1) As presented above, the flexible power management for HSDPA ensures that the HSDPA throughput is maximized once the remaining Node-B PA power is not used for DCH traffic. As defined by the 3GPP standard, all UTRAN resources (PA power, ...) used for HSDPA can be preempted by any DCH traffic. In case of significant PA power load by DCH traffic, a Node-B parameter allows customers to ensure a minimum of PA power resources for cell HSDPA operation.
3.19. FEATURE 27932 - HSDPA STEP 1

As major objective in UA04.2, Nortel HSDPA UTRAN solution aims European/Asian 3G operators at offering commercial high speed DL packet accesses for not GBR PSD (Interactive/Background) traffic to mobile as well as nomadic in-building subscribers.
Operational impact
HSDPA is not supported on Powerwave PA D1/D2/D3. One additional VCC AAL2 has to be created on the Iub interface.
Nortel Confidential
28
3.20. FEATURE 27935 - MULTI-CARRIER HSDPA TRAFFIC SEGMENTATION

A UA04.2 supports 2 frequencies layers, one with UA04.2 HSDPA cells and the other one with UA04.2 R99 cells. See figure below:
SGSN
Non-HSDPA f1
RNC
HSDPA f2
BTS BTS
BTS
Multi Carrier HSDPA Traffic Segmentation

The feature provides the possibility to move the HSDPA capable mobiles on the HSDPA frequency layer. It also provides the possibility to move the R99/R4 only capable mobiles on the R99/R4 frequency layer. These movements are carried out at call set up. The implementation uses the RRC Connection Setup procedure with a Redirection to another frequency. The R99 to R5 redirection is triggered if all the following conditions are met: the UE is a R5 mobile (Access stratum release indicator) the UE requests MO/MT call for Interactive or Background traffic class there is at least one inter-frequency neighbor cell configured for the current cell which supports HSDPA
The R5 to R99 redirection is triggered if all the following conditions are met: the UE is a R99 or R4 mobile (absence of the Access stratum release implies R99) the call is not an emergency call there is at least one inter-frequency neighbor cell configured for the current cell
Nortel Confidential
29
3.21. FEATURE 27936 - HSDPA INTRA-FREQUENCY MOBILITY

In UA04.2 a given RNC or a given Node B may control HSDPA and non-HSDPA cells. See figure below:
SGSN
Non-HSDPA
RNC
HSDPA
BTS BTS BTS
HSDPA Intra Frequency Mobility

The Intra-frequency mobility feature supports the following mobility scenarios: a HSDPA UE moving from an HSDPA cell to another HSDPA cell a HSDPA UE moving from an non-HSDPA cell to a HSDPA cell a HSDPA UE moving from an HSDPA cell to non HSDPA cell
In Idle mode, the mobility is performed through the cell reselection mechanism. In HSDPA connected mode, a Hard Handover is performed in order to move the HSDSCH of the Primary cell, while the associated DCH performs Soft/Softer handover. If the new Primary cell is controlled by a Drift RNC, the HSDPA call is switched to DCH. If a UE connected to a Drift RNC on a DCH channel has its primary cell moving back to its Serving RNC, the call is upgraded to HSDPA.
Nortel Confidential
30
3.22. FEATURE 27937 - HSDPA ALARM MOBILITY

In UA04.2, a given Node B may control HSDPA and non-HSDPA cells on different frequencies. See figure below:
SGSN
Non-HSDPA f1
RNC
RNC
HSDPA f1 HSDPA f2
BTS
BTS
BTS
HSDPA Alarm Mobility (figure 4)

When the alarm criteria are reached in a HSDPA call, a handover toward a 2G cell is triggered. Note that an HSDPA capable UE in PS I/B single Radio Bearer from 2G or 3G network enters a 3G HSDPA cell in HSDPA mode.
Nortel Confidential
31
3.23. FEATURE 27939 - HS-SCCH POWER CONTROL

The feature aims to dynamically optimize the power allocated to HS-SCCH based on the radio conditions reported by the scheduled UE. The HS-SCCH power thresholds are set by the operators as a function of the number of CQI ranges.
The higher the available power for HS-PDSCH(s), the higher the shared DL throughput.
BTS transmit power

Power (SHO,) Margin
Maximum
HS-PDSCH
PA x%
HS-SCCH
DCH Common
Dynamic PA power usage for HSDPA (remaining power usage) ! Fixed code allocation for HSDPA cell operation !
NodeB Power Allocation
Nortel Confidential
32
3.24. FEATURE 27940 - H-BBU POOL ACROSS SECTORS

The feature enables the iCEM BBU sharing over sectors where HSDPA is implemented. The iCEM BBU (also named H-BBU) that implements the HSDPA software is managed by the Node B as a pool of processing resources over sectors. The H-BBU processing resources are dynamically shared over carrier/sectors (cells) as a function of the cell traffic load. Hence all H-BBU processing resources are potentially allocated to the MAC-hs scheduler of one of Node-B cells according to the traffic load per sector. Sharing a single H-BBU over 3 HSDPA cells is equivalent to consider that each cell will use on average a third of the processing capacity. Thanks to this feature the minimum iCEM configuration in a Node B is 2 iCEM128s.
H-BBU
3-sector H-BBU sharing BBU
. .
BBU
H-BBU H-BBU H-BBU
H-BBU/cell
BBU
. .
BBU
SEE FIGURE BELOW.

HBBU Pool Across Sectors (figure 7) H-BBUs handling HS-DPCCH HS-SCCH HS-PDSCH(s) BBU(s) handling DPCH(s) Associated HSDPA DPCH Cell CCH(s)
Nortel Confidential
33
3.25. FEATURE 27941 - NODE B MODULE OPERATION FOR HSDPA

Independently of the existing on-field Node-B configurations (first generation of BTS module, iModules), this feature ensures the functional coexistence between already installed modules (including CEM) and the additional iCEM(s) for the Node-B HSDPA support.
Nortel UMTS BTS architecture

iCEM128 BBU BBU iCEM128 BBU BBU BBU
TRM or iTRM CCM or iCCM
MCPA
DDM
iCEM64
TRM or iTRM TRM or iTRM
MCPA
DDM
iCEM64
BBU MCPA
DDM
CEM
BBU BBU
Digital
NodeB Module Operation for HSDPA
Radio
Nortel Confidential
34
3.26. FEATURE 27942 - ALWAYS-ON ON HSDPA

While downlink (DL) user traffic is carried over the HS-DSCH channel, the uplink (UL) traffic is carried over an associated DCH channel. This feature minimizes the impact of inactive HSDPA users on UTRAN resources by downgrading these users to CELL_FACH when inactive during a certain period of time. To save in NodeB base band resources (i.e. CEM), the UL dedicated channel is not maintained during a period of inactivity. In addition, since the admission process in the RNC for HSDPA is based on a maximum number of users that can be simultaneously supported, inactive users are not counted since they actually have no data to transmit. Thanks to Nortel Always-On feature it is possible to move inactive users to CELL_FACH and to PMM-idle mode in a second step based on user traffic monitoring and inactivity timers. Always-On on HSDPA works as follow: For each user mapped on HSDPA, the RNC monitors the traffic in UL and DL If UL and DL user traffic falls below the configured throughput threshold during T1 timer (1st inactivity timer), the UE is moved to CELL_FACH In a 2nd step, if UL and DL user traffic equal to zero during T2 timer (2nd inactivity timer), the RRC connection is released and the UE is moved to PMMidle mode (PDP contexts are kept active) When in CELL_FACH, upsizing (i.e. transition back to CELL_DCH) is triggered as soon as UL or DL DTCH buffer is above configured thresholds
Downsizing (T1 expiry)
Idle mode transition (T2 expiry)
CELL_DCH (UL DCH/ DL HS-DSCH)
CELL_FACH (RACH/FACH)
Idle Mode
Upsizing
Always On on HSDPA
Nortel Confidential
35
3.27. FEATURE 27943 - IUB BANDWIDTH LIMITATION HANDLING

With HSDPA, the effective throughput per UE is variable. A flow control mechanism has been introduced between the Mac-d (RNC) and the MAC-hs (NodeB) entities in order to fill the NodeB buffers with sufficient data to provide to the UEs and hence be more reactive to throughput variations. This flow control is based on three main procedures: The Capacity Request procedure that provides means for the CRNC to indicate for each session of each UE its buffer occupancy (at MAC-d level). The Capacity Allocation procedure generated by the NodeB to indicate to the RNC how many MAC-d PDUs are required for the desired session and the interval in which these data should be sent. This is based on the estimated throughput for this session and the number of remaining MAC-d PDUs in NodeB transmission buffer. The HS-DSCH data transfer procedure in which the RNC sends the MAC-d PDUs grouped in FP frames (1 to 255 PDUs per FP frame). The updated buffer occupancy is also given. The RNC may choose to send all the required MAC-d PDUs in a single FP frame, or to space out (within the notified interval) the transmission in several FPs.
In most of the cases, the available Iub bandwidth will be lower than what is required for when dealing with the worst case scenario, where high capacity UEs are asking for large amounts of data at the same time. This may generate temporary congestion situations over the Iub, which would lead to some random loss of frames and finally to a strong degradation of the throughput for the end user. This feature detects such temporary congestion situations before they happen and makes preventive decisions in order to limit their consequences to a minimum thus improving the throughput available for the end users.
Operational Impact
The Passport IMA defense must be deactivated. The BTS IMA defense must be activated.
Nortel Confidential
36
3.28. FEATURE 27945 - HSDPA RADIO BEARERS

HSDPA capable UEs require new features (such as hybrid-ARQ) or new modulation schemes to be supported. In order to enable different levels of terminal complexity, 12 UE categories have been defined with the maximum data rate (at physical layer) ranging from 900kbit/s for UE category 11 up to 14.4Mbit/s for UE category 10. In this release of HSDPA, UE categories 6 and 12 are supported, allowing a maximum data rate in downlink of respectively 3.65Mbit/s and 1.8Mbit/s. As a consequence the following radio bearers will be supported: Interactive or background / UL:8 DL: [max bit rate for UE categories 12 and 6] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH Interactive or background / UL:32 DL: [max bit rate for UE categories 12 and 6] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH Interactive or background / UL:64 DL: [max bit rate for UE categories 12 and 6] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH Interactive or background / UL:128 DL: [max bit rate for UE categories 12 and 6] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH Interactive or background / UL:384 DL: [max bit rate for UE categories 12 and 6] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH
Operational impact
For all the services, the new format is SRB3.4.
3.29. FEATURE 27947 - PS I/B UL:384

The following new PS I/B Radio Bearer (RB) configuration is introduced: PS I/B UL:384 kbit/s
In the RNC, UL and DL RB configurations are provisioned and managed independently. Hence any new UL rate (or DL rate) introduced in a given release can be combined with any DL rate (or UL rate) which is either introduced in the same release or already supported in previous releases.
List of supported UL and DL rate combinations
PS I/B UL:x DL:y x (kbit/s) y (kbit/s) 8 32 64 128 256

8
S S S S S
32
S S S S S
64
S S S S S
128
S S S S S
384
S S S S S
Nortel Confidential
37
384
Supported in previous release New UL/DL RB supported in that release
Nortel Confidential
38
3.30. FEATURE 28036 - MOBILITY PERFORMANCE IMPROVEMENTS

The following enhancements are introduced:
Faster Measurement activation at call establishment: thanks to the Measurement information broadcasted by the RAN in the SIB 11 the UE sends its Measurement Reports to the RNC earlier in the call establishment procedure enabling SHO mode earlier, when necessary. Support of RlRestore after RlFailure in SHO: this adds the ability to restore a link after temporary RL failure.
3.31. FEATURE 28040 - POWER CONTROL AND RATE MATCHING ENHANCEMENTS

This feature contains 3 improvements on Power Control and Rate Matching: 1. UL Power Control The UL OLPC algorithm is multi-referenced, i.e. the active transport channels are used to compute BLER and to be checked for updating the SIR target. 2. DL Power Control In previous releases the DL outer loop power control is limited for two reasons: There is only one DL BLER target (the quality target sent to the UE) defined for all the supported RABS (as defined by ASConf). When there is a reconfiguration from one set of RABs to another (change of ASConf), the DL BLER target is not updated.
Therefore, depending on the RAB configuration transitions during a call, the DL BLER target may not be the same for a given Radio Bearer. For Example, if one mobile establishes a voice call through CELL_DCH and another one through CELL_FACH, the first one will have two reference channels (speech + SRB) while the second one will have only one (speech). The first improvement is to align the object model to the UL Outer Loop Power Control (OLPC) one. The following items have been modified to ensure this alignment: Multiple reference transport channels per RAB combination (ASConf) A quality target (DL BLER) per RBSetConf
The second improvement applies when reconfiguring the RAB (as in Synchronious Radio Link Reconfiguration (SRLR)), the RNC in UA04.2 is able to reconfigure the DL OLPC on already established transport channels. 3. Rate matching configuration flexibility: Rate matching parameters and gain factors play an important role in the effective BLER value of one transport channel when it is multiplexed with other Transport channels in a RAB.
Nortel Confidential
39
These Rate Matching parameters need to be optimized in live networks in order to improve some Key Performance Indicators (KPI) such as call drop rates, in accordance with other network specific parameters. Therefore in UA04.2, Rate Matching parameters are Class 3 Operator parameters.
3.32. FEATURE 28047 - CALL ESTABLISHMENT KPI IMPROVEMENTS

The following feature is implemented in order to obtain Call Establishment Time and Success Rate improvements. SRLR enhancement: Dynamic delta CFN in UA04.2 is a function of the call type, RRC message, SRB, BLER and/or engineering parameter(s) ActiveSet evaluation is based on the last received measurement reports, right after activation time expiry
Idle mode
1
CELL_DCH 3.4 or 13.6
signalling phase
CELL_FACH 3.4
Dynamic deltaCFN
CELL_DCH
RAB is assigned
CELL_FACH
dynamic deltaCFN
SHO Evaluation based on MRs received during the signaling procedure deltaCFN
Measurement reports
t
SRB Establishment End of Signaling procedure RAB Assigned
SHO based on MRs received during signaling

Call Establishment KPI Improvements (figure 8)
Nortel Confidential
40
3.33. FEATURE 28109 - UA04.2 - 3GPP BASELINE & ADDITIONAL CRS

The goal of this feature is twofold: To define the 3GPP baseline to be used for the Nortel UA04.2 release. The 3GPP baseline is the set of 3GPP specifications used as input reference documents for: Design (functional specs, high / detailed level design, coding, testing ...) Statement of Compliance documents For each of the interfaces, the 3GPP baseline is defined by the following set of information: 3GPP release and 3GPP plenary number e.g. 3GPP no.24, june04. To keep a provision for additional corrections (that can be defined by the standard bodies further to the baseline selected) and to be compliant with these additional corrections in order to ensure correct product behavior and/or multivendor interoperability.
The 3GPP baseline for Nortel UA04.2 is defined in the following table:
Interface
3GPP release
Spec version
Iu Iur Iub Radio
R4 R5 R5 R5
3GPP R4 Dec 2003 3GPP R5 June 2004 3GPP R5 June 2004 3GPP R5 June 2004
The other infrastructure external interfaces (Iu-bc, Iu-pc and interfaces with the OMC) are out of the scope of this feature.
In addition to this baseline, UA04.2 will be compliant with some corrections approved after the above baseline by 3GPP when these corrections appear to be essential for proper product behavior or for solving potential interoperability issues. See the following document managed by the PPS Nortel team for these additional CRs : UMT/SYS/DD/015313 UTRAN and Core Network releases compliance with respect to 3GPP [R27].
Nortel Confidential
41
3.34. FEATURE 28144 - IRM SCHEDULING DOWNGRADING BASED ON TXCP

This feature is an enhancement of the iRM scheduling feature. It consists in changing the iRM Scheduling downgrading trigger based on RLC retransmissions counters to a trigger based on Transmitted Code Power (TxCP). The fact that the upgrading and downgrading triggers are different is problematic since Iub congestion can trigger downgrade while radio conditions are good and upgrade is triggered. Therefore, it is required to align dowgrade trigger on upgrade trigger. This feature also covers the support of iRM Scheduling feature, both downgrading and upgrading, over the Iur.
Operational Impact
As far as the NBAP dedicated measurement initiation, termination and report are not managed over the Iur. The iRM scheduling upgrading feature is not supported when the primary is on a DRNC, and the iRM scheduling downgrading feature is always performed on quality trigger when the primary is on a DRNC.
Nortel Confidential
42
3.35. FEATURE 28302 - Y-SPLITTER AT THE RNC

The Y-Splitter functionality allows a single fiber to connect to 1 of 2 possible interface cards. Provides FP equipment protection through use of LAPS (if ports on 2 cards are used) Provides NO line protection Implemented with 1 fiber pair connected through an external splitter to one of 2 interface ports (on separate cards typically)
The following is a description of Y-Splitter configuration. Two 16p OC3/STM1s deployed as dual protected FPs APS ports are configured as Y-Splitter enabled instead of APS 1+1 TX1 and TX2 optics are selectively enabled/disabled through S/W during HSM or EP RX1 and RX2 are selectively enabled/disabled through S/W during Hitless Software Migration procedure or Equipment Protection No Line protection is supported between MSS15k and Splitters
Passive fiber splitters

TX1
RX1 TX1
TX2
RX1
RX2
RNC
Y Splitter at RNC
CPE Device
Nortel Confidential
43
3.36. FEATURE 28330 - PS STREAMING UP TO 128KBIT/S

The following new Streaming Radio Bearers (RB) is introduced in UA04.2: PS Streaming DL:128 kbit/s
In the RNC, UL and DL RB configurations are provisioned and managed independently. Hence any new DL rate (respectivelyUL rate) introduced in a given release can be combined with any UL rate (resp. DL rate), which is either supported in this release or already supported in the previous releases. Therefore, since PS Streaming UL:16/DL:64 is supported in the UA04.1, as shown in the table below, PS Streaming UL:16/DL:128 is now supported.
3.37. FEATURE 28331 - PS STREAMING UP TO 128KBIT/S + PS I/B 8KBIT/S

The following new Streaming Radio Bearers (RB) is introduced in UA04.2: PS Streaming DL:128 kbit/s + PS I/B DL:8 kbits/s
In the RNC, UL and DL RB configurations are provisioned and managed independently. Hence any new DL rate (respectively UL rate) introduced in a given release can be combined with any UL rate (respectively DL rate), which is either supported in this release or already supported in the previous releases. Therefore, since PS Streaming UL:16/DL:64+PS I/B UL:8/DL:8 is supported in the UA04.1, PS Streaming UL:16/DL:128+PS I/B UL:8/DL:8 is now supported.
3.38. FEATURE 28847 - CHANGE OF SAI REPORTING

This feature tracks the location (at the SAI level) of a UE during a call, this is initiated at the core network level. When the Core Network sends a RANAP LOCATION REPORTING CONTROL whose request type is Change of SAI, the RNC sends a RANAP LOCATION REPORT message with the Service Area Identity whenever the information given in the previous LOCATION REPORT message or INITIAL UE MESSAGE message is not valid anymore.
Nortel Confidential
44
3.39. FEATURE 28900 - STSR1+1 NODE B

Where operators wish to activate a second carrier, this feature will make it possible to keep the same amount of power (Watts) dedicated to the first carrier and therefore will let RF design remain consistent.
The STSR1+1 configuration uses one MCPA and one TRM per carrier: one MCPA/TRM chain ( 1st carrier F1) is connected to Main path and a second MCPA/TRM chain ( paired RF chain ) is used for 2nd carrier ( F2 ) and connected to Diversity path, thus STSR1+1 uses 6 MCPAs per cabinet. F1 and F2 must be in the same band ( 2110-2170 MHz band for UMTS2100 or 19301990 MHz band for UMTS1900 ), but carriers may be spaced by 4,6MHz minimum or by up to 55MHz maximum.
This 2 carriers configuration delivers 33W/carrier at BTS port. This configuration uses the same cabling/modules as STSR2 with TX diversity. This feature in not intended to provide dual-band configuration capability.
STSR1+1 configuration
Nortel Confidential
45
3.40. FEATURE 29361 - HANDOVER AND RRM CONFCLASS RANGE EXTENSION

This feature defines the extension of the cardinality for Handover and RRM confClass objects to 15. This evolution is requested by operators in order to allow a finer optimization of Mobility and RRM parameters.
Handover and RRM confClass cardinalities have initially been set to 5, i.e. 5 different templates can be used or referred by the fddcells. However, analysis performed by operators showed that extending the cardinality of those classes would allow a finer optimization. Effectively, different environments (residential, high speed, indoor, outdoor, corner, etc ..) require specific SHO, HHO, or RRM parameterization.
3.41. FEATURE 30038 - NODE B CAC: MAX HSDPA USERS PER NODE B
This feature introduces a CAC based on the number of HSDPA users per NodeB.
Nortel Confidential
46
3.42. FEATURE 30311 - RAB BASED CAC

This feature enables call admission based on the up-link cell load. The UL Radio Bearer Adaptation introduced in this release is driven by the traffic variation and therefore can lead to frequent use of 384 kbps Radio Bearer. At this rate the UEs generate a significant interference level as illustrated in the following diagram.
Noise rise
Nois e ris e [dB] 6 5 4 3 2 1 0 1 2 3 4 s im ultane ous UL 384 calls Theoretical Noise rise Measured Noise rise
Noise increase with UL 384 kbit/s RBs

The existing Call Admission Control located in the Node-B monitors the resources left for new calls. The point is that NodeB HW can accept more than the radio can support and therefore wont prevent the issue described above. The increase of the noise rise contributes to what is known as cell breathing (as illustrated in the following figure) which rends the network unstable.
SF = 256
Spreading Factor
SF = 32
SF = 8 Low speed Data High speed Data
Speech
Node B
Relative distance
The RAB based CAC is therefore introduced to keep the level of UL interferences at an affordable level.
Nortel Confidential
47
4.
ACCESS OAM05.0 FEATURES

This chapter covers the OAM05.0 portfolio dedicated to the Access domain. This chapter gives: in 4.1: the list of the OAM05.0 features dedicated to the Access domain as defined in [R29] from 4.2 to 3.70: the description of all the features as defined in [R3] and in [R29]
4.1.
ACCESS OAM05.0 FEATURE IMPACT LIST

The following tables give the list of the new Access OAM05.0 features and their impacts.
4.1.1 ACCESS OAM FAULT MANAGEMENT

Network Architecture Compatibility Table/Upgrade path Interfaces changes Fault Management System & Security Management Upgrade, patch & migration Configuration Management Performance Management
Feature ID
Platform
NRP
Feature Title
27514 30266
Continued CM/FM/PM for Access Shelf Level Display Zoom In / Zoom Out
x x
FAP
Nortel Confidential
48
4.1.2 ACCESS OAM CONFIGURATION MANAGEMENT

Feature ID
Platform
NRP NRP
Feature Title
26444 27233 27360 29109
RRM Instances Explicit Naming Smart activation enhancements RNC Audit Report file naming evolution WPS checks
x x No operational impact x
4.1.3 ACCESS OAM PERFORMANCE MANAGEMENT

Feature ID
Platform
Feature Title
27517 27520 28538
Call Trace Configuration Wizard Enhancements UMTS UTRAN Performance Metrics and Reports UTRAN Call trace KPIs
x x x
FAP
FAP
Nortel Confidential
49
4.1.4 ACCESS OAM MANAGEMENT
ADMINISTRATION
Compatibility Table/Upgrade path
AND
SECURITY
Feature ID
Interfaces changes
Fault Management
System & Security Management
Upgrade, patch & migration
Configuration Management
Performance Management
Platform
NRP NRP x
Feature Title
27809
27811
28142 28143 28377
W-NMS support of IPSec to RNC W-NMS support of Radius authentication for RNC Upgrade path: UA4.0 -- > UA4.2 Upgrade path: UA4.1 -- > UA4.2 Migration RNC 1000 -- > RNC 1500 UA4.2
x x x
4.1.5 ACCESS OAM FEATURE ACTIVATION RECONFIGURATION PROCEDURES

Compatibility Table/Upgrade path Fault Management System & Security Management Upgrade, patch & migration Configuration Management Performance Management
AND
NETWORK
Feature ID
Interfaces changes
Platform
Feature Title
28536 28718
Reconfiguration Procedures HSDPA Activation Procedure
FAP x x
FAP
Nortel Confidential
50
4.2.
FEATURE 26444 - RRM INSTANCES EXPLICIT NAMING

In many cases, an RRM instance corresponds to a specific QoS class (e.g. Gold/Silver/Bronze of Olympic Services), a specific RAB, RB, services, Measurement pattern, cellColors (Green, yellow, red), Radio Link Condition (good/bad) etc. This feature brings an evolution in the object model in order to provide explicit naming of the RRM instances, both at the W-NMS Main server and WPS level, including the CM XML files. RRM instances are now identified with an explicit string selected from a predefined set defined in the RAN Model. For upgrade complexity reasons, this enhancements is introduced starting from UA4.2 but will not be propagated to previous UA releases.
4.3.
FEATURE 27233 - SMART ACTIVATION ENHANCEMENTS

This feature describes an enhancement brought to the smart activation mechanism with regards to the handling of the lock/unlock commands so as to limit the downtime. In the current implementation, the required locks detected during the synchronization steps are performed globally at the beginning of the synchronization, and once all create-delete-set operations have been performed, required unlock are performed. This process has the main drawback of locking resources longer than the operation effectively requires, leading to a non optimized impact on service. The requested enhancements consists in optimizing the lock/unlock behavior so as to limit the downtime to the operated object. More information on this feature can be found in document reference [R18] Functional Notes Smart Activation.
4.4.
FEATURE 27360 - RNC AUDIT REPORT FILE NAMING EVOLUTION

This feature allows to historize the RNC audit reports and to be able to compare with an old report. The previous behavior was to use the same name for RNC audit reports. Once a new report was generated, the previous one was overwritten. Starting OAM05.0, the RNC audit report follows the following naming convention: RNC<UserLabel>_<YYYYMMDDHHMM>.xml This new naming convention ensures that the RNC audit report will no more be overwritten and therefore be available. Note that these reports will be stored on the Main server until they are purged (refer to feature 26885 Smart purge for more information to enhanced purge mechanism introduced in OAM05.0).
Nortel Confidential
51
4.5.
FEATURE 27514 - CONTINUED CM/FM/PM FOR ACCESS

This feature provides the support of newly introduced UA4.2 release and the backward compatibility of the Radio Access devices (UA4.1 and UA4.0) for the Main and Performance servers. At a high level, the UA04.2 Product Objectives are Commercial Launch of HSDPA: Significantly increase UMTS downlink data transfer speeds Product Stability and Quality: Stable network behavior against stress and load in commercial context Quality of Service: Enhancement of UTRAN accessibility and mobility robustness Operational Effectiveness: Parameters on-line modifications, call trace enhancements, reduce supervision loss by OAM servers
Nortel Confidential
52
4.6.
FEATURE 27517 - CALL TRACE CONFIGURATION WIZARD ENHANCEMENTS

This feature consists of enhancing the UTRAN Call Trace Wizard application to allow for better management of the Call Trace sessions. The enhancements are summarized as follows:
GUI logic evolution

Add a new operation List Call Trace Sessions to enable the user to list the created call trace sessions and their status. Add three new configurable parameters per Trace Session (startTime, fileUploadSize, fileUploadPeriod). Add printing capabilities to enable the printing of the Trace Session status and parameters.
The new version of the Call Trace Wizard supports the following operations on each trace session Create/Delete/List/Print.
Template edition
The following operations are supported for each Call trace template: - Create - Delete - List - Print Please note the following: The Trace Records are not modifiable (they can only be displayed). The Trace Mode parameter is applicable at the filtering level. The predefined templates cannot be modified or deleted by the users.
New Call Trace sessions Parameters

Enable the user set specific reporting period to each type of the following NBAP dedicated measurement. The reporting periods can be set within the following range [500ms, 2s]:
NbapDedicatedMeasConfigForCallTrace.roundTripTimeReportPeriodicity NbapDedicatedMeasConfigForCallTrace.roundTripTimeRequired NbapDedicatedMeasConfigForCallTrace.sirReportPeriodicity NbapDedicatedMeasConfigForCallTrace.sirRequired NbapDedicatedMeasConfigForCallTrace.transmittedCodePowerReportPeriodicity NbapDedicatedMeasConfigForCallTrace.transmittedCodePowerReportRequired
The Call Trace Wizard is 2 releases backward compatible. However the above parameters are supported only on the RNC aligned with UA 4.2 load. For RNC running older loads (UA 4.0 and UA 3.1) the Call Trace Wizard blocks the user from configuring the latter parameters.
Creation of multiple CTb Sessions on a given RNC:

The Call Trace wizard allows the user to setup up to 5 CTb sessions simultaneously on a given RNC.
Nortel Confidential
53
4.7.
FEATURE 27520 - UTRAN PERFORMANCE METRICS AND REPORTS

This feature specifies the list of Utran Performance Metrics and Reports to be build based on the list of new counters introduced in OAM05.0 and managed by the NIMSPrOptima for W-NMS solution. Performance metrics are defined by the engineering organization.
4.8.
FEATURE 27809 - W-NMS SUPPORT OF IPSEC TO RNC

This feature provides IPSec solution capabilities between the W-NMS solution servers (main servers and performance server) to the RNC 1500 (specifically, the RNC A-Node and RNC I-Node are supported). The following IPSec key capabilities are supported: Support to transport mode Support of ESP Support for DES and 3DES for encryption Support of HMAC-MD5 Support of HMAC SHA-1
Manual management of keys ( IKE is not supported in this release )
The IPSec security associations are set up to provide confidentiality of the following traffic flows that contain sensitive credentials related information between the OAM servers and the RNC 1500: ftp telnet FMIP NTP Radius
Nortel Confidential
54
4.9.
FEATURE 27811 - W-NMS SUPPORT OF RADIUS AUTHENTICATION FOR RNC

This feature provides support of centralized authentication for the RCN 1500, using a centralized Radius authentication solution. The RNC implements a Radius client, and for authentication requests are directed to the RNC, for telnet, ftp, fmip, and local port requests, for which no local account exists, a Radius authentication request is directed to a centralized Radius sever on the W-NMS main server. For the RNC, a default set of 5 roles has been defined in this release, within the centralized W-NMS authentication server, and when there is an authentication request received from the RNC, as part of the Radius response, the appropriate VSA (Vendor Specific Attribute) is sent back in the Radius response to the RNC, to enable the appropriate authorization for the specific login.
Request Access User X Read-Write OK

NE
Aut ho Use rize rX ?
Re a
d -W rite O
LDAP database User X --> R/W role

W-NMS Main Server
4.10. FEATURE 28142 - UPGRADE PATH: UA4.0 UA4.2

OAM05.0 release supports 2 UA upgrade paths: UA4.0 -- > UA4.2 for RNC 1000 UA4.1 -- > UA4.2 for RNC 1000 and RNC 1500
For RNC-1000 upgrade, following upgrade types are supported: Type 7 Type 6
For RNC-1500 upgrade, following upgrade types are supported: With new MIB With Current MIB
Nortel Confidential
55
4.11. FEATURE 28143 - UPGRADE PATH: UA4.1 UA4.2

OAM05.0 release supports 2 UA upgrade paths: UA4.0 -- > UA4.2 for RNC 1000 UA4.1 -- > UA4.2 for RNC 1000 and RNC 1500
For RNC-1000 upgrade, following upgrade types are supported: Type 7 Type 6
For RNC-1500 upgrade, following upgrade types are supported: With new MIB With Current MIB
4.12. FEATURE 28377 - MIGRATION RNC 1000 RNC 1500 UA4.2

UTRAN4.1 release has introduced an evolution of the existing RNC 1000 product, c.f. UA feature 24257 RNC 1500 Product Introduction described in UA04.1 CPO/FPG. This feature allows migration of RNC 1000 UA4.2 to RNC 1500 UA4.2. At a high level, this migration requires multiple steps. Additional Software download Removal of no longer used modules, retrofit Hardware modules Physical and Logical connectivity modification Provisioning modification
As a consequence following teams inputs and modules are required: Team: I&C and OAM Operations Modules: OAM Modules (SRM, SRS, WAUT, CM XML Import/Export)
The procedure has been designed to reduce at much as possible the duration (around 3 hours), the OAM supervision loss (30 minutes) and the end customer services (10 minutes).
Nortel Confidential
56
4.13. FEATURE 28536 - RECONFIGURATION PROCEDURES

This feature ensures that the previously supported Network Reconfiguration Procedures and Feature Activation Procedures are updated to run under an OAM05.0 environment. NodeB addition Inter-RNC nodeB reparenting Neighboring plan update Scrambling code plan update Cell Fach activation OCNS activation IuPc Agps location services 3G to 2G Ho with/without compress mode LAC/RAC update Access part only NRP NRP NRP NRP FAP FAP FAP FAP NRP
4.14. FEATURE 28538 - UTRAN CALL TRACE KPIS

This feature introduces the concept of reference call to better characterize the UTRAN Call Trace performance. It defines the W-NMS Call Trace KPIs in terms of minutes of reference call for a list of common activation profiles and for different Performance Server hardware configurations. It updates the maximum duration of call Trace sessions for different hardware configurations according to maximum NE throughput, CPU quota (defined in FEATURE 27437) and limitations on the number of simultaneous call trace sessions (as specified in the Call Trace System Specifications defined in UMT/SYS /DD/00077). It defines the rules for activation of concurrent call trace sessions.
4.15. FEATURE 28718 HSDPA ACTIVATION PROCEDURE

HSDPA is a major evolution of the Radio resource management of UMTS network. It impacts several objects / class of the configuration model. The Activation Procedure for HSDPA provides guidelines and stepped operations path to activate the feature.
Nortel Confidential
57
4.16. FEATURE 29109 - WPS CHECKS

A major added-value of the WPS lies in its ability to check the consistency of data to be delivered on the live network. On top of the model checks delivered with the object model, WPS provides a wide collection of engineering checks derived from Nortel engineering expertise in configuring UTRAN networks. WPS has this unique advantage of centralizing the configurations of all UTRAN Network Elements, hence allowing cross-NEs consistency checks. In OAM05.0, around 250 new checks are implemented in WPS.
Nortel Confidential
58
4.17. FEATURE 30266 - SHELF-LEVEL DISPLAY ZOOM IN / ZOOM OUT

This feature provides Zoom in / Zoom out / Fit in window / Zoom reset / Zoom back capabilities in the shelf level display. This feature is applicable to RNC and NodeB sheld level display. It provides the following capabilities:
Normal View or Reset Zoom
Zoom fit in window
Zoom In
Zoom Out
Nortel Confidential
59
5.
PLATFORM
This chapter gives any information about the hardware impact due to the UA04.2 introduction. All the information is available in [R1].
5.1.
UA04.2 PLATFORM FEATURES

Feature 27930 - HSDPA Service Feature 27931 - HSDPA Flexible Resource Management Feature 27932 - HSDPA Step1 Feature 27935 - Multi-carrier HSDPA traffic segmentation Feature 27936 - HSDPA Intra-frequency Mobility Feature 27937 - HSDPA Alarm Mobility Feature 27939 - HS-SCCH Power Control Feature 27941 - Node-B Module Operation For HSDPA Feature 27942 - Always-On on HSDPA Feature 28900 - STSR1+1 NodeB
5.2.
OBSOLETE HARDWARE
None
5.3.
NEW HARDWARE
None
Nortel Confidential
60
5.4.
MODIFIED HARDWARE
5.4.1 HSDPA IMPACT

HSDPA is only supported on STSR-1 and STSR-2 (HSDPA can be deployed on one frequency only). HSDPA is not supported with OTSR.
H-BBU is only supported on iCEM (but mixity with alpha modules is supported). One, two or three H-BBU can be deployed by Node B. Note: H-BBU corresponds to the same hardware than a normal BBU but running a different software. Possible BBU configurations are:
D-BBU: BBU managing dedicated services H-BBU: BBU managing HSDPA The number of H-BBUs to allocate in the BTS is determined by the number of cells which have different hsdpaResourceId values but ignoring the ones for which hsdpaResourceActivation is false. It is not possible to have more than 3 H-BBUs. All BBUs on CEM alpha are considered as D-BBUs. On iCEM, H-BBUs are allocated in priority compared to D-BBUs, knowing that if there are only iCEM in the BTS, the first BBU is a D-BBU (for common channels). The remaining BBUs are D-BBUs. This allocation is done when BTS starts up or when a new CEM board is plugged in. HBBUs are not reallocated when a CEM hosting an H-BBU fails. The mapping of cells on H-BBUs is determined by the value of hsdpaResourceId: it gives directly number of the H-BBU on which the cell has to be mapped. In case of failure of this H-BBU, it is not possible to remap the impacted cells on other H-BBUs. If it is not possible to map on an H-BBU a cell for which HSDPA has been configured (hsdpaResourceActivation is true), an alarm is generated by the BTS on this BtsCell (eg : only CEM alpha in the BTS).
Nortel Confidential
61
5.4.2 STSR1+1 IMPACT

No impact on RNC side: from RNC point of view, an STSR1+1 configuration is equivalent to an STSR2 configuration.
The STSR1+1 configuration and all depopulation (BTBR1+1 and OTOR1+1) are possible on all BTS that can host 6 MCPA. In this release, this includes the following BTS: 12010-1-700 (a.k.a indoor 700) 12010-1-600 (a.k.a indoor 600) 12010-2 (a.k.a indoor2) 12020-1 (a.k.a outdoor1) 12020-2 (a.k.a outdoor2)
The STSR1+1 configuration does not impose a restriction on usage of CEM, iCEM, TRM, iTRM, xTRM, CCM, iCCM. The control on MCPA is the following In Outdoor2, MCPA NTUM30AA is not allowed (Outdoor2 requirement) In Outdoor1, MCPA NTUM30AA is allowed the following mode o o 30W mode only if there are 6 MCPA 30W or 45W otherwise
In Indoor BTS, MCPA NTUM30AA is allowed in 30 or 45W Other MCPA (other than NTUM30AA) are allowed in any BTS in 30 or 45W
In STSR1+1 configuration, 2 TRM are needed, the slot position in the digital shelf of these 2 TRM are identical as in STSR2 configuration. Note: the 1+1 configuration is not managed with TX SPLITTER. In other words, OTSR1+1 configuration and OTBR1+1 configuration are not allowed.
Nortel Confidential
62
5.5.
HARDWARE BASELINE
This paragraph describes the Hardware Baseline for UMTS products for UA04.2. The baseline for one system release lists the FRU (Field Repair Unit) supported by the release. The FRUs are defined by their part number code without the factory revision level, because the fact that the equipment is exchangeable, is not depending of the factory revision level. In case of exception, the baseline specifies the factory revision levels not supported by the system release
The hardware baseline information will be available in a future edition of this document. In the meantime, would you please direct your inquiries to your Nortel Account.
Nortel Confidential
63
6.
6.1.
COMPATIBILITY TABLE / UPGRADE PATH

UA04.2 COMPATIBILITY / UPGRADE PATH FEATURES
None
6.2.
SYSTEM UPGRADE PATHS & COMPATIBILITY MATRIX

Refer to [R2] for additional information.
Nortel Confidential
64
7.
TOOLS
TBC
Nortel Confidential
65
8.
8.1.
FAULT MANAGEMENT
UA04.2 FAULT FEATURES
Feature 26407 - IPsec support validation on RNC Feature 26409 - Support of Radius Client on RNC Feature 27930 - HSDPA Service Feature 27931 - HSDPA Flexible Resource Management Feature 27932 - HSDPA Step1 Feature 27935 - Multi-carrier HSDPA traffic segmentation Feature 27936 - HSDPA Intra-frequency Mobility Feature 27937 - HSDPA Alarm Mobility Feature 27939 - HS-SCCH Power Control Feature 27940 - H-BBU Pool Across Sectors Feature 27941 - Node-B Module Operation For HSDPA Feature 27942 - Always-On on HSDPA Feature 28302 - Y Splitter at the RNC Feature 28900 - STSR1+1 NodeB
8.2.
OAM05.0 FAULT FEATURES

Feature 27339 - Persistent Alarm Mgr user preferences Feature 27344 - W-NMS Grid View Feature 27514 - Continued CM/FM/PM for Access Feature 28401- Operator Annotation on Alarm type Feature 28403 - Alarm Forwarding to multiple destinations Feature 28404 - Automatic acknowledgement of Alarm
8.3.
UA04.2 NEW/DELETED/MODIFIED ALARMS

Refer to Annex A.
Nortel Confidential
66
8.4.
ALARM MANAGER WINDOW

27339 Persistent Alarm Mgr user preferences Refer to Chapter Interface Changes.
27344
W-NMS Grid View
Refer to Chapter Interface Changes.
28401
Operator Annotation on Alarm type
28403
Alarm Forwarding to multiple destinations
Feature 28404 - Automatic acknowledgement of Alarm Refer to Chapter Interface Changes.
Nortel Confidential
67
9.
9.1.
CONFIGURATION MANAGEMENT
UA04.2 CONFIGURATION FEATURES
Feature 13451 - 3G to 2G Redirection for Speech calls Feature 24082 - MSA32 enhancement to sustain 28E1 with IMA Feature 26234 - NodeB support of 2 OAM IP addresses Feature 26407 - IPsec support validation on RNC Feature 26409 - Support of Radius Client on RNC Feature 27330 - RB adaptation based on traffic: DL and UL with start @64kbit/s Feature 27597 - Service-based inter-freq/inter-RAT selection for HHO Feature 27740 - Iub load in iRM Feature 27901 - UA04.2 Parameters evolution Feature 27930 - HSDPA Service Feature 27931 - HSDPA Flexible Resource Management Feature 27932 - HSDPA Step1 Feature 27935 - Multi-carrier HSDPA traffic segmentation Feature 27936 - HSDPA Intra-frequency Mobility Feature 27937 - HSDPA Alarm Mobility Feature 27939 - HS-SCCH Power Control Feature 27940 - H-BBU Pool Across Sectors Feature 27941 - Node-B Module Operation For HSDPA Feature 27942 - Always-On on HSDPA Feature 27943 - Iub Bandwidth Limitation Handling Feature 27945 - HSDPA Radio Bearers Feature 27947 - PS I/B UL:384 Feature 28036 - Mobility Performance Improvements Feature 28047 - Call Establishment KPI Improvements Feature 28144 - iRM Scheduling downgrading based on TxCP Feature 28330 - PS Streaming up to 128kbit/s Feature 28331 - PS Streaming up to 128kbit/s + PS I/B 8kbit/s Feature 28847 - Change of SAI reporting Feature 28900 - STSR1+1 NodeB Feature 29361 - Handover and RRM ConfClass range extension
Nortel Confidential
68
Feature 30038 - Node-B CAC: Max HSDPA users per Node-B
Nortel Confidential
69
9.2.
OAM05.0 CONFIGURATION FEATURES

Feature 26444 - RRM Instances Explicit Naming Feature 27217 - WPS Partial Template Import & Export Feature 27233 - Smart activation enhancements Feature 27478 - WPS Cross-domain and Scalable Installation Feature 27514 - Continued CM/FM/PM for Access Feature 27672 - WPS Enhancements Feature 28282 - CM files backward compatibility Feature 29109 - WPS checks Feature 29231 - Template file migration
9.3.
UA04.2 NEW/DELETED/MODIFIED PARAMETERS

Refer to Annex B.
9.4.
SMART ACTIVATION
27233 Smart activation enhancements This feature is associated to the 23257 feature (Smart activation) available in OAM03.1. From OAM05.0, the synchronization sequence handles the creation/deletion and the MO update operations differently to avoid long lock periods on class 2 parameters update: All create/delete of MO instances are performed in a dedicated group where all locks are performed at the beginning of the group processing, and all unlocks are performed at the end of the group processing. Updates on MO instances are performed on each instance sequentially and the duration of the class 2 parameters lock is limited to the duration of the update of the instance.
This enhancement is a first step and will be enriched in the next releases.
Nortel Confidential
70
10. PERFORMANCE MANAGEMENT

10.1. UA04.2 PERFORMANCE FEATURES
Feature 13451 - 3G to 2G Redirection for Speech calls Feature 25100 - UTRAN Call Trace: Additional Measurement Reporting (NBAP Common measurement, RRC BLER, etc..) Feature 26407 - IPsec support validation on RNC Feature 26409 - Support of Radius Client on RNC Feature 27219 - Intra-frequency Event-triggered Measurements Feature 27729 - UA04.2 Counters evolution Feature 27330 - RB adaptation based on traffic: DL and UL with start @64kbit/s Feature 27597 - Service-based inter-freq/inter-RAT selection for HHO Feature 27740 - Iub load in iRM Feature 27930 - HSDPA Service Feature 27931 - HSDPA Flexible Resource Management Feature 27932 - HSDPA Step1 Feature 27935 - Multi-carrier HSDPA traffic segmentation Feature 27936 - HSDPA Intra-frequency Mobility Feature 27937 - HSDPA Alarm Mobility Feature 27939 - HS-SCCH Power Control Feature 27940 - H-BBU Pool Across Sectors Feature 27941 - Node-B Module Operation For HSDPA Feature 27942 - Always-On on HSDPA Feature 27943 - Iub Bandwidth Limitation Handling Feature 28144 - iRM Scheduling downgrading based on TxCP Feature 28330 - PS Streaming up to 128kbit/s Feature 28331 - PS Streaming up to 128kbit/s + PS I/B 8kbit/s Feature 30311 - RAB based CAC
10.2. OAM05.0 PERFORMANCE FEATURES

Feature 27514 - Continued CM/FM/PM for Access Feature 27517 - Call Trace Configuration Wizard Enhancements Feature 27520 - UMTS UTRAN Performance Metrics and Reports
Nortel Confidential
71
Feature 28167 - SDA PC Based Tool Enhancements Feature 28538 - UTRAN Call trace KPIs
10.3. UA04.2 NEW/DELETED/MODIFIED COUNTERS

Refer to Annex C.
Nortel Confidential
72
11. SYSTEM AND SECURITY MANAGEMENT

11.1. UA04.2 SYSTEM AND SECURITY MANAGEMENT FEATURES
Feature 26234 - NodeB support of 2 OAM IP addresses Feature 26407 - IPsec support validation on RNC Feature 26409 - Support of Radius Client on RNC
11.2. RNC SECURITY

26407 IPsec support validation on RNC CDN Passport IPSec feature (CD 2089) is supported on RNC 1500 from UTRAN V4.2 after rebasing with PCR 6.1.1. This feature will allow to support IPSec at RNC level. Supporting IPSec on the RNC is required to secure the OAM traffic between OMC-R and RNC CP management virtual router. The purpose of the present security feature is to improve the security of the UMTS RNC OAM Plane toward the following Network Threats: Masquerading Denial of Service Hacking Sabotage Intrusion Snooping Modification of Data
In order to improve the level of security toward the previous threats, we propose to introduce a secured data channel between the RNC site and the OMC site of network. The secured data channel would make use of the IPSec technology. IPSec in RNC 1500 will support: Data integrity Data authentication Manual ESP
Nortel Confidential
73
26409
Support of Radius Client on RNC
This feature will allow to support Radius at RNC (1500 and above, including AN) level. Supporting Radius on the RNC is required to secure the link to this NE and will allow supporting centralized password management. SE/PE is not impacted by this feature as the OAM is responsible for the authentication in that case. The external DATA base is the one to be looked at first. If the link to the Radius server is missing, the local DATA base is used. If the link becomes available, the user should be required to re-authenticate.
11.3. NODE B AVAILABILITY

Currently the NodeB stores only 1 OAM IP address. In case of OAM disaster, the NodeB supervision is lost for long time as the NodeB does not store multiple IP addresses (therefore multiple OAM server). Having the NodeB supports multiple IP address (as all passport based Node, MSC and HLR, etc) allows development of high availability OAM platform to cover disaster recovery situation. This feature will allow reducing the OAM unavailability time by 3 to 6 hours.
Nortel Confidential
74
12. UPGRADE, PATCH AND MIGRATION MANAGEMENT

This section covers the upgrade and patch procedures for the UMTS5.0 release. It presents the OAM operations needed to upgrade the UTRAN network.
12.1. UA04.2 UPGRADE, PATCH AND MIGRATION MANAGEMENT FEATURES

No specific feature. The migration paths are covered by the OAM portfolio. Refer to paragraph 11.2.
12.2. OAM05.0 UPGRADE, PATCH AND MIGRATION MANAGEMENT FEATURES

Feature 24157 - Patch documentation available from Software repository interface Feature 28142 - Upgrade Path: UA4.0 -> UA4.2 Feature 28143 - Upgrade Path: UA4.1 -> UA4.2 Feature 28377 - Migration RNC 1000: UA4.2 -> RNC 1500 UA4.2 Feature 29793 - Domain Upgrade Paths OAM 5.0.0 to OAM 5.0.1
12.3. GENERAL OPERATIONAL CONSTRAINTS

TBC
12.4. OBSOLETE UPGRADE PROCEDURES

None
Nortel Confidential
75
12.5. NEW UPGRADE PROCEDURES 12.5.1 411-8111-241: RNC 1500 SOFTWARE UPGRADE PROCEDURE USING OAM 5.0 (INTER RELEASE NEW MIB)
This procedure supports the RNC 1500 software upgrade from UA 4.1 to UA 4.2. Description: The upgrade overall process is presented in the following figure:
Steps 1 to 6 have no impact on the RNC service. During steps 5 and 6, the OAM and the RNCs will not be synchronized, but with no impact on service. During step 7, the activation is performed sequentially, first on the interface node, then on the access node. Service loss starts with step 7 (activation), and ends with I-node provisioning upgrade completion.
Nortel Confidential
76
The detailed procedure is presented in the following figure:
Durations are given for a maximal network configuration.
The detailed fallback procedure is presented in the following figure:
Constraints: During the upgrade, call traces linked to the RNC to upgrade are lost.
Nortel Confidential
77
A firmware upgrade might be needed. For the upgrade paths described in this procedure, there is also a provisioning upgrade; during this operation, the manufacturer parameters of the RNC configuration are lost (set to the default value). The values can be recovered by running WICL scripts during the upgrade. A fallback can only be conducted during the maintenance window and probative phase. If a fallback is needed out of the probing phase, and if any configuration update occurred since the upgrade, contact your next level support.
Durations: Durations are given for a maximal configuration, including 4 RNCs Maintenance window: The timeframe during which disruptive operations are performed on the network, including critical tests and the fallback operation if needed is: 215 minutes plus 60 minutes for the fallback. Outage duration: During the upgrade, the service is lost during the restart of the RNC nodes at the software activation phase. Duration is 15 minutes. Upgrade duration: The global operational duration of an upgrade is about 9 hours and 20 minutes. This duration doesnt take into account the fallback duration.
Nortel Confidential
78
12.6. MODIFIED UPGRADE PROCEDURES 12.6.1 411-8111-240: NODE-B SOFTWARE UPGRADE PROCEDURE USING OAM 5.0 (INTRA UPGRADE)
This procedure performs a software upgrade of Node-Bs. It supports the following upgrade paths: UA40-UA40, UA41-UA41, UA42->UA42. Description: The upgrade is composed of two main steps: The software download (up to 200 downloads in parallel) The activation (activation is followed by a nodeB reset. This activation includes a service and supervision loss)
The procedure includes a fallback operation.
The upgrade procedure sequence is presented in the following figure:
The fallback sequence is presented in the following figure:
Evolutions for OAM 5.0: FDDCell osi state check added.
Constraints:
Nortel Confidential
79
The Rncs to which the Node-Bs to be upgraded are parented should have been upgraded to UA4.2 prior to the beginning of the upgrade. Features activations and any kind of configuration change must not be performed in parallel with this upgrade. Hardware intervention, upgrade using the TIL or configuration changes from OAM are not permitted. During the Upgrade, counters generated on the Node-Bs are lost. It is recommended to perform bulk Node-B upgrade on a RNS basis. Note that no build is needed during this procedure.
Durations:
Duration: Taking into account the pre/post checks and all the steps needed to complete the upgrade, the global upgrade duration is estimated to 230 minutes for 200 Node-B. Maintenance window: The timeframe during which disruptive operations are performed on the network, including the fallback duration is: 50 minutes plus 40 minutes for the fallback (100 nodeBs) Outage: The impact on service occurs at the end of the software activation, when the Node-B restart. This duration is 5 minutes, whatever the number of Node-Bs.
Nortel Confidential
80
12.6.2 411-8111-239: NODE-B SOFTWARE UPGRADE PROCEDURE USING OAM 5.0 (INTER UPGRADE)
This procedure performs a software upgrade of Node-Bs. It supports the following upgrade paths: UA40-UA42, UA41-UA42. Description: The upgrade is composed of three main steps: The software download (up to 200 downloads in parallel) The provisioning upgrade at OAM level with the WAUT (Wireless Access Upgrade Tool) The activation (including the new MIB download to the Node-Bs)
During step 4, the OAM database gets out of synchronization with the Node-B MIB The outage occurs during activation.
Nortel Confidential
81
Evolutions for OAM 5.0: FDDCell osi state check added. Update with WAUT interface evolutions
Constraints: The Rncs to which the Node-Bs to be upgraded are parented should have been upgraded to UA4.2 prior to the beginning of the upgrade. Features activations and any kind of configuration change must not be performed in parallel with this upgrade. Hardware intervention, upgrade using the TIL or configuration changes from OAM are not permitted.
Nortel Confidential
82
During the Upgrade, counters generated on the Node-Bs are lost. It is recommended to perform bulk Node-B upgrade on a RNS basis.
Durations:
Duration: Taking into account the pre/post checks and all the steps needed to complete the upgrade, the global upgrade duration is estimated to 255 minutes for 200 Node-B. Maintenance window: The timeframe during which disruptive operations are performed on the network, including the fallback duration is: 55 minutes plus 55 minutes for the fallback (100 nodeBs) Outage: The impact on service occurs at the end of the software activation, when the Node-B restart. This duration is 5 minutes, whatever the number of Node-Bs.
Nortel Confidential
83
12.6.3 411-8111-238: RNC 1000 SOFTWARE UPGRADE PROCEDURE USING OAM 5.0 TYPE 7 INTRA RELEASE
This procedure describes the RNC 1000 software upgrade type 7. It supports the following migration paths: UA4.0 to UA4.0 UA4.1 to UA4.1 UA4.2 to UA4.2
Upgrade type is defined by the software delivery.
Description: The upgrade is composed of two main steps: The software download. This operation is done in parallel for the target RNCs (up to 4). For each RNC, the download is performed sequentially for the control node, the interface node and the access node. The software activation. This is a type 7 and impacts the RNC service. For each RNC the activation is performed in parallel for the Control Node and the Interface Node, then upon completion, on the Access Node.
Nortel Confidential
84
Evolutions for OAM5.0: Number of RNCs that can be upgraded in parallel (4).
Nortel Confidential
85
Software download operation includes security commands (for SDS on Solaris 9 operating system). Procedure includes TAP patch application for I-Node and A-Node.
Constraints: Fallback operation can be conducted only during the maintenance window and probative phase. If fallback is required out of the probing period, and if any configuration update happened between upgrade and fallback, contact Nortel support. Firmware upgrade may be requested.
Durations: Upgrade duration: The global operational duration is about 7 hours and 20 minutes for a maximal network configuration. During this time, up to 4 RNCs can be upgraded in parallel. Maintenance window: The maintenance window starts when disruptive operations that affect the service are performed on the network and ends when all checks and critical tests have been successfully performed after the upgrade This includes the fallback procedure in case of check failure. The duration is about 300 minutes (200 minutes plus 100 minutes for the fallback). Outage duration: If the upgrade implies module flashing, outage duration is 50 minutes. If flashing is not required, duration is 30 minutes.
Nortel Confidential
86
12.6.4 411-8111-237: RNC 1000 SOFTWARE UPGRADE PROCEDURE USING OAM 5.0 TYPE 6 INTRA RELEASE
This procedure describes the RNC 1000 software upgrade type 6. It supports the following upgrade paths: UA4.0 to UA4.0 UA4.1 to UA4.1 UA4.2 to UA4.2
Upgrade type is defined by the software delivery. Up to 4 RNC can be upgraded in parallel. Description: The upgrade is composed of three main steps: The software download (this operation is done in parallel for the target RNCs). For each RNC, the download is performed sequentially for the control node, the interface node and the access node. The online upgrade build step of the new RNC MIB The software activation. This is a type 6 and impacts the RNC service. For each RNC the activation is performed in parallel for the Control Node and the Interface Node, then upon completion, on the Access Node. After activation, the new software and the new MIB are running
Nortel Confidential
87
Nortel Confidential
88
Evolutions for OAM5.0: Number of RNCs that can be upgraded in parallel (4). Software download operation includes security commands (for SDS on Solaris 9 operating system). Procedure includes TAP patch application for I-Node and A-Node.
Constraints: If the CN software is kept unchanged during the upgrade, a type 7 upgrade is to be performed. Firmware upgrade may be requested.
Durations: Upgrade duration: The global operational duration is about 8 hours and 50 minutes for a maximal network configuration. During this time, up to 4 RNCs can be upgraded in parallel. This duration doesnt take into account the fallback duration. Maintenance window: The maintenance window starts when disruptive operations that affect the service are performed on the network and ends when all checks and critical tests have been successfully performed after the upgrade This includes the fallback procedure in case of check failure. The duration is about 190 minutes + 120 minutes for the fallback. Outage duration: If the upgrade implies module flashing, outage duration is 50 minutes. If flashing is not required, duration is 30 minutes.
Nortel Confidential
89
12.6.5 411-8111-236: RNC 1000 SOFTWARE UPGRADE PROCEDURE USING OAM 5.0 TYPE 6 INTER RELEASE
This procedure describes the RNC 1000 software upgrade type6. It supports the following upgrade paths: UA4.0 to UA4.2 UA4.1 to UA4.2
Upgrade type is defined by the software delivery. Up to 4 RNC can be upgraded in parallel.
Description: The following figure presents the high level view of the upgrade procedure:
The software download is done in parallel for the target RNCs. For each RNC, the download is performed sequentially for the control node, the interface node and the access node. The provisioning upgrade at OAM level is done with the WAUT (Wireless Access Upgrade Tool)
Nortel Confidential
90
The software activation is performed in parallel for the target RNC. It is done in parallel on the Control Node and the Interface Node, and after completion, on the Access Node. Step 1 to 6 have no impact on the RNC service. Step 3 can be performed independently from steps 1 and 2. Those steps (1, 2 and 3) can be performed in parallel before starting step 4 to 8. During steps 5 and 6 the OAM and the RNCs are out of synchronization but with no impact on service.
Nortel Confidential
91
Nortel Confidential
92
Evolutions for OAM5.0: Number of RNCs that can be upgraded in parallel (4). Software download operation includes security commands (for SDS on Solaris 9 operating system). IuxIf CM XML file import into OAM database. Procedure includes TAP patch application for I-Node and A-Node.
Constraints: For the upgrade paths described in this procedure, there is also a provisioning upgrade; during this operation, the manufacturer parameters of the RNC configuration are lost. The values can be recovered by running WICL scripts during the upgrade. Firmware upgrade may be requested. During the upgrade, call traces linked to the RNC to upgrade are lost.
Durations: Upgrade duration: The global operational duration is about 10 hours and 50 minutes for a maximal network configuration. During this time, up to 4 RNCs can be upgraded in parallel. This duration doesnt take into account the fallback duration. Maintenance window: The maintenance window starts when disruptive operations that affect the service are performed on the network and ends when all checks and critical tests have been successfully performed after the upgrade This includes the fallback procedure in case of check failure. The duration is about 370 minutes plus 120 minutes for the fallback. Outage duration: The service is lost at the restart of the RNC nodes at the software activation phase (step 7) and is recovered after the passport CM XML file import (step 8). Duration is 55 minutes.
Nortel Confidential
93
12.6.6 411-8111-243: RNC 1000 TO PROCEDURE USING OAM 5.0
RNC
1500
MIGRATION
This procedure describes the migration from RNC 1000 to the RNC 1500. This migration is applicable for OAM05.0, UA04.2.
Description: The following figure presents the high level view of the upgrade procedure:
Part of step 7 (Passport CM XML file import) has an impact on the RNC service. For the selected RNC, the CM XML is exported, migrated with the WAUT (Wireless Access Upgrade Tool), then re-imported. The procedures includes several steps, the detailed sequence is listed in the following figure.
Nortel Confidential
94
Nortel Confidential
95
The fallback sequence is defined as follows for failure during step 11:
The fallback sequence is defined as follows for failure during step 15 and above:
Evolutions for OAM5.0: Procedures cleanup and alignment with OAM5.0.
Constraints: Parallel migration is not supported The RNC hardware must be in a supported configuration before proceeding with the migration. I-Node must be in version V4.2 and if a retrofit is needed, two CP cards are required Some configurations requires specific procedure (ex: RNC 300-9-7-x) or additional operation (ex: RNC 300 11-10-X).
Durations: Durations are given for one RNC. Maintenance window: The timeframe during which disruptive operations are performed on the network is: 2 hours 40 minutes plus 60 minutes for the fallback. Outage duration: During the migration, the service is not available during part of the CM XML import phase. Duration is 10 minutes. Upgrade duration: The global operational duration of an upgrade is about 6 hours and 30 minutes.
Nortel Confidential
96
12.6.7 411-8111-232: RNC 1500 PATCHING PROCEDURES

This procedure supports the software fix deliveries in a non disruptive way for RNC1500 product. Its scope is Utran 4.2. Description: The patch application is made with no interruption of service. It supports patch precedence and mutual exclusion constraints. It also allows activation / deactivation of the patches. The patching procedure is composed of two main steps: Patch download and installation in the SRS Patch download and activation in the RNC.
The provided procedures include: Software download from Nortel website Patch installation in SRS Patch download to the RNC Patch activation. Patch deactivation
Evolutions for OAM5.0: Minor update alignment for OAM5.0.
Constraints: No specific constraint.
Durations: Outage duration: No service outage.
Nortel Confidential
97
12.6.8 411-8111-244: RNC 1500 SOFTWARE UPGRADE PROCEDURE USING OAM 5.0 (INTRA RELEASE CURRENT MIB)
This procedure supports the RNC 1500 software upgrade for UA42 (Intra release upgrade). This procedure is selected when no MIB build is needed (this is defined by the software release note. A MIB build is required when the new software is not compatible with the existing MIB). Description: The upgrade is composed of two main steps: The software download (this operation is done in parallel for the target RNCs). The activation. First performed on the I-Node, then on the A-Node (this operation is done in parallel for the target RNCs).
The detailed procedure is presented in the following figure::

Nortel Confidential
98
Evolutions for OAM5.0: Number of RNCs that can be upgraded in parallel (4). RNC check procedure updated with MIB audit. Software download operation includes security commands (for SDS on Solaris 9 operating system).
Constraints: During the upgrade, call traces linked to the RNC to upgrade are lost. Firmware upgrade may be requested.
Durations: Durations are given for a maximal configuration, including 4 RNCs Maintenance window: The timeframe during which disruptive operations are performed on the network, including critical tests and the fallback operation if needed is: 160 minutes plus 40 minutes for the fallback. Outage duration: During the upgrade, the service is lost during the restart of the RNC nodes at the software activation phase. Duration is 10 minutes. Upgrade duration: The global operational duration of an upgrade is about 6 hours and 20 minutes. This duration doesnt take into account the fallback duration.
Nortel Confidential
99
12.6.9 411-8111-242: RNC 1500 SOFTWARE UPGRADE PROCEDURE USING OAM 5.0 (INTRA RELEASE NEW MIB)
This procedure supports the RNC 1500 software upgrade for UA42 (Intra release upgrade). This procedure is selected when a MIB build is needed (this is defined by the software release note. A MIB build is required when the new software is not compatible with the existing MIB). Description: The upgrade is composed of three main steps: The software download (this operation is done in parallel for the target RNCs) The MIB online build The software activation. First performed on the I-Node, then on the A-Node. The loss of service occurs during the activation phase. This is performed in parallel for the target RNCs (up to 4).
Nortel Confidential
100
Evolutions for OAM5.0: Number of RNCs that can be upgraded in parallel (4). RNC check procedure updated with MIB audit. Software download operation includes security commands (for SDS on Solaris 9 operating system).
Constraints: During the upgrade, call traces linked to the RNC to upgrade are lost. Firmware upgrade may be requested.
Durations, downtimes and risks: Durations are given for a maximal configuration, including 4 RNCs Maintenance window: The timeframe during which disruptive operations are performed on the network, including critical tests and the fallback operation if needed is: 210 minutes plus 60 minutes for the fallback. Outage duration: During the upgrade, the service is lost during the restart of the RNC nodes at the software activation phase. Duration is 10 minutes. Upgrade duration: The global operational duration of an upgrade is about 7 hours and 20 minutes. This duration doesnt take into account the fallback duration.
Nortel Confidential
101
12.7. FEATURE ACTIVATION STATE AFTER AN UTRAN UPGRADE

The following table gives the activation status for all the UTRAN features. The following information is provided: Feature ID: the feature identification Feature title: the feature name Activation status: the feature activation state after an upgrade: o o Default: it is automatically activated Activable: activable through configuration or FAP
FAP: the feature activation procedure if any. When no FAP is listed, the activation is done by simple configuration (with WPS).
Feature Id 13451
24082
25100 26234 26407 26409 26521 26614 27219 27330 27597 27639 27729 27740 27901 27930 27931 27932
Feature Name 3G to 2G Redirection for Speech calls MSA32 enhancement to sustain 28E1 with IMA UTRAN Call Trace :Additional Measurement Reporting (NBAP Common measurement, RRC BLER, etc..) NodeB support of 2 OAM IP addresses IPsec support validation on RNC Support of Radius Client on RNC RNC supports QAAL2 Alternate Routing RNC Implements QAAL2 Address Translation Intra-frequency Event-triggered Measurements
RB adaptation based on traffic: DL and UL with start @64kbit/s Service-based inter-freq/inter-RAT selection for HHO PP7K optical STM-1 channelized card in POC UA04.2 Counters evolution Iub load in iRM UA04.2 Parameters evolution HSDPA Service HSDPA Flexible Resource Management HSDPA Step1
Activation status activable

activable
FAP
activable activable activable activable activable activable activable activable activable activable activable activable activable activable activable activable Feature Activation Procedure HSDPA 411-8111-575 Feature Activation Procedure HSDPA 411-8111-575 Feature Activation Procedure HSDPA 411-8111-575
Feature Activation Procedure HSDPA 411-8111-575
Nortel Confidential
102
Feature Id
27935 27936 27937 27939 27940 27941 27942 27943 27945 27947 28036 28040 28047 28109 28144 28302 28330 28331 28847 28900 29361 30038 30311
Feature Name
Multi-carrier HSDPA traffic segmentation HSDPA Intra-frequency Mobility HSDPA Alarm Mobility HS-SCCH Power Control H-BBU Pool Across Sectors Node-B Module Operation For HSDPA Always-On on HSDPA Iub Bandwidth Limitation Handling HSDPA Radio Bearers PS I/B UL:384 Mobility Performance Improvements Power Control and Rate Matching enhancements Call Establishment KPI Improvements UA04.2 - 3GPP baseline & additional CRs iRM Scheduling downgrading based on TxCP Y Splitter at the RNC PS Streaming up to 128kbit/s PS Streaming up to 128kbit/s + PS I/B 8kbit/s Change of SAI reporting STSR1+1 NodeB Handover and RRM ConfClass range extension Node-B CAC: Max HSDPA users per Node-B RAB based CAC
Activation status
activable activable activable activable activable activable activable activable activable activable default activable default activable activable activable activable activable activable activable activable fap fap
FAP Feature Activation Procedure HSDPA 411-8111-575 Feature Activation Procedure HSDPA 411-8111-575 Feature Activation Procedure HSDPA 411-8111-575 Feature Activation Procedure HSDPA 411-8111-575 Feature Activation Procedure HSDPA 411-8111-575 Feature Activation Procedure HSDPA 411-8111-575 Feature Activation Procedure HSDPA 411-8111-575 Feature Activation Procedure HSDPA 411-8111-575 Feature Activation Procedure HSDPA 411-8111-575 Feature Activation Procedure HSDPA 411-8111-575
Feature Activation Procedure HSDPA 411-8111-575 Feature Activation Procedure HSDPA 411-8111-575
Nortel Confidential
103
13. INTERFACE CHANGES

This section lists the features that impact somehow UTRAN interfaces. Note that all interfaces are considered.
13.1. UA04.2 INTERFACE FEATURES

Feature 13451 - 3G to 2G Redirection for Speech calls Feature 25100 - UTRAN Call Trace: Additional Measurement Reporting (NBAP common measurement, RRC BLER, etc ...) Feature 26521 - RNC supports QAAL2 Alternate Routing Feature 26614 - RNC Implements QAAL2 Address Translation Feature 27219 - Intra-frequency Event-triggered Measurements Feature 27330 - RB adaptation based on traffic: DL and UL with start @64kbit/s Feature 27597 - Service-based inter-freq/inter-RAT selection for HHO Feature 27930 - HSDPA Service Feature 27931 - HSDPA Flexible Resource Management Feature 27932 - HSDPA Step1 Feature 27935 - Multi-carrier HSDPA traffic segmentation Feature 27936 - HSDPA Intra-frequency Mobility Feature 27937 - HSDPA Alarm Mobility Feature 27939 - HS-SCCH Power Control Feature 27940 - H-BBU Pool Across Sectors Feature 27941 - Node-B Module Operation For HSDPA Feature 27942 - Always-On on HSDPA Feature 27943 - Iub Bandwidth Limitation Handling Feature 27945 - HSDPA Radio Bearers Feature 27947 - PS I/B UL:384 Feature 28036 - Mobility Performance Improvements Feature 28109 - UA04.2 - 3GPP baseline & additional CRs Feature 28330 - PS Streaming up to 128kbit/s Feature 28331 - PS Streaming up to 128kbit/s + PS I/B 8kbit/s Feature 28847 - Change of SAI reporting
Nortel Confidential
104
13.2. OAM05.0 INTERFACE FEATURES

Feature 24157 - Patch Documentation available from Software repository interface Feature 27339 - Persistent Alarm Mgr user preferences Feature 27344 - W-NMS Grid View Feature 27561- Log file viewer for NSP Feature 28401- Operator Annotation on Alarm type Feature 28403 - Alarm Forwarding to multiple destinations Feature 28404 - Automatic acknowledgement of Alarm Feature 28220 - 3GPP R6 File Transfer IRP Feature 28221 - 3GPP R6 Communications Surveillance IRP Feature 28229 - 3GPP R6 PM IRP R6 Baseline Feature 28692 - 3GPP R4 to R6 upgrade support Feature 30266 - Shelf Level Display zoom in / out functions
Nortel Confidential
105
13.3. ACCESS GUI INTERFACE 13.3.1 SCOPE

This section is dedicated to W-NMS graphical user interface. Other graphical user interfaces (SDA, WPS) evolutions are presented in the Tool section of this document. Note that it is mainly dedicated to Utran supervision; Refer to NTP Access Network OAM Commands (411-8111-512) for a complete description of Utran GUI operations.
13.3.2 W-NMS GUI EVOLUTIONS

This section presents the evolution on a per feature basis.
24157
Patch Documentation available from Software repository interface
Patch documentation may be downloaded at the same time as downloading the patch software from the SRM. The documentation can be bundled with the patch. It can be present within the same delivery file(s) at installation or it can be downloaded later. In either case, if documentation is available, it will be listed as a hyperlink next to the delivery.
30266
Shelf Level Display zoom in / out functions
It is possible to zoom in or out of the physical cabinet view by selecting the icon buttons just under the cabinet tab. By using these buttons, you can zoom in for a closer look at the cards or zoom out for a more general view. In addition it is possible to fit the shelf display to the window at the touch of a button. The following figure lists the zoom operations:
Nortel Confidential
106
27561
Log file viewer for NSP
The log browser gives a common framework for browsing logs generated from different sources. It also gives an efficient means to search, filter and sort large amounts of log data.
The log browser main window has the following three sections: Retrieval Criteria area Retrieval Results list Log details area
The Retrieval Criteria pane at the top of the Log Browser main window displays a list of network element and alarm attributes that you can use to select and define the criteria for browsing your data file. The Retrieval Results pane displays a list of the log information that was retrieved according to the selected criteria. The Details pane is located below the Retrieval Results pane and displays the full log record for logs you have selected from the Retrieval Results list.
Nortel Confidential
107
28404
Automatic acknowledgement of Alarm
This feature allows the operator to automatically acknowledge alarms on a per type basis. For details on managing the auto-acknowledgement feature see the Setting automatic acknowledgement of an alarm procedure The Auto-acknowledgement function is configured from the Alarm Stream Management Rule Set (ARS) menu. The Rule definition filter window tells the NSP how to treat each alarm received via a set of filtering criteria which explicitly describe the type of alarm. By selecting the application
AutoAck for the filter criteria chosen for a specific rule, the alarm will automatically be acknowledged.
Nortel Confidential
108
28403
Alarm Forwarding to multiple destinations
This feature allows for the forwarding of an alarm to multiple destinations based on alarm Filtering criteria so that, should a serious problem occur, people are notified in the minimum amount of time. This feature allows the operator to forward alarms to up to five electronic mail or SMS recipients. It is accessed via the Alarm Stream Management Rule Set (ARS). The operator may select the action to send an E-mail or SMS from the drop down window, shown in the figure below
W-NMS allows for the possibility of notifying different destinations for various defined events, so, for example, the relevant people could be notified for specific hardware, or for different locations.
Nortel Confidential
109
28401
Operator Annotation on Alarm type
Using this feature the operator benefits from being able to add additional custom information, tips and hints that can help during the day to day supervision tasks. The operator has the ability to annotate alarm type (not the alarm instance) from the alarm browser by right clicking on an alarm.
The latest user to edit the annotation has the ability to edit the entire annotation. The user name, the date and time as well as the hostname and IP address of the location is recorded in the annotation.
27339
Persistent Alarm Mgr user preferences
The NSP GUI maintains the size, shape, ordering and column positions of the alarm manager window on closure. These are restored on reopening the window. This occurs even if the user logs out.
Nortel Confidential
110
27344
W-NMS Grid View
A Grid Layout View is a convenient way to present large numbers of NEs such as those associated with wireless edge networks. This feature provides additional ways to display the Wireless network. The Resource Browser GUI provides two kinds of views: The Topology View The Grid View
The Grid View includes the following capabilities: - In a Grid View only NEs and groups are displayed. They are automatically displayed in a grid pattern of uniform rows and columns of objects. All NEs are displayed in front of all groups. The links interconnecting the NEs are not displayed. - The grid size of a Grid View can be altered. Changing the grid size enables the user to control the number of objects that are visible in a single window. When a smaller grid size is selected, the information displayed for each NE or group (alarm balloons, labels, icons, etc.) is reduced to enable more objects to be visible in the window. - Information in a Grid View can be sorted and filtered according to certain options such as sorting both NEs and groups by name, or filtering so that only the ones with new alarms are displayed. The information displayed for each Grid Layout view is shown in the table below. An x shows that the item is supported for that view:
Other GUI evolutions

Nortel Confidential
111
Changes to generic GUI services (not specific to Utran), particularly the Resource browser and Equipment monitor windows. Changes to TIL window (showing green LEDs on both CCMs): Refer to the tool section of the Utran ROI.
13.4. UA04.2 COMPLIANCE TO 3GPP SPECIFICATIONS

The high level conformance of Nortel Networks Radio Access Network (RNS) to the 3GPP Technical specifications that are applicable to UMTS 5.0 (Utran 4.2 and OAM5.0) is summarized in document UMT/SYS/DD/9966 (UA04.2 High Level Compliance to 3GPP specifications).
Nortel Confidential
112
13.5. IUB INTERFACE 13.5.1 IUB TRANSPORT

The following figure presents the Iub protocol stack, subdivided in two parts: the Radio Network Layer and the Transport layer:
Nortel Confidential
113
RNC
RNC CAPACITY Release 4-2: Up to 200 nodeBs per RNC, TBC Release 4-1 and previous: Up to 200 nodeBs per RNC IUXIF / IUBIF / AAL2IF Release4.2: The Iuxif component is removed and replaced by two components: IubIf and aal2If. PATHID Release4 & 3: Up to 2100 aal2 Pathid values are available on RNC. AAL2 PATH ASSIGNMENT TO PMC-PC Release 4-2: All Paths from one NodeB are assigned to one single PMC-PC. This modification is linked to the Hsdpa introduction. The loadBalancing parameter is removed. This parameter was set to weighted on the Iub interface and determined the way the Iub paths were assigned to the PMC-PC.
Release 4-1 and previous: All Paths from one NodeB may be assigned to different PMC-PCs. The Path assignment to PMC-PC is dictated by the parameter loadBalancing set to weighted.
AAL2 LINK CAC Bandwidth Reference: Release 4-2: Enhancement of the AAL2 link CAC in such a way the bandwidth taken into consideration (ACR) is either 1) The NodeB per Path bandwidth, 2) The NodeB per AAL2 QOS bandwidth: Aal2Qos0 ACR = Sum of DS Vcc ECR Aal2Qos1 ACR = Sum of NDS Vcc ECR Aal2Qos2 ACR = Hsdpa Vcc ECR
3) The IubIf bandwidth (per Iubif, Sum of VCC GCAC ECR). Release4 -1: Enhancement of the AAL2 link CAC in such a way the bandwidth taken into consideration (ACR) is either 1) The NodeB per AAL2 QOS bandwidth:
Nortel Confidential
114

Aal2Qos0 ACR = Sum of DS Vcc ECR, Aal2Qos1 ACR = Sum of NDS Vcc ECR,
2) The IuxIf bandwidth.
Node B
IMA IMA bandwidthReduction, Configuration of ImaDefense mechanism through OMC-R: Release 4-2: The Previous IMA LG Bw reduction/Restoration is replaced by a new one. The NodeB Call processing is no more involved in traffic reduction/restoration, beside atm Vcc are deactivated/activated. Reason for change: satisfies the RNC aal2 Congestion Management mechanism introduced for Hsdpa traffic. Release 4-1: NodeB IMA bandwidthReduction defense mechanism is activated by setting the parameter: IMA DefenseDelay. The parameter IMA DefenseActivated is no more present. IMA DefenseDelay parameter is optional. AAL1 CES Release 4-2: AAL1 CES SDT NOT available. QOS NodeB set of priorityLevel values, case of trafficShaping Not activated: Release 4-2: Reason for Modification: - Introduction of CES, - Introduction of Hsdpa Vcc, - MCR taken into account by NodeB. Release 4-0 & 4-1: Reason for Modification: MCR not taken into account by NodeB.
Nortel Confidential
115
As long as the MCR is not taken into account in NodeB, the CP and CCP serviceCategory is changed from UBR+ to UBR, in parallel the UP DS PriorityLevel is changed from 0 to 1 (same as CP and CCP PL). The MCR configured against the OAM Vcc is taken into account by the scheduling.
TRAFFIC MANAGEMENT TRAFFIC DESCRIPTOR PARAMETER VALUES NodeB UBR+/MCR availability: Release 4-2: MCR configured for UBR+ VCC is taken into consideration by NodeB. UBR+/MCR may be configured against aal5 and aal2 Vcc. Release 4-1: MCR configured for UBR+ VCC, is not taken into consideration by NodeB when trafficShaping is not activated. AAL2 VCCs can not be configured with UBR+ serviceCategory. Only AAL5 VCC may be configured with UBR+. PLANE RELATIVE UMTS HSDPA PLANE: Release4-2: The UMTS HSDPA traffic flow is added. HSDPA is handled on Iub interface, not on Iur interface.
Nortel Confidential
116
13.6. IUR INTERFACE 13.6.1 IUR WHEN SRNC AND DRNC RUN DIFFERENT RELEASES
This section provides features impact over IuR for various RNS configurations. It lists: IuR impacts facing RNS V4.1.1 IuR impacts facing RNS V4.0 IuR impacts facing RNS V4.2 without feature activation
No impact means that if the feature is supported over Iur it also works over an Iur with a V4.1.1 RNC. If the feature is not supported over Iur then no impact means the situation is not worse on account of the DRNC belonging to a previous release.
Nortel Confidential
117
IuR impacts facing RNS V4.1.1

Id 28109 28910 28880 27932 UA04.2 Feature Title 3GPP baseline & additional CRs UA04.2 Performance Targets UA04.2 Support on 2100 and 1900 HSDPA Step1 IuR Impacts facing RNS V4.1.1 No impact. No impact. No impact.
No impact. HSDPA not supported over Iur (fall-back to cell_DCH).
27930
HSDPA Service
27943
Iub Bandwidth Limitation Handling
Same behaviour regardless of the neighbouring RNC release.
27931
HSDPA Flexible Resource Mgt
27945
HSDPA Radio Bearers
27942 27941 27940
Always-on On HSDPA Node-B Module Operation For HSDPA H-BBU Pool Across Sectors
No impact. HSDPA not supported over Iur (fall-back to cell_DCH). N/A
27935
Multi carrier HSDPA Traffic segmentation
27330
RB adaptation DL and UL with access @64
27947 27936
PS I/B UL:384 HSDPA Intra-frequency Mobility
No impact due to the mechanism but if RB adaptation chooses an RB that is not supported by the drift, the RB adaptation procedure will fail. No mobility over Iur for this RAB.

Nortel Confidential
118
Id
UA04.2 Feature Title
IuR Impacts facing RNS V4.1.1
27937
HSDPA Alarm Mobility - inter RAT: 3G to 2G only and blind No impact. HSDPA not supported over Iur (fall-back to cell_DCH). HS-SCCH Power Control 3G to 2G Directed Retry for Speech calls RNC supports QAAL2 Alternate Routing RNC Implements QAAL2 Address Translation Iub load in iRM PP7K Optical STM1 Channelized card in POC Call establishment KPI improvement STSR1+1 NodeB RRC improvement Service-based Interfreq/interRAT selection for HHO Selection between Inter-frequency and InterRAT measurements per service Change of SAI reporting Mobility Performances Improvements Power Control and Rate Matching enhancements Intra freq Event-triggered measurement reporting RNC support for RADIUS Client RNC support for IPSec MSA32 enhancement to sustain 28E1 with IMA Y-Splitter Support TMA2 (TMA AISG) Handover and RRM ConfClass range extension UA04.2 MANDATORY Counters evolution UA04.2 MANDATORY Parameters evolution Utran Performance metrics Call Trace Additional measurement Reporting (NBAP Common measurement, ) NodeB support of 2 OAM IP addresses Use Ranap Cause For Iu release message after an O&M intervention
27939 13451 26521 26614 27740 27639 28047 28900 28041 27597 28847 28036
No impact. HSDPA not supported over Iur (fall-back to cell_DCH). No impact. No impact. No impact. No impact. N/A Same behaviour regardless of the neighbouring RNC. N/A N/A No impact. No impact.
Same behaviour regardless of the neighbouring RNC release. No impact.
28040
27219 26409 26407 24082 28302 26386 29361 27729 27901 28758 25100 26234 27023
Same behaviour regardless of the neighbouring RNC release. N/A N/A N/A N/A N/A N/A N/A N/A N/A No impact. Feature not supported over Iur. N/A No impact.
Nortel Confidential
119
Id 27024 28330 28331
UA04.2 Feature Title Use Ranap Cause For Reset initiated from the RNC PS Streaming up to 128kbit/s PS Streaming up to 128kbit/s + PS I/B 8kbit/S
IuR Impacts facing RNS V4.1.1
No impact. No mobility over Iur for this RAB. No mobility over Iur for this RAB.
IuR impacts facing RNS V4.0
Id
IuR Impacts facing RNS V4.0

No impact. No impact. No impact. In order to have fall-back to cell_DCH functionning, a provisionning work-around is needed: deactivate HSDPA on cells in direct neighbourhood to a V4.0 RNC. In order to have fall-back to cell_DCH functionning, a provisionning work-around is needed: deactivate HSDPA on cells in direct neighbourhood to a V4.0 RNC.
28109 3GPP baseline & additional CRs 28910 UA04.2 Performance Targets 28880 UA04.2 Support on 2100 and 1900 27932 HSDPA Step1
27930 HSDPA Service
27943 Iub Bandwidth Limitation Handling
Same behaviour regardless of the neighbouring RNC release. In order to have fall-back to cell_DCH functionning, a provisionning work-around is needed: deactivate HSDPA on cells in direct neighbourhood to a V4.0 RNC. In order to have fall-back to cell_DCH functionning, a provisionning work-around is needed: deactivate HSDPA on cells in direct neighbourhood to a V4.0 RNC. In order to have fall-back to cell_DCH functionning, a provisionning work-around is needed: deactivate HSDPA on cells in direct neighbourhood to a V4.0 RNC. N/A In order to have fall-back to cell_DCH functionning, a provisionning work-around is needed: deactivate HSDPA on cells in direct neighbourhood to a V4.0 RNC. In order to have fall-back to cell_DCH functionning, a provisionning work-around is needed: deactivate HSDPA on cells in direct neighbourhood to a V4.0 RNC.
27931 HSDPA Flexible Resource Mgt
27945 HSDPA Radio Bearers
27942 Always-on On HSDPA 27941 Node-B Module Operation For HSDPA 27940 H-BBU Pool Across Sectors
27935 Multi carrier HSDPA Traffic segmentation
Nortel Confidential
120
Id
27330 RB adaptation DL and UL with access @64
No impact due to the mechanism but if RB adaptation chooses an RB that is not supported by the drift, the RB adaptation procedure will fail. No mobility over Iur for this RAB. In order to have fall-back to cell_DCH functionning, a provisionning work-around is needed: deactivate HSDPA on cells in direct neighbourhood to a V4.0 RNC. In order to have fall-back to cell_DCH functionning, a provisionning work-around is needed: deactivate HSDPA on cells in direct neighbourhood to a V4.0 RNC. In order to have fall-back to cell_DCH functionning, a provisionning work-around is needed: deactivate HSDPA on cells in direct neighbourhood to a V4.0 RNC. No impact. No impact. No impact. No impact. N/A Same behaviour regardless of the neighbouring RNC. N/A N/A No impact. No impact.
27947 PS I/B UL:384
27936 HSDPA Intra-frequency Mobility
HSDPA Alarm Mobility - inter RAT: 3G to 2G only 27937 and blind
27939 HS-SCCH Power Control 13451 26521 26614 27740 27639 3G to 2G Directed Retry for Speech calls RNC supports QAAL2 Alternate Routing RNC Implements QAAL2 Address Translation Iub load in iRM PP7K Optical STM1 Channelized card in POC
28047 Call establishment KPI improvement 28900 STSR1+1 NodeB 28041 RRC improvement Service-based Interfreq/interRAT selection for HHO 27597 Selection between Inter-frequency and Inter-RAT measurements per service 28847 Change of SAI reporting 28036 Mobility Performances Improvements
28040 Power Control and Rate Matching enhancements
27219 Intra freq Event-triggered measurement reporting 26409 RNC support for RADIUS Client 26407 RNC support for IPSec
Same behaviour regardless of the neighbouring RNC release. N/A N/A

Nortel Confidential
121
Id
24082 MSA32 enhancement to sustain 28E1 with IMA 28302 26386 29361 27729 27901 28758 Y-Splitter Support TMA2 (TMA AISG) Handover and RRM ConfClass range extension UA04.2 MANDATORY Counters evolution UA04.2 MANDATORY Parameters evolution Utran Performance metrics Call Trace Additional measurement Reporting (NBAP 25100 Common measurement, ) 26234 NodeB support of 2 OAM IP addresses Use Ranap Cause For Iu release message after an 27023 O&M intervention 27024 Use Ranap Cause For Reset initiated from the RNC 28330 PS Streaming up to 128kbit/s 28331 PS Streaming up to 128kbit/s + PS I/B 8kbit/S
N/A N/A N/A N/A N/A N/A N/A No impact. Feature not supported over Iur. N/A No impact. No impact. No mobility over Iur for this RAB. No mobility over Iur for this RAB.
IuR impacts facing RNS V4.2 without feature activation Id

28109 28910 28880

3GPP baseline & additional CRs UA04.2 Performance Targets UA04.2 Support on 2100 and 1900
IuR Impacts facing RNS V4.2 without feature activation N/A N/A
No impact.
27932
HSDPA Step1
27930
HSDPA Service
27943
Iub Bandwidth Limitation Handling
Same behaviour regardless of the neighbouring RNC release.
27931
HSDPA Flexible Resource Mgt
Nortel Confidential
122
Id
IuR Impacts facing RNS V4.2 without feature activation
27945
HSDPA Radio Bearers
27942
Always-on On HSDPA
27941
Node-B Module Operation For HSDPA
No impact. HSDPA not supported over Iur (fall-back to cell_DCH). N/A
27940
H-BBU Pool Across Sectors
27935
Multi carrier HSDPA Traffic segmentation
27330
RB adaptation DL and UL with access @64
27947
PS I/B UL:384
No impact due to the mechanism but if RB adaptation chooses an RB that is not supported by the drift, the RB adaptation procedure will fail. No impact.
27936
HSDPA Intra-frequency Mobility
27937
HSDPA Alarm Mobility - inter RAT: 3G to 2G only and blind
27939
HS-SCCH Power Control
13451 26521 26614 27740 27639 28047 28900 28041
3G to 2G Directed Retry for Speech calls RNC supports QAAL2 Alternate Routing RNC Implements QAAL2 Address Translation Iub load in iRM PP7K Optical STM1 Channelized card in POC Call establishment KPI improvement STSR1+1 NodeB RRC improvement
No impact. HSDPA not supported over Iur (fall-back to cell_DCH). No impact. No impact. No impact. No impact. N/A Same behaviour regardless of the neighbouring RNC. N/A N/A
Nortel Confidential
123
Id
HHO

Service-based Interfreq/interRAT selection for
IuR Impacts facing RNS V4.2 without feature activation

No impact. No impact.
27597
Selection between Inter-frequency and Inter-RAT measurements per service

Change of SAI reporting
28847
28036
Mobility Performances Improvements
28040
Power Control and Rate Matching enhancements
27219
Intra freq Event-triggered measurement reporting
26409 26407 24082 28302 26386 29361 27729 27901 28758 25100 26234 27023 27024 28330 28331
RNC support for RADIUS Client RNC support for IPSec MSA32 enhancement to sustain 28E1 with IMA Y-Splitter Support TMA2 (TMA AISG) Handover and RRM ConfClass range extension UA04.2 MANDATORY Counters evolution UA04.2 MANDATORY Parameters evolution Utran Performance metrics Call Trace Additional measurement Reporting (NBAP Common measurement, ) NodeB support of 2 OAM IP addresses Use Ranap Cause For Iu release message after an O&M intervention Use Ranap Cause For Reset initiated from the RNC PS Streaming up to 128kbit/s PS Streaming up to 128kbit/s + PS I/B 8kbit/S
Same behaviour regardless of the neighbouring RNC release. N/A N/A N/A N/A N/A N/A N/A N/A N/A No impact. Feature not supported over Iur. N/A No impact. No impact. No impact. No impact.
Nortel Confidential
124
13.6.2 IUR TRANSPORT

The following figure presents the Iur protocol stack, subdivided in two parts: the RNL (Radio Network Layer) and the TNL (transport network layer):
RNC AAL2
AAL2 PATH ASSIGNMENT TO PMC-PC Release4-2: The loadBalancing = [weight, spread] parameter is removed. A new algorithm is in charge of distributing the Utran aal2 vcc over the PMC-PC. Release4-1 and previous releases: The path assignment algorithm is based on the parameter loadBalancing set to spread. AAL2 LINK CAC Note: The CAC per VCC (per path bandwidth) is not officially supported in UA04.2 since it has not been tested yet. Release4-2: As an option the aal2LinkCAC bandwidthReference is either the ACR for the entire Iur aal2 interface, the ACR per aal2 interface and aal2 Qos or the ACR per aal2 path: The Aal2If bandwidth (per Aal2If, Sum of Vcc GCAC ECR) or The per aal2Qos Aal2If bandwidth (per aal2If, Sum of aal2Qos i Vcc GCAC ECR), two aal2Qos are currently configured on the Iur interface, or The per path bandwidth is Vcc GCAC ECR.
Nortel Confidential
125
Release4-1: The aal2LinkCAC bandwidthReference is always the bandwidth configured against the IuxIf: ACR = Sum ECRgcac for all aal2 Vccs under an IuxIf. AAL2 PC CAC Release4&3: The PC-CAC is active on RNC-IN. ALCAP Release4-2: Alcap is implemented in the PMC-M. Alcap is based on recommendation Q2630-2. Note: The main difference with the introduction of Q2630-2 is the sending of the path type parameter in the ERQ message. Other additional functions from Q2630.2 are not needed and hence not supported. The introduction of the path type should cause no issue and be discarded by Q2630.1 nodes provided they are compliant to the Q2630.1 compatibility rules. Release4-1 & previous release: Alcap is implemented in the TMU. Alcap is based on recommendation Q2630-1
AAL2 COMPONENTS Release4-2: The IuxIf component is replaced by the IurIf and Aal2If components. Release4-1 & previous release: Within the Nortel RNC, each adjacent aal2 node (aal2Switch or neighbor RNC) is identified by one IuxIf instance. QAAL2 ALTERNATE ROUTING Release4-2: Supported. Release4-1 & previous release: Not supported.
RNC SS7
TOPOLOGY: Aal2 Topology: The RNC supports up to 10 AAL2 switches on each AAL2 interface. MTP3 COMPLIANCY: Release4&3: SS7 Stack migration to RNC-IN: MTP3-B are supported: quasi-associated mode is supported since UA04.1 (it means that there could be STPs in the network). ITU-T and China variants are supported When changeOver occurs, non transmitted and non acknowledge MSU are discarded
Nortel Confidential
126
This MTP3 implementation does not support the following: Route management Signaling Transfer Points Forced rerouting Controlled rerouting Multiple congestion thresholds
SCCP COMPLIANCY Release4&3: SS7 Stack migration to RNC-IN: ITU-T Q.711-715 (1996) is supported; Class 0 and Class 2 are supported; Class1 and Class 3 are not supported; Global Title Translation not supported; Congestion Control is not supported (SCC is not supported);
13.6.3 IUR INTEROPERABILITY

26614 - RNC Implements QAAL2 Address Translation This feature allows for interconnecting a Nortel RNC to an E/// RNC through Iur interface.
Nortel Confidential
127
13.7. IU INTERFACE 13.7.1 IU TRANSPORT

The following figures present the Iu protocol stacks according to 3GPP, subdivided in two parts: the RNL (Radio Network Layer) and the TNL (transport network layer): IU-CS protocol stack
IU-PS protocol stack
Nortel Confidential
128
AAL2
RNC, AAL2 PATH ASSIGNMENT TO PMC-PC Release4-2: The loadBalancing = [weight, spread] parameter is removed. A new algorithm is in charge of distributed the Utran aal2 vcc over the PMC-PC. Release4-1 and previous releases: - The path assignment algorithm is based on the parameter loadBalancing set to spread. UA4-1 RNC aal2 Path assignment to PMC-PC section: The TBM provides two algorithms for aal2 Vcc assignment to PMC-PC. The algorithm is selected per UTRAN interface through the parameter IuxIf/loadbalancingMethod set either with Weight or Spread: - LoadbalancingMethod = weight: means the paths from an aal2If are assigned to different PMCPC in such a way the PMC-PC components are equally loaded. The Vcc ECRgcac is considered to be the cost of the aal2 Path: ECRgcac = 2*SCR*PCR/(SCR+PCR). The load of a PMC-PC is estimated by summing ECRgcac of each Path assigned to it. - LoadbalancingMethod = spread: means the paths within an aal2If are assigned to different PMCPC in a round robin fashion. Only Spread value is available on Iu/Iur. On IuCS and Iur, set LoadbalancingMethod = Spread. On Iub, set LoadbalancingMethod = Weight.
Moreover TBM assigned Paths to PMC-PC with respect to the following rules: PMC-PC are loaded equally for a given QOS, PMC-PC are loaded equally, Within an Aal2If, for a given QOS, the paths have to be evenly distributed among the PMC-PCs. Within an Aal2If, the paths with different QOS should be assigned together to the same PMC-PC.
RNC, AAL2 LINK CAC Release4-1: The aal2LinkCAC bandwidthReference is always the bandwidth configured against the aal2If: ACR = Sum ECRgcac for all aal2 Vccs under an Aal2If. RNC, ALCAP Release4-2: Alcap is implemented in the PMC-M. Release4-1 & previous release: Alcap is implemented in the TMU. RNC, QAAL2 ALTERNATE ROUTING Release4-2: Supported. Release4-1 & previous release: Not supported. RNC, AAL2 COMPONENTS
Nortel Confidential
129
Release4-2: The IuxIf component is replaced by the IucsIf and Aal2If components Release4-1 & previous release: Within the Nortel RNC, each adjacent aal2 node (aal2Switch or MGW) is identified by one IuxIf instance.
IU NODES
UMGW In the current release, it is planned to support up to 2016 voice sessions per VSP4e. VSP: Release 4-2: VSP4e availability, VSP2 no more supported
Nortel Confidential
130
14. NETWORK ARCHITECTURE

No information is available for this release.
Nortel Confidential
131
15. NETWORK RECONFIGURATION PROCEDURES (NRPS)

15.1. OAM05.0 NETWORK RECONFIGURATION FEATURES
Feature 28536 - Reconfiguration Procedures
15.2. NRP PROCEDURES

Complex network operations, sometimes involving service impact, need to be clearly documented in a process document. This section lists network reconfiguration procedure documentation set evolution for the current release.
15.2.1 OBSOLETE PROCEDURES

None
15.2.2 NEW PROCEDURES

None
Nortel Confidential
132
15.2.3 MODIFIED PROCEDURES

15.2.3.1 411-8111-539 NODE B ADDITION
This NRP provides procedures to add several node(s)-B to a network without interruption of service on the existing RNCs. The document applies to Utran V4.2, Utran V4.1 and Utran V4.0.
Description: The procedure includes an optional reverse engineering phase that imports a view of the current network configuration into WPS, then updates are done at WPS level, workorders are exported from WPS and configuration updates are imported in W-NMS. The document includes a reverse procedure.
The following figure presents an overview of the different steps to be conducted to introduce a new nodeB:
Nortel Confidential
133
Detailed procedure for NodeB preparation with WPS is presented in the following figure:
Evolutions for UMTS50: Activation pre-checks: Network and OMC are up and running without any problem (alarm, MIB state, synchronization state, etc.), calls can be performed on the impacted RNC, the new node B has been installed and commissioned.
Constraints: Once the CM XML export is performed, no online modification can take place on the target NE(s) until the end of the procedure in order to guarantee that the initial view is synchronous with the Main server MIB. All design parameters regarding the new node B should be available (cell planning information, topological information). The partial reverse is not supported. It is done for all the Node B that have been added. The procedure does not cover inter Main Server neighboring. Other constraints listed in the document.
Durations: Timing depends on many parameters: hardware and software configurations, network size, transmission network performance, etc Provided information is informative only. Durations are given for the addition of one NodeB in a network containing 7 RNCs and 860 NodeB.
Nortel Confidential
134
The following figure presents the duration of the various steps of the procedure:
Nortel Confidential
135
15.2.3.2
411-8111-540 NODE B REPARENTING

This NRP provides procedures that aim at reparenting N active Node B(s) from a source to a target RNC without interruption of service on the existing RNCs.. The document applies to Utran V4.2, Utran V4.1 and Utran V4.0.
Description: The procedure includes an optional reverse engineering phase that imports a view of the current network configuration into WPS, then updates are done at WPS level, workorders are exported from WPS and configuration updates are imported in W-NMS. The document includes a reverse procedure.
An overview of the reparenting procedure is presented in the following figure:
Nortel Confidential
136
The detailed steps for the reparenting preparation with WPS are presented below:
Evolutions for UMTS50: Activation pre-checks: Network and OMC are up and running without any problem (alarm, MIB state, synchronization state, etc.), calls can be performed on the impacted RNC and node B, the new node B is ready to be reparented.
Constraints: Once the CM XML export is performed, no online modification can take place on the target NE(s) until the end of the procedure in order to guarantee that the initial view is synchronous with the Main server MIB. Impact on the service is summarized in the following table for the various steps of the procedure:
All design parameters regarding the new node B should be available (cell planning information, topological information). The partial reverse is not supported. It is done for all the Node B that have been reparented Transmission network operation is needed. The procedure does not support intra RNC reparenting, nor inter ROC reparenting. If the source and target RNCs are not homed by the same Main server, a BTS Equipment and its associated Site must be re-homed prior to the reparenting. Other constraints listed in the document.
Nortel Confidential
137
Durations: Timing depends on many parameters: hardware and software configurations, network size, transmission network performance, etc Provided information is informative only. Durations are given for the reparenting of one NodeB in a network containing 7 RNCs and 860 NodeB.
Nortel Confidential
138
15.2.3.3
411-8111-514 SCRAMBLING CODE PLAN UPDATE

This NRP provides procedures to update a scrambling code plan on existing cells and at propagating the scrambling code changes on related neighboring links in the UMTS network. The document applies to Utran V4.2, Utran V4.1 and Utran V4.0. Description: The procedure includes an optional reverse engineering phase that imports a view of the current network configuration into WPS, then updates are done at WPS level, with input data provided by the Cell Planning team. Workorders are exported from WPS and configuration updates are imported in W-NMS. The document includes a reverse procedure.
An overview of the procedure is presented in the following figure:
Nortel Confidential
139
The detailed steps for the scrambling code plan update with WPS are presented below:
Evolutions for UMTS50: Activation pre-checks and post-checks: Network and OMC are up and running without any problem (alarm, MIB state, synchronization state, etc.), calls can be performed on the impacted RNC; the new scrambling code plan is ready to be imported, and effective after update. .
Constraints: The procedure is applicable to one ROC. If neighboring links towards cells belonging to other ROCs are updated, the procedure should be applied on each ROC. Impact on the service is summarized in the following table for various steps of the procedure:
Once the CM XML export is performed, no online modification can take place on the target NE(s) until the end of the procedure in order to guarantee that the initial view is synchronous with the Main server MIB. All design parameters regarding the new Scrambling code plan should be available (cell planning information). The Cell planning tool and the OMC must contain the same network coverage in terms of managed node B and UMTS FDD Cells. Configuration files coming from the Cell Planning tool should be compatible with WPS CP XML format (recommended), or CM XML format; Other constraints listed in the document.
Durations:
Nortel Confidential
140
Timing depends on many parameters: hardware and software configurations, network size, transmission network performance, etc Provided information is informative only. Durations are given for the scrambling code update for a network including 7 RNCs, 860 BTSEquipments, and 2540 Cells. The following figure presents the duration of the various steps of the procedure:
Nortel Confidential
141
15.2.3.4
411-8111-551 LAC/RAC PLAN UPDATE

This procedure aims at updating the LAC/RAC plan on existing cells and neighboring links in the live network. Modification is applied on UMTS FDD Cells, GSM Cells and their associated neighboring links. The document applies to Utran V4.2, Utran V4.1 and Utran V4.0. Description: The procedure includes an optional reverse engineering phase that imports a view of the current network configuration into WPS, then updates are done at WPS level, with input data provided by the Cell Planning team. Workorders are exported from WPS and configuration updates are imported in W-NMS. The document includes a reverse procedure.
Nortel Confidential
142
An overview of the procedure is presented in the following figure:
The detailed steps for the LAC/RAC plan update with WPS are presented below:
Evolutions for UMTS50: Activation pre-checks and post-checks: Network and OMC are up and running without any problem (alarm, MIB state, synchronization state, etc.), calls can be performed on the impacted RNC; the new LAC/RAC plan is ready to be imported, and effective after update. .
Nortel Confidential
143
Constraints: This NRP doesnt cover the core network LAC/RAC configuration. The LAC/RAC plan should be up to date or ready to be updated at the Core Network side in order to synchronize the end to end network configuration. Once the CM XML export is performed, no online modification can take place on the target NE(s) until the end of the procedure in order to guarantee that the initial view is synchronous with the Main server MIB. The procedure is applicable to one ROC. If neighboring links towards cells belonging to other ROCs are updated, the procedure should be applied on each ROC. Impact on the service is summarized in the following table for various steps of the procedure:
If LAC/RAC is updated for GSMCell, equivalent activity needs to be performed on 2G system for coherency. The Cell planning tool and the OMC must contain the same network coverage in terms of managed node B and UMTS FDD Cells. Configuration files coming from the Cell Planning tool should be compatible with WPS CP XML format (recommended), or CM XML format; Other constraints listed in the document.
Durations: Timing depends on many parameters: hardware and software configurations, network size, transmission network performance, etc Provided information is informative only. Durations are given for the LAC/RAC update for a network including 7 RNCs, 860 BTSEquipments, and 2540 Cells.
Nortel Confidential
144
Nortel Confidential
145
15.2.3.5
411-8111-545 NEIGHBORING PLAN UPDATE

This NRP provides procedures to update the neighboring plan of an UMTS network, without interruption of service on the existing RNCs. The neighboring plan update is requested either after a new site addition or an addition, deletion, update of neighboring links in the UMTS network. The document applies to Utran V4.2, Utran V4.1 and Utran V4.0.
Description: The procedure includes an optional reverse engineering phase that imports a view of the current network configuration into WPS, then updates are done at WPS level, with input data provided by the Cell Planning team. Workorders are exported from WPS and configuration updates are imported in W-NMS. The document includes a reverse procedure.
Nortel Confidential
146
15.2.4 AN OVERVIEW OF THE PROCEDURE IS PRESENTED IN THE FOLLOWING FIGURE:
The detailed steps for the Neighboring plan update with WPS are presented below:
Evolutions for UMTS50: Activation pre-checks and post-checks: Network and OMC are up and running without any problem (alarm, MIB state, synchronization state, etc.), calls can be performed on the impacted RNC; the new Neighboring plan is ready to be imported, and effective after update. . Partial neighbouring is possible if CP XML format is used.
Nortel Confidential
147
Constraints: Impact on the service is summarized in the following table for various steps of the procedure:
The procedure is applicable to one ROC. If neighboring links towards cells belonging to other ROCs are updated, the procedure should be applied on each ROC. Once the CM XML export is performed, no online modification can take place on the target NE(s) until the end of the procedure in order to guarantee that the initial view is synchronous with the Main server MIB. Equivalent activity needs to be performed on 2G system for reciprocal neighbours. The Cell planning tool and the OMC must contain the same network coverage in terms of managed node B and UMTS FDD Cells. Configuration files coming from the Cell Planning tool should be compatible with WPS CP XML format (recommended), or CM XML format; If the new neighboring plan comes from a CM XML file, no partial neighboring plan can be obtained. Other constraints listed in the document.
Durations: Timing depends on many parameters: hardware and software configurations, network size, transmission network performance, etc Provided information is informative only. Durations are given for the Neighboring plan update for a network including 7 RNCs, 860 BTSEquipments, and 2540 Cells.
Nortel Confidential
148
Nortel Confidential
149
16. FEATURE ACTIVATION PROCEDURES (FAPS)

16.1. OAM05.0 FEATURE ACTIVATION FEATURES
Feature 28536 - Reconfiguration Procedures Feature 28718 - HSDPA Activation Procedure
16.2. FAP PROCEDURES 16.2.1 OBSOLETE PROCEDURES

411-8111-557 Password Expiration Policy
Nortel Confidential
150
16.2.2 NEW PROCEDURES

16.2.2.1 411-8111-575 HSDPA
The procedure describes the activation operations for the HSDPA feature on the OMC emphasizing the datafill impact on the UTRAN subsystem. Description: The feature activation can be performed either directly on W-NMS (for a small set of cells) or with WPS. WPS operations include a reverse engineering phase that imports a view of the current network configuration into WPS, then updates are done at WPS level, workorders are exported from WPS and configuration updates are imported in W-NMS. Detailed activation procedure with WPS is presented in the following figure:
Deactivation can also be performed at W-NMS or WPS level. Procedure being decomposed in two sub-procedures: one at cell level, the other one at RNC level. Detailed deactivation procedure with WPS at cell level is presented in the following figure:
Detailed deactivation procedure with WPS at RNC level is presented in the following figure:
Nortel Confidential
151
Reverse steps procedures are also provided, with WPS or directly with W-NMS. . Constraints: All the RNC and BTS must be at least running Utran V4.2 IuB dimensioning and provisioning must be well configured. Especially at least one dedicated traffic Vcc for Hsdpa must be pre-defined supporting specific QoS and specific service category. RAB definition for HSDPA at RNC level must be well defined according to expected behaviors (AlwaysOn, Ho, ). Once the CM XML export is performed, no online modification can take place on the target Nes until the end of the overall procedure in order to guarantee that the initial view, on which the procedure is based, is aligned with the main server MIB.
Durations: Information is given per sheet, as presented in the detailed description: Sheet 1: (reverse engineering): about 30 minutes for 7 RNCs, 860 BtsEquipments and 2540 Cells Sheet 2: (activation with WPS): 10 minutes for 360 FDD Cells of 120 NodeB. Sheet 3: (workorders export): a few seconds. Sheet 4: (XML import and activation in W-NMS): Less than one hour for 360 FDD Cells of 120 nodeB. Note that for BTS equipments, the build requires a reset (3 minutes outage). Sheet 5: (hsdpa activation with W-NMS): About 3 minutes for 3 Cells of 1 BTSEquipment. Note that for BTS equipments, the build requires a reset (3 minutes outage). Sheet 6: (hsdpa deactivation with WPS at Cell level): about 10 minutes per RNC Sheet 7: (hsdpa deactivation with WPS at RNC level): about 2 minutes per RNC Sheet 8: (hsdpa de-activation with W-NMS at cell level): about 3 minutes for 3 Cells of 1 BtsEquipment. Note that for BTS equipments, the build requires a reset (3 minutes outage) Sheet 9: (hsdpa de-activation with W-NMS at RNC level): about 2 minutes per RNC; Note that for BTSEquipments, HSDPA resources are not released for non HSDPA services.
Nortel Confidential
152
16.2.3 MODIFIED PROCEDURES

16.2.3.1 411-8111-507 IUPC - AGPS LOCATION SERVICES
This FAP provides procedures to configure and activate the AGPS Location Service feature. This service provides User Equipment based assisted GPS positioning. The document applies to utran V4.2 (1900 and 2100 bands), Utran V4.1 (1900 and 2100 bands) and Utran V4.0 (1900 band).
Description: The procedures are divided in two categories: Procedures related to IuPC interface configuration and activation Procedures related to AGPS location services activation
WPS operations include a reverse engineering phase that imports a view of the current network configuration into WPS, then updates are done at WPS level, workorders are exported from WPS and configuration updates are imported in W-NMS. A reverse procedure is also provided. Detailed procedures for IuPc Configuration and activation are presented in the following figures:
Nortel Confidential
153
IuPc configuration and activation:
IuPc and Agps location services configuration and activation:
Detailed procedures for Agps location services activation only is presented in the following figure:
Nortel Confidential
154
Evolutions for UMTS5.0: Activation pre-checks and post-checks (Network and OMC is up and running without any problem (alarm, MIB state, synchronization state,etc.), calls can be performed on the impacted RNC, workorder for activation is ready to be imported, feature is activated after procedure completion. ;
Constraints: IuPC software must have been downloaded and activated on the RNC IN-PSFP cards.
Durations: Timing depends on many parameters: hardware and software configurations, network size, transmission network performance, etc Provided information is informative only. Durations are given for the activation of one NodeB in a network containing 7 RNCs and 860 NodeB.
Nortel Confidential
155
16.2.3.2
411-8111-549 ORTHOGONAL CHANNEL NOISE SIMULATION

This FAP provides procedures to activate the OCNS feature on the OMC emphasizing the data fill impact on the Utran subsystem. This service is used during acceptance to check the network quality when it is highly loaded. The load per cell is tuned up to the maximum cell capacity, leaving only enough power for setting a couple of communications for the test mobiles. The document applies to utran V4.2, Utran V4.1 and Utran V4.0.
Description: The activation procedure can be performed either with WPS Access or directly on WNMS. WPS operations include a reverse engineering phase that imports a view of the current network configuration into WPS, then updates are done at WPS level, workorders are exported from WPS and configuration updates are imported in W-NMS. The document includes a reverse procedure.
Detailed procedure with WPS is presented in the following figure:
Detailed procedure with W-NMS is presented in the following figure:
Evolutions for UMTS50: Activation pre-checks and post-checks (Network and OMC is up and running without any problem (alarm, MIB state, synchronization state,etc.), calls can be performed on the impacted RNC, workorder for activation is ready to be imported, feature is activated after procedure completion. ;
Constraints:
Nortel Confidential
156
OCNS artificially loads UMTS FDD Cells only (GSM or UMTS TDD network is excluded). During activation, impacted FDDCells are locked then unlocked.
Durations: Timing depends on many parameters: hardware and software configurations, network size, transmission network performance, etc Provided information is informative only. Durations are given for the activation on 3 FDDCells of one NodeB in a network containing 7 RNCs and 860 Node B.
Nortel Confidential
157
16.2.3.3 411-8111-542 3G COMPRESSED MODE
TO
2G
HANDOVER
WITH
OR
WITHOUT
This document provides procedures to configure and activate the feature 3G to 2G handover with or without compressed mode. Supported handovers are: Blind Handover, HO with measurement (Dual receiver UE) and HO with compressed mode. The document applies to utran V4.2, Utran V4.1 and Utran V4.0.
The following table lists the possible activations supported by the FAP
Description: The activation procedure can be performed with WPS Access or directly on W-NMS. The activation performed directly with W-NMS requires the GSM neighboring plan already configured on the OMC. If not, the WPS procedure should be performed. WPS operations includes a reverse engineering phase that imports a view of the current network configuration into WPS, then updates are done at WPS level, workorders are exported from WPS and configuration updates are imported in W-NMS. The document includes reverse procedures.
Nortel Confidential
158
Detailed procedures with WPS are presented in the following figure:
Detailed procedures with W-NMS are presented in the following figure:
Evolutions for UMTS50: Activation pre-checks and post-checks (Network and OMC is up and running without any problem (alarm, MIB state, synchronization state, etc.), calls can be performed on the impacted RNC, workorder for activation is ready to be imported, feature is activated after procedure completion. ; UA42 specific parameters settings.
Constraints: The classical handover with compressed mode and the fast alarm handover can not be run simultaneously: theses two features are exclusive at RNC level. Three compressed mode patterns have been defined in V4 releases: o Two for GSM (inter RAT HO): GSM RSSI Measurements and GSM Initial BSIC Identification. Both must be activated to allow 2G measurements. If one is de-activated, the 2G compressed mode is considered as not activated. One for FDD (3G-3G inter-freq HO)
Nortel Confidential
159
The different patterns (for 2G or 3G measurements) cannot be configured active at the same time: if both of measurements are possible, only one kind of pattern will be used. If the primary cell contains at least one 2G neighbor cell, then the 2G compressed mode patterns will be used. . Many prerequisites are defined at the core level (UMTS: GSM): o o o o o o o 3G-MSC and 2G-MSC belong to the same PLMN. It is recommended to very well synchronize the 3G-MSC and 2G-MSC and propagate the synchronization to the related Node Bs and 2G BTS 3G Core and UTRAN are integrated. In case of non-Nortel Core, MVSI tests must be performed. 2G NSS and BSS are integrated and are compliant with Release 99 in terms of UE class mark. UMTS Core and GSM NSS datafill have been performed. 3G MSC/VLR 2G MSC/VLR (MAP E interface) are already integrated. For Nortel switches only: 3G-MSC and 2G-MSC loads are at least GSM15 with right level of patch (all 3G->2G CR fixed).
Durations: Timing depends on many parameters: hardware and software configurations, network size, transmission network performance, etc Provided information is informative only. Durations are given for the activation on one NodeB in a network containing 7 RNCs and 860 Node B.
Nortel Confidential
160
Nortel Confidential
161
16.2.3.4
411-8111-548 CELL FACH

This FAP provides procedures to configure and activate the CELL_FACH feature. This service is subdivided into four functional steps, three being supported: Step 1: NAS signaling on FACH Step 2: Call setup on FACH Step 4: Always ON on FACH The document applies to utran V4.2, Utran V4.1 and Utran V4.0.
Description: The activation procedure can be performed with WPS Access or directly on W-NMS (for UA4.0 only). WPS operations includes a reverse engineering phase that imports a view of the current network configuration into WPS, then updates are done at WPS level, workorders are exported from WPS and configuration updates are imported in W-NMS. The document includes reverse procedures. Detailed procedure for Cell FACH step 1&2 with WPS is presented in the following figure:
Nortel Confidential
162
Detailed procedure for Cell FACH step 1, 2 & 4 with WPS is presented in the following figure:
Detailed procedure for Cell FACH step 4 with WPS is presented in the following figure:
Detailed procedure for Cell FACH step 1&2 with W-NMS is presented below:
Detailed procedure for Cell FACH step 1,2&4 with W-NMS is presented below:
Nortel Confidential
163
Detailed procedure for Cell FACH step 4 with W-NMS is presented in the following figure:
Evolutions for UMTS50: Activation pre-checks and post-checks (Network and OMC is up and running without any problem (alarm, MIB state, synchronization state,etc.), calls can be performed on the impacted RNC, workorder for activation is ready to be imported, feature is activated after procedure completion. ; W-NMS procedure limited to Utran 4.0.
Constraints: Inter RNC cell update is not supported In case of unsuccessful transition to CELL_FACH due to CELL FACH CAC failure, the call is released. For Utran V4.0, cell reselection parameters in Idle mode and CELL_FACH are not differentiated. For cell fach step4: Feature AlwaysOn must be activated and enabled. The Sccpch ClassId of all FDD Cells on which Cell Fach Step 4 has to be activated must point to the Rnc/<rncName> RadioAccessService/0 SccpchClass/1 object.
The following tables give impact for WPS operation (resp. W-NMS operation)
Durations:
Nortel Confidential
164
Timing depends on many parameters: hardware and software configurations, network size, transmission network performance, etc Provided information is informative only. Durations are given for the activation on one RNC in a network containing 7 RNCs and 860 Node B.
The following table gives mean time for the various sheets listed in the procedures:
Nortel Confidential
165
17. NTP REFERENCE LIST

Title
UMTS Network Overview Terminology Nortel UMTS BTS (12000, 6000, and 1000 Families) Description Nortel GSM-UMTS BTS 18000 Description UMTS BTS (12000, 6000, and 1000 Families) Hardware Preventive Maintenance Guide UMTS BTS (12000, 6000, and 1000 Families) Hardware Corrective Maintenance Guide Nortel GSM-UMTS BTS 18000 Hardware Preventive Maintenance Guide Nortel GSM-UMTS BTS 18000 Hardware Corrective Maintenance Guide UMTS BTS Fault Analysis BTS TIL Tool Nortel UMTS RNC 1000 Description Nortel UMTS RNC 1500 Description UMTS RNC 1000 Hardware Maintenance Guide UMTS RNC 1500 Hardware Maintenance Guide UMTS RNC 1000 and 1500 Fault Analysis RNC 1000 TML Tool RNC 1500 TML Tool Access Network Parameters (P1-P6) Access Network Parameters Plates Access Network Observation Counters (P1-P3) RNC 1500 Patching Procedures
Reference
411-8111-101 411-8111-804 411-8111-905 411-8111-936
411-8111-559
411-8111-560
411-8111-561 411-8111-562 411-8111-556 411-8111-518 411-8111-906 411-8111-931 411-8111-508 411-8111-563 411-8111-554 411-8111-519 411-8111-565 411-8111-813 411-8111-805 411-8111-822 411-8111-232
Nortel Confidential
166
Title
RNC 1000 Software Upgrade Procedure Using OAM 4.2 - Type 7 IntraRelease RNC 1000 Software Upgrade Procedure Using OAM 4.2 - Type 6 IntraRelease RNC 1000 Software Upgrade Procedure Using OAM 4.2 - Type 6 InterRelease RNC 1000 to RNC 1500 Migration Procedure Using OAM 4.2 Node-B Software Upgrade Procedure Using OAM 4.2 - Inter-Release Node-B Software Upgrade Procedure Using OAM 4.2 - Intra-Release RNC 1500 Software Upgrade Procedure Using OAM 4.2 - Current Mib Intra-Release RNC 1500 Software Upgrade Procedure Using OAM 4.2 - New Mib Intra-Release RNC 15000 Patching procedures
Reference
411-8111-221 411-8111-222 411-8111-224 411-8111-226 411-8111-227 411-8111-228 411-8111-229 411-8111-230 411-8111-232
Nortel Confidential
167
18. NRP REFERENCE LIST

The Network Reconfiguration Procedures for OAM05.0 are listed in the following table:
Network Reconfiguration Procedures OAM 5.0 Document reference

411-8111-514 411-8111-539 411-8111-540 411-8111-545 411-8111-551
Title
Scrambling code plan update Node B Addition Node B Reparenting Neighboring plan update 551 LAC/RAC plan update
Status
Updated Updated Updated Updated Updated
Nortel Confidential
168
19. FAP REFERENCE LIST

The Feature Activation Procedures for OAM05.0 are listed in the following table:
Feature Activation Procedures OAM 5.0 Document reference

411-8111-507 411-8111-542 411-8111-548 411-8111-549 411-8111-575
Title
IUPC - AGPS Location Services 3G to 2G Handover with or without compressed mode CELL FACH Orthogonal Channel Noise Simulation HSDPA
Status
Updated Updated Updated Updated Introduced for OAM05.0
The following OAM04.2 FAP has been removed from the list: 411-8111-557 Password Expiration Policy Removed for OAM05.0
Nortel Confidential
169
20. ABBREVIATIONS AND DEFINITIONS

20.1. ABREVIATIONS
AN CM CN EM FM GUI IN MO PM WICL Access Node Configuration Management Control Node Equipment Monitor Fault Management Graphic User Interface Interface Node Managed Object Performance Management Wireless Internet Command Language
20.2. DEFINITIONS
Itf-B Itf-R Interface between the Node B and its Element Manager Interface between the RNC and its Element Manager
Nortel Confidential
170
ANNEX A: NEW/DELETED/MODIFIED ALARMS

This annex lists the new, deleted and modified alarms between UA04.1 and U404.2, and OAM04.2 and OAM05.0.
1.
1.1.
UA04.2/OAM05.0 NEW ALARMS

BTS NEW ALARMS
This part lists the new alarms for the UA04.2 release. It is split in two parts: Equipment alarms (refer to paragraph 1.1.1) OAM alarms (refer to paragraph 1.1.2)
1.1.1 BTS NEW ALARMS

This section lists the new alarms for the BTS introduced for the UA04.2 release. The alarm detailed description is available in [R10]. For each new alarm for a managed object, the following information is presented: <fault probable cause> on <EquipmentType> (Fault name) The following alarms have been added: ANTENNA ACCESS ALARMS None
BOARD ALARMS None
BTS CELL ALARMS None
BTS EQUIPMENT ALARMS Configuration Or Customization Error on BTS (NOT ENOUGH HSDPA RESOURCE)
Nortel Confidential
171
COOLING SYSTEM ALARMS None
NODEBCBP ALARMS None
PASSIVE COMPONENT ALARMS None
PCM ALARMS None
POWER SYSTEM ALARMS None
SITE LAN ALARMS None
1.1.2 BTS OAM NEW ALARMS

This section lists the new OAM alarms for the BTS introduced for the UA04.2 release. The alarm detailed description is available in [R10]. For each new alarm for a managed object, the following information is presented: <fault probable cause> on <EquipmentType> (Fault name) The following alarms have been added: Underlying Resource Unavailable (Hardware extraction): OAM_54 Unspecified Reason (Hardware insertion): OAM_55
Nortel Confidential
172
1.2.
RNC ALARMS
This part lists the new alarms for the UA04.2 release. It is split in two parts: Equipment alarms (refer to paragraph 1.2.1) OAM alarms (refer to paragraph 1.2.2)
1.2.1 RNC NEW ALARMS

This section lists the new alarms introduced for the UA04.2 release. The alarm detailed description is available in [R9]. For each new alarm for a managed object, the following information is presented: <fault probable cause> on <EquipmentType> (Fault name) The following alarms have been added: Equipment Malfunction on HsdpaResource (ANO CELL NOT HSDPA CAPABLE INFORMATION) Configuration Or Customization Error on CONFIGURATION FAILURE INFORMATION) FDDCell (ANO HSDPA
Cause Of Restart Or Switchover on HsdpaResource (ANO HSDPA HARDWARE RECOVERY INFORMATION) Equipment Malfunction on FDDCell (ANO DEGRADED CELL STATUS INFORMATION) Equipment Malfunction on RNC (ANO GENERIC ALARM)
1.2.2 RNC NEW OAM ALARMS

This section lists the new alarms for the RNC introduced for the UA04.2 release. The alarm detailed description is available in [R9]. Communications Subsystem Failure (Unexpected RNC MIBState set to update in progress): OAM_53 Configuration Or Customization Error (RNC family not compatible with RNC architecture): OAM_56 Configuration Or Customization Error (MIB number received from NE different from MIB number stored in the active view): OAM_57
Nortel Confidential
173
2.
2.1.
UA04.2/OAM05.0 DELETED ALARMS

BTS DELETED ALARMS
This part lists the modified alarms between the UA04.1 and UA04.2 releases. It is split in two parts: Equipment alarms (refer to paragraph 2.1.1) OAM alarms (refer to paragraph 321.2)
2.1.1 BTS DELETED ALARMS

No deleted alarm.
2.1.2 BTS DELETED OAM ALARMS

No deleted alarm.
2.2.
RNC DELETED ALARMS

This part lists the modified alarms between the UA04.1 and UA04.2 releases. It is split in two parts: Equipment alarms (refer to paragraph 2.2.1) OAM alarms (refer to paragraph 2.2.2)
2.2.1 RNC DELETED ALARMS

No deleted alarm.
2.2.2 RNC DELETED OAMALARMS

No deleted alarm.
Nortel Confidential
174
3.
3.1.
UA04.2/OAM05.0 DELETED ALARMS

BTS MODIFIED ALARMS
For more information, please refer to [R10].
3.1.1 BTS MODIFIED ALARMS

No modified alarm.
3.1.2 BTS MODIFIED OAM ALARMS

No modified alarm.
3.2.
RNC MODIFIED ALARMS

For more information, please refer to [R9].
3.2.1 RNC MODIFIED ALARMS

No modified alarm.
3.2.2 RNC MODIFIED OAM ALARMS

No modified alarm.
Nortel Confidential
175
ANNEX B: NEW/DELETED/MODIFIED PARAMETERS

This annex lists the new, deleted and modified parameters between UA04.1 and U404.2, and OAM04.2 and OAM05.0.
1.
UA04.2/OAM05.0 NEW PARAMETERS

The number of New Objects is: 38 for CNode 2 for ANode 13 for INode 1 for BTS 0 for OAM 0 for POC
The information is presented in a table with, in the first row, the name of the object, and in the following rows, the names of the parameters associated to the object: Object A Parameter 1 Parameter 2
1.1.
CNODE NEW PARAMETERS
CallEstabCauseConfClass operatorId rdnId DlRbRaTrafficMonitoring operatorId raMaxConfidenceInt raModifiedStudentCoef raNbOfSample raSduQueueThreshold raUnitPeriodTime
Nortel Confidential
176
userSpecificInfo rdnId FullEventHOConfHhoMgt IntraFreqInterRnc_cpichEcNoReportingRange operatorId timerAlarmHoEvent userSpecificInfo rdnId FullEventHOConfHhoMgtEvent2D cpichEcNoThresholdUsedFreq2D cpichRscpThresholdUsedFreq2D operatorId userSpecificInfo rdnId FullEventHOConfHhoMgtEvent2F cpichEcNoThresholdUsedFreq2F cpichRscpThresholdUsedFreq2F operatorId userSpecificInfo rdnId FullEventHOConfShoMgt cpichEcNoReportingRange1A cpichEcNoReportingRange1B cpichEcNoThresholdUsedFreq1E cpichEcNoThresholdUsedFreq1F operatorId userSpecificInfo rdnId FullEventRepCritHhoMgt operatorId userSpecificInfo rdnId
Nortel Confidential
177
FullEventRepCritHhoMgtEvent2C maxNbReportedCells2C operatorId timeToTrigger2C userSpecificInfo rdnId FullEventRepCritHhoMgtEvent2D maxNbReportedCells2D operatorId timeToTrigger2D userSpecificInfo rdnId FullEventRepCritHhoMgtEvent2F maxNbReportedCells2F operatorId timeToTrigger2F userSpecificInfo rdnId FullEventRepCritHhoMgtEvent3C maxNbReportedCells3C operatorId timeToTrigger3C userSpecificInfo rdnId FullEventRepCritIntraFreqInterRncEvent amountRep hysteresis maxNbReportedCells operatorId repInterval timeToTrigger userSpecificInfo rdnId
Nortel Confidential
178
FullEventRepCritShoMgt operatorId userSpecificInfo rdnId FullEventRepCritShoMgtEvent1A amountRep1A maxNbReportedCells1A operatorId repInterval1A timeToTrigger1A userSpecificInfo rdnId FullEventRepCritShoMgtEvent1B amountRep1B maxNbReportedCells1B operatorId repInterval1B timeToTrigger1B userSpecificInfo rdnId FullEventRepCritShoMgtEvent1C amountRep1C hysteresis1C maxNbReportedCells1C operatorId repInterval1C timeToTrigger1C userSpecificInfo rdnId
Nortel Confidential
179
FullEventRepCritShoMgtEvent1D hysteresis1D maxNbReportedCells1D operatorId timeToTrigger1D useCIOfor1D userSpecificInfo rdnId FullEventRepCritShoMgtEvent1E maxNbReportedCells1E operatorId timeToTrigger1E userSpecificInfo rdnId FullEventRepCritShoMgtEvent1F maxNbReportedCells1F operatorId timeToTrigger1F userSpecificInfo rdnId HsdpaCellClass maximumNumberOfUsers minimumPowerForHsdpa numberOfHsPdschCodes numberOfHsScchCodes operatorId userSpecificInfo rdnId
Nortel Confidential
180
HsdpaResource hsdpaCellClassId hsdpaCellClassRef operatorId userSpecificInfo rdnId HsdpaRncConf deltaCfnForHsdpaChannelTypeSwitching deltaCfnForHsdpaMobility deltaCfnForHsdpaRLCReconfiguration isRLCReconfigurationForChannelTypeSwitching maxIubHsDschFrameSize nbOfSpiConfiguration operatorId suspendTimeOffset userSpecificInfo rdnId HsdpaUserService ackNackRepetitionFactor ackPowerOffset cqiFeedbackCycleK cqiPowerOffset cqiRepetitionFactor discardTimer hsScchPowerOffset macHsWindowSize measurementPowerOffset nackPowerOffset operatorId timerT1 userSpecificInfo rdnId
Nortel Confidential
181
HsDschFlowInformation maxNumberOfRetryRequest minTimeBetweenRequest operatorId userSpecificInfo rdnId IrmCEMLoadParameters green2YellowDlCEMThreshold operatorId red2YellowDlCEMThreshold userSpecificInfo yellow2GreenDlCEMThreshold yellow2RedDlCEMThreshold rdnId IrmIubTransportLoadParameters green2YellowDlTLCThreshold irmIubLoadQos operatorId red2YellowDlTLCThreshold userSpecificInfo yellow2GreenDlTLCThreshold yellow2RedDlTLCThreshold rdnId IrmPreemptionCEMLoadParameters congested2NormalDlCEMThreshold normal2CongestedDlCEMThreshold operatorId userSpecificInfo rdnId
Nortel Confidential
182
IrmPreemptionIubTransportLoadParameters congested2NormalDlTLCThreshold irmPreemptionIubLoadQos normal2CongestedDlTLCThreshold operatorId userSpecificInfo rdnId IrmSchedulingDowngradeTransCodePower operatorId userSpecificInfo rdnId LowRbA maxbitRate operatorId thresholdTransCodePowerDefinitionParam timeToTrigger userSpecificInfo rdnId RACHComputedGainFactors operatorId refTfcId rdnId RACHSignalledGainFactors betaC betaD operatorId refTfcId rdnId
Nortel Confidential
183
ReferenceUlRbSetList operatorId referenceUlRbSetConfId referenceUlRbSetConfRef userSpecificInfo rdnId RRCSysInfoMeas operatorId sib11IntraFreqMeasurementFilterCoeffOnRACH sib11IntraFreqMeasurementNbrOfCellOnRACH userSpecificInfo rdnId SourceConformanceInformation maximumBucketSize maximumTokenGenerationRate operatorId sourceConformanceStatus userSpecificInfo rdnId SpiConfiguration backgroundSpi interactiveSpi operatorId priorityLevel streamingSpi userSpecificInfo rdnId
Nortel Confidential
184
UlRbRaTrafficMonitoring operatorId raMaxConfidenceInt raModifiedStudentCoef raNbOfSample raUnitPeriodTime userSpecificInfo rdnId UserServicesPerEstabCause dlUserServiceId dlUserServiceRef estabCause operatorId ulUserServiceId ulUserServiceRef rdnId userLabel
Nortel Confidential
185
1.2.
Server
ANODE NEW PARAMETERS
ipAddress ipStack stratumLimit rdnId Time timeDifferenceLimit
Nortel Confidential
186
1.3.
Aal2If
INODE NEW PARAMETERS
customerIdentifier commentText ecrOverBook cacMethod loadBalancingMethod qos0BwReservation qos1BwReservation qos2BwReservation qos3BwReservation umtsInterfaceList rdnId Alcap AlcapConn destPointCode networkIndicator Aal2Lk linkToAal2If rdnId rdnId rdnId IuPs commentText gtpEchoReqInterval gtpEchoRspTime gtpEchoReqAttempts Iub commentText rdnId
Nortel Confidential
187
Iucs commentText rdnId Iur commentText rdnId IuUplane Aal2EndPoint address rdnId Fc iubFlowControlActivation qosDiscardThreshold qosBackPressureThreshold cellColor Qaal2P originatingA2ea timerErq timerRel timerRes timerBlo timerUbl timerMod resetRetries Route linkToAal2If cost rdnId
Nortel Confidential
188
1.4.
BTS NEW PARAMETERS
HsdpaConf dchPowerMargin harqNbMaxRetransmissions harqType hsdpaResourceId hsdschInterval hsscchPcOffset maxRateGrowth operatorId userSpecificInfo rdnId
1.5.
OAM NEW PARAMETERS

None
1.6.
POC NEW PARAMETERS

None
Nortel Confidential
189
2.
UA04.2/OAM05.0 DELETED PARAMETERS

The number of Deleted Objects is: 4 for CNode 3 for ANode 1 for INode 0 for BTS 0 for OAM 1 for POC
2.1.
A2EA
CNODE DELETED PARAMETERS
addressA2EA iuxIfId operatorId userSpecificInfo rdnId rdnId ALCAPDistantSignallingEntity alcapRouteSetId alcapRouteSetRef operatorId userSpecificInfo rdnId rdnId DlOuterLoopPowerCtrl dlBlerQuality operatorId userSpecificInfo rdnId
Nortel Confidential
190
RouteSet destinationPointCode networkIndicator operatorId userSpecificInfo rdnId
2.2.
Test
ANODE DELETED PARAMETERS
automaticBusClockTest Time Server ipAddress ipStack rdnId
2.3.
IuxIf
INODE DELETED PARAMETERS
customerIdentifier commentText accessType cacMethod loadBalancingMethod qos0BwReservation qos1BwReservation qos2BwReservation qos3BwReservation rdnId
Nortel Confidential
191
2.4.
BTS DELETED PARAMETERS

None
2.5.
OAM DELETED PARAMETERS

None
2.6.
E1
POC DELETED PARAMETERS
lineType clockingSource crc4Mode sendRaiOnAis raiDeclareAlarmTime raiClearAlarmTime ssmE1SaNumber customerIdentifier vendor commentText ifAdminStatus
Nortel Confidential
192
3.
UA04.2/OAM05.0 MODIFIED PARAMETERS

The number of Deleted Objects is: 94 for CNode 14 for ANode 28 for INode 20 for BTS 10 for OAM 10 for POC
3.1.
CNODE MODIFIED PARAMETERS
3.1.1 ACCESSSESSION (ACCESSSESSION)

Modified Parent: RNC CallTrace AccessSession Modified Attribute Visibility Old Value customer New Value manufacturer
New Parameters: dataFileUploadPeriod Deleted Parameters: datafileUploadPeriod
3.1.2 AGPSUEBASEDLOCATIONTECHNOLOGYEXTENDEDPARAMS (AGPSUEBASEDLOCATIONTECHNOLOGYEXTENDEDPARAMS)

Modified Parent: RNC LocationServices AGPSUeBasedLocationTechnology AGPSUeBasedLocationTechnologyExtendedParams Modified Attribute Visibility Old Value manufacturer New Value manufacturer
Nortel Confidential
193
3.1.3 ALARMHARDHOCONF (ALARMHARDHOCONF)

New Parameters: nbConditionsFulfilledBeforeBlindInterFreqHo Modified Parameters: Parameter Name counter initialValue 20 5 Modified Attribute Old Value New Value
3.1.4 ALWAYSONCONF (ALWAYSONCONF)

Modified Parameters: Parameter Name alwaysOnDlRbSetDchId range alwaysOnDlRbSetFachId range alwaysOnUlRbSetDchId range alwaysOnUlRbSetFachId range isAlwaysOnAllowed initialValue preferredTransportTypeForAlwaysOn initialValue Dch Fach false N.A. RNC UlRbSetConf RadioAccessService UlRbSetConf RNC UlRbSetConf RadioAccessService UlRbSetConf RNC DlRbSetConf RadioAccessService DlRbSetConf RNC DlRbSetConf RadioAccessService DlRbSetConf Modified Attribute Old Value New Value
3.1.5 ALWAYSONTIMER (ALWAYSONTIMER)

New Parameters: timerT1ForHsdpa timerT2ForHsdpa Modified Parameters: Parameter Name timerT1 initialValue 10000 100 Modified Attribute Old Value New Value
Nortel Confidential
194
3.1.6 ANODE (ANODE)

Modified Parameters: Parameter Name PPProvisionedSystemRelease visibility customer manufacturer Modified Attribute Old Value New Value
3.1.7 ANODESOFTWARE (ANODESOFTWARE)

Modified Parent: RNC RNCEquipment ANode ANodeSoftware Modified Attribute Visibility Old Value customer New Value manufacturer
3.1.8 AOONFACHPARAM (AOONFACHPARAM)

Modified Parameters: Parameter Name timeToTrigger timeToTrig0, timeToTrig10, timeToTrig20, timeToTrig40, timeToTrig60, timeToTrig80, timeToTrig100, timeToTrig120, timeToTrig160, timeToTrig200, timeToTrig240, timeToTrig320, timeToTrig640, timeToTrig1280, timeToTrig2560, timeToTrig5000 timeToTrig0 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 0 Modified Attribute Old Value New Value
range
initialValue
3.1.9 ARPRIORITYLEVEL (ARPRIORITYLEVEL)

Modified Parameters: Parameter Name irmDlRbSetId range RNC RadioAccessService DlRbSetConf DlRbSetConf Modified Attribute Old Value New Value
Nortel Confidential
195
3.1.10 CACCONFCLASS (CACCONFCLASS)

Modified Parent: RNC RadioAccessService DedicatedConf CacConfClass Modified Attribute Cardinality Old Value 0..5 New Value 0..15
New Parameters: maxUlEstablishmentRbRate Modified Parameters: Parameter Name rdnId range [0..9] [0..14] Modified Attribute Old Value New Value
3.1.11 CALLACCESSPERFORMANCECONF (CALLACCESSPERFORMANCECONF)

Modified Parameters: Parameter Name deltaCpichEcNoUsedQuickRepeat presence dataType range initialValue deltaCpichRscpUsedQuickRepeat presence dataType range initialValue isFachPowerAdjustmentEnabled visibility n351 initialValue numberOfQuickRepeat presence t351 range initialValue 0, 100, 200, 300, 400, 500 0, 400, 500, 600, 700, 800 400 700 optional required 2 1 manufacturer customer optional Decimal [0..75] 37 required Signed [-50..50] 0 optional Decimal [0.0..7.5] 3.7 required Signed [-5.0..5.0] 0 Modified Attribute Old Value New Value
Nortel Confidential
196
3.1.12 CALLTRACE (CALLTRACE)

Modified Parent: RNC CallTrace Modified Attribute Visibility Old Value customer New Value manufacturer
3.1.13 CC1 (CC1)

Modified Parent: RNC RNCEquipment CNode CC1 Modified Attribute Visibility Old Value manufacturer New Value manufacturer
3.1.14 CELLCOLORS (CELLCOLORS)

New Parameters: userLabel Modified Parameters: Parameter Name rdnId visibility customer manufacturer Modified Attribute Old Value New Value
3.1.15 CELLSESSION (CELLSESSION)

Modified Parent: RNC ObjectTrace CellSession Modified Attribute Visibility Old Value customer New Value manufacturer
3.1.16 CMODEPATTERNSEQINFO (CMODEPATTERNSEQINFO)

Nortel Confidential
197
3.1.17 CNODESOFTWARE (CNODESOFTWARE)

Modified Parent: RNC RNCEquipment CNode CNodeSoftware Modified Attribute Visibility Old Value customer New Value manufacturer
3.1.18 COMPUTEDGAINFACTORS (COMPUTEDGAINFACTORS)

Modified Parameters: Parameter Name refTfcId range [0..3] [0..30] Modified Attribute Old Value New Value
3.1.19 CONTROLPORT (CONTROLPORT)

Modified Parameters: Parameter Name vc range [0..4095] [0..16128] Modified Attribute Old Value New Value
3.1.20 CORESESSION (CORESESSION)

Modified Parent: RNC CallTrace CoreSession Modified Attribute Visibility Old Value customer New Value manufacturer
3.1.21 CSCORENETWORKACCESS (CSCORENETWORKACCESS)

New Parameters: iucsIfId sccpDestinationPointCode sccpNetworkIndicator Deleted Parameters: sccpRouteSetId sccpRouteSetRef
Nortel Confidential
198
3.1.22 DEDICATEDCONF (DEDICATEDCONF)

Modified Parent: RNC RadioAccessService DedicatedConf Modified Attribute Cardinality Modified Parameters: Parameter Name rdnId range [0..1] [0..0] Modified Attribute Old Value New Value Old Value 1..* New Value 1..1
3.1.23 DELTASIR2ANDAFTER2 (DELTASIR2ANDAFTER2)

Modified Parent: RNC RadioAccessService DlUserService DeltaSir2AndAfter2 Modified Attribute Visibility Old Value manufacturer New Value manufacturer
3.1.24 DHIGHRBB1 (DHIGHRBB1)

Modified Parameters: Parameter Name thresholdTransCodePower unit domain step dataType range N.A. Decimal [0..255] N.A. dBm dBm 0.5 Signed [-10.0..46.0] Modified Attribute Old Value New Value
3.1.25 DLDYNAMICPARAMETERPERDCH (DLDYNAMICPARAMETERPERDCH)

New Parameters: dlRateMatchingAttribute
Nortel Confidential
199
3.1.26 DLRBSETCONF (DLRBSETCONF)

New Parameters: dlBlerQuality dlRbRateAdaptationDownsizeThreshold dlRbRateAdaptationUpsizeThreshold dlSrbErrorMatching isDlRbRateAdaptationAllowedForThisDlRbSetConf isDlReferenceTransportChannelAllowed isThisRbRateAdaptationDlRbSetTargetAllowed userLabel Modified Parameters: Parameter Name iuCsTransportQosId initialValue reEstablishTimer initialValue rlcConfClassId range rdnId visibility customer manufacturer RNC RadioAccessService RlcConfClass RlcConfClass reestablishTimerUseT315 N.A. 0 N.A. Modified Attribute Old Value New Value
3.1.27 DLRLCACKMODE (DLRLCACKMODE)

Modified Parameters: Parameter Name lastRetransPuPoll initialValue lastTransPuPoll initialValue misPuIndic initialValue nbrOfPuBetweenPolling initialValue nbrOfSduBetweenPolling initialValue pollingTimer initialValue prohibitedPollingTimer initialValue prohibitedStatusTimer initialValue
Modified Attribute
Old Value N.A.
New Value true
N.A.
true
N.A.
true
N.A.
64
N.A.
30
N.A.
200
N.A.
10
N.A.
Nortel Confidential
200
3.1.28 DLRLCTMODE (DLRLCTMODE)

Modified Parameters: Parameter Name segmentationInd initialValue N.A. false Modified Attribute Old Value New Value
3.1.29 DLRLCUMODE (DLRLCUMODE)

Modified Parameters: Parameter Name rlcDiscard initialValue N.A. timerDiscard100ms Modified Attribute Old Value New Value
3.1.30 DLUSERSERVICE (DLUSERSERVICE)

Modified Parent: RNC RadioAccessService DlUserService Modified Attribute Cardinality Old Value 1..30 New Value 1..40
New Parameters: isDlRbRateAdaptationAllowedForThisDlUserService isTransCodePowerIrmSchedulingDowngradeAllowedFromThisDlUserService userLabel Deleted Parameters: dlRbSetConfId dlRbSetConfRef Modified Parameters: Parameter Name isAlwaysOnAllowed initialValue isGsmCModeActivationAllowed initialValue isIrmSchedulingAllowed initialValue rdnId visibility range customer [0..29] manufacturer [0..39] false N.A. false N.A. false N.A. Modified Attribute Old Value New Value
Nortel Confidential
201
3.1.31 DLUSPOWERCONF (DLUSPOWERCONF)

Modified Parent: RNC RadioAccessService DedicatedConf PowerConfClass DlUsPowerConf Modified Attribute Cardinality Old Value 1..30 New Value 1..40
New Parameters: dlIrmSchedDowngradeTxcpTrigger_threshold_delta dlIrmSchedDowngradeTxcpTrigger_timeToTrigger isIrmSchedDowngradeTxcpAllowed userLabel Modified Parameters: Parameter Name minDlTxPower initialValue rdnId visibility range customer [0..29] manufacturer [0..39] -11 N.A. Modified Attribute Old Value New Value
3.1.32 DXCHCONF (DXCHCONF)

Modified Parent: RNC RadioAccessService SccpchClass DxChConf Modified Attribute Visibility Modified Parameters: Parameter Name Modified Attribute fachClassId range RNC RadioAccessService FachClass RadioAccessService FachClass Old Value New Value Old Value manufacturer New Value manufacturer
3.1.33 DYNAMICPARAMETERPERDCH (DYNAMICPARAMETERPERDCH)

New Parameters: qeThreshold ulRateMatchingAttribute ulUpSirStep updateThreshold validityCondition Modified Parameters: Parameter Name ulBlerTarget initialValue
Modified Attribute -1
Old Value
New Value N.A.
Nortel Confidential
202
3.1.34 EVENT1A (EVENT1A)

Modified Parent: RNC RadioAccessService DedicatedConf MeasurementConfClass Event1a Modified Attribute Visibility Modified Parameters: Parameter Name reportingAmount range amountReport1, amountReport2, amountReport4, 1, 2, 4, 8, 16, 32, amountReport8, amountReport16, amountReport32, 64, Infinity amountReport64, amountReportinfinity 4 timeToTrig10, timeToTrig60, timeToTrig120, timeToTrig240, timeToTrig1280, timeToTrig20, timeToTrig80, timeToTrig160, timeToTrig320, timeToTrig2560, Modified Attribute Old Value New Value Old Value manufacturer New Value manufacturer
initialValue amountReport4 timeToTrigger timeToTrig0, timeToTrig40, timeToTrig100, timeToTrig200, timeToTrig640, timeToTrig5000
range
0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 40
initialValue timeToTrig40
3.1.35 EVENT1F (EVENT1F)

Modified Parent: RNC RadioAccessService DedicatedConf MeasurementConfClass Event1f Modified Attribute Visibility Modified Parameters: Parameter Name timeToTrigger timeToTrig0, timeToTrig10, timeToTrig20, timeToTrig40, timeToTrig60, timeToTrig80, timeToTrig100, timeToTrig120, timeToTrig160, timeToTrig200, timeToTrig240, timeToTrig320, timeToTrig640, timeToTrig1280, timeToTrig2560, timeToTrig5000 timeToTrig40 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 40 Modified Attribute Old Value New Value Old Value manufacturer New Value manufacturer
range
initialValue
Nortel Confidential
203
3.1.36 FACH (FACH)

Modified Parent: RNC NodeB FDDCell SCCPCH FACH Modified Attribute Cardinality New Parameters: maxFachPowerRelativeToPcpich Modified Parameters: Parameter Name Modified Attribute fachClassId range rdnId range [0..9] [0..1] RNC RadioAccessService FachClass RadioAccessService FachClass Old Value New Value Old Value 1..10 New Value 1..2
3.1.37 FACHCLASS (FACHCLASS)

Modified Parent: RNC RadioAccessService FachClass Modified Attribute OnLineCreation OnLineDeletion Visibility Old Value Allowed Allowed manufacturer New Value NotAllowed NotAllowed manufacturer
Nortel Confidential
204
3.1.38 FACHPOWERADJUSTMENTPARAMS (FACHPOWERADJUSTMENTPARAMS)

Modified Parent: RNC RadioAccessService ServiceInit CallAccessPerformanceConf FachPowerAdjustmentParams Modified Attribute Presence Cardinality New Parameters: initialFachPowerAdjustment Deleted Parameters: fachPowerControlExtendedParams Modified Parameters: Parameter Name fachPowerAdjustmentCpichEcNoThreshold visibility fachPowerAdjustmentCpichRscpThreshold visibility fachTransmitPowerLevelStep visibility dataType range manufacturer Signed [-3.0..3.0] customer Decimal [0.0..3.0] manufacturer customer manufacturer customer Modified Attribute Old Value New Value Old Value optional 0..1 New Value required 1..1
3.1.39 FASTALARMHARDHOCONF (FASTALARMHARDHOCONF)

Modified Parameters: Parameter Name blindHhoTimerForGsm initialValue counter initialValue 20 5 8000 6000 Modified Attribute Old Value New Value
Nortel Confidential
205
3.1.40 FDDCELL (FDDCELL)

New Parameters: callEstabCauseConfClassId callEstabCauseConfClassRef hsdpaActivation isCallEstabCausePerCellBasisActivated isEventTriggeredMeasAllowed isFachPowerAdjustmentActivated isSib11MeasReportingAllowed sib11MeasReportingUsHoConfId sib11MeasReportingUsHoConfRef Modified Parameters: Parameter Name blindHoGsmNeighbourTargetCgi range cacConfId range hoConfId range incomingLinksRef dataType range maxCellRadius initialValue 16 measurementConfId range powerConfId range powerCtrlConfId range powerPartId range RNC RadioAccessService RadioAccessService DedicatedConf DedicatedConf PowerPartConfClass PowerPartConfClass
Modified Attribute
Old Value
New Value
RNC GSMCell
GSMNeighbour
GSMNeighbour GSMCell
RNC RadioAccessService RadioAccessService DedicatedConf DedicatedConf CacConfClass CacConfClass RNC RadioAccessService RadioAccessService DedicatedConf DedicatedConf HoConfClass HoConfClass Variable[64] ServiceLink List of
Variable[64] List of Not Applicable
RNC NodeB FDDCell UMTSFddNeighbouringCell 1920
RNC RadioAccessService RadioAccessService DedicatedConf DedicatedConf MeasurementConfClass MeasurementConfClass RNC RadioAccessService RadioAccessService DedicatedConf DedicatedConf PowerConfClass PowerConfClass RNC RadioAccessService RadioAccessService DedicatedConf DedicatedConf PowerCtrlConfClass PowerCtrlConfClass
Nortel Confidential
206
Parameter Name ucId
Modified Attribute visibility
Old Value
New Value
customer
manufacturer
3.1.41 GEOGRAPHICALSESSION (GEOGRAPHICALSESSION)

Modified Parent: RNC CallTrace GeographicalSession Modified Attribute Visibility Old Value customer New Value manufacturer
3.1.42 GSMCELL (GSMCELL)

Modified Parameters: Parameter Name GSMbandIndicator visibility cgi accessRight range readOnly writeAtCreation customer manufacturer Modified Attribute Old Value New Value
[0..2147483647].[0..65535].[3..3].[2..3] [0..65535].[0..65535].[3..3].[2..3]
3.1.43 GSMNEIGHBOURINGCELL (GSMNEIGHBOURINGCELL)

New Parameters: gsmCellLink Modified Parameters: Parameter Name Modified Attribute gsmCellCgi class dataType range rdnId visibility customer manufacturer 0 ServiceLink N.A Decimal.Decimal.Bcd.Bcd Old Value New Value
RNC GSMNeighbour GSMCell [0..65535].[0..65535].[3..3].[2..3]
Nortel Confidential
207
3.1.44 HOCONFCLASS (HOCONFCLASS)

Modified Parent: RNC RadioAccessService DedicatedConf HoConfClass Modified Attribute Cardinality Modified Parameters: Parameter Name rdnId range [0..9] [0..14] Modified Attribute Old Value New Value Old Value 1..5 New Value 1..15
3.1.45 INODE (INODE)

Modified Parameters: Parameter Name PPProvisionedSystemRelease visibility customer manufacturer Modified Attribute Old Value New Value
3.1.46 INODESOFTWARE (INODESOFTWARE)

Modified Parent: RNC RNCEquipment INode INodeSoftware Modified Attribute Visibility Old Value customer New Value manufacturer
3.1.47 INTERFREQHHOFDDCELL (INTERFREQHHOFDDCELL)

New Parameters: isRedirectionBasedOnEstablishmentCause isRedirectionForTrafficSegmentation
3.1.48 IRMONRLCONDITIONPARAMETERS (IRMONRLCONDITIONPARAMETERS)

Modified Parameters: Parameter Name dlRbSetConfId range RNC RadioAccessService DlRbSetConf DlRbSetConf Modified Attribute Old Value New Value
Nortel Confidential
208
3.1.49 IRMPREEMPTIONEXTENDEDPARAMS (IRMPREEMPTIONEXTENDEDPARAMS)

Modified Parent: RNC RadioAccessService IrmPreemption IrmPreemptionExtendedParams Modified Attribute Visibility Old Value manufacturer New Value manufacturer
3.1.50 IUCSTIMINGALIGNMENT (IUCSTIMINGALIGNMENT)

Modified Parent: RNC RadioAccessService DlRbSetConf IuCsTimingAlignment Modified Attribute Visibility Old Value manufacturer New Value manufacturer
3.1.51 LOCATIONSERVICES (LOCATIONSERVICES)

New Parameters: IsLocationReportUponChangeOfSaiAllowed
3.1.52 MEASUREMENTCONFCLASS (MEASUREMENTCONFCLASS)

Modified Parent: RNC RadioAccessService DedicatedConf MeasurementConfClass Modified Attribute Cardinality Modified Parameters: Parameter Name rdnId range [0..4] [0..14] Modified Attribute Old Value New Value Old Value 0..5 New Value 0..15
3.1.53 MEDIUMRBB2 (MEDIUMRBB2)

Modified Parameters: Parameter Name deltaThresholdTransCodePower unit domain step range intermediateRate initialValue N.A. 128 N.A. [0..255] N.A. dBm dBm 0.5 [0.0..56.0] Modified Attribute Old Value New Value
Nortel Confidential
209
3.1.54 MLPTOOLS (MLPTOOLS)

Modified Parent: RNC RadioAccessService MlpToOls Modified Attribute Visibility Old Value manufacturer New Value manufacturer
3.1.55 MMS (MMS)

Modified Parent: RNC RNCEquipment CNode OMU MMS Modified Attribute Visibility Old Value manufacturer New Value manufacturer
Modified Parent: RNC RNCEquipment CNode MMS Modified Attribute Visibility Old Value manufacturer New Value manufacturer
3.1.56 MTPSIGNPOINT (MTPSIGNPOINT)

Modified Parent: RNC MtpSignPoint Modified Attribute Visibility Old Value customer New Value manufacturer
3.1.57 NBAPMEASUREMENT (NBAPMEASUREMENT)

Modified Parameters: Parameter Name commonMeasurementReportingPeriod initialValue r5NbapCommonMeasurementReportingPeriod range initialValue [10..60000] 60000 [10..3600000] 20000 60000 20000 Modified Attribute Old Value New Value
Nortel Confidential
210
3.1.58 NEIGHBOURINGRNC (NEIGHBOURINGRNC)

New Parameters: defaultIrmCellColour iurIfId sccpDestinationPointCode sccpNetworkIndicator Deleted Parameters: sccpRouteSetId sccpRouteSetRef Modified Parameters: Parameter Name cacConfClassId range hoConfClassId range measurementConfClassId range powerCtrlConfId range RNC RadioAccessService RadioAccessService DedicatedConf DedicatedConf PowerCtrlConfClass PowerCtrlConfClass RNC RadioAccessService RadioAccessService DedicatedConf DedicatedConf MeasurementConfClass MeasurementConfClass RNC RadioAccessService RadioAccessService DedicatedConf HoConfClass DedicatedConf HoConfClass RNC RadioAccessService RadioAccessService DedicatedConf CacConfClass DedicatedConf CacConfClass Modified Attribute Old Value New Value
3.1.59 NODEB (NODEB)

New Parameters: iubIfId Deleted Parameters: iuxIfId Modified Parameters: Parameter Name nodeBConfClassId range provisionedSystemRelease visibility customer manufacturer RadioAccessService RNC RadioAccessService DedicatedConf DedicatedConf NodeBConfClass NodeBConfClass Modified Attribute Old Value New Value
Nortel Confidential
211
3.1.60 NODEBCONFCLASS (NODEBCONFCLASS)

Modified Parent: RNC RadioAccessService DedicatedConf NodeBConfClass Modified Attribute Cardinality Modified Parameters: Parameter Name rdnId range [0..4] [0..14] Modified Attribute Old Value New Value Old Value 1..5 New Value 1..15
3.1.61 NODEBSAALUNIPARAMS (NODEBSAALUNIPARAMS)

Modified Parent: RNC NodeB NodeBSaalUniParams Modified Attribute Visibility Old Value manufacturer New Value customer
3.1.62 OBJECTTRACE (OBJECTTRACE)

Modified Parent: RNC ObjectTrace Modified Attribute Visibility Old Value customer New Value manufacturer
Modified Parameters: Parameter Name rdnId range [1..1] [0..0] Modified Attribute Old Value New Value
3.1.63 OMU (OMU)

Modified Parent: RNC RNCEquipment CNode OMU Modified Attribute Visibility Old Value manufacturer New Value manufacturer
3.1.64 PCH (PCH)

Deleted Parameters: r5NrPagingIndPerFrame
Nortel Confidential
212
3.1.65 PERFSCANNER (PERFSCANNER)

Modified Parent: RNC PerfScanner Modified Attribute Visibility Old Value customer New Value manufacturer
3.1.66 POWERBALANCINGADJUSTMENTPARAMETERS (POWERBALANCINGADJUSTMENTPARAMETERS)

Modified Parameters: Parameter Name adjustmentPeriod initialValue adjustmentRatio initialValue maxAdjustmentStep initialValue 5 3 80 60 2 1 Modified Attribute Old Value New Value
3.1.67 POWERCONFCLASS (POWERCONFCLASS)

Modified Parent: RNC RadioAccessService DedicatedConf PowerConfClass Modified Attribute Cardinality Modified Parameters: Parameter Name dlAlgoSelector class sibMaxAllowedUlTxPowerOnRach class rdnId range [0..4] [0..14] 0 3 0 3 Modified Attribute Old Value New Value Old Value 1..5 New Value 1..15
Nortel Confidential
213
3.1.68 POWERCTRLCONFCLASS (POWERCTRLCONFCLASS)

Modified Parent: RNC RadioAccessService DedicatedConf PowerCtrlConfClass Modified Attribute Cardinality Modified Parameters: Parameter Name rdnId range [0..4] [0..14] Modified Attribute Old Value New Value Old Value 1..5 New Value 1..15
3.1.69 POWERPARTCONFCLASS (POWERPARTCONFCLASS)

Modified Parent: RNC RadioAccessService DedicatedConf PowerPartConfClass Modified Attribute Cardinality Modified Parameters: Parameter Name rdnId range [0..4] [0..14] Modified Attribute Old Value New Value Old Value 1..5 New Value 1..15
3.1.70 PSCORENETWORKACCESS (PSCORENETWORKACCESS)

New Parameters: sccpDestinationPointCode sccpNetworkIndicator Deleted Parameters: routeSetId routeSetRef
Nortel Confidential
214
3.1.71 RADIOACCESSSERVICE (RADIOACCESSSERVICE)

New Parameters: callsEligibleFor3Gto2GVoiceCallRedirectOnRabEstabFail irmSchedDowngradeTxcpMaxBitRate is3Gto2GVoiceCallRedirectOnRabEstabFailAllowed isDetectedSetCellsAllowed isDlCemLoadCalculationEnabled isDlIubTransportLoadColourCalculationEnabled isDlRbRateAdaptationAllowed isHsdpaAllowed isIrmSchedDowngradeTxcpAllowed isNodebLoadComputingAtRncAllowed isOvsfCodeReservationForCacOnShoAllowed isShoCacOnNodebLoadAtRncAllowed isUlRbRateAdaptationAllowed rbRateAdaptationPingPongTimer rlRestoreTimer rlRestoreTimerAfterRlFailure shoAfterBlockingPhaseEnable shoRlRestoreTimer Deleted Parameters: isEventTriggeredMeasAllowed Modified Parameters: Parameter Name filteringActivationFlag initialValue isSupportOfExtendedRbAllowedOnDrnc initialValue locUpdatePeriod initialValue 0 20 false true false true Modified Attribute Old Value New Value
3.1.72 RLCCONFCLASS (RLCCONFCLASS)

Nortel Confidential
215
3.1.73 RLCONDITION (RLCONDITION)

3.1.74 RNC (RNC)

New Parameters: clusterId pmClusterId Modified Parameters: Parameter Name accessRestrictionList dataType range provisionedSystemRelease visibility customer manufacturer Variable[2] ServiceLink Operator List of Variable[1] AsciiString Not Applicable List of Modified Attribute Old Value New Value
3.1.75 RNCMIB (RNCMIB)

Modified Parent: RNC RncMIB Modified Attribute Visibility Old Value customer New Value manufacturer
3.1.76 RRCMEASUREMENT (RRCMEASUREMENT)

Deleted Parameters: sib11IntraFreqMeasurementFilterCoeffOnRACH sib11IntraFreqMeasurementNbrOfCellOnRACH Modified Parameters: Parameter Name rrcIntraFreqMeasurementDropPrimaryRlDelta visibility manufacturer customer Modified Attribute Old Value New Value
Nortel Confidential
216
3.1.77 SCCPCH (SCCPCH)

Modified Parameters: Parameter Name sccpchClassId range initialValue RNC SccpchClass 0 RadioAccessService RadioAccessService SccpchClass N.A. Modified Attribute Old Value New Value
3.1.78 SERVICEINIT (SERVICEINIT)

New Parameters: isSrlrDeltaCfnOptimized srlrDelayMargin
3.1.79 SHOLINKADDITIONPARAMS (SHOLINKADDITIONPARAMS)

Modified Parameters: Parameter Name shoLinkAdditionCpichEcNoThreshold initialValue 0 -11.0 Modified Attribute Old Value New Value
3.1.80 SHOLINKDELETIONPARAMS (SHOLINKDELETIONPARAMS)

Modified Parameters: Parameter Name shoLinkDeletionCpichEcNoThreshold initialValue -24 -17.0 Modified Attribute Old Value New Value
3.1.81 SIGNALLEDGAINFACTORS (SIGNALLEDGAINFACTORS)

Modified Parameters: Parameter Name refTfcId range [0..3] [0..30] Modified Attribute Old Value New Value
Nortel Confidential
217
3.1.82 SOFTHOCONF (SOFTHOCONF)

Modified Parameters: Parameter Name legAdditionDelta initialValue legDroppingDelta initialValue shoLinkAdditionAbsoluteThresholdEnable initialValue shoLinkDeletionAbsoluteThresholdEnable initialValue false true false true 6 11 4 3 Modified Attribute Old Value New Value
3.1.83 TMU (TMU)

Modified Parent: RNC RNCEquipment CNode TMU Modified Attribute Visibility Old Value manufacturer New Value manufacturer
3.1.84 UETIMERCSTCONNECTEDMODE (UETIMERCSTCONNECTEDMODE)

Modified Parameters: Parameter Name n313 initialValue t313 initialValue t314 visibility t315 visibility manufacturer customer manufacturer customer 3 6 n313_4 n313_10 Modified Attribute Old Value New Value
3.1.85 ULOUTERLOOPPOWERCTRL (ULOUTERLOOPPOWERCTRL)

New Parameters: primaryReferenceUlRbSetConfId primaryReferenceUlRbSetConfRef Deleted Parameters: ulRbSetConfId ulRbSetConfRef ulUpSirStep
Nortel Confidential
218
3.1.86 ULRBSETCONF (ULRBSETCONF)

New Parameters: isThisRbRateAdaptationUlRbSetTargetAllowed isUlRbRateAdaptationAllowedForThisUlRbSetConf ulRbRateAdaptationDownsizeThreshold ulRbRateAdaptationUpsizeThreshold userLabel Modified Parameters: Parameter Name endPoint initialValue isAlwaysOnAllowed initialValue iuCsTransportQosId initialValue rlcConfClassId range rncWs initialValue rdnId visibility customer manufacturer N.A. 3 RNC RadioAccessService RlcConfClass RlcConfClass 0 N.A. disabled N.A. N.A. 5 Modified Attribute Old Value New Value
3.1.87 ULRLCACKMODE (ULRLCACKMODE)

Modified Parameters: Parameter Name lastTransPuPoll initialValue misPuIndic initialValue nbrOfSduBetweenPolling initialValue pollingTimer initialValue prohibitedPollingTimer initialValue prohibitedStatusTimer initialValue 10 N.A. 200 N.A. 30 N.A. N.A. 1 N.A. true N.A. true Modified Attribute Old Value New Value
Nortel Confidential
219
3.1.88 ULRLCTMODE (ULRLCTMODE)

Modified Parameters: Parameter Name segmentationInd initialValue N.A. false Modified Attribute Old Value New Value
3.1.89 ULRLCUMODE (ULRLCUMODE)

Modified Parameters: Parameter Name rlcDiscard initialValue N.A. timerDiscard100ms Modified Attribute Old Value New Value
3.1.90 ULUSERSERVICE (ULUSERSERVICE)

Modified Parent: RNC RadioAccessService UlUserService Modified Attribute Cardinality Old Value 1..25 New Value 1..35
New Parameters: isUlRbRateAdaptationAllowedForThisUlUserService userLabel Modified Parameters: Parameter Name isAlwaysOnAllowed initialValue rdnId visibility range customer [0..24] manufacturer [0..34] false N.A. Modified Attribute Old Value New Value
Nortel Confidential
220
3.1.91 ULUSPOWERCONF (ULUSPOWERCONF)

Modified Parent: RNC RadioAccessService DedicatedConf PowerConfClass UlUsPowerConf Modified Attribute Cardinality New Parameters: userLabel Modified Parameters: Parameter Name initialUlSirTarget initialValue rdnId visibility range customer [0..24] manufacturer [0..34] 7 N.A. Modified Attribute Old Value New Value Old Value 1..25 New Value 1..35
3.1.92 UMTSFDDNEIGHBOURINGCELL (UMTSFDDNEIGHBOURINGCELL)

Modified Parameters: Parameter Name ucId accessRight readOnly writeAtCreation Modified Attribute Old Value New Value
3.1.93 USERSERVICES (USERSERVICES)

New Parameters: userLabel Modified Parameters: Parameter Name dlUserServiceId range rrcEstablishmentCause visibility ulUserServiceId range rdnId visibility customer manufacturer RNC RadioAccessService UlUserService UlUserService customer manufacturer RNC RadioAccessService DlUserService DlUserService Modified Attribute Old Value New Value
Nortel Confidential
221
3.1.94 USHOCONF (USHOCONF)

Modified Parent: RNC RadioAccessService DedicatedConf HoConfClass UsHoConf Modified Attribute Cardinality New Parameters: fastAlarmHhoStrategy userLabel Deleted Parameters: shoAlgorithmExtendedParams Modified Parameters: Parameter Name rdnId visibility range customer [0..29] manufacturer [0..39] Modified Attribute Old Value New Value Old Value 1..30 New Value 1..40
Nortel Confidential
222
3.2.
ANODE MODIFIED PARAMETERS
3.2.1 ATMINTERFACE (ATMIF)

Modified Parameters: Parameter Name ctdCalculation range off, on off, version1on, version2on Modified Attribute Old Value New Value
3.2.2 ATMCONSTANTBITRATE (CBR)

Modified Parameters: Parameter Name txQueueLimit range minPerVcQueueLimit range [5..512000] [5..1011840] { [5..512000],autoConfigure } { [5..1011840],autoConfigure } Modified Attribute Old Value New Value
3.2.3 ATMNONREALTIMEVARIABLEBITRATE (NRTVBR)

3.2.4 ATMREALTIMEVARIABLEBITRATE (RTVBR)

Nortel Confidential
223
3.2.5 ATMUNSPECIFIEDBITRATE (UBR)

3.2.6 ATMTRAFFICMANAGEMENTPROV(TM)
Modified Parameters: Parameter Name txQueueLimit range { [5..512000],sameAsCa } { [5..1011840],sameAsCa } Modified Attribute Old Value New Value
3.2.7 INWATMCONNECTION (AC)

Deleted Parameters: ipDscp
3.2.8 APMVC4 (VC4)

New Parameters: applicationFramerName
3.2.9 SHELF (SHELF)

New Parameters: repeatFanAlarm
Nortel Confidential
224
3.2.10 CARD (CARD)

Modified Parameters: Parameter Modified Name Attribute cardType CP, V11, V35, DS1, DS1V, DS3, E1, E1V, E3, none, 1pFddiMultiMode, 4pTokenRing, 6pEth10BaseT, DS1C, E1C, 3pE3Atm, 3pDS3Atm, 3pOC3MmAtm, 3pOC3SmAtm, 3pE1Atm, 3pDS1Atm, J2MV, 4pEthAui, 1pFddiSingleMode, 1pDS1V, 1pE1V, 2pJ6MAtm, HSSI, 8pDS1, CFP1, DEV1, CFP2, DEV2, 4pDS1Aal1, 4pE1Aal1, 1pDS3C, IlsForwarder, 8pDS1Atm, 8pE1Atm, 1pE1Mvp, 1pDS1Mvp, 1pTTC2mMvp, 1pDS3cAal, 2pDS3cAal, 12mVspAal, 2pEth100BaseT, 2pOC3MmAtm2, 2pOC3SmAtm2, 3pDS3Atm2, 3pE3Atm2, CPeD, CPeE, 4pOC3SmIrAtm, 4pOC3MmAtm, 12pDS3Atm, 12pE3Atm, 1pOC12SmLrAtm, 1pE1Mvpe, 1pDS1Mvpe, 1pTTC2mMvpe, 32pDS1Msa, 32pDS1MsaMt, 32pDS1MsaMtp, 32pDS1MsaSt, 32pDS1MsaStp, 32pE1Aal, 1pOC48SmSrAtm, 4pDS3Ch, 4pDS3ChAtm, 1pSTM1ChSmIr, 1pSTM1ChSmIrAtm, 4pOC12SmIrAtm, 4pOC12SmLrAtm, 12mPcusp, 32pE1Msa, 32pE1MsaMt, 32pE1MsaMtp, 32pE1MsaSt, 32pE1MsaStp, 1pOC48ChSmIrAtm, 16pOC3SmIrAtm, 1pOC48SmIrAtm, 4pDS3ChAal1, Vsp2, VpnAccelerator, 24pBCNW, 6mPktServSP, 2pGPDsk, WPDS, 11pMSW, 1pOC48SmSrPos, 1pOC48SmIrPos, 2mPktServSP, 1pOC48Pos, 4pOC12Pos, 16pOC3PosAtm, 4pDS1Mvpe, 4pE1Mvpe, 4pOC3ChSmIr, 1pOC12SmSrPos, 1pOC12SmIrPos, 4pOC3SmSrPos, 4pOC3SmIrPos, 2pSTM1eAtm, VpnXc, 2pGeMmSrVsp3, 4pGe, 2pSTM1eCh, 2pOC3ChSmIrVsp3, Vsp2W, 34pGeLxTdmVsp, 3pGeLxOC3SmIrVsp, 6mAppServ, 2pVS, 2pOC3ChSmIrVsp4 CP, V11, V35, DS1, DS1V, DS3, E1, E1V, E3, none, 1pFddiMultiMode, 4pTokenRing, 6pEth10BaseT, DS1C, E1C, 3pE3Atm, 3pDS3Atm, 3pOC3MmAtm, 3pOC3SmAtm, 3pE1Atm, 3pDS1Atm, J2MV, 4pEthAui, 1pFddiSingleMode, 1pDS1V, 1pE1V, 2pJ6MAtm, HSSI, 8pDS1, CFP1, DEV1, CFP2, DEV2, 4pDS1Aal1, 4pE1Aal1, 1pDS3C, IlsForwarder, 8pDS1Atm, 8pE1Atm, 1pE1Mvp, 1pDS1Mvp, 1pTTC2mMvp, 1pDS3cAal, 2pDS3cAal, 12mVspAal, 2pEth100BaseT, 2pOC3MmAtm2, 2pOC3SmAtm2, 3pDS3Atm2, 3pE3Atm2, CPeD, CPeE, 4pOC3SmIrAtm, 4pOC3MmAtm, 12pDS3Atm, 12pE3Atm, 1pOC12SmLrAtm, 1pE1Mvpe, 1pDS1Mvpe, 1pTTC2mMvpe, 32pDS1Msa, 32pDS1MsaMt, 32pDS1MsaMtp, 32pDS1MsaSt, 32pDS1MsaStp, 32pE1Aal, 1pOC48SmSrAtm, 4pDS3Ch, 4pDS3ChAtm, 1pSTM1ChSmIr, 1pSTM1ChSmIrAtm, 4pOC12SmIrAtm, 4pOC12SmLrAtm, 12mPcusp, 32pE1Msa, 32pE1MsaMt, 32pE1MsaMtp, 32pE1MsaSt, 32pE1MsaStp, 1pOC48ChSmIrAtm, 16pOC3SmIrAtm, 1pOC48SmIrAtm, 4pDS3ChAal1, Vsp2, VpnAccelerator, 24pBCNW, 6mPktServSP, 2pGPDsk, WPDS, 11pMSW, 1pOC48SmSrPos, 1pOC48SmIrPos, 2mPktServSP, 1pOC48Pos, 4pOC12Pos, 16pOC3PosAtm, 4pDS1Mvpe, 4pE1Mvpe, 4pOC3ChSmIr, 1pOC12SmSrPos, 1pOC12SmIrPos, 4pOC3SmSrPos, 4pOC3SmIrPos, 2pSTM1eAtm, VpnXc, 2pGeMmSrVsp3, 4pGe, 2pSTM1eCh, 2pOC3ChSmIrVsp3, Vsp2W, 34pGeLxTdmVsp, 3pGeLxOC3SmIrVsp, 6mAppServ, 2pVS, 2pOC3ChSmIrVsp4, 8pEth100BaseT, 4pMRPosAtm, 4pEth100BaseT Old Value New Value
range
Nortel Confidential
225
3.2.11 INWIP (IP)

New Parameters: lcmCacheMissTrace preConfigFwdPath
3.2.12 INWIPSTATIC (STATIC)

New Parameters: maxEcmpNextHops
3.2.13 INWIPSTATICROUTEENTRY (ROUTE)

New Parameters: protected protectedFailureBehavior
3.2.14 INWIPPORT (IPPORT)

Nortel Confidential
226
3.3.
INODE MODIFIED PARAMETERS
3.3.1 PSSS7ROUTE (RO)

Modified Parameters: Parameter Name priority range [1..2] [1..255] Modified Attribute Old Value New Value
3.3.2 SIGNALLINGBEARER (SIG)

New Parents: EM Iub Sig Deleted Parents: EM IuxIf Sig
3.3.3 NAILEDUPACCESSPOINT (NAP)

New Parents: EM Iub Sig SaalUni Nap Deleted Parents: EM IuxIf Sig SaalUni Nap
3.3.4 SAALUNI (SAALUNI)

New Parents: EM Iub Sig SaalUni Deleted Parents: EM IuxIf Sig SaalUni
3.3.5 INWATMCONNECTION (AC)

Nortel Confidential
227
3.3.6 INWOSPFAREAENTRY (AREA)

Modified Parameters: Parameter Name authType range none, simplePassword none, simplePassword, md5 Modified Attribute Old Value New Value
3.3.7 ATMINTERFACE (ATMIF)

Modified Parameters: Parameter Name ctdCalculation range off, on off, version1on, version2on Modified Attribute Old Value New Value
Nortel Confidential
228
3.3.8 CARD (CARD)

Modified Parameters: Parameter Modified Name Attribute cardType CP, V11, V35, DS1, DS1V, DS3, E1, E1V, E3, none, 1pFddiMultiMode, 4pTokenRing, 6pEth10BaseT, DS1C, E1C, 3pE3Atm, 3pDS3Atm, 3pOC3MmAtm, 3pOC3SmAtm, 3pE1Atm, 3pDS1Atm, J2MV, 4pEthAui, 1pFddiSingleMode, 1pDS1V, 1pE1V, 2pJ6MAtm, HSSI, 8pDS1, CFP1, DEV1, CFP2, DEV2, 4pDS1Aal1, 4pE1Aal1, 1pDS3C, IlsForwarder, 8pDS1Atm, 8pE1Atm, 1pE1Mvp, 1pDS1Mvp, 1pTTC2mMvp, 1pDS3cAal, 2pDS3cAal, 12mVspAal, 2pEth100BaseT, 2pOC3MmAtm2, 2pOC3SmAtm2, 3pDS3Atm2, 3pE3Atm2, CPeD, CPeE, 4pOC3SmIrAtm, 4pOC3MmAtm, 12pDS3Atm, 12pE3Atm, 1pOC12SmLrAtm, 1pE1Mvpe, 1pDS1Mvpe, 1pTTC2mMvpe, 32pDS1Msa, 32pDS1MsaMt, 32pDS1MsaMtp, 32pDS1MsaSt, 32pDS1MsaStp, 32pE1Aal, 1pOC48SmSrAtm, 4pDS3Ch, 4pDS3ChAtm, 1pSTM1ChSmIr, 1pSTM1ChSmIrAtm, 4pOC12SmIrAtm, 4pOC12SmLrAtm, 12mPcusp, 32pE1Msa, 32pE1MsaMt, 32pE1MsaMtp, 32pE1MsaSt, 32pE1MsaStp, 1pOC48ChSmIrAtm, 16pOC3SmIrAtm, 1pOC48SmIrAtm, 4pDS3ChAal1, Vsp2, VpnAccelerator, 24pBCNW, 6mPktServSP, 2pGPDsk, WPDS, 11pMSW, 1pOC48SmSrPos, 1pOC48SmIrPos, 2mPktServSP, 1pOC48Pos, 4pOC12Pos, 16pOC3PosAtm, 4pDS1Mvpe, 4pE1Mvpe, 4pOC3ChSmIr, 1pOC12SmSrPos, 1pOC12SmIrPos, 4pOC3SmSrPos, 4pOC3SmIrPos, 2pSTM1eAtm, VpnXc, 2pGeMmSrVsp3, 4pGe, 2pSTM1eCh, 2pOC3ChSmIrVsp3, Vsp2W, 34pGeLxTdmVsp, 3pGeLxOC3SmIrVsp, 6mAppServ, 2pVS, 2pOC3ChSmIrVsp4 CP, V11, V35, DS1, DS1V, DS3, E1, E1V, E3, none, 1pFddiMultiMode, 4pTokenRing, 6pEth10BaseT, DS1C, E1C, 3pE3Atm, 3pDS3Atm, 3pOC3MmAtm, 3pOC3SmAtm, 3pE1Atm, 3pDS1Atm, J2MV, 4pEthAui, 1pFddiSingleMode, 1pDS1V, 1pE1V, 2pJ6MAtm, HSSI, 8pDS1, CFP1, DEV1, CFP2, DEV2, 4pDS1Aal1, 4pE1Aal1, 1pDS3C, IlsForwarder, 8pDS1Atm, 8pE1Atm, 1pE1Mvp, 1pDS1Mvp, 1pTTC2mMvp, 1pDS3cAal, 2pDS3cAal, 12mVspAal, 2pEth100BaseT, 2pOC3MmAtm2, 2pOC3SmAtm2, 3pDS3Atm2, 3pE3Atm2, CPeD, CPeE, 4pOC3SmIrAtm, 4pOC3MmAtm, 12pDS3Atm, 12pE3Atm, 1pOC12SmLrAtm, 1pE1Mvpe, 1pDS1Mvpe, 1pTTC2mMvpe, 32pDS1Msa, 32pDS1MsaMt, 32pDS1MsaMtp, 32pDS1MsaSt, 32pDS1MsaStp, 32pE1Aal, 1pOC48SmSrAtm, 4pDS3Ch, 4pDS3ChAtm, 1pSTM1ChSmIr, 1pSTM1ChSmIrAtm, 4pOC12SmIrAtm, 4pOC12SmLrAtm, 12mPcusp, 32pE1Msa, 32pE1MsaMt, 32pE1MsaMtp, 32pE1MsaSt, 32pE1MsaStp, 1pOC48ChSmIrAtm, 16pOC3SmIrAtm, 1pOC48SmIrAtm, 4pDS3ChAal1, Vsp2, VpnAccelerator, 24pBCNW, 6mPktServSP, 2pGPDsk, WPDS, 11pMSW, 1pOC48SmSrPos, 1pOC48SmIrPos, 2mPktServSP, 1pOC48Pos, 4pOC12Pos, 16pOC3PosAtm, 4pDS1Mvpe, 4pE1Mvpe, 4pOC3ChSmIr, 1pOC12SmSrPos, 1pOC12SmIrPos, 4pOC3SmSrPos, 4pOC3SmIrPos, 2pSTM1eAtm, VpnXc, 2pGeMmSrVsp3, 4pGe, 2pSTM1eCh, 2pOC3ChSmIrVsp3, Vsp2W, 34pGeLxTdmVsp, 3pGeLxOC3SmIrVsp, 6mAppServ, 2pVS, 2pOC3ChSmIrVsp4, 8pEth100BaseT, 4pMRPosAtm, 4pEth100BaseT Old Value New Value
range
Nortel Confidential
229
3.3.9 ATMCONSTANTBITRATE (CBR)

3.3.10 INWLOCALMEDIAINTERFACE (IF)

Modified Parent: EM LocalMedia If Modified Attribute Cardinality Modified Parameters: Parameter Name trafficType range rdnId range [0..4] [0..7] rnc, cpds, internalTraffic, oamTraffic cpdsCoreNetwork, rnc, cpds, cpdsCoreNetwork, locationServices, internalTraffic, locationServices, oamTraffic, reserved1, reserved2 Modified Attribute Old Value New Value Old Value 0..5 New Value 0..8
3.3.11 INWIP (IP)

New Parameters: lcmCacheMissTrace preConfigFwdPath
3.3.12 INWIPPORT (IPPORT)

3.3.13 LINEAUTOMATICPROTECTIONSWITCHING (LAPS)

New Parameters: sendLineAisDuringMigration
Nortel Confidential
230
3.3.14 INWIPLOGICALIF (LOGICALIF)

New Parameters: linkToPimSmCandidateRp linkToPimSmCandidateBsr
3.3.15 ATMNONREALTIMEVARIABLEBITRATE (NRTVBR)

3.3.16 INWIPOSPF (OSPF)

New Parameters: attachAsTag Deleted Parameters: extLsdbLimit
3.3.17 INWOSPFIF (OSPFIF)

New Parameters: authType
3.3.18 ATMCONNECTIONMAPPINGOVERRIDE (OV)

Modified Parameters: Parameter Name numVccsForVpiZero dataType range initialValue Decimal [0..16384] 768 MixedDecimal { [0..16384],autoConfigure } autoConfigure Modified Attribute Old Value New Value
Nortel Confidential
231
3.3.19 IUXIFPATH (PATH)

New Parents: EM Aal2If Path Deleted Parents: EM IuxIf Path
3.3.20 INWIPSTATICROUTEENTRY (ROUTE)

New Parameters: protected protectedFailureBehavior
3.3.21 ATMREALTIMEVARIABLEBITRATE (RTVBR)

3.3.22 SHELF (SHELF)

New Parameters: repeatFanAlarm
3.3.23 INWIPSTATIC (STATIC)

New Parameters: maxEcmpNextHops
3.3.24 ATMTRAFFICMANAGEMENTPROV (TM)

Modified Parameters: Parameter Name txQueueLimit range { [5..512000],sameAsCa } { [5..1011840],sameAsCa } Modified Attribute Old Value New Value
Nortel Confidential
232
3.3.25 INWOSPFIFTYPEOFSERVICE (TOS)

Modified Parameters: Parameter Name tosMetric initialValue N.A. 1 Modified Attribute Old Value New Value
3.3.26 ATMUNSPECIFIEDBITRATE (UBR)

3.3.27 INWOSPFVIRTIFENTRY (VIRTIF)

New Parameters: authType
3.3.28 PSSS7SERVICEINDICATOR (SERVIND)

Modified Parent: EM Ss7 Mtp3 ServInd Modified Attribute Cardinality Modified Parameters: Parameter Name rdnId range 3 3, 12 Modified Attribute Old Value New Value Old Value 0..1 New Value 0..2
Nortel Confidential
233
3.4.
BTS MODIFIED PARAMETERS
3.4.1 AAL2BEARER (AAL2BEARER)

Modified Parameters: Parameter Name vccId range BTSEquipment VCC VCC Modified Attribute Old Value New Value
3.4.2 ANTENNAACCESS (ANTENNAACCESS)

Modified Parameters: Parameter Name externalUlDelay range [0..2080] [0.000..2080.000] Modified Attribute Old Value New Value
3.4.3 BOARD (BOARD)

Modified Parent: BTSEquipment Board Modified Attribute Visibility Old Value manufacturer New Value manufacturer
3.4.4 BTSCELL (BTSCELL)

New Parameters: AntennaConnectionListRef hsdpaResourceActivation Deleted Parameters: hsdpaResourceId Modified Parameters: Parameter Name antennaConnectionList range BTSEquipment AntennaAccess AntennaAccess Modified Attribute Old Value New Value
Nortel Confidential
234
3.4.5 BTSEQUIPMENT (BTSEQUIPMENT)

New Parameters: clusterId hsdpaMaxNumberUser hsdpaMaxNumberUserPerNodeB hsdpaResourceMaxCapacity pmClusterId Modified Parameters: Parameter Name accessRestrictionList dataType range bbVersion class maxDifferentialDelay range nbPcm initialValue provisionedSystemRelease visibility rxDemodulation dataType range initialValue timerCellImpactNoCcp class timerNodeBCPCellValidity visibility class neId range [0..64] [0..25] manufacturer 0 customer 3 0 3 Enumeration rxDemodulationMl, rxDemodulationMap rxDemodulationMl Decimal [0..2147483647] 0 customer manufacturer 1 N.A. [0..2147483647] [1..25] 0 3 Variable[2] List of ServiceLink Operator Variable[1] AsciiString Not Applicable List of Modified Attribute Old Value New Value
Nortel Confidential
235
3.4.6 BTSEQUIPMENTMIB (BTSEQUIPMENTMIB)

Modified Parent: BTSEquipment BTSEquipmentMIB Modified Attribute Visibility Old Value manufacturer New Value manufacturer
3.4.7 BTSEQUIPMENTSOFTWARE (BTSEQUIPMENTSOFTWARE)

Modified Parent: BTSEquipment BTSEquipmentSoftware Modified Attribute Visibility Old Value customer New Value manufacturer
3.4.8 CCP (CCP)

3.4.9 COOLINGSYSTEM (COOLINGSYSTEM)

Modified Parent: BTSEquipment CoolingSystem Modified Attribute Visibility Old Value manufacturer New Value manufacturer
3.4.10 COUNTERFAMILY (COUNTERFAMILY)

Modified Parameters: Parameter Name rdnId visibility customer manufacturer Modified Attribute Old Value New Value
Nortel Confidential
236
3.4.11 DEVICETABLE (DEVICETABLE)

Modified Parameters: Parameter Name dnsServer dataType range managerAddress dataType range AsciiString Not Applicable Ip4Address [0..255].[0..255].[0..255].[0..255] AsciiString Not Applicable Ip4Address [0..255].[0..255].[0..255].[0..255] Modified Attribute Old Value New Value
3.4.12 IMAGROUP (IMAGROUP)

Modified Parameters: Parameter Name imaPcmList range BTSEquipment PCM PCM Modified Attribute Old Value New Value
3.4.13 NODEBCP (NODEBCP)

3.4.14 OMCBCONNECTION (OMCBCONNECTION)

Modified Parent: BTSEquipment OMCBConnection Modified Attribute Visibility Modified Parameters: Parameter Name omcbIpAddress visibility omcbTcpPort visibility manufacturer customer manufacturer customer Modified Attribute Old Value New Value Old Value manufacturer New Value customer
Nortel Confidential
237
3.4.15 PASSIVECOMPONENT (PASSIVECOMPONENT)

Modified Parent: BTSEquipment PassiveComponent Modified Attribute Cardinality Visibility Modified Parameters: Parameter Name rdnId range [0..9] [0..14] Modified Attribute Old Value New Value Old Value 0..10 manufacturer New Value 0..15 manufacturer
3.4.16 POWERSYSTEM (POWERSYSTEM)

Modified Parent: BTSEquipment PowerSystem Modified Attribute Visibility Old Value manufacturer New Value manufacturer
3.4.17 ROUTECES (ROUTECES)

Modified Parent: BTSEquipment RouteCes Modified Attribute Cardinality New Parameters: rxCellDelayVariationTolerance Modified Parameters: Parameter Name Modified Attribute pcmId range pcmTimeSlotMask range vccId range vccRef range rdnId range [0..5] [0..7] BTSEquipment VCC, BTSEquipment VCC BTSEquipment VCC BTSEquipment VCC, BTSEquipment VCC VCC [0..32] [32..32] BTSEquipment PCM PCM Old Value New Value Old Value 0..6 New Value 0..8
Nortel Confidential
238
3.4.18 RTOBSSESSION (RTOBSSESSION)

Modified Parameters: Parameter Name familyState range BTSEquipment CounterFamily CounterFamily Modified Attribute Old Value New Value
3.4.19 SITELAN (SITELAN)

Modified Parameters: Parameter Name subNetworkAddress dataType range subNetworkMaskOfSiteLan dataType range AsciiString Not Applicable Ip4Address [0..255].[0..255].[0..255].[0..255] AsciiString Not Applicable Ip4Address [0..255].[0..255].[0..255].[0..255] Modified Attribute Old Value New Value
3.4.20 VCC (VCC)

Modified Parent: BTSEquipment VCC Modified Attribute Cardinality Modified Parameters: Parameter Name cdvTolerancePCR unit domain cdvToleranceSCR unit domain rdnId range [0..28] [0..30] s s s s Modified Attribute Old Value New Value Old Value 0..29 New Value 0..31
Nortel Confidential
239
3.5.
OAM MODIFIED PARAMETERS
3.5.1 EXTERNALALARMMAPPINGTABLE (EXTERNALALARMMAPPINGTABLE)

Modified Parent: ExternalAlarmMappingTable Modified Attribute Visibility Old Value manufacturer New Value manufacturer
3.5.2 EXTERNALALARMMAPPINGTABLEENTRY (EXTERNALALARMMAPPINGTABLEENTRY)

Modified Parent: ExternalAlarmMappingTable ExternalAlarmMappingTableEntry Modified Attribute Visibility Old Value manufacturer New Value manufacturer
3.5.3 SCOPE (SCOPE)

Modified Parent: TraceSession Scope Modified Attribute Visibility Old Value manufacturer New Value manufacturer
3.5.4 TRACEFILTER (TRACEFILTER)

Modified Parent: TraceFilter Modified Attribute Visibility Modified Parameters: Parameter Name mode visibility traceRecordList accessRight visibility writeAtCreation manufacturer readWrite customer manufacturer customer Modified Attribute Old Value New Value Old Value manufacturer New Value manufacturer
Nortel Confidential
240
3.5.5 TRACERECORD (TRACERECORD)

Modified Parent: TraceRecord Modified Attribute Visibility Old Value manufacturer New Value manufacturer
3.5.6 TRACESESSION (TRACESESSION)

Modified Parent: TraceSession Modified Attribute Visibility New Parameters: datafileUploadPeriod datafileUploadSize startTime Old Value manufacturer New Value manufacturer
3.5.7 TRACESESSIONTEMPLATE (TRACESESSIONTEMPLATE)

Modified Parent: TraceSessionTemplate Modified Attribute Visibility Modified Parameters: Parameter Name Modified Attribute duration accessRight traceFilterList accessRight visibility dataType type accessRight writeAtCreation readOnly writeAtCreation manufacturer Variable[5] List of ServiceLink readWrite customer Fixed[1..1] List of ServiceLink writeAtCreation readWrite Old Value New Value Old Value manufacturer New Value manufacturer
3.5.8 USEREQUIPMENTID (USEREQUIPMENTID)

Modified Parent: TraceSession UserEquipmentId Modified Attribute Visibility Old Value manufacturer New Value manufacturer
Nortel Confidential
241
3.5.9 PMCLUSTER (PMCLUSTER)

Modified Parent: PMCluster Modified Attribute OnLineCreation OnLineDeletion Visibility Old Value N.A. N.A. customer New Value NotAllowed NotAllowed customer
3.5.10 CLUSTER (CLUSTER)

Modified Parent: Cluster Modified Attribute OnLineCreation OnLineDeletion Visibility Old Value N.A. N.A. customer New Value NotAllowed NotAllowed customer
Nortel Confidential
242
3.6.
POC MODIFIED PARAMETERS
3.6.1 AAL1ACTIVEENDPOINT (AEP)

Modified Parameters: Parameter Name calledVpiVci presence required optional Modified Attribute Old Value New Value
3.6.2 ATMCELL (CELL)

Modified Parameters: Parameter Name scrambleCellPayload presence required optional Modified Attribute Old Value New Value
3.6.3 ATMPNNI (PNNI)

Modified Parameters: Parameter Name outgoingNcciIeFormat presence required optional Modified Attribute Old Value New Value
3.6.4 CASROOT (EM)

Modified Parameters: Parameter Name mdmFmGroup initialValue N.A. FMGROUP Modified Attribute Old Value New Value
3.6.5 DCSSPOOLER (SP)

Modified Parameters: Parameter Name spooling presence maximumNumberOfFiles presence required optional required optional Modified Attribute Old Value New Value
Nortel Confidential
243
3.6.6 E1 (E1)
New Parents: EM Lp Sdh Vc4 Vc12 E1 Modified Parameters: Parameter Name lineType presence crc4Mode presence required optional required optional Modified Attribute Old Value New Value
3.6.7 E1CHAN (CHAN)

Modified Parameters: Parameter Name timeslots presence optional required Modified Attribute Old Value New Value
3.6.8 INWHOSTENTRYCOS (HOST)

Modified Parameters: Parameter Name tunnelDestinationAddress presence required optional Modified Attribute Old Value New Value
3.6.9 INWIPLOGICALIF (LOGICALIF)

Modified Parameters: Parameter Name linkDestinationAddress presence required optional Modified Attribute Old Value New Value
3.6.10 PMSTC (TC)

Modified Parameters: Parameter Name replacementData presence required optional Modified Attribute Old Value New Value
Nortel Confidential
244
ANNEX C: NEW/DELETED/MODIFIED COUNTERS

This annex lists the new, deleted and modified counters between UA04.1 and U404.2, and OAM04.2 and OAM05.0.
1.
UA04.2/OAM05.0 NEW COUNTERS

This paragraph lists the new counters between UA04.1 and U404.2.
1.1.
RNC NEW COUNTERS

LackCidIub LackBwthIub INodeRefusal unused LackCid LackBwthIub INodeRefusal LackCidIub LackBwthIub INodeRefusal
VS.RadioLinkSetupUnsuccess - #2
VS.RadioLinkReconfigurationPrepareUnsuccess - #8
VS.RadioLinkFirstSetupFailure - #20
VS.RadioLinkSetupRequest - #21 VS.RadioLinkAdditionReq - #22 VS.RadioLinkReconfPrepReq - #23 VS.RadioLinkFirstSetupSuccess - #24 VS.RrcHoFromUtranCommand - #101 VS.RrcHoFromUtranCommandNeighbRnc- #102 VS.RrcHoFromUtranFailure - #103 VS.RrcHoFromUtranFailureNeighbRnc - #104 VS.3gto2gHoDetectionFromFddcell - #109 VS.3gto2gHoDetectionFromFddcellNeighbRnc - #110 VS.3gto2gOutHoSuccess - #134
VS.3g2gOutHoFailure - #135
BlindSpeechRedir NonBlindspeechRedir BlindSpeechRedir NonBlindspeechRedir BlindSpeechRedir NonBlindspeechRedir BlindSpeechRedir NonBlindspeechRedir BlindSpeechRedir NonBlindspeechRedir BlindSpeechRedir NonBlindspeechRedir RescueCs RescuePs ServiceCs BlindSpeechRedir NonBlindSpeechRedir RelocPrepOrCancel RelocComplFail
Nortel Confidential
245
VS.IntraRncOutInterFreqHoAttempt - #138
VS.IntraRncOutInterFreqHoFail - #139
VS.IntraRncIncInterFreqHoAttempt - #140
VS.IntraRncIncInterFreqHoFail - #141
RRC.FailConnEstab - #404
CsFailureRadioProc PsFailureRadioproc Unexpected Capacity Mobility WithMeas R5UeToHsdpa R5UeToNonHsdpa NonR5UeToNonHsdpa BlindNotEnoughResources BlindNodeBFail BlindRRC WithMeasNotEnoughRes WithMeasNodeBFail WithMeasRRC Capacity Mobility WithMeas R5UeToHsdpa R5UeToNonHsdpa NonR5UeToNonHsdpa BlindNotEnoughResources BlindNodeBFail BlindRRC WithMeasNotEnoughRes WithMeasNodeBFail WithMeasRRC 8 9 10
SHO.SuccRLAddUESide - #418 IRATHO.SuccOutCS - #505 Succ3G3GReloc RATHO.SuccOutPSUTRAN - #506 VS.IuRelocationRequestFailuresCs - #536 Succ3G3GReloc 3Gto3GRRCCtxt 2Gto3GRRCCtxt 3Gto3GIuCnxCtxt 2Gto3GIuCnxCtxt 3Gto3GRRCCtxt 3Gto3GIuCnxCtxt OtherCause DlRLCErrSRB UlRLCErrSRB DlRLCErrTRB UlRLCErrTRB DlRLCErrSRB UlRLCErrSRB DlRLCErrTRB
VS.IuRelocationRequestFailuresPs - #537 VS.IuReleaseRequestCs - #540
VS.IuReleaseRequestPs - #541
Nortel Confidential
246
VS.IuAbnormRelReqCs - #542
UlRLCErrTRB OamIntervention IuUserPlaneFailure UnspecifiedFailure RepeatedIntegrityCheckFailure UeGeneratedSignallingConnectionRelease RadioConnectionWithUeLost AbnormalConditionTimerRelocExpiry Other DlRLCErrSRB UlRLCErrSRB DlRLCErrTRB UlRLCErrTRB UserInactivity IuUserPlaneFailure OamIntervention UnspecifiedFailure RepeatedIntegrityCheckFailure UeGeneratedSignallingConnectionRelease RadioConnectionWithUeLost AbnormalConditionTimerRelocExpiry Other DlRLCErrSRB UlRLCErrSRB DlRLCErrTRB UlRLCErrTRB CsReqByRNC PsReqByRNC CsReqByCN PsReqByCN 3Gto3GCs 3Gto3GPs 3Gto2GCs 3Gto3GCs 3Gto3GPs 3Gto2GCs 3Gto3GRelocTimeout 3Gto3GAlreadyInProgr 3Gto3GFailTarget 3Gto3GUnableToEstab 3Gto3GOther 3Gto2GFailTarget 3Gto2GUnableToEstab 3Gto2GOther RabPsInter32D_384U RabPsBgnd32D_384U RabPsInter64D_384U RabPsBgnd64D_384U
VS.IuAbnormRelReqPs - #543
VS.IuSccpCnxSuccess - #548
VS.IuRelocationRequired - #549
VS.IuRelocationCommands - #550
VS.IuRelocationCmdFailuresCs - #551
VS.RabEstablishmentSuccessPerGrantedRabType - #623
Nortel Confidential
247
VS.RabEstablishmentRequestsPerRabType - #621
RabPsInter32D_384U RabPsBgnd32D_384U RabPsInter64D_384U RabPsBgnd64D_384U RabPsInter128D_384U RabPsBgnd128D_384U RabPsInter256D_384U RabPsBgnd256D_384U RabPsInter384D_384U RabPsBgnd384D_384U RabPsInterHsdpa_32U RabPsBgndHsdpa_32U RabPsInterHsdpa_64U RabPsBgndHsdpa_64U RabPsInterHsdpa_128U RabPsBgndHsdpa_128U RabPsInterHsdpa_384U RabPsBgndHsdpa_384U RabPsInter32D_384U RabPsBgnd32D_384U RabPsInter64D_384U RabPsBgnd64D_384U RabPsInter128D_384U RabPsBgnd128D_384U RabPsInter256D_384U RabPsBgnd256D_384U RabPsInter384D_384U RabPsBgnd384D_384U RabPsInterHsdpa_32U RabPsBgndHsdpa_32U RabPsInterHsdpa_64U RabPsBgndHsdpa_64U RabPsInterHsdpa_128U RabPsBgndHsdpa_128U RabPsInterHsdpa_384U RabPsBgndHsdpa_384U RabPsInter128D_384U RabPsBgnd128D_384U RabPsInter256D_384U RabPsBgnd256D_384U RabPsInter128D_384U.Cum RabPsInter128D_384U.NbEvt RabPsInter128D_384U.Min RabPsInter128D_384U.Max RabPsBgnd128D_384U.Avg RabPsBgnd128D_384U.Cum RabPsBgnd128D_384U.NbEvt RabPsBgnd128D_384U.Min RabPsBgnd128D_384U.Max RabPsInter256D_384U.Avg
VS.RabEstablishmentSuccessPerRequestedRabType #622
VS.NumberOfRabEstablished. - #627
Nortel Confidential
248
VS.RadioBearerEstablishmentUnsuccess - #631
VS.RabReleaseRequest - #624
VS.NumberOfRabEstablished - #627
RabPsInter256D_384U.Cum RabPsInter256D_384U.NbEvt RabPsInter256D_384U.Min RabPsInter256D_384U.Max RabPsBgnd256D_384U.Avg RabPsBgnd256D_384U.Cum RabPsBgnd256D_384U.NbEvt RabPsBgnd256D_384U.Min RabPsBgnd256D_384U.Max RabPsInter384D_384U.Avg RabPsInter384D_384U.Cum RabPsInter384D_384U.NbEvt RabPsInter384D_384U.Min RabPsInter384D_384U.Max RabPsBgnd384D_384U.Avg LackBwthIu LackCidIur LackBwthIur RabPsInter384D_384U RabPsBgnd384D_384U RabPsInterHsdpa_32U RabPsBgndHsdpa_32U RabPsInterHsdpa_64U RabPsBgndHsdpa_64U RabPsInterHsdpa_128U RabPsBgndHsdpa_128U RabPsInterHsdpa_384U RabPsBgndHsdpa_384U RabPsInter32D_384U RabPsBgnd32D_384U RabPsInter64D_384U RabPsBgnd64D_384U RabPsInter128D_384U RabPsBgnd128D_384U RabPsInter256D_384U RabPsBgnd256D_384U RabPsInter384D_384U RabPsBgnd384D_384U RabPsInterHsdpa_32U RabPsBgndHsdpa_32U RabPsInterHsdpa_64U RabPsBgndHsdpa_64U RabPsInterHsdpa_128U RabPsBgndHsdpa_128U RabPsInterHsdpa_384U RabPsBgndHsdpa_384U RabPsInter32D_384U.Avg RabPsInter32D_384U.Cum RabPsInter32D_384U.NbEvt RabPsInter32D_384U.Min
Nortel Confidential
249
RabPsInter32D_384U.Max RabPsBgnd32D_384U.Avg RabPsBgnd32D_384U.Cum RabPsBgnd32D_384U.NbEvt RabPsBgnd32D_384U.Min RabPsBgnd32D_384U.Max RabPsInter64D_384U.Avg RabPsInter64D_384U.Cum RabPsInter64D_384U.NbEvt RabPsInter64D_384U.Min RabPsInter64D_384U.Max RabPsBgnd64D_384U.Avg RabPsBgnd64D_384U.Cum RabPsBgnd64D_384U.NbEvt RabPsBgnd64D_384U.Min RabPsBgnd64D_384U.Max RabPsInter128D_384U.Avg RabPsBgnd384D_384U.Cum RabPsBgnd384D_384U.NbEvt RabPsBgnd384D_384U.Min RabPsBgnd384D_384U.Max RabPsInterHsdpa_32U.Avg RabPsInterHsdpa_32U.Cum RabPsInterHsdpa_32U.NbEvt RabPsInterHsdpa_32U.Min RabPsInterHsdpa_32U.Max RabPsBgndHsdpa_32U.Avg RabPsBgndHsdpa_32U.Cum RabPsBgndHsdpa_32U.NbEvt RabPsBgndHsdpa_32U.Min RabPsBgndHsdpa_32U.Max RabPsInterHsdpa_64U.Avg RabPsInterHsdpa_64U.Cum RabPsInterHsdpa_64U.NbEvt RabPsInterHsdpa_64U.Min RabPsInterHsdpa_64U.Max RabPsBgndHsdpa_64U.Avg RabPsBgndHsdpa_64U.Cum RabPsBgndHsdpa_64U.NbEvt RabPsBgndHsdpa_64U.Min RabPsBgndHsdpa_64U.Max RabPsInterHsdpa_128U.Avg RabPsInterHsdpa_128U.Cum RabPsInterHsdpa_128U.NbEvt RabPsInterHsdpa_128U.Min RabPsInterHsdpa_128U.Max RabPsBgndHsdpa_128U.Avg RabPsBgndHsdpa_128U.Cum RabPsBgndHsdpa_128U.NbEvt RabPsBgndHsdpa_128U.Min
Nortel Confidential
250
VS.RabNormalRelease - #629
VS.RadioBearerEstablishmentUnsuccess - #631
VS.RabAssignmentReleaseSuccess - #633 VS.CallEstablishmentDuration - #639
VS.RabAssignmentSetupUnsuccess - #632
RabPsBgndHsdpa_128U.Max RabPsInterHsdpa_384U.Avg RabPsInterHsdpa_384U.Cum RabPsInterHsdpa_384U.NbEvt RabPsInterHsdpa_384U.Min RabPsInterHsdpa_384U.Max RabPsBgndHsdpa_384U.Avg RabPsBgndHsdpa_384U.Cum RabPsBgndHsdpa_384U.NbEvt RabPsBgndHsdpa_384U.Min RabPsBgndHsdpa_384U.Max RabPsInter32D_384U RabPsBgnd32D_384U RabPsInter64D_384U RabPsBgnd64D_384U RabPsInter128D_384U RabPsBgnd128D_384U RabPsInter256D_384U RabPsBgnd256D_384U RabPsInter384D_384U RabPsBgnd384D_384U RabPsInterHsdpa_32U RabPsBgndHsdpa_32U RabPsInterHsdpa_64U RabPsBgndHsdpa_64U RabPsInterHsdpa_128U RabPsBgndHsdpa_128U RabPsInterHsdpa_384U RabPsBgndHsdpa_384U LackCidIu LackCidIub LackBwthIub RabPsBgndHsdpa_384U Conversational.Max Streaming.Avg Streaming.Cum Streaming.NbEvt Streaming.Min RabPsInter32D_384U RabPsBgnd32D_384U RabPsInter64D_384U RabPsBgnd64D_384U RabPsInter128D_384U RabPsBgnd128D_384U RabPsInter256D_384U RabPsBgnd256D_384U RabPsInter384D_384U RabPsBgnd384D_384U RabPsInterHsdpa_32U RabPsBgndHsdpa_32U
Nortel Confidential
251
VS.RabAssignmentReleaseSuccess - #633
VS.RabAssignmentReleaseUnsuccess - #634
VS.RabEstablishmentFirstOfTheCall - #637
RabPsInterHsdpa_64U RabPsBgndHsdpa_64U RabPsInterHsdpa_128U RabPsBgndHsdpa_128U RabPsInterHsdpa_384U RabPsBgndHsdpa_384U RabPsInter32D_384U RabPsBgnd32D_384U RabPsInter64D_384U RabPsBgnd64D_384U RabPsInter128D_384U RabPsBgnd128D_384U RabPsInter256D_384U RabPsBgnd256D_384U RabPsInter384D_384U RabPsBgnd384D_384U RabPsInterHsdpa_32U RabPsBgndHsdpa_32U RabPsInterHsdpa_64U RabPsBgndHsdpa_64U RabPsInterHsdpa_128U RabPsBgndHsdpa_128U RabPsInterHsdpa_384U RabPsInter32D_384U RabPsBgnd32D_384U RabPsInter64D_384U RabPsBgnd64D_384U RabPsInter128D_384U RabPsBgnd128D_384U RabPsInter256D_384U RabPsBgnd256D_384U RabPsInter384D_384U RabPsBgnd384D_384U RabPsInterHsdpa_32U RabPsBgndHsdpa_32U RabPsInterHsdpa_64U RabPsBgndHsdpa_64U RabPsInterHsdpa_128U RabPsBgndHsdpa_128U RabPsInterHsdpa_384U RabPsBgndHsdpa_384U RabPsInter32D_384U RabPsBgnd32D_384U RabPsInter64D_384U RabPsBgnd64D_384U RabPsInter128D_384U RabPsBgnd128D_384U RabPsInter256D_384U RabPsBgnd256D_384U RabPsInter384D_384U
Nortel Confidential
252
VS.RabrReconfiCompl3Gto3GReloc - #638
VS.CallEstablishmentDuration - #639
VS.HsdpaMobilitySuccess - #950
RabPsBgnd384D_384U RabPsInterHsdpa_32U RabPsBgndHsdpa_32U RabPsInterHsdpa_64U RabPsBgndHsdpa_64U RabPsInterHsdpa_128U RabPsBgndHsdpa_128U RabPsInterHsdpa_384U RabPsBgndHsdpa_384U Cs Ps CsPs Conversational.Avg Conversational.Cum Conversational.NbEvt Conversational.Min Streaming.Max Interactive.Avg Interactive.Cum Interactive.NbEvt Interactive.Min HsdpaToHsdpa NonHsdpaToHsdpa HsdpaToHsdpa NonHsdpaToHsdpa HsdpaToNonHsdpa ActSetUpd RadioLinkFail RABSetup RABRelease RABSetup RABRelease RABSetup
VS.HsdpaMobilityUnsuccessful - #951
VS.HsdpaCellDeletion - #952 VS.HsdpaDCHToHsdpaTransSucc - #953 VS.HsdpaToDCHSucc - #954 VS.DCHToHsdpaUnsuccessful - #955 VS.HsdpaToDCHUnsuccessful - #956 VS.MeasEvent1DNeighRNC - #1031 VS.MeasEvent1ENeighRNC - #1032 VS.MeasEvent1FNeighRNC - #1033 VS.MeasEvent2DNeighRNC - #1034 VS.MeasEvent2FNeighRNC - #1035 VS.CallEstablishmentDuration - #639
VS.UEDlRBRateAdapActiv - #640
CpichEcNo CpichRscp CpichEcNo Interactive.Max Background.Avg Background.Cum Background.NbEvt Background.Min Background.Max PsRB32D PsRB64D PsRB128D
Nortel Confidential
253
VS.UEDlRBRateAdapDeactiv - #641
VS.UEUlRBRateAdapActiv - #642
VS.UEUlRBRateAdapDeactiv - #643
VS.UEDlRBRateAdapDownReq - #644
VS.UEDlRBRateAdapUpReq - #645
VS.UEDlRBRateAdapDownSucc - #646
VS.UEDlRBRateAdapUpSucc - #647
VS.UEUlRBRateAdapDownReq - #648
VS.UEUlRBRateAdapUpReq - #649
VS.UEUlRBRateAdapDownSucc - #650
VS.UEUlRBRateAdapUpSucc - #651
PsRB256D PsRB384D PsRB32D PsRB64D PsRB128D PsRB256D PsRB384D PsRB32U PsRB64U PsRB128U PsRB384U PsRB32U PsRB64U PsRB128U PsRB384U PsRB32D PsRB64D PsRB128D PsRB256D PsRB384D PsRB32D PsRB64D PsRB128D PsRB256D PsRB384D PsRB32D PsRB64D PsRB128D PsRB256D PsRB384D PsRB32D PsRB64D PsRB128D PsRB256D PsRB384D PsRB32U PsRB64U PsRB128U PsRB384U PsRB32U PsRB64U PsRB128U PsRB384U PsRB32U PsRB64U PsRB128U PsRB384U PsRB32U PsRB64U PsRB128U
Nortel Confidential
254
VS.UERBRateAdapDownReqCell - #652 VS.UERBRateAdapUpReqCell - #653 VS.UERBRateAdapDownSuccCell - #654 VS.UERBRateAdapUpSuccCell - #655 VS.UERBRateAdapDownReqNeighbCell - #656 VS.UERBRateAdapUpReqNeighbCell - #657 VS.UERBRateAdapDownSuccNeighbCell - #658 VS.UERBRateAdapUpSuccNeighbCell - #659 VS.DlAsConfIdAvgNbrEstablished - #660
VS.PagingRecordsType2PagCausePs - #818
VS.PagingRequestsIuPagCauseCs - #819
VS.HsdpaToDCHUnsuccessful - #956 VS.HsdpaCACSuccess - #957 VS.HsdpaCACUnccessful - #958 VS.HsdpaIuRelAbnormal - #959
PsRB384U Downlink Uplink Downlink Uplink Downlink Uplink Downlink Uplink Downlink Uplink Downlink Uplink Downlink Uplink Downlink Uplink Avg Cum NbEvt Min Max TerminatingConversationalCall TerminatingStreamingCall TerminatingInteractiveCall TerminatingBackgroundCall TerminatingHighPrioritySignalling TerminatingLowPrioritySignalling TerminatingCauseUnknown TerminatingConversationalCall TerminatingStreamingCall TerminatingInteractiveCall TerminatingBackgroundCall TerminatingHighPrioritySignalling TerminatingLowPrioritySignalling TerminatingCauseUnknown RABRelease
CreditAllocProtErr CACReject MobilityFailure
VS.MeasEvent1ACell - #1017 VS.MeasEvent1BCell - #1018 VS.MeasEvent1CCell - #1019 VS.MeasEvent1DCell - #1020 VS.MeasEvent1ECell - #1021 VS.MeasEvent1FCell - #1022 VS.MeasEvent2DCell.CpichEcNo - #1023
CpichEcNo CpichRscp
Nortel Confidential
255
VS.MeasEvent2FCell.CpichEcNo - #1024 VS.MeasEvent2CCell.CpichEcNo - #1025 VS.MeasEvent3CCell - #1026 VS.MeasCallFailTraceDetectCell- #1027 VS.MeasEvent1ANeighRNC - #1028 VS.MeasEvent1BNeighRNC - #1029 VS.MeasEvent1CNeighRNC - #1030 VS.MeasEvent2FNeighRNC - #1035 VS.MeasEvent2CNeighRNC - #1036 VS.MeasEvent3CNeighRNC - #1037 VS.MeasCallFailTraceDetectNeighRNC - #1038 VS.MeasurementControlFailure - #1039
CpichEcNo CpichRscp CpichEcNo CpichRscp FullEvt OtherEvt
CpichRscp CpichEcNo CpichRscp FullEvt OtherEvt Other Evt1A1B1C1D1E1F Evt2D2FCpichEcNo
VS.IRMSchedulingTxCPRejectedSuccessNeighbRnc #1152 VS.IrmTimeDlIubTransportColorRed - #1148
Avg Cum Max Min NbEvt
VS.IRMSchedulingTxCPDowngradedSuccess - #1149 VS.IRMSchedulingTxCPDowngradedSuccessNeighbRnc #1150 VS.IRMSchedulingTxCPRejectedSuccess - #1151 VS.IRMSchedulingTxCPDowngradedFailure - #1153 VS.IRMSchedulingTxCPDowngradedFailureNeighbRnc #1154 VS.IrmTimeDlIubTransportColorYellow - #1155
VS.IrmPreemptionTimeDlIubTransportCongested - #1156
VS.IurDrncRadioLinkSetupUnsuccess - #1302
VS.IurDrncRadioLinkAdditionUnsuccess - #1304
Avg Cum Max Min NbEvt Avg Cum Max Min NbEvt LackCidIur LackBwthIur LackCidIub LackBwthIub LackCidIur LackBwthIur LackCidIub
Nortel Confidential
256
LackBwthIub VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess #1308 LackCidIur LackBwthIur LackCidIub LackBwthIub RabPsIB32D_64U RabPsIB32D_128U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIB32D_64U RabPsIB32D_128U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIB32D_64U RabPsIB32D_128U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIB32D_64U RabPsIB32D_128U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIB32D_64U RabPsIB32D_128U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIB32D_64U RabPsIB32D_128U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIB32D_64U RabPsIB32D_128U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIBHsdpa_384U RabPsIB32D_64U RabPsIB32D_128U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIB32D_64U RabPsIB32D_128U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIB32D_64U RabPsIB32D_128U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIB32D_64U RabPsIB32D_128U
VS.DedicatedUplinkMissingPduRlc - #1448 VS.DedicatedUplinkKbytesRlc - #1442
VS.DedicatedDownlinkKbytesRlc - #1443
VS.DedicatedUplinkPduRlc - #1444
VS.DedicatedDownlinkPduRlc - #1445
VS.DedicatedUplinkSduRlc - #1446
VS.DedicatedDownlinkSduRlc- #1447
VS.DedicatedUplinkMissingPduRlc - #1448 VS.DedicatedDownlinkKbytesRlcReferenceCell - #1459
VS.DedicatedUplinkPdusRlcReferenceCell - #1460 VS.DedicatedDownlinkDiscardSduRlc - #1449
VS.DedicatedDownlinkPaddingSduRlc - #1450
VS.DedicatedUplinkBadPdus - #1451
Nortel Confidential
257
VS.DedicatedDownlinkActivityRlc - #1454
VS.DedicatedUplinkActivityRlc - #1455
VS.DedicatedUplinkKbytesRlcActiveCells - #1456
VS.DedicatedDownlinkKbytesRlcActiveCells - #1457
VS.DedicatedUplinkKbytesRlcReferenceCell - #1458
VS.DedicatedDownlinkKbytesRlcReferenceCell - #1459 VS.DedicatedUplinkPdusRlcReferenceCell - #1460 VS.HsdpaIubCreditsConsumed - #1469
RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIB32D_64U RabPsIB32D_128U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIB32D_64U RabPsIB32D_128U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIB32D_64U RabPsIB32D_128U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIB32D_64U RabPsIB32D_128U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIB32D_64U RabPsIB32D_128U RabPsIBHsdpa_128U RabPsIB32D_64U RabPsIB32D_128U RabPsIBHsdpa_32U RabPsIBHsdpa_64U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIB32D_64U RabPsIB32D_128U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIB32D_64U RabPsIB32D_128U RabOther RabCsConv12_2 RabCsConv64 RabCsStr14_4 RabCsStr57_6 RabPsIB8D_32U RabPsIB8D_8U RabPsIB32D_32U RabPsIB64D_64U RabPsIB128D_64U RabPsIB128D_128U RabPsIB384D_64U RabPsIB256D_64U RabPsStr64D_16U
VS.HsdpaIubFPDiscardedBytes - #1470 VS.DedicatedDownlinkPdusRlcReferenceCell - #1461
VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell #1462
VS.RlcUnrecoverableError - #1463
Nortel Confidential
258
VS.HsdpaDiscardNonConfTraffic - #1464
VS.HsdpaIubDlControlFrames - #1465
VS.HsdpaIubNonZeroCapacityAlloc - #1466
VS.HsdpaIubZeroCapacityAlloc - #1467
VS.HsdpaIubCreditsRequested - #1468
VS.RabIncomingRefCell - #663
VS.RabAbnormRelPerReqRabTypRefCel - #665
RabSrb RabPsIBHsdpa_32U RabPsIBHsdpa_64U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIB32D_64U RabPsIB32D_128U RabPsIBHsdpa_32U RabPsIBHsdpa_64U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIBHsdpa_32U RabPsIBHsdpa_64U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIBHsdpa_32U RabPsIBHsdpa_64U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIBHsdpa_32U RabPsIBHsdpa_64U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsIBHsdpa_32U RabPsIBHsdpa_64U RabPsIBHsdpa_128U RabPsIBHsdpa_384U RabPsInter64D_64U RabPsBgnd64D_64U RabPsStr64D_64U RabPsInter128D_64U RabPsBgnd128D_64U RabPsStr128D_64U RabPsInter128D_128U RabPsBgnd128D_128U RabPsStr128D_128U RabPsInter384D_64U RabPsBgnd384D_64U RabPsStr384D_64U RabPsInter256D_64U RabPsBgnd256D_64U RabPsStr256D_64U RabPsStr64D_16U RabPsInter64D_384U RabPsBgnd64D_384U RabPsInter128D_384U RabPsBgnd128D_384U RabPsInter256D_384U RabPsBgnd256D_384U RabPsInter384D_384U
Nortel Confidential
259
VS.IuRelocationCmdFailuresCs - #551 VS.UEDlRBRateAdapActiv - #640 VS.UEDlRBRateAdapDeactiv - #641 VS.UEUlRBRateAdapActiv - #642 VS.UEUlRBRateAdapDeactiv - #643 VS.UEDlRBRateAdapDownReq - #644 VS.UEDlRBRateAdapUpReq - #645 VS.UEDlRBRateAdapDownSucc - #646 VS.UEDlRBRateAdapUpSucc - #647 VS.UEUlRBRateAdapDownReq - #648 VS.UEUlRBRateAdapUpReq - #649 VS.UEUlRBRateAdapDownSucc - #650 VS.UEUlRBRateAdapUpSucc - #651 VS.MeasurementControlFailure - #1039
VS.IRMTimeCellRadioColorRed - #1124
VS.IRMTimeCellRadioColorYellow - #1125
VS.IRMTimeCellRadioColorGreen - #1127
VS.IntraRncOutInterFreqHoAttempt - #138 VS.IntraRncOutInterFreqHoFail - #139
VS.IntraRncIncInterFreqHoAttempt - #140 VS.IntraRncIncInterFreqHoFail - #141
VS.IuReleaseCommandCs - #552
RabPsBgnd384D_384U RabPsInterHsdpa_32U RabPsBgndHsdpa_32U RabPsInterHsdpa_64U Rab.RabPsBgndHsdpa_64U 3Gto2GRelocTimeout 3Gto2GAlreadyInProgr PsRBOtherD PsRBOtherD PsRBOtherU PsRBOtherU PsRBOtherD PsRBOtherD PsRBOtherD PsRBOtherD PsRBOtherU PsRBOtherU PsRBOtherU PsRBOtherU Evt2D2FCpichRscp Evt2CCpichEcNo Evt2CCpichRscp Evt3C Avg Cum NbEvt Min Max Avg Cum Min Max NbEvt Avg Cum Min Max NbEvt WithCM WithCMMeasNotEnoughRes WithCMMeasNodeBFail WithCMMeasRRC WithCM WithCMMeasNotEnoughRes WithCMMeasNodeBFail WithCMMeasRRC NormalRelease ReleaseDueToUtranGeneratedReason Other RelocationCancelled
Nortel Confidential
260
VS.IuReleaseCommandPs - #553
OAMIntervention Unspecified UserInactivity NoRemainingRab NormalRelease ReleaseDueToUtranGeneratedReason Other RelocationCancelled OAMIntervention Unspecified UserInactivity NoRemainingRab OamIntervention IuUserPlaneFailure UnspecifiedFailure RepeatedIntegrityCheckFailure UeGeneratedSignallingConnectionRelease RadioConnectionWithUeLost AbnormalConditionTimerRelocExpiry Other AlwaysOnDowngrade IuUserPlaneFailure OamIntervention UnspecifiedFailure RepeatedIntegrityCheckFailure UeGeneratedSignallingConnectionRelease RadioConnectionWithUeLost AbnormalConditionTimerRelocExpiry Other RabOther RabCsConv12_2 RabCsConv64 RabCsStr14_4 RabCsStr57_6 PsInter8D_32U RabPsBgnd8D_32U RabPsInter8D_8U RabPsBgnd8D_8U RabPsInter32D_32U RabPsBgnd32D_32U RabPsInter64D_64U RabPsBgnd64D_64U RabPsStr64D_64U RabPsInter128D_64U RabPsBgnd128D_64U RabPsStr128D_64U lRabPsInter128D_128U
VS.IuReleaseRequestCs - #554
VS.IuReleaseRequestPs - #555
VS.RabOutgoingRefCell - #662
Nortel Confidential
261
VS.RabIncomingRefCell - #663
RabPsBgnd128D_128U RabPsStr128D_128U RabPsInter384D_64U abPsBgnd384D_64U RabPsStr384D_64U RabPsInter256D_64U RabPsBgnd256D_64U RabPsStr256D_64U RabPsStr64D_16U RabPsMultipleInter64D_64U RabPsMultipleBgnd64D_64U RabPsInter32D_64U RabPsBgnd32D_64U RabPsInter32D_128U RabPsBgnd32D_128U RabPsInter32D_384U RabPsBgnd32D_384U RabPsInter64D_384U RabPsBgnd64D_384U RabPsInter128D_384U RabPsBgnd128D_384U RabPsInter256D_384U RabPsBgnd256D_384U RabPsInter384D_384U RabPsBgnd384D_384U RabPsInterHsdpa_32U RabPsBgndHsdpa_32U RabPsInterHsdpa_64U RabPsBgndHsdpa_64U RabPsInterHsdpa_128U RabPsBgndHsdpa_128U RabPsInterHsdpa_384U RabPsBgndHsdpa_384U RabOther RabCsConv12_2 RabCsConv64 RabCsStr14_4 RabCsStr57_6 RabPsInter8D_32U RabPsBgnd8D_32U RabPsInter8D_8U RabPsBgnd8D_8U RabPsInter32D_32U RabPsBgnd32D_32U RabPsMultipleInter64D_64U RabPsMultipleBgnd64D_64U RabPsInter32D_64U RabPsBgnd32D_64U RabPsInter32D_128U RabPsBgnd32D_128U
Nortel Confidential
262
VS.RabEstabSuccPerReqRabTypRefCell - #664
RabPsInter32D_384U RabPsBgnd32D_384U RabPsInter64D_384U RabPsBgnd64D_384U RabPsInter128D_384U RabPsBgnd128D_384U RabPsInter256D_384U RabPsBgnd256D_384U RabPsInter384D_384U RabPsBgnd384D_384U RabPsInterHsdpa_32U RabPsBgndHsdpa_32U RabPsInterHsdpa_64U RabPsBgndHsdpa_64U RabPsInterHsdpa_128U RabPsBgndHsdpa_128U RabPsInterHsdpa_384U RabPsBgndHsdpa_384U RabOther RabCsConv12_2 RabCsConv64 RabCsStr14_4 RabCsStr57_6 RabPsInter8D_32U RabPsBgnd8D_32U RabPsInter8D_8U RabPsBgnd8D_8U RabPsInter32D_32U RabPsBgnd32D_32U RabPsInter64D_64U RabPsBgnd64D_64U RabPsStr64D_64U RabPsInter128D_64U RabPsBgnd128D_64U RabPsStr128D_64U RabPsInter128D_128U RabPsBgnd128D_128U RabPsStr128D_128U RabPsInter384D_64U RabPsBgnd384D_64U RabPsStr384D_64U RabPsInter256D_64U RabPsBgnd256D_64U RabPsStr256D_64U RabPsStr64D_16U RabPsMultipleInter64D_64U RabPsMultipleBgnd64D_64U RabPsInter32D_64U RabPsBgnd32D_64U RabPsInter32D_128U
Nortel Confidential
263
VS.RabAbnormRelPerReqRabTypRefCel - #665
RabPsBgnd32D_128U RabPsInter32D_384U RabPsBgnd32D_384U RabPsInter64D_384U RabPsBgnd64D_384U RabPsInter128D_384U RabPsBgnd128D_384U RabPsInter256D_384U RabPsBgnd256D_384U RabPsInter384D_384U RabPsBgnd384D_384U RabPsInterHsdpa_32U RabPsBgndHsdpa_32U RabPsInterHsdpa_64U RabPsBgndHsdpa_64U RabPsInterHsdpa_128U RabPsBgndHsdpa_128U RabPsInterHsdpa_384U RabPsBgndHsdpa_384U RabOther RabCsConv12_2 RabCsConv64 Rab.RabCsStr14_4 RabCsStr57_6 RabPsInter8D_32U RabPsBgnd8D_32U RabPsInter8D_8U RabPsBgnd8D_8U RabPsInter32D_32U RabPsBgnd32D_32U RabPsInter64D_64U RabPsBgnd64D_64U RabPsStr64D_64U RabPsInter128D_64U RabPsBgnd128D_64U RabPsStr128D_64U RabPsInter128D_128U RabPsBgnd128D_128U RabPsStr128D_128U RabPsInter384D_64U RabPsBgnd384D_64U RabPsStr384D_64U RabPsInter256D_64U RabPsBgnd256D_64U RabPsStr256D_64U RabPsStr64D_16U RabPsMultipleInter64D_64U RabPsMultipleBgnd64D_64U RabPsInter32D_64U Rab.RabPsBgnd32D_64U
Nortel Confidential
264
RabPsInter32D_128U RabPsBgnd32D_128U RabPsInter32D_384U RabPsBgnd32D_384U RabPsInterHsdpa_128U RabPsBgndHsdpa_128U RabPsInterHsdpa_384U RabPsBgndHsdpa_384U
Nortel Confidential
265
1.2.
BTS COUNTERS
VS.CESReceivedCells - #10140 VS.CESSentCells - #10141 VS.CESSnLostCells - #10142 VS.CESSnMisinsertCells - #10143 VS.CESSnSeqce - #10144 VS.CESSpErrors - #10145 VS.CESRxGov - #10146 VS.CESTxGun - #10147 VS.CESReSync - #10148 VS.HsdpaHSPDSCHTxPwr.Avg - #10801
VS.HsdpaHSPDSCHCodesPerTTI.Avg - #10802
VS.HsdpaHSSCCHTxPwr.Avg - #10803
VS.HsdpaHSSCCHCodesPerTTI.Avg - #10804
Avg Cum NbEvt Min Max Avg Cum NbEvt Min Max Avg Cum NbEvt Min Max Avg Cum NbEvt Min Max Avg Cum NbEvt Min Max Avg Cum NbEvt Min Max Avg Cum NbEvt Min Max Avg Cum NbEvt
VS.Hsdpa16QAMUsage - #10805 VS.HsdpaMACdPDUAckBits.Avg - #10806
VS.HsdpaRxDataBitsMAChs.Avg - #10807
VS.HsdpaTxDataBitsMAChs.Avg - #10808
VS.HsdpaTxDataBitsSchedTotal.Avg - #10809
Nortel Confidential
266
Min Max VS.HsdpaNbrACKRcv - #10810 VS.HsdpaNbrNACKRcv - #10811 VS.HsdpaNbrDTX - #10812 VS.HsdpaDiscMACdPDUsTimerExpiry - #10813 VS.HsdpaDiscTransportBlocksOnMaxRetrans - #10814 VS.HsdpaMeanNbrRetrans.Avg - #10815
VS.HsdpaDataBufferedNodeB.Avg - #10816
Avg Cum NbEvt Min Max Avg Cum NbEvt Min Max
VS.HsdpaPAOverload - #10817 VS.HsdpaTTIsUsed - #10818
Nortel Confidential
267
2.
UA04.2/OAM05.0 DELETED COUNTERS

This paragraph lists the deleted counters between UA04.1 and U404.2.
2.1.
RNC DELETED COUNTERS

NbEvt Avg Cum Max Min Avg Cum Max Min NbEvt IurCallInit IurCallTerm IuPcCom RncCall NobCall RrmDed Spare3 Spare2 Spare1 Spare0
VS.UlAsConfIdAvgNbrEstablished.NbEvt - #620
VS.RabAvgNbrEstablished.Avg - #619
VS.RncCallCleanup.IurCallInit - #3002
2.2.
BTS DELETED COUNTERS

None
Nortel Confidential
268
3.
UA04.2/OAM05.0 MODIFIED COUNTERS

This paragraph lists the modified counters between UA04.1 and U404.2.
3.1.
RNC MODIFIED COUNTERS

None
3.2.
BTS MODIFIED COUNTERS

None

To order documentation from Nortel Wireless Knowledge Services from all countries except North America, contact: Tel.: (1) (615) 432-4848 To order documentation from Nortel Wireless Knowledge Services from North America, contact: Tel.: (1) (877) 662-5669 [Option 4] or (1) (919) 997-8015 To report a problem in this publication from all countries except North America, contact: Nortel Documentation Department Parc d'Activit de Magny-Chteaufort Chteaufort 78928 Yvelines Cedex 9 France Fax: (33) (1) 39-44-50-29 To report a problem in this publication from North America, contact: Nortel Global Knowledge Services 2221 Lakeside Boulevard Richardson TX 75082 USA Tel.: (1) (800) 466-7838 or (1) (972) 684-5935 From any country, you can also use the "Contact Us" link from the Nortel Networks Customer Documentation World Wide Web site at: http://www.nortel.com/documentation
Copyright 2003-2005 Nortel Networks, All Rights Reserved
NORTEL CONFIDENTIAL
The information contained in this document is the property of Nortel Networks. Except as specifically authorized in writing by Nortel Networks, the holder of this document shall keep the information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties and use same for evaluation, operation and maintenance purposes only. The content of this document is provided for information purposes only and is subject to modification. It does not constitute any representation or warranty from Nortel Networks as to the content or accuracy of the information contained herein, including but not limited to the suitability and performances of the product or its intended application. This is the Way. This is Nortel, Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks. All other trademarks are the property of their owners.
Document number: Document issue: Document status: Product Release: Date:
NN-20500-044 01.02/EN Preliminary UMTS 5.0 March 2006
Originated in France

UTRAN Release Operational Impacts (Features, Counters... )

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

UTRAN Release Operational Impacts (Features, Counters... )

Caricato da

Copyright:

Formati disponibili

NN-20500-044

UTRAN Release UMTS5.0

UTRAN RELEASE OPERATIONAL IMPACTS UMTS5.0

Copyright 2003-2005 Nortel Networks

UTRAN Release Operational Impacts - UMTS5.0

Copyright 2004 Nortel Networks

Copyright 2003-2005 Nortel Networks

Nortel Networks Confidential

Copyright 2004 Nortel Networks

4.12. 4.13. 4.14. 4.15. 4.16. 4.17. 5.

Copyright 2003-2005 Nortel Networks

Nortel Networks Confidential

13.3.1 13.3.2 13.4. 13.5. 13.6.

13.5.1 13.6.1 13.6.2 13.6.3 13.7. 13.7.1 14.

NETWORK ARCHITECTURE .................................................................................................130

15.2.1 15.2.2 15.2.3 15.2.4 16.

16.2.1 16.2.2 16.2.3 17. 18. 19. 20.

Copyright 2003-2005 Nortel Networks

UTRAN Release Operational Impacts - UMTS5.0

Nortel Networks Confidential

Copyright 2003-2005 Nortel Networks

UTRAN Release Operational Impacts - UMTS5.0

Nortel Networks Confidential

Copyright 2004 Nortel Networks

ANODE MODIFIED PARAMETERS ..........................................................................................222

INODE MODIFIED PARAMETERS ...........................................................................................226

Copyright 2003-2005 Nortel Networks

UTRAN Release Operational Impacts - UMTS5.0

Nortel Networks Confidential

BTS MODIFIED PARAMETERS ..............................................................................................233

OAM MODIFIED PARAMETERS .............................................................................................239

POC MODIFIED PARAMETERS .............................................................................................242

3.6.2 3.6.3 3.6.4 3.6.5 3.6.6 3.6.7 3.6.8 3.6.9 3.6.10

ATMCELL (CELL) ........................................................................................................242 ATMPNNI (PNNI).........................................................................................................242

Copyright 2003-2005 Nortel Networks

UTRAN Release Operational Impacts - UMTS5.0

Nortel Networks Confidential

Copyright 2004 Nortel Networks

[R3] UMT/SYS/INF/07906 V01.07/EN [R4] 411-8111-813 (P1 to P6)

NN-20500-044 01.02/EN Preliminary March 2006

Copyright 2003-2005 Nortel Networks

[R27] UMT/SYS/DD/15313 with respect to 3GPP [R28] HSDPA 411-8111-575

[R29] UMT/OAM/INF/11587 Planning Guide OAM05.0

NN-20500-044 01.02/EN Preliminary March 2006

Copyright 2003-2005 Nortel Networks

UA04.2 FEATURE IMPACT LIST

NN-20500-044 01.02/EN Preliminary March 2006

Copyright 2003-2005 Nortel Networks

3.1.1 PERFORMANCE AND CAPACITY FEATURE IMPACT LIST

NN-20500-044 01.02/EN Preliminary March 2006

Copyright 2003-2005 Nortel Networks

3.1.2 TRANSMISSION AND TRANSPORT CAPABILITY FEATURE IMPACT LIST

Network Architecture x Network Architecture

3.1.3 SECURITY FEATURE IMPACT LIST

IPsec support validation on RNC Support of Radius Client on RNC

NN-20500-044 01.02/EN Preliminary March 2006

Copyright 2003-2005 Nortel Networks

3.1.4 RADIO MOBILITY FEATURE IMPACT LIST

3G to 2G Redirection for Speech calls Service-based inter-freq/inter-RAT selection for HHO

NN-20500-044 01.02/EN Preliminary March 2006

Copyright 2003-2005 Nortel Networks

3.1.5 RESOURCE MANAGEMENT AND OPTIMIZATION / SERVICES FEATURE IMPACT LIST