Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
3Activity
0 of .
Results for:
No results containing your search query
P. 1
Data Throughput Issue

Data Throughput Issue

Ratings: (0)|Views: 34 |Likes:
Published by Enbi Acorda Ferrer

More info:

Published by: Enbi Acorda Ferrer on Oct 30, 2012
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as XLSX, PDF, TXT or read online from Scribd
See more
See less

07/12/2013

pdf

text

original

 
First thing to remember for throughput troubleshootingWhat kindof tools we need for troubleshoot ?Test SetupsBasic and Common steps to check before floodWCDMA (R99)
Data Throughput Issues
I ave een eng ase to trouesot te trougput ssueso many times. Unfortunately my experience says "There isno clear/logical/deterministic way to troubleshoot forthroughput test".Ten wat are we suppose to o Are we suppose to reyon "Hit and Miss" strategy everytime we do the throughputtest ? Is this process totally random ?No at least we are not in such a worst case, fortunately. Ithink we can set some guidelines at least.
LTE Physical Layer Throughput - PDSCH Decoding PerformanceThroughput in Live NetworkLinks on Throughput Test in the fieldFactors influencing the throughput
Throughput Test Software
iperf - UDP/TCP FloodingHSDPAHSPA+HSPA+ Dual CarrierIdeal MAX throughput for UMTS UECQI vs Throughput for UMTSLTE
ne sentence. Trougput trouesootng s not smpe atall.", "Don't expect it to be simple.". If I solved the problemwith single shot, I would say "I was just lucky, It is notbecause I am technically competent".Even troubleshooting with wired communication is not easy.Think about how many more factors would get involved inthe data path.That's all for the first thing. Now let's move to the secondimportant thing for this issue. What is the second thing ?
First thing to remember for throughputtroubleshooting
 
ii) TE port on PC (e.g, Ethernet Card).iii) TE port on throughput test equipment (e.g, Data packetport on Network Emulator)iv) PDCP layer on test equipmentv) RLC layer on test equipmentvi) MAClayer on test equipmentvii) L1 (Transport and PHY)layer on test equipmentIt's "Don't give up. You will eventually find the solution!" -:). It is just matter of time and depend on how muchdedicated you are during the troubleshoot.Now the third things comes (Many people think this is thefirst thing since it sound more technical, but I don't think itis the case).a wan you o o as er ems s up a enodes from the data transmitter to the reciever, and followall the steps without skipping anything.". One example I cangive you is (this is an example where you use a NetworkEmulator for the test).i) IP Application Software on PC (e.g, iperf, FileZilla)xiv) IP Application Software on PC to which the UE isconnected.e more you unersan on eac o ese ems, e eerposition you are in for troubleshooting. (If you really enjoyyour job as engineer, one of the topic I would recommendyou is to try with throughput troubleshoot or optimization.To me it looks like an art at the same time being atechnology).important, most critical factor for the throughput ?". I wish Ihad a simple/clear answer to this, but my experience says"the answer varies depending on the situation". Especially itwould differ depending on what kind of radio technolotyyour device is using. (e.g, Is it R99 WCDMA Device, HSDPA,HSPA+, LTE ?)viii) L1 (Transport and PHY)layer on UE (mobile phone ordata card)ix) MAClayer on UEx) RLC Layer on UExi) PDCP layer on UExii) TE port on UE (e.g, Modem connector)xiii) TE port on PC (e.g, USB port the UE is connected to)In aton to te maor tecnca actors ste aove,sometimes very simple things as follows make you spendseveral hours to several weeks for troubleshoot if you are inbad luck.
 
w ry o go roug eac ype o rao ecnoogy antry to point out the important factor for that specifictechnology. (Try to memorize all the steps listed abovesicne I will talk about the steps for each of the followingsections).
What kind of tools we need for troubleshoot ?
i) LAN Cable type (Sometimes you have to use 'direct cable'and sometimes you have to use 'cross over' cable).ii) Category of LAN cable. (Is it Cat 5 cable or Cat 6 cable ?)iii) Ethernet Port Capability (Is it only for 10/100 M, orGigabit ethernet ?)iv) Firewall setting on your PC (I will go back to this later ina separate section).iv) YOUR SKILLs to use and analyze the logging toolv) YOUR PATIENCE to step through the log for each andevery transmission and receptionSince the throughput process get involved in the fullprotocol stack and one/two PCs, and in addition IP tools,you would need to have tools to monitor each and everysteps along the end-to-end data path. The logging toolshould be able to show not only scheduling and event log,but also all the payload (contents of the data). Withoutthese tools, you would end up saying "I have tested thisdevice with many different test equipment and didn't seeany problem before. This is the only equipment that I seethis problem.. so the problem is on the equipment side." or"I have tested many different UE with this equipment, but Ididn't see this kind of problem before. So this is UE sideproblem". Both may be right or wrong at the same time.Our job as an engineer is to find the root cause of theproblem and fix it, not blaming the other party. (But to behonest, I have to admit I often blame the other partywithout even realizing it. Is this a kind of bad nature of engineers ? or my personal problem ?)Let's try to have proper tools and skills to fight against theproblem, not fight against your counter part engineers. Myrecommendation about the tool is as follows :i) Ethernet, IP logging tool (e.g, Wireshark)ii) UE side logging tooliii) Network side logging tool

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->