The following Figures illustrate the mean and maximum channel elements
usage in Uplink and Downlink (target thresholds: 256 DL, 64 UL).
200,0000
150,0000 DL Channel Elements
usage [mean]
100,0000
DL Channel Elements
50,0000 usage [max]
0,0000
00
00
00
00
00
0
00
,0
,0
,0
,0
0,
10
20
40
80
16
Figure 27: channel elements usage, Downlink direction, voice only service
160,0000
140,0000
120,0000 UL Channel Elements
100,0000 usage [mean]
80,0000
60,0000 UL Channel Elements
40,0000 usage [max]
20,0000
0,0000
00
00
00
00
00
0
00
,0
,0
,0
,0
0,
10
20
40
80
16
Figure 28: channel elements usage, Uplink direction, voice only service
In this case, the Figure that reaches the 64 channel elements in Uplink is
within the interpolation range so the interpolation fits with similar correlation
coefficient produce a very similar Figure (therefore only the case with the
highest correlation coefficient is provided). In the case of Downlink,
98
extrapolation is used and therefore a range of values is given. The results are
summarized in the following tables.
Coefficient Data:
a= 17.6737
b= 0.8078
Coefficient Data:
a= 15.544373
b= 0.90265331
c= -0.0005
CE Uplink Target = 64 CE
a= 0.5444
b= 0.9027
c= -0.0005
1000,0000
800,0000
600,0000
Kbps
00
00
00
00
0
00
,0
,0
,0
,0
0,
10
20
40
80
16
With the current version of the Wines Simulator, it was found that the Iub
measurements are only monitored as a mean value of the amount of data
present on the Iub traffic. As in the definition of KPIs the proposal was to
monitor the Iub utilization according to the number of reserved radio bearers
(as it is currently implemented in VF-NL), then the Max. PCR (Peak Cell Rate)
was taken into account as the Iub limit which indicates congestion in the Iub.
In the next version of Wines (to be released in October 2005) the Iub
utilization based on reservation will be implemented, but as far as this study
concern, the Iub threshold is set to the Max. PCR = 2786 cells/sec * 48
bytes/cell * 8 bits/byte = 1.07 Mbps, assuming 1 E1 link between each Node
B and the RNC [Iub-observability]. The obtained results are presented in the
following table.
100
Target for Iub DL throughput = 2786 cells/sec * 48 bytes/cell * 8 bits/byte = 1.07 Mbps
Coefficient Data:
a= 3
b= 6
c= -0.0031
Coefficient Data:
a= 15.5115
b= 5.0227
This gives:
Note that in the calculation we use 30Kbps and not 12.2 because we have to
take into account the coded channel (which includes the overhead caused by
coding and protection techniques) and not just the end-user data rate.
UL Load [%]
100,0000%
90,0000%
80,0000%
UL Load [%]
70,0000%
60,0000%
50,0000% UL Load [%]
40,0000%
30,0000%
20,0000%
10,0000%
0,0000%
00
00
00
00
00
00
0
0
,0
,0
,0
,0
0,
10
20
40
80
16
Traffic Density [Erl/Km^2]
For this case, it was also proposed in the KPIs definition to measure the
RTWP and see if its level exceeds the target (given by the two Ericsson
parameters) for a time higher than the hysteresis time (defined by the
Ericsson parameter iFHyst) . That is how Uplink load is determined in the real
system. For the simulation analysis however, it was difficult to try to average
these results because congestion happens at a different times in different
cells, it was decided to work with the approach presented in [Holma, Jabber]
which is to assume a maximum Noise Rise (in dB) and then calculate the
target UL Load in terms of the uplink load factor (nul) using the following
equation:
NR [dB] = - 10 * Log (1- nul ) ( 7-6)
Where:
Assuming a Noise Rise level of 4 dBs [Holma], we get nul = 0.6 (60%) which
will be our target level for the Uplink Load. The results of the interpolation
are mentioned in the following table.
102
Target Value =
Uplink Noise Rise 0.60
Coefficient Data:
a= 0.02258
b= 0.0059
Number of Users/cell 18
Quadratic Fit:
y=a+bx+cx^2
Coefficient Data:
a= -0.0240
b= 0.0079
c= -1.20E+02
Number of Users/cell 16
Table 15: Estimation of the users per cell according to the simulation output, Uplink Noise Rise
congestion target = 60%
DL_TxPower [dBm]
38,5000
38,0000
Power [dBm]
37,5000
37,0000 DL_TxPower [dBm]
36,5000
36,0000
35,5000
00
00
00
00
00
00
0
0
,0
,0
,0
,0
0,
10
20
40
80
16
Coefficient Data:
a= 36.3788
b= 0.01140
Coefficient Data:
a= 363.747
b= 0.0116
c= -1.06E+01
104
7.1.1.6 Downlink Code Tree Usage
45,0000%
40,0000%
Code tree usage [%]
35,0000%
30,0000%
25,0000% DL_Code tree
20,0000% usage[%]
15,0000%
10,0000%
5,0000%
0,0000%
00
00
00
00
00
00
0
0
,0
,0
,0
,0
0,
10
20
40
80
16
traffic density [Erl/Km^2]
Target Level to trigger soft congestion mechanism = 60% (0.6 in linear scale)
a= 0.03858
b= 0.0023
a= 0.0320
b= 0.0026
c= -1.70E+01
Next table presents the summary with the KPI’s ordered by the traffic
densities that reach first the target level (only considering the lower values
for the number of users of each KPI, i.e. taking the most restrictive
approach):
CE UL 64 13
UL Load 60% 16
Blocking prob 1% 49
CE DL 256 51
Dropping prob 1% 62
Table 18: Ordered KPI's, voice-only service
After the analysis of the Speech service, the analysis corresponding to this
Packet Switched service is presented next.
106
Blocking probability [%]
60,0000%
50,0000%
40,0000%
30,0000% Blocked services [%]
20,0000%
10,0000%
0,0000%
00
00
00
00
00
62
25
49
7
,9
,9
1,
3,
6,
12
25
Traffic Density [Erl/Km^2]
100,0000%
80,0000%
60,0000%
%
0
00
00
00
90
70
62
25
49
,9
,9
1,
3,
6,
12
25
a) MMF Model:
y=(a*b+c*x^d)/(b+x^d)
a= -246.7280
b= 1.2024
c= 50.1275
d= 1.5127
a= -0.3167
b= 0.0975
Analyzing the results, very low Figures were found, near 1 user / cell. In
order to check the results, an analytical approach was used again, assuming
that the main limitation for packet-switched services is Downlink Power
consumption as it was shown in [Schneider-1]. According to [Holma], the
Downlink load factor is defined as:
ndl = Σ υj * (Eb/No)j / W/Rj [1-α+i], j=1 to N ( 7-7)
Where:
• N = number of users in the cell
• υj = service activity factor (for PS services assumed to be 1)
• W = chip rate = 3.84 Mchips/sec
• Rj = Data Rate of user j
• Eb/Noj = Eb/No for user j
• α = Downlink Orthogonality factor, for the formula, 1 means
maximum orthogonality (for the simulator 0.4 is used but 0
means in the simulator context full orthogonality, so for the
formula calculation a value of 0.6 is assumed)
• i = Other cell/ Own cell interference factor, assumed 0.65 for a
macro-cell scenario [Holma]
108