Nothing Special   »   [go: up one dir, main page]

Ericsson Irat HO - Details

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 14

IRAT HO

Definition , Why use Irat ?

Definition:
Inter-system handover is a Ho between GSM and WCDMA
networks and vice versa.

Why:
Integrate both systems as one network and guarantee that the
services will not be disrupted when a customer moves in the coverage
area. The used GSM and WCDMA radio access layers need to
integrate and operate as one seamless cellular network.

Page 2
Definition , Why use Irat ?
Strategy - Example

UTRAN

Conected mode Idle mode GSM

GSM_p GSM_p
None None None None None
referred referred

GSM GSM GSM GSM GSM GSM GSM GSM GSM

Page 3
Definition , Why use Irat ?
Irat Process

Page 4
Definition , Why use Irat ?
Connection Monitoring
- Check if current DL and UL coverage is good.

How : Monitoring the Connection in DL and UL

DL : CPICH Ec/No and CPICH RSCP : 2d and 2f

UL : UE TX power : 6d and 6b

Page 5
Events
Compressed Mode events
2d event trigger:
usedFreqThresh2dEcno+ serviceOffset2dEcno
Or
usedFreqThresh2dRscp+ serviceOffset2dRscp.

2f event trigger:
usedFreqThresh2dEcno+ serviceOffset2dEcno+ usedFreqRelThresh2fEcno
and
usedFreqThresh2dRscp+serviceOffset2dRscp+usedFreqRelThresh2fRscp

6d event trigger:
UE Tx Power reaches maximum during timeToTrigger6d
6b event trigger:
ueTxPowerThresh6b

Page 6
Events
Compressed Mode
Action1: UE enters
Compressed Mode and
starts measuring IRAT/
IFHO neighbors

Action2: UE exits
Compressed Mode
and stops measuring
IRAT/IFHO neighbors

1 2

Page 7
Events
Irat Events

3a event trigger:
usedFreqThresh2dEcno+ serviceOffset2dEcno+ utranRelThresh3aEcno
or
usedFreqThresh2dRscp+ serviceOffset2dRscp+ utranRelThresh3aRscp

and gsmThresh3a

Page 8
Events
Irat

Action: UE asks to perform IRAT HO on a selected GSM cell

Page 9
Events
Parameters
usedFreqThresh2dEcno-Utrancell
serviceOffset2dEcno-UeRc
usedFreqThresh2dRscp-Utrancell
serviceOffset2dRscp-UeRc
usedFreqRelThresh2fEcno-UeMeasControl
usedFreqRelThresh2fRscp-UeMeasControl
timeToTrigger6d-UeMeasControl
ueTxPowerThresh6b-UeMeasControl
timeTrigg6b-UeMeasControl
utranRelThresh3aEcno-UeMeasControl
gsmThresh3a-UeMeasControl

Page 10
Parameters
Troubleshoot

Phases
- Preparation Phase

- Execution Phase

- Confirmation Phase

Page 11
Troubleshoot
Troubleshoot

Page 12
Troubleshoot
Troubleshoot
Failures in the Preparation Phase
Once the RNC determines that a handover to 2G is necessary, it contacts
the 2G Network via the 3G MSC and starts a timer. If the 3G MSC comes
back with a negative response or if the timer expires before the 3G MSC
comes back with a response, then the handover is considered unsuccessful

Failures in the Execution Phase


If after receiving the handover command from the RNC the UE cannot
make it on the 2G network, it will try come back to the 3G network and will
advise the RNC that the handover was unsuccessful

Failures in the Confirmation Phase


If the RNC does not receive confirmation from the 2G network that the
handover was successful and it does not hear back from the UE, the
handover is considered unsuccessful (IRAT drop)

Page 13
Troubleshoot
Troubleshoot
Failures in the Preparation Phase
 Majority of Problems due to “Relocation Failure in Target CN/RNC or
Target System”.
 Typically indicates incorrect data in external GSM table (i.e. 3G MSC
sends a cell ID that the 2G MSC does not know about).
 For this failure, an audit of the UTRAN target GSM cell information is
recommended.

Failures in the Execution Phase


 Majority of the problems may be associated “Physical Channel Failures”
and these failures could be related to:
• Co-BCCH/BSIC ambiguity
• Missing GSM neighbor
• GSM NL too long (NL selection truncates important GSM neighbors)
• GSM target cell quality degradation (degrades significantly so that
IRAT handover was not able to complete)
Page 14
Troubleshoot

You might also like