RSCP is an acronym used in UMTS and other CDMA cellular communications systems and stands for Received Signal

Code Power .
While RSCP can be defined generally for any CDMA system, it is more specifically used in UMTS. Also, while RSCP can be measured in principle on the downlink (DL) as well as on the uplink (UL), it is usually associated only with the downlink and thus it is presumed to be measured by the UE and reported to the Node-B. It is defined by 3GPP as follows:
Definition: the received power on one code after de-spreading measured by UE on the pilot bits on a given channel. The reference point for the RSCP is the antenna connector of the UE. If Tx diversity is applied on the measured channel then the received code power from each antenna is separately measured and summed together in watt to produce a total received code power on the measured channel.
RSCP is used in UMTS as a handover criterion and in DL and UL open loop power control, UL open loop power control and for calculation of pathloss using the formula:
Pathloss = Transmitted channel power [dBm] - RSCP [dBm]
In UMTS FDD-mode RSCP is measured on Primary CPICH, in TDD-mode it is measured on the pilot bits of Primary CCPCH.
In UMTS RSCP is measured in dBm (decibels relative to 1 watt power) within a bandwidth of 3.84 MHz. In UMTS FDD messages RSCP is transmitted as an integer value in the range of -115 dBm to -25 dBm. The value is coded into integers from 0 to 99 according to the following table:
The accuracy with which RSCP is reported in UMTS FDD is in the range of 6 dB to 11 dB (absolute accuracy) and 3 dB (relative accuracy).
Reported value Measured quantity value
CPICH_RSCP_LEV _00 CPICH RSCP <-115
CPICH_RSCP_LEV _01 -115 CPICH RSCP < -114
CPICH_RSCP_LEV _02 -114 CPICH RSCP < -113 RSCP=RSSI +EcNo
... ...
CPICH_RSCP_LEV _89 -27 CPICH RSCP < -26
CPICH_RSCP_LEV _90 -26 CPICH RSCP < -25
CPICH_RSCP_LEV _91 -25 CPICH RSCP
CPICH_RSCP_LEV _92 (spare, value not assigned)
CPICH_RSCP_LEV _93 (spare, value not assigned)
... ...
CPICH_RSCP_LEV _99 (spare, value not assigned)
CPICH
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
RSCP is an acronym used in UMTS and other CDMA cellular communications systems and stands for Received Signal Code Power .
While RSCP can be defined generally for any CDMA system, it is more specifically used in UMTS. Also, while RSCP can be measured in principle on the downlink (DL) as well as on the uplink (UL), it is usually associated only with the downlink and thus it is presumed to be measured by the UE and reported to the Node-B. It is defined by 3GPP as follows:
Definition: the received power on one code after de-spreading measured by UE on the pilot bits on a given channel. The reference point for the RSCP is the antenna connector of the UE. If Tx diversity is applied on the measured channel then the received code power from each antenna is separately measured and summed together in watt to produce a total received code power on the measured channel.
RSCP is used in UMTS as a handover criterion and in DL and UL open loop power control, UL open loop power control and for calculation of pathloss using the formula:
In UMTS FDD-mode RSCP is measured on Primary CPICH, in TDD-mode it is measured on the pilot bits of Primary CCPCH.
In UMTS RSCP is measured in dBm (decibels relative to 1 watt power) within a bandwidth of 3.84 MHz. In UMTS FDD messages RSCP is transmitted as an integer value in the range of -115 dBm to -25 dBm. The value is coded into integers from 0 to 99 according to the following table:
The accuracy with which RSCP is reported in UMTS FDD is in the range of 6 dB to 11 dB (absolute accuracy) and 3 dB (relative accuracy).
RSCP=RSSI +EcNo
CPICH EcNo CPICH RSCP
0 -24 -5 -120
1 -23.5 -4 -119
2 -23 -3 -118
3 -22.5 -2 -117
4 -22 -1 -116
5 -21.5 0 -115
6 -21 1 -114
7 -20.5 2 -113
8 -20 3 -112
9 -19.5 4 -111
10 -19 5 -110
11 -18.5 6 -109
12 -18 7 -108
13 -17.5 8 -107
14 -17 9 -106
15 -16.5 10 -105
16 -16 11 -104
17 -15.5 12 -103
18 -15 13 -102
19 -14.5 14 -101
20 -14 15 -100
21 -13.5 16 -99
22 -13 17 -98
23 -12.5 18 -97
24 -12 19 -96
25 -11.5 20 -95
26 -11 21 -94
27 -10.5 22 -93
28 -10 23 -92
29 -9.5 24 -91
30 -9 25 -90
31 -8.5 26 -89
32 -8 27 -88
33 -7.5 28 -87
34 -7 29 -86
35 -6.5 30 -85
36 -6 31 -84
37 -5.5 32 -83
38 -5 33 -82
39 -4.5 34 -81
40 -4 35 -80
41 -3.5 36 -79
42 -3 37 -78
43 -2.5 38 -77
44 -2 39 -76
45 -1.5 40 -75
46 -1 41 -74
47 -0.5 42 -73
48 0 43 -72
44 -71
45 -70
46 -69
47 -68
48 -67
49 -66
50 -65
51 -64
52 -63
53 -62
54 -61
55 -60
56 -59
57 -58
58 -57
59 -56
60 -55
61 -54
62 -53
63 -52
64 -51
65 -50
66 -49
67 -48
68 -47
69 -46
70 -45
71 -44
72 -43
73 -42
74 -41
75 -40
76 -39
77 -38
78 -37
79 -36
80 -35
81 -34
82 -33
83 -32
84 -31
85 -30
86 -29
87 -28
88 -27
89 -26
90 -25
While RSCP can be defined generally for any CDMA system, it is more specifically used in UMTS. Also, while RSCP can be measured in principle on the downlink (DL) as well as on the uplink (UL), it is usually associated only with the downlink and thus it is presumed to be measured by the UE and reported to the Node-B. It is defined by 3GPP as follows:
Definition: the received power on one code after de-spreading measured by UE on the pilot bits on a given channel. The reference point for the RSCP is the antenna connector of the UE. If Tx diversity is applied on the measured channel then the received code power from each antenna is separately measured and summed together in watt to produce a total received code power on the measured channel.
In UMTS RSCP is measured in dBm (decibels relative to 1 watt power) within a bandwidth of 3.84 MHz. In UMTS FDD messages RSCP is transmitted as an integer value in the range of -115 dBm to -25 dBm. The value is coded into integers from 0 to 99 according to the following table:
While RSCP can be defined generally for any CDMA system, it is more specifically used in UMTS. Also, while RSCP can be measured in principle on the downlink (DL) as well as on the uplink (UL), it is usually associated only with the downlink and thus it is presumed to be measured by the UE and reported to the Node-B. It is defined by 3GPP as follows:
Definition: the received power on one code after de-spreading measured by UE on the pilot bits on a given channel. The reference point for the RSCP is the antenna connector of the UE. If Tx diversity is applied on the measured channel then the received code power from each antenna is separately measured and summed together in watt to produce a total received code power on the measured channel.
Figure 1 Interaction of radio network planning with other radio network activities
System
Dimensioning
Radio Network
Planning
Pre-launch
Optimisation
Post-launch
Optimisation
3G neighbour lists
2G neighbour lists
Antenna tilts
Local area
parameter tuning
Site selection
Site design
3G neighbour lists
2G neighbour lists
Scrambling codes
Location areas
Routing areas
RNC areas
Link budget analsysis
Node B count and
configuration
RNC count and
configuration
Transmission
capacity and
configuration
RF carriers
Sectorisation
ROC to CEC
Node B power
Baseband proc.
Transmission
HSDPA
Microcells
Capacity
Evolution
Performance Monitoring
3G neighbour lists
2G neighbour lists
Antenna tilts
Local area
parameter tuning
Additional sites
User experience
optimisation
Wide area parameter tuning
System
Dimensioning
Radio Network
Planning
Pre-launch
Optimisation
Post-launch
Optimisation
3G neighbour lists
2G neighbour lists
Antenna tilts
Local area
parameter tuning
Site selection
Site design
3G neighbour lists
2G neighbour lists
Scrambling codes
Location areas
Routing areas
RNC areas
Link budget analsysis
Node B count and
configuration
RNC count and
configuration
Transmission
capacity and
configuration
RF carriers
Sectorisation
ROC to CEC
Node B power
Baseband proc.
Transmission
HSDPA
Microcells
Capacity
Evolution
Performance Monitoring
3G neighbour lists
2G neighbour lists
Antenna tilts
Local area
parameter tuning
Additional sites
User experience
optimisation
Wide area parameter tuning
System
Dimensioning
Radio Network
Planning
Pre-launch
Optimisation
Post-launch
Optimisation
3G neighbour lists
2G neighbour lists
Antenna tilts
Local area
parameter tuning
Site selection
Site design
3G neighbour lists
2G neighbour lists
Scrambling codes
Location areas
Routing areas
RNC areas
Link budget analsysis
Node B count and
configuration
RNC count and
configuration
Transmission
capacity and
configuration
RF carriers
Sectorisation
ROC to CEC
Node B power
Baseband proc.
Transmission
HSDPA
Microcells
Capacity
Evolution
Performance Monitoring
3G neighbour lists
2G neighbour lists
Antenna tilts
Local area
parameter tuning
Additional sites
User experience
optimisation
Wide area parameter tuning
System
Dimensioning
Radio Network
Planning
Pre-launch
Optimisation
Post-launch
Optimisation
3G neighbour lists
2G neighbour lists
Antenna tilts
Local area
parameter tuning
Site selection
Site design
3G neighbour lists
2G neighbour lists
Scrambling codes
Location areas
Routing areas
RNC areas
Link budget analsysis
Node B count and
configuration
RNC count and
configuration
Transmission
capacity and
configuration
RF carriers
Sectorisation
ROC to CEC
Node B power
Baseband proc.
Transmission
HSDPA
Microcells
Capacity
Evolution
Performance Monitoring
3G neighbour lists
2G neighbour lists
Antenna tilts
Local area
parameter tuning
Additional sites
User experience
optimisation
Wide area parameter tuning
chanellization code generation
SF = 3.84Mcps / bit rate
The longer the code, the lower will be data rate
The SF correspond to the length of the code and the number of channels sending at certain bit rate
SF=>1(2
0
) 1
Always remember => SF =2 (2
1
) 1 1
1 -1
SF=>4(2
2
) 1 1 1 1
1 -1 1 -1
1 1 -1 -1
1 -1 -1 1
SF=>8(2
3
) 1 1 1 1 1 1 1 1 a
1 -1 1 -1 1 -1 1 -1 c
1 1 -1 -1 1 1 -1 -1 b
1 -1 -1 1 1 -1 -1 1 d
1 1 1 1 -1 -1 -1 -1 a
1 -1 1 -1 -1 1 -1 1 c
1 1 -1 -1 -1 -1 1 1 b
1 -1 -1 1 -1 1 1 -1 d
SF=>16(2
4
) 1 1 1 1 1 1 1 1
1 -1 1 -1 1 -1 1 -1
1 1 -1 -1 1 1 -1 -1
1 -1 -1 1 1 -1 -1 1
1 1 1 1 -1 -1 -1 -1
1 -1 1 -1 -1 1 -1 1
1 1 -1 -1 -1 -1 1 1
1 -1 -1 1 -1 1 1 -1
1 1 1 1 1 1 1 1
1 -1 1 -1 1 -1 1 -1
1 1 -1 -1 1 1 -1 -1
1 -1 -1 1 1 -1 -1 1
1 1 1 1 -1 -1 -1 -1
1 -1 1 -1 -1 1 -1 1
1 1 -1 -1 -1 -1 1 1
1 -1 -1 1 -1 1 1 -1
DL SF 1(2) 2 (2
1
) 4(2
2
) 8(2)
Spreading Factor (SF)=(3.84*10^6)/8 = 480 kbps
a 1 1 1 1
1 1 1 1
a 1 1 1 1
1 1
b 1 1 -1 -1
1 1 -1 -1
b 1 1 -1 -1
Chip rate =3.84 Mcps
1
c 1 -1 1 -1
1 -1 1 -1
c 1 -1 1 -1
1 -1
d 1 -1 -1 1
1 -1 -1 1
d 1 -1 -1 1
Figure:1 Example of the allocation of the code tree for 8 users sending at the same rate of 480 kpbs.
SF 1(2) 2 (2
1
) 4(2
2
) 8(2)
1 1 1 1
1 1 1 1
1 1 1 1
(User with 4 x bit rate)
1.92 Mbps 1 1
1 1 -1 -1
1 1 -1 -1
1 1 -1 -1
Chip rate =3.84 Mcps
1
1 -1 1 -1
1 -1 1 -1
1 -1 1 -1
1 -1
1 -1 -1 1
1 -1 -1 1
1 -1 -1 1
Figure:2 Example of the allocation of the code tree for 4 users sending at SF =8( 480 kpbs) and 1 user at SF=2 (1.92 Mbps)
Let say SF=2
bit rate= 1920000 1.92 Mbps
Let say SF=4
bit rate= 960000 960 kbps
Let say SF=8
bit rate= 480000 480 kbps
Let say SF=16
bit rate= 240000 240 kbps
Let say SF=32
bit rate= 120000 120 kbps
Let say SF=64
bit rate= 60000 60 kbps
Let say SF=128 3840
bit rate= 30000 30 kbps
Let saySF=256
bit rate= 15000 15 kbps
1 1 1 1 1 1 1 1 a
1 -1 1 -1 1 -1 1 -1
1 1 -1 -1 1 1 -1 -1 c
1 -1 -1 1 1 -1 -1 1
1 1 1 1 -1 -1 -1 -1 b
1 -1 1 -1 -1 1 -1 1
1 1 -1 -1 -1 -1 1 1
1 -1 -1 1 -1 1 1 -1
-1 -1 -1 -1 -1 -1 -1 -1 a
-1 1 -1 1 -1 1 -1 1
-1 -1 1 1 -1 -1 1 1 c
-1 1 1 -1 -1 1 1 -1
-1 -1 -1 -1 1 1 1 1 b
-1 1 -1 1 1 -1 1 -1
-1 -1 1 1 1 1 -1 -1
-1 1 1 -1 1 -1 -1 1
1 1 1 1 480 kb/s
Two codes are said to be orthogonal when their inner product is zero
eg: (1,1,1,1) and ( 1,1,-1,-1) are orthogonal since (1*1)+ (1*1)+(1*-1)+(1*-1)=0
-1 -1 -1 -1 480 kb/s
Digital/Analog Mapping
logic 0 <> analog +1
1 1 -1 -1 480 kb/s logic 1 <> analog -1
-1 -1 1 1 480 kb/s
1 -1 1 -1 480 kb/s
-1 1 -1 1 480 kb/s
1 -1 -1 1 480 kb/s
-1 1 1 -1 480 kb/s
Figure:1 Example of the allocation of the code tree for 8 users sending at the same rate of 480 kpbs.
1 1 1 1 unusable code space
-1 -1 -1 -1
1 1 -1 -1
-1 -1 1 1
1 -1 1 -1 480 kb/s
-1 1 -1 1 480 kb/s
1 -1 -1 1
480 kb/s
-1 1 1 -1 480 kb/s
Figure:2 Example of the allocation of the code tree for 4 users sending at SF =8( 480 kpbs) and 1 user at SF=2 (1.92 Mbps)
32 64 128 256
Two codes are said to be orthogonal when their inner product is zero
eg: (1,1,1,1) and ( 1,1,-1,-1) are orthogonal since (1*1)+ (1*1)+(1*-1)+(1*-1)=0
The Common Pilot Channel
15 TS =0.01 Sec
1 TS =(0.01/15)*1 =666.667 u sec
2560 chip * 15 TS =38400 chip
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
10 Symbols /Slot
1 TS =2560 Chips=10 Symbols=20 bits=666.667 uSec
1 Frame=15 TS=10 msec =0.01Sec = 38400 chips
1. WCDMA uses 18 Shift Registers to create the SC used in DL.
2. This produces a code length of 262 143( 2
18
-1) chips; however only the first
38400 chips are used by the system.
3. Since the Chip rate is 3.84 Mchip/s, it will take 10 milisec to send 38400 chips.
4. This time duration is referred to as one Frame
5. The Frame is sub-divided into 15 TS, each containing 2560 (38400/15) chips.
6. The duration of one TS is 666.667 uSec.
38400
3840000
1 TS =(0.01/15)*1 =666.667 u sec
2560 chip * 15 TS =38400 chip
miliWatt Watt dBm Watt_dBm conversion dBm Watt miliWatt
0.1 0.0001 -10.00 dBm = 10*log(mW) 0 0.00 1.00
0.2 0.0002 -6.99 1 0.00 1.26
0.3 0.0003 -5.23 2 0.00 1.58
0.4 0.0004 -3.98 3 0.00 2.00
0.5 0.0005 -3.01 4 0.00 2.51
0.6 0.0006 -2.22 5 0.00 3.16
0.7 0.0007 -1.55 6 0.00 3.98
0.8 0.0008 -0.97 7 0.01 5.01
0.9 0.0009 -0.46 8 0.01 6.31
1 0.001 0.00 9 0.01 7.94
2 0.002 3.01 10 0.01 10.00
3 0.003 4.77 11 0.01 12.59
4 0.004 6.02 12 0.02 15.85
5 0.005 6.99 13 0.02 19.95
6 0.006 7.78 14 0.03 25.12
7 0.007 8.45 15 0.03 31.62
8 0.008 9.03 16 0.04 39.81
9 0.009 9.54 17 0.05 50.12
9 0.009 9.54 18 0.06 63.10
10 0.01 10.00 19 0.08 79.43
20 0.02 13.01 20 0.10 100.00
30 0.03 14.77 21 0.13 125.89
40 0.04 16.02 22 0.16 158.49
50 0.05 16.99 23 0.20 199.53
60 0.06 17.78 24 0.25 251.19
70 0.07 18.45 25 0.32 316.23
80 0.08 19.03 26 0.40 398.11
90 0.09 19.54 27 0.50 501.19
100 0.1 20.00 28 0.63 630.96
200 0.2 23.01 29 0.79 794.33
300 0.3 24.77 30 1.00 1000.00
400 0.4 26.02 31 1.26 1258.93
500 0.5 26.99 32 1.58 1584.89
600 0.6 27.78 33 2.00 1995.26
700 0.7 28.45 34 2.51 2511.89
800 0.8 29.03 35 3.16 3162.28
900 0.9 29.54 36 3.98 3981.07
1000 1 30.00 37 5.01 5011.87
2000 2 33.01 38 6.31 6309.57
3000 3 34.77 39 7.94 7943.28
4000 4 36.02 40 10.00 10000.00
5000 5 36.99 41 12.59 12589.25
6000 6 37.78 42 15.85 15848.93
7000 7 38.45 43 19.95 19952.62
8000 8 39.03 44 25.12 25118.86
9000 9 39.54 45 31.62 31622.78
10000 10 40.00 46 39.81 39810.72
11000 11 40.41 47 50.12 50118.72
12000 12 40.79 48 63.10 63095.73
13000 13 41.14 49 79.43 79432.82
14000 14 41.46 50 100.00 100000.00
15000 15 41.76 51 125.89 125892.54
16000 16 42.04 52 158.49 158489.32
17000 17 42.30 53 199.53 199526.23
18000 18 42.55 54 251.19 251188.64
19000 19 42.79 55 316.23 316227.77
20000 20 43.01 56 398.11 398107.17
21000 21 43.22 57 501.19 501187.23
22000 22 43.42 58 630.96 630957.34
23000 23 43.62 59 794.33 794328.23
24000 24 43.80 60 1000.00 1000000.00
25000 25 43.98 61 1258.93 1258925.41
26000 26 44.15 62 1584.89 1584893.19
27000 27 44.31 63 1995.26 1995262.31
28000 28 44.47 64 2511.89 2511886.43
29000 29 44.62 65 3162.28 3162277.66
30000 30 44.77 66 3981.07 3981071.71
31000 31 44.91 67 5011.87 5011872.34
32000 32 45.05 68 6309.57 6309573.44
33000 33 45.19 69 7943.28 7943282.35
34000 34 45.31 70 10000.00 10000000.00
35000 35 45.44 71 12589.25 12589254.12
36000 36 45.56 72 15848.93 15848931.92
37000 37 45.68 73 19952.62 19952623.15
38000 38 45.80 74 25118.86 25118864.32
39000 39 45.91 75 31622.78 31622776.60
40000 40 46.02 76 39810.72 39810717.06
41000 41 46.13 77 50118.72 50118723.36
42000 42 46.23 78 63095.73 63095734.45
43000 43 46.33 79 79432.82 79432823.47
44000 44 46.43 80 100000.00 100000000.00
45000 45 46.53 81 125892.54 125892541.18
46000 46 46.63 82 158489.32 158489319.25
47000 47 46.72 83 199526.23 199526231.50
48000 48 46.81 84 251188.64 251188643.15
49000 49 46.90 85 316227.77 316227766.02
50000 50 46.99 86 398107.17 398107170.55
51000 51 47.08 87 501187.23 501187233.63
52000 52 47.16 88 630957.34 630957344.48
53000 53 47.24 89 794328.23 794328234.72
54000 54 47.32 90 1000000.00 1000000000.00
55000 55 47.40 91 1258925.41 1258925411.79
56000 56 47.48 92 1584893.19 1584893192.46
57000 57 47.56 93 1995262.31 1995262314.97
58000 58 47.63 94 2511886.43 2511886431.51
59000 59 47.71 95 3162277.66 3162277660.17
60000 60 47.78 96 3981071.71 3981071705.53
61000 61 47.85 97 5011872.34 5011872336.27
62000 62 47.92 98 6309573.44 6309573444.80
63000 63 47.99 99 7943282.35 7943282347.24
64000 64 48.06 100 10000000.00 10000000000.00
65000 65 48.13
66000 66 48.20
67000 67 48.26
68000 68 48.33
69000 69 48.39
70000 70 48.45
71000 71 48.51
72000 72 48.57
73000 73 48.63
74000 74 48.69
75000 75 48.75
76000 76 48.81
77000 77 48.86
78000 78 48.92
79000 79 48.98
80000 80 49.03
81000 81 49.08
82000 82 49.14
83000 83 49.19
84000 84 49.24
85000 85 49.29
86000 86 49.34
87000 87 49.40
88000 88 49.44
89000 89 49.49
90000 90 49.54
91000 91 49.59
92000 92 49.64
93000 93 49.68
94000 94 49.73
95000 95 49.78
96000 96 49.82
97000 97 49.87
98000 98 49.91
99000 99 49.96
100000 100 50.00
dBm_Watt Conversion
s
e
r
v
i
c
e

T
y
p
e
D
e
f
a
u
l
t

P
o
w
e
r
(
d
B
m
)
D
e
f
a
u
l
t

P
o
w
e
r
(
W
a
t
t
)
M
i
n

A
c
t
i
v
i
t
y

(
%
)
M
i
n

A
v
e

P
o
w
e
r

(
W
)
M
i
n

A
v
e

P
o
w
e
r

(
d
B
m
)
M
a
x

A
c
t
i
v
i
t
y
M
a
x

A
v
e

P
o
w
e
r
(
W
)
mW =10^(dBm/10) CPICH 36 3.98 100 3.98 36.00 100 3.98
P-SCH 30 1 10 0.1 20.00 10 0.1
S-SCH 30 1 10 0.1 20.00 10 0.1
PCCPCH 28 0.63 90 0.567 27.54 90 0.567
SCCPCH 33 2 25 0.5 26.99 115 2.3
PICH 25 0.32 96 0.3072 24.87 96 0.3072
AICH 25 0.32 0 0 80 0.256
TOTAL 5.5542 37.45 7.6102
The Power of
Common
Physical
Channel are
set relative to
CPICH
M
a
x

A
v
e

P
o
w
e
r
(
d
B
m
)
R
e
m
a
r
k
s
36.00 CPICH as Ref
20.00 -6
20.00 -6
27.54 -8
33.62 -3
24.87 -11
24.08 -11
38.8139607
The Power of
Common
Physical
Channel are
set relative to
CPICH
Watt
40 2.398797736 Max OVERLOAD
0.398797736 Min OVERLOAD
39.60120226 PtxTargetMax+PtxOffset
39 39.6 PtxTarget Max
38 37.60120226 PtxTargetMin+PtxOffset
37 37.6 Ptx Target Min
36
35
34
33
32
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
9
8 7.6 Max
7
6 5.6 Min
5
4
3
2
1
0
Total DL Common CH PWR
FEASIBLE AREA
MARGINAL AREA
OVERLOAD AREA
0.001202 PtxOffset =0.8 dBm=0.0012 Watt
80%
19%
14%
ISHO 2G -> 3G Parameters
GSM ISHO example
minEcnoThreshold
(MET)
MIN_ECNO_THRESHOLD

minimum CPICH Ec/Io level

qSearchC (QSRC) Qsearch_C threshold for multi-RAT MS
minIntUnsuccIsHo
MIN_INTERVAL_BETWEE
N_UNSUCC_ISHO_ATTE
min interval between unsucc ISHO
utranHoThScTpdc
LOAD_THRESHOLD_FOR
_SC_IS_HO
min traffic load for speech call
Nokia parameter Specification name Parameter
Changeable Parameter
Qsearch_C_Initial

FDD_MULTIRAT_REPORTING

3G_SEARCH_PRIO
FDD_REP_QUANT
Specification name
Indicates the Qsearch value to be used in
connected mode before Qsearch_C is
The number of cells from the access
technology/mode FDD that shall be
Indicates if 3G cells may be searched
Indicates the reporting quantity for
Parameter explanation
Hidden Parameter
Load Threshold for Speech Calls inter-RAT Handover
utranHoThScTpdc = 80%
Min Ec/No threshold for a handover to the UTRAN adjacent cell
minEcnoThreshold = -15 dB
qSearchC = 7 (measure UTRAN adjacent cells always)

1Load of the serving cell = 45% and the measured Ec/No =
--> Handover to the UTRAN not possible due to low load and low Ec/No
2Load of the serving cell = 45% and the measured Ec/No =
--> Handover to the UTRAN not possible due to low load
3Load of the serving cell = 95% and the measured Ec/No =
--> Handover to the UTRAN possible

-15 dB

-240.5 dB

minEcnoThreshold
(MET)
15 (never) rec. 015 qSearchC (QSRC)
3 s 0255 s minIntUnsuccIsHo
80% 0-100% utranHoThScTpdc
Default value Range Nokia parameter
Not tunable,
Fixed value 0
0 = use Qsearch_I,
1 = (always)
Indicates the Qsearch value to be used in
connected mode before Qsearch_C is
Not tunable,
Fixed value 2
03

The number of cells from the access
technology/mode FDD that shall be
Not tunable, 0 = no, Indicates if 3G cells may be searched
Not tunable, 0=RSCP, Indicates the reporting quantity for
Note Value range
RAT Handover
Min Ec/No threshold for a handover to the UTRAN adjacent cell
qSearchC = 7 (measure UTRAN adjacent cells always)
1Load of the serving cell = 45% and the measured Ec/No = - 20 dB
due to low load and low Ec/No
2Load of the serving cell = 45% and the measured Ec/No = - 10 dB
due to low load
3Load of the serving cell = 95% and the measured Ec/No = -10 dB
>>With RAS05.1, a new BTS called Flexi BTS is available
>>The system module provide up to 192 CEs with 1-3 cells configuration - require 16 CEs for CCCH processing
>> For HW point 240 CEs Capacity(with 26 CE for common channel processing)
>> Basic HSDPA needs 32 CEs per cell ,thus enabling 16 HSDPA users/cell
>>With RAS05.1 ED, the Baseband Extension Module is available, increasing Flexi BTS to 2*192=384 CE
>> Example on, System module capacity with 192CEs, 1-3 cells, with option:-
1. 16 HSDPA users/BTS (only 1 cell) -->>32 CE s only
2. 16 HSDPA users/cell -->>32 CEs /cell or 96 CEs /site/BTS (32*3)
3. Without HSDPA activated.
user data rate/kbps
(BEARER)
(1) system module
max cap, with 1-3 cells
CCCHs and HSDPA
activated in BTS ( only
1 cell)
(2) system module max
cap, with 1-3 cells CCCHs
and HSDPA activated in 3
cells
(3) system module max
cap, with 1-3 cells CCCHs
( HSDPA not activated)
AMR Voice (12.2) 192 - 16 - 32 = 144 192 - 16 - 96 = 80 192 -16 =176
PS 16 192 -16 -32 =144 192 - 16 -96 =80 192 -16 =176
PS 32 (192 - 16 -32) / 2= 72 (192 -16 -96)/2 =40 (192 -16)/2 = 89
PS64 and CS64(video) (192 -16 -32) /4 =36 (192 -16 -96) / 4=20 (192 -16)/4 =44
PS 128 (192 -16 -32) /4 =36 (192 -16 -96) / 4=20 (192 -16)/4 =44
PS 256 (192 -16 -32) / 8 =18 (192 -16 -96) / 8 =10 (192-16) / 8= 22
PS 384 (192 -16 -32) / 16 =9 (192 -16 -96) /16 =5 (192 -16)/16 = 11
>> CE consumption with Flexi BTS
Bearer CEs Needed
AMR 1
<16 1
32 2
64 4
128 4
256 8
384 16
>>The system module provide up to 192 CEs with 1-3 cells configuration - require 16 CEs for CCCH processing
OverView
>> RNC dimensioning is based on RNC throughput requirement in :-
1. Mbps and Erlangs
2. No of BTS/cells to be connected to RNC
3. Total sum of AAL2 ( ATM Adaptation Layer Type 2) connectivity for Iub, Iur and Iu-CS interface
Therefore, the RNC dimensioning requires preliminary dimensioning of BTSs, Uu, Iub, Iur and Iu interfaces
With RAS05.1, the new RNC450 with enhanced capacity is available
This RNC450 can be delivered in 3 capacity step with Iub throughput of 150, 300 and 450 Mbps
The max capacity for RNC450 is 8000 Erlangs, OR 450 Mbps PS data, OR 112.5Mbps CS data on Iub.
Eg:- RNC Dimensioning
There are 1000 BTSs, with an average busy hour traffic per BTS and SHO traffic also included:-
1. 20 Erlang AMR voice
2. 2*64 CS Data
3. 6*64 PS Data
4. 500 kbps HSDPA data
On the FP (Framing Protocol) Level, the throughput per BTS are:-
services # users FP rate, kbps
AMR 20 Erlang
CS 64 2 66.1
PS 64 6 69.5
HSDPA 550
sum
Thus, traffic per BTS is 20 Erlang AMR + 1100 kbps data.
Traffic for all 1000 BTSs is:-
(20 *1000)/1.4 (BH traffic + SHO traffic) =14 285 Erlangs AND 1100kbps*1000BTSs =1100 Mbps to Iub

FROM NED,The max capacity for RNC450 is 8000 Erlangs, OR 450 Mbps PS data, OR 112.5Mbps CS data on Iub.
The traffic mix rule indicates that:-
14 285 / 8000 + 132 / 450 + (417+ 550) / 450 = 4.2 RNCs are needed
Normally dimension the RNCs to be filled up to 70% by their launch phase in order to have capacity available
for increasing traffic
Since, 100% required 4.2 RNCs , thus 70% required ONLY 6 RNCs
So the average services is as follows:-
services average
AMR (traffic) 2381
CS 64 22
PS 64 70
HSDPA 92
CROSS CHECK:_
RNC LOAD:= 2381/800 + 22/ 450 + (70+92)/450 =0.71
RNC450 (FROM NED)
Table: Capacity and reference call mix model
High capacity RNC RNC450/150 default
Number of subscribers 181 000
Busy hour call attempts 240 000
3. Total sum of AAL2 ( ATM Adaptation Layer Type 2) connectivity for Iub, Iur and Iu-CS interface Erlangs 4 000
Therefore, the RNC dimensioning requires preliminary dimensioning of BTSs, Uu, Iub, Iur and Iu interfaces Iub throughput Mbit/s 150
Number of carriers 600
Number of BTSs 200
AAL2UP Connectivity Mbits/sec 1 950
This RNC450 can be delivered in 3 capacity step with Iub throughput of 150, 300 and 450 Mbps RRC connected mode users 35 000
The max capacity for RNC450 is 8000 Erlangs, OR 450 Mbps PS data, OR 112.5Mbps CS data on Iub.
Table: Voice Service Call mix
Property Value
There are 1000 BTSs, with an average busy hour traffic per BTS and SHO traffic also included:- Mean holding time (MHT)
1
90s
Proportion of UE originating calls (UOC) 70%
Proportion of UE terminating calls (UTC) 30%
For terminating call attempts, the proportion
of no-answer call attempts to paging request
(NAC)
63%
Proportion of handovers 40%
- hard handovers 0.1 per call
- soft handovers 3 per call
Bearer 16 kbit/s
Traffic per user 22 mErl
Sum Kbps
132.2 Table: HSDPA capacity figures
417 RNC450/150
550 Max HSDPA peak rate per UE [Mbit/s]
1100 HSDPA active users per cell
HSDPA active users per RNC 360
Iu-ps HSDPA net bit rate [Mbit/s] 135
HSDPA BTS 200
HSDPA carriers 600
(20 *1000)/1.4 (BH traffic + SHO traffic) =14 285 Erlangs AND 1100kbps*1000BTSs =1100 Mbps to Iub
Table: Interfaces
Configuration
FROM NED,The max capacity for RNC450 is 8000 Erlangs, OR 450 Mbps PS data, OR 112.5Mbps CS data on Iub.
Max number of cards
RNC450/150
4 or 6
1
RNC450/300
8 or 10
2
RNC450/450 12
Normally dimension the RNCs to be filled up to 70% by their launch phase in order to have capacity available
TRAFFIC MIX RULE FORMULA
3.6
16
Interfaces
STM-1 / OC-3
AMR traffic(Erlang) /max AMR traffic (Erl) + CS traffic( Mbps)/ max Iub throughput (Mbps) + PS traffic (Mbps)/max Iub throughput (Mbps) <=1
RNC450/300 RNC450/450
284 000 360 000
375 000 576 000
6 250 8 000
300 450
900 1 152
300 512
2 800 3 594
70 000 100 000
RNC450/300 RNC450/450
720 1620
270 405
300 512
900 1152
Nbr of int unprot. /
(Protected)
Max number
of cards
Nbr of int unprotected
16 / (8+8 or 12+12
1
)
1 optional 16
24 / (16+16 or
20+20
2
)
1 optional 16
24 / (24+24) 1 optional 16
3.6
16
Interfaces
STM-1 / OC-3 E1 / T1
AMR traffic(Erlang) /max AMR traffic (Erl) + CS traffic( Mbps)/ max Iub throughput (Mbps) + PS traffic (Mbps)/max Iub throughput (Mbps) <=1
Find HSPDSCHcode set enable and code combination description as per below, please check the ABH1RNC01 dump to clearify R6 sites with code license key installed part of RU10 RNC upgarde, also check CE No./WCell.
HSPDSCHCodeSet Code Combination Binary
32 5 100000 basic
1312 5,8,10 10100100000
1440 5,7,8,10 10110100000
2016 5,6,7,8,9,10 11111100000
8160 5,6,7,8,9,10,11,12 1111111100000
50464 5,8,10,14,15 1100010100100000
54560 5,8,10,12,14,15 1101010100100000 NSN Global standard
54688 5,7,8,10,1,14,15 1101010110100000
54752 5,6,7,8,10,12,14,15 1101010111100000
65312 5,8,9,10,11,12,13,14,15 1111111100100000
to calculate this, convert the HSDPSCHcodeset value to Binary, then leave first five ZEROs from right to left, then if the 6th digit is 1 it means 5 codes is activated. If 7th digit is 1/0 it means 7th code is activated/deactivated.... it goes on ....
Find HSPDSCHcode set enable and code combination description as per below, please check the ABH1RNC01 dump to clearify R6 sites with code license key installed part of RU10 RNC upgarde, also check CE No./WCell.
to calculate this, convert the HSDPSCHcodeset value to Binary, then leave first five ZEROs from right to left, then if the 6th digit is 1 it means 5 codes is activated. If 7th digit is 1/0 it means 7th code is activated/deactivated.... it goes on ....
to calculate this, convert the HSDPSCHcodeset value to Binary, then leave first five ZEROs from right to left, then if the 6th digit is 1 it means 5 codes is activated. If 7th digit is 1/0 it means 7th code is activated/deactivated.... it goes on ....
Frequency Bands and ARFCN
Frequency Band Uplink/Downlink
Separation
Uplink Frequency Range
(Transmit Device = Mobile)
Downlink Frequency
Range (Transmit Device =
Base)
ARFCN
GSM 450 10 MHz 450.4 to 457.6 MHz 460.4 to 467.6 MHz 259 to 293
GSM 480 10 MHz 478.8 to 486 MHz 488.8 to 496 MHz 306 to 340
GSM 750 30 MHz 747 to 762 MHz 777 to 792 MHz 438 to 511
GSM 850 45 MHz 824 to 849 MHz 869 to 894 MHz 128 to 251
P-GSM 900 45 MHz 890 to 915 MHz 935 to 960 MHz 1 to124
0 to124
and
975 to 1023
0 to124
and
955 to 1023
DCS 1800 45 MHz 1710 to 1785 MHz 1805 to 1880 MHz 512 to 885
PCS 1900 45 MHz 1850 to 1910 MHz 1930 to 1990 MHz 512 to 810
ARFCN to Frequency Calculator / Table
ARFCN stands for Absolute Radio Frequency Channel Number. ARFCN is a radio channel numbering scheme used to identify specific RF channels in a cellular mobile radio system.
To calculate ARFCN channel frequency, enter Absolute Radio Frequency Channel Number (ARFCN) below. Or, enter start and end ARFCN values to generate a table.

UL DL
ARFCN
Frequency
(MHz) ARFCN Frequency (MHz)
975 880.2 975 925.2
976 880.4 976 925.4
977 880.6 977 925.6
978 880.8 978 925.8
979 881 979 926
980 881.2 980 926.2
981 881.4 981 926.4
982 881.6 982 926.6
983 881.8 983 926.8
984 882 984 927
985 882.2 985 927.2
986 882.4 986 927.4
987 882.6 987 927.6
988 882.8 988 927.8
989 883 989 928
990 883.2 990 928.2
991 883.4 991 928.4
992 883.6 992 928.6
993 883.8 993 928.8
994 884 994 929
995 884.2 995 929.2
996 884.4 996 929.4
997 884.6 997 929.6
E-GSM 900 45 MHz 880 to 915 MHz 925 to 960 MHz
R-GSM 900 45 MHz 876 to 915 MHz 921 to 960 MHz
998 884.8 998 929.8
999 885 999 930
1000 885.2 1000 930.2
1001 885.4 1001 930.4
1002 885.6 1002 930.6
1003 885.8 1003 930.8
1004 886 1004 931
1005 886.2 1005 931.2
1006 886.4 1006 931.4
1007 886.6 1007 931.6
1008 886.8 1008 931.8
1009 887 1009 932
1010 887.2 1010 932.2
1011 887.4 1011 932.4
1012 887.6 1012 932.6
1013 887.8 1013 932.8
1014 888 1014 933
1015 888.2 1015 933.2
1016 888.4 1016 933.4
1017 888.6 1017 933.6
1018 888.8 1018 933.8
1019 889 1019 934
1020 889.2 1020 934.2
1021 889.4 1021 934.4
1022 889.6 1022 934.6
1023 889.8 1023 934.8
977
ARFCN stands for Absolute Radio Frequency Channel Number. ARFCN is a radio channel numbering scheme used to identify specific RF channels in a cellular mobile radio system.
To calculate ARFCN channel frequency, enter Absolute Radio Frequency Channel Number (ARFCN) below. Or, enter start and end ARFCN values to generate a table.
HSDPA
In the future, user application are likely to involve the transport of large volumes of data
and require high bit rates
HSDPA introduces a new transport channel type - HS-DSCH
that makes efficient use of valuable radio freq resources and takes into accout busty packet data
this new transport channel share multiple access code, transmission power and use infrastructure hardware between users
The radio n/w resource can be used efficiently to serve a large number of users who are accessing to the resource
In other word, several users can be time multiplxed so that during silent periods, the resource are available for other users.
HSDPA offers max peak rates of up to 14.4 Mbps in 5 Mhz channel
However, more importantly than the peak rate is packet data throughput capacity, which is improved significantly.
This will increase the number of users that can be supported at higher data rates on a single radio carrier.
Another important characteristic of HSDPA is the reduced variance in DL transmission delay
A guaranteed short delay time is important for many applications such as interactive games.
In general, HSDPA's enhancement can be used to implement the efficiently the "interactive" and "background " QoS.
HSDPA's high data rates also will improve the use of streaming applications on share packet channel
while the shorthened roundtrip (RTT) will benefit web-browsing application
HSDPA Features
HSDPA enhanced data rates and spectrum efficiency
HSDPA improves system capacity and increase user data rates in DL , that is, transmission from Radio Access n/w(RAN) to mobile
This improved performance is BASED on:
1. ADAPTIVE MODULATION and CODING
(Data rates are optimised dynamically during the session according to radio link quality - This ensures HIGHEST possible data rates to end users)
2. A FAST SCHEDULING function, which is controlloed in WBTS, rather than by RNC
(
3. FAST RETRANSMISSION with soft combining and incremental redundancy
that makes efficient use of valuable radio freq resources and takes into accout busty packet data
this new transport channel share multiple access code, transmission power and use infrastructure hardware between users
The radio n/w resource can be used efficiently to serve a large number of users who are accessing to the resource
In other word, several users can be time multiplxed so that during silent periods, the resource are available for other users.
However, more importantly than the peak rate is packet data throughput capacity, which is improved significantly.
This will increase the number of users that can be supported at higher data rates on a single radio carrier.
Another important characteristic of HSDPA is the reduced variance in DL transmission delay
A guaranteed short delay time is important for many applications such as interactive games.
In general, HSDPA's enhancement can be used to implement the efficiently the "interactive" and "background " QoS.
HSDPA's high data rates also will improve the use of streaming applications on share packet channel
HSDPA improves system capacity and increase user data rates in DL , that is, transmission from Radio Access n/w(RAN) to mobile
(Data rates are optimised dynamically during the session according to radio link quality - This ensures HIGHEST possible data rates to end users)
Terminal Category Support
The 3GPP standard includes different optional feature support as well as parameter settings corresponding to the possiblitity to support different HSPA terminal categories
Different choices made regarding these parameters and features could impact the possibility for full support of these different terminal categories
HSDPA
HSDPA Category HSDPA Codes Modulation Maximum bit rate(Mbps)
Category 1 5 QPSK, 16 QAM 1.2
Category 2 5 QPSK, 16 QAM 1.2
Category 3 5 QPSK, 16 QAM 1.8
Category 4 5 QPSK, 16 QAM 1.8
Category 5 5 QPSK, 16 QAM 3.6
Category 6 5 QPSK, 16 QAM 3.6
Category 7 10 QPSK, 16 QAM 7.3
Category 8 10 QPSK, 16 QAM 7.3
Category 9 15 QPSK, 16 QAM 10
Category 10 15 QPSK, 16 QAM 14.4
Category 11 5 QPSK 0.9
Category 12 5 QPSK 1.8
HSUPA
HSUPA Category HSUPA Codes TTI Length Maximum bit rate(Mbps)
Category 1 1 10 ms only 0.73
Category 2 2 10 ms/ 2 ms 1.46
Category 3 2 10 ms only 1.46
Category 4 2 10 ms/ 2 ms 2.00 / 2.92
Category 5 2 10 ms only 2.00
Category 6 4 10 ms/ 2 ms 2.00 / 5.76
The 3GPP standard includes different optional feature support as well as parameter settings corresponding to the possiblitity to support different HSPA terminal categories
Different choices made regarding these parameters and features could impact the possibility for full support of these different terminal categories
UL Service DPCH Generic Nokia UL Service Link Budgets
Service Type Nokia Specific Speech CS Data
Uplink bit rate No 12.2 64
Maximum transmit power UE dependant 21 21
Terminal antenna gain UE dependant 0 2
Body loss No 3 0
Transmit EIRP UE dependant 18 23
Chip rate No 3.84 3.84
Processing gain No 25.0 17.8
Required Eb/No Yes 4.4 2
Target uplink load No 50 50
Rise over thermal noise No 3.0 3.0
Thermal noise power No -108 -108
Receiver noise figure Yes 3 3
Interference floor No -102 -102
Receiver sensitivity Yes -122.6 -117.8
Node B antenna gain No 18.5 18.5
Cable loss No 2 2
Benefit of using MHA No 2 2
Fast fading margin Yes 1.8 1.8
Soft handover gain Yes 2 2
Building penetration loss No 12 12
Indoor location probability No 90 90
Indoor standard deviation No 10 10
Slow fading margin No 7.8 7.8
Isotropic power required Yes -121.5 -116.7
Allowed propagation loss Yes 139.5 139.7
DL Service DPCH Generic Nokia DL Service Link Budgets
Service Type Nokia Specific Speech CS Data
Downlink bit rate No 12.2 64
Maximum transmit power Yes 34.2 37.2
Cable loss No 2 2
MHA insertion loss Yes 0.5 0.5
Node B antenna gain No 18.5 18.5
Transmit EIRP Yes 50.2 53.2
Processing gain No 25.0 17.8
Required Eb/No UE dependant 7.9 5.3
Target loading No 80 80
Rise over thermal noise No 7 7
Thermal noise power No -108 -108
Receiver noise figure UE dependant 8 8
Interference floor No -93 -93
Receiver sensitivity UE dependant -110.1 -105.5
Terminal antenna gain UE dependant 0 2
Body loss No 3 0
Fast fading margin UE dependant 0 0
Soft handover gain UE dependant 2 2
MDC gain UE dependant 1.2 1.2
Building penetration loss No 12 12
Indoor location probability No 90 90
Indoor standard deviation No 10 10
Slow fading margin No 7.8 7.8
Isotropic power required Yes -90.5 -90.9
Allowed propagation loss Yes 140.7 144.1
DL CPICH Link Budget Generic Nokia DL CPICH Link Budget
Service Type Nokia Specific CPICH
Maximum transmit power Yes 33 dBm
Cable loss No 2 dB
MHA insertion loss Yes 0.5 dBi
Node B antenna gain No 18.5 dBi
Transmit EIRP Yes 49 dBm
Required Ec/Io UE dependant -15 dB
Target loading No 80 %
Rise over thermal noise No 7 dB
Thermal noise power No -108 dBm
Receiver noise figure UE dependant 8 dB
Interference floor No -93 dBm
Receiver sensitivity UE dependant dBm
Terminal antenna gain UE dependant 0 dBi
Body loss No 3 dB
Fast fading margin No 0 dB
Building penetration loss No 12 dB
Indoor location probability No 90 %
Indoor standard deviation No 10 dB
Slow fading margin No 7.8 dB
Isotropic power required Yes -85.2 dBm
Allowed propagation loss Yes 134.2 dB
The 3G link budget results must be adjusted prior to being used within the planning tool
Link budget results are generated in terms of maximum allowed path loss whereas the majority of planning tools display contours of signal strength
This means that a relatively arbitrary Node B transmit power must be selected and then a signal strength threshold computed by subtracting the link budget maximum allowed path loss.
PS Data
64 kbps
21 dBm kTB = assumed temperature of Node B Receiver
2 dBi
0 dB dBm = 10*log(mW)
23 dBm 1 0.00
3.84 Mcps
17.8 dB Processing Gain=10*LOG (Chip Rate/Bit Rate)
2 dB Service C/I Requirement=EbNo - Processing Gain
50 %
3.0 dB RiseOverThermalNoise= -10*LOG(1 - Target Load)
-108 dBm Thermal Noise Power=10*LOG(kTB)=10*LOG(1.4*10^(-23)*290*(3.84*10^6))=-138dBW=-108dBm
3 dB
-102 dBm
-117.8 dBm Receiver Sensitivity=Service C/I Requirement+Thermal Noise Power+RiseOverThermal Noise + Receiver Noise Figure
18.5 dBi
2 dB
2 dB
1.8 dB
2 dB
12 dB
90 %
10 dB
7.8 dB
-116.7 dBm Isotropic Power Required=Receiver Sensitivity - Antenna Gain + Cable Loss - MHA Benefit +Fast Fading Margin - Soft HO Gain + Building Penetration Loss + Slow Fading Margin
139.7 dB Allowed Propagation Loss=Transmit EIRP - Isotropic Power Required
64 128 384 kbps Nokia's admission control determines the maximum downlink transmit power for real time services according to:
37.2 40 40 dBm
2 2 2 dB
0.5 0.5 0.5 dB
18.5 18.5 18.5 dBi for non-real time services according to:
53.2 56 56 dBm
17.8 14.77 10 dB
5 4.7 4.8 dB
80 80 80 %
7 7 7 dB PtxDPCHmax and PtxDLabsMax are the RNC databuild parameters. MaxDLCalulated is computed from the expression:
-108 -108 -108 dBm
8 8 8 dB
-93 -93 -93 dBm
-105.8 -103.1 -98.2 dBm
2 2 2 dBi
0 0 0 dB
0 0 0 dB
2 2 2 dB
1.2 1.2 1.2 dB
PS Data
( ) lated MaxDLCalcu PtxDPCH Min er MaxRTDLPow max, 43+ =
( ) x PtxDLabsMa lated MaxDLCalcu PtxDPCH Min wer MaxNRTDLPo , max, 43+ =
(
(
(

+
+
=
) 10 (
) 10 ( ) 10 (
10
Re Pr
Re
10
10 10
Re
f
EbNo
Service
EbNo
SRB
EbNo
BR
BR BR
LOG
fRABOffset CPICHto imaryCPICH PTx lated MaxDLCalcu
f
Service SRB
12 12 12 dB
90 90 90 %
10 10 10 dB
7.8 7.8 7.8 dB
-91.2 -88.5 -83.6 dBm
144.4 144.5 139.6 dB
The CPICH link budget is similar to the downlink service link budget
In this case the transmit power is defined by the PtxPrimaryCPICH RNC databuild parameter
The downlink service Eb/No requirement and processing gain are replaced by the CPICH Ec/Io requirement.
This is equivalent to the downlink service C/I requirement
The terminal antenna gain is assumed to be 0 dB.This represents a worst case assumption
The CPICH is not combined during soft handover and so there are no soft handover gains for the CPICH link budget.
The downlink CPICH allowed propagation loss should be compared with the uplink service and downlink service allowed propagation losses.
Link budget results are generated in terms of maximum allowed path loss whereas the majority of planning tools display contours of signal strength
This means that a relatively arbitrary Node B transmit power must be selected and then a signal strength threshold computed by subtracting the link budget maximum allowed path loss.
Thermal Noise Power=10*LOG(kTB)=10*LOG(1.4*10^(-23)*290*(3.84*10^6))=-138dBW=-108dBm
Receiver Sensitivity=Service C/I Requirement+Thermal Noise Power+RiseOverThermal Noise + Receiver Noise Figure
Isotropic Power Required=Receiver Sensitivity - Antenna Gain + Cable Loss - MHA Benefit +Fast Fading Margin - Soft HO Gain + Building Penetration Loss + Slow Fading Margin
Allowed Propagation Loss=Transmit EIRP - Isotropic Power Required
Nokia's admission control determines the maximum downlink transmit power for real time services according to:
PtxDPCHmax and PtxDLabsMax are the RNC databuild parameters. MaxDLCalulated is computed from the expression:
( ) lated MaxDLCalcu PtxDPCH Min er MaxRTDLPow max, 43+ =
( ) x PtxDLabsMa lated MaxDLCalcu PtxDPCH Min wer MaxNRTDLPo , max, 43+ =
(
(
(

+
+
=
) 10 (
) 10 ( ) 10 (
10
Re Pr
Re
10
10 10
Re
f
EbNo
Service
EbNo
SRB
EbNo
BR
BR BR
LOG
fRABOffset CPICHto imaryCPICH PTx lated MaxDLCalcu
f
Service SRB
In this case the transmit power is defined by the PtxPrimaryCPICH RNC databuild parameter
The downlink service Eb/No requirement and processing gain are replaced by the CPICH Ec/Io requirement.
The terminal antenna gain is assumed to be 0 dB.This represents a worst case assumption
The CPICH is not combined during soft handover and so there are no soft handover gains for the CPICH link budget.
The downlink CPICH allowed propagation loss should be compared with the uplink service and downlink service allowed propagation losses.
This means that a relatively arbitrary Node B transmit power must be selected and then a signal strength threshold computed by subtracting the link budget maximum allowed path loss.
Isotropic Power Required=Receiver Sensitivity - Antenna Gain + Cable Loss - MHA Benefit +Fast Fading Margin - Soft HO Gain + Building Penetration Loss + Slow Fading Margin