Beruflich Dokumente
Kultur Dokumente
=
=
=
=
=
+ =
bps hroughput MaxPagingT
bps ughput PagingThro
PagingLoad
SCCPCH of #
SCCPCH of #
bps hroughput MaxPagingT
bit ize ingRecordS AveragePag
bit ize ingRecordS AveragePag e1 fPagingTyp MaxAmountO ughput PagingThro
LA/RA the in cells among , M1006C26 LA/RA the in cells among M1006C25 e1 fPagingTyp MaxAmountO
Air Interface
This should on TB level
RN31577EN20GLA1
Paging and inter-RNC optimization
31
Soc Classification level
31 Nokia Siemens Networks RN31577EN20GLA1
Max P.T.1/sec Max PCH Throughput
2 SCCPCH
PCH Loading Estimation Process
Statistically, Paging Type1 is generated in the random manner by a lot of
subscribers, except the special case like Happy New Year call
Number of Paging Type1 generated would form Poisson distribution
Through the below flow
1 SCCPCH 8[kbps]
24[kbps]
100
300
Target PCH
Load
Averaged # of simul. Paging Type1/sec Poisson Distribution
Paging Type1=200bit
Failure Probability
Acceptable?
Failure Probability
Acceptable?
OK
NO
YES
Divide LA/RA
YES
NO
Air Interface
RN31577EN20GLA1
Paging and inter-RNC optimization
32
Soc Classification level
32 Nokia Siemens Networks RN31577EN20GLA1
PCH Loading Cumulative Poisson Distribution
Air Interface
Relation between Probability of Simultaneous "Paging Type1" and PCH Loading
Max PCH Throughput=8[kbps] / Size of Paging Type 1=80[bits]
(Poisson Distribution)
90
92
94
96
98
100
0 10 20 30 40 50 60 70 80 90 100 110 120 130 140
# of Simultaneous "PagingType1" [count/sec]
C
u
m
u
l
a
t
i
v
e
P
r
o
b
a
b
i
l
i
t
y
[
%
]
PCHLoad=10% PCHLoad=30% PCHLoad=50% PCHLoad=70% PCHLoad=80% max limit (SCCPCH=1)
When PCH load=80%, ~1.3% of P.T1 fails.
It would be good to have Practical Max PCH Load as 70%
so that simultaneous #P.T1/sec is practically less than max(=100).
NOTE: THIS IS PURELY FROM PCH POINT OF VIEW AND DOES NOT
INCLUDE THE PAGING BUFFER HANDLING ASPECT
2005/Dec/31 23:00 @RNC510
No need to have 2 SCCPCH
nor LA/RA division
Practical Max PCH Load = 70%
RN31577EN20GLA1
Paging and inter-RNC optimization
33
Soc Classification level
33 Nokia Siemens Networks RN31577EN20GLA1
PCH Loading Estimation Results
Air Interface
PCH Load @18:00
2005/Jun/01~Dec/31
PCH Throughput=8[kbps] / PagingType1=80[bits]
0.000
1.000
2.000
3.000
4.000
5.000
6.000
7.000
8.000
9.000
0
5
/
0
6
/
0
1
0
5
/
0
6
/
0
8
0
5
/
0
6
/
1
5
0
5
/
0
6
/
2
2
0
5
/
0
6
/
2
9
0
5
/
0
7
/
0
6
0
5
/
0
7
/
1
3
0
5
/
0
7
/
2
0
0
5
/
0
7
/
2
7
0
5
/
0
8
/
0
3
0
5
/
0
8
/
1
0
0
5
/
0
8
/
1
7
0
5
/
0
8
/
2
4
0
5
/
0
8
/
3
1
0
5
/
0
9
/
0
7
0
5
/
0
9
/
1
4
0
5
/
0
9
/
2
1
0
5
/
0
9
/
2
8
0
5
/
1
0
/
0
5
0
5
/
1
0
/
1
2
0
5
/
1
0
/
1
9
0
5
/
1
0
/
2
6
0
5
/
1
1
/
0
2
0
5
/
1
1
/
0
9
0
5
/
1
1
/
1
6
0
5
/
1
1
/
2
3
0
5
/
1
1
/
3
0
0
5
/
1
2
/
0
7
0
5
/
1
2
/
1
4
0
5
/
1
2
/
2
1
0
5
/
1
2
/
2
8
date
P
C
H
L
o
a
d
[
%
]
RNC501 RNC509 RNC519 RNC510
Peak hour is 18:00 and the below graph shows the PCH load @ 18:00 (hourly data)
Friday is the busiest day in the week except special events.
Increase : 4[%] in 6[month] from 4[%] to 8[%] 0.67[%/month]
But still quite difficult to forecast with non-linear approximation.
Tenjin Festival
Fireworks
@Yodo River
0.67[%/month]
RN31577EN20GLA1
Paging and inter-RNC optimization
34
Soc Classification level
34 Nokia Siemens Networks RN31577EN20GLA1
PCH Loading Conclusions
Currently, PCH Load is still only10[%] at most.
Only linear trend of PCH Load increase can be seen
4% increase during the past 6 months, from 4% to 8%
Periodical check of PCH Load is necessary but still it
will not reach the max.
Calculations about PCH load can be used to plan the LA/RA areas BUT it should be noted that
the paging buffer handling analysis should be included as well.
RN31577EN20GLA1
Paging and inter-RNC optimization
35
Soc Classification level
35 Nokia Siemens Networks RN31577EN20GLA1
Paging and inter-RNC optimization
Paging Performance in 3G
- Paging capacity improvement RU20
- Cell resource states
- Paging capacity improvement RU20
RN31577EN20GLA1
Paging and inter-RNC optimization
36
Soc Classification level
36 Nokia Siemens Networks RN31577EN20GLA1
Introduction (1/2)
24 kbps Paging Channel
Paging load/activity
- 8 kbps paging channel capacity is
implemented for (RU10)
- 24 kbps can be allocated for RU20 (ASW)
- Transport block size increase
- The stand alone 24kbps PCH is allocated on
S-CCPCH with SF128,
comparing 8 Kbps/SF256 (more PwR)
- If Paging 24 kbps is used,
maximum of available HSDPA codes are
only14
WCEL: PtxSCCPCH1
It carries a PCH or FACH (mux) or FACH
/dedicated). Spreading factor is SF64 (60 kbps)
Cch,256,0
Cch,256,1
Cch,256,2
Cch,256,3
Cch,128,4
Cch,128,5
CPICH
P-CCPCH
AICH
PICH
Cch,64,1
Cch,256,14
S-CCPCH 1
E-AGCH
HS-SCCH
E-HICH & E-RGCH
S-CCPCH 2
Cch,128,6
Cch,16,0
No HSDPA code free No HSDPA code free
Pilot coverage
S-CCPCH
setup
Paging Ch with 24 kbps Paging Ch with 24 kbps
Bottleneck is PwR Bottleneck is PwR
Not code tree allocation Not code tree allocation
(calculation on next slide) (calculation on next slide)
RN31577EN20GLA1
Paging and inter-RNC optimization
37
Soc Classification level
37 Nokia Siemens Networks RN31577EN20GLA1
Introduction (2/2)
Example: Power benchmark Example: Power benchmark
What limits first: PwR or Code tree occupation
Average HSDPA throughput hardly affected by loss of 1 code, as CQI extremely seldom
good enough for 15 codes (e.g. probability < 1 : 1000)
With SF128 PCH (24kbps) needs power 2 dB below CPICH = 31 dBm = 1.26 Watt
With SF256 PCH (8kbps) needs power 5 dB below CPICH = 28 dBm = 0.63 Watt
Power loss = 1.26 W 0.63 W = 0.63 W approx. 600 mW
3 % of 20 W max. cell power (1% = 200mW, 3% =600 mW)
5 % (600 mW) of about 12 W available for user data
8/24 kbps Paging Channel
60kbps/24kbps, cc. 1/2 60kbps/24kbps, cc. 1/2
30kbps/8kbps cc.1/2 30kbps/8kbps cc.1/2
RN31577EN20GLA1
Paging and inter-RNC optimization
38
Soc Classification level
38 Nokia Siemens Networks RN31577EN20GLA1
Logical channel
Transport channel
Physical
channel
PCCH
To support higher paging capacity, the size of transport block for PCH is increased:
If WCEL: PCH24KbpsEnabled parameter is set to enabled, the PCH transport
channel is mapped to a dedicated S-CCPCH physical channel.
8 kbps = 80 Bit / 10ms TTI (default)
PCH
SCCPC
H
Concept
24 kbps = 240 Bit / 10ms TTI (optional)
24 kbps Paging Channel
8 kbps = up to 50 8 kbps = up to 50- -75% PCH load 75% PCH load
Several Several
S S- -CCPCH possible CCPCH possible
RN31577EN20GLA1
Paging and inter-RNC optimization
39
Soc Classification level
39 Nokia Siemens Networks RN31577EN20GLA1
Transport Format Set
Transport Format Sets for the
8 kbps and 24 kbps PCH are
very similar
Only difference is the
increased transport block
size
TFS
TFS
TTI
TTI
Channel
coding
Channel
coding
CRC
CRC
8 kbps PCH
8 kbps PCH
24 kbps PCH
24 kbps PCH
0: 0x80 bits
(0 kbit/s)
1: 1x80 bits
(8 kbit/s)
0: 0x80 bits
(0 kbit/s)
1: 1x80 bits
(8 kbit/s)
0: 0x240 bits
(0 kbit/s)
1: 1x240 bits
(24 kbit/s)
0: 0x240 bits
(0 kbit/s)
1: 1x240 bits
(24 kbit/s)
10 ms
10 ms
CC 1/2
CC 1/2
16 bit
16 bit
10 ms
10 ms
CC 1/2
CC 1/2
16 bits
16 bits
RN31577EN20GLA1
Paging and inter-RNC optimization
40
Soc Classification level
40 Nokia Siemens Networks RN31577EN20GLA1
S-CCPCH Configuration 1
This configuration limits the PCH bit rate to 8 kbps
The PCH is multiplexed with the FACH-u and FACH-c
The PCH always has priority
SF64 is required to transfer the FACH-u and FACH-c bit rates
Logical channel
Transport channel
Physical channel
DTCH DCCH CCCH BCCH PCCH
FACH-u FACH-c PCH
SCCPCH 1
SF 64
U U- - user data user data C C- - control data control data
RN31577EN20GLA1
Paging and inter-RNC optimization
41
Soc Classification level
41 Nokia Siemens Networks RN31577EN20GLA1
S-CCPCH Configuration 2a
Logical channel
Transport channel
Physical channel
DTCH DCCH CCCH BCCH PCCH
FACH-u FACH-c PCH
SCCPCH 1 SCCPCH 2
SF 64 SF 256
PCH24kbpsEnabled is configured to disabled with this configuration
Limits the PCH bit rate to 8 kbps
The PCH is allocated its own S-CCPCH
SF256 is allocated to the PCH as a result of the low bit rate
RN31577EN20GLA1
Paging and inter-RNC optimization
42
Soc Classification level
42 Nokia Siemens Networks RN31577EN20GLA1
S-CCPCH Configuration 2b
Logical channel
Transport channel
Physical channel
DTCH DCCH CCCH BCCH PCCH
FACH-u FACH-c PCH
SCCPCH 1 SCCPCH 2
SF 64 SF 128
PCH24kbpsEnabled is configured to enabled with this configuration
Increases the PCH bit rate to 24 kbps
The PCH is allocated its own S-CCPCH
SF128 is allocated to the PCH to support the increased bit rate
RU 20 RU 20
24 kbps 24 kbps
RN31577EN20GLA1
Paging and inter-RNC optimization
43
Soc Classification level
43 Nokia Siemens Networks RN31577EN20GLA1
S-CCPCH Configuration 3a
PCH24kbpsEnabled is configured to disabled with this configuration
Limits the PCH bit rate to 8 kbps
The PCH is allocated its own S-CCPCH
SF256 is allocated to the PCH as a result of the low bit rate
Logical channel
Transport channel
Physical channel
DTCH DCCH CCCH BCCH CTCH
FACH-u PCH FACH-s
SCCPCH
connected
SCCPCH
idle
PCCH
FACH-c FACH-c
SCCPCH
page
SF 64 SF 128 SF 256
RN31577EN20GLA1
Paging and inter-RNC optimization
44
Soc Classification level
44 Nokia Siemens Networks RN31577EN20GLA1
S-CCPCH Configuration 3b
PCH24kbpsEnabled is configured to enabled with this configuration
Increases the PCH bit rate to 24 kbps
The PCH is allocated its own S-CCPCH
SF128 is allocated to the PCH to support the increased bit rate
Logical channel
Transport channel
Physical channel
DTCH DCCH CCCH BCCH CTCH
FACH-u PCH FACH-s
SCCPCH
connected
SCCPCH
idle
PCCH
FACH-c FACH-c
SCCPCH
page
SF 64 SF 128 SF 128
RN31577EN20GLA1
Paging and inter-RNC optimization
45
Soc Classification level
45 Nokia Siemens Networks RN31577EN20GLA1
Code Allocation
Channelisation code for 24 kbps
PCH uses a larger section of the
code tree
HSDPA cannot use 15 HS-
PDSCH codes when HSUPA 2 ms
TTI is enabled with 24 kbps PCH
Requirement for 2nd E-AGCH
code
Requirement for F-DPCH code
Cch,256,0
Cch,256,1
Cch,256,2
Cch,256,3
Cch,128,4
Cch,128,5
CPICH
P-CCPCH
AICH
PICH
Cch,64,1
Cch,256,14
S-CCPCH 1
E-AGCH
HS-SCCH
E-HICH & E-RGCH
S-CCPCH 2
Cch,128,6
Cch,16,0
RN31577EN20GLA1
Paging and inter-RNC optimization
46
Soc Classification level
46 Nokia Siemens Networks RN31577EN20GLA1
Thank You !
Paging and inter-RNC optimization