5.2.13 Intra- and inter-SGSN SRNS relocation

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

For the intra SGSN SRNS relocation procedure, the SGSN shall send the UESBI-Iu to the target RNS in the Iu Relocation Request message. The Inter-SGSN SRNS relocation is illustrated in FigureĀ 5.2.13-1 (copied from 3GPP TS 23.060 [4]).

Figure 5.2.13-1. Inter-SGSN SRNS relocation

Inter-SGSN SRNS relocation is initiated as described in 3GPP TS 23.060 [4].

2 The UESBI-Iu is NOT sent by the Source RNC to the old SGSN.

3 In case of inter-SGSN SRNS relocation, the old SGSN initiates the relocation resource allocation procedure by sending a Forward Relocation Request message to the new SGSN. The old SGSN shall include the IMEISV in the Forward Relocation Request message.

If the new SGSN did not receive the IMEISV in the Forward Relocation Request message (for example because the old SGSN does not support the PUESBINE Feature), then the new SGSN shall get IMEISV from the MS during the Routing Area update procedure (step14). In this case the new SGSN shall send the UESBI-Iu to the RNC during step 14.

4 The new SGSN shall use the IMEISV to obtain the UESBI-Iu and then the new SGSN shall send the UESBI-Iu in the Relocation Request message to the target RNC.

If the target RNC did not receive the UESBI-Iu in the Relocation Request message (for example because either the old or the new SGSN does not support the PUESBINE Feature) then the RNC shall not reject the Iu-RELOCATION REQUEST because the UESBI-Iu is missing.

At point 14, Inter-SGSN Routing Area Update is performed as described in clause 5.2.4.

The rest of the steps are as described in 3GPP TS 23.060 [4].