VNPT System Parameter Review 20120322

VNPT Network Analysis Report – System Parameter Review

Preliminary version – Mar, 2012

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

2

Table of Content

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

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

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

3

Idle Mode Parameters

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

4

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

Cell (Re-) Selection Parameters

NW setting SIB 3 SIB 11

QC Recommended Settings (Rev K) Comments

qQualmin -18dB -18dB / -16dB (edge) = -18

qRxlevmin -115dBm -113dBm / -107dBm (edge) = -58 x 2 + 1 = -115dBm

Sintrasearch Always 10dB / 8dB (edge)

Sintersearch Negative so = 0dB 8dB / 6dB (edge)

4dB if diff freqs are defined with diff LA IDs

SsearchRAT, GSM 4dB 2dB SsearchRAT = IE x 2dB

Effective 2G threshold = -18 + 4 = -14dB

Slimit,searchRAT, GSM 0x2 = 0dB 0dB

ShcsRAT, GSM 1x2+1 = 3dB 5dB / 2dB(edge) RSCP signal threshold for measuring GSM = -115 + 3 = -112dBm

Qhyst1s Qhyst2s

= 2 * 2 = 4dB 2dB Qualcomm recommend less effective hysteresis (Qhyst+Qoffset =3dB), and additional Qoffsets for different LAs and different RATs to avoid unnecessary signaling

Qoffset1s1 Qoffset2s1

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

Treselection 2s 1 second UE may originate in a suboptimal cell if Treselection is too long

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

5

ShcsRAT and Slimit,searchRAT Rules when HCS is not used

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

6

QHyst2s defaults to QHyst1s If QHyst2s is not sent in the SIB3

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

7

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




qQualmin -16dB -18dB / -16dB (edge)

qRxlevmin -105dBm -113dBm / -107dBm (edge) =-53 * 2 + 1 = -105

Sintrasearch 8dB 10dB / 8dB (edge) = 4 * 2 = 8dB

Intra-frequency search if Ec/No < -8dB

Sintersearch 6dB 8dB / 6dB (edge)


Neighbor Carrier Frequency = 10612 = 3 * 2 = 6dB

Intra-frequency search if Ec/No< -10dB

SsearchRAT, GSM 2dB 2dB = 1 * 2 = 2dB GSM search if Ec/No < -14dB

Slimit,searchRAT, GSM 0dB 0dB

ShcsRAT, GSM Not used 5dB / 2dB(edge) No RSCP-based 2G search threshold

Only search for 2G if UE loses suitability (< -115dBm)

Qhyst1s (RSCP) Qhyst2s (Ec/No)

= 2 * 2 = 4dB = 1 * 2 = 2dB 2dB Qualcomm recommend additional

Qoffsets for different LAs/ freqs and different RATs to avoid unnecessary signaling

Qoffset1sN Qoffset2sN

No Intra-freq Qoff No Inter-freq Qoff for

10612 GSM Qoff1s = 0dB

1dB 3dB (diff LA / freq)

5dB (diff RAT)

Treselection 1 second 1 second Better than HCMC

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

8

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

Int

erna

l Use

Onl

y (M

ar 2

012)

9

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 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)

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

10








Intra-frequency search if Ec/No < -8dB

Sintersearch 6dB 8dB / 6dB (edge)


Neighbor Carrier Frequency = 10562 and 10587 (not suggested)

= 3 * 2 = 6dB Intra-frequency search if Ec/No< -10dB

SsearchRAT, GSM 2dB 2dB = 1 * 2 = 2dB GSM search if Ec/No < -14dB





= 2 * 2 = 4dB = 1 * 2 = 2dB 2dB Qualcomm recommend additional

Qoffsets for different LAs/ freqs and different RATs to avoid unnecessary signaling


No Intra-freq Qoff No Inter-freq Qoff for

10587 and 10562 GSM Qoff1s = 0dB

1dB 3dB (diff LA / freq)

5dB (diff RAT)


For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

11

Inter-Freq. Neighbor Considerations Inter-Freq Neighbor Relations between 10612 and (10562 and 10587) SIB11 (on freq carrier

10612) shows inter-frequency 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

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

12

Inter-Freq. Neighbor Considerations Inter-Freq Neighbor Relations between 10612 and (10562 and 10587) 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)

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

13








UE searches for intra-frequency neighbors if Ec/No < -8dB

Sintersearch 16dB (Always search for inter-freq neighbors)

8dB / 6dB (edge) 4dB if diff freqs are defined with

diff LA IDs

Neighbor Carrier Frequency = 10612, 10562 (same PSC as 10587)

SsearchRAT, GSM 4dB 2dB = 2 * 2 = 4dB





= 2 * 2 = 4dB = 1 * 2 = 2dB 2dB Qualcomm recommend less effective

hysteresis (Qhyst+Qoffset =3dB), and additional Qoffsets for different LAs and different RATs to avoid unnecessary signaling


No Intrafreq Qoff GSM Qoff1s = 0dB Qoff 2s = -50dB for

same sector on 10562

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


For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

14

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

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

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

15

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

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

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

16

Inter-Frequency Ranking Example – Hanoi Qoffset = -50dB Case #2 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

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

Consistent between calculations and log packet values

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

17

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

UE was about to trigger Cell

Reselection > 1 second of Treselection UE needed to read SIBs before

camping onto PSC 20 on frequency 10562

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

18

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

Int

erna

l Use

Onl

y (M

ar 2

012)

19

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

Int

erna

l Use

Onl

y (M

ar 2

012)

20

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

Int

erna

l Use

Onl

y (M

ar 2

012)

21

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

Int

erna

l Use

Onl

y (M

ar 2

012)

22

Random Access Parameters – HCMC

Random Access Parameters

Network Settings (SIB1 /

SIB5)


T300 2s 1.2 seconds

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 KPI’s

N300 5 5

Mmax 32 3 to 6

Preamble Retrans Max 32 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 Ramp Step 1dB 2 to 3 dB

Constant Value -19dB -27 to -24 dB

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.

Power Offset Pp-m -4dB 0 to 2 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.

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

23

Random Access Parameters – Hanoi

Random Access Parameters

Network Settings (SIB1 /

SIB5)


T300 2 seconds 1.2 seconds

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

Mmax 8 3 to 6

Preamble Retrans Max 20 6 to 10

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

Power Ramp Step 2dB 2 to 3 dB

Constant Value -20dB -27 to -24 dB

Power Offset Pp-m -2dB 0 to 2 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.

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

24

Paging Parameters – HCMC

Paging Parameters Network Settings


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 1.28s 1.28 to 2.56 seconds

UTRAN DRX Cycle Length Coefficient 0.64s 0.64 to 1.28 seconds Used in Cell_PCH or URA_PCH

PICH Power Offset -7db -7 to -6dB

PI Count per Frame 18 18 For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

25

Paging Parameters – Hanoi

Paging Parameters Network Settings


CS Domain CN DRX Cycle Length

2 ^ (6) * 10ms = 0.64 second 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

2 ^ (6) * 10ms = 0.64 second 1.28 to 2.56 seconds

UTRAN DRX Cycle Length Coefficient

2 ^ (6) * 10ms = 0.64 second 0.64 to 1.28 seconds Used in Cell_PCH or URA_PCH

PICH Power Offset -7dB -7 to -6dB Higher PICH power offset is required to support a larger PI count per frame so that

the PICH decoding success rate can be maintained. PI Count per Frame 36 18 Fo

r VN

PT I

nter

nal U

se O

nly

(Mar

201

2)

26

Connected Mode Parameters

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

27

Radio Link Parameters – HCMC

Radio Link Parameters Network Settings QC Recommended Settings

(Rev K) Comments

N312 1 1 CPHY-Sync-IND measured over the previous 40 ms period

T312 10 seconds 1 second

UE may take too long to declare physical channel establishment failure, delay the re-try mechanism leading to a longer physical channel establishment period

N313 100 50 CPHY-Out-of-Sync-IND each measured over the previous 160

ms period

T313 Defaults to 3 seconds 3 sec (with call recovery) 5 sec (without call recovery)

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)

N315 Defaults to 1 1 CPHY-Sync-IND measured over the previous 160 ms period

T314 0s (No call recovery) 12 seconds useT314 in CS RBSetup useT315 in PS RBSetup

Suggest enabling call recovery T315 0s (No call recovery) 12 seconds

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

28

Radio Link Parameters – Hanoi

Radio Link Parameters Network Settings QC Recommended Settings

(Rev K) Comments

N312 1 1 CPHY-Sync-IND measured over the previous 40 ms period

T312 6 seconds 1 second

UE may take too long to declare physical channel establishment failure, delay the re-try mechanism leading to a longer physical channel establishment period

N313 50 50 CPHY-Out-of-Sync-IND each measured over the previous 160

ms period

T313 Defaults to 3 seconds 3 sec (with call recovery) 5 sec (without call recovery)

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)

N315 Defaults to 1 1 CPHY-Sync-IND measured over the previous 160 ms period

T314 0s (No call recovery) 12 seconds useT314 in CS RBSetup useT315 in PS RBSetup

Suggest enabling call recovery T315 0s (No call recovery) 12 seconds

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

29

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

Handover Parameters Network Settings


Filter Coefficient fc2 (289ms) fc3 (458ms) More filtering allows better evaluation of the cell quality

Intra Freq Meas Quantity CPICH Ec/No CPICH Ec/No

Event 1a Reporting Range 3 dB 3dB

Event 1a Triggering Condition

Detected Set and Monitored

Set Cells

Event 1a w 0 0

Event 1a Report Deact. Threshold 2 2

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

30

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

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

Event 1a Reporting Amount Infinity Infinity

Event 1a Reporting Interval 1s 0.5 or 1 second

Event 1a Hysteresis 0db 0dB

TTT1a 320ms 100ms Faster addition of fast rising pilots should be considered.

Event 1a Reporting Cell Status

All Active, Monitored and/or Detected Set Fo

r VN

PT I

nter

nal U

se O

nly

(Mar

201

2)

31

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



Filter Coefficient fc3 (458ms) fc3 (458ms) Hanoi enables more filtering compared to HCMC

Intra Freq Meas Quantity CPICH Ec/No CPICH Ec/No

Event 1a Reporting Range 3dB 3dB

Event 1a Triggering Condition

Detected Set and Monitored

Set Cells

Event 1a w 0 0

Event 1a Report Deact. Threshold 2 2 Max ASET size = 2+1 = 3

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

32

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


Event 1a Reporting Amount 16 Infinity

Event 1a Reporting Interval 4 seconds 0.5 or 1 second

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 Hysteresis 0dB 0dB

TTT1a 320ms 100ms Faster addition of fast rising pilots should be considered.


All Active, Monitored and/or Detected Set

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

33

Handover Parameters (Event1b) - HCMC



Event 1b Reporting Range 5 dB 4.5dB

Event 1b Triggering Condition Active Set Cells Active Set Cells

Event 1b w 0 0

Event 1b Hysteresis 0db 0dB

TTT1b 640ms 640ms

Event 1b Reporting Cell Status Within Active Set

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

34

Handover Parameters (Event1b) - Hanoi



Event 1b Reporting Range 6dB 4.5dB

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 Triggering Condition Active Set Cells Active Set Cells

Event 1b w 0 0

Event 1b Hysteresis 0db 0dB

TTT1b 640ms 640ms

Event 1b Reporting Cell Status Within Active Set

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

35

Handover Parameters (Event1c) - HCMC


Event 1c Replace. Activation Threshold 3 3

Event 1c Reporting Amount Infinity Infinity

Event 1c Reporting Interval 1s 0.5 or 1 second

Event 1c Hysteresis 1dB 3dB Qualcomm recommendations based on bigger Hysteresis and shorter TTT. For fast rising pilots, it is better to add them faster. TTT1c 320ms 100ms

Event 1c Reporting Cell Status

All Active, Monitored and/or Detected Set Fo

r VN

PT I

nter

nal U

se O

nly

(Mar

201

2)

36

Handover Parameters (Event1c) - Hanoi


Event 1c Replace. Activation Threshold 3 3

Event 1c Reporting Amount 16 Infinity

Event 1c Reporting Interval 4 seconds 0.5 or 1 second

Too long to repeat Event 1c MRMs – this may cause delay of ASET update and thus result in high interference or even call drops

Event 1c Hysteresis = 8 * 0.5 = 4dB 3dB 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.

TTT1c 640ms 100ms

Event 1c Reporting Cell Status

All Active, Monitored and/or Detected Set

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

37

Handover Parameters (Event 1d) – HCMC

Measurement Id 1: Based on Release 99 Measurement (Ec/No based is used). Not used for HSDPA Mobility


Event 1d Hysteresis 7.5dB

Mainly for detecting abnormal conditions

TTT1d 2560ms

Event 1d Reporting Cell Status

All Active plus Monitored and/or Detected Set

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


Event 1d Hysteresis 1dB 3dB

Low Hysteresis causes frequent HS serving cell changes which results

in higher signaling rate and unnecessary data interruptions

TTT1d 640ms 640ms

Event 1d Reporting Cell Status Within Active Set

High Hysteresis may cause UE to hold onto weaker HS serving cell

that results in lower HS performance.

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

38

Handover Parameters (Event 1d) – Hanoi

Measurement Id 1: Based on Release 99 Measurement (Ec/No based is used). Not used for HSDPA Mobility


Event 1d Hysteresis 4dB 3dB High Hysteresis may cause UE to hold onto weaker HS serving cell

that results in lower HS performance.

TTT1d 640ms 640ms

Event 1d Reporting Cell Status

All Active plus Monitored Set

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

39

Compressed Mode Triggering (Event 6d) & De-Triggering (Event 6b) for Voice/Data – HCMC

Compressed Mode Triggering Parameters Network Settings QC Recommended

Settings (Rev K) Comments

Measurement Quantity ue_TransmittedPower

Filter Coeff. fc3

TTT6d 320ms

If event 6a is not configurable, reduce TTT6d to small value

such as 0ms

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

Event 6b Transmitted Power Threshold 18dBm

TTT6b 1280ms

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

40

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

Int

erna

l Use

Onl

y (M

ar 2

012)

41

Compressed Mode Triggering (Event 2d) and De-Triggering (Event 2f) for Voice – HCMC

Compressed Mode Triggering Parameters

Network Settings

QC Recommended Settings (Rev K)

Comments

Filter Coeff. fc2 fc3 fc3 is slower in response but considers more time filtering samples

E2d Used Frequency Threshold (Voice)

Ec/No: -14dB RSCP: -103dBm

Ec/No: -13dB RSCP: -107dBm 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

E2d Used Frequency W 0 0

E2d Hysteresis Ec/No: 0dB RSCP: 0dB 2dB

TTT2d 320ms 320ms

E2f Used Frequency Threshold (Voice)


Ec/No: -12dB RSCP: -105dBm 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

E2f Used Frequency W 0 0

E2f Hysteresis Ec/No: 0dB RSCP: 0dB 2dB

TTT2f 1280ms 1280ms

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

42

Compressed Mode Triggering (Event 2d) and De-Triggering (Event 2f) for PS – HCMC


Network Settings


Comments


E2d Used Frequency Threshold (Data)



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.



TTT2d 320ms 320ms

E2f Used Frequency Threshold (Data)





TTT2f 1280ms 1280ms

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

43

Compressed Mode Triggering (Event 2d) and De-Triggering (Event 2f) for HS – HCMC


Network Settings


Comments





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.



TTT2d 320ms 320ms






TTT2f 1280ms 1280ms

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

44

3G to 2G IRAT Parameters – HCMC

3G to 2G IRAT (Event 3a) Parameters Network Settings QC Recommended


UTRAN / GSM Filter Coeff.

fc2 / fc1 fc3 / fc0

Event 3a Threshold Own System (WCDMA) Ec/No: -14dB

Ec/No: -11dB RSCP: -104dBm 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 Threshold Other System (GSM) -95dBm -98dBm

E3a Used Frequency W 0 0

Event 3a Hysteresis 0dB 0dB

TTT3a 100ms 0ms Minimum delay


Active, or Virtual Active Set-InterRAT Cells

Active, or Virtual Active Set-InterRAT

Cells

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

45

Compressed Mode Triggering (Event 2d) and De-Triggering (Event 2f) for HS – Hanoi


Network Settings


Comments




Ec/No: -15dB RSCP: -109dBm 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


E2d Hysteresis =4 * 0.5 = 2dB 2dB

TTT2d 320ms 320ms





E2f Hysteresis = 4 * 0.5 = 2dB 2dB

TTT2f 1280ms 1280ms

On 10587 and 10562

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

46

Inter-Frequency Handover Parameters for HS – Hanoi

Inter-Frequency Parameters Network Settings


Comments

Filter Coeff. fc3 fc3

Freq Quality Estimate Quantity-FDD CPICH_RSCP

Periodical / Event Trigger Periodical

Reporting Interval 0.5 second

Reporting Cell Status

Within ActSet AndOr Monitored

Used Freq Or Virtual Act Set

AndOr Monitored Non Used Freq

From 10587 (HS carrier) to 10562 (base carrier)

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

47

Compressed Mode Triggering (Event 2d) and De-Triggering (Event 2f) for Voice – Hanoi


Network Settings


Comments




Ec/No: -13dB RSCP: -107dBm 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


E2d Hysteresis =4 * 0.5 = 2dB 2dB

TTT2d 320ms 320ms





E2f Hysteresis = 4 * 0.5 = 2dB 2dB

TTT2f 1280ms 1280ms

On 10562 and 10612

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

48

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

Inter-Frequency Parameters Network Settings QC

Recommended Settings (Rev K)

Comments

# of TGPS for CM 3 sequences Seq 1 for FDD measurement and Seq 2&3 for GSM measurements (RSSI and BSIC)

UTRAN Filter Coeff. fc3 fc3

Freq Quality Estimate Quantity-FDD CPICH_RSCP

Periodical / Event Trigger Periodical

Reporting Interval 0.5 second

Reporting Cell Status

Within ActSet AndOr Monitored

Used Freq Or Virtual Act Set

AndOr Monitored Non Used Freq

From 10612 (base carrier) to 10562 / 10587 (HS carrier)

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

49

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

3G to 2G IRAT (Event 3a) Parameters Network Settings QC Recommended


UTRAN / GSM Filter Coeff.

fc3 / fc3 fc3 / fc0

Event 3a Threshold Own System (WCDMA) RSCP: -97dBm

Ec/No: -11dB RSCP: -104dBm The existing settings are higher than

QC recommendations so this gives better performance at the expense

of 3G coverage. Event 3a Threshold Other System (GSM) -95dBm -98dBm

E3a Used Frequency W 0 0

Event 3a Hysteresis 2dB 0dB = 4 * 0.5 = 2dB

TTT3a 0ms 0ms


Active, or Virtual Active Set-InterRAT Cells

Active, or Virtual Active Set-InterRAT

Cells

From 10612 (base carrier) to 10562 / 10587 (HS carrier)

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

50

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

Int

erna

l Use

Onl

y (M

ar 2

012)

51

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

Int

erna

l Use

Onl

y (M

ar 2

012)

52

Inter-frequency Handover – Hanoi (HS) Step 3: Inter-frequency Handover via Physical Channel Reconfiguration

Finally, the network sent Phy. Ch. Reconfiguration to command the inter-frequency handover to 10562 PSC 41

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

53

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

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

54

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

Network Settings QC


Comments

HS-SCCH Code Info 1 2-3 HS-SCCHs if shared with R99

3 if HS only

No code-division multiplexing allowed with 1 HS-SCCH. More HS-SCCHs allow scheduling more simultaneous HS users utilizing more code resources.

Measurement Power Offset 8dB 6.5 to 8.5dB

CQI Feedback Cycle 8ms 2 – 8 ms

CQI Repetition Factor 1 1

Delta CQI 4(12/15) for no SHO

6(19/15) for SHO (some cells only)

5 (15/15) or 6 (19/15) for SHO Higher power offsets used in

C6_PS_VNP_HCM_Cluster6_1213_01 when UE is in SHO Same power offsets used in C6_PS_VNP_HCM_Cluster6_1213_02 when UE is in SHO

Delta ACK 5 (15/15) for no SHO

7 (24/15) for SHO (some cells only)

5 (15/15) 7 (24/15) for SHO

Delta NACK 5 (15/15) for no SHO

7 (24/15) for SHO (some cells only)

5 (15/15) 7 (24/15) for SHO

ACK-NACK Repetition Factor 1 1

MAC-hs Window Size 16 16

Reordering Release Timer T1 50ms 60ms

Number of HARQ Processes 6 6

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

55

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

Network Settings QC


Comments

Transmission RLC Discard No Discard No Discard

RLC PDU Size 336 bits 336 bits 336 bits okay for low data rate

UE RLC Rx Window Size 2047 PDUs 2047 PDUs

RLC timer Status Prohibit (HSDPA Cat 6) 60ms

Low RLC TSP can avoid RLC window stall, but could cause duplicate retransmission if set less than RLC RTT

Missing PDU Indicator 1 1

Timer Poll 140ms (R99 UL SF16) 150ms

This should not be set too large to avoid delaying detection of missing PDUs and subsequent RLC retx (TCP ACKs for FTP DL)

Max Dat 30 (R99 UL SF16) 40 Max values selected to avoid causing multi-RAB call drops (affecting the voice service); poor RF can still trigger L1 RLF

Timer RESET 250ms (R99 UL SF16) 1000ms

Max RESET 4 (R99 UL SF16) 32

UE RLC Tx Window Size 512 (R99 UL SF16) > 191 PDU/s * 0.140 = 27

Last Transmission PDU Poll 1 1

Last Re-Transmission PDU Poll 1 1

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

56

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

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

57

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

Network Settings QC


Comments

HS-SCCH Code Info 4 2-3 HS-SCCHs if shared with R99

3 if HS only

Too many HS-SCCHs would consume code/power resources unnecessarily

Measurement Power Offset 7.5 dB 6.5 to 8.5dB

CQI Feedback Cycle 2ms 2 – 8 ms

CQI Repetition Factor 1 1

Delta CQI 4(12/15) / 5 (15/15) 5 (15/15) or

6 (19/15) for SHO

Check Huawei’s mechanism in changing the power offsets Delta ACK 4(12/15) / 5 (15/15)

5 (15/15) 7 (24/15) for SHO

Delta NACK 4(12/15) / 5 (15/15) 5 (15/15)

7 (24/15) for SHO

ACK-NACK Repetition Factor 1 1

MAC-hs Window Size 16 16

Reordering Release Timer T1 60ms 60ms

Number of HARQ Processes Actix showed 5

but network used 6 6

Actix mis-read issue identified – will report this to Actix that mis-reads the number of HARQ processes

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

58

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

Network Settings QC Recommended Settings (Rev K) Comments

Transmission RLC Discard No Discard No Discard

RLC PDU Size 656 bits 656 bits

UE RLC Rx Window Size 2047 PDUs 2047 PDUs (HSDPA)

RLC timer Status Prohibit (HSDPA Cat 10) 60ms

Low RLC TSP can avoid RLC window stall, but could cause duplicate retransmission if set less than RLC RTT

Missing PDU Indicator 1 1

Timer Poll 250ms (HSUPA) 150ms

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 Dat 20 (HSUPA) 40 Max values selected to avoid causing multi-RAB call drops (affecting the voice service); poor RF should trigger L1 RLF

Timer RESET 450ms (HSUPA) 1000ms

Max RESET 32 (HSUPA) 32

UE RLC Tx Window Size 2047 (HSUPA) 2047 (HSUPA)

Last Transmission PDU Poll 1 1

Last Re-Transmission PDU Poll 1 1

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

59

RLC No Discard Scheme

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.

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

STATUS PDU (ACK SUFI)

AMD PDU with Polling Bit=1

Sender Receiver

AMD PDU with Polling Bit=1

TimerPoll < MaxDAT -1

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

60

RLC Reset Parameters – TimerRST

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 user’s tolerance)

Recommended: 1000ms = 1 second (max)

RESET ACK PDU

RESET PDU

Sender Receiver

RESET PDU TimerRST < MaxRST -1

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

61

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 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)

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

62

Maximum RLC Reset Process

Bad Radio Channel

(maxDat – 1) * timerPoll

timerPoll (maxRST-1) * timerRST

RLC Reset

RLC Reset

RLC Reset

RLC Reset

Poll UnrecoverableError

How long would it take to drop the call under continuous bad radio channel conditions?

Time

HCMC Ericsson: (30-1)*140 + (4-1)*250 = 4810 ms or 4.81 secondsHanoi Huawei: (20-1)*250 + (32-1)*450 = 18700 ms or 18.7 secondsQualcomm: (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.

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

63

OVSF Code Allocation

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

64

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

(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

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

65

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)

Fo

r VN

PT I

nter

nal U

se O

nly

(Mar

201

2)

66

Code Allocation in Example Log File (HCMC – Ericsson) CPICH and PCCPICH CPICH SF256 code 0 (static) PCCPCH SF256 code 1 (static)

This occupies the 1st SF128 code (code 0)

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)

R99 Control in SIB 5

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

67

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

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

RB Setup

RRC Connection Setup

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

68

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)

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)

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

R99 Control in SIB 5

HSUPA Control in RB Setup

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

69

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

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

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

R99 DPCH in RRC Conn. Setup

HSDPA Control in RB Setup

R99 A-DPCH in RB Setup

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

70

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

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

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

71

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

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

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

72

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

Int

erna

l Use

Onl

y (M

ar 2

012)

73

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

What is the maximum number of HS-PDSCHs that can be assigned? a) 14 b) 13 c) 15

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

74

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

Int

erna

l Use

Onl

y (M

ar 2

012)

75

2G-to-3G IRAT Parameters

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

76

2G to 3G IRAT Parameters (2ter & 2quater) - HCMC 2G to 3G IRAT Parameters Network Settings QC Recommended


3G_SEARCH_PRIO / SEARCH_3G_PRIO No (CS) 0 for CS, 1 for PS

Qsearch_I Search (always) 7 – always

Qsearch_C_Initial use Qsearch_I 7 – always

Qsearch_C Search (always) 7 – always

Qsearch_P Not found 7 – always

FDD_Qmin -12dB -12dB / -10dB (edge) 3G Ec/No >= FDD_Qmin

FDD_Qoffset and FDD_GPRS_Qoffset

0 = -infinity (always select a cell if acceptable) or

-28dB

0 = -infinity (always select a cell if acceptable)

3G RSCP > RLA_C + FDD_Qoffset 3G RSCP > RLA_P + FDD_GPRS_Qoffset

FDD_RSCPmin Not found -104dBm /

-100dBm(edge) RSCP >= FDD_RSCPmin

FDD_REP_QUANT Ec/No RSCP

FDD_MULTIRAT_ REPORTING

1 0 for CS, 3 for PS # of UTRAN FDD cells included in the measurement reports

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

77

2G to 3G IRAT Parameters (2ter & 2quater) - Hanoi 2G to 3G IRAT Parameters Network Settings QC Recommended


3G_SEARCH_PRIO / SEARCH_3G_PRIO 0 for CS, 1 for PS

Qsearch_I 7 – always

Qsearch_C_Initial 7 – always

Qsearch_C 7 – always

Qsearch_P 7 – always

FDD_Qmin -12dB / -10dB (edge) 3G Ec/No >= FDD_Qmin

FDD_Qoffset and FDD_GPRS_Qoffset

0 = -infinity (always select a cell if acceptable)

3G RSCP > RLA_C + FDD_Qoffset 3G RSCP > RLA_P + FDD_GPRS_Qoffset

FDD_RSCPmin -104dBm /

-100dBm(edge) RSCP >= FDD_RSCPmin

FDD_REP_QUANT RSCP

FDD_MULTIRAT_ REPORTING

0 for CS, 3 for PS # of UTRAN FDD cells included in the measurement reports

For

VNPT

Int

erna

l Use

Onl

y (M

ar 2

012)

VNPT System Parameter Review 20120322

Documents

Transcript of VNPT System Parameter Review 20120322