Catalog of RANAP Message

RANAP messages can be classified as

follows:
 Iu signal link establish/release/direct transfer
Relocation

 RAB assignment/Security/Co-ordinate Paging

 PS domain specific procedure

Connectionless procedure

 UE tracing and location report

Brief of RANAP Message in PS domain

Signalling transport shall provide two different service modes for the RANAP.

1.Connection oriented data transfer service.

This service is supported by a signalling connection between RNC and CN domain. It
shall be possible to dynamically establish and release signalling connections based on
the need. Each active UE shall have its own signalling connection. The signalling
connection shall provide in sequence delivery of RANAP messages. RANAP shall be
notified if the signalling connection breaks.

2.Connectionless data transfer service. RANAP shall be notified in case a RANAP

message did not reach the intended peer RANAP entity.
RANAP_RELOCATION_PREPARATION_FAILURE

Problem Description
All the Inter RNC handovers failed with the trace message RANAP_RELOCATION_PREPARATION_FAILURE.
      
Attached the respective traces.
      
Handling Process
After we analysed the traces, we found out that the cause for the RANAP_RELOCATION_PREPARATION_FAIL
URE was "Relocation not supported in
target RNC or target system".
      
Root Cause
N/A
Solution
We checked the ADD NRNC command settings on the RNC and we found out that the "SHOHHOTRIG" parameter 
was set to OFF. This parameter
indicates whether to trigger soft handover and hard handover cross the Iur interface between the RNC and the neigh
boring RNC. So  this was the 
reason why the RNC wasn't accepting Iur relocations.
      
Suggestions and Summary

none.

Download

 (Main Document) RANAP_RELOCATION_PREPARATION_FAILURE

 ( Attachments ) RNC60_CMB_Iu_2006-04-20-14-39-37.tmf