UMTS PS Service Analysis Guide

UMTS PS Service Analysis
Guide
UMTS PS Service Analysis Guide
1 Introduction
Research on PS data transmission performance belongs to the end-to-end (UE <-> data
service server) category. Every constitutional part of the network may affect the data
transmission performance. When doing data transmission performance optimization,
mostly we focus on RAN side (RNC-NodeB-UE) and other system parts (CN, FTP server
and internet etc.). We usually use exclusive method to judge in which NE the service is
interrupted and in which NE the packet is lost, which leads to the rate decrease. Capture
packets at the interfaces of NEs or use NE tracing function to specify the NE, and then
locate the problem based on NE features or experiences.
2 PS Service Data Transmission Analysis

Method
The upper layer of PS services includes FTP and HTTP services etc. Most services are
established over TCP protocol which is a reliable transmission protocol and
retransmission may occur. Retransmission will have great impact on the rate. If
parameters are improperly configured or packets are wrong or lost during the
transmission, data transmission rate will also be affected. The service quality can be
estimated by using the UE as the Modem, i.e. using UE + PC to dial. Therefore the
performance of the computer and server may also affect the data transmission. In this
case, first confirm whether the problem is caused by the network or other. Usually
methods such as exclusion, separation, and packet capture are used to locate and solve
the problem.
2.1 Universal Analysis Method
2.1.1 Data Collection

End-to-end data transmission process
As shown in the above figure, data transmission optimization involves multiple NEs.
Therefore collecting complete information at different interfaces is important for
2
optimization and problem location. Data collection mainly includes OMC traffic statistics
collection, DT data collection, background tracking of NEs and end-to-end data capture
on the user plane.
2.1.1.1 DT/CQT Data Collection
Currently the DT/CQT is usually carried out using CNT software (connected to the UE,
Scanner or GPS). Thus information such as pilot coverage, signaling flow, DL BLER and
UE transmission power can be obtained. Combining with measurement tracking of users
in OMC-R, UL BLER, DL code field transmission power, UL receiving power and
signaling flow at RNC side can be acquired. Use CNA processing software to make
comprehensive analysis based on data collected by CNT, QXDM, and tracking record in
OMC-R operation and maintenance console.
Note: Time synchronization should be performed before data collection.
Information that should be collected is shown in the following table:
Main Parameters That Should Be Collected Through DT/CQT
Parameter Method Function

Geographic information
CNT+GPS Record the track
(longitude and latitude)
Scrambling code, RSCP,
Ec/Io of cells in the active CNT+UE Analyze the problem
set
Analyze the problem and
UE Tx Power CNT+UE
export the report
Analyze the problem and
UL BLER CNT+UE
export the report
Throughput in UL/DL Analyze the problem and
application layer and in CNT+UE
RLC layer export the report
RRC, NAS signaling at UE

CNT+UE Analyze the problem
side
HSDPA CQI, HS-SCCH Analyze the problem and
scheduling success rate, CNT+UE
throughput at MAC layers. export the report
HSUPA average SG, Analyze the problem and

throughput at layers of CNT+UE
MAC export the report
RNC single user signaling

OMC-R Analyze the problem
tracing
Iub bandwidth OMC-B Analyze the problem
3(62)
Parameter Method Function

DL carrier transmission Analyze the problem and
power and non-HSDPA OMC-R
carrier transmission power export the report
2.1.1.2 Collection of Other Data
Traffic statistics, DT/CQT and user complaints help to find faults. Apart from traffic
statistics and DT/CQT, other tools and their functions can be combined to analyze and
locate faults. Functions such as connection performance measurement and cell
performance measurement of RNC background tracking, alarm query, and status query
of NEs, and tools such as FlashGet, DU Meter can all help to locate faults. In PS service
test, to reduce the effect brought by TCP receive window of the application layer, multi-
thread downloading tool such as FlashGet is recommended and the thread count is
generally set to 5. For UL data transmission, multiple FTP processes can be used for
uploading.
Data That Should Be Collected
Data
Data
Viewing/
Data Collection Function Remark
Analyzing
Tool
Tool
DT/CQT QXDM+UE/
QCAT/CNA
testing data CNT+UE
Connectivity Combining DT/CQT
OMCR/ measuring data and
measurement
, cell analysis RNC tracing data,
make analysis from the Refer to online
performance 1.22.26/sign
perspectives of call help on RNC
OMCR alingCalDat
measurement process and coverage O&M
eRa
and RNC etc. console.
e/runsignal
signaling
UESigStat
tracing
OMCR(OM OMCR(OM View the alarms and
Alarms
CB) CB) find the abnormal NE.
Upload or Multi-thread PS service
FlashGet
download null downloading to get the test assisted
etc.
software stable throughput rate. tool.
Rate DU Meter null Make real-time PS service
monitoring monitoring of the test assisted
software throughput rate of the tool.
application layer, and
record total
throughput, average
throughput rate and
peak throughput rate
(the result can only be
recorded through
4
Data
Data
Viewing/
Data Collection Function Remark
Analyzing
Tool
Tool
screenshots).
2.1.2 Data Analysis Method
2.1.2.1 Common Problem Analysis Method
When problems occur, make tracing of relevant equipment to make the problem recur,
and get the relevant information:
1. Collect configuration and alarm information of relevant equipment. If necessary,

get the traffic statistics of important tasks. Judge whether packets are lost and
retransmitted based on the existing information. Analyze whether there is data
transmission in the uplink and no data transmission in the downlink at SGSN side
or whether there is great delay based on user tracing in SGSN. If the UE cant be
located, use packet capture and exclusive methods to locate the problem.
2. PS data transmission problem mainly includes blocked data transmission,

interrupted data transmission and low data transmission rate. The universal
approach is to make tracing of related UEs or make packet capture at UE
interfaces so as to locate the problem.
3. Take low rate problem for example, it is typical and hard to be located. The problem
usually occurs when the PC accesses the network through the UE to perform the
FTP download or VOD services etc. The procedures to locate the problem are
shown below:
i. Start user tracing in the SGSN and GGSN and monitor and eliminate obvious
faults in signaling plane and user plane. Run packet capture tool (for example,
Ethereal) in the PC (connected to the UE), Gi interface or the server.
ii. After the service is stopped, analyze the captured PPP packets at Gi interface
and UE side. Monitor the UL and DL data flow and confirm whether there is
packets loss, retransmission, or out-of-order etc, which affects the rate. By
data flow comparison at different interfaces, judge which part brings the
problem.
a) To judge whether there is packet loss, check whether the number of UL

and DL packets captured at the UE side is consistent with that at the
Gi interface. If it is inconsistent, there must be packet lost in the
WCDMA system. Analyze user tracing in SGSN, that in GGSN and
captured packets at Gi interface to see in which NE there is incoming
data packets but no outgoing packets. Then the NE in which the
5(62)
packet is lost can be located. Use the relevant NE equipment fault

location method to locate the fault. If permitted, capture packets at Gn
interface and compare the captured packets at Gn and Gi to judge
whether whether the packets are lost at GGSN.
b) For data transmission rate problem, if the UL and DL packet number in

the UE and that at the Gi is consistent, there is no packet loss in the
WCDMA system, and the problem may be caused by large system
delay. Capture packets at the UE and Gi sides, and make comparison
of the UL delay and DL delay. If the delay is large but less than 1.5 s,
and the service is based on TCP protocol, enlarge the TCP window
and run the service again. If the delay is large and less than 1.5 s, and
the service is VOD (RTSP/UDP/IP), response will not affect the DL
packet transmission but may affect the VOD play effect; if VOD service
is discontinuous, set the buffering time to be longer. If the delay is
larger than 1.5 s which is considered to be too large, the problem may
exist at RAN or CN side. If there is no problem at RAN side, there may
be problem at CN side. Conduct mirror packet capture at Gn and Gi
interfaces of the GGSN to judge whether there is large delay at the CN
side. By experience, if there is no hardware bug, the delay at the CN
side should be small.
c) If the packet number in the UL and DL of UEs and that at Gi is

consistent, conduct data packet capture at the UE side to check
whether the retransmitted data at Gi interface has been received, and
whether the received packets are correct (through TCP validation). If
the packets are wrong, which is serious, locate the problem using the
method described in the following sections, or ask help from the R & D
engineers.
The above procedures are targeting at the low rate problems; the procedures to locate
data transmission problem are similar.
2.1.2.2 Typical NE Locating Method
Using the above exclusive method, the NE can be located. As described above, PS
networking (not including access network) mainly involves the following equipment: the
SGSN, GGSN, switch, router, and firewall. Use the following method to locate the NE.
SGSN user plane
Of the equipment listed above, the SGSN is the relatively complicated equipment with
many interfaces, and the data transmission function of the user plane has its own
features. Generally, lu interface between the RNC and SGSN is the ATM port, and the
interface between the Gn and Gp is IP Ethernet port (FE or GE). The data packets of the
UL user plane is transmitted as below: the RNC sends the packets of the user plane to
the forwarding engine of the specified UHPU via the ATM (the IPOA to the RNC has
6
been created in the forwarding engine). If the IP address of this forwarding engine is the
same with that of the destination of the data packet, the data packet will be processed
directly; otherwise, the forwarding engine will search for the route based on the IP
address of the data packet and send it to the destination forwarding engine (PDP context
is created on this forwarding engine).
The procedures to handle the PS service problems relevant to the SGSN are:
1. Check that user tracing function is normal.
2. Confirm that PDP has been correctly created on the user plane.
3. Check whether there is wrong statistics.
The packets are lost at GGSN.
If it is suspected that the packets are lost at GGSN, check it based on packet loss
statistics of the NP layer. The NP problem is caused by the product design; therefore
contact the product engineer to solve the problem.
Packet loss of data communication equipment.
Generally the current data communication equipment supports making packet loss
statistics. Execute commands to query the interface status, check the number of packets
received and sent to see whether there is any packet lost. It should be noted that the
packet loss of the data communication equipment does not indicate the equipment is
abnormal. For example, when filtering rules are configured in the firewall, unreasonable
packets and attacking packets will be discarded. The configuration of the equipment may
lead to the loss of the correct packets. There are many data communication equipment,
please refer to their product command manual to see the command to view the packet
loss statistics.
3 Data Analysis
The data transmission problems of WCDMA PS service falls into three categories in the
aspect of phenomenon: access failure (or dialing connection setup failure), successful
access without the traffic flow, and data transmission with low rate or great fluctuation.
Different problems require different analysis and handling processes.
General DT/CQT data analysis flow is shown as follows:
7(62)
Analysis flow of DT/CQT data
3.1 Basic Problem Analysis
3.1.1 Access Failure

There are two ways to launch the PS service. One is launching the PS service directly
on the UE, and browsing the webpage and watching stream media through the UE
directly. The other is launching the service through personal computer in the method of
PC+UE, and using the UE as the Modem of the personal computer.
In the optimization test, the method of PC+UE is most commonly used. During the
DT/CQT test, the drive test tool software CNT runs on a personal computer, which is
usually a portable one. And this method is shortly called as CNT+UE. If the UE fails to
launch the PS service directly, the engineer can use the method of CNT+UE for further
verification to acquire more information. Therefore, the following problem analysis
focuses on CNT+UE.
3.1.1.1 UE directly launches the PS service
If the UE launches the PS service directly, the analysis flow of access failure is as
follows:
8
Analysis flow of UEs failure of launching the PS service directly
The process of launching the PS service directly on the UE and the process of launching
the PS service in the method of PC+UE are the same in the signaling flow, but they have
different APNs (name of the access point), and setting approaches of the service visiting
address. If the UE fails to launch the PS service directly, the engineer can find the cause
of the problem by taking the following steps.
1. Make verification in the method of PC+UE. If the PS service is normal, then the
system works normally. The engineer should check and modify the settings of APN,
service visiting address, Proxy and password of the UE.
2. If the access failure of PS service launched in the method of PC+UE happens, the
engineer should analyze and locate the problem according to section 3.1.1.2.
3.1.1.2 UE as the Modem of PC
If the UE is used as the Modem of the PC, the analysis flow of the access failure is
shown as follows:
9(62)
Analysis flow of UEs failure of launching PS service
1. Port opening failure
The analysis flow of port opening failure is shown as follows:
10
Handling flow of port opening failure
The main causes of the port opening failure:
i. Incorrect Port Configuration in the CNT
The engineer should check the Port Configuration in the CNT, and make sure
the port No. corresponds to the Com port and the Modem port in the Windows
Hardware Manager.
ii. Abnormal port status
Wrong driver installation and abnormal termination of the drive test tool during
the test may cause the status of the port mapped by the UE to become
abnormal in the Windows Hardware Manager. For example, the yellow
exclamation mark appears.
Solution: Reinstall the driver, insert and extract the data cable or data card of
the UE.
iii. The port is not closed after abnormal termination of the software
11(62)
During the test with the drive test tool such as the CNT, the software
terminates abnormally and may not close the corresponding port.
Solution: The engineer can try to restart the CNT software. If the problem still
exists, restart the personal computer.
iv. Something wrong with the UE software
Try to solve the problem by restarting the computer.
v. Incomplete installation of the UE driver
It is necessary to reinstall the driver, and this problem usually happens when
the personal computer is connected with the UE for the first time.
2. The port is opened successfully, but the access is still a failure.
In this condition, the failure is usually caused by the signaling flow, and the analysis
should focus on the signaling flow during the access process. The analysis flow is
shown as follows:
Signaling analysis flow of access failure
12
Trace the NAS and RRC signaling in CNT or trace the single-user signaling in the
OMCR, and analyze the problems according to the standard data service signaling
flow. The problems may be:
i. RRC connection setup failure
[Description]
Problems appear during the RRC connection setup process (From UE

sending the RRC Connection Request message to RNC receiving the RRC
Connection Setup Complete message).
[Analysis]
If the engineer finds that the UE does not send the RRC Connection Request
message from the RRC Message traced by the CNT, the possible causes may
be:
a) The Modem port is not selected during port configuration in the CNT.
b) The Test Controller in the CNT is not set, or is set incorrectly.
c) The UE port is abnormal. Details can be checked in Port Opening Failure

in the earlier part of this guide.
If the UE does not receive any responses, or receives the RRC Connection
Reject message after sending the RRC Connection Request message, the
possible causes are:
a) Poor coverage
b) Admission refusal caused by uplink/downlink overload
c) Illegal parameter setting
For the illegal parameter setting, the main scenario is described as

follows: the uplink subscription request of the PS service is beyond the
capability of the UE, which leads to the direct refusal from the RNC. After
the RAB setup failure caused by the incorrect parameter setting which is
beyond UE's capability, SGSN will negotiate a new RAB assignment
again to launch a new RAB assignment, until the UE has the capability to
support the assignment, and finally the RAB assignment is finished.
For the users, PDP activation can be successful, and the actual
maximum rate is the maximum rate the UE can support. However, if
even the minimum guaranteed bit rate required by the QoS setting in the
UEs PDP activation request is beyond the UEs capability, although the
network has negotiated a lower rate to accept the PDP activation request
of the UE, the UE will send a request of deactivating PDP when it finds
13(62)
out that the rate negotiated by the network in the PDP activation accept
request is lower than the minimum guaranteed bit rate, and finally, the
PDP activation cannot be completed.
ii. UE does not send the Service Request message.
[Description]
There is no Service Request message in the NAS message.
[Analysis]
The possible causes may be:
a) UE does not open the PS function
Some UEs can be set to support CS, PS, or CS+PS. If the UE is set to
support CS, the PS service cannot be set up. And then it is necessary to
check the UE setting, and modify it to PS or CS+PS.
b) UE does not finish the registration in PS domain.
Viewing from the signaling flow, the engineer finds that UE receives the
Attach Reject message from the network side after sending the Attach
Reject message. The CN side engineer should check whether the PS
service is supported in USIM card subscription.
iii. Problems in the authentication and encryption process
[Description]
The signaling flow between NAS signaling Authentication AND Ciphering REQ
and RRC signaling Security Mode Complete is abnormal.
[Analysis]
The CN side engineer should check whether the authentication switch in the
PS domain of the core network is opened, and whether the cryptographic
algorithm and integrity protection algorithm of CS domain, PS domain and
RNC of the core network are consistent.
iv. PDP activation is refused.
[Description]
The UE sends the Activate PDP Context Request message, but receives the
Activate PDP Context Reject message.
14
The problems fall into two categories. One is incorrect setting of APN and rate
limitation at the UE side and the other is the core network problem.
a) APN setting problem at the UE side.
If the cause value of the Activate PDP Context Reject message is

Missing or unknown APN, the cause is usually that the APN setting is not
in accordance with that of the CN side. The engineer can check the APN
setting at the CNT+UE side, and compare it with the HLR APN. The CN
side engineer should check the user's APN at the HLR.
b) Rate setting problem at the UE side
If the cause value of the Activate PDP Context Reject message is

Service option not supported, the cause is that the rate required by UE is
higher than the subscription rate. The engineer can check the required
rate setting at the CNT+UE side, and compare it with the HLR
subscription rate. The CN side engineer should be clear about the users
subscription rate in the HLR. The current APN and applied rate can be
checked in the Activate PDP Context Reject message.
c) Core network problem
If there are other cause values, and the APN and rate limitation setting at
the UE side is correct, the problem may lie in the core network, for
example, some interfaces of the core network are not through. The
engineer can work with other engineers in the PS domain of the core
network to locate the problem. What is more, if the PS service is
debugged for the first time, the problem may be caused by the case that
the subscription APN in the HLR and that used in the GGSN are
different. The engineer can ask the personnel in charge of the PS
domain of the core network for confirmation.
v. RB setup failure
[Description]
After the Activate PDP Context Request message is sent, the RB setup
message such as the Radio Bearer Setup message is not received, but the
release message is received instead.
vi. Others
Refer to the method described in Section 3.2.3, Comparison and Analysis of

Operation Type and compare the relative parts one by one to narrow the
problem range.
15(62)
3.1.2 No Traffic flow on the User Plane
The PS service is set up successfully on the signaling plane, but there is no traffic flow
on the user plane. The problem analysis flow is shown as follows:
3.1.2.1 Analysis of the Problem at the RAN Side
The successful setup of connection means there is traffic flow on the signaling plane.
But there is no traffic flow on the user plane, which may be caused by the TRB reset at
the RAN side. Especially for HSDPA, the service is borne on the HS-PDSCH, and the
signaling is borne on the associated DCH. When the HS-PDSCH does not have enough
power, there is traffic flow on the signaling plane, but no traffic flow on the user plane.
The following analysis is made from the two aspects of the PS service on the DCH and
the PS service on the E-DCH.
1. DCH Bearer
16
Analysis of no traffic flow on user plane at RAN side on DCH
i. Check the coverage
Trace the service cell pilot RSCP and Ec/Io in CNT+UE mode, and judge
whether this place is with poor coverage. If the RSCP is less than -100 dBm or
the Ec/Io is less than -18 dB, data service can hardly be finished.
Solution: If the RSCP is poor, improve the coverage angle to optimize it. If
the RSCP is fine, but the Ec/Io is very poor, then the following checks are
necessary:
a) Check the pilot pollution, and optimize the seriously polluted pilot.
b) Check the power configuration of the pilot channel, and the power is
always configured as 33 dBm.
17(62)
c) Check and inform the operator to remove the outside interference.
ii. Check the call drop causes
iii. Trace and measure the throughput rate and bandwidth of uplink/downlink.
Through monitoring the change of access layer rate and non-access layer rate
of current connected uplink/downlink data transmission, the engineer can
analyze the dynamic channel configuration function and the changing
characteristic of the service source rate conveniently.
iv. Others
Check the problem at the CN side. Please refer to Section 3.2.3, Comparison
and Analysis of Operation Type for the operation method, and compare the
relative parts one by one to narrow the problem range. Then, make a
feedback about the problem.
2. HSPA bearer
When the PS service is be borne on the HSPA, and the engineer can check the
following items.
i. The alarms in the RNC
Check the alarms record to see whether there is anything abnormal at the
time point of the problem, and provide the diagnostic information.
ii. Deactivate the HSDPA feature, and set up the PS service on DCH.
With DEA CELLHSDPA, the engineer activates the HSDPA feature of the cell,
and builds dial-up connection to set up the PS service on DCH. If the data
transmission of the PS service on DCH fails, please refer to the earlier section
for the handling method. If the data transmission of PS service on DCH is
normal, the problem locates at HSDPA, and the engineer should continue with
the following steps.
iii. Check the CQI, HS-SCCH scheduling success rate, SBLER and whether GBR
is configured.
Trace and record the UE reported CQI, HS-SCCH scheduling success rate
and SBLER reported by the UE.
a) CQI
The UE estimates and reports the UE reported CQI on the base of Ec/Nt
of PCPICH. If the UE reported CQI is zero, the NodeB will not send any
data to the UE. If the parameter configurations of pilot Ec/Io,
CellMaxPower, PcpichPower, and MPO constant are normal, but the CQI
18
is poor, the engineer can try to change the personal computer. PCs with
different model have different noise floors, which will influence the
reported CQI at certain degree.
b) HS-SCCH scheduling success rate
The HS-SCCH Success Rate (%) is the users HS-SCCH scheduling

success rate which is relative to the currently configured HS-SCCH
channel number, accessed HSDPA user number, and the scheduling
algorithm parameter. If one HS-SCCH channel is configured in the
HSDPA cell, the RR scheduling algorithm is used, and all the accessed
UEs continue transferring data, then the HS-SCCH scheduling success
rate of every user is about the reciprocal of the HSDPA user number,
which means all the users share the resource of this HS-SCCH in time
division.
If the users HS-SCCH Success Rate is about zero, then the use's data
transmission rate is about zero, which means there is no traffic flow on
the user plane.
The possible reasons why the HS-SCCH Success Rate is about zero:
There is no data to transfer on the application layer, and the

engineer can confirm this situation by checking the actual
transmission data volume.
The CQI reported by the UE is too low, which causes that the NodeB
does not schedule this user.
c) SBLER 100%
SBLER is the HS-DSCH block error rate. The above WCDMA HSDPA
Decoding Statistics dialog box shows the SBLER and retransmission
conditions under different TB, and in WCDMA HSDPA Link Statistics
window, the HS-DSCH SBLER-Delta and HS-DSCH SBLER-Average
are shown, in which Delta is an instantaneous value, and Average is an
average value. The reason for the SBLER being 100% is that the HS-
PDSCH Ec/Nt is too low, while the fundamental reason is that the
HSDPA power is not enough. If this parameter is not less than the largest
transmission power of the cell, this power configuration is the dynamic
configuration. In the case of dynamic configuration, HS-PDSCH available
power = largest transmission power of the cell - power margin - R99
downlink load (including common channel load) - HS-SCCH power; in
the case of static configuration, HS-PDSCH available = power of HS-
PDSCH and HS-SCCH HS-SCCH power.
From the above two formulate, in the case of dynamic configuration, the
high power margin configuration, or R99 downlink overload or high HS-
19(62)
SCCH power configuration may cause the problem that the HS-PDSCH
available power becomes too low.
Solution: Correct the parameter configuration. If the R99 load is too high, the
engineer should consider carrier addition to solve the problem.
iv. Check the available bandwidth, the occupied bandwidth and the assigned
bandwidth of lub.
If the transmission data configuration is wrong, and the IMA group Nos. of
AAL2PATH (for HSDPA) of the NodeB and the RNC are not corresponding to
each other, then the data transmission will not be through.
If the transmission configuration is in the ATM+IP mode, the HSDPA service is

transmitted in the IP mode, and the signaling is transmitted in the ATM mode,
then the FE interruption will cause the problem that the signaling can be
transmitted, but there is no traffic flow on the user plane.
3.1.2.2 Analysis of the Problem at the CN side
The problem at the CN side may be caused by the service server with problem, the
incorrect user name and password and so on.
20
Analysis of the problem of no traffic flow on user plane at the CN side
The engineer can make sure that the service software server and the service software
runs normally through other access networks (or LAN).
1. LAN
Through the personal computer on the LAN, the engineer can perform the FTP or
HTTP service to make sure that the services are normal and verify the accessible
user name and password.
2. Other radio access networks in the same core network
Establish the PS connection on 3G access networks in the same core network or

on the GPRS, and then check whether the service is normal. If the engineer finds
the service server works normally after finishing the above step, he should analyze
21(62)
the problem at the RAN side. If the engineer finds that the service server works
abnormally, the problem must lie in the CN.
i. HLR
One SIM card can be configured with multi APNs, and each APN corresponds
to a highest rate. When there is no maximum rate limit at the UE side, the
RAB assignment request message delivered by the core network carries the
subscription rate of the user. If there is no limit on the power, code resource
and other resources at the RNC side, the assigned rate will be sent to the UE
through the Activate PDP content Accept message in the NAS signaling, and
the rate in the PDP activation acceptance can be viewed in the QXDM or
other drive test tools.
ii. GGSN
To modify the users QOS parameter on GGSN, the engineer should set the
downlink bit rate and guaranteed rate which are 384 kpbs by default. Set the
maximum downlink rate as 2048 kpbs, so that the CN allows the HSDPA
downlink maximum rate to be 2 Mpbs.
iii. SGSN
The SGSN uses SET 3GSM to modify the users downlink maximum rate and
guaranteed rate to 2 M.
iv. Summary
The checking result shows that the cells have been established. Therefore
problems at the RAN side can be excluded. Then the engineer should check
the HLR subscription rate and the users QoS parameter of the SGSN and the
GGSN at the CN side.
3.2 Problems of Data Transmission Performance

From the aspect of throughput rate measurement, the poor data transmission
performance is represented as unstable and low rate, and great fluctuation. From the
aspect of service quality, poor data transmission performance is represented as poor
stream media graphic quality, the need to buffer stream media and slow webpage
response. The PS data transmission path is shown in Appendix 8.1, and the PS data
mainly passes the internet service server, the GGSN, the SGSN, the RNC, the NodeB,
and finally arrives at the UE. During the transmission, the data passes five interfaces: Gi,
Gn, IuPS, Iub, and Uu. In this process, the internet server communicates with the GGSN
by the IP protocol, and there are one or more route equipment and firewall between
them. The PS service takes the AM mode of the RLC, and it is equipped with the
retransmission function. For the FTP and HTTP service, the TCP protocol, which also
has the function of retransmission, is used for communication. The parameters of the
22
two protocols (RLC/TCP) have great influence on the rate. If the parameters are
improperly configured, or packet error and packet loss happen during the transmission,
the data rate may be reduced. When observing the service quality, the engineer always
uses the application program on the computer with the UE as the MODEM to judge the
quality, then the performance of the computer and the server is involved. Therefore,
there are many factors affecting the PS data transmission performance, and these
factors fall in the categories of the access network problem, the core network equipment
problem, and the application and the service software problem. In this guide, the
application and service software problem and the core network equipment problem are
generalized as the problem at the CN side; and the access network problem is referred
as the problem at the RAN side.
The analysis flow of poor data transmission performance is shown as follows:
Analysis flow of data transmission performance problem
3.2.1 Checking the Alarms

After the problems appear, the engineer should check whether there is alarm appearing.
The alarms of the NodeB and the RNC at the RAN side, and the alarms of SGSN,
23(62)
GGSN, LANSWITCH, ROUTER, FIREWALL and other NEs at the CN side should be
checked. The alarms of the clock problem, the transmission errors, the instantaneous
interruption of transmission and other abnormal conditions of the equipment may affect
the data transmission. If the engineer cannot locate the problem by alarms of NEs, he
should make comparison and analysis of the operation type, and try to screen out the
affecting factors and narrow the range of the problem. If the cause of the PS data
transmission problem can be determined to be at the RAN side, the engineer should
analyze the problem at the RAN side; If the cause of problem can be determined to be at
the CN side, the engineer should analyze the data transmission problem at the CN side.
If the cause the problem cannot be fixed, the engineer should analyze from both the
RAN side and the CN side.
3.2.2 Factors Affecting the Data Transmission at the lub Interface
The Iub interface transmission error, delay jitter, and lub bandwidth problem will affect
the data transmission. The analysis flow is shown as follows:
Analysis of the factors affecting the data transmission at the lub interface
1. Transmission error and delay jitter
The engineer can check whether the problem exists by checking the transmission
alarm and the clock alarm.
2. Iub bandwidth problem
24
The methods of checking whether lub congestion exists are shown as follows:
a) Iub bandwidth performance checking
b) The abnormal record in the signal checking
3.2.3 Comparison and Analysis of Operation Type
Comparison and analysis of the operation type is to find out the NE on which the
problem happens, and tell where the cause of the problem is: the core network or
service software or the access network. The comparison includes the following
operations:
Changing the USIM card, the cell phone/data card and the PC;
Changing the webpage, gateway and the service mode;
Changing the networks in the same server, for example, 2G or other 3G networks
Comparison and Conclusion
No. Operation Result Conclusion

The data The problem may
transmission returns relate to the USIM
to normal. card subscription.
1 Changing the USIM card The cause cannot be
The data located, and the
transmission problem engineer should
still exists. continue the
troubleshooting.
This problem may
relate to UE, for
The data
example, the
transmission returns
compatibility or the
to normal.
UE performance
Changing the cell problem.
2
phone/data card
The cause cannot be
troubleshooting.
This problem may
relate to the drive
The data program installation,
Changing the personal
3 transmission returns APN setting in the
computer
to normal. personal computer,
rate limit setting and
the firewall.
25(62)

The cause cannot be
troubleshooting.
The cause is the
The data problem at the CN
Changing the service in the transmission returns side, and may relate
same server ( making sure to normal. to the service
that the server is in the software.
4
normal working status, and The cause cannot be
trying the PING and stream The data located, and the
media service) transmission problem engineer should
troubleshooting.
The cause is the
problem at the CN
The data side, and may relate
transmission returns to the server
to normal. performance, TCP/IP
Changing the website parameter or the
5 (making the download from service software.
other websites)
The cause cannot be
troubleshooting.
The data The cause is the
Changing other access transmission returns problem at the RAN
networks in the same to normal. side.
6
server, such as the GPRS The data
network. The cause cannot be
transmission problem
located.
still exists.
This problem is
caused by the
The data transmission problem
transmission returns or the improper
to normal. configuration of RNC
7 Testing other NodeBs parameters related
with the NodeB.
The data
The cause cannot be
transmission problem
located.
still exists.
What is more, for further troubleshooting, the engineer can send the data from the upper
level equipment to the UE for comparison.
26
Packet Delivery Check and Conclusion
The downloading The cause is not CN

Delivering packets actively returns to normal and RNC problem
1
from PDN to UE
The downloading The cause is CN or
problem still exists RNC problem.
The cause is the
The downloading
problem at the RNC
Delivering packets actively returns to normal
side.
2 from RNC to UE.
The cause is the
The downloading
problem at the RAN
problem still exists
side.
The cause is the
Delivering packets actively The downloading
3 problem at the IUB
from NodeB to UE returns to normal
interface.
If the engineer still cannot find out where the problem lies after making the comparison
and analysis according to the above operation step by step, he should analyze the
problems step by step in the sequence of the RAN side and the CN side.
3.2.4 R99 Problem

The analysis flow of the poor data transmission performance on DCH at RAN side:
27(62)
3.2.4.1 Factors Affecting the Data Transmission at the Uu Interface (DCH)
If the PS service is on the DCH, the factors affecting the data transmission at the Uu
interface mainly include the allocated channel bandwidth, the state migration occurrence
and the error condition at Uu interface. The analysis flow is shown as follows:
28
Analysis of the factors affecting the data transmission at the Uu interface
1. DCH Bandwidth
When the PS service is on the DCH, RNC allocates certain channel bandwidth for
every accessed UE. The size of the bandwidth is decided by the spreading factor
and the coding method of the code resource.
If the measurement shows that the UEs allocated bandwidth is lower than that in
expectation, there are two possible causes. One is that the channel with higher rate
cannot be allocated to the UE because of the congestion and other abnormal
reasons, which is an abnormal condition. The other is the DRBC algorithm of RNC.
If the parameter of the DRBC algorithm is reasonable, this rate decrease is normal.
Based on the on-site configured parameter, taking the algorithm into account, the
engineer should check whether the current bandwidth allocation and adjustment is
reasonable, whether there is anything abnormal and whether it is necessary to
adjust the parameter to solve the problem. For the low bandwidth caused by
congestion and other abnormal conditions, the engineer can make single-user
tracing, check the downlink load and code resource allocation and the size of the
lub available bandwidth, and acquire the corresponding association log to check
the abnormal printing information, then the clue of the problem can be found.
2. Error at the Uu Interface
The uplink/downlink error at the Uu interface directly affects PS throughput. If the

average values of the measured UL BLER and DL BLER during a certain period of
time are near or better than the BLER Target, the error condition at the Uu interface
29(62)
is normal. Otherwise, it is necessary to analyze the factors causing the error at the
Uu interface.
Power control and coverage are the main factors affecting the uplink/downlink
BLER.
i. External loop power control switch
The engineer should make sure that the RNC external loop power control
switch is open.
ii. Coverage
The engineer should make sure that the uplink/downlink power is limited in the
area with poor UL BLER and DL BLER.
iii. UE performance
The engineer can try to change the UE, or compare the current UE and the
UE of other types.
3. In-sequence delivery
Setting the In-Sequence Delivery to TRUE or FALSE will affect the rate and
fluctuation of uplink data transmission. If the In-Sequence Delivery is set to TRUE,
RLC will keep the transfer order of the high-level PDUs. If it is set to FAUSE, RLC
entity which receives the data will allow the SDUs to be transferred to the high-level
in the order different from that of the sender, and then the uplink data transmission
rate will be low, with great fluctuation. It is suggested to set the In-Sequence
Delivery to True, and the setting can be modified in HLR of CN.
3.2.4.2 Comparison of the Throughputs on APP Level and RLC level
The engineer can acquire the throughputs on APP level and RCL level through DT/CQT
test.
If Throughput on APP level/ Throughput on RLC level is lower than the normal range of
theoretical analysis, it means the TCP/IP retransmission costs too much overheads.
TCP receiving window and MTU setting can be checked and modified.
3.2.4.3 Data Transmission Interruption Analysis
1. Phenomenon: Data transmission is interrupted for a period of time during the

transmission process.
2. Possible Reasons:
30
i. Call drop during the data transmission;
ii. The data transmission is interrupted after the handover from 3G to 2G;
iii. The state migration from CELL_DCH to CELL_FAC and CELL_PCH happens
during the data transmission. When the data transmission is recovered, the
systems cannot migrate back to CELL_DCH status, because the resource is
not enough. And the data transmission will be affected.
iv. Other abnormal conditions, such as transmission interruption
3. Analysis: The engineer analyzes this problem from the aspects of alarms, signaling
flow.
i. Alarms
The engineer checks the alarms of CN and RAN NE, understands the
abnormal condition of the current system, and guide the problem analysis and
troubleshooting. The engineer can find out the problems such as the
transmission interruption, the cell clock asynchronizaiton and the NE
congestion through the alarms.
ii. Signaling Flow
The data transmission problem location mainly depends on the signaling

specific analysis, for example, judging whether there is call drop, handover
from 3G to 2G, and channel state migration. There are two ways to collect the
31(62)
signaling: one is to use CNT+UE to collect the signaling sent and received at
the UE side, the other way is to use the OMCR single-user tracing to collect
the signaling sent and received at the RNC side. Through the comparison of
the signaling collected by the two ways, the engineer can check whether there
is message loss caused by the air interface with poor quality. What is more,
the engineer can take the association log into account to locate the problem.
a) Call drop
b) Channel state migration
After the channel status is migrated to the common channel, the channel
cannot migrate back to the CELL_DCH status. The engineer can check
the signal to check whether the problem is caused by the downlink
overload or the lub bandwidth congestion. To solve the problem, the
engineer can add the carriers or the transmission resources.
c) Handover between 3G and 2G
The data transmission failure caused by the handover from 3G to 2G

relates to the coordination of the two networks. If the 2G network is HWs
network, the problem location is even harder. Firstly, the engineer checks
whether the PS service can be normally set up on the 2G system. If the
data transmission is normal when the 2G network is accessed, and it
becomes abnormal after the handover, then the engineer should check
the UE side, and the signaling flow at the 3G and 2G equipment. The
cause of the problem may be the unsuccessful update of the routing area
caused by the inconsistent cryptographic algorithm configuration of
subscription and Authentication.
3.2.5 HSDPA Analysis
HSDPA schedules power and code resources among multiple users in code-division or
time-division mode. Under the single-user condition (that is when there is only one
HSDPA user in the cell), the factors that affect data transmission rate are available
power for HSDPA, the number of HS-PDSCH codes (only one HS-SCCH channel is
needed under the single-user condition), the UE category (the maximum number of
codes supported by the UE and the availability of 16QAM support function), radio signals
at the location of the UE, the UEs subscription rate, Iub bandwidth, and the maximum
rate supported by the RNC, NodeB, GGSN, and SGSN. Under the multi-user condition,
apart from the above factors, the algorithm used in the NodeB, the number of HS-
SCCHs configured for the cell will also affect the data transmission rate.
32
3.2.5.1 HSDPA Working Process
1. The UE reports CQI on the HS-DPCCH, and the NodeB acquires the channel
quality of the location of the UE.
2. The scheduling module in Node B evaluates different UEs on the channel

condition, the data volume in each UEs buffer area and the latest service duration
to determine the HS-DSCH parameters.
3. The NodeB sends the HS-DSCH parameters on the HS-SCCH, and then sends the
parameters on the HS-DSCH after 2 slots.
4. The UE monitors the HS-SCCH to see whether there is any information for itself. If
there is, then the UE starts receiving data from the HS-DSCH and then cache the
data.
5. According to information on the HS-SCCH, the UE can judge whether to integrate

the data received from the HS-DSCH with that in the soft buffer area.
6. The UE demodulates the data received from the HS-DSCH, and sends the
ACK/NACK in response to the uplink HS-DPCCH according to the CRC results.
7. If the NodeB receives NACK, it will resend the data until it receives ACK from the
UE or until the number of resending times reaches the maximum value.
3.2.5.2 Whether Services are Borned on HSDPA
Judge whether the services are based on HSDPA from the following aspects:
1. Whether the cell supports HSDPA: Check whether the HSDPA cell at the RNC side
has been activated, and whether the attribute of the local cell at the NodeB side
has been configured to support HSDPA.
2. HSDPA services access failure will also cause the RNC to reconfigure HSDPA
services to 384 kbps as R99 services. Check whether the following configurations
are reasonable: the uplink and downlink load of R99 services, downlink code
resource, Iub transmission resource, the number of HSDPA services users, the
total rate threshold in the HSDPA cell, the guaranteed rate threshold and the
guaranteed power threshold of stream services.
3. The HSDPA threshold of downlink BE services is too high. The HSDPA threshold of
downlink BE services determines the rate decision threshold of the PS domain
Background/Interactive services on the HS-DSCH. Only when the maximum
downlink rate of the PS domain Background/Interactive services is not less than
this threshold, can the services be borne on the HS-DSCH; otherwise, they will be
borne on the DCH.
33(62)
3.2.5.3 Locating Scheduled Rate Problem
During the NodeB scheduling process, TB size is decided by CQI, code, and power. And
TB size/2 ms is the scheduled rate. In the normal condition, scheduled rate and the UE
reported CQI are in a mapping relationship (which depends on the NodeB CQI mapping
table in practical use). Strictly speaking, because the NodeB will filter and correct the UE
reported CQI, in fact the scheduled rate may be in a mapping relationship with the
NodeB scheduled CQI, rather than with the UE reported CQI. Therefore, the following
table shows the corresponding relation between CQI and the reference TB size
according to the protocol 25.214, and the relation between CQI and the scheduled rate
can be worked out.
34
CQI Mapping Table When UE Level Is 11-12

Transport Block Number of HS- Reference Power
CQI Value Modulation
Size PDSCH Adjustment
0 N/A Out of range
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
19 3319 5 QPSK -4
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
25 3319 5 QPSK -10
26 3319 5 QPSK -11
27 3319 5 QPSK -12
28 3319 5 QPSK -13
29 3319 5 QPSK -14
30 3319 5 QPSK -15
CQI Mapping Table When UE Level Is 1-6

CQI Transport Number of Reference Power
Modulation
Value Block Size HS-PDSCH Adjustment
0 N/A Out of range
1 137 1 QPSK 0
2 173 1 QPSK 0
35(62)
CQI Transport Number of Reference Power

Modulation
Value Block Size HS-PDSCH Adjustment
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 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
The factors that affect the scheduled rate are CQI, HSPDA cell available power, and
HSDPA cell available codes. The analysis can be made from the following perspectives:
1. CQI
i. Problem of low CQI
If the UE downlink rate is low, check whether the UE reported CQI is too
low and at the same time check the RSCP and Ec/lo of the PCPICH in
the current cell. The problem may be caused by:
a) The coverage is poor and the UE reported CQI is low.
b) Interference is relatively serious, the pilot is polluted, and the UE

reported CQI is relatively low.
c) If the HSDPA user changes cells frequently, he/she will be forbidden

changing cells as a punishment. Therefore the UE reported CQI will be
low.
d) Poor receiving performance of some UE built-in antennas or UE

individuality will also cause low UE reported CQI and therefore affect
rate.
36
ii. Solutions:
a) For the poor coverage problem, optimize RF or add sites to improve the
UE reported CQI.
b) For the serious interference problem, optimize RF to adjust the antenna

directional angle and the down tilt angle to provide a dominant serving
cell.
c) For the problem of the frequent change of HSDPA cells, optimize RF to

adjust the antenna directional angle and down tilt angle or add sites to
avoid frequent handover. In addition, in our system, there is a timer
(T1d), which defines the punishment time between cell changes. This
time is 4 seconds by default, but in fact, this time is too long so that it
affects the HSDPA throughput rate. Therefore, the plan is to set it to 0
second or 2 second.
d) For the UE problem, it is suggested to exclude other problems before

changing it.
2. HSDPA cell available power
If the available power for the HSDPA cell is too low, it will affect the TB size during
the NodeB scheduling process.
If HSDPA power is dynamic configuration, HSDPA available power = total power of

the cell x (1- power margin) - the power of R99 service channel and common
channel.
The available power of HSDPA cells can be affected by the following factors:
i. HS-PDSCH MPO constant
The HS-PDSCH MPO constant can be modified in the RNC OMC. Under the
condition of HSDPA, the UE reports CQI, and according to the reported CQI,
the NodeB can judge the quality of the current radio link and adjust the TB
size and the power. When the UE reported CQI is less than 5, the NodeB will
not send data to this UE. And the MPO constant can adjust the UE reported
CQI, which can be calculated based on the pilot Ec/Nt.
ii. HS-SCCH power
The HS-SCCH power can be configured in static mode or dynamic mode. In

static mode, the HS-SCCH power is configured to a percentage of the
maximum emission power of the cell. This percentage is 2.5% for now. In
dynamic mode, the power of the HS-SCCH can be adjusted dynamically.
37(62)
3. HSDPA cell available codes
Configuration of SF for the downlink physical channel of HSDPA cells: While

configuring SF for the HSDPA cell, in addition to the common channels as for R99
cells, SF codes should also be reserved for the HS-SCCH (static configuration
only) and the HS-PDSCH (when code resource is allocated in static mode). For the
HS-SCCH, SF is fixed to 128, and for the HS-PDSCH, SF is fixed to 16. In this
condition, R99 users cannot take the code resource configured for HSDPA.
i. When the code resource is allocated in dynamic mode, usually the OMC will
assign the initial number of HS-DSCHs, the maximum number of HS-DSCHs
and the minimum number of HS-DSCHs. The number of HS-DSCHs occupied
by users should be between the maximum one and the minimum one. If more
R99 CS users need to access the network, they may take the HSDPA code
resource.
ii. HSDPA accompanies the DCH code resource allocation. When a user applies
the high speed PS services, the system will bear the services on HSDPA. This
user occupies the HS-SCCH and the HS-PDSCH, and meanwhile when the
services are being established, the user will be assigned with an associated
DCH (A-DPCH) to transmit signaling at 3.4 kbps. This channel is a dedicated
downlink channel with SF256.
iii. If the codes allocated to HSDPA users are too few, the TB size scheduled by
the NodeB will also be affected.
4. HSDPA UE capacity
i. Protocol 25.306 specifies 12 categories of UE. In one TTI, different UE

categories obtain different maximum TB sizes. Therefore the maximum
scheduled rate obtained by the UE is different.
ii. In the message RRC Connection Setup Complete the UE will report its
capacity. The IE (information element) of HSDSCH physical layer category
reflects the UEs ultimate capacity.
5. The data volume that can be scheduled by the UE is smaller than the largest TB.
The TB size scheduled by the NodeB depends not only on the UE available power
and codes, but also on the data volume that can be sent by the UE. If the data
volume sent by the UE is smaller than the largest TB, then the physical layer rate
will be lower than the expected value. This problem usually occurs when there is
still data in the NodeB buffer area, but the data volume is smaller than the largest
TB that can be scheduled.
38
3.2.5.4 Analysis of HSDPA Data Transmission Interruption
One RAB can be mapped only to the HS-DSCH of one cell, which means that it does not
support soft handover. Therefore data transmission will be interrupted when the serving
cell is changed.
The data transmission interruption can be divided into two types:
1. Serving cell remains unchanged or no handover happens.
2. Serving cell changes or handover happens.
Data transmission interruption happens when the serving cell remains unchanged or no
handover happens, and the possible causes are as follows:
1. Call drops or TRB resets.
2. Other problem appears, such as the breaking of transmission or complete of data

download.
Perform the following steps to locate the problem:
1. Check the alarms.
Check the alarms of different NEs of the CN and RAN to see the operating status of
the system. This can guide the troubleshooting. Check the alarms for transmission
interruption, clock synchronization failure, and NE congestion.
2. Check whether the download of the file is completed.
During the data transmission, if the data transmission is interrupted for a long
period and cannot be recovered, checked whether the FTP download is completed.
3. Check the signaling flow.
Analyze the signaling of the RNC and UE to check for call drops, H2H serving cell
changes, or H2D/D2H handovers. For the transmission interruption caused by call
drops, analyze the reasons of call drops.
4. Analyze the transmission interruption duration
Use Ethereal to capture the TCP/IP packets, and analyze the transmission interval
between different TCP/IP packets.
3.2.6 HSUPA Analysis

PS data transmission performance reflects the system performance in an end-to-end
perspective (UE <-> data service server). Each component of the system may impact
39(62)
the data transmission. When testing and optimizing the HSUPA data transmission
performance, we usually focus on the impact from the RAN side (RNC-NodeB-UE).
Impacts brought by other components of the system, such as the CN side (SGSN,
GGSN), data service server, and external network, should be eliminated before the
testing. Then, we can focus on the optimization of the radio network.
From the throughput rate aspect, when the data transmission performance is poor, the
rate is instable, low, or fluctuates greatly. From the QoS aspect, the image of the
streaming media blurs, the watching may be blocked, and the webpage opens slowly.
3.2.6.1 HSUPA Working flow
1. The UE sends the Scheduling Information through the E-DPDCH to request for the
data transmission. The Scheduling Information is determined by UE Power
Headroom (UPH) and _Q (Data volume to be transmitted).
2. The NodeB will determine the grant level based on SI sent by the UE, measured
RoT, and the Happy Bit sent by the UE (carried by E-DPCCH). Then the NodeB
would send T/P through E-AGCH and the tuning command (+1, 0, -1) through E-
RGCH.
3. The UE sends the data based on the grant level, and sends SI for the next frame
and Happy Bit about the grant level through E-DPDCH.
4. After the NodeB receives the demodulation data, it returns ACK/NACK through E-
HICH to feed back whether the data reception succeeds.
3.2.6.2 Whether Services are Borne on E-DCH
Check whether the services are borne on E-DCH through servingEDCH_RL_indicator in

the RB SETUP message. If the indicator is True, the service is borne on E-DCH, as
shown in Error: Reference source not foundollowing picture.
40
The services will be borne on DCH if they are not borne on E-DCH, and then the service
rate will be that for R99 services, which is usually 384 kbps or lower.
If the service is not borne on E-DCH, analyze this problem from the following aspects:
1. The UE will indicate whether it supports HSUPA and HSDPA in the

RRC_CONN_REQUEST message. Check whether the UE supports HSUPA, and
check the UE E-DCH level in the rrcConnectionSetupComplet message.
2. Check whether the MBR in the UL subscription information is normal, and check
whether the rate threshold of the E-DCH is too high. If the MBR assigned by the CN
has not reached the rate threshold of E-DCH, the service will be borne on DCH.
3. Check whether the HSUAP cell is activated.
4. The admission of HSUPA users failed.
3.2.6.3 Locating Serving Grant Rate Throughput Problem
Serving Grant Rate Throughput is the Scheduled Rate. To locate this problem, compare
the current Serving Grant Rate Throughput and the maximum allowed ETFC based on
the ETFC of the current SG and the Happy/Unhappy Bit sent by the UE.
Note that when the UE sends the Happy Bit does not necessarily mean that the users
are happy with the current rate. Analyze the reason that the UE sends the Happy Bit.
The Serving Grant Rate Throughput is abnormal. To confirm this, check whether the UE
reports Happy Bit or Unhappy Bit.
If the UE sends the Happy Bit, while the rate cannot reach MBR, the possible causes are
as follows:
1. UE capability or RAN capability restriction
2. UE TX power restriction
3. UE traffic volume restriction
If the UE sends the Unhappy Bit, and the user rate cannot reach MBR, the possible
causes are as follows:
1. SG (UE grant) restriction
2. RAN resource restriction, such as the air interface load, Iub bandwidth, and CEs
i. Cause one: Air interface load restriction
ii. Cause two: Iub bandwidth restriction
41(62)
iii. Cause three: NodeB CE restriction
As specified in the protocol, the UE shall indicate that it is unhappy if the following
criteria are met:
1. UE is transmitting as much scheduled data as allowed by the current Serving

Grant; and
2. UE has enough power available to transmit at higher data rate; and
3. Total buffer status would require more than Happy_Bit_Delay_Condition ms to be

transmitted with the current Serving_Grant x the ratio of active processes to the
total number of processes.
The first criterion is always true for a deactivated process and the ratio of the third
criteria is always 1 for 10ms TTI.
Otherwise, the UE shall indicate that it is happy.
1. The UE reports it is happy.
i. UE capability or RAN capability restriction
Principle:
If the HSUPA physical layer category of the UE is CAT5 (corresponding to 2-Mbps

MAC-e), then the RAN can maximally support 2 x SF4 (corresponding to1.4484-
Mbps MAC-e). The maximum rate that a single UE can acquire is restricted by the
capability of the RAN.
UE HSUPA physical layer categories
Observing method:
a) Checking the UE capability
Generally, the UEs that support HSUPA will support HSDPA. In other
words, the HSPA carries the user services as a whole. The following part
would check whether the UE supports the HSPA and the specific HS-
DSCH/E-DCH physical layer category based on the RRC messages.
42
Firstly, the UE will report whether it supports HSDPA and HSUPA in the
RRC_CONN_REQUEST message. As shown in following picture, we
can see that the UE supports HS-DSCH and E-DCH.
The specific E-DCH physical layer category will be displayed in the

rrcConnectionSetupComplete message. As shown in following picture,
the HS-DSCH physical layer category is 8 and the E-DCH physical layer
category is 6.
43(62)
b) Observing the maximum capability configured at the RAN side
When the services are constructed, the RNC sends the RL RECFG
PREP message to the NodeB, which includes the maximum spreading
factor that the UE can use. The corresponding cell is maxSet-E-
DPDCHs. In following picture, maxSet-E-DPDCHs = 9 indicates that the
UE supports two SF4+2SF2 spreading factors.
Solution:
Improve the capability of the RAN, or use the UE of higher capability.
ii. UE TX power restriction
Principle:
The UE can calculate the TB size based on the current available TX power. Then
the UE will compare the TB size supported by the TX power and that supported by
SG, and then choose the small one as the actual TB size. Though the UPH of
44
different UEs is the same, their TB sizes may be different. The following factors
affect the TB size:
a) The UE is at cell edge, and the path loss on the UL is great;
b) The UL load of the cell is heavy (the UE is not at the cell edge);
c) The UE is performing hybrid services, and the DCH services occupy too
many resources, and the remaining power for E-DCH is limited.
Solution:
a) If the UE is at cell edge, move the UE to the cell center;
b) If the UL load of the cell is too high, lower the cell load (if possible);
c) If the UE is performing hybrid services, deactivate the R99 services and

then observe the rate of HSUPA services.
iii. UE traffic volume restriction
Principle:
Insufficient data volume in UE RLC buffer leads to low MAC-e PDU Non-DTX Rate.
Solution:
Try to use the UL packet delivery method to exclude the impact of TCP. If this still
does not work, check whether the packets are lost at certain link.
Sometimes the application software of the PC may affect the data transmission.
Change a portable computer. If the problem still exists, use the tool to capture the
packets to locate the abnormality between the PC and the UE.
2. The UE reports the Unhappy bit.
i. SG (UE grant) restriction
The HSUPA scheduling has two basic functions:
[Function one]: Control cell load;
If the actual load of the cell is heavier than the target value, reduce the UE SG to
reduce the cell throughput rate, when the actual load of the cell is less than the
target value, increase the SG of the UEs reporting Unhappy Bit to increase the cell
throughput rate.
[Function two]: Perform MBR rate restriction for single UE.
45(62)
When the MAC-e rate (including retransmission blocks) of a single UE is larger

than MBR, the RG Down message will be sent to reduce the SG of the UE, thereby
decreasing the UE TX rate. This helps to ensure that the actual rate approximates
MBR.
The UE upgrades the SG information through AG and RG (UP, Hold, Down) sent by
the NodeB. The UE would refer to the SG when deciding the actual TX rate, so the
actual TX rate will be lower than or equal to that specified in SG.
ii. RAN resource restriction, such as the air interface load, Iub bandwidth, and
CEs
The resource restriction at the RAN side will leads to the fact that the UE SG
assigned by the NodeB is small, which will further lead to that the UE reports the
restriction of SG.
Cause one: Air interface load restriction
Solution:
a) Set the ROT target value properly.
b) Set the background noise equal to the actual value.
c) Eliminate the inter-RAT interference.
Cause two: Iub bandwidth restriction
Solution:
Increase the available Iub bandwidth for HSUPA.
Cause three: NodeB CE restriction
Solution:
Add CEs.
iii. Service MBR restriction, such as NodeB MBR restriction
Solution:
To increase the throughput rate, the subscription information must be modified, and
a larger MBR should be configured.
iv. UE demodulation error, for example, the AG CRC verification error leads to
the failure of the SG upgrade, or the incorrect UE RG demodulation.
46
Cause one: The CRC verification error of the AG value leads to the failure of
the SG upgrade.
Cause two: The demodulation of UE RG is incorrect.
Solution:
As to cause one, increase the E-RGCH power offset based on the baseline
parameters and the coverage at cell edges.
As to cause two, fix the UE.
3.2.7 Poor Data Transmission Performance at CN Side
3.2.7.1 Problem Analysis Flow
The following picture shows the analysis flow for poor data transmission performance at
the CN side.
47(62)
Poor data transmission performance at CN side
3.2.7.2 Congestion Avoidance
The packet losses at the CN side will lead to RTT timeout, which will trigger congestion
avoidance. The TCP can provide reliable transmission layer. One of its functions is to
acknowledge the message sent by the other end. However, both the data and
acknowledge messages may be lost. To solve this problem, the TCP will trigger a timer
when sending the data. If it fails to receive the ACK message after the timer expires, it
will retransmit the data. The TCP TX end will measure the RTT value, which is the length
of time it takes for a signal to be sent plus the length of time it takes for an
acknowledgment of that signal to be received, and will maintain an RTT timer. If the
measured RTT has timed out, the TCP will think that the network is congested, and will
trigger congestion avoidance. Thus, the data transmission rate is affected. The IP packet
losses at the CN side will lead to RTT timeout.
48
3.2.7.3 Environment Issue
Rate is also related with the performance and the operating system of the computer, as
well as the installed application software, because the inner algorithm of the application
software and the TCP parameters of the operating system may have great influence on
the performance. Similarly, the PS data transmission rate of the computer with WIN2000
operating system is better than that with WIN98 operating system. Therefore it is
recommended that the computer and server should be installed with WIN2000 Pro and
WIN2000 Server respectively or high versions. Because the portable computer is usually
installed with WINXP, the performance issue caused by the operating system does not
exist. However, the server should use WIN2000 Server rather than WINXP, otherwise
the data transmission will be seriously affected. The computer working as the UE
background must be able to provide better performance. It is verified that the IBM
provides better performance when demonstrating the VOD. If the CPU usage of the
portable computer reaches 100% at the RX end, the TCP receive window will be full.
When the TCP receive window is full, the RX end will inform the TCP TX end, and then
the TCP TX end will stop the data transmission. As a result, RLC BO is zero, the NodeB
cannot perform the data scheduling, and the data transmission performance is affected.
Meanwhile, the performance of the server may also affect the services, and this is
another factor that we must consider.
3.2.7.4 TCP Receive and Send Windows
For services using the TCP protocol, such as VOD and FTP, the sizes of the TCP
windows on the test computer (as the Client) and the server have great influence on the
service. The window size is usually set to a large value to ensure good performance,
and the window sizes on the Client and the Server should be the same. Theoretically,
the TCP receive window should be larger than the product of bandwidth and delay.
Capacity (bit) = Bandwidth (b/s) x Round-trip time (s)
The 64-K window is sufficient for the HSDPA CAT12 1.6-MHz bandwidth, but it is
insufficient for the HSDPA CAT6 3.6-MHz bandwidth. Especially when the delay is larger
than 200 ms, the TCP window may be easily fully occupied. Then we will observe that
RLC and NodeB buffer is 0.
Solution:
Set the TCP window size of the portable computer to 80 Kbytes.
3.2.7.5 Maximum Transmission Unit (MTU)
If there is one data packet to be transmitted at the IP layer, with its length larger than that
of the MTU at the link layer, then the IP layer will divide the packet into different
segments. Each segment is shorter than the MTU. To improve the transmission
efficiency, we should avoid the IP segmentation and regrouping and use a longer MTU
49(62)
(usually does not exceed 1450 bytes). To modify the MTU length, modify the MTU at the
server and the portable testing computer. After the PS services are connected, the
Server and Client will negotiate about the MTU length. Then, the shorter MTU is used.
3.2.7.6 Service Related Problems
1. FTP
When selecting the FTP software, the commercial FTP is preferred. It usually
provides better services than the FTP software of the operating system. Besides,
the FTP uses the binary mode to download the data. Thus, you are advised to use
the multi-thread download software, such as FlashGet. If the upload rate is low, you
can use multiple FTPs to perform the transmission, or use the software to send the
packets at a fixed rate to test the bottom layer.
2. VOD
The maximum transmission rate of the RealPlay should be larger than 384 K, and
the buffering time should be short, for example, 3 s. As to some portable computers
with poor graphics cards, frequency hopping may appear. You can set the
resolution ratio to 800 x 600 pixels. If the problem still exists, replace the graphics
card.
3. NetTV
When the rate at the bottom layer is reduced, the performance of NetTV is hard to
recover. You must pay special attention to this point.
4. Video conference
The output rate of the video conference should be slightly less than the rate at the
bottom layer, otherwise packet losses will occur. For example, the rate for the
NetTV of one vendor is set to 128 K initially, which will be increased by 64 K every
time. Actually the recommended value for this NetTV is 320 K. If this rate is too low,
the bandwidth cannot be fully used; otherwise, a rate higher than 320 K, such as
384 K or higher, may lead to packet losses because the bottom layer cannot satisfy
the demand. Then the effect of video conference will be influenced. The lightning
bolt on the upper right corner of the screen indicates that there are some error
codes or some packets are lost during the transmission process.
50
4 Typical Case Analysis
4.1 RAN Cases
4.1.1 Call Drops Due to Congestion (Iub Resource Limited)

Problem description: In one project, there were numerous testing 3G UEs or data
cards and their services were free. Therefore the traffic model of this area is special: the
busy traffic hours are usually around 23 oclock and then PS call drops occur.
Problem analysis: Performance statistics shows that the traffic of this cell is relatively
heavy. Iub bandwidth is 1 M and the band is fully occupied. If the user logs on to the
internet and there is continuous data transmission, the status is stable. If the user
browses a webpage and there is no data transmission for a period of time, the UE will
switch to idle state based on the DRBC algorithm. In this case, if data transmission is
required, the resources should be applied again; because the resources are used by
other users, the application will fail, the connection will be broken, and call drops
happen. Only when the user number is reduced can the service be successfully
established again. The problem is caused by too many users, therefore try the following
methods to solve the problem:
1. Reduce the testing users.
2. Add Iub bandwidth.
4.1.2 Low HSDPA/HSUPA Downloading Rate of One New Site

Problem description:
HSDPA downloading rate of one site was low, which was 4 M; HSUPA downloading rate
of that site was even lower, which was about 400 K. On the same conditions, uploading
and downloading tests of R99/PS 384 K were conducted, and the services were found to
be normal.
Fault location:
Based on UE logs and LMT measurement, it was initially concluded that it was caused
by UL packet loss. The Uu interface rate was obviously higher than the RLC rate.
Packets of the site were captured and analysis was made. It was found that there was
packet loss from the NodeB to the RNC and packet loss based on the data capture of
the CCI board of the NodeB. Special attention was paid to packet loss based on the data
capture of the CCI board of the NodeB, but no fault was located. Then the problem of
the packet loss from the NodeB to the RNC was checked. BPO equipment room
engineer checked the GIPI boards and no exception was found. Packets were pinged
from the CCI board of the NodeB to Switch 6513 of the Iub interface, and 8 out of 100
51(62)
packets were lost. The operation was repeated three times, and the results were the
same. The Ethernet cable was used to connect the SP directly (skip Switch 2818) to
BBUB and to ping Switch 6513, none of the 100 packets was lost. Therefore it was
concluded that there was packet loss between Switch 2818 and BBUB. Considering the
Ethernet cable between BBUB and Switch 2818 was self-made, the engineer changed
the cable to ping packets to Switch 6513, and there was no packet loss. Therefore the
problem must be caused by this self-made cable. The following picture compares the
application layer rates with the abnormal cable and the normal cable.
Application layer rate comparison with the abnormal Ethernet cable and the normal
Ethernet cable
Solution: Change the Ethernet cable between Switch 2818 and BBUB.
4.1.3 Low HSDPA Downloading Rate of One New Site

The HSDPA downloading rate of one site was low, which was about 3.5 M.
Fault location:
Investigation showed this site was adjacent to another testing site which was not
configured as its neighbor cell and thus brought strong interference to this site.
Therefore the testing site should be blocked during the HSDPA downloading.
The following picture shows the comparison before and after the testing site was
blocked. Please pay attention to the change of CQI.
52
CQI comparison before and after the testing site was blocked with QXDM
After the testing site was blocked, the HSDPA rate increased to 4.5 Mbps, which was
relatively low. Further investigation indicated that there was another exception:
Attempts to ping packets from the CCI board of the NodeB to Switch 6513 were
conducted.
When the cell had no HSDPA downloading service, none of the 100 packets were lost.
Ping statistics for 10.10.42.254:
Packets: Sent = 100, Received = 100, Lost = 0(0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2 ms, Maximum = 3 ms, Average = 2 ms
When the cell had HSDPA downloading service, 3 to 8 of the 100 packets were lost.
Ping statistics for 10.10.42.254:
Packets: Sent = 100, Received = 94, Lost = 6(6% loss),
Approximate round trip times in milli-seconds:
Minimum = 2 ms, Maximum = 3 ms, Average = 2 ms
SP was connected directly (skip Switch 2818) to the NodeB. Data was captured in
Switch 2818. The result showed that packets had been sent to Switch 6513, but no
packet was returned, as shown below:
53(62)
Data capture of ping packets to Switch 6513 on the CCI board of the NodeB
Therefore it was concluded that there was packet loss from Switch 2818 to Switch 6513.
FST-2802 device was used to test this Iub interface and there was a serious problem of
packet loss.
Solution:
After the SP has repaired the transmission, HSDPA downloading becomes normal.
Suggestions:
There are two factors affecting the HSDPA downloading rate: signaling quality and Iub
interface transmission. The two factors should be checked one by one.
4.1.4 Low HSDPA Downloading Rate of Another New Site
The HSDPA downloading rate was low and the service was unstable.
Fault location:
Seen from the map, the site was very close to another site.
54
Site location
The QXDM showed:
55(62)
Site shown with QXDM
This area was seriously polluted. Engineers blocked one site and the HSDPA
downloading rate became normal, as shown below:
56
Testing result after one site was blocked
Solution:
Perform radio network optimization to solve the pollution problem and the HSDPA
downloading rate becomes normal.
4.2 CN Cases
4.2.1 Computer Firewall Disabling PS Service

One user found that his MR632 inserted in one computer was not able to perform the PS
service.
Problem analysis:
The user complained that MR632 was normal, but one day it did not work. The problem
must be caused by the computer. Investigation showed that this user had newly installed
the firewall. After the firewall was uninstalled, the service became normal.
4.2.2 Low PS Service Rate of One Demo Site

57(62)
The PS HSDPA downloading rate of one demo site was low.
Problem analysis:
Tests and analysis show that the access network seemed to be problematic. Based on
the fault location concept, engineers traced detailed user signaling, and collected
statistics of the user plane, information of Uu-interface quality and information of packet
loss on the Iub interface, nothing was found abnormal. The network planning engineers
arrived at the site, and signaling was found to be normal. The engineer changed the PC,
and HSDPA service became normal. Then the problem must be caused by the driver of
the public portable computer. After the portable computer was changed, the problem was
solved.
4.2.3 FTP Unable to be Stopped After Long-Time Downloading
Engineers from the operator complain that the service can not be normally stopped
when downloading a file longer than 10 minutes in the 3G network. In the networks of
other operators or in 2G networks, there is no such problem.
Problem analysis:
Analysis on the FTP messages captured in ethereal shows that the data session had
been transmitted, but the control session had no interaction completion process. There
was no 221-Goodbye character but the downloaded file could be normally opened. As
shown in following picture, the file had been downloaded and could be used normally.
58
CuteFTP interaction interface
To make it clear, a comparison between the signaling messages respectively for normal
FTP downloading and abnormal FTP downloading is provided here.
The following messages appeared during the normal FTP downloading process.
59(62)
Normal FTP downloading process
The following messages appeared when the service was abnormal.
Abnormal FTP downloading process
60
Carefully compare the two figures and the problem will be found. Engineers used
Qualcomm 6250 to activate PS service downloading, and captured packets at RNC and
SGSN sides respectively to make analysis.
1. The engineer used the FTP tool of the operator to download a 3.5-M file for about
12 minutes, and the problem occurred.
2. The engineer executed the FTP command of the Windows operating system to
download a 3.5-M file for about 30 minutes, typed bye to quit, and the problem also
occurred. During this process, outlook was transferring data in the background, which
might affect the service. The service was disconnected abnormally a long time after the
transfer was completed, which was also abnormal.
3. The engineer executed the FTP command of the Windows operating system to
download a 0.4-M file for about two minutes, typed bye to quit, and there was no
problem.
4. The engineer used the FTP tool of the operator to download a 0.4-M file for about
two minutes and there was no problem.
5. Same as Step 2, the engineer disconnected the downloading service in the outlook,
and the result was the same.
Then it could be concluded that the problem was related to time instead of the file size. A
lot of statistic analysis shows that the FTP data transmission was normal and the content
was correct and usable, except that the signaling could not be normally closed. The
engineer used the method of changing the NE (UE or server) to locate the problem.
Conclusion:
The engineer used different UEs, and FTP servers to make the test, and the same
problem occurred. Therefore the problem must lie in the network. The engineer
performed tests in the 3G network, 2G network, and conducted the 3G-to-2G handover
test.
The result indicated that the problem must lie between GGSN and FTP server. The on-
site engineers performed tests and found that no problem occurred if the server was not
installed with the firewall. Data analysis shows that the FTP data transmission at the port
was normal but was blocked after 10 minutes. Only the firewall on the system can limit
the time for the ports. If it is set in the firewall that the connection will get broken if there
is no data interaction for ten minutes at one port, the problem will occur. The firewall
professionals give the following explanation to this problem:
The FTP session will generate two session entries in the firewall: one is used for the
FTP control channel, and its default aging time is ten minutes; another is used for the
FTP data channel, and its default aging time is four minutes. If the detect ftp command
was not configured in the domain the aging time will not be updated during data
transmission in the data channel, and the control channel will be invalid after ten minutes
61(62)
and then be deleted. Then the problem occurs. If the detect ftp command is configured
in the domain, the aging time of the control channel will be updated when data is
transmitted. Thus it can be concluded that the problem has nothing with the radio access
network. The process and result of this fault location are meaningful and needs careful
consideration. The test method of changing the NE is really useful.
62

UMTS PS Service Analysis Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

UMTS PS Service Analysis Guide

Uploaded by

Copyright:

Available Formats

UMTS PS Service Analysis

2 PS Service Data Transmission Analysis

2.1 Universal Analysis Method

2.1.1 Data Collection

2.1.1.1 DT/CQT Data Collection

Note: Time synchronization should be performed before data collection.

Information that should be collected is shown in the following table:

Main Parameters That Should Be Collected Through DT/CQT

Parameter Method Function

RRC, NAS signaling at UE

HSUPA average SG, Analyze the problem and

RNC single user signaling

Parameter Method Function

2.1.1.2 Collection of Other Data

Data That Should Be Collected

2.1.2 Data Analysis Method

2.1.2.1 Common Problem Analysis Method

1. Collect configuration and alarm information of relevant equipment. If necessary,

2. PS data transmission problem mainly includes blocked data transmission,

a) To judge whether there is packet loss, check whether the number of UL

packet is lost can be located. Use the relevant NE equipment fault

b) For data transmission rate problem, if the UL and DL packet number in

c) If the packet number in the UL and DL of UEs and that at Gi is

2.1.2.2 Typical NE Locating Method

SGSN user plane

1. Check that user tracing function is normal.

3. Check whether there is wrong statistics.

The packets are lost at GGSN.

Packet loss of data communication equipment.

General DT/CQT data analysis flow is shown as follows:

Analysis flow of DT/CQT data

3.1 Basic Problem Analysis

3.1.1 Access Failure

3.1.1.1 UE directly launches the PS service

Analysis flow of UEs failure of launching the PS service directly

3.1.1.2 UE as the Modem of PC

Analysis flow of UEs failure of launching PS service

1. Port opening failure

The analysis flow of port opening failure is shown as follows:

Handling flow of port opening failure

The main causes of the port opening failure:

i. Incorrect Port Configuration in the CNT

ii. Abnormal port status

iv. Something wrong with the UE software

Try to solve the problem by restarting the computer.

v. Incomplete installation of the UE driver

2. The port is opened successfully, but the access is still a failure.

Signaling analysis flow of access failure

i. RRC connection setup failure

Problems appear during the RRC connection setup process (From UE

b) The Test Controller in the CNT is not set, or is set incorrectly.

c) The UE port is abnormal. Details can be checked in Port Opening Failure

b) Admission refusal caused by uplink/downlink overload

c) Illegal parameter setting

For the illegal parameter setting, the main scenario is described as

ii. UE does not send the Service Request message.

There is no Service Request message in the NAS message.

The possible causes may be:

a) UE does not open the PS function

b) UE does not finish the registration in PS domain.

iii. Problems in the authentication and encryption process

iv. PDP activation is refused.

a) APN setting problem at the UE side.