1. Slide title In CAPITALS 50 pt Slide subtitle 32 pt Cingular UMTS Phase II Markets Pre-Launch RF Activities

2. 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 2-5 20 pt Ericsson Confidential2006-05-162 Cluster Pre-Launch Tuning and Go/No-Go Drives Scope perform Initial Tuning to prepare clusters for commercial launch and at the same time monitor cluster performances (GoNoGo drive). Initial Tuning is an Ericsson internal activity with the only purpose of improving network performances while market GoNoGo is the official activity for network performance assessment and for reporting network performance indicators to customer. Venue Testing is another network performance assessment activity which is performed during Pre-Launch phase

3. 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 2-5 20 pt Ericsson Confidential2006-05-163 Cluster Pre-Launch Tuning and Go/No-Go Drives Activities Flowchart Scanner + (Speech Long) #1 Preparation Phase Launch Long and Short PS R99 + HSDPA # 3 Go/No-Go (On Request) Speech Long and Short M to M # 2 Go/No-Go Drive #4 2 days for the analyses combined 3 day for the analyses 1 day for the analyses 3 days for tilt implementation 1 day dr. Go/No-Go Drive (Optional) 1 day for the analyses 1 day dr. Tuning Drive Venue Testing

4. 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 2-5 20 pt Ericsson Confidential2006-05-164 Cluster Pre-Launch Tuning and Go/No-Go Drives Activities Flowchart Purpose: Perform Go/No-Go drive and prepare complete and incomplete clusters (missing sites) for the Market Launch Duration: 12 days/cluster including GNG Drive # 1  Also includes 3 days tilt implementation time 15 days/cluster including GNG OnRequest and Optional Drive  Also included 3 days tilt implementation time Cluster Drive Time: 6hrs. (Tuning/GNG route). Except Tuning Drive#1 which is for entire One day Drive Type: All Drives are in FORCE Mode except GNG drives Prerequisites: 80 % sites on Air at least 3 tuning and 1 GNG drives per Cluster  Site testing will be performed if there are no cluster available for GNG and Tuning drives  Cluster will be tuned only for the GNG route Cingular must arrange for Remote Electrical Tilt (RET) teams to be provided to complete changes to sites in a cluster that require down-tilt changes within 3 days of drive analysis being completed

5. 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 2-5 20 pt Ericsson Confidential2006-05-165 Cluster Pre-Launch Tuning and Go/No-Go Drives Activities Breakdown

6. 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 2-5 20 pt Ericsson Confidential2006-05-166 Cluster Pre-Launch Tuning and Go/No-Go Drives Venue Testing Scope: assess network performance in spot areas that have been identified by Cingular. For more information on Venue Testing refer to: \\Cingular_UMTS1\Cingular UMTS\Performance Team\Market Drives\Venue Testing Venue Testing Scanner + (Speech Long) #1 Preparation Phase Launch Long & Short PS R99 + HSDPA # 3 Go/No-Go (On Request) Speech Long and Short M to M # 2 Go/No-Go Drive #4 2 days for the analyses combined 3 day for the analyses 1 day for the analyses 3 days for tilt implementation 1 day dr. Go/No-Go Drive (Optional) 1 day for the analyses 1 day dr.

7. 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 2-5 20 pt Ericsson Confidential2006-05-167 Cluster Pre-Launch Tuning and Go/No-Go Drives Preparation Phase Scope: make sure the cluster is ready for its performances to be evaluated and it is as clear as possible from any problems that can affect call accessibility/retainability (e.g. sites not yet on air, swapped feeders, wrong antenna settings, missing neighbors, alarms…) Scanner + (Speech Long) #1 Preparation Phase Launch Long and Short PS R99 + HSDPA # 3 Go/No-Go (On Request) Speech Long and Short M to M # 2 Go/No-Go Drive #4 2 days for the analyses combined 3 day for the analyses 1 day for the analyses 3 days for tilt implementation 1 day dr. Go/No-Go Drive (Optional) 1 day for the analyses 1 day dr.

8. 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 2-5 20 pt Ericsson Confidential2006-05-168 Cluster Pre-Launch Tuning and Go/No-Go Drives Preparation Phase The following is a list of activities that are part of the Preparation Phase: Site Verification Alarm Check TCM Parameter & Configuration Consistency Check UTRAN Configuration Consistency Check RF Parameter Consistency Check Tilt Audit Cell Availability Iub link Check (T1 Errored Seconds) Iu link Check (AAL Outgoing Connection History) Scrambling Code Collisions Check Neighbour Cell Check Handset Software Version Check RSSI check Traces Setup

9. 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 2-5 20 pt Ericsson Confidential2006-05-169 Cluster Pre-Launch Tuning and Go/No-Go Drives Preparation Phase Site Verification, which includes: swapped feeders wrong antenna directions/tilt setting low coverage (due to propagation obstructions or loose/faulty connectors/antennas). Responsible: - RF engineer responsible of the cluster Tool: - test call or scanner data analysis through ACP Action: - contact Integration Team Time Required: - in case site verification is performed through test call it can take 2/3 hrs per site. - In case site verification is performed through scanner data analysis it takes from 2 to 3 hrs per cluster For more information on site verification refer to Links_for_phase2_markets.doc Note: theoretically each site in the cluster and everyone of its sectors should be checked against all these potential problems. Due to time and budget constraints this activity will be performed ONLY IF THERE ARE NO CLUSTER AVAILABALE FOR PRE-LAUNCH TUNING ACTIVITIES. Site verification will then be in many cases deferred to the analysis of the scanner measurements collected in the first cluster drive (drive #1).

10. 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 2-5 20 pt Ericsson Confidential2006-05-1610 Cluster Pre-Launch Tuning and Go/No-Go Drives Preparation Phase Alarm Check: all the sectors in the clusters MUST be checked against alarms just before and throughout each and every drive is performed. Alarm check can be easily done accessing the SONAR web server of the relative market. Responsible: - RF engineer responsible of the cluster Tool: - SONAR web server of the relative market Action: - contact UTRAN Team which is responsible for debugging alarms Time Required: - 15 mins through SONAR web server For more information on some of the alarms that might have impact on RF performances refer to proper section in: Links_for_phase2_markets_PA1.doc

11. 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 2-5 20 pt Ericsson Confidential2006-05-1611 Cluster Pre-Launch Tuning and Go/No-Go Drives Preparation Phase TCM Parameter & Configuration Consistency Check: ensures all the radio/transport parameters are properly set according to the Ericsson recommended and the Cingular required settings (contained in the Parameter Baseline and eventually in the Local Market Exceptions list) and radio configuration data are set according to the design data (RND-CIQ). TCM team performs this check based on RF market team lead request. TCM will only perform 3 of these checks: 1.Before Pre-Launch Tuning 2.Before Launch 3.After Post-Launch Responsible: - RF market lead to issue a request for check to TCM team - RF market lead to provide updated RND-CIQ (and eventually Local Market Exceptions list) - TCM Team to run the check and generate the inconsistencies - TCM Team to verify the inconsistencies with RF\UTRAN team - RF market lead to update the RND-CIQ with eventual inconsistencies - ELS team to implement the changes Time Required: - if all the needed info are provided to TCM team the check should take less than 24 hrs For more information on Consistency Check refer to proper section of: Links_for_phase2_markets.doc

12. 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 2-5 20 pt Ericsson Confidential2006-05-1612 Cluster Pre-Launch Tuning and Go/No-Go Drives Preparation Phase UTRAN Configuration Consistency Check: ensures all radio configuration data are set according to design data (RND-CIQ). Typically this consistency check targets newly integrated sites (i.e. sites that are integrated after the full network audit performed by TCM team). The RF market team lead, in accordance with UTRAN support team, will identify the newly integrated sites and then the occurrences of the check. Responsible: - RF market lead issue the request to UTRAN - RF market lead provide updated RND-CIQ for check - UTRAN Team run the check and generate the inconsistencies - UTRAN Team verify the inconsistencies with RF market team - ELS team implement the changes - RF market lead update the RND-CIQ with eventual inconsistencies Time Required: - if all the needed info are provided to UTRAN team the check should take less than 24 hrs For more information on Consistency Check refer to proper section of: Links_for_phase2_markets.doc

13. 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 2-5 20 pt Ericsson Confidential2006-05-1613 Cluster Pre-Launch Tuning and Go/No-Go Drives Preparation Phase RF Parameter Consistency Check: ensures radio\transport parameters are properly set according to the Ericsson recommended and the Cingular required settings (contained in the Parameter Baseline database and eventually in the Local Market Exceptions list). The check also performs: missing neighbor analysis for both UTRAN and IRAT (RND-CIQ contains this info) Scrambling Code plan verification (against SC collisions) (RND-CIQ contains this info) Monitored List truncation analysis (RND-CIQ contains this info) The scope of this additional parameter consistency check is to keep track of the frequent and many changes that typically occur during tuning. (mainly new neighbors, but also SC allocation, PCpichPower or cell level tuned parameters) Responsible: - RF market lead is responsible for the check - RF market lead retrieve the network configuration file (KgetAll) through Sonar Web Server, the updated RND-CIQ and eventually the Local Market Exception list. - ELS team implement the change requests Tool: - C3 (consistency check) and RFCR (forward to ELS the change requests to be implemented) Action: - RF market lead run the check, review the inconsistencies, forward the change requests to ELS (through the RFCR tool) and update relative databases accordingly Time Required: - network configuration (kgetAll file) can be retrieved through Sonar web server in less than 10 mins. The consistency check takes max 30 mins. For more information on Consistency Check refer to proper section of: Links_for_phase2_markets.doc

14. 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 2-5 20 pt Ericsson Confidential2006-05-1614 Cluster Pre-Launch Tuning and Go/No-Go Drives Preparation Phase Tilt Audit: ensures all the antennas have their tilt set according to the RND-CIQ. (Tilt audit is not part of any consistency check). Responsible: - RF market team lead run the audit - Integration Team/Cingular should provide the tilt information - Integration Team implement changes Tool: - NA Action: - tilt misalignment will be fixed by integration team Cell Availability: makes sure most of the sites in the cluster are transmitting just before and throughout each and every drive. Responsible: - RF market team (RF engineer responsible of the cluster) Tool: - SONAR web server of the relative market Action: - contact UTRAN local support for debugging/resolution Time Required: - 8 mins through the Sonar web server

15. 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 2-5 20 pt Ericsson Confidential2006-05-1615 Cluster Pre-Launch Tuning and Go/No-Go Drives Preparation Phase Iub link Check (T1 Errored Seconds): the stability of the Iub links between the RBS and the RNC should be checked just before and throughout the data collection. Responsible: - RF market team (RF engineer responsible of the cluster) Tool: - SONAR web server of the relative market Action: - contact UTRAN support Time Required: - 8 mins through the Sonar web server Iu link Check (AAL Outgoing Connection History): the stability of the Iu links between the RNC and the CN should be checked just before and throughout data collection. Responsible: - RF market team (RF engineer responsible of the cluster) Tool: - SONAR web server of the relative market Action: - contact UTRAN support Time Required: - 8 mins through the Sonar web server

16. 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 2-5 20 pt Ericsson Confidential2006-05-1616 Cluster Pre-Launch Tuning and Go/No-Go Drives Preparation Phase Scrambling Code Collisions Check: eliminates the possibility that two different cells with the same scrambling code can be part of the same monitored set. The activity is a consistency check of the scrambling code plan in relation to neighbor cell definitions contained in the RND CIQ. Responsible: - RF market team lead Tool: - C3 Action: - in case of severe SC collisions the SC plan needs to be revised Time Required: - C3 tool performs the check in less than 30 mins

17. 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 2-5 20 pt Ericsson Confidential2006-05-1617 Cluster Pre-Launch Tuning and Go/No-Go Drives Preparation Phase Neighbor Cell Check: minimizes the number of dropped calls due to missing neighbors. The RF engineer is responsible for this activity. The lack of sites or the presence of new sites in the cluster, might trigger a revision of the design neighbor plan. This can be accomplished using the planning tool (or, in case of time constraints, by visual inspection on map). Also the definition of too many neighbors and the fact that the each neighbor list may not be prioritized might lead to dropped call due to truncation of the UE monitored list. The monitored list truncation analysis can be performed by C3 tool. The request for new neighbors implementation is handled through the RFCR tool. Responsible: - RF engineer responsible of the cluster - RF market lead make sure new sites are integrated with the proper neighbor defined (communication between RF-UTRAN-ELS) - ELS implement the change requests Tool: - C3 for monitored list truncation analysis - RFCR (forward to ELS the change requests to be implemented) Action : - review neighbor plan in case of missing or new integrated sites - change requests are forwarded to ELS team for implementation through RFCR tool. Time Required: - 3 hrs per cluster For more information on Neighbor Cell Check refer to proper section of: Links_for_phase2_markets.doc

18. 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 2-5 20 pt Ericsson Confidential2006-05-1618 Cluster Pre-Launch Tuning and Go/No-Go Drives Preparation Phase Handset Software Version Check: ensures the correct version of the mobile is used for data collection. Responsible: - RF market team lead Tool: - use the UE SW version tracker to get the latest UE SW Action: - RF market team lead to upgrade the UE accordingly Time Required: 1 hr For more detailed information about handset in use and relative issues refer to proper section of: Links_for_phase2_markets.doc

19. 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 2-5 20 pt Ericsson Confidential2006-05-1619 Cluster Pre-Launch Tuning and Go/No-Go Drives Preparation Phase RSSI check: ensures no external interferers are present in the area and helps out in detecting sites with eventually swapped feeders or faulty/loose connectors Responsible: - RF engineer responsible of the cluster Tool: - SONAR web server of the relative market Time Required: - 8 mins through the Sonar web server For more information about the RF effects of swapped feeders and site verification refer to proper section of: Site Verification in Links_for_phase2_markets.doc Traces set up: ensures all the needed traces are up and running before every drive. In case of UETR traces provide UTRAN support team the IMSI of the test UEs so they can activate them. UE Exception traces should be activated by default. Responsible: - RF engineer responsible of the cluster requires activation - UTRAN support team activate them Action: - contact UTRAN support for trace checkup/setup Note: in case of UETR set up ALL the protocols need to be activated (RRC, RANAP, RNSAP, NBAP, NAS)

20. 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 2-5 20 pt Ericsson Confidential2006-05-1620 Cluster Pre-Launch Tuning and Go/No-Go Drives Drive # 1 (Scanner + Long Voice call) Scanner + (Speech Long) #1 Preparation Phase Launch Long and Short PS R99 + HSDPA # 3 Go/No-Go (On Request) Speech Long and Short M to M # 2 Go/No-Go Drive #4 2 days for the analyses combined 3 day for the analyses 1 day for the analyses 3 days for tilt implementation 1 day dr. Go/No-Go Drive (Optional) 1 day for the analyses 1 day dr. Purpose of the drive is to verify single cell coverage and eventually suggest tilt adjustments. Missing neighbor analysis is also performed. It is very important this drive is performed with the highest Cell Availability figure (80% at least)

21. 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 2-5 20 pt Ericsson Confidential2006-05-1621 Cluster Pre-Launch Tuning and Go/No-Go Drives Drive # 1 (Scanner + Long Voice call) The drive test is setup according to: \\Cingular_UMTS1\Cingular UMTS\Info for PhaseII-Markets\Cingular UMTS Phase2 Pre Launch Tuning Drive Test Process.doc The density of this drive ranges from 250 to 750 meter resolution grid according to the accuracy of the prediction model. As a default use 500 meter grid for tuned models. After the drive is finished use the Sonar web server to check for eventual node restart during data collection and also check for Iu\Iub link status and alarms. Scanner (only) data will be analyzed by Omega or ACP tool with the purpose of single cell coverage verification and missing neighbor analysis (Omega tool). The data will also be used by ACP tool for tilt recommendations (in case site availability is at least 80%). The engineer MUST review all the ACP tilt recommendations before they are implemented. Any proposed recommendations will be forwarded to the ELS team for implementation through the RF Change Request tool. The tool keeps track of all the RF change requests per cluster. (for more details on the tool please refer to proper section in: Links_for_phase2_markets.doc)

22. 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 2-5 20 pt Ericsson Confidential2006-05-1622 Cluster Pre-Launch Tuning and Go/No-Go Drives Drive # 1 (Scanner + Long Voice call) Once the recommendations have been implemented in the network the master database has to be updated by the RF engineer responsible for the change. (For more information on which is the master database and on how to keep track of the implemented changes in the network, please refer to proper section in : Links_for_phase2_markets.doc) It is strongly recommended the engineer responsible for the cluster reports all the issues found during the analysis in the proper tracker. The purpose is to keep track of all the issues on a market basis. The same tracker will also be used for the description of the problem when it has to be escalated to the RF national team for more detailed analysis (a template of the Tuning Issue List can be found at: \\Cingular_UMTS1\Cingular UMTS\Info for PhaseII-Markets\Templates) The Voice data part will not be analyzed but only post processed by Omega tool. The resulting retainability figure will be used to evaluate whether next “On Demand” GoNoGo drive should be performed.

23. 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 2-5 20 pt Ericsson Confidential2006-05-1623 Cluster Pre-Launch Tuning and Go/No-Go Drives Drive # 2 (Long Voice + Mobile to Mobile Short Voice) To do list for the drive: 1.Alarm check 2.Cell Availability check 3.Iub and Iu links stability check (before and after the drive) 4.Neighbor Cell Check (in case new sites have been integrated) 5.Set up UETR traces for test UEs Scanner + (Speech Long) #1 Preparation Phase Launch Long and Short PS R99 + HSDPA # 3 Go/No-Go (On Request) Speech Long and Short M to M # 2 Go/No-Go Drive #4 2 days for the analyses combined 3 day for the analyses 1 day for the analyses 3 days for tilt implementation 1 day dr. Go/No-Go Drive (Optional) 1 day for the analyses 1 day dr. Purpose of the drive is to investigate any possible issue affecting call retainability and accessibility (both MO & MT). This is the most important drive for tuning purposes

24. 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 2-5 20 pt Ericsson Confidential2006-05-1624 Cluster Pre-Launch Tuning and Go/No-Go Drives Drive # 2 (Long Voice + Mobile to Mobile Short Voice) The drive test is setup according to: \\Cingular_UMTS1\Cingular UMTS\Info for PhaseII-Markets\Cingular UMTS Phase2 Pre Launch Tuning Drive Test Process.doc The drive uses the same route as the GoNoGo drive (at least 6 hrs). After the drive is finished use the Sonar web server to check for eventual node restart during data collection. Also check for alarms and Iu\Iub link status throughout the test duration. Use UETR traces and UE Exceptions traces (both traces are easily retrievable from the Sonar web server) together with UE and Scanner logs for detailed troubleshooting. (i.e. Drops and Access failures analysis and classification) It is possible to escalate issues that cannot be sorted out at market level to national RF team provided that: the issue is reported in the proper tracker (see next) all the needed traces and information are provided

25. 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 2-5 20 pt Ericsson Confidential2006-05-1625 Cluster Pre-Launch Tuning and Go/No-Go Drives Drive # 2 (Long Voice + Mobile to Mobile Short Voice) It is strongly recommended the engineer responsible for the cluster reports all the issues found during the analysis in the proper tracker. The purpose is to keep track of all the issues on a market basis. The same tracker will also be used for the description of the problem when it has to be escalated to the RF national team for more detailed analysis (a template of the Tuning Issue List can be found at: \\Cingular_UMTS1\Cingular UMTS\Info for PhaseII-Markets\Templates) TIW’s UE and scanner logs are post-processed by Omega tool for calculating various performance indicators (KPIs) for both retainability and accessibility. Recommendation for missing neighbors should be very limited at this stage (as it should be the number of tilt change proposals in case the ACP analysis has been performed in drive #1). Recommendations for some of the Local level parameters can be reported but no recommendations are expected for National Level parameters. (for more detailed information on parameter scope please refer to proper section in: Links_for_phase2_markets.doc)

26. 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 2-5 20 pt Ericsson Confidential2006-05-1626 Cluster Pre-Launch Tuning and Go/No-Go Drives Drive # 2 (Long Voice + Mobile to Mobile Short Voice) The proposed recommendations will be forwarded to the ELS team for implementation through the RF Change Request tool. The tool also keeps track of all the RF change requests per cluster. (for more details on the tool please refer to proper section in: Links_for_phase2_markets.doc) Once the recommendations have been implemented in the network the master database has to be updated by the RF engineer responsible for the change request. (For more information on which is the master database and on how to keep track of the implemented changes in the network, please refer to proper section in : Links_for_phase2_markets.doc)

27. 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 2-5 20 pt Ericsson Confidential2006-05-1627 Cluster Pre-Launch Tuning and Go/No-Go Drives Drive # 3 (Long & Short PS R`99 + HSDPA Download) Scanner + (Speech Long) #1 Preparation Phase Launch Long and Short PS R99 + HSDPA # 3 Go/No-Go (On Request) Speech Long and Short M to M # 2 Go/No-Go Drive #4 2 days for the analyses combined 3 day for the analyses 1 day for the analyses 3 days for tilt implementation 1 day dr. Go/No-Go Drive (Optional) 1 day for the analyses 1 day dr. To do list for the drive: 1.Alarm check 2.Cell Availability check 3.Iub and Iu links stability check (before and after the drive) 4.Neighbor Cell Check (in case new sites have been integrated) 5.Set up UETR traces for test UEs Purpose of the drive is to assess network retainability (PS long) accessibility (PS short) and HSDPA performances.

28. 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 2-5 20 pt Ericsson Confidential2006-05-1628 Cluster Pre-Launch Tuning and Go/No-Go Drives Drive # 3 (3 MB PS R`99 + 5 MB HSDPA Download) The drive test is setup according to: \\Cingular_UMTS1\Cingular UMTS\Info for PhaseII-Markets\Cingular UMTS Phase2 Pre Launch Tuning Drive Test Process.doc The drive uses the same route as the GoNoGo drive (at least 6 hrs). After the drive is finished use the Sonar web server to check for eventual node restart during data collection. Also check for alarms and Iu\Iub link status throughout the test duration. Use UETR traces and UE Exceptions traces (both traces are easily retrievable from the Sonar web server) together with UE and Scanner logs for detailed troubleshooting. (i.e. Drops and Access failures analysis and classification) It is possible to escalate issues that cannot be sorted out at market level to national RF team provided that: the issue is reported in the proper tracker (see next) all the needed traces and information are provided

29. 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 2-5 20 pt Ericsson Confidential2006-05-1629 Cluster Pre-Launch Tuning and Go/No-Go Drives Drive # 3 (3 MB PS R`99 + 5 MB HSDPA Download) It is strongly recommended the engineer responsible for the cluster reports all the issues found during the analysis in the proper tracker. The purpose is to keep track of all the issues on a market basis. The same tracker will also be used for the description of the problem when it has to be escalated to the RF national team for more detailed analysis (a template of the Tuning Issue List can be found at: \\Cingular_UMTS1\Cingular UMTS\Info for PhaseII-Markets\Templates) TIW’s UE and scanner logs are post-processed by Omega tool for calculating various performance indicators (KPIs) for both retainability and accessibility. Recommendation for missing neighbors should be very limited at this stage (as it should be the number of tilt change proposals in case the ACP analysis has been performed in drive #1). Recommendations for some of the Local level parameters can be reported but no recommendations are expected for National Level parameters. (for more detailed information on parameter scope please refer to section 4.6.2 Parameter Scope in: Links_for_phase2_markets.doc)

30. 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 2-5 20 pt Ericsson Confidential2006-05-1630 Cluster Pre-Launch Tuning and Go/No-Go Drives Drive # 3 (3 MB PS R`99 + 5 MB HSDPA Download) The proposed recommendations will be forwarded to the ELS team for implementation through the RF Change Request tool. The tool also keeps track of all the RF change requests per cluster. (for more details on the tool please refer to proper section in: Links_for_phase2_markets.doc) Once the recommendations have been implemented the master database has to be updated by the RF engineer responsible for the change. (For more information on which is the master database and on how to keep track of the implemented changes in the network, please refer to proper section in : Links_for_phase2_markets.doc) It is strongly recommended the engineer responsible for the cluster analysis reports all the issues found during the analysis in the proper tracker. (a template of the Tuning Issue List can be found at: \\Cingular_UMTS1\Cingular UMTS\Info for PhaseII- Markets\Templates)

31. 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 2-5 20 pt Ericsson Confidential2006-05-1631 Cluster Pre-Launch Tuning and Go/No-Go Drives Drive # 4 Go No Go Drive To do list for the drive: 1.Alarm check 2.Cell Availability check 3.Iub and Iu links stability check (before and after the drive) 4.Neighbor Cell Check (in case new sites have been integrated) 5.Set up UETR traces for test UEs Scanner + (Speech Long) #1 Preparation Phase Launch Long and Short PS R99 + HSDPA # 3 Go/No-Go (On Request) Speech Long and Short M to M # 2 Go/No-Go Drive #4 2 days for the analyses combined 3 day for the analyses 1 day for the analyses 3 days for tilt implementation 1 day dr. Go/No-Go Drive (Optional) 1 day for the analyses 1 day dr. Purpose of the drive is to monitor network performances according to GNG scope and report the KPIs to Cingular which will then decide whether the commercial launch can take place

32. 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 2-5 20 pt Ericsson Confidential2006-05-1632 Cluster Pre-Launch Tuning and Go/No-Go Drives Drive # 5 Go No Go Drive The drive test is setup according to: \\Cingular_UMTS1\Cingular UMTS\Info for PhaseII-Markets\Cingular UMTS Phase2 Pre Launch Tuning Drive Test Process.doc Use the GNG drive (at least 6 hrs) The Agilent logs will then be post-processed by Actix. Detailed troubleshooting is performed in case the GoNoGo KPIs are not fulfilled. An explanation MUST be provided for the KPI which is failing and each and every failure (drop or access failure) MUST be classified. It is very important to identify all the issues in the cluster that are affecting the GNG KPIs. In case site availability, interim solution site, delay in antenna tilt implementation and T1 link instability are affecting the GNG KPIs, no additional GNG drive should be performed until most of these problems are fixed. The following and final GNG drive (Optional) should then only be performed when most of the cluster issues have been fixed.

33. 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 2-5 20 pt Ericsson Confidential2006-05-1633