RANOP2 Module3 Neighbour&RF Optimization RAS06

1 © Nokia Siemens Networks Presentation / Author / DateFor internal use

3G RANOP2 RAS06 Module 3-Neighbour & RF Optimisation


Module 3- Neighbour & RF Optimization

Objectives

After this module the participant shall be able to:

•Describe the main neighbour optimization methods and tools

•Describe KPI analysis for neighbour list optimization

•Learn how neigbour & RF optimization can be done with Optimizer2.0 and E-NAPS


Contents

• Neighbour optimization Methods & Tools

• Adjacency Based Measurements

• NetAct Optimiser 2.0 overview

• Propagation Delay

• E-NAPS tool


Neighbour optimization

• RAS51 handover measurement provides cell to cell HO statistic which can be used for neighbour performance optimisation 1013 Autodef SHO 1014 Autodef IFHO 1015 Autodef ISHO

• Autodef HO Measurement can used and activated as any other basic RAN performance measurements

• Autodef HO measurement are also used with help of the NetAct optimiser 2.0 optional feature (automatic adjacency optimisation).

• NetAct Optimiser 2.0 use Autodef counters for deleting adjacencies and ICSU statistics still for creating adjacencies (Optimiser 1.6 use ICSU statistic only).

• E- NAPS tool is internal tool using Autodef KPI info for neighbour optimization (no need to make ICSU logging.


Neighbour list Combination procedure- SHO/ISHO to undefined neighbour possible

I• Active Set may contain cells, which are not necessary adjacencies with each other. • The list of cells to be measured is send by the RNC in a MEASUREMENT

CONTROL message and is changed at every Active Set Update. The RNC then combines the Neighbour lists according to the following rules:

1.Active set cells (1-3 according ranking)

2.Neighbour cells which are common to three active set cells

3.Neighbour cells which are common to two active set cells , and from which one is the controlling cell

4.Neighbour cells which are defined for only the controlling cell (latest PL info)

5.Neighbour cells which are common to two active set cells (latest PL info)

6.Neighbour cells which are defined for only the 2nd cell

7.Neighbour cells which are defined for only the 3rd cell

• If the total number of cells to be measured exceeds the maximum value of 32 during any step then handover control stops the Neighbour list generation


Neighbour list Combination procedureII• Because of the combination explained in the previous slide, it is possible to

measure handover activity between 2 cells which do not have an adjacency defined between them.

• In this example intra-frequency adjacencies exist between cells 2-6 and 6-7, but not between 2-7. Activity is measured when the lists of cells 2 and 6 are combined and 7 can be added, while 2 is still the best cell in the Active Set. The same effect applies for Inter-System list combining

Neighboured

Not neighboured

1

23 4

56

7

89

UE path

Neighboured

Not neighboured

1

23 4

56

7

89

UE path


RAS06 new SHO counters

• It is possible to see the ASU performance with RAS06 counters:• M1006C121 ACTIVE SET UPDATE RL ADD ATTEMPTS

• M1006C122 ACTIVE SET UPDATE RL ADD SUCCESS

• M1006C123 ACTIVE SET UPDATE RL ADD FAILURE UE

• M1006C124 ACTIVE SET UPDATE RL ADD FAIL NO REPLY

• M1006C125 ACTIVE SET UPDATE RL DEL ATTEMPTS

• M1006C126 AS_UPDATE_RL_DEL_SUCC


RAS06 Active Set Add FAIL_UE/NO REPPLY- example (wcel level, 13.03.2008)

0

5000

10000

15000

20000

25000

1 18 35 52 69 86 103 120 137 154 171 188 205 222 239 256 273 290 307 324 341 358 375 392 409

0

5

10

15

20

25

30

AS_UPDATE_RL_ADD_ATT

AS_UPDATE_RL_DEL_ATT

AS_UPDATE_RL_ADD_FAIL_UE

AS_UPDATE_RL_ADD_NOREPLY


RAS06 Active Set Add/Del success- example, RNC

0.9989

0.999

0.9991

0.9992

0.9993

0.9994

0.9995

0.9996

0.9997

0.9998

0.9999

0.00%

0.01%

0.01%

0.02%

0.02%

0.03%

0.03%

0.04%

0.04%

AS_UPDATE_RL_ADD_SUCC %

AS_UPDATE_RL_DEL_SUCC %

AS_UPDATE_RL_ADD_FAIL_UE %

AS_UPDATE_RL_ADD_NOREPLY %

Some failures due to no reply

to ASU


ASU FAILURES• In RAS06 it is possible to see some Active Setup Update failure reasons as

below:Counter Name Counter ID Update Cause

AS_UPDATE_RL_ADD_ATT M1006C121

When an RRC: ACTIVE SET UPDATE message is sent by the serving RNC to the UE for adding one or more radio links to the active set. The counter is updated by the number of radio links that are attempted to be added to the active set, also in a cell replacement procedure. The counter is updated for the cells that are attempted to be added to the active set. In case of a DRNC cell, the WBTS-0/WCEL-0 object is used

AS_UPDATE_RL_ADD_SUCC M1006C122

When the serving RNC receives an RRC: ACTIVE SET UPDATE COMPLETE message from the UE, this counter is updated by the number of radio links added with the active set update procedure, also in a cell replacement procedure. The counter is updated for the cells which were added to the active set. In case of a DRNC cell, the WBTS-0/WCEL-0 object is used

AS_UPDATE_RL_ADD_FAIL_UE M1006C123

When the serving RNC receives an RRC: ACTIVE SET UPDATE FAILURE message from the UE, this counter is updated by the number of radio links that were attempted to be added to the UE's active set with the active set update procedure, also in a cell replacement procedure. The counter is updated for the cells which were attempted to be added to the active set. In case of a DRNC cell, the WBTS-0/WCEL-0 object is used.

AS_UPDATE_RL_ADD_NOREPLY M1006C124

When the serving RNC does not receive a reply to an RRC: ACTIVE SET UPDATE message sent to the UE, this counter is updated by the number of radio links that were attempted to be added into the UE's active set with the active set update procedure, also in a cell replacement procedure. The counter is updated for the cells which were attempted to be added into the active set. In case of a DRNC cell, the WBTS-0/WCEL-0 object is used.

AS_UPDATE_RL_DEL_ATT M1006C125

When an RRC: ACTIVE SET UPDATE message is sent by the serving RNC to the UE for deleting one or more radio links to the active set. The counter is updated by the number of radio links that are attempted to be deleted from the active set, also in a cell replacement procedure. The counter is updated for the cells that are attempted to be deleted from the active set. In case of a DRNC cell, the WBTS-0/WCEL-0 object is used.

AS_UPDATE_RL_DEL_SUCC M1006C126

When the serving RNC receives an RRC: ACTIVE SET UPDATE COMPLETE message from the UE, this counter is updated by the number of radio links deleted from the active set update procedure, also in a cell replacement procedure. The counter is updated for the cells which were deleted from the active set. In case of a DRNC cell, the WBTS-0/WCEL-0 object is used


Content



• NetAct Optimiser 2.0 overview


• E-NAPS Tool


Adjacency Based Measurements Counters

M1013 Autodef SHO• M1013C0 Number of Intra Frequency SHO attempts

• Counter is Updated when SRNC starts a Branch Addition or Branch Replacement procedure.

• M1013C1 Number of completed Intra Frequency SHO• Counter is updated when SRNC successfully ends the Branch Addition or Branch Replacement procedure.

M1014 Autodef IFHO• M1014C0 Number of Inter Frequency HHO attempts

• Counter is updated when SRNC starts inter-frequency HHO

• M1014C1 Number of completed Inter Frequency HHO• Counter is updated when SRNC successfully ends inter-frequency HHO

M1015 Autodef ISHO• M1015C0 Number of Inter System HHO attempts

• Counter is updated when SRNC starts inter-system HHO

• M1015C1 Number of completed Inter System HHO• Counter is update when SRNC receives RANAP:IU RELEASE COMMAND from core network after successful

Inter System HHO


SHO Share

• HO Share provides distribution of HO attempts from the source cell• Useful detect neighbour relations which has exceptional amount of attempts

• It is possible to get the total number of outgoing HO attempts from the Autodef HO measurements by taking a sum over all the adjacencies reported for a source cell

• SHO HO Share (M1013 AutoDef SHO)

• IFHO HO Share (M1014 AutoDef IFHO)

• ISHO HO Share (M1015 AutoDef ISHO)

)_____(______

)_____(*100903___

ATTSHOFREQINTRAADJSHOcellthefromadjaalloverSum

ATTSHOFREQINTRAADJSHOsumaRNCShareSHO

)_____(______

)_____(*100904___

ATTHHOFREQINTERADJHHOcellthefromadjaalloverSum

ATTHHOFREQINTERADJHHOsumaRNCShareIFHO

)_____(______

)_____(*100905___

ATTHHOSYSINTERADJHOcellthefromadjaalloverSum

ATTHHOSYSINTERADJHOsumaRNCShareISHO


HO Success per Adjacency

• The HO success rate per adjacency can be calculated by using formulas below

• Can be used to detect badly performing neighbours

• SHO Success per Adjacency (M1013 AutoDef SHO)

• IFHO Success per Adjacency (M1014 AutoDef IFHO)

• ISHO Success per Adjacency (M1015 AutoDef ISHO)

)_____(

)_____(*100900_____

ATTSHOFREQINTRAADJSHOsum

COMPLSHOFREQINTRAADJSHOsumaRNCADJSpersuccessSHO

)_____(

)_____(*100901_____

ATTHHOFREQINTERADJHHOsum

COMPHHOFREQINTERADJHHOsumaRNCADJIpersuccessIFHO

)_____(

)_____(*100902_____

ATTHHOSYSINTERADJHOsum

COMPLHHOSYSINTERADJHOsumaRNCADJGpersuccessISHO


Content



• NetAct Optimiser 2.0 overview• Creating ADJx based on PM data


• E-NAPS Tool


Automated Adjacency Optimisation for 3G in Optimizer 2.0• Accurate and efficient process for optimising operational WCDMA cell

adjacencies

• Measurement based optimisation• Current adjacency status analysis

• Deletion of unused adjacencies based on KPIs

• HO attempts, HO success

• Adjacency candidate identification, activation and measurement

• Interfering intra-frequency cells

• Cell pair Ec/No difference from WCDMA

• Neighbour cell signal strength from GSM

• Final adjacency list optimisation

• Scrambling code re-allocation

• Full visibility and control to the user


• A fast way to identify missing intra-frequency adjacencies• Interference measurements colleted from RNC

• New adjacencies can be created based on that statistics

• Rotation method used to achieve the optimal lists for other adjacency types

• Optimizer creates adjacency candidates

• Candidates are downloaded to network and measured• Statistics collected directly from RNC

• Cell pair Ec/No difference

• Successful BSIC verifications & BSIC verification time

• Final adjacency list is generated

Creating new adjacencies


Content



• NetAct Optimiser 2.0 overview• Creating ADJx based on PM data (AutoDef)

• Creating ADJx based on DSR measurements (ICSU)

• WCDMA Interference analysis


• E-NAPS tool


Creating ADJx based on PM data (AutoDef)

• Optimizer will show adjacency based SHO amounts for undefined neighbours

• Purpose is to search all ADJS and ADJG new neighbours which are within certain max distance

• Example 1-5 km in urban area and 4-10 km outside urban area.

• After that only those will be selected which have enough SHO/ISHO attempts.

• The selected neighbours could be provisioned straight away to the network


How to create Missing ADJx based on PM data-1

1. Select area from the map

And start the ADJ

Optimization tool

2. Select ADJG, ADJS and ADJW types



3. Select right actions from rules,

common Deletion and

Creation tabs



4. Purpose is to search all ADJS and ADJG new neighbours which are within certain max

distance like 1-5 km in urban area and 4-10 km outside urban area. After that only those will be

selected which have enough SHO/ISHO attempts.

5. Start from here

6. Save plan from here with any name



7. List all new neighbors


How to create Missing ADJx based on PM data-5 8. Select the whole week

or one day for PM data analysis

10. Update the list of

Neighbours from here

9. Select the right profile to browser (ADJG, ADJS)

11. Sort according to

the PM attempts



12. See the ADJ on top of the map

13. Provision the selected neighbors to the network

Note ! These neighbors are defined only for one way direction.

See next slides how to make those bidirectionally (Refresh actual operation with RAC)



14. Open the CM data exchange

under the main window

15. Select refresh actual and wait

Until the data is updated

16. Open the adjacency optimization without selecting any

tabs from Deletion or Creation, just to find just created one way ADJx



17. Save the plan and list the planned elements

18. You can see now the ADJx neigbours which

can now provisioned to the network


Content





• WCDMA Interference Analysis


• E-NAPS tool (AutoDef)


Creating ADJx based on DSR measurements (ICSU)• Detected set measurements are not coming from undefined

neighbours (based on ICSU logs)

• Aim is to find source of interference • cell having many DSR results but no SHO attempts (with neighhbour list

combination list)

• Solutions• Add found cell to the neighbour

• Downtilt to decrease the interference

• DSR measurements are suitable also for ADJG neighbours


DSR activation

• When DSR is not activated, UE monitors only cells in its NCL (either read from BCCH or sent from RNC in SHO case).

• When DSR IS activated, UE scans ALL scrambling codes in same frequency band and if cells are found that fulfil certain criteria, UE reports this/these cell(s) as detected cells.

• criteria for detection is that UE has to be able to detect if Ec/N0 is greater than -18 (or -20???) dB

• for a DSR to be triggered, detected cell/s must fulfil "normal" HO criteria, i.e. for example, are within the reported range relative to P-CPICH of strongest AS cell.

• Details of activation :MML command that is sent to RNC that sets some flag active and RNC orders UE to measure and report. It can be done by HIT macro, but Optimizer is not (supposed to) using them but same commands that are in HIT macros are sent directly to RNC.


1. Select scope, area from map

Or individual site or cell

2. Select tools/ Adjacency Optimization

3. Select ADJS,(ADJS=3G/3G,

ADJG=3G->2G,ADJW=2G->3G

ADJI= 3G-3G,ADJE=2G-2G)


6. ChangeDSR parameters

from here

4. Rules: Fill and keep adjacencied in same Site and Fill bidirectionality

5. Common: Use Bidirectional Optimisation and Enable Changes between

Scope and Buffer area


7. If you want look at cells,which are seen by DSR, but are not in combined list

(no SHO attempts to that one), select SHO attempts big enough to find

The cells which are purely interference sources


Tästä halutut solut kartalle

8. Start optimization and you see the found created adjacencies

in browser, if you want to see the cells on map, the plan should be stored


9. Here you can see DSR reports

10.If you want implement this neighbor, just select both directions from Adjacencies tab:

list to browser and further by selecting both directions and with right mouse button:

Provision instantly


Select both directions and provision instantly


Optimizer does not create neighbours if one rule below is true.However if all missing neighbours want’s to be seen, these rules can be omitted (and see all interfering cells based on

DSR). If you want to add neighbors, it is recommended to check SC problems with by Scrambling code allocation tool. Don’t use this in normal operation.


11. It is possible to find ADJG/ADJW based on Measurement data, if bidirectional

Neighbours are wanted both ADJG and ADJW should be selected


Content









WCDMA Interference Analysis

• it is possible to see WCDMA internal interference situation of certain cell which is caused by other WCDMA cells (in terms of distance,RSCP and EcNo level). Also non-neighbours can be measured with DSR.

• Both Incoming and Ongoing interference levels can be studied with certain cell pairs.

• Interference information is based on UE measurements where the signal strength and quality of every Primary Scrambling code is reported to RNC.

• Before interference analysis the following actions should be done

1. Start WCDMA interference measurements

2. Activate measurements from Interference matrix (from selective RNCs or all measurements)

3. Start Interference analyzer for WCDMA –tool (from Scope, RNC or site)

4. Analyze the selection which was done in step 3


WCDMA Interference Analysis

• The analysis shows for example the number of measured adjacencies with number of reports (SHO + DSR measurements) and if it is neighbour or not.

• If there is lot of reports from non-neighbour cell it would make sense to add it to the neighbour, at least if the distance is reasonable and if the RSCP levels are high. This will mean that the cell could be interferer, especially if there is not much SHOs (low SHO share %) to that cell (even with SHO combination).

DSR result from no

neighbourRSCP,EcNo

criteria


Content









RAS06 Propagation delay counters

• PRACH propagation delay statistics is presented using a distribution consisting of 21 counters M1006C128-M1006C148. One of the counters is updated by value 1 when the UE sends RRC Connection Request or Cell Update.

• Each counter covers one or more PROP_DELAY values and the mapping of measured values to counters can be controlled by WCEL parameter PRACHDelayRange that defines five different mapping tables for various cell sizes

Range 60 km (this is fixed in RAS06)bin 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20from(m) 0 234 468 936 1170 1638 2106 3042 3978 4914 6084 7020 7956 10062 14976 19890 25038 29952 34866 40014 50076PROP_DELAY (from) 0 1 2 4 5 7 9 13 17 21 26 30 34 43 64 85 107 128 149 171 214to(m) 234 468 936 1170 1638 2106 3042 3978 4914 6084 7020 7956 10062 14976 19890 25038 29952 34866 40014 50076 infinitePROP_DELAY (to) 0 1 3 4 6 8 12 16 20 25 29 33 42 63 84 106 127 148 170 213

bin size(m) 234 234 468 234 468 468 936 936 936 1170 936 936 2106 4914 4914 5148 4914 4914 5148 10062


RAS05 practise- UE Delay Compensation removed in RAS06 ?

• Tentative mapping between PRACH delay class and UE-Node B distance based on measurements in a single network".

• 760 m offset taken out from the measurements: not valid anymore ?

PRACH 60 km range delay class from to

0 0 01 0 02 0 1763 176 4104 410 8785 878 13466 1346 22827 2282 32188 3218 41549 4154 5324

10 5324 626011 6260 719612 7196 930213 9302 1421614 14216 1913015 19130 2427816 24278 2919217 29192 3410618 34106 3925419 39254 4931620 49316 infinite


RAS06-PRACH example, RNC, 2 weeks data

0

100000

200000

300000

400000

500000

600000

0.00%

20.00%

40.00%

60.00%

80.00%

100.00%

120.00%

average

CDF

Main Distance 468-936 m


RAS06-PRACH example, WCEL, one day

0

50

100

150

200

250

300

350

400

450

PRACH_DELAY_CLASS_12









Class 14: 14.5 km-20km

Sorted by Class12


Extended cell

Counter id Counter name Distance [meters]M1006C128 PRACH_DELAY_CLASS_0 0...234M1006C129 PRACH_DELAY_CLASS_1 234...468M1006C130 PRACH_DELAY_CLASS_2 468...936M1006C131 PRACH_DELAY_CLASS_3 936...1170M1006C132 PRACH_DELAY_CLASS_4 1170...1638M1006C133 PRACH_DELAY_CLASS_5 1638...2106M1006C134 PRACH_DELAY_CLASS_6 2106...3042M1006C135 PRACH_DELAY_CLASS_7 3042...3978M1006C136 PRACH_DELAY_CLASS_8 3978...4914M1006C137 PRACH_DELAY_CLASS_9 4914...6084M1006C138 PRACH_DELAY_CLASS_10 6084...7020M1006C139 PRACH_DELAY_CLASS_11 7020...7956M1006C140 PRACH_DELAY_CLASS_12 7956...10062M1006C141 PRACH_DELAY_CLASS_13 10062...14976M1006C142 PRACH_DELAY_CLASS_14 14976...19890M1006C143 PRACH_DELAY_CLASS_15 19890...25038M1006C144 PRACH_DELAY_CLASS_16 25038...29952M1006C145 PRACH_DELAY_CLASS_17 29952...34866M1006C146 PRACH_DELAY_CLASS_18 34866...40014M1006C147 PRACH_DELAY_CLASS_19 40014...50076M1006C148 PRACH_DELAY_CLASS_20 greater than 50076

• Feature "RAN1127: Extended Cell (180 km)" extends the theoretical maximum cell range from 20 km to 180 km

• New counters in RRC measurements (M1006) can be used to evaluate how far UEs are from the cell


Content









E-NAPS to be used with AutoDef measurements• The NAPS tool has been unofficially modified to support the use of the

RAS5.1 Autodef statistics for 3G-2G and 3G-3G

• Site location info included also

• Tool uses a set of macros which requires configuration files to be present in the required directory on the local drive.


E-NAPS- Process

1. Import cell data (2G/3G) in the right format• Based on Planeditor mdB & Excel

2. Import KPI Data in the right format• Based on AutoDef measurements

3. Analyze the results• 3G->2G ISHO, defined and not defined

• 3G ->3G SHO, defined and not defined


E-NAPS Files configuration

• The below figure show the files needed to run the tool fully. If site location data or 2G datafill parameters are not needed, then NAPS_2G.xls, NAPS_3G.xls and c_bts.txt can be omitted.


E-NAPS Database & Process

• The results will go to C:\Users\NAPS_out.xls

1

23

45

6


E-NAPS- output example –missing ADJS

RncId WBTSId CId AdjsRNCidAdjsWBTSId AdjsCI Distance HOs HOsTotal HOsShare Success_RateDefined AdjgCount AdjsCount AdjTotal5 13507 13509 4 11360 11362 1913 9236 23111 0.399636537 99.85 No 15 7 224 13033 13035 6 11236 11237 1184 434 1475 0.294237288 100.00 No 12 9 213 13261 13262 4 11735 11736 1156 15540 70754 0.219634226 99.92 No 19 15 345 10995 10997 5 11994 11995 2955 3652 18614 0.196196411 99.95 No 15 8 233 11886 11886 6 12012 12012 3975 3596 18429 0.195127245 100.00 No 13 11 245 46078 46079 5 46078 46080 0 6578 35369 0.185982075 99.95 No 16 7 236 45206 45206 6 13899 13899 98 3554 19426 0.182950685 99.92 No 6 5 114 11779 11781 4 10000 10000 2747 3274 17992 0.181969764 99.73 No 19 10 294 13753 13753 4 11940 11941 1958 377 2168 0.173892989 100.00 No 13 7 205 11631 11633 4 10000 10002 1675 37784 220934 0.171019399 99.79 No 27 11 386 45220 45637 6 11190 11192 1230 1903 11951 0.159233537 99.32 No 9 10 194 13119 13120 5 46091 46093 3473 510 3241 0.15735884 100.00 No 14 13 274 11448 11450 4 12289 12293 390 13802 92393 0.149383611 99.98 No 11 11 226 13333 13333 6 10044 10046 373 2607 17553 0.14852162 99.92 No 9 14 236 10370 10374 6 11320 11321 1642 3459 23440 0.147568259 100.00 No 8 11 193 11892 11892 6 12012 12012 4093 6528 44297 0.147368896 99.72 No 20 17 374 13667 13669 4 11962 11964 939 2905 20060 0.144815553 99.90 No 13 7 204 11694 11694 4 10556 10558 447 3003 21038 0.142741705 100.00 No 13 10 234 46400 46401 4 11991 11992 1819 529 4005 0.132084894 100.00 No 12 14 265 13182 13184 5 12355 12357 897 1727 13901 0.124235666 99.94 No 16 9 25

Still room in ADJx

SHARE from all

SHOs in the cell


ENAPS- output example –missing ADJG

RncId LAC WBTSId LcrId CId AdjgLAC AdjgCI Distance HOs HOsTotal HOsShare Success_RateDefined AdjgCount AdjsCount AdjTotal6 29000 13944 1 13944 9000 15987 79 57 120 0.48 96.49 No 8 7 155 29009 11651 2 11652 9115 2281 999 130 289 0.45 99.23 No 10 14 246 29007 11238 2 11239 9006 35764 15 114 292 0.39 98.25 No 3 22 256 29006 12381 1 12381 9006 297 0 122 329 0.37 99.18 No 3 10 136 29006 45220 2 45637 9006 15425 267 173 487 0.36 99.42 No 9 10 195 8888 45277 3 45279 9115 55 3349 513 1549 0.33 99.81 No 11 9 206 29006 12181 3 12183 9005 15289 0 70 214 0.33 94.29 No 9 18 274 29110 45338 2 46309 9110 64249 911 248 761 0.33 96.37 No 9 13 224 29005 11697 2 11698 9110 214 410 146 457 0.32 98.63 No 4 22 266 29000 10578 1 10578 9000 40998 0 302 977 0.31 97.35 No 8 13 214 29110 45338 3 46310 9110 64249 911 311 1025 0.30 93.89 No 7 9 164 29005 11270 2 11271 9110 63220 476 61 202 0.30 100.00 No 5 19 243 29008 13324 1 13324 9008 8228 0 190 640 0.30 100.00 No 20 18 384 29111 13198 1 13198 9114 16196 383 204 703 0.29 100.00 No 14 15 294 29120 10563 1 10563 9120 62022 948 396 1395 0.28 99.24 No 8 10 184 29007 10082 1 10082 9121 62006 521 134 478 0.28 98.51 No 4 19 236 29000 46302 1 46302 9000 16849 0 176 633 0.28 99.43 No 5 11 166 29006 13333 1 13333 9005 62033 373 113 415 0.27 97.35 No 9 14 236 29006 11469 2 11470 9005 62033 1153 608 2238 0.27 98.36 No 9 25 344 29113 10561 1 10561 9114 39606 2486 47 179 0.26 97.87 No 11 15 26

Ordered with

SHO share

Date post:	16-Apr-2015
Category:	Documents
Upload:	chaitanya-prasad
View:	175 times
Download:	11 times

RANOP2 Module3 Neighbour&RF Optimization RAS06

Documents