Cisco Cisco ASR 5000
InTracer Support for SGSN
How it Works ▀
SGSN Administration Guide, StarOS Release 18 ▄
How it Works
Architecture
The figure below depicts different signaling messages exchanged between SGSN and the IPMS server during a GMM
attach procedure.
attach procedure.
Figure 47. GMM Attach Request message from MS
The GMM attach request received by the SGSN via the BSC is sent from the BSSGP stack to the IPMS server along
with identities like call-id. As and when the SGSN learns about the subscriber's IMSI, it is communicated to the server
along with call-id as a standalone message but the PDU will be absent in the message.
with identities like call-id. As and when the SGSN learns about the subscriber's IMSI, it is communicated to the server
along with call-id as a standalone message but the PDU will be absent in the message.
Identities in Signaling Messages
This section describes how the SGSN obtains knowledge of different subscribers and MS identities from various
signaling messages.
signaling messages.
1. IMSI: The SGSN obtains the subscriber's IMSI from:
IMSI attach request from the MS.
Identity response for IMSI from the MS during the local or non-local PTMSI-Attach procedure.
GTP identification procedure for IMSI during a non-local PTMSI-Attach procedure.
SGSN Context Response during an Inter SGSN RAU procedure.
2. IMEI/IMEISV: The SGSN obtains mobile station's IMEI/IMEISV from:
Authentication response with IMEI/IMEISV from MS during Attach or RAU procedure.
Identification procedure for IMEI/IMEISV from MS during the Attach or RAU procedure.
SGSN Context response during inter SGSN RAU procedure.