Professional Documents
Culture Documents
UM TS N e t w or k
Actix Education Services
April 2006
All contents of this document are the property of Actix and are provided for information
purposes only. The information in this document is subject to change without notice.
Actix will not be held liable for technical or editorial omissions made herein, and will not
be held liable for incidental, consequential or other similar damages resulting from the
use of its products.
Class size is limited to ensure that everyone receives extensive one on one
instruction. Participants are given ample opportunity to ask questions
relevant to their particular optimization needs. Upon completing the course,
participants will be able to use what they learned in class to identify and
solve real network problems.
Prerequisites
Familiarity with network infrastructure and operation of the air
interface.
Topics to be covered
Configuring your workspace, including map, cell site, and
parameter configuration in order to display your geographic
area and network cell plan.
Link budget
establishment and
Nominal design
Deployment activities
(site acquisition, civil
works, installation etc)
Ongoing optimization
= Ongoing Optimization of
Growing and mature network
Site Integration
Site integration is performed to test how well Node B is functioning,
hardware (e.g. installation of aerials and cabling), and software
(e.g. correct parameters downloaded and connection with RNC
functions). A drive test can be conducted where scanner and trace
mobile are used to verify if node B is functioning well.
Cluster Integration
Cluster integration is performed to maximize the coverage in the
cluster with the available sites. When performing on an unloaded
network, cluster integration is coverage based. After the initial
tuning (cluster integration), ongoing optimization tasks, such as
Dedicated Drive Test (dedicated mode with SC scanning) will be
performed. The network deployment activities will deal with real
traffic KPI s, and trouble tickets will be raised if necessary.
Ongoing Optimization
The ongoing optimization is performed on the growing and mature
network to assure best quality of the network. Tracking and
defining the optimum KPIs will be the key tasks in fine tuning and
optimizing the network. If a new site or cluster is required, the site
and cluster integration phases will be repeated.
Scanner Thresholds
Uu_Scan_PilotPollutionThreshold (Scanner Pilot Pollution)
Recommended value is -15 dB and value should vary between -10 and
-18 dB. By changing this threshold value, it will directly affect the
Uu_Scan_PilotPollution attribute.
EventCellAddition
EventCellRemoval
EcIo_in_ActiveSet
EcIo_in_MonitoredSet
Scanner Preferences
The WCDMA options within the General Settings group in the Tool
Preferences dialog control the simulated active set feature. When this
feature is selected, Analyzer calculates a UMTS simulated active set from
the scanner data, as it envisages the handset would see it. You can
configure the simulated active set and specify the maximum size of the
simulated active set in the range 1 8. The simulated active set feature was
useful in the early days of WCDMA technology, when logging devices were
not readily available. Now that they are available, you may want to turn off
the feature.
The parameters depicted in the picture are based on the WCDMA events
defined in the 3GPP TR 25.922 V4.1.0 (2001- 09) Radio Resource
Management Strategies specification.
Max. Active Set Size (up to 8) specifies the maximum size of the Active
Set (1-8).
Disable active set simulation.
Select this check box to turn off the active set simulation feature. This will
usually give faster file loading times and will mean that the lines to cells
feature in the map will be based on the measured SC (if it's available)
rather than the simulated active set. This option is off (deselected) by
default.
UE Thresholds
Look at each SC and try to find out what is the best way to optimize
the area. See the training document for a full detailed description on
optimization techniques.
Look at each SC and try to find out what is the best way to optimize
the area. See the training document for a full detailed description on
optimization techniques.
The following data groups are created under the UMTS node:
Downlink Measurements
This group contains Uu interface
measurements reported by the mobile.
Pilot Measurements
This group contains signal
strength measurements for
individual SCs detected within the
logfile.
Event Data
Call events triggered by the current state
of the UMTS mobile. If an event is not
present in the tree, it did not occur in the
file. This group also contains events with
user-definable thresholds, such as
Uu_PilotPollution and
Uu_CoverageLimited.
Statistics Data
This group contains statistics calculated based on UMTS protocol messaging,
including Call Duration and timing components of Call Setup Time.
Vendor Specific
This group contains parameters
unique to a specific type of data
collection equipment.
Other
This group contains scanner
measurements concerning RSSI, Chip
Offset, Carrier Error and the Scan
Code Group.
Nth Best
This node contains ranked
measurements for EcNo, RSCP, SC
and PathLoss. Within each group, the
0 element contains the best
performing data. For example,
CPICH_Scan_EcIo_SortedBy_EcNo_0
gives the strongest EcNo of all SCs
scanned.
Ec/Io
This group contains the interference-
to-chip-energy measurements
organized by various dimensions.
RSCP
This group contains the Received Signal Code Power organized by various
dimensions.
Delay
Find the CPICH Scan Delay Spread for each SC in this group.
Active Set
This group contains simulated Active
Set measurements based on scanner
data and the user-defined WCDMA
settings in the
Tools Preferences dialog.
Monitored Set
This group contains simulated Monitored Set measurements based on
scanner data and the user-defined WCDMA settings in the
Tools Preferences dialog.
Event Data
Events in this group are based on the simulated Active Set and Monitored Set
SCs based on scanner data and user defined thresholds set under WCDMA in
the Tools Preferences dialog.
GPS Data
This group contains mobile longitude, latitude,
distance traveled, and speed.
Message Info
The date and time for the start of the data stream can
be found in this group. This information is useful
when building report templates.
Device Info
This group contains settings for the mobile
device on which data is logged.
Vendor Specific
Vendor Specific measurements may be grouped here or under the UMTS
node. In either case, this group provides measurements specific to the
particular collection device used.
Site Integration
Site integration is performed to test the well functioning of the Node B,
hardware (e.g. installation of aerials and cabling), and software (e.g.
correct parameters downloaded, connection with RNC functioning).
Cluster Integration
Cluster integration is performed to maximize the coverage in the cluster
with the available sites.
Cluster integration is coverage based and as such it is performed in an
unloaded network.
After cluster integration (initial tuning), ongoing optimization tasks will be
performed. These actions are based upon (real) traffic KPI s and eventually
trouble tickets.
If a new site is needed, the steps in site integration will be repeated.
Before you start to integrate a site or/and a cluster, the following roll-out
procedure should be performed and make sure the site and integration
information documentation is available. This section elaborates how a site
and cluster is integrated (from the beginning to the end of roll-out process).
It also defines the integration pre-requisites and how the integration is
triggered or performed.
a) Cluster definition
Cluster definition is performed at the stage of network design and according
to the rules and thresholds coming from the link budget analysis. In general
clusters will contain between 15 and 20 sites.
Node B type
Sector definition
Antenna type per sector
Azimuths and tilts per sector
Initial CPICH power setting
Antenna heights and cable lengths
Additional radio equipment (boosters, MHA, combiners, etc)
Before you start to integrate a site and cluster, the following documentation
should be available on the cluster:
At this point, the design will be pre-optimized for coverage. It is clear that
the design will not completely fulfill the coverage objectives of the cluster if
not all planned sites are ready for integration. These simulations will help
you (RF engineer) to detect trouble areas in the cluster where you should
be focus on during cluster integration.
Site Integration
Drive Tests
Traces are collected from the scanner and the mobiles using any
measurement data collection tool.
2. Call Event
CS Event
PS Event
3 . MHA Malfunction
Conclude if Malfunction is due to high UL Tx Power
1. RF Condition
a) Active Set
By examining the Active Set attributes, you can find out the answers
of the following questions:
Are the correct Scrambling codes implemented on each cell
compared with the data fill values?
Are all intra-site SHO working, i.e. active set updates in both
directions: addition and deletion?
Things to be considered:
Is the CPICH RSCP a normal value?
Should it be better than -70 dBm, close to the site (< 150m)
and outdoor?
Is the CPICH Ec/Io a normal value?
Should it be better than -8 dB, close to the site (< 150m) and
outdoor?
Thing to be considered:
Is the CPICH Ec/Io a normal value?
Should it be better than -8 dB if it is close to the site (< 150m)
and outdoor?
d) UE TX power
By displaying the UE TxPower information on a map, it will quickly and
easily detect any hardware or installation issue on the downlink path
(from Power Amplifier to antenna positioning). The view immediately
shows that there are problems with this site.
Thing to be considered:
Is the UE Tx Power a normal value?
Should it be less than 0 dBm if it is close to the site (< 150m)
and outdoor.
If issues occur, it is possibly come from the Node B (hardware) or from the
CS core side.
b) PS throughput
Do we have a normal throughput under good radio conditions and low
load? Is it better than 90% of maximum RAB (currently 90% of 384 kbps
is 350 kbps)?
Any throughput that is lower than this may come from issues on mobile /
laptop configuration, or issues on the PS side.
c) Crossed feeders
A typical problem that can be, and must be detected at this stage is the
crossedfeeder problem.
Formulae:
For most measurement points over the service area of the cell, the
MHA functionality needs to be checked. This criteria can be checked
with the Analyzer tool.
The map below shows you the result of UE TxPower = 0 based on the
criteria mentioned in the previous page. This means there is no problem.
If all these parameters are OK, the site is considered as verified and can be
included in the cluster optimization phase. Followed by that, a site integration
report should be generated. The report should contain the following
information:
Procedure
As mentioned, it is necessary for the person defining the drive test routes to
carry this task out in conjunction with viewing various simulation plots from
the radio-planning tool.
Drive Test 1:
Unloaded scan test
& Dedicated CS
There are four important criteria for best practice while performing a cluster
integration drive test:
Criteria 1: Optimizing UL Coverage
Criteria 2: Optimizing DL Coverage
Criteria 3: Avoiding Pilot Pollution
Criteria 4: Avoiding Cell Overlap
The first two criteria are the pilot coverage criteria including slow fading
losses. They are drawn from the link budget calculation. Bear in mind that
these pilot coverage criteria give the uplink coverage indication for the
limiting service for the morphology only when CPICH power settings are set
to its default values:
30 dBm at antenna entrance
The third criteria is taken from the pilot pollution criteria and defined for
3G radio design.
The measurement conditions for pilot pollution and cell overlap cannot be
taken immediately from the measurement but can be calculated using Actix
Software. The plots and queries that need to be visualized, and examples of
the reports that can be drawn from a drivetest, can be generated
automatically (see the following pages).
In this stage, apart from fulfilling the above mentioned criterion as much as
possible, we should try to minimize interference induced or caused in
neighbour cells. For this purpose we will visualize the CPICH RSCP per SC.
From this plot we will detect any unnecessary coverage outside the area
where the SC is dominant. Action should be undertaken to avoid
overshooting and unnecessary leaking into neighbour cells.
The map above is a combination of different drive tests in the same cluster.
The attribute CPICH_Scan_RSCP_Sortedby_EcIo_0 is dragged and
dropped different times on the map view.
Best practice:
The better solution is to create a super stream of all files from one cluster
and perform the analysis on the super stream.
In this map, we only have problems of UL coverage outside the cluster and in
the centre of the 3 sites. The next necessary step is to find out where we
have the dominant servers. We can do this by displaying the
CPICH_Scan_SC_Sortedby_EcIo_0 attribute on the map to find out the
dominance areas.
Not much problem for the example above, only some degraded downlink
quality at the edge of the cluster. This is due to edge of coverage.
Number of
[Best CPICH Ec/Io - CPICH Ec/Io 2 x SH O_ w in dow ] 4
All measurement points fulfilling the criterion above suffer from pilot pollution
and optimization changes need to be undertaken. The possible solution for
pilot pollution can be:
Up tilt the antenna providing the best server in the area in order to
improve the CPICH RSCP
Down tilt the antennas from interfering cells and as such reduce the
RSSI.
Change azimuth from antennas in order to create a dominant server in
the polluted area.
In the following graph you can detect an area of pilot pollution. The next step
in this case would be to detect which of the surrounding sites is covering the
area and to try to limit the amount of servers through up- and down tilting.
That comes down to creating 1 or 2 dominant servers.
In the example above, there is only some coverage overlap on area were the
sites are built very close to each other. By applying the appropriate tilt and
azimuth, you can avoid this problem.
Value
Description
Note: The scanner reports SC numbers, so Actix RVS selects the closest cell to the drive
1
Example of angle to site threshold for validation of SC 203, 302 and 302
This is repeated for all points in the scanned drivetest route, creating an
array of SC s at each point, sorted by their EcIo value, which satisfy the
selection criteria and are not currently defined as a neighbour of the
Nth_Best_0 cell at that time.
If the Only use Nth Best cell option is disabled, not only the Nth_Best cell will
be considered. Using the principle that if cell A and cell B are within 5dB, and
cell A and cell C are within 5dB, the relationship between cell B and cell C
should be analysed too. This obviously increases where processing is needed
at each point, and is recommended for neighbour list optimisation of more
mature networks.
Once the final list of suggested Missing Neighbours has been compiled, the
results can be viewed in two ways: through the Accelerated Network
Rollout Analysis pack report (Neighbour List Recommendations), and
also by visualising them on the map/chart/table.
SC 200 is not already in the adjacency list for SC 110, all criteria have been
met for this cell, so it is suggested as a Missing Neighbour.
SC 112 was scanned enough times to recommend to be kept in the
adjacency list.
SC 113 (at the same site as SC 112, 3.5Km away from SC 110) was only
scanned 5 times, so it has been recommended to be removed.
NOTE:
It is important to drive enough routes and collect enough data to ensure
these cell suggestions are statistically valid.
The lists are sorted by signal strength and contain the SC values of the cells
in the list at each point in the scanned drivetest. The strongest Missing
Neighbour (Missing_Neighbour_0) should be analysed first, as it could
potentially be the strongest pollution source at that time.
Drag the parameter onto the map and open the Top 10 Scan Measurements
stateform (optionally dock it to under the Workspace Explorer). The legend of
the map gives you the list of SCs that were the strongest Missing Neighbour
at any point in the drive. The most frequent SC should be targeted first, and
by selecting any point in the map, the stateform will synchronise to show the
top 10 scanned measurements giving the Nth_Best SC at the top of the list2.
A decision needs to be made whether to add this suggested Missing
Neighbour SC into the adjacency list of the Nth_Best SC.
2
In the case of repeated SC values, the closest cell with a matching SC to the Nth_Best_0 cell
will be selected.
Once all the strongest Missing Neighbours have been analysed, the next
strongest signal should be analysed. Following this process with ensure that
the most important Missing Neighbours are analysed first.
This requires the scanner and UE traces to be collected at the same time,
and for the resulting collection files to be superstreamed together (and
correcting any time offset between the collection devices). See the online
Help for instructions on superstreaming using Time Offsets. Once the files
have been combined, parameters such as the UTRA_UE_CarrierRSSI and
the Uu_CallDropped event can be dragged onto the map. By opening the
UE Missing Neighbours stateform for the superstream and synchronising it
with dropped call, the top 10 scanned measurements can be visually
compared to the Active and Monitored sets for the UE at the time.
This allows the engineer to understand whether the UE had dropped a call
due to a missing neighbour not being defined in the cell s adjacency list, or
whether it was a handset problem, resulting in a neighbour that had already
been defined not being added to the Monitored Set, and therefore never
being able to be added to the Active Set.
When the drop call occurs, a specific function looks for the next
origination and gets the value of the new SC in the active set. If the
new SC is different from the SC s in the active set before the call
dropped, the function looks for the last neighbour list before the call
dropped. If that same neighbour list does not contain the new SC, it is
a possible missing neighbour.
After the RRC connection procedure the algorithm, considers the first
Measurement Control message to be the Setup and builds up an
internal array of Scrambling Code with their corresponding index
numbers (from attributes
Uu_RRC_NewIntraFreqCell_intraFreqCellID and
Uu_RRC_PrimaryCPICH_Info_primaryScramblingCode). This
information is then used to populate attributes Uu_UE_NbrList and
Uu_UE_NbrListCount (i.e. the number of SCs in the array).
Note:
If there are any missing Measurement Control messages, this
neighbour list will become out of sync with the true neighbour list
being measured by the UE.
In the figure above, Cell A is the best server by CPICH Ec/Io. Cells B and C
are within a user-specified threshold of Cell A's are Ec/Io, and so are counted
as potential neighbors of A. Cell D is not within the required threshold and
so is not counted as a prospective neighbor, nor is Cell E which did not have
a measurable signal contribution at this point in the drive test.
A B C D
A N/A 10 2 15
B 10 N/A 40 0
C 2 40 N/A 12
D 15 0 12 N/A
SU F_DL
50
F_DL cov e r ag e p e r ce n t ag e
40
3 3 .0
2 6 .7
30
2 3 .1
H6 5 V 6 T0
H6 5 V 6 T2
1 6 .7
1 6 .5
1 6 .5
20 H6 5 V 6 T4
1 2 .2
1 1 .9
1 1 .0
9 .8
9 .6
8 .9
8 .2
7 .9
7 .3
7 .2
10
6 .7
6 .6
6 .1
6 .0
5 .7
5 .1
4 .6
4 .5
4 .3
4 .0
3 .5
3 .4
3 .1
2 .6
2 .6
2 .4
2 .0
0
6
8
4
2
2
2
0,
0,
1,
1,
1,
1,
0,
1,
0,
>
=
a)
=
=
=
=
<
=
tr
a)
<
<
<
<
<
<
<
<
<
n
a)
a)
a)
a)
a)
a)
a)
a)
a)
tr
ii
tr
tr
tr
tr
tr
tr
tr
tr
tr
n
ii
/
n
n
n
n
n
r
ii
ii
ii
ii
ii
ii
ii
ii
ii
te
/
r
/
/
/
/
/
in
te
r
r
r
r
r
te
te
te
te
te
te
te
te
te
(i
in
L
in
in
in
in
in
in
in
in
(i
FD
i
L
(i
(i
(i
(i
(i
(i
(i
(i
(i
FD
L
L
L
L
L
e
FD
FD
FD
FD
FD
FD
FD
FD
FD
g
ra
<
2<
0<
ve
4<
<
<
<
<
<
<
8
1,
0,
6
1
Co
0,
e
0,
0,
1,
1,
1,
e
e
g
g
ra
e
g
ra
ra
g
g
ra
ve
ra
ra
ra
ra
ra
ra
ve
ve
ve
ve
Co
ve
ve
ve
ve
ve
Co
Co
Co
Co
Co
Co
Co
Co
Co
The graph above shows the F factor on a map and indicates areas
where we have too much interference. In this example, F factor is
smaller than 2 covers 95% of the area.
Note: F factor will be equal to 2 when the mobile station is at the cell edge.
4 6.7541x
y = 0.0023e
4
3
3
2 F
F
2 Expon. (F)
1
1
0
0.40 0.60 0.80 1.00 1.20
Fraction DL PL
8 0
7
-5
6
5 -10
F factor
EcIo
4
3 -15
2
-20
1
0 -25
-88.5
-91.5
-94.5
-97.5
-100.5
-103.5
-106.5
-109.5
-112.5
-115.5
-118.5
-121.5
-124.5
-127.5
-130.5
-133.5
-136.5
-139.5
-142.5
-145.5
-148.5
-151.5
-154.5
-157.5
-160.5
-163.5
-166.5
-169.5
-172.5
-175.5
-178.5
Path Loss (dB) in 3dB steps
F Factor Report
Objective
The objective of this example is to find out bad pilot coverage areas within
the network. We will then determine whether the problem is localized, and
the effect that the problem is having on the network quality.
Attributes
Uu_ActiveSet_RSCP_0
Uu_CallDropped
Uu_IncomingCallSetupFail
Uu_OutgoingCallSetupFail
Uu_Trch_DownlinkBlerAgg
CPICH_AllSets_UE_RSCP_For_SC
Stateforms
UMTS UE Active Set + Monitor Set
Queries
Poor Mobile Receive Power, or
Low Mobile Receive Power
(Condition: Uu_ActiveSet_RSCP_0 < -95dBm)
Screen Layout
UMTS Coverage Analysis
Flirst click on the stream name, then click on
Layouts UMTS UMTS Coverage Analysis
In the example above, Cells A, B and C are part of the Active Set, as
determined by the Simulated Active Set module. Cell D has a CPICH Ec/Io
within a user-specified pollution threshold of the Active Set s best server
Ec/Io, and so is counted as a contributer to pilot pollution at this point in the
drive test. Cell E has a CPICH Ec/Io that is not within this threshold and so is
not a pollution source.
Sector ID Pollution
Count
A 0
B 150
C 45
D 12
As shown below, the Pilot Pollution Analysis Report indicates the worst
interferers sorted by Scrambling Code:
Drive Test 2:
Dedicated Mode with
SC Scanning
UE 1
o video call (voice call if not possible) mobile originating
o 90 seconds call
o 10 seconds guard before new call is set up
UE 2
o Video call mobile terminating
Apart from the coverage criteria, the dropped calls will be analyzed.
The cluster integration is successful when no dropped calls are due
to radio quality. Note that this is only applicable when the cluster is
fully built. If radio drops are a consequence of a missing site (and the
site is in the final design), they cannot be a blocking point for cluster
integration at this point.
If a call drops the messaging before the drop should be checked and
compared with the normal messaging sequences.
b) DL BLER
c) RRC Messages
The other types of non- radio related drops are due to the following
problems:
Mobile Issue
Core Network Issue
1. Missing neighbour
See Dropped Call Analysis due to Missing Neighbours in pg 67.
In this case there is no other way to optimize this area than adding a
new site, as no other antenna change will improve the situation. Else
low RSCP can be improve by up tilt, and low Ec/Io by giving only one
sector dominant in the area where the drop occurs.
3. UE TX power
No example from pre-launch. This will hardly ever happen since the
measurements are taken out door, while our design is done for indoor
coverage. The only possible occurrence of this problem is where we
drive outside 3G coverage areas. This will only happen during the exit
criterion drive test.
The reason of call drop in the example above is not very clear, but the BLER
goes up to 100% and the serving cells are not the obvious ones. A downlink
power limitation is probably the reason for this.
1. Mobile Issue
CM service abort, pegged as a drop, but coming from a cancellation on
mobile side
Objective
The objective of this example is to analyze each dropped call (10 seconds
before and 5 seconds after) and report a possible diagnosis.
Attributes
Uu_ActiveSet_SC_0
Uu_IncomingCallOK
Uu_OutgoingCallOK
Uu_CallDropped
CPICH_AllSets_UE_RSCP_For_SC
Stateform
UMTS UE Active + Monitor Set
Queries
UMTS Call Statistics query shows which File/Sector/Cell/Call ID that
contains the drop call. Which one should we look at?
Dropped Call Analysis query shows event and what causes the drop
2 Drop Call
RSSI
BLER
Exam and further investigate the result (i.e: Check out which File
3
contains the drop call).
Close Statistic Explorer and open the problematic file.
4
Superstream them if there are more than 1 file.
Display Uu_ActiveSet_SC_0, Uu_IncomingCallOK,
5 Uu_OutgoingCallOK, and Uu_CallDropped on the map. Display
the relevant attributes on tables and chart if necessary.
6 Zoom in on the Call Dropped event.
Display UMTS UE Active + Monitored Set stateform.
7
Note: Make sure the stateform is synchronized with the map.
Objective
The objective of this example is to investigate the call setup failure based on
the layer 3 messaging for call setup procedures.
Attributes
Uu_IncomingCallSetupFail
Uu_OutgoingCallSetupFail
Uu_ActiveSet_SC_0
Uu_ActiveSet_EcNo_0
UE_TxPow
Stateform
N/A
Queries
UMTS Call Setup Statistic, or
UMTS Call Setup Failure Analysis
Application Packs
UMTS Call Setup Analysis
Drive tests executed for the exit criterion need to fulfil different
requirements than those performed for the first 2 drive tests in the
FN8c procedure:
Drive test 1:
Within 3G coverage, focus on CR (setup, maintain and clear)
Metrics
o UE1 - DL Throughput (average), for successful calls
o DL CR (call success rate, = Call setup, maintained and
cleared)
o UE2 - CR (call success rate, = Call setup, maintained and
cleared)
Targets
Drive test 2
o UE 1: CS voice short call: 10 sec call and release with 5
sec guard
o UE 2: PS file download: 10 sec call and release with 5 sec
guard
o The following statistics are taken from the drive tests:
CS call setup success rate
PS call setup success rate
In Actix Software, you can open the pre-defined report UMTS Cluster
Acceptance App Pack (Application Pack) from Analysis UMTS
Cluster Acceptance App Pack to obtain the following information:
When preparing the optimization changes of the new Node B and the
surrounding cells, try to achieve the following:
Cell Reselection
In idle mode, the cell reselection can be detected through the decoding
of a new BCCH. In cell PCH and cell FACH state, the reselection can be
noticed by an RRC cell update message. The transitions from those
states to idle mode and back can be detected by the following RRC
messages:
Where:
Parameter Description
Squal Cell Selection quality value (dB)
Applicable only for FDD cells.
Srxlev Cell Selection RX level value (dB)
Qqualmeas Measured cell quality value. The quality of the
received signal expressed in CPICH Ec/N0 (dB)
for FDD cells. CPICH Ec/N0 shall be averaged.
Applicable only for FDD cells.
Qrxlevmeas Measured cell RX level value. This is received
signal, CPICH RSCP for FDD cells (dBm) and P-
CCPCH RSCP for TDD cells (dBm).
Qqualmin Minimum required quality level in the cell (dB).
Applicable only for FDD cells.
Qrxlevmin Minimum required RX level in the cell (dBm)
Pcompensation max(UE_TXPWR_MAX_RACH P_MAX, 0) (dB)
UE_TXPWR_MAX_RA_CH Maximum TX power level an UE may use when
accessing the cell on RACH (read in system
information) (dBm)
P_MAX Maximum RF output power of the UE (dBm)
(Re-) Selected cell is a suitable cell (fulfils the S criterion) and is the best
ranked cell (has the highest R). The UE shall however reselect the new cell,
only if the following conditions are met:
The new cell is better ranked than the serving cell during a time
interval Treselection
More than 1 second has elapsed since the UE has camped on the
current serving cell
Measurement Rules
R s = Qmeas,s + Qhysts
R n = Qmeas,n Qoffsets,n
Handover
While moving from one cell to another, the best server conditions change and
there is a need to redirect the mobile to a new serving base station. Unlike in
GSM, WCDMA takes advantage of the time where the received signal
strength of different pilot channels is within a certain window.
During this time the mobile is connected to different serving base stations,
this is called soft handover (softer if the serving cells are from the same
Node B). In the case of soft handover the RNC performs selective combining
on all the active links. This gives a typical gain of 4dB (2 links) or 5 dB (3
links), depending on the fading conditions. In the case of softer handover,
the signals are rake processed in the Node B, and the gain is slightly higher.
Active Set
The cells in the active set form a soft handover connection to the Ue
Monitored Set
Remaining Set
Is the set of all the other scrambling codes in use, which are not in the
active or the monitored set
This name is not frequently used, only for planning purposes.
You can obtain the Intra-Freq handover information by displaying the UMTS
Handover Analysis (Intra Freq) screen layout from
Layouts UMTS UMTS Handover Analysis (Intra Freq)
These are the basic, standardised handover events and they are UE triggered
event. As for other, more complicated handover algorithms will be vendor
dependant and you can make use of the available measurement report data
to obtain the information you need.
They are always periodic and the way of using the measurements in
handover algorithms is not part of the standard.
The first group of measurements can be used by the RNC to trigger inter-
RNC or system handover. The second group is used to adjust the downlink
DPCH air interface timing, when the difference ion time between the UE
uplink DPCCH/DPDCH frame transmission and the first significant path of the
downlink DPCH frame from a measured active set cell becomes too large.
Note:
This attribute is only incremented if the RRC event Diagram is in the RRC
Connected State.
CellChangeOrderfromUTRAN
Uu_RRC_MsgType == CellChangeOrderfromUTRAN
And then
GSM_Um_Msg_Type == RR Channel Request
OR
GSM_Um_Msg_Type == RR Immediate Assignment
OR
GSM_Um_Msg_Type == RR Immediate Assignment Extended
Note:
One of the above must be received before the expiry of the timer
Uu_t309_wait_timer
CellChangeOrderfromUTRAN
Uu_RRC_MsgType == CellChangeOrderfromUTRAN
And then
Uu_RRC_MsgType == CellChangeOrderFromUTRANFailure
OR
Any UMTS BCCH messages.
OR
Timer Expiry, which is configured by threshold
Uu_T309_Wait_Timer
OR
Uu_RRC_MsgType == RRC Connection Request
Note:
If a call is completed in GSM mode (after the handover from UTRAN
to GSM), the call event will appear in the GSM section of the
Workspace Explorer window.
Uu_IRAT_Reselection3G2G, Uu_IRAT_Reselection2G3G
(IRAT Reselection)
If a device is determined to be idle, and system information from the
other technology is seen then there will be an event to indicate there has
been a technology change.
Reports showing the percentage of handoff state for each sector and for the
total drive test may then be calculated.
Creating Reports
Objective
The objective of this exercise is to create a report template that will return
KPIs from one file. Create a report template from existing parameters and
queries which can be run on any file. This will return the total number of
dropped calls, a histogram of the handoff state, the average call setup time,
mean (linear) RSCP for the strongest SC in the Active Set and total call
duration for all calls in the whole file.
Procedure
Step Action
1 Choose and load a log file.
2 Based on the requirement, this report can be separated into
existing KPIs and new KPIs (new queries).
Existing KPIs:
Average call setup time
(Uu_TimeBetweenRRC_REQandCallStart)
Total Dropped Call (Uu_CallDropped)
New KPIs:
HandOff State Histogram
Mean(linear) RSCP from the strongest Active Set SC
Total Call duration for the whole file
The Handoff State is an attribute (Dedicated Radio Link
Uu_UE_HandOffState) that you can drag and drop to a
workbook to obtain an automatic histogram view of data.
Somehow, we are trying to create a generic report template to be
run on other files. To use the automatic view, the legends will be
controlled through the format group of the parameter and may
filter out ranges not found in the file. For this reason, we need to
force the number of ranges used in the histogram through a
query.
3 Display the call setup time parameter
Uu_TimeBetweenRRC_REQandCallStart (from the
UMTS Statistics Data data group) on a workbook.
Notice how all three views from these two attributes have been added
to the workbook (Series, Histogram and S.tatistic Formatted Data
tabs).
5 Save your workbook
6 To create new query, goto Analysis Manager (ctrl- A)
7 Create a histogram query using the Uu_UE_HandoffState
parameter, and creating discrete values from 0 (inclusive) to 6
(inclusive).
8 Create a crosstab query with FileName from the Attribute
Picker( ) as the dimension, and add 2 new statistics for:
Mean (linear) of Uu_ActiveSet_RSCP[0] formatted as
WCDMA RSCP, and
Sum of Uu_CallDuration formatted as Time.
9 Save your query into the workspace and check the results are
accurate.
10 Open the report template through the Workbook Open
Workbook/Report menu option, and choose to run it on your log
file.
11 Right-click on Queries folder, find your new query and display it on
the existing workbook. It will be added to a new sheet called
Crosstab Formatted Data.
12 These tabs will contain the results from whatever file you run the
report template on. Open Sheet 1 and create your KPI statistics
here as follows (see next page):
From Crosstab
results
Step Action
13 Now go back into the all other sheets and delete the raw data
from row 2 downwards. This cleans the report template so that it
can be run on any other file, of varying size.
14 Save your report template.
15 Open another log file and run the report template on this file as
you did in step 10. Compare the results.
Key
Word
Search
Result
Selected
Attribute
Highlighted Item in the Workspace and the Corresponding Entry in Attribute Help
MyActix (Extranet)
If you would like to obtain the latest information of the software release,
problem reporting, support issues, access to our self-study modules or
Knowledge Base, please register yourself at http://www.myActix.com
(1)
At least one of those messages (RRC Connection Request, Setup or
Complete) needs to be present to initiate the call setup
(*)
The messages with the symbol star are usually present but not
mandatory
(1)
At least one of those messages (RRC Connection Request, Setup or
Complete) needs to be present to initiate the call setup
(*)
The messages with the symbol star are usually present but not
mandatory
Uu_CallCompleted When in Call (Outgoing Call Ok or Incoming Call Ok), you get one
of the following messages:
*GSM_Um_Msg_Type == CC Disconnect or
*GSM_Um_Msg_Type == CC Release Complete or
*GSM_Um_Msg_Type == CC Release
And any of the above messages with a normal cause for ending
the call (CauseCodeCC is equal or less than 31)
Uu_CallDropped When in Call (Outgoing Call Ok or Incoming Call Ok), you get any
of the following options:
Any BCCH Message or
Uu_RRC_MsgType == RRC Connection Release AND Release
Cause is not Normal or
One of the following messages:
*(GSM_Um_Msg_Type == CC Disconnect) OR
*(GSM_Um_Msg_Type == CC Release Complete) OR
*(GSM_Um_Msg_Type == CC Release)
*AND any of the above messages with NOT a normal cause for
ending the call (CauseCodeCC is greater than 31)
All Coverage Events which make use of thresholds may be customized by the
user in the Tools Display Thresholds menu.
Uu_TooManyServers 4 or more pilots are detected within X dB of the server, threshold X is set
by the user as Uu_TooManyServersThreshold
Uu_MissingNeighbor SC in Active Set after drop is not in Active Set before drop and
SC in Active Set after drop is not in Neighbor List before drop