UTRAN Optimisation Process when Introducing HSDPA

Document number: Document issue: Document status: Date: UMT/IRC/APP/019971 01.01 / EN Draft 18/Jul/2006

Confidential document - Not to be circulated outside Nortel

Copyright© 2004 Nortel Networks, All Rights Reserved Printed in France NORTEL CONFIDENTIAL The information contained in this document is the property of Nortel Networks. Except as specifically authorized in writing by Nortel Networks, the holder of this document shall keep the information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties and use same for evaluation, operation and maintenance purposes only. The content of this document is provided for information purposes only and is subject to modification. It does not constitute any representation or warranty from Nortel Networks as to the content or accuracy of the information contained herein, including but not limited to the suitability and performances of the product or its intended application. This is the Way. This is Nortel, Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks. All other trademarks are the property of their owners.

UTRAN Optimisation Process when Introducing HSDPA

PUBLICATION HISTORY
18/JUL/2006
Issue 01.01 / EN, Draft Creation

Nortel confidential

UMT/IRC/APP/019971

01.01 / EN

Draft

18/Jul/2006

Page 2/25

................. 4.................2.......................... 4............................4..................3 FEATURES AND PARAMETER ALIGNMENT WORKSHOPS ................................................2... QUALITY BENCHMARK.............3... 6.......................................................................3 PROJECT PROCESSES .................3 4......1......................................3 3...................................................................4.......................................................................................................................................................................................3..2.......................3 MEASUREMENT AND ACCEPTANCE PROCESS ..........................................................3 4........................................................................................3 5.......1 Deviations and Exclusions ....................... RF DESIGN AUDIT WORKSHOPS AND STUDIES................................................................... HSDPA CAPACITY AND RF QUALITY ASSESSMENT.......3 2........3 REFERENCE DOCUMENTS.........................................................................................5.............3 4......... INTRODUCTION .........3 HSDPA TROUBLE SHOOTING AND LOCAL OPTIMISATION .................................................................................................... 4........................................... 2..................................................................................................... 2........................3 AUDIENCE FOR THIS DOCUMENT .......... 4.........6..3 6..................................... APPLICABLE DOCUMENTS ........................................................................ PILOT PHASE...................................................................... OVERVIEW ............ 1........ 7...........................3 PERFORMANCE BENCHMARKS ..................3 RF OPTIMISATION ................1.................3 1.......................................... PROJECT PREPARATION.................................3 4.............................................................................................................................................................................................3 RELATED DOCUMENTS............................................................................................................. OBJECT ....................................................................................................................3 PLANNING...............................3 PROJECT DATABASE .................. 1.......3 SCOPE OF THIS DOCUMENT .........7.....................6........ 6......................01 / EN Draft 18/Jul/2006 Page 3/25 ..........................2.............1........... 4........................................................3 3............................................................... PROJECT PLAN ..............................1................ 6........UTRAN Optimisation Process when Introducing HSDPA CONTENTS 1..................................................3 Nortel confidential UMT/IRC/APP/019971 01...............................................3 OPTIMISATION PROCESS ...3 MONITORING WORKSHOPS ................1..................................................................3.............. 6.....................................

As any process.2. AUDIENCE FOR THIS DOCUMENT Project and Account Teams.1. 1. Time necessary to perform the checks (reduced mobility and speed). INTRODUCTION OBJECT This document aims at describing the engineering tasks that are executed before and after the introduction of the HSDPA functionality in a live UMTS network.2 RF Optimisation”). a deeper optimisation activity will need to be scheduled. resources. Optimisation and Engineering Teams.UTRAN Optimisation Process when Introducing HSDPA 1. Potentially higher impact of the load in the performance. Refer to [A1] for more details on this specific step. it is assumed that the network to be “upgraded” has already been optimised and therefore the call performance and the radio coverage and interference are at correct levels. The goal is to end up with an UMTS network ready to absorb the future HSDPA traffic controlling the interferences that a WCDMA system working close to a radio load of 100% will generate. Nortel confidential UMT/IRC/APP/019971 01. Thus. tools…). 1. The optimisation intends to limit or eliminate the impact that the activation of such feature can have on the existing network. SCOPE OF THIS DOCUMENT This document gives a project level view of the different optimisation tasks and provides some examples of the performance indicators that have been used during these activities. this document intends to recommend a way to achieve the best results but it needs to be adapted accordingly specially when the customer impose specific metrics to monitor or report. As the activity is carried out in a live network. the optimisation one has to be adapted to the requirements imposed by the customer and the different constraints to be managed (environment. 1. time. The intention of this document is not to describe in detail the RF Optimisation process to be applied locally when necessary (as described in chapter ”6. Otherwise. The following document concerns sites with outdoor coverage but it could be adapted to the indoor one taking into account some specific constraints: • • • Tracing capabilities inside a building.01 / EN Draft 18/Jul/2006 Page 4/25 .3. budget.

REFERENCE DOCUMENTS [R1] [R2] UMT/IRC/DD/0011 UMT/IRC/APP/014654 UTRAN Parameters User Guide HSDPA Engineering Guide Nortel confidential UMT/IRC/APP/019971 01. 2.1.01 / EN Draft 18/Jul/2006 Page 5/25 . RELATED DOCUMENTS APPLICABLE DOCUMENTS [A1] [A2] [A3] UMT/IRC/APP/019972 UMT/IRC/APP/018901 UMT/IRC/APP/018947 UTRAN Optimisation Process HSDPA Introduction Methodology User Guide HSDPA Engineering Handbook 2.UTRAN Optimisation Process when Introducing HSDPA 2.2.

can be obviated if the capacity needs related to the activation of HSDPA have already been addressed by the customer and that there is enough confidence on the current RF profile of the network (network well RF optimised). The RF optimisation. Therefore. Nortel confidential UMT/IRC/APP/019971 01.01 / EN Draft 18/Jul/2006 Page 6/25 . the activation of HSDPA will not degrade the R99 users. If there is a requirement to fully drive test the area before the activation of HSDPA (expensive option). it is not necessary to assess the network radio conditions during the HSDPA assessment. the RF optimisation levels of the network. Troubleshooting and fine-tuning of any remaining issue at the cluster. can have a different priority with regards to the “frequency shared” scenario. it can be possible to obviate the first steps and go directly to the last one. the HSDPA activation will have little impact on current R99 users. • • • 1 If HSDPA traffic is separated from R99 traffic. 2. This process is applied in a in-service network: OCNS will not be used. The process is applied in a cluster per cluster basis following the availability of the HSDPA sites after the I&C operation sometimes called “HSDPA refresh”. with the consequent risk associated: • HSDPA assessment. HSDPA activation once the optimisation is finished using the parameter settings driven from the experimentation in the Golden Cluster. 3. both R99 and HSDPA. If the network has already correct levels of RF control to deal with HSDPA. while still needed. Finally. 4. Optimisation of the RF coverage of any cell that could interfere once HSDPA is activated. Assessment of the impact of the HSDPA activation considering the current and future load and traffic in each cell. the HSDPA deployment strategy (shared/dedicated1 frequency) and the customer requirements (set of target KPIs). the HSDPA assessment methodology uses data provided by Nortel’s CTg (Call Tracing). Depending on the project scope.UTRAN Optimisation Process when Introducing HSDPA 3. The proposed process consists in: 1. In case of equipment swaps. some of the steps above can be skipped. OVERVIEW The objective of the RF optimisation is to control the coverage of the existing cells and reduce the overlaps guaranteeing the service levels and offering a good quality of service for all the users. those data cannot be available except in the case the former supplier had an equivalent feature (Nortel’s tools might be adapted to other data formats).

the optimization.01 / EN Draft 18/Jul/2006 Page 7/25 . Therefore. QUALITY BENCHMARK If the operator intends to verify the quality of the achieved optimisation by comparing the performance obtained by the R99 users before and after the “HSDPA refresh”. The assessment can also be proposed as an independent service if no optimisation or benchmarking is required. Poorly optimised networks will increase the workload during the project and add risk and pressure during any quality benchmark. Nortel’s experience in HSDPA fine tuning in different trial networks will help in determining quickly the good setting for the customer clients (cf.2).UTRAN Optimisation Process when Introducing HSDPA The impact assessment of the introduction of HSDPA is fully described in “HSDPA Introduction Methodology User Guide” [A2]. This document only provides a highlevel description of this important step and includes it in the overall optimisation project. This is to allow to work on the open performance issues. The first benchmark (“before”) is to be done before the start of the RF optimisation (06.1. the deployment. The performance assessment before and after the HSDPA introduction or refresh is done through monitored metrics (counter-based and/or drive-test-based) at cell and cluster levels. and the monitoring of HSDPA including useful guidelines on parameter tuning. it is important to avoid any site densification or major hardware upgrade in any cluster that is being “refreshed” and which has not been accepted by the customer (exit performance benchmark). the operator can request Nortel to monitor the “refreshed” site just after the installation of the new HSDPA hardware (even if HSDPA is not activated just afterwards). In order to ease the process and be able to correctly compare the performance before and after the “refresh”. The “HSDPA Engineering Handbook” [A3] provides the necessary keys for the study. 3. [R1]). Those settings are then to be propagated to the entire network. It is proposed to optimise and determine the HSDPA generic parameters in a Golden Cluster through extensive testing. The goal is to be sure that the I&C operation has not impacted the UMTS service on the NodeB. Nortel confidential UMT/IRC/APP/019971 01. In some cases. The duration of the project can be impacted if an important number of sites need aerial optimisation because a poor RF optimisation. The second benchmark (“after”) will be done after the fine tuning of the cluster. It is assumed that the network to be upgraded to HSDPA has already been optimised and therefore the call performance and the radio coverage and interference are at correct levels. a benchmark campaign can be proposed. the benchmarks need to be done under the same conditions. The assignment of priorities to the clusters during the roll out can include considerations on how urgent is to add new sites an area.

These steps should be part of the overall project plan and be planned appropriately in advance of the operational activities. If during this step. there is no need to define the drive testing processes or the protocol to deal with antenna sub-contractors. This phase of the project will help in creating the project processes (aligning them with the customer needs and constraints) and in defining the detailed project plan. Indeed. The following workshops need to be held before starting any operational activity. if the process only requires performance monitoring at counter level or if there is no budgeted antenna optimisation. important issues are discovered. Nortel confidential UMT/IRC/APP/019971 01. this phase permits the team to verify that the design assumptions used by the operator will not impeach that goal. the exclusion zone definition or the measurement methodology should be reviewed.UTRAN Optimisation Process when Introducing HSDPA 4. The best trade off between capacity. PROJECT PREPARATION As in any complex project. The following chapter aims at describing some important steps that need to be addressed in order to prepare the optimization activity. processes and agreements that follow each workshop and preparation phase must be correctly documented. The final objective is to diminish the project risks. Nortel will assure the transfer of the necessary information between the design and optimisation teams. RF DESIGN AUDIT WORKSHOPS AND STUDIES The RF Design Audit allows the optimisation team to be aware of all design assumptions that could impact the service performance of the network. design tools … This phase can be forfeited if Nortel has had the responsibility of the network design.1. simulated RF footprints. As the optimisation service has to achieve contractually challenging performance indicators. routes. coverage and quality of coverage is what needs to be discussed at this stage. Obviously. the preparation phase is key for the success and the efficiency of the work to be done by the on-the-field teams. the KPI targets. Each one of the outcomes. the optimisation team also begins to know the network that need to be optimised: sites. During this phase. the extent and contents of each of the following workshops and project processes will depend on the customer quality requirements and the operational tasks that need to be executed.01 / EN Draft 18/Jul/2006 Page 8/25 . 4.

depending on the type of antenna. feeders. couplers. reserved power. If necessary. publication of the changes. Use that plan to influence roll-out and I&C plans. TX power and the study of the HSDPA evolution and strategy (number of carriers. • • • • • • • • • Acceptance routes are generally a subset of the optimisation ones. points of reference for the NodeB power setting…). margins/methodology used to guarantee indoor coverage from outdoor sites… Define the priorities to respect when a compromise is needed between indoor coverage and pilot contention.UTRAN Optimisation Process when Introducing HSDPA Other items to consider are: • • • Review Nortel’s HSDPA design assumptions and contrasted them with the customer’s ones in order to fix a baseline for the RF design review activity. Flag the indoor coverage requirements: indoor sites. traffic per service and per area. It is recommended to have at least 90% of the sites available.). propagation models…) has to be guaranteed during the whole duration of the project. Determine the optimisation clusters and the routes for the optimisation and acceptance drive tests2. This will help in homogenising the optimisation choices. densification) and marketing (traffic. Flag Hot Spots and marketing-driven “Golden areas”. OMC .01 / EN Draft 18/Jul/2006 Page 9/25 . Site dossiers (pictures. Review the RF design in each region (type of service per area. Define the Golden Clusters of the network. RF Configuration Audit. Fine tune the plan with the rest of the operational teams involved (I&C. clutter documentation and definition). Nortel confidential 2 UMT/IRC/APP/019971 01. The acceptance methodology will need to consider the cases of not fully completed clusters and late-sites. CCCH powers. Access to cell planning tools and databases (DTMs. reporting …) Try to define rules of thumb on the way the tilts and azimuth changes have to be decided. installation details …) must be available to the optimisation teams. plan a training period and a validation of the customer planning tools if they are not correctly known by Nortel. Gather the sites aerial constraints (antenna set. A special attention is needed during the definition of the CPICH power. A cluster has to be coherent from a RF coverage point of view.. Set the minimum percentage of sites needed in order to launch the optimisation of a cluster. site height and distance to clear.. Prioritise the clusters following schedule (accessibility. Understand operator’s process in terms of network design and configuration (validation of the changes. HSDPA ready) constraints. access…) in order to anticipate the solutions available if problems arise. It is recommended to use a common RF planning tool between the customer and Nortel’s teams. The optimisation routes pretend to cover comprehensively the cluster area.

those which the optimisation manager has to approve and those that need to be sanctioned by the customer. SHO setting. The methodology must be adapted to the project plan. Define carefully the metrics used during the quality benchmarks including the averaging procedures and the minimum sample size to make them significant. it can evolve following changes in coverage. Analyse the chosen settings. Define conjointly formulas which could match the metrics the customer is used to manage and report. Call Tracing capabilities must be fully dedicated to the optimisation team. The limitations of that feature must be known and respected. Identify those that could be tuned during the optimisation Put special attention to the mobility features: neighbour plan.UTRAN Optimisation Process when Introducing HSDPA 4. parameters and Gather the main RF configuration parameters. conjointly with the customer.e.01 / EN Draft 18/Jul/2006 Page 10/25 . MONITORING WORKSHOPS • • • Explain Nortel’s Monitoring process and tools.2.3. Nortel confidential • • • • • • UMT/IRC/APP/019971 01. • 4. reporting …). Determine the hand-over of the supervision responsibility between Nortel and the operator once each site has been swapped / integrated / optimised / accepted. Recommend reporting and supervision methodology during the “refresh” period and during the hours that follow the “refresh” of each site (“worst-cell list”). Prepare. Access to cell Performance Management server has to be guaranteed during the whole duration of the project. Align and homogenise (Configuration Audit). i. Recommend reporting methodology during the project. the parameter setting within the network • • • Define lists with parameters and setting ranges that can be set locally by the optimisation engineer without approval. Alarm management and troubleshooting must be guaranteed during the optimisation process. Try to define rules of thumb on the way the parameters need to be tuned.. a preliminary test plan for the Golden Cluster or Pilot areas indicating the features and parameters to test. IRM… Understand operator’s process in terms of network design and configuration (validation of the changes. FEATURES AND PARAMETER ALIGNMENT WORKSHOPS • • Describe Nortel’s UTRAN features and associated recommended values. publication of the changes. and recommended typical metric targets. list of activated features or traffic.

definition and follow-up of the contractual deliverables. Configuration. Customer …. The following are critical operational processes that need to be agreed between the optimisation manager and the managers of the involved organisations: NOC. together with the customer and with each third party company involved in the project. The report’s usefulness. it is mandatory to sign Non Disclosure Agreements (NDA) with all the involved parties. It is also necessary to prepare procedures to change or complete the process during the project execution (Change Control system). partners. A heavy reporting can delay the work without bringing enough benefits. They need to be clearly defined and accepted before starting any operation in the network once the contract has been granted. Internally within the optimisation team but also externally. This process needs to cover the approval (deliverable) of the change by the customer (after control). timeliness and workload need to be balanced. reporting metrics (both internal to the project and external to the customer) and the description of the contractual deliverables. Identification of the stakeholders. Datafill / Configuration Change Request Process. engineering. service levels to be respected. project management. Their SLA need to be clearly defined and respected in order to honour the planning and the efficiency of the on-thefield teams: • • • Trouble Ticket Process (both at project and at Product Support (GPS) levels). Aerial Configuration Change Process. at enough level of extent.4. • • Nortel confidential UMT/IRC/APP/019971 01. The sign-off reports (deliverables) for each step of the project phases need to contain enough relevant information without impacting the project progress. the impact of “out-of-the-process” scenarii and conduct “what-if” analysis (Risk Analysis). deliverable reception sign-off. Supervision. If confidential information is exchanged with the customer and between partners and subcontractors. Communication Plan.UTRAN Optimisation Process when Introducing HSDPA 4. accountabilities (escalation / approval). the communication path to the subcontractor and the managing of issues and performance metrics. Define the operator’s needs in terms of progress reporting (including quality metrics to be provided). follow-up of the penalties. JCO process. Partners. Contract Management Process. PROJECT PROCESSES The processes associated with the optimisation project need to be agreed by all stakeholders: customer. invoicing and formal final acceptance. in each case. The process description should include: working templates.01 / EN Draft 18/Jul/2006 Page 11/25 . This process is to be defined. with all the project stakeholders. Study.

Nortel confidential UMT/IRC/APP/019971 01. In addition. it is likely that. big optimisation projects can need a large headcount which needs to be served accordingly. when the site is brought into the live network. chapter 4. Therefore.01 / EN Draft 18/Jul/2006 Page 12/25 . alarm status … It is advisable to think in the office constraints the project team will require: office footprint. service templates. The following are internal processes used within the optimisation team. it is advisable to make available to the optimisation team a direct link to the supervision reports (trouble tickets) or the Fault Management system of the UTRAN. Data Management process (and related database • • • • Optimisation Equipment Management Process (and related database specification). IT support… Indeed. Optimisation Training and Quality Process (of the team involved in the optimisation project). The optimisation teams need to be aware and eventually provide feedback on the site Integration and Commissioning (I&C) Process. Measurement and Acceptance Process (cf. the management of the RF configuration parameters at the NOC (Network Operations Center).UTRAN Optimisation Process when Introducing HSDPA It is recommended to establish direct communication links between UTRAN. is vital to feed the optimisation databases and plan the steps that precede the live testing: neighbouring relationships. They can include customer requirements when needed (for example in the communication path) and can be used as a quality assurance procedures: • Drive Test Procedures and Checklists: trace mobiles (hardware and software). That training can cover both technical and procedural topics. desks. radio chain. it is important to plan those activities accordingly and agree on their scope and duration in advance. That will help in crosschecking any important degradation observed in the field and the status of the opened tickets. networking. The nature and results of the tests performed by the “commissioners” are of vital importance to assess the readiness of the site to become part of an “to-optimise-ready” cluster. The reason for this is two fold: the optimisation team has to be informed on any activity or event that affects performance and also be able to contact the adequate peers in order to debug any issue. Core Network and Service platforms.6 below for details). PCs. by the final phases of the optimisation project. They have to be primarily agreed between the optimisation manager and the partners and subcontractors controlled by her. averaging. frequencies in use. calibration procedures. In order to increase the reactivity and facilitate the communication. CORE and Service Platform teams. Finally. the customer requires knowledge transfer sessions (KTS) including formal or informal (on-the-job) training (OJT). binning. scanner configuration… Optimisation specification).

UTRAN Optimisation Process when Introducing HSDPA 4. if using external antennas. The exit criteria has to be defined properly and in very detailed manner including all the exclusions allowed. Site issues. coherence has to exist between the contractual requirements in terms of optimisation and what is possible to achieve in a dynamic environment as WCDMA. Equipment tracking. The work involved and the test conditions that need to be guaranteed (features to be activated or not. budget and schedule of the optimisation project. If attenuation boxes are used. Nortel confidential UMT/IRC/APP/019971 01. workload. changes in traffic conditions…) have to be well understood during the definition of the scope. delays. they need to be calibrated as well. cost and customer satisfaction (assuring him that the optimisation done is the best we could deliver). The acceptance methodology will probably need to include ways to manage the acceptance of a “not fully optimised cluster” (exclusions to be defined during the benchmark) and the acceptance of a “late-site” (need of a “light” procedure. escalated issues… Work Orders and implementation delays. The optimisation teams need to trust the collected data.6. 4. Implemented/Planed Changes. among other information: • • • • • • • • Site configuration. UEs. A special attention must be brought to the radio chain of the drive test car.01 / EN Draft 18/Jul/2006 Page 13/25 .5. Reporting templates. PROJECT DATABASE It is mandatory for a correct follow up of all the operations to have a common and unique project information system (Project Database) which should include. statistical methods) will be presented and consolidated with the customer. radio paths…) and methodology (exclusions. In any case. for both the test handset and the scanner. The acceptance methodology is a key document that needs to be studied carefully and that will define the final contractual deliverable and influence the whole optimisation and verification steps. The attenuation of all elements must be known and proper calibration has to be periodically done in order to guarantee the exactness of the recovered data. downtimes. This process needs to be linked to the “Drive Test Procedures” document and known by the whole data acquisition team. It is mandatory to use the same radio elements. It is important to find the good trade off between optimisation efectiveness. Updated operations plan. Metrics: performance KPI. MEASUREMENT AND ACCEPTANCE PROCESS Measurement process (tools.

Inability to set the correct antenna tilt / azimuth: GSM/UMTS antenna… Inability to optimise further due to limitations on site profile: street furniture… Non ideal antenna heights due to site or planning constraints Sites missing: not-contracted sites. equipment upgrade. If the data collection activity is outsourced. during that period. Bound the accountability to the areas of the network controlled by Nortel. Clearly take into account the coverage-related exclusion zones and define the methods to not count the samples recorded in those zones. it would be necessary to determine the precise configuration of the whole measurement chain (including attenuators). Include exception management when the team faces issues with the mobiles or the Core Network. in order to fairly compare results. it is mandatory to perform all the measurement campaigns on the same routes. radio chain. equipment swap…). • • If testing under simulated load or simulated indoor conditions is requested. car.UTRAN Optimisation Process when Introducing HSDPA The KPI measurement methodology has to be very clearly described: • • The KPIs need to be calculated using the information available in the collected traces: use only objective formulas and avoid difficult post-processing. Should the customer decide to perform any changes or modifications on those nodes. it is important to be able to recover the reports and traces and be able to post-process them with Nortel tools. no change occurs in the core network.01 / EN Draft 18/Jul/2006 Page 14/25 . Determine the minimum number of samples (minimum number of hours driven and calls performed) and how the averaging must be performed (at cluster and city levels). In order to be able to compare correctly the performance before and after.6. server…) and the same post-processing tools. Nortel would expect to be made aware and commonly re-examine with her the potential impacts on the overall methodology and targets. with the same equipment (mobile. not-radiating sites… Nortel confidential UMT/IRC/APP/019971 01. 4. The results need to have enough statistical value. It is important to verify the format needs both of the optimisation teams and the support teams (GPS).1 DEVIATIONS AND EXCLUSIONS Deviations and exclusions will be triggered where it was not possible to implement the appropriate optimisation recommendations: • • • • • • Derived from the RF Design Audit When the built network does not comply with the design rules in that area. transmission network or services platform. it is assumed that. antenna. next-phase sites. If any comparative performance benchmark is necessary during the optimisation process (feature analysis.

The contractual targets are lowered. Nortel confidential UMT/IRC/APP/019971 01. The contractual targets are kept. All the resources.…) and hardware (mobiles. 4. This will be described in the “KPI Measurement methodology” document.01 / EN Draft 18/Jul/2006 Page 15/25 . desks …) elements that are needed by the optimisation team must be identified and available before starting the optimisation phases. The logistics has to be managed. The following aspects should be covered: • • • • Phases Activities Timelines Interdependencies The project plan has to include details on the resource plan (headcount. must be on site at the planned moment. databases. and defining consecutive concessions on the KPI. scanners. both human and material. the RF design and neighbouring settings of the surrounding region might be revisited. It should be agreed prior to service commencement and include an escalation process for non-agreement on non-compliant design issues. Where non-compliance issues exist: • Nortel may propose new performance indicators for the area (cell/group of cells/subset of cells) affected by the minor non-compliance.UTRAN Optimisation Process when Introducing HSDPA This process will include the development and agreement of situations for triggering those exclusions and deviations. skills…) and indicate when those resources are available to the project. PCs. • • After a site or area.7. PROJECT PLAN Preliminary project plan will be finalised once all the processes. KPI definitions. cars. Nortel may propose to enlarge the exclusion zone where major issues exists or if they cover a large area. exit criteria and communication channels have been discussed and agreed. Nortel may exclude the number of failures affecting the KPI due to this situation. The performance indicators will be reported but they will not be bound to the contractual targets. All the necessary software (tools.

carriers. very different between them.01 / EN Draft 18/Jul/2006 Page 16/25 . Optimise and fine tune generic HSDPA parameters to be applied network wide. Validate the acceptance protocol and the list of metrics (counter-based and/or drive-test-based) Define a test plan for further testing. HSDPA Optimisation Process. Power. SHO thresholds… Nortel confidential UMT/IRC/APP/019971 01. resources usage (CEM. PAs. The main objectives of this phase are: • • • • • • • • • • Assess the impact of HSDPA introduction with the current network settings Analyse the operator’s strategy and the capacity bottlenecks. well known and optimised environment. cluster characteristics… Parameters audit: CCCH power settings. E1s. It is recommended to define more than one Golden Cluster in the network (but not too many) if several. quality target. PILOT PHASE The Pilot or Golden Cluster help in defining the general recommended parameter settings and to show the good performance obtained with them in a controlled. Recommend generic parameter changes on already activated features. E1)… RF quality (Call Trace): distribution of CPICH Ec/No. During this phase the following is validated: • • • I&C process. RRM thresholds and timers. sectors per user. Recommend the activation of new features. ASET update rate. Monitoring Process. features enabled. Tune/Improve/Simplify the operational processes. radio environments need deep testing. The analysis for the HSDPA assessment includes data coming from: • • • • • Performance monitoring: CS/PS traffic split. The Pilot size has to be comparable to the typical cluster size used during the HSDPA refresh project. Use the cluster for any advance study during the project. Identify those parameters that potentially need local optimisation and recommend methodology to get the optimal value. CEMs mix… Environment factors: indoor/outdoor coverage. Code. RSCP. DL Transmitted Code Power … BTS Hardware: sectors.UTRAN Optimisation Process when Introducing HSDPA 5. power settings.

resource reservation. The characteristics of this functionality make the required analysis to be two-fold: Nortel confidential UMT/IRC/APP/019971 01. The HSDPA Introduction assessment is only applicable in areas with enough R99 traffic. This chapter describes the recommended procedure for collecting drive-test data and be able to optimise the RF profile of the network through antenna system optimisation. it is recommended that when working on 2 clusters in parallel. 3G2G). Even if the counter monitoring is a key part of the process. • • • • OBJECTIVES The objective of this phase is to estimate the impact of the activation of HSDPA capability in the selected cluster.01 / EN Draft 18/Jul/2006 Page 17/25 . Generic HSDPA parameters will be optimised during at least 5 weeks in a Golden Cluster (at least 1 per region). acceptance protocol agreed … Clusters have been defined. measurement methodology agreed. OPTIMISATION PROCESS The verification or optimisation process can be based on just drive-test-based performance indicators or on both counter-based and drive-test-based indicators. features activation plan. CTg and OAM limitations need to be respected.UTRAN Optimisation Process when Introducing HSDPA • Operator’s strategy: priorities. 6. mobility strategy (interfreq. HSDPA service definition and applications… 6. The monitoring is mandatory if there are counter-based metrics in the acceptance procedure. A counter-based monitoring system has to be implemented in parallel in order to follow the evolution of the optimisation actions and the swap operation. HSDPA CAPACITY AND RF QUALITY ASSESSMENT PREREQUISITES • All the preparation steps need to have been completed: processes definition.1. Due to the CTg limitations. RF optimisation process defined. It is necessary then to adapt the process to the acceptance requirements keeping in mind that the drive test option is expensive but their results are better controlled and can be better analysed. some performance indicators and specific optimisation studies can only be obtained with drive tests. each one belong to a different RNC. mobile mix.

Launch of Call Trace (CTg) on the selected sites in order to collect detailed information regarding the radio performance of the real users on the area. sources. Nortel confidential UMT/IRC/APP/019971 01. common to all operators. Typical recommended cluster size is of around 80 sites. This methodology has already been applied in live HSDPA trials.01 / EN Draft 18/Jul/2006 Page 18/25 . Event-Triggering functionality activated …). Nortel has developed and built a complete methodology (“HSDPA Introduction Methodology User Guide” [A2]). it is recommended to collect at least 6 busy hours do Call Trace per site. more expensive. to have enough statistically significant data. Determine the capacity bottlenecks and areas which need RF Optimisation (polluted or weak covered areas). The methodology and results remain the same but the input data is coming from other. by using HSDPA channels. increase the radio load of the cell up to 100%. CTg analysis is to be performed in 40-50 sites belonging to each cluster in order to get enough samples and not delay the overall process. The complete methodology will be explained during the workshops that will precede the operational activities of the HSDPA refresh. Indeed. TASKS • • • • Collection of performance and capacity counters (sites of the cluster) Identification of the sites with highest PS traffic and those potentially more impacted by the HSDPA activation. Assessment of the impact in terms of radio interference of the users that. In order to address this important objective. IMPORTANT: if the collection of a representative amount of CTg data is not possible (recently swapped UTRAN. it is recommended to launch a drive test campaign in order to assess the RF quality of the network. Both assessments are needed to grant the successful activation of the HSDPA functionalities network wide.UTRAN Optimisation Process when Introducing HSDPA • • Assessment of the need to increase the capacity of the BTS to accommodate the HSDPA traffic.

3G2G). carriers. includes data coming from: • • • • • • Performance monitoring: CS/PS traffic split. mobility strategy (interfreq. features enabled. DL Transmitted Code Power … BTS Hardware: sectors.Codes . Code. cluster characteristics… Parameters audit: CCCH power settings. ASET update rate. resources usage (CEM.Power . power settings.PA addition .Neighbours … HSDPA Implementation The analysis phase.UTRAN Optimisation Process when Introducing HSDPA The overall procedures are shown in the following picture: Network Data Collection • • • • • Parameters Perf monitoring Call Profile RF Quality Features Current Analysis • • • • • • • Codes Power RF Simus CEM Iub RF Quality … Re-Engineering Activities . List of cells that require a specific parameter setting. features activation plan. mobile mix. quality target. resource reservation. Power. E1)… RF quality (Call Trace): distribution of CPICH Ec/No. HSDPA service definition and applications… OUTPUTS • • • List of areas that require RF Optimisation.Design … R99 & HSDPA Network Optimization Customer Strategy • Call profile • Data Subs • Forecast services Forecasted Analysis • • • • • • • • Codes Power RF Simus UTRAN Dim CEM Iub RF … Re-Optimization Activities . RSCP. Recommendations on hardware upgrades considering the current and future HSDPA and R99 traffic. SHO thresholds… Operator’s strategy: priorities. CEMs mix… Environment factors: indoor/outdoor coverage. Nortel confidential UMT/IRC/APP/019971 01.New Freq . partly executed during the preparation and pilot phases.01 / EN Draft 18/Jul/2006 Page 19/25 . PAs. E1s. RRM thresholds and timers. sectors per user.

Otherwise a complete RF survey through drive testing might be necessary. The objective of the RF optimisation will be to limit the overlap or SHO areas. when the carrier (frequency) is shared between R99 and HSDPA users. Performance report. specially in areas where is required high indoor penetration and the design options are limited.2. Interference will increase and therefore the performance can be degraded. Aerial optimisation decisions will be backed by simulation studies and agreed with the customer. Call performance will be checked before and after the implementation of the suggested changes. Nortel confidential UMT/IRC/APP/019971 01. it is not necessary to drive and test the whole cluster. It will be necessary to reach agreements on trade offs associated with this optimisation phase. The Nortel standard process for RF optimisation are to be used. Only the areas identified as problematic will be optimised.01 / EN Draft 18/Jul/2006 Page 20/25 . OUTPUTS • • List of changes. RF OPTIMISATION PREREQUISITES • • The areas to optimise have been identified. OBJECTIVES Thanks to the previous step in the process. TASKS Data for the optimisation decisions will be collected through several runs of drive tests using WDCMA scanners and UMTS mobiles.UTRAN Optimisation Process when Introducing HSDPA 6. The services to be tested will be bound to two. Note that all the RF optimisation activities have to have finished before going to the next step in the process. RF Optimisation process (subset of the generic one provided for roll-out) has been defined. It is necessary to improve the radio coverage of the problematic area as the activation of the HSDPA functionality will increase the radio load of each site. As the next step is the activation of the HSDPA functionality. increase the dominance of single SC and reduce the SPU. This step in the process is specially important and its potential impact higher.

TASKS The “HSDPA Engineering Handbook” [A3] provides the necessary keys for the study. 6. Nortel confidential UMT/IRC/APP/019971 01. using WDCMA scanners and UMTS and HSDPA mobiles. and the monitoring of HSDPA including useful guidelines on parameter tuning.01 / EN Draft 18/Jul/2006 Page 21/25 . most of them in static mode. tested and optimised in the Golden Clusters have been applied. UMTS and HSDPA parameters can be tuned locally at this stage in order to boost the user performance in the area. some aerial optimisation can still be necessary at this stage. The focus will be given to the parameter optimisation tasks.3. OBJECTIVES Once the cluster has been optimised and HSDPA activated. However. Data for the optimisation decisions will be collected through several runs of tests. including the HSDPA ones. the performance and quality on those areas will be highly degraded once HSDPA users start using this functionality. HSDPA TROUBLE SHOOTING AND LOCAL OPTIMISATION PREREQUISITES • • • RF Optimisation of the cluster is finished The parameter settings. Note that the order of the above pre-requisites have to be respected. a second round of optimisation is launched in order to: • • • Check the impact of HSDPA users in the areas optimised in the previous step. Detect new weak areas not detected before. Check the HSDPA parameters implemented and tune them locally if necessary in order to increase the performance.UTRAN Optimisation Process when Introducing HSDPA if that is done and areas with high interference remain. HSDPA is enabled in the cells of the cluster. the deployment. Any optimisation decision can launch a more detailed study in the Golden Cluster if the potential gain is thought to be important and applicable to the whole network. the optimization.

Stability of the monitored area is granted. The objective of the optimisation campaign is to deliver the best possible network for all the users. it is suggested to have a window of two weeks of monitoring before starting the aerial optimisation (step 2 of this process) and after the troubleshooting period (step 3 of this process). Nortel confidential UMT/IRC/APP/019971 01. A detailed schedule is in chapter “7 Planning”. Update of optimised sites. in average (at network level). the performance and optimisation reports will be used to support the decisions made. Performance report. The monitoring metrics to monitor can be counter-based.4.UTRAN Optimisation Process when Introducing HSDPA OUTPUTS • • • List of parameters optimised. It is necessary to assure a permanent access to the Performance Monitoring platforms during all the project. The impact of HSDPA is higher in single carrier configurations (HSDPA and R99 in a shared frequency) than in dual carrier configurations (except if the network was not enough optimised before the refresh and an important aerial modification campaign was necessary). 6. TASKS In order to collect a significant amount of statistics. once the optimisation process is finished. all the metrics. PERFORMANCE BENCHMARKS PREREQUISITES • • • • The areas to monitor has gone through the previous steps. it is expected to improve. drive-test-based or a combination of both. Metric formulas and averaging windows have been agreed. Therefore. If there is any local degradation of any metric. Aerial changes impact both carriers.01 / EN Draft 18/Jul/2006 Page 22/25 . OBJECTIVES The monitoring benchmarks are used to compare key metrics before and after the HSDPA refresh in order to be sure that the performances of the current users have been not affected by the activation of that functionality.

Traffic can be low at certain cells (few samples to monitor). The mobility parameters could be modified in order to reduce changes of the primary cell. OUTPUTS • • Performance report.01 / EN Draft 18/Jul/2006 Page 23/25 . 1 HSDPA Capacity and Radio Assessment Analysis of Performance Indicators (counters) Identification of High Traffic Areas (Top 40/50 sites) CT Data Collection Post-Processing and Analysis Identification of poorly RF-covered areas > R99 Performance Benchmark #1 (Optional) RF Optimisation (Aerial Tuning) HSDPA ACTIVATION HSDPA Local Optimisation / Troubleshooting > R99 Performance Benchmark #2 (Optional) Reporting 2 3 4 5 6 7 8 9 10 11 12 13 14 The process for a single cluster (80 sites) is composed by : • • • • 4 weeks of capacity and RF quality assessment 5 weeks of RF optim. We take into account that the first analysis show that between 20 and 50% of the sites need re-optimisation. 2-3 weeks of trouble shooting A final phase of acceptance or benchmark. Further optimisation recommendations. • • • The above makes specially difficult to compare monitoring metrics at cell level and some margins on the target values must be allowed.UTRAN Optimisation Process when Introducing HSDPA It must be noted during the comparison exercise that: • The footprint of the cells will change significantly after a RF optimisation campaign that tries to reduce at its minimum the interference levels (traffic will be distributed differently after the optimisation). Nortel confidential UMT/IRC/APP/019971 01. CTg analysis to be performed in 40-50 sites and must respect the CTg and OAM limitations. PLANNING The following figure provides a typical timeframe of the described activities for a cluster of 80 sites (recommended cluster size). 7. Traffic patterns will be modified with HSDPA or new R99 users.

UTRAN Optimisation Process when Introducing HSDPA The HSDPA Introduction Methodology is only applicable in areas with enough R99 traffic.01 / EN Draft 18/Jul/2006 Page 24/25 . Generic HSDPA parameters are optimised during at least 5 weeks in a Golden Cluster (at least 1 per region). Nortel confidential UMT/IRC/APP/019971 01.

UTRAN Optimisation Process when Introducing HSDPA END OF DOCUMENT  Nortel confidential UMT/IRC/APP/019971 01.01 / EN Draft 18/Jul/2006 Page 25/25 .

Sign up to vote on this title
UsefulNot useful