Operation and Strategy Used in India for Implementation Mobile Number Portability

Only available on StudyMode
  • Topic: Mobile number portability, Local number portability, Porting Authorisation Code
  • Pages : 8 (1302 words )
  • Download(s) : 768
  • Published : February 3, 2011
Open Document
Text Preview
[pic]

OPERATION AND STRATEGY USED IN INDIA FOR IMPLEMENTATION MOBILE NUMBER PORTABILITY

NAME: - Shashank Kumar
FACULTY: - Prof. Rajiv Misra XAT ID: - 2406497 BATCH: - PGCBM-18 CENTRE:-Patna

ABSTRACT

With rapid increase of mobile service provider in world and as a developing country, India has emerged as the largest mobile service user country.

To improve the subscriber facility Indian telecom market had planned to implement the mobile number portability on PAN India basis as per guideline of DOT (Department of telecom).

This project will look at the operation and strategy used by different operators to implement the MNP on PAN India basis.

INTRODUCTION

Mobile service marketing undergoing a significant transformation, with previous voice centric service to values added service like sms, CRBT etc. and from 2G service to 3G services. The mobile service provider had studied the market and the found that many customer want to use the other operator service’s but unable to use the same because they don’t want to change the MSISDN.

So, as per guideline of department of telecom all service provider of India planned to introduce the new product MNP (Mobile number portability).

In MNP subscriber shall be allowed to choose mobile service provider without changing the MSISDN. They can use services provided by new service provider i.e. all existing service will be applicable for both ported & non ported number.

For implementation of MNP every operator have formed new team how will analyze the modification required to do current configuration, implementing the same and testing the all existing services.

PROJECT AIM

1. To analyze the change in definition of current system and impact.

2. To make strategy for testing the call scenario.

Change in definition of current system

For implementation of MNP call scenario, customers haven’t required to change in call dialing only they have to change the SIM of new service provider, hence only service provider have to change their system configuration and required to setup separate team to analyze the current configuration, making plan for new configuration & implementation and after completion of implementation we have to test the call scenario as per guideline.

For change in definition we required to upgrade different nodes as per requirement.

Core node (Call handling system)

• MNP feature implementation

• CDR format adaptation

• Capacity re-arrangement

• Signaling expansion

• Routing re-configuration

Pre-paid Charging System

• MNP feature implementation

• Traffic table updates

• Signaling expansion

• Capacity re-arrangement

IT System

• Required to made connectivity with central server

• MNP feature implementation

• Capacity re-arrangement

For change in core & pre-paid charging system new node STP introduced by telecom vendor for controlling the call scenario and those STP connected with DOT STP for controlling the migration of subscriber from one service provider to other. After connecting the new node signaling architecture also revised

– STP for Intra-Circle IN traffic

– MNP database within co-located STP

– SMS traffic within Cluster

– Roaming traffic within Cluster

Strategy used for testing the call scenario

As per DOT there are 23 circles in India and approx 16 operator which are providing service in same excluding PSTN & ILD service provider. To complete the testing PAN India basis as per DOT one day is given to each operator to complete the...
tracking img