TTP30026W - LTE RF Optimization Methods PR PDF

LTE RF Optimization Methods & Procedures
TTP30026
Bill (William) Hsieh
Central Quality Assurance & Customer Care
July 14, 2010

Learning Objectives
Upon completion of this training session, the attendee should be able to:
 Get a high level overview of the Optimization Methods and Procedures
 Recognize the trade offs between Local Optimization vs Partial Remote

Optimization, Syncro Test vs. No Syncro Test
 Recognize the functions of RF Engineer, Data Collector, and Driver
 Get a high level overview of how to collect data and analyze data
 Detailed steps are presented in “LTE RF Optimization M&P”, draft available in

2 weeks
 Write to williamhsieh@alcatel-lucent.com for URL
 TTP21400 eDAT for LTE, TTP30025 LTE Toolkit and LLDM
2 | Presentation Title | Month 2006 All Rights Reserved © Alcatel-Lucent 2006, #####
Event Sequence
 Attend kick-off meeting with customer to confirm mutual expectations on:
 Entrance criteria
 Exit criteria like throughput, hand-over failure rate, and other KPIs.
 Local or Partial Remote Optimization
 Interface between the customer and ALU
 Problem resolution: like how to change antenna, how to change

parameters, when to collect data
 All the negotiated items should be written on a piece of paper and signed
by both the customer and ALU representatives.
Event Sequence (Continue 1)
 Order WIND servers, DAT machines, and Data collection kits
 Configure WIND servers, DAT machines, and Data Collection machines.
 Install WINDS server
 Hire drivers, data collectors, rent van, train data collectors
 If the sector test information is not provided by either the customer or third
party, conduct sector test to ensure that the eNodeB and antennas are
configured, installed, and operates properly.
 For stationary KPIs, identify the data collection spots. (SINR between 13 and
17 dB)
 For mobility KPIs, design cluster test drive route and the System Verification
drive route. Obtain customer agreement on the cluster driver routes.
 Baseline the existing system
Event Sequence (Continue 2)
 Analyze the data, identify problem area, devise solution, and obtain
agreement from customer about the solution
 Change the parameters, re-collect the data
 After having done all the cluster tests, conduct the System Verification drive.
 Similar to Cluster drive, collect data, analyze data, identify problem areas,
devise solutions, obtain agreement from customer about the solution
 Chang the parameters, and re-collect the data.
 Compare the final result with the Baseline result
 Prepare Exit Package
 Obtain customer’s agreement in writing on the satisfaction of exit criteria
Local vs. Partial Remote Optimization
Definition
 Local: All personnel in market
 Partial Remote: Only some of the engineers in marke
Benefits of Partial Remote Optimization
 Efficient use of skilled resources
 Saves on Travel and Entertainment
 Keep RF engineers happy
Partial Remote Optimization
Requirements
 Customer is receptive
 Market requires more than one RF engineers
 Well defined communication between in-market team and off-market team
 Share server, VPN, FTP, login, password available
Syncro Test benefits
 Not going to the data collection site.
 Speeds up turn around time by remotely transfer the data from the data
collection van to the Data Analysis PC.
 The RF engineer can analysis the data in the office, change the parameters
and re-collect the data.
 Collect data from several vans at the same time.
 The Syncro Test data collector can be less skillful and easier to recruit
Requirement
 Access to a separate data network
Entrance Criteria
 Should be specified in the Statement Of Work before the start of Optimization
 Status of Network should be delivered to Lead RF engineer 1 week before

Optimization
 Provide RSRP map and SINR map
 Provide eNodeB site locations
 Provide Neighbor List
 Specified condition of the test environment, like minimum RSRP, SINR,

backhaul available throughput
 Having completed all integration tests for all eNodeBs within 2nd tier of
cluster
Entrance Criteria (Continue 2)
 Being free of critical and major alarms for 48 hours
 Having transmitted the proper Cell ID from each sector
 Having successfully handovered calls between sectors of the same eNodeB
 Having cleared the spectrum
Exit Criteria
 Up Link Throughput
 Down Link Throughput
 Radio Resource Control (RRC) Failure Rate
 Radio Resource Control (RRC) Drop Rate
The testing conditions, KPI definitions and Exit Criteria should be clearly
defined and signed by ALU and the client.
Optimization Data Collection Overview
WINDS Application Server PC
 Should sit close to PGW
 Should NOT go through private or public internet
 Should be assigned a static IP address
 WINDS
 VNC
 Syncro Test WINDS Probe
Configuring Data Collection PC
 Turn PPP Compression off
 Turn IP header compression off
 With Syncro Test
o Enable remote data collection
o Quick turn around
o Requires access to a separate data network
 Without Syncro Test
o More intimate knowledge of data collection environment
Configuring Data Collection PC (Continue 2)
WINDS Client
 UDP, you can pre-define for both send and receive
o Data rate
o Payload size
o Duration
 FTP, you can pre-define for both send and receive
o Data block size
o Duration
 Ping, you can pre-define

o Timeout
o Duration
Data Collection PC (Continue 3)
Syncro Test LLDM Probe:
 Controls LLDM
Serial Splitter
 Distributes GPS signal to several com ports
 Software is pre-installed in the Data Collection PC
Street Atlas:
 You can predefine drive route
 You can predefine eNodeB locations
 It will show you where you are with reference to eNodeBs and predefined drive
route
 It will help reduce the chances of making wrong turns and having to re-collect
the data
DAT PC
Syncro Test (Master Controller)
 Remotely controls the LLDM via Syncro Probe
 Pre-configures the test cases
VNC
 Remote control of WINDS Server
eDAT
 Data Analysis
Staffing Functions
RF Engineer
 Interface with customer
 Hire data collector and driver
 Train data collectors
 Obtain spectrum clearance data
 Define clusters and verification drive routes
 Setup drive testing tools
 Analyze collected data
 Consult with customer to change parameters and antenna azimuths and tilts
 Prepare exit package
 Obtain customer sign off
Staffing Function (Continue 3)
Data Collector:
 Manage the data collection PC, the UE, and the GPS
 Start and stop the data collection at the proper location
 Make sure that there is communication between the eNodeB and the UE
 Make sure that data is being collected by the data collection software
 Transfer the collected data to the Lead Engineer
 Assist the driver in navigating along the drive route
Driver:
 Obtain the drive route from the Lead Engineer
 Prepare sufficient money for toll and gas
 Drive safely
Sector Testing
Purpose: Ensures sectors are:
 Radiating at expected power levels
 Radiating in the correction directions
 Radiating the correct Cell ID
 Handing over to intra-eNodeB sectors properly
 Procedure:
 Start from the bore sight of the sector to be tested within ¼ to ½ cell radius
 Set up LTE session on UE1, start the ping test, then start logging on LLDM
 Set up LTE session on UE2, start FTP, start logging on LLDM
 Collect data for a few minutes to obtain stationary throughput data under good
RF condition.
 Drive around the eNodeB.
 Once in the bore sight of the second sector, repeat the stationary test
Stationary Test
Purpose: Collect data in a predefined RF condition while standing still
 Locate positions that meet predefined RF conditions, like SINR between 17 dB

and 21 dB using LLDM
 The spots should be in areas where the van can park for a long time
 Identify the spots on a map
 Conduct predefined tests
Cluster Test
Purpose: Optimize a manageable piece of the network at a time
 Cluster size: 15 to 30 eNodeBs
 Core area will be divided into clusters
 Border area will be grouped with Inter-frequency or Inter-Technology handover

enabled eNodeBs.
 Available drive routes
 Readiness of eNodeBs (most efficient is when 100% of the eNodeBs are

available)
 Heavy handover area should not be broken up into multiple clusters
Cluster Test Drive Route and other considerations
 Within the predefined coverage area based on RSRP or SINR
 Total duration of a 19 eNodeB cluster drive should be between 5 to 9 hours
 Covers all the eNodeBs within the cluster
 Covers all the major rouads and intersections
 Covers all the handovers within the cluster
 Avoid coverage holes
Other considerations:
 Loaded and Un-loaded drives should use the same cluster drive route
 Forward Loading: Use OCNS
 Reverse Loading: will not perform because of high cost
Data Collection – With Syncro Test – DAT PC
For RF engineer in the office:
 In the DAT PC, find out the IP address of the PPP adapter
 Tell Data Collector in the van of the IP address
Data Collection – With Syncro Test – Data Collector PC
For Data Collector in the van:
 Physically connect LG UE to the Data Collector PC
 Start LLDM
 Set Com Port to allow LLDM to communicate with UE
 Start LG LTE CM
 In the LG LTE window, click to start the synchronization process and the
attach process
 Start Syncro Test LLDM Probe to display:
Data Collection – With Syncro Test – Data Collector PC (continue 2)
•Click Tools, and click options to display
Data Collection – With Syncro Test – Data Collector PC (continue 3)
In Probe
ID, type in
a unique
identifier.
In
Adapter,
select
Wireless
Connectio
n
In
Control
Server
Address:
Key in the
IP address
provided
by the RF
•In Syncro test LLDM Probe, click Register to enable the RF engineer to control
Engineer
LLDM Probe from Master Controller in the office
Click OK
Data Collection – With Syncro Test – DAT PC
 Syncro Test Master Controller window:
 Click File, and click

Load Predefined
Tests
 Click Predefined
Tests and select the
test case
 Click Start Test
 Click Start Logging
 Click Stop Test
 Click Stop Logging
Data Collection – With NO Syncro Test
Use Only WINDS Client and LLDM
 Connect LG UE to the Data Collector PC
 In the Data Collector PC, start LLDM
 Start LG LTE CM
 In the LG LTE window, click to start the synchronization process and the
attach process
 Start WINDS Client
Data Collection – With NO Syncro Test (Continue 2)
 In WINDS window, click Transfer, select the test case and fill in the
parameters
 Click Start to start the test
 In LLDM window, click to open Logging Status window
Data Collection – With NO Syncro Test (Continue 3)
 Click Start to start logging.
 Click Stop to stop logging.
Baseline Existing System
 Before optimization, collect data for every cluster
 Calculate the KPIs
 Used to compare with Post-optimization KPIs
Data Analysis - eDAT
 Import LLDM data

and WINDS data
 Automatically
import maps from
ALU server
 Filter and massage

and present data in
many different
ways
 For example,
Present several KPIs
on the same map to
help identify
problem
Data Analysis – eDAT (Continue 2)
 Map and Grid together
 Identify and group messages
Filter in only data in agreed up RF environment
Build-in Reports

TTP30026W - LTE RF Optimization Methods PR PDF

Uploaded by

Document Information

Original Title

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

TTP30026W - LTE RF Optimization Methods PR PDF

Uploaded by

Copyright:

Available Formats

LTE RF Optimization Methods & Procedures

Bill (William) Hsieh

Central Quality Assurance & Customer Care

July 14, 2010

 Get a high level overview of the Optimization Methods and Procedures

 Recognize the trade offs between Local Optimization vs Partial Remote

 Recognize the functions of RF Engineer, Data Collector, and Driver

 Detailed steps are presented in “LTE RF Optimization M&P”, draft available in

 Write to williamhsieh@alcatel-lucent.com for URL

 TTP21400 eDAT for LTE, TTP30025 LTE Toolkit and LLDM

 Attend kick-off meeting with customer to confirm mutual expectations on:

 Local or Partial Remote Optimization

 Interface between the customer and ALU

 Problem resolution: like how to change antenna, how to change

 Order WIND servers, DAT machines, and Data collection kits

 Configure WIND servers, DAT machines, and Data Collection machines.

 Install WINDS server

 Hire drivers, data collectors, rent van, train data collectors

 Baseline the existing system

 Change the parameters, re-collect the data

 Chang the parameters, and re-collect the data.

 Compare the final result with the Baseline result

 Prepare Exit Package

 Obtain customer’s agreement in writing on the satisfaction of exit criteria

 Local: All personnel in market

 Partial Remote: Only some of the engineers in marke

Benefits of Partial Remote Optimization

 Efficient use of skilled resources

 Saves on Travel and Entertainment

 Keep RF engineers happy

 Market requires more than one RF engineers

 Well defined communication between in-market team and off-market team

 Share server, VPN, FTP, login, password available

 Not going to the data collection site.

 Collect data from several vans at the same time.

 Access to a separate data network

 Should be specified in the Statement Of Work before the start of Optimization

 Status of Network should be delivered to Lead RF engineer 1 week before

 Provide RSRP map and SINR map

 Provide eNodeB site locations

 Provide Neighbor List

 Specified condition of the test environment, like minimum RSRP, SINR,

 Being free of critical and major alarms for 48 hours

 Having transmitted the proper Cell ID from each sector

 Having successfully handovered calls between sectors of the same eNodeB

 Having cleared the spectrum

 Down Link Throughput

 Radio Resource Control (RRC) Failure Rate

 Radio Resource Control (RRC) Drop Rate

 Should sit close to PGW

 Should NOT go through private or public internet

 Should be assigned a static IP address

 Syncro Test WINDS Probe

 Turn PPP Compression off

 Turn IP header compression off

 With Syncro Test

o Enable remote data collection

o Quick turn around

o Requires access to a separate data network

 Without Syncro Test

o More intimate knowledge of data collection environment

 UDP, you can pre-define for both send and receive

 FTP, you can pre-define for both send and receive