5.2.5 Inter-SGSN routeing area update with Gs

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

The Combined RA / LA Update (inter-SGSN) procedure is illustrated in Figure 5.2.5-1 (copied from 3GPP TS 23.060 [4]).

Figure 5.2.5-1: Combined RA / LA update in the case of inter-SGSN RA ppdate procedure

1) The MS sends a Routeing Area Update Request to the new SGSN (see TS 23.060 [4]).

2) The new SGSN sends SGSN Context Request to the old SGSN and the old SGSN returns the SGSN Context Response message (see TS 23.060 [4]).

The IMEISV shall be sent by the old SGSN to the new SGSN at inter-SGSN Routeing Area Update in the SGSN Context Response message (see TS 29.060 [11]). GTPv1 is assumed to be available in both SGSNs.

The new SGSN derives the UESBI-Iu from the IMEISV.

3a, b, c, d) If the new SGSN does not receive the IMEISV from the old SGSN (eg because the old SGSN does not support the PUESBINE Feature) then the new SGSN shall either use the GMM Identification procedure or the GMM Authentication and Ciphering procedure to obtain the IMEISV from the UE (see TS 24.008 [3]).

The new SGSN shall transfer the UESBI-Iu to the RNC over the Iu interface. The order of 3a and 3c is dependent upon the implementation of the SGSN.

The SGSN shall send the UESBI-Iu information to the RNC before sending the RANAP Security Mode Command message to the RNC.

If the RNC does not receive the UESBI-Iu information before the RANAP Security Mode Command, then the RNC should assume that no UESBI-Iu information is available for this UE (for example, because the SGSN does not support the PUESBINE Feature) (unless, in the case of non-combined RA update, the RNC has already received UESBI-Iu from the Iu-cs interface).

4 -10) Steps 4 to 10 are as described in TS 23.060 [4].

11) The SGSN shall send the IMEISV to the MSC in the Gs interface Location Update Request message.

If the MSC does not receive the IMEISV in Gs interface Location Update Request message (eg because the SGSN does not support the PUESBINE Feature) then the MSC shall obtain the IMEISV from the UE at the next Iu-cs or A interface connection establishment.

12-16) Steps 12 to 16 are as described in TS 23.060 [4].