Vous êtes sur la page 1sur 77

For VNPT Internal Use Only (Mar 2012)

VNPT Network Analysis Report System Parameter Review


Preliminary version Mar, 2012

Table of Content
3G Idle Mode Parameters
Cell (Re-) Selection Parameters Random Access Parameters Paging Parameters

For VNPT Internal Use Only (Mar 2012)

3G Connected Mode Parameters


Radio Link Parameters Handover Parameters Compressed Mode Parameters 3G-to-2G IRAT Parameters HSDPA Parameters

OVSF Code Allocation 2G-to-3G IRAT Parameters


2

For VNPT Internal Use Only (Mar 2012)

Idle Mode Parameters

Cell (Re-)Selection Parameters on UARFCN 10787 (Single-Carrier) HCMC


Cell (Re-) Selection Parameters qQualmin qRxlevmin Sintrasearch NW setting SIB 3 SIB 11 -18dB -115dBm Always QC Recommended Settings (Rev K) -18dB / -16dB (edge) -113dBm / -107dBm (edge) 10dB / 8dB (edge) 8dB / 6dB (edge) 4dB if diff freqs are defined with diff LA IDs 2dB SsearchRAT = IE x 2dB Effective 2G threshold = -18 + 4 = 14dB Comments = -18 = -58 x 2 + 1 = -115dBm

For VNPT Internal Use Only (Mar 2012)

Sintersearch

Negative so = 0dB

SsearchRAT, GSM Slimit,searchRAT, GSM ShcsRAT, GSM Qhyst1s Qhyst2s Qoffset1s1 Qoffset2s1 Treselection

4dB

0x2 = 0dB 1x2+1 = 3dB = 2 * 2 = 4dB No Qoffsets 2s

0dB 5dB / 2dB(edge) 2dB 1dB 3dB (diff LA)/5dB (diff RAT) 1 second RSCP signal threshold for measuring GSM = -115 + 3 = -112dBm Qualcomm recommend less effective hysteresis (Qhyst+Qoffset =3dB), and additional Qoffsets for different LAs and different RATs to avoid unnecessary signaling UE may originate in a suboptimal cell if Treselection is too long

ShcsRAT and Slimit,searchRAT


Rules when HCS is not used

For VNPT Internal Use Only (Mar 2012)


5

QHyst2s defaults to QHyst1s


If QHyst2s is not sent in the SIB3

For VNPT Internal Use Only (Mar 2012)


6

Cell (Re-)Selection Parameters on UARFCN 10562 (Multi-Carrier) Hanoi


Cell (Re-) Selection Parameters qQualmin qRxlevmin Sintrasearch NW setting SIB 3 SIB 11 -16dB -105dBm 8dB QC Recommended Settings (Rev K) -18dB / -16dB (edge) -113dBm / -107dBm (edge) 10dB / 8dB (edge) 8dB / 6dB (edge) 4dB if diff freqs are defined with diff LA IDs 2dB 0dB No RSCP-based 2G search threshold Only search for 2G if UE loses suitability (< -115dBm) Qualcomm recommend additional Qoffsets for different LAs/ freqs and different RATs to avoid unnecessary signaling =-53 * 2 + 1 = -105 = 4 * 2 = 8dB Intra-frequency search if Ec/No < -8dB Neighbor Carrier Frequency = 10612 = 3 * 2 = 6dB Intra-frequency search if Ec/No< -10dB = 1 * 2 = 2dB GSM search if Ec/No < -14dB Comments

For VNPT Internal Use Only (Mar 2012)

Sintersearch

6dB

SsearchRAT, GSM Slimit,searchRAT, GSM ShcsRAT, GSM Qhyst1s (RSCP) Qhyst2s (Ec/No) Qoffset1sN Qoffset2sN Treselection

2dB 0dB

Not used = 2 * 2 = 4dB = 1 * 2 = 2dB No Intra-freq Qoff No Inter-freq Qoff for 10612 GSM Qoff1s = 0dB 1 second

5dB / 2dB(edge)

2dB 1dB 3dB (diff LA / freq) 5dB (diff RAT) 1 second

Better than HCMC

Inter-Freq. Re-selection Example Hanoi


From 10562 to 10612 Case #1 No large Qoffset2s Cell Reselection Packets show:
Old Serving Cell: UARFCN: 10562 PSC 240 New Serving Cell; UARFCN: 10612 PSC 451

For VNPT Internal Use Only (Mar 2012)


8

Inter-Freq. Re-selection Example Hanoi


From 10562 to 10612 Case #1
Measurement Packet show Serving Cell 10562 PSC 240
QHyst1s = 4dB RSCP rank = RSCP +4 = -72 + 4 = -68 QHyst2s = 2dB Ec/No rank = EcNo +2 = -11.5 + 2 = -9.5

For VNPT Internal Use Only (Mar 2012)

Inter-freq Ncell 10612 PSC 451


Qoffset2s = -50dB RSCP rank = -90dBm Ec/No rank = -3

Ncell Ec/No Rank (-3dB) > Serving Cell Ec/No Rank (-9.5dB) Reselection critera fulfilled from 13:39:00.620 to 13:39:02.040 (> 1 second Treselection) Cell reselection occurred @ 13:39:03.350 (after reading SIB11)

Cell (Re-)Selection Parameters on UARFCN 10612 (Multi-Carrier) Hanoi


Cell (Re-) Selection Parameters qQualmin qRxlevmin Sintrasearch NW setting SIB 3 SIB 11 -16dB -105dBm 8dB QC Recommended Settings (Rev K) -18dB / -16dB (edge) -113dBm / -107dBm (edge) 10dB / 8dB (edge) 8dB / 6dB (edge) 4dB if diff freqs are defined with diff LA IDs 2dB 0dB No RSCP-based 2G search threshold Only search for 2G if UE loses suitability (< -115dBm) Qualcomm recommend additional Qoffsets for different LAs/ freqs and different RATs to avoid unnecessary signaling =-53 * 2 + 1 = -105 = 4 * 2 = 8dB Intra-frequency search if Ec/No < -8dB Neighbor Carrier Frequency = 10562 and 10587 (not suggested) = 3 * 2 = 6dB Intra-frequency search if Ec/No< -10dB = 1 * 2 = 2dB GSM search if Ec/No < -14dB Comments

For VNPT Internal Use Only (Mar 2012)

Sintersearch

6dB

SsearchRAT, GSM Slimit,searchRAT, GSM ShcsRAT, GSM Qhyst1s (RSCP) Qhyst2s (Ec/No) Qoffset1sN Qoffset2sN Treselection

2dB 0dB

Not used = 2 * 2 = 4dB = 1 * 2 = 2dB No Intra-freq Qoff No Inter-freq Qoff for 10587 and 10562 GSM Qoff1s = 0dB 1 second

5dB / 2dB(edge)

2dB 1dB 3dB (diff LA / freq) 5dB (diff RAT) 1 second

10

Better than HCMC

Inter-Freq. Neighbor Considerations


Inter-Freq Neighbor Relations between 10612 and (10562 and 10587)

For VNPT Internal Use Only (Mar 2012)


11

SIB11 (on freq carrier 10612) shows interfrequency neighbor relations for 10587 10587 is a dedicated HS carrier so UE should not camp on this carrier Large negative Qoff will push the idle UEs from 10587 to 10562 so UE will not stay on 10587 UE will waste time in re-selecting from 10612 to 10587 and then from 10587 to 10562
Suggest removing the inter-freq neighbors for 10612 -> 10587

Inter-Freq. Neighbor Considerations


Inter-Freq Neighbor Relations between 10612 and (10562 and 10587)

For VNPT Internal Use Only (Mar 2012)

Also the inter-freq neighbor relations for carrier freq 10587 were listed before those for carrier freq 10562
There were 22 inter-freq neighbors set for 10587 Only 8 inter-freq neighbors set for 10612 30 inter-freq neighbors make the UEs very busy in measuring these cells The more important inter-freq neighbors should be placed in the SIB11 first After all, inter-freq neighbors for 10587 are not needed (should be removed)

12

Cell (Re-)Selection Parameters on UARFCN 10587 (Multi-Carrier) Hanoi


Cell (Re-) Selection Parameters qQualmin qRxlevmin NW setting SIB 3 SIB 11 -18dB -115dBm QC Recommended Settings (Rev K) -18dB / -16dB (edge) -113dBm / -107dBm (edge) =-58 * 2 + 1 = -115 = 5 * 2 = 10dB UE searches for intra-frequency neighbors if Ec/No < -8dB Neighbor Carrier Frequency = 10612, 10562 (same PSC as 10587) = 2 * 2 = 4dB Comments

For VNPT Internal Use Only (Mar 2012)

Sintrasearch

10dB

10dB / 8dB (edge) 8dB / 6dB (edge) 4dB if diff freqs are defined with diff LA IDs 2dB 0dB

Sintersearch

16dB (Always search for inter-freq neighbors) 4dB 0dB

SsearchRAT, GSM Slimit,searchRAT, GSM ShcsRAT, GSM Qhyst1s (RSCP) Qhyst2s (Ec/No) Qoffset1sN Qoffset2sN Treselection

Not used = 2 * 2 = 4dB = 1 * 2 = 2dB No Intrafreq Qoff GSM Qoff1s = 0dB Qoff 2s = -50dB for same sector on 10562 1 second

5dB / 2dB(edge)

No RSCP-based 2G search threshold Only search for 2G if UE loses suitability (< -115dBm) Qualcomm recommend less effective hysteresis (Qhyst+Qoffset =3dB), and additional Qoffsets for different LAs and different RATs to avoid unnecessary signaling

2dB

1dB 3dB (diff LA)/5dB (diff RAT)

1 second

Better than HCMC

13

Inter-Frequency Ranking Example Hanoi


Qoffset = -50dB Case #1
Large negative Qoffset2s set for inter-freq same sector neighbor Cell Reselection Packet shows
Serving Cell (10587 PSC 240):
QHyst1s = 4dB RSCP rank = RSCP +4 = -61 + 4 = -57 QHyst2s = 2dB Ec/No rank = EcNo +2 = -4 + 2 = -2 Log pkt rank: -4 * 0.5 = -2dB

For VNPT Internal Use Only (Mar 2012)

Inter-freq Ncell (10562 PSC 240):


Qoffset2s = -50dB RSCP rank = -60dBm Ec/No rank = EcNo (-50) = -3.5 + 50 = 46.5 Log pkt rank: 93*0.5 = 46.5

Consistent between calculations and log packet values


14

Inter-Frequency Ranking Example Hanoi


Qoffset = -50dB Case #1 Carrier Frequency 10562 had super high Rank EcIo:
Log pkt @14:24:14.750 Log pkt @ 14:24:16.040

For VNPT Internal Use Only (Mar 2012)

UE was about to trigger Cell Reselection


> 1 second of Treselection UE was starting a new PS call so it stayed on 10587 to avoid delaying the PS call setup

15

Inter-Frequency Ranking Example Hanoi


Large negative Qoffset2s set for inter-freq same sector neighbor@ 10562 Cell Reselection Packet shows
Serving Cell (10587 PSC 240):
QHyst1s = 4dB RSCP rank = RSCP +4 = -65 + 4 = -61 QHyst2s = 2dB Ec/No rank = EcNo +2 = -3 + 2 = -1dB Log pkt rank: -2*0.5 = -1dB

Qoffset = -50dB Case #2

For VNPT Internal Use Only (Mar 2012)

Inter-freq Ncell (10562 PSC 240):


Qoffset2s = -50dB RSCP rank = -62dBm Ec/No rank = EcNo (-50) = -3 + 50 = 47dB Log pkt rank: 94*0.5 = 47dB

16

Consistent between calculations and log packet values

Inter-Frequency Ranking Example Hanoi


Qoffset = -50dB Case #2
PSC 20 on frequency 10562 had super high Rank EcIo:
Log pkt @17:17:46.340 Log pkt @17:17:46.950 Log pkt @17:17:47.590

For VNPT Internal Use Only (Mar 2012)

UE was about to trigger Cell Reselection


> 1 second of Treselection UE needed to read SIBs before camping onto PSC 20 on frequency 10562

17

Inter-Frequency Ranking Example Hanoi


Qoffset = -50dB Case #2 UE started a PS call after camping on PSC 20 on carrier frequency 10562 UE got redirected to carrier frequency 10587 upon Radio Bearer Setup

For VNPT Internal Use Only (Mar 2012)


18

Multi-carrier Strategy Hanoi


From another log, frequency changes from 10587 to 10562 could also be observed in connected mode due to bad coverage on 10587 (some cells may not have the second carrier 10587) UE call setup on carrier frequency 10562 was re-directed to carrier frequency 10587 Need to clarify the multi-carrier camping and call setup redirection strategies From the logs, it looks like that UE camps on carrier frequency 10562 UE may get redirected to carrier frequency 10587 upon call setup UE should re-select to frequency carrier 10562 upon completion

For VNPT Internal Use Only (Mar 2012)


19

Multi-carrier Strategy Hanoi


UE on 10562 Inter-freq neighbor set for freq 10612 in SIB11 without Qoffset No inter-freq neighbor set for freq 10587 in SIB11 10562 and 10612 seem to be the base carriers 10587 is a dedicated carrier for HS call setup redirection Qoffset2s = -50 set to force returning from 10587 to 10562

For VNPT Internal Use Only (Mar 2012)


20

Hanoi Network Configurations


1st Configuration (for low traffic cells) One carrier: 10562 2nd Configuration (for medium traffic cells) Two carriers: 10562 + 10587(HS) 3rd Configuration (for high traffic cells) Three carriers: 10562 + 10587(HS) + 10612 This explains why a large negative Qoffset is used to force the idle UEs back to 10562 10587 mainly for HS traffic (with call setup redirection from 10562) 10562 gives the best contiguous coverage because every cell has this carrier

For VNPT Internal Use Only (Mar 2012)


21

Random Access Parameters HCMC


Random Access Parameters Network Settings (SIB1 / SIB5) QC Recommended Settings (Rev K) Comments Changes to Qualcomm setting can help the overall call setup time in case RACH attempt failure occurred. Low priority change. There should not be impact on NW KPIs

For VNPT Internal Use Only (Mar 2012)

T300

2s

1.2 seconds

N300 Mmax Preamble Retrans Max

5 32 32

5 3 to 6 6 to 10 Existing settings suggest many preamble retransmission attempts with smaller steps which would lead to slower ramp-up and unnecessary uplink interference. QC recommendation is to increase step size and reduce the number of preamble attempts. Closed loop power control can effectively correct required transmit power at later stage. Power offset for the initial preamble (higher constant value can compensate for slower ramp-up, but may use more power than needed) need to check the preamble stats. QC recommendation allows a higher message transmission power for the RRC Connection Request to improve the call setup success rate. Closed loop power control can effectively correct required transmit power at later stage.

Power Ramp Step

1dB

2 to 3 dB

Constant Value

-19dB

-27 to -24 dB

Power Offset
22

Pp-m

-4dB

0 to 2 dB

Random Access Parameters Hanoi


Random Access Parameters Network Settings (SIB1 / SIB5) QC Recommended Settings (Rev K) Comments

For VNPT Internal Use Only (Mar 2012)

T300

2 seconds

1.2 seconds

N300

Too small N300 each cell reselection during random access will increment V300 (out of N300 in total)

Mmax Preamble Retrans Max Power Ramp Step Constant Value

8 20 2dB -20dB

3 to 6 6 to 10 2 to 3 dB -27 to -24 dB QC recommendation allows a higher message transmission power for the RRC Connection Request to improve the call setup success rate. Closed loop power control can effectively correct required transmit power at later stage.

20 x 2 = 40dB correction compared to 10x 3 = 30dB correction (okay)

Power Offset

Pp-m

-2dB

0 to 2 dB

23

Paging Parameters HCMC


Paging Parameters Network Settings QC Recommended Settings (Rev K) Comments

For VNPT Internal Use Only (Mar 2012)

CS Domain CN DRX Cycle Length

0.64s

1.28 seconds

Changing the setting to Qualcomm recommendation has positive impact on the UE battery life time. However, there might be slight impact on the paging performance. Detailed study per market is needed before network wide deployment.

PS Domain CN DRX Cycle Length UTRAN DRX Cycle Length Coefficient PICH Power Offset PI Count per Frame

1.28s 0.64s -7db 18

1.28 to 2.56 seconds 0.64 to 1.28 seconds -7 to -6dB 18 Used in Cell_PCH or URA_PCH

24

Paging Parameters Hanoi


Paging Parameters Network Settings QC Recommended Settings (Rev K) Comments

For VNPT Internal Use Only (Mar 2012)

CS Domain CN DRX Cycle Length

2 ^ (6) * 10ms = 0.64 second

1.28 seconds

PS Domain CN DRX Cycle Length UTRAN DRX Cycle Length Coefficient PICH Power Offset PI Count per Frame

2 ^ (6) * 10ms = 0.64 second 2 ^ (6) * 10ms = 0.64 second -7dB 36

Changing the setting to Qualcomm recommendation has positive impact on the UE battery life time. However, there might be slight impact on the paging performance. Detailed study per market is needed before network wide deployment.

1.28 to 2.56 seconds 0.64 to 1.28 seconds -7 to -6dB 18 Used in Cell_PCH or URA_PCH Higher PICH power offset is required to support a larger PI count per frame so that the PICH decoding success rate can be maintained.

25

For VNPT Internal Use Only (Mar 2012)

26

Connected Mode Parameters

Radio Link Parameters HCMC


Radio Link Parameters N312 Network Settings 1 QC Recommended Settings (Rev K) 1 CPHY-Sync-IND measured over the previous 40 ms period UE may take too long to declare physical channel establishment failure, delay the re-try mechanism leading to a longer physical channel establishment period Comments

For VNPT Internal Use Only (Mar 2012)

T312

10 seconds

1 second

N313

100

50 CPHY-Out-of-Sync-IND each measured over the previous 160 ms period 3 seconds is okay considering call recovery procedure (T314) needs some time to re-establish channels, but current both T314 and T315 are set to 0 (disabled)

T313

Defaults to 3 seconds

3 sec (with call recovery) 5 sec (without call recovery)

N315 T314 T315

Defaults to 1 0s (No call recovery) 0s (No call recovery)

1 CPHY-Sync-IND measured over the previous 160 ms period 12 seconds 12 seconds useT314 in CS RBSetup useT315 in PS RBSetup Suggest enabling call recovery

27

Radio Link Parameters Hanoi


Radio Link Parameters N312 Network Settings 1 QC Recommended Settings (Rev K) 1 CPHY-Sync-IND measured over the previous 40 ms period UE may take too long to declare physical channel establishment failure, delay the re-try mechanism leading to a longer physical channel establishment period Comments

For VNPT Internal Use Only (Mar 2012)

T312

6 seconds

1 second

N313

50

50 CPHY-Out-of-Sync-IND each measured over the previous 160 ms period 3 seconds is okay considering call recovery procedure (T314) needs some time to re-establish channels, but current both T314 and T315 are set to 0 (disabled)

T313

Defaults to 3 seconds

3 sec (with call recovery) 5 sec (without call recovery)

N315 T314 T315

Defaults to 1 0s (No call recovery) 0s (No call recovery)

1 CPHY-Sync-IND measured over the previous 160 ms period 12 seconds 12 seconds useT314 in CS RBSetup useT315 in PS RBSetup Suggest enabling call recovery

28

Handover Parameters (Event1a) [1/2] - HCMC


Handover Parameters Filter Coefficient Intra Freq Meas Quantity Event 1a Reporting Range Event 1a Triggering Condition Event 1a w Event 1a Report Deact. Threshold Network Settings fc2 (289ms) CPICH Ec/No 3 dB Detected Set and Monitored Set Cells 0 2 0 2 QC Recommended Settings (Rev K) fc3 (458ms) CPICH Ec/No 3dB Comments More filtering allows better evaluation of the cell quality

For VNPT Internal Use Only (Mar 2012)


29

Handover Parameters (Event1a) [2/2] - HCMC

For VNPT Internal Use Only (Mar 2012)

Handover Parameters

Network Settings

QC Recommended Settings (Rev K)

Comments

Event 1a Reporting Amount Event 1a Reporting Interval Event 1a Hysteresis

Infinity

Infinity

1s

0.5 or 1 second

0db

0dB Faster addition of fast rising pilots should be considered.

TTT1a Event 1a Reporting Cell Status

320ms All Active, Monitored and/or Detected Set

100ms

30

Handover Parameters (Event1a) [1/2] - Hanoi


Handover Parameters Filter Coefficient Intra Freq Meas Quantity Event 1a Reporting Range Event 1a Triggering Condition Event 1a w Event 1a Report Deact. Threshold Network Settings fc3 (458ms) CPICH Ec/No 3dB Detected Set and Monitored Set Cells 0 2 0 2 Max ASET size = 2+1 = 3 QC Recommended Settings (Rev K) fc3 (458ms) CPICH Ec/No 3dB Comments Hanoi enables more filtering compared to HCMC

For VNPT Internal Use Only (Mar 2012)


31

Handover Parameters (Event1a) [2/2] - Hanoi

For VNPT Internal Use Only (Mar 2012)

Handover Parameters

Network Settings

QC Recommended Settings (Rev K)

Comments

Event 1a Reporting Amount

16

Infinity 4 seconds is too long time for repeating the important Event 1a MRMs as the UE is suffering from the interference of the new cell that is waiting to be added to the ASET.

Event 1a Reporting Interval

4 seconds

0.5 or 1 second

Event 1a Hysteresis

0dB

0dB Faster addition of fast rising pilots should be considered.

TTT1a Event 1a Reporting Cell Status

320ms All Active, Monitored and/or Detected Set

100ms

32

Handover Parameters (Event1b) - HCMC

For VNPT Internal Use Only (Mar 2012)

Handover Parameters

Network Settings

QC Recommended Settings (Rev K)

Comments

Event 1b Reporting Range Event 1b Triggering Condition Event 1b w

5 dB

4.5dB

Active Set Cells

Active Set Cells

Event 1b Hysteresis

0db

0dB

TTT1b Event 1b Reporting Cell Status

640ms

640ms

Within Active Set

33

Handover Parameters (Event1b) - Hanoi


Network Settings QC Recommended Settings (Rev K)

For VNPT Internal Use Only (Mar 2012)

Handover Parameters

Comments Larger ASET size expected as the UE holds onto the degrading cell until it is 6dB below the strongest ASET cell. This can avoid kicking a cell out of the ASET easily and needing to add back quickly this approach can help performance if cell quality is changing rapidly.

Event 1b Reporting Range

6dB

4.5dB

Event 1b Triggering Condition Event 1b w

Active Set Cells

Active Set Cells

Event 1b Hysteresis

0db

0dB

TTT1b Event 1b Reporting Cell Status


34

640ms

640ms

Within Active Set

Handover Parameters (Event1c) - HCMC


Handover Parameters Network Settings QC Recommended Settings (Rev K) Comments

For VNPT Internal Use Only (Mar 2012)

Event 1c Replace. Activation Threshold Event 1c Reporting Amount Event 1c Reporting Interval Event 1c Hysteresis TTT1c Event 1c Reporting Cell Status

Infinity

Infinity

1s

0.5 or 1 second Qualcomm recommendations based on bigger Hysteresis and shorter TTT. For fast rising pilots, it is better to add them faster.

1dB 320ms All Active, Monitored and/or Detected Set

3dB 100ms

35

Handover Parameters (Event1c) - Hanoi


Handover Parameters Network Settings QC Recommended Settings (Rev K) Comments

For VNPT Internal Use Only (Mar 2012)

Event 1c Replace. Activation Threshold Event 1c Reporting Amount

16

Infinity Too long to repeat Event 1c MRMs this may cause delay of ASET update and thus result in high interference or even call drops The super long TTT1c is going to cause performance issues in case of fast rising pilots, especially when R1b is set large (6dB) such that UE may hold onto some weak cells in the ASET, that would take long time to replace.

Event 1c Reporting Interval Event 1c Hysteresis

4 seconds

0.5 or 1 second

= 8 * 0.5 = 4dB

3dB

TTT1c

640ms

100ms

Event 1c Reporting Cell Status

All Active, Monitored and/or Detected Set

36

Handover Parameters (Event 1d) HCMC


Measurement Id 1: Based on Release 99 Measurement (Ec/No based is used). Not used for HSDPA Mobility Handover Parameters Event 1d Hysteresis TTT1d Event 1d Reporting Cell Status Network Settings 7.5dB 2560ms All Active plus Monitored and/or Detected Set Mainly for detecting abnormal conditions QC Recommended Settings (Rev K) Comments

For VNPT Internal Use Only (Mar 2012)

Measurement Id 6: Based on Release 5 Measurement (RSCP based is used). Mainly Used for HSDPA Mobility QC Recommended Settings (Rev K)

Handover Parameters

Network Settings

Comments Low Hysteresis causes frequent HS serving cell changes which results in higher signaling rate and unnecessary data interruptions

Event 1d Hysteresis

1dB

3dB

TTT1d

640ms

640ms High Hysteresis may cause UE to hold onto weaker HS serving cell that results in lower HS performance.

Event 1d Reporting Cell Status


37

Within Active Set

Handover Parameters (Event 1d) Hanoi


Measurement Id 1: Based on Release 99 Measurement (Ec/No based is used). Not used for HSDPA Mobility Handover Parameters Event 1d Hysteresis TTT1d Event 1d Reporting Cell Status Network Settings 4dB 640ms All Active plus Monitored Set QC Recommended Settings (Rev K) 3dB 640ms Comments High Hysteresis may cause UE to hold onto weaker HS serving cell that results in lower HS performance.

For VNPT Internal Use Only (Mar 2012)


38

Compressed Mode Triggering (Event 6d) & DeTriggering (Event 6b) for Voice/Data HCMC
Compressed Mode Triggering Parameters Measurement Quantity Network Settings QC Recommended Settings (Rev K) Comments

For VNPT Internal Use Only (Mar 2012)

ue_TransmittedPower

Filter Coeff.

fc3 Event 6d is triggered when the UE Tx power reaches its maximum value and UE does not have sufficient power to run SF/2 CM. Event 6a is more appropriate with configurable threshold, i.e., at 21dBm to trigger CM

TTT6d

320ms

If event 6a is not configurable, reduce TTT6d to small value such as 0ms

Event 6b Transmitted Power Threshold TTT6b

18dBm 1280ms

39

Compressed Mode Triggering based on Event 6x for Voice/Data Hanoi


Event 6 settings for triggering Compressed Mode are not found in Hanoi logs This means the network is not triggering Compressed Mode based on Uplink conditions

For VNPT Internal Use Only (Mar 2012)


40

Compressed Mode Triggering (Event 2d) and De-Triggering (Event 2f) for Voice HCMC
Compressed Mode Triggering Parameters Network Settings QC Recommended Settings (Rev K)
fc3 Ec/No: -13dB RSCP: -107dBm 0 2dB 320ms Ec/No: -12dB RSCP: -105dBm 0 2dB 1280ms

For VNPT Internal Use Only (Mar 2012)

Comments

Filter Coeff. E2d Used Frequency Threshold (Voice) E2d Used Frequency W E2d Hysteresis TTT2d E2f Used Frequency Threshold (Voice) E2f Used Frequency W E2f Hysteresis TTT2f

fc2 Ec/No: -14dB RSCP: -103dBm 0 Ec/No: 0dB RSCP: 0dB 320ms Ec/No: -12dB RSCP: -100dBm 0 Ec/No: 0dB RSCP: 0dB 1280ms

fc3 is slower in response but considers more time filtering samples

Effective threshold is same (-13dB 1dB = -14dB) for entering the e2d conditions, but it is less easy to leave the CM triggering conditions with QC recommendations: Ec/No > -12dB

Effective threshold is higher for entering the e2f conditions (-12dB + 1dB = -11dB) with QC settings, and the leaving condition is Ec/No > -13dB provided it hit -11dB once

41

Compressed Mode Triggering (Event 2d) and De-Triggering (Event 2f) for PS HCMC
Compressed Mode Triggering Parameters Network Settings QC Recommended Settings (Rev K)
fc3 Ec/No: -15dB RSCP: -109dBm 0 2dB 320ms Ec/No: -14dB RSCP: -107dBm 0 2dB 1280ms

For VNPT Internal Use Only (Mar 2012)

Comments

Filter Coeff. E2d Used Frequency Threshold (Data) E2d Used Frequency W E2d Hysteresis TTT2d E2f Used Frequency Threshold (Data) E2f Used Frequency W E2f Hysteresis TTT2f

fc2 Ec/No: -19dB RSCP: -108dBm 0 Ec/No: 0dB RSCP: 0dB 320ms Ec/No: -17dB RSCP: -105dBm 0 Ec/No: 0dB RSCP: 0dB 1280ms

fc3 is slower in response but considers more time filtering samples

PS Data Event 2d thresholds are very low and this negatively impacts the PS IRAT success rate. Quite likely the call would drop in 3G before being handed to 2G.

42

Compressed Mode Triggering (Event 2d) and De-Triggering (Event 2f) for HS HCMC
Compressed Mode Triggering Parameters Network Settings QC Recommended Settings (Rev K)
fc3 Ec/No: -15dB RSCP: -109dBm 0 2dB 320ms Ec/No: -14dB RSCP: -107dBm 0 2dB 1280ms

For VNPT Internal Use Only (Mar 2012)

Comments

Filter Coeff. E2d Used Frequency Threshold (Data) E2d Used Frequency W E2d Hysteresis TTT2d E2f Used Frequency Threshold (Data) E2f Used Frequency W E2f Hysteresis TTT2f

fc2 Ec/No: -24dB RSCP: -115dBm 0 Ec/No: 0dB RSCP: 0dB 320ms Ec/No: -22dB RSCP: -112dBm 0 Ec/No: 0dB RSCP: 0dB 1280ms

fc3 is slower in response but considers more time filtering samples

PS Data Event 2d thresholds are very low and this negatively impacts the PS IRAT success rate. Quite likely the call would drop in 3G before being handed to 2G.

43

3G to 2G IRAT Parameters HCMC


3G to 2G IRAT (Event 3a) Parameters
UTRAN / GSM Filter Coeff.

For VNPT Internal Use Only (Mar 2012)

Network Settings

QC Recommended Settings (Rev K)

Comments

fc2 / fc1

fc3 / fc0

Event 3a Threshold Own System (WCDMA) Event 3a Threshold Other System (GSM)
E3a Used Frequency W

Ec/No: -14dB

Ec/No: -11dB RSCP: -104dBm

-95dBm

-98dBm

The QC settings are designed to make it easy to go to 2G once CM is started and a suitable GSM cell is found

Event 3a Hysteresis TTT3a Event 3a Reporting Cell Status

0dB 100ms Active, or Virtual Active Set-InterRAT Cells

0dB 0ms Active, or Virtual Active Set-InterRAT Cells Minimum delay

44

Compressed Mode Triggering (Event 2d) and De-Triggering (Event 2f) for HS Hanoi
On 10587 and 10562
Compressed Mode Triggering Parameters Network Settings QC Recommended Settings (Rev K)
fc3 Ec/No: -15dB RSCP: -109dBm 0 2dB 320ms Ec/No: -14dB RSCP: -107dBm 0 2dB 1280ms

For VNPT Internal Use Only (Mar 2012)

Comments

Filter Coeff. E2d Used Frequency Threshold (Data) E2d Used Frequency W E2d Hysteresis TTT2d E2f Used Frequency Threshold (Data) E2f Used Frequency W E2f Hysteresis TTT2f

fc3 Ec/No: -14dB RSCP: -95dBm 0 =4 * 0.5 = 2dB 320ms Ec/No: -12dB RSCP: -92dBm 0 = 4 * 0.5 = 2dB 1280ms

fc3 is slower in response but considers more time filtering samples

PS Data Event 2d/2f RSCP thresholds are very high compared to HCMC settings. The IRAT success rate would be better with these high settings at the expense of 3G coverage. Effective Ec/No thresholds: E2d: -15dB (E2d triggering) E2d: -13dB (E2d de-triggering) E2f: -11dB (E2f triggering) E2f: -13dB (E2f de-triggering) E2d triggering and E2f triggering = 4dB!! Not so easy to de-trigger CM

45

Inter-Frequency Handover Parameters for HS Hanoi


From 10587 (HS carrier) to 10562 (base carrier)
Inter-Frequency Parameters Network Settings
fc3 CPICH_RSCP Periodical 0.5 second Within ActSet AndOr Monitored Used Freq Or Virtual Act Set AndOr Monitored Non Used Freq

For VNPT Internal Use Only (Mar 2012)

QC Recommended Settings (Rev K)


fc3

Comments

Filter Coeff. Freq Quality Estimate Quantity-FDD Periodical / Event Trigger Reporting Interval

Reporting Cell Status

46

Compressed Mode Triggering (Event 2d) and De-Triggering (Event 2f) for Voice Hanoi
On 10562 and 10612
Compressed Mode Triggering Parameters Network Settings QC Recommended Settings (Rev K)
fc3 Ec/No: -13dB RSCP: -107dBm 0 2dB 320ms Ec/No: -12dB RSCP: -105dBm 0 2dB 1280ms

For VNPT Internal Use Only (Mar 2012)

Comments

Filter Coeff. E2d Used Frequency Threshold (Data) E2d Used Frequency W E2d Hysteresis TTT2d E2f Used Frequency Threshold (Data) E2f Used Frequency W E2f Hysteresis TTT2f

fc3 Ec/No: -14dB RSCP: -95dBm 0 =4 * 0.5 = 2dB 320ms Ec/No: -12dB RSCP: -92dBm 0 = 4 * 0.5 = 2dB 1280ms

fc3 is slower in response but considers more time filtering samples

PS Data Event 2d/2f RSCP thresholds are very high compared to HCMC settings. The IRAT success rate would be better with these high settings at the expense of 3G coverage. Effective Ec/No thresholds: E2d: -15dB (E2d triggering) E2d: -13dB (E2d de-triggering) E2f: -11dB (E2f triggering) E2f: -13dB (E2f de-triggering) E2d triggering and E2f triggering = 4dB!! Not so easy to de-trigger CM

47

Inter-Frequency & 3G-to-2G Inter-RAT Handover Parameters for Voice Hanoi


From 10612 (base carrier) to 10562 / 10587 (HS carrier)
Inter-Frequency Parameters Network Settings QC Recommended Settings (Rev K) Comments

For VNPT Internal Use Only (Mar 2012)

# of TGPS for CM UTRAN Filter Coeff. Freq Quality Estimate Quantity-FDD Periodical / Event Trigger Reporting Interval

3 sequences fc3 CPICH_RSCP Periodical 0.5 second Within ActSet AndOr Monitored Used Freq Or Virtual Act Set AndOr Monitored Non Used Freq fc3

Seq 1 for FDD measurement and Seq 2&3 for GSM measurements (RSSI and BSIC)

Reporting Cell Status

48

Inter-Frequency & 3G-to-2G Inter-RAT Handover Parameters for Voice Hanoi


From 10612 (base carrier) to 10562 / 10587 (HS carrier)
3G to 2G IRAT (Event 3a) Parameters
UTRAN / GSM Filter Coeff.

For VNPT Internal Use Only (Mar 2012)

Network Settings

QC Recommended Settings (Rev K)

Comments

fc3 / fc3

fc3 / fc0

Event 3a Threshold Own System (WCDMA) Event 3a Threshold Other System (GSM)
E3a Used Frequency W

RSCP: -97dBm

Ec/No: -11dB RSCP: -104dBm

-95dBm

-98dBm

The existing settings are higher than QC recommendations so this gives better performance at the expense of 3G coverage.

Event 3a Hysteresis TTT3a Event 3a Reporting Cell Status

2dB 0ms Active, or Virtual Active Set-InterRAT Cells

0dB 0ms Active, or Virtual Active Set-InterRAT Cells

= 4 * 0.5 = 2dB

49

Inter-frequency Handover Hanoi (HS)


Step 1: Detection of Weak Frequency and Compressed Mode Configuration Frequency 10587 got weak and UE triggered Event 2d MRM The network sent Phy. Ch. Reconfiguration to configure Compressed Mode measurements

For VNPT Internal Use Only (Mar 2012)


50

Inter-frequency Handover Hanoi (HS)


Step 2: Configuration of Inter-Frequency Neighbors and CM Activation The network sent Measurement Control Message to list inter-frequency neighbors on 10562, and activated Compressed Mode ASET: HS PSC38, PSC208

For VNPT Internal Use Only (Mar 2012)


51

Inter-frequency Handover Hanoi (HS)


Step 3: Inter-frequency Handover via Physical Channel Reconfiguration Finally, the network sent Phy. Ch. Reconfiguration to command the interfrequency handover to 10562 PSC 41

For VNPT Internal Use Only (Mar 2012)


52

3G-to-2G Inter-RAT Handover Hanoi (Voice) triggered by Event 3a

For VNPT Internal Use Only (Mar 2012)


53

HSDPA Parameters (HSDPA Cat 6 / R99 UL SF16) HCMC Cluster 6


HSDPA Parameters Network Settings QC Recommended Settings (Rev K) 2-3 HS-SCCHs if shared with R99 3 if HS only 6.5 to 8.5dB 2 8 ms 1 5 (15/15) or 6 (19/15) for SHO 5 (15/15) 7 (24/15) for SHO 5 (15/15) 7 (24/15) for SHO 1 16 60ms 6 Comments No code-division multiplexing allowed with 1 HS-SCCH. More HS-SCCHs allow scheduling more simultaneous HS users utilizing more code resources.

For VNPT Internal Use Only (Mar 2012)

HS-SCCH Code Info

Measurement Power Offset CQI Feedback Cycle CQI Repetition Factor Delta CQI

8dB 8ms 1 4(12/15) for no SHO 6(19/15) for SHO (some cells only) 5 (15/15) for no SHO 7 (24/15) for SHO (some cells only) 5 (15/15) for no SHO 7 (24/15) for SHO (some cells only) 1 16 50ms 6

Higher power offsets used in C6_PS_VNP_HCM_Cluster6_121 3_01 when UE is in SHO Same power offsets used in C6_PS_VNP_HCM_Cluster6_121 3_02 when UE is in SHO

Delta ACK

Delta NACK ACK-NACK Repetition Factor MAC-hs Window Size Reordering Release Timer T1 Number of HARQ Processes
54

RLC Parameters (HSDPA Cat 6 / R99 UL SF16) HCMC Cluster 6


HSDPA Parameters Transmission RLC Discard Network Settings QC Recommended Settings (Rev K) No Discard Comments No Discard

For VNPT Internal Use Only (Mar 2012)

RLC PDU Size UE RLC Rx Window Size RLC timer Status Prohibit (HSDPA Cat 6) Missing PDU Indicator

336 bits 2047 PDUs

336 bits 2047 PDUs

336 bits okay for low data rate

60ms

Low RLC TSP can avoid RLC window stall, but could cause duplicate retransmission if set less than RLC RTT 1 This should not be set too large to avoid delaying detection of missing PDUs and subsequent RLC retx (TCP ACKs for FTP DL) Max values selected to avoid causing multi-RAB call drops (affecting the voice service); poor RF can still trigger L1 RLF > 191 PDU/s * 0.140 = 27 1 1

Timer Poll

140ms (R99 UL SF16)

150ms

Max Dat Timer RESET Max RESET UE RLC Tx Window Size Last Transmission PDU Poll Last Re-Transmission PDU Poll

30 (R99 UL SF16) 250ms (R99 UL SF16) 4 (R99 UL SF16) 512 (R99 UL SF16) 1 1

40 1000ms 32

55

Selecting RLC PDU Size and TSP


Current RLC PDU size and TSP are good for Cat 6 UE For Targeted Throughput of 7Mbps using Cat 8 UE # RLC PDU/sec = 7Mbit / 320 (PDU payload) = 21875 PDUs/second # RLC PDU in RLC RTT(assumed to be 50ms) = 21875 * 0.05 = 1094 < RLC Rx Win (2047) But in the worst case, # RLC PDU in RLC RTT(50ms) + TSP (60ms) = 21875 * 0.11 = 2406 > RLC Rx Win (2047) Chances of RLC window stall! Therefore, a bigger PDU size or shorter TSP should be used for HSDPA Cat 8 if RLC RTT does not improve RLC RTT + TSP < 93ms in order to keep 7Mbps with 336 bits RLC PDUs If RLC RTT = 50ms (fixed), then TSP = 40ms should be set (< RLC RTT) Duplicate RLC retransmissions can happen so RLC BLER must be low
56

For VNPT Internal Use Only (Mar 2012)

HSDPA Parameters (HSDPA Cat 10 / HSUPA Cat 3) Hanoi


HSDPA Parameters Network Settings QC Recommended Settings (Rev K) 2-3 HS-SCCHs if shared with R99 3 if HS only 6.5 to 8.5dB 2 8 ms 1 5 (15/15) or 6 (19/15) for SHO 5 (15/15) 7 (24/15) for SHO 5 (15/15) 7 (24/15) for SHO 1 16 60ms Actix mis-read issue identified will report this to Actix that misreads the number of HARQ processes Check Huaweis mechanism in changing the power offsets Comments Too many HS-SCCHs would consume code/power resources unnecessarily

For VNPT Internal Use Only (Mar 2012)

HS-SCCH Code Info Measurement Power Offset CQI Feedback Cycle CQI Repetition Factor Delta CQI Delta ACK Delta NACK ACK-NACK Repetition Factor MAC-hs Window Size Reordering Release Timer T1

4 7.5 dB 2ms 1 4(12/15) / 5 (15/15) 4(12/15) / 5 (15/15) 4(12/15) / 5 (15/15) 1 16 60ms Actix showed 5 but network used 6

Number of HARQ Processes

57

RLC Parameters (HSDPA Cat 10 / HSUPA Cat 3) Hanoi


HSDPA Parameters Transmission RLC Discard RLC PDU Size UE RLC Rx Window Size RLC timer Status Prohibit (HSDPA Cat 10) Missing PDU Indicator Network Settings No Discard 656 bits 2047 PDUs QC Recommended Settings (Rev K) No Discard 656 bits 2047 PDUs (HSDPA) Low RLC TSP can avoid RLC window stall, but could cause duplicate retransmission if set less than RLC RTT 1 HSUPA HARQ should correct most errors so timerPoll is not as critical in TX error detection, but the cost of DL status reports is small and this avoids delaying RLC retx (i.e., TCP ACKs for FTP DL) Max values selected to avoid causing multi-RAB call drops (affecting the voice service); poor RF should trigger L1 RLF Comments

For VNPT Internal Use Only (Mar 2012)

60ms

Timer Poll

250ms (HSUPA)

150ms

Max Dat Timer RESET Max RESET UE RLC Tx Window Size Last Transmission PDU Poll Last Re-Transmission PDU Poll

20 (HSUPA) 450ms (HSUPA) 32 (HSUPA) 2047 (HSUPA) 1 1

40 1000ms 32 2047 (HSUPA) 1 1

58

RLC No Discard Scheme


Sender AMD PDU with Polling Bit=1 Receiver

For VNPT Internal Use Only (Mar 2012)

TimerPoll
AMD PDU with Polling Bit=1 STATUS PDU (ACK SUFI)

< MaxDAT -1

MaxDAT

Definition: Controls the maximum number transmissions of a Status PDU (= MaxDAT-1) before the RLC entity is reset (i.e., when VT(DAT) = MaxDAT) Tradeoffs:
Should be large enough to allow time for a temporarily poor radio connection to recover, before the RESET procedure is initiated.

59

Recommended: 40 times (maximized to avoid causing multi-RAB call drops)

RLC Reset Parameters TimerRST


Sender RESET PDU Receiver

For VNPT Internal Use Only (Mar 2012)

TimerRST
RESET PDU RESET ACK PDU

< MaxRST -1

TimerRST Definition: The maximum time to wait for acknowledgement to a RESET PDU before retransmitting the RESET PDU Tradeoff:
Should be set larger than RTT to allow time for a RESET ACK to return Should not be too small which may cause multi-RAB call drops in a short time If set too large, there will be an unnecessarily long delay for the RLC reset process if Radio Link can recover (should be set based on the users tolerance)

60

Recommended: 1000ms = 1 second (max)

RLC Reset Parameters MaxRST


MaxRST
Definition: Controls the maximum number of transmissions of RESET PDU (= MaxRST-1) before declaring Radio Link failure Tradeoff: MaxRST releases the radio connection; it is a tradeoff between:
maximizing the probability of maintaining the Radio Link in temporarily poor radio conditions, minimizing the delay of releasing a call in unrecoverable, bad radio conditions.

For VNPT Internal Use Only (Mar 2012)

For PS data calls, temporarily reduced throughput will be perceived more favorably by the end user than a dropped call. Considering the risk of causing multi-RAB call drops, large MaxRST should be used Recommended: 32 (max)

61

Maximum RLC Reset Process


Poll (maxRST-1) * timerRST Time Unrecoverable Error timerPoll

For VNPT Internal Use Only (Mar 2012)

(maxDat 1) * timerPoll RLC Reset RLC Reset RLC Reset RLC Reset

Bad Radio Channel

How long would it take to drop the call under continuous bad radio channel conditions? HCMC Ericsson: (30-1)*140 + (4-1)*250 = 4810 ms or 4.81 seconds Hanoi Huawei: (20-1)*250 + (32-1)*450 = 18700 ms or 18.7 seconds Qualcomm: (40-1)*150 + (32-1)*1000 = 36850 ms or 36.85 seconds The idea is to keep up the PS call so as to avoid dropping the multi-RAB call affecting the voice service. Suggest holding onto the call until RLF due to L1.

62

For VNPT Internal Use Only (Mar 2012)

63

OVSF Code Allocation

OVSF Code Allocation


Each HSDPA only user consumes only one fixed Associated DPCH which requires one SF128 or SF256 code resource (SF256 more typical), and up to 15 SF16 codes are dynamically shared

For VNPT Internal Use Only (Mar 2012)

(Dynamically assigned and shared among all R99 and HSPA users)

HSUPA requires one common E-AGCH SF = 256 and for each UE, one E-RGCH+E-HICH SF = 128
64

Code Allocation to Allow 15 HS-PDSCHs


To support 15x SF16 HS-PDSCHs, all non- HS-PDSCH channels need to fit into the first SF16 code (= 8x SF128 codes)
CPICH, PCCPCH, AICH and PICH => 2x SF128 codes One SCCPCH SF128 or SF64 for FACH and PCH => 1x or 2x SF128 code One HS-SCCH => 1x SF128 code This allows space of 3x / 4x SF128 codes for the following 1x SF128 for RRC Conn Setup 1x SF256 for R99 A-DPCH 1x SF256 for E-AGCH (for HSUPA) 1x SF128 for E-RGCH+E-HICH (for HSUPA)

For VNPT Internal Use Only (Mar 2012)


65

Code Allocation in Example Log File (HCMC Ericsson) R99 Control in SIB 5
CPICH and PCCPICH
CPICH SF256 code 0 (static) PCCPCH SF256 code 1 (static)
This occupies the 1st SF128 code (code 0)

For VNPT Internal Use Only (Mar 2012)

SIB 5 contains the code assignment for the remaining DL common channels:
AICH SF256 code 2 PICH SF256 code 3
This occupies the 2nd SF128 code (code 1)

SCCPCH (FACH) SF64 code 1


This occupies the 3rd and 4th SF128 codes (code 2 and 3)

SCCPCH (PCH) SF128 code 4


This occupies the 5th SF128 code (code 4)

66

Code Allocation in Example Log File (HCMC Ericsson)


RB Setup contains the code assignment for HS-SCCH(s)
One HS-SCCH SF128 code 5
This occupies the 6th SF128 code

RRC Connection Setup

For VNPT Internal Use Only (Mar 2012)

RB Setup

Altogether, the control channels have occupied the first 6x SF128 codes
One DPCH SF128 code 13 assigned during RRC Connection Setup One R99 A-DPCH SF256 code 13 assigned during RB Setup (in SF128 code 6) No HSUPA but this already spans into the 2nd SF16 code space Max # of HS-PDSCHs = 14

67

Code Allocation in Example Log File (Hanoi - Huawei)


CPICH and PCCPICH
CPICH SF256 code 0 (static) PCCPCH SF256 code 1 (static)
This occupies the 1st SF128 code (code 0)

R99 Control in SIB 5

For VNPT Internal Use Only (Mar 2012)

SIB 5 contains the code assignment for the remaining DL common channels:
AICH SF256 code 2 PICH SF256 code 3
This occupies the 2nd SF128 code (code 1)

SCCPCH (FACH and PCH) SF64 code 1


This occupies the 3rd and 4th SF128 codes (code 2 and 3)

HSUPA Control in RB Setup

SF128 code 4 and 5 not used for R99 common channels:


E-AGCH SF256 code 8 (in SF128 code 4) E-RGCH/HICH SF128 code 5 (first user) SF256 code 9 not used

68

Code Allocation in Example Log File (Hanoi - Huawei)


RB Setup contains the code assignment for HS-SCCH(s)
Four HS-SCCHs SF128 code 6, 7, 8, and 9
This occupies the 7th to 10th SF128 codes

For VNPT Internal Use Only (Mar 2012)

HSDPA Control in RB Setup

Altogether, the control channels have occupied up to the first ten SF128 codes
One SF16 = 8 x SF128 codes First 10 x SF128 codes used
SF128 code 0 to 7 in the first SF16 code space Therefore, SF128 code 8 and 9 already in the second SF16 code space

R99 DPCH in RRC Conn. Setup

R99 A-DPCH in RB Setup

User got allocated initial RRC Connection (SF128 Code 11) and subsequently A-DPCH SF256 code 24 (in SF128 code 12) Max # of HS-PDSCHs = 14
69

HSDPA + HSUPA Code Tree Consumption


To facilitate HSUPA physical layer control information, each HSPA (HSDPA + HSUPA) user consumes:
One SF256 A-DPCH (assuming F-DPCH is not deployed) One SF128 E-RGCH and E-HICH

For VNPT Internal Use Only (Mar 2012)

In addition, a common E-AGCH (One SF256) is required for all HSUPA users in the cell A typical commercial network configuration is as shown below:

Up to 5 HSPA users sharing up to 14x SF16 codes

70

Maximum Number of HSPA Users Per Cell


Maximum number of HSPA users per cell is typically limited by infrastructure software license and hardware When more HSPA or R99 AMR / PS users enter into the cell, the Node B can dynamically reduce the number of HS-PDSCH codes (SF16) to make available code tree space for new users

For VNPT Internal Use Only (Mar 2012)

Up to 11 HSPA users sharing up to 13x SF16 codes

71

More HSPA Users


The following example assumes more HSPA users / AMR / R99 PS users
Up to 21 HSPA users sharing 11 SF16 codes

For VNPT Internal Use Only (Mar 2012)


72

Question #1
100 subscribers in one cell
70 subscribers idle 30 subscribers with PS sessions
20 subscribers in CELL_FACH 10 subscribers in CELL_DCH
3 subscribers using R99 PS with DL 32kbps 7 subscribers using HSDPA+HSUPA (with 2 HS-SCCHs)
2 subscribers scheduled in one TTI 5 subscribers not scheduled in the same TTI

For VNPT Internal Use Only (Mar 2012)

What is the maximum number of HS-PDSCHs that can be assigned?


a) 14 b) 13 c) 15

73

Question #2
If all HSPA users do not receive any DL data scheduling, what is the maximum number of R99 PS384 that can be assigned?
a) 7 b) 6 c) 5

For VNPT Internal Use Only (Mar 2012)


74

For VNPT Internal Use Only (Mar 2012)

75

2G-to-3G IRAT Parameters

2G to 3G IRAT Parameters (2ter & 2quater) - HCMC


2G to 3G IRAT Parameters 3G_SEARCH_PRIO / SEARCH_3G_PRIO Qsearch_I Qsearch_C_Initial Qsearch_C Qsearch_P FDD_Qmin FDD_Qoffset and FDD_GPRS_Qoffset FDD_RSCPmin FDD_REP_QUANT FDD_MULTIRAT_ REPORTING
76

Network Settings

For VNPT Internal Use Only (Mar 2012)

QC Recommended Settings (Rev K) 0 for CS, 1 for PS 7 always 7 always 7 always 7 always -12dB / -10dB (edge) 0 = -infinity (always select a cell if acceptable) -104dBm / -100dBm(edge) RSCP 0 for CS, 3 for PS

Comments

No (CS) Search (always) use Qsearch_I Search (always) Not found -12dB 0 = -infinity (always select a cell if acceptable) or -28dB Not found Ec/No 1

3G Ec/No >= FDD_Qmin 3G RSCP > RLA_C + FDD_Qoffset 3G RSCP > RLA_P + FDD_GPRS_Qoffset RSCP >= FDD_RSCPmin

# of UTRAN FDD cells included in the measurement reports

2G to 3G IRAT Parameters (2ter & 2quater) - Hanoi


2G to 3G IRAT Parameters 3G_SEARCH_PRIO / SEARCH_3G_PRIO Qsearch_I Qsearch_C_Initial Qsearch_C Qsearch_P FDD_Qmin FDD_Qoffset and FDD_GPRS_Qoffset FDD_RSCPmin FDD_REP_QUANT FDD_MULTIRAT_ REPORTING
77

Network Settings

For VNPT Internal Use Only (Mar 2012)

QC Recommended Settings (Rev K) 0 for CS, 1 for PS 7 always 7 always 7 always 7 always -12dB / -10dB (edge) 0 = -infinity (always select a cell if acceptable) -104dBm / -100dBm(edge) RSCP 0 for CS, 3 for PS

Comments

3G Ec/No >= FDD_Qmin 3G RSCP > RLA_C + FDD_Qoffset 3G RSCP > RLA_P + FDD_GPRS_Qoffset RSCP >= FDD_RSCPmin

# of UTRAN FDD cells included in the measurement reports