GPRS Course Contents

Day-1 Introduction to GPRS

• Packet Switching
• GPRS basics (Coding schemes, etc,)
• GPRS network architecture
• GPRS functioning - Attach, PDP context activation, Concept of APN
• Mobile Terminal & Modes of Operations, Cell reselection
• Demo of GPRS sessions, Internet browsing using laptop, WAP, MMS
• Hands-on for using GPRS service

Day-2 GRPS core

• PCU
• GSN Complex
• SGSN
• GGSN
• DHCP and AAA RADIUS
• ISS (Charging gateway, DNS)
• CommHub
• APN configuration
• OMC-G

Day-3 GPRS provisioning and Billing

• GPRS provisioning on HLR

• Static vs. dynamic IP
• GPRS CDRs
• Integration with Billing for packetized billing
• GPRS drive testing
Day-4 GPRS applications and GPRS roaming

• WAP
• MMS
• Games download
• Realtime charging for prepaid subscribers
• On-line lottery, ATM service
• GPRS Roaming concept
• GRx architecture
• Integration with GRx.
• GPRS extended to circles using common core
• Advantages of common core
• Requirements from Circle end
 Introduction
GPRS Stands for General Packet Services. It is a new standard that provides packet
switching within a GSM network.

GPRS uses a packet-mode technique to transfer high-speed and low-speed data and
signaling in an efficient manner. GPRS optimizes the use of network and radio resources.
Strict separation between the radio subsystem and network subsystem is maintained,
allowing the network subsystem to be reused with other radio access technologies. GPRS
does not mandate changes to an installed MSC base. New GPRS radio channels are
defined, and the allocation of these channels is flexible: from 1 to 8-radio interface
Timeslots can be allocated per TDMA frame, timeslots are shared by the active users, and
up and downlinks are allocated separately. The radio interface resources can be shared
dynamically between speech and data services as a function of service load and operator
preference. Various radio channel coding schemes are specified to allow bit rates from 9
to more than 150 kbit/s per user. Applications based on standard data protocols are
supported, and interworking is defined with IP networks and X.25 networks. GPRS
allows SMS transfer over GPRS radio channels. Three GPRS MS modes of operation are
supported: An MS in class-A mode of operation operates GPRS and other GSM services
simultaneously. An MS in class-B mode of operation monitors control channels for
GPRS and other GSM services simultaneously, but can only operate one set of services at
one time. An MS in class-C mode of operation exclusively operates GPRS services.
The SGSN is connected to the base station system with Frame Relay. The Gateway GSN
(GGSN) provides interworking with external packet-switched networks, and is connected
with SGSNs via an IP-based GPRS backbone network. The HLR is enhanced with GPRS
subscriber information, and the SMS-GMSCs and SMS-IWMSCs are upgraded to
support SMS transmission via the SGSN. Optionally, the MSC/VLR can be enhanced for
more-efficient co-ordination of GPRS and non-GPRS services and functionality: e.g.,
paging for circuit-switched calls that can be performed more efficiently via the SGSN,
and combined GPRS and non-GPRS location updates. GPRS security functionality is
equivalent to the existing GSM security. The SGSN performs authentication and cipher
setting procedures based on the same algorithms, keys, and criteria as in existing GSM.
GPRS uses a ciphering algorithm optimized for packet data transmission. A GPRS ME
can access the GPRS services with SIMs that are not GPRS-aware, and with GPRS-aware
SIMs. An MS may perform the GPRS Cell selection autonomously, or the base station
system instructs the MS to select a certain cell. The MS informs the network when it re-
selects another cell or group of cells known as a routing area.

In order to access the GPRS services, an MS shall first make its presence known to the
network by performing a GPRS attach. This operation establishes a logical link between
the MS and the SGSN, and makes the MS available for SMS over GPRS, paging via
SGSN, and notification of incoming GPRS data. In order to send and receive GPRS data,
the MS shall activate the packet data address that it wants to use. This operation makes
the MS known in the corresponding GGSN, and interworking with external data
networks can commence.
User data is transferred transparently between the MS and the external data networks
with a method known as encapsulation and tunneling: data packets are equipped with
GPRS-specific protocol information and transferred between the MS and GGSN. This
transparent transfer method lessens the requirement for the GPRS PLMN to interpret
external data protocols, and it enables easy introduction of additional interworking
protocols in the future. User data can be compressed and protected with retransmission
protocols for efficiency and reliability.

Packet Switching
Unlike circuit switching, packet switching does not require dedicated channel. Instead,
the computer connected to a mobile station sends and receives bursts, or packets, of data
through the network along communication lines shared with the other channels. The data
is sent in the form of discrete packets, each with a header-containing source and
destination routing information and address. In this way, packets from many different
transmissions may be multiplexed over the same circuit. The path taken by successive
packet may not be same. However, the routing information contained in the header of
each packet ensures that the packet reach their destination where they are reassembled
into the correct sequence.

GPRS basics (Coding schemes, etc,)

Different Coding Scheme (CS) used for GPRS are
CS1 – Rate = 9.05 Kbps
CS2 – Rate = 13.4 Kbps
CS3 – Rate = 15.6 Kbps
CS1 – Rate = 21.4 Kbps (no encryption)

When GPRS starts sending data, its first burst occupies all the TS available and by
looking C/I parameters it decides the coding scheme to be given to data transmission and
accordingly releases the TS.
GPRS network architecture
The GPRS protocol stack
 GPRS Interfaces

E SMSC C

D
MSC / VLR HLR
Gs Gd Gr
A

Um Gb Gn Gi
MS BSS SGSN GGSN PDN
Gp
Gn BPL MOBILE
Gf
GPRS NETWORK

GGSN CGF
Signaling SGSN EIR Gb
Other PLMN
Signaling and Data
 GPRS Transmission Plane

WAP / HTTP

Application

IP
IP / X.25 IP / X.25

SNDCP NSAPI ( during PDP ) SNDCP GTP GTP

TID
(NSAPI/IMSI)

TLLI (IMSI / PTMSI)

LLC LLC TCP TCP
UDP UDP
RLC BPL RLC BSSGP BVCI BSSGP
MO IP IP
MAC BIL MAC Network NSVCI Network Layer 2 Layer 2
Service DLCI Service
E
GSM RF GSM RF L1 bis L1 bis Layer 1 Layer 1
GPR
S
MS NET BSS SGSN GGSN
WO
Um Gb Gn Gi
RK
GPRS functioning - Attach, PDP context activation,
Concept of APN
All traffic from an MS, whether voice or data, is transported over the air interface to the
BTS, and from BTS to the BSC, in the same manner as a standard GSM message. The
GSM BTS and BSC both require a soft upgrade to handle GPRS.

GPRS packet data traffic is separated from GSM voice and circuits-witched data at the
BSC. GSN traffic is sent to the MSC as usual, while GPRS traffic is sent to the PCU, a
new component that adds GPRS functionality to the BSS.

The PCU segment Logical Link Control (LLC) frames into Radio link Control (RLC)
packets for transmission to the MS by the BSC, and reverses the process for RLC packets
received from the BSC for transmission to the SGSN. The PCU also manages time-slot
allocation and packet scheduling.
The SNSG delivers packet to and from MS in it’s service area, and tracks the location of
the MS. As an MS moves from one SGSN coverage area to another, the GSNS
communicates with each other and update the user location.

The GGSNs are connected to the SGSN via the GPRS backbone. The GGSN acts as
logical interface between MSs and the Internet and other outside GPRS networks. It
maintains routing information used to tunnel PDUs to the serving SGSN, allowing the
MS to move freely within the coverage area. The GGSN also collects charging
information and forwards it to a billing system.

Mobile Terminal & Modes of Operations, Cell

reselection
A GPRS MS can operate in one of three modes of operation. The mode of operation
depends on the services that the
MS is attached to, i.e., only GPRS or both GPRS and other GSM services, and upon the
MS's capabilities to operate GPRS and other GSM services simultaneously.

• Class-A mode of operation: The MS is attached to both GPRS and other GSM
services, and the MS supports simultaneous operation of GPRS and other GSM
services.
• Class-B mode of operation: The MS is attached to both GPRS and other GSM
services, but the MS can only operate one set of services at a time.
• Class-C mode of operation: The MS is exclusively attached to GPRS services.
An MS (in any mode of operation (A, B, or C)) cannot camp on more than one cell. This
means that the cell selection and reselection procedure should choose cells that support
services the user has subscribed to.
If the MS is in idle mode, then it shall behave as described below:

When the MS is in GPRS IDLE state and wishes to initiate the GPRS Attach procedure,
the following applies:

 If the currently camped-on cell supports GPRS then no cell reselection is

required.
 If the currently camped-on cell does not support GPRS, then reselection of
a cell supporting GPRS is required before execution of the attach
procedure.

If the MS is in GPRS STANDBY or READY state, cell selection and reselection

procedures specific to GPRS shall be used,
The cell reselection procedure used in READY state shall minimize the cell changes.

If the MS is in dedicated mode, then the changes from one cell to another is performed
according to the
Network-controlled handover procedures. There may be co-ordination of the idle and
dedicated mode procedures used for circuit-switched services with the READY state
procedure for MSs that are both IMSI-attached and GPRS-attached.

GPRS Mobile Time-Slots Capabilities

Class 1 UL 1 Tch DL 1 Tch Motorola Accompli A008 Trium

Mondo, Sirius.

Class 2 UL 1 Tch DL 2 Tch Motorola Accompli A008 Trium

Mondo, Sirius.

Class 3 UL 2 Tch DL 2 Tch

Class 4 UL 1 Tch DL 3 Tch Motorola TimeportT260.

Class 6 UL 2 Tch DL 3 Tch (Conf) Nokia 6310, 6510, 8310,ND-211.

Class 8 UL 1 Tch DL 4 Tch Siemens S45, ME45, M50 Trium

Eclipse.

Class 10 UL 1 Tch DL 4 Tch (Conf) Philips Fisio 820

Class 12 UL 1 Tch DL 4 Tch (Conf) Sierra Wireless Aircard 750

GSM/GPRS PC Card
Class 29 UL 8 Tch DL 8 Tch
 GRPS core
Packet Unit Control (PCU)
The Packet control unit (PCU) uses Compact PCI_ based hardware to implement the new
BSS functionality that integrates the Gb interface with existing Motorola GSM
equipment. The PCU is a component of the Base Station Subsystem (BSS), which
connects the Serving GPRS Support Node (SGSN) to the Base station controller (BSC)
using the Gb interface. The PCU is collocated with the BSC.

The PCU also provides the General Packet Radio System (GPRS) radio channel control
functions, such as timeslot allocation, media access control (MAC), error detection for
the air interface, radio link control automatic request for retransmission (RLC ARQ),
power control, timing advance and system information message generation, using radio
link control (RLC)/media access control (MAC) protocols. A PCU is capable of a
maximum configuration of 1080 air timeslots. A maximum of 270 air timeslots can be
active at one time, with 810 on standby.

The main components of the PCU are:

• A CompactPCI chassis.
• An alarm module.
• A power distribution module.
• Three fan/power supply sleds (one for redundancy).
• One MPROC/HSC pair.
• Up to twelve DPROCs and their associated transition modules, (quantity
dependant on customer requirements).

The following digital modules are available:

MPROC:
The master processor (MPROC) is the system slot processor, which is responsible for bus
arbitration and CPCI clock generation. It hosts interface and BSSGP protocol functions,
and is called the PCU System Processor (PSP). Only one PCU System Processor (PSP)
may be equipped at each PCU.

DPROC:
The data processor (DPROC) boards are non-system slot processor boards (or I/O
boards), which have two PMC sockets. The DPROC can be configured as either a Packet
Interface Control Processor (PICP) or as a Packet Resource Processor (PRP).
NIB:
The network interface board (NIB) is a PCI mezzanine card (PMC). The NIB has the
functionality of an MSI card and performs all of the physical layer termination of the E1
links between the PCU, the BSC and the SGSN.

Hot swap controller (HSC) bridge:

The HSC bridge also known as the PCI to PCI Bridge (PPB) allows an MPROC to link
two separate PCI bus domains. The HSC Bridge and MPROC are paired boards.
E1 transition modules:
Transition modules are used in the rear non-system slots to allow the PMC E1 interfaces to be
connected at the rear of the PCU.

GSN Complex

GSN Complex Overview

The GPRS Support Node (GSN) Complex provides a router for the GPRS infrastructure.
The GSN Complex consists of Serving GPRS Support Node (SGSN) and Gateway GPRS
Support Node (GGSN) components connected to a single LAN switch known as the
communications Hub (CommHub). These components, together with Integrated Support
Services (ISS) cluster nodes and high availability disk storage arrays, are housed in two
or more GSN Complex cabinets.
A basic GSN Complex consists of a communications cabinet and an expansion cabinet.
Up to two further expansion cabinets can be added to increase capacity.
GSN hardware Architecture

GSN Complex Components

The following components make up the GSN Complex:
 CommHub.
 ISS.
 Terminal Concentrator.
 SGSN Unit.
 GGSN.
SGSN
The SGSN Unit comprises a Motorola Compact PCI CPX8216 system with Compact PCI
bus; containing the following SGSN related hardware:

SGSN. This is a three-card set that includes a Control Function (CF) card, TF0 (Gb) card,
and TF1 (Gn) card. The SGSN detects and tracks new GPRS MSs in its service area and
provides a reliable, secure data channel as the MS moves between cells.
Signaling Function (SF). This is a single card that provides SS7 signaling protocols for
signaling exchange between SGSN and GSM network entities.
Shelf Manager. This is a two-card set containing a system slot processor (SSP) module
and a hot swap controller (HSC) bridge module. The Shelf Manager performs the bus
control functions, enabling communication between non-system slot cards over the PCI
bus; relays shelf alarms to the OMC-G, and performs software load management. Each
SGSN Unit contains two Shelf Managers (four cards in total).

GGSN
The GGSN is a Cisco 7206 router that provides GPRS network access to external hosts,
so they can communicate with MSs. It also decapsulates and forwards external data
network packets to the appropriate data network and handles the billing of traffic data.
The GGSN contains routing information for attached GPRS users. This routing
information is used to tunnel packets uplink and downlink. Uplink provides GPRS
network access to external hosts that wish to communicate with the mobile subscribers.
Downlink directs mobile terminated packets to the SGSN currently serving the MS,
allowing the mobile subscribers to move freely within the coverage area of its home
network, or a foreign network.
The GGSN also collects charging information from the GPRS network and transfers the
information to a network operator billing system, by way of a centralized CGF located in
the ISS cluster (Integrated Support Server).

DHCP and AAA RADIUS

Dynamic Host Configuration Protocol – This is a protocol that lets network
administrators centrally manage and automate the assignment of IP Addresses on the
corporate network. When a company sets up its computer users with a connection to the
Internet, an IP address must be assigned to each machine. Without DHCP, the IP address
must be entered manually at each computer. DHCP lets a network administrator
supervise and distribute IP addresses from a central point and automatically sends a new
IP address when a computer is plugged into a different place in the network. DHCP uses
the concept of a ‘lease’ or amount of time that a given IP address will be valid for a
computer. Using very short leases, DHCP can dynamically reconfigure networks in
which there are more computers than there are available IP addresses.

Authentication, Authorization and Accounting – The RADIUS server acts as a

security gateway to the PLMN and authenticates and authorizes all remote access. The
RADIUS server is accessed during PDP context activation. The GGSN functions as a
client of the PLMN RADIUS server. The GGSN is responsible for passing user
information to a designated RADIUS server and acting on any response. User
authentication is performed by a series of communications exchanges between the GGSN
and the RADIUS server. Once a user is authenticated, the GGSN provides user access to
a specific network resource, (for example, the Internet). When a user initiates a PLMN
ISP access (indicated by the APN), the GGSN behaves as a RADIUS authentication
client.

ISS (Charging gateway, DNS)

The ISS is a Sun Cluster comprising two Cluster Nodes (Sun Netra t 1125s) and two HA
Disk Arrays (Sun Netra st D1000s). The ISS provides GPRS system components with
reliable disk storage, a charging gateway, current time, domain name translation, and
network information.
ISS Cluster provides the following network functions: -
 Domain Name Service (DNS), which maps logical names, to network layer
Internet Protocol (IP) Address.
 Network File Server (NFS) which provides long-term storage for network
configuration information, charging data information and network statistics.
 Charging Gateway Function (CFG), which collects and store subscriber
accounting data for collection by a Billing system (BS).

CommHub
The CommHub is the backbone of the GSN Complex. The CommHub is a Cisco 5500
switch that comprises switch router and Ethernet switch modules providing a central
connection point for the components in a GPRS system. The CommHub provides LAN
connectivity between GPRS components through Ethernet, and WAN connectivity to
data networks outside a GPRS system.
APN configuration
When an MS is attached to a GPRS network, it can choose to use the default APN or to
select a different pre-configured APN from a list sent to it by the HLR. The user-
selectable APN feature gives an MS the ability to select from this list.

An APN is an identifier for a PDN that is configured on, and accessible from, a GGSN. It
is used to specify the PDN to which an MS wishes to connect. The APN can be a label or
a fully qualified domain name according to DNS naming conventions as specified in
GSM.

OMC-G
The OMC-G allows the operator to perform operation and maintenance of the GPRS
system by performing analysis of the events, alarms and statistics within the GPRS
system. The OMC-G complements existing OMC systems within a GSM network under
the control of a common Network Management Center (NMC). The OMC-G works in
conjunction with the GSN Complex, which handles all the GPRS communications.

OMC-G GPRS management functions

The following management facilities are provided at the OMC-G workstation screens for
the user to maintain and operate the GPRS system.
Configuration management
Configuration Management allows the operator to configure the Network Elements. It
allows the operator to perform the following tasks:
• View SGSN, Shelf Manager, and Cisco GGSN configuration.
• Modify SGSN and Shelf Manager configuration.
• Perform a sanity check of an SGSN database.
• Change SGSN and Cisco GGSN configuration via updated database files.
• View and change load sharing and redundancy configuration on Gb link.
• Compare SGSN data related to Gb link with the corresponding PCU data
(retrieved from OMC-R).
• Provide telnet access to SGSN, Shelf Manager, Cisco GGSN, CommHub, and
ISS.
• Provide tftp access to SGSN, Shelf Manager, Cisco GGSN, CommHub, and ISS.
GPRS provisioning on HLR

• IMSI
• GPRS enabled / disabled
• PDP Records
• APN
 IP Version (IPv4 or IPv6)
 IP address (If static address is allocated)
 QoS profile name
 Roaming (HPLMN / VPLMN)

Integration with Billing for packetized billing

Gr
HLR Siemens
OMC
GPRS
SGSN Provisioning

CMISE
Charging
GPRS Backbone GTP’
Gateway
(ISS)
G-CDRs
S-CDRs
M-CDRs
FTP
Billing System
S-SMO-CDRs
GGSN S-SMT-CDRs
Billing
Files v6.0

Internet
GPRS Billing
• Service Access Point (Internet, Corporate Intranets, Mail service, Gaming zone,
etc.)
• Uplink data volume (MB of data transferred)
• Downlink data volume (MB of data transferred)
• QoS offered to the subscriber (Coding scheme, peak throughput, priority, etc. )
• Time of usage (e.g. 10pm to 8am)
• Content based billing (Via third-party software)
• Monthly subscription based

References
GSM02.60 GPRS; Service description; Stage 1
GSM03.60 GPRS; Service description
GSM07.60 GPRS; Mobile Station (MS) supporting GPRS
GSM12.15 GPRS; GPRS Charging
GSM08.08 MSC – BSS interface: Layer 3 specification
WAP
Introduction: -
The Wireless Application Protocol (WAP) is a set of open, global protocols for
developing applications and services that use wireless networks. The WAP protocols are
mainly based on already existing Internet protocols, but are optimized for mobile users
with wireless devices.
WML is the WAP equivalent to HTML (HyperText Markup Language), which is a
markup language used to construct web pages. WML stands for Wireless Markup
Language. Pages written in WML can be read by a WAP phone or similar device. Since
WML is actually an application of XML (eXtensible Markup Language), the syntax
reminds of XML, with its strictness. If you have some experience with HTML, it is not
difficult to learn WML; many tags and attributes are almost the same, but there are fewer
tags. Unlike HTML, you can play around with variables in WML, making it more
dynamic. It is also possible to have many sub-pages (called 'cards') in one WML page
(called a 'deck'). Each WML card works like a web page and it's content is displayed to
the user.

The WAP Forum released its first specification – WAP 1.0 – in 1998. In subsequent
WAP specification releases, the WAP Forum addressed interoperability, established a
certification program, and added various features in response to changes in market
requirements and improvements in networks, devices and new technologies.

WAP 2.0 is a next-generation set of specifications that, like previous releases, marks the
WAP Forum's ongoing efforts to adopt the most recent Internet standards and protocols.
WAP 2.0 also optimizes usage of higher bandwidths and packet-based connections of
wireless networks worldwide. While utilizing and supporting enhancements in the
capabilities of the latest wireless devices and Internet content technologies, WAP 2.0 also
provides managed backwards compatibility to existing WAP content, applications and
services that comply to previous WAP versions.

The following items represent the major architectural components of WAP 2.0:
Protocol Stack Support – In addition to the WAP Stack introduced in WAP 1, WAP 2.0
adds support and services on a stack based on the common Internet stack including
support for TCP, TLS and HTTP. By encompassing both stacks, WAP 2.0 provides a
connectivity model on a broader range of networks and wireless bearers.
WAP Application Environment – Nominally viewed as the 'WAP Browser', the WAP
2.0 Application Environment has evolved to embrace developing standards for Internet
browser markup language. This has led to the definition of the XHTML Mobile Profile
(XHTMLMP). XHTMLMP is based on the modularity framework of the eXtensible
HyperText Markup Language (XHTML) developed by the W3C to replace and enhance
the currently used HTML language common today. The use of Internet technologies is
not new for WML, as WML1 is a fully conformant XML language in its own right.
Additional Services and Capabilities – The WAP specifications have had items that
were neither part of the 'WAP Stack' nor the 'WAP Browser' but helped to enrich the
 environment defined in the WAP specifications. With WAP 2.0, there is a considerable
increase in the number of features available to developers, operators and users.

WAP Network

Web Server
http://wap.yahoo.com
WAP
Enabled
Mobiles

Encoder &
Script Compiler Internet
WSP HTTP /
WTP WAP HTTPS
Gateway Web Server

PDA
WAP browser
Carriers
CSD
SMS Web Server
http://wap.mizone.bplmobile.com
GPRS
Laptops with
WAP browser
MMS
Introduction: -
The Multimedia Messaging Service (MMS), as its name implies, is intended to provide a
rich set of content to subscribers in a messaging context. It supports both sending and
receiving of such messages by properly enabled client devices.
The Multimedia messaging service is viewed as a non-real-time delivery system. This is
comparable to many messaging systems in use today. Prime examples include traditional
email available on the Internet and wireless messaging systems such as paging or SMS.
These services provide a store-and-forward usage paradigm and it is expected that the
MMS will be able to interoperate with such systems. Real-time messaging also exists in
various forms. For example, instant messaging available from various vendors or various
chat services (e.g. text, voice) are becoming popular. Such services are not currently
supported with the MMS system but may be considered for future releases.

Elements of MMSC Environment: -

MMS Client – This is the system element that interacts with the user. It is expected to be
implemented as an application on the user’s wireless device.
MMS Proxy-Relay – This is the system element that the MMS Client interacts with. It
provides access to the components that provide message storage services, and it is
responsible for messaging activities with other available messaging systems. Some
implementations may combine this component with the MMS Server.
MMS Server – This system element provides storage services for MM messages. Some
implementations may combine this component with the MMS Proxy -Relay.
Email Server – This system element provides traditional Internet email services. It
supports the SMTP protocol to send messages as well as POP and/or IMAP protocols to
retrieve messages.

WAP Gateway Server –

SMSC CMD-II Login –
Real-time charging for prepaid subscribers

Flow Diagram.

Whenever a subscriber sends a Service request to the Content Provider/Application

Server it will call the authenticate function using the HTTP interface. Apart from
MSISDN and amount required for the transaction, application has to pass the user id and
password given to it.
After receiving the authenticate request, IMS will check that the request has come from a
valid client. Once the client validation is done it will proceed with the authentication of
the MSISDN.
After the MSISDN is identified as pre-paid, communicate with SCP to authenticate the
validity of the MSISDN. Then block the required amount on the SCP. Respond back to
the Application / Content server with the Authenticate success. IMS will assign a unique
transaction id to every successful authenticate request response.
Once application gets a successful authentication response it will go ahead with the
transaction. Once the transaction is successful the application will call the accounting
request mentioning the transaction id, onto the IMS.
When the IMS gets accounting request for a transaction it will generate the CDR and
release the particular transaction id. The transaction has to expire within a definite time
period. After the authentication request if the system does not receive accounting request
within the defined time period, the System will release the active resources used for that
particular transaction. If the application does not get a successful response, it needs to
retry, the frequency of which will be configurable. In the event that the response fails for
good, the transaction ids need to be given to IMS for reconciliation in a ASCII file with
format as follow.

GPRS Roaming concept

The GPRS system Network is responsible for the communication of a large amount of
data, and at a respectable high speed. The signaling and other related infrastructures are
designed to be relatively fault tolerant.

Another important aspect of GPRS signaling is the concept of Roaming. Service

providers must make sure that the machine when out of the home network, must not
suffer with no communication possibility.

GPRS Roaming, as much similar to the existing GSM Roaming patterns, requires signal
protocols to be recognized by the various participating service providers in the network.
Thus this requires an efficient communication channel and a well established inter
network among all the service stations striving together for roaming. This makes it
possible to design a generic design map, somewhat resembling the K (x,y) meshed
architecture.
GRx architecture
Roaming eXchange (GRX) provides a secure platform for the global exchange of General
Packet Radio Service (GPRS) traffic. This service allow users to connect their mobile
phones to a wide range of public and private data networks using TCP/IP and X.25.With
the anticipated growth of the wireless Internet around the globe.

International data and IP network, combined with Global Data Centres can provide a
global coverage and quality of service. Services include International Voice, VoIP,
International Toll Free, Global Internet Access, and VPN services using native IP, ATM,
Frame Relay and MPLS.

Through our GRX peering arrangements, global connectivity by GPRS roaming partners
via a single connection shall save much time and money involved in setting up
connections. Built-in flexibility and a choice of port sizes, shall make it easy to select a
solution that suits the needs of the user. The GRX solution will be competitively priced,
secure and scalable, providing users with an excellent opportunity to increase the GPRS
traffic.

GRx Roaming Documents

• IR 21
• IR 35
 Integration BPL Network with GRx.
BPL MOBILE GPRS NETWORK

Internet
WAP MMSC SMSC

203.124.225.173 GPRS
Complex
203.124.225.174
203.196.249.161 10.254.1.14

Public LAN Lease Line Router

Firewall

10.254.1.10
BPL 10.254.1.25
RSM
MOBILE
GPRS Vlan 100
GPRS LAN NETWORK 10.254.1.26
Border Gateway router
10.254.1.9 203.196.203.202

For existing Bplgprs.com subscribers

 GPRS extended to circles using common core

Kerala Pune (Maharashtra)

PCU1 PCU3 PCU1 PCU5

Gb Gb Gb Gb

Gr
HLR MUX HLR MUX
Gr 1-E1 1-E1
Two Tchs / PCU Two Tchs / PCU
Gr Gr

MUX
Gb Gr
CG Gr

SGSN F SGSN Pune

Kerala CF SF
SF TF GbCF SF
SF TF
SGSN 1
Internet
PCU1Gb Gn Gn
MUX

CF TF
Gn
SF
GGSN
Gi NAT
Gn
PCU17 Router
CF TF
Mumbai
Common
SGSN 2 Gr OMC-G / DHCP / DNS

HLR