LTE RF Optimization Methods & Procedures

(1)

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 Date: William Hsieh

(2)

Authors

This part provides the names of the authors who wrote the respective sections (Some sections have been deleted).

Section

Number Section Title Author

1 Entrance Criteria William Hsieh

2 Exit criteria William Hsieh

3 Support Information Sreenu Pamidi

4 Organization chart Sri Adimulam

5 Optimization Strategy Alex Anokye

Sri Adimulam (Design Engineer Role) 6 Data collection kit configuration Guillermo Alvarez (Kit

configuration) Alex Anokye (PC configuration)

7 Naming Convention Saad Al Adhami

8 How to set up and use LG Adrenalin UE Guillermo Alvarez

9 Using IPerf and WINDS Alex Anokye

10 How to set up and use LLDM to collect drive test

data Alex Anokye

11 How to set up and use NEMO to collect drive test

data Guillermo Alvarez

12 How to use JDSU E6474A-X to collect Drive Test

Data Guillermo Alvarez

13 How to use JDSU scanner Cliff Castillo

14 How to use PcTel scanner Auillermo Alvarez

15 How to set up and use Syncro Test Aderemi Adeyeye

16 Data Collection Procedure Aderremi Adeyeye

17 How to use eDAT Mateen Hussain

18 How to detect problems and how to fix them Alex Anokye 19 How to use SAM to examine network status Sri Adimulam 20 How to use SAM to change eNodeB parameters Sri Adimulam

21 How to change OCNS Cliff Castillo

22 How to examine system parameters and change neighbor list using WPS

Vansotheavy Sem 23 How to use SAM to collect call trace data Sri Adimulam 24 How to use SAM to change the antenna electrical

tilt Sri Adimulam

25 Procedure to change antenna azimuth and

mechanical tilt William Hsieh

26 Plot scanner data to compare LTE signal strength

vs. UMTS and GSM signal strength Vansotheavy Sem

27 Additional Information Sreenu Pamidi

(Support Escalation Path), Alex Anokye (Server)

(3)

Date Section Title Reason Issue # September,29,

2010 Initial Release V1.0

September 2,

2011 All sections Revise the organization and the content of the whole document V2.0

(4)

 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

 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

(11)

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

o Actual user gets higher priority

 As test UE moves around, actual user data packets will substitute OCNS RE on the serving sector

o 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 person’s roles and responsibilities should be communicated to the entire team.

5.5 Optimization Deployment Team Structure

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 RF Director Data Factory RF Cluster Lead SME SAM Engineer Troubleshooting Team CTA/PLM Technical Lead

(12)

o Provides LTE technical troubleshooting support

o Provides assistance to RF Lead and Cluster Engineer in solving real-time problems

o Provides support to RF lead in explaining any technical issue that comes from the customer o Provides training for new RF engineers and contractors

o Work very closely with Troubleshooting team in Resolving RF issues o 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

(13)

 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

(14)

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

Obtain a copy of the RNP 9955 export that shows sites list, cell configuration: antenna heights, Azimuth, and tilts, PCI, Neighbor List

2 Get a WPS export to verify RNP data is captured correctly during provisioning ( this can possibly be done using RNP2PMCtool) 3 Obtain a copy of RF design CID report and view coverage prediction

4 Obtain MAPinfo files for Cluster & Supercluster Polygons (from Design Team) 5

Obtain Cluster Drive Route (Mutually agreed to by AT&T and Optimization Team) & Supercluster Drive Routes (from AT&T)

6 Export sites configuration & polygons onto Google Earth and view morphology of the Cluster 7 Obtain copies of antenna tilt settings screen-capture from installation team & verifyagainst design baseline 8 When sites come on air, review RITC integration report and check (1)Tx Power, (2)RTWP values, and (3) that call test were made

9

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.

10 Assess alarm impact & plan testing accordingly

5.9 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.

(15)

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

(16)

o Drive around 3 sectors close to a cell to ensure each sector is transmitting in the desired direction o To verify that PCIs are implemented correctly as per RF Design

o 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

(17)

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

(18)

 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

o 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

(19)

o Ensure minimal latency and packet drops between the PGW and external gateway to the internet/test server

o Important for realizing full potential of the LTE high speed data rates  FTP more sensitive to packet losses

 HTTP more sensitive to latency

o Consider regional distribution of PGW and SGW as opposed to cross-country location  Ideally both should be co-located

o Use of IP network tools to trace and isolate the problem link/element o Match line modes/speeds between various network elements in the chain

o Allocate proper bandwidth in the core network to support LTE peak data rates with several users across several eNBs

 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

o 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

(20)

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

(21)

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.

(22)

Overshooting Cell contributing to low throughput and drop call

(23)

Figure 11 Overshoot Impact on Drop Call

5.17 IRAT

5.17.1 IRAT Test Preparation Procedure:

1. Make sure that all parameters for LTE to eHRPD are reviewed

2. Define LTE to UMTS/eHRPD border route and agree with the customer 3. Test the UE in LTE only to make sure it works in LTE

4. Test the UE in UMTS/CDMA only to make sure it works in UMTS/CDMA 5. Configure the Communication Module to “GMSS”

5.17.2 IRAT Test Execution Procedure:

(24)

Figure 12 LLDM and QXDM 1. Attach in LTE

2. Check IP assignment (make a note) 3. Start DL UDP or FTP

4. Gradually drive towards the eHRPD/UMTS coverage area (away from LTE signal)

5. 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 (E-UTRA: 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]

(25)

5.17.3 Measuring LTE->UMTS/eHRPD HO interruption time using WiReshark (start capture packets in non-promiscuous mode)

1. Call is up on LTE – active DL data transfer (UDP or FTP)

2. HO to UMTS/eHRPD, wait until data transfer Resumes before you stop the logging 3. Take a note of the timestamp where MR was sent ‘Signal Log Messages’ on LLDM

4. 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. Attach on LTE

2. Check IP assignment (make a note)

3. Start pinging your test server (e.g. 10.203.9.200) 4. Stop pinging (make sure the UE goes idle)

5. Gradually drive towards the UMTS/eHRPD coverage area (away from LTE signal) 6. Make sure LTE signal is lost and you have UMTS/eHRPD – check your IP

(26)

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 Data Collection Kit Configuration 6.1 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

(27)

 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 Device 1 WABA_18_4_7_11Mar16 114524.1.nmf

LTE Scanner WABA_18_4_7_11Mar16 114524.4.nmf

UMTS/GSM Scanner WABA_18_4_7_11Mar16 114524.5.nmf

8 How to set up and use LG Adrenalin UE 8.1 LG Adrenaline Tips

 Adrenaline LED

Figure 16 LGE Adrenaline LED

(28)

Figure 17 Adrénaline 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

9 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

(29)

 Make sure iperf program is installed on your PC and Server

 Execute iperf from where the program resides 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

(30)

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

You’ll 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 iperf’s default is 1.0 Mbits/second, so it’s not a network problem. We can try some different values to see what happens. Let’s 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. That’s 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 2683/187644 (1.4%) The –i option generates a progRess display every second.

9.1 WINDS

Winds (Wireless IP Network Data Source) _ Background

(31)

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

(32)

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

(33)

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

(34)

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

(35)

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

(36)

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

(37)

10 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 Description CPU Pentium IV 1.8 GHz~ RAM 512MB ~ Video 1024 * 768 ~

Operating System Windows XP Professional

Interfaces USB 2.0 High Speed

(38)

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

(39)

Figure 34 Select Component to Install

(40)

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

(41)

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.

(42)

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

(43)

Figure 40 Port Setting Description

Port LTE USB Modem Port

Baud Rate Baud Rate (115200 fixed)

Flow Control Flow Control Type (None, Hardware,

Software type)

RTS RTS (Request To Send)

DTR DTR (Data Terminal Ready)

Log Mask 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.

(44)

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

(45)

Figure 42 Log Mask Setting Dialog

(46)

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 description

Logging status Current logging status

Log start time Time that logging was started

(47)

Stop Stop the logging

Pause Pause the logging

Resume 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

(48)

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

(49)

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

(50)

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.

(51)

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

(52)

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 can’t calculate PDCCH BLER because UE doesn’t 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.

(53)

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.

(54)

(55)

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)

(56)

ii. CHI L1 Control (checks whether Ue power is fixed or power control is turned on) iii. CH1 Signal Log Message (checks RRC and NAS signaling between UE and eNdoeB) iv. CH1 L1 Graph (visual Downlink information received by UE)

v. Logging Status (gives logging information such as log start time and log start end)

c. 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

Figure 58 Port Setting

(57)

Figure 59 Port Setting (2) e. Set up the GPS by clicking on GPS tab as indicated

Figure 60 GPS Set Up

f. Set up log mask using predefined log mask. Click on log mask icon; log mask sub menu would pop up

(58)

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”

(59)

Figure 63 Use Connection Manager to Connect

I. UE would synchronized with eNodeB and start the attach process

Figure 64 Attachment Process j. Monitoring Test Progress on L1 Signal Graph

Ue synchronized with eNB

Successful Attach

(60)

Figure 65 Signal Graph

K disconnect the Ue when test is done

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) Successful

(61)

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 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.

o Ensure that the Adrenaline LED is illuminated

o Query the modems to ensure that the UE is communicating with the laptop

o 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

 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

(62)

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

(63)

 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)

 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

(64)

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

 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

(65)

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

 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:

o Select “Work Offline”

o Disconnect the USB cable from the laptop

o Disconnect the scanner DC power cable so that it is off

o Reconnect scanner power cable, and connect scanner USB back to laptop o Enable Online mode in Nemo-Outdoor again

Figure 73 Non-responsive PCTEL Scanner prevents Nemo-Outdoor from going online

(66)

11.2.5 NEMO-OUTDOOR: WORK ON-LINE

 Click on the button to enable Online Mode (i.e. start the devices) o Device status indicator should be flashing green

o 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

(67)

Figure 77 - Record & start scripts in Nemo

o Press the Start Recording button if you want to start recording without executing the scripts

Figure 78 - Starting scripts without recording

o 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)

(68)

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

(69)

Figure 82 - Configuration Mgr through View Menu

o Within the User Interface Properties, select the Measurement tab o You can edit the Filename structure