Vous êtes sur la page 1sur 3

1 List out all questions from L1 and give detailed answer to give strongly support discussing with

customer. Responsible: Wubo. Complete date: 2014/5/5


FACH(SMS) RRC SR:
For the FACH RRC SR, there is no way to disable the FACH algorithm as it was in R13. You
can find the detail of this change from the RN.
DCH RRC SR:
please confirm that if HQ just need provide optimization solution to reach the target
value(99.5%), if yes, the optimization method is list in point 3.
service RRC SR:
the same with DCH RRC SR.
IRATHOPS issue
Please feedback current progress and confirm if it need our continue clarification.
RRC REJ OTHER issue
The RRC other congestion is related to an algorithm change between R13 and R14, attached the
detail analysis email. Please confirm if there is any question about the analysis.
The parameter change between R13 and R14
I will reply the email after I confirm it.
2 Provide optimization method for FACH RRC SR. Responsible: Wubo Complete date: 2014/5/5
For the FACH RRC SR, there is way to disable the FACH algorithm as it was in R13. If it need to
continue optimizing, the FACH_USER_NUM_NOT_CTRL switch is the choice.
3 Provide optimization method for Service RRC SR. Responsible: Wubo Complete date: 2014/5/5
The 4 optimizations are as below:
1) Increase Maximum number of resend times of message "RRC CONNECTION SETUP":
SET UCONNMODETIMER: N381=D2; (current value is D1)
2) Choose some top cells of uunoreply and modify the Threshold for intra-frequency cell reselection.
This measure makes the UE access the network in better coverage.
MOD UCELLSELRESEL: CellId=xxxx, IdleSintrasearch=8current value is 5
3) expand the timer used to wait for RRC connection setup complete message from UE in RRC
procedure
SET USTATETIMER: RRCUERSPTMR=13000;current value is 8
4) elude some UE compatibility problem, the detail can be found in the RN and the command
is as below
SET UALGORSVPARA: RsvSwitch0=RESERVED_SWITCH_0_BIT14-1;
1.

The RRC connection setup success rate decreases because some


UEs repeatedly send RRC CONNECTION REQUEST messages to
the RNC.

Trouble Ticket DTS: DTS2012082002280


Number
Description

During the RRC connection setup procedure, some UEs do


not respond to the RRC CONNECTION SETUP messages
sent by the RNC. Instead, they retransmit RRC
CONNECTION REQUEST messages to the RNC. As a result,
the RRC connection setup success rate decreases.

Severity

Suggestion

Root Cause

Upon receiving RRC CONNECTION REQUEST messages


from UEs, the RNC responds with RRC CONNECTION
SETUP messages. However, some UEs retransmit RRC
CONNECTION REQUEST messages instead of sending
response messages to the RNC.
If the number of times that the RNC processes RRC
CONNECTION REQUEST messages retransmitted by a UE
exceeds the value of the N300 parameter in the SET
UIDLEMODETIMER command, the RNC does not process
subsequent RRC CONNECTION REQUEST messages sent
by the UE. Instead, the RNC waits for an RRC CONNECTION
SETUP COMPLETE message from the UE. If the RNC does
not receive any RRC CONNECTION SETUP COMPLETE
message from the UE within the specified time, the RNC
abnormally releases the RRC connection.
However, the UE continues to retransmit RRC CONNECTION
REQUEST messages. As a result, the RRC connection setup
procedure fails several times, reducing the RRC connection
setup success rate.

Solution

Upon receiving an RRC CONNECTION REQUEST message


from a UE, the RNC does not calculate how many times this
message has been processed. After sending an RRC
CONNECTION SETUP message to a UE, the RNC extends
the length of the timer that is used to wait for a response
message from the UE. In this way, the number of abnormally
released RRC connections is reduced.
The reserved bit RESERVED_SWITCH_0_BIT14 of the
RsvSwitch0 parameter in the SET UALGORSVPARA
command is now used to control whether the RNC
optimizes the RRC connection setup procedure.

When this switch is turned on, the RNC optimizes the


procedure. That is, it does not calculate how many times
the RRC CONNECTION REQUEST message has been
processed.

When this switch is turned off, the RNC does not


optimize the procedure. That is, the RNC processes
RRC CONNECTION REQUEST messages based on the
value of the N300 parameter. This switch is turned off by
default.

To turn on this switch, run the following command:

SET UALGORSVPARA: RsvSwitch0 =


RESERVED_SWITCH_0_BIT14-1;
To turn off this switch, run the following command:

SET UALGORSVPARA: RsvSwitch0 =


RESERVED_SWITCH_0_BIT14-0;
The RsvdPara7 parameter in the SET URRRSVDPARA
command is now used to set the length of the timer that is
used to wait for a response message from the UE during an
RRC connection setup procedure. When this timer expires,
the RNC releases the RRC connection. The RsvdPara7
parameter replaces the RrcUeRspTmr parameter in the
SET USTATETIMER command. The RsvdPara7
parameter is valid only when the
RESERVED_SWITCH_0_BIT14 switch is turned on.
The following is an example of setting the RsvdPara7
parameter:
SET URRRSVDPARA: RsvdPara7 = 10000;

Solution Impact When the RESERVED_SWITCH_0_BIT14 switch of the


RsvSwitch0 parameter in the SET UALGORSVPARA
command is turned on, the RRC connection setup success
rate increases and the values of the following counters
increase:
VS.RRC.ConnEstabTimeMax.CellFACH
VS.RRC.ConnEstabTimeMean.CellFACH
VS.RRC.ConnEstabTimeMax.CellDCH
VS.RRC.ConnEstabTimeMean.CellDCH.
Test Case ID

CASE_Commercial_PR_Regression_V9R14C00SPC520_107