Beruflich Dokumente
Kultur Dokumente
3G Paging
There are 5 TMSI per TTI (10 ms), with assume that
concurrent user for paging is maximum 5, that
means only have 5 channel in one time that can be
use simultaneusly.
So, with erlang table 5 channel GoS 1% is
around 1,36 Erlang, maksimum occupancy = 1.36 /
5 = 27.22 %
For hourly, that mean if occupancy can reach 100%,
the attempt is 3600 s *5 TMSI / 10 ms =
3600*5*1000/10 = 1.800.000 per hour
27.22% * 1.800.000 is 500.000 paging per hour
3G Paging
Why Paging Utilization<100% but with Paging Congestion?
Paging Channel Specification
PCH channel support maximum paging 5 user with 1 TTI(Transmission Time Interval, 1TTI=10ms)
Maximum
Paging 5 UE
per TTI
Paging Discard
Statistic
Period
Because the paging attempt is not stable within the statistic period, some times is higher,
some times is lower, so we will face the paging congestion while the PCH
Utilization<100% .
3G Paging
How big the PCH utilization will trigger paging congestion
Base on the Erlang B Table, if the Number of Channel is 5, and the GOS is 1%, it can bear
1.361 Erl traffic, in other words, the utilization is 27.22% (=1.361/5) while the GOS=1%
The PCH channel can support paging 5 user within 1 TTI,
We can assume the Number of Channel of 5, base on Erlang B table, when the the
utilization just 27.22%, GOS/Congestion Rate=1%.
3G Paging
Why there are some RNC with high Paging
attempt but Low Congestion Compare with
Other RNC?
Because there is parameter setting that allow
RNC to re-transmit paging
RNC will just increase the counter paging
congestion if the both 1st and 2nd time paging
discard due to PCH Channel congested.
3G Paging
When we do RAC or LAC Splitting
When Paging Attempt LAC-RAC > 500 K
When Paging Congestion >= 1 %
3G Power
The TCP consumption are break down to CCH, FACH, PCH, RRC, AMR, PS R99, HSDPA
signaling and HSUPA DL channel. RNC TBS Metro result as below:
Region Name
RNCID
CCH
Load
Y
S
M
T
W
353
354
625
164
154
35.12%
39.02%
30.48%
34.74%
35.54%
FACH
Load
4.89%
4.56%
5.66%
14.71%
14.00%
4.52%
3.90%
5.60%
2.22%
2.39%
2.53%
2.37%
2.85%
3.85%
3.67%
PS R99
Load
3.32%
6.67%
3.07%
4.42%
3.98%
HSDPA
HSUPA
HSDPA
Sig Load DL Load User Load
21.28%
17.85%
23.61%
17.87%
19.03%
1.08%
0.90%
1.76%
1.84%
1.77%
HSDPA user part and HSDPA Signaling part consume about 45% of total
used power, while CS just consume 3% power.
25.77%
23.36%
25.97%
19.25%
18.28%
Total TCP
Utility
Ratio
49.60%
42.39%
57.01%
53.73%
54.18%
3G Power
Single User Power Consumption VS Coverage / Load
25.00%
20.00%
15.00%
10.00%
5.00%
-116
-113
-110
-107
-104
-101
-98
-95
-92
-89
-86
-83
-80
-77
-74
-71
-68
-65
-62
-59
-56
-53
-50
-47
-44
-41
0.00%
AMR_Load0.5
AMR_Load0.6
AMR_Load0.9
AMR_Load0.8
Conclusion:
Power consumption per user / connection will be much higher
when coverage is poor.
3G Power
95
90
85
80
75
70
65
60
55
50
45
40
35
30
25
0
10
15
20
25
V S.HSDPA .UE.Mean.Cell
R99TCP
30
35
40
TatalTCP
Conclusion :
When HSDPA user reach 20, total Power utilization will reach 70%
Major factor of power utilization is HSDPA user number.
45
3G CE
Hardware channel requirement per traffic channel is a function of bit rate
RAB
Traffic Class
AMR Speech
AMR Speech
AMR Speech
AMR Speech
AMR Speech
AMR Speech
AMR Speech
Packet
Packet
Packet
Packet
Packet
Packet
UDI
Streaming
Streaming
Conversational
Conversational
Conversational
Conversational
Conversational
Conversational
Conversational
Interactive / Background
Interactive / Background
Interactive / Background
Interactive / Background
Interactive / Background
Interactive / Background
Conversational
Streaming
Streaming
1.2
7.95
5.9
4.75
12.65
8.85
6.65
16
32
64
128
256
384
64
57.6
14.4
SF
UL
64
64
64
64
64
64
64
64
32
16
8
4
4
16
16
64
DL
128
128
128
128
128
128
128
128
64
32
16
8
8
32
32
128
Req CE/Connection
RU20/RU30
UL
DL
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
2
4
4
4
4
8
8
16
16
4
4
4
4
1
1
3G CE
HSDPA may or may not need CE, depend on NodeB version and specific per
vendor
3G Code
Users are separated by codes (code channels), not by frequency or time
(in some capacity/hierarchical cell structure cases, also different
carrier frequencies may be used).
Freq. 1
3G Code
DL SC allocation is done by RNP
other codes are allocated by system
Usage
3G Code
Hierarchical selection of short codes from a "code tree" to maintain orthogonality
Several long scrambling codes can be used within one sector to avoid shortage of short
code
3G Code
Orthogonality is a measure of how transparent one code channel is to other code
channels. OSVF codes are completely orthogonal when time synchronised.
Multi-path delay spread introduces non-synchronised components. Delay spread is small
within micro/indoor environment relative to an outdoor environment resulting in a greater
orthogonality
Orthogonality impacts downlink capacity
Orthogonality has been evaluated by simulation of delay spread propagation channels
Scrambling codes are not orthogonal to one another i.e. inter-cell interference does not
benefit from orthogonality
Introducing a secondary scrambling code e.g. for capacity reasons, has an impact upon
orthogonality
Orthogonality is part of the RNC data build
RNC Load
The most important parameter to be monitored in RNC
in processor load :
Quiz
Average CE Utilization in a Node B : 85% for DL and 90
% for UL. This condition cause low accessibility.
Hardware capacity Node B : 512 DL CE and 384 UL CE.
Node B has 512 DL CE licenses and 512 UL CE licenses.
Based on study, call will be rejected if average CE
Utilization >= 70%.
As Capacity Engineer what should we suggest ?
Quiz
Many customers complaining slow throughput when
they download a file. After investigation we found that
IuB, CE, power and code utilization is still below 50%.
Average Ec/Io in that area is -12.
As capacity engineer what else that we need to check ?
19