huawei draft

Huawei Cluster

Summary of Observations

Confidential and Proprietary Qualcomm Global Services, Inc. | MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION 80-XXXXXXX Rev A 3

RACH parameters template with sub optimal settings, call setup with maximum RACH attempts failure detected.

Cases of RRC rejection due to congestion detected.

Cases of failure due to reaching Max allowed RRC connection request seen.

Some access fails detected with missing CC Alert or CC Connect (bad MT call).

Different call setup time seen between RNC1 and RNC4, caused by different SRB channel type selected (FACH vs. DCH).

Different SRB mapping is seen between both RNC in RRC phase (HSPA vs. DCH).

Huawei Clusters Summary of Observations


Many cases of Radio Link Failure detected, and sub optimal settings for Radio Link parameters in both UL and DL.

Call Re-establishment is not activated on RNC-4

Some drops were caused by missing neighbors.

LAC ping pong detected in several areas.

High UL interference seen in some areas reaching ~-70dBm

Some Intra-frequency Mobility parameters needs fine tuning.

Some IDLE parameters needs fine tuning

Huawei Clusters Summary of Observations

Short Voice Calls

RACH Performance


Initial PRACH transmit power depends on the open loop estimate:

Preamble_Initial_Power = Primary CPICH Tx power CPICH_RSCP + UL_Interference + Constant Value

Where: [Primary CPICH Tx power CPICH_RSCP]

Downlink path loss from the NodeB to the UE

Primary CPICH Tx power is sent in SIB5

UL Interference

Interference seen on the UL. Higher the interference, the more transmit power needed to overcome it.

Sent in SIB7

Constant Value

Can account for any difference between Uplink and Downlink propagation and/or transmit-receive chain

Sent in SIB 5

RACH Parameters Preamble Initial Power


Preamble Retransmission Max

Setting Tradeoff: If set large, the uplink interference increases especially in areas requiring more RACH re-transmissions (edge of coverage)

Mmax

Setting Tradeoff: If set large, the uplink capacity consumption may unnecessarily increase

Constant Value

Setting Tradeoff: If set too large, the preamble initial transmit power may be larger than needed for reliable detection at the Node B. This causes unnecessary uplink interference

RACH Parameters Sib 5 RACH Parameters


Power Offset: Power offset of control part of RACH message relative to last transmitted preamble

The Preamble is used to synchronize the physical layers of the UE (Tx) and the NodeB (Rx). Physical layer synchronization means that the NodeB has detected the location (time and frequency) of the UEs signal and demodulated it.

After synchronization, the NodeB sends an acknowledgment on the AICH channel and the UE then transmits the message part of the RACH message. This can be the RRC Connection Request and is decoded by the RRC layer.

RACH Parameters Power Offset P p-m

Preamble

RACH Message

control partP p

-m RACH Message

data part


RACH parameters were extracted for each vendor from the filed test logs.

To simulate RACH performance, fixed Radio condition will be assumed and cell edge conditions will be chosen to demonstrate the performance in poor radio conditions.

Moderately high UL load will be assumed to consider Busy hour performance.

RACH Performance RACH Simulation


Considering average busy hour UL interference of -98dBm, as observed in the test logs and under cell edge conditions (e.g. Ec/No = -14dB and RSCP = -104 dBm) Preamble Initial Power starts at 19dBm and flats out at 24dBm after 4th RACH retransmissions, and for the next 16 retransmissions.

This may increase the UL interference

Lowering Constant value, may reduce the initial Preamble Power

Lowering preambleRetransMax may reduce UL interference

Huawei RACH Simulation Cell Edge Conditions


Keeping UL interference value of -98dBm, at the edge of coverage (RSCP = -104dBm, Ec/No = -14 dB):

Recommended RACH parameters yield to Initial RACH power of 12dBm, and then flats out to max UE Tx Power after 7th RACH re-transmissions

The recommended parameters will reduce the overall UL interference, however monitoring is required to determine any negative impact.

RACH Simulation - Recommended Cell Edge Conditions


Access & Paging Parameters [1/2]

Parameter Huawei Qualcomm

Recom. Comments

DRXCYCLELENCOEF

CN-specific DRX cycle length coefficient

6 7 to 8

[1.28 to 2.56 s]

DRXCYCLELENCOEF

UTRAN-specific DRX cycle length coefficient

6 6 to 7

[0.64 to 1.28 s]

AICHPOWEROFFSET -6 -7 to -5 dB

PICHPOWEROFFSET -7 -7 to -6 dB

POWERRAMPSTEP 2 2 to 3 dB

PREAMBLERETRANSMAX 20 6 to 10 If parameter is too large, the uplink interference increases

Mmax 8 3 to 6 If parameter is too large, the uplink capacity consumption

may unnecessarily increase

Max Allowed UE UL TX power (Sib 3) 24 24 NSN is limiting the UE from using its Maximum power

which decrease the UL coverage


Access & Paging Parameters [2/2]

Parameter Huawei Qualcomm

Recom. Comments

NB01min 0 10 ms The shortest period of time after which a UE can reinitiate a

random access attempt incase a negative AICH Ack. is received

NB01max 0 10 ms This IE shall be set larger or equal to NB01min

Gain Factor c (PRACH) ctfc2: 0

Gain Factor d (PRACH) ctfc2: 0

PowerOffsetPpm ctfc2: 0

c = 13 10

d = 15 15

-3 0 to 2dB If parameter is too small, decoding of the RACH message part

may be unreliable

Gain Factor c (PRACH) ctfc2: 1

Gain Factor d (PRACH) ctfc2: 1

PowerOffsetPpm ctfc2: 1

c = 10 10

d = 15 15

-2 0 to 2dB If parameter is too small, decoding of the RACH message part

may be unreliable

CONSTANTVALUE -20 -27 to -24 dB With large value, the preamble initial transmit power may be

larger than needed for reliable detection at the Node-B, causing

unnecessary uplink interference.

T300 2000 1200 RRC Conn. Req. to RRC Conn. Setup

N300 3 5 The RRC connection might fail due to temporarily insufficient

RF conditions

Short CS Calls


Data was collected to test the performance of AMR Call setup

The Drive test route duration:

Duration of the route was hours and minutes

Four RF carriers were observed during all idle testing rounds

F1 DL UARFCN 10713

F2 DL UARFCN 10738

F3 DL UARFCN 10763

F4 DL UARFCN 3024 - UMTS900 channel

Tests completed in forced UMTS only mode (3G)

Introduction Short Calls Test


M-to-M Short Calls Drive Test Route

short_MO_Calls_DownlinkUARFCN

3024 (511) 14.1%

10713 (2146) 59.2%

10738 (832) 23.0%

10763 (114) 3.1%

3087 (10) 0.3%

10613 (12) 0.3%

Short_MT_Calls-Uu_DownlinkUARFCN

3024 (490) 10.3%

10713 (1621) 34.1%

10738 (2596) 54.7%

3087 (19) 0.4%

10613 (12) 0.3%

2959 (11) 0.2%

Mobile Originated Mobile Terminated


Reason of failure # of failures

No ALERT Message: Bad MT

Call 3

NO CONNECT after ALERT:

Bad MT call 3

RLF during Call Setup 3

max preamble. RACH Failure 2

RBS Failure due to

physicalChannelFailure. Blind IFHO

1

DISCONNECT with unspecified

reason after 25 seconds from

CALL_PROCEEDING. No

RadioBearerSetup Message.

3

Call 1: RLF after Alert and then

Call 2: CM_SERVICE_REJECT 2

UE Not camped on a cell 4

Short Call Analysis AMR Short MO Call Statistics

Metrics KPI Average Value

RF Statistics

ASET Size [#] 1.45

Combined Ec/No [dB] -12.7

RSCP [dBm] -87.7

UE Tx. Power [dBm] -15.25

MO Call Statistics

# MO Call Attempts 239 MO Calls

# RRC Connection Attempts 258 RRC connection request

MO Failure / RRC Connection Failure [#] 21 / 24

MO Call Setup Success Rate [%] 91.2%

RRC Connection Setup Success Rate [%] 90.7 %

Call Setup Latency [sec] 6.5

Random Access (RACH)

Statistics

RRC Connection Setup Time [msec] 320

# of Preambles / RRC Connection Request 1.78

Power of the Last Preamble [dBm] 3.49

# RRC Connection Requests / Successful Call

Attempt 1.15

Mobile Terminated side

issue


Short Call Analysis AMR Short MT Call Statistics

Metrics KPI Average Value

RF Statistics

ASET Size [#] 1.24

Combined Ec/No [dB] -13.2

RSCP [dBm] -86.9

UE Tx. Power [dBm] -13.6

MT Call Statistics

Sample Size [#] 221 MT calls attempt

Call Setup Failures [#] 6

Call Setup Success Rate [%] 97.3 %

RRC Connection Setup Time [msec] 360

Reason of failure # of failures

Call drop during call setup due

to bad RF 3

Maximum # of RRC Connection

Request attempt due to bad RF 2

RRC Connection Reject with

cause Congestion 1


Call setup time for RNC-4 is ~2 seconds higher than call setup time for RNC-1

See next slide for call flow comparison from both RNCs

Call Setup Time vs RNC


Although both RNCs have the same call flow, In this example RNC1 had 1.84 sec less overall call setup time compared to RNC4 In RNC1 RRC Connection Setup message maps SRB on EUL where in RNC4 it maps SRB on DCH

Radio Bearer message maps SRB on DCH in both RNCs

1.5 seconds difference was measured between RRC Connection Setup message and Radio Bearer Setup message

Call Flow comparison between RNC 1 & RNC 4

RNC 1

2.87ms

4.44ms

RNC 4

4.38ms

6.28ms


Comparing the 2 RNCs SIGCHTYPE for different RRC establishment causes 2 difference were found: Originating Conv. Call

Registration

For Originating Conv. Call SRB 13.6 kbps is recommended for shorter call setup time.

For Registration, SRB 3.4 Kbps is recommended for better coverage, since registration occurs in mobility at cell edge.

Call Flow comparison between RNC 1 & RNC 4 RRC Establishment causes vs. SigChType

RRC Establishment Cause RNC 1 RNC 4 RRCCAUSE=ORIGCONVCALLEST SIGCHTYPE=DCH_13.6K_SIGNALLING SIGCHTYPE=DCH_3.4K_SIGNALLING

RRCCAUSE=ORIGSTREAMCALLEST SIGCHTYPE=DCH_13.6K_SIGNALLING SIGCHTYPE=DCH_13.6K_SIGNALLING

RRCCAUSE=ORIGINTERCALLEST SIGCHTYPE=DCH_13.6K_SIGNALLING SIGCHTYPE=DCH_13.6K_SIGNALLING

RRCCAUSE=ORIGBKGCALLEST SIGCHTYPE=DCH_13.6K_SIGNALLING SIGCHTYPE=DCH_13.6K_SIGNALLING

RRCCAUSE=ORIGSUBSTRAFFCALLEST SIGCHTYPE=DCH_13.6K_SIGNALLING SIGCHTYPE=DCH_13.6K_SIGNALLING

RRCCAUSE=TERMCONVCALLEST SIGCHTYPE=DCH_13.6K_SIGNALLING SIGCHTYPE=DCH_13.6K_SIGNALLING

RRCCAUSE=TERMSTREAMCALLEST SIGCHTYPE=DCH_13.6K_SIGNALLING SIGCHTYPE=DCH_13.6K_SIGNALLING

RRCCAUSE=TERMINTERCALLEST SIGCHTYPE=DCH_13.6K_SIGNALLING SIGCHTYPE=DCH_13.6K_SIGNALLING

RRCCAUSE=TERMBKGCALLEST SIGCHTYPE=DCH_13.6K_SIGNALLING SIGCHTYPE=DCH_13.6K_SIGNALLING

RRCCAUSE=EMERGCALLEST SIGCHTYPE=DCH_13.6K_SIGNALLING SIGCHTYPE=DCH_13.6K_SIGNALLING

RRCCAUSE=INTERRATCELLRESELEST SIGCHTYPE=DCH_3.4K_SIGNALLING SIGCHTYPE=DCH_3.4K_SIGNALLING

RRCCAUSE=INTERRATCELLCHGORDEREST SIGCHTYPE=DCH_3.4K_SIGNALLING SIGCHTYPE=DCH_3.4K_SIGNALLING

RRCCAUSE=REGISTEST SIGCHTYPE=DCH_13.6K_SIGNALLING SIGCHTYPE=FACH

RRCCAUSE=DETACHEST SIGCHTYPE=FACH SIGCHTYPE=FACH

RRCCAUSE=ORIGHIGHPRIORSIGEST SIGCHTYPE=DCH_13.6K_SIGNALLING SIGCHTYPE=DCH_13.6K_SIGNALLING

RRCCAUSE=ORIGLOWPRIORSIGEST SIGCHTYPE=FACH SIGCHTYPE=FACH

RRCCAUSE=CALLREEST SIGCHTYPE=DCH_3.4K_SIGNALLING SIGCHTYPE=DCH_3.4K_SIGNALLING

RRCCAUSE=TERMHIGHPRIORSIGEST SIGCHTYPE=DCH_13.6K_SIGNALLING SIGCHTYPE=DCH_13.6K_SIGNALLING

RRCCAUSE=TERMLOWPRIORSIGEST SIGCHTYPE=FACH SIGCHTYPE=FACH

RRCCAUSE=TERMCAUSEUNKNOWN SIGCHTYPE=FACH SIGCHTYPE=FACH

RRCCAUSE=MBMSCALLEST SIGCHTYPE=DCH_3.4K_SIGNALLING SIGCHTYPE=DCH_3.4K_SIGNALLING

RRCCAUSE=DEFAULTEST SIGCHTYPE=DCH_3.4K_SIGNALLING SIGCHTYPE=DCH_3.4K_SIGNALLING


Parameters RNC 1 RNC 4

SrbChlType HSPA HSPA

SrbChlTypeRrcEffectFlag TRUE FALSE

Call Flow comparison between RNC 1 & RNC 4 SRB Mapping

Parameters Description:

SrbChlTypeRrcEffectFlag : Whether the configured type of channel that preferably carries the signaling RB is effective in the case of RRC connection establishment.

SrbChlType : Type of channel that preferably carries the signaling RB. - DCH: Both uplink and downlink are preferably carried on DCH. - HSDPA: Uplink is preferably carried on DCH, and downlink is preferably carried on HS-DSCH. - HSUPA: Uplink is preferably carried on E-DCH, and downlink is preferably carried on DCH. - HSPA: Uplink is preferably carried on E-DCH, and downlink is preferably carried on HS-DSCH.

Further investigation about SRB performance in both cases will be done in the HSDPA/HSUPA project.


For RRC Setup time:

Most of the samples are showing values below 350 ms with few samples above 750 ms !

For Call Setup Time:

Samples distributed around 7 Seconds with few samples showing CST > 15 seconds

Huawei Short Call Analysis RRC Setup / Call Setup Time Distribution (MO)

0%

20%

40%

60%

80%

100%

120%

0%

10%

20%

30%

40%

50%

60%

0.1 0.15 0.2 0.25 0.3 0.35 0.4 0.45 0.5 0.55 0.6 0.65 0.7 0.75 > 0.75

PD

F/C

DF

Time [seconds]

RRC Connection Setup Time

PDF

CDF

0%

20%

40%

60%

80%

100%

120%

0%

10%

20%

30%

40%

50%

3 4 5 6 7 8 9 10 11 12 13 14 15 More

PD

F/C

DF

Time [seconds]

Call Setup Time

PDF

CDF


For Preamble Count:

28% of the samples required more than 1 preambles until an acknowledgement is received.

For last Preamble power:

High sample of RACH attempts sending Preamble with power > 20 dBm

Huawei Short Call Analysis RACH Preamble Count and Power

72%

0%

20%

40%

60%

80%

100%

120%

0%

20%

40%

60%

80%

1 2 3 4 5 6 7 8 9

PD

F/C

DF

Preamble count

RACH Preamble Count

PDF

CDF

0%

20%

40%

60%

80%

100%

120%

0%

5%

10%

15%

20%

25%

< -25.0 -10.0 -5.0 0 5 10 15 20 > 20.0

PD

F/C

DF

Preamble Power [dBm]

RACH Last Preamble Power

PDF

CDF


4% of samples had UL Interference > -95 dBm

Some samples measured UL Interference = -75dBm

Audit of UL Interference is crucial in CDMA NW. This can be captured from NW counters for all Cells

UL Interference as reported by Cell in SIB-7

96%

0%

20%

40%

60%

80%

100%

120%

0%

5%

10%

15%

20%

25%

-109

-108

-107

-106

-105

-104

-103

-102

-101

-100

-99

-98

-97

-96

-95

-94

-93

-92

-91

-90

-89

-88

-87

-86

-76

-75

PD

F/C

DF

UL Interference [dBm]

UL Interference

PDF

CDF


UE receives DISCONNECT message after PROGRESS Message

No Alert Message

Failure at Mobile Terminated side for different reasons

Huawei Short Call Analysis Access Failure due to failure on the MT side


UE never received RB Setup message which lead to setup failure

DISCONNECT message is received after 25 seconds from CALL_PROCEEDING

As UE never received RB Setup Message. This could be related to Radio resources congestion or other reasons.

Huawei Short Call Analysis Access Failure due to No RB Setup message from the NW side


UE Never received CONNECT message after ALERTING message.

UE was in very bad RF and attempted the IFHO, but no good neighbors

UE Turned off its Power Amplifier at 12:56:11

As call setup took long after alerting, user hit DISCONNECT but without going over the air

Second Call Attempt failed with CM_SERVICE_REJECT Cause 101 (Message Not Compatible With The Protocol State)

This is an indication that the NW never released the first call resources

This could be due to NW RLF Failure procedure timers

20 seconds between attempt 1 ALERTING message and attempt 2 CM_SERVICE_REQUEST message.

19 seconds between UE Turing off TX power and second attempts.

Huawei Short Call Analysis 2 back to back Access Failure due to Bad RF & NW timers

Call 1

Call 2


During call setup the NW sent Radio Bear Setup message with Blind HO to U900

UE attempted setup on the U900 cell but failed and returned back to original cell

UE sent RB Setup failure but NW never ACKed the RLC message which lead to RLC Reset.

UE attempted re-establishment but NW sent RRC Connection Release

Huawei Short Call Analysis Access Failure with RB Setup Failure and no Re-establishment


UE initiated LAU/RAU procedure

NW setup the call on FACH state

UE did Cell reselection and Cell Update procedure

Due to some sub-optimal RF condition Procedure took 13 seconds in which the UE will not be pageable.

It is recommended to implement LAU/RAU procedure on Cell_DCH instead of Cell_FACH state

Huawei Short Call Analysis Long LAU/RAU Procedure in FACH state impacts UE Pageability


aside is the nominal call flow showing possible repetitions within call setup.

The UE sends RRC connection request and in case of no replay it waits T300 before repetition, and until N300 times.

Upon reception of the UE request, the RNC will Send RRC connection Setup, N381 times with T381 ms in between repetitions.

The RNC waits to receive RRC connection setup complete within RRCUERSPTMR, in case it wasnt received the RRC fails with cause no replay

Huawei Performance Call Setup timers Flow from Idle

UE RNC

T381

RRC Connection Request

RRC Connection Setup


T381

RRC Connection Request

RRC Connection Setup complete

RR

CU

ER

SP

TM

R


T300


Parameter RNC Dump / from

Logs

Qualcomm

Recomm. Comments

T300 2000 1200 Maximum time from transmission of RRC Connection Request message to reception of

RRC Connection Setup message

If T300 is chosen long, the call set-up delay increases unnecessarily

N300 3 5 Maximum number of retransmissions of the RRC Connection Request message

If N300 is set low, the RRC connection might fail due to temporarily insufficient RF

conditions

T381 D600 [0.6 sec] D600 [0.6 sec] T381 is started after the RNC send message "RRC CONNECTION SETUP"(or "CELL

UPDATE CONFIRM"). If T381 expire and RNC does not receive "RRC CONNECTION

SETUP COMPLETE"(or the response of "CELL UPDATE CONFIRM") and V381 is

smaller than N381, RNC resend "RRC CONNECTION SETUP"(or "CELL UPDATE

CONFIRM") and restart timer T381 and increase V381. If RNC receive "RRC

CONNECTION SETUP COMPLETE"(or the response of "CELL UPDATE CONFIRM"),

T381 will be stopped

N381 D1 D2 - D3

RRCUERSPTMR 5000 [5 Sec] 10000 [10 Sec] Allowing more time to wait for response from the UE helps increase the probability of

success of the RRC connection.

Huawei Performance Parameters Review


Call Setup Performance Recommendations

RF optimization:

This step should be completed before the parameter optimization is applied.

Improve idle mode Ec/No and RSCP in highlighted areas where poor Ec/No and RSCP is observed.

SRB mapped to EUL in RRC Connection Setup message lead to 2 second faster call setup time

Trial of SRB over EUL in RRC Connection Setup is recommended

Review of NW Counters related to establishment success rate and call DCR

LAU/RAU procedure in Cell_FACH state impacted Mobile Terminated Call

LAU/RAU in Cell_FACH procedure takes longer time than Cell_DCH state. This might lead to missed page at the Mobile terminated call side.

Implementing LAU/RAU procedure in Cell_DCH is recommended

Review the impact on Code/Power utilization from NW counters before implementation at NW level

Huawei Long CS Calls


The drive test was done between xx and xx October.

The call was on 37.1% on F1 (10713), 46.6% on F2 (10738), 2.8% on F3 (10763), and 9.9% on F4 (3024).

The UE was locked on 3G.

Huawei Long Call Analysis UARFCN


Low overall EcNo distribution.

22.8% of the samples below -15 dB. This offers weak UMTS coverage.

Further RF optimization is recommeded

Below is EcNo Distribution per carrier, F4 (3024) is showing higher samples in the lower ranges.

See next slide for RSCP distribution.

Huawei Long Call Analysis EcNo - Distribution

0%

5%

10%

15%

20%

25%

30%

35%

40%

-18 -15 -12 -9 -6 0

Best server EcNo Distribution

UARFCN: 3024

UARFCN: 10713

UARFCN: 10738

UARFCN: 10763

Long CS Calls_3G_Locked_ActiveSet_EcNo (dB)

Below -18.00 (28635) 11.0%

>= -18.00 to < -15.00 (30530) 11.8%

>= -15.00 to < -12.00 (61120) 23.6%

>= -12.00 to < -9.00 (76775) 29.6%

>= -9.00 to < -6.00 (38306) 14.8%

Above -6.00 (23804) 9.2%


RSCP Distribution shows good sample percentage in the low ranges which could indicate a poor indoor coverage.

Distributing RSCP per carrier, F4 (3024) is showing the lowest RSCP distribution This might explain the low Ec/Io seen for this layer

Not expected RSCP distribution for U900

Investigation is recommended.

Huawei Long Call Analysis RSCP - Distribution

ActiveSet_CalculatedRSCP_0 (dBm)

Below -115.00 (4984) 1.9%

>= -115.00 to < -105.00 (12510) 4.8%

>= -105.00 to < -95.00 (49497) 19.1%

>= -95.00 to < -85.00 (79496) 30.7%

>= -85.00 to < -75.00 (61236) 23.6%

>= -75.00 to < -60.00 (45709) 17.6%

Above -60.00 (5738) 2.2%

0

0.1

0.2

0.3

0.4

0.5

0.6

0.7

-115 -105 -95 -85 -75 -60 More

PD

F [

%]

RSCP [dBm]

Best server RSCP Distribution

UARFCN: 3024

UARFCN: 10713

UARFCN: 10738

UARFCN: 10763


Assuming EcNo and RSCP thresholds for DL coverage evaluation:

Good EcNo Threshold Up to -14 dB

Good RSCP threshold Up to -95 dBm

Summary: In general around 69.2% of the samples had Good

EcNo and RSCP,

8.1% Good EcNo and Poor RSCP for these areas we have few number of sites but no high load.

5% Poor EcNo and Good RSCP this could indicates pilot pollution or high load areas

17.7% Poor EcNo and RSCP coverage problems/ edge of coverage/ pilot pollution

Further investigation is recommended in these areas

Huawei Long Call Analysis UE Coverage

Uu_Ue_Coverage

GoodEcIo_GoodRSCP (179281) 69.2%

GoodEcIo_PoorRSCP (20914) 8.1%

PoorEcIo_GoodRSCP (13033) 5.0%

PoorEcIo_PoorRSCP (45942) 17.7%


54.1% 33.1%

12.7%

UARFCN: 10713

AS # 1 AS # 2 AS # 3

For Active Set count, 59.4% of the samples showed 1 cell in the active set and 12.2% showed a full Active Set (3 cells)

Distributing the Active Set count per carrier shows that U900 Layer has higher percentage of 1 active set.

This is inline with the Low RSCP, low EcNo detected for the U900 layer in the previous distributions.

Huawei Long Call Analysis Active Set Count

Uu_ActiveSet_Count (Count)

3 (31745) 12.2%

2 (73486) 28.4%

1 (153940) 59.4%

78.6%

17.0%

4.4%

UARFCN: 3024

52.8% 31.4%

15.7%

UARFCN:10738

61.5% 17.3%

21.1%

UARFCN: 10763


UE Tx Power shows good values in general with 93.7% of the samples below 10 dBm.

High UE TX power is localized to certain location

Distributing the UE TX power per carrier shows:

UE sends higher power on F4(3024) This is in line with low RSCP for U900

Huawei Long Call Analysis Tunis UE Tx Power

UE_TxPow (dBm)

Below -25.0 (3803) 29.4%

>= -25.0 to < 0.0 (6859) 53.1%

>= 0.0 to < 10.0 (1318) 10.2%

>= 10.0 to < 15.0 (411) 3.2%

>= 15.0 to < 20.0 (228) 1.8%

Above 20.0 (295) 2.3%

0.0%

20.0%

40.0%

60.0%

80.0%

100.0%

-25 0 10 15 20 More

Ul Tx Power Distribution

UARFCN: 3024

UARFCN: 10713

UARFCN: 10738

UARFCN: 10763


5 radio link failures occurred during the drive test route

3 RRC drops were detected, but they didnt lead to call drops due to the RRC re-establishment.

2 call drops without reestablishment due to bad & missing neighbors then bad RF

Huawei Long Call Analysis Tunis Failures / Drops

Bad RF &

Re-established

Sudden UE Max Tx

Power in good RF &

Re-established

Bad RF &

No Re-establishment

Case3: Missing

Neighbor

No re-establishment

Case 1

Case 2


In good DL Ec/Io & RSCP, UE TX Power suddenly increased to Maximum and lost UL synchronization call dropped

The UE sent Cell_Update to re-establish the call with cause radiolinkFailure.

The call was re-established successfully

See next slide for more analysis

Huawei Long Call Analysis - Case 1 Sudden Max TX power in Good DL RF condition [1/2]


UE was SHO with PSC 390 & 391

NW removed PSC 991 through MCM

PSC 390 Still very strong

UL Power control suddenly lead UE TX Power to Maximum

NW sent UL Out of sync power control pattern

NW sent intra frequency MCM

UE RLC ACKed the message but NW never received the RLC PDU due to bad UL

NW re-transmitted the RLC PDU multiple times till Max DAT occurred and NW turned off DL which lead to UE RLF

Investigation is recommended with Vendor



In good DL Ec/Io & RSCP, UE TX Power suddenly increased to Maximum and lost UL synchronization call dropped

The UE sent Cell_Update to re-establish the call with cause radiolinkFailure.

The call was re-established successfully

See next slide for more analysis


RL Failure Re-

establishment


While UE in CM it sent Inter-Freq MCM

Network Acked the UE RLC with DL RLC PDU

While in relatively good RF condition Sudden increase in UL Tx Power all 1s sent by the UE for DL PC.

And then UL TPC went to Out of sync pattern

This is an indication that the NW turned off DL for some reason

Call dropped and then re-established

Investigation is recommended with Vendor



Due to missing neighbor PSC 72 UE could not add the cell to Active Set

This caused high DL interference as it shows in Power control pattern

UE request all 1s for DL TPC

NW is fluctuating 0s/1s

UE Tx power -4.17dBm

Review location for missing Neighbor

Huawei Long Call Analysis - Case 3 Call drop due to missing Neighbor


DL failure is based on N [N313] consecutive out-of-sync failures.

After M or N out-of-sync indicators are received (by upper layers), a timer is started [T313].

If the timer expires before a specified number of successive in-sync indicators are received [N312], radio link failure is declared.

DL Radio Link Failure Radio Link Failure is based on the Layer 1 Out-of-Sync Condition:

UE

RNC

N313 DPCCH OoSync (UE

Tx-off)

T-313 started

UE declares RLF

And sends 1st Cell Update (T-314 is

started)

T313 Timer

UE can send up to N302 CU, at least every

T302 sec.

(after UE acquires a suitable cell and before

T314/T315 (12 sec/180sec) expires)

N302 Counter ++

T302 = 2 sec Cell Update

Cell Update Confirm N313

Voice/Data Interruption


Call retention relies on delaying RLF declaration on DL, in hope that RF conditions would improve and the call would be maintained

Increasing T313 may improve call drop rate due to RLF

RL Failure Timers OTA RRC Parameters DL RLF Declaration and Recovery Counters

Parameter Type Tunisie QC

Recommendation Comments

N313 UCONNMODETIMER 50 50 Maximum number of successive out of sync indications from L1 to trigger T313 timer begin and monitor/declare physical channel radio link failure

T313 UCONNMODETIMER 3 Sec 5 Sec Maximum time for UE to receive N315 in-sync indications from L1 before declaring radio link failure

N315 UCONNMODETIMER 1 1

Number of successive "in sync" indication required from L1 to stop the

T313 timer. If N315 is chosen too small, the low number of in- sync indications may unnecessarily prevent expiry of the T313 in cases of only

short improvements in link quality delaying declaration of radio link failure.

If N315 is chosen too large the radio link may improve significantly though

T313 may expire leading to declaration of radio link failure before N315 is

reached


RRC Timers Vendors Parameters UL Radio Link Recovery



NoutsyncInd UCELL 20 50

Maximum number of successive out of sync indications to trigger TRIFailure timer begin and monitor/declare physical

channel radio link failure

NInsyncInd UCELL 8 1

times of successive in-sync indications required for the NodeB to

trigger the radio link recovery process. If NInsyncInd is chosen

too small, the low number of in- sync indications may unnecessarily prevent expiry of the TRIFailure in cases of only

short improvements in link quality delaying declaration of radio

link failure. If NInsyncInd is chosen too large the radio link may

improve significantly though TRIFailure may expire leading to

declaration of radio link failure before NInsyncInd is reached

TRLFailure UCELL 50 [5 Sec] 5 sec

Maximum time for UE to receive NInsyncInd in-sync indications before declaring radio link failure. If TRIFailure is chosen short,

NInsyncInd in-sync indications may not be received within this time-frame resulting in the UE declaring radio link failure

prematurely


Maintaining the call longer also depends on the internal timers used for the RRC procedures to be completed (i.e. RRC Messages sent on DL with required RRC UL Complete)

These procedures mainly are: Active Set Update (ASU), Physical Channel Reconfiguration, and Radio Bearer Reconfiguration

Current settings in line with QC recommendations

RRC Timers Vendors Parameters RRC Message Timeouts

Parameter Description Tunisie QC


HoAsuTmr HO active set update response timer 10000 ms 10000 ms A timer for RNC to wait for the response to active set

update in soft handover procedure

HoPhychRecfgTmr HO PhyCh reconfiguration timer 10000 ms 10000 ms A timer for RNC to wait for the response to physical

channel reconfiguration in hard handover procedure

RbSetupRspTmr Wait RB setup response timer 10000 ms 10000 ms A timer for RNC to wait for the RB setup response from

UE in the RB procedure

RbRecfgRspTmr Wait RB reconfig response timer 10000 ms 10000 ms A timer used to wait for the RB reconfiguration response

from UE in the RB procedure


Huawei Long Call Analysis Radio Link Timers & Constants I


Recomm. Comments

T300 UETIMERCONST

2000 1200 ms

Maximum time from transmission of RRC Connection Request message to reception of RRC

Connection Setup message. If T300 is chosen long, the call set-up delay increases

unnecessarily

N300 UETIMERCONST

3 5

Maximum number of retransmissions of the RRC Connection Request message. If N300 is set

low, the RRC connection might fail due to temporarily insufficient RF conditions

T312 UCONNMODETIM

ER 6 sec 1 Sec

Max. time for UE to receive N312 in-sync indications from L1 to confirm establishment of physical channels. If T312 is chosen too long the UE may take too long to declare physical

channel establishment failure, delay the re-try mechanism leading to a longer physical channel

establishment period.

N312 UCONNMODETIM

ER 1 1 Max. number of in-sync indications from L1 to confirm establishment of physical channels

N313 UCONNMODETIM

ER 20 50

Maximum number of successive out of sync indications from L1 to trigger T313 timer begin and monitor/declare physical channel radio link failure. If N313 is chosen too small, the low

number of out of sync indications may unnecessarily trigger T313 in cases of small fluctuations in link quality leading possibly to early declaration of radio link failure

T313 UCONNMODETIM

ER 5 Sec 5 Sec

Maximum time for UE to receive N315 in-sync indications from L1 before declaring radio link failure, If T313 is chosen short, N315 in-sync indications may not be received within this time-frame resulting in the UE declaring radio link failure prematurely


Huawei Long Call Analysis Radio Link Timers & Constants II


Recomm. Comments

T314 UCONNMODETIM

ER

12

0 RNC 4 12 Sec

Maximum time for UE in which it must successfully complete Cell Update

procedure for CS domain due to radio link failure following which UE should

locally release the RRC connection For a CS call a high value has limited benefit,

as it is unlikely that a user will wait so long. Could be gradually increased.

T315 UCONNMODETIM

ER

30

0 RNC 4 180 Sec

Maximum time for UE in which it must successfully complete Cell Update

procedure for PS domain due to radio link failure following which UE should

locally release the RABs. 180 Sec allows for a longer period to recover the call

without requesting for user-intervention and is beneficial for PS service. Could be

gradually increased with assessment of end user behavior.

T302 UCONNMODETIM

ER

2000/

1600 1200 ms

Maximum time for UE from transmission of Cell Update to receive Cell Update

Confirm before it re-attempts Cell Update/ URA Update procedure as long as

N302 is not exceeded. The T302 value is chosen similar to T300

N302 UCONNMODETIM

ER 3 5

Maximum number of re-transmissions of Cell Update/ URA Update message. If

N302 is chosen too small, few re-tries of the Cell Update procedure will be

possible within the T314/T315 before local release of the RRC

Call Re-establishment Feature is NOT activated on RNC4! recommendation to activate it


Huawei Long Call Analysis Intra-frequency Mobility

Parameter Tunisie QC Recomm. Comments

Filter Coefficient (FC) Fc3 Fc3

E1A Reporting Range 6 6 [3dB]

E1A Time To Trigger (TTT) 320 100

If parameter is too large, the UE will delay transmission of MEASUREMENT

REPORT message corresponding to monitored or detected cells of relatively

good quality.

E1B Reporting Range 12 [6dB] 9 [4.5dB] If parameter is set to a value too large, cells of relatively poor quality may not

trigger an Event 1b and capacity will be degraded.

E1B Time To Trigger (TTT) 640 640

E1C Hysteresis 8 6

If parameter is set to a value too large, cells of relatively good quality may not

trigger an Event 1c and will not replace cells of relatively poor quality, therefore

degrading downlink capacity.

E1C Time to trigger 640 100

If parameter is too large, the UE will delay transmission of MEASUREMENT

REPORT message corresponding to monitored cells of relatively better quality

E1D Hysteresis 8 6

E1D Time to trigger 640 640

Reporting Range E1A/E1C 4000 ms 500-1000 ms


Connected Mode Performance Recommendations RF optimization:



Mobility Intra-Frequency Events setting review

Review of Events 1a, 1b, & 1c thresholds and timers.

Neighbor Lists review

Call drop was observed due to missing Neighbor.

Regular audit of Neighbor list relationship is recommended

IRAT Performance


Inter-RAT Handover - Configuration IRAT HO configuration in the test clusters RRC signaling

UE RNC

Measurement Control

Measurement Report

UTRAN configures

Event 2d and Event 2f

Using same thresholds as

Interfrequency HO

Event 2d triggered

RNC activates Compressed Mode

Measurement Control

UE takes WCDMA

measurements

Periodic measurement

Report

UE takes GSM

measurements

Periodic Meas. Report

UTRAN completes IRAT

Handover preparation phase Handover from UTRAN

Handover complete

UE performs IRAT

handover

BSC

RNC sets up GSM measurements

periodic reporting & GSM NL

Phy. Channel Reconfig.


Inter-RAT Handover Definitions

IRAT Compressed Mode and Handover Categories

Compressed Mode

Successful CM Compressed mode ending in IRAT Handover (no deactivation)

Unsuccessful CM Compressed mode ending in CM deactivation

IRAT Interruption time

Duration of interruption to packet data service during Hard Handover from 3G to 2G. Calculated from the difference between the timestamp when the UE receives the DL DCCH CellChangeOrderFromUTRAN from the RNC and the timestamp when the UE sends the L3 UL GPRS MM Routing Area Update Complete to the SGSN.


22 IRAT HHO were performed successfully within the drive test.

Average CM Duration for successful cases = 1.36 Sec

Average Handover Duration = 326 msec

Average G2W reselection time = 1.33 seconds

Tunis IRAT W2G - CS IRAT

0.00%

20.00%

40.00%

60.00%

80.00%

100.00%

0.00%

20.00%

40.00%

60.00%

80.00%

100.00%

350 400 450 500

Handover Duration

PDF

CDF


IRAT Stats: 25 Event 2d reported

25 times Compressed Mode Activated

22 IRAT execution

0 Failures

Compressed Mode efficiency (CM leading to HO) = 22/25 = 88% CM showing good efficiency

IRAT Success rate = 100% CM thresholds are conservative, so the IRAT is done mostly in

good RF decreasing the probability of failure.

Tunis IRAT CS IRAT Efficiency


2 CCO were sent to UE during the test, with an average IRAT Interruption time of 8.15 Sec.

Events Stats:

9 Event 2d reported

8 times Compressed Mode Activated

2 CCO executions

0 Failures

CM Efficiency = 2/8 = 25% Low number of samples due to the extended triggering thresholds

G2W average time = 1.5 sec

Tunis - IRAT W2G - PS R99 CCO

Type Request Success No response Failure Success Rate [%]

Routing Area Update 8 6 2 0 75%


Parameter Recommendations CS IRAT Param.

Event ID

For CS

Comment

Current Settings QC Recom.

3G Core 3G Border

2d

Threshold (-100 | -95 ) /-14 -107/-16 -105/-14 Few cells with -95 threshold

Hysteresis 4 [2dB] 2 dB 2 dB

W 0 0 0

TTT 320 - 640 ms 320 - 640 ms 320 - 640 ms Majority of the cells have TTT = 640ms

2f

Threshold (-97 | -92) /-12 -104/-13 -102/-11 Few cells with -92 threshold

Hysteresis 4 [2dB] 2 dB 2 dB

W 0 0 0

TTT 1280 ms 1280 ms 1280 ms

Filter Coefficient 3 3


Event ID

For PS R99

Comment Current Settings

QC Recom.

3G Core 3G Border

2d

Threshold -105/[-14,-16] -110/-18 -110/-16 Majority of cells -16 dB

Hysteresis 2dB 2 dB 2 dB

W 0 0 0

TTT 320 - 640 ms 320 - 640 ms 320 - 640 ms Majority of cell 640 ms

2f

Threshold -102/[-12,-14] -106/-16 -106/-14

Hysteresis 2dB 2 dB 2 dB

W 0 0 0

TTT 1280 ms 640 -1280 ms 640 -1280 ms

Filter Coefficient 3 3

Parameter Recommendations PS R99 IRAT Param.


Parameter Recommendations GSM-to-WCDMA Reselection

Parameter Tunis QC Recomm. Comment

Q_Search_I/

Q_Search_P

7/ 7

(always) 7 / 7 (always)

For some cells with a setting of 15, searching on 3G is not

allowed. If UE is to return to 3G the setting needs to be changed

to 7.

FDD_Qmin -12 dB -12 dB With Qqualmin = -18 dB and SsearchRAT= 2dB, UE would likely

trigger GSM reselection at CPICH Ec/No < -16 dB and reselect

back to WCDMA at -12 dB

FDD_Qoffset 0 0 (-infinite) Setting this value to 0 would imply that always select a cell if the

quality is acceptable to maximize time on 3G.

FDD_RSCPmin -102 -104 dB Use a setting of -104 dBm to ensure return to 3G cell with good

coverage.

Current settings are in line with recommendations, except for FDD_RSCPmin which could be further stretched to allow for faster return to 3G.


Fast Return to 3G from GSM Proposed trial

After UE releases the CS call while in GSM, network can send Channel Release in GSM with redirection information about WCDMA cell/freq This will trigger the UE to directly move to WCDMA after the CS call release

No Location Area Updating needed Reduced Signaling Overhead

For the feature to function well, the WCDMA neighbor list defined in GSM needs to be configured well measurement-based FR2W FR2W will mainly work when UE reports WCDMA Cell in the last Measurement Repot before the Channel Release

IDLE Performance

Idle Mode Performance Huawei


Data was collected to test the performance of UEs in the idle mode

The Drive test route duration:

Duration of the route was hours and minutes

Four RF carriers were observed during all idle testing rounds

F1 DL UARFCN 10713

F2 DL UARFCN 10738

F3 DL UARFCN 10763

F4 DL UARFCN 3087 - UMTS900 channel

Tests completed in Auto mode (3G/2G)

Introduction Idle Test


Idle State Drive Test Route Technology & Frequency

Technology_Mode

Unknown (887) 0.9%

UMTS Mode (84761) 88.8%

GSM mode (9824) 10.3%

DownlinkUARFCN

3024 (937) 21.9%

10713 (1484) 34.6%

10738 (1675) 39.1%

10763 (192) 4.5%


UE Aggregate Ec/No Map

Low overall Ec/Io Distribution (43.1% of drive route samples > -12 dB)

Aggregate Ec/No is all CPICH power over noise measured for a single PSC. It is what the UE detects in idle mode.

It is the metric used in cell reselection decision

For a loaded system, any area below 18 dB should be investigated.

Areas with poor Ec/No, due

to lack of dominant pilot or

distant cells over-shooting.

Ec/No (dB)

Average -13.5

STDEV 5.3

Recommended

Ec/Io signal

level

distribution

For each cluster and for the market :

> -11 dB for 50% of the area > -13 dB for 80% of the area > -15dB for 95% of the area


Areas where there is coincidence between poor Ec/No and poor RSCP.

An implication that Ec/No is a result of shortage in RSCP coverage.

Addition of sites maybe needed.

Camping Cell RSCP (dBm)

RSCP is the other indicator for evaluating network coverage.

Low overall RSCP Distribution

88.3% of samples > -95dBm

For indoor coverage > -80dBm should be targeted

RSCP (dBm)

Average -80.8

STDEV 12.7

ActiveSet_CalculatedRSCP_0 (dBm)

Below -115.00 (1) 0.0%

>= -115.00 to < -105.00 (417) 0.7%

>= -105.00 to < -95.00 (6539) 11.0%

>= -95.00 to < -85.00 (18022) 30.3%

>= -85.00 to < -75.00 (16857) 28.3%

>= -75.00 to < -60.00 (13025) 21.9%

Above -60.00 (4651) 7.8%

Recommended

RSCP signal

level

distribution

For each cluster and for the market :

> -70 dBm for 95% of dense urban area > -75 dBm for 95% of urban area > -83 dBm for 95% of suburban area > -91 dBm for 95% of rural area


Some cells in the drive route measured high UL Interference

Audit Network counters for cells with high UL Interference is recommended

UL Interference from SIB7 for different Cells

-115

-110

-105

-100

-95

-90

-85

-80

-75

SIB7_ul_Interference

F1 F2 F3 U900


Circled areas experienced multiple Location Area Updates.

Location Area boundaries should be cleaner and has dominant cells to avoid LAU/RAU ping pong

During LAR/RAU the UE will be unreachable and will experience Paging & Mobile Terminated call failures

Cell reselection parameters in these areas need to be more stringent to reduce cell reselection.

Location Area Updates

Location 1.

See details next

slide


Call Start Time End Time Duration RNC STATE LAC Flow Summary

1 10:01:13.617 10:01:16.372 2.76 4 FACH 10001011

2 10:01:35.684 10:01:36.981 1.30 1 DCH 10001001

3 10:01:48.320 10:01:49.682 1.36 1 DCH 10001011

4 10:01:51.457 4 FACH 10000110 UE did Cell Reselection & Cell Update procedure. Bud due to RF, CU procedure failed and registration failed

5 10:02:05.660 10:02:07.227 1.57 2 DCH 10001001

6 10:02:50.621 10:02:53.866 3.25 4 FACH 10000111

7 10:03:02.204 10:03:06.160 3.96 2 DCH 10001001 2 RRC Connection Requests which increased the procedure time

8 10:03:08.063 10:03:11.393 3.33 2 DCH 10000111 2 RRC Connection Requests which increased the procedure time

9 10:03:21.484 10:03:23.929 2.45 4 FACH 10000111

10 10:03:36.971 10:03:38.278 1.31 2 DCH 10001001

11 10:03:41.901 4 FACH 10000111 Cell update in middle of LAU followed by directedsignallingconnectionre-establishment

12 10:03:43.931 10:03:46.606 2.68

(4.7 seconds rom

start of call 11)

4 FACH 10000111

13 10:03:54.421 10:03:55.832 1.41 2 DCH 10001001

14 10:04:12.687 10:04:14.908 2.22 4 FACH 10000111

15 10:04:19.649 10:04:25.999 6.35 4 FACH 10001001 Back to back CU lead to GMM_ROUTING_AREA_UPDATE_REJECT with "implicitly Detached cause

16 10:04:39.859 10:04:43.179

3.32

(23.5 seconds

from start of call

15)

4 FACH 10001001 After LAU UE initiated attach procedure

Summary of Location Area update ping pong (location 1)

Average LAU Procedure while in DCH = 1.39 seconds

Average LAU Procedure without issues or Cell Reselection and while in FACH state = 2.67 seconds.

LAU in Cell FACH had few incidents where Cell Reselection caused longer procedure

Cell Reselection to new LAC while in LAU procedure caused procedure to fail and restart in the new LAC

Some cases LAU procedures took long time

Up to 6.35 Seconds

In worst case 23.5 seconds

Overall, in this location the UE was back to back in multiple LAU procedures for 3 minutes & 30 seconds where the UE is expected to have paging & MT Call issue


Cell Reselection Thresholds Graphical Presentation

Thresholds shown on the figure demonstrate the levels where the UE starts different Cell Reselection procedure

These thresholds can be modified as per traffic distribution strategy requirement.

Thresholds can be set differently on each frequency.


System Parameters

WCDMA Reselection and WCDMA-to-GSM Reselection

Parameter Tunisie Eng. Value QC Rec. Comment

Qqualmin -18 dB -18 dB To maximize WCDMA coverage.

Qrxlevmin -115 dBm -111 dBm OTA value is low, increasing the risk of camping on a cell with poor

coverage quality and inability to reliably receive system information.

Sintrasearch 10 dB 10 dB

Sintersearch 8 dB & 14 dB 8

In all frequencies, 14dB was configured in some cells. Use a

consistent value of 8 dB to allow for the UE to search for cells on the

current frequency carrier then search for cells on the other frequency

carriers. On cells with a setting of 14 dB, the UE will search for a better

cell on the other frequency before searching on the current frequency.

14dB setting forces the UE to start searching for inter-frequency at

Ec/Io =-4dBm which leads to major battery consumption in certain

locations. This is acceptable on frequencies that dont allow idle camping.

SsearchRAT 4 dB 2 dB Tunisie setting will lead to early 3G-> 2G Cell reselection


System Parameters

WCDMA Reselection and WCDMA-to-GSM Reselection

Parameter Tunisie Eng. Value QC Rec. Comment

FDD quality measure Ec/No Ec/No Ensures that loading of the cell is factor in the cell reselection

decision

Qhyst1 (RSCP) 4 dB 2 dB Use a value of 2 dB consistently across cells in the network

Qhyst2 (Ec/No) 2 dB 2 dB Use a value of 2 dB consistently across cells in the network

Treselection 1 sec 1 sec

Use a consistent value of 1 second. Higher value would

increase the risk of loosing coverage while loosing the

opportunity to camp on a good cell

CN DRX cycle length

(CS/PS) 0.64 sec 1.28 sec

1.28 seconds can help improve UE battery time. Higher value,

in certain networks, might impact paging performance. Trail is

recommended on small cluster before implement it on network

level.


Idle Mode Performance Recommendations

RF optimization:



High UL interference reported in the SIB7.

A few cells reported high UL interference above -97 dBm multiple times.

This UL interference could be caused by excessive traffic or initial call setup or RAB setup parameters in which case an audit of the initial RAB and call setup / admission control configuration parameters is recommended.

It may also be caused by external sources and in this case the following is recommended:

UL frequency sweep test on related PSCs might be necessary

Test using external equipment such as a Spectrum Analyzer could also provide insight

Intra-frequency and Inter-frequency Search priority

Adjust S-Intersearch value of 14 to 8 in order to avoid the situation where the UE would search for better cells on other frequency carriers before searching on the current


Idle Mode Performance Recommendations

LAU/RAU Procedures:

It is recommended to implement LAU/RAU procedure in Cell_DCH state instead of Cell_FACH state

Consider re-planning the RNC (LAC) boundary according to the traffic distribution in the areas with ping pong cases

Avoid placing the boundary in high traffic areas.

Trial of DRX 1.28 second Increasing the DRX from 0.64 to 1.28 second will help UE battery time in the NW.

Small cluster to be evaluated before deploying change at NW level

Paging related counters should be evaluated before & after change

huawei draft

Documents