23.1953GPPProvision of User Equipment Specific Behaviour Information (UESBI) to network entitiesRelease 5TS
For the intra-3G_MSC SRNS relocation procedure described in 3GPP TS 23.009 , the 3G_MSC-B shall send the UESBI-Iu to the target RNS in the Iu Relocation Request message.
The Inter-MSC SRNS relocation procedure is illustrated in Figure 5.2.12-1 (copied from 3GPP TS 23.009) .
Figure 5.2.12-1. Inter-MSC SRNS relocation
Inter-MSC SRNS relocation is initiated as described in 3GPP TS 23.009 .
1 The UESBI-Iu is NOT sent by RNS-A to 3G_MSC-A.
2 3G_MSC-A derives the UESBI-Iu from the IMEISV. The UESBI-Iu shall be sent by 3G_MSC-A to 3G_MSC-B in the MAP_Prepare_Handover request message.
If 3G_MSC-B did not receive the UESBI-Iu (for example because 3G_MSC-A does not support the PUESBINE Feature) then the 3G_MSC-B shall ignore this fact.
3 3G_MSC-B shall store the UESBI-Iu in case it is needed for a later inter RNC intra MSC-B handover.
4 3G_MSC-B shall send the UESBI-Iu to the target RNC in the Iu-RELOCATION-REQUEST message.
If the RNC does not receive the UESBI-Iu in the Iu-RELOCATION REQUEST message (eg because either 3G_MSC-A or 3G_MSC-B does not support the PUESBINE Feature) then the RNC shall not reject the Iu-RELOCATION REQUEST because the UESBI-Iu is missing.
The rest of the steps are as described in 3GPP TS 23.009 .
For Subsequent Inter-MSC handover, MSC-A shall transfer the UESBI-Iu to MSC-B’.