Security Level:

PS Faults Analysis and

Troubleshooting

www.huawei.com

Author/ Email: Author's name/Author's email

Version: V1.0(20YYMMDD)
HUAWEI TECHNOLOGIES CO., LTD.
 Contents
 GSM PS Service
 UMTS PS Service
 LTE PS Service

Page2

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 2

 Contents
1 PS Data Transmission Evaluate Method
 PS Data Transmission Counter Evaluate Method
 PS Data Transmission DT Evaluate Method
 Ping Delay Evaluate Method
2 PS Data Transmission Issue Sort and Clarification

3 PS Data Transmission Issue Influence Factor

4 PS Data Transmission Issue Solution Scheme

5 Implementation Results and Template

6 PS Data Transmission Tool Intro

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Page 3 3
 PS Data Transmission Counter Evaluate Method
LLC Weighted Throughput (Cross-range Indicator Comparison)
Manufac Evaluate Network
Indicator Indicator Signification Element Remark
turer Items
Numerator: Each time the service transmission is
[Throughput of Uplink/Downlink (E) GPRS complete TBF of users, the transmission rate of
Users LLC PDU]/[Total Bytes of LLC PDUs is calculated. The transmission rate is
Uplink/Downlink (E) GPRS Users LLC PDUs equal to the number of transmitted bytes divided
*8/1024]; or by the transmission duration. This transmission
Cell [Throughput of Uplink/Downlink (E) GPRS rate multiplied by the number of transmitted bytes
HW BSC
Throughput Background/Interactive Service LLC]/{[Total yields the throughput of transmitted LLC PDUs. In
Bytes of Uplink/Downlink (E) GPRS the end, the throughput is accumulated to the
Background/Interactive Service LLC PDUs counter.
Sent]*8/1024} Denominator: This measurement provides the total
Units: kbps number of bytes at the LLC layer of users in a
granularity period.

Ericsson: Time period in

extended uplink TBF mode or
Numerator: Average Throughput of Delayed release in downlink TBF
(Dl/Ulbg (e) gthr+Dl/Ulthp1 (e)
Uplink/Downlink (E) GPRS not include; FAKE PDU not
gthr+Dl/Ulthp2 (e) gthr+Dl/Ulthp3 (e) gthr) /
Background/Interactive Service LLC Layer*Flow include; Small packet not
Cell (Dl/Ulbg (e) gdata+Dl/Ulthp1 (e)
Ericsson of Uplink/Downlink (E) GPRS BSC include. Only include dispatched
Throughput gdata+Dl/Ulthp2 (e) gdata+Dl/Ulthp3 (e)
Background/Interactive Service LLC Layer. high priority PFC; DTM,
gdata)
Denominator: Total flow of Uplink/Downlink (E) attempted transfers not include.
Units: kbps
GPRS Background/Interactive Service LLC Layer GMM/SM signal not include;
Ericsson formula is in the
ascendant.

WTHLLC|= transfers rate in this time * (transfers

length in this time/total transfers length), which Siemens material do not explain
transfers rate in this time=transfers length in this whether include time period in
Cell WTHLLC_1~20
Siemens time/LIFETIME, LIFETIME begin at the first BSC extended uplink TBF mode or
Throughput Units: KBytes/s
RLC/MAC block send, end at downlink Delayed release in downlink TBF
RLC/MAC block send successfully, viz. received or not, but conclude not include.
PKT DL ACK or timeslot re-assignment.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Page 4 4
 PS Data Transmission DT Evaluate Method

Network
Sort Evaluate Items Evaluate Software Priority
Element

MS High
Application Layer TEMS; CDS; Probe; Dingli
EGPRS (GPRS)
Throughput ATU
MS High

TEMS; CDS; Probe; Dingli

MS Medium
ATU
EGPRS (GPRS) LLC Throughput
PS SigTool BSC Medium

TEMS; CDS; Probe MS Medium

EGPRS (GPRS) RLC Throughput
PS SigTool BSC Medium

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 5

Page 5
 PS Data Transmission Ping Delay Evaluate Method

Definition: Ping Delay KPI is the KPI from begin to end, which means the time delay from
sending ping request with test equipment to receiving ping reply with test server.
Key information confirm: Ping delay issue need to confirm 3 important information firstly:
Ping packet size
Normally, ping delay increase along with ping packet size.
Server position (destination address)
Server position have important affect to ping Delay, normally, ping delay in intranet is
quite less than which of internet. The server position in internet have quite different in
different position (inside country or outside country).
Whether exist background data transmission
If ping in upload or download, ping delay will be much longer than ping without upload or
download.
Evaluate Method:
DT/CQT: If evaluation is in moving state, all cells related to test need to be analyzed.
Statistics mean value/distribution: if statistics distribution, analysis focuses on delay
abnormal point.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 6

Page 6
 Contents

1 PS Data Transmission Evaluate Method

2 PS Data Transmission Issue Sort and Clarification

3 PS Data Transmission Issue Influence Factor

4 PS Data Transmission Issue Solution Scheme

5 Implementation Results and Template

6 PS Data Transmission Tool Intro

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 7

Page 7
 PS Data Transmission Issue Sort and Clarification
Sort Sort Issue
Recognition Method Check Mode
Level1 Level2 Source
Swap network
Counter throughput According to BSC counter, contrast and Throughput indicator
Contract
Throughput indicator cannot analyze indicator at the same time period decrease than original
assess
Issue reach the before and after swapping. network after swapping.
standard

Swap/ Swap, competition etc.

DT demonstrate/ According to MS side trace tool (Probe, scenario, comparing
KPI reach
Throughput characteristic TEMS, CDS, ATU etc.) analysis single user application layer download
the standard
Issue function/check/c application layer average throughput throughput as ftp with CQT
ompetition or DT.

According to BSC counter, contrast and

Stock network KPI indicator is stabilization
analysis network action (upgrade, reform,
throughput in stock network, throughput
Complaint Complaint characteristic function etc.) indicator at the
indicator indicator or reception
same time for one week, or reception
become worse become worse.
become worse.

Ping delay test cannot reach

KPI reach According to windows ping command count the standard
Ping Delay Ping delay
the standard ping Delay or worse than other
manufacturer

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 8

Page 8
 Contents

1 PS Data Transmission Evaluate Method

2 PS Data Transmission Issue Sort and Clarification

3 PS Data Transmission Issue Influence Factor

 PS Data Transmission Counter Issue Influence Factor
 PS Data Transmission DT Issue Influence Factor
 PS Data Transmission Complaint Issue Influence Factor
 PS Data Transmission Ping Delay Issue Influence Factor
4 PS Data Transmission Issue Solution Scheme

5 Implementation Results and Template

6 PS Data Transmission Tool Intro

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Page 9 9
 PS Data Transmission Counter Issue Influence Factor
Counter Throughput Issue Influence Factor (Sort 1)
Abnormal
KPI Mapping Abnormal alarm Parameter Version Check
operation
KPI Mapping: For swap or indicator competition scenario, checking the different between HW and other manufacturer in KPI
definition formula, then mapping the formula.
Abnormal operation: Operation in BSC (operation log record), like PDCH Channel Priority Type, transfers network or core
network reform action will affect PS data transmission.
Abnormal alarm: Common as E1/T1 frame out-of-sync alarm will affect throughput, in stipulate action will check it.
Parameter: Common algorithm parameter or channel parameter affect PS data transmission, see PS data transmission
parameter checklist.
Version check: Commonly algorithm implement or compatibility issue, software bug which release as early warning or
version release notes.

Counter Throughput Issue Influence Factor (Sort 2)

Resource Traffic
Overlay
PDCH Transfers Multiplex Preemptions Single Timeslot Throughput Model

Resource: PDCH resource, transfers resource and quality, channel multiplex rate, channel preemptions etc. will affect PS
throughput.
Overlay: Show Um quality, as BEP distribution.
Traffic Model: Resource is limit, traffic change lead to user resource change, then affect PS throughput.

Sort 1 factor according to Forward Check, Sort 2 factor according to Backward Check

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 10

Page 10
 PS Data Transmission DT Issue Influence Factor
DT Throughput Issue Influence Factor (Sort1)
Notebook
Abnormal Abnormal Terminal Server performance CN+ Test
Parameter Version Check performance and
operation alarm performance and windows setting Route mode
windows setting
Abnormal operation: Operation in BSC (operation log record), like PDCH Channel Priority Type, transfers network
or core network reform action will affect PS data transmission.
Abnormal alarm: Commonly as Gb link break, Cell out of service etc. alarm will affect throughput, according to
alarm log check it.
Parameter: Common algorithm parameter or channel parameter affect PS data transmission, see PS data
transmission parameter checklist.
Version check: Commonly algorithm implement or compatibility issue, software bug which release as early warning
or version release notes.
Notebook/Server performance and windows setting: Bad performance or incorrect window size setting will affect
TCP layer data process and Ack feedback duly.
CN+ Route: Packet loss due to core network factors, delay too long, overload etc. will affect PS throughput.
Test mode:Test mode as single thread or multi-thread will affect PS throughput, so as DT test vehicle velocity.
DT Throughput Issue Influence Factor (Sort2)
Resource
Overlay Traffic Model
PDCH channel number Abis Gb Boardload Coding Scheme

Resource: PDCH channel number, Abis, Gb transfers resource, coding scheme will affect PS throughput.
Overlay: Show Um quality, as CQI distribution.
Traffic Model: Resource is limit, traffic change lead to user resource change, then affect PS throughput.

Sort 1 factor according to Forward Check, Sort 2 factor according to Backward Check

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 11

Page 11
 PS Data Transmission Complaint Issue Influence Factor
Complaint issue includes single user complaint and area complaint. For the former,
single user information (Single user Signal etc.) in DT issue is needed to analyze. For the
latter, follow counter throughput issue, counter analysis firstly. If counter analysis cannot
solve, then DT test and enter DT throughput analysis flow.
The content of forward check is the same as counter throughput issue and DT
throughput. Backward check includes resource, overlay, traffic model analysis. If DT is
needed, enter analysis L1, L2, L3, Application Layer analysis.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 12

Page 12
 PS Data Transmission Ping Delay Issue Influence Factor (Sort1)

Ping Delay Issue Influence Factor (Sort1)

Notebook
Abnormal Abnormal Version Server performance CN+ Test
Parameter performance and
operation alarm Check and windows setting Route mode
windows setting

Abnormal operation: Operation in BSC (operation log record), like PDCH Channel Priority Type, transfers network
or core network reform action will affect PS ping delay.
Abnormal alarm: Common alarms, such as E1/T1 frame out-of-sync alarm, will affect the ping delay, in stipulate
action will check it.
Parameter: Common algorithm parameter or channel parameter affect PS data transmission, see PS data
transmission parameter checklist.
Version check: Commonly algorithm implement or compatibility issue, software bug which release as early warning
or version release notes.
Notebook/Server performance and windows setting: Bad performance or incorrect window size setting will affect
TCP layer data process and Ack feedback duly will affect PS ping delay.
CN+ Route: Packet loss due to core network factors, delay too long, overload etc. will affect ping delay.
Test mode: Test whether include upload or download which will affect PS ping delay.
Sort 1 factor according to Forward Check, Sort 2 factor according to Backward Check

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 13

Page 13
 PS Data Transmission Ping Delay Issue Influence Factor (Sort2)
Ping Delay Issue Influence Factor (Sort2)
Resource
Traffic whole Application
Single timeslot Overlay GB Abis UM
PDCH Transfers Multiplex Preemptions Model delay Layer Data
throughput
Resource: PDCH Channel Resource, Transfers Resource and Quality, Channel Multiplex Rate, Channel Preemptions
etc. will affect ping delay.
Overlay: Show Um quality, as BEP distribution.
Traffic Model: Resource is limit, traffic change lead to user resource change, then affect PS throughput.
Whole Delay: Collect whole ping delay, isolate up part or down part of ping service (upwards or downwards BSS).
Application Layer Data: Make sure current ping service state: success or not. If success, delay too long or not. If
failed, make sure ping service exist (NO ping request and NO ping reply), or no reply ping request upwards GB.
GB: Judge GB data transfers is normal. N (U) disorder, GB packet loss, GB data cannot resolution to correct ICMP
packet, will affect successful rate of ping service.
Abis: Abis transfers quality bad, transfers resource abnormal. IP network ping delay, variation, packet loss rate is
large. RLC layer re-transmit exist in ping service. Coding scheme is too low in ping service etc.
UM: Radio environment test terminal or area is bad. TBF establishment failure or TBF drop exist in ping service.
Using RLC unacknowledged mode. Cell re-selection in ping service will affect ping service delay.

Sort 1 factor according to Forward Check, Sort 2 factor according to Backward Check

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 14

Page 14
 Contents

1 PS Data Transmission Evaluate Method

2 PS Data Transmission Issue Sort and Clarification

3 PS Data Transmission Issue Influence Factor

4 PS Data Transmission Issue Solution Scheme

 PS Issue Handle Flow
 Issue Confirmation
 Forward Check and Measure Execution
 Backward Check and Measure Execution

5 Implementation Results and Template

6 PS Data Transmission Tool Intro

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Page 1515
 PS Data Transmission Issue Handle Flow
PS data
PS data transmission issue includes 4 step, as follow table, particular flow see attachment: transmission issue Checklist part
Step Action Name Enter Condition Analysis Purpose
1) Confirm Issue Sort: Counter Throughput, DT Throughput, ping Delay Issue,
STEP 1: Issue Confirmation and sort Unconditional enter and Complaint Issue;
2) Confirm Issue scope: Whole-net issue, TOP cell issue, or single site issue;
Action 1: KPI definition Swap or competition counter KPI Check whether the KPI formula has mapped with other manufacturer, difference
and mapping unconditional enter; others skip Step. and affect in counter statistics point.
Check exist abnormal operation in BSC (operation log record), like PDCH
Action 2: Abnormal
Unconditional enter Channel Priority Type, transfers network or core network reform action will affect
STEP 2: operation check PS data transmission issue.
Forward
Check Action 3: Alarm check Unconditional enter Check whether there exists data transmission issue alarm.

Action 4: Version check Unconditional enter Check exist early warning, RN affect data transmission issue.
Action 5: Parameter
Unconditional enter Check exist abnormal configuration affect data transmission issue.
check
Action 6: Resource Check include: PDCH channel resource, transfers resource and quality, channel
Unconditional enter
analysis multiplex rate, channel preemptions etc. will affect PS throughput.

Action 7: Traffic model Analysis CS and PS traffic volume change, confirm throughput/volume change is
Unconditional enter
analysis whether relate to traffic model.
Action 8: Overlay
STEP 3: analysis Action 6 Transfers OK, then enter Analysis Um factor whether affect data transmission issue.
Backward
Check 1) DT throughput unconditional enter;
Action 9: Single user 2) Counter throughput and complaint AnalysisL1, L2, L3 and application layer, confirm PS data transmission issue
throughput trace data issue, first analysis counter data, then signal, L1, C/I change, L2 TBF establishment, radio block re-transmit, application
analysis analysis single user trace data (Signal layer delay and packet loss which affect throughput.
analysis part is optional)
Action 10: Single user Ping delay issue enter (Signal analysis Analysis whole delay, confirm GB, Abis, UM affect to ping delay, Confirm long
delay trace data analysis part is optional) delay part.

Step 4: Confirm issue solved Unconditional enter Confirm issue whether solved.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Page 1616
 Contents

1 PS Data Transmission Evaluate Method

2 PS Data Transmission Issue Sort and Clarification

3 PS Data Transmission Issue Influence Factor

4 PS Data Transmission Issue Solution Scheme

 PS Issue Handle Flow
 Issue Confirmation
 Forward Check and Measure Execution
 Backward Check and Measure Execution

5 Implementation Results and Template

6 PS Data Transmission Tool Intro

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Page 1717
 Counter Throughput Issue Confirmation

Counter Data Input OMStar Output Follow-up

(Recom solution
Whole-Net Issue enter
1. Counter
BSC Indicator: Counter Issue Forward
1) LLC PDU Bytes mendati Stat. Table;
Check and every
2. Confirm
L9407+L9408+L9429+L9430 or on) Whole-Net
Backward Check;
L9421;
L9410+L9411+L9431+L9432 or or FMA Issue or TOP Top Cell Issue enter
Cell Issue; Counter Issue Forward
L9423;
L9511+L9512+L9533+L9534 or Check (Alarm, Cell
L9525; Parameter, Site
L9514+L9515+L9535+L9536 or configuration) and part
L9527; Backward Check
2) LLC Layer Throughput (Resource, Overlay etc.);
L9413+L9414+L9433+L9434 or
L9422;
L9415+L9416+L9435+L9436 or
L9424;
L9517+L9518+L9537+L9538 or
L9526;
L9519+L9520+L9539+L9540 or
L9528

Analysis Rules: if remove 20% Top

Cell, throughput indicator did not
reach target value, consider as
"Whole-Net Issue", else is TOP Cell
Issue.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 18

Page 18
 Contents

1 PS Data Transmission Evaluate Method

2 PS Data Transmission Issue Sort and Clarification

3 PS Data Transmission Issue Influence Factor

4 PS Data Transmission Issue Solution Scheme

 PS Issue Handle Flow
 Issue Confirmation
 Forward Check and Measure Execution
 Backward Check and Measure Execution

5 Implementation Results and Template

6 PS Data Transmission Tool Intro

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Page 1919
 Forward Check (Action 1: KPI Definition and
Mapping)
Input Output Follow-up
KPI solution
Mappin 1. KPI Mapping 1. Formula
KPI Definition; g Tool+ Result; Mapping or
Counter Name 2. Counter Stat. not;
Manual point difference. 2. Difference
check explained or
not.

Case 1: E country throughput does not reach the standard.

E country certain project swap Ericsson, after optimize, PS Throughput still cannot reach
the standard, about 2-3K lower. Analysis conclusion is statistics difference between two
manufacturer. Ericsson KPI is in advantage. Clarify KPI statistics.
Clarify report:
LLC Weighted
Throughput Difference Clarif

If project is swap, original network formula and mapping formula need to be provided; in some
condition, original network counter handbook is needed too.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 20
Page 20
 Forward Check (Action 2: Abnormal operation; Action 3: Alarm; Action 4: Version)
Input Output Follow-up
OMStar+ solution
1. Parameter
return (Abnormal
1. BSC MML Configuration and Manual 1. Check
operation);
license; Result
2. M2000 output Alarm Log;
check 2. Alarm resume;
3. Early warning
3. M2000 output Operation Log elusion perform

Case 2: M Project Throughput Low Issue

M project certain BSC throughput is low, check operation log, it's found open SGSNPOOL
function operation when indicator waved. At the same time, other normal BSC did not
operate. Then, check more configuration, open SGSNPOOL but did not configure NRI,
uplink data may sent to wrong SGSN node. It cause whole throughput decreased.

Abnormal operation, Alarm, Version need to be checked manually.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 21

Page 21
 Forward Check (Action 5: Parameter Check)
Input Output Follow-up
PFMSTU solution
1. Abnormal
1. Parameter
BSC MML Configuration and DIO+ parameter list;
return;
2. Abnormal
LICENSE; Tool integrated Manual License list;
2. License
check parameter item and rules modification.
check
PS data
transmission parameter check

Case 3 (<Allocate One PDCH for Signaling Data> Parameter Configuration): A project
swap Ericsson, LLC layer weighted throughput cannot reach the standard, executed
parameter check, then found parameter: Allocate One PDCH for Signaling Data
/ALLOCSINGLEPDCHFORSIGNALLING is open, cause whole throughput is affected.
Close the parameter and throughput was improved.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 22

Page 22
 Contents

1 PS Data Transmission Evaluate Method

2 PS Data Transmission Issue Sort and Clarification
3 PS Data Transmission Issue Influence Factor

4 PS Data Transmission Issue Solution Scheme

 PS Issue Handle Flow
 Issue Confirmation
 Forward Check and Measure Execution
 Backward Check and Measure Execution
 Counter Throughput Issue analysis and measure execution
 DT Throughput Issue analysis and measure execution
 Complaint Issue analysis and measure execution
 Ping Delay Issue analysis and measure execution

5 Implementation Results and Template

6 PS Data Transmission Tool Intro

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Page 2323
 Counter Throughput Backward Analysis (Action 6: Resource analysis)

Input Output Follow-up

solution
1. Radio Resource
OMSTAR expand capacity;
Network
BSC original Counter; (Recomme Analysis Report
2. Transfers
BSC Configuration; Resource expand
BSC license; ndation) capacity;
or FMA 3. Board Resource
expand capacity;
Analysis Rules: OMSTAR 4. Parameter
integrated Check Rules; modified.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Page 2424
 Case 4: G project PS Throughput lower than other manufacturer (Lack of resource)

[Issue description] G project HW area LLC layer throughput lower than area in other manufacturer, need optimized.
[Issue analysis]
STEP 1: Issue Confirmation and sort
Confirm Whole-net issue, decreased about 20K than other manufacturer.
STEP 2: Forward Check

Stipulated Action Check Result Performed Action

Action 1: KPI definition and mapping OK NONE
Action 2: Abnormal operation check OK NONE
Action 3: Alarm check OK NONE
Action 4: Version check OK NONE
Action 5: Parameter check OK NONE
STEP 3: Backward Check

Stipulated Action Check Result Performed Action

Based on ABIS transfers resource check, Follow tool output result to
Action 6: Resource analysis
most of sites are lack of idle timeslots. add idle timeslots.
Action 7: Traffic model analysis OK NONE
Action 8: Overlay analysis OK NONE
Action 6: Resource analysis: Check high coding scheme rate is only about 45%, check ABIS transfers resource:
ABIS timeslot apply successful rate is only about 12%. There are many timeslot application failure and main reason
is Unsuccessful Application Attempts of Abis Timeslot Because of no Idle Timeslot. Most of sites configuration did
not provide enough idle timeslots. It's suggested to follow the maximum TSCOUNT configuration.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 25

Page 25
 Counter Throughput Backward Analysis (Action 7: Traffic Model Analysis)

Input OMSTAR Output Follow-up

(Recomm solution
1. Expand capacity or
BSC original Counter; endation) Comparison
not;
2. Parameter optimize
BSC Configuration; or FMA of traffic
or not; limit PDCH
volume trend
num. or half-rate rate.
Analysis Rules: Consider CS and Low throughput
PS traffic volume simultaneity, area traffic
whether exist increase; Combine
volume
with PDCH channel resource
check comparison

OMSTAR Traffic Volume and PDCH Channel

Resource Check Result:

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 26

Page 26
 Case 5: A project LLC Layer user throughput decreased after upgraded (Traffic increase)
[Issue description] A project LLC Layer user throughput decreased about 5k after upgraded.
[Issue analysis]
STEP 1: Issue Confirmation and sort
Confirm BSC whole area issues, Issue time point is not relate to BSC upgraded time point. Part of cells
average throughput decreased trend obviously.
STEP 2: Forward Check
Stipulated Action Check Result Performed Action
Action 1: KPI definition and mapping OK NONE
Action 2: Abnormal operation check OK NONE
Action 3: Alarm check OK NONE
Action 4: Version check OK NONE
Action 5: Parameter check OK NONE

STEP 3: Backward Check

Stipulated Action Check Result Performed Action
PDCH occupancy increased after upgraded. PDCH
Action 6: Resource analysis Application failures For CELL PDCH Ratio Thresh Traffic Model analysis
increased too.
Service channel are not
Action 7: Traffic model analysis Part of cell PS traffic increased obviously occupied totally. Increase
PDCH ratio threshshold.
Action 8: Overlay analysis OK NONE

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 27

Page 27
 Case 5: A project LLC Layer user throughput decreased after upgraded (extended)

Action 7: Traffic Model analysis

Part cell PS traffic

volume increased
obviously.

PDCH dynamic
transform failure,
most of it are
because of PDCH
ratio thresh, and
reclaimed busy
dynamic PDCHs
are less, show no
CS preemptions.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 28

Page 28
 Counter Throughput Backward Analysis (Action 8: Overlay analysis)

Input Output Follow-up

solution
OMSTAR
BSC MML Configuration
BSC counter (Recomm Comparison If some Indicator
of Um is abnormal, need
endation) Indicator Um optimize,
Analysis Rules: or FMA when swap include overlay,
Count RX Level and Quality interference etc.
Distribution, Trx Balance,
Interference Band, BEP
Distribution, TA Distribution when
swap.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 29

Page 29
 Contents

1 PS Data Transmission Evaluate Method

2 PS Data Transmission Issue Sort and Clarification
3 PS Data Transmission Issue Influence Factor

4 PS Data Transmission Issue Solution Scheme

 PS Issue Handle Flow
 Issue Confirmation
 Forward Check and Measure Execution
 Backward Check and Measure Execution
 Counter Throughput Issue analysis and measure execution
 DT Throughput Issue analysis and measure execution
 Complaint Issue analysis and measure execution
 Ping Delay Issue analysis and measure execution

5 Implementation Results and Template

6 PS Data Transmission Tool Intro

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Page 3030
 DT Throughput Issue Confirmation

Input Output Follow-up

1) Sites/Cells scope of solution
DT throughput/;
2) DT throughput test
LOG mode: DT or CQT, FTP
MS trace or Enter
throughput figure Analysis or HTTP etc.;
3) Issue phenomenon Forward
Tool confirm: test to reach Analysis
the standard or locate
Analysis Rules: follow DT rules
single point test.
(DT rules is customer designated or
third party designated normally)
feedback.

Case: M project swap 160 2G sites, before swap, DT throughput is 100kbit/s, after swap, at
the same area, DT throughput is about 80kbit/s, DT mode is FTP download. Particularly see
Case 11.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 31

Page 31
 DT Throughput Backward Analysis (Action 9: L3 Analysis)

Input Output Follow-up

1) MS confirm solution
BSC mode check
result
Gb Downlink PDU Signal Analysis Manual 2) MS open 1) change
1) MS Confirm Mode Check: a-bit accounts acknowledge
2) open accounts throughput check: check throughput
mode terminal
peak-bit-rate check result
2) HLR re-set
3) MS multi-slot capability: egprs- 3) MS multi-slot
capability check open accounts
multi-slot-class
throughput
Analysis Rules: 3) Change
1) Observe signal field a-bit; high multi-slot
Observe MS acknowledge mode; capability
2) In signal field peak bit rate, observe terminal.
open accounts throughput. If lower
than service open accounts throughput, 1) Terminal confirm mode;
is abnormal;
3) If multi-slot capability is lower than 2) Terminal open accounts
10, MS downlink maximum occupancy
PDCH number.
throughput;
3) Terminal multi-slot
capability

Note: DT throughput action 1~8 are almost the same as counter throughput (Forward Check add
server, notebook, test mode check to PS parameter checklist), differences are analysis sites or cell
distinguish.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 32
Page 32
 DT Throughput Backward Analysis (Action 9: L1 analysis)

Input LOG Output Follow-up

analysis
1) CI check result
solution
1) according to DT
BSC Tool + 2) BEP check software to find
better and more
PS result
3) Radio resource steady CQI test
Test Terminal Signal Trace SigTool (channel position;
log occupancy, high
2) a change CQI
coding scheme
usage, channel more steady
Analysis Rules:
multiplex). access position;
1) Observe MS report CI<25
rx-level, overlay b change same
(peak value test is maximum check result
value), and fluctuate type terminal or
frequently; other type terminal
2) mean bep less than 25 is to test;
abnormal; 3) a set as baseline
3) Test terminal occupancy b update License,
Um resource less than50%; resource expand
4) High coding scheme rate capacity;
less than 70%; 4) a close flow
5) PDCH Channel occupancy control;
number is less than 4;
b multi-thread test;

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 33

Page 33
 DT Throughput Backward Analysis (Action 9: L2 analysis)
Input Output Follow-up
solution
1) According to TBF
PS Sig 1) TBF establishment fail
establishment reason: expand capacity
BSC Tool fail reason transfers resource or
2) TBF drop optimize transfers
reason check quality
BSC side single user signal trace 3) RLC re- 2) Optimize Um
transmit check transfers or using
parameter optimize to
Analysis Rules: reduce TBF drop delay
1) If TBF establishment failure number 3) Optimize Um
is 0, enter next step check; transfers or using
2) If Um downlink ack message parameter optimize to
include lots of NACK message, it may reduce re-transmit.
cause LLC PDU cannot sent in time,
and cause application layer data make
up packet hard;
3) If TBF drop always happened, it
may cause data transfers difficult. It's
abnormal situation, need more analysis.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 34

Page 34
 DT Throughput Backward Analysis (Action 9: Application Layer
Analysis)

Input PS Signal Output Follow-

analysis up
BSC 1) Gb exist N (U)
Tool disorder or not solution
1) check BSC
inside and data
2) BSC upwards transmit
Use signal analysis Tool to open single
user signal trace, click right-button and
IP packet loss, between BSC
disorder check and SGSN.
choose TMF to CAP, and get pcap message result 2) assort with
files. Lead to IP message analysis Tool 3) Server and
or wireshark tool. analysis notebook
other net
element
Analysis Rules: Tool+ performance
check result
upwards BSC
3) modify
1) Observe Gb signal N (U) whether
continuously. If N (u) is not
Wireshark window size of
server and
continuous, need Gb wireshark to notebook;
observe BSC Issue or other network change better
element upward BSC Issue; performance
2) If N (U) continuous, and only TCP server or
layer packet loss, it shows other notebook;
network element upward BSC Issue;

Case 6: G project open website hard Issue (next page)

G project open website hard, check TCP layer exist TCP PDU packet loss, initially, estimate that other network
element upward BSC. Then confirmed is WAP gateway move user load operation cause TCP layer data transfers
abnormal. Particular analysis see next page.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 35

Page 35
 Case 6: G project open website hard Issue (Backward Factor)

[Issue description] G project open website hard Issue.

[Issue analysis]
STEP 1: Issue Confirmation and sort
Confirmed other user open website hard too, after DT test terminal throughput low and data flow bread
are serious.
STEP 2: Forward Check
Stipulated Action Check Result Performed Action
Action 1: KPI definition and mapping NONE NONE
Action 2: Abnormal operation check OK NONE
Action 3: Alarm check OK NONE
Action 4: Version check OK NONE
Notebook window is set to Change the window size to
Action 5: Parameter check
64K. 256K.
STEP 3: Backward Check and measure execution
Stipulated Action Check Result Performed Action
Action 9: L3 analysis N (U) is continuous, OK NONE
CI check result. BEP check result. radio resource. access
Action 9: L1 analysis NONE
RX-level and overlay check result, OK
Action 9: L2 analysis RLC/MAC data transfers is normal, OK NONE

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Page 3636
 Case 6: G project open website hard Issue (Backward Factor)

L1 analysis Result

L2 analysis Result

From L1, L2 analysis: Uplink/Downlink TBF establishment is normal release, Um resource

transfers is normal, LLC layer N (U) is continuous.
need enter Application layer to more analysis.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Page 3737
 Case 6: G project open website hard Issue (Backward Factor)

Action 9: Application Layer analysis

1) Check Gb Signal N (U) is continuous, which proved data transfers was normal between BSC and SGSN, issue may
occur in other network element upward BSC.
2) Using wireshark check Gb transform to TCP layer data transfers packet, it was found TCP layer packet loss
seriously when open website.
3) Need other network element upward BSC to check data transfers issue.

TCP layer data exist disorder, but Gb data N (U) is continuous, which proved disorder exist in other
network element upward BSC
For this issue, the main reason is other network element upward BSC issue. Forward analysis cannot find issue
real reason, but according to backward analysis located other network element upward BSC issue fast. This
Issue Need other network element upward BSC to check data transfers issue.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Page 3838
 Contents

1 PS Data Transmission Evaluate Method

2 PS Data Transmission Issue Sort and Clarification
3 PS Data Transmission Issue Influence Factor

4 PS Data Transmission Issue Solution Scheme

 PS Issue Handle Flow
 Issue Confirmation
 Forward Check and Measure Execution
 Backward Check and Measure Execution
 Counter Throughput Issue analysis and measure execution
 DT Throughput Issue analysis and measure execution
 Complaint Issue analysis and measure execution
 Ping Delay Issue analysis and measure execution

5 Implementation Results and Template

6 PS Data Transmission Tool Intro

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Page 3939
 Complaint Issue analysis and measure execution
Complaint issue includes single user complaint and area complaint. For the former,
single user information (Single user Signal etc.) in DT issue is needed to analyze. For the
latter, follow counter throughput issue, counter analysis firstly. If counter analysis cannot
solve, then DT test and enter DT throughput analysis flow.
The content of forward check is the same as counter throughput issue and DT
throughput. Backward check includes resource, overlay, traffic model analysis. If DT is
needed, enter analysis L1, L2, L3, Application Layer analysis.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 40

Page 40
 Contents

1 PS Data Transmission Evaluate Method

2 PS Data Transmission Issue Sort and Clarification
3 PS Data Transmission Issue Influence Factor

4 PS Data Transmission Issue Solution Scheme

 PS Issue Handle Flow
 Issue Confirmation
 Forward Check and Measure Execution
 Backward Check and Measure Execution
 Counter Throughput Issue analysis and measure execution
 DT Throughput Issue analysis and measure execution
 Complaint Issue analysis and measure execution
 Ping Delay Issue analysis and measure execution

5 Implementation Results and Template

6 PS Data Transmission Tool Intro

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Page 4141
 Ping Delay Issue Confirmation

Input Output Follow-up

solution
1) Ping packet size Enter
MS Trace or Ping Test Log
Result and server address; forward
Analysis 2) Device in ping analysis
Tool service (include process
Analysis Rules: follow DT rules
transfers device).
(DT rules is customer designated or
third party designated normally)
feedback

Case: See Case 7

Note: Ping Delay Issue action 1~8 are almost the same as counter throughput (Forward Check add
server, notebook, test mode check to PS parameter checklist), differences are analysis sites or cell
distinguish.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 42

Page 42
 Ping Delay Problem Backward Analysis
1. Overall delay analysis: Check whether the
problem occurs before or after the Gb interface.
PING REPLY
n PING REQUEST
2. Application layer
Application data analysis: Check
whether pinging succeeds.
IP/X.25 Relay

SNDCP SNDCP

LLC LLC
Relay
RLC RLC BSSGP BSSGP

MAC MAC NS NS

GSM PF GSMPF L1 L1

MS BSS SGSN

Um Abis
4. Abis interface analysis: Check
Gb
3. Gb interface analysis:
5. Um interface analysis: C/I value, whether there is delay, jitter, packet Check whether there is loss
BEP, level quality, TBF loss, retransmission at the RLC and sequence error of
establishment failure, and call drop layer, and low High Coding packets.
Scheme Rate.

Note: Overall delay analysis is mandatory. Analysis on other dimensions can be

performed based on the site conditions.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 43

43
 Ping Delay Problem Backward Analysis
(Action 10: Overall Delay Analysis)
Follow-up
Input PS signaling Output solution
analysis 1. Identified If problems, such
tools: problems, such as the loss and
as the loss and sequence error of
PS single subscriber
TranExpert sequence error packet before
signaling, TEMS log, and .cap +log of packet before BSS are found,
file analysis tool BSS. locate the NE
2. Summary of problem before
overall ping BSS and provide
Use Signaling Analysis Tool delay. a solution.
to open PS single subscriber
traced signaling. Right-click
tmf to Pcap to obtain .cap
files in the same directory.

Analysis rules:
1. Check whether there
are problems, such as the
loss and sequence error of
packet before the packet
capture point.
2. Use the TEMS Log tool
to summarize the overall
delay in pinging tests.

Overroll Ping
Delay Data

Note: Actions 1-8 for troubleshooting ping delay problems are similar to those for troubleshooting the throughput-
related counter problems, except that the sites and cells to be analyzed are different. New items in the forward
analysis are server, laptop, and test method, which are all included in the PS Parameter Checklist.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 44

44
 Ping Delay Problem Backward Analysis
(Action 10: Application Layer Data Analysis)
Follow-up solution
Input Output
If ping request is
Check results:
not responded
1. If the ping
.cap files Wireshark+ service fails,
over and before
IP packet identify failure the Gb interface,
analysis scenarios. locate the
Analysis rules: 2. If the ping transmission
tool
1. Check whether the ping service service succeeds, problem of Gb
fails. If yes, check whether the failure
is caused by the following reasons: a.
identify the Gb interface and
The ping service is not available (no interface delay. provide a solution.
ping request or response). b. Ping
request is not responded over and
before the Gb interface.
2. If the ping service succeeds, check
whether the Gb interface delay is
excessive.

Case 7: The ping delay fails to meet the specified limit because the server in office S fails to respond to the
ping request.
Problem description: According to the ping delay test result, the success rate is only about 80%, which is
below the acceptance standard.
Root cause: The server fails to respond to the ping request, causing failed ping test.
Follow-up solution: Locate the transmission problem at the core network side.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 45

Page 45
 Ping Delay Problem Backward Analysis
(Action 10: Gb Interface Analysis)

Output Follow-up solution

Check results:
Original traffic
statistics/PS single
Input 1. N (u) errors occur in the
1. For N (u) errors,
locate the Gb
subscriber signaling downlink LLC PDU data interface
FMA or over the Gb interface. transmission
Analysis rules: PS 2. N (u) is not consecutive,
which is caused by packet
problem and provide
1. Check whether N (u) errors occur in the a solution.
downlink LLC PDU data over the Gb signaling loss or failure of data 2. If Gb interface
interface during the ping service. analysis over the Gb transmission
2. Check whether N (u) is not consecutive analysis interface. resources are not
during the ping service. If yes, check 3. Results after the check
whether it is caused by packet loss or tool of Gb interface
sufficient, expand
the capacity and
failure of data analysis over the Gb transmission resources.
interface. provide a solution.
3. If packet loss over the Gb interface is
found, check whether the Gb interface is
overloaded.

Case 8: The ping delay fails to meet the specified limit because N (u) errors occur in the downlink LLC
PDU data over the Gb interface in office M.
Problem description: According to the ping delay test result, the success rate is below the acceptance
standard (85%).
Root cause: Signaling analysis results show that a large number of N (u) errors occur over the Gb
interface, causing failure of assembling ICMP packets in the upper system and low success rate of ping
service.
Follow-up solution: Rearrange the sequence of downlink LLC PDU data to resolve the problem.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 46
Page 46
 Ping Delay Problem Backward Analysis
(Action 10: Abis Interface Analysis)

Input Output
1. Results of analysis
Follow-up
of Abis interface solution
transmission quality
Original traffic statistics, PS single FMA or and resources For more
subscriber signaling, and TEMS log. PS 2. Results of analysis details, see the
signaling of the delay, jitter, sections about
packet loss rate in the analysis of
analysis the Abis over IP
throughput
Analysis rules: tool or log networking mode.
1. Check whether the Abis interface 3. Transmission data statistics.
analysis
transmission quality is good and at RLC layer
whether transmission resources are tool 4. Coding scheme
sufficient. rate of ping service
2. Check whether the delay, jitter,
packet loss rate are normal in the Abis
over IP networking mode.
3. Check whether there is data
transmission at RLC layer during
pinging.
4. Check whether the coding scheme
rate is excessively low during pinging.

Cases to be collected

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 47

Page 47
 Ping Delay Problem Backward Analysis
(Action 10: Um Interface Analysis)
Follow-up
Input Output solution
PS 1. Check results 1. If the Um interface quality
of Um interface is poor, optimize the Um
PS single subscriber signaling signaling quality interface or change the test
and TEMS log analysis 2. Check results area. Then provide a solution.
of TBF access 2. If TBF establishment failure
Analysis rules:
1. Check the Um interface quality in the
tool or and and TBF drop occur, perform
sustainability the ping test again. Then
area where the terminal is located, log 3. RLC layer provide a solution.
including the C/I, BEP, and Rx level, and
check whether the Um interface needs to analysis operation mode 3. If the RLC layer operates in
4. Terminal the unacknowledged mode,
be optimized. tool residence in the change the mode. Then
2. Check whether TBF establishment service cell provide a solution.
failure and TBF drop occur during 4. If cell reselection occurs,
pinging. perform the ping test again to
3. Check whether the RLC layer operates prevent this problem. Then
in the unacknowledged mode during provide a solution.
pinging.
4. Check whether cell reselection occurs
during pinging.

Case 9: The ping delay fails to meet the specified limit because the RLC operates in the unacknowledged mode in office Y.
Problem description: According to the ping delay test result, the success rate is below the acceptance standard (80%).
Root cause: The SIM card for test is registered to be the unacknowledged RLC mode and lost packets cannot be
retransmitted over the Um interface. Therefore, there is difficulty in successfully pinging and assembling packets at the LLC
layer, causing failure of ping service.
Follow-up solution: modify the SIM card registration information to resolve this problem.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 48

Page 48
 Contents

1 PS Data Transmission Evaluate Method

2 PS Data Transmission Issue Sort and Clarification

3 PS Data Transmission Issue Influence Factor

4 PS Data Transmission Issue Solution Scheme

5 Implementation Results and Template

6 PS Data Transmission Tool Intro

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Page 4949
 Implementation Results and Template
1. Provide the analysis report after analysis according to specified actions. For the
report template, see the Project XX PS Data Transmission Problem Analysis
Report Template, as attached below.

Analysis Report
on PS Data Transmission P

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 50

Page 50
 Case 10: LLC Throughput in Office M Below the Standard (1)
Problem description: After the swap of Ericsson equipment in Office M, GPRS LLC throughput is more
than 10 kbit/s below the standard.
Problem analysis
Step 1: Problem identification and classification
During the swap, two cells of one BTS are cut over, and after the swap, the downlink GPRS LLC weighted
throughput of both cells significantly deteriorates. Therefore, both the two cells need to be analyzed.
Step 2: Forward analysis
Specified Action Check Result Measure
Action 1: KPI definition and mapping OK
Action 2: Abnormal operation check OK
Action 3: Abnormal alarm check OK
Action 4: Version check OK
The following three parameters are not mapped
Action 5: Parameter check onto original settings: UPEXTTBFINACTDELAY, Modify parameters.
MaxDlEstRetryNum, and DNTBFRELDELAY.

Comparison Parameter Original Setting

analysis UPEXTTBFINACTDELAY 1000
result MaxDlEstRetryNum 0
DNTBFRELDELAY 2200

Notify the frontline personnel to map these parameters onto original settings. Increase
the value of parameters by two to three kbit/s. Then perform backward analysis.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 51
Page 51
 Case 10: LLC Throughput in Office M Below the Standard (2)

Step 3: Backward analysis and measures

The backward analysis includes the resources analysis, traffic model analysis, and coverage analysis. The following table
shows analysis results.

Specified Action Check Result Measure

The single timeslot throughput and multi-

1. Configure channels for GPRS and EGPRS separately to
timeslot occupancy rate are roughly the
reduce the GPRS multiplex rate.
Action 6: Resource analysis same as that before the swap, except
2. Increase the value of PDCH Downlink Multiplex Threshold
significant increase in the GPRS multiplex
to guarantee the access of PS services.
rate. Channel resources are not sufficient.

Action 7: Traffic model analysis No significant change

Action 8: Coverage analysis OK

Action 6: Resource analysis

The analysis by using the OMStar PS service rate tool shows that the GPRS multiplex rate is higher than the specified limit
and PDCH resources are not sufficient.

The original network is configured with the BPDCH. That is, GPRS channels are only used for GPRS services. Therefore, the
average number of simultaneous TBFs is 1. In contrast, in Huawei network, channels for GPRS and EGPRS are not
configured separately, the downlink multiplex rate is generally about 4.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 52

Page 52
 Case 10: LLC Throughput in Office M Below the Standard (3)

Action 6: Resource analysis

The analysis by using the OMStar PS service rate tool shows that the GPRS multiplex rate is
higher than the specified limit and PDCH resources are not sufficient.

The red line represents the Maximum Rate Threshold of PDCH in a Cell (60%). The PDCH
usage rate almost reaches the threshold. A large number of application failures due to the
threshold indicates that PDCH resources are not sufficient.
The sum of FR TCH Occupied Rate, HR TCH Occupied Rate, and PDCH Occupied Rate is
almost 100%, which indicates that Um interface resource is not sufficient.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 53

Page 53
 Case 10: LLC Throughput in Office M Below the Standard (4)

Step 4: Troubleshooting and confirmation

After measures are taken after backward analysis, the throughput is increased by 5-6 kbit/s,
roughly reaching the throughput before the swap.

Throughput
Action Throughput
Specified Action Before
Time After Action
Action
Action 1: KPI
definition and
mapping
Action 2: Abnormal
operation check
Action 3: Abnormal
alarm check 2011-8-26 20 kbit/s 23 kbit/s

Action 4: Version
check

Action 5: Parameter
check

Action 6: Resource
analysis

Action 7: Traffic model 2011-9-21 23 kbit/s 28 kbit/s

analysis
Action 8: Coverage
analysis

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 54

Page 54
 Case 11: FTP Download Rate in Office F Below the Standard (1)

Problem description: The FTP download rate in office F is below the standard.
Problem analysis
Step 1: Problem identification and classification
According the drive test result, the throughput in only one site is below the standard.
Step 2: Forward analysis

Specified Action Check Result Measure

Action 1: KPI definition and mapping N/A None
Action 2: Abnormal operation check OK None
Action 3: Abnormal alarm check OK None
Take preventive
Action 4: Version check N/A
measures.
Action 5: Parameter check OK None

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 55

Page 55
 Case 11: FTP Download Rate in Office F Below the Standard (2)

Step 3: Backward analysis and measures

The backward analysis includes the resource analysis, traffic model analysis, and drive test data analysis.
Specified Action Check Result Measure
Action 9: L3 analysis OK
Optimize the Um interface
Action 9: L1 analysis Poor C/I
quality.
TBF drops and significant Optimize the Um interface
Action 9: L2 analysis
retransmission of RLC/MAC data block quality.
Action 9: Application layer analysis OK

Action 9: L1 analysis

C/I statistics indicate that if the mean C/I is low, Um interface data transmission is affected. High
coding scheme rate cannot be used unless C/I is above 30 to improve the data transmission rate
during the drive test. The frontline personnel are advised to optimize the Um interface by
interference suppression and carrier adjustment.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 56

Page 56
 Case 11: FTP Download Rate in Office F Below the Standard (3)

Action 9: L2 analysis

According to the result of signaling analysis at the BSC side, TBF access is resumed after TBF drop.

RLC/MAC data blocks are frequently retransmitted over the Um interface, causing
low transmission rate and drops.
According to the result of L2 signaling analysis, Um interface transmission quality is
poor, causing significant retransmission, drops, and low transmission rate. You are
advised to identify the Um interface transmission problem.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 57
Page 57
 Contents

1 PS Data Transmission Evaluate Method

2 PS Data Transmission Issue Sort and Clarification

3 PS Data Transmission Issue Influence Factor

4 PS Data Transmission Issue Solution Scheme

5 Implementation Results and Template

6 PS Data Transmission Tool Intro

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Page 5858
 PS Data Transmission Issue analysis Tool

Issue type Tool Name Data Source

PS Rate Script. BSC Counter. BSC MML

OMSTAR PS rate Tool
Configuration
Network
Performance PFMSTUDIO BSC MML Configuration

Alarm Log. Operation Log. BSC Counter. BSC

FMA
MML Configuration
WIRESHARK TCP/IP packet trace

IP message analysis Tool TCP/IP packet trace

Single user
Data
PS Signal analysis Tool BSC Signal
Transmission
PROBE MS PROBE log
TEMS TEMS LOG

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 59

Page 59
 OMStar PS Rate Tool

STEP2: Import the BSC STEP3: Select

MML configuration file and the assessment
SBC original counter file. items, and
export the
STEP1: Select report.
the PS service
rate analysis
script.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 60

Page 60
 Parameter Check by Using PFMSTUDIO

Step 4: Click the

start icon.

Step 1: Add MML configuration

files. Step 3: Select
scenarios.

Step 2: Select corresponding

subjects.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 61

Page 61
 FMA Analysis

Step1: Establish project, input counter, Step 2: Choose configuration or performance counter,

configuration, alarm etc. Data choose needed analysis counter or KPI in right list, show
as figures.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 62

Page 62
 PS Signaling Analysis Tool (1)
This tool is designed specifically for PS signaling analysis with simple and convenient interface, as shown
below.

Step1: Select the

required signaling
with the user-defined
filtering function.

Step 2: Right-click
the selected
signaling and
choose the required
function such as
statistics, export, or
extraction function.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 63

Page 63
 PS Signaling Analysis Tool (2)
This tool has complete functions.
Take the Single User Signal Trace
file as an example, this tool can
realize the following functions:
1. Calculation of the number of
channels used
2. Calculation of the data rate of
LLC and RLC layers
3. Calculation of the rate of each
coding scheme used to transmit
RLC blocks
4. Conversion of Gb interface data
to .cap files
5. Comparison of signaling
information fields

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 64

Page 64
 cap File Analysis Tool (Wireshark)

Wireshark can analyze .cap files at any time and analyze the data transmission of LLC, BSSGP, and TCP layers.
Currently, the analysis of drive test signaling is performed by using the following method: Convert the Gb interface
signaling to .cap files by using the signaling analysis tool and view the signaling transmission by using Wireshark.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 65

Page 65
 The Main Functions of TranExpert

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 66

Page 66
 TranExpert--- Ping Analysis
Attention to typical faults of all transmission protocol, such as drop, delay, jitter, out-of-
order. Help to decide whether the drop scene up or down to the capture scene.

1 ） Ping Analyse （ 1 ） Open the file ， click QoS->ping (2) Select the 5-elements-data to be analysed.
Analyse

(4)Double click the Particular result filtered by

(3) Ping Analysis result
priority, no drop found.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 67

Page 67
 Contents
 GSM PS Service
 UMTS PS Service
 LTE PS Service

Page68

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 68

 Contents
1 Methods for Evaluating HSPA Data Transmission Problems
 Methods for Evaluating HSPA Data Transmission Problems Detected Through Traffic
Statistics
 Methods for Evaluating HSPA Data Transmission Problems Detected Through a Drive Test
 Methods for Evaluation Ping Delay Problems
2 Classification and Clarification of HSPA Data Transmission Problems

3 Factors Affecting HSPA Data Transmission

4 Solutions to HSPA Data Transmission Problems

5 Deliverable Example and Template

6 Appendix: Introduction to HSPA Data Transmission Troubleshooting Tools

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 69

Page 69
 Methods for Evaluating HSPA Data Transmission Problems Detected Through
Traffic Measurement (1)
HSDPA (Contrast KPI)
Vendor Item KPI Description NE Remarks
Numerator: total bits at the MAC-D layer This formula is used to calculate the
sum(VS.DataOutput.Mean*{measurement
correctly sent by HSDPA users over the air throughput at the MAC-D layer in
period})/sum[(VS.DataTtiRatio.Mean-
interface in a cell in a measurement period R014SPC330 and earlier versions.
Huawei Cell throughput VS.HSDPA.InactiveDataTtiRatio.Mean)*{measurem NodeB
Denominator: duration of sending data in the The throughput measured using the
ent period}];
cell by at least one HSDPA user in a formula provided by Ericsson or NSN
Unit: Kbit/s
measurement period is higher.

This formula is used to calculate the

Numerator: total bits at the MAC-HS layer
VS.CellReserve.Counter1*1000/ throughput at the MAC-HS layer in
correctly sent by HSDPA users over the air
((VS.DataTtiRatio.Mean- R014SPC330 and earlier versions.
Cell throughput interface in a cell in a measurement period NodeB
Huawei VS.HSDPA.InactiveDataTtiRatio.Mean)*{measurem The throughput measured using the
Denominator: duration of sending data in the
ent period}); formula provided by Ericsson or NSN
cell by at least one HSDPA user in a
Unit: Kbit/s is the same as that using the formula
measurement period
of Huawei

The denominator is the same as that

SUM(HS_DATA_ACK_SPI_XX) *8/ (SUM
in the formula of Huawei, but the
(HS_SCCH_PWR_DIST_CLASS_0 +
Numerator: total bits at the MAC-HS layer numerator in the formula of NSN is
HS_SCCH_PWR_DIST_CLASS_1 +
correctly sent by HSDPA users in a cell in a the data amount of the MAC-HS
HS_SCCH_PWR_DIST_CLASS_2 +
measurement period layer, which is greater. Therefore, the
NSN Cell throughput HS_SCCH_PWR_DIST_CLASS_3 + NodeB
Denominator: duration of sending data in the throughput measured using the
HS_SCCH_PWR_DIST_CLASS_4 +
cell by at least one HSDPA user in a formula of NSN is higher than that of
HS_SCCH_PWR_DIST_CLASS_5) /500)
measurement period the first formula provided by Huawei,
where XX = [0 .. 15]
and is the same as that of the
Unit: Kbit/s
second formula provided by Huawei.

The numerator in the formula of

Numerator: total bits at the MAC-HS layer
Ericsson is used to measure data
correctly sent by HSDPA users over the air
amount at the MAC-HS layer.
SUM(pmSumAckedBitsSpiXX) interface based on the SPI statistics in a cell in
Therefore, the throughput measured
/(0.002*pmNoActiveSubFrames) where XX = [0 .. a measurement period
Ericsson Cell throughput NodeB using the formula of Ericsson is
15] Denominator: duration of sending data in the
higher than that of the first formula of
Unit: Kbit/s cell by at least one HSDPA user in a
Huawei, and is the same as that of
measurement period
the second formula provided by
Huawei.
Numerator: total bits at the MAC-D layer
correctly sent by HSDPA users over the air
500*sum(VS.HsdpaMACdPDUAckBits)/sum interface statistics in a cell in a measurement
The throughput is equivalent to that
ALU Cell throughput (VS.HsdpaTTIsUsed) period NodeB
of Huawei MAC-D layer.
Unit: Kbit/s Denominator: duration of sending data in the
cell by at least one HSDPA user in a
measurement period

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 70

Page 70
 Methods for Evaluating HSPA Data Transmission Problems Detected Through
Traffic Measurement (2)
HSDPA (Contrast KPI)

Vendor Item KPI Description NE Remarks

This formula is used to calculate

the scheduled throughput at the
Numerator: total bits at the MAC-D layer correctly sent by HSDPA
VS.DataOutput.Mean*{SP}*60/ MAC-D layer in R014SPC330 and
Throughput users over the air interface in a cell in a measurement period
Huawei (VS.HSDPA.All.ScheduledNum*2) NodeB earlier versions. The data
per user Denominator: duration of scheduling in the cell by all users in a
Unit: Kbit/s measurement of the numerator is
measurement period
low.

This formula is used to calculate

the scheduled throughput at the
Numerator: total bits at the MAC-HS layer correctly sent by HSDPA
MAC-HS layer in R014SPC330
Throughput VS.CellReserve.Counter1*1000/ users over the air interface in a cell in a measurement period
Huawei NodeB and earlier versions. The
per user (VS.HSDPA.All.ScheduledNum*2) Denominator: duration of scheduling in the cell by all users in a
scheduled throughput of Huawei is
measurement period
higher than that provided by
Ericsson.

Numerator: amount of MAC-D data received by the NodeB on the Iub In the formula of NSN, the
interface, except the packets discarded due to flow control. In at least denominator is greater than that of
the following four scenarios, the NSN's throughput measured is higher Huawei, but the numerator is
sum ([RECEIVED_HS_MACD_BITS] - than that of Huawei: greater than that of Huawei's first
[DISCARDED_HS_MACD_BITS]) / sum 1. The serving cell changes across NodeBs. formula in some scenarios and
Throughput
NSN ([ALLO_DUR_HS_DSCH_FLOW_INT] + 2. The number of HARQs exceeds the maximum number of NodeB smaller than that of Huawei's
per user
[ALLO_DUR_HS_DSCH_FLOW_BGR]) / 100)) retransmission times. second formula in most cases. The
Unit: Kbit/s 3. Data is discarded if timeout occurs when the NodeB buffers data. throughput measured using the
4. A user releases a call. formula of NSN is lower than that
Denominator: duration of flow allocation in at the MAC-D layer. The using the formula provided by
time precession is 10 ms. Huawei.

This formula is used to calculate

the throughput at the MAC-HS
layer. The numerator is greater
Numerator: total bits at the MAC-HS layer correctly sent by HSDPA
SUM(pmSumAckedBitsSpiXX) than that of Huawei's first formula
users over the air interface based on the SPI statistics in a cell in a
Throughput /(0.002*pmSumNonEmptyUserBuffers) where and is equivalent to that of
Ericsson measurement period NodeB
per user XX = [0 .. 15] Huawei's second formula. The
Denominator: duration of sending data in the cell by all users in a
Unit: Kbit/s throughput measured using the
measurement period
formula provided by Ericsson is
lower than that provided by
Huawei.

Throughput
ALU None None N/A N/A
per user

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 71

Page 71
 Methods for Evaluating HSPA Data Transmission Problems Detected Through
Traffic Measurement (3)
HSUPA (Contrast KPI)

Vendor Item KPI Description NE Remarks

Numerator: total bits at the MAC-D layer that are

In softer handover
correctly received by HSUPA users over the air
scenarios, the throughput
VS.HSUPA.Thruput / (VS.HSUPA.DataTtiNum * 0.002) interface in a cell in a measurement period
Huawei Cell throughput NodeB measured using the formula
Unit: Kbit/s Denominator: duration of sending data by at least
of Huawei is lower than the
one HSUPA user in the cell in a measurement
actual throughput.
period

Numerator: received MAC-E PDU traffic in serving This formula is used to

(VS.CellReserve.Counter11+VS.CellReserve.Counter12)/ cells during softer handovers calculate the throughput at
Huawei Cell throughput NodeB
(VS.HSUPA.DataTtiNum.TRB*0.002) Denominator: duration in which the NodeB receives the MAC-E layer in
data from the air interface R014SPC360.

Numerator: received MAC-E PDU traffic in each cell

(pmSumAckedBitsCellEulTti2+pmSumAckedBitsCellEulTti1 The data traffic of the
in the active set during softer handovers
0)/ numerator measures that at
Denominator: duration in which the NodeB receives
Ericsson Cell throughput (0.002*pmNoActive2msIntervalsEulTti2+0.01*pmNoActive1 NodeB the MAC-E layer, which is
data from the air interface. When hardware
0msIntervalsEulTti10) greater than that at the
resources are insufficient, the duration is not
Unit: Kbit/s MAC-D layer.
measured.
Numerator: total bits at the MAC-D layer that are
correctly received by HSUPA users over the air In soft handover scenarios,
500*VS.eDCHdataBitSentToRNC.Cum/
interface in a cell in a measurement period the throughput measured
ALU Cell throughput VS.eDCHdataBitRec.NbEvt NodeB
Denominator: duration of sending data by at least using the formula of Huawei
Unit: Kbit/s
one HSUPA user in the cell in a measurement is higher than that of ALU.
period

(EDCH_DATA_SCELL_UL+EDCH_DATA_NSC_S_EDCH_UL+EDC
H_DATA_NSC_NS_EDCH_UL)*
8*0.001/(DUR_HSUPA_USERS_1_OR_2
+DUR_HSUPA_USERS_3_OR_4+DUR_HSUPA_USERS_5_OR_6+
DUR_HSUPA_USERS_7_OR_8+DUR_HSUPA_USERS_9_OR_10+
DUR_HSUPA_USERS_11_OR_12+DUR_HSUPA_USERS_13_OR_ The data traffic of the
14+DUR_HSUPA_USERS_15_OR_16+DUR_HSUPA_USERS_17_ numerator measures that at
OR_18+DUR_HSUPA_USERS_19_OR_20+DURA_HSUPA_USERS Numerator: MAC-E SDU traffic
NSN Cell throughput NodeB the MAC-E layer, which is
_21_TO_24+DURA_HSUPA_USERS_25_TO_28+DURA_HSUPA_U Denominator: online duration of users in a
SERS_29_TO_32+DURA_HSUPA_USERS_33_TO_36+DURA_HS measurement period (accuracy: 1s) greater than that at the
UPA_USERS_37_TO_40+DURA_HSUPA_USERS_41_TO_44+DUR MAC-D layer.
A_HSUPA_USERS_45_TO_48+DURA_HSUPA_USERS_49_TO_52
+DURA_HSUPA_USERS_53_TO_56+DURA_HSUPA_USERS_57_
TO_60+DURA_HSUPA_USERS_61_TO_64+DURA_HSUPA_USER
S_65_TO_72)
Unit: Kbit/s

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 72

Page 72
 Methods for Evaluating HSPA Data Transmission Problems Detected Through
Traffic Measurement (4)
HSUPA (Contrast KPI)

Vendor Item KPI Description NE Remarks

Throughput VS.HSUPA.MeanChThroughput This formula measures the throughput

Huawei RNC
per user Unit: Kbit/s of SDU at the RLC layer.

(VS.CellReserve.Counter11+VS.CellReserve.Counter12)/ This formula measures the

Throughput This formula measures the throughput
Huawei (VS.HSUPA.2msPDU.TTI.Num*0.002+VS.HSUPA.10msPD NodeB throughput of PDU at the MAC-E
per user of PDU at the MAC-E layer.
U.TTI.Num*0.01) layer in R014SPC360.

SUM(EDCH_DATA_SCELL_UL) * 8 /{SUM(MACE_PDU_RETR_00_COUNTER +
MACE_PDU_RETR_01_COUNTER*2 + MACE_PDU_RETR_02_COUNTER*3 +
MACE_PDU_RETR_03_COUNTER*4 + MACE_PDU_RETR_04_COUNTER*5 +
MACE_PDU_RETR_05_COUNTER*6 + MACE_PDU_RETR_06_COUNTER*7 +
MACE_PDU_RETR_07_COUNTER*8 + MACE_PDU_RETR_08_COUNTER*9 +
MACE_PDU_RETR_09_COUNTER*10 + MACE_PDU_RETR_10_COUNTER*11 +
MACE_PDU_RETR_11_COUNTER*12 +
The data traffic of the numerator
MACE_PDU_RETR_12_COUNTER*13)*0.01*(MACE_PDUS_10MS_TTI /(MACE_PDUS_10MS_TTI + The formula of NSN measures the
Throughput MACE_PDUS_2MS_TTI))}+{SUM(MACE_PDU_RETR_00_COUNTER + measures that at the MAC-E
NSN MACE_PDU_RETR_01_COUNTER*2 + MACE_PDU_RETR_02_COUNTER*3 + throughput of SDU at the NodeB
per user MACE_PDU_RETR_03_COUNTER*4 + MACE_PDU_RETR_04_COUNTER*5 + layer, which is greater than that at
MACE_PDU_RETR_05_COUNTER*6 + MACE_PDU_RETR_06_COUNTER*7 + MAC-E/MAC-I layer.
MACE_PDU_RETR_07_COUNTER*8 + MACE_PDU_RETR_08_COUNTER*9 + the RLC layer.
MACE_PDU_RETR_09_COUNTER*10 + MACE_PDU_RETR_10_COUNTER*11 +
MACE_PDU_RETR_11_COUNTER*12 +
MACE_PDU_RETR_12_COUNTER*13)*0.002*(MACE_PDUS_2MS_TTI /(MACE_PDUS_10MS_TTI +
MACE_PDUS_2MS_TTI))}
Unit: Kbit/s

((pmSumAckedBitsCellEulTti2+pmSumAckedBitsCellEulTti The data traffic of the numerator

Throughput 10)/((0.002*pmNoActive2msFramesEul) measures that at the MAC-E
Ericsson The formula of Ericsson measures the NodeB
per user +(0.01*mNoActive10msFramesEul))) layer, which is greater than that at
throughput of PDU at the MAC-E layer.
Unit: Kbit/s the RLC layer.

Throughput
ALU None None N/A N/A
per user

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 73

Page 73
 Methods for Evaluating HSPA Data Transmission Problems Detected Through
a Drive Test

Category Item Evaluation Software NE Remarks

Laptop
Dumeter, NetMeter High
computer
Application layer
HSDPA
throughput Probe, Dingli, XCAL,
UE High
Qvoice, Tems, QXDM

Laptop
Dumeter, NetMeter High
computer
Application layer
HSUPA
throughput Probe, Dingli, XCAL,
UE High
Qvoice, Tems, QXDM

Windows command:
HSPA Ping delay UE High
ping ipaddress

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 74

Page 74
 Methods for Evaluating Ping Delay

• Definition: Ping delay, is an end-to-end KPI that indicates the delay from when the test equipment
sends a ping request message to when received the ping reply message from server.
• Confirmation of key information: Confirm the following key information for any ping delay
problem:
• Ping packet size
Generally, when the size of a ping packet increases, the ping delay also increases.
• Server location (target address)
The server location has a great impact on ping delay. The ping delay in an internal network is much lower than that
in an external network.
The ping delay in an external network where the server is located varies greatly depending on the server location (at
home or abroad).
• Whether data transmission is involved
If a ping operation is performed during data upload or download, the ping delay is much higher than that when data
upload or download is not performed.

• Evaluation method:
• Moving/fixed-point: If the ping delay is evaluated in the moving status, all cells involved need to be
analyzed.
• Statistical average value/distribution: If distribution is measured, focus on analyzing the points
when delay is abnormal.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 75

Page 75
 Contents
1 Methods for Evaluating HSPA Data Transmission Problems

2 Classification and Clarification of HSPA Data Transmission Problems

3 Factors Affecting HSPA Data Transmission

4 Solutions to HSPA Data Transmission Problems

5 Deliverable Example and Template

6 Appendix: Introduction to HSPA Data Transmission Troubleshooting Tools

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 76

Page 76
 Classification and Clarification of HSPA Data
Transmission Problems
Level 1 Level 2 Source Identification Method Evaluation Mode
The throughput Assessment Compare and analyze the throughput by After swap, the throughput
Throughput of a swapped in the using traffic measurement of RNC/NodeB in is lower than that before
problem in network does not contract the same time segment one week before and swap.
traffic meet the after swap.
measurement requirement.

Swap, KPI Analyze the average application layer HSPA+ demonstration or

demonstration/fe requirement throughput of a single user through tracing on HSPA+ feature activation
ature activation the UE side by using Probe, QXDM, XCAL, or acceptance does not meet
Throughput acceptance, and Qvoice. the requirement. The
problem in a competition score in the competitive
drive test test is lower than those of
peer vendors.

The throughput Complaint Compare and analyze the throughput through

of the legacy traffic measurement of RNC/NodeB one week The throughput of the
network before and after network actions (such as legacy network whose
becomes lower. upgrade, rectification, and feature activation) KPIs are stable becomes
Complaint are taken or collect poor experience reports lower or the user
from field engineers. experience becomes poor.

Ping delay Ping delay KPI Measure the ping delay by using the ping Test shows that the ping
requirement command in Windows system. delay does not meet the
requirement specified in
the contract or is longer
than those of peer
vendors.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 77

Page 77
 Contents
1 Methods for Evaluating HSPA Data Transmission Problems

2 Classification and Clarification of HSPA Data Transmission Problems

3 Factors Affecting HSPA Data Transmission

 Factors affecting HSPA problems detected through traffic measurement

 Factors affecting HSPA problems detected through a drive test
 Factors affecting ping delay problems

4 Solutions to HSPA Data Transmission Problems

5 Deliverable Example and Template

6 Appendix: Introduction to HSPA Data Transmission Troubleshooting Tools

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 78

Page 78
 Factors Affecting HSPA Data Transmission Problems Detected
Through Traffic Measurement
Factors affecting throughput problems detected through traffic measurement (level 1)

Abnormal operation Abnormal alarm Parameter Known problem Transmission configuration

Abnormal operation: including operations of RNC/NodeB (operation logs). For example, modifying the IUPS route,
transmission network, or core network have a great impact on HSPA data transmission.
Abnormal alarm: Common alarms such as alarms about packet loss during transmission affect the throughput, which are
tested in the SOP.
Parameter: common algorithm parameters and channel parameters affecting HSPA data transmission. For details, see the
checklist of HSPA data transmission related parameters.
Known problem: generally algorithm implementation or compatibility problems. Software bugs are indicated through early
warning or release notes.
Transmission configuration: Transmission bandwidth, DSCP configuration, and transmission mapping of the service type
affect HSPA data transmission.

Factors affecting throughput problems detected through traffic measurement (level 2)

Resource
Coverage Traffic model
Code word Power CE Board load Iub/Iu interface bandwidth
Resource: Code words, power (uplink RTWP and downlink TCP), CE, bandwidth, and board load affect the HSPA
throughput.
Coverage: air interface quality, for example, CQI distribution
Traffic model: Resources are limited. Traffic change causes change of user resources, which then affects the HSPA
throughput.

Perform a forward check for factors at level 1 and a reverse check for factors at level 2.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 79

Page 79
 Factors Affecting HSPA Data Transmission Problems Detected
Through a Drive Test
Factors affecting throughput problems detected through drive test (level 1)

Server Test
Abnormal Transmission Terminal Portable performance
Abnormal alarm Parameter Known problem performance and CN mode
operation configuration performance and TCP window
TCP window

Abnormal operation: including operations of RNC/NodeB (operation logs). For example, modifying the IUPS route and rectifying the
transmission network or core network have a great impact on HSPA data transmission.
Abnormal alarm: Common alarms such as alarms about packet loss during transmission affect the throughput, which are tested in the
SOP.
Parameter: common algorithm parameters and channel parameters affecting HSPA data transmission. For details, see the checklist of
HSPA data transmission related parameters.
Known problem: generally algorithm implementation or compatibility problems. Software bugs are indicated through early warning or
release notes.
Transmission configuration: Transmission bandwidth, DSCP configuration, and transmission mapping of the service type affect HSPA
data transmission.
Laptop computer/server performance and TCP window: Poor performance of the laptop computer or server or improper window
setting affects data processing and return of ACK messages at the TCP layer and the HSPA throughput.
CN: Factors of the core network such as packet loss, high delay, and overload affect the HSPA throughput.
Test mode: The test mode such as single thread test mode or multi-thread test mode affects the HSPA throughput.

Factors affecting throughput problems detected through drive test (level 2)

Resource
Coverage Traffic model
Code word Power CE Board load Iub/Iu interface bandwidth

Resource: Code words, power (uplink RTWP and downlink TCP), CE, bandwidth, and board load affect the HSPA throughput.
Coverage: air interface quality, for example, CQI distribution
Traffic model: Resources are limited. Traffic change causes change of user resources, which then affects the HSPA throughput.

Perform a forward check to identify level-1 factors and a reverse check to identify level-2 factors.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 80

Page 80
 Factors Affecting HSPA Problems Collected from Complaints

The factors affecting problems collected from complaints are similar to

those affecting problems detected through traffic measurement or a drive
test. Based on problem locating methods, analyze and solve the problems
through traffic measurement first. If the problems persist, analyze the
problems by using drive test data.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 81

Page 81
 Factors Affecting HSPA Ping Delay Problems
Factors affecting the ping delay (level 1)

Server Test
Abnormal Known Transmission Terminal Portable performance
Abnormal alarm Parameter performance and CN mode
operation problem configuration performance and TCP window
TCP window

Abnormal operation: including operations of RNC/NodeB (operation logs). For example, modifying the IUPS route and rectifying the
transmission network or core network have a great impact on HSPA data transmission.
Abnormal alarm: Common alarms such as alarms about packet loss during transmission affect the throughput, which are tested in the
SOP.
Parameter: common algorithm parameters and channel parameters affecting HSPA data transmission. For details, see the checklist of
HSPA data transmission related parameters.
Known problem: generally algorithm implementation or compatibility problems. Software bugs are indicated through early warning or
release notes.
Transmission configuration: Transmission bandwidth, DSCP configuration, and transmission mapping of the service type affect HSPA
data transmission.
Laptop computer/server performance and TCP window: Poor performance of the laptop computer or server or improper window
setting affects data processing and return of ACK messages at the TCP layer and the HSPA ping delay.
CN: Factors of the core network such as packet loss, high delay, and overload affect the HSPA ping delay.
Test mode: Whether upload or download is enabled during the test affects the HSPA ping delay.

Factors affecting the ping delay (level 2)

Resource
Coverage Traffic model
Code word Power CE Board load Iub/Iu interface bandwidth

Resource: Code words, power (uplink RTWP and downlink TCP), CE, bandwidth, and board load affect the HSPA ping delay.
Coverage: air interface quality, for example, CQI distribution
Traffic model: Resources are limited. Traffic change causes change of user resources, which then affects the HSPA ping delay.

Perform a forward check to identify level-1 factors and a reverse check to identify level-2 factors.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 82

Page 82
 Contents
1 Methods for Evaluating HSPA Data Transmission Problems
2 Classification and Clarification of HSPA Data Transmission Problems

3 Factors Affecting HSPA Data Transmission

4 Solutions to HSPA Data Transmission Problems

 HSPA Troubleshooting Procedure
 Analysis on Throughput Problems Detected Through Traffic Measurement
 Analysis on Throughput Problems Detected Through a Drive Test
 Analysis on Problems Collected from Complaints
 Analysis on Ping Delay Problems

5 Deliverable Example and Template

6 Appendix: Introduction to HSPA Data Transmission Troubleshooting Tools

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 83

Page 83
 HSPA Data Transmission Troubleshooting Procedure
HSPA data transmission troubleshooting covers four steps, as listed in the following table. For
details, see the attachment. Standard Actions for Troubleshooting HSPA Data Transmission Problems.rar

Step Action Entry Condition Purpose

1. Confirm the problem type: throughput problem detected through traffic
Step 1: Confirm and classify the measurement, throughput problem detected through drive test, ping delay problem,
None
problem. or problem collected from complaints.
2. Determine the scope of the problem: entire network, top cells, or a single site.
Check whether any abnormal operations exist (operations on the RAN side can be
Action 1: Check abnormal seen from operation logs and scripts and some operations on other sides except
None
operations. RAN side, for example, transmission rectification and upgrade of core network,
need to be obtained from the customer).
Action 2: Check alarms. None Check whether any alarms affecting data transmission are generated.
Step 2:
Perform a Action 3: Check early
None Check whether any early warnings affecting data transmission exist.
forward warnings.
check. Action 4: Check
parameters (including None Check whether any abnormal configurations affecting data transmission exist.
licenses).
Action 5: Check
Check whether the transmission configuration complies with specifications and
transmission None
whether it affects data transmission if it does not comply with specifications.
configurations.
Action 6: Analyze Check whether any bottlenecks of resources such as CPU, code word, CE, power,
None
resources. and bandwidth exist and whether the bottlenecks affect data transmission.
Action 7: Analyze traffic Analyze the change of CS Erlang, PS R99, PS HSPA traffic, and number of users
None
models. and check whether the change of throughput is related to traffic models.
Action 8: Analyze The throughput detected through traffic Analyze whether coverage affects data transmission problems and analyze CQI
coverage. measurement changes slightly. distribution in the downlink and proportion of UE power restriction in the uplink.
Step 3:
Perform a 1. A throughput problem detected through
reverse a drive test occurs.
Analyze L3 signaling, L1 signaling, L2 signaling, and application layer signaling
check. Action 9: Analyze the 2. If a throughput problem detected
and confirm the impacts of signaling of the HSDPA/HSUPA problem, L1
traced data about the through traffic measurement or collected
scheduling, L2 retransmission, application layer delay, and packet loss on the
single user throughput. from complaints cannot be located by
throughput.
analyzing traffic statistics, analyze the
traced data about a single user.
Action 10: Analyze the
Analyze the channel where signaling is transmitted, general delay, delay on the Uu
traced data about the A ping delay problem occurs.
interface and Iub interface, and confirm the points with high delay.
single user delay.
Step 4: Check whether the problem is
None Check whether the problem is solved.
solved.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 84
Page 84
 R99 PS Data Transmission Troubleshooting Procedure

R99 PS data transmission troubleshooting covers four steps, as listed in the following table.
Step Action Entry Condition Purpose
Step 1: Confirm and classify the problem. None similar to that for HSPA data transmission troubleshooting

Action 1: Check abnormal

None similar to that for HSPA data transmission troubleshooting
operations.

Step 2: Action 2: Check alarms. None similar to that for HSPA data transmission troubleshooting
Perform a Action 3: Check early
None similar to that for HSPA data transmission troubleshooting
forward check. warnings.
Action 4: Check parameters
None similar to that for HSPA data transmission troubleshooting
(including licenses).
Action 5: Check
None similar to that for HSPA data transmission troubleshooting
transmission configurations.
Action 6: Analyze resources. None similar to that for HSPA data transmission troubleshooting

Action 7: Analyze traffic

None similar to that for HSPA data transmission troubleshooting
models.

Do not perform this step when you

Action 8: Analyze coverage. solve R99 PS data transmission
problems.
Step 3: 1. A throughput problem detected
Perform a through a drive test occurs.
reverse check. 2. If a throughput problem detected
Action 9: Analyze the traced
through traffic measurement or
data about the single user similar to that for HSPA data transmission troubleshooting
collected from complaints cannot
throughput.
be located by analyzing traffic
statistics, analyze the traced data
about a single user.
Action 10: Analyze the
traced data about the single A ping delay problem occurs. similar to that for HSPA data transmission troubleshooting
user delay.
Step 4: Check whether the problem is solved. None similar to that for HSPA data transmission troubleshooting

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 85

Page 85
 Root Causes of HSPA Data Transmission Problems and Distribution of
Standard Actions

According to the analysis on root causes of online problems in 2012, more than 80% of problems can
be located following the standard actions.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 86

Page 86
 Contents
1 Methods for Evaluating HSPA Data Transmission Problems
2 Classification and Clarification of HSPA Data Transmission Problems

3 Factors Affecting HSPA Data Transmission

4 Solutions to HSPA Data Transmission Problems

 HSPA Troubleshooting Procedure
 Analysis on Throughput Problems Detected Through Traffic Measurement
 Analysis on Throughput Problems Detected Through a Drive Test
 Analysis on Problems Collected Through Complaints
 Analysis on Ping Delay Problems

5 Deliverable Example and Template

6 Appendix: Introduction to HSPA Data Transmission Troubleshooting Tools

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 87

Page 87
 Confirming a Throughput Problem Detected Through Traffic
Measurement
Traffic statistics Input Output Solution
If the problem involves the
1. Traffic entire network, perform a
NodeB KPI: measurement forward check on problems
1. HSDPA: OMStar form; detected through traffic
VS.DataOutput.Mean, 2. Whether the measurement and a
VS.DataTtiRatio.Mean, problem reserve check on all items.
Traffic Statistic Analysis Model for UMTS PS Data Transmission.rar
VS.HSDPA.InactiveDataTtiRatio.Me involves the If the problem involves top
an; Tool entire network
or top cells
cells, perform a forward
2. HSUPA: check on problems
VS.HSUPA.Thruput, detected through traffic
VS.HSUPA.DataTtiNum measurement (for
example, check on alarms,
Or RNC KPI:
cell related parameters,
3. HSDPA:
and site configuration) and
VS.HSDPA.MeanChThroughput.Tot a reverse check on some
alBytes; items (such as resource
VS.HSDPA.MeanChThroughput and coverage).
VS.HSDPA.UE.Mean.Cell
4. HSUPA:
VS.HSUPA.MeanChThroughput.Tot
alBytes;
VS.HSUPA.MeanChThroughput
VS.HSUPA.UE.Mean.Cell

Analysis rule: If the network

throughput measured still cannot
meet the requirement after 20% of
top cells are excluded, the problem
is a network problem; otherwise,
the problem is caused by top cells.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 88

Page 88
 Forward Check (Action 1: Check Abnormal Operations; Action 2:
Check Alarms; Action 3: Check Early Warnings)

Input Output Solution

1. Perform
rollback (in the
SOP inspection case of an
1. Configuration files of RNC and
NodeB and license file OMStar report abnormal
operation).
2. Alarm logs exported from the
2. Clear the
M2000
alarm.
3. Operation logs exported from
the M2000 Tool 3. Take
preventive
measures.

Case 1: The Internet access speed is low in office S.

At a site of office S, dual-stack transmission mode is used. The IP path is interrupted after the
National Day and is not restored, that is, only the bandwidth of one E1 is available. As a result, the
Iub interface bandwidth is limited and the Internet access rate is low.

Any abnormal operations, alarms, and early warnings can be checked based on the SOP.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 89

Page 89
 Forward Check (Action 4: Check Parameters)
Input FMA (see the Output Solution
appendix for
Configuration files of RNC tool 1. List of
abnormal 1. Perform
and NodeB and license instructions.)
parameters rollback.
file 2. Modify the
2. List of
abnormal license.
Checklist for HSPA
parameters and license Tool licenses

Parameter Checklist for PS Data Transmission V1.11.rar

Case 2 (incorrect setting of the R99 DCCC 4a threshold): In busy hours, the number of HSUPA
users exceeds the allowed value, that is, 20. When HSPA users move from the DRD of an R99 cell
to an HSPA cells, the users are forced to go back R99 cell. The initial rate of the R99 cell is 64 Kbit/s,
whereas the R99 DCCC 4a threshold is set to 4 Kbit/s and the baseline value is 1 Kbit/s. As a result,
the uplink rate cannot rise to 384 Kbit/s, affecting the HSDPA rate.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 90

Page 90
 Forward Check (Action 5: Check Transmission
Configuration)
Input Output Solution
Configuration files of
RNC and NodeB
FMA Results of the
check on Perform
UMTS transmission transmission
configuration specifications configuration
rollback.
Tool specifications

1. Use the FMA tool to convert the configuration of Node B from xml
to mml (see the appendix).
2. For the configuration of RNC, use the FMA tool to filter the
configuration of NodeB.

See case 3: The HSUPA Rate Drops in Office L Because the Transmission Configuration
Does not Comply with Specifications

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential • Page9191

 Case 3: The HSUPA Rate Drops in Office L Because the Transmission
Configuration Does not Comply with Specifications
Problem description: After the NSN network in office L is swapped, the HSUPA RAB establishment
success rate is low and the cell HSUPA throughput and average throughput of HSUPA users are almost 0
(see the following table), which results in rollback on the day.
Problem analysis
Step 1: Confirm and classify the problem.
Confirm that the problem comes from customer complaints and confirm that the problem occurs in two
sites on the day of swap.

VS.HSUPA.RAB.A VS.HSUPA.MeanChTh VS.HSUPA.MeanCh

Time VS.HSUPA.RAB.FailEstab
ttEstab roughput.TotalBytes Throughput
2011-8-18 8:30 14 14 0 0
2011-8-18 9:00 65 65 0 0
2011-8-18 9:30 36 36 0 0
2011-8-18 10:00 15 15 0 0
2011-8-18 10:30 1 1 0 0
2011-8-18 11:00 32 32 0 0
2011-8-18 11:30 7 8 0 0
2011-8-18 12:00 23 23 9720 15.247059
2011-8-18 12:30 3 3 0 0
2011-8-18 13:00 11 11 0 0
2011-8-18 13:30 0 0 0 0
2011-8-18 14:00 2 2 0 0
2011-8-18 14:30 47 47 0 0
2011-8-18 15:00 53 53 0 0
2011-8-18 15:30 6 6 0 0

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 92

Page 92
 Case 3: The HSUPA Rate Drops in Office L (Continued)
Step 2: Perform a forward check.
The transmission configuration check shows that the value of IPPATH DSCP carried over HSUPA
signaling is 34, which is the same as that of the OMCH channel of the NodeB. The DSCP value
recommend by transmission configuration specifications is 38.
Executed Action
Standard Action Check Result

Action 1: Check abnormal operations. OK

Action 2: Check alarms. OK

Action 3: Check early warnings. OK

OK
Action 4: Check parameters.
Action 5: Check transmission The DSCP value configured differs greatly from the Modify the DSCP value according to
configurations. recommended value, which results in the problem. transmission configuration specifications.

Transmission configuration specifications Field transmission configuration

Step 3: Check whether the problem is solved.
The value of IPPATH DSCP carried over HSUPA SRB is 34, which is the same as that of the OM channel. The correct
information cannot be configured on the VLAN. After the value of IPPATH DSCP carried over HSUPA SRB is changed to 38,
the problem is solved.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 93

Page 93
 Reverse Analysis on Throughput Problems Detected Through Traffic
Measurement (Action 6: Analyze Resources)
Input OMStar Output Solution
1. Network evaluation 1. Analysis
module 1. Expand radio
2. Network
report on
optimization module network resources.
Original traffic statistics of RNC For details, see 2. Analysis 2. Expand
and NodeB appendix 1: OMStar report on transmission
Configuration files of RNC and Network Evaluation network resources and
NodeB Tool.
optimization check detailed
License files of RNC and NodeB
packet loss.
Tool 3. Expand board
resources.
Analysis rule: See the
network evaluation
module and the network
optimization module.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 94

Page 94
 Case 4: The PS Traffic of a Site in Office O Is Low
(Resources Are Insufficient)
Problem description: The PS traffic of a site in office O is low. After the site is upgraded, the problem is solved.
Problem analysis:
Step 1: Confirm and classify the problem.
Confirm that the problem occurs at one site: The HSDPA throughput in peak and off-peak hours and the average user
throughput drop obviously.
Step 2: Perform a forward check.
Standard Action Check Result Executed Action
Action 1: Check abnormal operations. OK None
Action 2: Check alarms. OK None
Action 3: Check early warnings. OK None
Action 4: Check parameters. OK None
Action 5: Check transmission configurations. OK None

Step 3: Perform a reverse check.

Standard Action Check Result Executed Action
The traffic measurement data of NodeB shows that Disable HSUPA flow
Action 6: Analyze resources. the uplink bandwidth is only 300 Kbit/s before control.
upgrade.
Action 7: Analyze traffic OK None
models.
Action 8: Analyze coverage. OK None
Action 6: Analyze resources.
The traffic measurement data of NodeB shows that the uplink bandwidth is only 300 Kbit/s before upgrade. This is because
the NodeB receives a message indicating packet loss or delay from the RNC and modifies the uplink bandwidth (the lowest
bandwidth can be set to 300 Kbit/s). After the NodeB resets, the NodeB changes the uplink bandwidth to the initial value,
that is, 10 Mbit/s. After the NodeB is upgraded to R13 and HSUPA flow control is disabled, the problem is solved.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 95 95

 Reverse Analysis on Throughput Problems Detected Through Traffic
Measurement (Action 7: Analyze Traffic Models)

Input OMStar Output Solution

1. Network 1. Increase the R99
Original CDRs of RNC
1. Analysis report on
evaluation traffic and expand
Configuration file of network evaluation
module carriers.
RNC 2. Analysis report on
2. Network 2. Increase the
network optimization
optimization number of HSDPA
module users, expand carriers,
Analysis rule: See the
modify the GBR, and
network evaluation module
Tool limit the number of
and the network
HSDPA users.
optimization module.

Results output by the network evaluation and optimization modules

of OMStar:

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 96 96

 Case 5: The Average Rate of HSDPA Users Drops After Office G Is
Upgraded (Traffic Is Added)
Problem description: After office G is upgraded from R12 to R13, the average throughput of HSDPA
users drops from 700 Kbit/s to 600 Kbit/s.
Problem analysis:
Step 1: Confirm and classify the problem.
Confirm that the throughput drops in the whole RNC and the time when this problem is not related to the
time when the RNC is upgraded. In peak hours, the average throughput of HSDPA users drops obviously.

Step 2: Perform a forward check.

Standard Action Check Result Executed Action

Action 1: Check abnormal operations. OK None

Action 2: Check alarms. OK None
Action 3: Check early warnings. OK None
Action 4: Check parameters. OK None

Action 5: Check transmission configurations. OK None

Step 3: Perform a reverse check.

Standard Action Check Result Executed Action

After the RNC is upgraded, the number of congestion Analyze traffic models.
Action 6: Analyze resources. increases in peak hours, which is related to increase of
traffic. In this case, analyze traffic models.
Action 7: Analyze traffic HSPA traffic increases obviously.
models.
Action 8: Analyze coverage. OK None

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 97 97

 Case 5: The Average Rate of HSDPA Users Drops After Office G Is
Upgraded (Continued)
Action 7: Analyze traffic models.

The number of
HSDPA RAB
establishment
attempts or the
number of
successfully
established HSDPA
RABs increases
since April 6 and is
larger than that
before upgrade.

The average number

of HSDPA users
tends to increase
gradually since April
6.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 98 98

 Reverse Analysis on Throughput Problems Detected Through Traffic
Measurement (Action 8: Analyze Coverage)
Input
Tool Output Solution
Documents about counters of peer
If CQI distribution
vendors Compare the differs greatly
Configuration scripts of RNC/NodeB Excel charts of CQI before and after
before and after swap
distribution swap, compare the
Counters of RNC/NodeB before and multi-carrier policy
after swap before and
after swap and HSDPA bearer
policy and check
coverage.
Analysis rule:
Measure the CQI distribution before
and after swap and compare the charts.

HSDPA: Compare the CQI distribution.

Consistent Inconsistent
before and before and after
after swap swap

HSUPA: Compare the proportion of HSUPA users whose UPH is limited in the cell (VS.HSUPA.MaxPwrLmtUserRatio).

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 99 99

 Contents
1 Methods for Evaluating HSPA Data Transmission Problems
2 Classification and Clarification of HSPA Data Transmission Problems

3 Factors Affecting HSPA Data Transmission

4 Solutions to HSPA Data Transmission Problems

 HSPA Troubleshooting Procedure
 Analysis on Throughput Problems Detected Through Traffic Measurement
 Analysis on Throughput Problems Detected Through a Drive Test
 Analysis on Problems Collected Through Complaints
 Analysis on Ping Delay Problems

5 Deliverable Example and Template

6 Appendix: Introduction to HSPA Data Transmission Troubleshooting Tools

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 100100

 Confirming Throughput Problems Detected Through a Drive Test

Output Solution
1. Scope of sites or
UE tracing data Input cells where the Perform a
or throughput throughput problem is
screenshot UE forward
detected in a drive test
analysis.
tracing 2. Test mode of
throughput in a drive
Analysis rule: provided based on tool test: moving or fixed
drive test rules, which are point, FTP or HTTP
specified by the customer or a 3. Confirm the problem
third party symptom: test on
whether the
throughput meets the
requirement or single
point test for locating
the problem.

Case: 160 3G sites in office M are swapped. The throughput obtained in a drive test in
moving mode is 730 Kbit/s before the swap, and the throughput obtained in a drive test in the
same area is about 600 Kbit/s after the swap. The drive test is performed in FTP download
mode. For details, see case 12.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 101101

 Reverse Analysis on HSDPA Throughput Problems Detected Through
a Drive Test (Action 9: Analyze L3 Signaling)

Input
RNC CDT
Output Solution
Analysis Rules for HSPA Single User Tracing Data.rar FMA 1. Check results
of UE 1. Replace the
1. Signaling for checking UE
capabilities:
FMA capabilities terminal of the
RRC_CONNECT_SETUP_CMP 2. Check result related
2. Signaling for checking the of the category.
registration rate: registration rate 2. Set the
RANNAP_RAB_ASSIGNMENT_REQ registration rate
3. Check results
3. Network capability check (ADT again on the
URES) of network
capabilities HLR.
3. Check
Analysis rules:
1. Observe the signaling field hsdsch-
whether related
physical-layer-category and UE boards of the
capability information. NodeB support
2. Observe the uplink and downlink • Terminal capability the
registration rates from the maxBitrate HSDPA/HSPA+
field and ExtendedMaxBitrate field. If the • Terminal registration
capability.
rates are lower than the required rates, • Network capability
an exception occurs.
3. In the resource audit response
message, check whether related service
feature capabilities are supported.

Note: Actions 1 to 8 for the throughput problems detected through a drive test are basically the
same as those for the throughput problems detected through traffic measurement except that the
sites and cells to be analyzed are different. In addition, the forward check covers the check on
servers, laptop computers, and test mode, which are included in the HSPA parameter checklist.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 102
Page 102
 Reverse Analysis on HSDPA Throughput Problems Detected Through
a Drive Test (Action 9: Analyze L1 Signaling)

NodeB Input Output Solution

See the 1. Find the test place
CDT appendix where the CQI is
for NodeB 1. Check result better and more
CDT of CQI stable by using the
1. DL HSDPA User Enhanced 2. Check result drive test software.
analysis
2. DL HSDPA User Flow Ctrl (HSDPA).
of BLER 2. a. Change the test
3. Trans Iub BW REQ and Trans 3. Check result place to the one
Iub BW RESP FMA of radio
resources (code
where the CQI is
stable.
and power) b. Replace the
4. Check result terminal and use
of transmission another terminal of
the same model or a
Analysis rules: different model.
1. Check the CQI reported by the UE Compare the test
(which is smaller than 25 and is the results.
maximum value in a peak value test). 3. a. Set the CQI
The CQI fluctuates frequently. based on the baseline
2. Check the BLER. If it is higher than value.
10%, an exception occurs. b. Update the license
3. Check whether the maximum number and expand code
of available HS-PDSCH codes in the resources.
cell is greater than or equal to 14 and 4. a. Disable HSDPA
whether the maximum power is lower flow control.
than 50%. If yes, the power is limited.
b. Perform a multi-
4. Check whether packet loss or a delay thread or packet
problem occurs. If yes, the bandwidth is injection test.
allocated improperly.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 103103

 Reverse Analysis on HSDPA Throughput Problems Detected Through a Drive
Test (Action 9: Analyze L1 Signaling)

Output Solution
RNC CDT Input See the 1. Check RLC 1. Change the
appendix BO is 0 or not. test to a multi-
for RNC 2. Check result thread or packet
1. L2 RLC Bo statistical chart CDT of RLC injection test.
2. PS L2 RB statistics analysis retransmission 2. Modify the flow
3. PS L2 FP packet statistics and control algorithm
(HSPA).
DownlinkWindow to the static flow
Analysis rules: FMA sfullnum control algorithm.
Change the test
3. Check results
1. If the value of RLC Bo is 0, an place to the one
of uplink air
exception occurs. Follow the handling where the
interface
measures. If the value of RLC Bo is not coverage is good.
bandwidth and
0, go to the next step. 3. Perform a
allocated
2. If the value of ulSufilistnum packet injection
bandwidth for
increases continuously, an exception test.
NodeB
occurs. Packet loss may occur on the
Iub interface or retransmission is
performed over the air interface. If the
value of DownlinkWindowsfullnum is
not 0 and increases continuously, an
exception occurs. Packets are blocked
in the RLC sending window on the RNC
side and cannot be sent.
3. If the count of Harqfailure increases
continuously, an exception occurs.
Related items of TNLIub can be used to
collect statistics of packet loss and
delay on the Iub interface in the uplink
of R99 or UPA. If the number of lost
packets or the delay increases
continuously, an exception occurs.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 104104

 Reverse Analysis on HSDPA Throughput Problems Detected Through
a Drive Test (Action 9: Analyze Application Layer Signaling)

RNC CDT
Input Output Solution
1. Enable RNC CDT by using 1. Change the path
FMA and choose Tool > User 1. Check to another APN path
plain extraction to obtain the results of and modify the flow
Pcap file in the same directory. FMA packet loss control algorithm to
Import TranExpert. on devices the static flow
TranEx above or control algorithm.
Analysis rule: pert below RNC 2. Modify the
Check the uplink packet loss at 2. Check window for servers
the point where packets are results of and laptop
captured and the analysis results performance computers. Replace
of delay on the RAN side. of servers servers and laptop
If the results show that packet and laptop computers with the
loss occurs in the uplink of the computers ones that have
packet capture point, packet loss better performance.
occurs in devices above the
RNC.
Generally, the measured delay is
about 100 ms. If the delay is
above 200 ms and fluctuates
greatly, an exception occurs.

Case 6: The Peak Rate Is Low During the DC Competitive Test in Office G (Next Page)

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 105105

 Case 6: The Peak Rate During the DC Competitive Test in Office G
Does not Meet the Requirement (Caused by Reverse Factors)
Problem description: The peak FTP download rate is always low during the DC competitive test in office G. The peak rate is
38 Mbit/s and the rate fluctuates greatly.
Problem analysis:
Step 1: Confirm and classify the problem.
Confirm that the problem is detected in a drive test and is about the throughput of a single user and confirm that the customer
requires a minimum DC rate of 40 Mbit/s.
Step 2: Perform a forward check.
Standard Action Check Result Executed Action

Action 1: Check abnormal operations. OK

Action 2: Check alarms. OK
Action 3: Check early warnings. OK
The size of the window for laptop computers is 64K. Modify the size of the
Action 4: Check parameters. The MTU is not checked until application layer window for laptop
signaling is analyzed in action 9. computers to 256K.
Action 5: Check transmission configurations. OK

Step 3: Perform a reverse check and take measures.

Executed Action
Standard Action Check Result
The terminal registration rate and core network assignment None
Action 9: Analyze L3 signaling. rate are normal.
The CQI and code resources are normal. The allocated FTP download +
Action 9: Analyze L1 signaling. bandwidth is sufficient, but data sources for the points where packet injection
the problem occurs are insufficient.
The value of HarqFailureNum does not increase and the None
uplink air interface is normal.
Action 9: Analyze L2 signaling. In the downlink, no retransmission occurs and packet loss or
a delay problem does no occur on the Iub interface.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 106106

 Case 6: The Peak Rate During the DC Competitive Test in Office G
Does not Meet the Requirement (Continued)

Results of analysis on L1 signaling

Results of analysis on L2 signaling

According to the analysis on L1 signaling and L2 signaling, delay problems do not exist on the
RAN and packet loss reduces the amount of data to be transmitted from the upper layer and results
in a low rate. An exception may occur on the CN. Then analyze application layer signaling.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 107107
 Case 6: The Peak Rate During the DC Competitive Test in Office G Does not
Meet the Requirement (Continued)
Action 9: Analyze application layer signaling.
1. The packet loss rate on devices above RNC is 0.06% and the number of out-of-order packets is 7776.
2. Compare the captured packets and lost packets on the Iu interface with those on the UE side. The comparison shows that the packets in yellow
are captured and lost packets on both the Iu interface and the UE side. The packets are lost before they reach the RNC. The packets in green are
lost packets detected by the UE. The analysis on the packets shows that the packets appear twice among the packets captured on the Iu interface
and some are fragmented before they reach the RNC. The RNC receives only the first segment. In this case, the packets fail to be assembled on
the RNC, which results in retransmission.

Packet statistics about discarded

Results of analysis on TCP packets fragments

After the MTU of routers on the CN is changed to 1500 bytes, the peak rate becomes stable and is around 40 Mbit/s.
This parameter is related to transmission equipment on the CN. It takes more time and efforts to check this
parameter than other parameters related to the RNC and NodeB. Reverse analysis shows that the MTU is limited.
This problem can be located through forward parameter analysis.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 108108
 Reverse Analysis on HSUPA Throughput Problems Detected Through
a Drive Test (Action 9: Analyze L3 Signaling)

RNC CDT Input Output Solution

1. Check 1. Replace the
1. Signaling for checking UE results of UE
capabilities: terminal of the
RRC_CONNECT_SETUP_CMP FMA capabilities related category.
2. Signaling for checking the 2. Check result 2. Set the
registration rate: FMA of the registration rate
RANNAP_RAB_ASSIGNMENT_REQ registration again on the HLR.
3. RRC_RB_SETUP rate 3. Check whether
3. Check related boards of
Analysis rules: results of the NodeB
1. Check the signaling field network support the
edch-physical-layer-category capabilities HSDPA/HSPA+
and observe the capability capability.
information about the UE.
2. Check the uplink registration
rate from the maxBitrate field.
3. Check the bearer information • 1. Terminal capability
of RB-MappingInfo whose RB ID • 2. Terminal registration
is 5. If the bearer information is • 3. Network capability
not E-DCH, an exception occurs.

Note: Actions 1 to 8 for the throughput problems detected through a drive test are basically the
same as those for the throughput problems detected through traffic measurement except that the
sites and cells to be analyzed are different. In addition, the forward check covers the check on
servers, laptop computers, and test mode, which are included in the HSPA parameter checklist.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 109

Page 109
 Reverse Analysis on HSUPA Throughput Problems Detected Through
a Drive Test (Action 9: Analyze L1 Signaling)

NodeB CDT
Input See the Output Solution
appendix
1. Check result 1. Set ROT to a
1. DL HSUPA RlEnhanced for NodeB of load on cells reasonable
2. Trans Iub HSUPA CDT CDT 2. value, set the
You can see the values of OutBw analysis Retransmission background
(outbound bandwidth allocated to (HSUPA). 3. Check results noise to the
transmission equipment) and Loss (lost of radio actual value, and
packets on the Iub interface) by using FMA resources (CE, suppress
the FMA tool. power, and external system
traffic volume) interference.
limitation 2. Change the
test place to the
Analysis rules: 4. Check results
one where the
1. Check whether the value of of transmission
coverage is
uhwDelayCurLoad reaches 75%. If printing
good.
yes, uplink overload occurs.
3. a. Update CE
2. Check whether the proportion of Hi
resources; b.
whose value is 0 exceeds 10%. If yes,
Change the test
packets are frequently retransmitted.
place to the one
3. If the scheduling reason is (0, 21),
where the
the number of CE resources is
coverage is
insufficient. If the value of
good; c. Adopt
rLScheInfo1.ucUph is smaller than 31,
the uplink packet
the power is insufficient. If the value of
injection mode.
rLScheInfo1.ucTebs is smaller than 25
4. Disable
and fluctuates, the UE buffer is
HSUPA flow
insufficient.
control.
4. Check whether packet loss or a
delay problem occurs. If yes, an
exception occurs (see related
description of HSDPA).

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 110

Page 110
 Reverse Analysis on HSUPA Throughput Problems Detected Through
a Drive Test (Action 9: Analyze L2 Signaling)

See the Output Solution

RNC CDT Input appendix
for RNC 1. Check 1. Adopt packet
1. PS L2 RB statistics (FMA- CDT results of RLC injection.
>tools->L2 static extraction->PS analysis retransmissio 2. Change the
L2 FWD->PS RB) (HSPA). n and test place to the
2. PS L2 FP packet statistics one with better
(FMA->tools->L2 static
FMA harqfailure
signal.
2. Lost
extraction->PS L2 FWD->PS FP) 3. Disable
packets or
HSUPA flow
delay on the
Analysis rules: control.
Iub interface
1. If the uplink load increases in the uplink
continuously, an exception
occurs. Packets may be lost on
the Iub interface or retransmitted
for multiple times over the air
interface.
2. If the value of Harqfailure
increases continuously, an
exception occurs (see related
description of HSDPA).
3. Related items of TNLIub can
be used to collect statistics of
packet loss and delay on the Iub
interface in the uplink of UPA
(see related description of
HSDPA).

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 111

Page 111
 Reverse Analysis on HSUPA Throughput Problems Detected Through
a Drive Test (Action 9: Analyze Application Layer Signaling)
See related analysis on HSDPA data transmission problems.

Case 7: The HSUPA Rate Is Low Due to Packet Loss on the Iub Interface
at a Site of Office T (Next Page)

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 112

Page 112
 Case 7: The HSUPA Rate in Office T Is Low (Caused by Reverse
Factors)
Problem description: Test shows that the maximum HSUPA rate at a site of Vodafone in office T is only about 1 Mbit/s,
which is lower than those tested at other sites. The HSUPA rate generally ranges from 700 Kbit/s to 800 Kbit/s.
Problem analysis:
Step 1: Confirm and classify the problem.
Confirm that the problem is a throughput problem detected through a drive test and that the customer requires a stable
HSUPA rate of 2 Mbit/s.
Step 2: Perform a forward check.
Standard Action Check Result Executed Action
Action 1: Check abnormal OK
operations.
Action 2: Check alarms. OK
Action 3: Check early warnings. OK
The values of power control parameters of HSUPA E- Set the parameter
HICH and E-RGCH are different from the baseline values to the baseline
Action 4: Check parameters. values. values.
The MTU is not checked until application layer
signaling is analyzed in action 9.
The DSCP on the RNC side and NodeB side is different. Modify the setting
Action 5: Check transmission according to the
configurations. baseline.

Step 3: Perform a reverse check and take measures.

Check results of analysis on L3:

Standard Action Check Result Executed Action

The terminal registration rate and None
Action 9: Analyze L3 signaling. CN assignment rate are normal.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 113

Page 113
 Case 7: The HSUPA Rate in Office T Is Low (Continued)
Action 9: Analyze L1 signaling.
1. The RTWP is normal, SGs are sufficient, and the power of UE and data sources are sufficient (TEBS).
2. When the rate is abnormal, the following scheduling results occur: 2(RG down) with cause value
4(FLOW_CONTROL_RG_DOWN) and 1 (hold) with the cause value 21
(FLOW_AG_RG_FORBIDDEN_HOLD_WHILE_UNHAPPY_UP).

Analysis on radio resources at L1

Analysis on scheduling at L1

Based on the analysis on L1 signaling, the rate is low because flow control is enabled, which is possibly
caused by packet loss or delay on the Iub interface. To locate the root cause, analyze L2 signaling.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 114
Page 114
 Case 7: The HSUPA Rate in Office T Is Low (Continued)

Action 9: Analyze L2 signaling.

Based on RNC CDT data, the values of DL suffilist and TNLIubEdchFrmLost increase, which indicates
that the RNC detects packet loss on the Iub interface.

Results of L2 signaling analysis

After the ping command is run on the NodeB LMT and continuous ping detection is enabled, the ping
command can be run successfully when the ping packet size is set to 1400 but fails when the ping
packet size is to set to 1470. The MTU of intermediate transmission equipment is set to an improper
value, that is, the value is smaller than 1500. After the MTU is set to 1500 bytes, the HSUPA rate
increase to 2 Mbit/s and remains stable.

This parameter is related to intermediate transmission equipment. It takes more time and efforts
to check this parameter than other parameters related to the RNC and NodeB. Reverse analysis
shows that the MTU is set improperly. This problem can be located through forward parameter
analysis.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 115

Page 115
 Case 8: The DPA Throughput Is Lower Than Those of Peer Vendors
(Caused by Reverse Factors)
Problem description: The drive test in Oslo area and test in Faberg lab performed by the customer
show that the FTP download rate is obviously lower than those of other networks (about 2 Mbit/s
lower). The current test shows that the rate fluctuates greatly.
Problem analysis:
Step 1: Confirm and classify the problem.
Confirm the throughput problem detected through a drive test and test in the lab. In addition, confirm
that the throughput under the RNC is low and fluctuates.
Step 2: Perform a forward check.

Standard Action Check Result Executed Action

Action 1: Check abnormal operations. OK

Action 2: Check alarms. OK
Preventive measures are not taken for Give early warnings and
Action 3: Check early warnings. flow control enabled on the UOIc board. take preventive measures.
Action 4: Check parameters. OK

Action 5: Check transmission OK

configurations.
Preventive measures:
Run the ADD ATMLOGICPORT command on the UOIc board (this operation is not required if the
command has been run), change the HSPA service bearer to AAL2PATH of the NRTVBR type, and
modify the transmission configuration on the NodeB accordingly.

After the preventive measures are taken, the throughput increases by 20%, which is close to those
of peer vendors but is not enough to win the first place. To find a solution to the problem, perform a
reverse check.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 116
Page 116
 Case 8: The DPA Throughput Is Lower Than Those of Peer Vendors (Continued)

Step 3: Perform a reverse check and take measures.

Perform a reverse check to analyze resources, traffic models, and drive test data. The check results are as
follows:

Standard Action Check Result Executed Action

Congestion occurs in ATM Perform IP-based reconstruction for the

Action 6: Analyze resources. transmission resources on the Iub ATM transmission bandwidth and optimize
interface and uplink power resources. RTWP for uplink power resources.
Action 7: Analyze traffic models. OK
Action 8: Analyze coverage. OK
Action 9: Analyze the traced data OK
about the single user throughput.
Action 10: Analyze the traced N/A
data about the single user delay.

Action 6: Analyze resources.

OMStar cannot be used to evaluate problems in RNC R11. Collect the statistics of ATM bandwidth usage on
the Iub interface and uplink RTWP manually.
In regard to the ATM bandwidth usage on the Iub interface, 42% of all 188 NodeBs managed by the RNC, that
is, 79 NodeBs, have a high bandwidth usage or have only two E1s.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 117

Page 117
 Case 8: The DPA Throughput Is Lower Than Those of Peer Vendors (Continued)

Uplink RTWP:
In busy hours, the RTWP is high in 11.3% of cells.

After field engineers execute Action 6, the throughput detected through a drive test
increases by 18%, which is higher than those of peer vendors.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 118

Page 118
 Case 8: The DPA Throughput Is Lower Than Those of Peer Vendors (Continued)

Step 4: Check whether the problem is solved.

After the forward check and reverse check are performed, the throughput increases by 38%,
which is higher than those of peer vendors. The problem is solved. The following describes the
increase of throughput in various phases:
Action Throughput Throughput
Standard Action Execution Before Actions After Actions
Date Are Executed Are Executed
Trend of throughput Action 1: Check abnormal
increase operations.

Action 2: Check alarms.

Action 3: Check early
warnings. 2012-01-
2.4 Mbit/s 2.88 Mbit/s
10
Action 4: Check
parameters.
Action 5: Check
transmission
configurations.
Action 6: Analyze
resources.
Action 7: Analyze traffic
models.
Action 8: Analyze
coverage.
Action 9: Analyze L3 2012-01-
signaling. 2.88 Mbit/s 3.4 Mbit/s
13
Action 9: Analyze L1
signaling.
Action 9: Analyze L2
signaling.
Action 9: Analyze
application layer signaling.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 119

Page 119
 Case 8-2 The R99 PS Service Volume Drops at Site W

Problem description: The R99 PS service volume drops at site W.

Problem analysis:
Step 1: Confirm and classify the problem.
The problem is confirmed to be an RNC-level problem. Starting from December 15th, the R99 PS service volume drops,
but the total service volume has no significant changes. Step 2: Perform a forward check.
Standard Action Check Result Executed Action
Action 1: Check abnormal operations. OK
Action 2: Check alarms. OK
Action 3: Check early warnings. OK
Action 4: Check parameters. OK
Action 5: Check transmission OK
configurations.

Step 3: Perform a reverse check and take measures.

Perform a reverse check to analyze resources, traffic models, and drive test data. The check results are as follows:

Standard Action Check Result Executed Action

Before the problem occurs, the R99

The traffic is transferred normally, and no
Action 6: Analyze resources. service volume is high and code words are
actions need to be performed.
congested.

The R99 service volume drops, and the The traffic is transferred normally, and no
Action 7: Analyze traffic models.
HSDPA service rises. actions are required.
Action 8: Analyze coverage. N/A
Action 9: Analyze the traced data about the single
N/A
user throughput.
Action 10: Analyze the traced data about the single
N/A
user delay.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 120

Page 120
 Case 8-3 The R99 PS Service Volume Rises After Upgrades at Site F

Problem description: The R99 PS service volume rises after upgrades at site F.
Problem analysis
Step 1: Confirm and classify the problem.
The problem is confirmed to be an RNC-level problem. After upgrades, the downlink R99 PS traffic rises drastically.

Step 3: Perform a reverse check and take measures.

Standard Action Check Result Executed Action
Action 1: Check abnormal
OK
operations.
Action 2: Check alarms. OK
The Release Notes of the corresponding Analyze the traffic statistics and
version is checked. In the Release Notes, an configurations to check whether
Action 3: Check early warnings.
algorithm has been changed, which is related the throughput has been
to this problem. affected.
Action 4: Check parameters. OK
Action 5: Check transmission
OK
configurations.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 121

Page 121
 Case 8-3 The R99 PS Service Volume Drops After Upgrades at Site F
(Continued)
Step 3: Perform a reverse check and take measures.
Perform a reverse check to analyze resources, traffic models, and drive test data. The check results are as follows:

Standard Action Check Result Executed Action

Action 6: Analyze resources. OK OK

The number of R99 PS users is

large, and especially DL 128 Kbit/s,
Action 7: Analyze traffic models. Analyze the detailed causes.
DL 64 Kbit/s, and DL 384 Kbit/s
users.
Action 8: Analyze coverage. N/A
Action 9: Analyze the traced data about the
N/A
single user throughput.
Action 10: Analyze the traced data about the
N/A
single user delay.
CMP_RAB_DRD_ROLLBACK_PUNI
SH_SWITCH is set to off. This
means that for DRD failures caused
by any kinds of Uu interface failures,
a permanent punishment is carried.
Services of some users remain in
R99 permanently, especially R99
384k services of high data rates. This
increases the downlink traffic for R99
PS services.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 122

Page 122
 Contents
1 Methods for Evaluating HSPA Data Transmission Problems
2 Classification and Clarification of HSPA Data Transmission Problems
3 Factors Affecting HSPA Data Transmission

4 Solutions to HSPA Data Transmission Problems

 HSPA Troubleshooting Procedure
 Problem Confirmation
 Forward Check and Measures
 Reverse Check and Measures
 Analysis on Throughput Problems Detected Through Traffic Measurement and
Measures
 Analysis on Throughput Problems Detected Through Drive Test and Measures
 Analysis on Problems Collected from Complaints and Measures
 Analysis on Ping Delay Problems and Measures

5 Deliverable Example and Template

6 Appendix: Introduction to HSPA Data Transmission Troubleshooting Tools

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 123

Page 123
 Analysis on Problems Collected from Complaints and Measures

Analysis on problems collected from complaints is the same as that on

throughput problems detected through traffic measurement. First analyze the
problems through traffic measurement and try to solve the problems. If the
problems persist, analyze the throughput rate through drive test data.

The items to be checked in forward check are the same as those for
throughput problems detected through traffic measurement and through a
drive test. In the reverse check, you need to check the resources, coverage,
and traffic models. If a drive test is required, analyze signaling at L1, L2, L3,
and application layer.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 124

Page 124
 Contents
1 Methods for Evaluating HSPA Data Transmission Problems
2 Classification and Clarification of HSPA Data Transmission Problems
3 Factors Affecting HSPA Data Transmission

4 Solutions to HSPA Data Transmission Problems

 HSPA Troubleshooting Procedure
 Problem Confirmation
 Forward Check and Measures
 Reverse Check and Measures
 Analysis on Throughput Problems Detected Through Traffic Measurement and
Measures
 Analysis on Throughput Problems Detected Through Drive Test and Measures
 Analysis on Problems Collected from Complaints and Measures
 Analysis on Ping Delay Problems and Measures

5 Deliverable Example and Template

6 Appendix: Introduction to HSPA Data Transmission Troubleshooting Tools

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 125

Page 125
 Confirming Ping Delay Problems
Output Solution
UE tracing or
ping test results
Input Perform a
1. Size of ping
UE forward
packets and server
check.
tracing address
2. Type of service
Analysis rule: provided based on
tool channel for the ping
ping test rules, which are operation
specified by the customer or a 3. Intermediate
third party equipment in the ping
operation (including
transmission
equipment and
network)

Case: For details about the case, see Case 9.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 126

Page 126
 Reverse Analysis on Ping Delay Problems (Action 10: Analyze
General Delay)

Input Output Solution

RNC CDT, and packet 1. Check results
capture results on the FMA of packet loss
According to
UE or router the check result
on devices
above or below
of the general

1. Enable RNC CDT by using FMA and

TranEx RNC delay, check
the nodes
2. Check results
choose Tool > User plain extraction to pert of performance where the
obtain the Pcap file in the same
directory. of servers and delay is high.
2. Capture packets on the UE or a laptop
router above the RNC. computers

Analysis rules:
1. Check the analysis results of
packet loss in the uplink and
delay on the RNC.
If packet loss occurs in the
uplink, packets are lost on
routers above the RNC.
2. The general delay measured
is around 100 ms. If the delay is
higher than 200 ms and
fluctuates greatly, an exception
occurs.

Note: Actions 1 to 8 for ping delay problems are basically the same as those for the throughput problems detected through
traffic measurement except the sites and cells to be analyzed are different. In addition, the forward check covers the check
on servers, laptop computers, and test mode, which are included in the HSPA parameter checklist.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 127

Page 127
 Reverse Analysis on Ping Delay Problems (Action 10: Analyze L3
Signaling)

Output Solution
RNC CDT Input
1. Whether
FMA RB
reassignment
Analysis rules: is performed 1. Change the test
1. Check whether RB place.
2. Bearer
reassignment is performed during 2. Modify the
channel
the ping test. setting of the
2. Check whether the channel channel parameter.
where ping packets are
transmitted is the correct channel
to be tested during the ping test.

Case 9: The ping delay does not meet the requirements because the state transition
policy is unreasonable in office M.
Problem description: The ping delay is 191 ms before the swap and 274 ms after the
swap, which does not meet the requirements and affects the swap and acceptance.
Root cause: The state transition policy is different from that of Ericsson. The DCH/HSDPA
state threshold is high. A 32-byte ping packet can be carried on only the FACH. The
normal delay on the FACH is around 260 ms.
Solution: Reduce the DCH/HSDPA state threshold. UEs still transit from the DCH to the
FACH state from time to time. After the H2F optimization function is enabled, the problem
is solved.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 128

Page 128
 Reverse Analysis on Ping Delay Problems (Action 10: Analyze the Uu
Interface)

Output
Probe/QXDM UE log
Input Solution
NodeB CDT
1. Whether
the PDU is
Probe sent as 1. Change the test
FMA expected place.
Analysis rules: 2. Packet 2. Modify the
1. According to the size of ping retransmission setting of the
packets, check whether the PDU rate in the channel parameter.
is sent as expected. uplink and
2. Check the retransmission rate downlink
of ping packets on the Uu
interface.

Case 10: The Ping Delay in Office R Is High (Next Page)

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 129

Page 129
 Case 10: The Ping Delay in Office R Is High (Caused by the Uu
Interface)
Problem description: Test shows that the ping delay in office R is high.
Problem analysis:

Step 1: Confirm and classify the problem.

Confirm that the problem is a ping delay problem that occurs at only one site.
Step 2: Perform a forward check.
Standard Action Check Result Executed Action

Action 1: Check abnormal operations. OK

Action 2: Check alarms. OK
Action 3: Check early warnings. OK
Action 4: Check parameters. OK
Action 5: Check transmission configurations. OK

Step 3: Perform a reverse check.

Standard Action Check Result Executed Action
Action 6: Analyze resources. OK
Action 7: Analyze traffic models. OK
Action 8: Analyze coverage. OK
Action 9: Analyze the traced data about the single N/A
user throughput.
Action 10: Analyze the traced data about the single The delay on the air interface is Further determine why the
user delay. high. delay is high.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 130

Page 130
 Case 10: The Ping Delay in Office R Is High (Continued)

Action 10: Analyze the traced data about the single user delay.
Analysis on the uplink CDT data shows that the uplink retransmission rate is high. It is
confirmed that the problem is caused by software defects.

Field engineers confirm that the delay is introduced on the Uu interface, and R&D
engineers analyze why the delay is introduced.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 131

Page 131
 Reverse Analysis on Ping Delay Problems (Action 9: Analyze the Iub
Interface)

Output Solution
Transmission delay Input
on the Iub interface
RNC CDT
FMA Transmission Check the
delay on the transmission
Iub interface configuration.
Analysis rules: Packet loss
1. Compare the delay data with rate at L2
the baseline value to check
whether the delay variation and
high delay exist.
2. Check whether packet loss
occurs at L2.

Case 11: The Ping Delay in Office C Is High (Next Page)

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 132

Page 132
 Case 11: The Ping Delay in Office C Is High (The Transmission
Equipment Fails)
Problem description: Timeout occurs when a ping command is sent from the RNC to a NodeB.
Problem analysis:
Step 1: Confirm and classify the problem.
Confirm that the problem is a ping delay problem that occurs at only one site.
Step 2: Perform a forward check.
Standard Action Check Result Executed Action

Action 1: Check abnormal operations. OK

The alarm (ALM-21581) indicating a path Clear the alarm according to
Action 2: Check alarms. fault is reported. the alarm help.
Action 3: Check early warnings. OK

Action 4: Check parameters. OK

Action 5: Check transmission OK

configurations.
Action 2: Perform analysis.
According to the alarm help, the alarm (ALM-21581) is reported possibly because the IP path ping test fails or the IP path is not
configured with a port (this cause is excluded after the configuration is checked).
1. Ping the NodeB from the RNC and send 100 ping packets continuously.
2. After the ping operation is complete, stop capturing packets and compare the captured packets. Analyze the number of ping
request packets sent by the RNC. The analysis shows that the RNC successfully sends 100 ping request packets but receives
less than 100 reply packets.
3. Analyze the packets captured on the NodeB. The analysis shows that the NodeB receives 100 ping request packets and returns
100 reply packets.
4. Analyze the packets captured on transmission equipment. The analysis shows that the transmission equipment sends 100 Ping
request packets but receives less than 100 reply packets and the number of reply packets received by the transmission equipment
is the same as that received by the RNC.
The preceding analysis indicates that packet loss occurs on the transmission network between transmission equipment and the
NodeB.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 133

Page 133
 Contents
1 Methods for Evaluating HSPA Data Transmission Problems

2 Classification and Clarification of HSPA Data Transmission Problems

3 Factors Affecting HSPA Data Transmission

4 Solutions to HSPA Data Transmission Problems

5 Deliverable Example and Template

6 Appendix: Introduction to HSPA Data Transmission Troubleshooting Tools

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 134

Page 134
 Deliverable Example and Template
1. Output an analysis report after analysis is completed according to standard actions. For details about
the report template, see the Template for the Analysis Report on HSPA Data Transmission Problems
in XX Project. The appendix provides an example of the analysis report based on case 12.

Analysis Report on HSPA Data Transmission Problems in the XX Project.rar

2. This slide describes the general analysis procedure. For details, see the HSPA Data
Transmission Troubleshooting Guide on the support.huawei.com website.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 135

Page 135
 Case 12: The Throughput Detected Through a Drive Test in Office M Does Not
Meet the Requirement (Caused by Forward and Reverse Factors)
Problem description: After the equipment of Ericsson is swapped in office M, the HSDPA throughput detected through a
drive test does not meet the requirement.
Problem analysis:
Step 1: Confirm and classify the problem.
Confirm that the problem is a throughput problem detected through a drive test and that field engineers perform a drive test
on more than 100 swapped sites managed by the RNC.
Step 2: Perform a forward check.
Standard Action Check Result Executed Action

Action 1: Check abnormal operations. OK

Action 2: Check alarms. OK
Preventive measures provided by the early warning for Take preventive
Action 3: Check early warnings. the HSUPA 2 ms policy are not executed. measures.
The values of the four parameters (RSCALLOCM, Modify parameter
Action 4: Check parameters. PWRMGN, MXPWRPHUSR, and settings.
CQIADJALGOFCON) differ from the baseline values.
Action 5: Check transmission OK
configurations.
SET MACHSPARA (field configuration)
Baseline
LOCELL=7328
Comparative RSCALLOCM=CODE_PRI POWERCODE_BAL
analysis on PWRMGN=20 PWRMGN=5
parameters
MXPWRPHUSR=70 MXPWRPHUSR=100
Recommendation in the drive test scenario:
CQIADJALGOFNONCON=NO_CQI_ADJ
CQIADJALGOFNONCON=CQI_ADJ_BY_DYN_BLER

After the parameters are set to baseline values, the throughput increases by 3% to 4%, which is
still 20 Kbit/s lower than the throughput before swap. Then perform a reverse analysis.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 136
Page 136
 Case 12: The Throughput Detected Through a Drive Test in Office M Does Not
Meet the Requirement (Continued)

Step 3: Perform a reverse check and take measures.

Perform a reverse check to analyze resources, traffic models, and drive test data. The check results are
as follows:

Standard Action Check Result Executed Action

Congestion occurs in uplink 1. Modify the high RTWP cell threshold to 85%.
Action 6: Analyze power and downlink power. 2. Modify the maximum transmit power in the downlink
resources. cells where congestion occurs from 30 W to 40 W.
The traffic volume increases by Optimize the HSUPA policy (long-term policy) and
Action 7: Analyze traffic 1.8 times compared with that expand dual carriers.
models. before swap.
Action 8: Analyze OK
coverage.
Action 9: Analyze the SCCH scheduling is less likely 1. Enable the TPE function.
traced data about the to be performed and the BLER 2. Enable dynamic BLER CQI correction.
single user throughput. is high.
Action 10: Analyze the N/A
traced data about the
single user delay.

Action 6: Analyze resources.

The analysis report based on the evaluation by using OMStar shows that severe uplink and downlink
power congestion occurs.
ULPower DLPower ULCE Cong DLCE Cong CODE Cong DLIUBBand ULIUBBand
RNCID
Cong Times Cong Times Times Times Times Cong Times Cong Times
11 11810 1257 477 0 328 5 2

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 137

Page 137
 Case 12: The Throughput Detected Through a Drive Test in Office M Does Not
Meet the Requirement (Continued)
Action 7: Analyze traffic models.
For a swapped network, the data before swap needs to be obtained from the operator and the data after swap can be
obtained from the traffic measurement data analyzed by using OMStar.

Analyze the distribution of online users by using the OMStar. The ratio of uplink 2 ms users to uplink 10 ms users is about
7:3. Most terminals support the 2 ms policy. The HSUPA 2 ms policy configured on the live network does not comply with
the baseline configuration and needs to be optimized.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 138

Page 138
 Case 12: The Throughput Detected Through a Drive Test in Office M
Does Not Meet the Requirement (Continued)
Action 9: Analyze the traced data about the single user throughput.
1. Scheduling probability: The scheduling probability of Ericsson (55%) is 15% higher than that of Huawei (40%) because
upper-layer data cannot be transmitted. The TPE function helps improve the data transmission efficiency at the TCP
layer and improves the scheduling probability at the TCP layer.
2. BLER: The BLER of Huawei (40%) is 27% higher than that of Ericsson (13%). In this case, enable dynamic BLER CQI
correction to reduce the BLER.

Scheduling probability 55% before swap Scheduling probability 40% after swap

BLER 13% before swap BLER 40% after swap

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 139

Page 139
 Case 12: The Throughput Detected Through a Drive Test in Office M
Does Not Meet the Requirement (Continued)
Step 4: Check whether the problem is solved.
After the measures for reverse check are taken, the throughput detected through a drive test increases by 10%, which is
higher than that before swap. The problem is solved.
Action Throughput Throughput
Standard Action Execution Before Actions After Actions
Date Are Executed Are Executed

Action 1: Check
abnormal operations.

Action 2: Check alarms.

Action 3: Check early
warnings. 2012-5-21 689.1 Kbit/s 707.4 Kbit/s
Action 4: Check
parameters.
Action 5: Check
transmission
configurations.
Action 6: Analyze
resources.

Action 7: Analyze traffic

models.
Action 8: Analyze
coverage. 2012-5-22 707.4 Kbit/s 776.5 Kbit/s
Action 9: Analyze the
traced data about the
single user throughput.
Action 10: Analyze the
traced data about the
single user delay.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 140

Page 140
 Contents
1 Methods for Evaluating HSPA Data Transmission Problems

2 Classification and Clarification of HSPA Data Transmission Problems

3 Factors Affecting HSPA Data Transmission

4 Solutions to HSPA Data Transmission Problems

5 Deliverable Example and Template

6 Appendix: Introduction to HSPA Data Transmission Troubleshooting Tools

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 141

Page 141
 Analysis Tools for HSPA Data Transmission Problems

Problem
Tool Name Data Source
Type
RNC script, RNC traffic statistics, RNC
OMStar network evaluation tool
license, and NodeB license
RNC script, RNC traffic statistics,
Network- OMStar network optimization tool NodeB license, and NodeB traffic
level statistics
performance
OMStar SOP tool RNC script and alarm logs
Alarm logs, operation logs, PCHR, and
FMA
RNC traffic statistics
WIRESHARK TCP/IP packet capture
Data
transmission TranExpert TCP/IP packet capture
for a single QXDM UE QXDM log
user
PROBE UE PROBE log

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 142

Page 142
 Comparing RNC Parameters by Using FMA
Step 2: Select the old
script. Step 4: Select All
Paras.
Step 1: Choose MML
Compare.

Step 3: Select the new

Step 5: Click
script.
Run.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 143

Page 143
 Converting Configuration Files of NodeB to MML Files in Batches by
Using FMA

Step 1: Choose NodeB XLM to MML.

Step 2: Select Normal Format or

Entire Format.

Step 3: Click Run.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 144

Page 144
 OMStar Network Evaluation Tool

Step 2: Export the RNC

configuration file, NodeB license
file, RNC license file, and original Step 3: Select the items to be
traffic measurement file of RNC. evaluated and export a report.

Step 1: Select NetworkAudit.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 145
Page 145
 RNC CDT Analysis (HSPA) Using FMA
PS L2 FP packet statistical analysis (Start the FMA, choose Extract Msg Para > PS L2 RB statistical analysis (Start the FMA, choose Extract Msg Para
L2_DATA_FWD from the short-cut menu.) > L2_DATA_FWD from the short-cut menu.)
 Select the Harqfailure option to collect statistics of uplink air interface retransmission  Select the DLRetranRate option to check the retransmission rate at
failures, determine the quality of uplink air interface, and accumulate values. the RLC layer.
 Select options related to TNLIub to collect statistics of packet loss and delay in the  Select options related to Sufilist to check packet loss at the RLC
R99 uplink or UPA uplink. layer. If Sufilist is sent, packets are lost continuously at the RLC
 Select the DschAlloc option to see the capacity allocation frame of the NodeB and layer and retransmission is required.
capacity request frames sent by the RNC.  Select the DownlinkWindowsfullnum option to determine whether
packets are blocked and cannot be sent in the RLC sending window on
the RNC side.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 146

Page 146
 NodeB CDT Analysis (HSDPA) Using FMA
HSDPA User Enhanced Schedule Data: user enhancement analysis by using the statistics function of FMA
 It can be used to check the reported CQI, sent CQI, power resources, BLER, and code resource usage.
HSDPA User Flow Ctrl Performance Data flow control analysis
 It can be used to check real-time air interface rate Vout and queue data status ucTmStatus and report the original CQI and
bandwidth allocation information.
Trans Iub BW REQ transmission printing
 It can be used to check packet loss or delay on the Iub interface.
Choose the statistic function from the short-cut
menu

Choose the information extraction

function from the short-cut menu,
and select the HSDPA User
Enhanced Schedule Data
message to be analyzed.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 147

Page 147
 NodeB CDT (HSUPA) Using FMA
HSUPA Rlenhance Info Statistic user enhancement
 It is used to check the TB size, uplink cell load, scheduling SG and result, scheduling reason, UE TEBS, Hi, and Happy bit.

Choose the information extraction

function from the short-cut menu
and select the HSUPA Rlenhance
Info Statistic message to be
analyzed.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 148

Page 148
 TranExpert

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 149

Page 149
 TranExpert (Continued)

After TCP Analysis is

performed, double-
click Lost Analysis
and Timedelay
Analysis to view the
analysis results of
packet loss and delay.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 150

Page 150
 Contents
 GSM PS Service
 UMTS PS Service
 LTE PS Service

Page151

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 151

 Contents
 LTE PS Service(Drive Test)
 LTE PS Service(Traffic
Statistics)
 LTE PS Service(Ping Delay)

Page152

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 152

 Contents
1 Classification and Evaluation Methods of DT Problems
2 Factors and Required Actions
Step 1: Problem Acknowledgement and Segmented Isolation
Action 1: Test Specifications Checks
Action 2: Problem Scope Confirmation and Segmented Isolation
Step 2: Basic Element Checks
Action 3: External Event and Historical Operation Checks
Action 4: Fault and Alarm Checks
Action 5: Known Issue Checks
Action 6: Parameter Checks
Step 3: Reasoning and Analysis
Action 7: Air Interface and Coverage Analysis
Action 8: Coding Efficiency Analysis
Action 9: Resource Analysis
Action 10: Channel and Interference Analysis
Action 11: Handover Analysis
Action 12: Transmission and TCP Analysis

3 Appendix: Data Collection Guidance

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 153
Page 153
 Abstract and Overview
Based on actual DT processes, this document provides specific operations corresponding to DT tool-based test
conduction, data analysis, and result dissection.
This document aims to solve the following problems:
 Low throughput during fixed-point tests or DTs
 Low DT throughput

Actions 3 to 6:
Air interface
Checking basic
differences
elements

Coding differences

Resource
differences
Actions 7 to 12:
Use the Assistant
Use the Probe and Isolate causes for Channel and Analyzing the
Extend for data
Optis for DTs. low throughput. interference corresponding
analysis.
differences causes

Handover
differences

Action 1: Checking Action 2: Isolating

test specifications problems Transmission and
TCP analysis

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 154

Page 154
 Overview
 Locating methods and procedure of low DT throughput

Basic element checks (mandatory)

Action 3: Checking external events Route

and historical operations
cause
Action 4: Checking faults and alarms
Problem Parameter
acknowledgement and Action 5: Checking known issues
segmented analysis Analysis
method Action 6: Checking parameters Appendix:
(mandatory) Interference Data Colle
and
ction Guid
Symptom

policy Reasoning and analysis (from a ance

Action 1: C Action 2: I clue) Coverage
hecking te solating pr
st specific oblems Action 7: Analyzing air interface and ……
ations coverage Appendix:
Typical Ca
Action 8: Analyzing coding efficiency ses
Product
Action 9: Analyzing resources
quality

Action 10: Checking channels and in Capacity

terference

Action 11: Analyzing handovers

Action 12: Analyzing transmission a

nd TCP

The actions provided in X solutions are formulated and methodically organized based on cases
and issue characteristics identification by following the principle for minimal costs.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 155

Page 155
 Factors in LTE Data Transmission
Factor Root Cause
Radio interface 1. Incorrect
channel: parameter Factor Root Cause Factor Root Cause
1. RSRP/SINR setting Bearer 1. Parameter 1. NE flow 1. TCP
2. Air interface 2. Limited traffic network setting control parameter
coding capacity channel: 2. Capacity or 2. Public setting
(MCS/MIMO/IBLER/ 3. Poor coverage 1. Bandwidth capability network 2. Capacity
Rank) 4. External restriction restriction bandwidth restriction
3. Radio interface interference 2. Large delay 3. Transmissio restriction
resource 5. Abnormal and jitter n quality
(Grant/RB) handover 3. Packet loss issue
4. Radio interface 6. Version issue and packet
delay disorder
5. QoS configuration
(AMBR)

Factor Root Cause

Factor Root Cause
1. UE capability 1. Hardware
1. Registration 1. Parameter
2. PC performan Factor Root Cause Factor Root Cause
configuration setting
performance ce
1. eNodeB rate 1. Parameter 2. Rate 2. Device fault
1. Server 1. Hardware
3. TCP setting 2. Parameter
restriction setting restriction 3. Version quality
capability performance
4. Software setting
2. eNodeB 2. Incorrect 3. Packet issue
2. TCP 2. Parameter
configuration 3. Software
processing engineering disorder 4. Service shaping
paramete setting
(FTP restriction
capability configuratio configuration
r setting
configuration,
3. eNodeB n (CAR) (Note 1)
3. Software
firewall)
feature 3. eNodeB setting
restriction fault
4. Version
To optimize performance, identifyquality
key E2Eissue
factors in and possible causes of PS data transmission problems.
Note 1: [CAR function] In general, CAR is configured on the UGW or a device at the interface of an external carrier network to categorize packets and control IP traffic so that IP packets enter and leave
the network at a specified rate. This helps a carrier better operate the network and provide guaranteed QoS.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 156

 Integrally Improving Data Transmission Performance
Ensure that the network is in the optimal status by performing the following
operations before analyzing data transmission problems:
Check test specifications.
Check whether key alarms are cleared.
Check whether optimized parameters are delivered.
Action 1: Test Specifications Checks Adopt a correct
measurement method.
Check whether the test tool and method meet requirements.

Action 3: External Event and Historical Operation Checks

Check for key alarms during tests and evaluate impact of
known problems. Eliminate negative
Action 4: Fault and Alarm Checks impact.

Check alarms of key faults and evaluate the fault impact.

Action 5: Known Issue Checks

Evaluate impacts of known issues.

Optimize parameter
Action 6: Parameter Checks settings.
Determine whether to deliver optimized parameters for basic
performance and comparison tests.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 157

 Action 1: Test Specifications Checks
 There is no restriction on performing this action. Checking data validity in the first place helps avoid a
waste of time on analyzing invalid data.
 For checking items involved in action 1, see section 2.1 Action 1 – Checking Test Specifications in
Attachment 1 – PS Data Transmission Optimization Guide in the LTE Network (Drive Tests).
The test PC must be equipped with a GEC, and the Ensure that the registered AMBR
hard disk protection function must be disabled. complies with the requirement that
It is recommended that the FileZlilla be installed the uplink throughput reaches 50
on both tested PC and the server. Other software eNodeB Mbit/s and the downlink throughput
is not recommended. reaches 150 Mbit/s.
The XCAL, QXDM, or Serv-U is not Use a postpaid card instead of a
recommended for testing peak throughput. You prepaid card for the test.
are advised to use Prboe3.6 or later for DTs.
EPC
PC UE

HiSilicon chips greatly differ from Check whether the eNodeB

is installed with a tower-
QualComm chips. Either one of them
mounted amplifier and uses
can be used for tests. an antenna with four or
The same test UE must be used before eight RX channels.
and after the network swapping,
comparison, and upgrades.

You are advised to select points with SINRs greater than 24 to test whether the peak throughput can be achieved at such points.
This is the most effective way to exclude causes for low DT throughput caused by PCs, terminals, and SIM cards.
You are advised to conduct a DT during off-peak hours to reduce background users' impact on DT users. During peak hours,
background users occupy more scheduling resources. As a result, interference from neighboring cells increases.
Air interface conditions are affected by test routes and direction. In addition, vehicle speed may also affect air interface conditions
due to frequency deviation effect. Therefore, the external environment should be identical.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 158

Page 158
 Action 2: Problem Scope Confirmation and
Segmented Isolation
 Perform action 2 after data validity checks are complete. Segment and isolate the problem to detect root causes.
 For how to segment and isolate the problem, see section 2.2 Action 2 – Identifying the Fault Scope and Demarcating
Faults in Attachment 1 – X Solutions for PS Data Transmission Optimization Guide in the LTE Network (Drive Tests) .
Analyze the symptoms and characteristics of the problem in terms of the following aspects:
 Geographical characteristics: Identify affected physical NEs, and determine whether this problem occurs on the
entire network or in TopN cells.
 Cause dissection and associated analysis: Match the analysis results with the problem symptoms to guide
subsequent analysis.
It is recommended that you use the Assistant Extend to process the data. For details about the Assistant Extend, see section
2.2 in Attachment 1 – PS Data Transmission Optimization Guide in the LTE Network (Drive Tests).
Difficult to handle problems due to a Files are combined. Multiple files can be
large number of files analyzed at a time.
Difficult to calculate user-defined More than ten calculation methods of user-
counters such as the overlap ratio defined counters are provided to comply
coverage with all the requirements.
Difficult to find TopN cells among a Counters are measured by cell. TopN cells
large number of cells can be easily obtained pertaining to specific
counters.
Difficult to evaluate problems due to a Handover data can be separately exported by
large number of handovers one click, facilitating analysis.

The Assistant Extend automatically draws the

Difficult to analyze problems due to corresponding diagrams so that you can
massive data directly observe the data change trend.

You can download the Assistant Extend from the following URL:
http://3ms.huawei.com/hi/group/9261/thread_4222425.html?mapId=3417611&for_statistic_from=all_group_forum

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 159

Page 159
 Radio environment and product capability
comprehensively reflecting the throughput
 Factors in the
throughput Sinr VS DL Throughput Pathloss VS UL Throughtput
Number of
transmitted bits Product 120000 60000
per RB under capability
100000 50000
the same air
interface 80000 40000
conditions DT 60000 30000
throug
40000 20000
hput
Radio Number of RBs 20000 10000
environment Bandwidth and scheduling 0 0
SINRs in the
times -10 -5 0 5 10 15 20 25 30 35 70 80 90 100 110 120 130
PS domain
The DT throughput is affected by radio environment, product capabilities, and bandwidth

 When the bandwidth keeps unchanged, the throughput is mainly affected by radio environment and product capabilities.
SINR_CDF SINR vs DL RLC DL RLC Throughput_CDF
100.00% 100.00%
35000 Throughput
90.00% 90.00%
30000

+
80.00% 80.00%

=
70.00% 25000 70.00%
60.00% 20000 60.00%
50.00% 15000 50.00%
40.00% 40.00%
10000
30.00% 30.00%
20.00% 5000 20.00%
10.00% 0 10.00%
0.00% -10 -5 0 5 10 15 20 25 30 0.00%
-10 -5 0 5 10 15 20 25 30
Affecting factors of the throughput curve: 0 10000 20000 30000
Affecting factors of the radio environment Devices: repeaters + channels + alarms + data transmission Throughput is affected by both radio
(SINR): + a server + UE capabilities environment and product capabilities.
Coverage: low SINR due to coverage restriction Power configuration (Pa, Pb) Therefore, throughput can be optimized
Interference: intra-RAT and inter-RAT interference Optimization on parameters and features (product capability) from these two aspects.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 160

 Graphical Isolation Method (Downlink)
Isolation of coding-efficiency problems
Isolation of air-interface problems
The MSCs in the blue curve are obviously
The RSRPs in the blue curve are better. lower.
Isolation of scheduling resources

RB resources in both curves are the

Rank 2 proportions in the blue curve are
same.
obviously lower.

The SINRs in the blue curve are obviously

higher.

All the IBLERs in the blue curve are smaller

than 10%, which are normal.

The Grant values in the red curve are lower,

The SINRs in the blue curve are higher when the and the values are centralized to 750. In this
RSRPs in both curves are the same. case, perform a check for low Grant
For the red curve, perform a check for low SINRs by
according to action 5.
following the instructions of action 3. The low rank 2 proportion and low MCSs in
the blue curve result in low spectral
efficiency. In this case, perform a check
according to action 4.
Remarks: These diagrams are
drawn by the Assistant Extend.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 161

Page 161
 Action 3: External Event and Historical Operation Checks
 Procedure Introduction:
 Based on problem scenarios, use different methods to check for operations and external events that affect the service rate.
 For performance deterioration problems, perform this step first to determine the correlation between the external events/historical operations and the
deterioration events in terms of time/scope.
 For multiple faulty eNodeBs, focus on operations that affect network performance, such as EPC or transmission operations. For eNodeB-level operations,
select top 10 cells for analysis.
 Triggering Condition: Mandatory. Focus on scenarios in which DT results vary greatly before and after the swapping and upgrade.
 Operation Method: For details about how to use the FMA, see the FMA help.
Data Source Tool Analysis Method and Deliverable Closed-Loop Action
Analysis method:
eNodeB operation
1. For the performance deterioration in the tests before and after the swapping and
records and original
upgrade, use the FMA to analyze operation logs during the period between the Determine whether the
traffic statistics (for a
two tests. operations can be rolled
cluster problem, select
2. If there are multiple faulty eNodeBs, further check whether suspected abnormal back. If yes, observe
top 10 problematic FMA
operations have common characteristics. whether the counters
eNodeBs; for a top N cell
Deliverables: are improved after the
problem, select top N
3. Lists operation records and analysis results of the impact on the rate. rollback.
eNodeBs serving the top
4. Records the operations of which the impact cannot be determined in the analysis
Common
cells) external events that affectreport.
the service rate:
Object Event or Operation Impact
Modify or add configurations, such as the rate
The rate may be limited. For details, see the parameter checks (for non-
EPC limit policy for a charging system, DPI function,
eNodeBs) part in slide 85.
and parameters related to dedicated bearers.
Transmission changes may trigger changes in transmission bandwidth or
Perform the transmission reconfiguration or
Transmission transmission efficiency, which may result in KPI changes of the eNodeB. For
transmission reconstruction.
details, see the parameter checks (for non-eNodeBs).
1. Modify core parameters related to the service
1. For detailed parameter modification, see the parameter checks.
rate of the eNodeB.
eNodeB 2. eNodeB addition or deletion may lead to changes on cell edge users
2. Add or delete an eNodeB surrounding the top
(CEUs), which further affects cell traffic and rate.
N eNodeBs.
Upgrade the UE version, deploy an external
Terminal performance may be limited, and compatibility problems may occur,
UE antenna, use the USB extension cable, and test
such as KPI deterioration related to the network rate.
the SIM card-based rate limit policy.
Check whether there are major holidays or rallies Traffic volume increases abruptly, which may result in device overload. In
Event
in DT areas. addition, this may deteriorate KPIs related to data transmission of the eNodeB.

Focus on external events that are not listed in this table but chronologically correlated with the KPI deterioration. In practices, a brief understanding of the
event, rather than event digging-out, is enough for analysis.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 162

 Action 4: Alarm Checks
 Procedure Introduction:
 Check whether there are active alarms or faults that affect the service rate. For alarms that have a significant impact on the service rate,
clear them first. For alarms whose impact is unknown, you are advised to further analyze whether they are the root cause of service rate
exceptions. Then, determine whether to clear the alarms.
 Analyze whether the alarm reporting time and scope match those of the service rate exceptions. For example, analyze whether the service
rate is abnormal in all sectors under the eNodeB experiencing an alarm that affects the whole eNodeB; analyze whether the rate is
abnormal in other sections under the eNodeB experiencing an alarm that affects one of the sectors under the eNodeB.
 For rate deterioration in top N eNodeBs, check whether new alarms are reported on surrounding eNodeBs during the deterioration period.
The number of CEUs in the surrounding eNodeBs increases due to site faults.
 Triggering Condition: Mandatory
 Operation Method: For detailed analysis on alarms and faults, see the FMA help.

Data Source Tool Analysis Method and Deliverable Closed-Loop Action

Analysis method:
1. Use the U2000 to analyze active alarms of the
NE alarm list on the problematic eNodeBs, or export alarm lists to an Excel
U2000+cell alarm file and then use the Excel to analyze the alarms. 1. Clear alarms in sequence
logs+internal fault 2. Use the FMA to query active alarms of the top N based on their impact on the
logs (for a cluster problematic eNodeBs, and analyze their impact on the service rate and confirm
U2000
problem, select top service rate. whether the problem is
, FMA
10 problematic 3. If there are multiple faulty eNodeBs, further check resolved.
eNodeBs; for a top N whether the alarms have common characteristics. 2. If some alarms cannot be
cell problem, select Note: In the event of deterioration, pay special attention to cleared, report the reason
top N eNodeBs alarms whose occurrence time and scope match those of and impact analysis.
serving the top cells) the deterioration.
Deliverables: Alarm and fault analysis list based on
the analysis method.
 Alarm checks on the non-eNodeB side: Consult customers to confirm whether transmission/ECP devices work properly.
 For common alarms that affect the service rate on the eNodeB side, see the attachment Alarm Check List.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 163

 Action 5: Known Issue Checks

 Release Notes, warnings, and avoidance guides are available at Huawei support website.

How to obtain LTE FDD related documents:

 The DBS3900 release notes are released together with the software package and are available at
Huawei support website > Product Support > Wireless Network > FDD > LTE FDD RAN > LTE
FDD_eNodeB. Then, you can choose the release note of the target version for download.
 Guide to avoiding problems on the live network is updated every half of a month.
 Precaution notices are available at Huawei support website > Product Support > Wireless
Network > FDD > LTE FDD RAN > LTE FDD_eNodeB.

How to obtain LTE TDD related documents:

 The DBS3900 release notes are released together with the software package and are available at
Huawei support website > Product Support > Wireless Network > TDD > LTE TDD RAN > LTE
TDD_eNodeB. Then, you can choose the release note of the target version for download.
 Guide to avoiding problems on the live network is updated every half of a month.
 Precaution notices are available at Huawei support website > Product Support > Wireless
Network > TDD > LTE TDD RAN > LTE TDD_eNodeB.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 164

 Action 6: Parameter Checks
 Principle:
Check all parameters by scenario and preferentially analyze the impact of differences between
core parameters. If the check cannot detect the root cause of the problem, analyze other
parameters.
 Action scenario: This action is performed unconditionally.
 For detailed check methods, see X Solutions for Parameter Check in the LTE Network.
Category Description
Associated Activation and configurations of parameters are strongly associated with other switches or parameters.
parameters Therefore, check results need to be analyzed along with other parameters.
Balancing The values are set based on site conditions. In practical checks, operators can modify the values in the
parameters parameter templates and customize a parameter check template.

Air interface Air interface parameter signaling is obtained from the DT data to compare parameter mappings during
comparison tests on commercial networks. The FMA can extract air interface parameter configuration
parameters information contained in L3 signaling from Probe logs or QXDM logs.
During analysis of non-eNodeB device faults, the network topology can be analyzed to provide
Non-eNodeB check or optimization suggestions for operators based on actual experience. As for throughput differences
between radio networks or transmission networks, parameter differences (transmission parameters, EPC-
parameters related parameters, and TCP parameters) between different networks must be analyzed, especially for
MTU parameters. For details, see the attachments.

This action involves 55 core parameters affect data transmission in the entire network for X Solutions for Parameter Check
and Optimization on the LTE Network. This document mainly describes the impact of parameters related to non-eNodeB
devices and provides 38 parameters that need manual checks, associated configurations, and balancing
configurations. For other parameter checks, see X Solutions for Parameter Check and Optimization on the LTE
Network.
For detailed parameter description and impact, see Attachment – Alarm Checklist and Attachment – Parameter
Checklist.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 165

 Action 6: Parameter Checks
eRAN 8.1 introduces new features and parameters to improve the MCS performance and competitiveness. Key parameters
are listed in the following table. For more parameters, see section 2.6 Action 6 – Checking Parameters in Attachment 1 – PS
Data Transmission Optimization Guide in the LTE Network (Drive Tests).

Optimization Optimization Application

Description Optimization Benefit
Measure Command Scenario

Downlink throughput
increases by 2% to 4% at
Set CqiAdjAlgoSwitch.Ad
the cell edge but does not
AdaptiveStepVarySw aptiveStepVarySwitch Accelerate the MCS adjustment and optimization. All
increase at the cell center.
itch to ON. -1
The average throughput
increases by 2.

Enhanced function of lowering the MCS of the small packets for

The SINR increases by
Enable the function of CELLDLSCHALGO.M multiple users: When RBPriMcsSelectStrategy is set to
0.2 dB to 0.5 dB, and the
lowering the MCS of ULTIUSR_LOWMCSL MULTIUSR_LOWMCSLIMIT_STRATEGY, the number of RBs All
downlink throughput
small packets. IMIT_STRATEG increases to lower the MCS index by a maximum of 3. This helps
increases by about 1%.
lower the interference.

The number of uplink RBs

increases by 0.7, and the
CELLDLSCHALGO.C
Set Adaptively adjust the PRACH position to preclude RB fragments throughput increases by
ELLALGOSWITCH.
PrachFreqAdjSwi between the PRACH and the PUCCH and increase the number of All about 1% only when there
PrachFreqAdjSwitch-
tch to ON. RBs used for a DT. is four or fewer users and
1
FullBuffer services are
performed.

The spectral efficiency can be improved by performing the 1. FTP upload

following operations: comparison:
Increase the target value of the IBLER when the SINR drastically Imposes
Set fluctuates and the uplink packet injection is performed at an restrictions on big Uplink throughout
CELLALGOSWITCH.
UlIblerAdjustSwit average or a high speed. packets. increases by about 3% at
UlIblerAdjustSwitch-1
ch to ON. Decrease the target value of the IBLER when the SINR is large 2. PBM services: the cell center.
and slightly fluctuates. Remove
Therefore, the uplink IBLER adjustment algorithm is enabled based restrictions on big
on SINR fluctuation to improve the uplink throughput in a DT. packets.

Note: For all throughput-related parameters, see X Solutions for Parameter Check and Optimization on the LTE Network of the latest
version.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 166

 Action 7: Air Interface and Coverage Analysis
 This action is required if analysis results of action 2 show that problems are related to the air interface or coverage.
For checking items of this action, see section 2.7 Action 7 – Analyzing Air Interface and Coverage in Attachment 1 –
PS Data Transmission Optimization Guide in the LTE Network (Drive Tests).

Configurations of the power

and mobility parameters Overshoot coverage

Missing neighboring cell Pilot pollution or PCI conflicts

configurations
Low RSRP Low SINR
Incorrect EVM or antenna
Faults related to RF channels
configurations

Excessively large inter-site External interference or

distance or test route differences interference from neighboring
cells

 For problems related to the air interface and coverage, this document only describes problem symptoms. For detailed handling methods,
see X Solutions for Basic LTE Network Planning and Optimization.
 For uplink interference, it is recommended that you observe the ChMeas.Pwr.Cell counter and analyze corresponding counters. If the
interference recorded in traffic statistics is greater than –110 dBm, interference exists.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 167

Page 167
 Action 8: Coding Efficiency Analysis (RS/Pa/Pb Impact)
 Low MCSs and low rank 2 proportion are key problems in this action. For low MCS, differences in power allocation
and networking require special attention.
The following table describes impacts of power allocation on the data rate vary
RE Power RE Pwer on
(Rs, Pa, Total Power Advantage over Configuration Disadvantage over Configuration of
on Type A Type B
Pb) (20 W) of (15.2, -3, 1) (15.2, -3, 1)
Symbol Symbol
(15.2, -3, 1) 16.56 mw 16.56 mw 2x20 W -- --
• The interference from neighboring
The power and throughput are cells to a local cell increases in the
(15.2, 0, 0) 33.11 mw 41.39 mw 2x40 W
improved in the case of no load. case of load.
• The output power is doubled.
• The output power is not
changed. The interference from neighboring cells
(12.2, 0, 0) 16.56 mw 20.7 mw 2x20 W • Improves power on type B to a local cell increases in the case of
symbols, thereby increasing load.
1. The AvgSINR-THP curve indicates that configuration of (0, 0) is better than that
the throughput.
of (-3, 1) because its pilot SINR is 3 dB lower than that of (-3, 1) and data power
on type B symbols is higher.
2. The AvgSINR-THP curve indicates that the configuration of (15.2, -3, 1) is worse
than that of (18.2, -3, 1) because its pilot and data SINRs are decreased by 3 dB.
3. When the pilot power is changed from (15.2, -3, 1) to (15.2, 0, 0) and the pilot
SINR remains the same with no load, the data symbol power is increased, which
helps improve the data throughput.
4. When there is large load, the throughput performance benefits are greater with
the configuration of (15.2, -3, 1).

Scenario (RS, Power, Pa, PB)

Benchmark scenario: no or
Recommended light load (less than 10%)
(15.2, 0, 0)
configuration
Commercial scenario:
heavy load (more than (15.2, -3, 1)
30%)
For details, see Attachment 5 Impact on PA&PB Parameter Setting V1.1.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 168

 Action 8: Air Interface Coding and Coverage Analysis (Time
Synchronization Networking Analysis)
• As shown in the right figure, when time synchronization networking
is not used, RS domains are not fully aligned, resulting in small RS
interference. When time synchronization networking is used, RS
domains are fully aligned, resulting in great RS interference.
• The following table provides analysis of interference in the RS domain
and data domain when the CFI is set to 1.
• From the comparisons in the table, interference in the RS domain is
increased while interference in the data domain is decreased with
time synchronization networking. Therefore, in time synchronization
networking, the curve indicating the ratios of the SINR to the MCS
looks better than that in frequency synchronization networking.
Note: Attachment 14 describes how to determine time
synchronization networking. Generally, the SINR in time
synchronization networking is 20 dB less than that in non-time
synchronization networking.

Scenario Frequency Synchronization Time Synchronization

Shift 0/4/7/11 OFDM Symbols
Serving Cell RS SINR RS Power/(PCFICH + Noise)
RS Power/[RS(16RE/RB) + Noise]
(CFI = 1) others
RS Power/Noise
Shift 0/3/7/10 OFDM Symbols
Serving Cell Data SINR Data Power/[RS(12RE/RB) + Noise]
Data Power/Noise
(CFI = 1) Others
Data Power/[RS(16RE/RB) + Noise]

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 169

 Action 8: Air Interface Coding and Coverage Analysis (Rank2
Ratio Impact Analysis)
You can check the following table for the cause of a low Rank2 ratio in DT scenarios.
Potential Cause Description

The eNodeB is configured with 2T2R in some networks. In scenarios of metros and shopping malls,
1T1R repeater repeaters are used for coverage holes, which causes 1T1R. As a result, the Rank2 ratios vary sharply by
area in the same cell during DTs.

Whether a UE reports Rank2 information is affected by the SINR. From live network applications, some
Intra-site MOD3 areas may experience intra-site MOD3 interference. Because time synchronization is naturally used for
interference the same site, strong MO3 interference reduces the SINR in the RS domain and a low RANK2 ratio if
optimization on overlapping coverage is not good.

Time When time synchronization is used, the inter-site pilot interference increases, which reduces the SINR and
synchronization affects the Rank2 ratio.

1. Standing wave ratio (SWR) alarm: When the SWR is high, the transmit channel may be closed even
though 2T2R is configured. As a result, only Rank1 can be used.
Antenna assurance
2. Cross feeder connection: causes imbalance between two receive antennas of the UE, which affects the
Rank2 ratio.
This parameter is used for setting the initial MIMO type: 1) When this parameter is set to TM2, the
downlink throughput rate is decreased because only one data flow can be used compared with the
InitialMimoType
setting of ADAPTIVE. 2) When this parameter is set to ADAPTIVE, the downlink throughput rate is
increased compared with the settings of TM2.
MIMO mode during data transmission. When this parameter is set to NO_ADAPTIVE, set downlink MIMO
to OL_ADAPTIVE for the UE based on the FixedMimoMode parameter, enabling adaptive open loop
MimoAdaptiveSwitc
transmission. When this parameter is set to CL_ADAPTIVE and the adaptive closed loop transmission is
h
set to OC_ADAPTIVE, the UE can switch over between open loop adaptive MIMO and closed loop MIMO.
The switchover depends on the UE capability.
MIMO mode selection in the fixed MIMO mode. When this parameter is set to TM2, all UEs use the TM2
mode, only one data flow is transferred. In this case, downlink peak rate is half of that with the setting of
FixedMimoMode TM3 or TM4 (two antenna ports configured on the network side) or lower (four antenna ports configured
on the network side, and the downlink throughput rate is greatly lower than that with the setting of TM3
or TM4.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 170

 Action 9: Resource Analysis
 This action is required if analysis results of action 2 show that problems are related to resources.
For checking items of this action, see section 2.9 Action 9 – Analyzing Resource in Attachment 1 – PS Data
Transmission Optimization Guide in the LTE Network (Drive Tests).

The following figure shows the method of locating problems related RBs and Grant.
Throughput restriction Postpaid cards are recommended because the throughput is restricted by the Online
on the EPC charging system (OCS) when prepaid cards are used.
Transmission Determine whether faults exist on the EPC using
restriction the UDP packet injection.
Other NEs AMBR Check the AMBR rate contained in the S1AP_INITIAL_CONTEXT_SETUP_REQ message
restriction traced over the SI interface.
Message subscription
on the U2000

Background RBs/Grant allocated to test users are insufficient

users because they are occupied by other users
Insufficient Perform analysis of
inflow TCP faults.
Power offset in the terminal

RBs/Grant Power insufficiency

in the downlink
system information

Synchronization channel offset

Insufficiency eNodeB The PRACH period is set to
Resources occupied by other a small value.
uplink channels The PUCCH occupies many
resources
In the downlink, the RBG is rounded up. RBs allocated for DT users decrease
Known issue because of background users.
checks In eRAN6.1 and later versions, UE scheduling resources become
insufficient due to two DTXs after the DRX is enabled.

Whether ANR is
enabled
Abnormal events (call drops, handovers, Whether UEs perform inter- Whether inter-frequency
frequency measurement handovers are triggered
reestablishments, and ping-pong handovers)
Whether event A2 threshold
is properly configured

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 171

Page 171
 Action 10: Channel and Interference Analysis
 If analysis results of action 2 show that problems are related to channels/interference, this action
is required.
 Impact of channel/interference on data transmission are as follows:
 Channel exceptions such as power imbalance between channels affect the rank 2 proportion, dual-stream gains, and system
capacity. As a result, coverage is affected, MCS is reduced, and the air interface efficiency is lowered.
 Intra-RAT inter-cell interference caused by incorrect PCI planning between sectors or incorrect RF configurations decreases the MCS
and system capacity and lowers the air interface efficiency.
 Inter-RAT interference increases the IBLER, decreases the MCS and system capacity, and lowers the air interface efficiency.

Route Data Tool Analysis Principle

Cause Source
The IBLER does U2000 N/A The IBLERs greater than 15% do not decrease, or deteriorates. If the
not decrease due tracing second-level tracing results on the U2000 show that interference
to uplink results values at some time points in some RBs are greater than –115
interference. dBm, the interference exists and needs to be checked. If
interference does not exist, the problem may be considered as a
version issue and needs to be handled by R&D engineers.

The receive Probe N/A If analysis results of action 2 show that interference exists on uplink
performance is data/U2000 receive channels, use Probe data to check whether the TX power of the
poor due to uplink tracing UE greatly increases, and check whether the SINR of uplink receive
interference. results signals is low on the U2000. If these two conditions are met, uplink
interference exists and needs to be checked. Otherwise, the
interference is not the root cause for the poor receive
performance.
After channel/interference exceptions are confirmed, follow the instructions in X Solutions for Troubleshooting RF
Channel Faults in the LTE Network to check channels and detect and eliminate the interference.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 172

Page 172
 Action 11: Handover Analysis Back to contents

 Handover checks are required when the throughput is low.

 Checking items are listed as follows:
Frequent handovers/Ping-pong handovers
Large handover delay

The handover ratio is used for analysis due to

frequent handovers within a short time period. The handover delay is larger than 200 ms.

Untimely handovers/Handover failures Inter-frequency gap-assisted measurement

Handover conditions are met but the handovers are Values of PDCCH Grant Count are centralized at 750 or
not performed in time. 875.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 173

Page 173
 Action 12: Transmission and TCP Analysis
 If analysis results of action 5 show that problems are related to the inflow, this action is required.
 The methods of locating TCP faults are as follows. For details, see Attachment 3 – TCP Data Transmission Fault Locating Guide.

Whether packet loss or packet disorder occurs. 1. Settings of the send

1. Settings of the receive Check the location of the lost packets if the packet window/MTU
window/MTU loss rate exceeds 0.5%. 2. Whether the server sends
2. Whether the ACKs are Multi-spot packet capture is recommended. packets quickly
responded quickly

S1-U
SGi

public network
S9312 NE40E servers
UE+PC eNodeB UGW

Larger RTT delay exerts severer impact on TCP rate. The RTT delay decreases at the TX end than that from the TX end.
You are advised to isolate and segment the long delay to check the delay source.
In addition, you can determine whether data transmission between the eNodeB and the EPC is normal. For details, see XXX.

Scenario Analysis Principle Monitoring Criteria

Check the rate over the S1 interface and determine whether
the problems occur above the eNodeB by running the DSP UDP services must be enabled for firewalls in operator networks.
IPPATH command.
Restricted
Check whether the transmission bandwidth is restricted by
transmissio Huawei EPC must be configured accordingly.
running the SET UDPLOOP command.
n
Use the average value (FEGE.TxMeanSpeed,
bandwidth
FEGE.RxMeanSpeed) and peak value (FEGE.TxMaxSpeed, The eNodeB traffic statistics need to be activated. Operators must provide
FEGE.RxMaxSpeed) to check whether the transmission correct information about the transmission bandwidth.
bandwidth is sufficient.
IP packets in RX/TX channels on the user plane suddenly
increase, but the average size of these packets suddenly The corresponding eNodeB counter needs to be activated.
decreases.
Transmissio The counter Gtpu.RxDropBytes suddenly increases. The corresponding eNodeB counter needs to be activated.
n packet The eNodeB must be of eRAN6.0 or a later version. Huawei EPC must be of PS
The counter VS.IPPM.Forword.DropMeans suddenly increases
loss 9.2 or a later version.
The counter
The eNodeB must be of eRAN6.1 or a later version. The EPC (including an EPC
VS.BSTWAMP.Forward.DropMeans/VS.BSTWAMP.Backward.Dro
of other vendors) must support TWAMP.
pMeanssuddenly suddenly increases.
The eNodeB must be of eRAN6.0 or a later version. Huawei EPC must be of PS
Others The counter VS.IPPM.Forword.DropMeans exceeds 20 ms.
9.2 or a later version.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 174
Page 174
 Appendix: Data Collection Guidance

Data Source Description Operation Guide

The tracing task is performed at the cell level, and
Cell DT tracing results
data of the call can be obtained at the TTI level.
The tracing task is performed at the cell level, and
IFTS tracing results data of the first UE that accesses the cell after the For detailed
tracing is enabled can be obtained at the TTI level. operations, see
Detailed UE tracing Detailed UE tracing is cell-level tracing and captures TTI- chapter 3 in
results level data based on UE's M-TMSI. Attachment 1 – Data
Transmission Fault
Data collected by the Locating Guide.
The QXDM is used to collect data.
QXDM
QXDM data collected by The Probe is used to collect the QXDM data. However,
the Probe only certain data can be obtained.
Packets captured by the The WireShark can be used to capture TCP/UDP
WireShark packets. For detailed
Packets captured by the The Microsoft Network Monitor is used to capture operations, see
Microsoft Network packets if the WireShark cannot detect the network chapter 5 in
Monitor interface card (NIC). Attachment 3 – TCP
Data Transmission
Packets captured by the Fault Locating Guide.
Packets are captured by the mirror server over the S1
mirror server over the S1
interface.
interface

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 175

Page 175
 Appendix: Case List
For all cases, see Attachment 1 – PS Data Transmission Optimization Guide in the LTE Network (Drive
Tests).
Root Cause
Case Name
Analysis
Determining Whether the Network Adopts Time
Air interface coding
Synchronization Mode According to QCAT
Air interface coding Intra-eNodeB MOD3 Conflict Causes Low Rank2 Percentage
Air interface coding The Data Rate Failed to Remain at the Peak Value
Impacts of System Information Bit Rate on the Number of
Resource
PDSCH RBs
Resource Impacts of Synchronization Channel Power on PDSCH RB
Resource Impacts of Background Users on PDSCH RB/Grant
Scheduling of DTX for DL Data Transmission Was Stopped for
Resource
Two Consecutive Times
Resource Determining Whether the UL Inflow is Sufficient According to the BSR
Resource IBLER-related Problems in Non-Huawei Networks
Resource Impacts of UL Smart Preallocation on UL DT UEs
Resource Impacts of UL IBLER on UL Grant
Inter-frequency Measurement Gap Causes Insufficient
Handover
Scheduling
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 176
Page 176
 Contents
 LTE PS Service(Drive Test)
 LTE PS Service(Traffic
Statistics)
 LTE PS Service(Ping Delay)

Page177

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 177

 Contents

1 Background

2 Standard Action for Performance Improvement

3 Analysis Method

4 Tools Introduction

5 Case

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 178

 Methods of Classifying and Evaluating LTE PS Traffic Statistics Issues

Deterioration Comparison Testing

Scenarios Scenarios

 Issue Description  Issue Description

Collect traffic statistics using the U2000 Collect traffic statistics using the U2000 to obtain
to obtain the following information about the following information about Huawei networks:
Huawei networks: 1) Whether uplink/downlink UE throughput on
1) Decrease in UE throughput Huawei networks is lower than that on Huawei
2) Decrease in cell throughput competitors' networks
3) Decrease in spectral efficiency 2) Whether the CQI vs downlink UE throughput
(bits/Hz) curve for Huawei networks is inferior to that for
4) Decrease in the values of user-plane Huawei competitors' networks
traffic KPIs, including the BLER, 3) Whether the values of user-plane traffic KPIs,
proportion of good CQI values, ARQ including the BLER, proportion of good CQI
retransmission rate, and PDCP delay values, ARQ retransmission rate, and PDCP
 Evaluation Criteria delay, for Huawei networks are lower than
1) UE throughput, cell throughput, or those for Huawei competitors' networks
spectral efficiency (bits/Hz) decreases.  Evaluation Criteria
2) UE throughput, cell throughput, or 1) Telecom operators complain that traffic KPIs
spectral efficiency (bits/Hz) decreases for Huawei competitors' networks are superior
by over 5% after an upgrade. to those for Huawei networks.
3) User-plane traffic KPIs deteriorate 2) The user-plane traffic KPIs for Huawei
significantly after a version upgrade or networks are lower than those for Huawei
parameter reconfiguration. competitors' networks.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 179

 Contents

1 Background

2 Standard Action for Performance Improvement

3 Analysis Method

4 Tools Introduction

5 Case

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 180

 Standard Action for Performance Improvement

To ensure satisfactory LTE throughput, the following actions for effective routine network maintenance and
optimization must be taken:

Action 1: Parameter Check Periodically check network parameters to ensure feature parameter
consistency and that feature parameters are set to the values
recommended for the current version. For details, see X Solutions for
Parameter Check in the LTE Network.

Action 2: Alarm Check Periodically check network alarms and clear those that may affect
output performance. For details about various types of alarms, see
Attachment 3 Alarm Checklist.

Build a system for regularly monitoring PS transmission KPIs by

following the instructions provided in X Solutions for Network
Action 3: Daily KPI Performance Monitor Performance Monitor. This ensures that the calculation formulas of the
monitored KPIs comply with 3GPP specifications or Huawei
requirements.

Good PS throughput performance is ensured by proper basic network

planning and optimization, which concentrates on optimization of the
Action 4: Basic Network Planning and SINR and rank 2 proportion.
Reference documents: X Solutions for Basic Network Planning and
Optimization
Optimization in the LTE Network and X Solutions for Troubleshooting
RF Channel Faults in the LTE Network

The analysis of transmission issues costs much. Perform acceptance

Action 5: Transmission Optimization tests on each site by strictly following the peak throughput
requirements, and efficiently identify transmission issues during the site
construction phase. Make all possible efforts to solve identified
To obtain the preceding reference transmission issues.
Reference documents: X Solutions for PS Data Transmission
documents, click Click. Optimization in the LTE Network(Traffic Statistics KPI)

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 181

 Contents

1 Background

2 Standard Action for Performance Improvement

3 Analysis Method

4 Tools Introduction

5 Case

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 182

 Factors Affecting LTE PS Performance

Customer OSS
Coverage/Modulation
 CQI/SINR
TCP/IP Performance
 MCS/IBLER/MIMO  Bandwidth/
 Grant/RB
Latency/Packet
RF
Drop User QoS
 Power Configuration  MTU
 MIMO 1T2R\2T2R\  TCP Parameter
HSS KPI Statistics Error
OL\CL KPI Mapping Error

Router
IP IP IP
Power Network Network Network
MME FireWall
QoS/Capacity  Capacity/CPU Load
 AMBR
 Feature/Parameter
 QCI 6/8/9
 Cat
 License/Alarm PS Core Network TCP Win
 Abnormal Operation  Speed Limit(CAR)
 Software defect  Feature(TCP Proxy/DPI)
 Hardware defect  Charge Policy

Cache (F5)

Every phase of the E2E process affects PS transmission performance. It is necessary to understand
the E2E key factors and possible causes affecting LTE PS performance.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 183

 Factors Affecting the ARQ

Element Factor Impact

The UE does not need to return an RLC ACK message after a handover or RRC
SRB retransmission
connection release procedure, which may cause the eNodeB to retransmit data.
Sending of downlink Downlink packets cannot be properly sent at the MAC layer due to a specific RBLER. For
packets details, see information about MAC RBLER analysis.
RLC analysis If uplink status cannot be reported in time, the timer eNB-PollRetransmit-Timer on the
eNodeB times out, causing retransmission of the polling instruction. When there are no
Improper setting of
error bits, RLC information cannot be sent in time if the timer eNB-PollRetransmit-Timer
the uplink status
on the eNodeB and the timer UE-StatusProhibit-Timer on the UE are improperly set. In
reporting timer
normal cases, the value of UE-StatusProhibit-Timer on the UE must be smaller than that
of eNB-PollRetransmit-Timer on the eNodeB.
A message may fail to be transmitted by the MAC layer due to poor channel quality.
Poor channel quality ARQ retransmission is triggered if the message still cannot be transmitted after the
number of NACK messages exceeds the maximum number of retransmissions.
SR LTE-capable UEs are used on China Telecom networks. Such SR LTE-capable UEs do
not notify the LTE network when listening to the paging channel of the CDMA network.
A large number of retransmissions at the MAC and RLC layers are triggered because SR
Continuous DTXs LTE-capable UEs periodically listen to the paging channel of the CDMA network.
MAC RBLER reaching the The PUCCH incorrectly detects messages. When the PUCCH has low transmit power or
analysis maximum number suffers from serious interference, the PUCCH transmit power cannot be adjusted in
of retransmissions time through PUCCH power control, which affects the PUCCH's demodulation
or scheduling performance. As a result, an ACK message is incorrectly detected as DTX or an NACK
stopped at the MAC message, causing retransmissions.
layer After DRX is enabled, false SR detection triggers scheduling on the eNodeB. At this
time, however, the UE is in the sleep time, and cannot properly receive data. As a
result, a large number of DTXs are triggered, causing retransmissions in the uplink and
downlink at the MAC and RLC layers.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 184

 Factors Affecting the CQI

Element Factor Impact

Network Weak coverage and The CQI is used to evaluate spectral efficiency. Spectral efficiency is low and the UE reports a
coverage overlapped coverage low CQI value in the event of weak coverage.
Time synchronization
Synchronization When time synchronization is implemented, interference increases, and the UE reports a lower
and frequency
method CQI value.
synchronization
Closed-loop MIMO and When closed-loop MIMO is used, the UE selects a channel based on the PMI, and therefore
open-loop MIMO reports a higher CQI value.

If the RS power decreases by 3 dB, the value of PA is changed from –3 to 0, but the RS SINR
PA and PB does not decrease by 3 dB, the UE measurement increases by 3 dB according to the value of
PA. As a result, the CQI value is greater than its actual value.

Wide-band CQI and sub- When the best sub-band CQI is reported, the measured CQI value is greater than its actual
UE's CQI
band CQI value.
reporting
Aperiodic CQI reporting is more reliable, and the PUCCH may incorrectly detect messages in
the event of periodic CQI reporting. In normal cases, aperiodic CQI reporting is superior to
Periodic and aperiodic
periodic CQI reporting. The CQI value becomes higher if the number of aperiodic CQI reports is
greater than that of periodic CQI reports.

A larger value of eNodeB detection indicates more occupied PUSCH indicators, less incorrect
Delta offset CQI index
CQI detection, and higher CQI reliability.
When false SR detection occurs, the eNodeB receives a random CQI value, which is small in
False SR detection
eNodeB most cases.
detection When incorrect CQI detection occurs, a random CQI value, which is small in most cases, is
Incorrect CQI detection
reported.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 185

 Action Analysis
Starting from the actual procedures involved in traffic statistics issues, this document provides actions for issue identification,
cause demarcation, and root cause location.
Closed-Loop
Cause Demarcation Cause Analysis
Optimization

Step 1: Check KPI definitions and traffic statistics.

Step 2: (Mandatory) Check basic elements to Step 3: Perform an E2E analysis to locate
Also identify the issue scope (including the TopN
find out whether issues are caused by basic issues. If the issues occur on the eNodeB,
cells, change trends on each frequency band, and
elements. Then, preferentially perform the identify their root causes. If they do not occur
change trends in MOCN networking) to obtain the
actions suggested by key factors based on the on the eNodeB, isolate NEs, and formulate
change trends of associated KPIs. Check whether
analysis results of associated KPIs. Obtain the optimization schemes based on the causes of
the KPIs in DTs on Huawei networks deteriorate
impact of each network node on throughput by the issues.
or are inferior to those on Huawei competitors'
an E2E analysis of the UE, eNodeB,
networks.
transmission network, and CN.

(Mandatory) Basic Product

Parameter CN
Actions 1 and 2 in elements check: configuration quality Non-
eNodeB-
X solutions actions 3 to 6 in X related Interference Network eNodeB- Transmission
solutions issues capacity related network
issues
Instead of being Coverage Network load UE
performed only in the Basic elements
event of issues, actions 3 analysis (based on
to 6 can be used as
obtained leads): Parameter RF Version
routine network
maintenance measures. actions 7 to 12 reconfiguration optimization improvement

Action 13: Some issues must be analyzed based on DTs. For

Traffic model Resource and
details, see X Solutions for PS Data Transmission
analysis capacity analysis
Optimization in the LTE Network (Drive Tests).
Coverage and air- Channel and
interface interference analysis
For details about transmission issues, see X Solutions for PS
performance analysis
Data Transmission Optimization in the LTE Network (Drive
Handover analysis Transmission and Tests) or X Solutions for PS Data Transmission Optimization
TCP analysis in the LTE Network.

The actions provided in X solutions are formulated and methodically organized based on cases and issue characteristics identification by
following the principle for minimal costs.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 186

 Differences in Actions Between Deterioration and Comparison
Testing Scenarios

Deterioration Comparison Testing

Scenarios Scenarios

Check whether the KPI calculation formulas Analyze the differences in KPI calculation formulas
Action 1: Check KPI
used on the live network are the same as between Huawei and its competitors if there are any.
definitions.
those on the FMA.
 Check for associated KPIs in which differences are
Focus on deteriorating KPIs. detected between Huawei and its competitors.
Action 2: Identify the  Perform DTs to demarcate and locate issues (for
issue scope and details, see action 13).
 Check for historical operations at the time
demarcate issues. of KPI deterioration.
 Check for new faults and alarms.
 Focus on the differences in air interface parameters
 Check for known issues in the current between Huawei and its competitors.
Actions 3 to 6: Check version.
 Check whether parameters are set to their optimal
basic elements.  Check the impact of parameter values to ensure transmission performance.
reconfiguration on traffic statistics.
 Check consistency between network parameters.

Preferably analyze the impact of difference-involved KPIs

Actions 7 to 12: Perform required actions according to the
according to the analysis results of action 2, for example,
Analyze the problem. analysis results of action 2, thereby locating
the impact of the number of UEs, restrictions on
the cause of the deterioration.
transmission bandwidth, and parameter setting
inconsistencies.
If the cause of the deterioration cannot be
Action 13: Perform identified through the preceding actions, you In normal cases, DTs are mandatory. DT results are
DTs. are advised to perform DTs, thereby compared between Huawei and its competitors to obtain
comparing and analyzing the KPIs before and differences, such as those in coverage and in limitations
after the deterioration. on spectral efficiency and transmission bandwidth. (DTs
are performed preferentially for issue location.)

Actions 3 to 6 are included in the technical guide, and therefore are not detailed in this document.
Instead of being performed only in the event of issues, actions 3 to 6 can be used as routine network maintenance
measures.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 187

 Overview of Required Actions for Performance Optimization (1)

Prerequisi
Step Action Purpose
te
Check whether the KPIs formulas used by Huawei are correct or the same as those used
Action 1: Check KPI by Huawei competitors.
definitions. None The methods of calculating traffic KPIs are incorrect.
Step 1: Check whether the number of cells in traffic statistics and the collection period differs
Identify and before and after the deterioration.
demarcate 1. 3 Characters: "geographical"(TOP Cell)+"time"+"Frequency Band"(Dual Band)
issues. Characters.
Action 2: Identify the
2. Execute associated traffic statistics analysis according to issue scenarios(deterioration
issue scope and None
or comparison testing).
demarcate issues.
3. Associated traffic statistics analysis: Coverage/Modulation and Coding, Resource and
Capacity, insufficient data source, RF Channel and Interference.
Action 3: Check
external events 1. Check the impact of abnormal eNodeB-side operations.
and historical 2. Check the impact of modifying the following factors on the service throughput: RF
antennas, transmission/TCP, EPC/datacom equipment, and user QoS.
operations Deterioratio
3. Determine the impact of external events (press conferences for new mobile phones
(including n scenarios
and great gatherings).
eNodeB-side 4. Check whether certain neighboring sites or cells are deactivated, sites are
operations and disconnected, or access is prohibited.
other operations).
Step 2:
Check basic Action 4: Check for None Check for alarms affecting the traffic services
elements. faults and alarms.
Action 5: Check for If deterioration occurs after an upgrade, check changes in the current Release Notes and
None
known issues. resolved issue in next version release Notes.
1. Parameters include eNodeB parameters, the AMBR, TCP, TCP window length, and
Internet exit bandwidth.
Action 6: Check 2. In deterioration scenarios, evaluate the impact of parameter changes.
None
parameters. 3. In comparison testing, check differences in parameter settings between Huawei and its
competitors and check whether parameter settings meet the requirement of achieving
the optimum throughput.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 188

 Overview of Required Actions for Performance Optimization (2)

Step Action Prerequisite Purpose

Action 7: Analyze the Check whether the traffic model has changed. Changes in the traffic model
traffic model. cause changes in throughput.
1. In deterioration scenarios, analyze the impact of changes in UE quantity,
uplink and downlink traffic, and common message overhead on throughput
Action 8: Analyze
and spectral efficiency.
resources and
2. In comparison testing scenarios, analyze the impact of differences in UE
capacity.
quantity and resource overhead between Huawei and its competitors on
throughput.
Action 9: Analyze air
Preferentially Analyze the impact of coverage and air interface coding efficiency on the
interface coding and
performed service throughput.
coverage.
based on
Action 10: Analyze action 2. 1. Analyze the impact of external interference on the service throughput.
Step 3: Analyze channels and 2. Analyze the impact of the dual-code(MIMO) proportion on the service
the problem. interference. throughput.
Analyze the impact of the following factors on the service throughput:
Action 11: Analyze
excessive (ping-pong) handovers, delayed handovers, inter-frequency
handovers.
handovers, and remaining neighboring cells.
Action 12: Analyze This X solution just provides the basic isolation method for Transmission and
transmission and TCP in Action 2 chapter. For details, see the X solutions for LTE driver test and
TCP. the X solutions for Transmission and TCP.
Performed
when issues Check whether the KPIs in DTs on Huawei networks are inferior to those on
Action 13: Perform cannot be Huawei competitors' networks after deteriorating.
DTs. resolved In comparison testing scenarios, perform DTs in Huawei' and its competitors'
through actions network areas preferentially in the event of issues.
7 to 12
Step 4: Check
Perform actions based on problem description to solve problems. In deterioration scenarios, analyze
whether If the problem is not solved, provide the preceding checklist and related
the impact None
problems areof factor changes on the throughput; in comparison
deliverables and submit testing scenarios,
the problem focus on the impact
to R&D personnel.
of Huawei's and its competitors' factors on the throughput.
solved.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 189

 Action 1: Checking KPI Definitions

Action 1 is performed on any condition. Checking KPI definitions in the first place helps avoid a
waste of time on analyzing invalid data. Focus on the following information during the KPI definition
check (for details, see Attachment 1 technical guide):
 Use the FMA to perform a secondary check on all traffic statistics provided by telecom operators.
 Ensure that the KPI mapping is correct before a KPI comparison between Huawei and its competitors. For details about the
KPI mapping, see the network swapping SOP 3.0, which can be downloaded from link.
 Verify that KPI calculation formulas are correct. When a KPI has multiple formulas, the values calculated by different
formulas vary. For example, the formula stipulated in 3GPP specifications is recommended for UE throughput.
 Check the method of collecting traffic statistics: average value of each cell, or weighted average value of the entire
network.
 Check consistency between traffic statistics, including whether the number of sites and that of cells remain unchanged
before and after the deterioration, and whether the collection period is the same before and after the deterioration.

The value of a KPI varies according to the calculation formula.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 190

 Traffic KPIs Related to LTE PS Performance

KPI Huawei E// Equipment Vendor

User DL (L.Thrp.bits.DL – = (pmPdcpVolDlDrb-
Throughput(Protocol L.Thrp.bits.DL.LastTTI)/L.Thrp.Time.DL.RmvLastT mPdcpVolDlDrbLastTTI) 1) Non-specification Avg-User DL throughput exit in this
) TI (according to 3GPP specifications) /pmUeThpTimeDl/1000 version X solution.
2) TDD-LTE Avg-User DL Throughput shall divide the
User UL (L.Thrp.bits.UL – = coefficient configured by TDD UL/DL sub-Frame
Throughput(Protocol L.Thrp.bits.UE.UL.LastTTI)/L.Thrp.Time.UE.UL.Rm pmUeThpVolUl/pmUeThpTim configuration, more detail see Appendix.
) vLastTTI (according to 3GPP specifications) eUl/1000
L.Thrp.bits.DL/
Cell DL Throughput NA
L..Thrp.Time.Cell.DL.HighPrecision①

Cell UL Throughput L.Thrp.bits.UL/L.Thrp.Time.Cell.UL.HighPrecision NA

Cell DL Traffic L.Thrp.bits.DL/1e9 = pmPdcpVolDlDrb/1e9

Specifies the total service volumes in cells within the
statistical period, which can reflect cell loads.
Evaluation

Cell UL Traffic L.Thrp.bits.UL/1e9 = (pmUeThpVolUl/1e9

item

[(L.Thrp.bits.DL/(Report_Period x
Spectrum Efficiency
60)]/1000000/[L.ChMeas.PRB.DL.Used.Avg/(Syst NA
DL_formula1 Reflects the cell throughput/Hz
em bandwidth x 5)]/System bandwidth②
Furthermore 100%RB throughput can also reflect the Max
L.Thrp.bits.UL/(Report_Period x cell throughput when 100% RB Usage
Spectrum Efficiency
60)/1000000/[L.ChMeas.PRB.UL.Used.Avg/(Syste NA
UL_formula1
m bandwidth x 5)]/System bandwidth}

ARQ DL Retrans "L.Traffic.DL.AM.Retrans.TxPackets" /

NA Indicates the downlink RLC retransmission rate in a cell.
Ratio "L.Traffic.DL.AM.TxPackets" * 100
("L.Traffic.DL.PktDelay.Time.QCI.1" + …….+
Indicates the average delay of packets in the downlink on
Packet Delay in the "L.Traffic.DL.PktDelay.Time.QCI.9") /
N/A the PDCP user plane. For details, see the definition of the
DL ("L.Traffic.DL.PktDelay.Num.QCI.1" + ……..+
PDCP delay.
"L.Traffic.DL.PktDelay.Num.QCI.9")
Indicates the delay of the first packet in the downlink on
First Packet Delay L.Traffic.DL.EmptyBuf.PDCPLat.Time/ pmPdcpLatTimeDl/
the PDCP user plane. For details, see the definition of the
(DL) L.Traffic.DL.EmptyBuf.PDCPLat.Num pmPdcpLatPktTransDl
PDCP delay.

① The cell throughput is calculated by excluding SRB volumes because cell-level statistical period measures only the DRB period.
② System bandwidth x 5: For example FDD 10Mhz, System bandwidth x 5=10*5=50 RBs

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 191

 Introduction to Avg User-Throughput Definitions for Protocol-Defined
Traffic Statistics KPIs
 Statistical period for services:
According to protocols, the ThpTime starts when MAC
schedules the first data packet and stops when the buffer is
cleared excluding the last TTI(empty buffer).
 Statistical scope for service volumes:
Effective user-plane data volumes at the PDCP layer are
measured, excluding the number of bits for retransmission and
MAC/RLC head on the MAC/RLC layer and last TTI data
volumes(empty buffer).
 Impact of the last TTI on the throughput:
The last TTI's data volume is insufficient, leading to a low
3GPP 32.450 6.3.2 Charter
throughput for the last TTI. In case of large-scale service
modules (such as the FTP and BT), the last TTI has little impact
on the throughput and the throughput almost keeps unchanged.
 Uplink throughput:
The uplink throughput is almost defined to be the same as the
downlink throughput. For details, see 3GPP 36.314 4.1.6.

Thp(excluding LastTTI)=(4K+4K)/2ms=4000Kbps
Thp(including LastTTI)=(4K+4K+2K)/3ms=3333Kbps

 Huawei FDD: Since eRAN6.0, eNodeB-side statistical methods are in

compliance with protocols.
 TDD: Protocol-defined statistical methods are incorporated in eRAN7.0.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 192

 PDCP Delay Definition (3GPP)

Definition of IP Latency for E-UTRAN  Delay definitions in 3GPP specifications

3GPP specifications provide two delay definitions:
Section 6.3.2 in 1) IP latency: indicates the interval between the time when a packet
3GPP TS 32.450
enters the buffer to the time when the packet is scheduled for the first
time in the downlink at the MAC layer.
2) Packet Delay in the DL per QCI: indicates the average PDCP
packet delay in the downlink on the user plane. The measurement
starts from the generation of a PDCP SDU packet and ends once the
scheduling of the packet is complete at the MAC layer, with the HARQ
feedback time excluded.
 Delay definitions supported by Huawei
Packet Delay in the DL per QCI
The IP latency for E-UTRAN was introduced in eRAN8.0, and
corresponds to First Packet Delay (DL) on page 15.
Packet Delay in the DL per QCI corresponds to Packet Delay in the
Section 4.1.4 in 3GPP
TS 36.314 DL on page 15.
 Delay definitions supported by Huawei
competitors:
Peer vendor E supports only the IP latency for E-UTRAN.
Peer vendor Z supports only the Packet Delay in the DL per QCI.

When PDCP-delay-related issues occur in comparison testing

scenarios, make sure that you have learned about the definitions of
delay supported by Huawei and its competitors. This helps avoid false
issues caused by inconsistent KPI calculation formulas.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 193

 Action 2: Identifying the Issue Scope and Demarcating Issues

This action is performed after you have verified that the KPI calculation formulas and data are valid. This action enables you to demarcate an
issue to identify the cause, helping determine the subsequent action and avoid unnecessary analysis.
First, obtain basic information about each issue:

Issue occurring on the entire ›If KPIs deteriorate in TopN cells, do not check the NEs (including the EPC, FTP server, some transmission devices, and tested
network or in TopN cells UEs) shared between TopN cells and non-TopN cells. Focus on differences, such as those in eNodeB configurations,
transmission, channel quality, and interference.

Issue occurring in MOCN ›Air interface parameters on the eNodeB are set without distinguishing between PLMNs. If one operator's network is faulty but
networking another operator's network is normal, the issue does not occur in the air interface pipe for the eNodeB. Focus on differences,
such as changes in the configurations of the EPC and transmission equipment, between operators.

Issue occurring on a ›Obtain the changes in the UE throughput, UE quantity, and parameter settings on each frequency band, the coverage
multi-band network capability of each frequency band, and the impact of differences in UE's frequency band capability.

Perform associated KPI analysis after The FMA can automatically complete this action,
the preceding information is obtained. including:

TopN cells need to be identified? Collecting traffic statistics about

Traffic
Model FMA TopN objects

Multiple frequency bands need to be Collecting statistics about KPI

Transmiss Resources isolated? objects by category
ion and and
TCP Capacity
It is difficult to analyze multiple traffic One-click import of traffic
statistics files? statistics
Associated
KPI Analysis Associated analysis on multiple KPIs One-click export of associated
is required? KPIs

Coverage Customized definition of traffic

and Air- Some traffic KPIs are not defined?
Channels KPIs
and Interference Interface
Performance

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 194

 Associated Traffic KPI Analysis

Identify the types of deteriorating KPIs to determine the subsequent action.

Demarcation of Associated KPIs

Resources and Coverage and Air- Channels and Transmission

Traffic Model Handover Analysis
Capacity Interface Performance Interference and TCP
Traffic KPIs

 Proportion of traffic  Number of users  Average CQI value  PUSCH  Handover  IPPM delay and
or duration of the  Traffic volume and CQI distribution interference success rate packet loss
last TTI  CCE usage  Average MCS index  PUCCH  Number of inter-  Maximum FE/GE
 Length distribution  PRB usage value and CQI index interference frequency bandwidth
of incoming PDCP  PUCCH RB distribution handovers
packets  IBLER/RBLER
 PDCCH DTX
 Rank 2 proportion
Actions

Action 8 Action 9 Action 10 Action 11 Action 12

Action 7

Supplementary information about traffic model analysis is as follows:

There are no AMBR-related traffic statistics. As a result, associated KPI analysis cannot be performed for
the AMBR. However, the AMBR is a core factor affecting the traffic model. Changes in the AMBR cause
changes in the packet-receiving model. Therefore, you also need to obtain the AMBR changes in TopN cells
through S1 interface tracing when analyzing the traffic model.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 195

 Action 7: Analyzing the Traffic Model

This action aims to identify the possible causes of traffic model changes based on the following factors:
Scenario Element Evaluation Criteria Involved KPI Factors
① [Multi-band networking] UEs migrate among frequency
[S1 tracing] The proportions of AMBRs bands.
change significantly, especially low AMBRs
AMBR -- ② Networks are put into commercial use, users choose other
Deterioration (for example, 64 kbit/s) whose proportion
operators, or large gatherings are held.
increases.
③ UEs' QoS (QCI) changes.
① Functions such as CAR and DPI are enabled on the CN.
Proportion of traffic The proportion of traffic within the last TTI
DL LastTTI data volume Ratio ② Transmission performance decreases.
within the last TTI increases by over 5%.
③ The AMBR decreases.
Length of an
The average length of incoming PDCP
incoming PDCP Avg PDCP DL Packet Size Modifications are made to MTU transmission nodes.
packets decreases by 100 bytes.
packet
[S1 tracing] The proportion of UEs with low
Comparison testing

AMBRs on Huawei networks is greater than

AMBR that on Huawei competitors' networks. -- AMBR limitation is enabled on Huawei networks.
Alternatively, low AMRBs such as 64 kbit/s
are detected on Huawei networks.
The value of the DL LastTTI
The AMBR on Huawei networks is lower than that on Huawei
The value of the DL LastTTI data volume data volume Ratio KPI on
Proportion of traffic competitors' networks.
Ratio KPI on Huawei networks is greater Huawei networks is greater
within the last TTI Transmission and TCP issues (for example, insufficient
than that on Huawei competitors' networks. than that on Huawei
bandwidth provision and packet loss) occur.
competitors' networks.
2014-8-14 AMBR changes
2014-10-15 cause a
throughput
decrease.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 196

 Action 8: Analyzing Resources and Capacity
After the traffic volume and number of UEs increase, some resources (for example, CCEs, PRBs, and scheduling
capabilities) are limited, decreasing throughput in traffic statistics.
Scenario Element Evaluation Criteria Involved KPI Factors
1) Parameters for inter-frequency handovers, inter-RAT handovers, load
Traffic User Avg
balancing thresholds, reselection thresholds, or priorities are reconfigured.
Traffic User Avg with data in DL
Number of 2) Networks are put into commercial use, users choose other operators, or
The number of UEs changes by over 5%. Buffer
UEs large gatherings are held.
Traffic User Avg with data in UL
3) The volume of service-package-allowed traffic is used up at the end of a
Buffer
month.
Deterioration
1) The number of UEs changes.
2) UEs' QoS (QCI and AMBR) changes.
The volume of uplink and downlink traffic 3) The volume of service-package-allowed traffic is used up at the end of a
Traffic Cell DL/UL Traffic
changes by over 5%. month.
4) Transmission changes cause transmission performance deterioration.
5) CN configurations (for example, CAR and DPI) change.
The number of average UEs and the CDF curve
showing the number of UEs on Huawei
networks are superior to those on Huawei
Number of competitors' networks. Air interface resources are evenly distributed. A grater number of UEs
Traffic User Avg
UEs indicates lower throughput per UE.
The CDF curve showing a comparison between
Comparison the number of UEs and throughput for Huawei
testing is inferior to that for Huawei competitors.
Difference in the number of
Scheduling scheduled resources between The EPF scheduling algorithm is used by default on Huawei networks. On
Testing is required. For details, see the
algorithm places of long distances to the cell Huawei competitors' networks, however, a scheduling algorithm similar to
technical guide.
differences center and those of short Max C/I may be used to improve the throughput per UE
distances to the cell center
The average uplink PRB usage is greater than
UL PRB Usage Rate Perform action 9 for coverage and coding analysis.
70%.
1) RF coverage analysis: Check for island sites and missing neighbor
True and false Alternatively, the average downlink PRB usage
Resource DL PRB Usage Rate relationships.
capacity is greater than 70%.
limitation 2) Check for abnormal MCS index selection.
issues Alternatively, the CCE usage is greater than
Relationship Between the Number of UEs and the Single-UE
70% or the proportion of DRB CCEs decreases PDCCH CCE Usage Rate(eRAN 6.0)
3) Check for false capacity issues: The IBLER, RBLER, or number of PDCCH
DTXs is abnormally high.
by 5%.
Throughput
Throughput decreases as the number of UEs increases. This figure is
for reference only. The throughput curve at a site varies according to
the network bandwidth and RF quantity, and does not serve as an
evaluation criterion.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 197

 Action 9: Coverage/Modulation and Coding Analysis
Coverage directly affects the service rate. Good coverage is necessary for ensuring high throughput. Air interface performance depends on both coverage
and product capabilities. The analysis method is as follows. For details, see Attachment 1 technical guide.
Scenari
Element Evaluation Criteria Involved KPI Factors
o
1)Avg CQI RF antenna adjustment/Out-of-service neighboring cells/Missing Neighbor
(Traffic KPIs) The average CQI decreases by 0.5 2)Statistics of the
Coverage Changes in power, handover parameters;
or greater. each CQI
proportion feature (MIMO mode, MRO, DRX, SFN, Time-Sync, eMBMs)
PUSCH MCS Deterioration in coverage and interference
Avg(eRAN 3.0) The proportion of special scheduling (②) increases.
PDSCH MCS
(Traffic KPIs) The uplink or downlink MCS greatly DL MCS: CQI adjustment Algorithm/ the threshold for MCS Selection with
Avg(eRAN 3.0)
deteriorates. Prioritized RBs
Statistics of the
each CQI UL MCS:UL Comp, SFN
proportion DL MCS: Simulator load makes DL MCS0 ratio increase
Deterio
(DL) Adjustment in CQI adjustment algorithms
ration Modulation (Traffic KPIs) The cell's uplink or downlink IBLER DL IBLER (DL)The CQI adjustment amplitude slowly improves (version defect). ③
and Coding increases or decreases by more than 3%. UL IBLER (Traffic KPIs) The cell's PDCCH DTX probability deteriorates greatly.
Scheme
UL MCS0 Ratio increase
PDCCH DTX PDCCH closed-loop adjustment switch/PUSCH DTX switch
(Traffic KPIs) The cell's uplink RBLER significantly
Ratio④ External interference
deteriorates.
PUSCH RBLER Version quality (DRX SR faulty/RRC Release/Ho CMD)
Feedback channel faults caused by PUSCH or PUCCH demodulation
See the common factors for coding efficiency. performance deterioration
Changes in version implementation
[DTs] The average indicating the RSRP or SINR,
the curve indicating the RSRP and SINR, and the
Improper RF network optimization and planning, improper inter-site
proportion of PCI-modulo-3 conflicts on Huawei NA distance, and missing neighbor relationships
networks are inferior to those on Huawei
Coverage competitors' networks.
[Traffic statistics] The CDF curve indicating the
average CQI and that indicating the CQI on Differences in LTE power parameter configurations, MIMO mode, and time
Huawei networks are inferior to those on Huawei
NA synchronization
Compar competitors' networks.
ison [Traffic statistics] Check the rank 2 proportion.
testing The check result shows that cells whose rank 2 NA RF channel alarms, MIMO configurations, and channel imbalance
proportion is 0 or less than 30% exist.
Modulation [DTs] The curve indicating the SINR and the
and Coding throughput, RB usage, or DL grant on Huawei
Scheme networks is inferior to that on Huawei
For details, see X Solutions for PS Data Transmission Optimization in the
competitors' networks. NA LTE Network (Drive Tests).
In addition, the curve indicating the SINR and
MCS index on Huawei networks is inferior to that
HUAWEI TECHNOLOGIES CO., LTD. competitors' networks.
on Huawei Huawei Confidential 198
 Action 10: Analyzing Channels and Interference

Channel problems affect transmission performance in the following ways: 1) The MIMO dual-codeword proportion is low. 2)
Interference mainly affects the MCS. 1) The MIMO dual-codeword proportion is low. 2) Interference mainly affects the MCS.
The preceding impact decreases spectral efficiency and the throughput in traffic statistics.
Elemen
Evaluation Criteria Involved KPI Factors
t
Internal/External interference
L.UL.Interference.Avg
[Traffic statistics] The cell interference Reconstruct RF antennas ①
Uplink Interference

Avg PUCCH Interference

noise floor increases by at least 3 dB.
Avg PUSCH Interference Power control parameters or IRC parameters are
modified.
The U2000 detects that interference is
strong at high frequencies and weak at U2000 Trace Interference randomization feature/parameters
low frequencies.
RF adjustment or cell out of service
[Traffic statistics] PUSCH/PUCCH RSRP
Avg PUCCH RSRP
decrease or the proportion of low RSRP Alarms about RF Channels
Avg PUSCH RSRP
increase.
Power control parameters modification
RF Channel alarms and faulty ②
Rank 2 proportion check

RF antennas are adjusted.

The MIMO mode modification
Emergency calling is enabled and the ARP of the
MIMO RANK2 PRB Ratio bearer used for emergency calling is the same as that
(Traffic KPIs) The proportion of cell's rank
Or of the bearer used for common services on the live
2 proportion decreases.
MIMO Rank2 TB Ratio network. For details, see optimization guidelines.

1) The RSRP of Channel paths is unbalanced. ③

2) 2T2R Macro-cell with 1T1R repeater
3) PCI mod3 conflict between intra-eNodeB cells
4) Time synchronization with inter-eNodeB

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 199

 Action 11: Handovers Analysis

The impact of handover issues on transmission performance is as follows: 1) Throughput decreases if handovers cannot be
completed in time or ping-pong handovers are triggered. 2) Improper inter-frequency measurement decreases throughput.
3) The performance of X2-based handovers is superior to that of S1-based handovers. 4) In multi-band networking,
throughput decreases if UE migration is caused by handover parameter reconfiguration.

Factor Evaluation Criteria Involved KPI Factors

1) Improper configurations of
1) In comparison testing scenarios, DT data is analyzed by
Frequent handovers handover parameters or
following the instructions provided in the X solutions for DTs. HO Success
(including ping-pong policies
2) In deterioration scenarios, the number of handover Rate
handovers 2) RF optimization issues: serious
implementations increases by over 10%.
overlapped coverage
1) In comparison testing scenarios, DT data is analyzed by
following the instructions provided in the X solutions for DTs.
Delayed handovers,
2) Associated analysis is performed on every two handovers in L.HHO.NCell.Exe Faulty or inactive neighboring
no handovers, or
the event of deterioration in TopN cells to check whether the cAttOut cells
handover failures
number of handovers between any cell and its neighboring
cells is 0.
1) Improper configurations of
1) In comparison testing scenarios, DT data is analyzed by handover parameters,
Abnormal event A2 Inter-Freq HO
following the instructions provided in the X solutions for DTs. especially the threshold for
causing gap-assisted Success Rate
2) In deterioration scenarios, the number of inter-frequency event A2 measurement
measurement
handovers increases by over 10%. 2) MR function enabled on the
U2000

X2- and S1-based X2 HO Out

The proportion of X2-based handovers decreases. Alarming or removal of X2 links
handovers Success Rate

Reconfiguration of handover
Handovers of The number of inter-frequency handovers changes by over Inter-Freq HO parameters (for example,
multiband UEs 10%. Success Rate thresholds, handover priorities,
and MLB)

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 200

 Action 12: Transmission and TCP Analysis
Transmission or TCP problems mainly affect the volume of incoming traffic on the eNodeB, preventing the eNodeB to provide services at full capacity and
decreasing the throughput in traffic statistics.
Element Evaluation Criteria Involved KPI Factors
Any of the following criteria regarding the maximum throughput, FEGE.TxMeanSpeed (average transmission
average throughput, and total bandwidth of Ethernet during peak rate)
hours is met: FEGE.RxMeanSpeed (average reception
1) The proportions of the average uplink transmission rate (or rate)
downlink average reception rate) in the eNodeB's available VS.FEGE.TxMaxSpeed (maximum
Transmission Bandwidth limitation, which requires
transmission bandwidth exceeds 70%, and such proportions account transmission rate)
bandwidth telecom operators to expand
for 80% or higher in the busy hours for a whole week. VS.FEGE.RxMinSpeed (maximum reception
limitation transmission capacity
2) The proportion of the maximum uplink transmission rate (or rate)
maximum downlink reception rate) in the bandwidth allocated to the VS.FEGE.TxTotalBW (negotiated
eNodeB exceeds 85%, and such proportions account for 10% or more. transmission bandwidth)
3. The output of the DSP ETHPORT command indicates a throughput VS.FEGE.RxTotalBW (negotiated reception
of 100 Mbit/s, which means that the bandwidth for LTE is limited. bandwidth)
[Traffic statistics] The value of the Gtpu.RxDropBytes counter Issue that must be sent to Huawei
Gtpu.RxDropBytes
increases abruptly at the time when throughput decreases. headquarters for analysis
[IPPM traffic statistics] The value of the VS.IPPM.Forword.DropMeans
counter increases abruptly at the time when uplink throughput VS.IPPM.Forword.DropMeans
decreases. Packet loss, which must be explained
to telecom operators and require
[Traffic statistics related to active IP monitoring] The value of the telecom operators to check for
VS.BSTWAMP.Forward.DropMeans or VS.BSTWAMP.Forward.DropMeans transmission issues
VS.BSTWAMP.Backward.DropMeans counter increases abruptly at the VS.BSTWAMP.Backward.DropMeans
Packet loss
time when uplink or downlink throughput decreases.
during
transmission Packet loss on transmission NEs,
Severe packet loss can be monitored by using the ping command.
which requires engineers to locate
Various sizes of packets are used for testing (because some issues N/A
faulty NEs by running the ping
cause the loss of large packets but not small packets).
command
1) Faults in transmission optical
modules
The output of the DSP ETHPORT command indicates accumulated
N/A 2) Configuration inconsistency
CRC errors.
between the eNodeB and the peer
layer-3 MTU
Exceedingly long transmission delay,
[Traffic statistics related to IPPM and active IP monitoring] The value of which must be explained to telecom
Common
Transmission issues the VS.IPPM.Rtt.Means or VS.BSTWAMP.Rtt.Means counter is greater
VS.IPPM.Rtt.Means or
operators and require telecom
RTT delay VS.BSTWAMP.Rtt.Means
than 20 ms. operators to check for transmission
1. The transmission bandwidth check method is used only to check for congestion on the transmission bandwidth from the eNodeB to the first peer transmission device.
issues
2. Traffic statistics related to IPPM and active IP monitoring (first available in eRAN8.0) can be activated only when the license has been obtained and related features are activated. For
details, see IP Performance Monitor and IP Active Performance Measurement.
3. The DSP ETHPORT command is executed only to check the bandwidth negotiated between the eNodeB and the first peer switch. The command output reflects only part of the
transmission bandwidth information.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 201

 Action 13: Performing DTs
 In deterioration scenarios, If the deterioration cannot be resolved through the preceding actions, you are advised to perform DTs to
compare the difference in spectral efficiency before and after the deterioration. This is the last resort for performance evaluation.
 In comparison testing scenarios, DTs are mandatory in most cases (and are preferentially performed during issue demarcation). DTs
are used to obtain the configurations of Huawei competitors' air interface parameters, and the differences in spectral efficiency,
coverage (RSRP/SINR), handover-caused service drops, and transmission performance. In addition, DTs are used as reference for
evaluating actual UE throughput.
 The Probe and a UE equipped with a QualComm chip are used to inject packets at the full rate according to FTP. Then, the following
KPIs are analyzed:
RSRP
SINR

Throughput is limited possibly

Spectral efficiency due to transmission bandwidth
limitation.

For details about the methods, procedures, and tools related to DT data analysis, see X Solutions for PS Data Transmission
Optimization in the LTE Network (Drive Tests) (Click).

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 202

 Contents

1 Background

2 Standard Action for Performance Improvement

3 Analysis Method

4 Tools Introduction

5 Case

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 203

 Common Data Sources and Tools for Locating Traffic Statistics Issues (1)

Action 1: Check KPI Action 2: Identify the Action 3: Check Action 4: Check Action 5: Check Action 6: Check
definitions. issue scope and external events and faults and alarms. known version parameters.
demarcate issues. historical operations. issues.

KPI definitions on Traffic statistics eNodeB operation logs, alarm logs, fault logs, or BRD Release notes eNodeB configuration
Huawei OSS collected by the U2000 logs file
Source data KPI definitions on Traffic statistics Probe log
Huawei competitors' collected by the PRS QXDM log
OSS
Differences in KPI OMSTAR/FMA/
definitions between QCAT/Probe
Huawei and its
competitors

N/A U2000 or FMA N/A OMSTAR/FMA/

QCAT/Probe
Tool

1. KPI calculation 1. Issue scope and Fault occurrence time, abnormal operations, abnormal Version changes 1.Differences in air-
formula check results TopN sites alarms, and fault information interface parameters
2. KPI value check 2. Associated KPI 2.Check results of
Output

results analysis results consistency between

network parameters
3.Whether parameters
are set to their
optimal values

Link Link Link Link Link Link

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 204

 Common Data Sources and Tools for Locating Traffic Statistics Issues (2)

Action 7: Analyze Action 8: Analyze Action 9: Analyze Action 10: Analyze Action 11: Analyze Action 12: Analyze Action 13: Perform
the traffic model. resources and coverage and the channels and handovers. transmission and DTs.
capacity. coding over the air interference. TCP.
interface.

S1 interface Traffic statistics Traffic statistics Files of Wireshark Probe or QXDM

Source data
tracing data of collected by the collected by the packet capturing logs for DTs
TopN sites Traffic statistics U2000 U2000 TMF files of IFTS
collected by the Traffic statistics Traffic statistics tracing data
U2000 collected by the collected by the
Traffic statistics PRS PRS
collected by the PRS RSSI or
interference
tracing data

FMA TranExpert/ QXDM, QCAT,

Wireshark Probe, or
U2000 Assistant_Extend
Tool

1. Identification 1. Identification 1. Whether 1. Whether 1. Trend of the 1. Problematic 1. DT-based

results of true results of true coverage channels are handover transmission NEs coverage
and false and false deteriorates abnormal success rate 2. Packet loss during analysis results
Output

capacity issues capacity issues 2. Causes of 2. Interference 2. Trend of the transmission 2. DT-based
2. PRB usage MCS index, within the number of 3. Packet disorder performance
and CCE IBLER, and system handovers during transmission analysis results
usage DTX changes 3. Interference 4. Transmission 3. Transmission
from eternal bandwidth limitation bandwidth
systems limitation
analysis results

Obtain the Assistant Extend and related operation guide from Link.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 205

 Efficiency Improvement for Transmission Issue Analysis Tools (1)
[FMA Tools] Tools > Parameter check > PS Performance Parameter check
Two new options are added for PS parameter check: Problem Scenario and Related indicator.

[FMA Tools] A new function is introduced to analyze the proportions of KPIs based on PDF traffic statistics.
The efficiency of analyzing the proportions of KPIs, such as the CQI and MCS index, improves significantly.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 206

 Efficiency Improvement for Transmission Issue Analysis Tools (2)

[FMA Tools] Tools > Parameter check > PS Performance Parameter check

The FMA supports one-click

export of all associated KPIs
required in X solutions.

[FMA Tools] CellDT/IFTS TTI analysis tool (for Huawei R&D and
GTAC engineers only)

Defined rule templates

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 207

 Contents

1 Background

2 Standard Action for Performance Improvement

3 Analysis Method

4 Tools Introduction

5 Case

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 208

 Case 3: Abrupt Decrease in the Cell's Average User Throughput Due to
Transmission Faults (1)
[Problem Description]
Site Information Project B; LTE FDD; commercial site
eNodeB Version DBS3900 V100R004C00SPC220
UE Version E398s commercially used in site B
Problem According to customers, the downlink traffic throughput in site A decreases abruptly(the average
Description user throughput decreases from 8 Mbit/s to 4 Mbit/s)

Problem Analysis:

Step 1: Identifying and segmenting the problem

Action Prerequisite Conclusion Status

Action 1: Checking test
None The check result shows that traffic KPIs are valid. OK
rules and KPI definitions
The problem occurs in a single cell.
Action 2: Identifying the
The analysis result shows that the cell traffic and full-load throughput
Problem Scope and
None decrease and that the number of discarded packets during transmission OK
Separating the Problem by
increases with the transmission throughput decrease. You are advised to
Segment
check transmission devices.
Gtpu.RxDropBytes traffic trend Cell's average user throughput change trend

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 209

 Case 3: Abrupt Decrease in the Cell's Average User Throughput Due
to Transmission Faults (2)

Step 2 Check basic factors. Check for transmission alarms based on traffic KPIs.

Action Prerequisite Conclusion Status

The check result shows that the SCTP link clear alarm is generated
Action 4: Check parameters. None before this problem occurs. According to frontline personnel, the customer OK
reconstructed cell transmission.
Action 5: Checking for Known Issues None No Version defect is detected. OK
Compare configurations of normal and abnormal sites. No abnormal
Action 6: Check parameters. None parameter settings are found. Service parameters are modified before OK
and after deterioration.

Step 3: Analyze the problem.

Action Prerequisite Conclusion Status

Conduct tests in cells Packet capturing results shows that massive packets are in disorder on the
Action 11: Analyzing
based on analysis transmission side. Transmission problems are located. In this case, you OK
Transmission and TCP
results of traffic KPIs. need to encourage the customer to check transmission.

Packet capturing analysis results in cells

Step 4 Check whether problems are
solved.

The customer modifies the parameters of third-party transmission

devices before cell performance deterioration. After the modified
parameters are recovered, the cell throughput returns to normal.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 210

 [Comparison Testing Case] Throughput on Huawei Network at Site
T Lower Than That in City A (1)
[Problem Description]
Site Information Site T (in commercial use) with a bandwidth of 10 Mbit/s; Vendor: Huawei/Huawei competitor
eNodeB Version DBS3900 V100R007C00SPC110
UE Version Smart phones such as Samsung and iPhone UEs
Problem The telecom operator complains that throughput on Huawei network at the site is lower than that in
Description city A and needs to be improved.

Vendor City DL Throughput

L 18.53
Symptom Huawei competitor
Ch 18.23
M 14.26
Huawei
G 12.68

[Problem Analysis]
Step 1 Identify and demarcate issues.
Prerequisit
Action Result Status
e
1) The mapping of KPI calculation formulas between Huawei and city A is correct.
Action 1: Check
None -----OK OK
KPI definitions.
2) Raw traffic statistics about Huawei network and city A are correct. -----OK
1) According to DTs, the average SINR is 11 and TopN cells with poor CQI values are
identified on Huawei network. The average SINR reaches 16 E network.
2) TopN cells: Check the CQI, rank 2 proportion, transmission performance, and
whether TopN cells can be identified.
Action 2:
3) Resources and capacity: For Huawei network, a large number of UEs are served
Identify the
by each site during peak hours, and the percentage of sites serving over 50 UEs
issue scope and None Abnormal
reaches 30%. For E network, the percentage of sites serving over 40 UEs reaches
demarcate
only 10%, and almost no site serves 90 or more UEs.
issues.
4) Transmission: According to traffic statistics and DTs, Huawei network encounters
serious transmission problems, which decrease transmission quality. In city A,
transmission quality is better, and the number of scheduling attempts in each cell
is greater than 900.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 211
 [Comparison Testing Case] Throughput on Huawei Network at Site
T Lower Than That in City A (2)
Resource and capacity
comparison On Huawei network, the throughput increases rapidly to 18
The number of UEs on Huawei network is
Mbit/s after the sites serving over 50 UEs are excluded.
twice that in city A.
The proportion of sites serving over 50 UEs on
Huawei network is 20% higher than that in city A.

Standard Standard
City Average Maximum Minimum Average Maximum Minimum Transmission
Deviation Deviation
comparison
City A 16.59 30 -5 6.68 -88.76 -53.75 -113.69 11.79
Throughput is limited
HW\\ M 11.59 29.95 -15.5 7.38 -85.65 -55.6 -116.66 9.58 possibly due to insufficient
transmission bandwidth
provision.
The average SINR in Huawei Morelia
area is 5 dB lower than that in city A.

According to the maximum

Coverage
receive throughput in traffic
comparison
statistics collected from Huawei
network, the maximum
throughput in 50% of the sites
is lower than 70 Mbit/s.

The average number of scheduling attempts on

Huawei network is lower than that on the competitor's
network. According to the SINR vs DL Grant curve,
more points with fewer scheduling attempts are
detected at places of short distances to the cell center.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 212

 [Comparison Testing Case] Throughput on Huawei Network at Site
T Lower Than That in City A (3)

Step 2 Check basic factors.

Action Prerequisite Result Status
Action 3: Check events
Not performed for
and historical NA
comparison testing
operations.
Action 4: Check
None No alarms affecting large-scale transmission are detected. OK
alarms.
Use the OMStar to check parameters on the entire network. The
Action 5: Check
None settings of some feature parameters are inconsistent, and these Abnormal
parameters.
parameters are not set to their optimal values.
Step 3 Analyze the problem.
Action Prerequisite Result Status

Action 11: Analyze Performed based on traffic The spectral efficiency of Huawei is better than that of the
OK
coverage and coding. statistics analysis results
competitor.

Step 4 Check whether the problem has been

solved.
The spectral efficiency
of Huawei is better than The transmission performance, coverage, and UE load on Huawei
that of the competitor. network are worse than those in city A. In addition, parameter settings
are inconsistent and parameters are not set to their optimal values on
Huawei network. However, the spectral efficiency of Huawei is similar
to that of the competitor. In summary, the throughput in traffic statistics
collected from Huawei network is lower than that collected in city A. To
improve throughput on Huawei network, you need to expand the
transmission capacity, optimize coverage and TopN cells, and set
parameters to their optimal values.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 213

 Appendix: Formula for Calculating the TDD User Rate

 DL User PDCP layer average throughput (Mbit/s)

= L.Thrp.bits.UL/(L.Thrp.Time.UL x 1000 x Coefficient)-----not protocol-defined
= (L.Thrp.bits.DL - L.Thrp.bits.DL.LastTTI)/(L.Thrp.Time.DL.RmvLastTTI x
Coefficient)-----protocol-defined
 UL User PDCP layer average throughput (Mbit/s)
= L.Thrp.bits.UL/(L.Thrp.Time.UL x 1000 x Coefficient)-----not protocol-defined
= (L.Thrp.bits.UL - L.Thrp.bits.UE.UL.LastTTI)/(L.Thrp.Time.UE.UL.RmvLastTTI x
Coefficient) -----protocol-defined
 For details, see the following table.
Subframe Ratio SA Special Subframe Proportion Downlink Coefficient Uplink Coefficient
1 (2:2) 5 (3:9:2) 5/2 5/2
1 (2:2) 7 (10:2:2) 5/3 5/2
2 (3:1) 5 (3:9:2) 5/3 5
2 (3:1) 7 (10:2:2) 5/4 5

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 214

 Contents
 LTE PS Service(Drive Test)
 LTE PS Service(Traffic
Statistics)
 LTE PS Service(Ping Delay)

Page215

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 215

 Contents

1 Introduction to Ping Delay

2 Optimization Methods of Ping Performance

3 Impact Factors and Required Actions

4 Appendixes and Cases

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 216

 Introduction to the Ping Delay
The Packet Internet Groper (PING) works based on the uniqueness of IP addresses of network
devices: It sends a packet to the destination IP address and requests a packet of the same size
from the peer to determine whether two network devices are properly connected as well as the
delay between the network devices. In this way, you can determine the end-to-end delay of a
network path.

S-GW/P-GW Ping server

eNodeB

The LTE network has certain requirements for the transmission delay to ensure sound network
performance. For example, HTTP DL/UL throughput, handover, and CSFB are all delay-sensitive.
On the other hand, many operators consider ping delay as an important indicator for evaluating
the end-to-end user experience of networks. The existence of the air interface also contributes to
the ping delay to a certain extent.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 217

 Main Factors Affecting the Ping Delay
Classification of ping delay problems

Measurement
method or tool
problems
Transmission 25%
problems above
the RAN
53%
Transmission problems above the RAN:
① Poor access network quality (microwave)
Parameter set-
② Improper server routing or transmission
Measurement tool and method ting problems (multiple hops)
22%
confirmation: ③ Long server delay (such as a server
① Measurement tool connection deployed outside China)
mode and tool model ④ Improper server configurations or poor
② Ping packet size, packet server performance (for example, packet
transmission interval, and loss and large jitter)
destination IP address

Air-interface performance (parameter settings)

① Preallocation configurations (SR and UL Grant)
② DRX configurations (long-period waiting time)
③ Other parameter settings (whether to fragment RBG allocation policies)

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 218

 Decrease of Ping Delay
Basic check is required before ping tests to identify whether there are other factors affecting the
ping delay and whether the current configurations are optimal for the ping delay.

Action: Check parameter settings. Optimize parameter

Check whether settings of preallocation parameters, DRX settings.
parameters, and the SRI period are optimal.

Action: Check external events, alarms, and known

issues.

Check key alarms during test and evaluate impacts of known

issues.
Eliminate negative
impacts.
Action: Check transmission above the S1 interface.

Run ping to identify the ping delay on the S1 interface during

loopback from the eNodeB to the UGW.

Action: Confirm the measurement tool and method. Adopt a correct

measurement method.
Check measurement tool and method normalization.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 219

 Impact Factors and Required Actions
Three steps are summarized in this section: problem identification, basic element check,
and inference analysis. Eight required actions are involved. The following figure shows the
relations between the three steps and actions.
LTE delay problem classification and evaluation methods

Tools & Methods Action 1: Confirm the measurement tool and method.

Action 2: Check external events and alarms.

Impact factors and required Basic element check
Action 3: Check parameter settings.
actions for ping delay problem

Action 4: Locate the problem by segment.

Action 5: Analyze the delay from the UE to the eNodeB.

Inference analysis
Action 6: Analyze the transmission delay from the
eNodeB to the server.

Appendixes

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 220

 Back
Action 1: Confirm the Measurement Tool and Method Abstract

Using an incorrect method or tool will result in poor ping test performance or inaccurate test results. Therefore, the measurement tool and
method must be confirmed according to the following rules:

Method
Tool

UE Portable PC Software
Destination Number of Ping packet
Portable PC server/IP ping tests size
Test form: test in the
Types: data cards and performance: CPU
smart devices resources and memory
CMD command prompt address
window delivered with Different ping packet
Connection mode: Impacts of background Number of ping
the system, test using Different ping sizes: causing
local test, access programs: occupation of tests: required to be
the software embedded servers: Different differential air-
through the USB, or CPU resources and greater than or
with the ping function, or destination IP interface
access through the network bandwidth equal to 50 to
test using HRPing addresses result in performance and
radio access point resources prevent poor results
Different ping options, different IP routes. fragmentation
(AP) Statistics are inaccurate due to air interface
such as the interval and problems. As a
Different connection and the packet and transmission
protocol packet header result, final results
modes cause different transmission capability is fluctuation.
size, can be configured are affected.
transmission delays. insufficient when ping is
for different ping tools.
used every 5 ms.
* Some software, such as Speedtest, does not calculate the delay in the same way as the ICMP-based ping utility does. Therefore, the troubleshooting using such software
is different from that using the ping utility.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 221

 Back

Action 2: Check External Events and Alarms Abstract

External event check Alarm check Known issue check

Operation log check: Check whether Alarm check of problematic cells: Check
current sites are subject to related whether related alarms exist. Analyze whether the problem symptom is the
operations. same as the symptom of precaution problems
or that of resolved problems in later versions.
Alarm check of neighboring cells: Check
Operation check of other NEs: Check
whether changes of the number of UEs
whether other NEs are subject to
are caused by alarms in neighboring
configuration changes, such as upgrade
cells. For problems in upgrade scenarios, check the
and cutover.
release notes to find suspicious version
changes.
Impact check of large events: Check Alarm check of other NEs: Check alarms
whether heavy-traffic scenarios, such as existing on related NEs.
gathering, exist on site.

Input data source: Entire-network alarm logs and Release notes

operation logs obtained on the U2000
P&R notices

FMA Attachment 03 Data Transmission (Ping Guide to avoiding problems on

Delay) Parameter & Alarm Checklist the live network

Determine the problem scope and find characteristics of the problem to facilitate troubleshooting.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 222

 Back
Action 3: Check Parameter Settings Abstract

Parameter setting check involves the following aspects:

Parameter setting check on the eNodeB:
Preallocation and DRX parameters in all eNodeB-related parameters directly affect the ping delay. Therefore, pay attention to these parameters when checking parameter settings. For details
about other parameters, see Attachment 03 Data Transmission (Ping Delay) Parameter & Alarm Checklist. In addition, parameters of neighboring cells or neighboring sites also need to be
checked.
Parameter Name Impact

PreAllocationSwitch/SmartPreAllocationSwitch Whether to enable preallocation determines whether to trigger UL Grant through the SR. The SR period waiting time can decrease in the event of preallocation.

PreallocationSize/PreallocationSizeForSparse The number of scheduling times can decrease if preallocation is mapped with the ping packet size.
PreallocationMinPeriod/PreAllocMinPeriodForSparse The preallocation period determines the scheduling waiting duration of uplink packets.
SmartPreallocationDuration/SmartPreAllocDuraForSparse Preallocation gains can be obtained every time ping is performed if the preallocation duration is mapped with the ping task period.
If DRX is enabled, the scheduling waiting time needs to be woken up when the UE sends uplink data. Data cannot be transmitted until OD if DRX is in a silent
DRXPARAGROUP
period in the downlink.
LongDrxCycle This parameter determines the duration of waiting OD of downlink packets when the downlink packets are transmitted in the sleep time of DRX.

The OMStar can be adopted for query of entire-

Obtaining of local-site/local- network parameter settings in batches and the
cell core parameter settings FMA is recommended for check of parameter
OMStar FMA settings at individual sites or a single site.
Check of other vendors' air-interface parameters:
When comparing parameter settings provided by Huawei and other vendors, first obtain parameter settings of other vendors because other vendors' parameter settings generally need to be
obtained through the operator or the diagnostic test during the drive test (for the diagnostic test method, see the introduction of the air interface parameter extraction function). After obtaining
some of the parameter settings of other vendors, compare them with Huawei's parameter settings for the standard interfaces to find the differences in parameter settings that may affect the
ping delay.

Data collection Data analysis Data review

Obtaining of parameter
settings of other vendors
through the diagnostic test
Probe FMA QCAT

The ping process is an E2E process. Therefore, besides parameters of the eNodeB, other parameters, such as those of transmission equipment, CN equipment, and servers, also need
to be checked. Because the equipment is not always provided by Huawei, cooperation and confirmation with the operator are required.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 223

 Back
Action 4: Locate the Problem by Segment Abstract

Ping loopback RTT

Problem location by segment
by IFTS 149 tracing

Perform this action when the problem needs to be located based on inference and analysis. First, locate the problem by segment and determine whether the
delay problem is caused by delay of the air interface below the S1 interface or the interfaces above the S1 interface.
 Procedure:
① Use the ping function to obtain the delay of the entire loopback.
② Calculate the delay from the eNodeB to the server by IFTS 149 tracing (tracing data can be directly obtained from the network side). For the detailed method of
collecting IFTS 149 tracing data, see Attachment 04 Analysis Guide for LTE 149 Trace Log. In addition, you can also run ping directly to test the network
communication from the eNodeB to the UGW.
③ Obtain the delay from the UE to the eNodeB by deducting the total delay by the delay from the eNodeB to the server. Obtain the total ping delay and the loopback
delay from the eNodeB's PDCP layer to the server's application layer by IFTS 149 tracing. Then deduct the total ping delay by the loopback delay to obtain the
delay from the UE to the eNodeB. In this way, it can be confirmed whether the problem is related to the air interface or above the air interface.

UE-to-eNodeB Delay Baseline eNodeB-to-Server Delay (Internal Network) eNodeB-to-Server Delay (External Network)
<15 ms < 5 ms Depending on the network environment of the server
④ Compare the delay from the eNodeB to the server and that from the UE to the eNodeB with baseline values to identify exceptions.

Long delay from the UE to the eNodeB Action 5: Analyze the delay from the UE to the eNodeB.
Problem segmentation result
Action 6: Analyze the transmission delay from the eNodeB
Long delay from the eNodeB to the server
to the server.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 224

 Action 5: Analyze the Delay from the UE to the Back

eNodeB Abstract

Perform action 5 if the segmentation results of action 4 show that there is a large delay from the UE to the eNodeB.
Segment the delay from the UE to the eNodeB, and measure the delay of each segment to locate the segment where the delay problem
occurs.

Above the S1
interface

Air interface

Application layer
of the UE
Ping delay

› Check whether preallocation configurations (including the period, data volume, and duration) meet the requirements of the ping
Analysis of the uplink
model when preallocation is enabled.
packet delay
› Check the current user's SR period (which can be obtained from signaling for RRC connections) when preallocation is disabled.

Analysis of the › Check whether DRX is enabled currently and whether settings of LongDrxCycle affect transmission of downlink packets.
downlink packet delay › Check whether congestion occurs due to heavy traffic based on traffic statistics.

› The radio conditions determine the air interface's encoding capability, which is a key factor in determining whether a ping packet
Coverage and encoding will be fragmented.
efficiency › The network coverage and interference are key factors in determining whether retransmission over the air interface will occur.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 225

 Action 6: Analyze the Transmission Delay from the eNodeB to Back
the Server Abstract

The delay caused by transmission above the air interface can be obtained by IFTS 149 tracing. However, the delay of transmission
above the air interface may involve multiple NEs, which also involves operator equipment and equipment provided by other vendors.
Therefore, cooperation is required during the troubleshooting. This action helps locate problems on the transmission side, but the root
cause needs to be located or the problem needs to be resolved under cooperation with the operator or the vendor of the malfunctioning
NE.
 Procedure:
Transmission above the air interface consists of the following three segments:
(1) eNodeB to UGW
(2) UGW to Internet gateway
(3) Internet gateway to the server
The three segments are as follows:
(4) Access network
(5) Operator's backbone network
(6) Public Internet
If the server is an operator's internal server, the UGW directly connects to the server.
Segment 1 Segment 2 Segment 3
Mirror
server

S1-U
SGi

UE+portable PC eNodeB S9312 UGW NE40E Server on the

public network

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 226

 Back
Introduction to Attachments Abstract

Name Description

Attachment 01 Technical Guide to PS Data Transmission (Ping Delay) Provides detailed guidelines for ping delay optimization and
Performance Optimization in the LTE Network V8.1.1 problem location step by step.

Attachment 02 LTE PS Data Transmission (Ping Delay) Problem Provides the template of a standard analysis report for ping
Analysis Report (Template) delay problem location.

Attachment 03 Data Transmission (Ping Delay) Parameter & Alarm Lists key parameters and alarms related to the ping delay on the
Checklist eNodeB.

Describes how to perform IFTS-based or user-plane-based 149

Attachment 04 Analysis Guide for LTE 149 Trace Log
data tracing and analysis.

Attachment 05 Guide to Capture Packets over the S1 Interface During Describes how to capture packets over the S1 interface during
Mirroring on BBU mirroring on the BBU.

Attachment 06 HRPing Installation Describes how to install and use HRPing.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 227

 Back
Introduction to Cases Abstract

No. Case Name Symptom Cause

Long transmission delays above IP addresses allocated to UEs by the UGW are different,
Ping delays of individual sites are
S1 interfaces at some sites, resulting in different IP routes for destination IP addresses.
1 longer than those of other sites
causing ping delays not to meet As a result, ping delays are long due to improper
during acceptance.
the requirements configurations of some routes.

Slow UE wake-up after DRX is The test ping delay after DRX is The wake-up duration from the DRX in a silent period to
2 enabled, causing a long ping enabled significantly becomes that in activation is long, resulting in a long delay. This
delay long. problem is a TopN UE compatibility problem.

A long delay packet may occur

RLC packet loss is caused by PDCCH false detection.
aperiodically when 3G
3 Unstable delay jitter Check whether jitter is proper based on configurations of
transmission services are
the RLC reordering timer and status report timer.
performed on the LTE network.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 228

 Thank you
www.huawei.com

Copyright©2011 Huawei Technologies Co., Ltd. All Rights Reserved.

The information in this document may contain predictive statements including, without limitation, statements regarding the
future financial and operating results, future product portfolio, new technology, etc. There are a number of factors that could
cause actual results and developments to differ materially from those expressed or implied in the predictive statements.
Therefore, such information is provided for reference purpose only and constitutes neither an offer nor an acceptance.
Huawei may change the information at any time without notice.