Top 10 3 G Radio Optimisation Actions
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Top 10 3 G Radio Optimisation Actions

  • 33,843 views
Uploaded on

Top 10 3 G Radio Optimisation Actions

Top 10 3 G Radio Optimisation Actions

More in: Education
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
33,843
On Slideshare
33,805
From Embeds
38
Number of Embeds
1

Actions

Shares
Downloads
3,895
Comments
9
Likes
16

Embeds 38

http://www.oj3g.com 38

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. TOP 10 3G 1 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 TOP 10 3G RAN Optimisation Actions Version 0.4 Author(s): Pekka Ranta Title: TOP 10 3G Optimisation Actions Key words: WCDMA optimisation, dominance, interference, throughput Department: NET/OSS/OS Performance, 3G Radio Program © Nokia Networks 2004, Company Confidential Page 1 of 21
  • 2. TOP 10 3G 2 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 HISTORY Date Version Author(s) Change /Notes 27.02.2004 0.1 Pranta First draft 04.03.2004 0.2 Pranta Updated version 04.03.2004 0.3 S.Irons Combined AMR and Video common parameters. Editorial changes. Addes NetAct references. 05.03.2004 0.4 Pranta Radio Plan check added, UE performance check added DISTRIBUTION Date Version Delivery 27.02.2004 0.1 Review team 04.03.2004 0.2 Review team 05.04.2004 0.4 NP Radio Intranet © Nokia Networks 2004, Company Confidential Page 2 of 21
  • 3. TOP 10 3G 3 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 Table of contents 1. Introduction.......................................................................................................................................4 2. Network planning rules for optimum performance.............................................................................4 3. Network health check ......................................................................................................................5 3.1 BTS Alarms causing Blocked cells .............................................................................................5 3.1.1 Fault in O&M and DSP SW interface....................................................................................5 3.1.2 ATM overflow.......................................................................................................................5 3.1.3 DSC-bus failure....................................................................................................................6 3.1.4 Unit SW download failed......................................................................................................6 3.1.5 WSP R-Bus Error.................................................................................................................6 3.1.6 No Connection to Unit..........................................................................................................6 3.2 Software and Parameter checks................................................................................................6 3.3 Neighbour Consistency checks...................................................................................................6 3.4 Cell load checks..........................................................................................................................7 3.5 RAN Counter and KPI checks.....................................................................................................7 3.5.1 Cell Availability.....................................................................................................................7 3.5.2 RRC setup and access complete ratio.................................................................................7 3.5.3 RAB setup and access complete ratio..................................................................................7 3.5.4 RAB drop ratio......................................................................................................................8 3.6 UE Performance check...............................................................................................................8 4. Performance check with Field Measurements...................................................................................8 5. Top 10 optimisation activities to improve call performance...............................................................9 5.1 Common Call Performance Issues..............................................................................................9 5.2 Voice (AMR) specific performance Issues.................................................................................11 5.3 Video Call Performance Issues.................................................................................................12 5.4 PS Call Performance Issues.....................................................................................................12 5.5 ISHO performance....................................................................................................................15 6. Optimisation Tools..........................................................................................................................15 6.1 Nokia Application Launcher (AL)...............................................................................................15 6.1.1 RNW Object Browser.........................................................................................................15 6.1.2 RNW Online Management..................................................................................................16 6.2 Nokia Plan Editor......................................................................................................................16 6.3 EOS Reporting Solution (RS)....................................................................................................17 6.4 NetAct Reporter........................................................................................................................17 6.5 Field Measurement Tools (FMT) ..............................................................................................17 6.5.1 RF scanner.........................................................................................................................18 6.5.2 NEMO TOM Drive Test tool................................................................................................18 6.6 Actix Analysis tool.....................................................................................................................19 7. References.....................................................................................................................................20 8. Glossary..........................................................................................................................................21 © Nokia Networks 2004, Company Confidential Page 3 of 21
  • 4. TOP 10 3G 4 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 1.INTRODUCTION The aim of this document is to summarize how to • Investigate the reasons for poor 3G radio performance (call set-up failure, call drop), • Describe the potential reasons • Propose actions to improve performance (as top 10 optimisation actions) o Both common and service specific (CS AMR, CS Video and PS) This document can be used as network pre-launch optimisation checklist. 2.NETWORK PLANNING RULES FOR OPTIMUM PERFORMANCE Experience has shown that the optimum performance will be achieved with the following network planning rules: - • Sites should be located close to the users • The cells should cover only what they are supposed to cover (avoid high sites) • Unnecessary overlapping should be avoided By doing so the overall interference level will be minimized and network capacity will be maximized. SHO helps to reduce the interference providing SHO gain which needs to balanced against used resources (BTS power, Iub transmission). First check could be done with Radio Planning tool by looking at the CPICH coverage, cell dominance, SHO overhead, service coverage and intercell interference areas. The main reasons for poor radio performance are related to: • Non optimum cell design (location, antenna type/height/bearing/tilt) • Wrong site implementation (antennas, cables, parameters) • Wrong or bad parameter planning (scrambling code allocations etc, CPICH etc.) • Wrong or missing neighbour relations There can be also other reasons than bad network planning, like: • UE-specific problems (hanging onto the cell, poor cell reselection, poor power control) • UE-NW incompatibilities • BTS, RNC or network faults © Nokia Networks 2004, Company Confidential Page 4 of 21
  • 5. TOP 10 3G 5 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 3.NETWORK HEALTH CHECK The Network health check ensures that the planned network is implemented correctly, all cells are up and running and correct parameters are set. These should be done before optimisation. There are many checks to look at: - • Alarm check (BTS, RNC, other) • SW and Parameter check • Neighbour consistency check • Cell load check • KPI check • UE performance check for all the services in a controlled environment 3.1BTS Alarms causing Blocked cells The alarm status has to be checked first because they affect performance. There could be faults in BTSs, transmission, RNC or in other network elements. The alarm info can be retrieved from NetAct. The alarms having the biggest impact on the performance is BTS alarm, numbered 7651 “Base station operation degraded”. Typically, 7651 alarms means that there would be call set-up failure, SHO failure or dropped call. To clear the alarm, BTS cell/site restart may be needed. However new BTS SW releases (>???) have significantly improved the situation. The alarm 7651 contains supplementary field information about the different fault reasons. Described below are the main reasons. More information about alarm info is available in RAN Customer Care Bulletins and the Alarm Manual in NED 7. . 3.1.1Fault in O&M and DSP SW interface Description: SFN synchronization is lost. Illegal SFN value in downlink. The WSP does not receive frame number from the Wideband Application Manager Unit (WAM), or the frame number is faulty. 3.1.2ATM overflow Description: Unable to allocate AAL2 resources. Instructions: The reason for this could be lack of transmission capacity. This can be also due to RNC because it has limit in transmission capacity related to AAL2 resources. The situation will improve in RAN1.5.2ED2 release. © Nokia Networks 2004, Company Confidential Page 5 of 21
  • 6. TOP 10 3G 6 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 3.1.3DSC-bus failure Description: Data, Control and Signalling Bus between WAMs and WSPs (DSC-Bus) Failure. Target Node (ASIC) detects a fault in its operation, or some ASIC has not been able to write data on the DSC-bus to the target node, or a failure in the DSC-bus, which means that messages do not get through via that DSC-bus. 3.1.4Unit SW download failed Description: In Case Alarming source O&M slave WAM or Wideband Signal Processor (WSP) the software downloading from SW Management subsystem to the unit/subunit has failed. This alarm is closely related to Fault in O&M and DSP SW interface problem. 3.1.5WSP R-Bus Error Description: Wideband Signal Processor (WSP) R-Bus Error IRAD ASIC has detected a R- bus error. 3.1.6No Connection to Unit Description: Auto detection does not get a response from a unit that is mentioned in the HW Database. 3.2Software and Parameter checks The SW in all NEs (WBTS, RNC, AXC etc.) should be checked (to be the latest one). Also the SW in optimisation tools (NEMO, UE etc.) should be checked (to be the latest). The parameters in the RNC database should be checked so that they are implemented as planned, including all interfaces (Iub, Iur). The latest parameter recommendations [ref?] should be reviewed and implemented before further optimisation. A history of the parameter changes into the network a consistency database for all parameters should be available. Mass modifications are possible with Nokia Plan Editor (see details in LACE reference 7) and small changes with Nokia Application Launcher (see details in NEMU documentation7). 3.3Neighbour Consistency checks Neighbour implementation should be checked so that it is as planned in order to have proper cell reselection and SHO functionality. Neighbours should be bi-directional. Neighbour plan can be checked using 3G Netplan tool 7. The purpose with this tool is to graphically display cells, which are using the same DL scrambling code and to show its neighbours defined in OSS database. © Nokia Networks 2004, Company Confidential Page 6 of 21
  • 7. TOP 10 3G 7 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 3.4Cell load checks Cell load can be checked by looking at the UL interference situation with PrxNoise counter in each cell. Normally the PrxNoise is around –102…-105 dBm, but if it is more than this, there is something wrong in the cell. The reason could be external interference, or incorrect MHA parameters. The total load in UL and DL (PtxTotal, PrxTotal) should be less than (PtxTarget, PrxTarget), otherwise the cell is overloaded. Nokia EOS Reporting Solution (RS) 7 can be used for this check. Alternatively NetAct Reporter tools [ref] can be used to extract the data from the NetAct database. 3.5RAN Counter and KPI checks Performance can be seen from the RAN counter statistics. The most important KPIs with recommended target values are below: • Cell availability, >98 % • RRC setup and access complete ratio, >95 % • RAB setup and access complete ratio, >95 % • RAB drop rate for voice, < 3 % • RAB drop rate for others,< 4 % EOS RS tool can be used to check counters and KPIs. See KPI info from different projects 7. Alternative these counters can be extracted using the NetAct Reporter tools [ref]. 3.5.1Cell Availability With the cell availability info it is checked that the cell is up and running. If not the BTS restart is needed. EoS Repoting Solution (RS) reports could be used to to check the cell availability. Also customer complains and Planner info will help to find sleeping cells. More info about cell availability definition is in reference 7 3.5.2RRC setup and access complete ratio This PI gives success rate for the RRC establishment. This is KPI for call setup performance, which is available in EOS RS reports. More info about how this is calculated is in reference 7. 3.5.3RAB setup and access complete ratio This PI gives success rate for the RAB establishment – this however is not Call Setup Success Rate as it does not include RRC phase. More info about how this is calculated is in reference 7. © Nokia Networks 2004, Company Confidential Page 7 of 21
  • 8. TOP 10 3G 8 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 3.5.4RAB drop ratio This PI can be used as dropped call rate. More info about how this is calculated is reference 7 3.6UE Performance check The UE behaviour might affect the network performance: it’s recommended to test in a controlled environment the UE performance for all the services, related to • Cell reselection • SHO • Power Control 4.PERFORMANCE CHECK WITH FIELD MEASUREMENTS For Performance check drive tests are typically needed. The set of cells and measurement route should be defined first (typically 10-15 sites, all cells must be measured). With drive test measurements basic KPIs can be verified. An example of KPIs and target values are listed below, see more info about definitions of those in 7. Gategory Name of the tests Target 1. Performance tests Value Call setup success rate for Voice > 94.0 % Call setup success rate for CS 64 kbits/s Data > 92.0 % Session setup success rate for PS 64 kbits/s Data > 92.0 % Call drop rate for Voice < 4.0 % Call drop rate for CS 64 kbits/s Data < 4.0 % Session drop date for PS 64 kbits/s data < 4.0 % 2. Coverage tests Depends on the planning criteria, suggestions below CPICH RSCP >-95 dBm CPICH EcNo >-12 dB 3. Capacity tests Throughput & Round trip delay for PS data DL 64 kbps > 50 kbits/s Round trip time for 32 bytes ping < 220 ms 3. Time Tests Call Setup Time for speech and CS data (MOC) Call Setup time <7s Session Setup Time for PS 64 kbits/s Data < 10 s Table 1 Example KPIs from Drive Surveys © Nokia Networks 2004, Company Confidential Page 8 of 21
  • 9. TOP 10 3G 9 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 5.TOP 10 OPTIMISATION ACTIVITIES TO IMPROVE CALL PERFORMANCE These activities are split into • Common performance issues that affect any service • Voice (AMR) call performance • CS Video call performance • PS call performance • ISHO performance There can be situations where the same problem will cause call set-up failures or call drops. The list of problems with possible solutions is listed below, starting with the most important ones. 5.1Common Call Performance Issues Behaviour Problem Description Possible solutions Call set-up failure Poor coverage If problem is poor Check Antenna line installation Call drop area coverage, this means (antenna position and quality, poor RSCP (<-95 dBm) cable length and quality). thus also the EcNo derades very rapidly (< Check that CPICH powers are -12 dB) when the balanced between the studied coverage border is cells. reached. Check presence of shadowing obstacles. Add a site to the area. Call set-up failure Poor dominance No main server in the Use buildings and other Call drop area. area, too many cells environmental structures to with weak CPICH level. isolate cell(s) coverage. CPICH EcNo is usually very bad even the Down tilt antennas to make cells RSCP is good e.q. dominant and limit effects of RSCP –80…-90 dBm interfering cell(s). but EcNo about –10 dB Check antenna bearing. Add a site. Call set-up failure Pilot Pollution Bad CPICH Ec/Io (<-12 Find interfering cell from Scanner Call drop dB) level although results. CPICH RSCP level is good. High site in the Adjust antenna bearing and down neighbourhood may tilt or lower the antenna height cause interference. (too much tilt will break the dominance). Add interfering cell to the neighbour of the serving cell. © Nokia Networks 2004, Company Confidential Page 9 of 21
  • 10. TOP 10 3G 10 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 Behaviour Problem Description Possible solutions Dropped Missing A good usable Check scanner data and look for call/SHO failure neighbour neighbour is present missing neighbours. within cells coverage area, can cause DL Check the cabling in antenna line. interference if it is not in the active set. Swapped sectors in WBTS. Call set-up High PrxTotal The PrxTotal level is Try to figure the possible Failure due to UL significantly higher than area/direction of the interference Call drop External expected in no/low load by checking PrxTotal level on interference conditions. neighbouring cells. Alternatively use spectrum analyser & directive antenna to locate interferer. Inform operator/regulator about the found conditions. Check if auto tuning range is large enough (20 dB). Call set-up failure High PrxToatal The PrxTotal level is In case of MHA is used in BTS Call drop due to wrong significantly higher than check MHA and cables loss MHA settings expected in no/low load parameters, otherwise PrxTotal conditions. value will be too high. MHA settings should be (If MHA parameter is set to ON, checked, see more in Cable loss parameter is used, reference 7 Cable loss = Real MHA gain = Feeder loss parameter) Call set-up failure High Prxtotal due The PrxTotal level is Check the antenna installation as Call drop to Installation significantly higher than the last alternative in high problems expected in no/low load PrxNoise case. conditions. Cell set-up failure Bad RRC RRC connection set-up Set parameters so that connection set- complete message not reselection process will start up success rate heard by BTS. earlier: due to slow Ue Qqualmin, Sintrasearch and cell reselection Qhyst2 as per latest recommendation 7 Long call set-up Long time The value of Parameter Use smaller value N312 (2, time interval for sync N312 is too high: recommendation is 4). between RNC maximum number of “in Use Actix for checking the call and BTS before sync” indications set-up delay (L3 messages). connection received from L1 during Use call set-up time optimisation the establishment of a feature Dynamic setting of physical channel “ActivationTimeOffset” (possible in RAN1.5.2 ED2) enables 200 to 500ms reduction for set up delay. © Nokia Networks 2004, Company Confidential Page 10 of 21
  • 11. TOP 10 3G 11 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 Behaviour Problem Description Possible solutions Dropped call SHO to wrong Overshooting cell come Pan away overshooting cell if it is cell will cause temporarily into active too close to the serving cell, drop call. set and forces a otherwise apply down tilting as suitable serving cell to well. be dropped out. Later RSCP suddenly drops in the “wrong cell” and causes a dropped call because there is no neighbour defined. Dropped call Cell suffering As the UE Tx power is Use cell individual offset from UL not enough for target (negative value) parameter to interference = DL cell synchronisation, the balance the DL and UL coverage. (CPICH) SHO fails which will coverage much cause call drop later. Check traffic direction of in-car bigger than UL UEs to decide which cell requires coverage offsets. Dropped call DL CPICH Cell with lower CPICH Use cell individual offset (positive coverage < UL power than the value) parameter to balance the coverage surrounding is having DL and UL coverage. “too good” UL Note: Cell individual offsets are performance, as this not taken into account when cells’ UL cannot be calculating the added cell Tx used efficiently due to power. SHO is decided upon DL (CPICH Ec/No). Dropped call Round the corner The call drops due to Use cell individual offset (positive effect too rapid CPICH value) parameter to balance the coverage degradation DL and UL coverage. for Cell A, and therefore Note: Cell individual offsets are there is not enough time not taken into account when for SHO. calculating the added cell Tx power. Dropped Too many In SHO area the Delete unnecessary neighbours. call/SHO failure neighbours number of combined neighbouring cells Improve dominance. become more than 31. HO list is created using RNC algorithm in the final stage some of the neighbours will randomly be removed. 5.2Voice (AMR) specific performance Issues No AMR Specific scenarios © Nokia Networks 2004, Company Confidential Page 11 of 21
  • 12. TOP 10 3G 12 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 5.3Video Call Performance Issues Behaviour Problem Description Possible solutions Dropped Not enough DL power CS video connection needs Increase the max DL Radio call to maintain good more power to maintain the SIR Link power by decreasing quality target and thus also BLER the CPICHtoRefRaBOffset target. In case the max power increment is a lot (~3dB) then the minimum power is increased by 3dB as well which can lead to the minimum power problems (BTS sending too much power to the UEs close to the BTS and therefore causing problems to the UE and even dropped call) Therefore the PCrangeDL parameter should be tuned according to the CPICHtoRefRabOffset parameter tuning (from the default) More info in reference 7. Call set- High PrxTotal due to The PrxTotal level is Try to figure the possible up Failure UL External significantly higher than area/direction of the Call drop interference expected in no/low load interference by checking conditions. PrxTotal level on neighbouring cells. Alternatively use spectrum analyser & directive antenna to locate interferer. Inform operator/regulator about the found conditions. Check if auto-tuning range is large enough (20 dB). 5.4PS Call Performance Issues PS call performance optimisation aims to maximise the data throughput. Throughput depends very much on the round trip time (RTT, delay from mobile, typically through USB , connector to server and back). The lower the RTT the greater the potential for higher throughput. Normally RTT is around 200ms. Also the radio resource efficiency for certain bit rate should be optimised, such that resources will only be allocated when needed, based on the throughput demand. This can be optimised with Dynamic Link Optimisation (DyLo) feature parameters. It should be noted that there is no optimum parameters set to be used for all networks for maximising PS throughput, but every networks needs some local optimisation. © Nokia Networks 2004, Company Confidential Page 12 of 21
  • 13. TOP 10 3G 13 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 Throughput also varies with UEs types. Below are the throughput and efficiency specific problems and solutions, although the common call performance issues also apply. Behaviour Problem Description Possible solutions Low Throughput The User bit rate is The reason for lower Measure throughput much less than the throughput problems in and RTT. Radio Bearer bit rate file transfer is in flow either in DL or UL. control between PC Increase TCP Window and UE which could Size - RWIN in case mean that TCP RTT is much more parameter settings are than 200ms and low not optimum, which throughput has been may cause achieved. degradation to the In Windows 2000 the throughput 7 default value is 17520 Bytes. There are many tools available to change the window size, for example DoctorTCP [13]. Optimal RWIN in client = 32660 B Optimal RWIN in server = 65535 B See more in reference 7. Low Throughput The User bit rate is When uploads and Measure throughput much less than the downloads are and RTT Radio Bearer bit rate in occurring bi-directional file. simultaneously then Increase TCP Window the TCP ACKs (for the Size - RWIN in case downloading) are RTT is much more competing with the than 200ms and low upload traffic to get throughput has been across the PPP link got. between the PC and UE. This competition In Windows 2000 this in combination with the has default value of flow control instigated 17620 Bytes. by the UE will delay Optimal RWIN in client the ACK. Depending = 32660 B on how big the extra Optimal RWIN in delay is will depend on server = 65535 B how much TCP will be forced to slow down. See reference 7. Low Throughput The User bit rate is PC has lots of data to Measure throughput much less than the send in uplink direction and RTT Radio Bearer bit rate in at a rate faster than bi-directional file. the actual radio Increase TCP Window interface between UE Size- RWIN in case and BTS (=64 kbit/s). RTT is much more To prevent overflow, than 200ms and low © Nokia Networks 2004, Company Confidential Page 13 of 21
  • 14. TOP 10 3G 14 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 Behaviour Problem Description Possible solutions UE turns flow control throughput has been on towards PC to stop got. data flow. The problem is that this IWindows 2000 as stops also TCP ACK default value of 17620 for downlink data, sent Bytes. in uplink direction. This causes downlink Optimal RWIN in client throughput reduction, = 32660 B because TCP session Optimal RWIN in (=ftp) is not receiving server = 65535 B ACKs so quickly. The phenomenon is See reference 7. bigger, if the DL data rate is faster than UL data rate. Low Throughput The User bit rate is The reason for lower Tune TCP parameters much less than the throughput problems in in the Server: Radio Bearer bit rate file transfer could be MSS = Maximum either in DL or UL. wrong parameters in Segment Size (in server. bytes) = TCP payload MTU = Maximum Transmission Unit (in bytes) = IP packet size MTU = MSS + TCP Header (20 bytes) + IP Header (20 bytes) Optimal MTU in client and server =1460 B Low Throughput The User bit rate is There is Problem in Change the FTP much less than the FTP server server. Radio Bearer bit rate in bi-directional file In general FTP server should be located right after the GGSN (not behind the public internet) so it would be recommended to have test FTP server located right to the GGSN. Make several FTP sessions instead of one to increase the throughput. Try with stream e.g. http//wwitv.com Low Throughput The User bit rate is Bluetooth connection Use USB connection much less than the has been used instead of bluetooth. Radio Bearer bit rate in between UE and PC. bi-directional file Low Efficiency BTS Power resources Dynamic Link Adjust the are wasted in case Optimisation (DyLo) PtxDLAbsMax © Nokia Networks 2004, Company Confidential Page 14 of 21
  • 15. TOP 10 3G 15 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 Behaviour Problem Description Possible solutions high bit rates are used parameters are not set parameter (default but throughput is low. optimum. value 50 dBm as maximum link power, optimum setting between 35-37dBm) to trigger DyLo earlier. 5.5ISHO performance Behaviour Problem Description Possible solutions Call drop RAN is not working No GSM neighbour list This should be correctly during SHO. is sent for corrected in laterRAN measurements in case release(s). there are 3 cells in Active Set. (RAN1.5.2 ED1 CD18) Call drop Failure to decode CM starts too late Set higher ISHO BSIC before the call thresholds, FMCS: drop. CPICH EcNo, CPICH RSCP, UE TX Pwr 7 Call drop Failure to decode BSIC verification takes Set smaller BSIC before the call too much time. measurement time for drop. GSM cells, FMCG: Maximum measurement period, Minimum measurement interval, 7 6.OPTIMISATION TOOLS Tools that can be used for problem solving, verification and performance improvement are described below. For checklist part the tools were already mentioned. 6.1Nokia Application Launcher (AL) Nokia AL is part of NetAct tools. Inside AL there are many tools, like object browser and cell load monitoring tools that are useful optimisation tools. With Radio Network (RNW) Object Browser parameter modifications and value checks is possible. With RNW Online Management tool cell load online monitoring could be followed. More info in reference 7 6.1.1RNW Object Browser Object browser is tool for the WCDMA parameter changing and checking. Parameters are divided into different categories: • RNC parameters, RNC • WBTS parameters, WBTS © Nokia Networks 2004, Company Confidential Page 15 of 21
  • 16. TOP 10 3G 16 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 • Cell parameters, WCEL • Neighbour parameters, ADJS (ADJI, ADJG) • Handover parameters, HOPS (HOPI, HOPG) • Measurement control parameters, FMCS (FMCI, FMCG) There are different sets for Intra-Frequency (market as xxxS), Inter-Frequency (market as xxxI) and Inter-System (market as xxxG) parameters for ADJx, HOPx and FMCx objects. In WCEL object the parameters are more divided into categories listed below: • General (identity) • Handover control, HO • Power control, PC • Admission control, AC • Load control, LC • Packet scheduler, PS • Common channel, CCH • System Information Block, SIB 6.1.2RNW Online Management Online Monitoring tool shows the actual cell level load situation both in UL and DL direction. Both the measurement results and parameter values could be seen on graphical user interface. The values in GUI are:- • PrxTotal (total UL load, measured value) • PtxTotal (total DL load, measured value) • PrxNoise, noise level, measured value • PrxTarget, planned target rx load of the cell • PtxTarget, planned target tx load of the cell 6.2Nokia Plan Editor Plan Editor is an off-line tool for manipulating Radio Access related parameters and plans. Plan Editor is a part of Radio Access Configurator (RAC) solution. Plan Editor features support daily tasks in network development and optimisation e.g. integrating new sites, or deleting objects, or optimising parameter values. © Nokia Networks 2004, Company Confidential Page 16 of 21
  • 17. TOP 10 3G 17 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 There is Plan Editor package support for OSS3.1 ED2, where Radio Access Configurator has updated functionality for managing 3G RN1.5.2 and 2G S10.5 ED parameter data. In addition to 3G RN1.5.2 parameters supported earlier, Plan Editor also supports common 2G BSS objects that can be used for defining intersystem adjacency relations (ISHO). There are also new re-hosting related profiles and added functionality. AXC C2.0 is supported for the parameters defined in the commissioning interface and more functionality will come with RN1.5.2 ED2. More information in reference 7 and 7 6.3EOS Reporting Solution (RS) EOS RS is tool developed for internal use, which has good RAN counter and KPI reporting. It needs NetAct database to be installed to the network as it works with counters collected from the network elements and stored in the database. PC is required run the tool and get info from the database. The following KPIs can be retrieved using the tool. • Cell Availability • RRC Set-up Success Rate • RRC Set-up and Access Success Rate • RRC Drop Ratio • RAB Set-up Success Rate • RAB Set-up and Access Success Rate • RAB Drop Ratio • SHO overhead • SHO Success ratio • Also cell load info (PrxTotal, PtxTotal) can be checked. More information is in reference 7 and 7. 6.4NetAct Reporter NetAct reporter is the official reporting functionality for Nokia NetAct platform. Tools include KPI Browser, Report Builder and Report Browser. These tools allow data extraction from the PM Database and are standard to the Nokia NetAct platform. Also, Content Creation group within Nokia have developed WCDMA Reporting Suite, which uses NetAct Reporter functionality. This is an optional feature so not all customers will have purchased it. Unlike the EOS RS the KPIs reports for RAN are not ready made although they could be created with Report Builder. 6.5Field Measurement Tools (FMT) © Nokia Networks 2004, Company Confidential Page 17 of 21
  • 18. TOP 10 3G 18 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 There are a growing number of FMT available for WCDMA systems. These are divided into scanner tools or Ue based measurements tools. Both these types play a key role in the optimisation of the network. A review of tools can be found at 7. 6.5.1RF scanner 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 full picture of the (on air) radio network within a selected frequency band. The results are used to identify and understand reasons for peculiar behaviour discovered during field measurements. In addition, the scanner will indicate presence of “illegal” RF interference within the sub bands allocated to the network. The scanner data analyses can be done for many purposes:- • For low coverage areas • For antenna installation problems • For missing neighbours • For coverage optimisation With the scanner you can get the following info from the surrounding cells: • Different Scrambling codes • CPCIH RSCP value (dBm) • CPICH EcNo value (dB) More information is in reference 7. 6.5.2NEMO TOM Drive Test tool The NEMO DT tool with the Nokia 6650 UE is used to measure and verify long and short AMR 12.2 kbps (voice) MOC calls. With TOM KPI verification can be done. – GPS receiver Laptop computer Charger DC/AC converter (12 VDC/230 VAC) 12 VDC (Car battery) © Nokia Networks 2004, Company Confidential Page 18 of 21
  • 19. TOP 10 3G 19 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 UE measurements are different than to RF scanner measurements. The Scanner measures all SCs, whereas the UE only measures SC signals from the cells that the system has informed/ordered the UE through the BCH (neighbour list) or via the “measurement control” message. With TOM you can get following info: • The BLER downlink • Carrier RSSI • Data Throughput Downlink • Data Throughput Uplink • Ec/No Active Cell • Ec/No Monitored Cell • Pilot BER • Random Access Initial Tx Power • Random Access Preamble Count • Random Access Preamble Step • Random Access Tx Power • SIR target • UE Tx Power • Call Statistic: AMR, CS and PS data calls More information is in reference 7. 6.6Actix Analysis tool Actix analyser is a tool for post-processing cellular network data (GSM, CDMA, WCDMA). The tool is specifically tailored to import measurement data from various (measurement) tools and file formats and then present it in map, table, workbook or chart format. Also it is possible to define your own specific queries, although Nokia have developed a standard set of queries. Note that there is more than one version of the Analyser. • Rollout Verification Solution (RVS) • System Verification Solution (SVS) • Infrastructure Verification Solution (IVS) © Nokia Networks 2004, Company Confidential Page 19 of 21
  • 20. TOP 10 3G 20 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 Below is a list of the capabilities of Analyser:- Radio Link Performance • Distant servers Troubleshooting: • Too many servers • Unnecessarily large neighbour lists • Excessive soft handoff Event Detection and Drive • Coverage problems Test Analysis: • Poor UL or DL, coverage limited, interference • Handover problems • Missing neighbours • Pilot pollution Overall Call View: • Detailed dropped call and failed set- up level analysis • Detected problem(s) identified per call • Individual call extraction for detailed message level analysis Neighbour List Analysis: • Generation of recommendations for optimal neighbour list settings • Integration with Network Element Database • Based on UMTS/WCDMA scanner drive test data Supported Measurements • Layer 1 scanner with Scanner are: measurements (for example EcIo, RSCP, etc.) Supported Measurements • Layer 1 handset measurements (for with Handset are: example EcNo, TxPow, etc.) • RRC Layer 3 signalling – Call Control (CC), Mobility Management (MM), GPRS Mobility Management, GPRS Session Management More information is in reference 7. 7.REFERENCES [1] LACE Materials [2] RNC Nemulandia [3] 3G Netplan material © Nokia Networks 2004, Company Confidential Page 20 of 21
  • 21. TOP 10 3G 21 (21) OPTIMISATION ACTIONS NET/OS/OS Performance March 2004 V.0.4 [4] KPI status from 3G projects [5] KPI formulas and Counters [6] Field Test Cases for System Acceptance [7] MHA settings [8] Parameter changes for RAN1.5.2 ED2 [9] WRST4 training material [10] GPRS Core Network Optimisation Guideline [11] TCP optimisation for 3G [12] 3G field tools [13] DrTCP [14] Plan Editor Intanet Page [15] NetAct Reporter Bookshelf [16] FMT Homepage [17] RN1.5.2ED on NOLS 8.GLOSSARY NW Network CS Circuit Switched PS Packet Switched SC Scrambling Code SW Software UE User Equipment (aka MS) NED Nokia Electronic Documentation © Nokia Networks 2004, Company Confidential Page 21 of 21