Title

A 3G/WLAN Integrated Network based Mechanism for Improving the Efficiency of Mobile
Number Portability Service.

OBJECTIVES
General objectives:
To Improve the Efficiency of Mobile Number Portability Service Utilizing 3G/WLAN Integrated
Networks
Specific objectives:
To investigate the NPBD traffic load, congestion and call setup delays during Conventional NP
calls.
To design a 3G/WLAN based system for distributing the routing information from the Database
to the UEs
To evaluate the alleviation of the heavy traffic load during NPDB queries and the reduction in
average response time for the NP call setup process after implementing the proposed mechanism.

JUSTIFICATION
The proposed mechanism will suppress the prolonged routing information processing time for a
large NPDB which is prevalent in the current system.
Performing the number translation process at the early stages (UE) of call setup process will
conserve the extra communicating resources and bandwidth that would have been consumed
during routing information query process.
The same 3G-WLAN network can be utilized to provide low cost voice communication services t
people in hotspot areas.
SIGNIFICANCE OF THE STUDY
The operators will make profits from the saved extra communication resources (Bandwidth) that
would have been occupied during the NPDB query process.
The storage of the routing information at the users’ terminals will effectively alleviates traffic
congestion and heavy workload on NPDB.
It will save the call setup time for the users.
It is a cost effective mechanism to distribute the routing information to the UEs over WLANs.
Every user will easily access the RIS to update the routing information by making it accessible
via the internet.
SCOPE OF THE PROJECT
The research has been conducted in the time frame of the academic year 2018/2019 between
January and May 2019.
The research is only limited to the evaluation of the proposed mechanism’s performance. It does
not give a detailed design and algorithm of the proposed mechanism.
The research focuses on service provider number portability (SPNP). Other forms of MNP like
location portability will not be covered in this research.
The research mainly focuses on voice call setup. Other services like SMS and data services have
not be considered.
The model is based on All Call Query (ACQ) call routing mechanism.
The research is limited to only wireless mobile communication services. It shall not consider fixed
or wireline communication services.
The simulations have been carried out using MATLAB and OMNET++ Network simulation
software.

Mobile Number Portability (MNP) service allows the mobile subscribers to retain their mobile
phone numbers when switching from one service provider (Operator) to another irrespective of
mobile technology or from one technology to another of the same or any other access service
provider, in a licensed service area..
Number Portability involves only the MSISDN number, and not the IMSI. A subscriber who
switches to another mobile network operator will be allocated a new IMSI (together with a new
SIM card) while retaining his MSISDN.
Originally, a telephone number is assigned to a mobile network. This network is called the number
range holder (NRH) network. The subscription network is the network with which a mobile
operator has contract to implement the services for a specific mobile phone number. The “moved”
number is referred to as a ported number.

Types of Number Portability

The various types of number portability are:-
Service Provider Number Portability: Subscribers can change the service provider while
retaining the same phone number. It is also called operator portability.
Location Number Portability: Subscribers can change their service location while keeping the
same telephone number.
Service Portability: Subscribers can change the subscribed services while retaining the same
telephone number. Service portability allows the subscribers to enjoy the subscribed services in
the same way when they roam outside their home networks
This research focuses on service provider number portability (SPNP), as SPNP is the
primary form of number portability that promotes competition among the mobile service
providers.

SERVICE PROVIDED NUMBER PORTABILITY

To support mobile number portability, the normal call termination procedure (without number
portability) must be modified to by adding mechanism for obtaining the correct routing
information. This is achieved by using a number portability database (NPDB) that stores the
records of the ported numbers.
The record information includes the ported MSISDN, the status (active or pending), the time
stamps (when the ported number record is created, activated, disconnected, and modified), the
NRH mobile operator, the subscription operator, and the routing information.
The routing information includes several addresses to support applications such as switch-based
services, calling card, and short message service. For non-ported numbers, no records will be
maintained in the NPDB.
Database queries are implemented using SRF-based or IN-based solutions. SRF utilize the MAP
protocol to enable the portable number translation. The IN-based solutions differ form the SRF-
based solutions in the way to access NPDB. In the SRF-based solution only GMSC can query
NPDB, but in the IN-based solution every switch equipped with the IN protocol can access NPDB.
The call initiation processes of IN-based and SRF-based systems are similar.

Number Portability Call Routing Mechanisms

1) Call related methods
ii) All Call Query method
The All Call Query method implies that the Originating network has the knowledge that the dialed
number is ported and can route the call directly to the recipient network without involving the
Initial donor network. It is the Originating network that will interrogate an NPDB for all calls (to
portable numbers), to check if the number has been ported or not and route the call to the
terminating network. The NPDB will in this case contain information of all ported numbers.
NOTE: This research focuses on All Call Query method described below
 Origination Network
Termination Network
MS 1
GMSC
MS 2
1 MSC 8
2 9

5
3 4 7

GMSC 6

HLR
NPDB
Subscription Network
Routing Information DB

The figure illustrates a call from a mobile station MS1 to a ported mobile station MS2 with the
following steps:
Steps 1&2: MS1 dials the MSISDN of MS2. An ISUP IAM message is routed from the originating
BSC, across the MSC to the originating GMSC.
Step 3: The originating GMSC issues the MAP send routing information message to the SRF.
Step 4: By consulting the NPDB, the SRF obtains the subscription network information of MS2
and forwards the information to the originating GMSC. The SRF provides the routing number
(RN) to the originating GMSC. The RN consists of a RN prefix plus the MSISDN of the called
party. The RN prefix points to the subscription GMSC, which may also provide the HLR address
of the called party.
Step.5: The originating GMSC then routes the IAM message to the GMSC of MS2 in the
subscription network. After this point, the call is set up following the standard GSM/UMTS
procedure.
Steps 6 & 7: The subscription network queries the home location register(HLR) for the MSRN of
the called party to reach the termination network, and forwards the IAM message to the termination
mobile switching center (MSC)) to set up the call.
ii) Onward Routing method
The Onward Routing method implies that the Originating network has no knowledge whether the
dialed Number is ported or not and uses the traditional routing plans for routing the call to the
Initial donor network for further routing decisions. It is the Initial donor network that will
interrogate an NPDB, but only for its own numbers, and then route the call to the terminating
network. The NPDB will in this case contain information of only the initial donor operator´s own
ported-out numbers.
1. From an Originating GMSC, the call is routed to the Initial donor network;
2. When GMSC in the Initial donor network receives the ISUP IAM, it requests routing
information by submitting a MAP SRI to SRF.
3. When the SRF receives the message, it retrieves the RN from the database and then respond to
the GMSC by sending an SRI ack with a RN + MSISDN.
4. GMSC uses the RN + MSISDN to route the call to GMSC in the Recipient network.

Non-call related methods

Non-call related functions is needed to support teleservices e.g. SMS and other supplementary
services.
Note: this research is based on only call related service.
Short Coming In The Above Convention NP Service
When the number of users grows rapidly, the numerous traffic of users incurs long NPDB query
delay. The considerable number of queries burdens the load of NPDB and therefore NPDB
searching becomes the bottleneck of NP service due to the long delay time of NPDB search, the
long queuing time and the heavy traffic load. Moreover, the bandwidth reserved for the caller is
occupied during the call setup process, but operators rarely make profit on it.
Therefore, there is need to enhance the efficiency of database queries in order to improve the
overall performance of NP service.

What Has Been Done To Overcome The Shortcomings

Some studies proposed the implementation of caches in the telecommunication network to reduce
the database queries however the efficiency of this method depends on the cache size, the policy
of cache management and the level of hierarchy at which the cache is applied
Implementing caches in the core network will require a large cache size to accommodate the
numerous dialed numbers with their corresponding routing information. But the cost to manage
and update such a large cache is expensive for operators to broadcast the altered routing
information to all terminals that a lot of transmission resources are consumed.
Further research also suggested the use of organization based mobile communication system which
exploit the fact that many calls within an organization are made between organization members
during business hours and therefore by keeping routing information of frequently dialed numbers
in organization-based (OGB) networks, the workload of portable number translation could be
shifted towards the OGB networks. However, this method can only benefit the users in the service
area of the OGB network.
Therefore, a much more effective approach is one that can minimize routing information queries
during call setup process by performing the number translation process at the User Equipment.
This research proposes a mechanism for distributing the routing information of the users’
frequently dialed numbers to the user’s terminal such that the number translation process is carried
out at the user’s terminal thus eliminating the need for database queries during call setup process.

3G/WLAN Interworking Communication System

The efficiency of MNP services can be improved by exploiting the emergency of 3G/WLAN
Interworking systems which is an integrated wireless data access network combining the 3G
cellular networks and WLANs to provide mobile users with both ubiquitous connectivity and low
cost high-rate data service in hotspot areas.
Since WLAN systems offer higher transmission rates of up to 500Mbits/s as well as data
distribution capabilities at a lower cost whereas 3G systems provide global coverage, 3G-WLAN
integrated services provide a way of combining the distributed data storage and computational
capabilities of WLAN with the global connectivity of 3G networks.
The 3G/WLAN dual mode user equipment (DMs) are equipped with interface to both 3G and
WLAN networks.
The two different interworking mechanisms developed to support mobility, security, QoS,
charging and billing are; the tightly coupled and loosely coupled heterogeneous networks.
In the tight-coupling architecture, the WLAN is connected to the 3G core network as one 3G
radio access network whereas in the loose-coupling approach the WLAN is connected to the
cellular core network indirectly through an external.
This system can therefore be utilized to achieve early stage number translation by distributing the
routing information from NPDB to a WLAN Routing Information Server (RIS) which will further
distribute this information to the DMs. In so doing, the time-consuming NPDB queries will be
omitted and the heavy NDPB traffic load mitigated. It will also conserve the extra communicating
resources and bandwidth that would have been consumed during routing information query
process.
This study discusses the method for distribution of the altered routing information of portable
numbers to the DMs.
Furthermore, it will investigate the prolonged NP call setup time and the heavy traffic load of the
NPDB during conventional NP service. Finally, it analyzes the efficiency of the proposed
mechanism by evaluating the alleviation of the heavy traffic load during NPDB queries, and the
reduction in NPDB queuing time and overall call setup time.

Distribution Of Routing Information to the DMs

WLAN
RIS
1 2
New Subscription Network

4 AP 3
DMS
I HLR
GMSC

GW II

GMSC

Customer
profile
Old Subscription Network
NPDB

For utilizing the user’s MS to perform the service of portable number translation, a mechanism to
distribute and renew the routing information of portable numbers from the NPDB to users’ MSs is
shown in the figure above.
Since most of the calls are set to the numbers called in the previous week. Keeping the routing
information of a user’s most frequently dialed numbers in the user’s UE can resolve the routing
addresses of most of the dialed numbers, which is a low-cost and effective solution to ease alleviate
the database queries.
The Figure presents the operation of retrieving and distributing routing information in the
3G/WLAN dual-mode communication environment.
When a number is ported out from one subscription network to another, both the old and new
subscription network issues an update message to the Database to update the new routing address
of the number in the NPDB as shown by the green doted lines.
Accordingly, in steps I & II , the RIS of the WLAN periodically retrieves altered routing
information for a portable number from the NPDB.
In steps 1 to 4, the DMs users interact with their subscription WLAN to update the routing
information on their MS. A WLAN subscriber can register a profile of his or her address book in
the RIS;
The routing information can be updated when the user in in the service region of the register
WLAN, or if they can access the WLAN by the Internet.
Since most of calls are set to numbers already stored in the phone contact list, the routing
information (subscription network ID) of the user’s frequently dialed numbers can be mapped to
and stored with their corresponding numbers in the address book.

Investigation Of Waiting Delay

In queuing theory, a queue is defined by Kendall’s notation A/B/c/N/K
A represents the interarrival-time distribution,
B represents the service-time distribution,
c represents the number of parallel servers,
N represents the system capacity,
K represents the size of the calling population.
Considering NPDB to be a single-server queuing system with a (M/M/1) modal;
This means the arrival rate is defined by a Poisson distribution with mean arrival rate λ
(𝝀𝒕)𝒏
Probability that n arrivals occur in interval of length t is 𝑷𝒏 (𝐭) = 𝒏!

The service time is exponentially distributed with mean µ

𝒕
Probability that next arrival occurs in t seconds is 𝐏(𝐒 ≤ 𝐭). = ∫𝟎 𝝁𝒆−𝝁𝒔 𝒅𝒔 where S is the time
between two random arrivals.
Using method of imbedded Markov chains to derive expression for the average database Queue
length (Lq).
𝝀
𝑳𝒒 = 𝝁(𝟏−𝝆) where ρ is the server utilization factor

From Little’s equations, the average waiting time (W) spent in the database is thus given by;
𝟏
𝑾=
𝝁(𝟏 − 𝝆)
The relation of expected waiting time and the offered traffic of the NP service network is illustrated
by figure below;

Let P denote the percentage NP calls routing routed using the information stored at the UE.The
figure below illustrates the reduction in average waiting time with increase in the value of P
Proposed Operation model For Routing Calls Using the Information at The UE
Depending on the type of user equipment, whether correct routing information is present at the UE
or no routing information for the dialed number is stored at the UE, the call will be routed to the
terminating network under three cases described below;

Case 1: When The information is not stored in the UE.

This is similar to the convention NP system where the call is routed to the terminating switch by
first querying the data base for the routing information. Therefore, both call setup delay (Tconv) and
traffic load are equal to those in the conventional system.

Origination Network
Termination Network

GMSC
7
1 MSC

DMS

4
2 3 6

GMSC HLR
NPDB
Subscription Network
Routing Information DB

Case 2: When the stored information is correct.

When the correct information of the dialed number is stored at the terminal, the number translation
process will be carried out at the terminal and then the call routed to the right subscription network
without querying the database.
The right subscription network ID will be carried in the initial IAM message and when the GMSC
determines that the number has already been translated it will directly route the call following the
normal non-NP call procedure.
This will result into a much more reduction in NP call setup time (Tcorr) and database traffic load
as compared to the conventional NP system.
Tcorr < < Tconv
 Origination Network
Termination Network
DMS
GMSC
1 MSC
2 6 7

3
5

GMSC 4

HLR
NPDB
Subscription Network
Routing Information DB

Case Three: When the stored information is incorrect.

This will be due to failure of the terminal to request for the updated information when it is unable
to access the RIS by either WLAN or internet.
When the obsolete information is carried in the IAM message, the call will be routed to a wrong
address and therefore the originating network switch will have to reissues a database query for the
correct routing information. This will result into a much more prolonged NP call setup time (Tobs)
as compared to the conventional NP system.
Tobs > > Tconv
 Wrong Network

4 GMSC

HLR

3 5
Subscription Network
Origination Network
GMSC 9
DMS 8
GMSC HLR
1
2
10

6 7

12

MSC 11
NPDB
Termination Network
Routing Information DB
 Wrong Network i-iii: Case 3: Cache miss

a: Case 1: Cache hit and data is correct

2 GMSC
1-6: Case 2: Cache hit and data is incorrect
HLR

3 1
Subscription Network
Origination Network
GMSC C
DMS 6
GMSC a HLR
A iii
B
D
i ii

4 5

MSC E
NPDB
Termination Network
Routing Information DB
Simulation Results
To evaluate the reduction in the traffic load, database congestion and the call setup time in the
proposed system as compared to the current NP system, Simulation has been carried out using the
knowledge of queuing theory and Omnet++ software
Since equal call setup delays and traffic load are experienced for both non-NP calls and NP calls
between the UE1 & OGMSC and between UE2 & TGMSC, the simulation only focuses on the
delays and traffic load between the originating network switch, NP database and the terminating
network switch.
Using the
above

diagrams, the originating network switch is the source(population) of calls that generates and send
calls to the database with a certain interarrival time according to the Poisson probability
distribution. Calls whose routing information has been obtained are forwarded by the originating
switch through the terminating network switch to the called Users equipment (UE).
The NP database is a single server First In First Out (FIFO) queueing system with a specified
Poisson inter arrival time and a specific exponentially distributed service rate. It serves based on
the memoryless property that during a very small time interval, only one events takes place and
therefore all Calls that arriving at the database will be kept in queue until they are served by the
server (their routing information is obtained) and then forwarded to the originating network switch
which further forwards them to the called UE.

Results Graphs
1) Graph of Maximum and Minimum delay time During Each Case

From the Graph, the delay for case 2 delay is less than Case 1 delay which is less than Case
3 delay

Graph showing the overall average delay time for the Three cases

The overall average delay time is less by cases 3 & 1 delay but more that case 2 delay. However,
this can be reduced to a value between case 1 and case 3 delay time if cases of routing using wrong
information are minimized.
 2) Variation In Queue Length

5) Queue waiting time Variation

Results for the Convention System

Comparison of results

Conv quelength

Prop delay

Prop average
Traffic load
Prop q length
Conv q length
Prop waiting time
Concv wait time