1 Normal Prepaid (IN) Call Flow

2 GPRS Call Flow

3 Mobile Terminated (MT) SMS Flow
4 Mobile Originated (MO) SMS Flow
5 GSM Mobile Terminated Call
6 GSM Originating Call Flow
(GSM) Mobile to Mobile Call Flow, Within Same
7 MSC/BSC

8 BASIC ISUP CALL FLOW

9 MNP Call Flow Normal Mobile to Mobile Call
1
0 Location Update Procedure
1
1 STP (Signaling Transfer Point)
1
2 KPI - Key Performance Indicators
Normal Prepaid (IN) Call Flow

Hi All,

As Prepaid Call Flow with MNP is already posted, but still many of our friends ask us for
detailed Normal Prepaid (IN) Call scenario, so here you go,

The above flow describes a basic direct dial call scenario with normal call termination:

1. Mobile A starts a new call by dialing Mobile B.

2. The MSC sends an IDP (Initial Detection Point) event, which notifies the IN-SCP of
the new call.
IDP Message Contains :- A-Party no, B-Party no., Service key=90, A Party Location, Time
stamp.
3. The IN SCP processes the request and after authorizing the user, the IN SCP sends
3 IN messages to the MSC -
  AC (Apply Charging) :- Check the A-Party Balance / tariff related facilities &
provides maximum granted time for a call.
 CIQ (Call Information Query) :- IN request from the MSC for call information, like
CAET - Call Attempt Elapsed Time (time between call ringing & user picks the
call), CCET - Call Connect Elapsed Time (Duration of a call), CST - Call Stop
Time (exact time when call disconnect), RC - Release Cause (Exact release
cause due to which call got disconnected).
 RRBCSM (Request Report Basic Call State Module) :- IN again request from
MSC for detailed Release Cause.

4. Connect :- After getting everything OK i.e. all request from IN side have been done
then IN sends a Connect message to MSC for further call processing & connect the call.

5. Activity Test :- After IN provides "connect" message to MSC, its a sort of ping
message which is unidirectional, sent by IN to MSC, to know the progress of a call.

6. Once the connection is made, an event report (for answer event) is sent to SDP via
IN-SCP.for preventing any revenue loss.

7. After conversation, when call gets disconnected, a new event report is sent to SDP
via IN-SCP, which in turn instructs to release the call.

8. Once the call is released, a new Apply Charging Report (ACR) is sent to IN-SCP,
which contains full time usage data of a call. This report is sent to SDP for accurate &
final call charging.

9. CIR (Call Information Report) :- By using the details which was noted in CIQ
message, MSC makes a report i.e. CIR (which contains CAET, CCET, CST, RC) &
sends to SDP via IN-SCP.

10. ERB (Evert Report BCSM) :- Another report send by MSC to IN, which contains
actual release cause in details, which may be - Abandon, B-Party Busy, B-Party no
answer, B-Party not reachable, route selection failure, disconnect.

11. Finally signaling terminates, which ends the call.

GPRS Call Flow

GPRS (General Packet Radio Service) is a packet based communication service for
mobile devices that allows data to be sent and received across a mobile telephone network. It's a
step towards 3G and is often referred to as 2.5G.
It’s an upgrade to the existing network that sits along side the GSM network. Many of the
devices such as the BTS and BSC are still used. Often devices need to be upgraded be it
software, hardware or both. When deploying GPRS many of the software changes can be made
remotely.
There are however 2 New Functional Elements which play a major role in how GPRS
works - SGSN & GGSN. In simple terms there are in practice two different networks working in
parallel, GSM and GPRS.
In any GSM network there will be several BSC’s. When implementing GPRS a software
and hardware upgrade of this unit is required. The hardware upgrade consists of adding a PCU
(Packet Control Unit). This extra piece of hardware differentiates data destined for the standard
GSM network or Circuit Switched Data and data destined for the GPRS network or Packet
Switched Data.
PCU can be a separate entity.

SGSN (Serving GPRS Support Node) - It takes care of some important tasks, including
Routing, Handover and IP address assignment. Its a logical connection to the GPRS device.
One job of the SGSN is to make sure the connection is not interrupted as you make your journey
passing from cell to cell. It works out which BSC to “route” your connection through. If the user
moves into a segment of the network that is managed by a different SGSN it will perform a
handoff to the new SGSN, this is done extremely quickly and generally the user will not notice
this has happened. Any packets that are lost during this process are retransmitted. The SGSN
converts mobile data into IP and is connected to the GGSN via a tunneling protocol.

GGSN (Gateway GPRS support node) - It is the “last port of call” in the GPRS network before
a connection between an ISP (Internet Service Provider) or corporate network’s router occurs.
The GGSN is basically a gateway, router and firewall. It also confirms user details with
RADIUS servers for security, which are usually situated in the IP network and outside of the
GPRS network.
The connection between the two GPRS Support Nodes is made with a protocol called
GPRS Tunneling Protocol (GTP). GTP sits on top of TCP/IP and is also responsible for the
collection of mediation and billing information. GPRS is billed on per megabyte basis.
GPRS Call Scenario :-
 A subscriber accesses the Internet with GPRS mobile phone to set the APN (Access Point
Names) & gateway IP address defined on subscription. In fact, APN is a logical name
indicating the external data network in GGSN. A subscriber can select different GGSNs
via different APNs. Currently, however, only one APN can be activated at a time. The
purpose of selecting different APNs is to access the external network via different
GGSNs, because without GGSN, a subscriber cannot access the PDN (Public Data
Network). An APN consists of a fully qualified DNS (Domain Name Server) name e.g.
airtellive.com.cn., which should be parsed by DNS to get the real IP address of GGSN.
 The call reaches the SGSN of the GPRS network. The SGSN triggers the service in the
corresponding SCP (Service Control Point) according to subscriber's authentication
information on the HLR interconnected to the corresponding home SCP for processing.
 The DNS parses the APN and get the IP address of the GGSN.
 The call is routed to the GGSN according to the IP address.
 The GGSN assigns the IP address to the subscriber.
 After SCP verifies the subscriber, the subscriber begins to transmit data and log in to the
external web sites via the gateway whose IP address is set in the mobile phone.
 The subscriber may select the service from the portal web site to connect the SP/CP web
site that provides the service, or enter the IP address of the SP/CP in the mobile phone to
access the SP/CP web site.
Mobile Terminated (MT) SMS Flow

Here is a Simple Explanation of Mobile Terminated (MT) SMS Flow -

SMS MT Call Flow :-

1. The Short Message is transferred from SMSC to SMS-GMSC.

2. SMS-GMSC queries the HLR (SRI) & receives the routing information for the mobile
subscriber (SRI-ACK).
3. The SMS-GMSC sends the short message to the MSC using "Forward Short Message"
(FSM) operation.
4. The MSC retrieves the subscriber information from the VLR. This operation may include
the Authentication Procedure.
5. The MSC transfers short message to the Mobile Station (MS).
6. The MSC returns the outcome of the "Forward Short Message" operation to the SMS-
GMSC (FSM-ACK).
7. If requested by the SMSC, it returns a status report indicating Delivery of the Short
Message.
Mobile Originated (MO) SMS Flow

Here is a simple explanation of Mobile Originated SMS flow.

SMS MO Call Flow :-

1. The mobile station transfers the short message to the MSC.

2. The MSC queries the VLR to verify that the message transfer does not violate the
supplementary services invoked or the restrictions imposed on the subscriber.
3. The MSC sends the short message to the SMS-IWMSC (Inter-Working MSC for SMS) using the
“forward Short Message” operation.
4. The SMS-IWMSC delivers the short message to the SMSC (Short Message Service Centre).
5. The SMSC acknowledges the successful outcome of the “forward Short Message” operation to
the MSC.
6. The MSC returns the outcome of the short message operation to the mobile station.
GSM Mobile Terminated Call

A Land Line Subsriber calling a Mobile Subscriber.

The main difference between a call to an MS and a call from an MS is that, the exact location of
MS is unknown. Hence, the MS must be located using paging before a connection can be
established.

1. The PSTN subscriber dials the MS’s telephone number (MSISDN), the MSISDN is
analyzed in the PSTN, which identifies that this is a call to a mobile network subscriber.
A connection is established to the MS’s home GMSC. The PSTN sends an Initial
Address message (IAM) to the GMSC.
2. The GMSC analyzes the MSISDN to find out which HLR, the MS is registered in, and
queries the HLR for information about how to route the call to the serving MSC/VLR.
The HLR looks up the MSISDN and determines the IMSI and the SS7 address for the
MSC/VLR that is servicing the MS. The HLR also checks if the service, “call forwarding
to C-number” is activated, if so, the call is rerouted by the GMSC to that number.
3. The HLR then contacts the servicing MSC/VLR and asks it to assign a MSRN to the call.
[MSRN - Mobile Station Routing Number].
4. The MSC/VLR returns an MSRN via HLR to the GMSC.
5. The GMSC sends an Initial Addressing message (IAM) to the servicing MSC/VLR and
uses the MSRN to route the call to the MSC/VLR. Once the servicing MSC/VLR
receives the call, the MSRN can be released and may be made available for reassignment.
6. The MSC/VLR then orders all of its BSCs and BTSs to page the MS. Since the
MSC/VLR does not know exactly which BSC and BTS the MS is monitoring, the page
will be sent out across the entire Location Area(LA).
7. When the MS detects the paging message to the BTS’s in the desired LA. The BTS’s
transmit the message over the air interface using PCH. To page the MS, the network uses
an IMSI or TMSI valid only in the current MSC/VLR service area.
8. When the MS detects the paging message, it sends a request on RACH for a SDCCH.
9. The BSC provides a SDCCH, using AGCH.
10. SDCCH is used for the call set-up procedures. Over SDCCH all signaling preceding a
call takes place. This includes: Marking the MS as “active” in the VLR. Authentication
procedure (Start ciphering, Equipment identification).
11. The MSC/VLR instructs the BSC/TRC to allocate an idle TCH. The BTS and MS are
told to tune to the TCH. The mobile phone rings. If the subscriber answers, the
connection is established.
GSM Originating Call Flow

A Mobile User calling a Land Line Subscriber.

1. MS after dialing a number & pressing SEND key, sends Channel Request(Chan_Req)
message on RACH to ask for a signaling channel (Radio Resources). [RACH - Random
Access Channel]
2. The BSC allocates a Traffic Channel(TCH) using AGCH. TCH allocation assigns a
specific Frequency & a Timeslot on that frequency. [AGCH - Access Grant Channel]
3. The MS sends a call setup request through SDCCH, to the MSC/VLR. [SDCCH - slow
dedicated control channel]. Over SDCCH, all signaling takes place. This includes:
marking the MS status as active in the VLR
4. Then comes Authentication Procedure which includes Ciphering (The channel is ciphered
so as to protect the call), Equipment Identification, etc.
5. The MSC/VLR instructs the BSC to allocate an Idle TCH (this message contains the
dialed digits and other information needed for call establishment). The BTS and MS are
told to tune to the TCH.
6. The MSC allocates a voice circuit on one the digital trunks between the MSC and the
BSS.
7. MSC informs the BSS about the allocated voice circuit. The call is also switched from
signaling to voice.
8. The BSS notifies the Mobile about the changeover to voice mode.
9. The MSC routes the call and sends the call towards the called subscriber.
10. The PSTN indicates to the MSC that it has received all the digits and the called
subscriber is being rung.
11. The MSC informs the mobile that the called subscriber is being alerted via a ring.
12. The called subscriber answers the call.
(GSM) Mobile to Mobile Call Flow, Within Same MSC/BSC

Hi Friends,

Here I tried to explain very basic call flow from mobile to mobile.

To make it simple following assumptions have been taken. A) Call is in same MSC and BSC. B)
No Authentication, C)No Ciphering , D) Messages on Ater and Air interface are not consider,
etc.

Call Flow Mesage Details:-

1. CM(Class Mark) Service Request – Message contains Global Cell Identity, Kind of
Service required by subscriber e.g Voice, SMS, Fax, USSD. Mobile Identity e.g
TMSI/IMSI.
2. CM Service Accept – Message is in reponse of CM Service Request.
3. Set Up - Message contains dailed number from Mobile A (i.e Mob B number) and speech
Codec.
4. Send Routing Info-Request (SRI) - After analysis of dialed numbers received from A in
set up message, MSC recognises its own MSISDN series and send SRI to HLR to get the
Mobile station roaming number(MSRN). This messge contains B MSISDN, Interrogation
type e.g Basic Call etc.
5. Assignment Request - Message is to seize a channel for voice call for Mob A between
MSC and BSC. Message contains Circuit Identification Code(CIC).
6. Assignment Complete - Acceptance from BSC end that same CIC has been seized.
7. Provide Roaming Number Request - HLR checks in its database to which VLR, Mob B
is registered & ask for roaming number from that VLR. Message contains IMSI,
MSISDN, VLR ID of Mob B.
8. Provide Roaming Number Response - Message is response of roaming no. request and
contains roaming number of Mob B. This message is for HLR. In this VLR checks its
database & allocate one free MSRN from its MSRN pool for B number.
9. Send Routing Info-Response - In this HLR forward same roaming number which it
receives in above message to MSC.
10. Paging Request - In this VLR checks the MSRN recieved from HLR & search which
MSISDN is against that MSRN, now MSC checks the VLR database of that MSISDN to
get the LAC & TMSI/IMSI of that MSISDN (Mob B) & initiates the paging request
message to that particular LAC on the basis of TMSI/IMSI in that BSC. BSC now page
to that LAC on the basis of IMSI/TMSI of Mob B. Message contains LAC, IMSI/TMSI,
DPC of BSC.
11. Paging Response - Mob B response to that paging with GCI (Global Cell Identity) to
BSC that inturn forwarded to MSC.
12. Assignment Request - Message is to seize a channel for voice call for Mob B between
MSC and BSC. Message contains Circuit Identification Code(CIC).
13. Assignment Complete - Acceptance from BSC end that same CIC has been seized.
14. Set Up - It is used to display Mob A number on Mob B handset.
15. Alert - This message indicates Mob A that Mob B is connected & its ringing. The Ring
Back Tone is send from MSC to Mob A.
16. Connect - Mob B answers the call & connect message from Mob B is send to MSC,
inturn MSC sends connect message to Mob A indiacting that phone has been answered &
connects those 2 voice channels which were seized during the assignment complete
message.
17. Connect Acknowledge - To acknowledge the connection.
BASIC ISUP CALL FLOW

Initial Address Message (IAM) — First message sent to inform the partner switch (here
MSC2) that a call has to be established on the CIC contained in the message. Contains
the called and calling number, type of service (speech or data) and many more optional
parameters.

Subsequent Address Message (SAM) — In case the IAM did not contain the full called
number, one or more SAMs may follow containing additional digits.

Address Complete Message (ACM) — Message returned from the terminating switch
(here MSC2) when the subscriber is reached and the phone starts ringing.

Answer Message (ANM) — Sent when the subscriber picks up the phone. Normally
charging starts at this moment.

Release (REL) — Sent to clear the call when a subscriber goes on hook.

Release complete (RLC) — Acknowledgement of the release – the timeslot is idle

afterwards and can be used again. This is also sent (without a preceding Release
message) if the terminating switch determines that the call cannot be completed. The
terminating switch also sends a Cause Value to explain the reason for the failure, e.g.,
"User busy".
MNP Call Flow Normal Mobile to Mobile Call

Hi All,
Writing this to throw some light on call flows when MNP(Mobile Number Portability) will be
implemented in India.
There is one very interesting a full form of MNP floating in industry "Mujhe Nahi Pata", hope
after reading this we will be able to say goodbye to that :)
Before coming to the point i would like to elaborate some terms which will used later in
explaination.

1) MNPDB--> Mobile Number Portability Database, where in all details of subscriber is stored.
2) Ported In/Out--> Ported In/Out subscriber are those which have changed there Service
provider
Exp: A was originally Airtel Subscriber and availed MNP and changed to
Vodafone so A will be Ported in number for Vodafone and Ported out Number for Airtel.
These terms are enough to get a feel of normal mobile to mobile in MNP.

Here i have taken example to Vodafone Delhi where Subscriber A in MSC1 and Subscriber B in
Coverage of MSC2.
Let us now go through signaling flow in steps:
1) Subscriber A dials Subscriber B
2) MSC1 receives B number and SRI is sent to MNP server instead of HLR as in case of
traditional call flow.
3) MNP checks its database and founds that this is own subscriber and relays that SRI to HLR.
4) HLR on receiving SRI check the VLR address of subscriber and send PRN to MSC2.
5) In response to PRN MSC2 returns with MSRN.
6) HLR forward that MSRN number to MSC1 in SRI Response Message
7) MSRN is now dialled out from MSC1 to MSC2 to establish the voice path between two MSCs
After this call flow remains same as in case of traditional call flow which is already posted in this
blog.
Location Update Procedure
In order to make a mobile terminated call, The GSM network should know the
location of the MS (Mobile Station), despite of its movement. For this purpose the MS
periodically reports its location to the network using the Location Update procedure.

Location Area (LA)

A GSM network is divided into cells. A group of cells is considered a location area. A
mobile phone in motion keeps the network informed about changes in the location area. If the
mobile moves from a cell in one location area to a cell in another location area, the mobile phone
should perform a location area update to inform the network about the exact location of the
mobile phone.

The Location Update procedure is performed:

 When the MS has been switched off and wants to become active, or
 When it is active but not involved in a call, and it moves from one location area to
another, or
 After a regular time interval.

Location registration takes place when a mobile station is turned on. This is also known as
IMSI Attach because as soon as the mobile station is switched on it informs the Visitor Location
Register (VLR) that it is now back in service and is able to receive calls. As a result of a
successful registration, the network sends the mobile station two numbers that are stored in the
SIM (Subscriber Identity Module) card of the mobile station.

These two numbers are :-

1. Location Area Identity (LAI)

2. Temporary Mobile Subscriber Identity (TMSI).

The network, via the control channels of the air interface, sends the LAI. The TMSI is used for
security purposes, so that the IMSI of a subscriber does not have to be transmitted over the air
interface. The TMSI is a temporary identity, which regularly gets changed.

 A Location Area Identity (LAI) is a globally unique number.

 A Location Area Code (LAC) is only unique in a particular network.
Every time the mobile receives data through the control channels, it reads the LAI and compares
it with the LAI stored in its SIM card. A generic location update is performed if they are
different. The mobile starts a Location Update process by accessing the MSC/VLR that sent the
location data.
A channel request message is sent that contains the subscriber identity (i.e. IMSI/TMSI) and the
LAI stored in the SIM card. When the target MSC/VLR receives the request, it reads the old LAI
which identifies
the MSC/VLR that has served the mobile phone up to this point. A signalling connection is
established between the two MSC/VLRs and the subscriber’s IMSI is transferred from the old
MSC to the new MSC. Using this IMSI, the new MSC requests the subscriber data from the
HLR and then updates the VLR and HLR after successful authentication.

Periodic location update is carried out when the network does not receive any location update
request from the mobile in a specified time. Such a situation is created when a mobile is switched
on but no traffic is carried, in which case the mobile is only reading and measuring the
information sent by the network. If the subscriber is moving within a single location area, there is
no need to send a location update request.
A timer controls the periodic updates and the operator of the VLR sets the timer value. The
network broadcasts this timer value so that a mobile station knows the periodic location update
timer values.
Therefore, when the set time is up, the mobile station initiates a registration process by sending a
location update request signal. The VLR receives the request and confirms the registration of the
mobile in
the same location area. If the mobile station does not follow this procedure, it could be that the
batteries of the mobile are exhausted or the subscriber is in an area where there is no network
coverage. In such
a case, the VLR changes the location data of the mobile station to “unknown”.
The Location Update process consists of the following phases

 Request for service; the MS detects that it has entered a new Location Area and requests
to update its location. The new MSC/VLR identifies the MS.
 Authentication - The new MSC/VLR requests to the AUC for authentication parameters
(SRES, Kc, RAND). Using these parameters the MS is authenticated.
 Ciphering - Using the parameters which were made available earlier during the
authentication the uplink and the downlink are ciphered.
 Update HLR/VLR - The new MSC/VLR requests to update the MS location in the HLR.
The MS is de-registered in the old VLR.
 TMSI re-allocation - The MS is assigned a new TMSI.

1. The MS detects that it has entered a new Location Area and transmits a Channel Request
message over the Random Access Channel (RACH).
2. Once the BSS receives the Channel Request message, it allocates a Stand-alone
Dedicated Control Channel (SDCCH) and forwards this channel assignment information
to the MS over the Access Grant Channel (AGCH). It is over the SDCCH that the MS
will communicate with the BSS and MSC.
3. The MS transmits a location update request message to the BSS over the SDCCH.
Included in this message are the MS Temporary Mobile Subscriber Identity (TMSI) and
the old Location Area Identification (oldLAI). The MS can identify itself either with its
IMSI or TMSI. The BSS forwards the location update request message to the MSC.
4. The VLR analyzes the LAI supplied in the message and determines that the TMSI
received is associated with a different VLR (old VLR). In order to proceed with the
registration, the IMSI of the MS must be determined. The new VLR derives the identity
 of the old VLR by using the received LAI, supplied in the location update request
message. It also requests the old VLR to supply the IMSI for a particular TMSI.
5. The new VLR sends a request to the HLR/AUC (Authentication Center) requesting the
“authentication triplets” (RAND, SRES, and Kc) available for the specified IMSI.
6. The AUC, using the IMSI, extracts the subscriber's authentication key (Ki). The AUC
then generates a random number (RAND), applies the Ki and RAND to both the
authentication algorithm (A3) and the cipher key generation algorithm (A8) to produce an
authentication Signed Response (SRES) and a Cipher Key (Kc). The AUC then returns to
the new VLR an authentication triplet: RAND, SRES, and Kc.
7. The MSC/VLR keeps the two parameters Kc and SRES for later use and then sends a
message to the MS. The MS reads its Authentication key (Ki) from the SIM, applies the
received random number (RAND) and Ki to both its Authentication Algorithm (A3) and
Cipher key generation Algorithm (A8) to produce an authentication Signed Response
(SRES) and Cipher Key (Kc). The MS saves Kc for later, and will use Kc when it
receives command to cipher the channel.
8. The MS returns the generated SRES to the MSC/VLR. The VLR compares the SRES
returned from the MS with the expected SRES received earlier from the AUC. If equal,
the mobile passes authentication. If unequal, all signaling activities will be aborted.
9. The new MSC/VLR requests the BSS to cipher the radio channel. Included in this
message is the Cipher Key (Kc), which was made available earlier during the
authentication.
10. The BSS retrieves the cipher key, Kc, from the message and then transmits a request to
the MS requesting it to begin ciphering the uplink channel.
11. The MS uses the cipher key generated previously when it was authenticated to cipher the
uplink channel, and transmits a confirmation over the ciphered channel to the BSS.
12. The BSS upon ciphering the downlink channel sends a cipher complete message to the
MSC. At this point, we are ready to inform the HLR that the MS is under control of a
new VLR and that the MS can be de-registered from the old VLR.
13. The new VLR sends a message to the HLR informing it that the given IMSI has changed
locations and can be reached by routing all incoming calls to the VLR address included in
the message.
14. The HLR requests the old VLR to remove the subscriber record associated with the given
IMSI. The request is acknowledged.
15. The HLR updates the new VLR with subscriber data (mobiles subscriber’s customer
profile).
16. The MSC forwards the location update accept message to the MS. This message includes
the new TMSI.
17. The MS retrieves the new TMSI value from the message and updates its SIM with this
new value. The mobile sends then an update complete message back to the MSC.
18. The MSC requests from the BSS that the signaling connection be released between the
MSC and the MS.
19. The MSC releases its portion of the signaling connection when it receives the clear
complete message from the BSS.
20. The BSS sends a "radio resource" channel release message to the MS and then frees up
the Stand-alone Dedicated Control Channel (SDCCH) that was allocated previously. The
BSS then informs the MSC that the signaling connections has been cleared.
STP (Signaling Transfer Point)

Hi,

There are different types of signaling points in SS7 Standards, like

Service Switching Point (SSP) - like MSC, Tandem Switch, etc.
Service Control Points (SCP) - like HLR, etc.
Signaling Transfer Point (STP).

These Signaling points provide access to the SS7 network, databases, & transfer messages to
other signaling points.

STP :- It is a vital element in SS7 network serving as a Signaling hub for the transfer of
digital data packets between network nodes.

It routes messages throughout the network using, call information & network addressing
structured within SS7 data packets.

It serves as dynamic router, controlling traffic flow & access to variety of SS7 nodes & network.

Functions of STP :-

1. Receives the MSU's & direct them to appropriate destination.

2. Network Management.
3. (ANSI to ITU) or (ITU to ANSI) protocol conversion.
4. Global Title Translation (GTT).
5. Measurement of Data.
6. Gateway Function.
7. Gateway Screening (GWS)
8. Local Number Portability (LNP).

Different Links used with STP :-

 A-Link - It provide STP/SSP or STP/SCP connectivity. Maximum of 16 links can be

there in a link set or maximum of 32 links in combined set.

 B-Link - It connects one STP to other STP of same hierarchical level. Maximum of 8
links in quad configuration of link set.
  C-Link - Maximum of 16 links in a link set.
 D-Link - Maximumof 8 links in a link set.

 E Links - It connects a STP to other STP other then its Home STP & provides an
alternate route for SS7 messages if congestion occurs at home STP.

 F Links - It provides SSP to SSP connectivity. It provides only Call Setup/TearDown

capability & it should be adjacent.

Why STP ???

 It provides Centralized Network Management, facilitating the delivery of Intelligent

Services throughout the network.
 Reduction in Signaling Terminal Hardware in SSPs / SCPs. (like MSC, IN, HLR, etc.)
 Central Database for GTT at STP, Minimizes Errors.
 Efficient Routing of Messages.
 Flexible SS7 Network Management.
 Fast Integeration of New Nodes in the network.
 Easy Migration to Next Generation Networks like VOIP, Soft Switch, etc.
KPI - Key Performance Indicators

Hi,

KPI tells the performance of a network on a daily/weekly/monthly basis, which helps to

improve the network, so that operator & customer both enjoys the service at its most.

Key Performance Indicators for Telecom Industry are :-

Systems and Network Performance Analysis / Capacity Planning

 Availability
 Grade of service
 Service life of equipment
 Bit error ratio (data, bits & elements transfer)
 Bit rate (data, bits and elements transfer)
 Downtime / Time out of service
 Call completion ratio
 Cost of support systems
 Cost of operational systems
 Average call length
 Analysis of ASR routes
 Network traffic, congestion
 Idle time on network
 Dropped calls

Quality / Usage (Airtime): Analysis of the volume of successful calls

 Mean Opinion Score

 Service
 Duration of calls
 Billed amount on each call

Coverage

 % of land covered with services

 % of population covered with services
 Average land unavailable to services
 Average population unavailable to services
 Access to customer service
Faults and complains (Trouble tickets analysis)

 % of open and level of escalation priority required

 % closed
 Mean time to resolved
 Work in progress
 Customer service level statistics

Customer Analysis

 Customer segmentation
 Analysis of subscriptions
 Top N customers
 Churn (No. of Subscriber who stopped using Services or left particular network)

ASR (Answer Seizure Ratio) - Number of successfully answered calls divided by the total
number of calls attempted (seizures) multiplied by 100.
(Answer / Seizure) * 100 = Answer Seizure Ratio.
Standard Value = 40% - 45%.

MOU (Minutes of Usage) per Subscriber – It calculates the Total Minutes used in a Network
divided by the number of subscribers.

CCR (Call Completion Ratio) - Total no of calls completed / Total no of calls attempted *
100%
Higher the ratio is better.
Standard Value > 98%.

LUSR (Location Update Success Rate) - Its a ratio of no.of times mobiles update its location
successfully to the no.of times mobiles request network for Location update.
LUSR = (Location Update Success / Location Update Request)*100.
Standard Value >= 98%.

PSR (Paging Success Rate) - Its a ratio of no.of times network successfully find the mobiles to
the no.of times network tries to locate the mobiles within its area.
PSR = (No.of Network Paging Response / No.of Network Paging Attempts)*100.
Standard Value >= 92%.