122761800-Ericsson-Field-Guide-for-Utran.pdf

(1)

ND-00150

ND-00150 AT&T CONFIDENTIAL & AT&T CONFIDENTIAL & PROPRIETARYPROPRIETARY Page Page 1 1 of of 170170 Rev.

V

ol

ume I

I –

E

ri

css

on

F

ield

G

ui

de for

UTRAN P3: Feature Parameters and Best

Practices

Netwo

Network

rk Servic

Servic es

es Docu

Document

ment :

: ND-

ND-001

00150

50 Rev. 3.0

Rev.

3.0 09/0

09/09/20

9/2007

07 Overview

Overview

Volume II of the Ericsson Fiel

Volume II of the Ericsson Fiel d Guide for UTRAN defines AT&T’s accepted d Guide for UTRAN defines AT&T’s accepted practices for optimization ofpractices for optimization of the Radio Access portion of the

the Radio Access portion of the UMTS network for Ericsson WRAN P5MD patch level P5.0.14 (Phase IIUMTS network for Ericsson WRAN P5MD patch level P5.0.14 (Phase II FOA exited August 23

FOA exited August 23rdrd, 2007). , 2007). The algorithms by which subscrThe algorithms by which subscriber devices interact with the netiber devices interact with the network arework are described in detail.

described in detail. Recommendations are provided Recommendations are provided that produce the best perfthat produce the best performance in the network formance in the network foror each type of interaction.

each type of interaction.

This Field Guide is composed of 11 sections which include descriptions of: This Field Guide is composed of 11 sections which include descriptions of:

•

• New features New features released in the released in the most recent RNS most recent RNS software version.software version. •

• WCDMA WCDMA design conceptdesign concepts and s and measurement measurement fundamentals.fundamentals. •

• A chronological stA chronological step by step ep by step description of how description of how the subscriber device and the subscriber device and network interact. network interact. Idle Mode, Idle Mode, CallCall

Establishment and Connected Mode are introduced and the algorithms associated with each are described and Establishment and Connected Mode are introduced and the algorithms associated with each are described and the involved parameters are explained.

the involved parameters are explained.

•

• OSS OSS access procedures access procedures and metand methods.hods.

The document concludes with an index

The document concludes with an index and tables wherein all configurable and tables wherein all configurable parameters and supportingparameters and supporting details are listed along with a list of well deserved credits.

details are listed along with a list of well deserved credits.

IMPORTANT:

This document is the result of an

This document is the result of an ongoing collaborative effort between

ongoing collaborative effort between

AT&T Market, Regional, National and Erics

AT&T Market, Regional, National and Ericsson staff and management.

son staff and management. It will continue to

It will continue to

be updated with the latest findings in the areas of optimization and vendor improvement

through the use of Field Studies and successive vendor software and hardware updates.

(2)

Figures

Figure 1: Slot and Frame Structure... 22

Figure 2: Power Ramping on RACH ... 29

Figure 3: RRC Connection Signaling Flow ... 30

Figure 4: Downlink DPCCH Power ... 32

Figure 5: Admission Control (Radio Link Request)... 40

Figure 6: Admission Control (DL Channelization)... 41

Figure 7: Admission Control (Spreading Factor Usage) ... 43

(6)

Figure 9: Admission Control (Uplink ASE Utilization) ... 46

Figure 10: Admission Control (Downlink ASE Utilization)... 47

Figure 11: Admission Control (Uplink Hardware Utilization)... 48

Figure 12: Admission Control (Downlink Hardware Utilization) ... 49

Figure 13: Event 1a Trigger ... 54

Figure 14: Event 1b Trigger ... 55

Figure 15: Event 1c Trigger... 56

Figure 16: Event 1d Trigger ... 57

Figure 17: Event 2d Trigger (Begin Compressed Mode)... 59

Figure 18: Event 2f Trigger (Cease Compressed Mode)... 60

Figure 19: Event 6d Trigger (Begin Compressed Mode)... 61

Figure 20: Event 6b Trigger (Cease Compressed Mode)... 62

Figure 21: Event 3a (EcNo)... 64

Figure 22: Event 3a (RSCP) ... 65

Figure 23: Event 3a (UE Tx) ... 66

Figure 24: Event 2b (EcNo)... 67

Figure 25: Event 2b (RSCP) ... 68

Figure 26: Event 2b (UE Tx) ... 69

Figure 27: Event 1d HS (HS Cell Change) ... 70

Figure 28: Dedicated (DCH/DCH) to Common Down-Switch... 73

Figure 29: HS (DCH/HS or EUL/HS) to Common Down-Switch... 74

Figure 30: Common to Dedicated (DCH/DCH, DCH/HS or EUL/HS) Up-Switch ... 75

Figure 31: Common to URA_PCH Down-Switch... 76

Figure 32: URA_PCH to Idle Mode Down-Switch... 77

Figure 33: Throughput triggered DCH to DCH Down-Switch (Downlink) ... 78

Figure 34: Throughput triggered DCH to DCH Down-Switch (Uplink) ... 79

Figure 35: Code Power check for Up-Switch (Downlink)... 80

Figure 36: Code Power check for Up-Switch (Downlink)... 81

Figure 37: Throughput Triggered Up-Switch (Uplink) ... 82

Figure 38: Covered Triggered Ded. to Ded. Down-Switch ... 83

Figure 39: Throughput Triggered Down-Switch (Multi-RAB) ... 84

Figure 40: Throughput Triggered Up-Switch (Multi-RAB)... 85

Figure 41: Throughput Triggered Down-Switch (2xPSMulti-RAB)... 86

Figure 42: Congestion Detection (Downlink) ... 89

Figure 43: Congestion Detection (Uplink) ... 90

Figure 44: OSS Connectivity... 98

Tables

Table 1: Operating Bands ... 13

Table 2: UARFCN List for Bands II and V (“Additional Channels” method) ... 14

(7)

Table 4: UE Categories (HSDPA)... 15

Table 5: UE Categories (EUL) ... 16

Table 6: Link Budget ... 16

Table 6: Master Information Block (MIB) Contents... 24

Table 7: System Information Block 1 (SIB 1) Contents ... 24

Table 8: System Information Block 3 (SIB 3)... 25

Table 13: Air Speech Equivalents (ASE) ... 44

Table 14: Maximum Bit Rates per Radio Link... 92

Table 15: UeRc, RAB and UeRcTrCh Identification ... 95

Table 16: blerQualityTarget values ... 96

Table 17: Configuration Management Access Procedures ... 99

Table 18: Counter Activation... 105

(8)

Document Revision History

This table identifies content revisions made to this document.

Date Rev Revision Descriptio n Writer Sponsor

11/01/2005 1.0 Release version Michael

Noah

Adnan Naqvi 11/28/2005 1.1 Updates to “Cingular Recommended” parameter values

based upon Field Optimization.

Michael Noah

Greg Scharosch 05/01/2006 2.0 Updates based upon Cingular P2 (Ericsson P5ED) FOA as

well as results from Field Studies

Michael Noah

Greg Scharosch 01/25/2007 2.1 Content extended – version not published. Michael

Noah

Greg Scharosch 03/30/2007 2.2 Moved to new AT&T template. Incorporated all existing

Field Guide Alerts.

Michael Noah

Greg Scharosch 09/09/2007 3.0 Updated for AT&T P3 Phase II (Ericsson P5MD P5.0.14) Michael

Noah

Somesh Razdan

RACI

This table identifies RACI team members.

Acc ou nt abl e Respon sibl e Con sult ed Infor med Somesh Razdan Michael Noah Market Engineering Mike Pietropola

Regional Engineering Eric Parker Regional OSS Support Adnan Naqvi National Field Support John Dapper Strategic Planning

National Quality Ericsson Support

For details see Consulted_List

(9)

1. Abo ut This Document

This section includes information about this document.

1.1

Purpose

The primary intention of this document is to serve as a common point o f understanding and reference. This volume includes recommendations for all configurable RNC and Node B parameters. The

recommendations made within this document are the result of collaborative efforts between all groups involved (see 1.3).

1.2

Scope

This document is mainly based upon Ericsson’s UTRAN implementation, focusing on the interaction between the User Equipment and UTRAN. For completeness, some facets of the Core Network are included, e.g. Paging, Routing and Location Area Update procedures, i.e. non-access stratum.

1.3

Audi ence

The audience for this document includes AT&T Market, Region and National Engineers and Technicians responsible for Ericsson UTRAN Optimization and Maintenance.

1.4

Acro nyms and Terms

All acronyms and terms are fully spelled out within the document.

1.6

Trademarks

The trademarks used in this document are the property of their respective owners.

1.7

Conventions

The following conventions are used throughout this document:

• The term “call” refers to any type of user plane connection between UE and the Core Network. It is not specific to

voice or data - UE originated or terminated. It specifically does not include any type of signaling used to support the communication of user information.

(10)

• The term “function” refers to Ericsson’s implementation of a certain portion of the 3GPP specification. A function is

limited to satisfying a specific action taken by either the network or UE. For example, the process of originating a call is referred to as a function. Once the call has been originated, handing the call over is considered a function and ending the call is a function. Within this document, parameters are explained relative to the functions they support.

• Each Operator Configurable Parameter expressed in bolditalic. Brackets enclose the Configurable Parameter’s

Level (RNC, Cell, etc.), AT&T Default Value, Units and Class (Policy, Rule, Fixed, Variable).

• Each Operator Configurable Paramter exists within a specifi Managed Opject Class (MOC). The Managed Object

Class will be specified only for parameters that exist within multiple Managed Object Classes. For example, qOffset1sn is a parameter that can be set differently for Intra-Frequency (UtranRelation) and Inter-RAT

(GsmRelation) neighbors. The parameter instances are therefore denoted as qOffset1sn(UtranRelation) [Nabr, 0, dB, Fixed] and qOffset1sn(GsmRelation) [Nabr, 7, dB, Fixed].

• All references to Radio Access Bearers (RABs) are denoted as UL/DL where UL is the Uplink RLC Data rate in

kilobits per second and DL is the Downlink Data rate in kilobits per second.

• The term “R99” is used to denote all CELL_DCH Radio Access Bearers referring to the release of the specification

that only supported Dedicated Channels (DCH). The term DCH/HS is used to denote HSDPA capability where the Uplink uses an R99 Radio Access Bearer. The terms EUL/HS or HSPA is used to denote the HSUPA / HSDPA capability.

• Some configurable parameters include an “(sho)” or an “(hho)” suffix. This suffix is used to specify a subset of

cells to which the parameter recommendation applies. The sho vs. hho distinction is as follows:

• (hho). The parameter recommendation is specific to UEs that might have no alternative to performing a Hard

Inter-RAT or Inter-Frequency Handover in order to maintain the call.

• (sho). The parameter recommendation is specific to cells that have Intra-Frequency overlap with other 3G

cells. Inter-RAT or Inter-Frequency Hard Handover is not normally needed to maintain the call.

• For example, usedFreqThresh2dRscp(hho) [Cell, -106 ±4, dBm, Fixed] is used to indicate the recommended

value of -106 dBm ±4dB is specific to cells that meet the “hho” distinction.

• The terms “Core” and “Border”

• Border Cell: Any 3G cell where the antenna orientation points out of a launch cluster or polygon into the 2G

network. With respect to IRAT terminology, these sectors are considered (hho) sectors.

• Core Cell: 3G cells within the UMTS polygon that do not qualify as Border Cells. These cells can be designated

as (sho) or (hho) if there are Inter-Frequency borders within the Core. Ideally, there should not be any Inter-RAT borders within the Core.

1.8

Contacts

For questions or comments about this document's technical content o r to request changes to the document, contact:

Michael Noah, Sr. System Engineer – National Field Support Desk: 425 580 6716

Wireless: 425 580 6716 E-mail: [email protected]

(11)

2. New Featur es in P3 (WRAN P5MD Phase II)

This section provides a summary of updates AT&T has elected to implement within this version of RNS software.

2.1

Idle Mode

2.1.1

URA_PCH

The URA_PCH State is now available to all UEs. The URA_PCH State allows the RNS to maintain the location of the UE within the RNC thereby reducing the Routing Area Update load on the SGSN.

2.1.2

Introd ucit on of CELL_FACH State for HS capable UEs

The CELL_FACH State is now available to HS capable UEs. Before P5MD, CELL_FACH was only available to R99 only UEs.

2.2

Call Establishment

2.2.1

2xPS Radio A ccess Bearers

UEs that are able to support multipl e Interactive / Background R99 Data RABs are now supported.

Speech + 2 Data RABs is also supported. For example, you can now use Video Share on your Samsung A707 while it is teathered to your laptop.

2.2.2

Enhanced Uplin k (EUL) or HSUPA

Ericsson P5MD introduces Enhanced Uplink (EUL) or HSUPA as specificed in Release 6 of the 3GPP specification. Enhanced Uplink (EUL) is much like HSDPA in that it allows for greater throughput and capacity through Link Adaptation. Unlike HSDPA however, EUL does use Macro Diversity and Inner Loop Power Contorl in the Uplink.

2.3

Mobility and Connection Management

2.3.1

Introduction of additional R99 RABs

In P5MD, R99 Radio Access Bearers include 64, 128 and 384 on both the Uplink and Downlink. All Uplink/Downlink combinations are now supporteded.

(12)

2.3.2

Event 6a has been replaced wit h Event 6d

If the UE transmitted power is at maximum for a time equal to timeToTrigger6d , then event 6d occurs and the UE is commanded to do Compressed Mode measurements.

2.3.3

Code Division Multiplexing for HSDPA

Cells can now support up to 15 High Speed Physical Downlink Shared CHannels (HS-PDSCH).

2.3.4

hoTypeDrncB and1-17 has been replaced wit h defaultHoType

In P5MD, the Serving RNC determines if UEs will measure Inter-RAT or Inter-Frequency for UEs served by a Drift RNC by using the defaultHoType [Cell, 1=GSM_PREFERRED, String, Fixed] parameter which is uarfcnDl [Cell, N/A, Integer, Variable] specific instead of band specific.

2.3.5

Calculation of maxDlPowerCapability

In P5ED, the configurable parameter maximumTransmissionPower [Cell, 400, 0.1dBm, Var.] which sets the maximum power (downlink capacity) available in the cell at the Reference Point (antenna connector) was used for Admission Control.

In P5MD, the minimum value of either maximumTransmissionPower [Cell, 400, 0.1dBm, Var.] or

maxDlPowerCapability (a value calculated by the Node B at the Reference Point and sent to the RNC) is used for Admission Control.

2.3.6

Throughput triggered Dedicated to Dedicated Up and Down-Switch (Uplink and Downlink)

Throughput based Down-Switch for all R99 RABs on the Uplink and Downlink is now supported.

2.4

OSS Related Functionality

2.4.1

Neighbor List Prioritization

It is now possible to re-order neighbor lists without having to remove and re-enter them. This is accomplished through a new neighbor indexing capability.

(13)

3. Signifi cant KPI Impact Parameters

Each parameter within this document will to a certain degree impact Key Performance Indicators (KPI). The following sections describes functions, e.g. Call Establishment, Handover, etc. that have the most impact on KPIs.

3.1

Accessi bili ty

5.1.2.2 Camping on a Suitable Cell

5.1.3.1 Attach Procedure - RACH Ramping and Initial DCH Power Algorithms and P arameters

5.2.2.2 Admission Control

5.3.2 Cell Reselection in Idle Mode or CELL_FACH

3.2

Retainability

5.3.3 Handover in Connected Mode (CELL_DCH) – Intra-Frequency

3.3

Quality

5.3.9 Downlink and Uplink Power Control

3.4

Throughput and Latency

5.1.3.1 Attach Procedure - RACH Ramping and Initial DCH Power Algorithms and P arameters

5.2.2.2 Admission Control

(14)

4. Desig n Criteri a

This section mainly covers areas specified in the 3GPP standard. It presents an overview of the

spectrum allocation, UARFCN designation and UE Power Class. A fundamental Link Budget is provided. The rest of the section provides a high level optimization concept for WCDMA including Pilot Pollution optimization, neighbor designation guidelines, and a detailed description of the fundamental W-CDMA measurements CPICH RSCP and CPICH Ec/No.

4.1

UE Capabilities

Multiband support for the United States (800/1900 MHz) was not defined until Release 6 of the 3GPP specification. For this reason, Release 6 is the reference for this section.

4.1.1

Frequency Bands

The frequency bands specified are shown in the table below including the separation (in MHz) between uplink and downlink frequencies. AT&T operates UMTS at 800 MHz (Band V) and 1900 MHz (Band II). The rest of the bands listed are included for completeness.

Table 1: Operating Bands

Operating Band UL Frequencies DL Frequencies TX-RX Separation

I 1920 – 1980 MHz 2110 – 2170 MHz 190 MHz II 1850 – 1910 MHz 1930 – 1990 MHz 80 MHz III 1710 – 1785 MHz 1805 – 1880 MHz 95 MHz IV 1710 – 1755 MHz 2110 – 2155 MHz 400 MHz V 824 – 849 MHz 869 – 894 MHz 45 MHz VI 830 – 840 MHz 875 – 885 MHz 45 MHz

4.1.2

Channel Numbering Scheme (UARFCN)

The UTRA Absolute Radio Frequency Channel Number allows easy reference to the spectrum allocated to UMTS. Distinct UARFCNs are used for uplink and downlink frequencies as opposed to a single UARFCN for a pair of UL/DL frequencies. The UARFCN for the downlink is controlled through uarfcnDl [Cell, N/A, Integer, Variable] and the uplink UARFCN is controlled through uarfcnUl [Cell, N/A, Integer, Variable]. A UARFCN occupies 5 MHz of spectrum.

The specification allows for two methods to be used to associate center carrier frequency to UARFCN.

• “ General” UARFCN method. Each UARFCN is defined with a specific center frequency. Beginning at 0 Hz, the

UARFCN is incremented by 1 with each increment in frequency of 200 kHz. The UARFCN corresponding to the center frequency is calculated by finding the product of 5 and the center frequency (in MHz); i.e. UARFCN = 5 * Frequency (MHz). When using the “general” method, this formula applies regardless of direction (uplink / downlink) and band.

• “ Additional Channels” UARFCN method. The “Additional Channels” are specified according to the table below.

(15)

Rev. 3.0 09/09/2007 Use pursuant to Company instructions © 2007 AT&T calculated by finding the product of 5 and the center carrier frequency (in MHz) minus 18 50.1 MHz, i.e UARFCN = 5 * (Frequency in MHz – 1850.1 MHz). For Band V, the UARFCN is calculated by finding the product of 5 and the center carrier frequency (in MHz) minus 670.1 MHz, i.e UARFCN = 5 * (Frequency in MHz – 670.1 MHz).

Either the “General” or “Additional Channels” method can be used to designate UARFCNs based upon where you choose to locate UMTS within your licensed spectrum.

Table 2: UARFCN List for Bands II and V (“ Addition al Channels” method) UL UARFCN UL Center Frequency (MHz) DL UARFCN DL Center Frequency (MHz) PCS / Cellular Band 12 1852.5 412 1932.5 PCS – A 37 1857.5 437 1937.5 PCS – A 62 1862.5 462 1942.5 PCS – A 87 1867.5 487 1947.5 PCS – D 112 1872.5 512 1952.5 PCS – B 137 1877.5 537 1957.5 PCS – B 162 1882.5 562 1962.5 PCS – B 187 1887.5 587 1967.5 PCS – E 212 1892.5 612 1972.5 PCS – F 237 1897.5 637 1977.5 PCS – C3 262 1902.5 662 1982.5 PCS – C4 287 1907.5 687 1987.5 PCS – C5 782 826.5 1007 871.5 Cellular – A 787 827.5 1012 872.5 Cellular – A 807 831.5 1032 876.5 Cellular – A 812 832.5 1037 877.5 Cellular – A 837 837.5 1062 882.5 Cellular – B 862 842.5 1087 887.5 Cellular – B

4.1.3

Power Classes

The table below indicates the UE Power Classes specified as of Release 6. Note the maximum power is the same for all bands within Power Classes 3 and 4. The power in dBm refers to the maximum total output capability of the UE at the antenna connector and not to the maximum power output of any particular Physical Channel.

(16)

Table 3: UE Power Classes

Power Class 1 Power Class 2 Power Class 3 Power Class 4 Operating Band Power (dBm) Tol (dB) Power (dBm) Tol (dB) Power (dBm) Tol (dB) Power (dBm) Tol (dB) I +33 +1/-3 +27 +1/-3 +24 +1/-3 +21 +2/-2 II - - - - +24 +1/-3 +21 +2/-2 III - - - - +24 +1/-3 +21 +2/-2 IV - - - - +24 +1/-3 +21 +2/-2 V - - - - +24 +1/-3 +21 +2/-2 VI - - - - +24 +1/-3 +21 +2/-2

4.1.4

UE Catego ry (HSDPA and EUL)

HSDPA capable UEs are further categorized based upon their throughput capabilities. The table below includes all of the UE Categories as defined in the 3GPP Specification. Note that Category 11 and 12 UEs only support QPSK. If supportOf16qam [Cell, 1=TRUE, Integer, Fixed] is set to 1=TRUE, then 16QAM is allowed and all categories of UE shown below are supported.

Table 4: UE Categor ies (HSDPA) HS-DSCH Category Maximum number of HS-DSCH codes received Minimum inter-TTI interval

Maximum number of b its of an HS-DSCH transpo rt block received within an

HS-DSCH TTI

Total number of soft channel bits Category 1 5 3 7298 19200 Category 2 5 3 7298 2889 Category 3 5 2 7298 2880 Category 4 5 2 7298 38400 Category 5 5 1 7298 57600 Category 6 5 1 7298 67200 Category 7 10 1 14411 115200 Category 8 10 1 14411 134400 Category 9 15 1 20251 172800 Category 10 15 1 27952 172800 Category 11 5 2 3630 QPSK Only 14400 Category 12 5 1 3630 QPSK Only 28800

EUL capable UEs are categorized based upon their throughput capabilities. The table below includes all of the UE Categories as defined in the 3GPP Specification. The initial UEs in the market are EUL

(17)

Volume

ND-00150

Table 5: : UE UE CategorCategor ies (EUies (EUL)L) E-D

E-DCH CH Category Category Maximum Maximum numbernumber of E-DPDCH codes of E-DPDCH codes and SF and SF Support for Support for 1010msms and/or

and/or 2ms TTI2ms TTI

Layer 1 Peak Rate/s Layer 1 Peak Rate/s

(10ms TTI) (10ms TTI)

Layer 1 Peak Rate/s Layer 1 Peak Rate/s

(2ms TTI) (2ms TTI) Category

Category 1 1 One One SF4 SF4 10ms 10ms only only 730kb 730kb --Category 2

Category 2 Two Two SF4 SF4 Both Both 1.46mb 1.46mb 1.46mb1.46mb Category

Category 3 3 Two Two SF4 SF4 10ms 10ms only only 1.46mb 1.46mb --Category 4

Category 4 Two Two SF4 SF4 Both Both 2.0mb 2.0mb 2.92mb2.92mb Category

Category 5 5 Two Two SF4 SF4 10ms 10ms only only 2.0mb 2.0mb --Category 6

Category 6 Four Four (2SF2+2SF4) (2SF2+2SF4) Both Both 2.0mb 2.0mb 5.76mb5.76mb

4.2

Link Budget

In this simple presentation of the li

In this simple presentation of the li nk budget, only the maximum transmit power and nk budget, only the maximum transmit power and receive sensitivity ofreceive sensitivity of the Node B and UE at

the Node B and UE at their respective antenna connectors is their respective antenna connectors is considered. considered. The difference between tThe difference between thehe maximum transmit power of one node and the maximum receive

maximum transmit power of one node and the maximum receive sensitivity at the other node issensitivity at the other node is considered to be the maximum allow

considered to be the maximum allowable path loss. able path loss. The resulting uplink and downlink path losses The resulting uplink and downlink path losses areare compared resulting in a difference in dB between the uplink and downlink maximum path losses. compared resulting in a difference in dB between the uplink and downlink maximum path losses.

Ta

Table ble 6: 6: Link BudgetLink Budget Downlin

Downlin k k Value Value NotesNotes

Max

Max Tx Tx Power Power (dBm) (dBm) +30 +30 Manually Manually calculated calculated (balanced) (balanced) Node Node B B Tx Tx Pwr.Pwr. Max Rx Sensitivity (dBm)

Max Rx Sensitivity (dBm) -115 -115 Specification based Specification based UE UE Rx Rx level level at at 0.1% 0.1% BLER.BLER. Max

Max path path loss loss (dB) (dB) 145 145 Difference Difference between between Node Node B B Tx Tx and and UE UE Rx Rx Sens.Sens. Uplink

Uplink Max

Max Tx Tx Power Power (dBm) (dBm) +24 +24 Max Max Tx Tx Power Power for for a a Power Power Class Class 3 3 UE.UE. Max Rx Sensitivity (dBm)

Max Rx Sensitivity (dBm) -121 -121 Specification based Specification based Node Node B B Rx Rx level level at at 0.1% 0.1% BLER.BLER. Max

Max path path loss loss (dB) (dB) 145 145 Difference Difference between between UE UE Tx Tx and and Node Node B B Rx Rx SensSens Difference

Difference (dB) (dB) 0 0 Difference Difference between between UL UL and and DL DL path path losseslosses The only non-specified value is “Max Tx Powe

The only non-specified value is “Max Tx Power (dBm)” for the r (dBm)” for the Downlink. Downlink. This value was chosenThis value was chosen specifically because it balances the Uplink and Downlink path losses.

specifically because it balances the Uplink and Downlink path losses.

A complete Link Budget analysis would include variables such

A complete Link Budget analysis would include variables such as LNA existence, various Radio as LNA existence, various Radio AccessAccess Bearers due to their difference

Bearers due to their difference in gain as a function of Spreading Factor in gain as a function of Spreading Factor (a description of (a description of SpreadingSpreading Factor is provided in the

Factor is provided in the Measurement Fundamentals section), cable loss, Antenna and Macro DiversityMeasurement Fundamentals section), cable loss, Antenna and Macro Diversity (a description of Macro Diversity is provided

(18)

4.3

Basic Design

Basic Design Re

Requirements

quirements

This section describes fundamental design guidelines that

This section describes fundamental design guidelines that are required for basic syare required for basic system operation. stem operation. It isIt is strongly suggested that these basic requirements be satisfied

strongly suggested that these basic requirements be satisfied before further optimization of the radiobefore further optimization of the radio network is pursued.

network is pursued.

For example, if this were an FDMA/TDMA network such as

For example, if this were an FDMA/TDMA network such as GSM or IS-136, frequency planning would beGSM or IS-136, frequency planning would be included in this section.

included in this section. However, since frequencHowever, since frequency reuse is not a primary consy reuse is not a primary consideration in WCDMA, it isideration in WCDMA, it is not included.

not included.

4.3.1

Pilot PollutionPilot Pollution

Since the basis of WCDMA is to allow for multiple access based upon code division instead of frequency Since the basis of WCDMA is to allow for multiple access based upon code division instead of frequency division, care must be taken t

division, care must be taken to manage over-propagation of cells in o manage over-propagation of cells in the network. the network. As mentioned later inAs mentioned later in the Neighbor List Determination section, all cells

the Neighbor List Determination section, all cells that provide coverage in a that provide coverage in a given geographic area mustgiven geographic area must be neighbors; else they are seen

be neighbors; else they are seen as noise. as noise. An over-propagating cell would therefore An over-propagating cell would therefore need to haveneed to have neighbor relationships with all cells with w

neighbor relationships with all cells with which it overlaps. hich it overlaps. This of course would mean tThis of course would mean the over-he over-propagating cell would be heavily utilized and would require a very large capacity.

propagating cell would be heavily utilized and would require a very large capacity.

Over-propagating cells also cause C

Over-propagating cells also cause Call Establishment problems. all Establishment problems. Call Establishment has its own sectCall Establishment has its own sectionion within this guide, but in short; a UE establishes calls on a single cell based upon its having the best within this guide, but in short; a UE establishes calls on a single cell based upon its having the best Common Pilot Channel (CPIC

Common Pilot Channel (CPICH) signal level and/or quality. H) signal level and/or quality. If a cell has propagated into If a cell has propagated into an area wherean area where there are no neighbors assigned from it to other closer cells in terms of distance to the mobile, the call will there are no neighbors assigned from it to other closer cells in terms of distance to the mobile, the call will drop.

drop. Even if there are neighbors assEven if there are neighbors assigned, the noise level will be increased for a igned, the noise level will be increased for a short time until theshort time until the surrounding cells have been added

surrounding cells have been added to the call through the process of to the call through the process of Soft Handover.Soft Handover.

Fundamentally, Pilot Pollution is

Fundamentally, Pilot Pollution is Common Pilot Channel (CPICH) power where it is not desired due Common Pilot Channel (CPICH) power where it is not desired due thethe over-propagation of cells.

over-propagation of cells. The current method used tThe current method used to reduce Pilot Pollution requires a drive test o reduce Pilot Pollution requires a drive test of theof the area with a CPICH

area with a CPICH scanner. scanner. CPICH propagation is then CPICH propagation is then analyzed graphically (maps) and statistanalyzed graphically (maps) and statistically.ically. The criteria for Pilot Pollution is 4 or more Common Pilot Channels serving within 5 dB of each other in The criteria for Pilot Pollution is 4 or more Common Pilot Channels serving within 5 dB of each other in the same geographic

the same geographic area. area. In most cases, In most cases, power changes, dowpower changes, down-tilts, azimuth changes n-tilts, azimuth changes or antennaor antenna changes are required to reduce over-propagation.

changes are required to reduce over-propagation.

4.3.2

NeNeighbor ighbor List List DeDeterminationtermination

Neighbor relationships fall into 3

Neighbor relationships fall into 3 categories where UMTS and the interaction between UMTS and GSMcategories where UMTS and the interaction between UMTS and GSM are concerned.

are concerned.

•

• Intra-UARIntra-UARFCN NeighborFCN Neighbor s.s. These neighbor relationships These neighbor relationships are assigned wherever there is coverage are assigned wherever there is coverage overlapoverlap

between cells having the

between cells having the same UARFCN. same UARFCN. These neighbor relationships These neighbor relationships allow for Soft Handover. allow for Soft Handover. It is important tIt is important too assign neighbor relationships between overlapping cells in order to

assign neighbor relationships between overlapping cells in order to allow multiple cells covering the sameallow multiple cells covering the same geographic area to collectively serve a given

geographic area to collectively serve a given UE.UE. A cell covering an area, but

A cell covering an area, but not in the other server’s neighbor lists is not in the other server’s neighbor lists is seen as noise by the UE wseen as noise by the UE whichhich causes the UE compensate by requiring more

causes the UE compensate by requiring more power.power.

•

(19)

Volume

ND-00150

UARFCNs. The neighboring UARFCNs can be The neighboring UARFCNs can be in either the same band in either the same band or in a different bandor in a different band. . NeighborNeighbor relationships should be assigned between all overlapping UARFCNs.

relationships should be assigned between all overlapping UARFCNs.

•

• Inter-RAT Inter-RAT NeighborsNeighbors .. Inter-RAT neighbor relationInter-RAT neighbor relationships allow for Hard Handover and ships allow for Hard Handover and Cell Reselection betweenCell Reselection between

UMTS and GSM

UMTS and GSM. . The UMTS coverage area in The UMTS coverage area in all AT&T markets all AT&T markets is a subset of the GSM is a subset of the GSM coverage. coverage. Inter-RATInter-RAT neighbors should only be defined from UMTS to GSM cel

neighbors should only be defined from UMTS to GSM cells that support EGPRS (EDGE). ls that support EGPRS (EDGE). This is done in order toThis is done in order to allow for the greatest throughput when the UE performs an Inter-RAT Cell Change

allow for the greatest throughput when the UE performs an Inter-RAT Cell Change from the 3G to the 2G network.from the 3G to the 2G network. Idle Mode Cell Reselection neighbors should be defined xx Inter-RAT neighbors should

Idle Mode Cell Reselection neighbors should be defined xx Inter-RAT neighbors should also be assigned to allowalso be assigned to allow UEs to handover from UMTS to GSM where there are no s

UEs to handover from UMTS to GSM where there are no s uitable UMTS carriers (coverage holes) within theuitable UMTS carriers (coverage holes) within the UMTS polygon.

UMTS polygon.

Important! – Neighbor relationships for speech must not be

Important! – Neighbor relationships for speech must not be defined from GSM to UMTS in order to avoidefined from GSM to UMTS in order to avoi dd E911 calls handing back to UMTS before they are ended.

E911 calls handing back to UMTS before they are ended.

Ericsson further defines neighbor types based upon

Ericsson further defines neighbor types based upon how they exist between different RNCs andhow they exist between different RNCs and technologies (GSM vs. UMTS).

technologies (GSM vs. UMTS).

•

• UTRUTRAN RelationsAN Relations .. All intra-RNC neighbor defAll intra-RNC neighbor definitions including Intra initions including Intra and Inter-UARFCN.and Inter-UARFCN. •

• External UTRAN ReExternal UTRAN Relationslations .. All inter-RNC neighbor deAll inter-RNC neighbor definitions including Intra afinitions including Intra and Inter-UARFCN.nd Inter-UARFCN. •

• GSM Relations.GSM Relations. All Inter-RAAll Inter-RAT neighbor T neighbor definitions.definitions.

4.3.3

ScramblinScramblin g Code Usageg Code Usage

Each cell in the network is assigned a

Each cell in the network is assigned a Primary Scrambling Code. Primary Scrambling Code. TheThe primaryScramblingCodeprimaryScramblingCode [Cell, 0[Cell, 0 to 511, Integer, Variable] p

to 511, Integer, Variable] parameter is an integer value 0-511 inclusive. arameter is an integer value 0-511 inclusive. For the interest of this seFor the interest of this section, itction, it is important to avoid co-UARFC

is important to avoid co-UARFCN co-Scrambling Code use in N co-Scrambling Code use in the same geographic area. the same geographic area. However, ifHowever, if there are more than 512

there are more than 512 cells in use, Scrambling Codes must cells in use, Scrambling Codes must be reused very carefully. be reused very carefully. It is suggestedIt is suggested that reuses of Scrambling Code among the same

that reuses of Scrambling Code among the same UARFCN only exist where there is ample isolation.UARFCN only exist where there is ample isolation.

Optionally, Scrambling Codes can also be

Optionally, Scrambling Codes can also be divided into 64 groups of 8 codes divided into 64 groups of 8 codes each. each. Scrambling CodeScrambling Code planning would then be much like freque

planning would then be much like frequency planning with a reuse of 64. ncy planning with a reuse of 64. The advantage to this type ofThe advantage to this type of planning could be a less complex code search procedure for the UE.

planning could be a less complex code search procedure for the UE.

4.4

Measurement Fundamentals

Before we get into Idle Mode, Call

Before we get into Idle Mode, Call Establishment and Mobility Management, it is Establishment and Mobility Management, it is important to understandimportant to understand the fundamental measurements

the fundamental measurements used by the UE and RNused by the UE and RNS to make radio related decisions. S to make radio related decisions. TheseThese measurements are commo

measurements are commonly used when referencing signal level (RSCP) nly used when referencing signal level (RSCP) and signal quality (Ec/No). and signal quality (Ec/No). TheThe signal level (RSCP) and signal

signal level (RSCP) and signal quality (Ec/No) of the Primary Common Pilot Channel (CPICH) define thequality (Ec/No) of the Primary Common Pilot Channel (CPICH) define the coverage area of the cell.

coverage area of the cell. SIR and BLER are also described as SIR and BLER are also described as they are used to control uplink andthey are used to control uplink and downlink power.

downlink power.

4.4.1

PCPICHPCPICH

The Primary Common Pilot Channel (CPICH) is one of

The Primary Common Pilot Channel (CPICH) is one of the continuously transmitted downlink Physicalthe continuously transmitted downlink Physical Channels.

Channels. It is unique in that it is tIt is unique in that it is the reference used by the UE to he reference used by the UE to make radio related decisions for make radio related decisions for CellCell Selection, Cell Reselection , Soft (intra-frequency) Handover and Hard (inter-frequency) Handover as well Selection, Cell Reselection , Soft (intra-frequency) Handover and Hard (inter-frequency) Handover as well

(20)

as Inter-RAT Handover. All signal level and quality measurements are made based upon or relative to the Primary Common Pilot Channel.

The power of Primary Common Pilot Channel is set to an absolute value per cell at the Reference Point (antenna connector) through the primaryCpichPower [Cell, 300, 0.1dBm, Fixed] parameter. All other downlink Physical Channels on the cell are set relative (dB) to the Primary Common Pilot Channel. Since proper downlink power settings are necessary to allo w the UE to enter Idle Mode, they are covered in detail in the Idle Mode section.

4.4.2

PCPICH RSCP

The Primary Common Pilot Channel Received Signal Code Power, commonly called “RSCP”, is simply the received power (dBm) of the Common Pilot Channel.

In order to really understand Received Signal Code Power (RSCP), it is important to understand the basic concept of spreading and de-spreading. Spreading is the process of taking a signal, in this case the Primary Common Pilot Channel (CPICH) signal, and transforming it into a signal that occupies a much larger bandwidth. This is done in two steps. First, the original signal is binary multiplied by a Spreading Code. The Spreading Code, also known as the Channelization Code or Orthogonal Variable Spreading Factor (OVSF) Code is unique within the cel l and when binary multiplied by Primary Common Pilot Channel (CPICH) signal allows it to be isol ated from the other spread signals within the cel l.

The Primary Common Pilot Channel (CPICH) has a bit rate of 30kb/s. 2 bits = 1 symbol in the downlink. The bits in the Spreading Code are referred to as “chips”. The number of chips per data symbol is called the Spreading Factor. 3,840,000 chips / 15,000 symbols = 256. The Primary Common Pilot Channel (CPICH) uses a Spreading Factor of 256. Seen yet another way, each Primary Common Pilot Channel (CPICH) symbol is spread into 256 chips causing the spread signal to occupy 256 times the bandwidth of the original signal.

Second, since the Spreading Codes are only unique within a cell, the signal must be further “scrambled” to make it unique within the geographic coverage area. This is done by exclusively ORing the already spread signal with a primaryScramblingCode [Cell, 0 to 511, Integer, Variable]. There are a total of 512 Primary Scrambling Codes available, so co-UARFCN co-Primary Scrambling Code use might be

necessary in geographic areas with greater than 512 cells. See the Scrambling Code Selection section for cautions.

At the other end, receiving the symbols is simply a matter of first de-scrambling, then de-spreading the signal using the same scrambling and spreading codes used to initially spread the symbols.

4.4.3

CPICH Ec/No (Ec/Io)

The Primary Common Pilot Channel (CPICH) received Energy per Chip (Ec) to Noise (No) ratio,

commonly referred to as Eee-Cee-N-Not, is used to measure the received quali ty of the Primary Common Pilot Channel (CPICH). It is the ratio of the received Energy per Chip to the Noise power spectral density in the band. In this case, the Chip Energy (Ec) is the power of the spread Primary Common Pilot Channel (CPICH) at the receiver. Ec is equivalent to Received Signal Code Power (RSCP) in that both measure the power of the Primary Common Pilot Channel (CPICH); the only difference being Ec is the power of

(21)

Rev. 3.0 09/09/2007 Use pursuant to Company instructions © 2007 AT&T the spread signal whereas RSCP is the power measured after de-spreading. No (N-not) is the received wide band power, including thermal noise and noise generated in the receiver within the receiver’s bandwidth.

The term Ec/Io is also used to denote Primary Common Pilot Channel (CPICH) quality with the onl y difference being the denominator where Io includes interference only. The use of the term Ec/Io is where receivers are concerned is not technically accurate due mainly to the fact that receivers do not discern Noise from Interference and as such, cannot accurately measure Ec/Io. However, Io is commonly used in RF Design (propagation) tools when noise is not considered.

4.4.4

Eb/No

Eb/No, commonly referred to as Eee-Bee-N-Not or ebno, is the received energy per Bit (symbol) of the signal over the received wide band power, including thermal noise and noise generated in the receiver, within the receiver’s bandwidth. The fundamental difference between Eb/No and Ec/No is Spreading Factor. Ec is of course the energy of the spread signal. By factoring in the Spreading Factor, we get the energy of a bit or symbol over the received wide band power, including thermal noise and noise

generated in the receiver, within the receiver’s bandwidth. Eb/No therefore equals Ec/No * Spreading Factor.

Eb/No is commonly used when referencing Physical Channels that carry user data or signaling as

opposed to Physical Channels such as the Common Pilot Channel (CPICH) which only carries repetitive data.

4.4.5

SIR

SIR is the Signal to Interference Ratio. It is equivalent to (RSCP / ISCP) * Spreading Factor. RSCP is defined above; ISCP is the Interference Signal Code Power which is essentially the interference from other cells (DL) or UEs (UL) excluding noise. SIR is a quality metric used to maintain appropriate power levels in the uplink and downlink. The UTRAN uses a very fast power control technique called “closed-loop power control” where power is adjusted 1500 times per second in order to maintai n the Signal to Interference Ratio at a configured target value. SIR is further explained in the Mobility Management section.

4.4.6

RSSI

The Received Signal Strength Indication is a signal level measurement of the downlink which includes thermal noise and noise generated in the receiver within the receiver’s bandwidth. Received Signal Strength Indication (RSSI) is equivalent to the No measurement used in Ec/No above.

4.4.7

RTWP

Received Total Wideband Power measured by the Node B is the received wide band power, including thermal noise and noise generated in the receiver within the receiver’s bandwidth.

(22)

4.4.8

BLER

BLER is the Block Error Rate at the Transport Channel Layer. CPICH RSCP, CPICH Ec/No, Eb/No and SIR are all measurements of the Physical Layer. The Transport Channel layer resides above the

Physical Layer. At the Transport Layer, data from the Physical Layer is put into CRC encoded Blocks. If a Block fails a CRC check, it is considered in error. BLER indicates the percentage of these Blocks in error.

(23)

5. Parameters Descri bed Within Cont ext

5.1

Idle Mode

Idle Mode is a state every UE enters when it is powered on. It is also the state in which each powered on UE spends most of its time. In this state, the UE must be ready and able to Originate and Terminate calls. This section includes cell selection, but does not include Cell Reselection as Cell Reselection is a function of mobility and as such is covered in the Mobility Management section.

5.1.1

Cell Search Procedure

After either power up or entry into network coverage, the UE must begin to read information on the BCCH. The Broadcast Control CHannel (BCCH) is used to broadcast System Information to all UEs within its coverage area. This is accomplished in 3 steps. However, before the 3 steps are described, it is important to understand the Slot and Frame structure of the downlink. A Slot is made up of 2560 Chips (meaning it’s a spread signal). 15 Slots make up one 10 ms Frame. 73 Frames make up one

Superframe.

1. Slot Synchronization with the downlink is acquired by correlating the Primary Synchronization Code, common to every cell and known by all UEs, with the Primary Synchronization Channel (P-SCH) transmitted on the downlink. It is important to know that neither the Primary nor the Secondary

Synchronization Channel are ever Scrambled using the Primary Scrambling Code. Each cell serving in the UE’s geographic area transmits a Primary Synchronization Channel (P-SCH). The cell that the UE is able to obtain the strongest correlation with is chosen as the serving cell. The Primary

Synchronization Channel (P-SCH) power level is controlled by the primarySchPower [Cell, -18, 0.1dB, Fixed] parameter which is set relative to the power of the Primary Common Pilot Channel (CPICH).

Figure 1: Slot and Frame Struct ure

S0 S1 S2

...

S13 S14

...

.667 ms F0 F1 F2

...

F70 F71

...

Superframe = 72 frames Frame = 15 Slots Slot = 2560 Chips 10 ms 720 ms

The process in which UARFCNs are chosen for a Slot Synchronization attempt is UE implementation dependant.

(24)

2. Even though the UE has acquired Slot Synchronization, it still needs to know the Slot number within a Frame (Frames have 15 Slots) so it can know where the Frame begins. It does this by correlating one of the 16 Secondary Synchronization Codes with the Secondary Synchronization Channel (S-SCH). It is important to know that neither the Primary nor the Secondary Synchronization Channel are ever Scrambled using the Primary Scrambling Code. The 16 Secondary Synchronization Codes are used to form 64 unique Secondary Synchronization Channel sequences. Once the UE has decoded 15 successive Secondary Synchronization Codes, i t not only knows where the Frame begins, but the Code Group (used in step 3) as well. The UE is now Frame Synchronized. The Secondary Synchronization Channel (S-SCH) power is controlled by the secondarySchPower [Cell, -35, 0.1dB, Fixed] parameter which is set relative to the power of the Primary Common Pilot Channel (CPICH).

3. Now that the UE is Slot and Frame Synchronized, it must still determine the cell’s Primary Scrambling Code before it can begin to read the Broadcast Control CHannel (BCCH). In step 2, the UE discovers the cell’s Code Group. Each Code Group identifies 8 possible Primary Scrambling Codes. The correct Primary Scrambling Code is determined by correlating each of the 8 possibilities with the Common Pilot Channel (CPICH). Once the correct Primary Scrambling Code has been found, the UE can detect the Primary Common Control Physical Channel (P-CCPCH) which carries the

Broadcast CHannel (BCH) Transport Channel. The Broadcast CHannel (BCH) transmission power is controlled throughput bchPower [Cell, -31, 0.1dB, Fixed] which is set relative to the power of the Primary Common Pilot Channel (CPICH). The Broadcast CHannel (BCH) carries the Broadcast Control CHannel (BCCH) Logical Channel. The cell’s Primary Scrambling Code is configured using the primaryScramblingCode [Cell, 0 to 511, Integer, Variable] parameter.

The Primary Common Control Physical Channel (P-CPPCH) carries the System Frame Number (SFN) which is used as the timing reference for all Physical Channels. The System Frame Number (SFN) ranges from 0 to 4095 (inclusive). For more information about Slot and Frame synchronization, see [3e].

5.1.2

PLMN Selection

Now the UE is able to read the Broadcast Control CHannel (BCCH). If the UE finds its subscribed Public Land Mobile Network (PLMN) it then continues to read System Information from the BCCH.

5.1.2.1 Inform ation on the Broadc ast Contro l CHannel (BCCH)

The Broadcast Control Channel (BCCH) broadcasts information consisting of a Master Information Block (MIB), up to 18 System Information Blocks (SIB) types numbered 1-18, and up to 2 Scheduling Blocks (SB). Ericsson has implemented a Master Information Block (MIB) and System Information Blocks (SIB) types 1, 3, 5, 7, 11 and 12.

The following breakdown of the Master Information Block (MIB) and System Information Blocks (SIBs) provides an indication of where the UE gets the information necessary in order to maintain Idle Mode, Establish Calls, and Manage Mobility. The “Layer 3 Message” column was derived from TEMS 6.0 log files. The Purpose column provides a brief description of where the parameter applies.

• Master Infor mation Bl ock (MIB). The Master Information Block (MIB) is sent at a fixed rate of every 8 Frames

(80ms). It contains information that identifies the network as well as the start position and interval of each of the System Information Blocks (SIBs). The Master Information Block (MIB) also contains a Value Tag associated with each System Information Block supported. If the Value Tag for any supported System Information Block changes, the UE must read that System Information Block (SIB). In order to avoid the UE having to read each and every Master Information Block (MIB), a Paging Type 1 message is sent and repeated noOfMibValueTagRetrans [RNC, 0, Retransmissions, Fixed] times to all UEs indicating a Value Tag has changed in the Master Information Block

(25)

Table 7: Master Inform ation Bloc k (MIB) Contents Ericsson Parameter Layer 3

Message

Purpose

mcc MCC : The Mobile Country Code

mnc MNC : The Mobile Network Code

sib1StartPos Repx : y Sets the start position of SIB 1 where x equals the repetition period and y equals the SFN / 2.

sib1RepPeriod sib-Pos : repx Sets the SIB 1 repetition period where x equals a number of Frames.

• System Informatio n Bl ock 1 (SIB 1). System Information Block 1 (SIB 1) contains Location Area (LA), Routing

Area (RA) information and timer parameters. Since this System Information Block contains the Location Area (LA) and Routing Area (RA) information, it must also be read when a LA or RA border is crossed. The parameter sib1PLMNScopeValueTag [Cell, 0 to 31, Integer, Variable] controls when System Information Block 1 (SIB 1) is read and must be set so that neighboring Location Areas and Routing Areas have different values.

Table 8: System Informati on Bloc k 1 (SIB 1) Contents

Ericsson Parameter Layer 3 Message Purpose

lAC LAC : xxxxx Location Area Code used by CS Core Network

t3212 CS domain – T3212 : x Periodic Location Area Update interval in deci-minutes, e.g. 1 = 6 minutes.

(26)

Ericsson Parameter Layer 3 Message Purpose Core Network

cnDrxCycleLengthCs CS domain – DRX-CycleLengthCoeff : k

Discontinuous Reception (DRX) Cycle Length Coefficient.

rAC RAC : xx Routing Area Code used by PS Core Network

nmo NMO : x Network Mode of Operation

cnDrxCycleLengthPs PS domain – DRX-CycleLengthCoeff : k

Discontinuous Reception (DRX) Cycle Length Coefficient.

• System Informatio n Bl ock 3 (SIB 3). System Information Block 3 (SIB 3) contains parameters for cell selection

and reselection.

Table 9: System Informati on Bloc k 3 (SIB 3)

qualMeasQuantity cellSelectQualityMeasur e : x

Determines if cell ranking uses quality measurements. sRatSearch s-SearchRAT : x Used to determine when Inter-RAT measurements

begin.

sHcsRat s-HCS-RAT : x Used to determine when Inter-RAT measurements begin.

qQualMin q-QualMin : x Used in Cell Selection and Re-selection qRxLevMin q-RxlevMin : x Used in Cell Selection and Re-selection qHyst2 q-Hyst-I-S : x Used in Cell Selection and Re-selection treSelection t-Reselection-S : x Used in Cell Selection and Re-selection

maxTxPowerUl

maxAllowedUL-TX-Power : x

Max UE power allowed on the uplink. cellReserved CellReservedForOperat

orUse : x

Indicates if the cell is reserved by the operator.

• System Informatio n Bl ock 5 (SIB 5). System Information Block 5 (SIB 5) contains parameters that determine the

configuration of Common Physical Channels (PhyCHs) in the cell. Table 10: System Inform ation Bl ock 5 (SIB 5)

pichPower pich-PowerOffset : x Power level of the Page Indication CHannel (PICH) relative to the Primary Common Pilot Channel (CPICH) power

aichPower Aich-PowerOffset : x Power level of the Acquisition Indication CHannel (AICH) relative to the Primary Common Pilot Channel (CPICH) power

primaryCpichPower primaryCPICH-TX-Power : x

Power level of the Primary CPICH

(27)

PRACH.

powerOffsetP0 powerRampStep : x Preamble power step when no Acquisition Indicator is received.

preambleRetransMax preambleRetransMax : x

Maximum number of Preambles sent in one ramping cycle

• System Informatio n Bl ock 7 (SIB 7). System Information Block 7 (SIB 7) contains uplink interference value.

Due to the fact that this value changes very often, this System Information Block’s interval is controlled by a timer. When the UE receives System Information Block 7 (SIB 7), a timer is started. Once the timer expires, the

information is considered invalid and the UE reads the information again. The expiration time is the value of the sib7RepPeriod [RNC, 16, Frames, Fixed] parameter multiplied by the sib7expirationTimeFactor [RNC, 1, Factor, Fixed] parameter.

Table 11: System Inform ation Bl ock 7 (SIB 7)

n/a ul-Interference Provides uplink Received Total Wideband Power (RTWP). RTWP = No

• System Informatio n Bl ock 11 (SIB 11). System Information Block 11 (SIB 11) contains the cell’s soft/softer

handover neighbor list including the Primary Scrambling Code of each neighbor. This handover list is supplied to the UE before a call is established so that the UE may make Intra-frequency measurements before receiving the MEASUREMENT CONTROL message from the Serving Radio Network Controller (SRNC).

Table 12: System Inform ation Bl ock 11 (SIB 11)

reportingRange1a e1a – reportingRange : x

CPICH reporting range add threshold. hysteresis1a e1a – hysteresis : x Hysteresis used for CPICH add threshold. timeToTrigger1a e1a – timeToTrigger : x Time between CPICH add and reporting. reportingRange1b e1b – reportingRange :

x

CPICH reporting range drop threshold. hysteresis1b e1b – hysteresis : x Hysteresis used for CPICH drop threshold. timeToTrigger1b e1b – timeToTrigger : x Time between CPICH drop and reporting. hysteresis1c e1c – hysteresis : 2 Hysteresis used for CPICH replacement.

timeToTrigger1c e1c – timeToTrigger : x Time between CPICH replacement and reporting. hysteresis1d e1d – hysteresis : x Hysteresis used in best CPICH replacement.

timeToTrigger1d e1d – timeToTrigger : x Time between best CPICH replacement and reporting.

• System Informatio n Bl ock 12 (SIB 12). System Information Block 12 (SIB 12) contains measurement control

122761800-Ericsson-Field-Guide-for-Utran.pdf

V

V

ol

ol

ume I

ume I

I –

I –

E

E

ri

ri

css

css

on

on

F

F

ield

ield

G

G

ui

ui

de for

de for

UTRAN P3: Feature Parameters and Best

UTRAN P3: Feature Parameters and Best

Practices

Practices

Netwo

Network

rk Servic

Servic es

es Docu

Document

ment :

: ND-

ND-001

00150

50

Rev. 3.0

Rev.

3.0 09/0

09/09/20

9/2007

07

Overview

Overview

This document is the result of an

This document is the result of an ongoing collaborative effort between

ongoing collaborative effort between

AT&T Market, Regional, National and Erics

AT&T Market, Regional, National and Ericsson staff and management.

son staff and management. It will continue to

It will continue to

be updated with the latest findings in the areas of optimization and vendor improvement

be updated with the latest findings in the areas of optimization and vendor improvement

through the use of Field Studies and successive vendor software and hardware updates.

through the use of Field Studies and successive vendor software and hardware updates.

Contents

Contents

Contents

Contents

Figures

Tables

Document Revision History

RACI

1. Abo ut This Document

Purpose

Scope

Audi ence

Related Documentation

Acro nyms and Terms

Trademarks

Conventions

Contacts

2. New Featur es in P3 (WRAN P5MD Phase II)

Idle Mode