23.1953GPPProvision of User Equipment Specific Behaviour Information (UESBI) to network entitiesRelease 5TS

For the intra-3G_MSC A/Gb mode to Iu mode handover procedure described in 3GPP TS 23.009 [5], the UESBI-Iu shall be sent from the 3G_MSC to the target RNS in the Iu Relocation Request message.

The Basic Inter-MSC Handover A/Gb mode to Iu mode is illustrated in Figure 5.2.9-1 (copied from 3GPP TS 23.009 [5]).

Figure 5.2.9-1: A/Gb mode to Iu mode inter-MSC handover

A/Gb mode to Iu mode handover is initiated as described in 3GPP TS 23.009 [5].

1 The UESBI-Iu is NOT sent by BSS-A to MSC-A.

2 MSC-A derives the UESBI-Iu from the IMEISV The UESBI-Iu shall be sent by 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 MSC-A does not support the PUESBINE Feature) then 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 include the UESBI-Iu in the Iu-RELOCATION-REQUEST message sent to the target RNC.

If the RNC does not receive the UESBI-Iu in the Iu-RELOCATION REQUEST message (eg because either MSC-A or 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 [5].

For subsequent Inter-MSC handover, MSC-A shall transfer the UESBI-Iu to MSC-B’.