Colorado

Drive Analysis Check Points

Voice Analysis
1) Verify whether all PN’s are transmitting in the drive.
2) Pilot pollution analysis
3) Identify over shooters
4) Sector swap issues( currently there shouldn’t be any cases).
5) Identify coverage holes
6) Call drop analysis
 Below check points for Drop Calls.
• Missing neighbors.
• Due to poor Ec/Io (Pollution)
• Wrong BCD definition or wrong Search set values.
• Poor coverage.
• Hardware issues/alarms on a particular site at the time of drive test.
• In recent drive, we are seeing missing ecsfb neighbors causing drop calls( esp. near D1 sites). Neighbor relations were added right away.
• Near GMR sites we are seeing drop call issues( GMR sites doesn’t have RET capability and they are attenuated by 1.8 or 3db( shrinking coverage)).
• In few scenarios(not in recent drive), UE camped on Femto PN 504, 507 and tried to handoff to macro and it pegged drop call. UE can’t perform handoff
from Femto to Macro.
• FER Verification
• Due to over shooter( either downtilt or add the neighbor relation).

©2015 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.
2
Voice Analysis
7) Call failure analysis
• Poor coverage. Esp. in our latest Denver root metrics drive we had 2 call blocks and both were pegged inside Walmart super
center. Previous we had similar issue on other market, call failure pegged inside home depot. Seems like foot print is not strong
enough at indoor locations( esp. near DN63XC010 & DN63XC095).
• Missing neighbors
• Hardware issues/alarms on a particular site at the time of drive test.
• RSSI issues.
• In recent drive, we are seeing missing ecsfb neighbors causing Block calls.
• GMR sites doesn’t have RET capability and they are attenuated by 1.8 or 3db( shrinking coverage).
• Due to coverage holes( challenging terrain areas).
• Overall in Denver metro we had issues at indoor location only due to poor coverage( interms of call failures).
8) Good coverage vs Poor Ec/Io analysis
9) Carrier cloud Analysis
10) BCD audit
11) Need to escalate break fix issues
12) Sleeping cell audit
13) NL prioritization and clean up.

©2015 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.
3
PN Propagation
• Verification of PN foot print: Verify whether all PN’s are propagating in the drive. If any PN sector is not
transmitting verify alarms/hardware issues at the time of drive test.
• (Example: DN63XC075 Alpha PN 111, DN63XC083 Alpha PN 75 are not transmitting in our LCC 1 st
iteration drive. No alarms/break fix issues observed but both these sites are GMR and site height is
34,48ft).
• Refer to next slide.

©2015 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.
4
Poor Ec Areas(both in PSTN & MO)
PSTN MO
Ec Ec GMR

Off-Air
DN63XC075 Alpha PN 111, DN63XC083
Alpha PN 75 are not transmitting

©2015 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.
5
Pilot pollution analysis
• Pilot pollution analysis: If 3 or more PN’s are propagating in one area with good Ec and Poor Ec/Io, we
need to remove the overshooter and unwanted PN’s in this area to reduce pollution( with the help of
RET changes).

©2015 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.
6
Polygon_ID Condition Opto Bucket RCA Analysis

PN 54(DN03XC127-0), PN387 (DN03XC127-2) PN 270 Poor Ec/Io observed in area due to pilot pollution The overshooting sectors are on relatively higher
23 Bad Pilot Pollution (DN03xc134-1), PN 357 (DN25XC073-2) & PN 180 elevation and closest serving site – DN03XC131 & DN73XC042 have low height. The driven roads are
(DN73XC090-1) creating Pillot pollution flyovers at higher elevation making it difficult for neighbor site to serve. RET optimization needed to
address pilot pollution in area.

Root Drop

• Area is in Broomfield
• Poor Ec/Io is observed in area due to pilot pollution caused by
overshooting PNs.
• Nearest serving sites – DN03XC131 & DN73XC042 have low
height of 48ft and 46ft respectively.
• The overshooting sectors observed are at slightly higher
elevation as compared to target area.
• Current RET on closest serving sector DN03XC131-0 is 5/8 and on
DN73XC042-2 is 0/0. Recommend to uptilt DN03XC131-0 to 4/6
to increase dominance in area.
• Downtilt on overshooting sectors – DN03XC127-0 (4/3 to 4/5),
DN25XC073-2 (4/5 to 5/6), DN73XC090-1 (4/6 to 5/7)

©2015 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.