5.2.3 Combined PS and CS attach with Gs

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

The Combined GPRS / IMSI Attach procedure is illustrated in Figure 5.2.3-1 (copied from 3GPP TS 23.060 [4]).

Figure 5.2.3-1: Combined GPRS / IMSI attach procedure

1-4) Steps 1-3 are as described in TS 23.060 [4].

4a,b,c) The equipment checking functions are defined in the clause "Identity Check Procedures" in 23.060 [4]. The SGSN shall obtain and store the IMEISV. Equipment checking with the EIR is optional.

The SGSN can use either the GMM Identification procedure or the GMM Authentication and Ciphering procedure to obtain the IMEISV (see TS 24.008 [3]).

If the GMM Identification procedure is used to obtain the IMEISV (and the GMM Identification Request is sent before the GMM Authentication and Ciphering Request message), then it depends upon the SGSN implementation as to whether the UESBI-Iu information is sent to the RNC before or after the GMM Authentication and Ciphering Request message.

4d, 5) 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).

6-7) Steps 6 and 7 are as described in TS 23.060 [4].

8a) 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.

8) Steps 8b to 8h are as described in TS 23.060 [4].

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