Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Contents
Figures
Tables
Abstract
The document serves the optimization of PS service problems in large networks. It describes problem
evaluation, data collection, and methods for analyzing problems.
DT Driver Test
SF Spreading Factor
UE User Equipment
NE Network Element
1. Introduction
Title Description
Chapter 1 Introduction
Chapter 6 Cases
Chapter 7 Summary
Chapter 8 Appendix
In WCDMA networks, besides traditional conversational service, data service is growing with
features. It has a significant perspective.
The indexes to indicate the performance of WCDMA data service includes:
• Access performance
It is reflected by the following indexes of data service:
• Success rate of RRC setup
• Success rate of RAB setup
• Success rate of PDP activation
• Call drop rate of PS service
• Throughput
• Delay
There are access delay and the service interruption delay caused by HHO.
This document addresses on problems in PS service optimization, such as access problems, data
transfer failure, low throughput of data transfer, unstable rate of data transfer, and interruption of data
transfer. It describes the method to analyze and solve DT/CQT problems. In addition, it describes the
flow for processing access failure and data transfer failure problems in optimization of PS throughput.
• BSC6800V100R006C01B064
• BTS3812E V100R006C02B040
When refer RRC arithmetic and product realization default is RNC V16, refer V17 it will be labeled.
The HSUPA problem analyses, description of MML command and product function are based on the
following product versions:
• BSC6800V100R008C01B082
• DBS3800-BBU3806V100R008C01B062
1. Requirements by
DT/CQT on PS
throughput
Index Service Reference Reference test method
• Uplink RTWP,IUB
bandwidth resource
and UE TX power
are not restricted.
• Pilot power
33dBm RSCP>=-
100dBm;
• Single subscriber in
unloaded
conditions
• set MTU 1500
bytes , set PDU =
336 bits
• In UE QoS profile in
HLR,
MBR=2Mbps,
200kbps~400kbps
service type is
(cell edge) Background/Intera
ctive
• The data resource of
FTP must make
sure that upload
can get the fast rate
in the wire
connection
conditions.
• Get the fast rate ,
combine UE
capability , get
APP rate in the
conditions of
uplink RTWP,IUB
bandwidth are not
restricted.
3. Data Collection
Title Description
3.2 DT/CQT
3.3 Others
There are two major methods for evaluating PS throughput: traffic statistics and DT/CQT.
1. Traffic Statistics
For collecting traffic statistics data, see W-Equipment Room Operations Guide.
2. DT/CQT
To obtain DT/CQT data, use the software Probe, UE, scanner, and GPS are involved. Obtain the
information output by UE, such as:
• Coverage
• Pilot pollution
• Signaling flow
• Downlink BLER
• TX power of UE
Based on the measurement tracing on RNC LMT, obtain the following information:
• Uplink BLER
• Downlink code transmission power
• Downlink carrier transmission power
• Signaling flow at RNC side
By the DT processing software Assistant, analyze comprehensively the data collected by Probe in
foreground DT and tracing record on RNC LMT.
3.2 lists the major parameters to be collected in DT/CQT.
1. Major parameters
to be collected in
DT/CQT
Parameter Tool Effect
In PS service test, to reduce the impact from TCP receiver window of application layer, using multi-
thread downloading tools like FlashGet is recommended. Set the number of threads to 5. For uplink
data transfer, start several FTP processes.
For the detailed test and operation methods of DT and CQT, see W-Test Guide. For detailed operations
on LMT, see W-Equipment Room Operations Guide.
3. Others
After finding problems by traffic statistics, DT/CQT, and subscribers' complaints, analyze and locate
problems with DT/CQT and the following aspects:
• RNC CHR
• Connection performance measurement
• Cell performance measurement
• Alarms on NEs
• States of NEs
• FlashGet
• DU Meter
3.3 lists the tools for collecting data.
1. Tools for
collecting data
When analyzing data with previous tools, engineers need to combine several data for analysis. For
example, in network maintenance stage, if some indexes are faulty, analyze some relative data such as
performance statistic, alarm data, and CHR. According to the level of problems, perform DT/CQT in
cell coverage scope; trace the signaling of single subscriber and conduct connection performance
measurement on RNC LMT.
If there are problems in DT/CQT, analyze them based on traffic statistics and alarms.
Title Description
1. Measured items
related to PS
throughput in
overall
performance
measurement of
RNC
Measured Major indexes Effect
item
4.1 lists the measured items related to PS throughput in cell performance measurement.
2. Measured items
related to PS
throughput in cell
performance
measurement
Measured Major indexes Effect
item
Cell measurement/cell Collect cell level data ,such as: • Take statistics
RLC measurement • Valid RLC data of valid data
rate Downlink rate at RLC
service layer
• Number of • The
In cell performance measurement, HSDPA part is added, and other indexes are the same as that of
R99. Some traffic statistics indexes corresponding to HSDPA services are not added to RNC traffic
statistics.
Table 4-3 lists the measured items related to HSDPA throughput (cell measurement).
3. Measured items
related to HSDPA
throughput (cell
measurement)
Measured Major indexes Effect
item
Table 4-4 lists the measured items related to HSDPA throughput (cell measurement).Measured items
4. related to HSUPA
throughput (cell
measurement)
Measured item Major indexes Effect
Measured item
Cell ”HSUPA.CELL” include the Know the HSUPA
measurement/HSDPA PI of service setup , release throughput and number
service measurement and the number of EDCH of subscribers in cell
handover
5. Other measured
items related to
throughput
Measured Major Effect
item indexes
Analyzing traffic statistics data is mainly based on overall performance measurement of RNC and cell
measurement. Analyzing RNC-level data addresses on evaluating and analyzing performance of entire
network. Analyzing cell-level data addresses on locating cell problems. Other measured items like Iu
interface and transmission help engineers to analyze problems in the whole process of performance
data analysis.
In actual traffic statistics analysis, evaluate the indexes of entire network and then locate cell-level
problems.
The cell-level traffic statistics data is obtainable from cell measurement/cell throughput of various
services, and volume measurement, including the average throughput and total volume of various
services.
Select a representative service in the network, or a continuous coverage service. Analyze the average
throughput of each cell for the selected service by Nastar and sort the cells by cell throughput. Select
the top N worst cells for analysis.
The cells with 0 PS RAB setup request is excluded from sorting alignment, namely, the total number
of the four indexes listed in 4.2.2 is 0. Such cells are considered as having no PS service request, so
they are excluded from sorting alignment the worst cells for PS throughput.
1. Indexes to judge
whether a cell has
For the worst cell, check that they are not with access, call drop, and handover problems. Then analyze
the cell performance from cell measurement/traffic measurement, cell measurement/cell algorithm
measurement, and cell measurement/cell RLC measurement.
1 4.2.2 describes the cell measurement/cell algorithm measurement analysis.
2. Cell
measurement/cell
algorithm
measurement
analysis
Index Meaning Analysis Solution
3. Analysis of cell
performance/Iub
interface
measurement
Index Meaning Analysis Solution
4. Cell
Measurement/Cel
l RLC
Measurement
Analysis
Index Meaning Analysis Solution
The causes of high RLC retransmission rate and PDU packet dropping rate are:
To confirm weak coverage problem, perform DT/CQT and analyze CHR as below:
Title Description
WCDMA PS service data transfer problems include the following three types in terms of phenomena:
1. Flow for
analyzing DT/CQT data
1. Access Failure
There are two ways to use PS services:
2. UE as the Modem of PC
5.1.2 shows the flow for analyzing access problem when the UE serves as the modem of PC.
Trace the NAS and RRC signaling in Probe or trace the signaling of single subscriber on RNC LMT.
Analyze the problem by comparing it to the signaling flow for standard data service. For the signaling
flow for standard data service, see the senior training slides of RNP: W-RNP Senior Training-
Signaling Flow.
5.1.2 shows the signaling flow of successful setup of a PS service in Probe.
4. Signaling flow of
successful setup of a PS
service in Probe
DCH bearer
5.2.1 shows the flow for analyzing RAN side problem about disconnection of service plane for DCH
bearer.
3. Connection Performance
Measurement-Downlink
Throughput and
Bandwidth window
In 5.2.1,
• The bandwidth shown is the bandwidth assigned for UE by system.
• The DLThroughput is the actual throughput of downlink data transfer.
Monitor the variation of access layer rate and non-access layer rate of
uplink and downlink data transfer for the current connection. This helps
analyze the functions of dynamic channel configuration and variation
features of service source rate.
• If the uplink throughput is 0, the uplink may be disconnected.
• If the downlink throughput is 0, the downlink may be disconnected.
When the RNC DCCC function is valid, distinguish the variation of
bandwidth caused by DCCC.
If the problem is still not located after previous operations, collect the data
packets received and sent at RNC L2 and by GTPU by using the tracing
tool RNC CDT. This helps judge whether the disconnection of subscriber
plane is in uplink or downlink, at CN side or RAN side.
Further
Check problems at the CN side according to analysis of problems at CN
side in 5.2.2.
Refer to Comparing Operations and Analyzing Problem. Change each part
and compare the operations. This helps reduce the scope of the problem.
Feed back the problem.
HSDPA Bearer
The HSDPA feature of cell is activated, The UE supports HSDPA. The rate requested by UE or the
subscribed rate is higher than HSDPA threshold for downlink BE service (for BE service) or HSDPA
threshold for downlink streaming service (for streaming service). When the PS services are carried by
HSDPA, follow the steps below:
4. HSDPA parameters in
Probe
• LAN
Use FTP or HTTP service on a PC connected to LAN, and check whether
the service is available. In addition, verify the user name and password of
the connected user.
• Other radio access network under the same CN
If different 3G access networks under the same CN sets up PS service or
sets up PS service from the GRPS network, check whether the service is
normal.
After previous checks, if the service servers work normally, focus on the problems at RAN side for
analysis. If the service servers are abnormal according to previous checks, ask the on-site engineers of
CN PS domain to solve the problem.
The IP address for visiting FTP and HTTP service servers by LAN is different from that for visiting
service servers after the UE sets up wireless connection. For details, turn to on-site engineers of CN
PS domain.
• RAN side
• CN equipment
• Applications and service software
The applications and service software problems are contained in the CN side problems. 5.3 shows the
flow for analyzing poor performance of data transfer.
1. Comparing
operations and
analyzing
problem
Order Operation Result Analysis
After the approximate scope of problem cannot be located after previous checks, analyze it as a
problem of data transfer at RAN side and CN side.
• Subscribed rate
• Bandwidth at Iub interface
• Maximum rate supported by RNC, NodeB, GGSN, and SGSN.
When there are multiple subscribers, besides previous factors, the scheduling algorithm used by
NodeB and number of HS-SCCH configured to cell affects the rate of data transfer.
An HSDPA subscriber works as below:
• The UE reports CQI on HS-DPCCH. The NodeB obtains the CQI of UE's
location.
• The scheduling module inside NodeB evaluates different subscribers by channel
conditions, the amount of data in cache for each subscriber, the last serving
time. It then determines the HS-DSCH parameters.
• The NodeB sends HS-DSCH parameters on HS-SCCH, and after two slots it
sends data on HS-DSCH.
• The UE monitors HS-SCCH for information sent to it. If there is any schedule
information, it starts receiving HS-DSCH data and buffers them.
• According to HS-SCCH data, the UE judges whether to combine the received
HS-DSCH data and data in soft buffer.
• The UE demodulates the received HS-DSCH data, and send the ACK/NACK
message on uplink HS-DPCCH according to CRC result.
• If the NodeB receives the NACK message, it resends the data until it receives
the ACK message or reaches the maximum retransmission times.
In the DT tool Probe, out of consideration for multiple subscriber scheduling and retransmission at
MAC-HS layer, there are three rates at MAC-HS layer:Scheduled Rate Served Rate MAC Layer
Rate.
NE Alarms
When the performance of data transfer for PS services is poor, analyze the NodeB and RNC alarms.
The clock alarms, alarms on transport code error, and transmission interruption may lead to fluctuation
of PS data. For querying NodeB and RNC alarms, see W-Equipment Room Operations Guide.
You can also check the information like reported CQI in the WCDMA HSDPA Link
Statistics window in the DT software Probe. If no information is in the window, the service must be
carried on DCH, as shown in 5.3.4.
If the service is not set up on HSDPA channel, it will automatically be set up on DCH. Now the
service rate is the rate of R99 service, usually equal to or smaller than 384 kbps.
If it is confirmed that the service is not set up on HSDPA channel, analyze it from the following
aspects.
1. Relationship
between CQI and
TB size when the
UE is in category
11–12
CQI Transpor Numbe Modulatio Reference
value t Block r of n power
Size HS- adjustment
PDSCH D
1 137 1 QPSK 0
2 173 1 QPSK 0
3 233 1 QPSK 0
4 317 1 QPSK 0
5 377 1 QPSK 0
6 461 1 QPSK 0
7 650 2 QPSK 0
8 792 2 QPSK 0
9 931 2 QPSK 0
10 1262 3 QPSK 0
11 1483 3 QPSK 0
12 1742 3 QPSK 0
13 2279 4 QPSK 0
14 2583 4 QPSK 0
15 3319 5 QPSK 0
16 3319 5 QPSK –1
17 3319 5 QPSK –2
18 3319 5 QPSK –3
20 3319 5 QPSK –5
21 3319 5 QPSK –6
22 3319 5 QPSK –7
23 3319 5 QPSK –8
24 3319 5 QPSK –9
2. Relationship
between CQI and
TB size when the
UE is at the level
1–6
CQI Transpor Number Modulatio Reference
value t Block of HS- n power
Size PDSCH adjustmen
t
1 137 1 QPSK 0
2 173 1 QPSK 0
3 233 1 QPSK 0
4 317 1 QPSK 0
5 377 1 QPSK 0
6 461 1 QPSK 0
7 650 2 QPSK 0
8 792 2 QPSK 0
9 931 2 QPSK 0
10 1262 3 QPSK 0
11 1483 3 QPSK 0
12 1742 3 QPSK 0
14 2583 4 QPSK 0
15 3319 5 QPSK 0
16 3565 5 16-QAM 0
17 4189 5 16-QAM 0
18 4664 5 16-QAM 0
19 5287 5 16-QAM 0
20 5887 5 16-QAM 0
21 6554 5 16-QAM 0
22 7168 5 16-QAM 0
23 7168 5 16-QAM –1
24 7168 5 16-QAM –2
25 7168 5 16-QAM –3
26 7168 5 16-QAM –4
27 7168 5 16-QAM –5
28 7168 5 16-QAM –6
29 7168 5 16-QAM –7
30 7168 5 16-QAM –8
• CQI
If the downlink rate of UE is low, check whether the CQI reported by UE
is over low, and check the PCPICH RSCP and Ec/Io of the serving cell
from the following aspects:
• The coverage is weak, and the CQI reported by UE is low.
• The interference is
strong, and there is pilot pollution, and the CQI reported by
UE is low.
• When the HSDPA serving cell is frequently updated, the HSDPA subscribers
cannot change accordingly due to punishment, so the CQI reported by UE is
low.
If the coverage is weak, improve the CQI reported by UE by RF optimization and
constructing sites.
If the interference is strong, adjust the azimuth and down tilt in RF optimization. This
forms a primary cell.
If the HSDPA serving cell is frequently updated, avoid frequent handover by adjusting
antenna azimuth and down tilt or constructing sites in RF optimization.
In static power distribution, the R99 services may occupy the power of HSDPA cell, so the actual
power used by HSDPA cell is not the configured power.
Analyze the factors affecting available power of HSDPA cell from the
following aspects:
• Query power margin by executing the command LST MACHSPARA on
NodeB. The default power margin is 10%, namely, the total downlink load of
cell can use 90% of total power of cell.
• On RNC LMT, select Realtime Performance Monitoring > Cell Performance
Monitoring > Tx Carrier Power. Observe the transmit carrier power and
power used by non-HSDPA subscribers. The available power of HSDPA =
transmit carrier power - power used by non-HSDPA subscribers. If the power
used by non-HSDPA subscribers is over high, the available power of HSDPA
cell becomes low, so the scheduled rate is affected.
• Available codes of HSDPA cell
If inadequate codes are assigned to HSDPA subscribers, the TB size of
NodeB scheduling will be affected..
• HSDPA UE CATEGORY
The 3GPP protocol 25.306 defines 12 types of UE category. In a TTI, the
UE of a type obtains different maximum TB size, so the maximum
scheduled rate obtained by UE is different.
The UE reports its capability in the IE hsdsch physical layer category of
the RRC Connection Setup Complete message..
• Amount of data to be transmitted being smaller than the maximum TB size
The TB size scheduled by NodeB depends on the available power and
codes of the subscriber, as well as the amount of data transferred by the
subscriber. If the amount of data sent is smaller than the maximum
scheduled TB size, the rate at physical layer is lower than the expectation.
This problem occurs when there is data in NodeB buffer but the amount of
data is inadequate for a scheduled maximum TB size.
1. HS-SCCH power
offset
Spreading HS-SCCH HS-SCCH
factor of power power offset
downlink offset in in SHO
DPCH non-SHO period
period
4 –10.75 –6.75
8 –7.75 –3.75
16 –4.75 –0.75
32 –1.75 +2.25
64 +1.25 +5.25
0 shows that HS-SCCH power control is based on CQI , which works like
this:
First set HS-SCCH initialization TX power
Then according to CQI change , adjust HS-SCCH power, like DCH inner-
loop power control.
At last , according to the ACK/NACK/DTX information from HS-
• IBLER
IBLER affects MAC-HS retransmission, so it consequently affects the
actual rate of subscribers. The IBLER here is number of incorrect
TBs/number of total new data blocks when the NodeB transmits new data.
The SBLER here is number of incorrect blocks/(number of incorrect and
correct blocks) when the NodeB transmits new data or retransmits data.
IBLER directly affects SBLER. Now the default IBELR is 10%. IBLER
directly affects the power for scheduling each subscriber. This is similar
with outer loop power control of R99.
Execute the command SET MACHSPARA to set the following items:
• Scheduling algorithm
• MAC-HS retransmission times
• Power margin
• HS-SCCH power
• Initial BLER
The MML command is as below:
SET MACHSPARA: LOCELL=1, SM=PF, MXRETRAN=4,
PWRMGN=10, PWRFLG=FIXED, PWR=5, IBLER=10;
• Low CQI and inadequate HSDPA power
If the CQI reported by UE is low, and the available power of HSDPA is
inadequate, SBLER will be high. The size of an MAC-d PDU is 336 bits.
The MAC PDU requires the TB size larger than 336 bits in transmission.
As a result, the CQI upon NodeB's scheduling must be larger than a value
to meet that IBLER is within 10%.
• CQI reported by UE being higher than actual one
The CQI reported by UE is inaccurate, higher than the actual one. The
NodeB adjusts the CQI according to target IBLER, but it takes some time
for adjustment. During this period, the NodeB transfers data with low
power according to the CQI reported by UE. As a result, the SLBER is
high, so the performance of data transfer is affected.
Solution: by Windows HyperTerminal, connect UE to the data card. Adjust
the CQI reported by UE by executing AT commands (This solution caters
for Huawei data card only. The current version does not support this).
Assume: before the following operations, the CQI reported by connected
UE is 25.
• Enable the function of adjusting CQI, set the offset to –200, and lower CQI.
In the WCDMA HSDPA Decoding Statistics window, you can see ACK-
>NACK/DTX. In , ACK->NACK/DTX is 76.01%. The right pane displays
detailed number of blocks that are correct received and retransmitted. As a
result, ACK->NACK/DTX=7808/(7808+2465)=76.01%.
In the WCDMA HSDPA Link Statistics window, the MAC Layer Rate-
Average is 67.33 kbps. In the left pane, the RLC DL Throughput is 16.19
kbps. The ratio of RLC rate and MAC rate is 16.19/67.33, equal to
24.05%. If the correct blocks that are repeated received is excluded from
calculating MAC layer rate, the MAC layer rate is 67.33 * (1- 76.01) =
16.15 kbps. The MAC layer rate is approximately equal to RLC rate.
• Over low configuration of HS-DPCCH power parameters
HS-DPCCH is an uplink dedicated physical channel, transporting the
ACK/NACK, and CQI messages at physical layer. HS-DPCCH is not
under respective power control, but has a power offset with downlink
DPCCH. When HS-DPCCH carries different information, it uses
different offset values.
If the ACK/NACK power offset on HS-DPCCH is over low, the ACK-
>NACK/DTX demodulated by NodeB in uplink will be overhigh, and
consequently the subscribers' rate is affected.
For the description of HS-DPCCH power parameters, see the appendix
HS-DPCCH Power Control Parameter Configuration.
• Uplink and downlink RL imbalance in handover areas
The uplink and downlink RL imbalance in handover areas are defined
as below, and shown in:
RL2_dl > RL1_dl
RL2_ul < RL1_ul
Because RL2_dl > RL1_dl, the serving cell is updated, and the HSDPA
service is set up in the cell 2. The RNC adjusts SIRtarget according to
combination result of two UL RLs due to SHO. The two cells perform
inner loop power control according to SIRtarget. The UE combines the
downlink TCP of the two cells. According to combination principles, if the
TCP of one cell is –1, lower power accordingly. When the TCP of two
cells is +1, raise power.
Because RL2_ul < RL1_ul, the RL1_ul SIR is converged to target value,
and RL2_ul SIR is lower than the target value. The power control over HS-
DPCCH is based on the associated channel of RL_ul, so the demodulation
performance of HS-DPCCH ACK/NACK/CQI cannot meet requirement.
As a result, the performance of data transfer for HSDPA subscribers is
poor.
Analysis proceeds as below:
• Obtain HSDPA-HSDPA handover test data, including the data at UE side and
RNC side.
• According to single subscribing signaling tracing, analyze to see whether there
is a serving cell updated due to UL RL failure. If yes, find the UE APP
throughput at the corresponding point.
• With the data at RNC side, draw a chart involving uplink SIR, SIRtarget, UL
BLER, downlink throughput, PCPICH RSCP and Ec/No. Obtain the SIR
information on HSDPA uplink associated channel.
• Based on the results
from Step 2 and 3 above, obtain the information about RL
imbalance.
• Analyze RL imbalance and provide solutions.
• Over high RLC retransmission rate due to over high residual BLER at MAC
layer
If the retransfer at MAC layer reaches the maximum times, the TBs
incorrectly received will be dropped. If the receiver detects dropping data
packets, it requires the sender to resend data packets by state report.
Retransfer lowers the sending efficiency of RLC, so it affects the valid
throughput of RLC. When residual BLER at MAC layer is over high, the
SBLER at MAC layer is probably over high. For detailed analysis, see the
analysis of over high SLBER in previous sections.
Normal the residual BLER at MAC layer is smaller than 1%.
shows the residual BLER at MAC layer in WCDMA HSDPA Decoding
Statistics window.
• The RTT delay at the RLC layer is exceptional (the RLC state report disable
timer is not set properly/the uplink BLER is not converged) so that the RLC
send window is full.
Currently, the maximum size of the RLC send window can be set to 2047
(the RLC receive/send window size of the terminal is 2047). When the
RLC transmission rate is very high, the RLC send window is easily full
and cannot send other data if the state report is not returned in time.
For example, the rate on the air interface is 3 Mbit/s and the MAC-D PDU
size is 336 bits, the RLC send window can send data for (2047 x 336)/(3 x
1024) = 224 ms. If the RNC fails to receive a state report within 224 ms,
the RLC send window is full.
The return time of the state report is related to the state report disable timer
and the uplink air interface quality. If the state report disable time is set too
long, or the uplink BLER is not converged, the RLC send window may be
full.
Solution:
Check whether the state report disable timer is set properly and whether it
is set to the default of the baseline. Currently, the default timer length is
120 ms (service-oriented configuration) in the RNC V16 and 80 ms for the
3.6 Mbit/s services (service-oriented configuration) in the RNC V17.
Check the convergence of the uplink BLER to ensure the BLER is
converged.
• Compare the throughputs at the application layer (APP) and the RLC layer.
TCP/IP adopts the inclusive acknowledgment strategy for reliable data
transmission and the sliding window protocol for flow control, and
performs congestion control when detecting a network congestion.
• Flow control (sliding window)
Flow control is used to prevent buffer overflows and saturation of the
receiving machine. Flow control generates a window value for the
sender to transmit the specified number of bytes in the window. After
that, the window is closed and the sender must stop data transmission.
The window is not opened until the sender receives an ACK from the
receiver.
• Inclusive acknowledgment strategy
All to-be-transmitted bytes before the confirmed byte number are
acknowledged. Suppose that 10 data fragments are to be transmitted.
These data fragments cannot reach the destination in sequence. TCP
During the optimization of the HSUPA throughput, you should combine the drive test data of the
Probe tool for analysis. The following describes HSUPA-related rates in the Probe tool:
• MAC-e PDU Non-DTX Rate = Sum of all TB sizes in the case of non-
DTX/(number of non-DTXs * TTI)
This rate is the actual rate of the MAC-e (excluding DTX, but including
the rate of retransmission blocks)
• Sum of all TB sizes in the case of non-DTX: Not only the block transmitted first but also the retransmitted
blocks are included.
• Number of non-DTXs * TTI: Only the time when data is transmitted is counted and the time when no data
is transmitted is excluded. For example, if only 50 sub-frames send data within the measurement period
of 100 sub-frames (200 ms), the denominator is 100 ms.
• MAC-e PDU Served Rate = Sum of all TB sizes in the case of non-
DTX/(NUM_SAMPLES * TTI)
This rate is the served rate of the MAC-e (including DTX and the rate of
retransmission blocks)
• Sum of all TB sizes in the case of non-DTX: Not only the block transmitted first but also the retransmitted
blocks are included.
• NUM_SAMPLES * TTI: The time when data is transmitted and the time when no data is transmitted are
both included. For example, if only 50 sub-frames send data within the measurement period of 100 sub-
frames (200 ms), the denominator is 200 ms.
• MAC-e PDU Available Rate = Sum of TB sizes when COMB_HICH is ACK or
ACK_NS in the case of non-DTX/(NUM_SAMPLES*TTI)
• Sum of TB sizes when COMB_HICH is ACK or ACK_NS in the case of non-DTX: Only the TBs
transmitted correctly are counted.
• NUM_SAMPLES * TTI: The time when data is transmitted and the time when no data is transmitted are
both included.
Relationship between these three throughputs:
• MAC-e PDU Served Rate = MAC-e PDU Non-DTX Rate * Non-DTX
Probability
• MAC-e PDU Available Rate ≈ MAC-e PDU Served Rate *(1-SBLER)
• Sum of bits of all RLC PDUs sent by the RLC layer within the measurement period: The first transmitted
data and the retransmitted data are included. In addition, the data is transferred by MAC-d and contains
the header overhead (16 bits) of the RLC PDU.
• Measurement period duration: The time when data is transmitted and the time when no data is transmitted
are both included.
Relationship with MAC-e PDU Available Rate:
• RLC PDU Throughput UL = MAC-e PDU Available Rate * (1-header overhead
ratio of MAC-e PDU)
• A precise relationship should exclude the header overhead and the padding bits when the TB size does not
match N RLC PDU bits
• UL RLC SDU Throughput = Sum of bits of all RLC SDUs sent by the RLC
layer within the measurement period/Measurement period duration
• Sum of bits of all RLC SDUs sent by the RLC layer within the measurement period: Compared with the
sum of RLC PDU bits, the retransmitted data and header overhead (16 bits) of the RLC PDU are
excluded.
• Measurement period duration: The time when data is transmitted and the time when no data is transmitted
are both included.
Relationship between RLC SDU Throughput UL and RLC PDU
Throughput UL:
• RLC SDU Throughput UL ≈ RLC PDU Throughput UL*(1-RLC PDU
Retransmission Rate UL)*header overhead ratio of the RLC PDU
The figure below shows the optimization flow of a low throughput of the HSUPA UE.
2. Optimization flow of a
low throughput of the
HSUPA UE
If the service is not borne on the HSUPA, the service is automatically set up on a DCH. In this case,
the service rate is the rate of the R99 service, usually 384 Kpbs or below.
• Check whether the capabilities reported by the UE include the HSUPA. The
RRC_CONN_REQUEST message reported by the UE indicates whether the
HSDPA and HSUPA are supported. The specific E-DCH capability level is
reported in an RRC_CONN_SETUP_CMP message.
• Check whether the MBR in the subscription information in the previous line is
normal and whether the rate threshold over an E-DCH is set too high. If the
MBR assigned by the CN does not exceed the rate threshold over an E-DCH,
the service is set up on a DCH.
• Check whether the HSUPA cell is available and activated.
• The access of the HSUPA UE fails.
• Check whether the type of the HSUPA AAL2PATH is configured correctly and
whether a type of HSUPA AAL2PATH is configured.
If the UE reports HAPPY, the user may not feel happy. Make specific analysis according to the
happy reasons.
If the MAC-e PDU Non-DTX Rate is abnormal, use the drive test tool Probe to determine whether the
UE reports HAPPY or UNHAPPY.
If the UE reports HAPPY and the UE rate cannot reach the MBR, the possible causes are as follows:
1. Categories of UE
HSUPA capability
levels
E-DCH Maximum Minimum Support Maximum
Category Number of Spreading for 10 Number of
E-DCH Factor and 2 Bits of an
Codes ms TTI E-DCH
Transmitted EDCH Transport
Block
Transmitted
Within a 10
ms E-DCH
TTI
2 ms TTI
2 ms TTI
2 ms TTI
NOTE: When 4 codes are transmitted in parallel, two codes shall be transmitted with SF2 and two with SF4
• Observation method:
• Observe the UE capability
Generally, the terminals supporting the HSUPA function all support the
HSDPA function. That is, the HSPA bears the services of users as a
whole. The following describes how to observe the HSPA function that
the UE supports and the specific HS-DSCH/E-DCH capability level in
5. RRC CONNECTION
REQUEST message
7. RL RECFG PREPARE
message
When the UE uses the maximum block (14480), Qualcomm chips of early versions also display the
limited transmit power, but in fact, the transmit power is not limited. This problem can be ruled out
by combining the current MAC-e PDU Non-DTX Rate with the actual transmit power of the UE.
• After confirming that the transmit power of the UE is limited, analyze the
limitation causes.
a.View the PCPICH RSCP of the cell where the UE is located and
check whether the UE is at the edge of the cell.
b.View the RTWP of the cell where the UE is located before the access
and check whether the uplink load of the cell is high.
c.View the uplink SIR of the UE to check whether the SIR is
exceptionally high.
d.View the service that the UE sets up and check whether the service is
a combined service.
• Solution:
• If the UE is at the edge of the cell, move the UE to the center of the cell.
• If the uplink load of the cell is high and the cell load is adjustable, reduce the
cell load.
• If the service that the UE sets up is a combined service, deactivate the R99
service and observe the rate of the HSUPA service.
The traffic of the terminal is limited.
• Principle description:
If the data in the UE RLC Buffer is insufficient, the actual MAC-e PDU
Non-DTX Rate is low.
• Observation method:
• Method of observing whether the traffic of the UE is limited
Observe the buffer limited rate reported by the UE through the
Assistant. If the buffer limited rate greater than 0%, the traffic of the UE
within the corresponding measurement period of the measurement value
is limited.
When the TCP layer rate is less than 320 kbit/s, the utilization is less
than 73%.
When the TCP layer rate ranges from 320 kbit/s to 736 kbit/s, the
utilization is 74% or so.
When the TCP layer rate ranges from 768 kbit/s to 1376 kbit/s, the
utilization is 75% or so.
3) When the IP is adopted on the Iub interface, the HSUPA Iub
bandwidth utilization = TCP layer rate/IP bandwidth
When the TCP layer rate is less than 224 kbit/s, the utilization is less
than 80%.
When the TCP layer rate ranges from 224 kbit/s to 448 kbit/s, the
utilization is 80% to 85%.
13. RAB
assignment request
message (containing an
MBR)
1. PO for the E-
If the actual signals at the edge of the cell in a scenario are worse, the
Ec/Io decreases by 1 dB and the PO of each channel increases by 1 dB.
Compare the AG received by the UE with the one sent by the NodeB
(the latter can be obtained from the NodeB scheduling debugging
information file).
2. PO for the E-
RGCH when the
If the actual signals at the edge of the cell in a scenario are worse, the
Ec/Io decreases by 1 dB and the PO of each channel increases by 1 dB.
Make comparison tests between NodeB and UE and ensure that the E-
RGCH power is properly set.
Step 3: If the power control mode is power control for UE based on the
DPCH transmit power (default algorithm in V22), no test experience is
available in V18 and test experience will be supplemented in later
versions.
For cause 2:
Cause 2 is caused by the signature used by the E-HICH and the E-
RGCH. A signature error exists in a NodeB test version. When the pilot
power is 33 dBm and HICH power is set to 33 – 21 = 12 dBm, AG
Hold is normally demodulated. When the HICH power is set to 13 dBm,
AG Hold is occasionally demodulated into AG UP. When the HICH
power is set to 14 dBm, AG Hold is most demodulated into AG UP.
When the HICH power is set to 16 to 18 dBm, AG Hold is basically all
demodulated into AG UP.
• Solution:
For cause 1, increase the PO of the E-RGCH on the basis of the baseline
parameters according to the actual signal coverage quality at the edge of
the cell.
For cause 2, rectify the product.
• The RLC layer is exceptional so that RLC data is not sent in time.
See "RLC SDU Throughput UL Exception Location".
• The TCP/IP layer is exceptional so that TCP data is not sent in time.
See "TCP/IP Layer Rate Exception Location".
3. PO for the E-
HICH when the
Ec/Io at the edge
of cells is –12 dB
Control Channel Scenario Power Offset
If the actual signals at the edge of the cell in a scenario are worse, the
Ec/Io decreases by 1 dB and the PO of each channel increases by 1 dB.
Since the R&D personnel do not distinguish between two cases (single
link and RLS including serving_DCH cell) in the implementation of the
power control, the PO for a single link is the same as that for RLS
including serving E_DCH.
Make comparison tests between NodeB and UE and ensure that the E-
HICH power is properly set.
When performing a test, ensure that the uplink channel is in good
condition, disable the outer loop power control, and set the SIR to 11
dB. Construct a scenario without HARQ retransmissions so that the
NodeB sends HARQ_ACK all the time. Test the probability of
demodulating ACK into NACK from the UE side.
• Step 2: Ifthe power control mode is power control for UE based on the DPCH
transmit power (default algorithm in V22), no test experience is available in
V18 and test experience will be supplemented in later versions.
• The uplink packet loss on the air interface (MAC-e layer residual SBLER >1%)
causes a high RLC retransmission rate.
• Principle description:
1) TBs are discarded if they are not received when the number of MAC-
e layer retransmissions reaches the maximum. This is packet loss for the
RLC layer.
2) If the receiver at the RLC layer detects packet loss, it requires the
sender to retransmit the packet through a state report.
3) Data retransmission reduces the transmission efficiency of the RLC,
and further affects its efficient throughput.
4) The uplink transmission quality on the air interface is controlled by
the uplink outer loop power control. If packet loss occurs in the uplink
of the air interface, the uplink outer loop power control is generally
exceptional.
• Observation method:
Method 1: Observe the RLC PDU retransmission rate UL on the Probe.
• Too small a TCP receive window on the receiver side makes the send window
easily full.
• Principle description:
TCP/IP adopts the sliding window protocol. The sliding window
protocol allows the sender to transmit multiple consecutive packets
before the sender stops transmission and waits for an acknowledgment.
As it is unnecessary for the sender to stop and wait for an
acknowledgment each time it transmits a packet, the sliding window
protocol increases the data transmission rate.
Theoretically, TCP receive window size should be greater than the
product of the bandwidth and the delay.
Capacity(bit)=bandwidth(b/s)*round-trip time(s)
A 66535-byte window is sufficient for the 1.6 Mbit/s service, but
insufficient for 3.6 Mbit/s service. Especially when the delay is greater
than 200 ms, the TCP window is easily full. As a result, you observe
that the buffers of the RLC and the NodeB are 0.
• Observation method:
1) Query the configuration of the TCP receive window at the receiver
end.
2) Obtain the current Ping delay (test the RTT)
3) Observe the rate on the UE/DU meter is approximate to the TCP
receive window size/RTT.
• Solution:
1) Change the TCP receive window size at the receiver end.
Use the following registry entries to set the receive window size to 80
KB (80*1024 = 81920).
Method 1:
Use the DRTCP tool to modify the receive window size and restart the
computer.
Method 2:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\
Services\Tcpip \Parameters\TcpWindowSize (REG_DWORD)
Restart the computer.
2) If no DRTCP tool is available, use multiple processes to perform
verification.
• A 100% CPU load at the receiving end cause the TCP receive window to be full.
• Principle description:
When the CPU load at the receiving end reaches 100%, the data in the
TCP receive window cannot be submitted to the upper layer and the
TCP receive window is full.
When the TCP receive window is full, the receiver notifies the TCP
sender of it and the sender stops transmitting data. As a result, the RLC
BO is 0 and the UE transmits no data.
• Observation method:
Observe the Performance tab page in the Windows Task Manager.
• Solution:
1) Close the programs not related to the test at the receiving end.
2) Use high-performance computer at the receiving end.
• The RTT timeout at the TCP/IP layer caused by packet loss at the CN side
triggers congestion avoidance.
• Principle description:
TCP provides the reliable transport layer. One of the methods that TCP
uses is acknowledging the data received from the other peer, however,
data and acknowledgment may be lost. TCP solves the problem by
starting a timer when it starts transmitting data. If no acknowledgment
is received when the timer expires, TCP retransmits the data.
The TCP sender measures the RTT of a connection (measures the RTT
from when it transmits a byte with a special sequence number to when it
receives an acknowledgment containing this byte) to maintain an RTT
timer.
If the RTT timer expires, TCP considers that a network congestion
occurs and triggers the congestion avoidance mechanism. As a result,
the data transmission rate is affected.
IP packet loss on the CN side causes the RTT timeout.
• Observation method:
Start Ethereal on the portable PC attached with a data card to capture
TCP data packets, and then analyze the captured packets. Check
whether the receiver sends repeated acknowledgment packets.
• Solution:
Check segment by segment to confirm that the problem lies in the RAN
Package lose on CN side result in TCP/IP layer RTT overtime touch off
congestion avoidance
TCP apply credible transmit layer. One method is to affirm the data which receive from the other side.
But data and affirmance may lose . TCP transit set a timer in the send time to solve the problem. When
the timer overflow , it don’t receive affirm message, it will retransmission data.
TCP send point will be a measure to a connect RTT. Maintain a RTT timer.
If it measure RTT overtime , TCP think net congestion , it will start-up congestion avoidance.
Consequently, it will affect data transmit rate.
IP package lose on CN side will make RTT overtime.
Environment Problems
The rate is relevant to PC, OS, and applications. The internal algorithm of software at different
application layer and TCP parameters of OS have great impact on performance. If other conditions are
the same, the rate of data transfer on Windows 2000 computer is superior to that on Windows 98
computer. Therefore, it is recommended to use Windows 2000 Professional and Windows 2000 server
as the OS of PCs and servers.
Now the laptops are installed with Windows XP, so there is no problem concerning perform due to
OS. Anyhow, the servers must be installed with Windows 2000 server, because Windows XP will
affect the performance of data transfer.
The PC (laptop) for being daemon of UE must be of good performance. Tests prove that IBM laptops
have good performance in playing VODs. Now Huawei RNP engineers use the new laptops of D
Corporation, which have worst performance in data transfer of HSDPA test than the new ones of H
Corporation.
Service-related Problems
• FTP
Use the commercial FTP software, because the FTP software embedded in
Windows OS is of average performance. Download data with FTP in
binary. The multi-thread downloading software like FlashGet is
recommended.
If update rate is low , it can consider process multi-FTP transmission at the
same time, or use tools send fixed rate package to make sure whether the
bottom has a problem.
• VOD
The software RealPlayer sets the maximum play rate to larger than 384
kbps. The buffer time must not be over long, and 3s is proper. Some
computers are installed with qualified video adapter, so the monitor jumps
some frames. Change the resolution to 800x600. If the problem is still
present, change the video adapter.
• Net TV
When the rate of down-layer declines, the Net TV is difficult to restore.
Note this.
• Video conference
Set the output rate of convergence TV smaller than the rate of down-layer;
otherwise, data packets will be dropped. Huawei conference video sets 64
kbps as step from 128 kbps. The recommended configuration is 320 kbps.
If the rate is over low, utilization rate of down-layer rate will be over low.
Otherwise, using the rate higher than 320 kbps, such as equal to or larger
than 384 kbps, leads to dropping data packets because the rate of down-
layer cannot meet the requirements by application layer. As a result, the
performance of video conference declines. If a lightning sign appears on
the right upper corner of conference TV, there must be code error or packet
dropping during transmission.
Signaling Flow
Analyze signaling in details to locate interruption of data transfer. Check whether call drops, whether
the UE hands over from 3G networks to 2G networks, and whether state transits.
Collect signaling in several ways. Collect the signaling at UE side by using Probe and UE. Collect the
signaling at RNC side on RNC LMT. By comparison of two signaling flow, check whether messages
are lost at air interface. Based on analysis and CHR, engineers can locate the problem or obtain the
rough direction.
• Call Drop
For call drop problems, see W-Handover and Call Drop Problem
Optimization Guide.
• Channel State Transit
When the cell state transits to CCH, it cannot restore to CELL_DCH.
Check the abnormal information in CHR. If the downlink load is over
large by confirmation, or the bandwidth at Iub interface is congested, add
carriers or transport resources.
• 3G2G handover
If the data transfer is problematic after handover from a 3G network to a
2G network, the problem involves the cooperation of the two networks. If
the 2G network was constructed by partners, locating the problem will be
more difficult.
Try to set up PS services in the 2G network, and see whether it runs
normally. If the data transfer upon access to the 2G network is normal, but
the data transfer after handover from the 3G network to the 2G network is
abnormal, check the UE and the signaling flow at 3G and 2G NE side.
In terms of causes, defining a subscriber or inconsistent configuration of
• Intra-NodeB. In the same DSP of a NodeB, interruption of data transfer does not
occur because no data needs transiting from one MAC-hs buffer to another
MAC-hs buffer.
• Inter-NodeB. When MAC-HS is reset, the NodeB drops original data in buffer
and restores the dropped data by RNC RLC retransmission. The interruption
of data transfer lasts for about 300ms.
During the inter-frequency and intra-frequency HHO associated HSDPA serving cell update, the
MAC-HS is reset, the NodeB drops original data in buffer and restores the dropped data by RNC RLC
retransmission. The interruption of data transfer also occurs.
During H2D SHO, intra-frequency HHO, inter-frequency HHO, D2H SHO, intra-frequency HHO, and
inter-frequency HHO, the interruption of data transfer also will occur.
During the handover between HSDPA and GPRS, data transfer will also be interrupted.
The interruption of data transfer includes two aspects:
• Alarms
Query the alarms on CN and RAN. Know the abnormalities in the
operation of current system. Guide analyzing and identifying problems.
Some problem, such as interruption of data transfer, clock
asynchronization in some cells, and NE congestion, can be known from
alarms.
• Whether downloading is complete
Data transfer is interrupted for a long time, so restoring it is impossible.
Check whether downloading the file by FTP is complete.
• Signaling Flow
According to detailed analysis of RNC and UE signaling, judge whether
• Use Qualcomm QXDM and QCAT tool. The interval between dropping packet
at receiver and receiving current data is the interruption time of data transfer.
• Capture TCP/IP packets directly by using the software Ethereal. Analyze the
interval between TCP/IP.
1. Interruption delay of
TCP displayed in
Ethereal
In 5.4.2, the data transfer is interrupted for two times, and the interruption delays are respectively
300ms and 300ms. Compare the TCP rate in Ethereal and the rate at application layer in Assistant, and
they must match. Therefore, obtain the update point of serving cell in Assistant.
6. Cases
Title Description
Analysis
According to traffic statistics, the traffic in the cell is heavy. The bandwidth at Iub interface is 1 Mbps,
always fully used. If a UE keeps transferring data on line, the transferring is stable. If the subscriber
browses web pages without data transfer, the UE transits to idle mode to save resource according to
DCCC algorithm. When the UE needs to transfer data again, it must apply for resource again.
However, the resource may be used by other UEs, so no resource is assigned to it. As a result, the
connection fails. The subscriber feels that he/she is off line. It is difficult to reconnect to the network.
When other subscribers use less resource, the subscriber can succeed in dial to connect to the network.
The essence of the problem lies in that excessive subscribers use the resources, so the resource is
congested.
To solve this problem, use the methods below:
Analysis
According to statistics of rate at RNC RLC layer, the maximum rate exceeds 64 kbps, and it fluctuates
sharply. As a result, the average rate at application layer displayed by the software FTP is low.
According to signaling tracing and statistics of uplink BLER, the uplink BLER is about 10%. As a
result, the rate at application layer fluctuates and the throughput declines.
Solution
Change the target uplink BLER to 6% or 1%. Change related power control parameter.
Setting different target BLER helps balance the performance of single UE and more UEs. According
to the information from other networks, different target BLER are set for different networks, but they
are small.
Note that setting target BLER is according to index of service type. The uplink and downlink
bandwidth are usually different, namely, the index of service type is different. Set target BLER after
confirming the index of service type.
In 8k/8k, the delay of each service is larger than 220ms. In 64k/128k, the delay is smaller. Therefore
the delay and bandwidth are relevant.
Execute the command ping by 32 bytes, and analyze as below:
In 8k/8k, execute the command ping by 32 bytes. It is 60 bytes including the IP head. The TTI of 8k is
40ms. Each TTI has a block. The TB size is 336 bits. As a result, executing the command ping by 32
bytes occurs on two TTIs, namely, 80ms. The downlink is similar.
The uplink and downlink must stagger a TTI. Assume that the processing at nodes and interface goes
infinitely fast. To the air interface and from the air interface take 200ms (5*40 ms).
In addition, a PC always sends data about MSN, HTTP protocols. If the PC sends other packet during
sending ping data, the ping command has to wait. Therefore, 8k bandwidth is over small.
In 64k/128k, execute the command ping by 32 bytes. It is 60 bytes including the IP head. The TTI of
128k is 20ms. Each TTI has 8 blocks. The TB size is 336 bits. As a result, executing the
command ping by 32 bytes occurs on a TTI, namely, 20ms. The downlink is similar.
The uplink and downlink must stagger a TTI. Assume that the processing at nodes and interface goes
infinitely fast. To the air interface and from the air interface take 60ms (3*20 ms). Adding this to CN
cost and laptop cost makes more than 100ms.
Execute the command ping by 8 bytes on conversational service. After on-site verification, the test is
consistent with prediction.
Analyze the parts of total delay from laptop, to UE, to NodeB, to RNC, to CN, and to server. Analyze
the factors that affect delay in each part. This helps locate delay problems.
Compared with 8k/8k streaming service, the typical parameters of 8k/8k conversational service must
be optimized.
Analysis
On-site NodeB engineers have demonstrated the service in laboratory, and the rate is normal, 1400
kbps. They use big antenna and lower the power on site to cover the sites of the operator. After this,
the Ec is –50 dBm, and Ec/Io is –3 dB. Namely, the coverage is qualified. In the on-site test, after
starting downloading data, the Ec/Io deteriorates sharply. According to QXDM tracing, the
transmission rate is 100% (engineers doubt that the problem is caused by interference and improper
installation of antenna, but the cause is not them according to frequency sweep and SITEMASTER
test). As a result, engineers doubt that the transmission on the interface board of NodeB and trunk are
faulty. After changing the interface board and trunk, the problem is still present.
Test with PS384k service, the result is normal. According to causes of problem, the HSDPA feature
leads to weak Ec/Io, as a result, the BLER and retransmission rate are high. At the beginning of test, to
reduce radiation, engineers lower the pilot power. However, the HSDPA network distribute power
according to amount of data as its feature, so the network distributes high power (near 35 dBm) to
TCH upon downloading. As a result, the Ec/Io declines, which consequently causes decline of
demodulation performance and increment of retransmission rate. Raise the pilot power, and then the
transmission rate is normal. The problem is solved.
Solution
Raise the pilot power from 23 dBm to 33 dBm, and the transmission rate will be normal.
Analysis
Once the on-site engineers download data, the CQI fluctuates sharply and frequently between 15 and
26. The rate fluctuates between 100 kbps and 600 kbps.
The load of HSDPA fluctuates sharply between 3% and 24%. This must be relevant to downloading
rate.
No FP packet is missing. No packet is missing because the queue is full. In the scheduling period,
abundant DTXs exist according to NodeB, with few NACK messages.
According to check, the receiving power of data card is as high as –45 dBm, exceeding the normal
range (–55 dBm to –85 dBm). The signals are strong, and the attenuation is inadequate, so the
measured CQI is inaccurate.
Solution
Add an attenuator at the antenna port, and keep the receiving power at about –70 dBm. After this, the
problem of frequently fluctuation, as well as the BLER problem, is solved.
1. Variation of total
throughput of one IMA
link of HSDPA codes
2. Variation of total
throughput of two IMA
links of HSDPA codes
In Figure 6-1 and Figure 6-2, the throughput of one E1 is lower than the throughput of two E1's.
Analysis
Solution
Change the AAL2PATH of HSDPA to 1.9 Mbps when there is one E1. Test again, and the rate of
subscribers is about 1.5 Mbps.
In actual networks, guarantee that the AAL2PATH allocated bandwidth to HSDPA is smaller than the
physical bandwidth at Iub interface. This will affect throughput of cell. Meanwhile, check NodeB
alarms whether there are E1 fault alarms.
• Maximum transmit power provided by the UE for uplink packet access (UPA)
• SG that the UE obtains, which indicates the maximum power that the NodeB
allows the UE to transmit
• Percentage of the data to be transmitted to the buffer, which indicates the size of
data that the UE needs to transmit
These factors are represented by corresponding parameters in the QXDM and Probe tools accordingly.
• Inthe Probe, the following limited rates are displayed in the HSUPA Link
Statistics window to represent these factors.
• Power Limited Rate
• SG Limited Rate
• Buffer Limited Rate
The highest limited rate indicates that it is the major factor affecting the
uplink transmission rate of the UE. The measurement period of the Probe
is long. These three limited rates are measured within a measurement
period of 200 ms.
• In each TTI in the data packets recorded by the QXDM, the Payload Reason
option is recorded. This option indicates the three factors for the limited
server payload: MAX power, SG, and buffer occupancy (that is, whether data
lacks or not).
• In the figure below, MP in the Reas column indicates the transmission rate of
the UE is currently subject to the maximum transmit power.
Low UL Rate Caused by the Limited Rate of the Buffer to Which the UE Sends
Data Through FTP
• Location method: The Buffer Limit Rate observed in the HSUPA Link Statistics
window of the Probe is high, approximate to 100%. BO is all displayed in the
Reas column of all packets captured by the QXDM.
2. Cases at CN Side
1. Low FTP Downloading Rate due to Over
Small TCP Window on Server TCP
Description
Activate uplink 64 kbps and downlink 384 kbps services on UE and laptop. Download data from the
servers of operator with CUTEFTP. The average downloading rate of UE is 33 kbps, much lower than
384 kbps. The average rate at FTP application layer is about 28 kbps.
Analysis
Activate uplink 64 kbps and downlink 128 kbps services, and download data. Engineers obtain the
required rate. However, after activating 384 kbps, the maximum rate cannot be reached. Try to connect
the UE to Huawei web server (the GGSN Gi interface <-> Lanswitch <-> NE08 <-> Internet <->
Server of operator. The <-> used here means connection between two network elements (NEs).
Huawei web servers connect to Lanswitch by Gi interface. The address of web server and the address
FTP server to client: After sending 6 TCP packets (4 * 1500 + 2 *1190), the
server stops sending, and 6 packets must be confirmed.
The FTP server receives an ACK message. After the FTP server and client
confirm two TCP packets, the server stops sending. There are 4 packets to
be confirmed.
The FTP server receives an ACK message again. After the FTP server and
client confirm two TCP packets, the server sends three continuous TCP
packets (2 * 1500 + 1190). There are 5 packets to be confirmed.
The FTP server receives an ACK message again. After the FTP server and
client confirm two TCP packets. The server sends 3 continuous TCP
packets (2 * 1500 + 1190). There are 6 packets to be confirmed.
It goes back to the first step. A cycle forms.
The FTP server sends at most 8.4 kbyte (4 *1500 + 2 * 1190) packets to be confirmed. According to
the second step above, the sender needs to send 4 kbyte data continuously. Therefore, the FTP server
sets the TCP sending window to be smaller than 10 kbyte, and the TCP is optimized to send large
block data (over 4 kbytes). The actual TCP window is 7 kbytes on average for FTP server. Assume
that the round-trip delay is t mm, so the maximum available rate is (7 kbytes/t) * 8 kbps.
According to previous analysis, after activating PS service, do not transfer data. Execute ping to server
on UE, and check the delay at the air interface. In Huawei system, the average delay for ping packets
is 250ms. According to analysis, 7 kbps/0.25 = 28 kbps. Namely, the theoretical average rate at
application layer is 28 kbps. This theoretical value is the same as the actual value. Therefore, the
operator must have restricted the TCP window at application layer on the server, so the rate keeps low.
Solution
• To increase rate, engineers must reduce the round-trip delay. When the delay is
smaller than 150ms, the rate can reach 384 kbps (7 kbps/0.15 = 46.7 kbps).
Actually reducing the delay at air interface is difficult. The Huawei delay at
air interface is about 250ms. Therefore, the rate cannot reach 284 kbps.
• Download data with multiple threads tool, such as FlashGet and NetAnt.
Multiple TCP connects to the server, so the rate can increase. According to
test result, download data with more than two threads by using FlashGet or
NetAnt, the rate can reach 47 kbps.
• Remove the restriction on sending window size of server, and set the sending
window size of server to 65535.
Analysis
Solution
According to previous analysis, increasing TCP window size of server leads to increasing downlink
theoretical rate. Actually, when using Huawei servers for test, set the TCP window size to 65535,
download with three threads by using FlashGet. Simultaneously upload data with CuteFTP. The
average sending and receiving rate is 46.5 KB/s in downlink and 6 KB/s in uplink.
Download data with multiple threads. According to test, download data with 10 threads from
operator's server when the TCP window size is 8192. The average sending and receiving rate is 42
KB/s in downlink and 6 KB/s in uplink. The data transfer is unstable with jitters.
Send the ACK message in downlink data packets, and sends uplink data packets at a fixed rate.
Restrict the uplink rate so that the uplink data packets will not be blocked at the air interface and the
delay at the air interface will not increase, and there is no jitter. Obviously, the decline of downlink
rate upon uplink and downlink data transfer is not due to Huawei system, and this problem cannot be
mitigated by this solution. This is a defect of TCP/IP protocol used in radio transmission. It is good to
combine the UE and the driver of wireless Modem to carry out the solution.
Analysis
Download data on one UE by FTP from operator's server, and the rate is as normal as above 47 KB/s.
Download data on two UEs, and then on three. The downloading rate keeps at about 47 KB/s with 4
UEs connected at most. When the fifth UE connects to the server, the rate declines. Try on site as
below:
Download data with four UEs from the operator's server, and with two UEs
from Huawei servers. Check whether the rate is faulty.
As a result, the downloading rate of 6 UEs reaches 47 KB/s.
Probably, the operator's server does not well cooperate with Huawei
networks.
Download data with six UEs from Huawei servers. Check whether the rate is
faulty.
Huawei servers cooperate well with Huawei networks. Probably the
operator's server does not well cooperate with Huawei networks.
The difference between the operator's server and Huawei server lies in the
router and firewall over the operator's server. Try to avoid the impact from
firewall and router, and check whether the rate increases.
Analysis
Figure 6-5 shows analyzing packets captured by Ethereal upon unstable PS rate.
3. Analyzing packets
captured by Ethereal
upon unstable PS rate
Analysis
Probably the problem is caused by loss of data packets and delay. After capturing packets by segment,
the cause proves on the firewall.
After repeated tests, the Up/Down and CRC Error occur frequently at the firewall 2 interface 2/2.
After another 3 hours' test, the cable between the firewall 2 interface 2/2 and LS12 must not be
physically broken, and CRC error must be due to improper installation of fiber.
A faulty firewall leads to loss of packets at the application layer, which has great impact on rate.
When the firewall is normal, the PS rate increases greatly. However, the rate is still unstable.
According to further analysis, the BLER at the air interface is 10%, so it is normal for PS rate to
fluctuate at the air interface. After engineers modify the BLER to 1%, the problem is solved. However,
the cost is more consumption of power at the air interface and impact on capacity.
Analysis
The subscriber can browse the portal websites, but cannot use streaming service. Meanwhile other
subscribers can use streaming service. Therefore, the PS service bearer is normal, and the cause cannot
be on RAN, SGSN, and GGSN. Probably the UE, USIM card, and server are faulty. According to
further analysis, the problem must be on the USIM card, and the subscriber did not pay for using
streaming service. The subscriber can browse the free portal websites.
Analysis
The subscriber feed back that other subscribers can use PS services with his card. He could use PS
service until one day recently. Therefore, the problem is about the laptop. The problem does not occur
after he changes the laptop. According to check, the subscriber has installed a firewall on his laptop
recently. After uninstalling the firewall, he can use PS services again.
Analysis
After numerous tests and analysis, the problem must be at RAN. After engineers analyze to detailed
subscriber signaling, data statistics at subscriber plane, the quality of signals at the air interface, and
loss of packets at Iub interface, the problem is still present. It is difficult. RNP engineers check the
signals on site, and the signals are qualified. After using the laptop of an RNP engineer, the data
transfer of PS service is normal. According to further analysis, the problem lies in the driver of public
laptop used in presentation. After engineers change the laptop, the problem is solved.
Analysis
According to analysis of FTP messages captured by Ethereal, the data session of FTP is over, but it
misses the last interactive completion process, and no messages like 221-Goodbye is found. The
downloaded files can be opened.
After the files are downloaded, they can be opened according to check.
Figure 6-6 shows the interactive interface in CuteFTP.
1. Interactive interface in
CuteFTP
2. Signaling of normal
downloading by FTP
3. Signaling of abnormal
downloading by FTP
Compare the tests in the 3G network, the 2G network, and the tests of
handover to the 2G network after access in the 3G network.
According to tests, the problem must be between GGSN and FTP server. This reduces the scope of
problem.
According to other tests, the problem does not occur when no firewall is over Huawei server. This
shows the cause. The problem does not reoccur due to no firewall.
According to data analysis, the data transfer at the FTP port is normal, but the signaling port is
disconnected after 10 minutes. This must be due to firewall. It is the firewall that can disconnect a port
without data transfer after 10 minutes, so the problem is due to firewall.
Processing the problem goes smoothly after focusing on the firewall. The expert on firewall explains
as below:
The FTP session includes two session tables on firewall. One is for FTP control channel, and the
default aging time is 10 minutes. The other is FTP data channel, and the default aging time is 4
minutes. The no detect ftp command is configured between domains, the data channel will not update
the aging time of control channel upon data transfer. As a result, the control channel is aging and
deleted after 10 minutes with the following phenomenon.
If the detect ftp command is configured, the data channel will update the aging time of control
channel. As a result, the problem does not occur.
The problem, in whole process, is irrelevant to RAN. However, the process and result of locating
problem is considerable.
Changing NEs in test is significantly useful.
The difficulty of problem may exceed engineers' consideration. It needs wide-range knowledge.
However, after the problem is solved, it seams easy.
Analysis
The UE hands over between the 3G network and 2G network. The UE camps on 3G network, and has
activated PDP, in PMM Connected state. When the UE moves at the edge of 3G network coverage
areas, it starts handing over to 2G network. When the handover is complete, the PS user plane is
restores and can perform data transfer. However, the problem lies in that the UE cannot continue data
transfer.
Analyze traced signaling.
Figure 6-9 shows the signaling of normal handover between 3G network and 2G network.
1. Signaling of normal
handover between 3G
network and 2G network
Check the 3G signaling LMT. During the handover from the 3G network to the 2G network, the
handover signaling is normal at 3G network side. After the UE sends the routing area update request
message to the 2G SGSN, the SGSN context and response flow between the 2G SGSN and 3G SGSN
is normal. Till now, the handover of 3G SGSN is complete. The next step is the signaling interaction
between the UE and the 2G SGSN, as shown in Figure 6-10:
Solution
This problem concerns the partner's equipment at RAN side. It cannot be solved at UE side due to
restriction from protocols. Therefore, the solution is to set the encryption item to non-encryption so
that the messages sent by UE are not encrypted. As a result, the problem is mitigated.
7. Summary
This document describe the access, disconnection of data transfer, low rate of data transfer, unstable
rate of data transfer, and interruption of data transfer. It provides the methods for analyzing and
processing these problems in terms of traffic statistics and DT/CQT. The experience from analyzing
problems in terms of traffic statistics is little, and will be supplemented.
8. Appendix
Title Description
8.8 PS Tools
1. Transport channel of PS
data
Observe different protocol layers, and there are different definitions of throughput, such as the
application layer throughput, RLC layer throughput, and MAC layer throughput.
1. TCP/IP Layer
Assume that the MTU is 1500 Bytes.
The TCP/UDP header overhead is 20 Bytes. The IP header overhead is 20 Bytes.
The TCP/UDP PDU size, namely, the payload at application layer, is 1460 Bytes, but the whole IP
packet size is 1500 Bytes.
2. RLC Layer
The RLC header overhead is 16 Bits.
The RLC PDU size is 336 Bits.
Assume that the rate at the application layer is 1 Bytes/s. if retransmission at each layer is not
considered, the corresponding rate at RLC layer is 1500/1460, namely, 1.027. The rate at MAC-d layer
is 1500/1460 * 336/320, namely, 1.079.
3. Retransmission Overhead
If the TCP layer retransmission (assume that the retransmission rate is r1) and RLC layer
retransmission are considered, the corresponding rate at RLC layer is 1500 * (1 + r1)/1460. The rate at
MAC-d layer is 1500 * (1 + r1)/1460 * (1 + r2) * 336/320.
4. MAC-HS Layer
If there is only one subscriber, without retransmission at MAC-HS layer, the rate at MAC-HS is
(scheduling transport block size TBs)/2ms, and the rate at MAC-d layer is 336 * (TBs/336s)/2ms.
In the DT tool Probe, with consideration of multiple subscriber scheduling and retransmission at
MAC-HS, there are three rate involved at MAC-HS layer: scheduled rate, served rate, and MAC layer
rate.
Served Rate = Scheduled Rate * HS-SCCH Success Rate
MAC Layer Rate = Served Rate * (1- SBLER)
Wherein, the HS-SCCH Success Rate is the success rate for receiving HS-SCCH data by a subscriber,
and SLBER is incorrect TB received at MAC-HS layer/total TBs received.
1. DCH
2. HSDPA
The network does not allocate fixed bandwidth or resources for the PS services carried by HSDPA, but
perform fast schedule every 2ms. Therefore, the throughput that a subscriber can reach depends on
abundant factors, such as:
Therefore, the throughput of single PS service carried by HSDPA fluctuates more sharply than that
carried by DCH. However, HSDPA uses new technologies, such as fast schedule, HARQ, and
16QAM, so the utilization rate of resources is higher, and throughput of whole cell is higher.
3. CCH
FACH can carried PS services of low traffic, it can also bear broadcasting services like CMB.
FACH uses code resource of different SFs, so it support variable channel rate. This depends on the
need by broadcasting services like CMB.
1. Tool Modification
Run the DRTCP.exe attached in the appendix 8.8.1. For the running interface, see the method for
modifying MTU.
Change the TCP Receive Window, such as 65535.
2. Regedit Modification
Detailed operations are as below:
In Windows 2000,
• In HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip,
add string: "TcpWindowSize"="65535"
• In
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Pa
rameters, add double type value TcpWindowSize. Set it to 65535 or ffff (hex).
1. Tool Modification
Run the DRTCP.exe attached in the appendix 8.8.1, with the running interface as shown in .
1. Running interface of
DRTCP
Server
Modify the MTU in Adapter Settings shown in Figure 8-6 , namely, the MTU at the network port.
Test Laptop
For test laptops, the UE is connected to it by data line and dial-up connection is set up. Data packets
are sent through USB port. As a result, modifying MTU of USB port is necessary, namely, the Dial
Up(RAS) MTU as shown in .
After modification, restart the Windows operating system.
2. Regedit Modification
Modifying MTU of server
Modify the MTU of network port on server.
In Windows 2000, in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\
{.........}\, add a double byte value, named mtu, with the value of 1450.
1. Detailed resolution of
Activate PDP Context
Request message
1. Traffic Classes:
The traffic classes in an Activate PDP Context Request message include the following:
Traffic class,
0 0 0 Subscribed traffic class
0 0 1 Conversational class
0 1 0 Streaming class
0 1 1 Interactive class
1 0 0 Background class
1 1 1 Reserved
Among them, Subscribed traffic class is not determined by the UE, but determined by the core
network according to the subscription information of the UE.
3. APN
The APN in the message is a character string in the ASCII format and cannot be read directly, as
shown in the figure below. You can use Ultra Edit to convert the ASCII codes into a character string.
Method of converting ASCII codes into a character string: Open the UltraEdit and create a file.
Click Edit and choose Hex Edit and enter the ASCII codes. Then you can see the character string of
the APN. In the figure below, the character string of the APN starts from the fourth bytes.
• Run UltraEdit
• Create a File
7. APN Effect
1. Major Effect
In GPRS/WCDMA networks, APN has the following effects:
3. APN Configuration
Before configuring APN on GGSN9811, the PDN that can be visited by subscribers must be clearly
known. Set different APNs to different PDNs. For example, the GGSN9811 allows a subscriber to
visit Internet through an ISP and an enterprise intranet simultaneously, and two APNs must be set up
on GGSN9811: one for visiting Internet, and the other for visiting the enterprise intranet.
8. PS Tools
1. TCP Receive Window and MTU
Modification Tools
Modify TCP receive window and MTU with the following tool:
For the detailed method, see the appendix 8.4 and 8.5.
2. Sniffer
4. HSDPA Test UE
In terms of test methods, the PS service test carried by HSDPA is the same as that carried by DCH.
Select the test UEs that support HSDPA.
Now the UEs available in HSDPA PS service test include Huawei E620 data card, Qualcomm
TM6275, and UB TM500.
Huawei E620 data card is a category 12 UE. It supports 5 HS-PDSCH codes at most. It supports
QPSK, but not 16QAM. The maximum throughput at physical layer is 1.8 Mbps. The actual
throughput at application rate is 1.4 Mbps. Huawei E620 data card supports combination of PS and
The MS sends SGSN the Activate PDP Context Request (NSAPI, TI, PDP Type, PDP Address, Access
Point Name, QoS Requested). The PDP Address indicates the dynamic address or the static address. If
the PDP Address is dynamic address, set it to null.
The following aspects lead to unsuccessful PDP activation process: