Call Flow for 2G

BSC IPs are defined in gbctx in CGSN. Also defined in gbctx are the MCC/MNC of the circles and their location area codes which are homed to the particular CGSN. When a 2G call lands on gbctx it is diverted to context ss7ctx via an associate-service map (associateservice map map context ss7ctx) The ss7ctx is connected to the HLR. The map-service map has IMSI ranges defined which act as filters to allow a range of IMSI The map-service map also indicates use of SCCP protocol Then the SGSN refers to global-title-translation association instance 1. This defines the action id for incoming IMSI and also the STP to which it has to be forwarded. Action id 1 indicates match only the 1st digit of the IMSI. Also the global-title-translation address-map instance 11 defined the self GT of the SGSN for reverse routing for STP. Thus it is forwarded to the HLR for authentication. Now after authentication the user is trying to access data services. It will hit the sgsn-global table in Global configuration mode. In this table operator-policies are defined for imsi-ranges of MCC/MNC The operator-policies in turn direct the APNs to their apn profiles. Also each operator policy directs the call to its call-control-profile (* Dont know what call-control-profiles decide) The apn-profiles provide the GGSN gateway address and pdp properties. For Eg. An APN of Rcomnet for a Mumbai Subscriber (MCC/MNC 405/15) on Mumbai CGSN has and operator policy of 3. The operator-policy-3 has a call-control-profile of 0 & apn profile for rcomnet is 0 The apn-profile-0 has a GGSN gateway address of 115.255.8.82 which is the local GGSN IP address. Now a create PDP request is sent to the gateway GGSN with the virtual apn for rcomnet.2g.postpaid or rcomnet.2g.prepaid The virtual apn is formed by concatenating a) The APN user is trying (rcomnet, rcomwap, rcommms or blackberry), b) The network user is latching to (2G or 3G) c) Customer type (postpaid or prepaid) as obtained from HLR The GGSN searches for the APN in the 4 contexts

a) giintctx ( for rcomnet) b) gibbctx ( for blackberry) c) giwdvpnctx ( for vpn apns) d) girapctx ( for mms) These 4 contexts have a parent APN configured in which we define the virtual APNs The virtual apn profile defines what is to be done with the subscriber in terms of accounting, authentication and charging. For eg Rcomnet postpaid requests are forwarded to Tekelec PCRF for policy control. Whereas Rcomnet prepaid requests are forwarded to Comverse IN for prepaid charging. In addition to this the virtual apn profile also defines the IP address to be given to the subscriber, DNS servers, the accounting mode and QoS action in case QoS is not provided by the PCRF. For VPN the parent apn defines the virtual apn domain name. The domain name defines the L2TP TEP for the customer. Now the IP address is assigned to the subscriber and the PDP is created. Now the user can access his 2G services.