Basic Question and answer

1. 1. How many paging messages can be sent in the same time?
Generally speaking, it does not make much sense to ask about the capacity for paging, since the MSC
performs a lot of tasks in parallel, and Paging is one of them. It does not make sense to state, that the
MSC can perform x-thousand pagings per hour, if nothing else is going on in the node. The performance
of the MSC is a function of the traffic profile (and that includes the paging). Paging is performed for each
MT call, and for 25% (in the default traffic profile) a second page attempt is done. So knowing the BHCA
of a node, and the % of MT, one can roughly calculate the total number of pagings.
2. Give examples of a gauge counter, a counter that can decrease and increase its values?
ATM Adaption Layer 2 Access Point Counters, pmExisOrigConns Description Performance monitoring
counter
pmExisOrigConns. Number of existing connections for the AP originating in this node.
3. How long is the paging queue and how can you set it? Is it any difference from the GSM paging
queue?
The paging flow is quite complex in the RNC. A page request may pass several MPs and SPs, depending
on LA definition and how the cells are distributed over internal resources (module MPs and cc SPs). A
single page request will be multiplied into several page signals to the CC SPs that are responsible for the
cells to be paged. Internally the page signals to a CC SP include cell lists with the cells to be paged from
that cc SP.
Each cc SP has a buffer of 30 000 paging signals to be sent on PCH. In a large RNC there is normally 55
cc SP (30000x55). In the most critical case, when every cell must be paged (2304 cells --> 2304 paging
signals) for a UE, the page buffer size is approx. 716 (30000x55/2304), i.e. 716 UEs can be paged
simultaneously. In practice, the max number of simultaneous UEs is much higher.
There are no specific paging queues at MP level, the paging signal flows are mixed with other signaling.
An RNC F configuration (1 LA) supporting 300 000 users according to Ericsson CTM will generate a
paging load of 280 000 paging/hour. Note, this is not a system limit; the RNC can support a much higher
paging load, depending on traffic model, HW release, LA configuration, etc.
4. Paging success rate formula?
Paging success should be measured at MSC level. Notice that even if a UE does not response to a
paging in a certain Location Area, a second paging might be sent throughout the whole MSC area
(depending on configuration) and UE can be finally reached. For this reason the most reliable indicator for
paging is the one obtained at MSC level.
Maybe a little old formula, but I am not an expert in the MSC world:
5. When is spreading factor 4 used?
Spreading factor 4 is used for PS384/HS connections
6. Is it possible for the counters to step if you do not activate them from the OSS-RC? Is there
another way to activate them and look at them without using OSS-RC?
Some of the counters are always active from start. OSS is the only way to activate the counters; it also
collects the counter ROP files from the nodes and puts them in a directory on the OSS server. You may
then chose to use OSS features to put this data in SDM and view it using OSS or process the rop files
using another system.

2. 7. Loadsharing to GSM, is there any special counters on the GSM side to compare to the
loadsharing counters on the WCDMA side? In order to see how many of the calls that is really
redirected to GSM? Where does the dropped call step if it is dropped during loadsharing.
There are no GSM counters for statistics on incoming HO from WCDMA to GSM (IRAT U2G). In the BSC
only HO from GSM to WCDMA (IRAT G2U) is stepped/counted.
GSM R12
HOVERCNTUTRAN Number of handover commands sent to the neighboring UTRAN FDD cell
HOVERSUCUTRAN Number of successful handovers to the neighboring UTRAN FDD cell
HORTTOCHUTRAN Number of handover attempts to the neighboring UTRAN FDD cell where the MS
returns to the old channel
HOREQCNTUTRAN Number of handover required sent for the neighboring UTRAN
[new]SUCURGHOUTRAN Number of successful handovers to the neighboring UTRAN FDD cell due
to urgency conditions
[new]URGHOVERUTRAN Number of handover commands sent to the neighboring UTRAN FDD cell
due to urgency conditions
[new]HOATTSHOULDUTRAN Number of handover commands to the neighboring UTRAN FDD
cell due to Service Handover value is equal to "should"
In the case of load sharing for Directed Retry to GSM and where the dropped call is stepped, it where in
the procedure the call is dropped.
If Directed retry to GSM attempt is initiated and if the call is dropped before "RANAP Iu Release
Command" with cause value 'successful relocation' or 'normal release' is received on WCDMA side for the
connection, the dropped call is stepped in WCDMA. If the calls drops after that RANAP message the
dropped call should be stepped in GSM since it is considered a successful IRAT U2G.
8. HSDPA counters for accessability, retainability and integrity?
pmTransmittedCarrierPowerNonHs - RBS counter monitoring the power of all codes not used for HS-
PDSCH or HS-SCCH
pmNoOfTermHsCong & pmNoOfIurTermHsCong - RNC counters monitoring no. of HSDPA users
released due to congestion
pmTransmittedCarrierPowerNonHs - RBS counter monitoring the power of all codes not used for HS-
PDSCH or HS-SCCH
pmNoOfNonHoReqDenied - RNC counter monitoring no. of admission rejects of HSDPA users
pmSamplesSf4Ul - Number of samples of the amount of radio links that are on SF=4 in UL
pmSumSf4Ul - Sum of the sampled amount of radio links that are on SF = 4 in UL
9. What is the difference between the primary and the secondary profiles created? What do they
contain?
In the very end of the document you will find a list of all the counters. http://cpi.al.sw.ericsson.se/alexserv?
UZ=cpi.al.sw:9230&ID=27246&DB=10230-enlzn734_1_r4g.alx&FN=25_1551-
AXD10503_1Uen.G.html#TOP
Performance statistics 25/1551-AXD 105 03/1 Uen G
10. What is the difference between the two formulas in the book at page 124? Release due to SHO
and release due to missing neighbors?
pmNoSysRelSpeechSoHo is the number of system disconnects of a speech call due to Soft Handover
action, for the best cell in the active set. sum (ct_Cell_UtranCell_Peak.pmNoSysRelSpeechSoHo)
pmNoSysRelSpeechNeighbr is the number of system disconnects of a speech call due to unknown
measured cell (missing neighbor relation), for the best cell in the active set. sum
(ct_Cell_UtranCell.pmNoSysRelSpeechNeighbr)
11. Is congestion control taken the Channel Elements into consideration? If not which function or
counters do consider the HW in the RBS?
In P4 the CE is checked by the capacity management, not by the congestion control.
However this is some complementary views:

3. Admission control always prevents the congestion or at least tries to. In P4 we have a RBS HW admission
policy. This policy is comparing the RBS HW towards the parameters ulHwAdm, beMarginUlHw,
dlHwAdm, beMarginDlHw Depending on how they are set the hardware is checked (in reality the
channel elements should be translated to these values)
12. When being denied in admission control, what kind of mode is the UE? Common or dedicated?
If the UE is denied during admission control it will stay on FACH, if the admission is granted the UE will try
to go on the DCH.
The channel switch from fach to dch can fail and then the UE will stay on the common channel if possible.
13. Is the constant regulator or the jump regulator the default algorithm?
It is the jump regulator algorithm that is default.
14. Is the parameter pwradm only working of the dedicated channels or on both common and
dedicated channels?
Congestion control is releasing the BE users on the dedicated channels.
15. What types of counters are the traffic counters? How do they aggregate the traffic values, or not?
The traffic volume counters measures the total amount of kb sent.
16. In compressed mode is the packet user at common channel or in dedicated channel?
What I have seen the users should be in dedicated mode.
For instance when using HSDPA, the UE is not allowed to enter the compressed mode state. It has to be
transformed to R99DCH in order to be in compressed mode.
For the cell reselection and G2U handover/cell change the only measurement quantity available is CPICH
Ec/No. PS cell change can only be performed from the PS 64/64 radio bearer. Hence even if the event 2d
is triggered while on a higher rate bearer compressed mode is not entered until the service is switched
down to the PS 64/64 bearer. This means that the channel switching parameter setting has to be
considered together with the IRAT cell change parameters.
The P4 release is enhanced with the possibility to trigger event 2d/6a and 2f/6b (start and stop of
compressed mode measurements) on both signal strength and signal quality, i.e. combined
measurements of Ec/No, RSCP and UETxPower. For instance triggering to start compressed mode P4
evaluation measures on usedFreqThresh2dEcno, usedFreqThresh2dRscp and ueTxPowerThresh6a.
17. Can a counter be activated through several profiles?
YES, only if it has not already been activated.
18. The parameter maxDlPowerCapability, how is it derived from the RBS? How do we use this
parameter?
maxDlPowerCapability is the minimum downlink power capability for the Cell. It is reported to the RNC,
given in unit of 0.1dBm. Actually there is an alarm in the system that refers to this parameter, it is called
Carrier_MaxDlPowerCapabilityOutOfRange. The likely cause of the alarm is one of the following:
• The parameter dlAttenuation for the affected antenna feeder cable is not in accordance with the
information specified in the Site Installation Documentation (SID)
• A faulty Antenna Interface Unit (AIU) or Single Antenna Interface (sAIU)
• A faulty Multicarrier Power Amplifier (MCPA) or Power Amplifier Unit (PAU)
• A faulty Filter Unit (FU) or a faulty Radio Unit (RU) or a faulty Remote Radio Unit (RRU)
One consequence of the alarm is that the cell setup request from the Radio Network Controller (RNC) is
rejected and the related UtranCell_NbapMessageFailure alarm is issued by the RNC.
The parameter maximumTransmissionPower allows the operator to limit the maximum used power in
the cell. To ensure that the maximum power in the cell is available, maximumTransmissionPower has to

4. be set at, or beyond, the downlink power capability reported by the RBS (maxDlPowerCapability). Note
that if maximumTransmissionPower is set to a higher value than maxDlPowerCapability, the actual
maximum power is still equal to maxDlPowerCapability.
19. Why should we have SDM if we have business objects for statistics? Can BO do the same thing
as SDM?
NWS-A (which uses the BO application) is the presentation layer and uses the data repositories in SDM.
SDM is the statistical data store, and is the source of data for NWS-A features at the presentation layer.
SDM is the data repository, BO is the presentation application
20. N300 is that an operator changable parameter? Is it on RNC level or cell level?
N300 is an RRC related parameter and can not be changed by the operator
21. Is there a counter for the total code power transmitted in a cell? When is this useful to know?
pmTransmittedCarrierPower is measured on the RBS and is sampled every 4th second. This is the total
carrier power used in the RBS. pmDpchCodePowerSfX, where x is the spreading factor, is the average
power transmitted over the Dedicated Physical Channel (DPCH)
Transmitted code power measurement is:
• started on the new Radio Link (RL) at RL Setup or, at RL addition owing to inter frequency hand
over or inter board hand over
• stopped on a RL when the RL or the RL Set (RLS) is deleted or released
• started on another RL (if any) at RL delete
There will only be 1 measurement per RLS. No new measurement is started at RL addition.
22. Are there other counters for Ul out of synch, not only for speech? Any timer counters?
There are no other counters that are directly correlated to ul out of synch than the counter
pmNoSysRelSpeechUlSynch.
23. Is there a timer for the parameter ReleaseConnOffset?
There is no timer correlated to the RelaseConnOffset parameter. The call will be released as soon as the
measured cpich value is above this threshold.
24. How is the loadsharing prioritized? Can we use the IFHO during the same time as the IRAT
handovers?
The IRAT or IFHO functionality can be enabled per cell. When bad connection quality has been triggered,
the type of HO to be attempted is configurable per cell. The parameter hoType can be set per cell to
GsmPreferred, IfPreferred or to None, and a setting to None means that no IRAT or IFHO can be done
from this cell, and compressed mode shall not be started.
25. How is the DL code power measured towards the target in order to down switch? The pilot bits is
sent in every frame, is it measured on every frame or on the transport blocks?
The DL Tx Code Power measurement is a NBAP Dedicated Measurement (as defined by 25.433). For P4
it has the following characteristics:
Measurement type = transmitted code power Activated per RL Event trigged (event E and F) Filter
coefficient: 6 Report hysterisis: 6 (=3dB)
The RBS reports to the RNC according to these criterias. After that the RNC orders downswitch if power
continues to be high during the time defined by coverageTimer (default=1 s).
The resulting characteristics are still approx. the same: We allow the DL Tx Code Power to be 'high' during
~1s before we order downswitch.
26. Why 500 in the formula regarding HSDPA throughput?

5. Each TTI is 2 ms and in order to get it up to the frame size (that is 10 ms) we have to multiply the value
with 500.
27. When is the PS streaming RAB really used?
The PS Streaming bearer can be used for TV, Video etc. The benefit of the PS Streaming bearer
compared to the PS Interactive/Background bearer for these types of services is that the QoS is
guaranteed. One example is that when starting compressed mode for Inter Frequency Handover
evaluation, CM method spreading factor reduction (maintaining the throughput but using more resources)
is used for the PS Streaming bearer and higher layer scheduling (reducing the throughput in order to cater
for the CM gaps) is used for PS Interactive/Background.
28. DCCH traces or similar traces, does Ericsson have a tool for analyzing these files?
Unfortunately there is no tool example to give to external customers, the traces are usually text files
where RNC developers, testers sometimes develop their own "tools" which help them to analyze
traces for their own purposes, but these are not used outside their own organisation.
29. When will the pmNegativeMessages be stepped and why?
This counter is an RBS counter. It is stepped whenever the negative AI message sent by the RBS
on the AICH.
When the UE tries to access the system on RACH and sends preambles to the RBS, the counter
will step if the RBS detects the preamble but for some reason cannot let the UE access, i.e. the
RBS sends a negative AI indicator on the AICH. Normally a rare case.
30. Where does the pmNoPreambleFalseDetection counter fit in the flowchart for random access?
This counter is and RBS counter and is increased whenever the number of false detections for
each GP caused by noise on the RACH. I have not found a flowchart for this counter due to the
fact that it is an RBS counter, and flowcharts only exist for RNC counters. There is no flowchart for
random access. I can therefore not put the counter in the counter flow.
31. How many users can it be on the HSDPA with SF4? Channelization codes up to 15 can be
used??
Actually the DL has SF16-= 16 codes but the RAB HSDPA/384 is limited by the SF in the uplink
which is 4.
32. Is there a counter flow for the NAS procedure available?
There are no counters for monitoring NAS messages directly in RAN.
It is possible to look at NAS messages in RAN by monitoring the RRC messages containing NAS
messages via the GPEH feature (e.g.INITIAL DIRECT TRANSFER, UPLINK DIRECT TRANSFER).
There are no counters for NAS in P4; however in P5 following counters will be introduced:
pmNnsfNriRouted
Number of Ue Initial Direct Transfer messages routed to this Iu interface by the NNSF (NonAccessStratum
node selection function), for which the NRI (Network Resource Identifier) transferred by the Ue matches
the NRI of this Iu interface.
pmNnsfLoadDistributionRouted
Number of Ue Initial Direct Transfer messages routed to this Iu interface by the NNSF (NonAccessStratum
node selection function), for which the NRI (Network Resource Identifier) transferred by the Ue does not
match the NRI of any configured Iu interface with availability status enabled. Will be answered in another
mail

6. 33. Give examples of when a L1 synchronization failure occurs and what we can do in order to
minimize the problems?
L1 Synchronization problems occur most of the times due to an unbalanced system - the DL and UL
coverage is not the same.
One type of problems could be when the UE is indoor and does not have the power to fully synchronize all
the time. The radio link supervision will compare the BER rate and then decide if the UE is in synch or not.
34. Is there a specific counter for UL RSSI and UL Interference?
YES, pmAverageRSSI on RBS level will show what the average UL RSSI is. It is a PDF counter and will
give you a range of different values.
If you want to know more about the RSSI you can do traces on the RBS in order to find the exact values
on a specific RBS.
35. Isn’t Admission control checking the HW usage before the UE setup a call? Why the counters
pmSetupFailureSfX should (where x is the relative SF) is checked in order to see if the RBS has
enough HW such as CE at the RAXB baseband boards?
The channel elements are checked during admission (by the parameter ulHwAdm).
It is up to the operator to set the parameter ulHwAdm. Either you can set it to 100% of the CEs to always
enable all HW or set it lower (70%) to have some margin for soft handover. When all HW is used it is not
possible to set up a call.
Please note that pmDeniedAfterAdm does not necessarily mean lack of CEs, it could be lack of
transmission too.
Which means that if you are in soft handover the calls can be blocked and the counters
pmSetupFailureSfX should be checked in order to see if the entire CE is used up.
36. Is there a counter flow for the counters pmNoSysRelSpeechSoHo and the
pmNoSysRelSpeechNeighbr?
pmNoSysRelSpeechSoHo is increased when the system disconnects a speech call for the best cell in the
active set due to Soft Handover action. pmNoSysRelSpeechNeighbr is increased when the system
disconnects of a speech call for the best cell in the active set due to unknown measured cell (missing
neighbor relation).
For both counters the network initiated call release of speech calls due to inability to include a non-valid or
valid cell in the active set. The counter shall be incremented for the best cell in the active set prior to the
call release.
37. In which release is the releaseconnoffset release to be considered as a normal release? How will
the operator find the drops due to low setting of the releaseconnoffset parameter?
This can be logged by the GPEH event SOHO_MISSING_NEIGHBOUR, one of the fields in the event is
an indication of if the call dropped. The counter pmNoSysRelSpeechNeighbr also logs the Drops, by only
for speech. It is not a normal release, I was wrong. The counter pmtotsystemrabrelease will also be
stepped.
38. The counter pmNoOfSwDownNgCong is said to be stepped when a release is done if a packet
call can not be downswitched. What kind of packet call is this and when does this occur?

7. There is a parameter that can make PS data on common channel not allowed for the whole RNC. If that
parameter is set, this counter will show number of UEs released due to congestion since the connection
shall be released instead of being switched to common channel. Otherwise the counter will be increased
when a UE using the best effort PS data service is switched down to common channel or released due to
cell congestion. The counter is increased in CRNC for non-drifting UEs for the one cell with congestion.
For drifting Ues the counter pmNoOfIurSwDownNgCong will be increased.
When the cell is in congestion packet calls will be switched from 384 to 128 and from 128 to 64 and finally
to FACH if the congestion remains. This counter counts the number of transfers from PS64 to FACH (or
PS64 drops if FACH is not allowed)
39. The counters pmNoFailedAfterAdm and pmNoReqDeniedAdm are they only increased during
RRC setup or both under RRC and RAB setup?
pmNoFailedAfterAdm is the number of RRC or RAB establishment requests failed after being admitted by
admission control. The counter is increased if a function that has been granted admission for a UE fails
after being admitted due to a problem in the RRC or RAB Setup procedure. Then the admission control
function must be informed about the release of previously requested resources due to the failed procedure
and this counter is increased. The counter is increased in the cell or cells where the UE is located. This
counter is stepped for all cells if UE is in macro diversity
pmNoReqDeniedAdm is the number of RAB establishment and RRC requests denied due to admission.
The counter is increased if admission control function denies admission to any UE in this cell. This counter
is stepped only for one cell if the UE is in macro diversity. The cell the counter is stepped for will be the
first cell for which admission control denies access. The remaining cells will not be checked by admission
control after admission is denied to a cell.
40. Are the counters for traffic volumes in the cases before or after macro diversity?
The data is before macro diversity
41. Are there any triggers for the counters pmNoReqDeniedAdm and pmNoFailedAfterAdm? Will the
counters be increased during RRC setup or both under RRC and RAB setup both
pmNoFailedAfterAdm and pmNoReqDeniedAdm seems to be a subset of the counter
pmTotNoUtranRejRrcConnReq. Is Adm ctrl. done twice, both under RRC and under RAB setup
procedure
The counters are incremented once, either if failed under RRC set-up or if failed under RAB set-up.
42. Why does the RNC goes down, why does the auto downtime increases?
Very difficult to say. If the RNC had worked before, and no one has touched the configuration, then one
can assume that it is not a configuration problem. So... Hardware problems, transmission disturbances,
main processor overload, too many scanners ongoing.
The RNC keeps track of how long time is it down.
43. Will the RBS be counted as down if the power to the RBS is down, what happens with the
availability counters?
The RNC keeps track of those RBS that are defined in OSS-RC as managed objects. If the RNC can not
get in contact with the RBS and the cell the counters for cell availability will increase.
44. The tool ESPA, how does this works compared to SDM?
ESPA (Ericsson System Performance Analyzer) is a customized platform for network performance
improvements activities, such as worst cell list, parameter consistency checks but they are all based upon
the data received from the Statistical Data Mart.

8. 45. How is the cell ranking done and what is the parameter name considering if it is Ec or Ec/Io level
that decides which cell that will be selected?
A suitable cell must fulfill the cell selection criteria. The UE bases its evaluation on two
quantities: Squal and Srxlev. The cell selection criteria are fulfilled when Squal > 0 and Srxlev >
0
The cells are ranked according to the R criteria: R(serving) = Qmeas(s) + qHyst(s)
Ranking of GSM neighbors is always made using the measurement quantity CPICH RSCP. For
WCDMA neighbors it is possible to control whether the ranking is made using CPICH RSCP or
CPICH Ec/N0. This is configured using the cell parameter qualMeasQuantity.
46. What happens if the paging is done at the same time as a Location update?
Normally the paging attempt will be sent in the LA that you are registered on. The UE will not listen to the
PICH until the new LA update is done. If the paging does not reach the UE, there will be a global paging in
the end.
Remember: One RNC - one LA, T3212, too short, will create more periodic LA updates, To small LA will
increase the LA update load but decrease the paging load
47. How many RBS per RNC can be connected?
The number of cells that you can define in the RNC is Hardware specific. Depending on the RNC type
(how many subracks, which determines the number of RncModules) there are a certain number of RBSs
recommended. Also the type of the hardware revision itself is a factor to be considered. Here is an
example, I see in one of the CPIs- only to show the relation:
Table 12 Maximum Number of Cells per RNC Module and Subrack Type, R3, R4 and R5 HW
Number of cells Maximum - R5 Maximum - R4 Maximum - R3
per RNC module 192 192 96
per Main Subrack 384 204 192
per Extension Subrack 960 429 300
(Remember, there are 2 RncModules in Main Subrack, and 5 RncModules per every Extension Subrack.
There can be a max of 5 Extension Subracks.)
48. How do the comp mode users affect the admission control?
Admission Control blocks admission requests for a radio link in compressed mode when the current
number of radio links exceeds the parameter compModeAdm. The measurements are done in order to
reduce the interference generated by the users in compressed mode. The Default value is 15 numbers of
radiolinks
49. Is there an alarm for the L1 synchronization failures?
Below you find Cello alarms trigged by Layer 1 synch problems, they are more or less related to
TUB hardware. (more info should be found in CPI). The managed Object is Synchronization for
all of the alarms
Loss of Synch Reference Redundancy = Only one reference available after loss of other
reference(s). This alarm is issued only if there is more than one predefined reference and all other
references are lost except the last one. It is classified as a Minor fault For both TU1/TU2 and
WCDMA CBU nodes
Loss of System Clock = Both system clock planes A and B are not available in the node.

9. Loss of System Clock Redundancy = Alarm is issued if system clock plane A or B is not
available in a redundant node. It is classified as a Warning. For both TU1/TU2 and CBU nodes
Loss of Tracking = Loss of tracking detected for a reference. It is classified as a Major fault For
both TU1/TU2 and CBU nodes
System Clock Quality Degradation=System clock in free running mode or warm up mode. It is
classified as a Critical fault For both TU1/TU2 and CBU nodes
System Clock in Holdover Mode= No synchronization references available. It is classified as a
Major fault For both TU1/TU2 and CBU nodes
Synch Reference Path HW Fault = A fault in the node internal reference distribution path
(board fault, cable, backplane, jitter/wonder). It is classified as a Major fault For both TU1/TU2
and CBU nodes
TuSyncRef = TU Synch Reference Loss of Signal. It could be either a fault on TU1/TU2/CBU
HW or on the synchronization cable. It is classified as a Major fault For both TU1/TU2 and CBU
nodes
50. Are there any counters for AAL2 failures such as in GSM errorseconds?
YES, in the CPI documents from the RNC you will find the ATM port statistics counters.
pmSecondsWithUnexp = Number of error seconds with discarded cells due to protocol errors,
unexpected events (UNEX). I.610: Protocol errors means reception of cells with either a non-
standardized or a non-currently allocated header value.
pmReceivedAtmCells = Number of received ATM cells through the ATM port
pmTransmittedAtmCells = Number of transmitted ATM cells through the ATM port
51. Are there any timers for the "out-of-sync" to get to "in-sync" state again?
The out-of-sync criterion is met when the UL synchronization is lost from the In-Sync state and
the synchronization has not been re-established during a configurable time. In other words when
nOutSyncInd number of consecutive frames is out-of-sync a timer rlFailureT is started and at
expiry the RLS is considered out-of-sync.
The UE enters the "wait-in-sync" box when the criterion for out of sync has been met. The RBS
starts a timer (rlFailureT) in order to wait for the synchronization on Uu to be re-established.
Whenever the RLS becomes synchronized, this timer is stopped. If the RBS does not re-establish
UL synchronization during the period of time given by the timer , the " Out-of-Sync" state is
entered and the RLS Supervision algorithm sends the NBAP message RADIO LINK FAILURE
INDICATION to the SRNC. The RBS, in order to retain synchronization, generates UL-TPC bits
in a pattern that gradually increases the output power.
The connection is considered lost by the RCS when the last RLS, for the connection, has been
out-of-sync for a time given by the parameter dchRcLostT. With other words the box "out-of-
sync" has been entered and we are waiting for this timer to expire.
52. How long time does it takes before the UE in the "in-sync" state when the UE has been in "wait-
for-sync" state?
The timer rlFailureT can be set between 0 - 25,5 seconds and this is a Guard period before
sending RL Failure

10. The timer dchRcLostT can be set between 0 - 10 seconds. The timer is started when all radio
links for a connection are lost. At time-out, the radio connection is considered lost
53. How do I get the RNC id?
I would probably use the Element Manager, open the Object Explorer and right click on
RncFunction, that is under the "Managed Element=1, RncFunction=1". Choose properties for the
RncFunction and you will find the RNC there.
The RNCID is an integer ( number between 0-4095).
54. Should I use the UL or DL UARFCN when defining a WCDMA cell as a neighbor in the GSM
network?
Command RLDEI and RLDEC are used to define cells in BSC.
When defining Utran cells (RLDEI command given with the options UTRAN and EXT), then the
following parameters are defined:
FDDARFCN, SCRCODE, UTRANID and MRSL
In this case, the last field in the UtranId parameter (=345) is the RNCid.
RLDEC:CELL=HLMU1,UTRANID=249-22-234-123-345, FDDARFCN=1,
SCRCODE=32,MRSL=12;
Also note that the FDDARFCN is the DL arfcn in the UMTS cell. (I think. Uplink does not
matter.)
55. What is the difference between block error rate BLER and bit error rate BER?
BER is the percentage of bits with errors divided by the total number of bits that have been
transmitted, received or processed over a given time period. The rate is typically expressed as 10
to the negative power. For example, four erroneous bits out of 100,000 bits transmitted would be
expressed as 4 x 10-5, or the expression 3 x 10-6 would indicate that three bits were in error out
of 1,000,000 transmitted. BER is the digital equivalent to signal-to-noise ratio in an analog
system.
BLER is an abbreviation of BLock Error Rate, but really represents frame error rate. For every
kind of service in UTRAN a BER or BLER threshold, that still satisfies the desired quality, can
be specified
56. What is the parameter ulSirStep resolution?
The resolution is 0, 1 dB.