TIS, Demystify Auto Configuration

v03, 13.May08
by, FJ Guenster & LIM, Seau Sian

Demystify AutoConfiguration:
PSC Selection background (phase-3)
Starting conditions: On the FMS the following parameters need to be provisioned: ( phase-3)
Name Description Syntax Values Default Rqd on Attr Interfaces
create Handl.

identityCheckEnable Indicate whether to perform identity check during boolean true no RW bulkcm, bsrprofile
dAutoConfig auto-configuration

femtoPSCStartRange Define the starting PSC of the femto PSC range integer [0..496] 0 no RW-RR, itf-bsr,
RW bulkcm, bsrprofile
femtoPSCRangeLeng Define the ending PSC of the femto PSC range integer [0..15] 15 no RW-RR, itf-bsr,
th RW bulkcm, bsrprofile
femtoPSCReservedIn Define the reserved femto PSC during auto- integer [1..16] 1 no RW bulkcm, bsrprofile
dex configuration
autoConfigProcedure Define the over-arching timer for the auto- integer [0..65535], 120 no RW bulkcm, bsrprofile
Timer configuration and is the maximum duration from unit=secs
receiving the indication from HNMS to start auto-
configuration to the H-BSR successfully re-create the
femto cell.
autoConfigProcedure Define the over-arching timer for the auto- integer [0..65535], 60 no RW bulkcm, bsrprofile
TimerSqInit configuration during subsequent initialisation and is unit=secs
the maximum duration from the BSR ready to
perform auto-configuration (i.e. all essential auto-
configuration parameters available) to start auto-
configuration to the H-BSR successfully re-create the
femto cell. If this attribute is set to 0, the BSR shall
skip auto-configuration.
autoConfigCMDelta Define the Radio Bearer Reconfiguration latency delta integer [-255..255] -10 no RW bulkcm, bsrprofile
during autoconfiguration
randomFemtoPSCpick Indicates whether to randomly pick a Femto PSC boolean true no RW bulkcm, bsrprofile
if initial PSC selection is not performed
TIS, Demystify Auto Configuration
v03, 13.May08
by, FJ Guenster & LIM, Seau Sian
How the Auto configuration of the PSC parameter work in Examples

0. Basics about the changeable Parameters:

0.a. Femto PSCStartRange 454
FemtoPSCRangelength 2
FemtoPSCReservedindex 1
i.e. >>> [454,455,456]
>>> First Femto initally start up with PSC=454
(according to index/reserved No.1)
>>> Picks PSC 455 or 456 after the UE measurement e.g. 455
>>> 2nd Femto initally start up with PSC=454
(according to index/reserved No.1)
>>> Picks PSC 456 after the UE measurement, for this example
>>> 3rd Femto initally start up with PSC=454
(according to index/reserved No.1)
>>> Picks PSC 455 or 456 after the UE measurement
(The UE measures the CPICH RSCP of the set PSC range)
Note: The 3rd Femto picks the same PSC with the lowest interference
hence the PSC of the Femto that is farthest from the 3rd Femto.

0.b. Start 454

length 1
index 1
i.e. >>> [454,455]
>>> First Femto initally start up with PSC=454
(according to index/reserved No.1)
>>> Picks PSC 455 after the UE measurement

---------------------------------------------------------------------------------------------
0.c. Start 454
length 3
index 2
i.e. >>> [454,455,456,457]
>>> First Femto initally start up with PSC=455
(according to index/reserved No.2)
>>> Picks PSC 454 or 456 or 457 after the UE measurement
Note: The PSC is basically randomly picked if you have 3 PSCs and only
one Femto and no interference on both PSC.
TIS, Demystify Auto Configuration
v03, 13.May08
by, FJ Guenster & LIM, Seau Sian

1. Marco and Femto NW relation for PSC:

The UE measures the PSC that are on air, the UE Measurement cannot distinguish
between Macro or Femto NW.
e.g.
Start 454
length 2
index 1
i.e. >>> [454,455,456]
Macro: same Freq.+ PSC= 455
No Femto on Air (Femto1 and Femto2 off)
1.1. Now switch on Femto1.
1.2. Femto1 start up with PSC=454 (according to index/reserved No.1)
1.3. If a UE is close by and registered in the ACL of Femto1 it will
make location update and inform Femto1
1.4. Femto1 moves to PSC 456, because 454 is reserved for initial
setting, 455 is already on Air for the Macro NW.
Therefore only 456 is free with (due to EcNO measurement,
no Interference)
Note: Nevertheless from a NW planning point of view, there should not be an overlap
of PSC ranges between Marco and Femto NW.
The Operator is advised to take different ranges for Femto and Macro NW.
TIS, Demystify Auto Configuration
v03, 13.May08
by, FJ Guenster & LIM, Seau Sian

2. Subsequent reboot , in other words a reboot after the very first (initial) Auto
Configuration:
2.0. conditions, e.g.:
Start 454
length 3
index 1
i.e. >>> [454,455,456,457]
2.1. Initial Auto configuration finished for Femto1 (PSC=455) and
Femto2 ( PSC=456)
2.2. Now reboot both (Switch off and then on Femto 2 and then Femto 1 later)
2.3. The Timer autoConfigProcedureTimerSqInit= 60sec gets in to play !
2.4. Now we manage that the Femto2 startup first
2.4.1. If the UE is close to the Femto and the UE send within 60sec
measurement to the Femto2, Femto will come up with either
PSC 455 or 456or 457 due to CPICH RSCP Measurement and
random choice out of the Range e.g. PSC=457
2.4.2. If the UE is not close or the Measurement is not send to the
Femto2 within 60sec the Femto2 remembers its old set value
PSC=456.
2.5. Femto1 does accordingly:
a. In case of 2.4.1.
a1: If the UE on Femto1 is close and send Measurement with in 60 sec,
the Femto1 gets PSC= 455or 456 for this example

a2: If the UE is not close or the Measurement is not sent to the Femto2
within 60sec the Femto1 remembers its old set value
PSC=455.

b. In case of 2.4.2.
b1: If the UE on Femto1 is close and send Measurement with in 60 sec,
the Femto1 gets PSC= 455 or 457 for this example
Due to the fact that Femto2 is already on PSC=456

b2: If the UE is not close or the Measurement is not send to the Femto1
within 60sec the Femto1 remembers its old set value PSC=455.
TIS, Demystify Auto Configuration
v03, 13.May08
by, FJ Guenster & LIM, Seau Sian
3. Sequential start up of 3 BSR femto and PSC Random Pick

femtoPSCStartRange 60
femtoPSCRangeLength 3
femtoPSCReservedIndex 1
autoConfigProcedureTimer 120sec , default
autoConfigProcedureTimerSqInit 60sec, default

We will switch on Femto-1, Femto-2, Femto-3.

Now be careful as the two timers get into play !

1. Femto-1,-2,-3 will get directly after DB dload for Autoconfiguration from

FMS always PSC=60, as the femtoPSCReservedIndex is set to 1.
In other words, the first PSC out of the entire range is reserved for the initial
PSC.
Note:
The 3 values for the Range will be (femtoPSCStartRange +1) =61 and 62,
and 63.
This means the operator need to reseve 4 PSC for the entire Range of this
example for the Femto NW= [60,61,62,63]

2. Assuming Femto-1 comes up first. If a UE is next to the Femto-1 (approx. 1m)

and its IMSI is registered on the Femto-1, the Femto-1 will change its PSC to
61 or 62 or 63 based on UE measurement. This will happen when the UE
makes a location update on the Femto-1. You may have to force the location
updated by power off/on the UE.

If there is no UE next to the e.g. Femto-1 then the autoConfigProcedureTimer

gets in to the game!

3a. Femto-1 will initaly come up with PSC 60 as above

3b. autoConfigProcedureTimer expires after 120sec with no UE on this
Femto-1
3c. If randomFemtoPSCpick is true then the Femto-1 will pick one PSC from
the Range [61,62,63] by itself and with a probability in this case of 33%.
note: The BSR will randomly select a femto PSC from the PSC range (minus
the reserved PSC) to radiate regardless of the CPICH RSCP.
3d. This randomly picked PSC is stored on the Femto-1, e.g. PSC=62

3. If you now power cycle the Femto-1 and put a UE is next to the Femto-1,
within the duration of autoConfigProcedureTimerSqInit then the Femto-1 will
pick a new PSC based on UE measurement e.g. PSC=61. In the case that the
autoConfigProcedureTimerSqInit=60sec expires due to the fact that the UE is
not close or the Measurement is not send to the Femto1 within 60sec
(depending onUE) the Femto1 remembers its old set PSC=62.

Note: Incase 3c. the randomFemtoPSCpick is False the Femto-1 will stop transmitting
and indicate an alarm with its LED.