HUAWEI UAE INTERVIEW QUESTION

1- How to handle the RRC setup success

rate problem
To handle this problem the following information is needed to check.
Coverage status
( if user is far away from the node-b there will be a possibility of UU no-reply during the RRC connestion request
usually downlink signal can received by the UE but the node-b cannot received the UL signal from the UE )
Here is the related counter to determine this problem
VS.RRC.FailConnEstab.NoReply
Congestion status ( you can use the counter VS.RRC.FailConnEstab.Cong to see if the reason of RRC failure
due to congestion. OMSTAR can give the detail in which type of congestion is experience by the cell using the
following counter

VS.RRC.Rej.ULPower.Cong
VS.RRC.Rej.DLPower.Cong
VS.RRC.Rej.ULIUBBand.Cong
VS.RRC.Rej.DLIUBBand.Cong
VS.RRC.Rej.ULCE.Cong
VS.RRC.Rej.DLCE.Cong
VS.RRC.Rej.Code.Cong

Hardware related problem

If this problem is needed te evaluate , we can check the status of the site using the
M2000, the common case that the site is having problen with harware is the site is
indicating an alarm. And from the KPI statisting some time we can see the value of
this counter is also high

VS.RRC.Rej.RL.Fail,

Transmission problem
For transimision problem you can observe this counter to check the reson of failure is
related to transmision or not.

Transmission quality can easily see in the M2000. Check the IPPM trend to see if there
is a packet loss

VS.RRC.Rej.TNL.Fail
 2- How to handle the RAB setup success
rate problem
The process of checking and solving the RAB connection failure is almost the
same as RRC connection problem if you will consider the transmission.
Hardware and congestion problem.

We can reffer on the following counter to analyze the reason of RAB fail due to
congestion

VS.RAB.FailEstabCS.Cong Number of Failed CS RAB Establishments for Cell (Congestion)

VS.RAB.FailEstabCS.DLIUBBand.Cong
VS.RAB.FailEstabCS.ULIUBBand.Cong
VS.RAB.FailEstabCS.ULCE.Cong
VS.RAB.FailEstabCS.DLCE.Cong
VS.RAB.FailEstabCS.Code.Cong
VS.RAB.FailEstabCS.ULPower.Cong
VS.RAB.FailEstabCS.DLPower.Cong
Number of Failed CS RAB Establishments for Cell (DL Iub Bandwidth Congestion)
Number of Failed CS RAB Establishments for Cell (UL Iub Bandwidth Congestion)
Number of Failed CS RAB Establishments for Cell (UL CE Congestion)
Number of Failed CS RAB Establishments for Cell (DL CE Congestion)
Number of Failed CS RAB Establishments for Cell (Code Congestion)
Number of Failed CS RAB Establishments for Cell (UL Power Congestion)
Number of Failed CS RAB Establishments for Cell (DL Power Congestion)

If the problem is related to transmission quality we can check this counter

VS.RAB.FailEstabCS.TNL

If the problem is related to RF we can check this counter

VS.RAB.FailEstabCS.UuNoReply

3-How to solve the code congestion

- Idealy if code congestion is happening we need to add new site or new carrier to
solve this problem. But for some cases the new site or new carrier is not require. We
need to optimized the cell having this problem using the current resource for code.

- In every cell we have 256 codes available and if the code define in the HSDPA is 15
we can limit the number of code alocated to HSDPA to allow more user to access the
cell. but this solution will make a low thrpougput to HSDPA user
- Theres a way also that User from one cell can shared to other neighboring cell , we
can limit the number of user that can access the cell to ensure that congestion will be
eliminated and let the other UEs camp on the neighboring cell

- We can enable the LDR function to easily share the traffic to the other cell or
interfrequency neighboring cell if the serving cell is experiencing the congestion.

- We can also enable the DRD ( directed retry decision ) this feature of huawei system
is applicable of multi carier netword in which the network can be set a priority of
service to be handle by each carier. Normally this is happen during the RRC and
RAB setup phase. Once the service type is identify by the system, it will initiate a
blind handover decision to the UE in order to camp on the target network carrier.

4-How to solve the UL power congestion

- Usually this proble is happening if the cell is serving so many user that make the
RTWP high, to avoid this problem ths first solution is to share the traffic to the
neighboring cell.
- we can modify the SHO parameter to make the handover fast to easily share the
user to neighboring cell
- modify the number of subscriber allowed to camp on a certain cell to inrease the
threslhold of UL power congestion ( please see the sample command below )
MOD UCELLCAC:CELLID=AIRCOM,ULTOTALEQUSERNUM=140; we can set the value up To 200
- we can add new site or New sector to offload the traffic of the congested cell
- we can add new carrier if F2 is available

5 How to solve RTWP problem

- check the traffic is high. RTWP is high if the user sa so many in the coverage area.
If the user is so many we can limit the number of user and share the user to other
neighboring cell, in No load condition it is normal that RTWP value is -103 Dbm,.
But if traffic is high we can say that -97 dbm is normal

- check the status of hardware, there is a case the RTWP is high dure hardware
problem. Some time it is related to TMA connected to the antenna system

- check if there is External interference in the netwokr, if the value of RTWP is

exceeding or close to the value of -85 dbm, there will be a posibility of external
interference. To do more evalutaion about this problen should notice that other
neighboring cell is experiencing high RTWP also
 -

5 If you have High Call drop In certain cell.

what is the proper procedure of trouble
shooting that you need to take on this
problem.
- Check the coverage if ok
- Check the status of the site if there is any alarm
- Check the status of the transmission quality
- Check is there missing neighbor
- From the counter we can easily determine the reason of call drop
See the sample counter below

VS.RAB.AbnormRel.CS.RF.SRBReset
VS.RAB.AbnormRel.CS.RF.ULSync
VS.RAB.AbnormRel.CS.RF.UuNoReply
RAB released by the RNC because of the downlink SRB reset due to poor
coverage/quality.
RAB released by the RNC because of Uplink Synchronization Failure
RABs released by the RNC because of the Failure in the Radio Interface
Procedure e.g SHO procedure. The failure is usually caused by the imbalance
between the uplink coverage and downlink coverage and fast signal change.

VS.RAB.AbnormRel.CS.OM
VS.RAB.AbnormRel.CS.UTRANgen
VS.RAB.AbnormRel.CS.Preempt
VS.RAB.AbnormRel.CS.IuAAL2
VS.RAB.AbnormRel.PS.RF.SRBReset
VS.RAB.AbnormRel.PS.RF.TRBReset
VS.RAB.AbnormRel.PS.RF.ULSync
VS.RAB.AbnormRel.PS.RF.UuNoReply
VS.RAB.AbnormRel.PS.OM
VS.RAB.AbnormRel.PS.Preempt
VS.RAB.AbnormRel.PS.GTPULoss
RABs released caused by the operation and maintenance work (for example,
the cell is blocked).
RABs released caused by the UTRAN Generated Reason
RABs released caused by the high-priority preemption. Such call drop occurs
when the load and resources are not enough.
The RNC initiates abnormal release after finding that the AAL2 Path on
the IU CS interface is abnormal
RAB released by the RNC because of the downlink SRB reset due to poor
coverage/quality.
RAB released by the RNC because of the downlink TRB reset due to poor
coverage/quality.
RAB released by the RNC because of Uplink Synchronization Failure
RABs released by the RNC because of the Failure in the Radio Interface
Procedure e.g SHO procedure.The failure is usually caused by the imbalance
between the uplink coverage and downlink coverage and fast signal change
RABs released caused by the operation and maintenance work (for example,
the cell is blocked).
RABs released caused by the high-priority preemption. Such call drop occurs
when the load and resources are not enough.
The RNC initiates abnormal release after finding that the GTPU on
the IU PS interface is abnormal
6- what is DRD

7- What is LDR

8- what are the different type of RRC

Establishment cause
RRC Establishment Cause Description
Cause 0 Originating Conversational Call
Cause 1 Originating Streaming Call
Cause 2 Originating Interactive Call
Cause 3 Originating Background Call
Cause 4 Originating Subscribed traffic Call
Cause 5 Terminating Conversational Call
Cause 6 Terminating Streaming Call
Cause 7 Terminating Interactive Call
Cause 8 Terminating Background Call
Cause 9 Emergency Call
Cause 10 Inter-RAT Cell re-selection
Cause 11 Inter-RAT Cell change order
Cause 12 Registration
Cause 13 Detach
Cause 14 Originating High Priority Signaling
Cause 15 Originating Low Priority Signaling
Cause 16 Call re-establishment
Cause 17 Terminating High Priority Signaling
Cause 18 Terminating Low Priority Signaling
Cause 19 Terminating cause unknown