UMTS RF Design Using Asset 3G

UMTS RF Design Using Asset3g Using Ericsson Equipment

Date First Issued Revision Number: Revision Date

May 22nd 2006 V3.0 Oct 10th 2006

© Copyright 2005 T-Mobile USA, Inc. All rights reserved. Confidential and proprietary information of T-Mobile USA, Inc. Not for distribution outside T-Mobile.

T-Mobile USA, INC. Confidential

2 of 115

Document Information The information in these materials is confidential and proprietary to T-Mobile USA, Inc. These materials are authorized for the use of T-Mobile USA service providers and their employees and agents, solely for the purposes of the agreement under which these materials are provided. The rights granted hereunder constitute a limited, nonexclusive, revocable license and not a transfer of title. Authorized T-Mobile USA service providers and their employees and agents may view, copy or print pages of these materials solely for the purposes set forth herein, but may not otherwise use, modify, copy, print, display, reproduce, distribute, transmit, publish, license, sublicense or create derivative works from these materials in whole or in part, or remove any copyright or other proprietary notices set forth herein, without the express written permission of T-Mobile USA. The information in these materials is subject to change without notice. T-Mobile USA's liability for any errors in these materials is limited to the documentary correction of errors. T-Mobile USA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THESE MATERIALS OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of these materials or the information in them. T-MOBILE, the T-MOBILE logo and the WORLD CLASS logo are registered or unregistered trademarks of Deutsche Telekom AG.


3 of 115

Revision History

Revision

Date

Author

Information

1.0

5/22/06

Dibyendu Goswami Himesh Bagley

Draft

2.0

6/30/06


Addition of 1: Prediction Manager. (Creating Path loss Predictions:) 2: Neighbor Planning. (Neighbors Planning) 3: Scrambling Code Planning. (Error: Reference source not found) 4. HSDPA Planning

3.0

10/10/06

1:Dibyendu Goswami 2: Himesh Bagley

Final agreed document with all changes.

Ericsson Reviewers 1: Damian Dimarzio 2: Jose Ramon Bacas-Malo 3.0

03/05/07


3.0

4/30/07


3.1

5/15/07


Sec 14.2 : HSDPA Traffic Raster Generation 14.4 : HSDPA output Arrays.

3.1

5/23/07


Sec 7.1: Addition of Traffic spreading inside a Polygon.

3.2

8/06/07

1:Dibyendu Goswami 2: Jess Pesito

Sec 16.2: Scrambling Code planning procedure. Using XML for Import.


1: Sec 8.0: Neighbor planning updated with values. 2: Sec 16.0: Scrambling Code planning changed from 32X 16 to 8X 64. Sec 17.0: UMTS FDD Multi-Carrier Planning

4 of 115

Table of Contents 1. Introduction........................................................................................................................................................7 1.1. Purpose.........................................................................................................................................................7 1.2. Objective.......................................................................................................................................................7 1.3. Scope............................................................................................................................................................8 2. Design objectives..............................................................................................................................................9 2.1. Design Statement.........................................................................................................................................9 2.2. Service types..............................................................................................................................................10 2.3. Coverage Requirements.............................................................................................................................10 2.4. Common Channels Power Distribution.......................................................................................................10 2.5. Design Key Performance Indicators............................................................................................................11 2.5.1. Nominal Design (Un-Loaded Case):..................................................................................................11 2.5.2. Optimal Design ( Loaded case) .........................................................................................................12 2.5.3. Vendor Acceptance Design Targets..................................................................................................12 2.6. Design process flow chart.........................................................................................................................13 3. Asset 3G settings...........................................................................................................................................15 3.1. Assumptions...............................................................................................................................................15 3.2. Importing a Pre defined user Polygon........................................................................................................15 3.3. UMTS Parameters setup in Asset3G..........................................................................................................18 3.3.1. UMTS Resources 18 3.3.2. UMTS Carriers: 19 3.3.3. Node B and UMTS Cell Parameters..................................................................................................20 3.3.4. Frequency Dependent Settings:.........................................................................................................23 3.3.5. UMTS Cell Parameters: 26 3.4. Clutter Parameters:.....................................................................................................................................27 3.5. Bearers.......................................................................................................................................................27 3.5.1. UMTS Bearer UL: 28 3.5.2. Noise Model: 28 3.5.3. Eb/No Speed and Delta: 29 3.5.4. Power Control: 29 3.5.5. Mobile TX Power Gain: 30 3.5.6. Average Power Rise Gain:.................................................................................................................30 3.5.7. Power Control Headroom Gain:.........................................................................................................31 3.5.8. DL Bearer: 31 3.6. Services......................................................................................................................................................32 3.7. Terminal Types...........................................................................................................................................35 3.7.1. Clutter Tab: 35 3.7.2. Vectors: 36 3.7.3. Polygons: 36 3.7.4. Services : 37 3.7.5. HSDPA 37 3.7.6. WCDMA Parameters: 38 3.8. Default Asset Parameters: .........................................................................................................................38 4. Site and Cell Naming Conventions for UMTS................................................................................................39 4.1. UMTS SiteID (Node B SiteID).....................................................................................................................39 4.2. UTRAN CellID (Sector ID)...........................................................................................................................39 5. Site Status Flags for UMTS:............................................................................................................................40 6. Creating Path loss Predictions:......................................................................................................................43 7. Traffic Spreading and Analysis.....................................................................................................................46 7.1. Creating Traffic Raster Files.......................................................................................................................46 8. Neighbors Planning.........................................................................................................................................53 8.1. UMTS intra-frequency neighbors................................................................................................................55 8.2. GSM to UMTS neighbor cells: ...................................................................................................................58 8.3. UMTS to GSM cells.....................................................................................................................................59 9. Nominal Design ...............................................................................................................................................62 9.1. Performing Nominal Design:.......................................................................................................................62


5 of 115

9.2. Displaying the Nominal Design Results .....................................................................................................67 9.2.1. Best Server: 67 9.2.2. Pilot Coverage: 68 9.2.3. Pilot Ec/Io 68 9.3. Generating Statistics from a Nominal Design..............................................................................................69 10. Internal Design Process ...............................................................................................................................71 11. Vendor Acceptance Design Process...........................................................................................................73 12. Simulator in ASSET 3G - 5.2 ( Optimal Design Stage)................................................................................75 12.1. Introduction...............................................................................................................................................75 12.2. Inputs to the simulator:..............................................................................................................................76 12.2.1. Bearers inputs: 76 12.2.2. Services inputs: 76 12.2.3. Terminal Types inputs 76 12.2.4. Traffic Raster inputs: 76 12.2.5. Running the Simulator: 76 13. Viewing Output Arrays:.................................................................................................................................82 13.1.1. Service Arrays: 83 13.1.2. CPICH RSCP: 83 13.1.3. Pilot Ec/Io: 83 13.1.4. DL Achieved Bearer: 84 13.1.5. Achievable UL Bearer: Dependencies: ...........................................................................................85 13.1.6. DL Coverage Probability: ................................................................................................................85 13.1.7. UL Coverage Probability:.................................................................................................................86 13.1.8. DL Iother / Iown: 86 13.1.9. Design Changes Allowed.................................................................................................................87 13.1.10. Defining CS 64 and PS 64 Service................................................................................................88 13.1.11. CPICH RSCP 89 13.1.12. Pilot Ec /Io: 89 14. HSDPA............................................................................................................................................90 14.1. HSDPA Configuration:..............................................................................................................................90 14.1.1. Adding and Editing HSDPA Coding Rates: .....................................................................................90 14.1.2. Defining Resources for HSDPA:......................................................................................................91 14.1.3. Creation of HSDPA Bearers:............................................................................................................91 14.1.4. Defining HSDPA Service:.................................................................................................................92 14.1.5. Defining HSDPA Terminal:...............................................................................................................94 14.1.6. Enabling HSDPA on the Site Level:.................................................................................................96 14.2. Traffic File Generation for HSDPA:...........................................................................................................97 14.3. HSDPA Arrays generation and Analysis:..................................................................................................97 14.4. Viewing Output Arrays:.............................................................................................................................97 15. Data Transfer to Ericsson for RF Design Review.......................................................................................98 16. Scrambling Code Planning...........................................................................................................................99 16.1. Scrambling Code Groups:.........................................................................................................................99 16.2. Scrambling Code planning procedure:......................................................................................................99 16.3. Using Scrambling code Planner:.............................................................................................................104 17. UMTS FDD Multi-Carrier Planning ............................................................................................................107 17.1. Introduction.............................................................................................................................................107 17.2. UMTS FDD Multi-Carrier Simulation ......................................................................................................107 17.3. Load Status and Distribution 10..............................................................................................................107 17.4. Carrier Prioritization Defined by the User................................................................................................108 17.5. Setup for 2nd Carrier Planning................................................................................................................109 17.5.1. Equipment Type Settings...............................................................................................................110 17.5.2. Site Database Settings 110 17.5.3. Service Assignment 112


6 of 115

1. Introduction 1.1. Purpose This document is designed for T-Mobile UMTS RF Planners who will use the Asset 3G Planning tool to design the UMTS network for their markets. This will serve as a guide with the understanding that certain situations will require further guidance and (sometimes) change in the values proposed here on a case by case basis for the appropriate design of the UMTS networks.

1.2. Objective The objective of this document is to introduce and describe each of the parameters within ASSET3G which relate to system modeling of a 3G network. Further, default values, sometimes by infrastructure vendor, are suggested for tool configuration. The relationship between the individual service link budgets and settings contained with ASSET3G are described. This document will serve as the master user reference guide for the use of Asset 3G. Actual tool settings should comply with the guidelines provided in this document. By the end of this document, user will be able to understand / perform the functionality of a 3G network using Asset 3G design tool. He will be able to understand / create UMTS functionality which includes hierarchical network planning, propagation modeling, service definition, analysis arrays, neighbor list definition, detailed reporting and simulation of network performance. Asset 3G allows you to plan either a UMTS Frequency Division Duplex (FDD) network or a UMTS Time Division Duplex (TDD) network. For UMTS FDD, it also supports Omni Transmit Sector Receiver (OTSR) and High Speed down Link Access (HSDPA) configurations. A definition feature of UMTS standard is to support for different services, such as Voice, Internet and Video. Asset 3G provides a flexible approach to planning and analyzing different services types by using a combination of services types, terminals types and terminal density arrays.


7 of 115

1.3. Scope The scope of the document is to explain UMTS RF design objectives, design input requirements, tool setup, simulations and performance analysis using Asset 3G RF planning tool. The overall task can be summarized as below:

•

Define service types and design objectives for an UMTS market.

•

Update site database based on site audits.

•

Update propagation models.

•

Update antenna settings based on site audit and UMTS antenna recommendations.

•

Set up Asset 3G. Define bearers, services and terminal for each UMTS service type.

•

Run coverage predictions and create best server arrays.

•

Do neighbor planning

•

Create Traffic raster files.

•

Generate and analyze Nominal and optimal Design.

•

Analyze KPI plots.

•

Implement changes and re-run simulations until design objectives are met.

•

Complete Scrambling code planning

•

Prepare deliverables.


8 of 115

2. Design objectives As with any endeavor, it is important that the goals are clearly set at the beginning. Before any 3g network can be designed, the specific targets must be laid out.

2.1. Design Statement T-Mobile will design and deploy an UMTS network across all markets nationwide that will be capable of providing voice, packet data and HSDPA services. The design (voice centric but data capable) will be an overlay on the existing GSM network. While designing the UMTS RF network, it should be looked as the design of a next generation network that will eventually become the primary network and carry most of T-Mobile’s total voice and data traffic. The objective of the design is an UMTS network that will provide same coverage and same or better performance as the current GSM network. Within a pre-defined UMTS coverage area, T-Mobile will do an overlay design on the existing GSM sites. Examples of exceptions to the overlay principle would be GSM sites purely built for capacity reasons which may not be needed in the UMTS design. Another exception would be high-sites that would be counter-productive to UMTS design. Other exceptions would be GSM sites which cannot accommodate the extra antennas, lines and equipment for UMTS. GSM sites that are in development (hard cost approved, soft cost approved with on-air dates projected within the launch date of the UMTS network) should also be considered in the UMTS overlay design. As is the case with most initial designs of mobile networks, the minimum requirement of the UMTS network within a pre-defined UMTS design polygon would be to provide in-vehicle coverage for voice service. The primary design objectives and considerations for the UMTS network can be summarized as follows: 1. The UMTS network will be a voice centric, but data capable network 2. Traffic forecast to be used for the design will be based on FP&A projections that will be converted into users/cell based on the GSM traffic profile. 3. The goal is to design for a traffic load that is projected for 12 months past launch of the network. 4. UMTS design will be done in a two step process : A: Internal design, in this the design will be done with mix traffic spread for indoor and outdoor scenarios. B: Vendor acceptance design, in this all the traffic will be simulated for In-car service. The idea behind this is as internal design is more stringent, passing Vendor acceptance would be easier. Further details will be discussed under section “Vendor Acceptance Design Process” and “ Internal design process” 5. The UMTS RF network design that will result from the above coverage and capacity requirements will be evaluated for call mix scenarios i.e. mix of voice and HSDPA services etc. This will provide a reasonable estimate of the performance of data services that can be provided by the voice-centric network


9 of 115

2.2. Service types Following service types should be considered for UMTS RF planning of a T-Mobile market: 1. Voice Circuit switched -AMR 12.2kbit/s UL /DL. 2. Call mix: High Speed Packet Data Access (HSDPA) with Voice 12.2 Radio Bearers, Services and terminal type should be defined for each offered service type as explained under Asset 3G settings. Asset 3G version 5.2 supports HSDPA. Detail HSDPA settings, simulation methodologies and analysis are discussed in section 12 of this document. Traffic raster file for each type of service and it’s association with terminal type is explained in Traffic section of this document.

2.3. Coverage Requirements This section is pulled from “UMTS RF Planning Guidelines v1.0 Sec : 2.2”

As far as coverage is concerned and as a starting point, the following values may be considered for a loaded network: Coverage Type ( On-Street)

AMR 12.2

CS Video 64

PS 64

PS 128

PS 384

PCPICH RSCP Outdoor PCPICH RSCP In-car PCPICH RSCP In-Building Residential PCPICH RSCP In-Building Commercial PCPICH RSCP In building High Dense Urban PCPICH Ec/N0 (all types)

-105 dBm -99 dBm -91 dBm

-102 dBm -96 dBm -88 dBm

-102 dBm -96 dBm -88 dBm

-97 dBm -91 dBm -83 dBm

-92 dBm -86 dBm -78 dBm

-85 dBm

-82 dBm

-82 dBm

-77 dBm

-72 dBm

-82dBm

-79dBm

-79dBm

-74dBm

-69dBm

-14 dB

-12 dB

-12 dB

-11 dB

-10 dB

As a reminder, the CPICH_Ec/N0 (Ec/N0 of the primary pilot signal) is the quantity that should drive the design. The link budget results are slightly more optimistic, especially for the PCPICH E c/N0 values. The above values were derived from the link budget results and adjusted accordingly to the recommendations from what has been observed on real networks in T-Mobile-Europe and other deployed UMTS network. These results factor the tolerances that should be included in the link budget calculations. These numbers have also been impacted by the contract negotiations with the vendors.

2.4. Common Channels Power Distribution Since the design is done as an overlay, we assume a site densification already higher than a phase-one voice-only green-field-network design. The main concern is therefore to control the radio and maximize the capacity. Following up with this idea, the total common channel power shall not exceed 25% of the maximum cell output power in all cases (this includes the HSDPA control channel, HS-SCCH). The pilot power shall be contain between 5% and 10% of the maximum cell output power. A good value to start with would be a ratio of 8%. Hereafter is a table of a suggested power partitioning (link budget values):


10 of 115

Channel PCPICH (relative to the maximum output power) PCCPCH (relative to PCPICH power) SCCPCH (relative to PCPICH power) PSCH (relative to PCPICH power) SSCH (relative to PCPICH power) PICH (relative to PCPICH power) AICH (relative to PCPICH power) Table 1: Power settings (Without HSDPA)

Channel PCPICH (relative to the maximum output power) PCCPCH (relative to PCPICH power) SCCPCH (relative to PCPICH power) PSCH (relative to PCPICH power) SSCH (relative to PCPICH power) PICH (relative to PCPICH power) AICH (relative to PCPICH power)

Settings

Duty Cycle (Activity)

8% -3.1 dB -1.25 dB -1.8 dB -3.5 dB -7 dB -7 dB

100% 90% 100% 10% 10% 96% 6.7%

Settings

Duty Cycle (Activity)

8% -3.1 dB -0.25 dB -1.8 dB -3.5 dB -7 dB -7 dB

100% 90% 100% 10% 10% 96% 6.7%

Table 2: Power settings ( With HSDPA) A value of 28 dBm is accounted as an average power across the cell for the HS-SCCH channel (for HSDPA link budgets). This additional power consumed by the downlink HS control channel is added to the SCCPCH power. Example: for a PCPICH power of 35.1 dBm (8% of 40W), an HSDPA simulation should bear a 34.8 dBm SCCPCH power (33.8 dBm for SCCPCH and an extra 1 dBm for HS-SCCH). The load is applied to the SCCPCH because of the current implementation of HSDPA in the RF planning tool Asset3G. The HS-SCCH power is calculated separately in the link budget. This would lead to an effective ratio of 23% of the power reserved for the common channels with HSDPA versus the maximum output power available. .

2.5. Design Key Performance Indicators The UMTS design will be done in two phases, nominal design using with no traffic loading and optimal design using Monte Carlo simulator with traffic loading. Key performance indicators for each phase are listed as below. Also listed are the targets to be met for equipment vendor’s acceptance of T-Mobile’s RF design. Please note that the design targets for the unloaded scenario are as important as those under loaded conditions.

2.5.1.

Nominal Design (Un-Loaded Case):

The purpose for this scenario is to maximize the Ec/Io before loading any traffic on the network. Only CS Voice 12.2 service will be included in the analysis. For running this scenario refers to Section 8.0 of this document. Service type: CS Voice 12.2: Best RSCP (Indoor Array) : >= - 104dbm for 98% of the covered area • Un-Loaded Pilot Ec/No. : >= -9 dB for 95% of the covered area Please note that the RSCP levels mentioned above refer to the use of indoor arrays.


11 of 115

2.5.2.

Optimal Design ( Loaded case)

There are two sets of targets specified in this section. One for internal design acceptance and one specific to vendor acceptance of the RF design. This is because the vendor acceptance targets are derived from levels agreed to in the equipment contract and directly relates to performance guarantees and meeting KPIs. Internal Design Targets (under load)

•

Best RSCP

: >= -104dBm for 98% of the area (or more)

•

Pilot Ec/No

: >= -12dB for 95% of the area

•

Pilot Ec/No

: >= -14dB for 98% of the area (or more)

•

Mean Served

: >= 95%

NOTE on internal design targets: Please note that the % of area to be covered by certain levels of RSCP and Ec/Io are based on typical area targets for an UMTS RF Design. The actual values that can be attained in a given market will be dictated by the following (and hence may be lower, especially the Ec/Io) 1. The overlay constraints that will be part of the UMTS design since this will be a design based on the existing GSM network. 2. If there are areas in the GSM network that don’t have any coverage, it will mean that it will be difficult to provide UMTS coverage to those areas without building additional UMTS only sites. Such areas will affect the overall % area targets for coverage 3.

For initial launches, we have to make sure (as much as possible) that we build UMTS in areas which already have GSM coverage to ensure IRAT handovers for E911. So, while all designs should be targeted to meet the internal design targets, there will be exceptions and each should be looked at on a case by case basis. The ultimate goal is to deliver a quality voice centric but data capable network at launch for all markets

2.5.3.

Vendor Acceptance Design Targets

The following section defines the design metrics relevant to the acceptance of the market’s RF design by the vendor. The following KPIs have to be met for the market in the RF design under loaded conditions before it can be submitted to the vendor for design review. Service Type: CS Voice 12.2 Mean Served

:

>=98%

This is generated automatically inside the service area (by the values defined in the Terminal settings), which will be the area within which the vendor will agree to meet all network KPIs. Any areas that will not meet the coverage targets mentioned below will be exempted from meeting network KPIs. Service Area Definition: Service areas will be defined based on the predicted signal levels of the final design. All areas greater or equal to the following thresholds will be considered as the service area for CS Voice 12.2 Pilot RSCP (Indoor Array)

>=-105dBm and

Pilot Ec/No

>=-14dB

Similarly, the service areas for CS64 and PS64 will be defined as areas greater or equal to the following thresholds Pilot RSCP (Indoor Array)

>=-102dBm and

Pilot Ec/No

>=-12dB


12 of 115

The service area for HSDPA services will be the same as that for PS64 Exemption areas will be areas which don’t meet the above coverage thresholds. Coverage exports of RSCP and Ec/No plots will be done in MapInfo and queries will be used to derive the intersection of areas which satisfy both the RSCP and Ec/No conditions. The intersection will define the service areas and the gaps will be the exemption areas

2.6.

Design process flow chart

The flow chart below will give an idea on the process to be followed for a UMTS network design.


13 of 115


14 of 115

3. Asset 3G settings 3.1. Assumptions Before we start describing Asset 3G related parameters and procedures we make following assumptions: • • • • • •

UMTS Polygon for a given market is defined and available. If Not available , follow section 3.2 Cluster boundaries are defined and available in Asset. Site database for initial UMTS planning is imported (XML import) and Node Bs is created. Antenna database is updated and configured as per design guidelines LNA if applicable are configured as per design guidelines. Feeders are defined and assigned per Node B.

3.2. Importing a Pre defined user Polygon. Firstly, ensure you have a Map View (2D View) window open with the required area and data types displayed. Click on the ENTERPRISE ‘Utilities’ Tab and select Tools → Vector… to obtain the Vector Editor window.

To create a user polygon, vector category. The following dialogue box will open and will have two options in there: 1: System Vectors 2: User Vectors ***


15 of 115

*** Note: If user Vector directory is not defined in the initial start of the project, User vector option will not appear in the vector editor. Select the ‘ User Vector’ option. You will now be prompted to provide a name for the new user Polygon.

Then click on the User Vector and import the vector file:


16 of 115

After selecting this option, an import tab will open asking for a Map Info Tab file location.

***

This version of Asset 5.2, a user can import Map info Tab files. *** Note: Before importing, make sure that the tab files are saved in correct projections as the project.


17 of 115

3.3. UMTS Parameters setup in Asset3G This section describes at a high level the parameters and settings required in Asset3g in order to perform coverage and capacity analysis. Please refer to the Asset3g reference guide for more detailed information if necessary. The screenshots used in this document have been taken from V5.2 of Asset3g.

3.3.1.

UMTS Resources

In Asset3g you can specify up to 6 UMTS resources. To define UMTS resources in Enterprise click the Asset3G tab and then go to Configuration  UMTS Resources.. Following window appears:

#

Check “Air interface” box for Channels, that will be used for R99 services. # Note: HSDPA is discussed in the section 12 of this document.. When defining a Node B Type (Equipment) you can associate up to 3 UMTS resources with it. These resources can be pooled at Node B, Carrier or Cell level. Resource limits can also be specified per Node B Type. To create a Node B type. Go to Equipment Node B Types. Following window appears:


18 of 115

Name the Node B type and click the “Resource Types” tab and select Channels under Resource 1.Specify resources under the “Default Limits” tab as shown below:

Go to Section 12 for HSDPA settings.

By default the resource limits are set to very large values i.e. 10000. This values in the channel section is kept default before vendor section. After the equipment vendor is decided, actual equipment values should be used.

3.3.2.

UMTS Carriers: To Define the carriers – Go to configuration > Carriers > UMTS Carriers:


19 of 115

UL and DL Frequency band should be specified in terms of corresponding channel numbers in the box shown above.

3.3.3.

Node B and UMTS Cell Parameters

Resources and Carriers: In the Site Database at the Node B, Resources tab you specify the use of a particular Node B Type that has been defined if any. Depending on where the particular resource is pooled that is where the resource limits are depicted i.e. in this particular case we have two resources Channels and Codes which are pooled at Node B and Cell respectively, this is illustrated in the two figures below.

NOTE: SNAP SHOTS ARE FOR EXAMPLE ONLY. ACTUAL VALUES SHOULD BE REFERENCED FROM THE ATTACHED “ASSET 3G SETTINGS” SECTION: 3.8. The resource limits can be edited on a per Node B or Cell basis in the Site Database. It is recommended to do a global edit for all the Node B.


20 of 115

UMTS Resources defined at the Node B – Cell level:

At the Node B user must also define the Carriers supported by it:


21 of 115

On the Antennas Tab at the UMTS Cell, feeders and MHA (or TMA) used at the cell can be specified, that is, if any are used. Feeders and MHA have to be defined in the equipment dialog prior to their use at the cell:

UMTS Cell: Antenna Tab. In the tab, the TMA and Feeder is defined.


22 of 115

3.3.4.

Frequency Dependent Settings:

As the Uplink and Downlink frequency’s are different, the settings of feeder losses will be different. On the Downlink, 2100 MHz losses have to be defined on the feeders

Frequency, Losses (db/m) and Total connector losses ( db) for 2100 to be defined here.

On the Cell level, Antenna Tab, assign the appropriate Feeders and TMA to each sector.

Antenna The wide band antennas have patterns for 1700, 1900, 2100 MHz. It is recommended to use 1900MHz antenna patterns for all sectors in the design tool.


23 of 115

Model Extrapolation RF propagation models have been tuned in the 1900MHz band. This is because the models that are used for UMTS design are models generated in the nationwide model tuning exercise done in 2006 for the GSM network. To use these models for UMTS design, they have to be extrapolated for the AWS frequencies. There is a 400MHz difference between the uplink and downlink frequencies, but we can specify only one model in Asset. It is recommended to extrapolate the model to 2100MHz and then provide a change in one of the uplink settings to account for the gain because of the difference in frequencies between uplink and downlink. Extrapolation of the Asset Macro cell 3 model (from 1900MHz to 2100MHz) This will be done by adding an additional 1dB loss to the clutter through loss factors of the different clutter types in the tuned 1900 model. For example, if the clutter through loss value for ‘Residential with few trees’ is 4dB in the model tuned for 1900MHz, then it should be changed to 5dB for the model to be used for UMTS design. Uplink change: Since the model is extrapolated to 2100MHz, the difference in path loss between 2100MHz and 1700MHz is now simulated by adding 2dB to the max UE TX power setting in the terminal section in Asset.


24 of 115

Terminal section:


25 of 115

3.3.5.

UMTS Cell Parameters:

The figure below shows the Cell Parameters page as available in V5.2:

The table below describes the list of cell parameters that must be specified at the cell level (some of these parameters: Parameter

Comments

Noise Rise Limit (dB) Orthogonality Factor Pilot Power (dbm) Max TX Power (dbm) PCCPCH (dbm) SCCPCH (dbm) PSCH (dbm) SSCH (dbm) AICH (dbm) PICH (dbm) HSDPA Link Power (dbm) Soft Handover Window (dB) Noise Figure (dB) Active Set Size Splitter Loss (dB )

Threshold Limit for system Noise. Specified on a per cell basis Common Pilot Channel (CPICH) Total PA Output Power Available at the Cell Primary Common Control Physical Channel Secondary Common Control Physical Channel Primary Synchronization Channel Secondary Synchronization Channel Acquisition Indicator Channel. Paging Indicator Channel. If HSDPA is enabled on the Cell. Handover Margin Noise Figure of the Receiver Active Set size for the cell. (Optional) DL only loss typically used for modeling the power splitter present in OTSR configured cells.

The maximum and minimum TX power per connection in DL can be specified and are used as hard limits in the simulator:


26 of 115

3.4. Clutter Parameters: Fading characteristics of the environment are morphology dependent. Asset3g allows the specification of the standard deviation of fading on a per clutter basis. Asset3g also allows the specification of Indoor Losses on per clutter basis and in V5.2 the specification of the Orthogonality Factor per Clutter basis instead of per cell basis. To define clutter parameters, go to Configuration Clutter Parameters  3g.. Following window appears:

Set up the values as in the embedded sheet – Asset Mapped Parameters “Clutter Parameter Tab”

3.5. Bearers Bearers for both UL and DL must be created for each service type. To define Bearers go to Configuration Bearer  UMTS+HSDPA. Click add, name the Bearer type and populate the fields from the “Asset3G settings” sheet included in the section 4.8.4. Screen shots are for example only.


27 of 115

3.5.1.

UMTS Bearer UL:

Air interface (bps): The Air Interface (bps) values are used in the processing gain calculations. User (bps): Values are used in the Throughput Reports. Control Overhead Factor (%): The Control Overhead Factor accounts for the fact that control channel power is transmitted even during inactive periods of a call. Channels: This represents the hard capacity loading imposed by a bearer. These include the default resource of channels plus up to 5 user defined resources. The user may wish to define fixed network capacity per site as a resource. Each bearer can then be defined as using up a certain fraction of this resource. Vendor dependent. Typically comes in 16kbps channel elements. For 12.2 kbps, this value is 1, for 64 kbps, this value is set to 4, for 128 kbps, this value is set to 8 etc. An example of a user defined resource would be the capacity of the fixed network feeding a particular site. This might limit the total user throughout to perhaps 1500 kbps and a resource of 1kbps can be declared

3.5.2.

Noise Model:

The mapping between the Eb / No and F.E.R. This tab is used to edit the Eb/No to FER curve for a UMTS Bearer. The pre-defined noise models (Gaussian or Rayleigh) provide default Eb/No to FER mapping values.


28 of 115

3.5.3.

Eb/No Speed and Delta:

In the Eb/No Speed Dependency pane, you can enter values to act as offsets (in dB) to the basic Eb/No requirements specified above. You can set speed variations on the terminal types.

3.5.4.

Power Control:

In this Tab, a user can specify how Power Control Headroom (fast fade margin) and the Average (interfering) Power Rise (to other cells) vary in dB according to the mobile speed.


29 of 115

3.5.5.

Mobile TX Power Gain:

The amount by which the mobile transmit power can be reduced to give the same quality of service when the mobile is in soft or softer handover. This depends on the difference between the Eb/No values received from the best two serving cells and also the speed of the mobile A mobile in soft handover can experience an uplink gain, which allows the mobile to transmit at lower power. This gain for mobile TX power (TXP) depends on both the mobile speed, and the difference between the best two achieved uplink Eb/No values.

3.5.6.

Average Power Rise Gain:

The amount by which the mobile Power Rise is assumed to be reduced in soft or softer handover. Again, this depends on the difference between the Eb/No values received from the best two serving cells and also the speed of the mobile. The average power rise (PR) for the interference caused by the mobile is lower for mobiles in soft handover. This "gain” depends on both the mobile speed, and the difference between the best two achieved uplink Eb/No values.


30 of 115

3.5.7.

Power Control Headroom Gain:

Mobiles at a cell edge transmit at higher powers than those nearer to the base station, and so are more likely to have difficulty dealing with deep fades near the cell edge. To model this, a Power Control Headroom (PCH) is added to the link budget. This margin is smaller for mobiles in soft handover. This "gain” depends on both the mobile speed, and the difference between the best two achieved uplink Eb/No values.

3.5.8.

DL Bearer:

Down Link Gain: Two parameters are entered here: the amount by which the target downlink Eb/No can be reduced when the mobile is in soft or softer handover. Again, this depends on the difference between the Eb/No values received from the best two serving cells and also the speed of the mobile. The improved radio channel which occurs when a mobile is in soft handover also allows the base station to transmit at lower power. This Downlink gain depends on both the mobile speed, and the difference between the best two received pilot Ec/Io values. The gain values are editable (in dB) for each Speed/Delta combination. The Max TX Power (dbm) is the maximum transmit power that may be allocated to an individual downlink bearer of this type. Please note that the specification of gains or dependencies of Eb/N0 targets for different speeds is really only useful in the planning tool if mobile speed characteristics are specified at the Terminal Type.


31 of 115

3.6. Services To define services, go to Configuration Services, click add for a new service type and follow the following steps:

To account for the different services offered to the subscriber, you can set up your own services and then allocate the services to terminal types. For example, services might have different costs, data rates, and other requirements such as quality of service. Some of these factors are determined by the bearers that assigned to a service. The parameters that you specify will change how the simulation behaves and will enable you to examine coverage and service quality for individual types of service.


32 of 115

This completes service type creation for any CS service. For packet service, select “Over ride packet model” option in the snap shot as shown above. Then go to UMTS DL Bearer / UMTS UL Bearer and change the “ Pow Activity %” and “Res Activity %” to 100% . Example snap shot shown below. :


33 of 115

Precedence Class: The priority that should be given to the packet switched service. By the feature a packet based service priority can be changed with respect to other service. Traffic Class: Conversational, interactive, streaming or background. ARQ max number re-transmission: The number of times the terminal will try to retransmit before giving up on transmitting a packet. Default value = 3. ARQ re-transmission timeout: The number of radio frames waited before a dropped block is retransmitted. This is used to calculate the mean retransmission delay. Mean packet size: Mean size of a packet. Mean # of packet calls per session : Mean number of packet calls per session. Reading time between calls: It is the time between a bunch of packets burst during a PS call. Mean # of packets in call: Mean number of packets transmitted during a PS call. Inter-packet arrival time: Mean time period between packets in a PS call. BLER working point :This is used to calculate the percentage retransmission rate. This is given by the formula-


34 of 115

3.7. Terminal Types To define Terminal types, go to Configuration  Terminal Types, click add for a new Terminal type and follow these steps:

Terminal Types represent the different types of mobile terminal in the network, and their geographical distribution. In a cellular network, subscribers can have different types of mobile terminals with different characteristics. In ASSET3g, we can define a variety of terminal types to represent current or projected distribution profiles of the subscribers in the network. The terminal can be associated with a specific or multiple cell layers, or specific or multiple services. We can also determine how the traffic will be spread according to specified geographic distributions in relation to the mapping data.

3.7.1.

Clutter Tab:


35 of 115

This tab helps in specifying the probability for each clutter type in relation to terminal percentage inside the building. A user can also specify the weighting related to the clutter type. For Clutter weighting values, refer to ”Asset3G Settings” excel sheet in section 4.8.4– Terminal section.

3.7.2.

Vectors:

Weights enable you to assign relative weights to the various vectors that your map data contains. These weights should represent the expected ratios of subscribers in each clutter type or vector. Densities enable you to define absolute traffic densities for each clutter type or vector. This is just for example but we will not use vector in our simulations. So make sure to set all values to zero.

3.7.3.

Polygons:

For either Weights or Density selected in the vector Tab, you can specify traffic to be spread into selected polygons. The traffic value for the polygon will be a total spread value if using Weights, or an absolute traffic density if using Density. Traffic can be spread into polygons with or without taking account of clutter weights. Polygons will not be used for our simulations. So make sure to set all the values to zero.


36 of 115

3.7.4.

Services :

Select the services to be supported by the Terminal Type.

3.7.5.

HSDPA

Disable HSDPA for R99 services.


37 of 115

3.7.6.

WCDMA Parameters: Specify WCDMA parameters for the terminal type as provided in the “Asset3G settings” sheet in section 4.8.

3.8. Default Asset Parameters: Attached sheet lists out all the default parameters for each type of services in relation to link Budget

Ericsson - Asset Mapped Parameters

Note: The Parameters are mapped to Link Budget. Any change in Link Budget, this sheet needs to be updated.


38 of 115

4. Site and Cell Naming Conventions for UMTS UMTS deployment for T-Mobile is intended to be an overlay design of the existing GSM network. For this purpose, we will be generating a separate set of sites (Node Bs) and sectors that will be part of the UMTS design in Asset 3G. This section describes the proposed naming convention to be used for the sites and cells for UMTS in Asset 3G. The naming convention should serve the purpose of maintaining a consistent relationship with the GSM site and CellIDs in Asset. If possible, the goal is to have a naming convention that can be co-related and matched with other network element naming conventions. Keeping the above mentioned points in mind, the following naming conventions are proposed for the UMTS site database in Asset 3G.

for all markets

4.1. UMTS SiteID (Node B SiteID) In Insite, the UMTS sites are not going to be defined separately. They are just going to be defined as additional sectors attached to the GSM SiteID. Hence the naming proposal for UMTS sites in Asset is to keep the siteID the same as that for GSM sites. Example: The GSM SiteID for an on-air site in Asset is CH12345A. The corresponding UMTS SiteID in the Asset database will then also be named CH12345A

4.2. UTRAN CellID (Sector ID) The naming convention for cells is to follow the current naming convention in Asset for GSM sectors but by replacing the last digit with numbers i.e. each sector will be named as SiteID followed by _1, _2 etc for sectors A, B etc. Example: CH12345A is a 3 – sectored UMTS Site in Asset 3G. The sectors/cellIDs for this site will be named as CH12345A_1, CH12345A_2 and CH12345A_3 In summary, the relationship with GSM site and cell identities will be maintained by the above proposed naming convention.


39 of 115

5. Site Status Flags for UMTS: For UMTS network design work, we need to incorporate new flags in Asset for planning purposes. Given below is a list of flags that are proposed. As the network gets deployed, we may find the need to add some flags which will be relevant for that Phase of activity. In addition, there may be certain flags which will be needed on a Regional level. This can be incorporated as necessary by the Regional Asset administrators. The first option for each flag group will be the default value for that flag. 1. Group - Site Status Options – N/A 2G On-Air 2G Hard Cost Approved 2G Soft Cost Approved 3 Year Plan New 3G Site De-Commissioned 3G On-Air 2G On-Air – This indicates that this site in the UMTS database is currently on-air in the GSM network. 2G Hard Cost Approved – This indicates that this site in the UMTS database is approved to be built in the GSM network. 2G Soft Cost Approved – This indicates that this site in the UMTS database is in development in the GSM network i.e. it is in the process of candidate search and finalization. 3 Year Plan – This indicates that this site in the UMTS database is part of a long term design plan for the GSM network i.e. search rings which are part of a long term RF design plan. New 3G site – This indicates that this site in the UMTS database is a new site proposed only for the UMTS design/network. These flags is intended to provide the current status of the site being used for the UMTS design. 2. Group - Site Selected for Design Options No Yes This flag is to indicate whether the site is in the UMTS design or not. 3. Group – Design Phase Options N/A 1 2 3 This flag is mainly to track the Phase of the network design/rollout that a given site will fall under. 4. Group – Design Cluster Options N/A 1…50


40 of 115

Typically, markets will be divided into smaller clusters/areas for design assignment to various Engineers. This flag will provide the ability to group sites into such clusters. 5. Group – Site Audit Complete Options No Yes This flag is to indicate whether the physical audit has been completed for this site. 6. Group - Pre-Audit Site Class Options Not considered for Design Considered for Design This flag is primarily for initial nominal designs that markets/Regions may want to do for certain markets. This will provide the ability to track a nominal design. 7. Group – Post-Audit Site Class Options N/A Minor Modifications Major Modifications Challenged Site This flag will provide a class for the work needed to deploy UMTS on a given site. This will be based on inputs from development and construction. N/A will indicate that the site audit is not done yet for this site. 8. Group – UMTS Antenna Configuration Options N/A Separate UMTS antenna Separate UMTS antenna but shared feeder Shared Antenna Shared Antenna and feeder Separate UMTS antenna – This indicates that the site has a separate (radome) UMTS antenna and feeder lines. Separate UMTS antenna but shared feeder – Antenna radome is separate, but the feeder lines are shared between GSM and UMTS. Shared antenna – This indicates that the antenna radome is shared (antenna ports are still separate) between GSM and UMTS. Shared antenna and feeder – This indicates that the antenna radome and antenna ports are both shared between GSM and UMTS. This is the least recommended configuration and should be avoided as much as possible. This flag will provide information on the antenna configuration needed/proposed for a site. This will also be information that will be reliable after the site audit. N/A will mean that the site has not been audited yet.


41 of 115

In addition, the Northeast team has found the need for the following flags at site or sector level. These are example of Regional flags. Site level flags: a. Group – Acceptance Cluster Options N/A 1…50 b. Group – Development Priority Options N/A 1 2 c.

Group – Existing Antenna Type Options N/A UMTS Supported UMTS Not Supported


42 of 115

6. Creating Path loss Predictions: After the network has been configured and all other necessary parameters have been set ,the next step would be to create Pathloss Predictions for all the UMTS cells included in the network. Once created prediction files can be used to create variety of arrays including coverage arrays for visual analysis. The arrays play crucial part in wide range of wizards, such as Traffic Rasters, Neighbor Planner, Scrambling Code planner, Static Analysis and Simulations. Best way to create pathloss prediction files is to use Pathloss Prediction manager. In Asset 3G go to Tools  Pathloss Predictor. The following window appears:

For all macro cells, it is recommended to run predictions for at least 20km. For micro cell / minicell models, a maximum of 2km should be sufficient.. There may be exceptions to these recommendations. Select the option “Sites and Cells in filter” and point to the user filter having all the UMTS cells. All the UMTS cells will appear in the lower pane. In the “Override Object Settings” box check both Radius and Resolution options and specify appropriate values. Set re-prediction Rule as “Only if out of date” and click Start. Pathloss Prediction Manager will start creating pathloss file. Progress can be seen in the status box in the right corner with details on total predictions, completed, elapsed time, estimated time remaining, start time and estimated finish time. When completed close this window and you are ready to create arrays. To create coverage array for best server go to Arrays  Signal Coverage  UMTS Pilot Coverage Wizard and follow the following steps:


43 of 115

Select view and click next:

Check the required filter and click next:


44 of 115

Select the Carrier, Array resolution, check “use only array resolution” and select “Best Server By Pilot”. Click finish. The wizard creates the best server array and display it on the 2D view. This can be saved and use it later for traffic spreading, neighbor list creation or scrambling code planning.


45 of 115

7. Traffic Spreading and Analysis NOTE: SNAP SHOTS ARE FOR EXAMPLE ONLY. ACTUAL VALUES SHOULD BE REFERENCED FROM THE ATTACHED “ASSET 3G SETTINGS” SECTION: 3.8. To run Monte Carlo simulations in Asset3G, it is necessary to have traffic raster files created for each service type and associate it with the terminal type. Traffic spreading strategy and traffic raster file creations are discussed in the following sections.

7.1. Creating Traffic Raster Files Creation of traffic raster for both Internal and Vendor Acceptance will follow the same procedure as described below. For creation of traffic raster, best server array should be in the back ground. For traffic raster, best server creation will not follow the procedure defined above. First run the simulator but do not run the snapshot process; these will cerate a bunch of arrays and one of them will be best server one. Traffic information has been derived by using subscriber projections provided by the FP&A group along with the existing GSM traffic profile. The result has been that we have traffic numbers on a per sector basis for the on-air sites in a given market. Because we are designing a voice centric network, we have converted projections of CS64 and PS users into equivalent voice users by using vendor specific Eb/No values etc. The result is that we are providing a single voice user equivalent value per sector. The goal is to generate a traffic raster and then keep it constant for the entire design process. The recommended method is to generate a traffic raster using all on-air GSM sites and HC approved GSM sites within the UMTS design polygon/area. The UMTS design should then be done to be able to carry that traffic. If additional sites are added, or if sites are removed, the traffic raster should still be kept the same. This will ensure that the target traffic to be carried remains the same throughout the design process. Creating traffic raster involves two steps, first to create Asset3G compatible traffic (.tpc) file and then use traffic wizard to create raster file. The created traffic raster is saved and all the design process is followed from there own. For 2G On-Air sites, where there is no projection information; then for those cases an average traffic will be assigned. The average traffic is calculated from the non missing sectors. This has to satisfy the following condition that the ratio of missing to not missing is less than 5%. Following steps will describe the process: Steps 1-Create a Live Traffic File for each of the four required traffic Rasters. To do this, run a report, based on your planned UMTS sites filter. Reports > Site/Node Report.


46 of 115

This will create a spreadsheet, which looks similar to:

Copy all the cells to another excel sheet and assign traffic with the header as shown below: A example txt file is also embedded at the end of this section.


47 of 115

Save it as tab delimited txt file. When you open the .txt file it should be like:

Close the file and rename it with “ *.tpc ” extension, which is one of the Asset input format. Once the traffic files are ready you can create the Raster file. The traffic Rasters spread the per cell traffic loaded, across the various clutter types, based upon the settings defined in the Terminal Types, as shown below. It is necessary to have a best server by pilot array created, to allow traffic spreading where coverage is present. (Arrays > Signal Coverage > UMTS Pilot Coverage Wizard). To create the traffic arrays, use the Traffic Wizard (Arrays > Traffic > Traffic Wizard) and follow the following steps:


48 of 115

By going to next, a terminal box will appear.


49 of 115

After clicking next, select the best server on which the traffic has to spread. Select the Indoor Best Server Array and spread the traffic to -104 dBm for Internal and -105 dBm for External Acceptance.


50 of 115


51 of 115

This completes the Traffic Raster creation. To save it, go to Arrays Array Manager, select the traffic array and specify the name and destination folder to save it .You can load it using the same menu whenever you need it.

Example Traffic File in text format:

Example Traffic File Text Format

Since an ACP tool will be used in conjunction to the Asset planning tool, it is necessary to bind the traffic inside the design polygon to achieve consistent results between the two tools. Embedded PPT document is showing the process of creating traffic raster which is bounded inside the design polygon. It also includes the methodology to scale traffic for indoor and outdoor rasters.

UMTS\Traffic Spreading within a Polygon.ppt


52 of 115

8. Neighbors Planning NOTE: SNAP SHOTS ARE FOR EXAMPLE ONLY. ACTUAL VALUES SHOULD BE REFERENCED FROM THE ATTACHED “ASSET 3G SETTINGS” SECTION: 3.8. Asset3g enables you to automatically generate neighbor list based on the predicted coverage / cell service areas of the network using Neighbor Wizard. Manual neighbor planning can also be done for more satisfactory results.

GENERAL DESCRIPTION In Asset 3G the algorithm starts its operation by creating a list that contains all the cells that will be neighborplanned (cells that their neighbors will be sought). The 2D view and the filter selection page are responsible for creating the planning list or each cell in this list the algorithm find the cell’s service area. The definition of a service area is the following: ‘All the pixels for which this cell is the best server’. If the cell is of GSM technology, a best server coverage array is used. If the cell is of UMTS technology, its service area is calculated ‘on the fly’. The neighbor planner starts with the first cell on the list. It visits each pixel of its service area and makes a list of all the other cells present in that pixel. A cell is present in a pixel if there is a signal value (strength) for that cell in that pixel. This list depends on the planning option, for instance the ‘GSM to UMTS’ option has been chosen, then the list will contain only the UMTS cells that are neighbor candidates. Apart of the identities of the neighbor candidate cells in each pixel the planner knows also their strengths. This list can have a variable size for each pixel in the service. The ‘maximum number of covering cells’ edit-box in page 3 of the wizards is used at this point to limit the entries in each pixel’s list and keep only the strongest neighbor candidates. So if on a pixel there are 10 cells present and the user uses 8 covering cells then 2 cells (the ones with the lowest power) will be taken out of the list. Using the data mentioned above, the algorithm assigns a neighbor probability weight in each candidate cell in each pixel. The way this probability is assigned depends on the planning option chosen. Using these weights, the algorithm calculates a percentage (%) overlap and an area overlap (km2) for each candidate cell. Only the cells that satisfy the minimum overlapping thresholds (set by the user at stage 3 of the wizard) qualify to stage 2 of the selection process. Stage 2 is controlled by the user who sets the ‘Maximum number of neighboring cells’. If the candidates that made it to stage 2 are more than the maximum number of neighbors allowed, the candidates with the lowest overlapping scores will be rejected until the number of cells equals that set by the user.


53 of 115

ALGORITHM FLOWCHART


54 of 115

Neighbor planning options available in Asset are • • • •

GSM neighbors for GSM cells UMTS neighbors for GSM cells GSM neighbors for UMTS cells UMTS intra-frequency neighbors UMTS inter-frequency neighbors

8.1. UMTS intra-frequency neighbors This option provides the solution to plan intra technology UMTS neighbors. To use Neighbor Wizard first make sure to create a coverage array at the desired resolution. From the Tool menu go to Tools  Neighbors  Neighbor Wizard. Neighbor Wizard window appears.

Select the view, make sure it covers the area that includes all the UMTS cells. Click next:


55 of 115

Parameters

Values

Neighbor planning margin (db)

3

Maximum number of neighboring cells

20 max to start.

Maximum number of covering cells

12

Override propagation model Std Deviation (db)

Un-Checked

Minimum overlapping (%)

10

Minimum overlapping area (km2)

0.05

Make Co-site cell neighbor

“checked”

Resolution for all plans

Same as map data.

Neighbor planning margin (dB): Parameter that is used when handover probability are calculated for each potential candidate. Maximum number of neighboring cells: This parameter limits the number of neighbors for each cell. If it is set to N, then a cell can have up to M ≤ Ν neighbors. Maximum number of covering cells: The algorithm uses this parameter to limit the number of cells that may be potential neighbors. Ec/Io Std Deviation: A lognormal error is inserted in the neighbor planning mechanism in order to account for signal imperfections. The user needs to specify a standard deviation for that error Minimum overlapping (%): For each potential neighbor cell an overlapping percentage is calculated by the planning algorithm. A cell will be considered as a neighbor only if this percentage is greater than


56 of 115

the minimum percentage specified Minimum overlapping area (km2): For each potential neighbor cell an overlapping area is calculated by the planning algorithm. A cell will be considered as a neighbor only if this area is greater than the minimum overlapping area specified Make co-site cells neighbors: Cells that are co-sited with the cell to be planned are made neighbors automatically and do not participate in the planning algorithm. The maximum number of neighboring cells is deduced to N-2 before the calculations start. However, their signal strength data is used when the algorithm calculates handover probability weights for other cells (e.g. in Ec/Io calculations) Select the appropriate resolution and click next:

Check the “Start neighbor analysis after planning” box and click next: Summary dialog window appears:

If satisfied with all settings, click finish. Neighbor Wizard will start running neighbor plan and analysis window will appear when it’s finished.


57 of 115

8.2. GSM to UMTS neighbor cells: At this time, the projects are separate. Future plan is that both GSM and UMTS databases will be merged. Then this feature can be used in Asset. The key in planning GSM to UMTS neighbor is the Ec/Io level. Before you can start doing GSM to UTMS neighbor, make sure that you have GSM sites information in the same project as UMTS. To use Neighbor Wizard first make sure to create a best server coverage array at the desired resolution. To use Neighbor Wizard first make sure to create a coverage array at the desired resolution. Select appropriate filter to be included in the neighbor plan and click next:

Table below shows the values to be defined for these fields. Parameters

Values

Ec/Io thresholds

-12 dB


20 max to start.


12

Minimum Overlapping (%)

10%

Minimum Overlapping area (km2)

unchecked

Ec/Io Std Deviation (dB)

Un-Checked.


“checked”


Same as map data.


58 of 115

Ec/Io threshold: Parameter that is used when handover probability weights are calculated for each potential candidate

8.3. UMTS to GSM cells For planning “GSM neighbors for UMTS” the parameter “GSM signal threshold” plays an important role.

Following parameter shall be used in “step 3 of 5” in Neighbor Planner (part of Neighbor wizard in Asset3g tool. Parameters

Values

GSM Signal Threshold (dBm)

-94


20 max to start.


12

Override propagation model Std Deviation (db)

Un-Checked

Minimum overlapping (%)

10

Minimum overlapping area (km2)

0.05


“checked”


Same as map data.

GSM Signal Threshold (dBm): Parameter that is used when handover probability are calculated for each potential candidate.


59 of 115

Select the filter, all the UMTS cells will appear. Click on any cell to view both inward and outward Neighbors. If we create the neighbor for the first time the list will appear only under “Plan only Neighbors”. To make all relations mutual click “Make Mutual” option. It’s possible to add/delete neighbor here. When satisfied click “Update Database” option to apply the neighbor list to the cells. To view neighbor for a cell expand Neighbor /Exceptions and check “All Neighbors” under Hand Over Neighbors” type.

click “Display Neighbors” from the drop down menu and click on any cell in the 2D view to display it’s Neighbors.


60 of 115

After the automatic neighbor plan has completed, it is advised to do a manual neighbor check. Make sure that the first tire neighbor are being considered. In some areas special case neighbor need to be defined manually also. It’s possible to change the display properties by double clicking “All Neighbor” in the Map information & Control box. Select Network type, Carrier type and check the Intra-frequency box. Click “Set Display” and change line and color settings for inward/outward/mutual Neighbors.

To Save/Load/Delete plan go to Tools  Neighbors dialog and select for the option.


61 of 115

9. Nominal Design NOTE: SNAP SHOTS ARE FOR EXAMPLE ONLY. ACTUAL VALUES SHOULD BE REFERENCED FROM THE ATTACHED “ASSET 3G SETTINGS” SECTION: 3.8. Introduction The idea behind Nominal design is to have a quick method of obtaining an estimate of the network capabilities in any region. It can be used to obtain the best server area per cell plus a Ec/Io of an un-loaded network. .The best practice is to maximize Ec/Io of the design area with out loading the cell with traffic. The target Ec/Io should be -9 db for un-loaded so that when traffic is added, Ec/Io should be around -14 db or better. In the initial rollout process we need to estimate the number of sites which are required to cover a geographical area .The Nominal design gives a rough but very quick estimate of the number of sites required by analyzing coverage area.

9.1. Performing Nominal Design: To carry out a Nominal Design, select Arrays → Simulator → Simulator Wizard. The following wizard will appear:

Select the 2D View area you want to work with. This is necessary because you might have more than one 2D View open. Click Next>


62 of 115

** Box has to be checked as Orthogonality per clutter is used.

Specify the parameters required to conduct the Nominal Design as explained next: Simulation Resolution: The resolution at which the simulation will be carried out in meters. Note: If predictions are not available in the desired resolution then they are converted from the next higher resolution. It is recommended that both traffic arrays and predictions are generated at the same resolution required for the simulation. Also, if a clutter raster is not available at the selected resolution, no per-clutter type parameters will be loaded into the simulator. So all terminals will be considered as outdoors, with no shadow fading and zero speed. Number of Covering Cells: The number of cells that are considered as primary covering cells, handover cells and interferers. Pilot Pollution Threshold: The tool calculates the Pilot Pollution threshold by looking at the Max Ec/Io at a given pixel and subtracting 6 db out of it. Any thing lower than this value is triggered as a polluter. Chip Rate: The chip rate of the system to be simulated. This value is used in combination with the service bit rate to calculate the processing gain for a service. Use Neighbor Lists: Whether Neighbor lists are to be considered in the Analysis. Intra-Site Correlation Coefficient: The correlation between fades (for a terminal) to cells on the same site. Inter-Site Correlation Coefficient: The correlation between fades (for a terminal) to cells on different sites. Cell Loading Parameters: Get Values from Database: Even though the creation of terminal types associated with UMTS services is essential, we can perform a static analysis without having spread any traffic within the analyzed area. In that case two parameters are going to be used to take into account a loaded network: the ‘Downlink Power’ transmitted by the cells, which is used to account for a downlink loading presenting a noise level to the terminals, and the ‘Uplink Noise Rise’, which accounts for an uplink loading presenting a noise level to the cells. These values can be entered in ‘Cell Params’ window of each cell on the Site Database. Calculate the values: In the case of the uplink an initial coverage area is determined using a link budget with the cell noise limit (presented noise) combined with the best server by pilot area array. For the traffic that is captured


63 of 115

under that area, assuming that all is being connected, the received noise at the serving cell is calculated (captured noise). If that amount of noise is higher than the noise rise limit then we can estimate a percentage of users that can be served. In the case of the downlink, similar calculations take place. Write values into the database: Decide whether to write the calculated Cell Loading Parameters into the Site Database. **Note: The Inter-Site and Intra-Site fading correlation coefficients are not used in the calculation of noise rise and DL power on the cell, but they are used during the passive scan stage of Static Analysis. Filter selection Stage:

Select the Filters that you want to include in the analysis. Click Next>


64 of 115

Select the Terminal Types that you wish to be included in the analysis. Click Next>

By clicking next, you should get this warning message saying no traffic raster associated with the terminal. This is showing that it is an unloaded scenario is being ran By clicking okay on this warning message, we should more to the next window-

By clicking next, we should get the next window >


65 of 115

For confirmation on unloaded scenario> we should be getting this warning message in the last window before the finish stage. After clicking the finish button, the simulator will start processing and a window will show up >

At this stage , press close and not the run option.


66 of 115

9.2. Displaying the Nominal Design Results To view the results of the analysis in the 2D-View go to ‘Show Data Types’ and select the ‘Simulator’ option. The results are provided on a ‘Per Service’ and ‘Per Carrier’ basis. The arrays provided on each category are different. Though most of the arrays generated at this stage are the same as those available from the Monte Carlo simulator. On this section we’ll focus on the basic results needed from the Nominal design Some key parameters we can obtain from the ‘Per Service’ arrays are:

9.2.1.

Best Server:

For each pixel, ASSET3g determines which serving cell layer will be the most likely server of a mobile in that pixel. This decision is based on parameters specified in the Site Database window and in the Array Settings dialog box. As with all the arrays, you can change the display properties by double-clicking the array in the list of display types. The colors for the best server array are assigned automatically. You can change the coverage probability threshold so that only pixels with a coverage probability above the threshold will show a best server. You can also change the transparency.


67 of 115

9.2.2.

Pilot Coverage:

The Pilot Coverage array displays the pilot strength in dbm for the selected carrier and is useful when determining pilot interference. This array shows the same information as the Pilot Strength array, but the powers can be grouped into categories of pilot strength. For example, you may want to categories received powers of -95 to -100 dbm to be Rural Outdoor.

9.2.3.

Pilot Ec/Io

Pilot Ec/Io array gives the highest Ec/Io values.


68 of 115

9.3. Generating Statistics from a Nominal Design It is possible to generate a spreadsheet quantifying the level of coverage following a Nominal design. Right click on Map information & Control)→ Simulator-“Array name” → Statistics…

Select the market/cluster polygon and click generate:


69 of 115

Output Result of the Statistics Generator:

Statistics should be generated for all the KPIs mentioned in the section 2.4.1- Nominal Design using Nominal Analysis.


70 of 115

10. Internal Design Process NOTE: SNAP SHOTS ARE FOR EXAMPLE ONLY. ACTUAL VALUES SHOULD BE REFERENCED FROM THE ATTACHED “ASSET 3G SETTINGS” SECTION: 3.8. In the method, a traffic spread is a combination of in-building and out-door users.. The idea behind is that not all the terminals will be in-car all the time. So 60% will be spread In-Building for clutters > Airports, Commercial and High Density Urban and Residential with Trees / Few Trees. As the tool only takes one kind of scenario “In – door “, there a requirement of parameters on the Node B > Cell Parameters plus also on the terminal level.

Terminal Level: On the terminal level, go to Clutter tab and define the values as described in the parameter excel embedded in sec: 4.8.


71 of 115

On the Clutter Parameter Section: The values for In-Door / Out- Door Fading and In-Door Losses are as shown below >

IMP: There is not separate KPI’s for the above two scenarios. All the KPI’s have to be passed on both the cases for acceptance.


72 of 115

11. Vendor Acceptance Design Process NOTE: SNAP SHOTS ARE FOR EXAMPLE ONLY. ACTUAL VALUES SHOULD BE REFERENCED FROM THE ATTACHED “ASSET 3G SETTINGS” SECTION: 3.8. The idea behind this design process is due to the way contract negotiations has been done. For the vendors, the design KPI’s have to be met in a In-car Design of the area . The traffic will be spread keeping in mind that all the users are in- car for using the 3G service. In the terminal section> Clutter Tab> In the In-Building percentage will be 100% as shown below in the pic.

Next is to change the 3G Clutter Parameter under the Configuration menu. Go to Configuration > Clutter Parameters > 3G

By making this change, all the traffic is in-door with a loss if 6db associated with each clutter. By creating this environment, we are going to simulate In- Car service and thus designing for that purpose. To summarize the above, only 2 places the values have to be changed: 1: On the Terminal section> Clutter Tab.


73 of 115

2: Clutter Parameters > 3G Settings.


74 of 115

12. Simulator in ASSET 3G - 5.2 ( Optimal Design Stage) NOTE: SNAP SHOTS ARE FOR EXAMPLE ONLY. ACTUAL VALUES SHOULD BE REFERENCED FROM THE ATTACHED “ASSET 3G SETTINGS” SECTION: 3.8.

12.1. Introduction Traditionally, TDMA/FDMA network planning used statistical analysis and calculated the margins for a tuned propagation model to allow for interference. Gains were applied to allow for the soft handover technique. However, since the level of intra-cell and inter-cell interference varies between cells, this approach gave misleading results in early networks. Thus, in CDMA networks, coverage and cell capacity was too interrelated to be predicted accurately by using a conventional statistical analysis to derive margins and gains. An alternative approach has developed based upon the static and dynamic simulation of networks using Monte Carlo algorithms concept incorporated into ASSET 5.2 simulator. The new Simulator introduced in ASSET3g 5.2 has been developed to achieve: • Efficient memory consumption • Fast creation of snapshots • Detailed and accurate outputs In the simulator, network is analyzed over various instances in time or "snapshots", where User Equipment (UEs) are in statistically determined places. A “Snapshot” does not represent a random distribution of terminals, but rather “the average instant in time for a random distribution of terminals”. The snapshot represents the average instant because all the measure of system load (i.e. UL interference, DL interference, resource usage and throughputs) are time- average. The ability of each terminal to make its connection to the network is calculated through an iterative process. Various failure mechanisms are considered: • Maximum mobile power • Maximum Node B power reached • No available channels • Low pilot SIR or Ec/Io. Flexible analysis of results is based on any user-specified combination (per carrier, per service, per terminal type, per bearer, and so on). The algorithm used in the Simulator has been designed to produce arrays which cover all pixels of the simulated region, and uses a relatively small number of snapshots to satisfy the convergence criteria. You can specify your exact output requirements using the Array Definition Controller dialog box. The Simulator produces only the arrays that you specify, creating them when you select to display them on the Map View. You can make changes to the array definitions at any time. The performance of the network is then analyzed from the results of the snapshots carried out. Dynamic simulation simulates User Equipment (UE) moving through the network in successive time steps. Time can be considered to be split into chips, bit periods or time steps. A mobile list is generated and solved for the first time step. Dynamic simulation is deemed to complex and as taking too long to provide statistically valid results for a practical implementation in a commercial planning tool. Because of these reasons, it is not implemented in Asset3g. Note : If you have used the 5.0 Simulator (and previous versions), you will notice that the process of snapshot creation is much faster in the new Simulator. However, the Map View “Redraw” does take a longer time, owing to the nature of the new algorithm


75 of 115

12.2. Inputs to the simulator: The simulator in Asset3g takes its inputs from the parameters set in the Bearers, Services, Terminal Types and Shadow Fading dialogs. In addition to that, it uses information from the Traffic raster in memory. We will look next at what these inputs are:

12.2.1.

Bearers inputs:

From the Bearers dialog, the simulator takes information such as: UL/DL Bit rate and Control Overhead factor UL/DL Link Eb/No requirements and its speed dependency DL Macro Diversity gains and Maximum transmit power per Bearer UL Power Control Headroom UL Mobile TX power reduction for different speeds UL Average Power Rise gains UL Power Control Headroom gains

12.2.2.

Services inputs:

From the Services dialog, the simulator uses the following information: Whether a Service is PS or CS CS and PS activity factor The Bearers used and their priorities for the Service

12.2.3.

Terminal Types inputs

From the Terminal Types dialog, the simulator takes information such as: The geographical distribution of terminals The % of In Building users for a given clutter type The Mobile Speed distribution for every clutter type The weight of the services provided by a given terminal The mobile terminal parameters such as Max TX power and required Pilot SIR

12.2.4.

Traffic Raster inputs:

The Traffic raster provides the simulator with the following information: Which terminals are to be spread over the geographical area, whether we want to restrict traffic spreading to the areas where coverage exists and the number of terminals to spread?

12.2.5.

Running the Simulator:

To carry out a simulation, select Arrays → Simulator → Simulator Wizard. The following wizard will appear:


76 of 115

Select the 2D View area you want to work with. This is necessary because you might have more than one 2D View open. Click Next>

This box has to checked as Orthogonality / clutter is used.

Here you can set the simulation parameters according to the description shown next: Simulation Resolution: The resolution at which the simulation will be carried out in meters. Note: If predictions are not available in the desired resolution then they are converted from the next higher resolution. It is recommended that both traffic arrays and predictions are generated at the same resolution required for the simulation. Also, if a clutter raster is not available at the selected resolution, no per-clutter type parameters will be loaded into the simulator. So all terminals will be considered as outdoors, with no shadow fading and zero speed. Number of Covering Cells: The number of cells that are considered as primary covering cells, handover cells and interferers.


77 of 115

Pilot Pollution Threshold: Any cell that provides an Ec/Io level higher than the Pilot Pollution Threshold, but is not in the terminal’s active set, is a pilot polluter for the terminal. The simulation provides an output array that shows the average number of pilot polluters on each carrier. Power Control Standard Deviation : The error due to imperfect power control in dB. It is recommended that this parameter is set to zero. This parameter is not used to explicitly model errors in the power control process, but rather to ensure that the simulation results exhibit certain features associated with imperfect power control. The parameter controls the distribution of achieved Eb/No values for successfully served terminals. If the standard deviation is set to zero, the Eb/No value for each successful terminal is achieved perfectly. In a real system this is not the case since imperfect power control produces a (log-normal) distribution of achieved Eb/No values. One consequence of having such a distribution of Eb/No values on the uplink is that a higher noise rise is achieved compared to the case when no distribution of Eb/No values is seen (assuming the same set of users in both cases of course). The simulator implements the effect of power control error by including a log-normal error on the uplink and downlink transmit powers of successfully served terminals. The errors on the uplink and downlink are uncorrelated, and are applied after all other handover gains and margins have been considered. Terminals are never dropped if the resulting error makes them transmit at too high or too low a power. Chip Rate: The chip rate of the system to be simulated. This value is used in combination with the service bit rate to calculate the processing gain for a service. Use Neighbor Lists: Whether Neighbor lists are to be considered in the Analysis. Intra-Site Correlation Coefficient: The correlation between fades (for a terminal) to cells on the same site. Inter-Site Correlation Coefficient : The correlation between fades (for a terminal) to cells on different sites. Go to Next>

Select the Filters that you want to include in the simulation. Click Next>


78 of 115

Select the Terminal Types that you wish to be included in the analysis. Click Next>

The following section describes the parameters in this window: Max. Number of Iterations: This is the maximum number of iterations within one snapshot. If the snapshot has not converged, the snapshot will still finish after this number of iterations. Max. Power Change (%): Maximum Power Change. This is the maximum percentage change in total UL noise power (over all the cells in the simulation) that you would allow to consider the snapshot to be stable. Only Scan Where Traffic Exists: Scan only where there is traffic. Click Next>


79 of 115

****

**** Note: This Warning message will appear if there is no traffic file made using the Traffic Wizard . Move to section 6.0 for traffic raster generation. If Traffic raster had been generated before but not reloaded, then this message will still appear. For those case, follow the procedure below: Go to Arrays > File Array Manager>

This box should come up, in this we see a Traffic Type > Right Click on the traffic > Load 9 As shown below.


80 of 115

Point to the directory where the raster was stored. The raster file should have a

“ **.tri” extension.

On completion of this stage, again move to section 9.0 and the warning message should appear. Below is the summary window which will appear after pressing the finish button.

$$

$$ Note: 15 to 20 snap shots are recommended for a reliable Analysis.


81 of 115

13. Viewing Output Arrays: Two sets of output arrays are generated: ‘Per Service’ arrays and ‘Per Carrier’ arrays. Both may be displayed in the 2D View. Simply select the item you want to display in the Data Types list and double click on it to set the colors that will be used for display. The minimum threshold value for Pilot Strength used by some of the arrays is set in the Array Settings window. These values can be left as set by default, but you can change them as shown next: The Array Settings Window: The Array Settings Window for Asset3g can be accessed under Arrays → Array Settings… It allows a minimum threshold value for pilot strength to be set for the Cell Uplink Load, Best Server by Pilot / Pilot Strength. Furthermore, it allows the settings for the Edge zone width to be set.


82 of 115

13.1.1.

Service Arrays:

Arrays should be generated for each Service type. Following are the examples for Voice service.

13.1.2.

CPICH RSCP:

13.1.3.

Pilot Ec/Io:

Pilot Ec/Io is calculated based on the equations below

Where:


83 of 115

13.1.4.

DL Achieved Bearer:

Dependencies: Terminal, Carrier, Indoor, Service, Speed. The purpose of this Array is to provide a combined coverage plot for down link bearers of a service. The array shows the highest priority down link bearer with acceptable down link coverage, i.e. with DL coverage probability meeting the coverage reliability level specified in Array Settings – Sim Display Settings.


84 of 115

13.1.5.

Achievable UL Bearer: Dependencies:

Terminal, Carrier, Indoor, Service, Speed The purpose of this Array is to provide a combined coverage plot for UP link bearers of a service. The array shows the highest priority UP link bearer with acceptable down link coverage, i.e. with UL coverage probability meeting the coverage reliability level specified in Array Settings – Sim Display Settings.

13.1.6.

DL Coverage Probability:

Dependencies: Terminal, Carrier, Indoor, Service, DL Bearer, Speed. This is the probability of satisfying the downlink bearer Eb/No requirements, assuming that the link powers of cells in the active set are at maximum allowed levels. This probability depends on the standard deviation of shadow fading for the clutter at that pixel. If this standard deviation has been set to zero, then there are only three possible coverage probabilities: 0% if the requirement is not satisfied, 50% if the requirement is satisfied exactly, and 100% if the requirement is exceeded.


85 of 115

13.1.7.

UL Coverage Probability:

Dependencies: Terminal, Carrier, Indoor, Service, UL Bearer, Speed This is the probability of satisfying the UL bearer Eb/No requirements, assuming that the link powers of cells in the active set are at maximum allowed levels.

13.1.8.

DL Iother / Iown:

Dependencies: Carrier This is the total ratio of downlink power received from other cells to down link power received from own cell, where “own cell” is the Best DL Cell (by RSCP).


86 of 115

Summary Report for Simulator 5.2: Go to Arrays > Simulator > Reports:

By choosing this option: Report Generation Dialogue box will open up:

13.1.9.

Design Changes Allowed

The following changes are allowed in the design to met the design KPI’s 1: Electrical Down Tilt – For controlling Pilot polluters or dominance creation, electrical down tilt of the UMTS antenna can be adjusted. 2: Mechanical down tilt can only be adjusted if there is no impact on the GSM side. 3: Azimuth can be changed if site audit indicates if there is flexibility to do so. 4: Pilot powers are fixed as defined in the Parameter sheet and should not be changed. 5: Sector heights cannot be changed.


87 of 115

13.1.10. Defining CS 64 and PS 64 Service. Bearers: Before running any scenarios on the CS / PS service, Bearers need to be set up. To set up and get explanation of the tabs, on the Bearer; follow section 4.5.1 of this document..

Services: For setting up services section, follow section 4.6 of this document.

Terminals: For terminals, follow the section 4.7 of this document.


88 of 115

13.1.11. CPICH RSCP

13.1.12. Pilot Ec /Io:


89 of 115

14.

HSDPA

NOTE: SNAP SHOTS ARE FOR EXAMPLE ONLY. ACTUAL VALUES SHOULD BE REFERENCED FROM THE ATTACHED “ASSET 3G SETTINGS” SECTION: 3.8. High Speed Downlink Packet Access (HSDPA) is an evolution of the WCDMA radio interface for data services, using very similar methods to those employed by EDGE evolution of the GSM radio interface. The higher data rates are achieved by Adaptive Modulation and Coding. The implementation of HSDPA in 3g networks involves the specification of three additional Channels: • High Speed Physical Downlink Shared Channel (HS-PDSCH) • High Speed Shared Control Channel (HS-SCCH) • High Speed Dedicated Physical Control Channel (HS-DPCCH)

14.1. HSDPA Configuration: ASSET3g enables you to define HSDPA related channels by using the UMTS Resources, and also to set a value for Maximum HSDPA Power for each HSDPA enabled cell in the Site Database. In addition, by defining HSDPA coding rates for QPSK and 16QAM modulation schemes, you can model adaptive modulation and coding within the appropriate HSDPA bearer definition.

14.1.1.

Adding and Editing HSDPA Coding Rates:

If you are implementing HSDPA within your network, you must set up HSDPA Coding Rates against one or both of the Modulation Schemes. To do this: From the Configuration menu, point to Lookup Tables and Curves and click HSDPA Coding Rates. In the dialog box that appears, there are initially five default coding rates for each modulation scheme (QPSK and 16QAM). You can edit or remove any of these coding rates, and you can also add your own sets of rates. You can also restore the defaults at any time by clicking the Defaults button.


90 of 115

14.1.2.

Defining Resources for HSDPA:

To define a HSDPA resource ,Go to > Configuration TAB > UMTS Resource

14.1.3.

Creation of HSDPA Bearers:

Go to Configuration Tab > Bearers > UMTS + HSDPA:

Bearer box will open, Added HSDPA bearer into the bearer definition. Recommendation on the name convention is to have the name same as Codec Rate name.


91 of 115

On the Eb/No & Speed Delta Tab, add he Eb/No values corresponding to the Code Rate as specified in the Link budget.

14.1.4.

Defining HSDPA Service:

Define a Service called HSDPA and assign it as Non Real Time ( Packet Switched). On the UMTS UL Bearer Tab, assign a 64K service as shown below:


92 of 115

On the UMTS DL Tab, assign the respected bearer which have been defined in the Bearer section.


93 of 115

14.1.5.

Defining HSDPA Terminal:

Go to Configuration Tab > Terminal Types:

Create an HSDPA terminal in the terminal window:

In the Clutter Tab, input the clutter weighting defined in the Parameter Sheet. On the service tab, assign the HSDPA service created previously-

On the HSDPA TAB, enable HSDPA with the coding Rates:


94 of 115

On the WCDMA Params Tab, put in the corresponding values from the ” Asset Mapped Parameters in Sec : 3.8 – HSDPA Tab”.


95 of 115

14.1.6.

Enabling HSDPA on the Site Level:

In the site database, on the cell parameter tab: Put in the appropriate value for HSDPA Link Power (dbm).

On the HSDPA Tab, activate the entire code rate (QPSK & 16QAM) scheme.

.


96 of 115

14.2. Traffic File Generation for HSDPA: HSDPA design is evolved after the Voice design has been completed and has met the required KPI’s. As HSDPA follows PS64 service area criteria; it is required to restrict traffic spread to -102dBm of CIPCH level. Following the above steps for HSDPA Bearer / Services / Terminal creation / settings, a separate raster has to be created. One user / sector for HSDPA will be added for design with the existing voice load. The TPC file used to create HSDPA raster will have one user per sector for those sectors selected for UMTS design. Create one HSDPA terminals (In-door) with corresponding traffic raster. No scaling factor has to be applied due to one raster creation only. There will be two raster from the Voice Traffic and one raster (Indoor) for HSDPA. All these three raster should be used in the simulation for HSDPA. Follow traffic raster creation method, as specified in Sec 7.1 “Creating Traffic raster File”.

14.3. HSDPA Arrays generation and Analysis: To Generate HSDPA arrays, Please refer to section “12.2.5 Running the simulator”

14.4. Viewing Output Arrays: Achievable DL Bearer - HSDPA


97 of 115

15. Data Transfer to Ericsson for RF Design Review. The outputs to be sent to Ericsson for the RF design verification are the following: •

Map data.

•

Model Tuning Info 1. CW raw data 2. Measurement site info 3. Model tuning Results and Parameters

•

Complete Asset Project 1.

Xml format.

2.

Traffic information (*.tpc and / or *.tri / * .trr)

3.

UMTS and GSM (as needed for inter-RAT verification)

•

Successful Simulations, separate for Speech 1.

Arrays - Best Server, Traffic, Monte Carlo (*.3gr file).

2.

Plots - CPICH RSCP, CPICH Ec/No, SHO Areas

3. Excel format.

Statistics - ASSET Generated Report containing all statistics in

•

Polygons 1. Service Area Polygons for Speech, CS64, PS64 in MapInfo tab format, based on speech simulations. 2.

•

Exemption Area Polygons in MapInfo tab format Equipment Specs

1.

Antenna Patterns for all tilts

2.

Antenna Line Product specs

•

Access to Site Audit Information 1.

Optimization Constrains per cell

2.

Summary spreadsheet from RFDS and Site Audit documentation.


98 of 115

16. Scrambling Code Planning Proper SC planning must be carried out for all WCDMA networks to ensure that all cells within the neighbor definition range are unique. The allocation of the Scrambling Code for the T-Mobile Wireless Network Should follow very closely the guidelines outlined by FSC and will be described in the following section.

16.1. Scrambling Code Groups: The Scrambling Codes allocated for the design sites are defined based on the matrix 8X64. The table below show the 8X 64 matrix on Scrambling Codes.

Scrambling code Planning Sheet.xls

16.2. Scrambling Code planning procedure: Scrambling code planning can be done in two phases. 1: Phase I: Dividing the design area into clusters of 18 sites each and assigning those clusters into color group. 2: Phase II: Assigning Scrambling Code to the clusters and Analysis of the assigned codes in the tool. Phase I: Divide the design area based on clusters with not more than 18 sites a cluster. The picture below gives an idea on the cluster division and groupings. The cluster naming can be based upon color schema or market facilitated names.


99 of 115

Generating Scrambling Code for Groups: After the clusters have been identified with different color groups, the next stage of Scrambling Code assignment and Group / Code generation comes in. Phase II: Creating and Assigning Scrambling Codes in Asset3g Once clusters have been assigned, you can produce a text file with the sites and sector IDs for each color group / clusters. Inside Asset3g, go to Database > Filters and build a filter called eg Red. Go through the wizard until you reach step 4 the dynamic/static choice


100 of 115

The text file should be a simple text file (last entry needs a carriage return ). Once imported, you can repeat for the 5 other colors group / clusters.

Repeating the above procedure, you should be able to generate 5 color filters, example as shown below.


101 of 115

Clusters with color definition.

In the 2D view, you should be able to view all the 5 clusters as shown below:


102 of 115

Using XML for the import: The next step is to assign the scrambling code group. Using Office 2003 Pro!! Export the UMTS-CELL-LIST001.xml specific to the defined cluster filter. Import into excel the UMTS-CELL-LIST001.xml into spreadsheet. When opening this XML file in Excel it will give you warning “The specified XML does not refer to a schema. Excel will create a schema based on the XML source data.” Ignore the message, this will be resolve on the next step.

Above picture is an example of UMTS-CELL-LIST001.xml opened in excel. Delete Columns that are not necessary to make this XML importable back to Asset3G. Leaving only the following columns.

Now using the vlookup method, assign the Scrambling Code Group / Scrambling Code inside this XML from the previously generate method. Save this XML as UMTS-CELL-LIST002.xml. Now import this xml into the tool and using the option of merge and not replace. Go to filter options and display Scrambling code ID and you should be able to see them on the 2D screen.


103 of 115

16.3. Using Scrambling code Planner: Scrambling code planning works best if you have assigned neighbors. If they haven’t been assigned this should not matter if your clusters have 20 sites as you can have a unique code for each cell. Once the schemas and filters have been defined you can use the Scrambling Code Planner to assign your SC’s to sites.

From the tools menu> go to Scrambling Code Wizard.

After checking the 2D view, make sure the site and codes are visible in the Scrambling Code Planner view box. By clicking next :


104 of 115

Check the Cluster / Clusters on which the code plan has to be preformed. By clicking next>

If the project has neighbors defined, check the box “ Consider Neighboring Cell”.

NOTE: make sure that in state column, Read Only is selected. If any other option is selected that the tool will not read the Scrambling assigned by you.


105 of 115

By pressing the Finish, the planner start to analyze the codes assigned by you.

The code screen will display if there where any clashing or broken codes.


106 of 115

17.

UMTS FDD Multi-Carrier Planning

17.1. Introduction ASSET3G allows the modeling of multi-carrier UMTS FDD networks in which each service run on a specific terminal has the choice of connecting to different UMTS carriers. The overflow traffic can be distributed between those different carriers supported by the service. The document describes the key features of multiple UMTS FDD carrier support in ASSET3G. The distribution of load and its prioritization on multiple carriers are thoroughly explained. Additionally, some basic examples are given to further enable the users to comprehend the multiple carrier planning functions.

17.2. UMTS FDD Multi-Carrier Simulation 3GPP defines the UMTS cell as actually a carrier-cell combination and therefore each cell in ASSET3G can be formed of one single carrier. In order to model a multi-carrier cell in the tool, multiple cells under the same Node B have to be defined, with each one formed of a different carrier. During the simulation, the terminals are randomly distributed on the pixels of a selected area. On each terminal many different services may run, each of them supporting different carriers and bearers. Each combination of service, carrier and bearer define a “Connection Scenario”, which can be achieved during each snapshot. In order for the simulator to decide which connection scenario to establish for each service, an ordered list of the various potential scenarios has to be created. It then attempts to achieve each scenario in a descending order, until one of these scenarios is achieved. The list is initially created by defining for each pixel all the potential servers (i.e. “Serving Cells”) of a service, based on their path loss values. For example, if six covering cells are defined, then the list for each pixel contains six cells with the lowest path loss values. Then the serving cells of each service are prioritized based on a highly flexible load distribution algorithm, which takes into account the Load Status of each cell and the Defined by the user Carrier Prioritization. If such prioritization is not defined by the user, then the cells are prioritized based on their Ec/Io values. Finally, the simulator checks the bearer priorities of that service, starting from the DL Bearers and continuing with the UL Bearers. The network parameters, which are taken into account for the establishment of a connection at the ASSET3G simulator, are listed in terms of significance: Cell Load Status •

Carrier prioritization defined by the user

•

Ec/Io if the user chooses not to prioritize

•

DL Bearer priority

•

UL Bearer priority

17.3. Load Status and Distribution 10 Load status is the first parameter which is checked in order to build up the connection scenario list. Each serving UMTS cell obtains a load status based on the traffic and on the DL and UL load thresholds defined. These “Load thresholds” provide a flexible and convenient way of distributing the UMTS load. The load overflow thresholds are defined in terms of downlink (DL) Traffic power and “Noise Rise” as shown below, controlling the DL and UL load respectively. This feature can be deactivated if the thresholds are set very low (i.e. set to Noise Rise threshold to zero for all cells) or very high (higher than the NR limit and the Max DL Power). The rules determining the connection scenario list are:


107 of 115

•

If the primary cell is overloaded then connection to the next server is attempted.

•

If a UMTS serving cell is found overloaded, then all the UMTS servers on the same carrier obtain an “overloaded” load status.

•

All over-loaded cells are pushed to the end of the connection scenario list.

•

When a terminal fails to connect to all non-loaded servers, only then the rest of the potential overloaded servers are tested.

Load Control Thresholds.

20 Load control thresholds values define the traffic movement between each carrier. The suggested values at present are: DL Traffic Power (dBm) = 46 Noise Rise (db)

=6

(Same as Node B level).

17.4. Carrier Prioritization Defined by the User After taking into account the Load Status of each serving cell, as described before, the simulator checks the prioritization of the carriers defined by the user. This user prioritization is optional and is done by using the up and down arrows, while defining the “Services” as shown below. As a result, a cell of a higher priority carrier precedes a cell of a lower priority carrier in the list of potential servers, even if it does not have the best signal power or SNR, as long as the cell is not overloaded. If the user chooses not to prioritize the carriers, the “Ignore Priorities” checkbox has to be selected (figure 3) and the tool prioritizes them, based on the highest Ec/Io. The “Prioritize 3G”, “Prioritize 2G” buttons have no effect, as it only takes effect if one of carrier is defined as “2G” and the load distribution is done between them. This document is solely dealing with two carriers each having “3G” service defined.


108 of 115

Priority Assignment.

To be ignored.

17.5. Setup for 2nd Carrier Planning Project set up in Asset requires duplication of the sectors under a Node B, as shown in the example below.

The addition of the new sectors “ D”, “E”,”F” should have exactly the same configuration as sectors “A”,”B”,”C”.


109 of 115

17.5.1.

Equipment Type Settings

On the Equipment tab Go to > Node B Type

Turn on the “Overflow Control” settings under “Load Control” Tab, as shown in the pic above.

17.5.2.

Site Database Settings

After creation of duplicate sectors for 2 carrier assignment , a sanity check for errors is recommended in the site database. • Antenna Tab :

Check if you can see total 6 antennas with all the related values populated; same as the number of sectors created in the Antenna configuration box. • Carrier Tab :


110 of 115

Check if the 2 carriers are showing up in the carrier tab. It is recommended to randomly sample sectors for error check. • Resources Tab :

• Antenna Tab : On the sector level > Antenna Tab

Check for antenna assignment to correct sectors under a Node B. • Cell Parameters Tab:

Check on the sector cell parameters level on 2nd carrier assignment for respective new added sectors. •

HSDPA Tab :


111 of 115

On the HSDPA tab in the sector level, using Global Edit activate HSDPA and activate the correct HSDPA code per sector. • Load and Power Control

The overflow control thresholds values have to be populated for each carrier. The value specified in “ DL traffic Power (dBm) “ and “ Noise Rise (dB)” connection on each carrier. Recommend value for carrier 1 -

DL Traffic Power (dBm) = 46 Noise Rise (dB) = 6.

Recommend value for Carrier 2 -

DL Traffic Power (dBm) = 46 Noise Rise (dB) = 6.

17.5.3.

Service Assignment

Second carrier can be used for designing multiple scenarios, below are few examples 1: Circuit Switched (CS) Voice on Carrier 1 and HSDPA on Carrier 2. 2: Circuit Switched (CS) Voice on Carrier 1, 2 and HSDPA on Carrier 2. 3: Circuited Switched (CS) Voice on Carrier 1 and PS / HSDPA on Carrier 2. To design any one of these scenarios requires a small modification change in the service type settings. Case 2 “CS voice on carrier 1, 2 and HSDPA on carrier 2” will be shown as example below.


112 of 115

Service Type Settings: For designing CS Voice on carrier 1, 2 and HSDPA on carrier 2; Go to > Configurations > Services > “ CS Voice Service”

Assign carriers two in the supported section, For Carrier 1 settings >

For Carrier 2 > UMTS UL Bearer:

UTMS DL Bearer


113 of 115

HSDPA Service definition for 2nd Carrier:

Assign 2nd Carrier in the “ Carriers / Cell Layers” in HSDPA service.

On the UMTS UL Bearer tab under the services, assign bearers for UL HSDPA service.


114 of 115

On the UMTS DL Bearer tab under the services, assign bearers for DL HSDPA service. Assignment priority for DL HSDPA bearer is from the highest data rate to the lowest data rate.

Terminal Types CS Voice_Multi-carrier:

HSDPA_Multi-Carrier:

On the terminal level, HSDPA settings have to be enabled. Simulation of 2nd carrier is follows the same procedures described from sec: 11.0 onwards.


115 of 115

UMTS RF Design Using Asset 3G

Recommend Documents