Slide title In CAPITALS 50 pt Slide subtitle 32 pt POST LAUNCH TUNING

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt Commercial in confidence Post-Launch Tuning Cluster Scope Purpose: Perform Post launch Cluster tuning after the commercial Launch and asses the network performance Pre-Requisites: All Clusters needs to be at 90% minimum site availability with no service affecting alarms 4 Drives per Cluster for tuning. Cingular must arrange for Remote Electrical Tilt (RET) teams to be provided to complete changes to sites in a cluster that require downtilt changes within 3 days after analysis being completed Estimate 70% of a cluster’s sectors will need RET adjustments after the first tuning drive  Average 42 sectors (14/day) in a 60 sector/20 site cluster  Estimate may be revised based on IT feedback

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt Commercial in confidence Post-Launch Cluster Activities/ Flowchart Scope Timelines **Tuning Drive **Drive Analysis Implement changes (3 days) **Tuning Drive **Drive Analysis Implement changes (2 days) AMR 12.2k and PS R99 unloaded Drive #1 *Site Testing AMR 12.2k and PS R99 loaded Drive #2 (w/ 5 users) ***GNG drive – Day 30 AMR 12.2k (MOC,MTC) + PS R99 + HS loaded Drive #3 (w/ 15 users) - Site Testing is a part of the integration team activities ** - Tuning drives and analysis duration is proportional to the number of sites per cluster. Every 10 sites: 1 day (8 hrs) for Drive, 1.5 days (12 hrs) for Analysis Example: Cluster with 20 sites: 2 days (16 hrs) for Drive, 3 days (24 hrs) for Analysis In any case (e.g. Clusters with >20 sites) the limit for drive is 2 days and the limit for analysis is 3 days *** - Drive#3 may start parallel to drive#1. This is a GNG drive, result will be delivered on 30 th day - Drive#4 will start after drive#3. This is a GNG drive, result will be delivered on 60 th day - No changes will be implemented after drive #4. Analyses and Recommendation will be provided after Drive#4 ***GNG drive – Day 60 AMR 12.2k (MOC,MTC) + PS R99 + HS loaded Drive #4 (w/ 15 users) Close out Summary Report and Customer Presentation (2 days) Assessment Drives (6 hrs) Analysis (1 day) Implement changes* (1 day) Report

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt Commercial in confidence Tuning drives are all performed with TIW as logging tool. Tuning the whole cluster area requires a very dense drive testing route (average is 2 days) Load for Drive #2 Following load will be used for drive # 3 and #4 5 speech OCNS Users per cell *20.3 dBm power per User *1.5 dB Standard Deviation Load for Drive #3 and #4 Following load will be used for drive # 3 and #4 15 speech OCNS Users per cell **22.2 dBm power per User **2.4dB Standard Deviation * Value based on results from Atlanta and Dallas calibration drives **This value has been calibrated in many markets and has been used during Go/No-Go drives for all markets The values above can be used without real OCNS calibration, one verification drive in one cluster can be carried; ± 1 dB is acceptable for Power per user ± 0.5 dB is acceptable for Standard Deviation Cluster Post-Launch Tuning Information

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt Commercial in confidence Cluster Post-Launch Tuning Unloaded Drive #1 Loaded #2 Both drives have the following setup: MS1: Scanner MS2: Speech Long Locked to UMTS MS3: Speech Short (MO) Locked to UMTS MS4: PS R’99 Short Locked to UMTS The density of the drive should target a 500 meters resolution grid. The drive test duration is proportional to the number of sites per cluster. Every 10 sites should correspond to 1 day (8 hrs) drive. Example; 1 cluster with 15 sites -> drive test duration is 1.5 days (12 hrs), analysis time for 2.25 days (18 hours) Maximum limit for drive duration is 2 days and for analysis duration is 3 days

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt Commercial in confidence Cluster Post-Launch Tuning Loaded drives #3 and #4 Both drives have the following setup: MS1: Scanner MS2: Speech (MOC) – UE in dual (automatic) mode MS3: Speech (MOT) – UE in dual (automatic) mode MS4: PS R’99 long (3 MB FTP) – UE in dual (automatic) mode MS5: HSDPA (5 MB FTP) – UE in dual (automatic) mode The drive route will be approximately 6 hours per cluster

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt Commercial in confidence Cluster Post-Launch Tuning Unloaded Drive #1 Loaded #2, #3 and #4 Scanner data can be analyzed with the purpose of single cell coverage verification and missing neighbor analysis. Scanner data can also be used for new tilt recommendations due to the newly integrated sites. The engineer MUST review all the tilt recommendations before they are implemented. Any proposed recommendations will be tracked through RFCR tool and implemented through Kodzilla

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt Commercial in confidence Cluster Post-Launch Tuning Unloaded Drive #1 Loaded #2, #3 and #4 After each drive has been completed the KPIs are compiled and reported For all the KPIs that are not fulfilling the target, explanation of the reasons should be provided. Also all the dropped calls and access failures should be classified The KPIs measured in the last tuning drive will be used to compile the cluster close out report. Report: - Close out Summary will be provided for tuning drives - Analysis for assessment drives will be provided and day 30 th and 60 th.

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt Commercial in confidence Cluster Key Performance Indicator (1/3) EXAMPLE REPORT

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt Commercial in confidence Cluster Key Performance Indicator (2/3) EXAMPLE REPORT

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt Commercial in confidence Cluster Key Performance Indicator (3/3) EXAMPLE REPORT

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt Commercial in confidence Possible Modification in Network  Uplink and Downlink logifles will be analyzed and based on that recommendation will be issued. Following are some of the possible changes; –Antenna Downtilt –Antenna Uptilt –Antenna Azimuth Change –Antenna Height Changes –Power Modification –Parameter Changes –Neighbor Optimization –IRAT Neighbors ACP Analyses

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt Commercial in confidence Appendix The attached presentation is a template for the Cluster Close Out report which has to be compiled for each and every cluster at the end of the Post-Launch phase. Once the Close out report has been signed by Cingular the Post launch tuning is over.

Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level pt Commercial in confidence