analytical research on subscriber data migration technique

IJSRD - International Journal for Scientific Research & Development| Vol. 5, Issue 09, 2017 | ISSN (online): 2321-0613

All rights reserved by www.ijsrd.com 302

Analytical Research on Subscriber Data Migration Technique in HLR Pratiksha Malviya

Gargi Institute of Science &Technology, Bhopal (M.P), India

Abstract— The objective of this research is solely

concentrated upon obtaining testing and verifying best

available technique in Subscriber Data Migration in HLR.

As now a days with the advent and innovation in

technologies there are lots of techniques and tools available

in the market for any purpose but as a service provider the

main emphasis lies upon customer satisfaction and ease in

utilization. But due to continuous highly projected growth

and competition in network and communication sectors

merger is now seems to be a common emerging term in

market. At this juncture customer data migration needs to be

dealt with highly expertise and professional in this field so

over keen interest in this project is to provide a depth

analysis on its methodologies and intervening process and

techniques that needs to dealt with the accompanying need

to complete this work successfully and efficiently.

Key words: HLR (Home Location Register), AuC

(Authentication Center), HDF (Hlr Data Function), ESM

(Enhanced Services Manager), Load Balancing Techniques

I. INTRODUCTION

This document describes the ‘Method of Procedure (MOP)’

to migrate the subscriber data from one server to another

geographically separate server in a running network. The

case where a whole subscriber data from one server will be

migrated to other servers is also described in this document.

HLR is the functional entity that represents the primary

database repository of subscriber information used to

provide control and intelligence in cellular and wireless

networks.

The HLR is managed by the cellular service

provider and represents the "home" database for subscribers

who have subscribed to the service in that home area.

The HLR contains a record for each home

subscriber that includes location information, subscriber

status, subscribed features and directory numbers.

Supplementary services or features that are provided to a

subscriber are also finally controlled by the HLR.

A. HLR for the Home Network

An HLR only stores subscribers belonging to the operator

whose HLR it is. An exception to this rule is when an

operator and an MVNO (mobile virtual network operator)

have an agreement whereby the operator provides HLR

space to the MVNO (generally along with other network

infra structure resources).

B. WHAT ARE THE FUNCTIONS OF AN HLR?

1) Authentication

Protecting the subscriber and operator from fraud.

2) Mobility management

Keeping track of each subscriber’s location in the network.

3) Call routing

Providing the subscriber’s location to the network.

4) Service profile management

Keeping track of changes to the profile

This service is designed for migration of HLR

subscriber data, but it can also be adapted to other scenarios.

It provides for migration of data to HLR nodes from one

HLR node to other HLR node. Through this service you can

expect higher end-user satisfaction, with little or no impact

on in-service performance and an end-user perceived

seamless service.

II. METHODOLOGY

This service is primarily designed for migration of

Prepaid/Postpaid system, HLR and SCP subscriber’s data,

but it can also be adapted to other scenarios. It provides for

migration of data to one HLR nodes from other HLR nodes.

Through this service you can expect higher end-

user satisfaction, with little or no impact on in-service

performance and an end-user perceived seamless service.

A. Pre-Migration procedure

Before the actual subscriber data is migrated, check that all

the prerequisites are fulfilled and all restrictions and

Recommendations have been considered.

B. Which directly speculate in that manner as directed-

1) Verify that both servers are running the same in-service

software release that support the

same authentication algorithm.

2) Verify that both servers are patch current.

3) Verify that the system datafill on the source data

SERVER(DF03) is also present on the destination

SERVER(DF04).

C. Right before starting the migration, check that neither of

the following occurs

software upgrade of nodes,

restarts,

link ovrload or failures,

processor overload,

image dump

D. System tools used for the process

UNIX operating system

Network element

Load balancing tool in server

Analytical Research on Subscriber Data Migration Technique in HLR

(IJSRD/Vol. 5/Issue 09/2017/073)


III. MIGRATION PROCEDURE:

Here we are discussing about the procedure which we are

using for subscriber data migration.

A. Step 1:

Network element available in esm server, to migrate the data

we need to do some setting for network element which is

given in below snap shot:

1) Network Element Setting for GUR DF04

2) Before Activity GUR DF0




3) Before Activity TUR DF03:

B. Step 2:

First we need to take subscriber dumps of directory number

& common phone(file name) in source node(GUR_DF03) &

take the health check of the system using below command.

df –h (for disk space)

ifconfig –a (network interface)

iostat –en (to check error hardware/software)

ntpq -crv (node synchronisation with NTP server)

Mirrors

dmesg

uptime

who –b

metastat

prstat

this are the hardware command used to check system health

check, it should be fine.

C. Step 3:

To migrate the data next step is to prepare input file which is

having subscriber data with the help of CUI(UNIX

COMMAND ).

50000 50kaa

50000 50kab

50000 50kac

50000 50kad

50000 50kae

50000 50kaf

20000 20kaa

20000 20kab

6467 20kac

We can prepare this file with the help of vi

editor/touch or cat command in unix.

During this period provisioning should be stopped,

here provisioning means any kind of activation or deletion

of any services for the subscriber’s number.

After preparing the above file need to upload the

same in load balancing tool

50000 in DF5 (50kaa is filename which is uploaded

in load balancing tool here source & destination server also

need to fill in tool as given below)

IV. EXPERIMENT AND RESULTS

In subscriber data migration analysis, the manual technique

for seamless data migration was compared with the advance

technique using load balancing tool in server & found that

using load balancing tool subscriber data is migrated in very

little time without knowing the subscriber.

A. Prepared file from source server (TUR_DF03)

To type text into the editor, type a lowercase “i” to enter

editing mode. Type your text and press Esc to return to

command mode. To close Vi and save your file, type “:wq”

and press Enter. created file uploaded in load balancing tool




1) Load balancing Start




2) While submitting the order

3) Subscriber data submitted with IMSI




4) Process in Progress

5) Process Succeeded




6) GUR DF03 after updating

7) TUR DF03 after updating

V. CONCLUSIONS AND FUTURE SCOPE

In manual migration technique, we have observed that more

time require for this process to migrate millions of data we

require a fast process which will help to migrate the data

quickly.

Here, we have observed that in manually we need

to create & delete the data one by one which was taking

time as well as during the time of creation of profile in other

server data was available in both the server by which

authentication process was failed & customer was suffered

from call drop. To avoid this problem we have installed a

load balancing tool in provisioning server in which we have

uploaded the subscriber’s data. To upload the data in load

balancing tool, first we created a file which have number of

subscriber data. Uploaded the file in load balancing tool &

set the network element field, source & destination server &

submit it. We have observed that data is migrated in very

less time period without any call dropping & within very

less period of time it will create the data in destination

server & delete the same from source server. The result we

have seen huge amount of data migration seamlessly.

REFERENCES

[1] Kurt Tutschku. Keynote: Mobile Service Evolution und

Research Trends in Future Internet. In Computer




Software and Applications Conference Workshops

(COMPSACW), 2011 IEEE 35th Annual, pages 46 –47,

July 2011.

[2] C.M. Machuca. Expenditures Study for Network

Operators. In Transparent Optical Networks, 2006

International Conference on, volume 1, pages 18 –22,

June 2006.

[3] J.D. Chimeh. Mobile services: Trends and evolution. In

Advanced Communication Technology, 2009. ICACT

2009. 11th International Conference on, volume 02,

pages 946 –948, February 2009.

[4] Marius Corici, Dragos Vingarzan, Thomas Magedanz,

and Thomas Magedanz. 3GPP Evolved Packet Core -

the Mass Wireless Broadband all-IP architecture.

Telecommunications: The Infrastructure for the 21st

Century (WTC), 2010, pages 1 –6, September 2010.

[5] Ericsson AB. Voice and Video calling over LTE,

February 2012. Available from:

http://www.ericsson.com/res/docs/whitepapers/

WP-Voice-Video-Calling-LTE.pdf. [Accessed 20

March 2012].

[6] Srini, Rao. Mobile Broadband Evolution - LTE and

EPC, April 2010. Available from: http://ieee-

boston.org/presentations_

society/lte_epc_ieee_comsoc_rao_april_8_2010.pdf.

[Accessed

25 November 2011].

[7] Ericsson AB. Introduction to IMS, March 2007.

Available from:

http://www.facweb.iitkgp.ernet.in/~pallab/mob_com/

Ericsson_Intro_to_IMS.pdf. [Accessed 22 November

2011].

[8] Korinthios Georgios. Mobile Services Network

Technology Evolution and the role of IMS. Available

from: http://www.ict-

fireworks.eu/fileadmin/events/FIREweek/2nd-WS-

Converged-Networks/

03-Georgios_Korinthios.pdf. [Accessed 23 November

2011].

[9] G. Camarillo and M.A. García-Martín. The 3G IP

Multimedia Subsystem (IMS): Merging the Internet and

the Cellular Worlds. John Wiley & Sons,

2007.

analytical research on subscriber data migration technique

Documents