Transcript RNO Wind

RNO Wind
Part I
Confidential
1
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
Part I - Content
Active set usage
Adjs Optimization
Pollution
Pollution Identification
Accessibility
Downlink and Uplink Admission Control algorithm (not enough radio or transport resource, UEBTS synchronization problems) and Congestion
Confidential
2
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
Active Set Usage
Confidential
3
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
Active Set Usage
M1013
(These counters are referred to cell addition and cell replacement – no target for deletion)
Absolute Value must be considered not Failure Rate!
Confidential
4
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
Active Set Usage
Minor
Major
High # outgoing
attempts?
Unbalanced ADJS
Yes
No Adjs
Yes
Failure ADJS
Yes
Zero
attempts?
Low used Adjs
High # outgoing fails for a
defined ADJS?
In – out
pairs?
High #
attempts for
a source?
Yes
Yes
High # fails for a
source?
Failure WCEL
Yes
Minor
Ping-Pong
Unbalanced WCEL
Filtering over attempts must be taken into count that:
- statistical data must stabilized over time.
- traffic distribution is not considered and a double-check to localize the
event and DT feedback is required to understand if fenomena is traffic
driven or cell dependent
Confidential
5
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
Filtering over failure in absolute terms it is possible to find
the major critical events
Active Set Usage
Filtering criteria:
Major
- High number of failures for a defined out-going adjs (failure ADJS)
- high number of fail for a defined source (failure WCEL)
Minor
- high number of attempts in-comig and out-going for a defined pair with occasional failure
(ping-pong)
Filtering action are required to find bi-lateral corrispondence
- very low number of attempt with failure (low used adjs)
- zero number of attempt for declared adjs– stabilized value (no adjs)
- high number of attempts with occsional failure for an out-going adjs (unbalanced ADJS)
Either in-coming or out-going condition is sufficient
- high number of attempts with occsional failure for a defined source (unbalanced WCEL)
Confidential
6
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
Failure ADJS
Source_cell_A
Source_cell_B
…
Source_cell_Z
Target_cell_A
Attempt
Fail
2
1
1
0
322
Target_cell_B
Attempt
Fail
23
1
11
0
54
15
Target_cell_C
Attempt
Fail
442
34
53
25
0
2
Failure ADJS
Analyze RSCP from DT &
NWP coverage plot
considering inter-site
distance
Yes
Down tilt
possibile?
Target_cell_Z
Attempt
Fail
4
0
345
0
12
0
Once anlyzed the RSCP, the
coverage plot taking care to
the evaluation of intersitedistance, it is easy to
understand if target can be
used.
Very low value of
RSCP that not allow
the adjs to be used
Target act
as polluter?
0
…
Yes
If not only down tilt is possible
or DERR (ADJS object
Paremeter) cell to avoid the
failure during SHO.
Down tilt must be carefully
anlyzed.
Analyze Ec/No from DT
DERR cell
Ec/No offset
Confidential
7
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
Down tilt
If from Ec/No the cell can be
recovered an individual offset
or filtering (ADJS object
Parameter) can be introduced
to fovourite it
Failure ADJS – Individual Ncell Offset
Ec/Io
P CPICH 1
Reporting
Range
AdjsEcNoOffset
to modify measurement
reporting behaviour.
Effectively 'moves' cell
border (shrinks or
enlarges cell)
P CPICH 2
Enlarging Cell 3 by x dB
P CPICH 3
time
Reporting
Event 1B
Reporting
Event 1A
Confidential
8
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
Failure ADJS – Forbidding Neighbour Cell
Ec/Io
P CPICH 1
Reportin
g Range
P CPICH 2
PCPICH3 is forbidden to
affect the reporting range as
its quality is quite unstable.
AdjsDERR
to forbid a cell from reporting
range calculation in some
instances
P CPICH 3
Time
Confidential
9
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
Failure WCEL
Source_cell_A
Source_cell_B
…
Source_cell_Z
Failure WCEL
Target_cell_A
Attempt
Fail
2
1
1
0
322
1
Target_cell_B
Attempt
Fail
23
15
11
0
15
0
Target_cell_C
Attempt
Fail
442
34
53
0
2
…
Target_cell_Z
Attempt
Fail
124
23
345
0
0
12
0
Most ofThe
thefollowing
Target failure
during
the of
1Aattempts
or 1C event.
gives the
number
per event
Analyze Ec/No &BLER
from DT & NWP coverage
plot considering inter-site
distance
RT Services
KPI(1) = M1007C10 CELL ADD_REQUEST ON SHO FOR RT
TRAFFIC
KPI(2) = M1007C12 CELL REPL_ REQUEST ON SHO FOR RT
TRAFFIC
Yes
WCEL
polluted/interfered?
Pollution/Interference
NRT Services
KPI(1) = M1007C27 CELL ADD_ REQUEST ON SHO FOR NRT
TRAFFIC
KPI(2) = M1007C29 CELL REPL_REQUEST ON SHO FOR NRT
TRAFFIC
Once anlyzed the Ec/No, BLER, the coverage plot taking care to the
evaluation of intersite-distance, it is easy to understand if the WCEL is
interferered/Polluted
Analyze Ec/No from DT
Yes
KPI(1) ?
Tune 1A
If not, two KPIs allow to separate the dominant contribute among the 1A
and 1C.
Relaxing the parameters an improvement should be achieved
The failure rate for all the procedure can be estimated as well
ADD(REPL)_ FAIL_ONSHO _FOR_x / ADD(REPL)_REQ_ON_SHO_FOR_x +
ADD(REPL)_ FAIL_ONSHO _FOR_x
Yes
KPI(2) ?
Tune 1C
M1007C14 / M1007C12 + M1007C14
M1007C36 /M1007C11 + M1007C36
M1007C30 / M1007C27 + M1007C30
M1007C37 / M1007C28 + M1007C37
M1007C31 / M1007C29 + M1007C31
Confidential
10
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
Failure WCEL - 1A
ActiveSetWeightingCoefficient
is used to weight either the
measurement result of the best active
set cell (0) or the sum of measurement
results of all active set cells (<>0)
Ec/Io
Strongest CPICH in AS:
AdditionWindow
determines the relative
threshold used by the
UE to calculate the
reporting range of
event 1A. The threshold
is either relative to the
CPICH Ec/No
measurement result of
the best active set cell
(0), or to the sum of
active set measurement
P CPICH 3
results (<>0)
P CPICH 2
1A
AdditionTime
defines the 'time-totrigger' interval
between the cell
entering the reporting
range and the UE
sending the
measurement report
to the RNC with the
1A event
Measurement
Report
Confidential
11
© Nokia Siemens Networks
no
Add to
the AS?
RNC
RNO / Wind 17/10/2007 - NMI
P CPICH 1
AdditionReportingInterval
defines the period of time that the
UE wait, if the RNC is unable to
add Ncell to AS, before sending
further reports periodically, with
interval
AdditionReportingInterval, until
the Ncell moves out of reporting
range, or RNC adds Ncell to AS.
time
Failure WCEL - 1C
ReplacementWindow
AS has 3 cells
Ec/Io
determines the margin by which the CPICH Ec/No
measurement result of the monitored cell (MNew) must
exceed the CPICH Ec/No measurement result of the an
active set cell (MInAS) before the UE can send the event
1C triggered Measurement Report to the RNC: MNew >=
MInAs + ReplacementWindow / 2
P CPICH 1
P CPICH 2
P CPICH 4
1C
P CPICH 3
weakest CPICH in AS
ReplacementTime
Defines the period of time the monitored cell
must continuously stay within the reporting
range before the UE can send a Measurement
Report to the RNC in order to replace an active
set cell with the monitored cell (event 1C).
time
ReplacementReportingInterval
If the RNC is not able to replace the active
cell with the monitored cell, the UE continues
reporting after the initial report by reverting to
periodical measurement reporting. The
parameter Replacement Reporting Interval
determines the interval of periodical
measurement reports when such reporting is
triggered by the event 1C.
no
Measurement
Report
AS
update?
RNC
Confidential
12
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
NO ADJS
Source_cell_A
Source_cell_B
…
Source_cell_Z
Target_cell_A
Attempt
Fail
2
1
0
322
1
Target_cell_B
Attempt
Fail
0
11
0
15
0
Target_cell_C
Attempt
Fail
442
34
53
0
2
0
…
Target_cell_Z
Attempt
Fail
124
23
345
0
12
0
No Adjs
Zero
attempts?
Repeat Analysis
Yes
Statistic data must be stabilized before decide to
remove it and DT analysis can help n estimating the
amount of residual noise if down tilt is not possible
Statistic
Stable?
Yes
DT analysis for the Adjs
Remove ADJS
Confidential
13
© Nokia Siemens Networks
Comparing the ADJS plan provisioned into the
network with the M1013 matrix, it is easy to find if one
declared ADJS is not used (not present in the list)
RNO / Wind 17/10/2007 - NMI
Low used ADJS
Low used Adjs
Source_cell_A
Source_cell_B
…
Source_cell_Z
Target_cell_A
Attempt
Fail
2
1
245
23
322
1
Target_cell_B
Attempt
Fail
25
4
11
0
3
Target_cell_C
Attempt
Fail
442
34
53
0
1
2
1
…
Target_cell_Z
Attempt
Fail
124
23
345
0
123
Analyze DT
result and
NWP data
It is not difficult in live network to find some pair
working with very low
Yes
ADJ Offset
For low used ADJS has to be intended and ADJS that
has few number of attemps in one day (e.g <3)
Monitored Qual
from DT
acceptable?
with occasional failure.
Alter. ADJS
present?
The ADJS removal has to be considered as the last
option, after the quality has been monitored by drive
test result, considering the overall capability of the
target to be recovered (e.g. inter-site distance, power
budget) and other options are available for that area.
Yes
Interference
evaluation
Remove ADJS
Confidential
14
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
Statistic data must be stabilized before decide to
remove it and DT analysis can help in estimating the
amount of residual noise if down tilt is not possible
20
Unbalanced ADJS
Source_cell_A
Source_cell_B
…
Source_cell_Z
Unbalance ADJS
Target_cell_A
Attempt
Fail
54
3
25
1
32
2
Analyze RSCP from DT & NWP
coverage plot considering intersite distance e traffic
distribution
No action
required
Yes
Down tilt
possibile?
DERR cell
Ec/No offset
Confidential
15
© Nokia Siemens Networks
45
…
Target_cell_Z
Attempt
Fail
124
5
2
The key point is the inviduation of the
attempt distribution, that in case are not
justified but partcualar populated area,
coluld generate lot of signalling.
Yes
Analyze Ec/No from DT
& evaluate unbalance
Target_cell_C
Attempt
Fail
23
1
137
3
An high number of attempt could be an
indication of a problem and even in case of
the failure is not associated an evaluation
is required.
Attempt over
the same UE?
Target act
as polluter?
Target_cell_B
Attempt
Fail
345
10
11
0
RNO / Wind 17/10/2007 - NMI
Yes
Down tilt
The attempts could be genarated by 1B
event ever the same UE not counted in the
M1013.
The possibility to recover the ADJS is the
favourite option and the down tilt carefully
analyzed considering the failure
associated.
Unbalanced WCEL
Unbalanced WCEL
Source_cell_A
Source_cell_B
…
Source_cell_Z
Analyze RSCP from DT & NWP
coverage plot considering
inter-site distance and traffic
distribution
Attempt over
the same UE?
No action
required
Yes
Yes
Interference /
pollution
WCEL interfered
polluted?
Target_cell_A
Attempt
Fail
543
13
25
1
32
2
Target_cell_B
Attempt
Fail
345
10
11
0
Target_cell_C
Attempt
Fail
876
7
137
3
45
…
Target_cell_Z
Attempt
Fail
124
5
2
An high number of attempt could be an
indication of a problem and even in case of the
failure is not associated an evaluation is
required.
The key point is the inviduation of the attempt
distribution, that in case are not justified but
partcular populated area, coluld generate lot of
signalling.
The attempts could be genarated by 1B event
ever the same UE not counted in the M1013.
Analyze Ec/No from DT
The possibility to have an interference/pollution
increase respect to the unbalanced ADJS.
The optimization should be performed at WCEL
level
Yes
KPI(1) ?
Tune 1A
Yes
KPI(2) ?
Tune 1C
Confidential
16
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
The KPI reported are the same of Failure
WCEL
Ping Pong
Down tilt
DERR cell
Ping-pong
Yes
pollution
32
No action
required
Attempt from
the same UE?
Yes
Filtering
Comparable
value?
Yes
Histeresys
using
Confidential
© Nokia Siemens Networks
45
…
Target_cell_Z
Attempt
Fail
124
5
2
RNO / Wind 17/10/2007 - NMI
In this particular case the high number
of attempt is concentrated in a pair
As in the previous case could be an
indication of a problem and even in
case of the failure is not associated an
evaluation is required to avoid to use a
lot signalling.
One of them act
as polluter?
Ec/NoOffset
on the pair
17
Target_cell_C
Attempt
Fail
23
1
137
3
From A >> B and from B >>A as in the
picture
Analyze Ec/No from DT
Not stable,
Fading?
2
Target_cell_B
Attempt
Fail
345
10
11
0
Down tilt
possibile?
Yes
Analyze RSCP from DT &
NWP coverage plot
considering inter-site
distance
Source_cell_A
Source_cell_B
…
Source_cell_Z
Target_cell_A
Attempt
Fail
54
3
987
13
The optimization should be performed
at ADJS level considering that the
filtering option could get to smoother
measured value
Ping Pong - Filtering
EcNoFilterCoefficient
EcNoAveragingWindow
Applied for averaging of
periodical meas. reports
I am in the
CELL_DCH substate
System Information [ ]
Measurement Control [ ]
UE
Measurement Type: Intra-frequency measurements
Reporting events:
1A: Event 1A triggered when CPCIH Ec/Io of the measured cell enters
UE
reporting range for a defined period of time
1B: Event 1B triggered when CPICH EC/I0 of the measured cell drops
out
of the UE reporting range for a defined period of time
1C: Event 1C triggered when CPICH EC/IO of the measured cell enter
in
AS by a defined margin for a defined period of time
Confidential
18
© Nokia Siemens Networks
UTRAN
RNO / Wind 17/10/2007 - NMI
Node B
RNC
Ec/NoFilterCoeff
controls the higher layer filtering of
physical layer measurements before the
event evaluation and measurement
reporting is performed by the UE.
Pollution
Confidential
19
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
Polluter Detection
The best way to individuate a Polluter is the Drive Test
A feedback can come from coverage plot, RNP feedback and Counters
A polluter can be of different type:
1.
PSC Pollution
Too high reuse factor for the PSC. New PSC plan is required
2.
DL Noise raise
ADJS signal strength out of usage window (will be never utilized by the UE)
A down tilt or power reduction is the solution evaluating all the side effects
3.
Dominant site
A dominant site over-shooting the ADJ becoming congested
A down tilt or power reduction is the solution evaluating all the side effects
Confidential
20
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
PSC Pollution
A confirm for the polluter of the first type can come from the counter
M1007C38-47 CELL SPECIFIC CPICH EC/NO - CLASS x
Pollution Criteria:
The M1007C38-47 gives an indication of Ec/No distribution value measured during event 1A .
Having the distribution higly unbalanced (normally centered on class 2, 3, 4) we have an
indication of a probable problem. For example unbalancing towards the scarce vaue of Ec/No
but continuing to add cells to AS could give an indication of pollution
High number
of class0-3?
Yes
Not Polluted WCEL
High number of
class>6?
Yes
Polluted WCEL
Confidential
21
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
Isolated/unavailable
WCEL
DL Noise Raise
Source_cell_A
Source_cell_B
…
Source_cell_Z
Target_cell_A
Attempt
Fail
2
1
245
23
322
1
Target_cell_B
Attempt
Fail
25
4
11
0
3
1
Target_cell_C
Attempt
Fail
0
53
0
0
-
…
Target_cell_Z
Attempt
Fail
124
23
345
0
123
20
The NO ADJS and low used ADJS criteria before presented can give a confirm for a
pollution of this type.
After the statistical data are stabilized, making across-check with the provisioned ADJS
Plan the probable polluters are individuated.
This is obviously a cautelative estimation to be integrated and confirmed by drive test
results
Confidential
22
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
Dominant site
Source_cell_A
Source_cell_B
…
Source_cell_Z
Target_cell_A
Attempt
Fail
2
1
245
23
Target_cell_B
Attempt
Fail
25
4
11
0
Target_cell_C
Attempt
Fail
26
3
53
0
…
…
245
45
…
Target_cell_Z
Attempt
Fail
124
23
Filtering the M1013 pairs for the recurrent target cell with associated occasional failure we
have an estimation of the probable polluters
For the polluters, originating failures a down tilt is required
Polluted Cell Criteria:
SHO over head can give a soft help in individuating cell where polluter/overshooting site
can be present or where unbalanced cell criteria could apply
Soft HandoverOverhead RNC_79B
 M1007C0ONE_CELL_IN_ACT _SET _RT  M1007C19ONE_CELL_IN_ACT _SET _NRT



N_ACT _SET _RT  M1007C20T WO_CELL_I
N_ACT _SET _NRT   2 
 M1007C1T WO_CELL_I

 M1007C2T HREE_CELL_IN_ACT _SET _RT M1007C21T HREE_CELL_IN_ACT _SET _NRT  3 

 1 100%
 M1007C0ONE_CELL_IN_ACT _SET _RT  M1007C19ONE_CELL_IN_ACT _SET _NRT



N_ACT _SET _RT  M1007C20T WO_CELL_I
N_ACT _SET _NRT 
 M1007C1T WO_CELL_I

 M1007C2T HREE_CELL_IN_ACT _SET _RT M1007C21T HREE_CELL_IN_ACT _SET _NRT



Confidential
23
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
Accessibility
Confidential
24
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
Accessibility
If LOW accessibility RRC from:
•
Accessibility Statistical Counters
•
DRIVE TEST
Specific counter for Resource monitoring can be evaluated:
1. RRC_CONN_STP_FAIL_AC/RRC_CONN_STP_FAIL_all >> UL/DL Cell Load & code
allocation
2. RRC_CONN_STP_FAIL_BTS/ RRC_CONN_STP_FAIL_all >> CE usage
3. RRC_CONN_STP_FAIL_TRANS/ RRC_CONN_STP_FAIL_all >> CAC rej or AAL2 setting up
fail
4. RRC SETUP FAIL DUE TO IUB AAL2 TRANS / RRC_CONN_STP_FAIL_all >> AAL2
shortage
5. RRC CONN SETUP FAIL DUE TO RNTI ALLO FAIL / RRC_CONN_STP_FAIL_all >> RRMU
overload
Could be useful for congestion detection to not neglect the analysis of failure in access
phase with cause RADIO
RRC_CONN_ACC_FAIL_RADIO/RRC_SETUP_COMP (Sync) >> UL/DL Cell Load and
coverage plot
Confidential
25
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
RRC Accessibility
RRC FAIL AC
RRC fail from
DT & Statistic
If the condition triggered is
RRC_CONN_STP_FAIL_AC the power analysis
is required either Tx or Rx and code availability
Radio
Congestion
Yes
Yes
If the thresholds are correctly settled but the cell
seems to be congested according to the class3
and class4 permanence time a cross check on
the effective traffic present is required.
Yes
KPI(1)?
RRC fail AC?
CE Congestion
Interference et al.
Some interferer can be discovered by the drive
test result.
Otherwise an expansion must be considered
Yes
Yes
RRC fail BTS?
KPI(2)?
RRC Fail BTS
HW problem et al.
RL rejection from BTS sending a NBAP: RL
Setup Failure.
Old counters M1005 are replaced by the one
created for 3GGP Iub
RRC fail Trans?
Iub not Congested
AAl2 Congestion
WSP expansion or new site is required
Yes
Yes
Iub Congestion
RRC fail AAL2?
Confidential
26
© Nokia Siemens Networks
The most important cause for RNO included in
is the lack of CE
RNO / Wind 17/10/2007 - NMI
RRC Accessibility – AC Congestion
PRXTOT _ DENOM _ X
100%
 PRXTOT _ DENOM _ k
Uplink Cell load
k  All _ Classes
PTXTOT _ DENOM _ X
100%
 PTXTOT _ DENOM _ k
Downlink Cell load
k  All _ Classes
256
 NO _ CODES _ AVAILABLE_ SFx
Code blocking
x4
NBR _ SUCC _ CODE _ TREE _ ALLO 
KPI (1)
100%
256
 NO _ CODES _ AVAILABLE_ SFx
x4
Average Code Tree Occupancy
RNC_113a
Confidential
27
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
 CODE_CAPACITY
 DENOM_CODE_CAPACITY
100%
RRC Accessibility – BTS Congestion
RNC_730A AverageRatio of utilised CE for DL in BTS 
CE Usage
RNC_731A AverageRatio of utilised CE for UL in BTS 
Confidential
28
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
M5001C7 AVG_USED_CE_DL
M5001C2AVE_AVAIL_CE
M5001C8AVG_USED_CE_UL
M5001C2AVE_AVAIL_CE
KPI (2)
RAB Accessibility
If Low accessibility RAB from:
•
DUETTO
•
DRIVE TEST
Considering that after RANAP: Rab Assignment Request from Core a double check is
requested.
Due to DCH0/0 allocation more significant are CS for AC and BTS fail cause and PS for
TRANS
after reconfiguration
PS services that can suffer more the following cases can be evaluated:
CS
1.
RAB SETUP FAILURES DUE TO AC
PS
1.
RAB SETUP FAILURES DUE TO BTS
2.
RAB SETUP FAILURES DUE TO TRANSPORT (AAL2)
3.
RAB SETUP FAILURES DUE TO IUB AAL2 TRANS
Confidential
29
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI
RAB Accessibility
When a RRC Fail TRANS is triggered a KPI for CAC rej & AAL2setup failure can be
useful to evaluate the failure rate
P S Iub Reserv Failure ratedue to CAC 
M1001C106RAB_ST P_FAIL_PS_INETR_T RANS M1001C111RAB_ST P_FAIL_PS_BACKG_T RANS
(M1002C150)ALLO_PS_INT ERA_8_DL
_IN_SRNC (M1002C151)ALLO_PS_INT ERA_16_D
L_IN_SRNC
(M1002C152)ALLO_PS_INT ERA_32_D
L_IN_SRNC (M1002C153)ALLO_PS_INT ERA_64_D
L_IN_SRNC
(M1002C154)ALLO_PS_INT ERA_128_
DL_IN_SRNC (M1002C155)ALLO_PS_INT ERA_256_
DL_IN_SRNC
(M1002C156)ALLO_PS_INT ERA_320_
DL_IN_SRNC (M1002C157)ALLO_PS_INT ERA_384_
DL_IN_SRNC
(M1002C166)ALLO_PS_BACKG_8_DL_IN_SRNC  (M1002C167)ALLO_PS_BACKG_16_DL_IN_SRNC
(M1002C168)ALLO_PS_BACKG_32_DL_IN_SRNC (M1002C169)ALLO_PS_BACKG_64_DL_IN_SRNC
(M1002C170)ALLO_PS_BACKG_128_DL_IN_SRNC (M1002C171)ALLO_PS_BACKG_256_DL_IN_SRNC
(M1002C172)ALLO_PS_BACKG_320_DL_IN_SRNC (M1002C173)ALLO_PS_BACKG_384_DL_IN_SRNC
(M1002C303)ALLO_FOR_DAT A_8_DL_
IN_DRNC (M1002C305)ALLO_FOR_DAT A_16_DL
_IN_DRNC
(M1002C307)ALLO_FOR_DAT A_32_DL
_IN_DRNC (M1002C310)ALLO_FOR_DAT A_64_DL
_IN_DRNC
(M1002C311)ALLO_FOR_DAT A_128_D
L_IN_DRNC (M1002C312)ALLO_FOR_DAT A_256_D
L_IN_DRNC
(M1002C313)ALLO_FOR_DAT A_320_D
L_IN_DRNC (M1002C314)ALLO_FOR_DAT A_384_D
L_IN_DRNC
Confidential
30
© Nokia Siemens Networks
RNO / Wind 17/10/2007 - NMI