Optimal routing in STC GSM network

This draft document describe the network configuration impact to introduce the
optimal routing service based on Prefixed and Non-prefixed dialling into GSM
network for the Post-paid subscribers.
The Pre-paid , Camel traffic cases and related optimally routed call CDRs has
not been addressed in this document but would need to incorporated on later
stage after getting more information about the service.

General Description

The optimal routing is a network feature, by which calls directed to a mobile

subscriber, who has roamed away from his HPLMN, are routed directly i-e locally
(instead of via the HPLMN) to the mobile subscriber's actual location, or the
forwarded-to destination.

Network Topology
The next figure shows the pilot network configuration.

I n t 'L
L o c a t io n u p d
N e t w
v ia I n t 'l n e t w

Traffic cases for OR dialling

S T C
I G W
 a) MO Call from Local STC GSM subscriber to In-bound roamer.
b) MO Call from In-bound roamer to another In-bound roamer in
STC network.

Pre-requiste:

- In Aljawal network MSC/GMSCs are configured to fire MAP

SRI message to Roamware OR node (optimal routing node).

- Define GRI route to fire SRI message (Existing GRI route

“0GRI3” can
be used which is built for MAP version 3.
- Define the MTP and SCCP routing for the new OR node with
SSN=6.
- Define B-number analysis to send the calls to new OR node.
- Define New charging case and and Tariff case to filter OR
related CDRs
( Further study will be done on this issue in coordiantion with
STC Eng).

General Non-prefix based OR call flow

- A party dial the Int’l MSISDN number.
- Originating MSC will fire MAP SRI message with dialled B-number
(B-party MSISDN) towards OR node.
- The Roamware OR node receive the SRI and perform checks to
see the optimal routing is allowed or not to the subscriber and its
operator.
- If check successful then obtain the MSRN for the B-party and
send SRI-Ack with MSRN back to the originating MSC and GMSC
will route the call locally.
- OR node will work as virtual HLR to send PRN to the terminating
MSC.
- If the B-party checks fail and OR is not allowed then the SRI-Ack
is returned with the original B-party MSISDN unchanged.This call
is then routed out through the GMSC in the normal way on the
int’l network.

General prefix based OR call flow

- A party dial the Int’l MSISDN number by adding pre-fix i-e *1.
 - Originating MSC will fire MAP SRI message with prefixed B-
number (B-party MSISDN) with out 00 towards OR node.
- The Roamware OR node receive the SRI and perform checks to
see the optimal routing is allowed or not to the subscriber and its
operator.
- If check successful then obtain the MSRN for the B-party and
send SRI-Ack with MSRN back to the originating MSC and GMSC
will route the call locally.
- OR node will work as virtual HLR to send PRN to the terminating
MSC.
- If the B-party checks fail and OR is not allowed then the SRI-Ack
is
returned with the Error message and the call released by the
originating
MSC and the call should not routed out through the GMSC in the
normal
way on the Int’l network.

Note:

1) No change in message flow for the location updating for

the
In-bound Roamers.

2) No change in message flow for the MO Call from In-bound

roamer
to Local STC GSM subscriber or to STC outbound
roamer.

3) No change in message flow for MO call from STC out-

bound roamer to In-bound roamer.

4) No need to establish new C-7 link, exiting C-7 link b/w

STGs and
Roamware node (RGM1) will be used to access new OR
node for the
optimal routing.

CDRs for Optimally routed call

- The MO TT record will be generated in the originating MSC/VLR
based on
the charging and tariff class specified in BO=32.

- No roaming call forward CDR will be generated as there is no CC

in BO=8 but it can be generated if needed.

- The MT TT record will be generated in the terminating MSC/VLR.

(It is required to devise a mechanism to identify tne MT CDRs for
OR calls.