Beruflich Dokumente
Kultur Dokumente
LTE/IRC/APP/032644
V4.2 / EN
Standard
04/JUL/2011
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks
are the property of their respective owners
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for
inaccuracies contained herein.
Copyright 2010 Alcatel-Lucent. All rights reserved.
Contains proprietary/trade secret information which is the property of Alcatel-Lucent and must not be
made available to, or copied or used by anyone outside Alcatel-Lucent without its written authorization
Not to be used or disclosed except in accordance with applicable agreements.
without notice. Alcatel-Lucent assumes no responsibility for errors that might appear in t.All other brand and
product names are trademarks or regist
ered trademarks of their respective holders.
LTE/IRC/APP/032644
Page 1/61
PUBLICATION HISTORY
18/FEB/2010
Issue 01.01 / EN, draft release
Denis Camboulives
01/MAR/2010
Issue 02.01 / EN, Final release
Denis Camboulives
03/AUG/2010
Issue 2.2 / EN,
Quality update
Denis Camboulives
29/OCT/2010
Issue 3.0 / EN,
Indoor measurement
Neighboring list
Denis Camboulives
10/MAR/2011
Issue 4.0 / EN,
Gladiator post processing
Denis Camboulives
07/APR/2011
Issue V4.1 / EN,
Neighbor list creation with Gladiator
Denis Camboulives
V4.2 / EN
Standard
04/JUL/2011
Page 2/61
V4.2 / EN
Standard
04/JUL/2011
Page 3/61
CONTENTS
1.
2.
INTRODUCTION ............................................................................................................................6
1.1.
OBJECT ............................................................................................................................6
1.2.
1.3.
1.4.
OBJET ...............................................................................................................................9
2.2.
2.3.
2.3.1
2.3.2
2.3.3
3.
4.
5.
6.
7.
OBJET .............................................................................................................................12
3.2.
3.3.
3.3.1
3.3.2
3.4.
3.4.1
3.4.2
prerequesite ..................................................................................................................18
Recording datas ............................................................................................................18
OBJET .............................................................................................................................19
4.2.
4.3.
QUALITY ......................................................................................................................................23
5.1.
5.2.
6.2.
POST PROCESSING...................................................................................................................27
7.1.
7.2.
EDAT.............................................................................................................................27
7.3.
GLADIATOR ....................................................................................................................32
7.3.1
LTE/IRC/APP/032644
V4.2 / EN
Standard
04/JUL/2011
Page 4/61
REPORTING ................................................................................................................................58
8.1.
V4.2 / EN
Standard
04/JUL/2011
Page 5/61
1.
INTRODUCTION
Operator
are
installing
new
generation network named LTE in
deployment phase with AlcatelLucent
Before starting the field acceptance
activities it is very important to
optimize the coverage efficiency in
order to clear all issues related to
radio environment.
1.1.
OBJECT
The object of this document is to explain step by step the RF optimization phases from
the site verification till the delivery of reporting to the operator
This part has to be done before any other field system performance activities as soon
as the cluster has been defined by the customer.
In order to highlight the problematic zones through the deployment area, and to
compare the coverage with the RNP predictions, a site verification followed by a
coverage measurement will have to be executed.
After the delivery of the reporting, a tilt optimization should be requested by RNP
engineer, and the measurement validation will have to be done again.
V4.2 / EN
Standard
04/JUL/2011
Page 6/61
1.2.
RF optimization is necessary after the first design to optimize the radio network and to
adapt it to the real field. Indeed when the RF design is realized, it uses standard
characteristics adapted to general environments often presented inside the digital map
as clutters. These clutters are defined by the averaged kind of build, spacing,
vegetation and outlines.
Clutters of environment are defined as macrostructures and can have punctually some
variation of build as masks or can be crossed by highways or railways. In this case,
the real behaviour of the waves could be locally modified. Sometimes some troubles
could also appear due to ground level variation (hilly areas). All of this modify the
propagation and can create interferences, wave guides or blocked areas.
On LTE network number of cells available in same place could have also significant
impact on cell efficiency. The more the number of neighbouring cells seen 10 dB
under the best server is ,the more the risk of interferences increase.
To limit the interferences impact due to others sites or to create more homogenous
design in term of serving cell coverage, RF optimization must be realized after the
deployment.
After the control of site status (all tested sites must be up and well done
parameterized), they must all loaded with 100% OCNS.
Drive test tour is organized around them, using LTE receiver and GPS for real
geopositioning. LTE radio data are collected on road and formatted to give view of
results. The main receiver advantage is to be independent of the network. That allows
to collect everything seen inside the Drive test area. The main results of this activity
are, area coverage map, best server map and the status of received cells for each
measurements point.
These main results of this field activity should be used to modify the tilt of antennas
used or sometime to optimize one cell azimuth to obtain the wanted coverage and a
relative homogeneity between all the cells coverage (no preponderance of one cell to
the detriment of the others). In parallel this is used to limit impact of neighbouring cells
seen inside specific cell coverage and to limit faraway interferences due to site or cell
positioning.
V4.2 / EN
Standard
04/JUL/2011
Page 7/61
1.3.
Site verification
Measurement
campaign
Post processing
and analysis
Tilt or
azimuth
changes
requeste
No d?
Yes
1.4.
V4.2 / EN
Standard
04/JUL/2011
Page 8/61
2.
SITE VERIFICATION
2.1.
OBJET
The aim of this part is to control that the given information are correct, because if there
is some gap between the real information and the one used for the prediction (as the
antenna height from ground, the implemented tilts, azimuths, or even the coordinates
of site) the prediction realized before will be wrong and the systems test could have
more problem than expected.
The other goal is also to check the mask present in the immediate environment of the
site, which could block the LTE signal. This part could allow Alcatel Lucent to
understand why the coverage is strongly decreasing in some parts of the driven roads.
In consequence the RF Optimisation has to be done before any system tests.
The following will present the needed tools and the way to use it.
2.2.
- Binocular
- Compass
- Digital camera
- Laser meter (or decameter)
- GPS
V4.2 / EN
Standard
04/JUL/2011
Page 9/61
2.3.
ON SITE JOB
V4.2 / EN
Standard
04/JUL/2011
Page 10/61
V4.2 / EN
Standard
04/JUL/2011
Page 11/61
3.
3.1.
OBJET
The RF Channel measurement is done to allow the trial team to start the acceptances
test in a optimized network.
A report has to be done, after these measurements, it must contain results presented
as followed:
Channel Power
Best cell ID
RSRP
RSRQ
RS-CINR
Serving cells within 10dB
Neighboring list
After results formatting and processing, the data must be given to RF planner
engineer, who optimize the RNP to reduce any problem of coverage, overlap and
interferences due to site installation and parameters.
At least, the RNP engineer will provide to the costumer a list of tilts to implement on
field.
V4.2 / EN
Standard
04/JUL/2011
Page 12/61
3.2.
V4.2 / EN
Standard
04/JUL/2011
Page 13/61
3.3.
NIXT OVERVIEW
NIXT (E6474A) is the software platform developed by Agilent to control the receivers
and to log measurement on the driven roads.
This part of the document is a short presentation of the configuration setup
V4.2 / EN
Standard
04/JUL/2011
Page 14/61
Project manager
File
After selecting the Project manager, and creating a new project, the field team must
install the correct device, by using the device wizard.
V4.2 / EN
Standard
04/JUL/2011
Page 15/61
Once the device is detected and installed, the operator has to select the measurement
needed (add measurement / LTE Channel Analyzer) and must configure the channel
to measure as shown below.
V4.2 / EN
Standard
04/JUL/2011
Page 16/61
Bar chart
Grid
Measurement selection
drag and drop the measurement
you want to see
V4.2 / EN
Standard
04/JUL/2011
Page 17/61
3.4.
3.4.1 PREREQUESITE
Before starting the OCNS must be declared on the system with a 100% value, to have
a full loaded signal, and the full network must be working.
No other activities on the tested area must be done during the RF measurement
campaign
Once the configuration is done, the measuring team has to start to collect data
The car speed must be as constant as possible and not to high
A maximum number of roads of the cluster must be measured, and will have to be
drive again if some tilts modifications are requested after the post processing.
To ensure that the same roads will be measured, we strongly recommend to keep
traces of the driven roads made during the first pass.
V4.2 / EN
Standard
04/JUL/2011
Page 18/61
4.
4.1.
OBJET
The RF Channel indoor measurement is done to check the coverage of the LTE
Network inside a specific building, where DAS system had been deployed
A report has to be done, after these measurements, it must contain results presented
as followed:
Channel Power
Best cell ID
RSRP
RSRQ
RS-CINR
Serving cells within 10dB
Neighboring list
After results formatting and processing, the data must be given to RF planner
engineer, who optimize the RNP to reduce any problem of coverage, overlap and
interferences due to site installation and parameters.
At least, the RNP engineer will confirm to the costumer if the antenna position are
correct regarding the expectation or if this position has to be modified
4.2.
NIXT SETTINGS
The way to set the software is similar to outdoor. The main difference will be how to
log the data. A touch Read laptop is needed to be able to work in indoor environment.
First of all, create a new workspace for the map.
V4.2 / EN
Standard
04/JUL/2011
Page 19/61
Open map
file
As soon as the map is opened, on the properties set the Indoor Mapping Mode to Yes.
By doing this the GPS will be disable, that why it is Mandatory to synchronise the
system with the GPS before doing that.
V4.2 / EN
Standard
04/JUL/2011
Page 20/61
4.3.
Anchor
V4.2 / EN
Standard
04/JUL/2011
Page 21/61
Then when the log is started , click on the start position with the arrow and start to
walk with a constant speed, as soon as you reach a reference point (corner, door)
click on the current position on the map, and the system will automatically place the
logged point at the correct position
arrow
V4.2 / EN
Standard
04/JUL/2011
Page 22/61
5.
QUALITY
5.1.
SCANNER VERIFICATION
Before starting any campaign of measurement, the receiver calibration date must be
checked, and also the good behavior of the system
5.2.
MEASUREMENT QUALITY
Since the Soft ware version 15.0 new fields appears on the measurement file
R0 RSRP,R1 RSRP, R0 RSCINR.,
The R0 branch is the one use to decode, and for the Synchronisation , this field is the
one used to do the RF optimization.
Some Ghost Cell Id can appear during those measurements , before post processing
the data , a statistic count on CELL ID must be done to delete the Ghost.
CELL ID with a non significant CELL ID number must be considered as trash
V4.2 / EN
Standard
04/JUL/2011
Page 23/61
6.
DATA EXPORT
To be able to post process the Data to set of export mut be provided to the post
processing team
Scanner data (*.aod, *.pgs ,*.aox, *.ecf, and *.axe files)
CSV file
6.1.
Export Project
Then select the measurement to export and choose where you want to copy it
This measurement are readable by using the nitx software , Edat or gladiator
V4.2 / EN
Standard
04/JUL/2011
Page 24/61
6.2.
V4.2 / EN
Standard
04/JUL/2011
Page 25/61
By selecting Save, the operator is able to save the export plan. By saving the export
plan, it can be given to all technical field team, in order to get the same level of
information for all parts of measurement campaign.
Otherwise export to file.
Be careful: The CSV files must be duplicated before any modification or analysis. The
duplicated files must be stored in directory named RAW DATA these are the references of
real measurements. The second set should be used to perform processing and analysis. If
any doubt about the processing appears, we need to go back on cloned raw data to redo
the processing and possibly perform debugging..
V4.2 / EN
Standard
04/JUL/2011
Page 26/61
7.
POST PROCESSING
7.1.
TOOLS REQUIRED
A system as MapInfo is requested and the post processing team could have to use or
develop tools as Excel Macro to be able to have the requested information(by using
the CSV export.
Or they can use internal software as EDAT, or external one as Gladiator
7.2.
EDAT
EDAT is a post processing tool developed by ALU, used to do the post processing of
UE and scanner measurement .
V4.2 / EN
Standard
04/JUL/2011
Page 27/61
Import data
Selection of metrics
V4.2 / EN
Standard
04/JUL/2011
Page 28/61
Best Cell ID
Best RSRP
V4.2 / EN
Standard
04/JUL/2011
Page 29/61
Grid export
V4.2 / EN
Standard
04/JUL/2011
Page 30/61
V4.2 / EN
Standard
04/JUL/2011
Page 31/61
7.3.
GLADIATOR
Gladiator is a post processing tool able to read different format of scanner and UE
format
V4.2 / EN
Standard
04/JUL/2011
Page 32/61
By selecting the new project, the user will be able to name the project
V4.2 / EN
Standard
04/JUL/2011
Page 33/61
Import data
Once the file converter is opened click on advanced mode to be able to choose the
export settings (if not all data contains into the files will be exported)
On the file selection part click on browse to select the data to import
Click on Browse to
select the scanner data
V4.2 / EN
Standard
04/JUL/2011
Page 34/61
On the Conversion Setting part select the correct NITX data (here LTE Scanner)
On the Advanced Setting , we are able to edit the conversion plan and to save it
V4.2 / EN
Standard
04/JUL/2011
Page 35/61
The conversion plan allows to select the exact data we want to export ( here the LTE TopN
Channel)
Once the data are converted, Right click on a file and select merge to merge all the data
together
V4.2 / EN
Standard
04/JUL/2011
Page 36/61
Select all the file to merge and then the device to include
V4.2 / EN
Standard
04/JUL/2011
Page 37/61
Add Transmitters
Right click on systems and select Import system (to import the site data from excel sheet)
V4.2 / EN
Standard
04/JUL/2011
Page 38/61
V4.2 / EN
Standard
04/JUL/2011
Page 39/61
Once the sytem imported, Check by a double click on the site data to see all the cells of the
network
V4.2 / EN
Standard
04/JUL/2011
Page 40/61
Add map
Right click on Vector and image data to import a geo-referenced map (as mapinfo map)
Add Workspace
Right click to create a new workspace
V4.2 / EN
Standard
04/JUL/2011
Page 41/61
It will fill
automatically the
range
V4.2 / EN
Standard
04/JUL/2011
Page 42/61
Once all data imported on the project view, we are able to start working with gladiator
V4.2 / EN
Standard
04/JUL/2011
Page 43/61
Create a map
All the information are on the workspace (frequency , cell id , rsrp....)
There are ordered by level (for exemple the freq 0 is the frequency of the best cell received, freq 1 the
second best ....)
Right Click on the wanted data on the layer control and select the properties to change the display
scheme. To create a new display scheme refer the next part.
V4.2 / EN
Standard
04/JUL/2011
Page 44/61
Export image
Once the map had been done there is a way to export it as an image, as a tab file or on google earth
format
V4.2 / EN
Standard
04/JUL/2011
Page 45/61
By using the CDC the operators will be able to generate automatic reports
Reports can represent the analysis results in either Map views, Result tables, or MS Excel
documents.
A custom report utilizes five types of components. These are outlined below:
Data sources
Parameters
Procedures
Outputs
Layouts
V4.2 / EN
Standard
04/JUL/2011
Page 46/61
DATA SOURCES
A data source provides a means to input tables into the Custom design center. Data sources are
separated into two main types. These include Device data sources and System data sources. The
Device data source is used to specify and create reports related to devices such as phones and
scanners. The System data source allows for designing of reports related to system parameters
such antenna azimuth and mechanical downtilt. Device data sources allow the user to specify what
data will be used for report generation based on Equipment manufacturer, Technology and
Device type. An example of such a data source would be an Agilent UMTS phone. System data
sources only require the user to provide the name of an existing system within the Gladiator project
view. Data sources defined are used in later stages in the report design process.
Add a new Device (for our example a JDSU LTE Scanner) and a new system ( defined in the
previous chapter)
PARAMETERS
Parameters are input variables the user can specify to be used in report generation. At creation
time the user can specify default values in specific ranges defined around that value. At run time of
the report the user can change this value as long as it is still within the range specified at creation
time. These features allow the user to create a flexible report that can generate dynamic results
based on inputs at report run time. There are multiple parameter types to choose from and inputs
characteristics can be specified for each. Such characteristics include setting valid input ranges for
value parameters and character length for text parameters and text length.
Add a new parameter group
V4.2 / EN
Standard
04/JUL/2011
Page 47/61
PROCEDURES
Procedures are the most important section of the Custom design center. Data is manipulated in the
Procedure node in order to provide relevant information to continue the report generation process.
Procedures have two main levels. The first level consists of data sets which is a starting point of
data manipulation. Data sets can contain data directly from the Data sources node or elsewhere
such as the result of a query from the Sql database. The second level called Operations perform
the actual data manipulation such as filtering or compression. The results of these Operations
nodes provide inputs to later stages.
Create 1 custom data set
Select the G_LTE scanner and take all the measured data
V4.2 / EN
Standard
04/JUL/2011
Page 48/61
Fill the column name between square baquets without using space
[serving_cells_counter]
Then set the expression to count the number of cell in 10 dB (see appendix)
V4.2 / EN
Standard
04/JUL/2011
Page 49/61
OUTPUTS
The Output node accepts defined procedures and uses the manipulated data to generate "Outputs"
such as tables, graphs and maps to place in next node "Layouts".
Add a new map (you can select as well new graph, table)
V4.2 / EN
Standard
04/JUL/2011
Page 50/61
LAYOUTS
Defining the Layout is the final stage to the report generation process. There are two types of
layouts possible; these are HTML layout and MS Excel layouts. To generate an HTML layout, the
user is provided with an embedded html editor to define exactly what the final report will look like.
In this stage all outputs are placed in the editor and descriptive text is placed around them as
necessary to describe the results of the reports. Custom design center also allows generation of a
MS Excel spreadsheet report. This report is based on an existing Excel 'template' document that
contains the desired formatting of the final report. Once this is complete, Custom design center
allows the user to simply 'place' each Output where desired on the template file. A copy of the
template file with the added output is generated hence allowing the template file to be reused as
desired.
V4.2 / EN
Standard
04/JUL/2011
Page 51/61
V4.2 / EN
Standard
04/JUL/2011
Page 52/61
7.4.
INFORMATION NEEDED
With MapInfo the post processor must provide coverage analysis, as shown below
(example taken on a trial in France)
CHANNEL POWER
V4.2 / EN
Standard
04/JUL/2011
Page 53/61
This best server view shows that tilts must be optimized to enhance or to limit the CELL ID coverage,
in order to limit the Handover request inside the area and to restore more homogenous cell coverage.
V4.2 / EN
Standard
04/JUL/2011
Page 54/61
RSRP COVERAGE
This view shows the global coverage for one ressource element including holes and poor level
The level must be over -95dBm ,in most of the case, inside the cluster area to allow a good
indoor penetration
RSRQ COVERAGE
This view shows the quality received for one resource element
95% of the measured samples has to be over -20 for 100% of load
V4.2 / EN
Standard
04/JUL/2011
Page 55/61
RS CINR COVERAGE
This view shows the coverage for the CINR for one resource element.
The level must be over -5dBm ,in most of the case, inside the cluster area.
V4.2 / EN
Standard
04/JUL/2011
Page 56/61
NEIGHBORING LIST
By using the server within 10 dB, the neighboring list have to be provided as follow
Server cell ID
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
4
3
3
3
3
5
6
8
6
4
4
4
3
3
6
5
5
4
5
4
6
8
9
7
5
5
5
4
6
8
6
7
7
7
5
7
10
11
8
13
6
7
5
7
9
7
12
11
8
6
10
11
15
9
14
7
12
6
8
10
15
13
12
9
8
11
16
16
10
15
10
13
7
9
11
Neigbors cell id
16
14
15
13
14
10
11
9
11
15
16
17
17
12
13
11
15
9
10
15
16
15
15
13
17
16
15
17
16
15
16
17
12
13
14
15
10
11
16
11
15
12
17
13
14
16
17
V4.2 / EN
Standard
04/JUL/2011
Page 57/61
8.
REPORTING
8.1.
MANDATORY DELIVERABLE
Once the raw data had been post processed, the contractor has to provide to AlcatelLucent :
V4.2 / EN
Standard
04/JUL/2011
Page 58/61
APPENDIX A
ANTENNA VALIDATION - Support
Site information
Site name
Site address
Site coordinates (WGS84)
Building height
Latitude =
Longitude =
Antenna 1
Antenna 2
Antenna 1
+45
-45
Antenna 2
+45
-45
Antenna 3
TYPE
AZIMUTH
TILT
HEIGHT from Roof
HEIGHT from ground
Antenna side
Radio Measurements
+45
Antenna 3
-45
Cable loss
VSWR
DTF
Spectrum Measurement
OK
NOK
OK
NOK
OK
NOK
OK
NOK
OK
NOK
OK
NOK
WGS84 (X,Y)
Length
Long=
Width
Lat=
Site Description
OK
OK
NOK
NOK
Environment description
OK
OK
OK
OK
OK
OK
NOK
NOK
NOK
NOK
NOK
NOK
Radio survey
OK
OK
OK
OK
NOK
NOK
NOK
NOK
Building Height
Antenna 1
OK
NOK
OK
NOK
OK
NOK
OK
NOK
OK
NOK
Antenna 2
OK
NOK
OK
NOK
OK
NOK
OK
NOK
OK
NOK
OK
OK
OK
OK
OK
Antenna 3
NOK
NOK
NOK
NOK
NOK
(**) Put a Cross inside the good compartment when picture is realized.
(**) At the end of survey if picture are not performed put cross in NOK compartment
V4.2 / EN
Standard
04/JUL/2011
Page 59/61
APPENDIX B
Copy and paste the following expression to count the serving cells within 10dB
case when [R0 RSRP (0)] - [R0 RSRP (1)] < 10 then 1 else 0 end +
case when [R0 RSRP (0)] - [R0 RSRP (2)] < 10 then 1 else 0 end +
case when [R0 RSRP (0)] - [R0 RSRP (3)] < 10 then 1 else 0 end +
case when [R0 RSRP (0)] - [R0 RSRP (4)] < 10 then 1 else 0 end +
case when [R0 RSRP (0)] - [R0 RSRP (5)] < 10 then 1 else 0 end +
case when [R0 RSRP (0)] - [R0 RSRP (6)] < 10 then 1 else 0 end +
case when [R0 RSRP (0)] - [R0 RSRP (7)] < 10 then 1 else 0 end +
case when [R0 RSRP (0)] - [R0 RSRP (8)] < 10 then 1 else 0 end +
case when [R0 RSRP (0)] - [R0 RSRP (9)] < 10 then 1 else 0 end +
case when [R0 RSRP (0)] - [R0 RSRP (10)] < 10 then 1 else 0 end +
case when [R0 RSRP (0)] - [R0 RSRP (11)] < 10 then 1 else 0 end +
case when [R0 RSRP (0)] - [R0 RSRP (12)] < 10 then 1 else 0 end +
case when [R0 RSRP (0)] - [R0 RSRP (13)] < 10 then 1 else 0 end +
case when [R0 RSRP (0)] - [R0 RSRP (14)] < 10 then 1 else 0 end +
case when [R0 RSRP (0)] - [R0 RSRP (15)] < 10 then 1 else 0 end +
case when [R0 RSRP (0)] - [R0 RSRP (16)] < 10 then 1 else 0 end +
case when [R0 RSRP (0)] - [R0 RSRP (17)] < 10 then 1 else 0 end +
case when [R0 RSRP (0)] - [R0 RSRP (18)] < 10 then 1 else 0 end +
case when [R0 RSRP (0)] - [R0 RSRP (19)] < 10 then 1 else 0 end
V4.2 / EN
Standard
04/JUL/2011
Page 60/61
END OF DOCUMENT
V4.2 / EN
Standard
04/JUL/2011
Page 61/61