HUAWEI 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 to 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 statistics some time we can see the value of this
counter is also high

VS.RRC.Rej.RL.Fail,
- If this counter is Having High value. Check first the utilization of the CPU. Maybe the cpu resoure
is already congested. This can be also one of the reson of this failure. To solve this problem we
can add the WBBP board to increase the capacity of CPU.

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 Power congestion

UL POWER
- 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

DL POWER
1).Command: MOD UCELLCAC:
Parameters optimization:
DlConvAMRThd=90(default 80), - Exceeding DL Load value to 90% will reject amr user
DlConvNonAMRThd=90(default 80), Exceeding DL Load value to 90% will reject non amr user
DlOtherThd=85(default 75), Exceeding DL Load value to 90% will reject other services user
DlHOThd=92(default 85), Exceeding DL Load value to 90% will reject the access cause by Hand over
DlCellTotalThd=95(default 90); Exceeding DL Load value to 90% will reject all user

2). Pmax: Check hardware and license capacity whether can increase power.
 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 due to hardware
problem. Some time it is related to TMA connected to the antenna system

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

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

- Check the Setting of Current HSUPA number allowed to access. If this parameter is
set to high. Noise rise can be increase.
-

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.

RABs released caused by the operation and maintenance work (for example,
VS.RAB.AbnormRel.CS.OM
the cell is blocked).
VS.RAB.AbnormRel.CS.UTRANgen RABs released caused by the UTRAN Generated Reason

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 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
Service Priority Group(ADD USPG)
Through the SPG, different services are set to different priorities so that the service layers are
differentiated. The Service priority group Identity is specified when a new cell is set up
through the ADD UCELLSETUP command.

SRNC CELLID CELLNAME SPGID

151 33111 BKC0097U_8NB01_S01 2
151 33121 BKC0097U_8NB01_S02 2
151 33131 BKC0097U_8NB01_S03 2
151 45137 BKC0097V_8NB01_S01 1
151 45138 BKC0097V_8NB01_S02 1
151 45141 BKC0097V_8NB01_S03 1

In the above configuration of SPG ID. V cell is set to 1 While U Cells are set to 2 Two
service priority group was assigned to in each Band.

SR SP PRIORITYSERVIC PRIORITYSERVICE PRIORITYSERVICE PRIORITYSERVICE PRIORITYSERVICE

NC GID EFORR99RT FORR99NRT FOREXTRAB FORHSDPA FORHSUPA

151 1 1 1 1 1 1
151 2 1 1 1 2 2

Base on the above configuration The cells Configured to SPG ID 1 have the higest priority for
the for all the service while cells in SPG ID 2 have also the highest prirority for R99 RT and
NRT, But for HSPA service have the second priority only.

The value range of the priority setting is 1 to 7. Value 1 indicates the highest priority, whereas
value 7 indicates the lowest priority.

SET UDRD: ServiceDiffDrdSwitch=ON, LdbDRDSwitchHSDPA=ON,

LdbDRDchoice=UserNumber, ConnectFailRrcRedirSwitch=OFF, LdbDRDOffsetDCH=35,
LdbDRDOffsetHSDPA=10, LdbDRDLoadRemainThdDCH=100,
LdbDRDLoadRemainThdHSDPA=100;
SET UDRD:DRMAXGSMNUM=5, SERVICEDIFFDRDSWITCH=OFF,
CONNECTFAILRRCREDIRSWITCH=OFF, CODEBALANCINGDRDSWITCH=OFF,
DELTACODEOCCUPIEDRATE=7, CODEBALANCINGDRDMINSFTHD=SF8,
CODEBALANCINGDRDCODERATETHD=13, REDIRBANDIND=DependOnNCell,
LDBDRDSWITCHDCH=OFF, LDBDRDSWITCHHSDPA=OFF,
LDBDRDCHOICE=UserNumber, LDBDRDOFFSETDCH=10, LDBDRDOFFSETHSDPA=3,
LDBDRDLOADREMAINTHDDCH=35, LDBDRDLOADREMAINTHDHSDPA=100,
LDBDRDTOTALPWRPROTHD=30, ULLDBDRDSWITCHDCHSDPA=OFF,
ULLDBDRDOFFSETDCHSDPA=10, ULLDBDRDLOADREMAINTHDDCHSDPA=25,
BASEDONMEASHRETRYDRDSWITCH=OFF, DPGDRDSWITCH=OFF;

DRMAXGSMNUM=5 Maximum number of inter-RAT RAB directed retries. It decides the

size of the candidate set for inter-RAT DRD. The value 0 indicates that inter-RAT RAB DRD is
not applicable. This parameter can be cell-oriented.
7- What is LDR
 Parameter Parameter Parameter Description
ID Name

CellId Cell ID Meaning: ID of a cell. For detailed information about this parameter, see 3GPP TS 25.401.

GUI Value Range: 0~65535

Actual Value Range: 0~65535

Unit: None

Default Value: None

Recommended Value: None

Parameter Relationship: None

Service Interrupted After Modification : No (No impact on the UE in idle mode)

Impact on Network Performance: None

UlLdrTrigThd UL LDR Meaning: If the ratio of UL load of the cell to the uplink capacity is not lower than this threshold, the UL load
trigger reshuffling function of the cell is triggered. After the basic congestion state of the cell load is released, the
threshold system no longer implements the LDR action. Because the load fluctuates, the difference between the LDR
release threshold and trigger threshold should be higher than 10%. The ping-pong effect of the preliminary
congestion state may occur.

GUI Value Range: 0~100

Actual Value Range: 0~1, step:0.01

Unit: %

Default Value: 55

Recommended Value: 55

Parameter Relationship: The value of this parameter must satisfy the following relationship: UlLdrTrigThd >=
UlLdrRelThd; UlOlcTrigThd > UlLdrTrigThd; UlNonCtrlThdForOther(See ADD UCELLCAC) >=
UlLdrTrigThd.

Service Interrupted After Modification : No (No impact on the UE in idle mode)

Impact on Network Performance: The lower the LDR trigger and release thresholds are, the easier the system
enters the preliminary congestion status, the harder it is released from this status, the easier the LDR action is
triggered, and the more likely the users are affected. But, the admission success rate becomes higher since the
resources are preserved. The carrier shall make a trade-off between these factors.
 Parameter Parameter Parameter Description
ID Name

UlLdrRelThd UL LDR Meaning: If the ratio of UL load of the cell to the uplink capacity is lower than this threshold, the UL load
release reshuffling function of the cell is stopped. After the basic congestion state of the cell load is released, the system
threshold no longer implements the LDR action. Because the load fluctuates, the difference between the LDR release
threshold and trigger threshold should be higher than 10%. The ping-pong effect of the preliminary congestion
state may occur.

GUI Value Range: 0~100

Actual Value Range: 0~1, step:0.01

Unit: %

Default Value: 45

Recommended Value: 45

Parameter Relationship: The value of this parameter must satisfy the following relationship: UlLdrTrigThd >=
UlLdrRelThd; UlOlcRelThd >= UlLdrRelThd.

Service Interrupted After Modification : No (No impact on the UE in idle mode)

Impact on Network Performance: The lower the LDR trigger and release thresholds are, the easier the system
enters the preliminary congestion status, the harder it is released from this status, the easier the LDR action is
triggered, and the more likely the users are affected. But, the admission success rate becomes higher since the
resources are preserved. The carrier shall make a trade-off between these factors.

DlLdrTrigThd DL LDR Meaning: If the ratio of DL load of the cell to the downlink capacity is not lower than this threshold, the DL
trigger load reshuffling function of the cell is triggered. After the basic congestion state of the cell load is released, the
threshold system no longer implements the LDR action. Because the load fluctuates, the difference between the LDR
release threshold and trigger threshold should be higher than 10%. The ping-pong effect of the preliminary
congestion state may occur.

GUI Value Range: 0~100

Actual Value Range: 0~1, step:0.01

Unit: %

Default Value: 70

Recommended Value: 70

Parameter Relationship: The value of this parameter must satisfy the following relationship: DlLdrTrigThd >=
DlLdrRelThd; DlOlcTrigThd > DlLdrTrigThd; DlOtherThd(See ADD UCELLCAC) >= DlLdrTrigThd.

Service Interrupted After Modification : No (No impact on the UE in idle mode)

Impact on Network Performance: The lower the LDR trigger and release thresholds are, the easier the system
enters the preliminary congestion status, the harder it is released from this status, the easier the LDR action is
triggered, and the more likely the users are affected. But, the admission success rate becomes higher since the
resources are preserved. The carrier shall make a trade-off between these factors.
 Parameter Parameter Parameter Description
ID Name

DlLdrRelThd DL LDR Meaning: If the ratio of DL load of the cell to the downlink capacity is lower than this threshold, the DL load
release reshuffling function of the cell is stopped. After the basic congestion state of the cell load is released, the system
threshold no longer implements the LDR action. Because the load fluctuates, the difference between the LDR release
threshold and trigger threshold should be higher than 10%. The ping-pong effect of the preliminary congestion
state may occur.

GUI Value Range: 0~100

Actual Value Range: 0~1, step:0.01

Unit: %

Default Value: 60

Recommended Value: 60

Parameter Relationship: The value of this parameter must satisfy the following relationship: DlLdrTrigThd >=
DlLdrRelThd; DlOlcRelThd >= DlLdrRelThd.

Service Interrupted After Modification : No (No impact on the UE in idle mode)

Impact on Network Performance: The lower the LDR trigger and release thresholds are, the easier the system
enters the preliminary congestion status, the harder it is released from this status, the easier the LDR action is
triggered, and the more likely the users are affected. But, the admission success rate becomes higher since the
resources are preserved. The carrier shall make a trade-off between these factors.

Naka set ng dedault

ADD UCELLLDM:CELLID=52121, ULLDRTRIGTHD=55, ULLDRRELTHD=45,

DLLDRTRIGTHD=70, DLLDRRELTHD=60, ULOLCTRIGTHD=95, ULOLCRELTHD=85,
DLOLCTRIGTHD=95, DLOLCRELTHD=85, DLLDTRNSHYSTIME=1000,
HSUPAURETRNSLDTRIGTHD=70, HSUPAURETRNSLDRELTHD=50,
TRIGRATIOFORULRTWP=73, RELRATIOFORULRTWP=60, FAIRNESSTHD=150;

Naka set ng dedault

SET UHOCOMM:DIVCTRLFIELD=MAY, HSPATIMERLEN=0,
COEXISTMEASTHDCHOICE=COEXIST_MEAS_THD_CHOICE_INTERRAT,
MAXEDCHCELLINACTIVESET=3, IFANTIPINGPANGTIMERLENGTH=30;

Naka set ng dedault

ADD UCELLALGOSWITCH:CELLID=52121, NBMCACALGOSWITCH=CRD_ADCTRL-

1&HSDPA_UU_ADCTRL-0&HSUPA_UU_ADCTRL-0&MBMS_UU_ADCTRL-
0&HSDPA_GBP_MEAS-0&HSDPA_PBR_MEAS-0&HSUPA_PBR_MEAS-
0&HSUPA_EDCH_RSEPS_MEAS-0&EMC_UU_ADCTRL-1&RTWP_RESIST_DISTURB-
0&FACH_UU_ADCTRL-0&MIMOCELL_LEGACYHSDPA_ADCTRL-
0&FAST_DORMANCY_ADCTRL-0,
NBMULCACALGOSELSWITCH=ALGORITHM_SECOND,
NBMDLCACALGOSELSWITCH=ALGORITHM_FIRST,
NBMLDCALGOSWITCH=INTRA_FREQUENCY_LDB-0&PUC-0&UL_UU_LDR-
1&DL_UU_LDR-1&UL_UU_OLC-0&DL_UU_OLC-0&OLC_EVENTMEAS-
0&CELL_CODE_LDR-1&CELL_CREDIT_LDR-1&UL_INTRA_FREQUENCY_ULB-0,
NBMMACHSRESETALGOSELSWITCH=ALGORITHM_DEPEND_ON_LCG,
HSPAPLUSSWITCH=64QAM-1&MIMO-0&E_FACH-0&DTX_DRX-
0&HS_SCCH_LESS_OPERATION-0&DL_L2ENHANCED-1&64QAM_MIMO-0&UL_16QAM-
0&DC_HSDPA-0&UL_L2ENHANCED-0&EDPCCH_BOOSTING-0&DCMIMO_HSDPA-
0&E_DRX-0, HSPAENHSWITCH=E_F_DPCH_OFF,
CELLCAPACITYAUTOHANDLESWITCH=TX_DIVERSITY_ON_TO_OFF-
0&TX_DIVERSITY_OFF_TO_ON-0,
NBMLDCUESELSWITCH=NBM_LDC_MATCH_UE_ONLY, OFFLOADSWITCH=OFF,
RSVDPARA1=RSVDBIT1-0&RSVDBIT2-0&RSVDBIT3-0&RSVDBIT4-0&RSVDBIT5-
0&RSVDBIT6-0&RSVDBIT7-0&RSVDBIT8-0&RSVDBIT9-0&RSVDBIT10-0&RSVDBIT11-
0&RSVDBIT12-0&RSVDBIT13-0&RSVDBIT14-0&RSVDBIT15-0&RSVDBIT16-0,
RSVDPARA2=0, RSVDPARA3=0, BERATEREDUCEONFAIRNESSSWITCH=OFF;

LDR ACTION

ADD UCELLLDR:CELLID=52121, DLLDRFIRSTACTION=CodeAdj,

DLLDRSECONDACTION=BERateRed, DLLDRTHIRDACTION=NoAct,
DLLDRFOURTHACTION=NoAct, DLLDRFIFTHACTION=NoAct,
DLLDRSIXTHACTION=NoAct, DLLDRSEVENTHACTION=NoAct,
DLLDREIGHTHACTION=NoAct, DLLDRNINTHACTION=NoAct,
DLLDRTENTHACTION=NoAct, DLLDRBERATEREDUCTIONRABNUM=1,
DLLDRPSRTQOSRENEGRABNUM=1, DLCSINTERRATSHOULDBEHOUENUM=3,
DLPSINTERRATSHOULDBEHOUENUM=1, DLLDRAMRRATEREDUCTIONRABNUM=1,
DLCSINTERRATSHOULDNOTHOUENUM=3, DLPSINTERRATSHOULDNOTHOUENUM=1,
ULLDRFIRSTACTION=BERateRed, ULLDRSECONDACTION=NoAct,
ULLDRTHIRDACTION=NoAct, ULLDRFOURTHACTION=NoAct,
ULLDRFIFTHACTION=NoAct, ULLDRSIXTHACTION=NoAct,
ULLDRSEVENTHACTION=NoAct, ULLDREIGHTHACTION=NoAct,
ULLDRBERATEREDUCTIONRABNUM=1, ULLDRPSRTQOSRENEGRABNUM=1,
ULCSINTERRATSHOULDBEHOUENUM=3, ULPSINTERRATSHOULDBEHOUENUM=1,
ULLDRAMRRATEREDUCTIONRABNUM=1, ULCSINTERRATSHOULDNOTHOUENUM=3,
ULPSINTERRATSHOULDNOTHOUENUM=1,
ULINTERFREQHOCELLLOADSPACETHD=20,
DLINTERFREQHOCELLLOADSPACETHD=20, ULINTERFREQHOBWTHD=200000,
DLINTERFREQHOBWTHD=200000, MBMSDECPOWERRABTHD=1,
CELLLDRSFRESTHD=SF8, LDRCODEPRIUSEIND=FALSE, MAXUSERNUMCODEADJ=1,
ULLDRCREDITSFRESTHD=SF8, DLLDRCREDITSFRESTHD=SF8,
LDRCODEUSEDSPACETHD=13, CODECONGSELINTERFREQHOIND=FALSE,
GOLDUSERLOADCONTROLSWITCH=OFF,
INTERFREQLDHOFORBIDENTC=R99_CONVERSATIONAL-0&R99_STREAMING-
0&R99_BE-0&HSDPA_CONVERSATIONAL-0&HSDPA_STREAMING-0&HSDPA_BE-
0&HSPA_CONVERSATIONAL-0&HSPA_STREAMING-0&HSPA_BE-0,
ULTTICREDITSFRESTHD=SF8, INTERFREQLDHOMETHODSELECTION=BLINDHO;

44
Sample scrip for load balancing.
SCENARIO: Need to pass the traffic from F2 TO F1
ORIGINAL MML
F1-F2
ADD UINTERFREQNCELL:RNCID=3, CELLID=38566, NCELLRNCID=3, NCELLID=38560, IDLEQOFFSET1SN=0,
IDLEQOFFSET2SN=0, BLINDHOFLAG=TRUE, NPRIOFLAG=FALSE, BLINDHOQUALITYCONDITION=-92, CIOOFFSET=0,
SIB11IND=TRUE, SIB12IND=FALSE, TPENALTYHCSRESELECT=D0, HOCOVPRIO=0, DRDECN0THRESHHOLD=-18,
MBDRFLAG=FALSE, MBDRPRIO=0, DRDORLDRFLAG=FALSE, INTERNCELLQUALREQFLAG=FALSE;
F2-F1
ADD UINTERFREQNCELL:RNCID=3, CELLID=38560, NCELLRNCID=3, NCELLID=38566, IDLEQOFFSET1SN=0,
IDLEQOFFSET2SN=0, BLINDHOFLAG=TRUE, NPRIOFLAG=FALSE, BLINDHOQUALITYCONDITION=-92, CIOOFFSET=0,
SIB11IND=TRUE, SIB12IND=FALSE, TPENALTYHCSRESELECT=D0, HOCOVPRIO=0, DRDECN0THRESHHOLD=-18,
MBDRFLAG=FALSE, MBDRPRIO=0, DRDORLDRFLAG=FALSE, INTERNCELLQUALREQFLAG=FALSE;
F1-F2- this configuration will delay the interfreqho to F2 celll. pababagalin ang pang punta sa F2.
ADD UINTERFREQNCELL:RNCID=3, CELLID=38566, NCELLRNCID=3, NCELLID=38560, IDLEQOFFSET1SN=0,
IDLEQOFFSET2SN=50, BLINDHOFLAG=TRUE, NPRIOFLAG=FALSE, BLINDHOQUALITYCONDITION=-92, CIOOFFSET=0,
SIB11IND=TRUE, SIB12IND=FALSE, TPENALTYHCSRESELECT=D0, HOCOVPRIO=0, DRDECN0THRESHHOLD=-18,
MBDRFLAG=FALSE, MBDRPRIO=0, DRDORLDRFLAG=FALSE, INTERNCELLQUALREQFLAG=FALSE;
F2-F1 this configuration will fasten the interfreqho to F1 celll. papabilisin ang pang reselect sa F1
ADD UINTERFREQNCELL:RNCID=3, CELLID=38560, NCELLRNCID=3, NCELLID=38566, IDLEQOFFSET1SN=0,
IDLEQOFFSET2SN=-50, BLINDHOFLAG=TRUE, NPRIOFLAG=FALSE, BLINDHOQUALITYCONDITION=-92, CIOOFFSET=0,
SIB11IND=TRUE, SIB12IND=FALSE, TPENALTYHCSRESELECT=D0, HOCOVPRIO=0, DRDECN0THRESHHOLD=-18,
MBDRFLAG=FALSE, MBDRPRIO=0, DRDORLDRFLAG=FALSE, INTERNCELLQUALREQFLAG=FALSE;
Using the above script. We can ensure that F2 will be less load compare to F1, When
implementing this parameter. We need to monitor the congestion and traffic performance on the
F1 cell.
Expected result: Traffic of f2 will be reduce and F1 traffic will increase
IDLEQOFFSET2SN
Meaning: Cell offset used for CPICH Ec/No measurement value in cell selection or reselection when the UE is in idle mode.
Offset of neighboring cell CPICH measurement value. This parameter is used for Ec/No measurement. The offset is subtracted from
the neighboring cell measurement value before cell reselection.In handover algorithms, this parameter is used for moving the border
of a cell. This parameter can be configured by the Radio Network Planner (RNP) based on the actual network.
Note that in FDD mode, this parameter is valid only when SIB11 Indicator is set as TRUE.
For details, see 3GPP TS 25.331.
GUI Value Range: -50~50
Unit: dB
Actual Value Range: -50~50
MML Default Value: None
Recommended Value: 0
Parameter Relationship: This parameter is valid when SIB11Ind is set to TRUE.
Service Interrupted After Modification : No (Impact on the UE in idle mode)
Impact on Network Performance: If this parameter is set to a greater value, the probability for selecting the neighboring cell as the
target cell reduces. If this parameter is set to a smaller value, the probability for selecting the neighboring cell as the target cell
increases.
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
WCDMA RAN
Fast Dormancy
Feature Parameter Description

2 Overview
When fast dormancy or enhanced fast dormancy is applied, the UE can request the RNC to
release the PS signaling connection if no more PS data is transmitted. After receiving the request,
the RNC can either release the signaling connection and put the UE into idle mode, or maintain
the signaling connection and put the UE into an efficient battery consumption RRC state such as
IDLE, CELL_PCH.

3 Fast Dormancy
UEs complying with 3GPP Release 8 support the fast dormancy function, as defined in 3GPP TS
25.331 CR3483. After a UE processing only PS services finishes the PS data transmission, it
sends the RNC a Signaling Connection Release Indication (SCRI) message, which contains the
cause value of "UE Requested PS Data session end". Upon receiving the message, the RNC
releases the RRC connection of the UE and enables the UE to quickly enter the power saving
mode.
The following figure shows the procedure of fast dormancy.
Figure 3-1 Fast dormancy

The RNC sends timer T323 in SIB1 or UTRAN Mobility Information to the UE to control fast
dormancy.
If
the value of T323 is INVALID, the timer is not sent to the UE, and accordingly the UE does
not send the SCRI message containing the information element (IE) "UE Requested PS Data
session end".
If the value of T323 is 0, the UE sends the release request only once.
If the value of T323 is a value other than 0, the UE sends the release request and initiates timer
T323. The UE sends the release request again after T323 expires.
4 Enhanced Fast Dormancy
4.1 Overview
As the number of intelligent UEs keeps increasing in mobile networks, the networks face
signaling storms produced by these UEs. With many customers all over the world, Huawei has
rich experience in network optimization. Huawei can provide a comprehensive end-to-end
solution to respond to network challenges based on network characteristics. This feature is a
component of the comprehensive solution. Deploying this feature only cannot solve the signaling
storm problem caused by intelligent UEs. It is recommended that this feature together with
professional services be deployed to optimize the quality of service of the entire network.
Note:
Consult Huawei engineers about the comprehensive solution to obtain professional technical support. Huawei
engineers will recommend the appropriate parameter settings for this feature based on the network conditions.
Do not configure the parameters related to this feature without Huawei professional technical support. Inappropriate
parameter settings may lead to network failures.
Enhanced fast dormancy applies to a network that serves a large number of intelligent UEs
supporting fast dormancy. This function can reduce the signaling processing efforts of the RNC
and avoid overflow of the signaling processing unit in the RNC that fast dormancy may cause.
To save power, when there is no PS data transmission, an intelligent UE sends the RNC an SCRI
message to request the RRC connection release or to indicate to the UTRAN that one of its
signaling connections has been released. In addition, the UE periodically sends the heartbeat
messages (to check new mails in the mail server for example) to the core network.
If fast dormancy (instead of enhanced fast dormancy) is applied, the RNC releases the RRC
connection as specified by the 3GPP specifications. In such a case, the heartbeat messages will
lead to performing the procedures of RRC connection setup, authentication, encryption, and
RAB setup. This greatly increases the signaling processing efforts of the RNC and may cause
overflow of the signaling processing unit in the RNC.
Enhanced fast dormancy is introduced to solve the preceding problem. With the application of
enhanced fast dormancy, the RNC changes the UE state to CELL_PCH instead of idle mode
after receiving the SCRI message from the UE. In such a case, when the UE periodically sends
the heartbeat messages, the signaling procedure between the UE and RNC is simplified because
the RRC connection is maintained. As the number of signaling exchange messages decreases, the
CPU resources of the RNC can be saved significantly, and the UE consumes as less battery
energy as a UE in idle mode.
The following figure shows the comparison between fast dormancy and enhanced fast dormancy.
Figure 4-1 Comparison between fast dormancy and enhanced fast dormancy

4.2 Identifying Fast Dormancy UEs

Two types of the fast dormancy mechanism are implemented in UEs. These UEs are referred to
as fast dormancy UEs in this document.
R8 fast dormancy: This mechanism is standardized by 3GPP Release 8. As specified, the UE
sends a SIGNALLING CONNECTION RELEASE INDICATION (SCRI) message to the
network with the IE "Signaling Connection Release Indication Cause" set to "UE Requested
PS Data session end."
The RNC can identify this type of UE by the SCRI message with IE "UE Requested PS Data
session end."
Pre-R8 fast dormancy: This mechanism, which is not standardized, is used for the early
proprietary implementations of fast dormancy prior to Release 8.
The RNC can identify this type of UE by its IMEI and its release version.
After the RNC receives the Security Mode Command Complete message from the UE, the RNC
identifies fast dormancy UEs as follows:
If the FD_TAC_MATCH_SWITCH of the parameter PROCESSSWITCH is turned on, the
following UEs are identified as fast dormancy UE.
UE (Pre-R8 fast dormancy) that complies with 3GPP Release 5 or later releases and whose IMEI
falls into the white list. The IMEI range for white list is specified by the binary group (TAC,
FastDormancy = ON) in the RNC MML command ADD UIMEITAC. If the FastDormancy switch
is on, the RNC considers the UEs specified by the IMEI (TAC) as capable of enhanced fast
dormancy.
UE (R8 fast dormancy) from which the SCRI message whose cause value is "UE Requested PS
Data session end." is sent.
 If the FD_TAC_MATCH_SWITCH of the parameter PROCESSSWITCH is turned off, the
following UEs are identified as fast dormancy UE.
UEs complying with 3GPP Release 5 or later releases are identified as fast dormancy UE
excluding the UEs in the black list..The IMEI range for the black list is specified by the binary
group (TAC, FastDormancy = OFF) in the RNC MML command ADD UIMEITAC. If the
FastDormancy switch is OFF, the RNC considers the UEs specified by the IMEI (TAC) as
incapable of enhanced fast dormancy.
The RNC can obtain the IMEI of the UE from the UE's response to the "IDENTITY REQUEST"
message. The range of the IMEI is specified by the parameter TAC in the RNC MML command
ADD UIMEITAC.
The IMEI (consisting of 14 decimal digits and one check digit) contains information on the
origin, model, and serial number of the UE. The structure of the IMEI is specified in 3GPP TS
23.003.
TAC (8bit) FAC (2bit) SNR (6bit) Spare (1bit)
The Type Allocation Code (TAC) indicates the particular type of device that has been
approved by a national GSM/WCDMA approval body. In the 3GPP specifications released
later than 2003, the TAC length is changed from 6 bit to 8 bit.
The Final Assembly Code (FAC), which is manufacturer-specific, indicates the location where
the UE is manufactured.
SNR is the serial number identifying the UE.
The RNC can determine whether a UE supports fast dormancy according to the information on
the manufacturer and model contained in the TAC.

4.3 State Transition of Fast Dormancy UEs

If enhanced fast dormancy is disabled, the RRC connection of the UE is released after the RNC
received the SCRI. The switches of enhanced fast dormancy are specified by the RNC level
subparameter FAST_DORMANCY_SWITCH of the parameter PROCESSSWITCH and cell
level subparameter FAST_DORMANCY_ADCTRL of the parameter NBMCacAlgoSwitch.
If enhanced fast dormancy is enabled, then
Ifthe UE is identified as R8 UE (the UE can report the SCRI with R8 extensional cause of
"data session end"),
If the RNC received the SCRI with the cause of "data session end", the RNC transfers the UE to
CELL_FACH or CELL_PCH.
Ifthe UE in not R8 UE and the UE is identified as fast dormancy UE,
If the RNC received the SCRI or the inactive timer for enhanced fast dormancy times out, the
RNC transfers the UE to CELL_FACH or CELL_PCH.
The following figure shows the detailed state transition of a fast dormancy UE.
Figure 4-2 State transition of a fast dormancy UE

Table 4-1 State Transition of Fast Dormancy UEs

Type Description
D2P D2P is from CELL_DCH to CELL_PCH. F2P is from CELL_FACH to CELL_PCH. D2F
D2F is from CELL_DCH to CELL_FACH.
F2P The RNC starts the PS inactivity timer for fast dormancy after the fast dormancy UE
changes the state.
PsInactTmrForFstDrmDch specifies the PS inactivity timer for CELL_DCH
PsInactTmrForFstDrmFach specifies the PS inactivity timer for CELL_FACH
PsInactTmrForPreFstDrm specifies the PS inactivity timer for CELL_PCH

If the UE is a fast dormancy UE and is not processing CS services, when the PS

inactivation timer for fast dormancy expires or the RNC receives the SCRI message or 4B
event from the UE, the state transition of the UE is performed as follows:
Ifthe UE is in the CELL_DCH state,
If the switch RsvdPara1 > RSVDBIT1_BIT29 (SET URRCTRLSWITCH) is turned off, RNC
will trigger the D2F state transition.
If the switch RsvdPara1 > RSVDBIT1_BIT29 (SET URRCTRLSWITCH) is turned on, RNC
will trigger the D2P state transition.
Ifthe UE is in the CELL_FACH state,
The RNC will trigger F2P state transition.
D2I D2I is from CELL_DCH to IDLE.
When the FACH is congested, D2F wont be triggered for inactive CELL_DCH users.
Instead, RNC will trigger D2I to release this UE.
The default D2I function switch is off. You can switch on the function through the following
command:
SET UCORRMALGOSWITCH: ReservedSwitch0=RESERVED_SWITCH_0_BIT16-1;
P2I P2I is from CELL_PCH to IDLE.
If the UE is in the CELL_PCH state, when the PS inactivation timer for fast dormancy
PsInactTmrForPreFstDrm expires, the RNC releases the RRC connection and then the
UE enters the IDLE state.
P2D P2D is from CELL_PCH to CELL_DCH.
If the switch RsvdPara1 > RSVDBIT1_BIT20 (SET URRCTRLSWITCH) is turned on:
When the UE tries to set up an originated or a terminated CS service and the FACH is
congested, the RNC instructs the UE to perform P2D state transition instead of P2F2D.
SET URRCTRLSWITCH: RsvdPara1=RSVDBIT1_BIT20-0;
Note: for the switch, the value 0 means on and 1 means off.
Ifthe switch PROCESSSWITCH > FD_P2D_SWITCH (ADD UIMEITAC) is turned on:
If the TAC of the UE is the same as that configured on the RNC and if the UE is in the
CELL_PCH and the UE is going to transmit uplink data or respond to paging message, the
RNC instructs the UE to perform P2D directly.

P2F P2F is from CELL_PCH to CELL_FACH.

When the UE transmits the heartbeat messages or traffic data, the RNC instructs the UE
to enter the CELL_FACH state.
F2D F2D is From CELL_FACH to CELL_DCH.
When the fast dormancy UE is in the CELL_FACH state, the state transition of the UE is
performed as follows:
If
the UE reports event 4A to the RNC, the RNC instructs the UE to enter the
CELL_DCH state.
If
the UE reports event 4B to the RNC, the RNC instructs the UE to enter the
CELL_PCH state.
When the fast dormancy UE periodically sends small heartbeat messages, the normal
state transition mechanism will change the UE status from the CELL_FACH state to
CELL_DCH state. To prevent the state transition triggered by small heartbeat messages,
a new threshold for Event 4A (FastDormancyF2DHTvmThd) is introduced.
To avoid too many UEs remaining in the CELL_FACH state, fast dormancy ensures that
the state transition switch does not affect the 4A and 4B measurement and state transition
from CELL_FACH to other state for fast dormancy UEs in CELL_FACH.
Parameter ID NE MML Command Description
FastDormancy BSC69 ADD UIMEITAC(Optional) Meaning:The switch of Fast Dormancy
00 MOD UIMEITAC(Optional) function for one type UE
GUI Value Range:OFF, ON
Actual Value Range:ON, OFF
Default Value:OFF
FastDormancyF2DH BSC69 SET Meaning:This parameter specifies the
TvmThd 00 UUESTATETRANS(Optio threshold of the traffic volume of 4A
nal) event for triggering the transition of fast
dormancy user from FACH/E_FACH to
DCH/HSPA
GUI Value Range:D16, D32, D64,
D128, D256, D512, D1024, D2k, D3k,
D4k, D6k, D8k, D12k, D16k, D24k,
D32k, D48k, D64k, D96k, D128k,
D192k, D256k, D384k, D512k, D768k
Actual Value Range:16, 32, 64, 128,
256, 512, 1024, 2k, 3k, 4k, 6k, 8k, 12k,
16k, 24k, 32k, 48k, 64k, 96k, 128k,
192k, 256k, 384k, 512k, 768k
Default Value:D3k
NBMCacAlgoSwitch BSC69 ADD Meaning:The above values of the
00 UCELLALGOSWITCH(Op algorithms represent the following
tional) information:
MOD CRD_ADCTRL: Control Cell Credit
UCELLALGOSWITCH(Op admission control algorithm.
tional) Only when
NODEB_CREDIT_CAC_SWITCH
which is set by the SET
UCACALGOSWITCH command and
this switch are on,the Cell Credit
admission control algorithm is valid.
HSDPA_UU_ADCTRL: Control HSDPA
UU Load admission control algorithm.
This swtich does not work when uplink
is beared on HSUPA and downlink is
beared on HSDPA.
HSDPA_GBP_MEAS: Control HSDPA
HS-DSCH Required Power
measurement.
HSDPA_PBR_MEAS: Control HSDPA
HS-DSCH Provided Bit Rate
measurement.
HSUPA_UU_ADCTRL: Control HSUPA
UU Load admission control algorithm.
This switch does not work when uplink
is beared on HSUPA and downlink is
beared on HSDPA.
MBMS_UU_ADCTRL: Control MBMS
UU Load admission control algorithm.
HSUPA_PBR_MEAS: Control HSUPA
Provided Bit Rate measurement.
HSUPA_EDCH_RSEPS_MEAS:
Control HSUPA Provided Received
Scheduled EDCH Power Share
measurement.
EMC_UU_ADCTRL: Control power
admission for emergency user.
RTWP_RESIST_DISTURB: Control
algorithm of resisting disturb when
RTWP is abnormal.
FACH_UU_ADCTRL: Admission
control switch for the FACH on the Uu
interface. This switch determines
whether to admit a user in the RRC
state on the CELL_FACH.
1. If this switch is enabled: if the
current cell is congested due to
overload, and the users are with RAB
connection requests or RRC
connection requests(except the cause
of ""Detach"", ""Registration"", or
""Emergency Call""), the users will be
rejected. Otherwise FACH user
admission procedure is initiated. A user
can access the cell after the procedure
succeeds.
2. If this switch is disabled: FACH
user admission procedure is initiated
without the consideration of cell state.
MIMOCELL_LEGACYHSDPA_ADCTR
L: Legacy HSDPA admission control
algorithm in MIMO cell.
FAST_DORMANCY_ADCTRL: Control
admission for Fast Dormancy user. If
this switch is disabled, state transition
from CELL-DCH to CELL-PCH or from
CELL-DCH to CELL-FACH is not
allowed for Fast Dormancy user.

If switches above are selected, the

 corresponding algorithms will be
enabled; otherwise, disabled
GUI Value
Range:CRD_ADCTRL(Credit
Admission Control Algorithm),
HSDPA_UU_ADCTRL(HSDPA UU
Load Admission Control Algorithm),
HSUPA_UU_ADCTRL(HSUPA UU
Load Admission Control Algorithm),
MBMS_UU_ADCTRL(MBMS UU Load
Admission Control Algorithm),
HSDPA_GBP_MEAS(HSDPA GBP
Meas Algorithm),
HSDPA_PBR_MEAS(HSDPA PBR
Meas Algorithm),
HSUPA_PBR_MEAS(HSUPA PBR
Meas Algorithm),
HSUPA_EDCH_RSEPS_MEAS(HSUP
A EDCH RSEPS Meas Algorithm),
EMC_UU_ADCTRL(emergency call
power admission),
RTWP_RESIST_DISTURB(RTWP
Resist Disturb Switch),
FACH_UU_ADCTRL(FACH power cac
switch),
MIMOCELL_LEGACYHSDPA_ADCTR
L(Legacy HSDPA Admission Control
Algorithm in MIMO Cell ),
FAST_DORMANCY_ADCTRL(Fast
Dormancy User Admission Control
Algorithm)
Actual Value Range:CRD_ADCTRL,
HSDPA_UU_ADCTRL,
HSUPA_UU_ADCTRL,
MBMS_UU_ADCTRL,
HSDPA_GBP_MEAS,
HSDPA_PBR_MEAS,
HSUPA_PBR_MEAS,
HSUPA_EDCH_RSEPS_MEAS,
EMC_UU_ADCTRL,
RTWP_RESIST_DISTURB,
FACH_UU_ADCTRL,
MIMOCELL_LEGACYHSDPA_ADCTR
L, FAST_DORMANCY_ADCTRL
Default Value:None
PROCESSSWITCH BSC69 ADD UIMEITAC(Optional) Meaning:1) FD_P2D_SWITCH (TAC-
00 MOD UIMEITAC(Optional) Level P2D Control Switch)
When the switch is turned on, state
transition from CELL_PCH/URA_PCH
to CELL_DCH of a UE is triggered if
the following conditions are met:
1. The TAC of the UE is the same as
that configured on the RNC.
2. The UE is in the CELL_PCH or
URA_PCH state, and the RNC
receives a CELL UPDATE message
containing a cause value of "uplink
data transmission" or "PS paging
response."
When the switch is turned off, state
transition from CELL_PCH/URA_PCH
to CELL_DCH is not triggered by the
CELL UPDATE message containing
"uplink data transmission" or "PS
paging response."
In this case, however, the state
transition can be triggered by other
factors in the system. For example, if
the UE is in the CELL_PCH or
URA_PCH state, the state transition to
CELL_DCH can be triggered by a CS
terminated call.
2) FD_TAC_FORCE_D2F_SWITCH
(TAC-based D2F Switch for UEs
Supporting Fast Dormancy)
When the switch is turned on, state
transition from CELL_DCH to
CELL_FACH is forcibly performed on
the UE with the corresponding TAC
and supporting fast dormancy.
When the switch is turned off,
CELL_DCH to CELL_PCH/URA_PCH
state transition is forcibly performed on
the UE with the corresponding TAC
and supporting fast dormancy
GUI Value Range:FD_P2D_SWITCH,
RSVDBIT1_BIT2,
FD_TAC_FORCE_D2F_SWITCH,
RSVDBIT1_BIT4, RSVDBIT1_BIT5,
RSVDBIT1_BIT6, RSVDBIT1_BIT7,
RSVDBIT1_BIT8, RSVDBIT1_BIT9,
RSVDBIT1_BIT10, RSVDBIT1_BIT11,
RSVDBIT1_BIT12, RSVDBIT1_BIT13,
RSVDBIT1_BIT14, RSVDBIT1_BIT15,
RSVDBIT1_BIT16, RSVDBIT1_BIT17,
RSVDBIT1_BIT18, RSVDBIT1_BIT19,
RSVDBIT1_BIT20, RSVDBIT1_BIT21,
 RSVDBIT1_BIT22, RSVDBIT1_BIT23,
RSVDBIT1_BIT24, RSVDBIT1_BIT25,
RSVDBIT1_BIT26, RSVDBIT1_BIT27,
RSVDBIT1_BIT28, RSVDBIT1_BIT29,
RSVDBIT1_BIT30, RSVDBIT1_BIT31,
RSVDBIT1_BIT32
Actual Value Range:This parameter is
set to 0 or 1 according to the related
domains
Default Value:None
PROCESSSWITCH BSC69 SET Meaning:1)INVOKE_TRACE_SWITCH.
00 URRCTRLSWITCH(Optio When it is checked, RNC will start
nal) Invoke Trace procedure upon receiving
INVOKE TRACE Message form CN,
otherwise, RNC won't start the Invoke
Trace procedure though it receives the
INVOKE TRACE message.
2)SYS_INFO_UPDATE_FOR_IU_RST.
When it is checked, RNC will broadcast
SYSTEM INFORMATION messages to
UE when Iu reset, otherwise, RNC
won't broadcast SYSTEM
INFORMATION messages to UE when
Iu reset.
3)DRNC_DIRECT_DSCR. When it is
checked, DRNC will start DSCR
procedure directly in RRC states other
than CELL_DCH, otherwise, DRNC will
transfer RRC CELL UPDATE message
to SRNC.
5)RNC_SHARE_SWITCH. When it is
checked, RNC traffic share function will
be valid, otherwise, RNC traffic function
cannot be used.
6)RNCAP_IMSI_HO_SWITCH. When it
is checked, Imsi handover function will
be used, otherwise it will be not used.
7)TERMINAL_VERSION_DEBASE_S
WITCH. When it is checked, terminal
version R4 will debase to R99.
8)SYS_HO_OUT_CIPHER_SWITCH.
When it is checked, the RNC will add
ciphering byte at GSM HANDOVER
COMMAND if the GSM system do not
add any cipher information at that
message.
9)SYS_HO_CIPHER_CONFIG. When
it is checked, the cipher configuration in
the added cipher byte in GSM will be
A5/1.When it is no checked ,the cipher
configuration is A5/0.
10)ARRED_CELL_FOR_CSDOMAIN_
RST. When it is checked, cell will be
bared when CS domain is invalid,
otherwise the CS domain will be bared
when CS domain is invalid. It is invalid
If SYS_INFO_UPDATE_FOR_IU_RST
is not checked.
11)CR2284R1_SWITCH.in section
8.6.6.28 of TS25.331 of R5
Before2006, it describes that the HFN
should add one when UE is ciphering
in the situation of Timing re-initialized
hard handover, while not specified in
RB SETUP process in the section of
8.6.4.3. so it is not clear whether to add
or not in RB SETUP in DRD scenarios.
CR2284R1 clarify that HFN should add
one in RB SETUP process with Timing
re-initialized hard handover. when it is
checked ,RNC accepts this CR2284R1;
when it is not checked ,RNC does not
accept this CR2284R1.
12)CDT_MSG_FULL_TRACE: When it
is checked, CDT trace function which
starts tracing from message RRC
CONNECT REQUEST.
13)CR2284R1_COMPATIBLE_SWITC
H.CR2284R1 causes the compatible
problem. if UE is not consistent with
RNC regarding whether accept the
CR2284R1 or not, it will cause the
problem of streaming when UEs are
communicating with each other. So
RNC creates this switch. when it is
checked, RNC is auto-adaptive to
accept the CR2284R1 according to UE
version information. The principles that
RNC judges UE whether to accept the
CR2284R1 are as follows: R5 and
above UE accepts the CR; R99/R4 UE,
if it receives the START LIST value
from RB SETUP COMPLETE,RNC
figures that UE accepts the CR;
R99/R4 UE, if it only receives the
START value from RB SETUP
COMPLETE,RNC figures that UE does
not accept the CR; when it is not
checked, whether RNC accept the CR
or not is according to
CR2284R1_SWITCH. The relations
between these two switches
CR2284R1_SWITCH and
CR2284R1_COMPATIBLE_SWITCH
are as follows:
(1)CR2284R1_COMPATIBLE_SWITC
H is checked, RNC is self-compatible,
so the CR2284R1_SWITCH is invalid;
(2)CR2284R1_COMPATIBLE_SWITC
H is not checked, the
CR2284R1_SWITCH is valid.
14)COMBINE_OPERATION_DRD_SW
ITCH. When it is on, RNC will not reject
the message RB SETUP CMP without
the IE active time.
15)UL_INTER_PROTECT_SWITCH.
When the switch is off, RNC will not do
integrity protection check for uplink
RRC messages.
16)FAST_DORMANCY_SWITCH.
When it is checked, RNC will apply
FAST DORMANCY function.
17)SYS_HO_IN_CIPHER_SWITCH.
When it is checked, don't receive the
encrypted ability information from
RELOC REQ ,default configured of
encrypted parameter are UIA1 and
UEA0.
18)PTT_EARLY_TRANS_SWITCH_O
FF. When it is checked, PTT user will
not apply the early transmission
function, otherwise, PTT user will apply
the early transmission function.
19)UPLINK_MDC_ENHENCEMENT_S
WITCH. This switch has become
invalid.
20)NODEB_PRIVATE_INTERFACE_S
WITCH. When it is checked, the NodeB
private interface data can be taken to
the NodeB through the IUB protocol
message.
21)PTT_SPEC_LI_SWITCH_OFF.
When it is checked, special LI will not
 be used for PTT user, otherwise,
special LI will be used for PTT user.
22)RNC_DF_2_URA_PCH_SWITCH.
When it is checked, RNC will support
transferring Fast Dormancy UE from
CELL_DCH or CELL_FACH to
URA_PCH. When it is not checked,
RNC will not support transferring Fast
Dormancy UE from CELL_DCH or
CELL_FACH to URA_PCH.
23)FD_TAC_MATCH_SWITCH. When
it is checked, RNC will apply FAST
DORMANCY function for UE whose
TAC is configured in database. When it
is not checked, RNC will apply FAST
DORMANCY function for UE whose
version is R5 or later
GUI Value
Range:INVOKE_TRACE_SWITCH,
SYS_INFO_UPDATE_FOR_IU_RST,
DRNC_DIRECT_DSCR,
RNC_SHARE_SWITCH,
RNCAP_IMSI_HO_SWITCH,
TERMINAL_VERSION_DEBASE_SWI
TCH,
SYS_HO_OUT_CIPHER_SWITCH,
SYS_HO_CIPHER_CONFIG,
BARRED_CELL_FOR_CSDOMAIN_R
ST, CR2284R1_SWITCH,
CDT_MSG_FULL_TRACE,
CR2284R1_COMPATIBLE_SWITCH,
COMBINE_OPERATION_DRD_SWIT
CH, UL_INTER_PROTECT_SWITCH,
FAST_DORMANCY_SWITCH,
SYS_HO_IN_CIPHER_SWITCH,
PTT_EARLY_TRANS_SWITCH_OFF,
UPLINK_MDC_ENHENCEMENT_SWI
TCH,
NODEB_PRIVATE_INTERFACE_SWI
TCH, PTT_SPEC_LI_SWITCH_OFF,
RNC_DF_2_URA_PCH_SWITCH,
FD_TAC_MATCH_SWITCH
Actual Value Range:This parameter is
set to 0 or 1 according to the related
domains
Default Value:None
PsInactTmrForFstDr BSC69 SET Meaning:This parameter specifies the
mDch 00 UPSINACTTIMER(Option value of the CELL-DCH inactivity timer
 al) for UEs enabled with the Fast
Domancy feature. When detecting that
the Fast Domancy User in PS domain
had no data to transfer in CELL-DCH
for a long time which longer than this
timer, the state transition from CELL-
DCH to CELL-FACH or CELL-PCH is
triggered. To enable this timer, set this
timer to a value other than 0
GUI Value Range:0~64800
Actual Value Range:0~64800
Default Value:4
PsInactTmrForFstDr BSC69 SET Meaning:This parameter specifies the
mFach 00 UPSINACTTIMER(Option value of the CELL-FACH inactivity
al) timer for UEs enabled with the Fast
Dormancy feature. When detecting that
the Fast Dormancy User in PS domain
had no data to transfer in CELL-FACH
for a long time which longer than this
timer, the state transition from CELL-
FACH to CELL-PCH is triggered. To
enable this timer, set this timer to a
value other than 0
GUI Value Range:0~64800
Actual Value Range:0~64800
Default Value:10
PsInactTmrForPreFst BSC69 SET Meaning:This parameter specifies the
Drm 00 UPSINACTTIMER(Option value of the CELL-PCH inactivity timer
al) for UEs enabled with the Fast
Dormancy feature. When detecting that
the Fast Dormancy User in PS domain
had no data to transfer in CELL-PCH
for a long time which longer than this
timer, the UE is released. To enable
this timer, set this timer to a value other
than 0
GUI Value Range:0~64800
Actual Value Range:0~64800
Default Value:360
ReservedSwitch0 BSC69 SET Meaning:CORRM algorithm reserved
00 UCORRMALGOSWITCH( switch 0. The switch is reserved for
Optional) further change request use.
1) RESERVED_SWITCH_0_BIT2:
When the switch is set to ON, only
uplink RLC or downlink RLC can be re-
established during the state transition
from CELL_FACH to CELL_DCH (F2D
for short).
2) RESERVED_SWITCH_0_BIT3:
When the switch is set to ON, signaling
radio bearers (SRBs) cannot be
changed from DCHs to HSPA channels
(including the channel change from
DCH to E-DCH in the uplink and from
DCH to HS-DSCH in the downlink)
during directed retry.
3) RESERVED_SWITCH_0_BIT4:
When the switch is turned on, the RNC
does not consider whether the cell is
congested during AMR service
establishment. That is, parameters are
set on the precondition that the cell is
not congested. This prevents
inconsistency in uplink and downlink
AMR modes.
4) RESERVED_SWITCH_0_BIT5:
When the switch is set to ON, the RNC
establishes the BE service of a UE on
R99 channels instead of on HSUPA
channels if the uplink coverage of the
UE is limited. The RNC determines
whether the uplink coverage of a UE is
limited on the basis of the Ec/N0
reported by the UE during RRC
connection establishment.
5) RESERVED_SWITCH_0_BIT6:
When the switch is set to ON, the
directed retry algorithm based on
downlink load balance is enabled.
When the switch is set to OFF, this
algorithm is disabled. This algorithm is
an optimization of the original downlink
load balance algorithm.
6) RESERVED_SWITCH_0_BIT7:
When the switch is set to ON, BE
services that are already established
on E-DCHs can be re-established on
DCHs due to insufficient coverage.
7)
RESERVED_SWITCH_0_BIT8: When
the switch is turned on, D2F state
transition is allowed regardless of
whether the CCCH exists on the Iur
interface. If D2F state transition fails,
DSCR is triggered. When the switch is
turned off, the RNC needs to determine
whether the CCCH exists on the Iur
interface before determining whether to
trigger D2F state transition.
8) RESERVED_SWITCH_0_BIT9:
When the switch is set to ON, the
uplink 0 kbit/s transport format of
subflow A of an AMR service (WB AMR
service or NB AMR service) is
0*TbSize. When the switch is set to
OFF, the uplink 0 kbit/s transport
format of subflow A of an AMR service
is 1*0.
9) RESERVED_SWITCH_0_BIT10:
When the switch is turned on, multiple
cross-Iur radio links (RLs) belonging to
the same DRNC can be added
simultaneously. If an RL fails to be
added with the failure cause of
RadioNetwork:unspecified (14), the
RNC attempts to reestablish the RL for
only once.
10) RESERVED_SWITCH_0_BIT11:
When the switch is turned on, the PS
service must be carried by DCHs in the
uplink if both CS and PS services exist
GUI Value
Range:RESERVED_SWITCH_0_BIT1,
RESERVED_SWITCH_0_BIT2,
RESERVED_SWITCH_0_BIT3,
RESERVED_SWITCH_0_BIT4,
RESERVED_SWITCH_0_BIT5,
RESERVED_SWITCH_0_BIT6,
RESERVED_SWITCH_0_BIT7,
RESERVED_SWITCH_0_BIT8,
RESERVED_SWITCH_0_BIT9,
RESERVED_SWITCH_0_BIT10,
RESERVED_SWITCH_0_BIT11,
RESERVED_SWITCH_0_BIT12,
RESERVED_SWITCH_0_BIT13,
RESERVED_SWITCH_0_BIT14,
RESERVED_SWITCH_0_BIT15,
RESERVED_SWITCH_0_BIT16,
RESERVED_SWITCH_0_BIT17,
RESERVED_SWITCH_0_BIT18,
RESERVED_SWITCH_0_BIT19,
RESERVED_SWITCH_0_BIT20,
RESERVED_SWITCH_0_BIT21,
 RESERVED_SWITCH_0_BIT22,
RESERVED_SWITCH_0_BIT23,
RESERVED_SWITCH_0_BIT24,
RESERVED_SWITCH_0_BIT25,
RESERVED_SWITCH_0_BIT26,
RESERVED_SWITCH_0_BIT27,
RESERVED_SWITCH_0_BIT28,
RESERVED_SWITCH_0_BIT29,
RESERVED_SWITCH_0_BIT30,
RESERVED_SWITCH_0_BIT31,
RESERVED_SWITCH_0_BIT32
Actual Value
Range:RESERVED_SWITCH_0_BIT1,
RESERVED_SWITCH_0_BIT2,
RESERVED_SWITCH_0_BIT3,
RESERVED_SWITCH_0_BIT4,
RESERVED_SWITCH_0_BIT5,
RESERVED_SWITCH_0_BIT6,
RESERVED_SWITCH_0_BIT7,
RESERVED_SWITCH_0_BIT8,
RESERVED_SWITCH_0_BIT9,
RESERVED_SWITCH_0_BIT10,
RESERVED_SWITCH_0_BIT11,
RESERVED_SWITCH_0_BIT12,
RESERVED_SWITCH_0_BIT13,
RESERVED_SWITCH_0_BIT14,
RESERVED_SWITCH_0_BIT15,
RESERVED_SWITCH_0_BIT16,
RESERVED_SWITCH_0_BIT17,
RESERVED_SWITCH_0_BIT18,
RESERVED_SWITCH_0_BIT19,
RESERVED_SWITCH_0_BIT20,
RESERVED_SWITCH_0_BIT21,
RESERVED_SWITCH_0_BIT22,
RESERVED_SWITCH_0_BIT23,
RESERVED_SWITCH_0_BIT24,
RESERVED_SWITCH_0_BIT25,
RESERVED_SWITCH_0_BIT26,
RESERVED_SWITCH_0_BIT27,
RESERVED_SWITCH_0_BIT28,
RESERVED_SWITCH_0_BIT29,
RESERVED_SWITCH_0_BIT30,
RESERVED_SWITCH_0_BIT31,
RESERVED_SWITCH_0_BIT32
Default Value:None
RsvdPara1 BSC69 SET Meaning:2) NAS_QOS_MOD_SWITCH
00 URRCTRLSWITCH(Optio (QoS Change Switch for NAS)
nal) When the switch is turned on, for UEs
whose HS-DSCH category is smaller
than 13, if the maximum downlink rate
specified in the PDP activation
requests from the UEs exceeds 16
Mbit/s, the requests are sent to the CN
after the rate is changed to 16 Mbit/s.
When the switch is turned off, the PDP
activation requests are sent to the CN
without changing the maximum
downlink rate.
15) RSVDBIT1_BIT15 (Reserved
Parameter 1 Bit 15)
When the switch is turned on, the RNC
enables the function of AMR mute
detection.
When the switch is turned off, the RNC
disables the function of AMR mute
detection.
16) RSVDBIT1_BIT16 (Reserved
Parameter 1 Bit 16)
When the switch is turned on, the RNC
can perform DRDs during the P2D
procedure.
When the switch is turned off, the RNC
cannot perform DRDs during the P2D
procedure.
17) SYSHO_CSIN_PERMIT_SWITCH
(2G-to-3G CS Handover Switch)
When the switch is turned on, inter-
RAT CS handovers from 2G cells to 3G
cells are allowed.
When the switch is turned off, inter-
RAT CS handovers from 2G cells to 3G
cells are not allowed.
20) RSVDBIT1_BIT20 (Reserved
Parameter 1 Bit 20)
When the switch is turned on, for UEs
that support fast dormancy and are in
the CELL_PCH state, the RNC
performs the CELL_PCH-to-
CELL_FACH (P2F for short) procedure
if the UEs perform cell update with the
cause value "uplink data transmission"
or "paging response."
When the switch is turned off, for UEs
that support fast dormancy and are in
the CELL_PCH state, the RNC
performs the P2D procedure if the UEs
perform cell update with the cause
value "uplink data transmission" or
"paging response."
21) RSVDBIT1_BIT21 (Reserved
Parameter 1 Bit 21)
When the switch is turned on, for UEs
that are establishing AMR services and
shifting from the CELL_FACH state to
the CELL_DCH state, the RNC stops
establishing AMR services to handle
cell update if the RNC receives from
the UEs a cell update message
containing the cause value "cell
reselection."
When the switch is turned off, for UEs
that are establishing AMR services and
shifting from the CELL_FACH state to
the CELL_DCH state, if the RNC
receives from the UEs a cell update
message containing the cause value
"cell reselection," the RNC stops
establishing AMR services to handle
cell update and resumes AMR services
only after cell update is completed.
22) RSVDBIT1_BIT22 (Reserved
Parameter 1 Bit 22)
When the switch is turned on, the RNC
does not trigger cell update with the
cause value "RL Failure" if the RNC
detects interrupted downlink
transmission on SRB2.
When the switch is turned off, the RNC
triggers cell update with the cause
value "RL Failure" and reestablishes
radio links if the RNC detects
interrupted downlink transmission on
SRB2.
23) RSVDBIT1_BIT23 (Reserved
Parameter 1 Bit 23)
When the switch is turned on, the RNC
does not trigger cell update with the
cause value "RL Failure" reported by a
UE if the associated NodeB reports to
the RNC that all radio links for the UE
experience synchronization loss.
When the switch is turned off, the RNC
triggers cell update with the cause
value "RL Failure" reported by a UE
and reestablishes radio links, if the
associated NodeB reports to the RNC
that all radio links for the UE
experience synchronization loss.
24) RSVDBIT1_BIT24 (Reserved
Parameter 1 Bit 24)
When the switch is turned on, for UEs
using CS services, the RNC does not
trigger cell update with the cause value
"RL Failure" reported by a UE, if the
RNC detects interrupted downlink
transmission on SRB2, or if the
associated NodeB reports to the RNC
that all radio links for the UE
experience synchronization loss.
When the switch is turned off, for UEs
using CS services, the RNC triggers
cell update with the cause value "RL
Failure" reported by a UE and
reestablishes radio links, if the RNC
detects interrupted downlink
transmission on SRB2, or if the
associated NodeB reports to the RNC
that all radio links for the UE
experience synchronization loss.
25) RSVDBIT1_BIT25 (Reserved
Parameter 1 Bit 25)
When the switch is turned on, for UEs
using PS services only, the RNC does
not reestablish radio links for a UE if
the RNC detects interrupted downlink
transmission on SRB2, or if the
associated NodeB reports to the RNC
that all radio links for the UE
experience synchronization loss.
When the switch is turned off, for UEs
using PS services only, the RNC
triggers cell update with the cause
value "RL Failure" reported by a UE
and reestablishes radio link, if the RNC
detects interrupted downlink
transmission on SRB2, or if the
associated NodeB reports to the RNC
that all radio links for the UE
experience synchronization loss.
26) RSVDBIT1_BIT26 (Reserved
Parameter 1 Bit 26)
When the switch is turned on, the RNC
does not reestablish radio links for a
UE if the UE reports to the RNC cell
update caused by SRB reset.
When the switch is turned off, the RNC
reestablishes radio links for a UE if the
UE reports to the RNC cell update
caused by SRB reset.
28) RSVDBIT1_BIT28 (Reserved
Parameter 1 Bit 28)
When the switch is turned on, for UEs
using CS services, if a NodeB reports
to the RNC that all radio links for a UE
experience synchronization loss, the
RNC starts the RL Restore timer
whose duration is specified by the
RlRstrTmr parameter in the SET
USTATETIMER command. After the
timer has expired, the RNC triggers cell
update with the cause value "radio link
failure" and reestablishes radio links for
the UE.
When the switch is turned off, for UEs
using CS services, if a NodeB reports
to the RNC that all radio links for a UE
experience synchronization loss, the
RNC starts the RL Restore timer
whose duration is specified by the
T313 parameter in the SET
UCONNMODETIMER command. After
the timer has expired, the RNC triggers
cell update with the cause value "radio
link failure" and reestablishes radio
links for the UE.
29) RSVDBIT1_BIT29 (Reserved
Parameter 1 Bit 29)
When the switch is turned off, the RNC
performs the CELL_DCH-to-
CELL_FACH (D2F for short) procedure
on UEs that support fast dormancy.
When the switch is turned on, the RNC
performs the CELL_DCH-to-
CELL_PCH (D2P for short) procedure
on UEs that support fast dormancy
GUI Value Range:RSVDBIT1_BIT1,
NAS_QOS_MOD_SWITCH,
RSVDBIT1_BIT3, RSVDBIT1_BIT4,
RSVDBIT1_BIT5, RSVDBIT1_BIT6,
RSVDBIT1_BIT7, RSVDBIT1_BIT8,
 RSVDBIT1_BIT9, RSVDBIT1_BIT10,
RSVDBIT1_BIT11, RSVDBIT1_BIT12,
RSVDBIT1_BIT13, RSVDBIT1_BIT14,
RSVDBIT1_BIT15, RSVDBIT1_BIT16,
SYSHO_CSIN_PERMIT_SWITCH,
RSVDBIT1_BIT18, RSVDBIT1_BIT19,
RSVDBIT1_BIT20, RSVDBIT1_BIT21,
RSVDBIT1_BIT22, RSVDBIT1_BIT23,
RSVDBIT1_BIT24, RSVDBIT1_BIT25,
RSVDBIT1_BIT26, RSVDBIT1_BIT27,
RSVDBIT1_BIT28, RSVDBIT1_BIT29,
RSVDBIT1_BIT30, RSVDBIT1_BIT31,
RSVDBIT1_BIT32
Actual Value Range:This parameter is
set to 0 or 1 according to the related
domains
Default Value:None
TAC BSC69 ADD Meaning:Type Allocation Code (TAC)
00 UIMEITAC(Mandatory) is part of the International Mobile
MOD Station Equipment Identity (IMEI), it is
UIMEITAC(Mandatory) used to identify the type of the UE
RMV GUI Value Range:0~99999999
UIMEITAC(Mandatory) Actual Value Range:0~99999999
Default Value:None
WCDMA RAN
Interference Cancellationo
verview of IC
The inherent self-interference in a WCDMA system has a serious impact on system capacity and
coverage range. The parallel interference cancellation (PIC) methods, including Control Channel
Parallel Interference Cancellation (CCPIC) and HSUPA UL Parallel interference cancellation
(E-DPDCH PIC), are introduced in to eliminate interference signals on the DPCCH and E-
DPDCH. PIC helps achieve higher signal-to-interference ratio (SIR) in demodulation and further
improve uplink capacity of the UMTS system. In addition, E-DPDCH PIC implements inter-
board IC and intra-board IC. In this way, other boards benefit from the IC technique. IC is a
multi-user detection technique.

3 Technical Description
3.1 Overview
The WCDMA system is also a self-interference system. Its capacity and performance are
affected by interference from other subscribers, known as multiple access interference (MAI). In
addition, the far-near effect problem still exists. That is, as the distances from subscribers to base
stations increase and the signals fade, strong signals may suppress weak signals. As a result, the
subscribers with relatively weak signals cannot be detected properly.
The Multi-user Detection (MUD) technique provides associated detection methods for
subscribers or reduces interference from received signals to eliminate MAI and inter-code
interference. This technique effectively combats the far-near effect, greatly improves system
performance, and increases capacity of the WCDMA system.
IC is one of the MUD techniques.

3.2 Multi-User Detection Technique

In the scenario of single user, the noise for the user includes background noise, Inter-symbol
interference (ISI), and exterior interference (including neighboring cell).
In the scenario of multiple users, interference between users should be considered as noise too.
This type of interference is called Multiple User Interference (MUI) or Multiple Address
Interference (MAI).
Noise Description
type
NO Background noise
ISI Inter-symbol interference (ISI) is a form of distortion of a signal in which one symbol
interferes with subsequent symbols. This is an unwanted phenomenon as the
previous symbols have similar effect as noise, thus making the communication less
reliable. ISI is usually caused by multipath propagation or the inherent non-linear
frequency response of a channel causing successive symbols to "blur" together.
The presence of ISI in the system introduces errors in the decision device at the
receiver output. Therefore, in the design of the transmitting and receiving filters, the
objective is to minimize the effects of ISI, and thereby deliver the digital data to its
destination with the smallest error rate possible. Ways to fight inter-symbol
interference include adaptive equalization and error correcting codes.
MAI MAI is caused by multiple access technology. Scrambling codes are used to
distinguish UEs in the uplink. Scrambling codes are not orthogonal. So the users
interfere with each other in the uplink and cause Multiple Access Interference (MAI).
When SF is large and subscriber number is small, the MAI is approximate to
Gaussian white noise and has little impact on performance. But when SF is small or
subscriber number is large, the MAI can not be taken as Gaussian white noise and
affects performance greatly.

A traditional detection technique uses a matched filter to despread the received signals and is
followed by an information bit decision. A common receiver does not perform combined signal
processing because it does not consider the MAI from other subscribers. That is, it does not use
transmission information from other subscribers.
Compared with the common detection technique, the multi-user detection (MUD) technique uses
signal information from all subscribers that have generated MAI to detect signals of a single
subscriber. The MUD technique improves the anti-interference capability of the system, solves
the near-far effect problem, efficiently uses the spectrum resource in the uplink (UL), and also
increases system capacity.

3.3 Classification of Multi-User Detection Technique

The MUD technique can be classified into optimal MUD and suboptimal MUD.
Optimal MUD is implemented by using a matched filter and the Viterbi algorithm to detect the
transmit sequence with the maximum posterior probability for the received signals. This
technique is also called maximum likelihood sequence (MLS) detection. The Viterbi algorithm
has excellent performance. The MLS detection uses the amplitude and phase of the received
signals, which are obtained through estimation. The computational complexity of the estimation
increases exponentially with the number of users and therefore the optimal MUD actually cannot
be implemented in reality.
Suboptimal MUD is classified into two types: linear MUD and non-linear MUD. The IC
technique is one of the non-linear MUD techniques. It estimates the MAI produced by different
subscribers, through decision and reconstruction, and then eliminates part of or all interference
from the received signals. The interference canceller (IC) need not include the calculation of
correlated matrix. It can be expanded without increasing the calculation complexity. In addition,
the interference canceller can improve the reception performance of low-power signals.
Therefore, the IC technique is often preferred in a third-generation (3G) communications system.
The basic idea of IC is to estimate the MAI in the received signals through decision and
reconstruction and then to eliminate part of or all interference before the decision. The main IC
methods are as follows:
Parallelinterference cancellation (PIC)
PIC performs decision and reconstruction on signals of multiple subscribers simultaneously to
reduce the impact of MAI between subscribers. Currently, the IC method used in Huawei products
is PIC.
Successive interference cancellation (SIC)
SIC performs decision and reconstruction on signals of a single subscriber at each level and then
eliminates interference from the received signals to reduce the impact of MAI on other subscribers
at lower levels. Generally, the operations by levels are performed in descending order of power of
received signals. That is, the SIC operation is performed on subscribers in sequence from strong
power to low power. Therefore, subscribers with lower power benefit most from the method.
Figure 3-1 MUD methods

3.4 Parallel Interference Cancellation

Based on different scenarios, Huawei provides the following PIC methods:
Control
channel parallel interference cancellation (CCPIC)
HSUPA UL interference cancellation (E-DPDCH PIC)

In addition to the principles of IC, differences and characteristics of the PIC methods are
described in the subsequent sections.

3.4.1 Basic Data Flow of Parallel Interference Cancellation

Figure 3-2 shows the basic data flow of PIC.
Figure 3-2 Basic data flow of PIC

The IC technique includes the following operations:

1. One-time demodulation or data regeneration: After the NodeB receives the antenna data
(data of all subscribers), it demodulates the data of each subscriber and then modulates the
data to obtain the modulated data of each subscriber, that is, regenerating subscriber data.
2. IC: The regenerated data is sent to the IC module.
3. NodeB demodulation: The NodeB demodulates the data after IC.

3.4.2 Interference Cancellation Objects

The HSUPA function of the WCDMA system provides a new UL transport channel, called E-
DCH. In contrast to HSDPA, HSUPA uses dedicated channels rather than shared channels. Each
UE is assigned a dedicated E-DCH, which is independent from the DCH and channels of other
UEs. At the same time, HSUPA uses various new physical channels, as shown in Figure 3-3.
Figure 3-3 shows all the physical channels required for running HSUPA, except the broadcast
channel.
The E-DPDCH is a physical channel used for the UE to transmit bits (E-DCH processing results)
to the NodeB. Subscriber data is carried on this channel. With the increase of the HSUPA rate,
the UL interference increases.
The IC technique is developed to eliminate interference signals on the two types of channels.
CCPIC is used to eliminate interference signals on the DPCCH. E-DPDCH PIC is used to
eliminate interference signals on the E-DPDCH.
Figure 3-3 Physical channels required for HSUPA when the R99 DCH is used in the DL

E-HICH: E-DCH HARQ Acknowledgement Indicator Channel

 E-RGCH: E-DCH Relative Grant Channel
E-AGCH: E-DCH Absolute Grant Channel
E-DPCCH: E-DCH Dedicated Physical Control Channel
E-DPDCH: E-DCH Dedicated Physical Data Channel
UE: User Equipment

3.4.3 Control Channel Parallel Interference Cancellation

Control Channel Parallel Interference Cancellation (CCPIC) is used to eliminate interference
signals on the DPCCH.
Each subscriber has a control channel that is the major source for the interference, especially for
low-rate and low-activity services. CCPIC is a simplified MUD technique of the receiver in the
NodeB. It is used in the heavy-load scenario. By eliminating interference from the UL control
channel signals in the baseband data and reducing UL interference, CCPIC improves system
capacity and thus reduces the investment for operators.
The principle of CCPIC is as follows: After receiving baseband signals, the NodeB demodulates
the signals. According to the multipath delay and fading signals, the data regeneration module
regenerates DPCCH signals and sends them to the IC module for IC processing. The data on
other channels such as the DPDCH, E-DPDCH, and E-DPCCH can be demodulated after IC is
performed on the DPCCH.

3.4.4 E-DPDCH PIC

HSUPA UL interference cancellation (E-DPDCH PIC) is used to eliminate interference signals
on the UL high-rate E-DPDCH. This function is controlled by the parameter IC_MODE.
HSUPA provides UL high-rate services. The Radio Access Network (RAN), based on the
wideband code division multiple access technology, is a typical self-interference system. With
the increase of the HSUPA rate, the UL interference increases. The UL interference is a major
factor affecting the UL capacity of the RAN.
E-DPDCH PIC greatly improves the UL capacity of the RAN system. When there are few high-
throughput HSUPA subscribers and several low-throughput HSUPA subscribers in the system,
high-throughput HSUPA subscribers generate serious UL interference to low-throughput
HSUPA subscribers, and the rate of the original high-throughput HSUPA subscribers is also
affected. E-DPDCH PIC can reduce the interference from high-throughput HSUPA subscribers
on other subscribers. When E-DPDCH PIC is used, more subscribers using low-rate services
such as VoIP can access the network, considering that the rate of the existing subscribers remains
unchanged.
In the HSUPA application scenario, if there are some high-rate HSUPA subscribers, E-DPDCH
PIC can be used to increase the SIR and the system capacity.
When E-DPDCH PIC is used, the NodeB demodulates the HSUPA UL E-DPDCH data and then
performs IC based on the demodulated data and the original received baseband data. Then, the
NodeB demodulates the baseband data again after IC. For the baseband data after IC, the
interference from the E-DPDCH data is eliminated and the MAI is reduced. Therefore, the
signal-to-noise ratio (SNR) of the data is improved.
Huawei NodeB can provide an IC resource pool to share signals generated after IC between the
boards. The functions of the IC resource pool are as follows:
Intra-boardIC: IC results cannot be shared between boards. IC results of an IC-capable board
can be used within the board only but cannot be shared with other boards, irrespective of
whether these boards are IC-capable.
 Inter-board IC: IC results can be shared between all boards in the NodeB. That is ,when there
are multiple IC-capable boards in a NodeB, IC-capable boards can share IC results with each
other. In addition, IC-incapable boards in this NodeB can also share the IC results of IC-
capable boards. As a result, users carried on IC-incapable boards can use the signals after IC
rather than the original signals for demodulation. This improves the demodulation
performance of users carried on IC-incapable boards and brings gain from IC.
Currently, only the 3800/3900 series base stations support inter-board IC. Other types of base
stations support intra-board IC only.
4 Parameters
Table 4-1 Parameter description
Parameter NE MML Command Description
ID
IC_MODE NodeB ADD LOCELL Meaning:Indicates whether Interference
MOD LOCELL Cancellation(IC) is supported by the cell
GUI Value Range:FALSE(FALSE),
TRUE(TRUE)
Actual Value Range:FALSE, TRUE
Default Value:FALSE(FALSE)
5 Counters
Table 5-1 Counter description
Counter ID Counter Name Counter Feature ID Feature Name
Description
50331892 VS.HSUPA.Ic.MeanEff Average WRFD-010691 HSUPA UL
efficiency of IC Interference
in a cell Cancellation
50341858 VS.HSUPA.Ic.MaxEff Maximum WRFD-010691 HSUPA UL
efficiency of IC Interference
in a cell Cancellation
4.1.2 Cell Selection Criteria (Criteria S)
The cell selection criterion S is fulfilled when:
Srxlev > 0 and Squal > 0,

Where:

Squal = Qqualmeas Qqualmin

Srxlev = Qrxlevmeas - Qrxlevmin - Pcompensation
Parameter Description
Squal Cell selection quality value (dB)
Applicable only to FDD cells
Srxlev Cell selection RX level value (dB)
Qqualmeas Measured cell quality value
Quality of the received signal indicated in average CPICH Ec/No (dB) for FDD
cells
Applicable only to FDD cells
Qrxlevmeas Measured cell RX level value
CPICH RSCP of received signal for FDD cells (dBm).
P-CCPCH RSCP of received signal for TDD cells (dBm)
Qqualmin Qqualmin, required minimum quality level
Qrxlevmin Qrxlevmin, required minimum RX level
Pcompensation Max (MaxAllowedUlTxPowerMaxUEPower, 0) (dB)
where,
MaxAllowedUlTxPower, maximum allowed UE UL TX power.

MaxUEPower: maximum RF output power of the UE (dBm)

MaxAllowedUlTxPower is set by the network according to the designed cell

coverage. When the maximum UE power is lower than the value, the effective
cell coverage for this UE is actually reduced by Pcompensation.

The parameters Qqualmin and Qrxlevmin can be set through the MML command ADD
UCELLSELRESEL or ADD UINTERFREQNCELL.
Ifthe parameter InterNCellQualReqFlag is set to True, the values of Qqualmin and
Qrxlevmin which are set through ADD UINTERFREQNCELL will be used and broadcast
through SIB11.
Otherwise, the values of Qqualmin and Qrxlevmin which are set through ADD
UCELLSELRESEL will be used and broadcast through SIB3.
4.2 Cell Reselection
The signal strength of both serving cell and neighboring cells varies with the movement of a UE
and so the UE needs to reselect the most suitable cell to camp on. This process is called cell
reselection. Cell reselection involves three parts: cell reselection process, measurement start
criteria, and cell reselection criteria.

4.2.1 Cell Reselection Process

The cell reselection process is as follows:
Step 1 The UE calculates the serving cell SX according to the following formulas:
Squal = Qqualmeas - Qqualmin
Srxlev = Qrxlevmeas - Qrxlevmin - Pcompensation

For detailed description of the formulas, see 4 Cell Selection.

Figure 4-1 shows the cell reselection of the UEs in idle mode.
Step 2 The UE decides whether to start the intra-frequency or inter-frequency measurement
according to the Sx and the UE movement state.
To start the intra-frequency, inter-frequency, or inter-RAT measurement, go to Step 3. For
details, see 4.2.2 Measurement Start Criteria.
Otherwise, end the cell reselection.
Step 3 The cells are queued according to the measurement results. The UE selects a suitable cell
to camp on according to the cell reselection criteria. For details, see 4.2.3 Cell Reselection
Criteria.
----End

4.2.2 Measurement Start Criteria

The Hierarchical Cell Structure (HCS) may affect the measurement start criteria for cell
reselection.
Measurement Start Criteria with HCS Disabled
Figure 4-2 shows the intra-frequency, inter-frequency and inter-RAT measurement criteria in
the case when the system information broadcast in the serving cell indicates that the HCS is
disabled.
Figure 4-2 Measurement start criteria for cell reselection with HCS disabled

Intra-frequency measurement
If Squal > Sintrasearch, the UE need not start the intra-frequency measurement.
If Squal Sintrasearch, the UE need to start the intra-frequency measurement.

If system messages do not contain Sintrasearch, the UE always need to start the intra-frequency
measurement.
Sintrasearch is set through IdleSintrasearch or ConnSintrasearch on the RNC side.
Inter-frequency measurement
If Squal > Sintersearch, the UE need not start the inter-frequency measurement.
If Squal Sintersearch, the UE need to start the inter-frequency measurement.
 If
system messages do not contain Sintersearch, the UE always need to start the inter-frequency
measurement.
Sintersearch is set through IdleSintersearch or ConnSintersearch on the RNC side.
Inter-RAT measurement
If Squal > SsearchRATm, the UE need not start the inter-RAT measurement.

If Squal SsearchRATm, the UE need to start the inter-RAT measurement.

If system messages do not contain SsearchRATm, the UE always need to start the inter-RAT
measurement.
SsearchRATm is set through SsearchRat on the RNC side.