Está en la página 1de 7

Performance Responsibility: Pre-checks completed: Cell is alarm-free verify through ROP All sectors are taking voice traffic

c Plot 3G CDMA traffic through SPO All sectors are taking data traffic Plot 3G EVDO traffic through SPO EVDO case Verify that router settings and IP addresses are correct EVDO case Verify that MCESM card (TX board) settings are correct. Check the RNC group and - router connected to correct RNC group. Blocking case/ High Access Failure count - Confirm that designed number of T1s are deployed and operational, H. RSSI, VSWR, RNC group connection, loose or bad cable measurements are under limits. A. B. C. D. E. F. G.

Assumption: Performance already have filtered the list of Top Offender sectors for break-fix issues and assigned remaining sites to RF for KPI improvement. RF assumes that following statements are true. (Please verify before starting optimization, if false then assign the cell back to performance/operations) Cell is alarm-free verify through ROP All sectors are taking voice traffic Plot 3G CDMA traffic through SPO All sectors are taking data traffic Plot 3G EVDO traffic through SPO

Preliminary Checks for RF:

Design Changes (Sprint NV vs. Legacy): From playbook analyze the antenna, azimuth, tilt changes and anticipated impact on coverage due to change in EIRP. In case of Azimuth change and site is rooftop, check the Final CD (as built) for any obstruction in antenna beam due to parapet or wall. Rule of thumb: Antenna needs at least 1 feet height to clear every 3ft of parapet/roof. Is the site on RNC or MSC border check inter MSC soft and Hard Handoff stats.

FST Audit (Form 36.2, Final CD 8.0, Sweep Results 40.0 and Photos 73.0): Complete FST audit for form 36.2, 8.0, 40.0 & 73.0. Assure effective tilts for NV design are at least equal or more than legacy network with increase in EIRP.

NCV: 1. CROSS FEEDER VERIFICATION: Plot individual coverage per sector and verify that site does not have cross feeders by plotting PN coverage per sector through NCV tool. 2. Compare coverage post-cutover vs. pre-cutover through NCV. If post-cutover coverage is larger than pre-cutover the recommend EDT appropriately. Try to avoid power reduction to shrink the coverage.

Display Average All Ec/Io average Display event location (of Drop Rate or Access Failure Percentage) Further, count should be displayed for particular sector to analyze the distance of majority drops. Event distribution or location (drop or access Fail)

Transcend: Translation analysis and resolve discrepancy (alignment) Verify Antenna Down tilt through RET RRH

Audit all critical RF Parameters, RITC Report, No Harm results, site performance etc. as needed Important Forms to be Audited o FCI Neighbor List o CEQFACE o CDHFL Hand off o CDHNL Inter-band Carrier Neighbor List o Cell 2 o Check Op alarms Pay attention to Critical RF Parameters: o RRH Attenuation (transmit power of each sector) o Neighbor List Entries and Priorities (FCI and CDHNL forms) o Soft Handoff Thresholds (t_add, t_drop, t_comp, t_tdrop, maxlegs) o Active set and neighbor set search window sizes(srchwina and srchwinn) o Pilot, Page, Sync, Quick Paging, Traffic Channel Digital Gain Settings o Access probe nom and init power levels(init_pwr, nom_pwr) o Sector Size and Access Preamble Size(cell_size, pam_sz)

SPO: (more details with snapshots are being added)

Generate following KPIs for problem sector Established Connection Rate Dropped Connection Rate Traffic Primary Erlangs for CDMA voice(or MBs for EVDO).

A. Parameter Audit Compare parameter through macro (as used in Boston market contact Ryan Ramos) against gold Standard (or pre-cutover standards). Mismatch parameter should be provided to Raj Goyal to make compliant with Gold Standard B. ROPs C. Add missing neighbors D. Trend Analysis:

a. SPO Pre/Post cutover sector trend including SM, pegs, and other counters supporting the analysis such as (equipment blocs, channel usage etc) b. Primary Sector Pre/Post Ec/Io from NCV Drop call and/or access fail location plots c. Analysis of NL/HO percentage/Missing NBR that needs to be added etc d. ROP messages/Alarms if there are any e. PCMD Drops/Access Fail location plot from SPO & PCMD based failed event analysis (reason, cause) f. Identify and trend component/pegs driving the increase Blocking Analysis Method: SM metrics for Channel Usage:

EVDO Optimisation Generate following KPIs for problem sector Established Connection Rate Dropped Connection Rate Forward and Reverse Data Rates (UL/DL data rates) Traffic Primary MBs.

Accessibility Analysis (If resource or backhaul capacity could be the cause) Forward Supplemental Channel usage (3D) Primary Traffic Code Channel Usage (2D, 3D, TD, TV) Reverse Supplemental Channel usage (3D) Secondary Traffic Code Channel Usage (2D, 3D, TD, TV) Total Traffic Code Channel Usage (2D, 3D, TD, TV) SM metrics for Overload: Orig & Term Block Rate due to FWD Power Overload Reverse Power Control Overload_Duration in sec. Access Channel Overload Control (TV)

Access Channel Overload Control Duration in sec (TV) Forward Power Control Overload_Duration in sec. (TV) Forward Power Control Overload_Number of Times (TV) SM metrics for Occupancy: Peak CDMA Access Channel Occupancy Processor Occupancy Rate Average CDMA Access Channel Occupancy Average CDMA Paging Channel Occupancy

I am thinking to have a step process that RF will look into and analyze before bringing sites to SME call with you. I am thinking to have the following items looked over at our end, please let me know if you think we need to add or modify the list. SPO SM trend such as blocks, equip blocks etc. Call Drops: count/rate/pegs Pre and latest weekly post cutover dates

Primary Sector Ec/Io, Drop call, access fail plots

Pilot Pollution:

NL/HO percentage/Missing NBR that needs to be added etc

ROP messages: 1. PCMD Drops/Access Fail location plot from SPO 2. PCMD based analysis from SPO (reason, cause) 3. Look at which component is driving the increase. 4. Sometime if the information is not captured in the message, look at the ROP.

(side notes) send all EDT forms updated with RET Sr. No Khurram Munawar - Top Offender Call Check the RNC group and - router connected to correct RNC group. RSSi, VSW, group connection, loose or bad cable - should pass. Look ROP's for possible alarms T1 or IP backhaul - how the capacity is limited Checklist - sent previously - Deepak & Chun presentation, additional email form Khurram

Power. Tilt, Parameter, Boston - tilt implemented on Friday and checking the results. Meeting Minutes 7/31/2012 1. EVDO top offender sectors in Boston and BAWA were reviewed. 2. Identified down tilt change recommendation on one Boston sector which will be implemented this week. 3. Statistical data, ROP log etc will be shared with Asif, Amit and Xinyu on the other sectors for further analysis and resolution recommendation. 4. Khurram will send SPO equipment blocking description to Xinyu and Asif. 5. Asif will see into putting a process and identifying POC to escalate HW alarm for explanation and/or resolution 6. Top offender sectors preliminary RF analysis needs to be send out to SMEs by Thursday for them to review before Mondays call. Working group to troubleshoot and improve top offending sectors KPI in phase 1 markets. Please make sure to send request to Performance (Mayank Patel) to verify Q5 PIR setting on the top offender sites through performance group. Please see the automated process to calculate RTT directly through the Wire shark generated .PCAP file with any number of RTT samples. This method will allow us to collect larger RTT sample size and automatically calculate the RTT response time and will also be less prone to mistakes.