DFCA

BSS14 Network Engineering Information
PS & SDCCH ON DFCA TRX BSS21161

Krystian Majchrowicz Network Engineering COO RA GERD SA Network Engineering PL ver. 2.3
November 2008
BSS14 PS & SDCCH ON DFCA TRX

BSS21161 Revision History
Issue Number 0.1 1.0 1.1 2.0 Date of Issue 28.02.2008 03.03.2008 18.04.2008 22.04.2008 Draft version Corrections after NE internal review Reason for Update
Corrections after review done by Janne Kaasalainen (COO RA GERD BSC RRM&L3 RRM Dev FI)
Approved by Sebastian Lasek Update according to the final Implementation Specification (v.1.0-1) Update with minor changes before enabling Update according to open points from enabling in Espoo (Oct 2008)
2.1
2.2 2.3
11.07.2008
13.10.2008 25.11.2008

BSS14 - Introduction
The standardisation baseline of BSS14 release is 3GPP Release 7 BSS14 consists of the releases: BSC S14, MetroSite CXM7, UltraSite CX7, and
FlexiEDGE EP3
BSS14 is supported by the following NE releases: NetAct OSS5.1 CD set 3, MSC

M14.4, MGW U4.2 and SGSN SG7 CD2
The basic BSC S14 software release will be compatible with Talk Family DF7 BTS
software release
BSC SW release S13 will be the last compatible software level for the former Nokia
InSite BTS SW, so no support of BSS14 is foreseen

Dependency Table
BSS
BSC
DX200 Platform
BTS Ultra Site
BTS Metro Site
BTS Talk Family
BTS Prime Site
Release
BSS14
S14
CX7.0
CXM7.0
BTS InSite
2nd Gen BTS
BTS Flexi EDGE
NetAct
SGSN
MSC
RAN
MS
Release
EP3.0
OSS5.2
PS & SDCCH ON DFCA TRX BSS21161

Contents
DFCA overview DFCA channel selection
History & Reason for Introduction

Feature details Parameters & counters
Activation & deactivation

Expected benefits Planning and dimensioning issues
Feature impact analysis
DFCA overview
Dynamic Frequency & Channel Allocation

Introduction
DFCA was introduced in BSS 11.5 as a new capacity/quality enhancement
feature in NSNs BSS
It is a revolutionary approach for managing the frequency usage in the

radio interface.
DFCA gives remarkable Capacity and Performance Gains, mainly due to: Interference control and Specific frequency plan on the fly @ the TSL level optimal from all
connections perspective Serving every connection with only required C/I to maintain a specific QoS

Target Customer Segments for DFCA
Bandwidth and Frequency Challenged Operators

Operators with growing traffic load. The impact of DFCA is in
reduction of site count in busy areas. DFCA eliminates the need for cell splitting due to increased interference in the network and saves costs Operators having strong growth potential with limited GSM band
Operators Re-farming GSM Frequencies to WCDMA

This is relevant already in the Americas and will become relevant in
other markets with WCDMA 850/900 Site configurations in typical allocation (10-15MHz) can be packed to 5MHz narrower frequency band which enables the implementation of one WCDMA carrier

DFCA principle
Random FH
TRX 1 TRX 2 TRX 3 TRX 4 BCCH
Random FH over a fixed frequency list
Loose interference control Relies on random spreading of the interference
DFCA
TRX 1 TRX 2 TRX 3 TRX 4 BCCH
Cyclic FH over individually selected frequency lists and MAIOs for each connection
C/I > C/I target
Accurate interference control (C/I estimations) Each connection is assigned with the most suitable radio channel (MA list, MAIO, TSL)

DFCA principle

DFCA ensures optimum radio channel allocation for every new call and incoming handover Precise interference control is achieved with: GPS Satellite
BTS with LMU
BSS synchronisation BSC information exchange Cyclic frequency hopping DFCA Algorithm uses comprehensive statistical data for channel selection process: Real time information Near real time information Non real time information DFCA algorithm assigns the radio channel for each individual connection with: Mobile Allocation (MA) Mobile Allocation Index Offset (MAIO) Radio Timeslot (TSL) Training Sequence Code (TSC) Power level in uplink and downlink BSC with DFCA Algorithm BSC-BSC Link
Goal is to provide a radio channel with sufficient C/I that depends on the type of the connection (i.e. meet different QoS requirements for FR, HR, AMR)

Background Interference Matrix (BIM)
BIM update process collects periodically statistical C/I data from all the cells that are reported by the mobiles in each DFCA BTS. This way there is a nice view on the interference situation at any time for channel allocation for a new call. BSC maintains BIM table for all the DFCA cell cells. In SDCCH phase of a call setup DL levels of neighboring cells are used; max 6 neighbors reported by the MS Significant interfering cells may not fit into 6 strongest neighbors => blind spots To solve the problem, statistics have been collected from all the measurement reports in a cell
Serving cell RXLEV N_cell 1 RXLEV N_cell 2 RXLEV N_cell 3 RXLEV N_cell 4 RXLEV N_cell 5 RXLEV N_cell 6 RXLEV N_cell 7 ? N_cell 8 ? N_cell 9 ?
...
Statistical C/I data is available for non-reported neighbors

BIM example
BTS1 Incoming BIM
BCCH 102 115 --BCCH 115 ---
BTS6 BCCH 102 BSIC 54

Status ok ok ---
C
I
BSIC 54 22 --BSIC 22 ---
C/I (dB) 12 18 --C/I 15 ---
SEG Id 6 12 --SEG 12 ---
Missed update 0 0 ---
I
BTS1 Outgoing BIM
C
BTS6 Incoming BIM

BCCH 115 --BSIC 22 --C/I (dB) 10 --SEG Id 12 --Missed update 0 --Status ok ---
BTS6 Outgoing BIM

BCCH 74 --BSIC 30 --C/I 12 --SEG 1 ---
C C I
Missed update 0 --Status ok ---
BTS12 Incoming BIM

BCCH 74 --BSIC 30 --C/I (dB) 15 --SEG Id 1 ---
BTS12 Outgoing BIM

BCCH 74 102 --BSIC 30 54 --C/I 18 10 --SEG 1 6 ---
DFCA channel selection

Checking C/N
Channel selection overview

INPUTS for each connection
MS measurement report
Calculate BIM scaling factor Pick TSL, MA and MAIO Incoming DL&UL CIR estimation + TX pwr setting
For each DFCA BTS

Incoming Outgoing BIM BIM
Outgoing DL&UL CIR estimation Determine CIR difference for this TSL, MA and MAIO
For each BSC

DFCA RR table
All checked
Yes
No
Choose the most suitable

DFCA adj.-channel lookup table No
Above soft blocking threshold

Yes
Block
Determine TSC

BIM scaling factor
Channel assignment request includes: Connection type (FR,HR,AMR FR, AMR HR)
Latest DL neighbouring cell measurements incoming BIM
The BIM scaling factor is used to correct the statistical C/I values of BIM tables to better correspond the users actual situation The scaling factor is mainly affected by the distance of the user from the serving BTS
BCCH, BSIC 102, 23 114, 52 104, 12 116, 32 108, 12 111, 43
Reported C/I 8 dB 12 dB 12 dB 15 dB 19 dB 20 dB
BIM C/I 4 dB 7 dB 9 dB 11 dB 15 dB 15 dB
C/I 4 dB 5 dB 3 dB 4 dB 4 dB 5 dB 4 dB
Average C/I (BIM scaling factor):

Incoming DL C/I estimations
DFCA assignment in cell: 100, 01 C/I target: 14 dB
C/I
Channel being checked: TSL 1, MA 2, MAIO 1

DFCA RR table MIN C/I diff Incom. DL Incom. UL Outgo. DL Outgo. UL DFCA adj.-channel lookup table MIN
1. Determine if co- or adjacent channel is being used in the cells listed in incoming BIM by using the DFCA tables
2. Calculate the real C/I caused by each of the ongoing interfering connections.
For the directly measured neighbouring cells the measured C/I is used For the unmeasured ones the incoming BIM value is used scaled with the BIM scaling factor In case of adjacent channel interference +18 dB offset is used The power reductions in the interfering connections are taken into account when the real C/I is determined
Incoming BIM (100, 01)

BCCH, BSIC
C/I diff C/I real C/I target after PC
102, 23 114, 52 104, 12 115, 30 101, 52 116, 32 103, 06 108, 12 111, 43
4 dB 7 dB 9 dB 10 dB 11 dB 11 dB 14 dB 15 dB 15 dB
102, 36
18 dB
Adj Co Co Co Adj Co
32 dB
14 dB
14 dB
20 dB
14 dB
2 dB
25 dB 18 dB 37 dB
14 dB 14 dB 14 dB
7 dB 0 dB 19 dB
26 dB
14 dB
8 dB
DL tx power reductions from DFCA RR table

BCCH, BSIC DL pwr reduction
18 +4 +4 = 26 102, 23 104, 12 116, 32 103, 06 108, 12 102, 36 6 dB 8 dB 10 dB 0 dB 0 dB 4 dB
3. The most restrictive C/I is identified (18 dB in this case) The initial DL power reduction is determined so that as a result the connection will be operating in it's C/I target 4. The C/I difference after power reduction is calculated and the lowest C/I difference is stored
MS Measurement report
BCCH, BSIC C/I
DL pwr reduction 18 dB - 14 dB = 4 dB
102, 23 114, 52 104, 12 116, 32 108, 12 111, 43
8 dB 12 dB 12 dB 15 dB 19 dB 20 dB
BIM scaling factor +4 dB

Incoming UL C/I estimations
BTS 6 BTS 1
Incoming UL Outgoing UL
Incoming DL
Same propagation path opposite direction
Outgoing DL
Existing connection New connection
DL & UL interference propagation paths

Incoming UL C/I estimations
DFCA assignment in cell: 100, 01 C/I target: 14 dB Channel being checked: TSL 1, MA 2, MAIO 1 DFCA RR table
C/I diff C/I real C/I target after PC
Outgoing BIM (100, 01)

BCCH, BSIC C/I
MIN C/I diff Incom. DL 0 Incom. UL DFCA adj.-channel lookup table
1. Determine if co- or adjacent channel is being used in the cells listed in outgoing interference BIM by using the DFCA tables 2. Calculate the real C/I caused by each of the ongoing interfering connections.
The incoming UL C/I estimations are always based on the statistical C/I values presented in the outgoing interference BIM table and scaled with the BIM scaling factor.
101, 52 102, 23 103, 06 110, 02
6 dB 8 dB Adj 40 dB 14 dB 26 dB 9 dB Co 13 dB 14 dB -1 dB 10 dB 14 dB 14 dB 14 dB 30 dB 3 dB 7 dB
-1
Outgo. DL
Outgo. UL MIN
105, 59 12 dB Adj 44 dB 116, 32 13 dB Co 17 dB 104, 12 15 dB Co 21 dB 111, 43 17 dB 108, 12 18 dB Adj 40 dB 102, 36 20 dB Co 34 dB 20 +4 +10 = 34
14 dB 14 dB
26 dB 20 dB
In case of adjacent channel interference +18 dB offset is used
Information from DFCA RR table

BCCH, BSIC UL pwr reduction Measured C/I for cell 100,01
The power reductions in the interfering connections are taken into account when the real C/I is determined DL Measurement report
3. The most restrictive C/I is identified (13 dB in this case) The initial UL power reduction is determined so that as a result the connection will be operating in it's C/I target
BCCH, BSIC
C/I
UL pwr reduction
13 dB - 14 dB = 0 dB*
102, 23 103, 06 105, 59 116, 32 104, 12 108, 12 102, 36
10 dB 0 dB 10 dB 0 dB 2 dB 4 dB 10 dB
11 dB 19 dB not measured 18 dB not measured 20 dB not measured
102, 23 114, 52 104, 12 116, 32 108, 12 111, 43
8 dB 12 dB 12 dB 15 dB 19 dB 20 dB * No reduction possible as C/I is below target BIM scaling factor +4 dB
4. The C/I difference after power reduction is calculated and the lowest C/I difference is stored

Outgoing DL C/I estimations
DFCA assignment in cell: 100, 01 Channel being checked: TSL 1, MA 2, MAIO 1
Outgoing BIM (100, 01)

BCCH, BSIC C/I
C/I real C/I target C/I diff
MIN C/I diff DFCA RR table Incom. DL 0 Incom. UL -1 Outgo. DL -2 Outgo. UL MIN DFCA adj.-channel lookup table
1. Interfered connections and interference type as determined in incoming UL interference check 2. Calculate the real C/I caused to each of the interfered ongoing connections.
If the C/I caused by cell 100,01 can be determined from measurement reports in DFCA RR table then the measured C/I is used For the unmeasured ones the outgoing BIM value is used scaled with the BIM scaling factor of the interfered connection In case of adjacent channel interference +18 dB offset is used
101, 52 102, 23 103, 06 110, 02
6 dB 8 dB Adj 27 dB 14 dB 13 dB 9 dB Co 19 dB 20 dB -1 dB 10 dB 16 dB 14 dB 14 dB 20 dB -2 dB 4 dB
105, 59 12 dB Adj 36 dB 116, 32 13 dB Co 12 dB 104, 12 15 dB Co 18 dB 111, 43 17 dB 108, 12 18 dB Adj 42 dB 102, 36 20 dB Co 23 dB 20 +3 +4 - 4 = 23

DL pwr reduction = 4 dB*
* From Incoming DL check
16 dB 14 dB
26 dB 9 dB
Information from DFCA RR table

BCCH, BSIC
DL pwr BIM scaling Measured C/I for cell 100,01 C/I target reduction factor
The power reductions in the interfering connections as well as in the DL of the serving connection are taken into account when the real C/I is determined
DL Measurement report
BCCH, BSIC C/I
3. The calculated C/I is then compared to the C/I target and a C/I difference is calculated. The lowest C/I difference is stored
102, 23 114, 52 104, 12 116, 32 108, 12 111, 43
8 dB 12 dB 12 dB 15 dB 19 dB 20 dB
102, 23 103, 06 105, 59 116, 32 104, 12
6 dB 0 dB 8 dB 10 dB 8 dB
+3 +6 +10 -2 +7
14 dB 20 dB not measured 16 dB 18 dB 14 dB not measured 14 dB
11 dB 15 dB
108, 12 102, 36
0 dB 4 dB
+4 +3
16 dB not measured 14 dB
20 dB

Outgoing UL C/I estimations
DFCA assignment in cell: 100, 01 Channel being checked: TSL 1, MA 2, MAIO 1
Incoming BIM (100, 01)

BCCH, BSIC C/I
C/I real C/I target
C/I diff 1 dB DFCA RR table
MIN C/I diff Incom. DL 0
1. Interfered connections and interference type as determined in incoming DL interference check 2. Calculate the real C/I caused by each of the ongoing interfering connections.
The statistical C/I from the incoming BIM table is used and scaled with the connection specific BIM scaling factor that is listed in DFCA RR table In case of adjacent channel interference +18 dB offset is used
102, 23 114, 52 104, 12 115, 30 101, 52 116, 32 103, 06 108, 12 111, 43 102, 36
4 dB Adj 15 dB 14 dB 7 dB 9 dB Co 14 dB 14 dB 10 dB 11 dB 11 dB Co 9 dB 14 dB 14 dB Co 20 dB 20 dB 15 dB Adj 41 dB 16 dB 15 dB 18 dB Co 11 dB 14 dB 18 +3 +0 - 10 = 11
Incom. UL - 1 0 dB
Outgo. DL - 2
Outgo. UL MIN
-5 -5
-5 dB 0 dB 25 dB
DFCA adj.-channel lookup table
C/I difference for TSL 1, MA 2, MAIO 1 Information from DFCA RR table

BCCH, BSIC UL pwr reduction BIM scaling factor C/I target
-3 dB
The UL power reductions in the interfering connections as well as in the UL of the serving connection are taken into account when the real C/I is determined
UL pwr reduction = 0 dB*

* From incoming UL check
DL Measurement report
BCCH, BSIC C/I
102, 23 104, 12 116, 32 103, 06 108, 12 102, 36
10 dB 2 dB 0 dB 0 dB 4 dB 10 dB
+3 +7 -2 +6 +4 +3
14 dB 14 dB 14 dB 20 dB 16 dB 14 dB
3. The calculated C/I is then compared to the C/I target and a C/I difference is calculated. The lowest C/I difference measures the quality of the evaluated DFCA assignment
102, 23 114, 52 104, 12 116, 32 108, 12 111, 43
8 dB 12 dB 12 dB 15 dB 19 dB 20 dB

Channel selection
The minimum C/I differences of all calculated channel possibilities are examined and the channels with 0 or higher C/I difference are possible candidates for assignment
If all C/I differences are negative, then the channels where soft blocking limit has not been broken are possible candidates for assignment
History & Reason for Introduction
PS & SDCCH on DFCA TRX

Introduction & Background
DFCA was introduced in BSS 11.5 Up to BSS 14 DFCA requires its own layer DFCA layer is dedicated for Circuit Switched Services only Speech on DFCA, Regular or BCCH layer Data and SDCCH on BCCH or Regular Layers PS territory cannot extend into the DFCA layer Regular layer may be needed for extra SDCCH and Data capacity In worst case scenario spectrum freed by DFCA can not be utilized: Spectrum used on the Regular layer in order to ensure good quality Virtually no capacity/quality gain: same KPIs but with a different airinterface scenario DFCA improvement in BSS 14.0 clearly means of getting rid of the dreadful regular layer

Since up to BSS 14.0 (E)GPRS is not supported in a DFCA TRX : Detailed planning needs to be done to see if Data can be handled in
BCCH TRX If more data territory is needed, Regular TRX needs to be activated on case by case basis
Since up to BSS 14.0 SDCCH is not supported in a DFCA TRX SDCCH

needs, e.g. SMS, must be handled by BCCH TRX or Regular TRX
BCCH
CS, PS, SDCCH, DTM
Regular DFCA
CS

Regular Layer Any non-DFCA TRX besides the BCCH
TRX Drawbacks:
BCCH Regular
frequency planning is required frequencies must be set aside for

regular LY DCR KPI gain is reduced (see next slide)
DFCA
Impact of regular LY on DFCA performance

Due to the lower spectral efficiency, a small fraction of TRXs require a major
fraction of available frequencies In a previous trial 6 Regular TRXs out of 197 non-BCCH TRXs, i.e. 3% TRX required
3 freqs out of 15 hoppers, i.e. 20%
Outside the busy hour, spectrum is wasted because it can not be dynamically
refarmed to the DFCA layer
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
BCCH Band
DFCA Band
Regular Band

Total DCR
4 3.5 3
DCR (%)
2.5 2 1.5 1 0.5 0 5 7 9 11 EFL (%) DFCA DFCA-3 DFCA-6 RF 1/1 RF 1/1-3 RF 1/1-6 13 15 17 19
45% DCR improvement 15% DCR improvement REFERENCE
With 3 spots (17% of the frequencies) carved to make room for Regular TRXs, DFCA improvement in terms of DCR (at the same traffic volume) drops from 45% to only 15%
Feature Details

Feature details
Up to BSS 14.0 BCCH

CS, PS, SDCCH, DTM
Regular DFCA
CS
In BSS 14.0 PS on DFCA TRX SDCCH on DFCA TRX No need for regular TRX
BCCH
CS, PS, SDCCH, DTM
DFCA

Feature details
Modifications: DMAL handling TRP & BFG modification PS allowed in DFCA TRX (allowed in PCU2 only) - DFCA use the same algorithm as currently to assign frequency for PS territory however: Entirely based on BIM entries, i.e. DL Measurement Reports (MR) are

not used All TSLs belonging to the territory are assumed to be in use all the time No Initial Power Reductions Introduces new parameters GRPS C/I targets (CIGP) GPRS soft-blocking C/I threshold (SBGP)
SDCCH allowed in DFCA TRX DTM allowed in DFCA TRX Pre-emption is allowed on DFCA TRX. Pre-emption is started with existing rules except that proper candidate can be searched from regular and also DFCA TRX (no need for ranking due to C/I). Two different hopping modes are not allowed in one BTS

Reason for modification of TRP parameters
Up to BSS 14.0 TRP parameter allows to set preference for TCH allocations for
BCCH or regular TRXs only. With DFCA voice was always allocated on DFCA layer. Due to this, for the sake of fair comparison TRP should always be set to 2 during pre-DFCA benchmarking phase.

Example of traffic volume in BCCH (from DFCA implementation in LAM) Before DFCA, much more traffic in BCCH than after DFCA ON
ASS CMD on BCCH only -> 1 I-frame ASS CMD on DFCA -> 2-3 I-frame Shorter ASS CMD better accessibility
Since operators using TRP=1 disagreed to change their policy it was requested
to have with DFCA the option to prefer TCH from BCCH TRX Moreover with BSS14.0 there is no need for regular TRX thus no need to prefer TCH allocations between regular and BCCH TRXs

Modification of BFG and TRP parameters
TRP parameter for preferring TCH allocations within regular TRXs was changed to
prefer TCH allocations between BCCH TRX and DFCA TRX. TCH allocations are preferred according to TRP parameter: no_pri_c = 0 Search started from DFCA layer but if there is no from_bcch_c = 1 not_bcch_c = 2 amr_not_b_c = 3
measurement results allocation starts from BCCH TRX Search started from regular TRX Search started from DFCA TRX
Search started from DFCA TRX for AMR users and from BCCH TRX for non-AMR users
BFG parameter for preferring GPRS area between BCCH TRX and non-BCCH
TRXs within regular TRXs was changed to prefer GPRS area between BCCH TRX and DFCA TRX (when DFCA TRX is configured for PS use in BTS). GPRS area is preferred according to BFG parameter: no_pr_c = 0 No preference for GPRS area. yes_c = 1 GPRS area allocated primarily from the
BCCH TRX.
no_c
=2
GPRS area allocated primarily from the DFCA TRX.

Dual City scenario and need for DMAL grupping
If a BSC serves DFCA cells in several areas (cities) City 2
City 1
55 km
wide apart, it is not allowed to allocate different frequency schemes between the cities, although those cities do not interfere each other at all. On the other hand, in some networks, sometimes it may be necessary to allocate different frequency bands in different cities. The DFCA feature in any BSC has no knowledge about interfering DMALs if the frequency allocation rules are not followed.
The same disadvantage may appear also in a case of frequency plan change in a network when the old plan have 'conflicting' DMALs against the new plan. The root cause for the frequency allocation rules with DFCA is derived from the nature of cyclic frequency hopping. DFCA can estimate interference only if DMALs are defined in a regular manner, and interfering timeslot collisions are constant between DMALs. DMALs of different lengths would lead to pseudorandom collision probability and to cope with such irregular DMAL plan would multiply the complexity of DFCA interference estimation algorithm.

DMAL groupping

New Group id parameter is defined for each DFCA MA list (DMAL). Frequency reuse and adjacent frequencies will be searched only from DFCA MA lists within the same group id when state of DFCA MA list is changed. Restrictions: The same frequency can appear only once on several DFCA MA lists which belongs to the same DFCA MA Group If there are adjacent frequencies on the DFCA MA list and some other DFCA MA list of the BTS and these DFCA MA lists belongs to same DFCA MA Group, then the amount of frequencies must be the same in each of them DFCA doesnt control the use of frequencies or interference with adjacent channel(s) between the two DFCA MA lists if two DFCA MA lists have same or adjacent frequencies but the lists belong to different DFCA MA list groups BTS is allowed to have DFCA MA lists of different groups attached. 2 DMALs in two different DMAL groups is the solution for the Dual City scenario

DFCA MAL handling
New DFCA MA list Usage parameter indicates if the DFCA MA list can be used for CS or/and PS. Restrictions: Only one DFCA MA list that is used for PS use can be attached to BCCH BTS.
Attaching DFCA MA lists to non-BCCH BTSs is not limited by usage and up to 32 DFCA MA lists can be attached.

DFCA hopping parameter selection for a new GPRS TRX
1)
DFCA hopping parameters for GPRS upgrade are selected only from BTSs MA list(s) that are allowed for PS use.
C/I is calculated for every TSL that is selected to be upgraded. Same formulas as for FR TCH allocation are used with the new GPRS parameters for C/I target and soft blocking C/I If unused MA, MAIO combination is found then it is selected. If unused combination was not found but all TSLs are above C/I target combination with highest C/I sum is selected. 63dB is used in calculation for idle TSL(s). If some TSLs are below C/I target (CIGP) but all are above C/I soft blocking limit (SBGP) sum of C/I values that are below C/I target is calculated and the MA MAIO combination with lowest sum below C/I target is selected. If the sum below C/I target is equal for several combinations then sum of values above C/I target is calculated and the MA MAIO combination with highest C/I sum above target is selected.
2)
3) 4)
5)
6)

DFCA hopping parameter selection for a new GPRS TRX
7)
If the sum below C/I target is equal for several combinations then sum of values above C/I target is calculated and the MA MAIO combination with highest C/I sum above target is selected.
If there is TSL below C/I soft blocking limit (SBGP) this TSL must be excluded from upgrade and only TSLs towards end of the TRX are allowed to be upgraded. Combination that allows most TSLs for upgrade is selected.
8)
9)
If all TSLs cannot be upgraded due to C/I soft blocking (SBGP) or because theres CS connection in own segment C/I blocking TSL is marked as planned GPRS territory and it is also marked as reserved channel in RR table. Forced intra cell handover is started to move CS connection in own segment to use different MA MAIO TSL combination and so allowing next TSL to be upgraded for GPRS use.

Marked TSL as planned GPRS territory
TSL 5 is the candidate for GPRS territory upgrade If C/I for this TSL is below softblocking threshold GPRS territory is not upgraded TSL 5 is marked as the planned GPRS territory. This causes that new connections avoid to allocate TSL 5 (in serving cell and surrounding cells) with the wanted frequency parameters. Only one TSL can be market as the planned at time, to avoid reserving unnecessarily frequencies. After 5 sec. (the default value of upgrade guard time) upgrade is tried again. Now it is possible that quality already allows the upgrade. If the wanted TSL, MA, MAIO combination is reserved in own cell then intra cell handover is performed (for neighbouring cells no intracell HO; only marking and waiting is done).

Forced HO due to GPRS
Forced handover is started for CS connection if it is using the TSL that is wanted for GPRS upgrade .
TSL 4 is the candidate for GPRS territory upgrade
If C/I for this TSL is above softblocking threshold, forced HO due to GPRS is performed
Once the TSL 4 is freed DFCA allocates the same MAIO, MA and TSC as for the other TSLs within GPRS territory and performs upgrade

Forced HO due to GPRS
With DFCA forced handover is also triggered in a situation when the same MA MAIO TSL that is needed for GPRS upgrade is used for CS connection on another DFCA hopping TRX.

GPRS territory upgrade on a new DFCA TRX
1) Need for GPRS upgrade is triggered.
2) TRX is selected according to setting parameter BFG (modified

meaning) and RTSLs are selected from TRX starting from RTSL 7 and going towards RTSL 0.
3) DFCA selects hopping parameters for these RTSLs
In case of Downlink Dual Carrier DFCA allocates channel in the same way as in case of territory upgarde to new TRX

GPRS territory upgrade on existing DFCA TRX
1) 2)
Need for GPRS upgrade is triggered. RRM notices that DFCA TRX has already DFCA hopping parameters for GPRS and uses the same DFCA hopping parameters for the new RTSLs included into the GPRS territory upgrade. DFCA makes C/I softblocking calculations for new TSLs that are selected for GPRS upgrade. If C/I softblock occurs for any TSL, only TSLs onward from the C/I blocking TSL (not included) to the border of GPRS territory can be selected as new TSLs for GPRS upgrade
3)

Static SDCCH allocation on DFCA TRX
All static SDCCH resources from BCCH TRX are used before SDCCH allocations are made for DFCA TRX. When all static SDCCH channels on BCCH TRX are occupied, search continues from DFCA TRXs. DFCA makes C/I calculation for every static SDCCH TSL that is not completely full on DFCA TRX(s). Hopping parameters are selected with the current DFCA algorithm when the first SDCCH subchannel is allocated in the SDCCH TSL. For the need of DFCA algorithm new parameters are introduced
SDCCH C/I targets (CISD ) SDCCH soft-blocking threshold (SBSD)

TSL and DFCA hopping parameters with best C/I are selected for channel allocation. If several combinations have the same C/I value then TSL having most SDCCH connections is selected. TSC is also selected for the first SDCCH allocation on TSL the same way as currently for CS allocation. For any other subchannel on SDCCH TSL the same DFCA hopping parameters (as for the first subchannel) are used

Dynamic allocation SDCCH on DFCA TRX
When all configured SDCCH channels are used, RRM can reconfigure free TCH TSL on DFCA TRX for SDCCH use When selecting TSL for dynamic SDCCH on DFCA, TRX with least SDCCH TSLs configured is preferred. Existing rules with maximum amount of SDCCH channels on TRX are appliedd ie. :
2 SDCCH TSLs (16 SDCCH subchannels) per TRX 3 SDCCH TSLS on BCCH TRX and 4 on non BCCH, with "Increased Dynamic SDCCH capacity" feature (BSS12 ED2.1)
Then MA, MAIO allowed for CS use and TSL with best C/I is selected. TSC is also selected.

DTM on GPRS DFCA TRX
When DTM connection is for DFCA TRX, DFCA PS hopping parameters (that was selected for GPRS territory on GPRS DFCA TRX) are used When DTM CS connection is setup or released, PS connection is reestablished and therefore C/I is recalculated for that connection using CS value in setup and PS value in release for C/I target, C/I soft blocking is not checked. If DTM CS connection is at the border of a GPRS territory and territory is downgraded, there is a special situation where DTM CS connection on GPRS territory changes to CS connection. CS connection continues using already defined hopping parameters (even if they are for PS only use) for that connection.

Hardware and software requirements
BSC with PCU2 card
this is requirement for PS traffic on DFCA TRX for the other subfunctionallities related to this feature (BSS21161) PCU2
card is not required
BTS: Metrosite and Ultrasite CX 7.0

or
Flexi Edge BTS EP3.0
Parameters & counters

New Database Parameters
Parameter
Soft Blocking C/I GPRS= -20
Description
Soft Blocking C/I GPRS (dfcaGprsConnection_softBlockingCi), this parameter sets the minimum acceptable C/I value for GPRS and EGPRS data connections. Special value -20 is used to deactivate soft blocking due to C/I.
object: unit: range: default:
BSC dB -20..43 (step 1) -20
Soft Blocking C/I SDCCH= -20 object: unit: range: default: BSC dB -20..43 (step 1) -20
Soft Blocking C/I SDCCH (dfcaSdcchConnection_softBlockingCi)) , this parameter sets the minimum acceptable C/I value for SDCCH connections. Special value -20 is used to deactivate soft blocking due to C/I.
The values of above parameters shall be equal to or lower than the corresponding C/I target values.

Parameter
C/I target for GPRS=20 object: unit: range: default: BSC dB 0..63 (step 1) 20
Description
C/I target for GPRS (dfcaGPRSConnection_ciTarget) , this parameter sets the target C/I value for GPRS and EGPRS data connections. When territory is upgraded for GPRS, RRM uses C/I target for GPRS parameters.
C/I target SDCCH=14 object: unit: range: default: BSC dB 0..63 (step 1) 14
C/I target for SDCCH (dfcaSDCCHConnection_ciTarget) , this parameter sets the target C/I value for SDCCH connections on DFCA layer.
The values of above parameters shall be equal to or greather than the corresponding C/I softblocking values.

Parameter
DFCA MA List Group ID =1 object: unit: range: default: MALD 1..32 (step 1) 1
Description
DFCA MA List Group ID (dfcaMAListGroupId) , this parameter indicates group id of DFCA MA list so that frequencies can be reused on DFCA MA lists of different groups. This way different sets of DFCA MA lists can be done for locations with different need that are apart from each other.
DFCA MA List usage =CS and PS

object: unit: range: default: MALD CS, PS, CS and PS CS and PS
DFCA MA List usage (dfcaMAListUsage) , this parameter indicates the usage of DFCA MA list that can be defined for CS use, PS use or CS and PS use.
Grouping is implemented for DFCA MA lists. Group id is defined for each DFCA MA list and adjacent frequencies will be searched only from DFCA MA lists within the same group id. Same frequency can be reused in different DFCA MAL groups, but can exist only once within group. Only one DFCA MA list that is used for PS use can be attached to BCCH BTS. When upgrading from older release without group id or if feature state of the license SDCCH and PS Data Channels on DFCA TRX is OFF, for all DFCA MA lists group id must be automatically set to 1 and DFCA MA List usage to CS and PS.

Modified Database Parameters
Parameter
Prefer BCCH Frequency GPRS =0 object: range: default: BTS 0,1,2 0
Description
Prefer BCCH Frequency GPRS (preferBCCHfreqGPRS2), this parameter defines whether the DFCA TRX or other TRXs is preferred in GPRS channel allocation. 0 (no prioritisation is determined between TRXs), 1 (GPRS channels are allocated primarily from the non DFCA TRX), 2 (GPRS channels are allocated primarily from DFCA TRX) TRX Priority In TCH Allocation (trxPriorityInTchAlloc) , this parameter defines whether DFCA or non-DFCA TRX is preferred in TCH channel allocation. 0 = search started from DFCA layer but if there is no measurement results allocation starts from BCCH TRX 1 = search started from non DFCA layer 2 = search started from DFCA layer 3 = Search started from DFCA layer for AMR users and from regular layer for non-AMR users
TRX Priority In TCH Allocation = object: range: default: BTS 0,1,2,3 0
When PS and SDCCH are allowed for DFCA TRX there is no more reason to configure extra non DFCA TRXs. Without changing functionality of those parameters those parameters are useless with DFCA, as currently parameters works only between BCCH TRX and extra regular TRXs. When PS is allowed for DFCA TRX it is also possible that operators want to prefer DFCA or BCCH TRX either for data or speech. These parameters makes possible to define priority between BCCH TRX and rest of the TRXs in the BTS. Some cases it is reasonable to prefer BCCH TRX for speech e.g. for EFR users as BCCH TRX quality is more constant, it does not change so much according to the load of the network, where as AMR can better adapt to the quality change of non BCCH TRXs, with the link adaptation.

New counters (1)
All existing C/I related counters for DFCA measurements: DFCA C/I target DL/UL (-15..+20) incoming DL/UL C/I relative to C/I target Most interfered C/I target UL/DL (-15..+20) - outgoing worst interfered DL/UL(C/I
relative to C/I target
were enhanced with the new connection types: SDCCH PS data Analogous measurements for SAIC capable MSs were enhanced as well

New counters (2)
All existing DFCA assignment counters:
Successful DFCA assignments Successful DFCA assignments in high load Soft Block DFCA assignments due to C/I
Soft Block DFCA assignments due to C/N Primary DFCA algorithm attempts Secondary DFCA algorithm attempts
were enhanced with the new connection types: SDCCH PS data Analogous measurements for SAIC capable MSs were enhanced as well
Activation/ deactivation

Activation of the feature
1)
Reconfigure usage of DFCA MA list(s) - DFCA MA list can be defined for CS and/or PS use. Note that DFCA MA list state (DMALS) must be OUT (DFCA OUT OF USE) when usage of DFCA MA list is modified. Modify BTSs and TRXs for GPRS (PS on DFCA TRX) BTSs must be locked to modify DMAL, TRXs must be locked or GENA (GPRS disabled in BTS ) to enable GTRX (GPRS enabled TRX) and DFCA on TRX. Reconfigure DFCA MA list(s) on BTSs if needed (PS on DFCA TRX) - It may be necessary to modify DMALs that are attached to BCCH BTSs. Only one DFCA MA list for PS use (usage is CSPS or PS) can be attached to BCCH BTS before PS can be used on DFCA TRX. Because all DMALs are set for CS and PS use by default BCCH BTS may have extra lists attached that are not allowed. Extra lists can be detached from BCCH BTS or old lists can be replaced with new list(s). Consider SDCCH configuration on TRXs (SDCCH on DFCA TRX) - DFCA must be activated on all TRXs except BCCH TRX in DFCA hopping BTS. SDCCH TSLs can be configured on DFCA TRXs when TRX is locked. Consider values of TRP and BFG parameters - TRP will prefer TCH allocation between regular TRX and DFCA TRXs. BFG will prefer GPRS territory between BCCH TRX and DFCA TRXs when DFCA TRX is configured for PS use. Unlock BTSs and TRXs.
2)
3)
4)
5)
6)

Deactivation of the feature
1)
If feature state of license is deactivated, following functionality changes automatically: Dynamic SDCCH is not allowed on DFCA TRX Functionality of TRP Pre-emption on DFCA DFCA MA list usage is not available for user in creation/modify
User actions are needed for complete deactivation of the feature : SDCCH and GPRS will continue to work on DFCA TRXs until BTS or TRX is locked. DFCA hopping BTS with GPRS enabled having GPRS DFCA TRX must be configured so that GPRS and DFCA is not used at the same TRX. DFCA hopping BTS having SDCCH DFCA TRX must be configured so that DFCA TRX has only TCH TSLs configured.
2)
Expected benefits

Key benefit
No need for Regular TRXs causes that more frequencies can be
used in DFCA layer BSS 11.5 DFCA capacity improvement is limited by DCR improvement ( 100%), therefore full DL and UL Quality gains (>200%) can not be capitalized:
Besides, C/I values >> 20 dB do not bring additional benefits for

voice calls On the other hand, EGPRS performance can be significantly boosted (throughput and delay) by high quality channels
120
Link Level Throughput per TS [kbps]
110 100 90 80 70 60 50 40 30 20 10 0 -10 -5 0 5 10 15 20 25 30 35 40 45 50
DFCA capacity gains in TMO DFCA trial.
SNIR [dB]
TU3, ideal frequency hopping
MCS-1 DBS-11
DBS-5 DBS-12
DBS-6
DBS-7
DBS-8
DBS-9
DBS-10

Simulation results
Assumptions

1 DFCA TRX, BCCH blocked 6 frequencies in 1 MA list 2 Simulated services:
50% AMR HR 50% EGPRS/FTP
DFCA offers better quality and therefore throughput is higher. This implies shorter LLC delay reduction and lower TBF blocking (due to faster transmison PDCHs are occupiated shorter)

Simulation results regular scenario
8,0 7,0 6,0 5,0 4,0 3,0 2,0 1,0 0,0 7,5 12,0 14,0 17,0 20,0 23,0 Number of Terminals (x1000)
Improved FER
BQS over 4.2% (%)
CS performance improvement is kept 15% average increase in throughput is

observed
15% higher throughput
135 Throughput (Kbps)
Improvement
RFH
DFCA PS
DFCA PS CoChannel
Much less FR
100 90 80 70 60 50 40 30 20 10 0 7,5 12,0
Full rate ratio (%)
125 115 105 95 85 7,5 12,0 14,0 17,0 20,0
Improvement
23,0
Number of Terminals (x1000)

14,0 17,0 20,0 23,0 Number of Terminals (x1000)
RFH
DFCA PS
DFCA PS CoChannel
RFH
DFCA PS
DFCA PS CoChannel
Better quality TSLs

25
Average PS territory size
The last plot conveys the key message:

the average territory size is much, much smaller in the DFCA PS case, the data performance in terms of all KPIs is better DFCA PS increases EDGEs spectral efficiency
15
10 5
DFCA Co Channel is a variation where all intra cell co-channels are reallocated prior to any upgrades. The alternative is to leave them there (if any) and do not allow the upgrade to take place. The former causes a bit more HO overhead, the latter makes upgrades harder to happen
7,5
12,0
14,0 17,0 Number of Terminals (x1000) DFCA PS
20,0
23,0
RFH
DFCA PS CoChannel
Less TSLs
20
Dropped Call Ratio (%)

3,00

Simulation results irregular scenario (DFCA voice vs DFCA mixed)
Uncompromised CS performance, in fact
it even improved DFCA CS only gains are retained /
improved Conservative C/I estimations: recall that DFCA considers PS territory TSLs to be transmitting at full power all the time, even if they are not
Less DCR Improvement
2,50 2,00 1,50 1,00 0,50 0,00 7,5 12,0 14,0 17,0 20,0
23,0
Number of Terminals (x1000)
RFH_voice RFH_mixed DFCA_mixed_CoChannel

BQS over 4.2% (%)
12,0
DFCA_voice DFCA_mixed
Less FER Improvement

10,0 8,0 6,0 4,0 2,0 0,0 7,5 12,0 14,0 17,0 20,0 23,0 Number of Terminals (x1000) RFH_voice RFH_mixed DFCA_mixed_CoChannel DFCA_voice DFCA_mixed
Extra gain
DFCA delivers better quality TSLs for the

territory All data related KPI improved, e.g:
Considerable throughput and hence LLC delay gain with same average PS territory size
10,0 9,0 8,0 7,0 6,0 5,0 4,0 3,0 2,0 1,0 0,0
LLC delay (s)
Shorter Delays Improvement
7,5
12,0
14,0
17,0
20,0
23,0
Number of Terminals (x1000) RFH DFCA_mixed DFCA_mixed_CoChannel
Planning and dimensioning issues

Impact on frequency planning
Need for regular TRX reguired frequency to be assigned Frequencies for the regular TRXs can be chosen from:
BCCH band and configured to operate
(AFP tool based on IM) to avoid frequency reuse in case of strong interferers (frequency assigned to BCCH layer is reused on regular TRX the most seldom)
on non-hopping mode Assumptions a very careful planning is required
non-BCCH band and configure to

operate in hopping or non-hopping mode
With PS & SDCCH on DFCA TRX no

need for regular TRX
This makes frequency planning much easier Since frequencies used previously for regular layer now can be used for DFCA it is easier
to follow DMALs lengt limitation

Impact on dimensioning - calculation example for BSS12 (1)
Assumptions
Frequency bandwidth BCCH band Assumptions Regular layer bandwidth 6,2 12 freqs 7 hopping freqs Mhz
DFCA layer bandwidth 12 freqs Assumed traffic model Signalling traffic per user # of TSL for signalling # of TSL for PS TCH traffic per user PS users penetration HR penetration avg PS traffic per user in BH http model ftp model ftp penetration http penetration 4.0 3 (2 for SDCCH) 8 (4 on BCCH and 4 on reg LY) 25.0 30 100 200.0 5/50/0 1/4700/0 40 60 % % mErl % % bps mErl

Results: Max EFL:
on 53 (5+48) trunks (assuming 2% blocking) we can serve 42 Erlangs (here limitation comes from softblocking not hardblocking)
On reg LY EFL=16,7% ->8 Erl On DFCA EFL=28,5% ->27,36 Erl BCCH -> 1 TRX -> 1 voice trunks Reg -> 1 TRX -> 4 voice trunks (4 Erl for voice) DFCA -> 3 TRX -> 48 voice trunks Traffic = 1Erl + 4 Erl + 27,36 Erl = 32,36Erl ->1294 users Assuming 30% PS users ->388 PS users average PDCH throughput = 35.8 kbps (result comes from C/I distribution for certain load and freq reuse) from PS capacity calculation: Avg throughput for http =69 kbps = 8,625 kB/s Avg throughput for ftp = 100 kbps = 12,5 kB/s

Assumptions
Frequency bandwidth BCCH band 6,2 12 freqs Mhz
In BSS 14.0 no need for regular layer
DFCA layer bandwidth 19 freqs Assumed traffic model Signalling traffic per user # of TSL for signalling # of TSL for PS TCH traffic per user PS users penetration HR penetration avg PS traffic per user in BH http model ftp model ftp penetration http penetration 4.0 3 (2 for SDCCH) 8 (4 on BCCH and 4 on reg LY) 25.0 30 100 200.0 5/50/0 1/4700/0 40 60 % % mErl % % bps mErl

Results: Max EFL:
On DFCA EFL=29,3% ->44,56 Erl BCCH -> 1 TRX -> 1 voice trunks DFCA -> 3 TRX -> 40 voice trunks Traffic = Erlang on 41 trunks at 2%= 31,9 Erl ->1276 users Assuming 30% PS users ->382 PS users average PDCH throughput = 37.7 kbps (assuming 15% DFCA gain) from PS capacity calculation: Avg throughput for http = 71 kbps = 8,875 kB/s Avg throughput for ftp = 105 kbps = 13,125 kB/s
Traffic from softblocking = 44,56 but to reduce # of TRX we are limited by hardblocking

Summary results
DFCA reduces number of needed TRXs while the quality of PS service (in
terms of average throughput) is even better The same capacity was achieved with the lower number of needed hardware (TRXs) It would be possible (instead of reducing # of TRX) to increase number of served users. In this way higher capacity with the same number of site counts could be achieved

Calculation example for BSS12 (no PS traffic)
Assumptions
Frequency bandwidth BCCH band Regular layer bandwidth DFCA layer bandwidth Signalling traffic per user # of TSL for signalling 6,2 12 freqs 7 hopping freqs 12 freqs Assumed traffic model 6.0 4 (3 for SDCCH: 2 on BCCH, 1 on regular) 25.0 100 mErl % mErl Mhz
Results: Max EFL:
TCH traffic per user HR penetration
on regular EFL=16,7% ->7 Erl on DFCA EFL=28,5% ->27,36 Erl on BCCH 5 Erl BCCH -> 1 TRX -> 5 voice trunks regular -> 1 TRX -> 7 voice trunks DFCA -> 3 TRX -> 48 voice trunks Traffic = Erlang on 60 trunks at 2%= 39,36 Erl ->1574 users

Calculation example for BSS14 (no PS traffic)
Assumptions
Frequency bandwidth BCCH band DFCA layer bandwidth Signalling traffic per user # of TSL for signalling TCH traffic per user HR penetration 6,2 12 freqs 12 freqs Assumed traffic model 6.0 4 (3 for SDCCH: 2 on BCCH, 1 on DFCA 25.0 100 mErl % mErl Mhz
Results - BSS14 scenario 1: Max EFL: on DFCA EFL=29,32% ->44,56

Erl on BCCH 7 Erl
BCCH -> 1 TRX -> 5 trunks DFCA -> 4 TRX -> 64 trunks Traffic = Erlang on 69 trunks at 2%
= 48,56 Erl ->1942 users Here there is hardblocking limitation however with 1 TRX less we are still able to serve ~ 100 users more then with regular layer
Results - BSS14 scenario 2 (with reduced #of TRXs): BCCH -> 1 TRX -> 5 trunks DFCA -> 3 TRX -> 48 trunks Traffic = Erlang on 53 trunks at 2% = 41,1 Erl ->1644 users

Summary results
2000 1800 # of served users
Increases number of served users Achieved higher capacity with the

same number of site counts
1942
1600
1400
1200 1000 800 600 400 200 0 BSS12 1574
1644
DFCA reduces number of TRXs

needed and still serve more users
BSS14 BSS14 scenario 1 scenario 2

Impact of Dynamic SDCCH
Previously presented dimensioning results are valid in case of static
SDCCH In BSS12.0 ED 2.1 enhancement was introduced which allows for up to 3 TSLs for SDCCH on BCCH TRX and 4 TSLs for SDCCH on nonBCCH TRX. These SDCCH TSLs must be configured as dynamic SDCCHs In case of static SDCCH limitation to 2 SDCCH TSLs per TRX is still valid. Dynamic SDCCH can only be configured when optional feature Dynamic SDCCH is activated. Mixture combination of static and dynamic SDCCH is allowed eg. 2 static SDCCH TSL + 1 dynamic on BCCH TRX 2 static SDCCH TSL + 2 dynamic on non - BCCH TRX Next slides gives the comparison between BSS 12.0 , BSS 12.0 ED 2.1 (with dynamic SDCCH) and BSS14

Calculation example: BSS12 vs BSS 12 ED2.1 (no PS traffic, static SDCCH)
Assumptions
Frequency bandwidth BCCH band Regular layer bandwidth DFCA layer bandwidth Signalling traffic per user # of TSL for signalling TCH traffic per user HR penetration
BSS 12
6,2 MhZ 12 freqs 7 hopping freqs 12 freqs Assumed traffic model 8 mErl 4 (3 for SDCCH) 25 mErl 100%
BSS 12 ED2.1
6,2 Mhz 12 freqs no need for regular LY 19 freqs 8 mErl 4 (3 for SDCCH) 25 mErl 100%
Results
max traffic on BCCH LY max EFL (max traffic) on regular LY max EFL (max traffic) on DFCA LY # of voice trunks on BCCH LY # of voice trunks on regular LY # of voice trunks on DFCA LY Total traffic / # of users
BSS 12
5 Erl 16,7% -> 7 Erl 28,5% -> 27,36Erl 5 trunks (on 1 TRX) 7 trunks (on 1 TRX) 48 trunks (on 3 TRXs) 39.36 Erl / 1574 users
BSS 12 ED2.1
4 Erl N/A 29,32% - > 44,56 Erl 4 trunks (on 1 TRX) N/A 64 trunks (on 4 TRXs) 48.56 Erl / 1924 users
Assuming 8 mErl/user of SDCCH traffic dynamic SDCCH allows to avoid regular TRX and in this way to serve more users. There is no need for SDCCH on DFCA.

Calculation example: BSS 12 ED2.1 vs BSS 14 (no PS traffic, dynamic SDCCH)
Assumptions
Frequency bandwidth BCCH band Regular layer bandwidth DFCA layer bandwidth Signalling traffic per user # of TSL for signalling TCH traffic per user HR penetration
BSS 12 ED2.1
6,2 MhZ 12 freqs 7 hopping freqs 12 freqs Assumed traffic model 11 mErl 5 (4 for SDCCH) 25 mErl 100%
BSS 14
6,2 Mhz 12 freqs no need for regular LY 19 freqs 11 mErl 5 (4 for SDCCH) 25 mErl 100%
Results
max traffic on BCCH LY max EFL (max traffic) on regular LY max EFL (max traffic) on DFCA LY # of voice trunks on BCCH LY # of voice trunks on regular LY # of voice trunks on DFCA LY Total traffic / # of users
BSS 12 ED2.1
4 Erl 16,7% -> 7 Erl 28,5% -> 27,36Erl 4 trunks (on 1 TRX) 7 trunks (on 1 TRX) 48 trunks (on 3 TRXs) 38.36 Erl / 1534 users
BSS 14
4 Erl N/A 29,32% - > 44,56 Erl 4 trunks (on 1 TRX) N/A 64 trunks (on 4 TRXs) 47.56 Erl / 1902 users
Assuming 11 mErl/user of SDCCH traffic dynamic SDCCH does not allow to avoid regular TRX. In this scenario only SDCCH on DFCA TRX feature allows to avoid regular layer.
Feature impact analysis

Feature Impact Analysis
Feature impact Reasoning
More freqs in DFCA layer (due to no need for regular) causes better quality TSLs what means higher MCS used more frequent Higher MCS used more often, means higher thoughput
How to measure
KPI: DL ACK RLC data share MCS-n, (rlc_24) DL UNACK RLC data share MCS-n, (rlc_25) KPI: Volume Weighted LLC Throughput (llc_3a) KPIs: Average DL TBF Duration (tbf_6c)
Higher MCS used more freqent
Higher LLC Data Throughput
Shorter DL TBF Duration
Higher thoughput means shorter TBF duartion
Higher application data throughput and reduced user perceived delay
Better quality TSLs means, higher MCS what gives higher throughput; all together causes shorter transmission delay
Drive tests required
In order to be able to observe expected benefits fair comparison is needed eg. PS on hopping with certain number of hoppers shall be compared with PS on DFCA with the same amount of freqs. (assuming the same CS & PS load)

Feature Impact Analysis
Following CS KPIs should be monitored in order to see if DFCA gain for CS was not lost: Feature impact
KPI: SDCCH blocking
How to measure
SDCCH Access Probability (SDR_1a)
KPI:
SDCCH drop rate
SDCCH Access Probability (CSF_1a)

KPI:
Dropped Call Rate
Dropped Call Rate (dcr_3i)

KPI: Bad DL Qual (x=5,6,7) (qdl_2) Bad UL Qual (x=5,6,7) (qul_2) KPI: Bad UL FER Rate (>4,2%) (ulq_3)
RxQual
Bad Quality Samples (FER>4,2%)

Summary
PS and SDCCH on DFCA TRX allows to get rid of regular TRX what
makes MA list planning a lot easier as there is no more need to define frequencies for regular TRXs
With PS and SDCCH on DFCA TRX old CS performance

improvements are not compromised no matter how many TRXs is needed for PS traffic.
PS on DFCA TRX offers better PS performance since DFCA delivers

better quality TSLs for the territory
Thank you for your attention!
Backup slides
MA encoding
PS Immediate Assignment message
In psw_territory_upgrade_s message PCU receives the DFCA hopping data (MA list, MAIO and TSC) to be included in the PS Immediate Assignment message. The MA list in BCCH BTS is always the MA list that is broadcasted in SI13 message (or in PSI14 message if that is used). So in this case indirect MA list coding method is used. In case that there is in a non BCCH band a BTS with DFCA PS TRX that have DFCA MA list that includes only one frequency, PCU can use the fixed frequency definitions to assign MS to the non BCCH band BTS. This makes possibly to use non BCCH band also for immediate assignments with DFCA
Backup slides
MA encoding
PS Assignment message
In the PS Assignment messages PCU uses the hopping data received in the psw_territory_upgrade_s message. The hopping data in the psw_territory_upgrade_s message includes frequency list for GPRS hopping, MAIO and TSC for the GPRS TRX. In the BCCH BTS the MA list is always the list that is broadcasted in SI13 message or in PSI14 and hence indirect MA list coding must be used. In non BCCH BTS the MA list is different than the broadcasted MA list and can be different also in every TRX, in this case PCU must use direct coding 2 .
Backup slides
Frequency parameters IE

DFCA

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

DFCA

Enviado por

Direitos autorais:

Formatos disponíveis

BSS14 Network Engineering Information

PS & SDCCH ON DFCA TRX BSS21161

BSS14 PS & SDCCH ON DFCA TRX

BSS21161 PS & SDCCH ON DFCA TRX

BSS14 is supported by the following NE releases: NetAct OSS5.1 CD set 3, MSC

BSS21161 PS & SDCCH ON DFCA TRX

BTS Ultra Site

BTS Metro Site

BTS Talk Family

BTS Prime Site

2nd Gen BTS

BTS Flexi EDGE

PS & SDCCH ON DFCA TRX BSS21161

DFCA overview DFCA channel selection

History & Reason for Introduction

Activation & deactivation

Feature impact analysis

Dynamic Frequency & Channel Allocation

It is a revolutionary approach for managing the frequency usage in the

Dynamic Frequency & Channel Allocation

Bandwidth and Frequency Challenged Operators

Operators Re-farming GSM Frequencies to WCDMA

Dynamic Frequency & Channel Allocation

Loose interference control Relies on random spreading of the interference

C/I > C/I target

Dynamic Frequency & Channel Allocation

BTS with LMU

Dynamic Frequency & Channel Allocation

Statistical C/I data is available for non-reported neighbors

Dynamic Frequency & Channel Allocation

BTS6 BCCH 102 BSIC 54

BSIC 54 22 --BSIC 22 ---

C/I (dB) 12 18 --C/I 15 ---

SEG Id 6 12 --SEG 12 ---

Missed update 0 0 ---

BTS1 Outgoing BIM

BTS6 Incoming BIM

BTS6 Outgoing BIM

BTS12 Incoming BIM

BTS12 Outgoing BIM

DFCA channel selection

Dynamic Frequency & Channel Allocation

Channel selection overview

For each DFCA BTS

For each BSC

Choose the most suitable

Above soft blocking threshold

Dynamic Frequency & Channel Allocation

BCCH, BSIC 102, 23 114, 52 104, 12 116, 32 108, 12 111, 43

Average C/I (BIM scaling factor):

Dynamic Frequency & Channel Allocation

Channel being checked: TSL 1, MA 2, MAIO 1

Incoming BIM (100, 01)

C/I diff C/I real C/I target after PC

102, 23 114, 52 104, 12 115, 30 101, 52 116, 32 103, 06 108, 12 111, 43

DL tx power reductions from DFCA RR table

18 +4 +4 = 26 102, 23 104, 12 116, 32 103, 06 108, 12 102, 36 6 dB 8 dB 10 dB 0 dB 0 dB 4 dB

102, 23 114, 52 104, 12 116, 32 108, 12 111, 43

BIM scaling factor +4 dB

Dynamic Frequency & Channel Allocation

Same propagation path opposite direction

Existing connection New connection

DL & UL interference propagation paths