LTE RF Optimization Methods & Procedures

RF-E346
LTE FDD RF Optimization Methods & Procedures Internal Version
Issue 2.0
LTE FDD RF Optimization Methods & Procedures

Internal Version
V2.0
September 2, 2011
As the undersigned EDITOR I am responsible for keeping this document current, and conforms to the RF
Document Template RF-Q001
Original Signature on File
William Hsieh
9/2/2011
Date:
Alcatel-Lucent PROPRIETARY Use pursuant to Company Instructions
Page 1 of 225
RF-E346
Issue 2.0
Authors
This part provides the names of the authors who wrote the respective sections (Some sections have been
deleted).
Section
Number
1
2
3
4
5
Section Title
Author
Entrance Criteria
Exit criteria
Support Information
Organization chart
Optimization Strategy
Data collection kit configuration
7
8
9
10
Naming Convention
How to set up and use LG Adrenalin UE
Using IPerf and WINDS
How to set up and use LLDM to collect drive test
data
How to set up and use NEMO to collect drive test
data
How to use JDSU E6474A-X to collect Drive Test
Data
How to use JDSU scanner
How to use PcTel scanner
How to set up and use Syncro Test
Data Collection Procedure
How to use eDAT
How to detect problems and how to fix them
How to use SAM to examine network status
How to use SAM to change eNodeB parameters
How to change OCNS
How to examine system parameters and change
neighbor list using WPS
How to use SAM to collect call trace data
How to use SAM to change the antenna electrical
tilt
Procedure to change antenna azimuth and
mechanical tilt
Plot scanner data to compare LTE signal strength
vs. UMTS and GSM signal strength
Additional Information
William Hsieh
William Hsieh
Sreenu Pamidi
Sri Adimulam
Alex Anokye
Sri Adimulam (Design
Engineer Role)
Guillermo Alvarez (Kit
configuration)
Alex Anokye (PC
configuration)
Saad Al Adhami
Guillermo Alvarez
Alex Anokye
Alex Anokye
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
Guillermo Alvarez
Guillermo Alvarez
Cliff Castillo
Auillermo Alvarez
Aderemi Adeyeye
Aderremi Adeyeye
Mateen Hussain
Alex Anokye
Sri Adimulam
Sri Adimulam
Cliff Castillo
Vansotheavy Sem
Sri Adimulam
Sri Adimulam
William Hsieh
Vansotheavy Sem
Sreenu Pamidi
(Support Escalation
Path), Alex Anokye
(Server)
CHANGE RECORD
This section provides a history of changes made to this document.
9/2/2011
Page 2 of 225
RF-E346
Date
September,29,
2010
September 2,
2011
Reason
Section Title
Initial Release
All sections
Revise the organization and the content of the whole

document
Issue 2.0
Issue #
V1.0
V2.0
END OF CHANGES
9/2/2011
Page 3 of 225
RF-E346
Issue 2.0
TABLE OF CONTENTS
1
Entrance Criteria........................................................................................................................................ 8
Exit Criteria................................................................................................................................................. 8
Support Information.................................................................................................................................. 8
Organization Chart..................................................................................................................................... 9
Optimization Strategy................................................................................................................................ 9
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
5.10
5.11
5.12
5.13
5.14
5.15
5.16
5.16.1
5.16.2
5.17
5.17.1
5.17.2
5.17.3
5.17.4
Performance in a LTE system depends on many different critical elements..................................9

RF Optimization Objectives................................................................................................................. 9
RF Optimization Parameters................................................................................................................ 9
RF Loading Consideration................................................................................................................. 10
Optimization Deployment Team Structure........................................................................................ 11
LTE RF Optimization Trouble Shooting Support..............................................................................13
Customer Communications & Reporting.........................................................................................13
Pre-Launch Optimization Steps......................................................................................................... 13
Key Entrance Criteria (before Preparation / Pre Test phase)..........................................................14
Preparation / Pre-Drive....................................................................................................................... 14
Sector Testing / Stationary Tests....................................................................................................... 15
Cluster Tests....................................................................................................................................... 15
System Test......................................................................................................................................... 16
Final Report......................................................................................................................................... 16
Troubleshooting considerations for other elements of the LTE network......................................17
Antenna Down Tilt Adjustment.......................................................................................................... 19
Pilot pollution................................................................................................................................... 20
Overshooting Cell............................................................................................................................ 21
IRAT..................................................................................................................................................... 23
IRAT Test Preparation Procedure:................................................................................................... 23
IRAT Test Execution Procedure:...................................................................................................... 23
Measuring LTE->UMTS/eHRPD HO interruption time using WiReshark.........................................25
Idle LTE- eHRPD/UMTS Handover.................................................................................................. 25
Data Collection Kit Configuration........................................................................................................... 26

6.1
6.2
Kit Configuration................................................................................................................................ 26
PC Configuration................................................................................................................................ 26
Naming Convention................................................................................................................................. 27
How to set up and use LG Adrenalin UE................................................................................................27

8.1
8.2
LG Adrenaline Tips............................................................................................................................. 27
Useful AT Commands......................................................................................................................... 28
Using IPerf and WINDS............................................................................................................................ 28
9.1
9.2
10
IPerf...................................................................................................................................................... 28
WINDS.................................................................................................................................................. 30
How to set up and use LLDM to collect drive test data........................................................................36
10.1
10.1.1
10.1.2
10.1.3
9/2/2011
LLDM (LGE Logging Diagnostic Monitor) Introduction...................................................................36

What is LLDM?................................................................................................................................ 36
Components:................................................................................................................................... 36
Target Systems................................................................................................................................ 37
Page 4 of 225
RF-E346
Issue 2.0
10.2
Installation........................................................................................................................................... 37
10.2.1
Required H/W and S/W................................................................................................................... 37
10.2.2
Installing LLDM................................................................................................................................ 37
10.3
License Key activation....................................................................................................................... 40
10.3.1
Step 1.............................................................................................................................................. 41
10.3.2
Step 2.............................................................................................................................................. 41
10.3.3
Step 3.............................................................................................................................................. 41
10.4
Operation............................................................................................................................................. 42
10.4.1
Setup Menu..................................................................................................................................... 42
10.4.1.1
Set Com Port.............................................................................................................................. 42
10.4.1.2
Logging Mask............................................................................................................................. 44
10.4.2
Information Menu............................................................................................................................. 45
10.4.2.1
Logging Status........................................................................................................................... 46
10.4.3
Replay Menu................................................................................................................................... 47
10.4.3.1
Load Replay Menu..................................................................................................................... 47
1.1.1.
Replay Toolbar................................................................................................................................. 48
10.4.4
Exit Menu......................................................................................................................................... 48
10.4.5
Tree View Menu............................................................................................................................... 48
10.4.6
Layer 1 Menu................................................................................................................................... 49
10.4.6.1
Wide- Band CQI Information...................................................................................................... 50
10.4.6.2
Serving Cell Quality Information................................................................................................. 51
10.4.7
Cell Information............................................................................................................................... 51
10.4.7.1
PDSCH PHY Throughput........................................................................................................... 51
10.4.7.2
PDSC H BLER (Block Error Rate)..............................................................................................52
10.4.7.3
PDCCH Detection Rate.............................................................................................................. 52
10.4.7.4
PUSCH PHY Throughput........................................................................................................... 52
10.4.7.5
LOGMASK.................................................................................................................................. 53
10.5
How to use LLDM................................................................................................................................ 55
11
How to set up and use NEMO to collect drive test data.......................................................................61
11.1
Getting Started.................................................................................................................................... 61
11.2
NEMO Outdoor.................................................................................................................................... 61
11.2.1
OPEN NEMO OUTDOOR............................................................................................................... 61
11.2.2
VERIFY YOUR SCRIPT SETTINGS...............................................................................................62
11.2.2.1
Check UE1 Settings (Iperf):........................................................................................................ 62
11.2.2.2
Check UE2 Settings (FTP)......................................................................................................... 63
11.2.2.3
Check UE3 Settings (Ping)......................................................................................................... 64
11.2.3
CONNECT YOUR SCANNERS....................................................................................................... 64
11.2.4
SCANNER(S) BECOME NON-RESPONSIVE................................................................................65
11.2.5
NEMO-OUTDOOR: WORK ON-LINE..............................................................................................66
11.2.6
NEMO OUTDOOR TIPS.................................................................................................................. 66
11.3
ADRENALINE & USB HUB PHYSICAL CONNECTIONS...................................................................74
11.4
TOOLS LAB ATT-LTE RF DRIVE TEST KIT CONFIGURATION.........................................................74
11.5
ADRENALINE RECOGNIZED BY LAPTOP........................................................................................75
11.6
HOW TO IDENTIFY COM PORT NUMBER ASSIGNMENTS..............................................................77
11.7
QUERY YOUR MODEM....................................................................................................................... 78
11.8
DRIVERS & SOFTWARE..................................................................................................................... 78
11.9
ADRENALINE UE SOFTWARE UPDATES......................................................................................... 78
11.10
LGE ADRENALINE TIPS..................................................................................................................... 79
12
How to use JDSU E6474A-X to collect Drive Test Data........................................................................79
13
How to use JDSU Scanner...................................................................................................................... 82
13.1
13.2
13.3
13.4
13.5
13.6
13.7
9/2/2011
Activate JDSU E6474A-X.................................................................................................................... 82

Creating a Project............................................................................................................................... 82
How to add a receiver based measurement.....................................................................................85
Creating a Measurement.................................................................................................................... 89
Creating a Workspace........................................................................................................................ 91
Probing the device (Connecting the device)....................................................................................98
Checking your settings.................................................................................................................... 100
Page 5 of 225
RF-E346
13.8
13.9
13.10
14
How to use PcTel Scanner.................................................................................................................... 109

Frequency Scanning - PCTEL GSM/UMTS Scanners....................................................................109
Frequency Scanning - PCTEL EX LTE Scanner..............................................................................111
Frequency Scanning - PCT GSM Scanner......................................................................................112
TOP-N Pilot Scanning PCTEL - UMTS............................................................................................. 114
LTE OFDM Scanning - PCTEL EX LTE............................................................................................. 116
How to set up and use Syncro Test...................................................................................................... 118
15.1
15.2
15.3
15.3.1
15.3.2
15.3.3
15.4
15.4.1
15.4.2
15.4.3
15.4.4
15.4.5
16
Establish Remote Control Connection........................................................................................... 119

Configure Adapters to Avoid Conflicts........................................................................................... 119
Configuring the Master Controller Control panel..........................................................................124
Testing Panel................................................................................................................................. 124
Log Data Panel.............................................................................................................................. 125
Snapshot View Panel..................................................................................................................... 126
Configuring Probe (LLDM, NEMO, etc.).......................................................................................... 127
LLDM Probe.................................................................................................................................. 127
Syncro Test LLDM Probe Options.................................................................................................128
Verify connectivity of Probe to the Master Controller.....................................................................129
Load Test Cases into the Master Controller...................................................................................132
Select the test to run on each UE.................................................................................................. 134
Data Collection Procedure.................................................................................................................... 136
16.1
16.2
16.3
16.4
17
Issue 2.0
Opening a Project (eg. ATT LTE)..................................................................................................... 103

Collecting data.................................................................................................................................. 105
How to export a project and associated drive test data................................................................106
14.1
14.2
14.3
14.4
14.5
15
LLDM Data Collection Software....................................................................................................... 136

Syncro Test....................................................................................................................................... 139
For Data Collector in the van:.......................................................................................................... 139
For Remote Control or Local Control.............................................................................................143
How to use eDAT.................................................................................................................................... 146
17.1
Download and Install eDAT.............................................................................................................. 147
17.2
Create a Project................................................................................................................................ 147
17.3
Open an existing Project.................................................................................................................. 147
17.4
Add Data to an Existing Project...................................................................................................... 147
17.5
Study: Examining and Aligning Data Files.....................................................................................147
17.6
Create Cell location files (LCAT)..................................................................................................... 149
17.7
Default Views of Metric and data..................................................................................................... 150
17.7.1
Un-binned data.............................................................................................................................. 151
17.7.2
Temporally binned data................................................................................................................. 151
17.7.3
Spatially binned data..................................................................................................................... 152
17.7.4
Scatter Plots.................................................................................................................................. 152
17.7.5
Histogram...................................................................................................................................... 152
17.7.6
Grid................................................................................................................................................ 153
17.7.7
Maps.............................................................................................................................................. 153
17.7.7.1
Show eNodeB sites.................................................................................................................. 154
17.7.7.2
Zoom in and Zoom out............................................................................................................. 154
17.8
Change Appearances....................................................................................................................... 154
17.8.1
Fixing Legend window................................................................................................................... 154
17.8.2
Changing bin size.......................................................................................................................... 154
17.8.3
Displaying labels............................................................................................................................ 154
17.8.4
Changing Themes......................................................................................................................... 155
17.9
Multi-Metric Map View...................................................................................................................... 157
17.9.1
View several metrics in the same map View Synchronization....................................................157
17.9.2
Multi-Metrics Grid View.................................................................................................................. 158
17.9.3
View Map and Grid........................................................................................................................ 159
17.10
Filters................................................................................................................................................. 160
17.10.1
Excluding data not meeting RSRP or SNR thresholds..................................................................160
17.10.2
Filtering with other criteria.............................................................................................................. 161
9/2/2011
Page 6 of 225
RF-E346
Issue 2.0
17.11
Messages (Message Explorer)......................................................................................................... 162
17.11.1
Text Search.................................................................................................................................... 162
17.11.2
Message Groups........................................................................................................................... 163
17.12
Reporting........................................................................................................................................... 165
18
How to detect problems and how to fix them......................................................................................167
18.1
18.2
18.3
18.4
18.5
18.6
18.7
18.8
18.9
18.10
Maximize distance between co-PCI cells........................................................................................ 167

Eliminate Co-PCI neighbors............................................................................................................. 168
Neighbor Reciprocity....................................................................................................................... 169
Missing Neighbor.............................................................................................................................. 170
Drop call Scenario No Handover Command Received...............................................................171
Drop call Scenario missing Neighbor contributed to 4 repeated drop calls............................173
RACH ISSUE...................................................................................................................................... 173
Identifying Pilot Polluted Areas....................................................................................................... 174
Call drop scenarios in the Handover regions.................................................................................177
Handover Parameters and Recommended Settings......................................................................180
19
How to use SAM to examine network status.......................................................................................188
20
How to use SAM to change eNodeB parameters................................................................................191
21
How to change OCNS............................................................................................................................ 194
22
How to examine system parameters and change neighbor list using WPS.....................................206
23
How to use SAM to collect call trace data...........................................................................................207
24
How to use SAM to change the antenna electrical tilt........................................................................210
25
Procedure to change antenna azimuth and mechanical tilt...............................................................214
26
Plot scanner data to compare LTE signal strength vs. UMTS and GSM signal strength.................215
27
Additional Information........................................................................................................................... 215
27.1
27.2
27.3
Support Escalation Path.................................................................................................................. 215

Filzella................................................................................................................................................ 219
DOS FTP............................................................................................................................................ 221
28
Reference............................................................................................................................................... 221
29
Acronyms............................................................................................................................................... 222
9/2/2011
Page 7 of 225
RF-E346
Issue 2.0
1
Entrance Criteria
The Statement Of Work (SOW) should specify the condition of the network before the RF team starts the
optimization. The status of the network criteria should be delivered to the RF Lead 1 week before the
commencement of the RF optimization. The RF Lead should review the status. If they meet the criteria stated in
the SOW, the RF Lead will direct the team to go ahead with the optimization. The criteria usually listed in the
SOWs are:
Providing the RSRP map and SINR map (by customer if customer performs the design, by the ALU
design team if it performs the design).
Providing eNodeB site locations (Lat / Lon and physical address), antenna azimuths, tilts, cell ids, and
neighbor lists by customer if customer performs the design, by the ALU design team if it performs the
design)
Providing all the eNodeB attributes, preferably in an Excel format (by the integration team)
Providing the configured Neighbor Lists, preferably in an Excel format (by the integration team)
Specify the agreed upon condition of the test environment like minimum RSRP, SINR, and backhaul
available throughput (usually listed in the SOW).
Having completed all the functional tests and site integration activities for all targeted eNodeBs and
untargeted eNodeBs located out to the 2nd tier.
Being free of critical and major alarms for 48 hours
Passing all Acceptance Test Procedures. A copy of the Integration Report is show in the document
below:
Integration
Report.doc
Having full end-to-end connectivity with the EPC (S1-SGW, S1-MME.)

Having successfully originated and terminated calls on every sector
Having transmitted the proper Cell ID from each sector
Having successfully handovered calls between sectors of the same eNodeB
Having cleared the spectrum in the planned optimization region. Any unresolved external interference
sources shall be documented and identified as part of the Excluded Area.
Stationary throughput test having passed the agreed upon percentage of eNodeBs in a cluster.
Additional Network Readiness items beyond site integration include:
Full X2 connectivity to all neighbor candidates via X2-MME
Neighbor list established and active
2
Exit Criteria
Exit criteria are defined in SOW. They typically include:
Up Link Throughput
Down Link Throughput
Radio Resource Control (RRC) Failure Rate
Radio Resource Control (RRC) Drop Rate
The exit KPI measurement environments and conditions and Exit Criteria should be clearly defined and signed by
ALU and the customer to avoid cost and time overrun due to misunderstandings.
3
Support Information
Toolkit, NEMO, LLDM, JDSU, IPerf:

Contact numbers in: http://usnavsgtk01.ndc.lucent.com/rftoolslab/Contacts.aspx
9/2/2011
Page 8 of 225
RF-E346
Issue 2.0
eDAT, Syncro Test, WINDS, SPO, ROVA:

URL: http://navigator.web.alcatel-lucent.com/
Tel: 908-743-4599
e-mail: navigatorhelp@alcatel-lucent.com
eNodeB and Core Network related:
To be provided by Directors of the customer team.
Customer Contacts:
To be provided by Directors of the customer team.
4
Organization Chart
To be provided by the Director of the Optimization Team.
5
Optimization Strategy
5.1
Performance in a LTE system depends on many different critical elements

RF link
eNodeB
SGW/PGW
Backhaul
MME
Routers
Core Network Backbone
Test Server (FTP/UDP)
Test Client
UE (User Equipment)
Proper optimization of each element is important to attain good end-user experience and system performance.
Lessons learned from prior deployments and from a technology trial will help refine RF optimization procedures
5.2
RF Optimization Objectives
The goal of RF optimization is to optimize user experience and system performance in a defined
coverage area by fine-tuning all aspects of air-interface elements.
System performance consists of:
o High data rates
o Low latency
o Good call setup rate
o Low Drop call rate
5.3
Performance is measured through a series of stationary and drive tests after a cluster of cells is
integrated and on the air
o Measurement with test UE
o Use of test Application (e.g. FTP, UDP, Ping)
Performance is optimized by fine tuning key RF parameters on a cluster of cells
RF Optimization Parameters
There are a lot of performance impacting parameters available

In order to deploy a network in a timely manner, it is critical to identify and categorize key RF parameters
Categorizing the parameters according to their importance, scope and frequency of adjustments
9/2/2011
Page 9 of 225
RF-E346

o
o
o
Primary Parameters Most often used for coarse coverage adjustment to ensure cluster and
system wide acceptable performance
Secondary Parameters Fine tune performance in localized problem areas
Fixed Parameters Algorithmic parameters
Often require careful study including simulations and lab evaluation
Typically should not be customized to fix local problems the parameter values are set
for an operators whole system
Many important recommendations are derived from technology trials
Field evaluation of commercial network will fine tune recommendations in the future
Cell site coverage parameters

o Antenna Adjustments
Antenna down tilt (mechanical and electrical), azimuth, beam width attributes
Maximize coverage while controlling interference and overshoots to neighboring cells
Antenna adjustments impact footprint of both links equally
For overlaid systems, many operators use shared antennas for two or more technologies.
Because adjusting the antenna for one technology will impact the coverage of another
technology, this is usually not a viable option. Moreover, share antennas usually have
lower gain compared to single used antennas.
eNodeB Power
o Can be conveniently adjusted with the Reference Signal power (dBm/RE) configuration.
Power level for all other channels (i.e. PDCCH, PDSCH, Primary and Secondary Sync,
PCFICH, PHICH) are provisioned relative to Reference Signal level
Note, however, this is not a preferred approach for adjusting cell coverage for several
reasons
o Generally prefer antenna adjustments over cell site power when adjusting coverage in order to
maintain Uplink/Downlink balance
Handover parameters
o Hard Handovers in LTE
o UE uses Hysteresis threshold and Time-To-Trigger to request Handover in connected state
Trade off between call drags and frequent data interruption (ping-ponging)
o Similar set of parameters in idle mode
Hysteresis, Reselection timer, Min RSRP level for the candidate cell, RSRP level at the
serving cell below which UE initiates intra frequency idle HO search
5.4
Issue 2.0
Fixed Parameters
o Several algorithmic parameters available in the deployment system
o Below is a list of functional areas/algorithms containing Fixed Parameters
Overhead and Traffic power settings
DL/UL scheduler settings
MCS translation table
CQI to SINR mapping table
Power Control parameters
RACH parameters
HARQ parameters
MIMO parameters
Call admission
Inter-Cell Interference coordination
RRH tx/rx propagation delays
RF Loading Consideration
DownLink
o OCNS may be used to simulate other cell loading
9/2/2011
Page 10 of 225
RF-E346
o
o
Issue 2.0
Specified number of REs can be keyed up to generate RF interference from surrounding

cells
Actual user gets higher priority
As test UE moves around, actual user data packets will substitute OCNS RE on the
serving sector
Sufficient to simulate other cell loading, no need to generate Resource contention within the test
cell
Single user will be assigned most of the available traffic REs
Per user throughput will simply scale down in proportion if additional users are added or
simulated on the serving sector (proportional fair scheduler)
Uplink
o IoT can be used on the UL to simulate the effect of interference from users of surrounding sectors
and of the serving sector.
Mutual agreement with customer on OCNS and IoT settings for testing
Before the start of the optimization, team structure should be in place and each persons roles and responsibilities
should be communicated to the entire team.
5.5
Optimization Deployment Team Structure

RF Director
Technical Lead
Troubleshooting
Team
RF Cluster
Lead
Data
Factory
SME
SAM
Engineer
CTA/PLM
Figure 1 Optimization Deployment Team Structure
RF Director
o Provide leadership and direction throughout the staff planning and the project delivery
o Ensure successful delivery, including managing of changes, up scopes, and profitability for the
project
o Manage customer relationship
o Accountable to the customer and ALU for delivering the project in accordance with the contract
RF Technical Lead
o Principle technical Interface to customer
o Maintains master schedule and tracks progress
o Defines Process and tools for test tracking
o Runs Project Meetings
Weekly Status
Daily execution
o Works with R&D and PLM to close Deployment gaps
o Project reporting
o Tracks critical deliverables
HW, SW, UEs, tools etc...
Subject Matter Expert (SME)

o Works closely with field and R&D to identify, isolate and resolve issues
Takes ownership of issues so lab teams and field teams can continue to progress
o Interfaces with R&D and UE manufacturer to prioritize, track and resolve issues
Communicates status and fixes to the rest of the team
9/2/2011
Page 11 of 225
RF-E346

o
o
o
o
o
o
Issue 2.0
Provides LTE technical troubleshooting support

Provides assistance to RF Lead and Cluster Engineer in solving real-time problems
Provides support to RF lead in explaining any technical issue that comes from the customer
Provides training for new RF engineers and contractors
Work very closely with Troubleshooting team in Resolving RF issues
Provide data analysis and presentation
Service Aware Manager (SAM) Engineer

o Monitors and Verifies Cell status on daily basis
Ensure that network elements are active prior to drive testing
o Verifies RF configuration settings using WPS
o Makes changes to RF configuration at the request of RF Cluster Engineer
o Executes all Work orders using SAM
o Runs OCNS for RF Loading
o Tracks all Physical antenna changes, uses SAM to remotely control electrical tilts
o Uses WPS to make all parameter changes
o Executes all WTA traces, (eNodeB and MME, SAM, XMS traces)
o Point of Contact for all eNodeB issues to DSC team for Resolution
o Places well compressed data files of various size (1GB, 200MB, 100MB) on the test server
o Obtains cell sites attributes (lat, lon, heights, azimuth, BW) and pass them on to the Cluster
Engineers
Data Factory
o Responsible for processing Cluster Drive data upon request from Market
RF Cluster Engineer Lead

o Provides support to cluster test drive team during testing
o Analyses Data and creates Presentations
o Works with customer to make sure all physical antenna changes recommended by RF cluster
engineers are scheduled and implemented
o Test planning
Definition of test cases and procedures
Analyses in support of test plan
Interface with R&D on product needs
Specifies new tools needed and defines required enhancement of existing tools.
o Manages weekly and daily optimization goals, coordinates drive routes and organizes cluster test
plan
CTA/PLM
o Provides information on eNode B integration status and schedule
o Provides help in resolving all eNode B issues
o Provides escalation path of all issues that are RF dependent
o Can be used as path of escalation to customer issues such as transport issues, defective
antenna/cable issues, transport/backhaul
o Assists in getting access to customer sites for site visits
Logistics Coordinator/Drive Test Coordinator

o Integrate Drive Test equipment
Ensures the team uses calibrated test UE with up to date firmware
Properly configures client laptop, GPS equipment, LLDM, NEMO software versions
o Field equipment readiness
o Field preparation
o Verifies procedures, tools etc
o Keeps track of all equipment that is necessary for RF Optimization
o Labels and assigns all equipment under the direction of the RF Lead
o Guides the activities every day during the cluster test
9/2/2011
Page 12 of 225
RF-E346
Issue 2.0
Office Assistant - optional

o Provides support to the RF Lead and entire RF Team
o Manages office environment
Makes sure printers are set up in the office
Keeps inventory of all equipment that will be shipped to the office
Keeps track of Third party contractor time sheet
Helps process RF data for RF cluster engineers
Makes sure sample plots are displayed on the walls of War Rooms
Tracks all integrated cell sites and the pending sites
Keeps record of all rented vans and other misc stuff that would be purchased locally.
Drive Teams
o Each drive team includes 1 data collector and 1 driver. The drive team performs the tests and
collects data.
5.6
LTE RF Optimization Trouble Shooting Support
Figure 2 Trouble Shooting Support
5.7
Customer Communications & Reporting

Status Reports providing one consistent view of the RF optimization progress to the customer are strongly
recommended
The reports should be created once a week or as negotiated with the customer
To strengthen communication links, ALU RF engineers should co-locate with customer RF engineers
while still keeping in a private area
Ongoing communication with the customer is strongly recommended
9/2/2011
Page 13 of 225
RF-E346
Issue 2.0
5.8 Pre-Launch Optimization Steps

RF Optimization process consists of a series of phases and tests
Preparation and Pre-Drive
Single user stationary good RF test and Sector Tests
Cluster Optimization Test
System Tests
Below are some basic pre-optimization Check Lists
1
2
3
4
5
6
7
8
9
10
5.9
Obtain a copy of the RNP 9955 export that shows sites list, cell configuration:
antenna heights, Azimuth, and tilts, PCI, Neighbor List
Get a WPS export to verify RNP data is captured correctly during provisioning
( this can possibly be done using RNP2PMCtool)
Obtain a copy of RF design CID report and view coverage prediction
Obtain MAPinfo files for Cluster & Supercluster Polygons (from Design Team)
Obtain Cluster Drive Route (Mutually agreed to by AT&T and Optimization Team) &
Supercluster Drive Routes (from AT&T)
Export sites configuration & polygons onto Google Earth and view morphology of
the Cluster
Obtain copies of antenna tilt settings screen-capture from installation team & verify
against design baseline
When sites come on air, review RITC integration report and check (1)Tx Power, (2)
RTWP values, and (3) that call test were made
Before starting any site test check for any eNodeB alarms either directly through
accessing SAM or from Operations. Please ensure that (1) the site is declared
QOS ready for optimization by AT&T and (2) eNodeB must be in the "reserved for
operator use" state.
Assess alarm impact & plan testing accordingly
Key Entrance Criteria (before Preparation / Pre Test phase)

Cluster Cells have been integrated
Cluster Cells are transmitting and call through testing completed to verify basic connectivity
Cluster a contiguous area served by 15-20 eNodeBs.
Figure 3 Key Entrance Criteria
9/2/2011
Page 14 of 225
RF-E346
Issue 2.0
5.10 Preparation / Pre-Drive

Prepare the cluster before initiating RF optimization tests. The more exhaustive the pre-checks, the fewer
obstacles and delays will be encountered during RF optimization. Steps include:
Spectrum Clearance
o Usually conducted by the operator
o Best to isolate external interferers prior to cell integration it is a time consuming process
Drive Route Selection

o Mutually selected drive route for optimization and cluster testing
o Typically 6-8 hours long drive route per cluster of 15 -20 cells
o Mix of major highways, primary and secondary routes through varying terrain
o Identify stationary locations and Sector test routes close to the test cells
Underlay System Baseline

o Good idea to obtain coverage and RF performance maps for the underlying system to pre-identify
trouble RF spots
Neighbor List Planning

o Careful planning goes a long way in minimizing Handover failures and throughput impact from
call drags due to NL omissions
o Underlay system configuration can be utilized to expedite NL planning and minimize omissions
Verify Configuration Settings

o Configure parameter settings in the system in accordance with ALU recommendations and
mutually agreed to golden set parameters.
Obtain cell site attributes

o Location, cell identity, antenna attributes to help with drive test data analysis
Validate various network elements that are active prior to drive testing
o Hardware Audits
o Alarms and Fault management Timing issues, etc
o Network integrity ping each IP network component in the system to verify inter-connectivity
Integrate Drive Test equipment

o Ensure use of calibrated test UE with up to date firmware, properly configured client laptop and
test server, GPS equipment, LLDM, NEMO software versions
o Interconnect drive test kit components, integrate in the test van
o Place well compressed data files on the test server fro FTP downloads
o Collect sample drive test logs / cell traces with FTP download and run through post processing
tools to validate compatibility
5.11 Sector Testing / Stationary Tests

Stationary Tests
o Goal to obtain best achievable data rates/low latency close to the cell in good RF
o Single user on the test sector, no users anywhere else
o Verifies that non RF components are fully optimized
Minimal packet drops on the backhaul, no issues with test UE/data logging, low latency to
the test server, etc
Difficult to isolate such problem elements using drive tests where RF conditions have
more dominant impact on the performance
o Typically, a small number of sectors are sampled during commercial deployment but since this is
new technology it may be advisable to conduct the test on all sectors one by one
o FTP downloads, uploads and ping tests
Sector Testing
9/2/2011
Page 15 of 225
RF-E346

o
o
o
Issue 2.0
Drive around 3 sectors close to a cell to ensure each sector is transmitting in the desired direction
To verify that PCIs are implemented correctly as per RF Design
Essentially validate proper cell identity, antenna orientation and antenna cabling for each sector
5.12 Cluster Tests

Collect a comprehensive set of RF performance statistics by drive testing on the pre-defined Cluster
drive routes
o Essential coverage drives with the test UE
o Iterative drive testing, after each set of parameter adjustments
Goal to improve performance to meet acceptance and exit criteria levels

o Isolate problem areas in terms of low throughputs and call drops
o Identify root cause through inspection of drive test logs and system traces
o Categorize root cause in terms of
Low signal strength
Excessive cell overlap
Neighbor List omissions
Sub-optimal parameter settings
Hardware defect, software issue, etc
o Adjust and iterate relevant RF parameters to Resolve performance issue
Primary and Secondary parameter
o Escalate product issues to development to remedy defect
o Catalog unresolved issues for long term solution (e.g., antenna adjustments)
Key RF Performance metrics (distribution and map plots)

o SINR
o Data Rates, MCS, RBs
o Throughput (DL & UL)
o BLER
o UE transmit/receive power levels
o Drop calls
o MIMO mode
o Latency results
Data collection primarily involves continuous FTP downloads of a large file

o Potentially multiple iterations after adjusting primary and secondary optimization parameters
o When the cluster is fairly optimized, several additional benchmarking tests can be executed
towards the end
5.13 System Test

After concluding Cluster level optimization on each cluster, various clusters in the network are
merged
System Test are designed to measure performance throughout the system
o Goal to ensure performance is preserved along cluster boundaries
Typical a drive route 4-6 hours long per system of 100 cells
o Iterate parameter adjustments similar to the Cluster tests
Benchmark typical RF performance metrics (listed earlier)
o Some of them serve as Exit Criteria to determine System readiness for commercial launch
Many times either Cluster or System Tests are executed, but not both
o Depends on size of the system and agreement with the customer
5.14 Final Report
9/2/2011
Page 16 of 225
RF-E346
Issue 2.0
The final report shall include all or some of the following items, depending on the agreement with the
customer:
Raw drive test data
Baseline of Coverage, Accessibility, Mobility, Retainability and Service Integrity. (Cluster level) and
Histograms (cluster). Plots should explicitly identify the included Area and any Excluded Areas
Optimized Coverage, Accessibility, Mobility, Retainability and Service Integrity (cluster level) and
Histograms (cluster). Plots should explicitly identify the included Area and Excluded Area
Baseline Site Configuration (table and database)
Optimized site configuration (tables or database)
Summary of all configuration changes and reasons for those changes
Baseline KPIs, at the cluster level. Any non-compliant KPIs would be expanded upon for future
attention
Any identified service-affecting bugs, faults, failures in any equipment during testing
The following metrics would be captured in the Reports
o Coverage
Serving RSRP, RSRQ, RSSI, RS-SINR
PUSCH and PUCCH Tx Powers
Serving Cells within 10dB
o Accessibility
RRC Connection Success Rate
Attach Success Rate
Service Request Success Rate
Access RACH Latency
o Retainability
RRC Drop Rate
Dedicated Bearer Drop Rate
o Mobility
S1 Handover Failure Rate
X2 Handover Failure Rate
S1 Handover Interruptions Time
X2 Handover Interruptions Time
IRAT Handover success rate and locations
o Service Integrity
DL/UL throughputs
PDSCH/PUSCH throughputs
PDSCH/PUSCH BLER
RLC BLER
MCS, Resource Utilization
5.15 Troubleshooting considerations for other elements of the LTE network
Some typical hardware issues/symptoms:

o Loose Antenna connector/Swapped sector cables (Sector drives/Functional Test)
o Low power / SNR (power amplifier module/filter/radio)
o GPS Timing circuitry (likely will impact co-located 1x/DO cells)
o High RSSI (possibly linked to external interference, eliminate that first)
o Issues in the uplink chain (RACH attempts maxing out)
o Issues in the forward link chain (low DL SINR and data rates close to the cell)
LTE Backhaul
o Provision adequate Bandwidth (100Mbps) and storage space (100GByte) in the server to support
peak data rates
o High Packet loss/latency/jitter
Ping from UE (client) to server under benign RF
Flood ping from MME and SGW to eNodeB
9/2/2011
Page 17 of 225
RF-E346
Issue 2.0
Use of PDM tool to isolate issues
Routers
o Two types of routers used to offer IP/MPLS service over backhaul
7750 Service Router terminates the backhaul at the ePC site
7705 Service Aggregation Router terminates backhaul at each eNodeB
o Ensures proper VLAN provisioning to separate OA&M traffic from user data and signaling traffic
o Floods ping/PDM tool to isolate packet drop/latency/jitter issues
Figure 4 LTE Elements
MME (Improper configuration of MME elements can impact throughput performance)

o Maintain and verify proper IP connectivity across various IP elements
eNB to MME and SGW
Proper VLAN provisioning for OA&M and user data streams
o
Use of high bandwidth ping to isolate bottlenecks
Duplicate IP address assignments can lead to high packet loss/latency
SGW/PGW
o Beware of any mismatches in the SGW/PGW Ethernet interface configuration
Match line speeds and mode between a pair of Ethernet interfaces
o
Mismatch between two endpoints will cause collisions, packet drops and/or large variations in
latency
Becomes more apparent with multiple users
E.g., Full duplex on one side/Auto-config on the other side
Applies to any intervening switches/routers between the PGW and SGW
Allocate adequate bandwidth between PGW and SGW
Core Network Backbone
9/2/2011
Page 18 of 225
RF-E346
Ensure minimal latency and packet drops between the PGW and external gateway to the
internet/test server
Important for realizing full potential of the LTE high speed data rates
FTP more sensitive to packet losses
HTTP more sensitive to latency
Consider regional distribution of PGW and SGW as opposed to cross-country location
Ideally both should be co-located
Use of IP network tools to trace and isolate the problem link/element
Match line modes/speeds between various network elements in the chain
Allocate proper bandwidth in the core network to support LTE peak data rates with several users
across several eNBs
o
o
Issue 2.0
Test Server
o Some of the considerations discussed earlier apply
Match line speeds/modes with the PGW/intervening switches/routers
Provision enough bandwidth (100 MB) between the PGW and the server to allow high
data rates with multiple users
Minimal hops/latency to the PGW
o
Server should be capable of staging multiple FTP sessions

Windows Server Edition is a good choice
Test UE
o Test with known/well calibrated terminals
Use of internal antennas for test consistency
Makes sure UE is not close to the laptop or on the ground of the van
Ensure no impact on throughput due to LLDM logging
Client
o Configure protocol stack parameters to optimize throughput performance
During RF optimization
Place UE away from the client laptop through USB cable
Do not plug UE directly in USB of client
Do not put UE on touchpad of Client laptop
o
Some recommended settings:

TCP window size: 512kbytes for DL/UL bi-directional
TCP window size: 1MB DL to achieve high single user DL TCP throughput
IP Header/VJ compression: off
Selective Ack: on
TCP Time stamping: off
Use Windows XP client
Use well compressed binary files for FTP testing

Binary mode for data transfer
5.16 Antenna Down Tilt Adjustment

o The optimal tilt angle depends on:
Base station height
Vertical beam width
Site spacing
9/2/2011
Page 19 of 225
RF-E346
Issue 2.0
Figure 5 Antenna Beam

The following situations can be used to justify or recommend mechanical down tilt to the customer
5.16.1 Pilot pollution
Figure 6 Pilot Pollution
The circled areas are pilot polluted areas that lead to drop calls. Pilots need to be controlled to create one or
two dominant pilots. Preference would be to control the pilot through antenna physical change such as
mechanical down tilts and electrical tilt
9/2/2011
Page 20 of 225
RF-E346
Issue 2.0
Figure 7 Dropped Call caused by Pilot Pollution

5.16.2 Overshooting Cell
Figure 8 Overshoot
Cell id 12 is overshooting beyond its coverage area into a neighbor cell causing interference. Signal can be
controlled through physical down tilts.
9/2/2011
Page 21 of 225
RF-E346
Issue 2.0
Overshooting Cell contributing to low throughput and drop call
Figure 9 Overshoot Impact on RSRP
Figure 10 Overshoot Impact on Throughput
9/2/2011
Page 22 of 225
RF-E346
Issue 2.0
Figure 11 Overshoot Impact on Drop Call
5.17 IRAT
5.17.1
1.
2.
3.
4.
5.
IRAT Test Preparation Procedure:

Make sure that all parameters for LTE to eHRPD are reviewed
Define LTE to UMTS/eHRPD border route and agree with the customer
Test the UE in LTE only to make sure it works in LTE
Test the UE in UMTS/CDMA only to make sure it works in UMTS/CDMA
Configure the Communication Module to GMSS
5.17.2 IRAT Test Execution Procedure:

Open LLDM for LTE and QXDM for eHRPD/UMTS on the same laptop
9/2/2011
Page 23 of 225
RF-E346
Issue 2.0
Figure 12 LLDM and QXDM

1.
2.
3.
4.
5.
Attach in LTE
Check IP assignment (make a note)
Start DL UDP or FTP
Gradually drive towards the eHRPD/UMTS coverage area (away from LTE signal)
Look for Measurement Report (MR) followed by RRCConnectionRealease on LLDM (This inicates HO to
eHRPD/UMTS)
6. On QXDM you will see some activity monitor Pilots sets and HDR Power
7. Check for successful IRAT by looking at [RRC Connection Release Other, Redirected Carrier info (EUTRA: NA, Fdd 4415, Tdd: NA] on signal log message
8. IRAT fails if you see [RRC Connection Release Other, Redirected Carrier info (E-UTRA: NA, Fdd:NA,
Tdd: NA]
Figure 13 Messages collected by UE
9/2/2011
Page 24 of 225
RF-E346
Issue 2.0
5.17.3 Measuring LTE->UMTS/eHRPD HO interruption time using WiReshark

(start capture packets in non-promiscuous mode)
1.
2.
3.
4.
Call is up on LTE active DL data transfer (UDP or FTP)

HO to UMTS/eHRPD, wait until data transfer Resumes before you stop the logging
Take a note of the timestamp where MR was sent Signal Log Messages on LLDM
Eye-ball around that timestamp on wireshark (make sure you have the right display format for time from
view -> Time Display Format -> Time of Day (ctrl-Alt+2)
5. Take the difference between the packet timestamps for the particular protocol type (UDP or FTP, ICMP)
that you used during data transfer
Figure 14 IRAT Handover Messages
5.17.4 Idle LTE- eHRPD/UMTS Handover

1.
2.
3.
4.
5.
6.
Attach on LTE
Check IP assignment (make a note)
Start pinging your test server (e.g. 10.203.9.200)
Stop pinging (make sure the UE goes idle)
Gradually drive towards the UMTS/eHRPD coverage area (away from LTE signal)
Make sure LTE signal is lost and you have UMTS/eHRPD check your IP
To make sure that UE goes idle use Wireshark to verify

9/2/2011
Page 25 of 225
RF-E346
Issue 2.0
1. ipconfig identify the IP address of the PPP link, e.g 10.212.130.211, and gateway IP 10.212.130.209
2. route delete 0.0.0.0 mask 0.0.0.0 10.212.130.209
The above step will stop Client Laptop from sending DNS queries. If you have a need for accessing specific
server you can always add the route to that server by
3. route add 10.203.9.200 mask 255.255.255.255 10.212.130.211
4. Use route print to verify your new routing table
6
6.1
Data Collection Kit Configuration

Kit Configuration
Figure 15 LTE Kit Configuration
6.2 PC Configuration
Data Laptop Configuration
The UE will interface with a data laptop to support applications such as pings, FTP, UDP data transfers
The laptop should be configured per the recommended parameters to optimize performance and provide
an appropriate comparison to existing data.
These recommendations include:
o Windows 2000 Professional or Windows XP editions
o IP header compression turn OFF
o PPP software compression OFF
o 512kbytes TCP window size downlink/uplink bi-directional traffic
o MTU of 500bytes
o No background application to steal Throughput, such as:
Windows automatic updates
Lucent Tunneling software
9/2/2011
Page 26 of 225
RF-E346
Issue 2.0
Real Player updates

Downloads of various ads could occur in background windows after web browsing
Make sure these types of programs are not running while testing
7
Naming Convention
The names and Numbers of Markets, and Clusters shall be discussed with and agreed by the customer.
An example of the Naming Convention is as follows:
File Names:
A separate log file will be output for each device. The log files should be named based on
the Cluster naming convention and should include the device identity conforming to
certain numbering scheme. An example of the file name creation is as follow:
Generic File name: AAAA_B_C_D_E_(timestamp).F.nmf
Where
AAAA = submarket code
B = cluster number
C = super cluster number
D = band indicator (7=700MHz, A=AWS)
E = LTE Bandwidth (5M=5MHz, 10M=10MHz)
(timestamp) = Nemo logic for timestamp at the start of logging

F = Device number (1,2,3,4 or 5)
For example, a drive conducted in the WABA submarket, cluster 18, super cluster 4, in the
700MHz band and with 10MHz bandwidth will have associated logfiles in the following
format:
LTE
LTE
LTE
LTE
Device 1
Device 2
Device 3
Scanner
WABA_18_4_7_11Mar16
WABA_18_4_7_11Mar16
WABA_18_4_7_11Mar16
WABA_18_4_7_11Mar16
UMTS/GSM Scanner
8
8.1
114524.1.nmf
114524.2.nmf
114524.3.nmf
114524.4.nmf
WABA_18_4_7_11Mar16 114524.5.nmf
How to set up and use LG Adrenalin UE

LG Adrenaline Tips
Adrenaline LED
Figure 16 LGE Adrenaline LED
9/2/2011
The Y-USB cable is used to ensure sufficient power to the UE (especially in poor coverage)
Page 27 of 225
RF-E346
Issue 2.0
Figure 17 Adrnaline Y-USB Cable
Remove the back cover to insert the SIM card.
Figure 18 Adrenaline with cover removed
8.2
Useful AT Commands
If you want to disable auto-attach, then you can use the AT COMMAND at%proc=0,1 via HyperTerminal
If you want test as LTE only mode, then you can use AT COMMAND at%ratmode=4,4 via
HyperTerminal This AT COMMAND should be typed every each time when you plug in the AD600 and
execute LG CM
If you want test as 3G only mode, then you can use AT COMMAND at%ratmode=2,2 via
HyperTerminal This AT COMMAND should be typed every each time when you plug the AD600 and
execute LG CM
If you execute LG CM without any above procedure, device runs as dual RAT mode
If you want test as PS only attach mode, use AT COMMAND at+cemode=0 via HyperTerminal
If you want test as CS/PS combined attach mode, use AT COMMAND at+cemode=2 via HyperTerminal
Using IPerf and WINDS
11.1 IPerf
IPERF: Background
Iperf is a commonly used network testing tool that can create UDP and TCP data streams and measure
the Throughput of a network that is carrying them.
It has client and server functionality; and it can measure the Throughput between the two ends either
unidirectional or bi-directional.
It is an open source software; and it runs on various platforms including Linux, Unix and Windows
When used for testing UDP capacity, iperf allows the user to specify the datagram size and provides
results for the datagram Throughput and the packet loss
Typical iperf output contains a time stamped report of the amount of data transferred and the Throughput
measured
Iperf reports bandwidth, delay, jitter, and datagram loss
9/2/2011
Page 28 of 225
RF-E346
Make sure iperf program is installed on your PC and Server
Execute iperf from where the program resides
Issue 2.0
Iperf software can be obtained from www.iperf.com

Install the program on the client pc and also on the server
You can vnc into the iperf server and execute iperf commands whilst you are sending in the test van or you will
need a dedicated person (SAM engineer) to help you execute iperf command on the server side
Iperf setup
Figure 19 IPerf Setup
Here is a diagram where iperf is installed on linux and microsoft windows machines.
Linux is used as the iperf client and windows as the iperf server. Of course, it is also possible to use tow linux
boxes
Iperf Execution Command
Downlink
o At the server, execute the following (Transfer Command)
$iperf c <UE IP AddRess> -u b 60M t240 l1400
o At the client, execute the following (Listen Command)
C:\iperf s u
Uplink
o At the server, execute the following
C:\iperf c <Server IP AddRess> -u b 30M t240 l1400
o At the client, execute the following
$iperf s u
c = client
s = server
u = udp
t = time(s)
b = bandwidth
l = payload
By default iperf uses TCP/UDP port 5001, so make sure its not blocked. This is an example
9/2/2011
Page 29 of 225
RF-E346
Issue 2.0
By default, iperf fling TCP packets over your wires as fast as possible. A bi-directional test, which is the d option,
runs both ways:
alex@uberpc:~$ iperf c <server ip address> -d
Iperf can test multi-cast performance by running several servers listening on your multi-cast address:
$ iperf su B 10.10.0.112
$ iperf su B 10.10.0.112
$ iperf c 10.10.0.112 u b 512k
Youll want to set the b value to a speed appropriate for your network, and use your own multi-cast IP address
You may use your own files for testing throughput on compressed and uncompressed files by specifying the
filenames on the client:
$ iperf c 10.10.0.112 F [filename]
Testing UDP
aanokye@linux:~$ iperf su
alex@uberpc:~ $ iperf c 10.10.0.112 u
[ 3] 0.0-10.0 sec
1.25 Mbytes
1.05Mbits/sec
0.003 ms
0/
893 (0%)
Why is UDP so slow ? Because iperfs default is 1.0 Mbits/second, so its not a network problem. We can try some
different values to see what happens. Lets tell it to use all available bandwidth:
aanokye@linux:~$ iperf su
alex@uberpc:~$ iperf c 10.10.0.112 u b 100m
[ ID]
Interval
Transfer
Bandwidth
Jitter Lost/Total
[ 4]
0.0-10.0 sec
113 Mbytes
95.0 Mbits/sec 0.008 ms
544/81389 (0.67%)
[ 4]
0.0-10.0 sec
1 datagrams
received out of-order
This is very good speed, and 0.67% datagram loss is insignificant. Thats a good clean connection.
The below example whales on your line by sending 200-byte datagrams at 100 Mbits/second:
aanokye@linux: ~$ iperf su I 1
alex@uberpc:~$ iperf c 10.10.0.112 u l 200 b 100m
[ 3]
0.0-10.0 sec
106 Mbytes
88.9 Mbits/sec 0.219 ms
The i option generates a progRess display every second.
2683/187644
(1.4%)
9.1 WINDS
Winds (Wireless IP Network Data Source) _ Background
Application instances reside on the client and server
Client side can invoke/control both upload and download
Single server instance can support request from multiple clients
Key Parameters:
o Transmission
9/2/2011
Page 30 of 225
RF-E346
Issue 2.0
o Packet Length
o Test Duration
o Server Destination
The Three types of Test that WINDS can perform are:
o UDP Test
o FTP Test
o Ping Test
Winds Configuration
Winds comes packaged with an installer, and must be installed on every laptop/client that is intended to
operate WINDS on as well as the server to which these client will communicate
Install the package and make the appropriate choice to use application run as a wireless terminal. This
can always be changed by the settings:Configure->adapter
Figure 20 Configure Server / Client Proterties
The next step is to configure the adapter: select configure->adapter. The following screen will appear
Click on New and assign a name to each adapter to be used for testing
Figure 21 Configure Adapter Properties
The final step is to configure the logging options. Select configure->logging. The following screen will
appear
9/2/2011
Page 31 of 225
RF-E346
Issue 2.0
Figure 22 Configure Logging Properties
Select the appropriate directory to log the files. This only needs to be specified if Enable Logging is
checked. Select the level of detail required for the logging and the periodicity for the periodic logs.
Periodic log interval is only applicable to UDP test. FTP test always has one-second
Running UDP Test Downlink

There must at least be one instance of the application running on both the server and the wireless terminal. This
wireless terminal may then either Request (Downlink) or Send (Uplink) data to the server. This may be done by
selecting Transfer->Request-> or Transfer->Send Respectively on the wireless terminal
Figure 23 WINDS
9/2/2011
Page 32 of 225
RF-E346
Issue 2.0
Figure 24 WINDS Request

Running UDP Test Uplink
Sending data over the uplink to the server is considerably simpler to configure. The transfer maybe initiated at the
wireless terminal by selecting Transfer->Send, or by selecting the indicated icon on the toolbar below
Figure 25 WINDS Request (2)
9/2/2011
Page 33 of 225
RF-E346
Issue 2.0
Figure 26 WINDS Send

Configuration of Winds FTP
Wireless terminal may open an FTP Test window by selecting Transfer->FTP or by selecting the indicated icon in
the tool bar
Figure 27 WINDS Tool Bar
9/2/2011
Page 34 of 225
RF-E346
Issue 2.0
Figure 28 WINDS FTP

FTP TASK
In the middle of the FTP window, there is a task list control, which allows users to create tasks to be done in a
test. To add a new task, simply right click in the task list to show a pop-up menu, and then select the desired task.
Figure 29 WINDS FTP

The following table shows description of each task
Task
Description
Get
Download a file from FTP server. The on-going transfer will be aborted when the timer expiRes
Put
Upload a file to FTP server. The on-going transfer will be aborted when the timer expiRes
Redo
Redo the previous Get or Put task until the timer expiRes. Redo has no effect on other tasks
Pause
Do nothing until the timer expiRes
Connect
Dial up the connection
Disconnect
Hang up the connection
Restart
Restart the previous tasks
Running FTP TEST
9/2/2011
Page 35 of 225
RF-E346
Issue 2.0
When Start button is clicked, the test starts henceforth. On the task list, the current task will be highlighted. The
fields such as (Elapsed Time), Size, %, and Rate will be updated every second. The Avg. field shows the average
throughput of successful transfers, and is updated every time a transfer is finished. The Count field shows the
number of times this tasks has been executed
The status monitor at the bottom of the window will show FTP commands and replies passed between WINDS
and the FTP server, as well as error warnings and informative messages
Configuration of Winds PING

Ping is usually used for checking if a remote host is Responding or measuring round-trip latencies between the
hosts. In wireless data network, it can also be used for waking up an access terminal from dormant mode
Figure 30 WUNDS Tool Bar
Figure 31 WINDS Ping

Running Winds PING TEST
When Start button is clicked, the test starts henceforth. On the lower part of the window, there are several fields
showing the status of the on-going test
9/2/2011
Page 36 of 225
RF-E346
10
Issue 2.0
How to set up and use LLDM to collect drive test data
10.1 LLDM (LGE Logging Diagnostic Monitor) Introduction
10.1.1 What is LLDM?
LLDM is a Diagnostic Monitor for logging and analyzing over-the-air network system performance and
parameters. It is used only for LG UEs.
10.1.2 Components:
PC Side
o LLDM Host (Measurement Tool): logs and analyzes real-time diagnostic and measurement data
LTE UE Side
o LLDM Agent: collects diagnostic and measurement data and transfers to LLDM
10.1.3 Target Systems
LTE
CPU
RAM
Video
Operating System
Interfaces
Description
Pentium IV 1.8 GHz~
512MB ~
1024 * 768 ~
Windows XP Professional
USB 2.0 High Speed
Figure 32 LLDM Operation Environment
9/2/2011
Page 37 of 225
RF-E346
Issue 2.0
10.2 Installation
10.2.1 Required H/W and S/W
LLDM is designed to be installed and run on a PC running Microsoft Windows XP
10.2.2 Installing LLDM
Execute DM Setup file

License Agreement
Figure 33 License Agreement Dialog
Select Component to install
9/2/2011
Page 38 of 225
RF-E346
Issue 2.0
Figure 34 Select Component to Install
Figure 35 Choose Install Location Dialog
9/2/2011
Page 39 of 225
RF-E346
Issue 2.0
Figure 36 Installing Dialog
10.3 License Key activation

If this is the first time to use LLDM, you may need license file to run LLDM. Please follow the steps below to get a
license file. If you already have the valid LLDM license file, you may skip this section. Otherwise, please go on to
the next step
9/2/2011
Page 40 of 225
RF-E346
Issue 2.0
10.3.1 Step 1
Figure 37 LGE_LLDM_PcSerialChecker
10.3.2 Step 2
Figure 38 PC Serial Number

10.3.3 Step 3
User should copy this ID in a clip board, and paste it into an email. Then please forward it to a person in charge.
(Bean, Vern)
After you receive the license file (named NETIMIZER.LIC), please copy it to the LLDM installation folder (i.e.;
C:\Program Files\LGE\LLDM).
Normally, the license file expires after a certain period of time, which depends on the license agreement. As long
as the license file is valid, you may upgrade the new LLDM if you get one. Thus please backup your own license
file into a safe folder.
9/2/2011
Page 41 of 225
RF-E346
Issue 2.0
10.4 Operation
10.4.1 Setup Menu
Figure 39 Setup Menu

10.4.1.1 Set Com Port
Choose LLDM program from {Start -> Programs -> LLDM} Menu and run LLDM.
Make sure LTE UE is running and USB cable is connected properly
Port Setting
o Select [Setup -> Set Com Port] in LLDM
o Click CH1 check box
o Set Port number (LTE USB Modem Port Number). If LTE UE is connected with LLDM through
USB, LTE USB Modem Port is appeared in Device Manager
o Set Baud Rate, Flow Control like the below picture
o Click Log Mask Icon to select items to be transmitted from LTE UE
o Click OK button
9/2/2011
Page 42 of 225
RF-E346
Issue 2.0
Figure 40 Port Setting
Port
Baud Rate
Flow Control
RTS
DTR
Log Mask
Description
LTE USB Modem Port
Baud Rate (115200 fixed)
Flow Control Type (None, Hardware,
Software type)
RTS (Request To Send)
DTR (Data Terminal Ready)
Only the log data items you choose in Log
Mask Setting Tree View are collected at
LTE UE side and sent to LLDM
The connection status of COM port can be checked on the status bar. When COM port is connected correctly
R(115200) will be appeared like the following picture.
9/2/2011
Page 43 of 225
RF-E346
Issue 2.0
Figure 41 Port Connection Status
10.4.1.2 Logging Mask

Only the log data items you choose in Log Mask Setting Tree View are gathered at LTE UE side and sent to
LLDM
9/2/2011
Page 44 of 225
RF-E346
Issue 2.0
Figure 42 Log Mask Setting Dialog
10.4.2 Information Menu
9/2/2011
Page 45 of 225
RF-E346
Issue 2.0
Figure 43 Information Menu
10.4.2.1 Logging Status

You can start/stop/pause/resume logging and monitor logging status in the Logging Status Dialog. When you
start logging, only log data items you choose in log mask setting tree view are logged into a log file
Figure 44 Logging Status Dialog

Item
Logging status
Log start time
Elapsed time
Log file name
Log file size
Received logs
Start
9/2/2011
description
Current logging status
Time that logging was started
Elapsed time from the log start time
Log file name
Log file size. (bytes)
Total received log number
Start the logging
Page 46 of 225
RF-E346
Stop
Pause
Resume
Issue 2.0
Stop the logging

Pause the logging
Resume the logging
When logging starts, LLDM automatically determine the name of logging file based on logging start time
10.4.3 Replay Menu
Figure 45 Logging Status Dialog
10.4.3.1 Load Replay Menu

Load a file you want to replay in LLDM
Figure 5-8: Select Log file Dialog

9/2/2011
Page 47 of 225
RF-E346
Issue 2.0
1.1.1.Replay Toolbar
After you load a file, you can see a Replay Tool like the following picture
Figure 46 Replay Toolbar
10.4.4 Exit Menu

When you want to exit LLDM click Exit menu
Figure 47 Exit Menu
10.4.5 Tree View Menu

To show Tree View, Move mouse point to left side in the LLDM main window
9/2/2011
Page 48 of 225
RF-E346
Issue 2.0
Figure 48 Tree View Menu
10.4.6 Layer 1 Menu

L1 menus consist of command and log items. L1 command items are intended for L1 single test without
protocol stack. Do not try to use L1 command items when UE Configuration menu in Protocol stack is enabled.
L1 log items can be displayed without any Restriction if each item log mask is enabled
Figure 49 Layer 1 Menu
9/2/2011
Page 49 of 225
RF-E346
Issue 2.0
Cell Information displays neighbor cell lists which are collected from the searcher and measurement module.
The cell information provides DL frequency, Frame boundary and RSRP value for all of cell in neighbor cell list
with detected cells, also history of RSRP of each cell is described by graph window.
Figure 50 Cell Information
10.4.6.1 Wide- Band CQI Information

The wideband CQI information shows measured CQI of wideband in the UE under the assumption of the
configuration of aperiodic CQI. It simultaneously shows CQI for rank1, rank2 of codeword 0 and 1 as well as
PMI for each. User can enable or disable the display of wide-band information by clicking the check-boxes in
the GUI. The rank information shows average of rank in the UE. The UE sends a rank, 0 or 1, according to
measured propagation condition. The DM shows an instant value of rank as well as average value. This
average is Reset when the Reset button is pressed.
9/2/2011
Page 50 of 225
RF-E346
Issue 2.0
Figure 51 CQI and Rank Information
10.4.6.2 Serving Cell Quality Information

The serving cell quality information shows SNR of reference signal (RS SNR) and received power of
reference signal (RS RSSI).
Figure 52 Serving Cell Quality Information
10.4.7 Cell Information

The CFI Information shows frequency counts for detected CFI during 1sec. It displays not the direct CFI value
but that of CFI index is displayed. The CFI index corresponds to the actual control symbol length of PDCCH
index pt PDCCH symbol length is given by:
User can enable or disable the display of that information by clicking check-boxes in the GUI
10.4.7.1 PDSCH PHY Throughput

This shows how much to get the downlink data in 1sec. This unit is Mbps.
First row: PDSCH PHY Total Throughput
Second row: PSSCH PHY Codeword0 Throughput
Third row: PDSCH PHY Codeword1 Throughput
9/2/2011
Page 51 of 225
RF-E346
Issue 2.0
Figure 53 Throughput
10.4.7.2 PDSC H BLER (Block Error Rate)
PDSCH BLER displays the ratio of transport blocks that get CRC_NAK over the total received transport
blocks. The unit is percentage
First row: PDSCH Total BLER
Second row: PDSCH Codeoword0 BLER
Third row: PDSCH Codeworkd1 BLER
Figure 54 Block Error Rate

10.4.7.3 PDCCH Detection Rate
UE cant calculate PDCCH BLER because UE doesnt know when eNodeB sends its PDCCH. In other words,
UE detects PDCCH blindly. So, UE DM supports this item similar with PDCCH BLER. This item displays how
much detects PDCCH (each DCI format) for 1 second. That is, it displays amount, not percentage (ratio)
10.4.7.4 PUSCH PHY Throughput

UL Throughput log shows the uplink data throughput at UE side. The types of information are transferred to
the DM. One is the number of bits in new transmission only. The other is the number of bits in all transmission
including new transmission. The new transmission information reflects the true transmission rate.
9/2/2011
Page 52 of 225
RF-E346
Issue 2.0
Figure 55 PDSCH Throughput

10.4.7.5 LOGMASK
The following is a sample log mask. Please use log mask attributes to collect data for all test cases. This log
mask has been verified by the eDAT Tool team.
9/2/2011
Page 53 of 225
RF-E346
9/2/2011
Issue 2.0
Page 54 of 225
RF-E346
Issue 2.0
Figure 56 Log Mask

10.5 How to use LLDM
a. Click on start-, click on All program, click on LLDM and hit <enter>
Figure 57 Activating LLDM

b. The following views should be opened for data collection for stationary test execution:
i. CH1 Multipath Information (tracks serving cell id that Ue is camp on)
9/2/2011
Page 55 of 225
RF-E346

ii.
iii.
iv.
v.
c.
Issue 2.0
CHI L1 Control (checks whether Ue power is fixed or power control is turned on)
CH1 Signal Log Message (checks RRC and NAS signaling between UE and eNdoeB)
CH1 L1 Graph (visual Downlink information received by UE)
Logging Status (gives logging information such as log start time and log start end)
Set the port by clicking on the icon for the port setting, port setting submenu would pop up>check on CH1 among the CH list

d. Click on Device Manager icon->Device Manager submenu would pop up->open up the
modem on the list-> right click on the LTE LGE USB Modem-> note the com port assigned and
assign to the port to the device
9/2/2011
Page 56 of 225
RF-E346
Issue 2.0
Figure 59 Port Setting (2)

e. Set up the GPS by clicking on GPS tab as indicated
Figure 60 GPS Set Up

f.
9/2/2011
Set up log mask using predefined log mask. Click on log mask icon; log mask sub menu would
pop up
Page 57 of 225
RF-E346
Issue 2.0
Figure 61 Port Setting (3)

g. Click on load on sub menu view, pick pre-defined log mask of choice and click ok
Figure 62 Select Pre-defined Log Mask

h. To make a call, click Go to start, Click on LGE LT CM icon; LG Communication Manager would pop
up. Make sure LTE signal bar shows up and click on Connect
9/2/2011
Page 58 of 225
RF-E346
Issue 2.0
Figure 63 Use Connection Manager to Connect
I. UE would synchronized with eNodeB and start the attach process
Ue synchronized
with eNB
Successful
Attach
Figure 64 Attachment Process

j. Monitoring Test Progress on L1 Signal Graph
9/2/2011
Page 59 of 225
RF-E346
Issue 2.0
Figure 65 Signal Graph
K disconnect the Ue when test is done
Successful
detach
l. Handover Mobility View (The following view should be monitored when cluster drive testing_
a. Signal Log Message (track RRC/NAS signaling between UE and eNodeB)
b. CH1 Radio Problem Cause (time stamp and radio failure log attributes)
c. CH1 Cell Information (tells what UE is synchronized and what neighbor eNodeBs monitored)
d. CH1 Handover History (gives Results of successful/failure handover between source and target cell
e. CH1 Neighbor cell list 2 ( gives serving cell and associated neighbor cell list for intra/inter frequency
f. CH1 Signal Graph (allows to monitor progress testing)
9/2/2011
Page 60 of 225
RF-E346
Issue 2.0
Figure 66 Handover View
11
How to set up and use NEMO to collect drive test data
Note: Adrenaline is a LG UE. The steps described below are applicable for other LG UEs.
11.1 Getting Started
o
Physical connections
Insert USB hub and USB GPS to laptop
Insert Nemo USB dongle into hub
Insert SIM card into UE and connect to USB hub
o
o
Upon inserting the Adrenaline, this may be recognized by the toolkit laptop as an external drive or
removable storage; and you may have to install Communication Manager.
Ensure that the Adrenaline LED is illuminated
o
o
Query the modems to ensure that the UE is communicating with the laptop
Verify you can make calls using LG Communications Manager and can connect to the internet
11.2 NEMO Outdoor

11.2.1 OPEN NEMO OUTDOOR
9/2/2011
Load your workspace (ALU-at&t-LTE is the ALU RF Tools Lab workspace)

Verify that your hardware is displayed
Ensure that your device configuration is loaded
Press start devices
Page 61 of 225
RF-E346
Issue 2.0
Figure 67 - Nemo Outdoor 1st Prompt
Nemo Outdoor tool opens

o Device status indicator should be flashing green
o Device state should be: Device is started
Figure 68 - Nemo Outdoor Main Screen
11.2.2 VERIFY YOUR SCRIPT SETTINGS

Note: Scripts are pre-defined for all the drive teams.
11.2.2.1 Check UE1 Settings (Iperf):
9/2/2011
Click on the device settings button of UE1 (Red exclamation point)
Page 62 of 225
RF-E346
Issue 2.0
Select Script Properties

Ensure that the correct script is loaded for the Iperf test
Press the Script Editor button
Click on each line in the test sequence and verify the specific market/network settings
Figure 69 - Verify Iperf Scripts in Nemo Outdoor
11.2.2.2 Check UE2 Settings (FTP)
9/2/2011
Click on the device settings button of UE2 (Red exclamation point)

Select Script Properties
Ensure that the correct script is loaded for the FTP test
Press the Script Editor button
Click on each line in the test sequence and verify the specific market/network settings
Page 63 of 225
RF-E346
Issue 2.0
Figure 70 - Verify FTP Scripts in Nemo Outdoor
11.2.2.3 Check UE3 Settings (Ping)

o Click on the device settings button of UE3 (Red exclamation point)
o Select Script Properties
o Ensure that the correct script is loaded for the Ping test
o Press the Script Editor button
o Click on each line in the test sequence and verify the specific market/network settings
Figure 71 - Verify Ping Scripts in Nemo Outdoor
11.2.3 CONNECT YOUR SCANNERS
9/2/2011
Note that PCTEL scanners have a known problem that causes them to be non-responsive in various
drive test tools (including Nemo-Outdoor)
o You will have to follow a specific sequence of events and rely on power-cycling the scanners
o A scanner is non-responsive when you cannot detect it in Nemo-Outdoor (note that the
scanner may still be visible in Windows Device Manager)
With Nemo-Outdoor open
o Power-cycle your scanners (i.e. physically disconnect the DC power cable)
o Unplug/Re-plug from the laptop (i.e. physically unplug the USB cable)
o Verify that the scanners are removed from Windows Device Manager and that they re-appear
after power-cycle and reconnecting to the USB ports
Page 64 of 225
RF-E346
Issue 2.0
Figure 72 Windows Device Manager (PCTEL Scanner)
Configure your scanner settings for your market-specific conditions and for the type of testing that you
will be performing (Refer to the overview of PCTEL scanner settings section)
11.2.4 SCANNER(S) BECOME NON-RESPONSIVE
o
o
o
o
o
The PCTEL scanners are known to enter a non-responsive state occasionally (most often when
restarting the drive test tools like Nemo Outdoor).
Note that the PCTEL scanners do not become non-responsive while Nemo Outdoor is in normal
operation in Online mode (i.e. your testing will not be impacted)
Your scanner is non-responsive when Nemo-Outdoor will not allow you to go into Online mode
A non-responsive scanner may also prevent the laptop from shutting down in which case you simply
need to disconnect the scanner from the laptop
If Nemo-Outdoor generates errors stating that the scanner failed to start when trying to enable Online
mode:
Select Work Offline
Disconnect the USB cable from the laptop
Disconnect the scanner DC power cable so that it is off
Reconnect scanner power cable, and connect scanner USB back to laptop
Enable Online mode in Nemo-Outdoor again
Figure 73 Non-responsive PCTEL Scanner prevents Nemo-Outdoor from going online
Figure 74 PCTEL Scanner is non-responsive
9/2/2011
Page 65 of 225
RF-E346
Issue 2.0
11.2.5 NEMO-OUTDOOR: WORK ON-LINE
o
o
Click on the button to enable Online Mode (i.e. start the devices)
Device status indicator should be flashing green
Device state should be: Device is started
Figure 75 Nemo-Outdoor with Online mode enabled
Ensure that your GPS is working in Nemo Outdoor

o Refer to the GPS Information screen to ensure that you are receiving adequate GPS data
Figure 76 - Verify GPS in Nemo Outdoor
11.2.6 NEMO OUTDOOR TIPS

To record data:
o Press the Start/Stop Scripts button to start the scripts & to start recording data
9/2/2011
Page 66 of 225
RF-E346
Issue 2.0
Figure 77 - Record & start scripts in Nemo
Press the Start Recording button if you want to start recording without executing the scripts
Figure 78 - Starting scripts without recording
Collected data is stored in the default folder: C:\Nemo Tools\Results
Devices are numbered by Nemo Outdoor and use this number to identify the device within Nemo
Outdoor (i.e. throughout multiple views or in the naming of the collected drive test files)
Figure 79 - Device identification in Nemo
9/2/2011
Page 67 of 225
RF-E346
Issue 2.0
Figure 80 - Device identification in the Nemo results
You can change the global Nemo Results file naming convention
o Go to the Configuration Manager (in the standard tools lab configuration this is available in the
Setup tab) or you can click on View Configuration Manager
o From within Configuration Manager, select Measurement Properties Rt-click Select
Properties
Figure 81 - Configuration Mgr Properties
9/2/2011
Page 68 of 225
RF-E346
Issue 2.0
Figure 82 - Configuration Mgr through View Menu
o
o
Within the User Interface Properties, select the Measurement tab

You can edit the Filename structure
Figure 83 - User Interface Properties: Measurement tab
9/2/2011
Page 69 of 225
RF-E346
Issue 2.0
Figure 84 - Edit the global naming structure
The results files (in C:\Nemo tools\Results) now reflect your global name change
Figure 85 - Results files reflect changes in naming convention
The naming convention is defined in the Naming Convention section. An Example is as follows:
UE1 - Iperf (Long Call)

UE2 - FTP (Short Call)
UE3 - Ping (Latency)
SMKT_Cluster#_SuperCluster#_Band_BW:
SMKT - Sub market code
Cluster# - Regular cluster number
SuperCluster# - Super cluster number in which the regular cluster located
Band - Frequency band like 700MHz or AWS
BW - LTE channel bandwidth like 10M or 5M

Example:
NYCX_6_2_7_10M_LC1.nmf (Long Call)
9/2/2011
Page 70 of 225
RF-E346
Issue 2.0
NYCX_6_2_7_10M_SC1.nmf (Short Call)

NYCX_6_2_7_10M_LT1.nmf (Latency
Nemo Outdoor is set up with multiple tabs/Groups

o Click on a tab/Group to view the content displayed in real time
o You can also access the various tabs/Groups by clicking on View View Groups Select the
tab/Group that you wish to view
Figure 86 - Nemo Outdoor Groups (tabs)
Figure 87 - Access the various groups (tabs) from the View menu
You can add your own tab/Groups by right-clicking in the Group bar and selecting Create New
Figure 88 - Creating a new group (tab)
9/2/2011
You can add/create additional views

If the existing views do not display the data that you are trying to see in real-time, simply open
a new view by clicking on the parameters tab in the right-hand side. This reveals the hidden
Parameters menu.
You can drill down in the sub-menus to find your specific measurement or you can type your
desired measurement in the search box to filter accordingly
Page 71 of 225
RF-E346
Issue 2.0
Figure 89 - Selecting your own measurement views
9/2/2011
If the desired measurement has a mini-graph icon, you can double-click on the desired
measurement to open that specific view, otherwise you will have to assign the measurement to a
graph or grid
Page 72 of 225
RF-E346
Issue 2.0
Figure 90 - Description of mini-icon when adding your own measurement views
Figure 91 - Adding your own measurement view
9/2/2011
Page 73 of 225
RF-E346
Issue 2.0
11.3 ADRENALINE & USB HUB PHYSICAL CONNECTIONS
Figure 92 - Connecting Adrenaline UE to USB hub
Figure 93 - USB hub connections

11.4 TOOLS LAB ATT-LTE RF DRIVE TEST KIT CONFIGURATION
9/2/2011
Page 74 of 225
RF-E346
Issue 2.0
Figure 94 - ALU at&t-LTE Nemo RF drive test kit configuration (kit #3)
11.5 ADRENALINE RECOGNIZED BY LAPTOP
Upon inserting the Adrenaline, this may be recognized by the toolkit laptop as an external drive/removable
storage or may try to install AT&TCM
o The first step is to stop all processes/actions that the UE is trying to undergo
o To make the Adrenaline be recognized as a modem go to My Computer Right-click on LGE 3G
Mobile Select Eject Note that you will have to do this each time you insert UE
Figure 95 - LG Adrenaline as an external drive
9/2/2011
Page 75 of 225
RF-E346
Issue 2.0
Figure 96 - LG Adrenaline attempting to install AT&TCM
Figure 97 - Eject Adrenaline Removable Storage to show m
If drivers/firmware/software was changed, the toolkit laptop may undergo the process of detecting the LG
Adrenaline as a new device
Figure 98 - LG Adrenaline detected as new device
Device Manager detects the Adrenaline Modem & COM ports

o LGE Adrenaline COM ports are not set to s standard COM port number assignment in ALU RF Tools
Lab RF drive test kits as these are susceptible to change with changes in firmware/software and
drivers
o The user is responsible for identifying the COM ports associated with the specific device as they are
assigned by Windows XP
9/2/2011
Page 76 of 225
RF-E346
Issue 2.0
Figure 99 - Device Manager detects Adrenaline as a modem
11.6 HOW TO IDENTIFY COM PORT NUMBER ASSIGNMENTS
To identify the port number associated with a modem

o Device Manager Right-click on desired modem Select Properties
o Go to Modem tab to verify current COM port number
Figure 100 - Select Modem
Figure 101 - Verify current COM Port
To identify the COM port associated with a standard (non-modem) COM port
9/2/2011
Page 77 of 225
RF-E346

o
Issue 2.0
Open Windows device manager and note that the current COM port number is visible in Device
Manager
Figure 102 - Select COM Port
11.7 QUERY YOUR MODEM
Query the modem to ensure connectivity between the UE and the laptop
Right-click on LGE F1 LTE USB CDC Modem Interface
Select properties
Go to Diagnostics tab
Press Query Modem
Look for responses to the commands indicating connectivity between the UE and the laptop
Figure 103 - Query modems to verify connectivity to laptop
11.8 DRIVERS & SOFTWARE
Only use software and drivers that are approved by the ALU RF Tools Lab
o Do not load any non-approved applications or drivers!
Drivers and software can be downloaded from the ALU RF Tools Lab Web Site
o ALU RF Tools Lab: http://usnavsgtk01.ndc.lucent.com/rftoolslab/ (LTE section)
o Adrenaline drivers, communication manager, etc.
o Software tools (i.e. Nemo Outdoor, etc.)
11.9 ADRENALINE UE SOFTWARE UPDATES
Access to LGE Adrenaline AD600 firmware/software updates are only available to Alcatel-Lucent
employees
To obtain the latest ALU RF Tools Lab approved firmware/software and the associated update procedure,
open a CARES ticket with the ALU RF Tools Lab
o Please contact the CARES Hotline: 1-866-Lucent8. Prompt 1
o Inform the CARES agent of the following:
9/2/2011
Page 78 of 225
RF-E346
Issue 2.0
o
o
The product is RF Kits

Provide a contact number where you can be reached
State that you are requesting LGE Adrenaline AD600 software updates (i.e. the user
wants access to the AT&TAdrenaline AD600 upgrade site)
Ensure that you obtain a CARES AR number from the CARES agent for reference
Someone from the ALU RF Tools Lab will reply to your CARES AR with the following:
Access to the LGE Adrenaline AD600 SharePoint site
Procedure to update the LGE Adrenaline AD600 software/firmware
Software update tools
Latest ALU RF Tools Lab approved software for the LGE Adrenaline AD600
11.10 LGE ADRENALINE TIPS
Adrenaline LED
Figure 104 - LGE Adrenaline LED
The Y-USB cable is used to ensure sufficient power to the UE (especially in poor coverage)
Figure 105 - Adrenaline Y-USB cable
Remove the back cover to insert the SIM card
Figure 106 - Adrenaline with cover removed
12
How to use JDSU E6474A-X to collect Drive Test Data
9/2/2011
Page 79 of 225
RF-E346
Issue 2.0
Connect UE LG G13 to USB port of the Data Collector PC.

In the Data Collection PC, click Start, click All Programs, click JDSU wireless solutions, click E6474A-X
and click E6474A-X
In the E6474A window, click File, and click Project Manager to display Project Manager screen as in
Figure 107.
Figure 107 Project Manager
In the Project Manager window, click New Project icon

108.
to display the New Project window as in Figure
Figure 108 New Project

In the New Project window, supply a name for the project in the Name box, and click OK.
In the E6474A-X window, click Configuration, click Device Wizard.
In the Add Device Window, click Next, click LG LTE Device, click Next, check LGE LTE DM Port, and click
Scan
The Device Detected window will appear as in Figure 109.
9/2/2011
Page 80 of 225
RF-E346
Issue 2.0
Figure 109 Device Detected

Click Yes to complete the process.
In the Add Device Wizard window, click Finish
Start WINDS the same way as mentioned in section Error: Reference source not found.
To start logging, in the E6474A window, click the green Log Mode
icon. The icon will turn grey. In the
Drives window inside of the Project Manager window, you will see a new log file is being created.
To stop logging, in the E6474A window, click the red
button. In the Drives window inside of the Project
Manger window, you will see the start time and end time of the log file.
To export the data, in the Project Manager window, click the Project you want to export, and click the Export
Project
icon to display the Export Project window as in Figure 110.
Figure 110 Export Project

In the Export Project window, select the log file you want to export, and click OK to display Browse For
Folder window as in Figure 111.
9/2/2011
Page 81 of 225
RF-E346
Issue 2.0
Figure 111 Browse for Folder

In the Browse For Folder window, indicate the folder you want to contain the exported log file, and click
OK.
13 How to use JDSU Scanner
Procedure on how to configure the JDSU Scanner for the following: RSRP, PCI
and Interference Signals.
13.1 Activate JDSU E6474A-X
Two ways to open E6474A-X

-
Click Start, Click All Programs, Click JDSU Wireless Solutions, Click E6474A-X, Click E6474A-X
OR
Double Click on the Icon E6474A-X
on the desktop.
13.2 Creating a Project.

-
9/2/2011
Click File, Click Project Manager as in Figure 112. After selecting Project Manager it will open
the project manager dialog box as in Figure 113.
Page 82 of 225
RF-E346
Issue 2.0
Figure 112
Figure 113
9/2/2011
Click New Project Icon to create a New Project as in Figure 114.
Page 83 of 225
RF-E346
Issue 2.0
Figure 114
-
Enter a project name in the Name box: example, ATT LTE as in Figure 115.
Click OK to close.
Figure 115
9/2/2011
Note: The ATT LTE Project that was created as in Figure 116.
Page 84 of 225
RF-E346
Issue 2.0
Figure 116
13.3 How to add a receiver based measurement.

- First a receiver is attached and connected as in Figure 117.
- Right Click on Hardware, select Add Device as in Figure 118.
Figure 117
9/2/2011
Page 85 of 225
RF-E346
Issue 2.0
Figure 118
Under Devices, expand JDSU as in Figure 119.
Figure 119
9/2/2011
Back View of the scanner labeled W1314A E11 as in Figure 120.

Select the correct device, for our case, the JDSU Scanner Receiver is W1314A E11 as in
Figure 121. Then click OK.
Page 86 of 225
RF-E346
Issue 2.0
Figure 120
Figure 121
9/2/2011
Under Hardware, W1314A E11 Device that was just created as inFigure 122.
Page 87 of 225
RF-E346
Issue 2.0
Figure 122
Note: W1314A E11 device shows disconnected as in Figure 123.
Figure 123
9/2/2011
Page 88 of 225
RF-E346
Issue 2.0
13.4 Creating a Measurement

- Right Click on W1314A E11, select Add Measurement as in Figure 124.
Figure 124
Select the measurement set you want to add as in Figure 125.
Figure 125
9/2/2011
Under Measurements for W1314A E11, select LTE Channel Analyzer as in Figure 126, then
click OK.
LTE Channel Analyzer under W1314A E11 as in Figure 127.
Page 89 of 225
RF-E346
Issue 2.0
Figure 126
Figure 127
9/2/2011
Preselector Drop Down Menu as in Figure 128.

In the Preselector Drop Down Menu as in Figure 129, Select 698 MHz 806 MHz.
Page 90 of 225
RF-E346
Issue 2.0
Figure 128
Figure 129
13.5 Creating a Workspace

The Workspace contains user defined views and layouts. Workspaces let you manage the display of your
open views. You can create multiple workspaces and display any of your open views in each of the created
workspaces. The workspace tabs appears at the top of the interface, below the toolbars.
-
Right Click New Workspace to display a new workspace as in Figure 130.
Figure 130
9/2/2011
In the New Workspace pop up window, in the New Tab Name box, provide the name of your
workspace, and then click OK as in Figure 131.
Page 91 of 225
RF-E346
Issue 2.0
Figure 131
Rename Workspace 1 to PCI as in Figure 132.

New Tab Name: PCI, then click OK as in Figure 133.
Figure 132
Figure 133
9/2/2011
Page 92 of 225
RF-E346
Issue 2.0
Right Click, New Workspace.

New Workspace Window, create a New Tab Name for Interference Analyzer as in Figure 134. Then
click OK.
Workspace for Interference Analyzer as in Figure 135.
Figure 134
Figure 135
9/2/2011
Select PCI Workspace

Click View, Click Device Views, Click W1314E11, Click LTE Channel User List as in Figure 136.
View of the LTE Channel List Channel Power as in Figure 137.
Page 93 of 225
RF-E346
Issue 2.0
Figure 136
Figure 137
9/2/2011
Select RSRP Workspace

Click View, Click Device Views, Click W1314E11, Click LTE RO R1 RSRP User List as in Figure
138.
View of the LTE User List R0 and R1 RSRP as in Figure 139.
Page 94 of 225
RF-E346
Issue 2.0
Figure 138
Figure 139
9/2/2011
Select Interference Analyzer Workspace

Click View, Click Device Views, Click W1314E11, Click GSM Interference Analyzer Adjacent Channel as
in Figure 140.
Page 95 of 225
RF-E346
-
Issue 2.0
Click View, Click Device Views, Click W1314E11, Click GSM Interference Analyzer Co Channel as in
Figure 141.
View of the GSM Interference Analyzer for Adjacent Channel and Co-Channel as in Figure 142.
NOTE: If you are not collecting GSM Interference, minimize the windows for CPU cycles.
Figure 140
9/2/2011
Page 96 of 225
RF-E346
Issue 2.0
Figure 141
Figure 142
9/2/2011
Page 97 of 225
RF-E346
Issue 2.0
13.6 Probing the device (Connecting the device)

- Right Click on W1314A E11, select Probe Device as in Figure 143.
Figure 143
9/2/2011
IF JDSU RECEIVER SERIAL PORT IS NOT SET as in Figure 144.

Select OK
Page 98 of 225
RF-E346
Issue 2.0
Figure 144
Check USB Serial Port (COM22) for the Scanner COM Ports, select Retry as in Figure 145.
Figure 145
9/2/2011
W1314A E11 shows connected as in Figure 146.
Page 99 of 225
RF-E346
Issue 2.0
Figure 146
13.7 Checking your settings

-
Click on Icon for
Live Mode (not recording data) as in Figure 147.
Figure 147
9/2/2011
E6474 [Project] ATT_LTE Live Mode.
RSRP Workspace: LTE RO R1 RSRP User List as in Figure 148.
Page 100 of 225
RF-E346
Issue 2.0
Figure 148
E6474 [Project] ATT_LTE Live Mode

PCI Workspace: LTE Channel List Channel Power as in Figure 149.
NOTE: LTE Physical Layer Cell ID: 18 as in Figure 149.
Figure 149
9/2/2011
Page 101 of 225
RF-E346

-
Issue 2.0
Description of the LTE Channel List Channel Power from Agilent that shows the LTE Physical
Layer Cell ID as in Figure 150.
Figure 150
9/2/2011
E6474 [Project] ATT_LTE Live Mode
Interference Analyzer Workspace: GSM Interference Analyzer Adjacent Channel and CoChannel as in Figure 151.
Page 102 of 225
RF-E346
Issue 2.0
Figure 151
Select Red Icon to STOP recording as in Figure 152.
Figure 152
13.8 Opening a Project (eg. ATT LTE)
9/2/2011
Page 103 of 225
RF-E346

-
Issue 2.0
Click on Project Manager as in Figure 153.
Figure 153
Right Click on ATT LTE, select Set As Active as in Figure 154.
Figure 154
9/2/2011
Page 104 of 225
RF-E346
Issue 2.0
Note: AT&TLTE Template Project as in Figure 155.
Figure 155
13.9 Collecting data.

-
Click on the Icon
to collect the data as in Figure 156.
Figure 156
9/2/2011
E6474 [Project] ATT_LTE Record Mode as in Figure 157.
Page 105 of 225
RF-E346
Issue 2.0
Figure 157
13.10 How to export a project and associated drive test data.
Click on the Project Manager Icon as in Figure 158.
Figure 158
9/2/2011
Project Manager window, select ATT LTE.

Select the Export Project Icon as in Figure 159.
Page 106 of 225
RF-E346
Issue 2.0
Figure 159
Export Project Window, select which drive test you want to export, select OK as in Figure 160.
Figure 160
9/2/2011
Browse for Folder Window. Locate the folder that you want to use for the export project. It is
recommended that you use a unique name folder for each exported project. Select OK to
start the export process as in Figure 161.
Page 107 of 225
RF-E346
Issue 2.0
Figure 161
The export progress dialog box displays when the export is completed and if there were any
problems.
Select Close as in Figure 162.
Figure 162
9/2/2011
Exported project folder contains many files. These files contains information about property
settings, view layout and drive test data. For example the aod file contain the drive test
data as in Figure 163.
Page 108 of 225
RF-E346
Issue 2.0
Figure 163
14
How to use PcTel Scanner
15.1 Frequency Scanning - PCTEL GSM/UMTS Scanners

Frequency scanning can be used to scan band power. It is also useful for checking that the band is
clear and for finding out the center frequency.
1. After the scanner is connected and activated in Nemo Outdoor, open the Measurement
Properties dialog by selecting Measurement | <device> | General Properties.
2. In the Measurement Properties dialog, go to the Frequency scanning, UMTS page.
9/2/2011
Page 109 of 225
RF-E346
Issue 2.0
Figure 164 UMTS Frequency Scranning Properties

3. In the Channel style field, select the channel width. The options are narrow band (200kHz) and
wide band (3.84 MHz).
To find out the center frequency used, set the Channel Style to 200 kHz and select all
the channels in the frequency region where the carrier should exist; for example, all
channels allocated to an operator. The center frequency will stand out in Frequency
Scanning mode. The received signal should be above the noise level in order to find out the
center frequency.
4. Click the Select Channels button to open the Select Channels dialog
Figure 165 UMTS Frequency Scanning: Select Channels
9/2/2011
Page 110 of 225
RF-E346
Issue 2.0
5. How to The table displays the channel numbers, not the frequencies. If you know the frequency but
not the channel number, the channel number can be calculated by multiplying the frequency in MHz
by five. The channel spacing is always 200 kHz.
6. Remove channels from the Selected list by selecting a channel and clicking the Remove button.
7. Add channels to the Selected list by selecting a channel from the Available list and clicking the Add
button.
8. Click OK to return to the Measurement Properties dialog.
9. Click OK and OK to close the Measurement Properties dialog and to re-start the scanner with the
new settings.
10. A green light on the scanner Device Info window should start blinking. This means that the device is
working properly and scanning using the default settings.
11. Click the Start Recording button to start recording the results in an output file
14.1 Frequency Scanning - PCTEL EX LTE Scanner
1. After the scanner is connected and activated in Nemo Outdoor, open the Measurement Properties
dialog by selecting Measurement | <device> | General Properties. By clicking the Advanced
button on the General page, you will access the Advanced Properties dialog. Here you can
enable and disable the integrated GPS receiver. This means you will not need an external GPS
receiver in order to collect position data.
2. On the Frequency scanning page, define the Channel style
Figure 166 LTE Frequency Scanning Properties

9/2/2011
Page 111 of 225
RF-E346
Issue 2.0
3. By clicking the Select Channels button, you can access the Select Channels dialog.
Figure 167 LTE Frequency Scanning: Select Channels

4. Select one band from the list or all of them. You can also select one band at a time and add the
bands you want to scan. If all bands are selected, you have the possibility to select Remove All
| ... items from every band. Alternatively, if only one band is selected you can remove only
items from the current band through Remove All | ...items from current band. The Available
view provides a list of channels that are available for scanning. To add channels to the Selected
list, click on a number in the Available list and then click the Add button or simply double-click a
channel to add it to the Selected list. To select all available channels for scanning, click the Add All
button. An alternative method to select channels is to type the channel numbers in the field at the
bottom of the dialog and to click Add. To remove channels from the Selected list, click on the
channel you want to remove and then click the Remove button or double-click the channel. To
remove all channels, click the Remove All button. You can select several channels simultaneously
by holding down the SHIFT key and clicking on the channels you want to add or remove.
5. After making the appropriate settings, click OK and OK again and go to online mode to start the
scanning.
7. Click the Start Recording button to start recording the results in an output file.
14.2 Frequency Scanning - PCT GSM Scanner

2. By clicking the Advanced button, you will access the Advanced Properties dialog. Here you
can enable and disable the integrated GPS receiver. This means you will not need an external
GPS receiver in order to collect position data.
3. Go to the Frequency scanning page
9/2/2011
Page 112 of 225
RF-E346
Issue 2.0
Figure 168 GSM Frequency Scanning Properties

Channel style refers to the style of the channel.
Selecting the BSIC decoding option displays BSIC value in a measurement window.
BSIC threshold defines the minimum BSIC level that the scanner reports.
Select the BCCH C/I check box to activate C/I measurements for the BCCH channel. This option
is available with PCTEL GSM scanners only.
By clicking the Select Channels button, you can access the Select Channels dialog.
4. By clicking the Select Channels button, you can access the Select Channels dialog.
9/2/2011
Page 113 of 225
RF-E346
Issue 2.0
Figure 169 GSM Freq. Scanning: Select Channels

5. Select one band from the list or all of them. You can also select one band at a time and add the
bands you want to scan. If all bands are selected, you have the possibility to select Remove All | ...
items from every band. Alternatively, if only one band is selected you can remove only items from
the current band through Remove All | ...items from current band. The Available view provides
a list of channels that are available for scanning. To add channels to the Selected list, click on a
number in the Available list and then click the Add button or simply double-click a channel to add it
to the Selected list. To select all available
channels for scanning, click the Add All button. An alternative method to select channels is to type
the channel numbers in the field at the bottom of the dialog and to click Add. To remove channels
from the Selected list, click on the channel you want to remove and then click the Remove button
or double-click the channel. To remove all channels, click the Remove All button. You can select
several channels simultaneously by holding down the SHIFT key and clicking on the channels you
want to add or remove.
Note that Sample size and Data mode are not enabled with PCT GSM frequency scanning
scanning.
7. A green light on the scanner Device info window should start blinking. This means that the
device is working properly and scanning using the default settings.
9/2/2011
Page 114 of 225
RF-E346
Issue 2.0
14.3 TOP-N Pilot Scanning PCTEL - UMTS
Unknown Pilot scanning can be used for scanning unknown pilots or the strongest pilots. The
Unknown Pilot Scan will from now on be referred to as TOP-N Pilot Mode.
2. Go to the Pilot scanning page
Figure 170 UMTS Pilot Scanning Settings
CPICH Ec/No threshold defines the minimum level for the CPICH Ec/No. If the values are below
the threshold, the pilots are not reported.
Data processing method defines how the scanned data is processed by the scanner. In
aggregate method, the sum of all peak pilot Ec/Io values above the PN threshold is
calculated. If there are no peaks above the PN threshold, value -30 dB is returned for WCDMA.
Pilot measurement mode defines the measurement mode for pilot scanning.
In High speed mode scanning speed is higher but sensitivity is lower. In high speed mode, weak
pilots may be undetected.
In High dynamic mode scanning speed is lower but sensitivity is higher.
Top-N check box enables/disables Top-N scrambling code scanning. If enabled, scanner will report
results from N best scrambling codes. Number of pilots field defines how many pilots are reported
by scanner in Top-N mode.
9/2/2011
Page 115 of 225
RF-E346
Issue 2.0
Time of arrival defines if the selected scanner will measure the time of arrival for each
scrambling code. The time of arrival value is relative to GPS time and is measured in chips.
Delay spread defines if the selected scanner will also measure the delay spread value (in chips)
for each scanned scrambling code. Delay spread is determined as the difference between the last
and first component to break the threshold set in PN Threshold.
P-SCH defines if the selected scanner will measure the P-SCH Ec/N 0 value for each scrambling
code.
SIR (signal to interference ratio) defines if the selected scanner will measure the SIR value for each
scrambling code.
S-SCH defines if the selected scanner will measure the S-SCH Ec/N 0 value for each scrambling
code.
To select channels:
1. In the Measurement Properties, Pilot scanning, UMTS page, click the Top-N
Configuration button. The Select Channels dialog is opened.
The table displays the channel numbers, not the frequencies. If you know the
frequency but not the channel number, the channel number can be calculated by
multiplying the frequency in MHz by five. The channel spacing is always 200 kHz.
2. Remove channels from the Selected list by selecting a channel and clicking the Remove button.
3. Add channels to the Selected list by selecting a channel from the Available list and clicking the
Add button.
With a PCTEL EX scanner a maximum of 15 channels can be selected in the pilot mode.
With a PCTEL LTE EX scanner a maximum of 15 channels can be selected in the pilot mode.
To select pilot parameters:
1. Check the TOP-N Mode check box.
2. Set the Number of scrambling codes value. This defines how many strongest pilots are to be reported by the
scanner. The maximum is 32 pilots
3. To improve on the accuracy of radio propagation models, High speed mode makes it possible to acquire more
samples (max 32 pilots per channel), while High dynamic mode offers fewer samples (max 16 pilots per
channel) with a larger dynamic range
To set general parameters:

1. Data processing method defines how the scanner will process samples before reporting.
2. PN threshold defines the limit above which Ec/N0 peaks must go if Aggregated data processing method is
used.
To select measured values:
9/2/2011
Page 116 of 225
RF-E346
Issue 2.0
In Pilot Scanning Mode the RSSI is always measured for each channel.
In Pilot Scanning Mode the P-CPICH Ec/N0 and RSCP are always measured for each scrambling
code.
1. In the Measurement Properties, Pilot scanning page:
Select the P-SCH option to enable P-SCH Ec/N0 and RSCP measurement.
Select the S-SCH option to enable S-SCH Ec/N0 and RSCP measurement.
Select the Time of arrival option to enable time of arrival measurement.
Select the Delay spread option to enable P-CPICH delay spread measurement.
Select the SIR option to enable P-CPICH SIR measurement.
Select the Delay profile option to enable P-CPICH Delay Profile measurement. In TOP-N pilot
scanning mode the scrambling code for delay profile measurement cannot be selected.
scanning.
14.4 LTE OFDM Scanning - PCTEL EX LTE

OFDM scanning can be used for scanning Reference signal / Sync signals with a PCTEL LTE
scanner and Nemo Outdoor.
1. After the PCTEL LTE scanner is connected and activated in Nemo Outdoor, open the
Measurement Properties dialog by selecting Measurement | <device> | General
Properties.
2. By clicking the Advanced button, you will access the Advanced Properties dialog. Here
you can enable and disable the integrated GPS receiver. This means you will not need an
external GPS receiver in order to collect position data.
3. In the Measurement Properties dialog, go to the Pilot scanning page.
9/2/2011
Page 117 of 225
RF-E346
Issue 2.0
Figure 171 LTE Pilot Scanning OFDM Setup

Cyclic prefix defines the type of signal the scanner is set to measure. With
Autodetect selected, the scanner will automatically detect the appropriate signal type.
Data processing method defines how the scanned data is processed by the scanner. In aggregate method, the
sum of all peak pilot Ec/Io values above the PN threshold is calculated. If there are no peaks above the PN
threshold, value -30 dB is returned for WCDMA
Sampling ratio option is available for PCTEL EX scanners only. The available options are 1:1, 1:2, 1:4
and 1:8. With ratio 1:1 all samples (Pilotscan events) are logged, with ratio 1:2 every second sample is
logged, with ratio 1:4 every 4th sample is logged, and with ratio 1:8 every 8th sample is logged. By
decreasing the sampling ratio you can decrease the output file size, but the scanning accuracy will be
diminished.
RSSI threshold determines a valid path (in dB). Subtracting the set value from a path with a
maximum correlation value gives the lower limit of the valid path.
Top-N check box enables/disables Top-N scrambling code scanning. If enabled, scanner will report
results from N best cells.
Number of cells field indicates the number of best cells you want the scanning to notify you of. Up
to 16 sectors are reported with specific cell ID.
CINR check box activates/deactivates Carrier to Interference and Noise Ratio measuring.
Carrier refers to either reference signal power or sync signal power depending on the selected signal
type.
Time offset refers to the number of samples between P-SCH Primary Synchronization Signal arrival
time with respect to receiver frequency reference that is derived from GPS reference time.
Sync signal refers to the ratio between the synchronization channel, i.e., primary and secondary signal received
power and the interference and noise from the same synchronization signal set.
9/2/2011
Page 118 of 225
RF-E346
Issue 2.0
Reference signal refers to the ratio between the reference signal received power (RSRP) and the
interference and noise from the same reference signal set.
The Top-N Configuration button will open the Select Channels where you can select channels for pilot scanning.
The maximum number of channels that can be selected is device specific.
4. When you select LTE channels, you can also define some channel-specific settings. In the LTE Channel
Specific Settings dialog, select the channel from the Selected channels list and define the settings.
Note that the available options are device specific.
Figure 172 LTE Pilot Scanning OFDM Setup: Channel Settings

Uplink-downlink configuration refers to LTE TDD frame structure.
15 How to set up and use Syncro Test
Overview of Steps
1.
Establish Remote Control Connection (Local Loopback, EVDO, UMTS, LAN or LTE)
2.
Configure the Master Controller
3.
Configure the Probe (LLDM, NEMO, etc.)
4.
Load Test Cases into the Master Controller
5.
If control connection is not Local Loopback, run continuous DOS ping of the Probes IP Address from the
Master Controller. Use the Ping button on the Probe to initiate continuous ping of the Master Controllers IP
Address from the Probe.
6.
With ping running both ways, register the Probe on the Master Controller, by pressing the Register button
on the Probe. Once Probe is registered, stop the pings and go to the appropriate steps below.
7.
On the Probe, establish LTE Connection
8.
On the Probe, start LLDM, then WINDS.
9.
On the Master Controller, select the appropriate test case to run.
10.
On the Master Controller, start the test
15.1 Establish Remote Control Connection

For EVDO or UMTS control connection, use the appropriate connection manager to establish connection on
the Master Controller. A sample connection manager for LTE is shown in Figure 173. In this example, one
9/2/2011
Page 119 of 225
RF-E346
Issue 2.0
would click on Connect WWAN to establish connection.
Figure 173 Verizon Access Connection Manager
15.2
Configure Adapters to Avoid Conflicts

1. On the Probe, with the UE plugged in but before establishing
LTE connection for the first time,
a. Select Network Connections from the Control panel
b. Highlight the LTE connection and select properties to see the picture in Figure 174.
c. Highlight Internet Protocol (TCP/IP) as shown in Figure 174.
9/2/2011
Page 120 of 225
RF-E346
Issue 2.0
Figure 174 Local Area Connection Properties
Click on Properties and see the screen as in Figure 175
9/2/2011
Page 121 of 225
RF-E346
Issue 2.0
Figure 175 Internet Protocol Properties
Click on Advanced and see the screen as in Figure 176.
9/2/2011
Page 122 of 225
RF-E346
Issue 2.0
Figure 176 Advanced TCP/IP Settings
Uncheck Automatic metric and enter 1 as shown in Figure 177.

Click OK
9/2/2011
Page 123 of 225
RF-E346
Issue 2.0
Figure 177 Advanced TCP/IP Settings (2)

This is necessary to resolve conflicts between EVDO/UMTS and LTE connections.
2. On both Master Controller and Probe laptops, disable all other connections (LAN, 1394). Leave
only the EVDO/UMTS and LTE connections active.
3. If Control is over LTE connection, use the appropriate connection manager to establish connection
on the Master Controller. Do the same on the Probe. Follow all the other steps stipulated for EVDO
connection.
4. If Control is over Local Loopback, no connection is necessary. Instead, select the MS-TCP-Local
Loopback from the Adapter pull-down menu shown in the next page, for the Master Controller, and
the Probes page, for the Probe.
5. After establishing both connections, verify internet accessibility by pinging yahoo.com or a similar
website on each of them.
6. Once internet accessibility has been verified, the Probe operator should obtain the IP address of the
Master Controller from the Master Controllers operator, and provide the IP address of the Probe to
the Master Controllers Operator.
7. From the Master Controller, perform a continuous DOS Ping of the Probes IP Address
(Ping t Probes IP Address)
9/2/2011
Page 124 of 225
RF-E346
Issue 2.0
15.3 Configuring the Master Controller Control panel

Start the Master Controller. From the pull-down menu of Options screen (select Tools, then Options to see the
screen below), select the correct adapter based on the type of Remote Control connection established (Verizon
Wireless VZAccess is shown in Figure 178)
Figure 178 Syncro TestMaster Controller Options

This completes the configuration of the first of the four panels (Control). The configurations of the remaining 3
panels are shown in the following pages.
15.3.1 Testing Panel

Normally, there is nothing to change on this panel. However, detailed description of each of the items is available
in Syncro Test Users Guide manual.
The box for continue testing if some probes fail setup is useful while performing mutli-UE tests. It allows
the test to continue even if one of the probes fails test setup.
9/2/2011
Page 125 of 225
RF-E346
Issue 2.0
Figure 179 Testing Panel
15.3.2 Log Data Panel

The log files can be sent to different locations with the following settings:
To leave the log files (test results) on the Probe for later upload or manual retrieval, select Dont Send.
To transfer the log files back, select one of the two options TCP or FTP.
TCP transfers the results directly to the Master Controller Laptop (the directory shown below).
o FTP allows transfer of the result to another FTP Server. When it is selected, the spaces for
entering details of the FTP Server
- FTP Server IP Address, Path Prefix, the type of login, open up.
All Probes Upload Simultaneously checkbox is for multi-UE tests. Selecting it allows test results from all
UEs to be uploaded at the same time. Otherwise the results are uploaded sequentially.
9/2/2011
Page 126 of 225
RF-E346
Issue 2.0
Figure 180 Data Log Panel
15.3.3 Snapshot View Panel

Select the control adapter and rate of screen refresh for registered Probes.
The OK button is activated only after this panel is configured.
9/2/2011
Page 127 of 225
RF-E346
Issue 2.0
Figure 181 Snapshot View Panel
15.4 Configuring Probe (LLDM, NEMO, etc.)
15.4.1 LLDM Probe

Start the Probe and select Tools, Options
9/2/2011
Page 128 of 225
RF-E346
Issue 2.0
Figure 182 Syncro Test LLDM Probe
15.4.2 Syncro Test LLDM Probe Options

In Probe ID box, enter the unique ID for the probe (this can also be done from the Master Controller).
In Control box, select the appropriate network Adapter (Verizon Wireless VZAcces is selected below).
Normally, no changes are necessary in Log Data box. However, details are available in Syncro Test Users Guide.
9/2/2011
Page 129 of 225
RF-E346
Issue 2.0
Figure 183 Syncro Test DMDS Probe Option

Once the options are configured, click OK.
15.4.3 Verify connectivity of Probe to the Master Controller
9/2/2011
Page 130 of 225
RF-E346
Issue 2.0
Figure 184 Syncro Test Ping

Ping the Master Controller continuously until response is obtained.
9/2/2011
Page 131 of 225
RF-E346
Issue 2.0
Figure 185 Register the probe
9/2/2011
Page 132 of 225
RF-E346
Issue 2.0
Figure 186 Probe is registered

15.4.4 Load Test Cases into the Master Controller
In the Master Controller, select File, Load Predefined Tests
9/2/2011
Page 133 of 225
RF-E346
Issue 2.0
Figure 187 Open Predefine Tests

Click on Predefined Tests, select the test group. From the group, select the particular test of interest
(WABA_1_1_7_10M_UL_DL_FTP) as shown in Figure 188.
9/2/2011
Page 134 of 225
RF-E346
Issue 2.0
Figure 188 Select Predefined Test

15.4.5 Select the test to run on each UE
On the Master Controller, select the UE; then select the test to run.
9/2/2011
Page 135 of 225
RF-E346
Issue 2.0
Figure 189 Multiple Tests for Probe

For multi-UE probe, select a test for each UE.
For single UE per probe, only 1 UE will show in UEs column in Figure 190.
9/2/2011
Page 136 of 225
RF-E346
Issue 2.0
Figure 190 UE 1 Test Selection Example
16
Data Collection Procedure
16.1 LLDM Data Collection Software

LLDM is a data collection software provided by LG corporation. It should be used in conjunction with LGE
Connection Manager, and the UE driver. You can download LLDM, Connection Manager, and the Driver from:
https://wcdma-ll.app.alcatel-lucent.com/livelink/livelink.exe?
func=ll&objId=57119978&objAction=browse&sort=name&viewType=1
To Install LLDM
Note: LLDM and LG Connection Manager should be pre-installed and licensed in the LTE RF Toolkits. Install
LLDM and LG Connection Manager if they are not in your computer or if there is a newer version.
To install LLDM, double click on the LLDM_XXX_.exe file. XXX is related to the version number.
9/2/2011
Page 137 of 225
RF-E346
Issue 2.0
After installing LLDM, click Start, click Programs, click LLDM, and click
LGE_LLDM_PCSerialChecker to obtain a string of data.
Copy the string and write to Vern Bean to get a zipped license file.
When you receive the zipped license file, unzip it, and put the unzipped license file in the LLDM
installation folder under c:/program files/lge/lldm.
Click Start, click Programs, click LLDM, and click LLDM to activate LLDM.
To Install Connection Manager
Unzip LG_Test_CM_XXX.zip XXX is the version number
Double click on setup.exe
Install Driver
Unzip LGLTEUSBDrivers_XXX.zip XXX is the version number
Connect LGE ADRENALIN UE to the PC USB port. If one USB cable cannot provide enough power, you
can connect the ADRENALIN to a Y cable and connect the 2 USB connectors of the Y cable to 2 USB
ports of the PC.
Double click on LGLTEUSBDrivers_XXX.exe
Click Start, click Programs, click LLDM, and click LLDM.
Connect ADRENALIN to the PC USB port as shown in Figure 191.
Figure 191 ADRENALIN
:
.
On the Data Collection PC, click Start, click Programs, click LLDM, and click LLDM.
In the LLDM window, click Set Up, and click Set Comport to display the Port Setting window as in
Figure 192.
9/2/2011
Page 138 of 225
RF-E346
Issue 2.0

In the Port Setting window, click the Device tab, and check the Comport button.
In the Comport window, check CH1 if you only optimize 1 channel.
In the Port drop-down box, select the port number associated with LGE LTE DM Port. You can refresh
the port settings by clicking the
Plug the GPS in a USB port.
button.
Click the GPS tab, check the GPS box. Click

to refresh. In the Port drop-down box, select the port
associated with GPS.
When finished, click OK to complete the configuration process. You will see the received signal
displayed in a screen as in Figure 193.
9/2/2011
Page 139 of 225
RF-E346
Issue 2.0
Figure 193 LLDM

In the Desktop click the LGE CM icon to activate LGE Connection Manager. The CE screen will be
displayed as in Figure 194.
Figure 194 LG Connection Manager

In the LG Command Manager window, the red C represents CDMA signal, the red L represents LTE
signal. Click CONNECT to start the attachment process.
16.2 Syncro Test

Syncro Test consists of two pieces of software: The Master Controller that resides in the Master Controller PC,
which could be the Data Analysis Tool (DAT) PC, and the LLDM Probe that resides in the Data Collection PC.
The engineer can sit in the office and use the Master Controller to control the LLDM Probe which controls the data
source and LLDM logging.
Both the Master Controller and the Probe can reside in the Data Collection PC (by selecting MS-TCP-Local
Loopback in Remote Connection). If both of them reside in the Data Collection PC, the data collector can use the
Master Controller to run the predefined test cases.
If the Master Controller and the Probe reside in two different PCs, the RF engineer in the office can use the
Syncro Test Master Controller to control the Syncro Test Probe in the van to direct the LLDM to collect the
predefined tasks. This section provides information to help you set up the Syncro Test Master Controller and to
perform the data collection tasks.
Note: When running the Syncro Test Master Controller the first time, the PC needs network connection in order to
verify the login information.
Syncro Test can be downloaded from https://sps.na.alcatel-lucent.com/sites/Services.Services_Tools/Syncro
Test/default.aspx
The username and password can be obtained by writing to NavigatorHelp@alcatel-lucent.com
16.3 For Data Collector in the van:
9/2/2011
In the Data Collector PC, physically connect LG UE to USB port of the Data Collector PC.
In the Data Collection PC, click Start, click Programs, click LLDM, and click LLDM to start LLDM.
Click Set Up, click Devise Tab, and check Channel 1.
In Port drop-down menu, select LTE DM Port, and click OK.
The L1 graph of LLDM will display the signal as in Figure 195.
Page 140 of 225
RF-E346
Issue 2.0
Figure 195 L1 Graph of LLDM

In Windows, click Start, click Programs, click LG LTE CM, and click LG LTE CM. A Communication
Manager window as in Figure 196 will be displayed.
Figure 196 LG LTE

Click Connect to start the attachment process. Once attached, the LG Connection Manager screen will
be changed to one like Figure 197.
Figure 197 LG ADRENALIN Attached

In the Data Collector PC, in Windows, click Start, click Programs, click Alcatel-Lucent, click Syncro
Test, and click LLDM Probe to display Syncro Test LLDM Probe as in Figure 198.
9/2/2011
Page 141 of 225
RF-E346
Issue 2.0
Figure 198 Syncro Test LLDM Probe and Syncro Test DMDS Probe Options
Click Tools, and click Options to display Syncro Test DMDS Probe Options as in Figure 199.
Figure 199 Syncro Test DMDS Probe Options

In the Syncro Test DMDS Probe Options window, fill in the boxes. The meanings of the labels are as
follows:
9/2/2011
Page 142 of 225
RF-E346

o
o
o
o
o
o
o
o
o
o
Issue 2.0
Probe ID:
Name of the probe at the Master Controller. We recommend you set the ID to
something meaningful that uniquely identifies the probe or its location, like Sandy. Probe ID can
also be changed from Master Controller.
Heartbeat Interval:
Interval in seconds that a heartbeat is sent.
Control Adapter:
In the selection box, select Wireless Connection or MS TCP Loopback.
Control Server Address: IP address of the DAT PC where the Master Controller resides.
Use Control Adapter For Log: Check this box.
Test Targets (WINDS & FTP Server):
Leave blank.
Probe Log Folder:
Folder that the probe stores its log data.
WINDS Log Folder:
Folder that WINDS logs are written to.
Auto Register:
If checked, the probe will auto register when run.
Auto-Resize Controlled Application:
If checked, the probe will auto resize the applications it
controls to fit everything on the screen.
Click OK to complete and close the Syncro Test DMDS Probe Options window, all the fields in Syncro
Test LLDM Probe window will also be populated.
In the Syncro Test LLDM Probe window, click Register. The LLDM Probe will be registered with the
Master Controller.
9/2/2011
Page 143 of 225
RF-E346
Issue 2.0
16.4 For Remote Control or Local Control
In Windows, click Start, and click Run.

In the Run box, type cmd, and click OK.
In the cmd window, type ipconfig, and press Enter in the keyboard.
In the cmd window, copy IP address of the PPP adapter.
Call the Data Collector in the van and tell him the IP address of the DAT PC.
After the data collector has pressed the Register button in the Syncro Test LLDM Probe window, the RF Engineer
will be able to conduct tests and log them from the Syncro test Master Controller window in the DAT PC (using
Wireless Connection) or in the Data Collection PC (using MS TCP Loopback). The procedures are as follows:
In the Syncro Test Master Controller, select File|Open Predefined Tests as shown in Figure 200 below.
Figure 200 Opening Predefined Tests
9/2/2011
Page 144 of 225
RF-E346
Issue 2.0
Click Tools, and click Options to display the Syncro Test Master Controller Options window as in
Figure 201.
Figure 201 Syncro Test Master Controller Options

In the Control Tab, in the Adapter box, select the appropriate network adapter.
Click the Log Data tab to display the screen as in Figure 202 :
9/2/2011
Page 145 of 225
RF-E346
Issue 2.0
Figure 202 Log Data tab

In the Log Data Tab, fill in data as follows:
o If you do not want Syncro test to send the log data from the Probe PC to the Master Controller PC
via the non-LTE data network (EVDO), chick Dont Send.
o If you want the log data to be sent via TCP to the Master Controller PC, check TCP, and provide
the path to the folder in the Master Controller PC where you want the log data to be sent. The
data will be sent to C:\SyncroTest\Data on the Master Controller, by default.
o If you want the log data to be sent via FTP, check FTP, and provide the FTP server information.
o In the Logging on Probe window, in the Log Folder box, provide the address of the log data folder
in the Data Collector (LLDM Probe) PC.
In the Syncro Test window, in the Name box, fill in the name of the test.
In the Far End Address box, supply the IP address of the WINDS server.
Click File, and click Load Predefined Tests to load the test cases you have pre-defned.
Click Predefined Tests, select the test case you want to conduct.
After the Syncro Test LLDM Probe is registered with the Syncro Test Master Controller, you can see the
screen of the Data Collector PC by clicking
in the middle of the Syncro Test Master Controller
window, and you will see screen image as in Figure 203.
9/2/2011
Page 146 of 225
RF-E346
Issue 2.0
Figure 203 Snap Shot View
In the Master Controller window, click Start Logging to start logging the messages.
Click Start Test to start the test.
Syncro Test will start the test for the duration specified and stop when the test duration expires
When done, click Stop Test (which was changed from Start Test) if you want to stop before the duration
expires.
Click Stop Logging (which was changed from Start Logging),
17 How to use eDAT

An engineer can use eDAT to analyze the KPIs that fall outside of the normally acceptable range. eDAT can help
identify the area of improvement by allowing you to:
Identify the geographic area where the problem occurs.
Plot several KPIs geographically and temporally side by side
Filter the data according to multiple sets of conditions.
Look at the messaging between the eNodeB and the UE.
Filter the messages that meet the pre-defined conditions.
After you have identified the problem area, you can refer to the Optimization Guideline and the RF
Troubleshooting Guideline for further guidance.
9/2/2011
Page 147 of 225
RF-E346
Issue 2.0
17.1 Download and Install eDAT

Before installing eDAT, you should get your username and password by writing to
navigatorhelp@alcatel-lucent.com
eDAT software can be downloaded from: http://navigator.web.alcatel-lucent.com/
17.2 Create a Project
In eDAT, all the related data are collected under Project folders.
Click File, click New.
In the Select the files to add to the project window, select the data files and their paths. The files that
eDAT can import include:
o Drive test data file (dml file collected using LLDM, nmf file collected with NEMO, and others)
o WINDS file (ftp or udp application and session measurements)
o EAT file
o Zip file that contains the above mentioned files in Winzip format.
After you have selected the files, click Open to continue.
If you have more data to add to the Project, click File, and click Add Data to Project1.
After having imported all the files, click File, and click Save Project1 As ..,
In the Save Project1 as .. window, select the proper folder. In the File name box, supply the project
name, and click Save.
17.3 Open an existing Project
If you have already created a project, you can open it as follows:
Click File, click Open, in the Open window, select the proper folder that contains the interested eDAT
project.
In the File name drop-down box, select the eDAT file, and click Open.
17.4 Add Data to an Existing Project
After you have created a project, you can add data to it as follows:
Click File, click Add data, and click the Project to which the data will be added.
In the Select the files to add to the project window, select the proper folder and the files to be added.
Click Open to complete the process.
17.5 Study: Examining and Aligning Data Files
A study is a group of data, usually collected during the same drive test. You can see the beginning time and
ending time of the files in the study. Sometimes the files are mismatched because the data collection computers
are not synchronized. eDAT provides you a function to align the mismatched files.
To examine the beginning and ending times of the files, please follow the steps below:
Click the Projects tab to display the Projects window.
Click the
button to un-hide the Projects window.
In the Study section, the different types of data associated with the study are presented in different rows.
In the time section (section in the right), you can find the begin time and end time of the data file by
moving the cursor to the file object. Figure 204 depicts the beginning and ending times of different files
in the study.
9/2/2011
Page 148 of 225
RF-E346
Issue 2.0
Figure 204 Type and Timing of Files in Study

To align the files, see the following example:
Right click on the file you want to change (WINDS file), click Align Journal To, click the project name
(Project1), click the study containing the file you want to align to (Study1), and pick the file you want
other files to align to. Figure 205 depicts the alignment process.
Figure 205 Aligning the Files

Figure 206 depicts all the files are aligned.
9/2/2011
Page 149 of 225
RF-E346
Issue 2.0
Figure 206 Aligned Files

To Reset the file to its original starting time, right click file icon (in this example, WINDS file icon as in Figure 206),
and click Reset Starting Time.
17.6 Create Cell location files (LCAT)
eDAT can create cell location file (LCAT) from either system snapshot (xcm) or from .csv file.
eDAT can automatically create an lcat file from the system snapshot (xcm file) generated by the WMS or SAM.
Below is the procedure to create an lcat file by importing a system snapshot.
From File menu, click Cell Info and select Import into Project link as presented in Figure 207.
Figure 207 Import Cell Info

Select the xcm file for the Market SnapShot you would like to import. Save your project. This will automatically
import and display the cell sites into the project.
An alternate method would be to create an csv file using he sample format below:
9/2/2011
Page 150 of 225
RF-E346
Issue 2.0
Sample lcat file.csv
And then follow the above procedure to import the csv file instead of xcm file into the Project.
You can hide and un-hide the cells by clicking the
button.
17.7 Default Views of Metric and data

After having created or having opened a project, in the Metric window, you will see many folders
containing different categories of data.
When you open a folder, you will find different types of data with different binning methods (Spatial
binning, Temporal binning). For unbinned data, right click on the Spatial or Temporal binning plots and
select unbinned data. Please be aware that due to the sheer volume of unbinned data, eDAT could slow
down significantly and even crash.
You can also look at the data in different perspectives: Map, Scatter, Histogram, and Grid. Moreover,
you can export the data in CSV format. Right click the data file to open a new window for you to select
different forms of data presentation as in Figure 208.
9/2/2011
Page 151 of 225
RF-E346
Issue 2.0
Figure 208 Different Presentation FormatsUn-binned data

17.7.1 Un-binned data
The data is presented in its native form.
17.7.2 Temporally binned data
The data is binned according to time. You can change the bin size as follows:
In the eDAT window, click Tools, click Options.
In the Options window, click Project,
In the Binning box, change the Temporal Binning Size, and click OK. See Figure 209 for more
information.
9/2/2011
Page 152 of 225
RF-E346
Issue 2.0
Figure 209 Adjust Binning Size
17.7.3 Spatially binned data

The data is binned geographically. You can change the bin size by following the similar steps as described in
Temporally binned data section above.
17.7.4 Scatter Plots
Scatter Plot displays the data with value on the Y axis and time on the X axis. is an example of Scatter Plot.
Figure 210 Scatter Plot

17.7.5 Histogram
Histogram displays the data with the value intervals on the X axis and the frequency of occurrences in the Y axis.
Figure 211 is an example of a Histogram.
9/2/2011
Page 153 of 225
RF-E346
Issue 2.0
Figure 211 Histogram

eDAT offers the functionality to compare multiple drive test results by adding a histogram from another open
project to an existing plot.
17.7.6 Grid
Grid displays all the data in a table format. Figure 212 is an example of Grid. This data can be exported into a csv
file.
Figure 212 Grid

17.7.7 Maps
When you click the Map the first time, eDAT will ask you if you want to download the appropriate street
map: local map, state map, or country map. Please select the maps just big enough for your analysis.
Selecting maps that are bigger than required will increase processing time.
Providing username and password: When eDAT asks you for the username and password, supply the
same username and password that NavigatorHelp provided you to install eDAT.
eDAT will automatically download the selected maps from the server to your local PC.
9/2/2011
Page 154 of 225
RF-E346
Issue 2.0
Google Map and Bing Map can also be downloaded. However, you need to first obtain an account ID
and passwords from these two companies.
A sample map is displayed in Figure 213.
Figure 213 Map

17.7.7.1 Show eNodeB sites
To hide and un-hide the eNodeB sites and cell azimuths, click
in the Tool bar.
17.7.7.2 Zoom in and Zoom out

There are three ways to zoom in and zoom out:
Double right click and double left click
Mouse wheel-up, and mouse wheel-down
Use the
and
from the tool bar
17.8 Change Appearances

17.8.1 Fixing Legend window
You can display and move the legend as follows:
Move the cursor to the Legend tab, the Legend window will drop down.
Quickly move the cursor to the right top corner of Legend window and click
.
Now, you can re-size the Legend window and move it to the location you want.
17.8.2 Changing bin size
You can change the bin size (temporal and spatial only) as follows:
Right click in the Legend window
In the Bin Size box, change the bin size (temporal units are in seconds, spatial units are in meters)
17.8.3 Displaying labels
You can display the label metrics in the map as follows:
9/2/2011
Page 155 of 225
RF-E346
Issue 2.0
Right click in the Legend window

Click the
button.
17.8.4 Changing Themes

If the default legend settings do not fit your need, you can change them by following the example below:
In Figure 214, the granularity between 5 and 20 is too rough; and you want to make them finer.
Figure 214 RS SNR Map

Click Tools, click Options.
In the Options window, under your project name, click Project to display a window as in Figure 215.
Figure 215 Options
9/2/2011
Page 156 of 225
RF-E346
Click Theme Set, and click
Issue 2.0
to display Edit Themes window as in Figure 216
Figure 216 Edit Themes

In the Search Box on the top left corner next to the + symbol, type in the exact name of the map of
which legend you want to change, and click Enter on the keyboard. The name of the map should be
highlighted in the tree below.
In the right pane, in the middle column, key in the new values, click OK, and click OK.
In eDAT window, close the map (in this case, RS SNR).
In eDAT window, double click RS SNR (Temporal) to display the map with new legend as in Figure 217.
Figure 217 Map with new legend
9/2/2011
Page 157 of 225
RF-E346
Issue 2.0
17.9 Multi-Metric Map View

17.9.1 View several metrics in the same map View Synchronization
To help find the underlying cause of an event or a metric, you can look at several metrics side by side as in Figure
218.
Figure 218 Multi-Metrics Plot

The steps to create a Multi-Metrics Plot are as follows:
In the Metrics window on the left, expand a folder by clicking
next to the folder, click on the map
icon of the desired temporal metric (right click on the metric if the map icon is not under the folder). A
map will be displayed.
In the Metric window, expand another folder, click and drag another map icon to the map pane. The map
pane will have 2 metrics displayed.
Continue the same process to display more metrics.
Click the Legend tab to display the legend.
To adjust the relative positions of the metric symbols, do the following:
Click Tools, click Options, click Project, click
Figure 219.
9/2/2011
next to Per Metric Layer Offset to display screen as in
Page 158 of 225
RF-E346
Issue 2.0
Figure 219 Per Metric Offset

Change the relative positions of the two metrics in X axis and Y axis, and click OK.
Close the maps and reopen them to apply the changes.
17.9.2 Multi-Metrics Grid View
Similar to Multi-Metrics Map View, You can view several metrics at a glance. The procedure is as follows:
In the Metrics window, expand a folder, click on the grid icon of the desired metric (right click on the
metric if the grid icon is not under the folder). A grid will be displayed.
In the Metric window, expand another folder, click and drag another grid icon to the map window. The
grid window will now have 2 metrics displayed.
Continue the same process to display more metrics.
A sample of Multi-Metrics Grid display is presented in Figure 220.
9/2/2011
Page 159 of 225
RF-E346
Issue 2.0
Figure 220 Multi-Metrics Grid
17.9.3 View Map and Grid

To view the Map and its corresponding Grid messages, do the following:
In the Metrics window, expand a folder by clicking the
next to the folder, click a map icon to display a
map (if the map icon is not under the folder, right click the metric, and click the map icon).
In the expanded folder, click the grid icon to display the grid (if the grid icon is not under the folder, right
click the metric, and click the grid icon).
If you want to display more metrics in the grid, drag another metric to the grid window.
In the eDAT window, click Window, click New Horizontal Tab Group, the two metric windows will be
arranged as in Figure 221.
9/2/2011
Page 160 of 225
RF-E346
Issue 2.0
Figure 221 Map and Grid Windows
If you want to see the corresponding location of a particular data point in the map, in the Grid window,
move the cursor to the left-most column i.e. the message number (the shape of the cursor changes to a
horizontal arrow), and click. The corresponding point in the map window will change to
.
If you want to see the corresponding time or value of a point or a set of points in the map, do the
following:
o Click the map window, click , move the cursor to the interested point and drag over a group of
points.
o The corresponding rows in the grid window will be grayed out.
It is also possible to play the file, from Play menu and select the speed needed, and that will cause the cursor to
move along the bins and down the Grid ( or Messages) rows as depicted in Figure 222.
9/2/2011
Page 161 of 225
RF-E346
Issue 2.0
Figure 222 Playing File

17.10 Filters
There are two ways to filter the data: Exclude all data that does not meet the RSRP threshold or SNR threshold;
Exclude other types of data.
17.10.1 Excluding data not meeting RSRP or SNR thresholds
In some projects we only have to optimize the area with RF coverage. The coverage is usually defined as an area
where the RSRP is greater than threshold A, and the SNR is greater than threshold B. This section describes how
to filter out the data that do not meet the RSRP threshold or the SNR threshold.
Click Tools, click Options to display window as in Figure 223. Click
LTE.
9/2/2011
to expand Technologies, click
Page 162 of 225
RF-E346
Issue 2.0
Figure 223 Statistics

In the Statics section, Under Applying Statics Filtering, click Applying Statistics Filtering, in the dropdown search box, select True.
In the RSRP Threshold box, fill in the RSRP value under which the data will not be used for analysis
calculations.
In the SNR Threshold box, fill in the SNR value under which the data will not be used for analysis
calculations.
Click OK to enable eDAT to filter out the data that do not meet the threshold criteria.
The Threshold section allows you to exclude all the data that does not meet the threshold. You can use
this to filter out the data below the noise floor by setting the RSRP Threshold to noise floor.
17.10.2 Filtering with other criteria
To filter other data, please see the illustration in Figure 224 and follow the explanations below:
9/2/2011
Page 163 of 225
RF-E346
Issue 2.0
:
Figure 224 Filter
In the Map screen, click the Filter tab.
In the Filter window, select:
o Filter, then Keep: You first use filter criteria to eliminate a part of data, and then take a percentage
of the remaining. Or
o Keep, then Filter: You first keep a percentage of data, then use filter criteria to eliminate another
portion of the data.
In the next box, select whether you want to keep the All, Max, or Min percentage of the data.
Click
to add another filtering criterion.
Select the criterion you want to use for next level of filtering.
Select the operant and the threshold.
When you are done with defining the filtering criteria, click Apply.
17.11 Messages (Message Explorer)

To display the messages exchanged between the UE and eNodeB, do the following:
Click View, click Message Explorer, and click the Study for the data you want to examine.
17.11.1 Text Search
To find the messages that you are interested in, do the following:
In the Tool Bar, click
to display the Find window as in Figure 225.
Figure 225 Find Window
9/2/2011
Page 164 of 225
RF-E346
Fill in the blanks and click Find to find the next occurrence. Click
occurrence.
or
Issue 2.0
for the previous and next
17.11.2 Message Groups

If you want to see the occurrences of a message or a group of messages, you high-light them as follows:
In the eDAT window, click View, click Message Explorer, and click the Study you want to look at.
In the eDAT window, click Tools, click Options to display the Options window as in Figure 226
Figure 226 Options

In the left window, click Application (Under Default)
In the right window, click Message ID Groups and click
to display a blank Message ID Group
Collection Editor window
In the Message ID Group Collection Editor window, click Add to display the Message Group collection
Editor window as in Figure 227.
9/2/2011
Page 165 of 225
RF-E346
Issue 2.0
Figure 227 Message ID Group Collection Editor

In the right Misc window, click <Unnamed> and type in a new name.
Click Message, the
Click
icon will appear at the right end of the line.
to display a window as in Figure 228
Figure 228 Message IDs Window
9/2/2011
Page 166 of 225
RF-E346
Issue 2.0
Check the boxes with the messages that you want to highlight. In the Background Color drop down box,
select the background color you want for the message. Click OK 3 times to return to the message
window.
Depends on the eDAT version, you may have to close the Message window and re-open it for the new
grouping to take effect.
The screen shot of the message window with Up Link Grant, Down Link Grant, and Channel Info
highlighted are displayed in Figure 229.
Figure 229 Message Group
17.12 Reporting
EDAT comes with some standard reports. In the bottom of the left window, there are 3 tabs: Metrics, Reports, and
Delta Metrics. Click Reports tab to display the reports available for the data in the current study.
Samples of some report titles are in Figure 230
9/2/2011
Page 167 of 225
RF-E346
Issue 2.0
Figure 230 Sample Report Titles

A Sample Report is in Figure 231.
9/2/2011
Page 168 of 225
RF-E346
Issue 2.0
Figure 231 Sample Report
18 How to detect problems and how to fix them

Cleaning the PCIs and neighbor lists are probably the most effective steps to improve LTE RF performance. Good
PCI assignment reduces call drops by enabling UE to clearly distinguish one cell from another. Good neighbor list
is important because without it, calls will drop when UEs cross cell coverage boundaries. After sector tests and
before conducting any other optimization procedure, the RF engineer should make sure that:
The PCIs are placed as far apart as possible
There is no first tier neighbors or second tier neighbors assigned the same PCI
Neighbors are reciprocated
There is no missing neighbor
18.1 Maximize distance between co-PCI cells
For LTE, there are a total of 504 unique PCIs. Each cell is assigned a PCI. If there are more than 504 cells, the
PCIs have to be re-used. In order to minimize confusion, the co-PCI cells should be as far apart as possible. The
procedure to check the co-PCI cell distances are as follow:
In SAM, take a snapshot of the network.
In eDAT, click File, click New Project, select the snapshot, and click Open.
In the bottom of the left pane, click Statistic tab.
Click
next to Cell icon to expand.
Click LTE Co-PCI Cells to display the distances between the Source Cell and the Target Cell as in Figure
232. Click the Distance cell to sort the pairs by distance.
9/2/2011
Page 169 of 225
RF-E346
Issue 2.0
Figure 232 Co-PCI Cells
For the co-PCI pairs that are too close together, change the PCI of one of the cells and re-check the distance
between the co-PCI cells.
18.2 Eliminate Co-PCI neighbors

If either the first tier or second tier neighbors have the same PCI, the UE cannot distinguish the source of the
reference signal. Therefore, the RF engineer should re-assign the PCIs to avoid this from happening. The
procedure to check the co-PCI neighbors is as follows:
Click
Click LTE Co-PCI Neighbors to display the Co-PCI second tier neighbors as in Figure 233.
9/2/2011
Page 170 of 225
RF-E346
Issue 2.0
Figure 233 Co-PCI Neighbors

In Figure 233, in the example enclosed by the green box, both cells 098126_3 and cells 098018_3 are the
neighbors of cell 102373_1, and they both have the same PCI. The PCI of one of the cell should be changed to
avoid confusion to the UE.
18.3 Neighbor Reciprocity
The Neighbor Reciprocity function identifies the cell that is a neighbor of another cell, but the other cell is not a
neighbor of the interested cell. The procedure to identify neighbors with no reciprocity is as follows:
Click
Click LTE Reciprocity Neighbor List Alert to display the non-reciprocating neighbors as in Figure 234. In
this figure, Target Cells are neighbor cells of Source Cells; but Source Cells are not neighbor cells of the
Target Cells.
You should create a WPS work order to add the Source Cells to the neighbor lists of the Target Cells.
9/2/2011
Page 171 of 225
RF-E346
Issue 2.0
Figure 234 LTE Reciprocity Neighbor List Alert
18.4 Missing Neighbor

Neighbor List based on cluster drive data. This approach complements the prediction based neighbor list with
measurement data. The basic idea is that if the cells of which RSRP are detected together in a large amount of
bins should be considered as neighbors. It is recommended to run a drive test that covers all the cells within a
cluster and its surrounding cells to collect data to support this activity. The procedure is as follows:
In SAM, take a snapshot of the network
Collect drive test data.
In eDAT, click File, click New Project, select the drive test file and the snapshot, and click Open.
Click
next to LTE-Coverage Overlap Analyser to expand
Click Coverage Overlap Analyser to display the analysis as in Figure 235.
9/2/2011
Page 172 of 225
RF-E346
Issue 2.0
Figure 235 Coverage Overlap Analysis
In Figure 235, let us look at the example enclosed in the green box. Cell 100250_2 and cell 100029_3
were 5637 meters apart; and they were not neighbors. The RSRPs of both cells were recorded in 82
bins which is 32% of total number of bins covered by Cell 100250_2, the source cell. Because of this
heavy overlap, these two cells should be assigned as neighbors.
18.5 Drop call Scenario No Handover Command Received

When UE sends measurement report to source cell, there should be Handover command sent to UE by the
source cell to complete the Handover successfully. If the UE does not receive Handover Command, the call
would stay on source cell and drop
Serving cell 14 UE sends Measurement Report (MR) for cell 350 but no Handover command. Please check
if this is a case of missing cells
9/2/2011
Page 173 of 225
RF-E346
9/2/2011
Issue 2.0
Page 174 of 225
RF-E346
Issue 2.0
18.6 Drop call Scenario missing Neighbor contributed to 4 repeated drop calls
Serving cell 488 has missing neighbor cell id 73 and cell id 277
18.7 RACH ISSUE

Serving Cell id 360 - UE sends measurement report (MR) for cell id 169. UE receives Handover command but
call drops after T304 (Handover failure) timer expires.
RACH 1probes eNodeB every 20 ms. RACH2 (Rach1 response) opportunities should be 5 TTIs after each
probe. Instead RACH2 is coming 15 TTIs after each probe. Problems were due to UE bug.
9/2/2011
Page 175 of 225
RF-E346
Issue 2.0
RACH1
RACH2
18.8 Identifying Pilot Polluted Areas

Pilot pollution refers to degradation in performance due to interference from common pilots sent by neighbor
cells. A common pilot may be a cell-specific reference signal used for demodulation and decoding, a
synchronization signal used for cell acquisition, etc. Any area where the number of pilot is within 6dB of the
dominant pilot is a polluted area. Most often this polluted areas leads to drop calls.
Antenna physical changes either through mechanical down tilts, azimuth changes, antenna re-orientation,
pilot power reduction and antenna heights reduction might help to mitigate the problem.
9/2/2011
Page 176 of 225
RF-E346
Issue 2.0
All the circled areas are polluted areas. Most of the areas ended in drop calls as can be seen below and
Handover failures on the next graph. UE is seeing too many pilots with equal strength and no dominant pilot.
9/2/2011
Page 177 of 225
RF-E346
9/2/2011
Issue 2.0
Page 178 of 225
RF-E346
Issue 2.0
18.9 Call drop scenarios in the Handover regions
9/2/2011
Page 179 of 225
RF-E346
9/2/2011
Issue 2.0
Page 180 of 225
RF-E346
9/2/2011
Issue 2.0
Page 181 of 225
RF-E346
Issue 2.0
18.10 Handover Parameters and Recommended Settings

All Handovers in LTE are essentially Hard-Handovers. There are a set of criteria and associated HO
parameters for filtering physical layer measurements at layer 3 and parameters for HO trigger.
Extensive set of HO parameters under eNodeBs control are communicated to UE via signaling messages at
the RRC layer. These help to optimize HO performance in terms of HO rate, ping-ponging, success rate,
throughput and BLER performance in the Handover region.
UE has control over physical layer measurements, so some dependency on UE implementation.
3GPP defines a set of events applicable for one or more HO types.
e.g eventA3 for intra-freq intra-LTE Handover
e.g eventA2 and eventB2 for inter technology Handover (LTE to UMTS)
Event A3:
Serving and Neighboring cell must meet the entry criteria for a neighboring cell to be considered for inclusion
on Measurement Report
ENTRY: Neighboring_signal Hysteresis > Source_signal + eventA3offset
Above condition must be met for timeToTrigger interval before MR will be triggered
9/2/2011
Page 182 of 225
RF-E346
Issue 2.0
Key Handover Parameters

1. Hysteresis/eventA3offset
Signal comparison thresholds between serving and neighboring cells for UE to trigger
MeasurementReport for Handover
Signal can be in terms of RSRP or RSRQ
In general, filtered signal for a neighbor must exceed that of serving cell by the combined [hysteresis
+ eventA3offset] amount for the UE to trigger MR
2. timeToTrigger
once a neighboring cell meets eventA3 entry criteria, it must hold the criteria for timeToTrigger
duration before MR is triggered
In simple terms, it is the hold time before UE will trigger MR for a stronger candidate cell
Can also be viewed as time hysteresis
3.
FilterCoefficientRSRP/RSRQ
Applied at L3 filter output of L1 signal measurements
Controls how fast a neighbor cell can meet the eventA3 criteria
In general, filtered signal for a neighbor must exceed that of serving cell by the combined [hysteresis
+ eventA3offset] amount for the UE to trigger MR
3GPP requires UE to adapt filter coefficient to preserve filter characteristics assuming T=200ms; L1>L3 reporting rate
9/2/2011
Page 183 of 225
RF-E346
9/2/2011
Issue 2.0
Page 184 of 225
RF-E346
Issue 2.0
4. Parameter Recommendation
5. Handover Parameter Optimization Impact
9/2/2011
Page 185 of 225
RF-E346
Issue 2.0
6. Additional HO related parameters

cellindividualOffset
o impacts eventA3 entry criteria
o Allows altering effective HO hysteresis in a certain direction for a given serving cell ->
neighboring cell pair
o Can be useful for local area optimization, careful about NL transmission impact
o Default recommendation: 0 dB
maxReportCells
o Max number of cells reported by UE on the MR
o Default recommendation: 1=> UE will report only the strongest neighboring cell
S-Measure
o UE will look for neighboring cells only if the serving cell RSRP falls below this threshold
o Default recommendation: -43dBm
reportingAmount/reportingInterval
o After the first MR sent, successive repeats at the RRC layer are controlled by these two
parameters
reportingAmount constrains the number of MR repeats
reportingInterval governs the spacing between MR repeats
o Per 3GPP, the earliest a Handover can be setup is after SecurityMode is completed during an
Attach or idle to Active setup
However, UE is allowed to send MR as soon as it can
Repetitons help ensure eNB sets up HO right after SecurityMode is completed,
reflecting most recent RF conditions
o reportingAmount/Interval apply to same set of neighbor cells
As part of multiple repeats, UE can update RSRP info for the same reported cells
If a new neighbor shows up, MR count is reset and can be sent right away
o Recommendation: r8/ms240
eNB will attempt to perform HO to the neighboring cell reported on the eventA3 based
MeasurementReport
o No signal comparison done at the eNB UEs check is sufficient
9/2/2011
Page 186 of 225
RF-E346

o
Issue 2.0
If maxReportCells set to greater than 1, eNB will take the first neighbor cell on the list
according to 3GPP, UE must rank the reported neighbors on the MR per signal strength
(strongest cell first)
If a new MR received while the first one in progress, eNB will abort the current HO evaluation and
process the new MR unless HO command already sent out
Unlike CDMA/EVDO or WCDMA, no need for transmitting Neighbor Lists to UE in LTE

o 3GPP requires UE to be self-sufficient in terms of detecting neighbors without eNBs
assistance
o However, a neighbor relationship must exist in the cell for it to process HO request
Regardless of the below HO types, same eventA3 trigger criteria apply

o Intra-eNB HO
o X2-based inter-eNB
o S1-based inter-eNB HO
7. Timers for Handover failures / drops

Several timers / mechanisms exist in the database file that influence HO failure rate / dropped calls
o T304: Successful transmission of HO confirm (RRC Connection Reconfiguration Complete)
following receipt of HO Command. Recommendation: ms2000
o
dsrTransMax: Max number of Scheduling Requests (SR) UE will send to request an UL

grant before declaring SR_Max failure. UE not receiving UL grants could be due to DL issues
(weak DL SINR) or UE running out of UL coverage. Recommendation: n64
T310: DL physical layer break-down (out-of-sync indication within UEs lower layers).
Recommendation: ms1000
timeAlignmentTimerCommon / Dedicated: UE must receive a Time Alignment (TA) update

within this interval, else declares TA failure. Recommendation: 2560ms
maxRetxThresholdDownlink / maxRetxThresholdUplink: Max number of times eNB on

DL/UE on UL retransmits a RLC packet before declaring max_RLC_RTx failure dropped call
UlSyncTimer: eNB declares loss of UL when unable to detect sufficiently strong SRS.
Recommendation: 3 sec.
8. Re-establishment
UE will attempt re-establishment following a Handover failure
o Goal to expedite recovery following the HO failure / Radio Link Failure (RLF)
Re-establishment supported on all 3 cells of the source and/or target eNB, depending on when the
RLF occurred
o If RLF occurs before MR is received, then only source eNB will have the context / will support
re-establishment
o If RLF occurs after MR is received and before HO confirm is received, then both eNBs will
have the UE context
o If RLF occurs after HO confirm is received and source has released resources, then only the
target eNB will have the UE context
9. Handover Performance Metrics
9/2/2011
Page 187 of 225
RF-E346
Issue 2.0
Key drive tests metrics evaluated when optimizing HO parameters (in order of priority)
o HO Success Rate
o Number of HO Attempts
o DL/UL throughput
o DL/UL BLER
o Re-establishment Success Rate
CDMA basics apply to LTE when optimizing HO performance / coverage
Minimize number of cells covering an area
Maintain dominant coverage
Strive to achieve good SINR
Becomes more important with LTE given the Hard Handover nature
10. Factors affecting HO Performance

Sensitivity to usage environment
o Current settings optimized based on drive testing
o Main goal to achieve a good HO success rate
o While minimizing number of HO attempts (HO interruptions) to maximize throughput
performance
Potential for optimizing HO parameters based on usage environment

o
Urban/Dense Urban topology typically has higher stationary usage. Due to slower fading, HO
failure not as much of a concern. Slower HO parameter set will tend to minimize number of
HO interruptions. Possible parameter sets:
o
Hysteresis = 3 dB
filterCoefficientRSRP =fc4; ttt=640ms
filterCofficientRSRP =fc11; ttt=0ms
Fast moving environments (e.g. predominantly highway coverage) will be the other extreme.
o
filterCoefficientRSRP=fc4
hysteresis = dB
UE search algorithm dependency

o L1 filtering is UE implementation dependent
o According to 3GPP, UE needs to automatically adjust L3 filter coefficients if L1 sampled faster
In general, monitor HO performance as UE implementations evolve
o May need to strike balance between UE differences when choosing HO parameter values
UE sensitivity differences / improvements
o Evidence of difference in RS / PDCCH performance sensitivity among UE vendors
o As a result, expect difference in HO success rate across UE types
o Expect sensitivity improvements need to monitor over time
RF Loading on the network
o Loading drives up the HO failure rate due to weakened DL SINR esp. in the HO region
9/2/2011
Page 188 of 225
RF-E346

o
o
Issue 2.0
When tuning HO parameters, consider effect of RF loading, esp. if applying slower HO parameter
set
As networks get loaded, need to study if a balance can be achieved faster HO set to switch to
the best cell as soon as possible versus adverse impacts from frequent ping-ponging / switching
to momentarily strong cells
RACH configuration / issues

o Contention free RACH supported for HO benefit under loaded conditions
o RACH parameter settings (e.g., starting RACH power, number of RACH msg1 repeats, etc.)
o UE issues more recent LGE G13 software version seems to have fix for RACH timing issue
which was causing T304 failures due to RACH msg2 timeouts
Cell Individual Offset (CIO)

o If CIO set to non-zero to optimize HO performance on specific cell pairs, those neighbors would
be signaled via Neighbor List transmission on the RRC Connection Reconfiguration message
(immediately after the one for HO command)
o Careful about enabling NL transmission everywhere
Some evidence that turning on NL transmission for all neighbors can increase drop call
rate
Potential impact from increase in processing burden from tracking all specified neighbors
instead of just looking for strong candidates
Contrary to expectations from CDMA/EVDO
Based on LGE G13 in a dense urban markets need to confirm in other markets/with
other UEs
RSRP versus RSRQ

o Field studies have not shown any clear benefit of using RSRQ as HO trigger
RSRP typically has provided as good or better HO performance than RSRQ
Possible UE implementation dependencies
Potentially evaluate in the future
9/2/2011
Page 189 of 225
RF-E346
19
Issue 2.0
How to use SAM to examine network status
1. Double click on the icon
on your desktop to open 5620 SAM Client.
2. Highlight Network to view the network status as in Figure 236.
9/2/2011
Page 190 of 225
RF-E346
Issue 2.0
Figure 236 SAM Network Status

3. Click on the Legend Icon to view the following Icons Legend, Colors Legend and Highlight Sessions as in
Figure 237.
Figure 237
4. Click on the Icons Tab as in Figure 238, Figure 239, and Figure 240. The Icon Tab describes the Icons of
the Network Element, different Icon Elements Description and Alarm Icon.
9/2/2011
Page 191 of 225
RF-E346
Issue 2.0
Figure 238
Figure 239
9/2/2011
Page 192 of 225
RF-E346
Issue 2.0
Figure 240
5. Click on the Colors Tab as in Figure 241. The Colors tab describes the different colors of the Physical
Link.
Figure 241
6. Click on the Highlight Sessions tab as in Figure 242.
9/2/2011
Page 193 of 225
RF-E346
Issue 2.0
Figure 242
20
How to use SAM to change eNodeB parameters
This section describes eNodeB online configuration, which is the process of configuring eNodeB parameters
using the 5620 SAM GUI.
Figure 243 SAM Client Logical View

Follow these steps for accessing eNodeB Configuration parameter forms.
Click on the plus sign for Network to expand the view to locate the appropriate eNodeB.
Right-click on an eNodeB and choose Logical View from the contextual menu. This will
Open eNodeB logical window as shown in Figure 244.
Right click on e-NodeB Instance and select Properties from the menu.
9/2/2011
Page 194 of 225
RF-E346
Issue 2.0
Figure 244 Equipment-E-NodeB Logical View

It will pop up another window as shown in Picture3. Select Components tab to see configuration parameter
groups for this eNodeB. Expand by clicking + sign to see child objects of the parameter group.
In below Figure 245 as an example RRC Measurement Conf is shown under RRM Services.
Figure 245 eNodeB NE Instance
LTE Cell Parameters:

Similarly we can see LTE Cell level parameters as described in Figure 246 below.
Figure 246 Equipment-E-NODEB Instance

From Logical Window view expand Cells by clicking on + sign then select the cell which you want to see
configuration settings.
Right click on the Cell and select Properties as shown in Figure 246.
9/2/2011
Page 195 of 225
RF-E346
Issue 2.0
It will pop up another window as shown in Figure 247. Select Components tab to see
configuration parameter groups for this LTE Cell. Expand by clicking + sign to see child
objects of the parameter group.
Figure 247 LTE Cell Instance

In Figure 247 we are expanding Cell Selection Reselection Conf group by clicking + sign as shown in this
example. At this time you will see the child object under Cell Selection Reselection Conf which is Cell Selection
Reselection Conf Name:0
Right click on this child object and select Properties. This will open a new window displaying Cell Selection
Reselection configuration parameters as shown in Figure 248.
Figure 248 Cell Selection Reselection configuration parameters
9/2/2011
Page 196 of 225
RF-E346
Issue 2.0
The user can review currently set values for configuration parameters in this window and similarly one can open
any other configuration parameter forms to see related parameter settings.
These parameter settings can be modified from this window as described below.
User can type in a new value for the parameter need to change. As Example for
QRxLevMin (dBm) can be changed from -110 to a new value like -120.
Once the new value is entered click Apply to make these changes take effective
Immediately.
Special Note:
Please note that some of these parameter changes need to Reset eNodeB as described below.
Configuration parameters are classified into classes that have consequences when modifying them:
Class A Will cause a Full Reset of eNodeB
Class B Will cause Partial (card) Reset of eNodeB
Class C No reset
21 How to change OCNS

Procedure on how to create an OCNS WO using WPS.
1. Two ways to open WPS V7.1
Click Start, click Programs, click WPS V7.1 LTE_WPS 021-20110201, and click WPS V7.1
OR
Double Click on the Icon WPSV7.1
Alcatel-Lucent 9452 WPS as seen in Figure 1 after opening WPS V7.1..
9/2/2011
on the desktop.
Page 197 of 225
RF-E346
Issue 2.0
Figure 249
2. Import a snapshot
Click File, click Import and Export as in Figure 250.
Figure 250
On the Import & Export Wizard Window

Select Import snapshot, then select Next as in Figure 251.
9/2/2011
Page 198 of 225
RF-E346
Issue 2.0
Figure 251
On the Import snapshot (Local file system) Window

Select, Replace initial snapshot & discard existing orders, then select Next as in Figure 252.
Figure 252
On the Import snapshot (Local file system) Window Replace initial Snapshot & discard existing orders.
Select Browse, and search for the file as in Figure 253.
9/2/2011
Page 199 of 225
RF-E346
Issue 2.0
Figure 253
On the CM XML snapshot Window

Select the snapshot (xcm) file, then select Open as in Figure 254.
Note: You can also import an XML file to create the WO for OCNS.
Figure 254
Select Next, as in Figure 255.
9/2/2011
Page 200 of 225
RF-E346
Issue 2.0
Figure 255
Select Next, as in Figure 256.
Figure 256
Select No, proceed without saving (cancel available).
Select Start as in Figure 257.
9/2/2011
Page 201 of 225
RF-E346
Issue 2.0
Figure 257
Select Close as in Figure 258.
Figure 258
Click on the Icon for Search including attributes as in Figure 259.
9/2/2011
Page 202 of 225
RF-E346
Issue 2.0
Figure 259
Click on the Tab for Edition.
Type OCNS, then click on the Icon for Find next as in Figure 260.
Figure 260
Two types of OCNS as in Figure 261

loadTargetForOCNSonPDDCH
loadTargetFOrOCNSonPDSCH
Figure 261
9/2/2011
Page 203 of 225
RF-E346
One can set the value from 0 to 100% loading as in Figure 14.
Type 50 for 50% loading , then select Set as in Figure 262.
Issue 2.0
Figure 262
Value changed from 0 to 50 for loadTargetForOCNSonPDSCH as in Figure 263.
Figure 263
By type settings is for multiple sectors or multiple eNBs as in Figure 264.
Scroll from left to right and search for loadTargetForOCNSonPDSCH as in Figure 264.
9/2/2011
Page 204 of 225
RF-E346
Issue 2.0
Figure 264
Setting 50% OCNS-PDSCH on multiple eNBs as in Figure 265.

Highlight loadTargetForOCNSonPDSCH and select the multiple eNBs you want to set as in Figure 265.
Figure 265
Type 50, then select Set button as in Figure 266.

Results of the multiple eNBs (LteCell086002 and LteCell086003) after setting the value to 50 as in Figure
266.
9/2/2011
Page 205 of 225
RF-E346
Issue 2.0
Figure 266
LteCell086002 and LteCell086003 were set to 50% OCNS as in Figure 267.
Figure 267
Creating a WorkOrder for LteCell086002 and LteCell086003 as in Figure 268.

Click new workorder (current) as in Figure 268.
Notice the eNBs for 086002 and 086003 for changes from 0 to 50 as in Figure 268. Previous value was 0
, Value 50 (this is the new value for OCNS).
9/2/2011
Page 206 of 225
RF-E346
Issue 2.0
Figure 268
In the Workorder new workorder window as in Figure 269.

In the Name box, supply a name for this procedure.
In the Description box, supply a description of this procedure.
In the Originator box, supply your name.
Click Apply to complete the process, and OCNS_PDSCH_20110311 will be displayed under
Workorders as in Figure 270.
Figure 269
WorkOrders created OCNS_PDSCH_20110311 as in Figure 22.
9/2/2011
Page 207 of 225
RF-E346
Issue 2.0
Figure 270
In the window as in Figure 271, Right Click OCNS_PDSCH_20110311, select Export WorkOrder, and
select on local file system, to display window as in Figure 271.
Figure 271
On the Select an output file window, create a File Name, then select SAVE as in Figure 272.
Figure 272
On the local file system window, the creation for WorkOrder OCNS_PDSCH_20110311.xwo and
OCNS_PDSCH_20110311_reverse.xwo as in Figure 273.
9/2/2011
Page 208 of 225
RF-E346
Issue 2.0
Select Close to close the window as in Figure 273.
Figure 273
WorkOrder on your local file system as in Figure 274.

FTP files (.xwo) to customer network to apply the WorkOrder through SAM.
Figure 274
22 How to examine system parameters and change neighbor list using WPS
Follow the steps below:
1. Download LTE WPS from follow LiveLink (required login/password)
Note : To get login/password call help desk and request access to LiveLink
https://wcdma-ll.app.alcatel-lucent.com/livelink/livelink.exe?
func=ll&objId=61577920&objAction=browse&sort=name&viewType =1
9/2/2011
Page 209 of 225
RF-E346
Issue 2.0
Recommend to download the latest and greatest version available in this link.
2. There are two file in each folder, download both files, one for setup and one for plug in. Plug in extension
is .wipsar and other file is setup file. If setup file is not with extension of .exe, add .exe to this file before
execute it.
3. LTE WPS can be installed in same computer with UMTS WPS, DO NOT have to uninstall UMTS WPS,
but make sure store in different directory from UMTS WPS.
4. Make sure unzip plug in and place in same directory where WPS setup program located. Plug in file has
extension of .wipsar
5. Common issue install with in-correct plug in or no plug in, after installation and importing snapshot,
there is no eNodeB display. If this issue occurs, reinstall and install again with proper plug in.
6. Follow Using WPS specifically written for RF for common RF related work such as changing parameters,
add/delete neighbor list.
23
How to use SAM to collect call trace data
The 5620 SAM supports call trace on eNodeB NEs. Call trace is a function that collects call-level data on an
interface. This data can be transferred to an external system for processing and analysis, and the resulting
information can help a network operator do things such as the following:
identify performance issues that may affect end-user QoS or SLAs
troubleshoot device malfunctions
monitor resource usage for capacity management
validate end-to-end network transmission
The 5620 SAM supports the following call-trace session types:
cell-baseda trace that the SAM initiates at operator request or as a scheduled task
event-baseda trace that begins when a specified threshold value is reached
signaling-baseda trace that the MME initiates
debuga troubleshooting trace performed by Alcatel-Lucent technical support
Note:
The user should have a proper login credentials to access SAM GUI Client for setting
call trace session and unix login to auxiliary servers to retrieve the log files.
Once the user log in to SAM GUI interface, follow this path as indicted below in Figure 275
Manage -> Mobile Access -> Call Trace Sessions
Figure 275 Call Trace Session menu
9/2/2011
Page 210 of 225
RF-E346
Issue 2.0
This action will pop up a new window called Manage Call Trace Sessions [Edit]. Please see enclosed Figure
276 and on this window select second tab which is Call Trace Sessions.
Figure 276 Manage Call Trace Sessions

Then click on Create button as shown in Figure 276. This will pop up another window called Call Trace Session
[Create]
Figure 277 Call Trace Session

This is the window where user will set the attributes related to a call trace,
Step1: Click on Select button to add eNBs those are needed to be traced. This will pop up another
window called Select eNodeB Instance as shown below.
Step2: Populate CallTraceSessionName & Description fields in Call Trace Session window.
Step3: Depending up on the requirement check the necessary fields to be traces. These three options
are available for eNodeB tracing.
o isRRCTraced For RRC layer tracing
o isS1MMETraced For S1 interface tracing
9/2/2011
Page 211 of 225
RF-E346
Issue 2.0
o isX2Traced For X2 link tracing

Once above steps are completed click on Apply button.
Selecting eNodeB Instances:
When you click Select button from Figure 277, you will get the window as in Figure 278.
Figure 278 Select eNodeB Instance

Click on Search button which will populate with entire list of eNodeBs currently managed by the SAM.
Select the eNodeBs by highlighting them and click OK button.
Note: Maximum numbers of eNodeBs can traced are limited to 100 in LA3.0
Figure 279 Call Trace Session

Once above mentioned steps completed, you will notice Activate button as shown in Figure 279. Click this button
will activate eNodeB trace and trace logs will be collected at the following location on Auxiliary server.
9/2/2011
Page 212 of 225
RF-E346
Issue 2.0
/opt/5620sam/calltrace
The eNodeB call trace file name format will be as shown below example.
A20110309.1731-0400-eNodeB.TAG_ENB_NAME.31001232769.115.gz
24
How to use SAM to change the antenna electrical tilt
In LA3.0 antenna electrical tilt can be adjusted remotely through SAM/NEM interface. For this functionality to work
properly actuator should be connected to RRH through AISG interface cable for remote controlling of antenna tilt.
Note: The user should have a proper login credentials to access SAM GUI Client.
Once log into SAM GUI client highlight the eNB for which you want to view and modify antenna tilt.
Right click on highlighted eNB and select Launch NEM which will launch a new window displaying eNB
related information.
Figure 280 NEM Display

Above picture is showing the hardware elements of a eNB. This screen displays CCM, BBU RRH, RET, TMA and
other components currently installed at the site.
Click on RET to see Remote Electrical Tilt related information.
9/2/2011
Page 213 of 225
RF-E346
Issue 2.0
Figure 281 RET Selection

This screen presented with a list of RET units that were discovered in the AISG bus by one or more of the RRHs
in the eNodeB. The first column is the name assigned by the system to each of these units. The second column
is the RET Logical Id that is not currently used by the system.
Some of these attributes are retrieved from these units when they were discovered and other attributes are
associated to the use of these units in our eNodeB.
The Unique Identification Number
Number of Actuators,
Maximum Tilt,
Minimum Tilt,
Mechanical Tilt (installed tilt);
Configuration File Name,
Current Tilt,
Serial number
9/2/2011
Page 214 of 225
RF-E346
Issue 2.0
Figure 282 RET Aid Table Display

RF Engineers can verify RET assignments for each antenna connected to eNB equipment. Click on Antenna
Port from eNB Tree on left side panel.
Figure 283 Antenna Ports in eNB Tree
Click on Antenna Ports on left side eNB tree view.

Click on Antenna Port RET tab on right side panel to view antenna post assignments to RET devices.
The following figure shows the RET assignments to each of the antenna ports. Notice that the same RET is
shown in two pairs of antennas because one RET control the tilt of both antennas on the sector.
Figure 284 Antenna Port Assignments

Antenna assignment to RET device information is critical to avoid mistakes while selecting the right sector to
change electrical tilt.
Changing Electrical Tilt:
9/2/2011
Page 215 of 225
RF-E346
Issue 2.0
3
1
4
Figure 285 Steps for tilt changes
Please make sure that below steps are followed to read currently set tilt information and changing the electrical tilt
and updating mechanical tilt.
Select HW Modules (1).

Select RET from eNB Tree on left side panel (2)
Select RET Aid Table tab on right side panel (3)
Make sure that you see all the field in right side panel by dragging the slide bar (4)
Click on row of RET which we are planning to change under Antenna Tilt field right click to see options
available for editing antenna tilt information.
Figure 286 Edit RET Data menu
9/2/2011
Page 216 of 225
RF-E346
Issue 2.0
From the above picture select Edit RET Data option for editing tilt information. A new window will pop up showing
current tilt information for that particular RET device.
Figure 287 Edit RET Data window

Below window is expanded version of Edit RET Data which displays current tilt information.
Figure 288
The following changes can be made on this window.
RET Log Number: This information is for record purpose.
Mechanical Tilt: This field is for recording the mechanical tilt set in the field. User can populate
mechanical tilt and any changes to this field will not change Mechanical tilt of the antenna in field.
Antenna Tilt: This is the field for changing electrical tilt of the antenna. User should make sure that any
changes to this field values should be within minimum and maximum allowable tilt for a given antenna.
Once the right values are populated click on OK button.
Once the user click OK button after setting the right values for antenna tilt, it will take about a minute to initiate
actuators and display will be updated with new tilt values.
25
Procedure to change antenna azimuth and mechanical tilt
9/2/2011
Page 217 of 225
RF-E346
Issue 2.0
Changing antenna azimuth and mechanical tilt can be used to enhance coverage and control interference. They
are performed by the customer. Because they are expensive to perform, the justifications need to be well
documented. They should include:
The drive test plots that indicate the points of concern, for example, the location of call drop or low
throughput.
The analysis that shows why you think antenna azimuth change or mechanical tilt will alleviate the
problem.
9955 design tool plots that show the predicted performance before and after the change.
Scanner data plots that show the coverage and interference of each PCI.
After you have prepared the justification material, you should discuss with the RF lead. If the RF lead agrees, you
and the RF lead should present it to the customer representative. An alternative is to present it to the ALU
program manager, and have the program manager present it to the customer.
26
Plot scanner data to compare LTE signal strength vs. UMTS and GSM signal strength
Under Construction
27
Additional Information
27.1 Support Escalation Path

Legend
LTE
ALU Installation/Integration/Optimization
LTE &
2G/3G
ORACL
E
eNB
SR/SAR
M&P
SAM
IPD (SAM)
TAC
RITC (eNB)
Bob Witts
John Lackey &

Stacy Groene
Paul Chory
RF
OSC
Kwing Lee
Paul Augustine
eNB Dev
Saurabh Gupta
7705 SAR
IPD TAC
Cyril Nadavallil
Oracle
HWR/Solaris
TAC
(Umesh Joshi)
Issue Type
SAM
Application
TEC NAR
(eNB)
Robin Schmuckal
7750 SR
SUN
Support
SAM Install
IPD (7750)
TEC
David M. Wong
James J. Zhang
IPD (7705)
TEC
Harry Schenk
IPD (SAM)
TEC
Robert Baker
IPD (SAM)
Dev
IPD DEV
IPD DEV
Chris Lefebvre
Assumes: 7x24 support will be provided starting Jan 1, 2011 for internal teams
except IPD SR/SAR.
9/2/2011
Page 218 of 225
RF-E346
Issue 2.0
Legend
LTE
LTE &
2G/3G
ORACLE
NPO
HP
AT&T
TAC
CITRIX
(Allison Burns)
Chris
Zervos
HWR/SOLARIS
CiITRIX outside
warranty
period and no
RTS contract)
HWR/SOLAR CITRIX
IS CITRIX
(within
warranty
period)
Issue Type
AT&T
ALU SWR
HWR/OS
(Allison Burns)
Tu-Chuong
Huynh
Issue Type
NPO
Application
NPO
WPS
SAM
WTA
Issue Type
CITIRX
TEC NAR
(NPO)
HWR
Robin Schmuckal
HP HWR/OS
CITRIX
ORACLE
NPO Dev
(Assignee based on
tracker)
except IPD SR/SAR.
9/2/2011
Page 219 of 225
RF-E346
Issue 2.0
LTE &
Legend
2G/3G
LTE
LTE &
2G/3G
WPS
WTA
Rajiv Singal
TAC
(Allison Burns)
Robin
Schmuckal
WPS
development
WTA SE/Dev
Amy Ortega
except IPD SR/SAR.
9/2/2011
Page 220 of 225
RF-E346
Issue 2.0
ALU RF Optimization
Kwing Lee
MME,
P/S-GW
Escalation
path
This is explained in
Specific eNB and
7750/7705 paths
eNB issue
OSC
Paul Augustine
Type
of
issue
Transport Issue
(7705 SAR/7750 SR)
Pauls team Will

continue
get support from
Robin Schmuckal
Pauls team
Contact
7750 SR/7705 SAR
Support
Listed in other
paths
TEC NAR
Robin Schmuckal
MME,
P/S-GW issue
Direct
AT&T
Contact
No, not getting

proper support,
escalate to ALU Market
TPM
Yes,
Successful
Look Below for

AT&T MME and
P/S-GW contacts
Market TPM
Phoenix: Charly Dukes
NY/NJ: Michael Lee/
Tim Duff
BAWA: David Craig
Contact AT&T
Market
PM and get
resources
9/2/2011
Page 221 of 225
RF-E346
Issue 2.0
ALU RF Optimization
Kwing Lee
No
Understo
od what
the issue
is
Antenna
Issue?
Antenna
Work (Tilt,
Azimuth)
Escalation
Path
Yes
OSC
Paul Augustine
Which
Market
TEC NAR
Robin Schmuckal
PHOENIX
BAWA
Market PM
Charles
Williams
Market PM
Sreedhar
Appasani
NY/N
J
Market PM
Joseph
Valente
Installati
on
Team
27.2 Filzella
FileZilla Server (windows) to be used as last resort when winds and iperf are not available
Filezilla Server Interface you have to modify some value:
o Settings/Miscellaneous
o Internal BufferSize=65535
o Socket BufferSize = 262144
Step1: Configure the Connection Speed with the maximum value 20000 kbps)
Step 2: Select Modify all Network Adapters
Step 3: Configure the MTU value with 1446
9/2/2011
Page 222 of 225
RF-E346
Issue 2.0
Step 4: Select Optimal Settings

Step 5: Apply Changes
Step 6: Restart the computer
Set Max connections as indicated in the picture below
Launch the Filezilla software

Populate the Host ip, username and password
Click on Quickconnect (This would authenticate the login account)
For downlink testing locate the files on the remote location and drop on the local directory
For uplink testing locate the files on the local directory and drop on the remote director
The following diagram highlands the location of the FTP server for the End-to-End setup
9/2/2011
Page 223 of 225
RF-E346
Issue 2.0
27.3 DOS FTP

DOS-FTP can be used as resort when Winds and Iperf are not available
Open up a command prompt by click on start->run->type cmd and hit enter
Log into the FTP server
o ftp 135.245.4.38
o Inter user name (e.g admin)
o Inter password (e.g admin1)
o Change directory to where the files would be downloaded from or uploaded to
o Set to binary by typing bin and press enter key
o Set to hask key by typing ha and press enter key
Downloadable files - downlink
28
Reference
9/2/2011
Page 224 of 225
RF-E346
Issue 2.0
LTE Engineering Optimization Handbook

LTE Optimization Troubleshooting Handbook
Documentations and Supports for Syncro Test, WINDS, and eDAT
29
Acronyms
BLER
BW
CFI
CQI
CTA
DL
ePC
GNG
HARQ
ICD
IoT
MCS
MIMO
OCNS
PDCCH
PDSCH
PUSCH
QOS
R&D
RACH
RF
RLC
RRH
RSRP
RSRQ
rx
SAM
SINR
SME
SOW
tx
UE
UL
Block Error Rate

Bandwidth
Control Frame Indicator
Channel Quality Indicator
Customer Technical Advocate
Down Link
Evolved Packet Core
Go-No-Go
Hybrid Automatic Retransmission
Request
Initial Cluster Design
Interference over Thermal
Modulation and Coding Scheme
Multiple Input Multiple Output
Orthogonal Channel Noise Simulator
Physical Downlink Control Channel
Physical Downlink Share Channel
Physical Uplink Share Channel
Quality Of Service
Research and Development
Random Access Channel
Radio Frequency
Radio Link Control
Remote Radio Head
Reference Signal Received Power
Reference Signal Received Quality
Receive
Service Awareness Manager
Signal to Interference plus Noise Ratio
Subject Matter Expert
Statement of Work
Transmit
User Equipment
Up Link
END OF PROCESS DOCUMENT
9/2/2011
Page 225 of 225

LTE RF Optimization Methods &amp; Procedures

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LTE RF Optimization Methods &amp; Procedures

Uploaded by

Copyright:

Available Formats

RF-E346

LTE FDD RF Optimization Methods & Procedures Internal Version

LTE FDD RF Optimization Methods & Procedures

Alcatel-Lucent PROPRIETARY Use pursuant to Company Instructions

LTE FDD RF Optimization Methods & Procedures Internal Version

Data collection kit configuration

Alcatel-Lucent PROPRIETARY Use pursuant to Company Instructions

LTE FDD RF Optimization Methods & Procedures Internal Version

Revise the organization and the content of the whole

Alcatel-Lucent PROPRIETARY Use pursuant to Company Instructions

LTE FDD RF Optimization Methods & Procedures Internal Version

Performance in a LTE system depends on many different critical elements..................................9

Data Collection Kit Configuration........................................................................................................... 26

How to set up and use LG Adrenalin UE................................................................................................27

LLDM (LGE Logging Diagnostic Monitor) Introduction...................................................................36

Alcatel-Lucent PROPRIETARY Use pursuant to Company Instructions

LTE FDD RF Optimization Methods & Procedures Internal Version

How to set up and use NEMO to collect drive test data.......................................................................61

How to use JDSU E6474A-X to collect Drive Test Data........................................................................79

How to use JDSU Scanner...................................................................................................................... 82

Activate JDSU E6474A-X.................................................................................................................... 82

How to use PcTel Scanner.................................................................................................................... 109

Establish Remote Control Connection........................................................................................... 119

Data Collection Procedure.................................................................................................................... 136

Opening a Project (eg. ATT LTE)..................................................................................................... 103

LTE FDD RF Optimization Methods & Procedures Internal Version

LLDM Data Collection Software....................................................................................................... 136

Alcatel-Lucent PROPRIETARY Use pursuant to Company Instructions

LTE FDD RF Optimization Methods & Procedures Internal Version

How to detect problems and how to fix them......................................................................................167

Maximize distance between co-PCI cells........................................................................................ 167

How to use SAM to examine network status.......................................................................................188

How to use SAM to change eNodeB parameters................................................................................191

How to change OCNS............................................................................................................................ 194

How to use SAM to collect call trace data...........................................................................................207

How to use SAM to change the antenna electrical tilt........................................................................210

Procedure to change antenna azimuth and mechanical tilt...............................................................214

Additional Information........................................................................................................................... 215

Support Escalation Path.................................................................................................................. 215

Alcatel-Lucent PROPRIETARY Use pursuant to Company Instructions

LTE FDD RF Optimization Methods & Procedures Internal Version

Having full end-to-end connectivity with the EPC (S1-SGW, S1-MME.)

Toolkit, NEMO, LLDM, JDSU, IPerf:

Alcatel-Lucent PROPRIETARY Use pursuant to Company Instructions

LTE FDD RF Optimization Methods & Procedures Internal Version

eDAT, Syncro Test, WINDS, SPO, ROVA:

Performance in a LTE system depends on many different critical elements

There are a lot of performance impacting parameters available

Alcatel-Lucent PROPRIETARY Use pursuant to Company Instructions

LTE FDD RF Optimization Methods & Procedures Internal Version

Cell site coverage parameters

Alcatel-Lucent PROPRIETARY Use pursuant to Company Instructions

LTE FDD RF Optimization Methods & Procedures Internal Version

Specified number of REs can be keyed up to generate RF interference from surrounding

Optimization Deployment Team Structure

Figure 1 Optimization Deployment Team Structure

Subject Matter Expert (SME)

Alcatel-Lucent PROPRIETARY Use pursuant to Company Instructions

LTE FDD RF Optimization Methods & Procedures Internal Version

Provides LTE technical troubleshooting support

Service Aware Manager (SAM) Engineer

RF Cluster Engineer Lead

Logistics Coordinator/Drive Test Coordinator

Alcatel-Lucent PROPRIETARY Use pursuant to Company Instructions

LTE RF Optimization Methods & Procedures

LTE RF Optimization Methods & Procedures