Sample Questions

Chicago, IL Market Breakdown Example
HSPA Session Establishment Failures

Background - T-Mobile’s session failure happens in
a solid RF environment in a core urban area
• Session set up failure happens
following a successful data cycle
in good environment
T-Mobile Data Network Access Failures

T-Mobile Data Network Access Success
Copyright © 2010 The Nielsen Company. Confidential and proprietary.

Background - Prior to the session failure, TMO
completed a full cycle but had throughput
degradation 6 7
Cycle Timeline preceding Access Failure
Time Message Xput HSPA Cell ID

7
kbps RSSI
15:25:56 Session Start -69.6

1 N/A
15:25:58 Session Set-up Success -70.98
2 15:26:05 Get 1 Start -63.83

206.4 10047
15:26:15 Get 1 Success -63.57
3 15:26:20 Post 1 Start -62.24

45.4
15:26:39 Post 1 Success -73.05
4 15:27:00 Get 2 Start -53.60

15:27:24 Get 2 Success 1648.3 -60.11
6
18008
5 15:27:29 Post 2 Start -59.88 4
15:27:43 Post 2 Success 55.2 -55.58
6 15:28:12 Get 3 Start 612.7 -56.89 10052

15:31:14 Get 3 Success -60.52 18051
3
7 15:31:20 Post 3 Start -59.52
87.9 18056
15:31:51 Post 3 Success -38.28
2
Note – throughput degrade significantly prior to access failure; 5

1
handoffs and 6 unique serving cells

Explain the Series of Events?
Cycle Timeline Access Failure

Time Message Cell ID
15:33:45
1 thru i
15:33:46
15:33:53 18036
2 thru Multiple - UL GPRS GMM - Routing Area Update Requests
15:34:24
DL GPRS GMM - Routing Area Update Accept

3 15:34:26 UL GPRS GMM - Routing Area Update Complete 1-2
RRC Connection Request - Inter RAT Cell Reselection 18036 3

4 15:34:34 DL CCCH - RRC Connection Setup-Cell_DCH 18036
UL DCCH - RRC Connection Setup Complete - HSDPA Category 10 18037
4
Call Origination
5 15:34:35 RRC Connection Setup Complete 5
6 15:34:37 DL DCCH- Signaling Connection Release

8
18037
7 15:34:38 RRC Connection Release
8 15:34:46 Session Failure New Session

Start
Cell ID - 18002

Hypothesis or Conclusion - Potential Root cause

Missing Neighbors
Poor Coverage
Pilot Pollution / Spillover
Poor Cell Reselection
Core Network Issues-power distribution issue
Non – availability of resources. Admission Control denies
Hardware Issues
Blocking (CE / Code blocking/ Power blocking/ )

Improper RACH Parameters(Preamble cycle timer value,no of preamble
attempts.)
5
External Interference
Copyright © 2010 The Nielsen Company. Confidential and proprietary. Title of Presentation
Next Steps – What should the engineer check or troubleshoot
now?
CCCH power allocation parameter.
We can check to proper channel power allocation
Reverse Link maximum power parameter.
Cell re-selection parameter
Intra-freq. handover parameter

Compress mode  2D event to start & 2F to end
Inter-RAT handover parameter
Power control parameter
Access power parameter
Upload Task Establishment Failures
Background - T-Mobile had a number of task
failures in a dense urban area between I-290 and I-
55
• The upload task failure 24322
occurred in a solid signal
environment; average RSSI = -66.1 2 1
1. Task Post 2 – Start

2. Task Post 2 – Failure
• Task Time – 181 Secs.

• Last RSSI - -66.2
T-Mobile Transaction Failures

Background 2 - Chronic Task Failures in Stickney
Unity West
Jr High 1-4
HSPA Cell
Time Message XPUT
RSSI ID
17:21:55 Session Start -58.1
1 11012
17:21:57 Session Successful -62.4
17:22:04 GET 1 Start -62.8
• Prior to failing Post 2,
2 1060.9 11012
17:22:07
17:22:11
T-Mobile
GET 1 Successful
POST 1 Start
-63.1
-59.8
successfully completed 3 Tasks

3 17:22:45 POST 1 Successful
-59.2 26.21 11012
4 17:23:05 GET 2 Start -57.8 800.6 11012

17:23:50 GET 2 Successful -60.1
• All tasks were completed while the vehicle was stationary

in good RF conditions

Explain the Scenario/events?
19 5
Time Message RSSI Cell ID

5 17:23:54 POST 2 Start -57.87 11012
6 17:23:55 Multiple (5x) - DL DCCH - Radio bearer Reconfiguration
17:24:58 POST 2 Failure
Avg. -61.4 11012
17:23:55
7 17:24:59 Multiple (5x) - UL DCCH - Radio bearer Reconfiguration Complete • During POST 2 task due
8 17:25:33 DL DCCH - Radio bearer Reconfiguration -58.07 11012 to multiple Reconfiguration
9 17:25:34 UL DCCH - Radio bearer Reconfiguration Complete -55.86 11017
10 17:25:55 DL DCCH - Physical Channel Reconfiguration -73.9 11017
messages the data flow
11 17:25:56 UL DCCH - Physical Channel Reconfiguration Complete -74.39 11017 was broken multiple times
12
17:26:00
Multiple (3x) - DL DCCH - Radio bearer Reconfiguration and eventually network
17:26:08
Avg. -73.8 11017 disconnected the device by
17:26:01
13 17:26:09 Multiple (3x) - UL DCCH - Radio bearer Reconfiguration Complete sending Connection
14 17:26:09 Multiple (4x) - DL DCCH - Physical Channel Reconfiguration release message. After 180
17:26:41
17:26:10
Avg. -66.0 11017 seconds timer expired and
15 17:26:42 Multiple (4x) - UL DCCH - Physical Channel Reconfiguration Complete
Upload failure was
16 17:26:46 UL - Location updating request -64.08 11017 observed.
17 17:26:47 DL - Location updating accept -65.28 11017
18 17:26:48 DL DCCH - Signaling Connection Release -65.19 11017
19 17:26:57 POST 2 - Upload Failure -66.39 11017
10

Background
32 23 20-21
Time Message RSSI xPut Cell ID

20 17:27:31 GET 3 Start -65.98 11018
21 17:28:24 GET 3 Successful -65.68 1411.98 11018
• Once device started next cycle on
22 17:28:28 POST 3 Start -66.17 11018
23 17:31:06 POST 3 Successful -58.16 53.35 25083
25083 Cell sites it was able to upload
24 17:31:54 Session Start -68.3 25083 and down load data with acceptable
25 17:31:56 Session Successful -75.2 25083 throughput values.
26 17:32:02 GET 1 Start -72.05 25083
27 17:32:05 GET 1 Successful -69.54 3000.25 25083
28 17:32:08 POST 1 Start -76.31 25083
29 17:32:12 POST 1 Successful -71.01 382.77 25083
30 17:32:33 GET 2 Start -78.5 25083
31 17:32:44 GET 2 Successful -79.85 4707.7 25082
32 17:32:47 POST 2 Start -81.35 25082
11

There could be two cases in this scenario:

1. Multiple PS cell change happening, which may be due to
border area of serving cell and frequent cell change is taking
place or the parameter setting for RSCP or EC/No for cell change
might be too low.
2. This could be due to frequent LAC update request and the

location would be in over-lapping of multiple LAC’s.
12
now?
1. Need to check dominant Server.

2. Need to verify the interference i.e. Ec/No value at the specified
location.
3. LAC boundary need to be checked.
13
Downlink Throughput Degradation
T-Mobile HSPA Low Download Speeds can be fixed
by ???
• Summary of Findings during Low
Application Download Speeds
– Poor RSCP,Ec/Io
– Low CQI value
– High no.of users
– In case of Non implementation of
higher modulation schemes(64-QAM)
• Suggestions
– Make good dominance of coverage
– Resetting the numhspdschcodes
– Increase Iub bandwidth
– Increase max HS(bandwidth in terms
of E1/T1) rate
– CQI adjustment ON
– Code threshold PDU656 ( eg. 373)-
W12 feature,redues the size of header
which enables higher throughput?
15

Layer 1/2/3 Analysis during Low Download Speeds
What are the key take

LARGE DOWNLOAD
away?
HIGH
SPEED LOW SPEED
Number of Intra Handoff State None None
Active Set List
Number of Changes 0 25
Most Used Active Set PN 283(100%) 264(17%)
HSUPA E-DPCH Happy Bit Count
Median 206 15
Minimum 2 1
Maximum 252 443
Standard Deviation 108 57
HSUPA E-DPCH_Summary Total TB Size
Median 358636 5431
Minimum 332 41
Maximum 543551 68328
HSUPA E-DPCH_Summary Total TB Size ACK
Median 100% 100%
Minimum 98% 38%
Maximum 100% 100%
Standard Deviation 1% 9%
16

Layer 1/2/3 Analysis during Low Download Speed
LARGE DOWNLOAD
HIGH
SPEED LOW SPEED
HSUPA E-DPCH_Summary HARQ Throughput
[kbps]
Median 359 6
Minimum 0 0
Maximum 593 1082
Qualcomm HSUPA E-DPCH_Summary MAC-e Throughput
[kbps]
Median 359 6
Minimum 0 0
Maximum 581 68
DPCH_Summary HICH_Comb. ACK Ratio [%]
Median 41 4
Minimum 0 0
Maximum 64 95
17

18
now?
19
Scranton, PA Market Breakdown Example
EVDO to 1xRTT
Sprint EVDO on 1XRTT
Concern: Sprint EVDO device latching onto 1XRTT even though good
EVDO REV A coverage is available.
Region Selection:
o To analyze the issue we picked Scranton, PA where high % of task on 1XRTT
are observed.
o We narrowed down the analysis to one portion of market where EVDO coverage
is excellent.
o File 20120508_1634_270E_10938 was picked for analysis that was driven in
good coverage. Figure 1 shows the location of the file and Sprint coverage map
showing good EVDO coverage.
21

Figure 1 : Region Selection

22

Deep Dive DRM Analysis:

• Device started the tasks on Sprint’s network (System ID 4162).
• After 6 cycles on Sprint’s network, device initiated Session establishment on EVDO
network and it was successful.
• Device performed GET 1 on EVDO but with very low throughput of <50 kbps, during
this task in Overhead message- Quick Config message we are observing on an
average 30-40 Forward Traffic Channel active. Pointing to network congestion.
Figure 2 shows Quick Config message.
• Same is observed while device was performing POST 1 with high number of Forward
Traffic Channel active.
• After POST 1 and before GET 2 we have 22 second of idle time. During this idle time
multiple Route Update – Traffic Channel Assignment / Traffic Channel Complete
messages are observed pointing to fact that device is trying to latch on the network with
enough resources so that GET 2 task can be complete. Figure 3 shows Route Update
messages.
• During the idle time after route update messages all of sudden Network is sending
Connection Close message. Where device disconnects from the network and instead
of latching back to EVDO network Device sends out Registration message on Verizon
(SYS ID 96) 1X RTT Network. Figure 4 shows 1XRTT Registration message and
Device performing GET 2 task on SYS ID 96.
23

Figure 2: Quick Config message with 36 active forward traffic

channel
24

Figure 3: Routing Update message
25

Figure 4: Device latching on to Verizon’s 1XRTT network.
26

• Situations ,where AT is receiving multiple Traffic channel

assignment messages but not able to complete the
assignments process depicts the UE trying to access high
loaded network which doesn’t have enough
resource(T1,Channel elements, power etc) on serving as
well as on its 1x network. Then AT try to latch to systems
which have enough resources(after certain idle time)
• Blocking(CFR) will be very high in such cases and it will

be easy to see capacity related counters in the systems.
27
now?
• Engineer can look for different capacity related

parameters(Max no.of users supported, slot utilization
etc.) and can recommend either in system related
parameter or also can move ahead with capacity addition
• Drive test can also provide the scenarios in which it is

triggering.
28
Market Breakdown Example
LTE Data Call Failures
Detailed Analysis - Nashville, TN
• For Nashville, TN recent drive area of concern is Session

failures for LTE Data card in recent March 2012 drive.
• Session Establishment failures for LTE (Flow of Messages):
– Failure scenario is same as we observed in Charlotte, NC, where device is
sending the required messages and we are observing handover, multiple
Reconfiguration and eventually after not getting rrc resources,
rrcConnection Release message on DL DCCH.
– Device tries for full 60 seconds and Setup Failure with Cause as Time out
is observed.
– Next 2 slides shows flow of messages.
30

31
Figure 4
32
Figure 5
• In this case device is sending the required messages and we
are observing handover, multiple Reconfiguration and
eventually after not getting RRC resources, reconnection
Release message on DL DCCH is observed
• This may due to Periodic TA update,or due to RSRP on LTE

carrier frequencies is not good resulting in high IRAT
handovers.
• In the Layer 3 analyis,it is shown that after RRC reconfiguration

complete, there is PDN connectivity request, which is followed
by Activate default EPS bearer and which should be followed
by ICMP router advertisement but there is not any such thing
in above layer 3 report.
33
now?
• Engineer need to look for eNB to PDN/SGW connectivity issue.

• Also need to look for other layer -3 signaling flow after Default
bearer assignment.
34
LTE KPIs
What RF, System and IP Backhaul KPI/metrics should one
consider to evaluate a LTE session Failure
Serving
Serving cell
cell poor
poor RSRP(dbm)
RSRP(dbm) Session
Session establishment
establishment timer
timer Temporary
Temporary outage
outage in
in the
the backhaul
backhaul
(t310,t311,n310,n311) are not proper causes problem in flow of radio
RF
signaling.
System Level
IP Backhaul
UE eNB
eNB does
does not
not support
support RRC
RRC
UE going
going out
out of
of sync:-The
sync:-The UEUE isis
expected reconfiguration
reconfiguration after
after RRC
RRC IP
IP assigned
assigned by
by the
the systems
systems is
is not
not valid
valid
expected to to monitor
monitor the
the RS
RS inin the
the
downlink. Based on the signal strength configuration fails
of
of the
the Reference
Reference Signals
Signals (i.e.,
(i.e., the
the During
During CS CS fallback,the
fallback,the UE
UE send
send s sa a
RSRP),
RSRP), thethe UE
UE will
will determine
determine ifif itit can
can extended
extended service
service request
request ,and
,and if
if itit not
not
decode
decode thethe PDCCH
PDCCH basedbased onon aa certain
certain supported
supported by by thr
thr N/W,then
N/W,then session
session
set of parameters that are provided in failure occurs
the specs. Each UE will have a UE tried to do Tracking area update
different
different RSRP
RSRP threshold
threshold in
in which
which it it which
which isis rejected
rejected byby N/W,then
N/W,then session
session
will
will assume
assume itit cannot
cannot read
read the
the PDCCH.
PDCCH. failure
failure occurs
occurs
If
If the
the Reference
Reference signals
signals have
have enough
enough
strength such that the UE can decode Coverage was good but UE is not able
consistently the PDCCH, then the link to start RRC establishment procedure
is due
due to
to temporary
temporary issue.
issue.
is In-Synch.
In-Synch.
Authentication problem.
Ping pong in dominant cells
Random Access done on CBRA basis

but UE not allowed for UL grant
36
consider to evaluate a LTE low Downlink Throughput
Poor SINR- Electrical and Delay in Signaling

RF
Mechanical tilts are
System Level
IP Backhaul
Overshooting of Backhaul capacity
neighboring cells not proper
Backhaul
High No.of IRAT Downlink configuration
Handovers Scheduling problem
algorithms
Lack of dominant Assignment of MME
cell Link adaptation or and S-GW during
not proper handovers
Coverage hole Modulation and
Missing neighboring coding schemes X2 and s1 interface
relationship problem
37
consider to evaluate a LTE low Uplink Throughput
Uplink interference-RSSI VSWR Backhaul capacity:-Often times,

the backhaul links are shared
RF
Multiple IRAT HO
System Level
IP Backhaul
among multiple RATs. Make sure
Low demand-can calculate through your backhaul is properly
max no.of attempted RRC or active Scheduler types(proportinal dimensioned.
connections fair,Round Robin,Max C/I
Maximum number of users etc.OEMs allow you to switch the
scheduled per TTI in the cell(s) of scheduler in your network but
interest recommend one in particular.
. The wrong scheduler may be the
The BLER should be smaller or reason for bad throughput
equal than 10%. If the value is
larger, then, there is an indication
of bad RF environmen
Power head room-A low value of

power headroom means that UEs
do not have available power to
transmit in the uplink and hence,
the throughput is low.
38

Sample Questions

Uploaded by

Copyright:

Available Formats

You might also like

Sample Questions

Uploaded by

Document Information

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

Sample Questions

Uploaded by

Copyright:

Available Formats

Chicago, IL Market Breakdown Example

HSPA Session Establishment Failures

T-Mobile Data Network Access Failures

Copyright © 2010 The Nielsen Company. Confidential and proprietary.

Time Message Xput HSPA Cell ID

15:25:56 Session Start -69.6

2 15:26:05 Get 1 Start -63.83

3 15:26:20 Post 1 Start -62.24

4 15:27:00 Get 2 Start -53.60

6 15:28:12 Get 3 Start 612.7 -56.89 10052

Note – throughput degrade significantly prior to access failure; 5

Copyright © 2010 The Nielsen Company. Confidential and proprietary.

Cycle Timeline Access Failure

DL GPRS GMM - Routing Area Update Accept

RRC Connection Request - Inter RAT Cell Reselection 18036 3

6 15:34:37 DL DCCH- Signaling Connection Release

8 15:34:46 Session Failure New Session

Copyright © 2010 The Nielsen Company. Confidential and proprietary.

Pilot Pollution / Spillover

Poor Cell Reselection

Core Network Issues-power distribution issue

Non – availability of resources. Admission Control denies

Blocking (CE / Code blocking/ Power blocking/ )

CCCH power allocation parameter.

We can check to proper channel power allocation

Reverse Link maximum power parameter.

Cell re-selection parameter

Intra-freq. handover parameter

Power control parameter

Access power parameter

1. Task Post 2 – Start

• Task Time – 181 Secs.

T-Mobile Transaction Failures

Copyright © 2010 The Nielsen Company. Confidential and proprietary.

successfully completed 3 Tasks

4 17:23:05 GET 2 Start -57.8 800.6 11012

• All tasks were completed while the vehicle was stationary

Copyright © 2010 The Nielsen Company. Confidential and proprietary.

Time Message RSSI Cell ID

Copyright © 2010 The Nielsen Company. Confidential and proprietary.

Time Message RSSI xPut Cell ID

Copyright © 2010 The Nielsen Company. Confidential and proprietary.

There could be two cases in this scenario:

2. This could be due to frequent LAC update request and the

1. Need to check dominant Server.

Copyright © 2010 The Nielsen Company. Confidential and proprietary.

What are the key take

Copyright © 2010 The Nielsen Company. Confidential and proprietary.

Copyright © 2010 The Nielsen Company. Confidential and proprietary.

Copyright © 2010 The Nielsen Company. Confidential and proprietary.

Figure 1 : Region Selection

Copyright © 2010 The Nielsen Company. Confidential and proprietary.

Deep Dive DRM Analysis:

Copyright © 2010 The Nielsen Company. Confidential and proprietary.

Figure 2: Quick Config message with 36 active forward traffic

Copyright © 2010 The Nielsen Company. Confidential and proprietary.

Figure 3: Routing Update message

Copyright © 2010 The Nielsen Company. Confidential and proprietary.

Figure 4: Device latching on to Verizon’s 1XRTT network.