When it comes to mobile number portability (MNP), it is always a different story in every country, with a unique combination of factors and conditions driving the introduction of MNP in each case. Typically, it is the government who wants to fuel competition in the communications sector by implementing regulation aimed at providing subscribers with more choice. In most countries with a population of more than 100 million people, MNP has already been launched or is on a trial run.
For telecom operators, enabling MNP is a complex and challenging task requiring a lot of investment with no guarantee of a return. It is commonly assumed that MNP spurs competition in the communications industry, allowing for a better quality of service. But, before this can be achieved, major changes have to be made to administration, address allocation and management, signaling, call handling and routing, payment systems, etc.
Faced with the challenge of MNP, operators have to deal with lots of issues and problems in order to make their infrastructure and systems MNP-ready, as well as to adjust their business processes accordingly. This explains why sometimes operators oppose the introduction of MNP – they just don't want to be the ones to bear the financial and personnel costs associated with it. To make things even worse, MNP launch-related investment is just the first step which is inevitably followed by additional investment in network upgrades (not just technical, but administrative and financial infrastructures need to be modernized as well), setup of an administrative framework for number portability, maintenance, routing, etc.
However, operators can easily turn all these challenges to their advantage and greatly benefit from MNP launch. What they need for this is a well thought-out approach to the implementation of the project and the right solution.
Integrates with BSS systems of other vendors via a message bus (MBUS)
Continues serving subscribers even after the centralized NPDB becomes unavailable
Provides data for inter-operator settlement and keeps the data up-to-date
Ensures correct call routing by providing the necessary data
Synchronizes with the centralized NPDB
Provides interfaces for integration with external systems over the AMQP protocol