intTypePromotion=1

3G_Pre-launch Optimization Guidelines

Chia sẻ: Trần Ngọc Sang | Ngày: | Loại File: PDF | Số trang:93

0
58
lượt xem
11
download

3G_Pre-launch Optimization Guidelines

Mô tả tài liệu
  Download Vui lòng tải xuống để xem tài liệu đầy đủ

Pre-launch optimization basically deals withassessing a newly-built network, uncoveringproblems and resolving them prior to commerciallaunch. It entails detailed field rf measurements,detecting and rectifying problems caused byradio, improper parameter settings or networkfaults and finally, grading the radio access part of the network to make sure that it passes certainevaluation criteria

Chủ đề:
Lưu

Nội dung Text: 3G_Pre-launch Optimization Guidelines

  1. GUIDELINES Version Status RF Optimization Guideline for AMX 3G Rollout 1 August, 27th 2007 Consulting and System Integrations Revised by: Danilo Cabral Raj Sandhu, Allan Bispo and Daniel Platero GUIDELINE for 3G RF OPTIMIZATION America Movil LATAM Projects Owner: NSN Scope: Guidelines Originator: Raj Sandhu, Allan Bispo and Daniel Platero Revised by: Danilo Cabral Status: Version 1.1 Document ID: Location: NSN BR
  2. GUIDELINES Version Status RF Optimization Guideline for AMX 3G Rollout 1 August, 27th 2007 Consulting and System Integrations Revised by: Danilo Cabral Raj Sandhu, Allan Bispo and Daniel Platero Table of Content DOCUMENT HISTORY ....................................................................................................................... 5 1. Introduction .................................................................................................................................. 6 1.1 Purpose................................................................................................................................. 6 1.2 Overview ............................................................................................................................... 6 2. RF Cluster Acceptance ................................................................................................................ 8 2.1 Preparation Phase................................................................................................................. 8 2.1.1 Compilation of planning data .......................................................................................... 9 2.1.2 Site Clustering ................................................................................................................ 9 2.1.3 Drive Routes and Site Selection for Stationary Test, IRAT and RAU .............................. 9 2.1.4 Field Measurement Tools ............................................................................................. 10 2.1.4.1 Field Measurement Tools Setup ............................................................................... 11 2.1.5 Post Processing Tools.................................................................................................. 11 2.1.6 Consistency Check....................................................................................................... 12 2.1.7 Alarm Check................................................................................................................. 12 2.1.8 PrxNoise Check............................................................................................................ 12 2.1.9 Cell Availability ............................................................................................................. 13 2.2 Optimization Phase.............................................................................................................. 13 2.2.1 Stationary Testing......................................................................................................... 13 2.2.2 IRAT Testing ................................................................................................................ 15 2.2.3 RAU Testing ................................................................................................................. 15 2.2.4 Mobile Testing .............................................................................................................. 15 2.2.5 Cluster KPI References ................................................................................................ 16 2.2.6 Drive-test UE Distribution – Cluster Level..................................................................... 16 2.2.7 Data Processing, Analysis and Report.......................................................................... 17 2.2.8 Change Request........................................................................................................... 17 2.3 Acceptance Phase............................................................................................................... 18 3. RF PROJECT Acceptance......................................................................................................... 19 3.1 Preparation Phase............................................................................................................... 20 3.2 Optimization Phase.............................................................................................................. 20 3.2.1 IRAT Testing ................................................................................................................ 21 3.2.2 Mobile Testing .............................................................................................................. 21 3.2.3 Cluster KPI References ................................................................................................ 21 3.2.4 Drive-test UE Distribution – Project Level ..................................................................... 21 3.2.5 Data Processing, Analysis and Report.......................................................................... 22 3.2.6 Change Request........................................................................................................... 22 3.3 Acceptance Phase............................................................................................................... 22 4. Radio Optimization Guide .......................................................................................................... 23 4.1 Initial Tuning ........................................................................................................................ 23 4.1.1 Definitions..................................................................................................................... 23 4.1.2 Initial Tuning Procedure – Overview ............................................................................. 24 4.1.2.1 Preparation Phase .................................................................................................... 24 4.1.2.2 Measurement Collection ........................................................................................... 25 4.1.2.3 Post-processing and Reporting ................................................................................. 30 4.1.2.4 RF Analysis............................................................................................................... 30 4.1.3 Pilot Pollution................................................................................................................ 38 4.1.4 Coverage for different services ..................................................................................... 39 4.1.5 Handover Verifications.................................................................................................. 39 4.1.5.1 Soft-Handover Area Distribution................................................................................ 40 4.1.5.2 Neighbour List Optimization ...................................................................................... 41 4.1.5.3 Missing Neighbour .................................................................................................... 43 4.1.5.4 Inter-system Handover Verification (IRAT HO).......................................................... 44 4.1.6 Other Issues not related to RF optimization .................................................................. 45
  3. GUIDELINES Version Status RF Optimization Guideline for AMX 3G Rollout 1 August, 27th 2007 Consulting and System Integrations Revised by: Danilo Cabral Raj Sandhu, Allan Bispo and Daniel Platero 4.1.6.1 UE Issues ................................................................................................................. 45 4.1.6.2 UTRAN HW and SW Issues...................................................................................... 46 4.1.6.3 CORE Issues ............................................................................................................ 46 4.1.6.4 Drive-test Equipment Issues ..................................................................................... 46 4.2 Optimization ........................................................................................................................ 47 4.2.1 Common performance issues that affect any service.................................................... 47 4.2.2 Video Call Performance Issues..................................................................................... 50 4.2.3 PS Call Performance Issues......................................................................................... 50 4.2.4 IRAT performance ........................................................................................................ 52 4.2.5 OSS KPI’s optimization................................................................................................. 53 4.2.5.1 Accessibility related problems ................................................................................... 53 4.2.5.2 Retainability related problems ................................................................................... 53 4.2.5.3 Availability and Usage related problems (Capacity optimization)............................... 54 4.2.5.4 Mobility related problems .......................................................................................... 54 4.2.5.5 Integrity related problems.......................................................................................... 54 5. Database parameters check and optimization............................................................................ 54 5.1 Parameter groups in RNC Database ................................................................................... 55 5.2 Consistency Check.............................................................................................................. 56 5.3 Parameter optimization........................................................................................................ 56 5.3.1 RNC Parameters .......................................................................................................... 56 5.3.2 COCO Parameters ....................................................................................................... 56 5.3.3 W ANE and WGS Parameters ....................................................................................... 56 5.3.4 W LCSE and WSMLC Parameters ................................................................................ 57 5.3.5 FMCI, HOPI and ADJI Parameters ............................................................................... 57 5.3.6 W BTS Parameters........................................................................................................ 57 5.3.7 W CEL........................................................................................................................... 57 5.3.8 FMCS ........................................................................................................................... 58 5.3.9 FMCG........................................................................................................................... 60 5.3.10 HOPS ....................................................................................................................... 60 5.3.11 HOPG ....................................................................................................................... 61 5.3.12 ADJS ........................................................................................................................ 61 5.3.13 ADJG ........................................................................................................................ 62 6. Appendix.................................................................................................................................... 63 6.1 KPI Targets ......................................................................................................................... 63 6.2 Drive-test KPI Measurements – Detailing of Layer 3 Messages........................................... 64 6.2.1 Drive-test KPI Measurements – CS Voice Service........................................................ 65 6.2.1.1 CS Voice Service: Voice Call Setup Success Rate ................................................... 65 6.2.1.2 CS Voice Service: Voice Call Setup Time ................................................................. 65 6.2.1.3 CS Voice Service: Voice Call Drop Rate ................................................................... 66 6.2.1.4 CS Voice Service: Voice Call BLER DL..................................................................... 67 6.2.1.5 CS Voice Service: Voice IRAT Handover – from 3G to 2G........................................ 68 6.2.1.6 CS Voice Service: Voice IRAT Handover – from 2G to 3G........................................ 69 6.2.2 Drive-test KPI Measurements – CS UDI Video Service ................................................ 70 6.2.2.1 CS UDI Video Service: Video Call Setup Success Rate............................................ 70 6.2.2.2 CS UDI Video Service: CS Video Call Setup Elapsed Time < 20 seconds ................ 70 6.2.2.3 CS UDI Video Service: CS Video Call Drop Rate...................................................... 71 6.2.2.4 CS UDI Video Service: CS Video Call BLER DL ....................................................... 72 6.2.3 Drive-test KPI Measurements – PS Realese 99 Data Service ...................................... 73 6.2.3.1 PS Realese 99 Data Service: PS RAB Establishment Success Rate ........................ 73 6.2.3.2 PS Realese 99 Data Service: PS Round Trip Time................................................... 74 6.2.3.3 PS Realese 99 Data Service: PS RAB Drop Rate..................................................... 75 6.2.3.4 PS Realese 99 Data Service: PS DL Throughput...................................................... 76 6.2.3.5 PS Realese 99 Data Service: PS UL Throughput...................................................... 77 6.2.4 Drive-test KPI Measurements – PS HSDPA Data Service ............................................ 78
  4. GUIDELINES Version Status RF Optimization Guideline for AMX 3G Rollout 1 August, 27th 2007 Consulting and System Integrations Revised by: Danilo Cabral Raj Sandhu, Allan Bispo and Daniel Platero 6.2.4.1 PS HSDPA Data Service: PS Round Trip Time......................................................... 78 6.2.4.2 PS HSDPA Data Service: PS HSDPA Throughput.................................................... 79 6.2.5 Drive-test KPI Measurements – TCP Setting for Data Services .................................... 80 6.2.6 Drive-test KPI Measurements – Multi-RAB Service ...................................................... 81 6.2.6.1 Multi-RAB Services: AMR Voice CSSR during PS Calls ........................................... 81 6.2.6.2 Multi-RAB Services: PS Data CSSR during AMR Voice Calls ................................... 83 6.2.7 Drive-test KPI Measurements – Others Services .......................................................... 85 6.2.7.1 Others Services: SMS Success Rate ........................................................................ 85 6.2.7.2 Others Services: SMS Delivery Time < 40 seconds .................................................. 86 6.2.7.3 Others Services: WAP Failure Rate .......................................................................... 87 6.2.7.4 Others Services: WAP Session Establishment Elapsed Time < 13 seconds ............. 88 6.2.7.5 Others Services: MMS Success Rate ....................................................................... 89 6.2.7.6 Others Services: MMS Delivery Time < 40 seconds.................................................. 90 6.2.8 Drive-test KPI Measurements – RAU Testing ............................................................... 91 7. References ................................................................................................................................ 92
  5. GUIDELINES Version Status RF Optimization Guideline for AMX 3G Rollout 1 August, 27th 2007 Consulting and System Integrations Revised by: Danilo Cabral Raj Sandhu, Allan Bispo and Daniel Platero DOCUMENT HISTORY DATE ISSUE EDITED BY SUMMARY OF CHANGES Aug 23th 07 V1.0 Initial version. Allan Bispo and Daniel Platero Aug 27th 07 V1.1 Revision 1 Allan Bispo and Danilo Cabral
  6. GUIDELINES Version Status RF Optimization Guideline for AMX 3G Rollout 1 August, 27th 2007 Consulting and System Integrations Revised by: Danilo Cabral Raj Sandhu, Allan Bispo and Daniel Platero 1. INTRODUCTION 1.1 Purpose This document describes the processes for Radio Access Network (RAN) optimization of the AMX LATAM WCDMA based third generation radio access network. The focus of this document is on the Radio Frequency (RF) optimization and acceptance criteria. 1.2 Overview The figure below shows the overview of acceptance requirement for the AMX LATAM project. Site RF Cluster RF Project Implementation PAC FAC Acceptance Acceptance Acceptance Figure 1 : AMX Acceptance Overview – NSN proposed version Site implementation acceptance is carried out by the implementation team after the site has been commissioned and put on air. Once site implementation acceptance has been granted and the cluster is deemed fit for optimization, RF cluster acceptance will begin. Here stationary and drive testing will be carried out. Once the KPI’s are achieved for all clusters, the RF project acceptance could begin. At this phase all tests carried out at the cluster acceptance will be done again at project level. The main diference here is, besides the amout of points of interstes of the stationary tests, the coverage test. Coverage verification at project level is carried out under 50% load. The other tests do not need this additional loading. After that Provisional Acceptance (PAC) can be granted. For the Final Acceptance (FAC) many key performance indicators need to be above the customer target during a certain stability period. The figure below shows the relationship between all acceptance stages.
  7. GUIDELINES Version Status RF Optimization Guideline for AMX 3G Rollout 1 August, 27th 2007 Consulting and System Integrations Revised by: Danilo Cabral Raj Sandhu, Allan Bispo and Daniel Platero Figure 2 : Overview of the Acceptance Stages – NSN proposed version
  8. GUIDELINES Version Status RF Optimization Guideline for AMX 3G Rollout 1 August, 27th 2007 Consulting and System Integrations Revised by: Danilo Cabral Raj Sandhu, Allan Bispo and Daniel Platero 2. RF CLUSTER ACCEPTANCE The figure below gives an overview of the RF Cluster Acceptance process. Network Planning Rollout Phase Preparation Phase Preparation Stage for Cluster Acceptance Testing Perform Stationary Testing Perform IRAT Testing* Perform RAU Testing Optimization Perform Perform Mobile Testing Phase Data Processing, Analysis & Network Optimization & Report Change Request N KPIs Achieved Y RF Cluster Acceptance Acceptance Phase Submit Report to AMX Project Acceptance Phase Figure 3 : RF Cluster Acceptance Process Overview * Only for clusters which contain 3G/2G borders sites The RF cluster acceptance process can be grouped into 3 main sections which are the preparation phase, optimization phase and the acceptance phase. 2.1 Preparation Phase This phase is triggered once the rollout phase is approaching its end. The objective of this phase is to prepare all the pre-requisites for the optimization phase. This can be broken down as below: Compilation of planning data V Site Clustering V
  9. GUIDELINES Version Status RF Optimization Guideline for AMX 3G Rollout 1 August, 27th 2007 Consulting and System Integrations Revised by: Danilo Cabral Raj Sandhu, Allan Bispo and Daniel Platero Drive Routes & Site Selection for IRAT and Stationary Test V Field Measurement Tools V Post-processing Tools V Parameter Consistency Check V Alarm Monitoring V PrxNoise Check V Cell Availability V 2.1.1 Compilation of planning data It is essential that all the planning data be collected and saved in an organized manner in order to be useful during the optimization phase. The required information from planning stage is: Technical Site Survey Report (TSSR) including panoramic pictures V As-built Site Drawing V Complete Site Database including Site_ID, Cell_ID, RNC_ID, BTS_ID, LAC, RAC, URA, SAC, V Antenna Type, Antenna Height, Azimuth, Tilt (Mechanical and Electrical), Scrambling Code, ATM layer parameters, Iu parameters, IP settings etc Coverage plots for Loaded and Unloaded cases V Service Area plots for the services that require optimization V 2.1.2 Site Clustering The clusters shall be defined by Nokia Siemens Networks and documented. Following criteria shall be used in defining the cluster: 1. Each cluster shall comprise a contiguous network area of approximately 10 to 15 sites. 2. Cluster shall not be defined across RNC boundary. 2.1.3 Drive Routes and Site Selection for Stationary Test, IRAT and RAU The drive routes for cluster acceptance will be mutually agreed by America Movil LatAm and NOKIA SIEMENS NETWORKS. Drive Routes must cover all main avenues and large streets within in the cluster. Main avenues should be driven in both directions as possible. The drive routes shall be selected such that the drive route can be completed, regarding all tests scenarios mutually agreed with the customer, in one (1) day. IRAT and stationary tests will demand one (1) additional day. Target sites for Stationary testing, IRAT and RAU will be mutually agreed by America Movil LatAm and NOKIA SIEMENS NETWORKS. The IRAT sites will also be known as 3G/2G Border Sites. Ensure the following has been carried out The stationary test locations have been mutually agreed by America Movil LatAm and NOKIA V SIEMENS NETWORKS. This should not be more then 20% of the total sites in the cluster and should be carried out in all sectors of the selected sites.
  10. GUIDELINES Version Status RF Optimization Guideline for AMX 3G Rollout 1 August, 27th 2007 Consulting and System Integrations Revised by: Danilo Cabral Raj Sandhu, Allan Bispo and Daniel Platero The IRAT and RAU drive routes have been mutually agreed by America Movil LatAm and NOKIA V SIEMENS NETWORKS. The mobile drive routes for cluster acceptance have been mutually agreed by America Movil LatAm V and NOKIA SIEMENS NETWORKS. 2.1.4 Field Measurement Tools The cluster acceptance test shall consist of drive tests using Field Measurement Tools (FMT) to verify that the call set-up and soft handovers are working properly, to detect bad quality and interference areas, to detect unexpected lack of coverage and to test the Radio Access Bearers (RAB) that are used to support the required services as specified in the contract. The chosen FMT should be at least be able to measure the required data in order to calculate the KPIs for cluster acceptance. It is extremely important to have the right FMT to carry out the RF cluster acceptance. The FMT comprises of the following: Notebook equipped with the FMT software V The notebook is used to record all the measurement from the FMT. Ensure the Notebook has specification in accordance with the FMT requirement which depends on the FMT tool used. Also the Notebook should NOT be a NOKIA SIEMENS NETWORKS customized notebook as these normally have encrypted hard drives and lots of security software which can affect the results of testing. This notebook should be used dedicated for the drive or stationary testing only. GPS for latitude/longitude information V UEs V These UEs should be supported by the FMT tool. Scanner V The purpose of using the RF scanner is to be able to scan and measure all used carriers/cells and their corresponding DL scrambling codes. This gives the complete air interface condition of the radio network within a selected frequency band. The results are used to identify and understand reasons for peculiar behavior discovered during field measurements. . The data obtained with the scanner can be useful to evaluate: low coverage areas o antenna installation problems o missing neighbors o coverage optimization o The field measurement tool to be used is NEMO Outdoor:
  11. GUIDELINES Version Status RF Optimization Guideline for AMX 3G Rollout 1 August, 27th 2007 Consulting and System Integrations Revised by: Danilo Cabral Raj Sandhu, Allan Bispo and Daniel Platero Figure 4: Field Measurement Tool Analysis 2.1.4.1 Field Measurement Tools Setup For the coverage verifications in Cluster Acceptance phase, the terminal antenna must be situated external to the vehicle, and the UE must be in idle mode. Coverage test at Project Level will be carried out with UE in connected mode in order to obtain an UE Tx power map. For all field QoS drives and verifications in Cluster and Project Acceptance phases, an external antenna must not be used. The UEs are part of the FMT. Below is showed a distribution of UE required to fullfil the most important 3G tests: ü PS Rel 99 UE : AMR Voice Calls, PS Rel99 Data Calls, PS Rel Multi-RAB, RAU, IRAT HO and coverage verification (in idle mode as well); ü HSDPA UE (Cat 12): HSDPA Multi-RAB calls and Data Calls; CS video; ü HSDPA Datacard (Cat 6): PS HSDPA Data Calls In the Figures 6 and 9 these UEs are arranged in order to fulfill the AMX acceptance tests. 2.1.5 Post Processing Tools The post processing tools are used for the purpose of analyzing performance related issues during the optimization phase. It is important that the analysis tool works well with the FMT in order to be able to capture all the events reported in the FMT. The outcome of the analysis tools will be used to generate the RF Cluster Acceptance Report. For the AMX project there are 3 options of post-processing tools being analyzed, as could be seen below. Gladiator is the first option until now because fulfills all technical requirements, allows implementing automatic analysis and reporting, and finally, is being offered by a competitive price. The other two options, Nemo Analyzer and Actix, also fulfill the technical requirements but do not allow any automatization. Nemo Analyzer is quite chipper than Gladiator while Actix is much more expensive.
  12. GUIDELINES Version Status RF Optimization Guideline for AMX 3G Rollout 1 August, 27th 2007 Consulting and System Integrations Revised by: Danilo Cabral Raj Sandhu, Allan Bispo and Daniel Platero Figure 5: Post-processing Tool Analysis 2.1.6 Consistency Check Consistency checks shall be carried out for RAN parameter to compare the actual to the planned. Also 2G and 3G neighbor bi-directional relationships shall be check for consistency between planned and actual. This should be carried out for all sites within the cluster to be tested up till its tier 3 neighbors before any acceptance testing. Further to this, ATM, Iu and IP settings should also be checked to be consistent to as planned. 2.1.7 Alarm Check The WBTS alarms shall be checked via the OSS to ensure there is no service effecting alarm. Should there be service effecting alarms; the optimization phase shall be delayed until the alarms are cleared. This should be carried out for all sites within the cluster to be tested up till its tier 3 neighbors before any cluster optimization testing. 2.1.8 PrxNoise Check The UL interference can be evaluated by looking into the PrxNoise measurements. The normal value for this is in the range of -102 dBm to -105 dBm. Higher values would give an indication that there maybe some issues in the cell. Possible scenarios could be external interference or wrong settings for MHA parameters.
  13. GUIDELINES Version Status RF Optimization Guideline for AMX 3G Rollout 1 August, 27th 2007 Consulting and System Integrations Revised by: Danilo Cabral Raj Sandhu, Allan Bispo and Daniel Platero 2.1.9 Cell Availability The cell availability of the sites gives an indication of the health of the WBTS. Prior to starting the cluster acceptance drive testing, at least 3 days data of cell availability should be looked at to ensure that the site has been in working condition. If there are periods of unavailability which has not been planned, then there may be issues on the cell. This has to be investigated prior to starting the cluster optimization. 2.2 Optimization Phase Once the mains sites defined in the target cluster have achieved all integration and site acceptance requirement, Nokia Siemens Networks will initiate the RF cluster optimization, being a requisite to that the sites in a cluster must not have any impeditive restriction. The technical aspects related to the optimization activities for cluster optimizaion are available at the chapter “Radio Optimizaiton Guide”. The optimization phase can be divided to 4 main activities: the Stationary Testing, IRAT Testing, RAU Testing and Mobile Testing. These are explained in more detailed below. 2.2.1 Stationary Testing Stationary Testing will be carried out on the predefined Sites which have been mutually agreed between Nokia Siemens Networks and America Movil LatAm. This should not be more then 20% of the total sites in the cluster and should be carried out in all sectors of the selected sites. The figure below shows the Stationary Test Cases to be carried out. Stationary testing Test Test case KPI collected Description ID - Mobile is in idle mode - Requests PDP Context Activation - Large ping to force DCH channel 1 PS Rel99 RTT PS Data Latency (release 99) - Pings specific IP address with 32 bytes packet - Set 100 pings - Repeat cycle - Mobile in car in idle state - Requests PDP Context Activation - Connects to FTP server and initiate FTP DL of 1Mbyte file PSD Throughput UE Mobile PS Rel99 DL 2 per RB - Wait some time at the end of DL (inactivity param. dependent) for Throughput PSD Call Set up time DCH to be released - Deactivate the PDP Context Activation - Repeat the cycle 10 times. - Mobile in car in idle state - Requests PDP Context Activation PS Rel99 UL PSD Throughput UE Mobile - Connects to FTP server and initiate FTP UL of 200 kbyte file 3 Throughput per RB - At the end, waits 15 sec. for DCH to be released PSD Call Set up time - Deactivate the PDP Context Activation - Repeat the cycle 10 times. - Mobile is in idle mode - Requests PDP Context Activation - Large ping to force HS-DCH channel 4 PS HSDPA RTT PS Data Latency (release 5) - Pings specific IP address with 32 bytes packet - Set 100 pings - Repeat cycle
  14. GUIDELINES Version Status RF Optimization Guideline for AMX 3G Rollout 1 August, 27th 2007 Consulting and System Integrations Revised by: Danilo Cabral Raj Sandhu, Allan Bispo and Daniel Platero - Mobile in car in idle state - Requests PDP Context Activation HSDPA Call 5 - Connects to FTP server and initiate FTP DL of 10Mbyte file PSD HSDPA Throughput UE 5 code (and 15 code - Wait some time at the end of DL (inactivity param. dependent) for Mobile per RB when available) HS-DCH to be released PSD HSDPA Call Set up time - Deactivate the PDP Context Activation - Repeat the cycle 10 times. - Large video streaming session is held (Rel99) - AMR Voice calls are started - A Party calls B Party and call held for 20 seconds AMR / Rel99 AMR voice CSSR during PS - A Party Terminates AMR Voice call 6 MultiRAB 64/64 call - Time between calls = 10 seconds - Repeat AMR voice calls 10 times - Stop PS session - Repeat the whole cycle - 3G to PSTN Voice call - Hold it indefinitely - Wait 10 seconds AMR / Rel99 PS 64/64 CSSR during AMR - GPRS attach and PDP Context Activation 7 MultiRAB Voice call - Pings specific IP address with 32 bytes packet 10 x - PDP Context De-activation and GPRS Detach - Repeat cycle 10 times - A Party terminates AMR voice call - Large video streaming session is held (Rel99) - AMR Voice calls are started - A Party calls B Party and call held for 20 seconds AMR / HSPA AMR voice CSSR during PS - A Party Terminates AMR Voice call 8 MuliRAB HSPA call - Time between calls = 10 seconds - Repeat AMR voice calls 10 times - Stop PS session - Repeat the whole cycle - 3G to PSTN Voice call - Hold it indefinitely - Wait 10 seconds AMR / HSPA PS HSPA CSSR during AMR - GPRS attach and PDP Context Activation 9 MultiRAB Voice call - Pings specific IP address with 32 bytes packet 10 x - PDP Context De-activation and GPRS Detach - Repeat cycle 10 times - A Party terminates AMR voice call - Mobile in Car in idle state and CS attached * Short Message SMS Success Rate - Send a SMS
  15. GUIDELINES Version Status RF Optimization Guideline for AMX 3G Rollout 1 August, 27th 2007 Consulting and System Integrations Revised by: Danilo Cabral Raj Sandhu, Allan Bispo and Daniel Platero 2.2.2 IRAT Testing IRAT Testing will be carried out on a predefined route and predefined sites in the clusters that contain 3G/2G border sites. Voice calls will be make in order to evaluate the IRAT Handover Failures. It should be carried out as functionality test at a defined 3G/2G border, repeting the process 10 times. The figure below shows the IRAT Test Cases to be carried out. IRAT testing Test Test case KPI collected Description ID - AMR continuous call (dual mode) established on the 3G side - DT car moves toward the 2G network H andover from Voice ISHO Success Rate (3G - IRAT handover 1 UTRAN for CS to 2G) voice service - Ends call in the 2G side - Repeat cycle. - Voice continuous call (dual mode) established on the 2G side H andover to - DT car moves toward the 3G network Voice ISHO Success Rate (2G 2 - IRAT handover UTRAN for CS to 3G) - Ends call in the 3G side voice service - Repeat cycle. T able 2: IRAT Test Cases 2.2.3 RAU Testing Routing Area Update (RAU) Testing will be carried out on a border of routing areas inside of the same SGSN footprint, for that clusters that contain different RAs, or are located on a border of RAs. RAU Testing will be carried out for Packet Calls evaluating the intra SGSN routing area update time. It is recommended repeating the cycle 10 times in both RA directions. The figure below shows the RAU Test Cases to be carried out. RAU testing Test Test case KPI collected Description ID - Mobile in Car in idle state, no PDP context established - UE enters in a new Routing Area PS Continuous Intra SGSN Routing Area - Requests PDP Context Activation 1 - UE requests Routing Area update Call (Dual Mode) Update Time - UE grants a new Routing Area - Repeat the cycle 10 times in both RA directions T able 3: RAU Test Cases 2.2.4 Mobile Testing Mobile testing will be carried out on the route defined to the acceptance which has mutually been agreed between Nokia Siemens Networks and America Movil LatAm. The table below shows the Mobile test cases to be carried out. Mobile testing Test Test case KPI collected description ID
  16. GUIDELINES Version Status RF Optimization Guideline for AMX 3G Rollout 1 August, 27th 2007 Consulting and System Integrations Revised by: Danilo Cabral Raj Sandhu, Allan Bispo and Daniel Platero 1 Idle Mode Coverage Verification - drive on the test route with UE in idle mode using an external antenna kit. - 3G to PSTN Voice call Voice CSSR (call setup - Originating side located in the vehicle, terminating side (an answer success rate) AMR Short Call machine) located in the customer MSC of the test area 2 Voice CST (call setup time) (3G to PSTN) - A Party calls B Party and call held for 60 seconds Voice Drop Rate - A Party Terminates Voice BLER - Time between calls = 10 seconds - 3G to 3G Video call CS Video CSSR (call setup - Originating side located in the vehicle success rate) - Terminating side located in office Video Short Call CS Video Call Setup Elapsed 3 - A Party calls B Party (3G to 3G) Time - Call held for 60 seconds after app. level has been set up Voice Drop Rate - A Party Terminates Voice BLER - Time between calls = 10 seconds - Mobile in car in idle state - Requests PDP Context Activation DL WCDMA User Throughput - Connects to a customer FTP server and initiate FTP DL of 1Mbyte file PS RAB Establishment 4 DL PS Rel99 - Wait some time at the end of DL (inactivity param. dependent) for DCH to Success be released PS RAB Drop - Deactivate the PDP Context Activation - Repeat the cycle 10 times. - Mobile in car in idle state UL WCDMA User Throughput - Requests PDP Context Activation PS RAB Establishment - Connects to a customer FTP server and initiate FTP UL of 200 kbyte file 5 UL PS Rel99 Success - At the end, waits 15 sec. for DCH to be released PS RAB Drop - Deactivate the PDP Context Activation - Repeat the cycle 10 times. - Mobile in car in idle state - Requests PDP Context Activation DL HSDPA Call - Connects to a customer FTP server and initiate FTP DL of 10Mbyte file 5 code (and 15 6 DL HSDPA User Throughput - Wait some time at the end of DL (inactivity param. dependent) for HS- code when DCH to be released available) - Deactivate the PDP Context Activation - Repeat the cycle 10 times. T able 4: Mobile Test Cases 2.2.5 Cluster KPI References See appendix in the end of the document. 2.2.6 Drive-test UE Distribution – Cluster Level In order to reduce the number of UEs to cover all measurements requested by the AMX the distribution below is showed. Additionally, this array avoids too much load on the sites during the tests that can jeopardize the quality of the system.
  17. GUIDELINES Version Status RF Optimization Guideline for AMX 3G Rollout 1 August, 27th 2007 Consulting and System Integrations Revised by: Danilo Cabral Raj Sandhu, Allan Bispo and Daniel Platero Cluster Level Stationary Testing Specific Area DT Drive #1 Drive #2 Coverage, Voice and Ping, Multi-RAB and Services ISHO and RAU Testing Video and PS Rel99 Tests HSDPA Tests AMR Continuous Call AMR Short Call (3G to UE1 DL and UL PS Rel99 DL PS Rel99 (Dual Mode) PSTN) PS Rel 99 PS Rel 99 RTT Voice CSSR ---------------------------------------- ISHO Succ Rate (3G to 2G) DL WCDMA User Throughput Voice CST AMR Voice CSSR during PS 64/64 Call ISHO Succ Rate (2G to 3G) UE1 KPIs PS RAB Establishment Succ Voice Drop Rate PS 64/64 CSSR during AMR Voice Call ( 4 hours) PS RAB Drop Voice BLER (2 hrs per point) UE2 HSDPA Datacard HSDPA DL HSDPA - - (Cat 6) DL HSDPA User PS HSPDA RTT Throughput UE2 KPIs - - (1/2 hr per point) DL HSUPA User Throughput SMS / WAP / MMS and PS Continuous Call (Dual UE3 Idle Mode UL PS Rel99 PS Rel 99 Multi-RAB Mode) PS Rel 99 SMS Success Rate SMS Delivery Time WAP Failure Rate RAU Time (RA1 to RA2) DL WCDMA User Throughput WAP Session Estab Time RAU Time (RA2 to RA1) UE3 KPIs Coverage Verification PS RAB Establishment Succ MMS Success Rate ( 4 hours) PS RAB Drop MMS Delivery Time (2 hrs per point) UE4 Video Short Call (3g to 3G) HSDPA Multi-RAB - - HSDPA UE (Cat 12) B party with auto-answering CS Video CSSR AMR Voice CSSR during HSPA Call CS Video CS Elapsed Time HSPA CSSR during AMR Voice Call UE4 KPIs - - CS Video Call Drop Rate (2 hrs per point) CS Video Call BLER # UE's 4 1 3 3 Figure 6: Drive-test UE Distribution 2.2.7 Data Processing, Analysis and Report Collected data from each test case shall be processed and KPIs generated. The collected data and the post-processing report must be delivered together to the analysis team. Test cases that fail to meet its target value are then analyzed in more detail to find out its failure causes. Based on the detailed analysis, change request shall be generated. Otherwise, if the cluster achieved all targets, the results shall be documented in the RF Cluster Acceptance Report, and delivered for customer approval. An optimized procedure to post-process the drive-test data is still under discussion, and this document will be updated after the decision about this issue. 2.2.8 Change Request The change request shall be carried out according to the process below:
  18. GUIDELINES Version Status RF Optimization Guideline for AMX 3G Rollout 1 August, 27th 2007 Consulting and System Integrations Revised by: Danilo Cabral Raj Sandhu, Allan Bispo and Daniel Platero Y Generate Final Acceptance KPIs Passed R eport N D etail Analysis Submit Change Request for Internal Review Perform Changes D ocument changes in master change request database Initiate redrive to evaluate changes Generate KPIs Figure 7: Change Request Process Template for Change Request has not been created at this time. Master Database to track the change request has not been created at this time. 2.3 Acceptance Phase The acceptance phase shall commence once the entire cluster KPIs have been reached. The acceptance phase shall involve the process of generating the RF Cluster Acceptance Report , submitting this report for internal review and then getting the reported approved by America Movil LatAm. After that the project level tests can be started. These tests will be detailed in the next chapter. The RF Cluster Acceptance Report template is presented below: Template on the intranet site
  19. GUIDELINES Version Status RF Optimization Guideline for AMX 3G Rollout 1 August, 27th 2007 Consulting and System Integrations Revised by: Danilo Cabral Raj Sandhu, Allan Bispo and Daniel Platero 3. RF PROJECT ACCEPTANCE The Project Acceptance Report is the RF document that will allow America Movil LatAm to grant the Provisional Acceptance (PAC) to Nokia Siemens Networks. In small cities where a site division in clusters is not necessary, it will be possible to go direct to the Project Acceptance Tests, taking in consideration all requisites described in the Cluster Acceptance Tests. This means, in case of project tests only, all activities in the preparation phase and optimization phase must be done considering the differences related to target KPI values and procedure tests between cluster and project level testing. The figure below gives an overview of the RF Project Acceptance process. Preparation Preparation Stage for Project Phase Acceptance Testing Perform Stationary Testing Perform IRAT Testing* Perform RAU Testing Perform Perform Mobile Testing Optimization Phase Data Processing, Analysis & Report Network Optimization & Change Request N KPIs Achieved Y RF Project Acceptance Acceptance Phase Submit Report to AMX 3G Network Launch * only in the 3G/2G networks border Figure 8: RF Project Acceptance The RF project acceptance process also can be grouped into 3 main sections, which are: the preparation phase, optimization phase and the acceptance phase.
ADSENSE
ADSENSE

CÓ THỂ BẠN MUỐN DOWNLOAD

 

Đồng bộ tài khoản
2=>2