 |
applications |
number portability
pulseINP’s Number Portability
module allows operators to efficiently and cost-effectively run
routing queries based on a local or external NP database.
Local Number Portability (LNP) is a requirement that every carrier
is mandated to meet today. It removes potential subscriber barriers
when moving between networks and provides the ability to retain
existing telephone numbers when switching from one carrier, region
or service to another.
The pulseINP NP module supports
any of the following scenarios:
- Local service provider portability: Customers maintain their
existing number while changing local service providers
- Service portability: Customers maintain their existing number
while changing their service (e.g. Wireline to Mobile or Mobile
to Wireline)
- Intra-number portability: Ability to port numbers from switches
or networks within the same carrier
- Geographic portability: Customers maintain their existing number
while changing locations
Benefits
- Simplified management: Operators can instantaneously manage
and update information from a user friendly web-based interface
- Proven ROI within existing operators: Existing pulse customers
have seen aggressive returns by being able to manage their database
with a reliable proven platform
- Flexibility: Provides operators the flexibility to host the
database internally or to outsource as required
- Modular and multi-application environment: Other services including
CNAM and LIDP services can easily be integrated and managed
|
|
Features
- Integration to multiple switches and provides centralized
management
- Support queries on SIP, SIGTRAN, ENUM, ESPP and SS7 Networks (IN AIN, GSM, CDMA, INAP)
- Support for other services such as Caller Name Delivery
(CNAM) and Line Information Database (LIDB) services
- Integration to third party Local Service Management Systems
(LSMS) and Service Order Administration (SOA) platforms
can integrate into various configurations for different
tiers of carriers:
For Tier 1 & 2
- LNP: Ported number moved to another carrier
- Intra-LNP for Tier 1 & Tier 2 carriers: Ported number
is within same carrier, same network or multiple networks
- Supports any of the following implemenations:
All Call Query or Direct Routing (central database
solution): This does not involve the donor switch
and requires centralized LNPDB to process the call.
Query on Release: In this case the originating
network queries the donor network to see if the DN has
been ported. If so, a centralized DB is queried for LRN
and call routing. This places a call routing burden on
the donor network.
Call Dropback or Return to Pivot (RTP):
Originating network routes call to donor network; the
donor network returns routing information for call completion.
The donor network maintains its LNPDB for its numbers.
Call routing burden is placed on the donor network.
Onward Forwarding or Indirect (call forwarding
solution): Routes calls to donor network, the
donor network maintains LNPDB and performs a lookup and
completes calls.
|
|
For Tier 3
- Full LNP solutions
- Complete the call using the LRN
- Lookup the DN and receive Global Title Translation (GTT)
information from the LNPDB and perform a query for the
LRN using GTT and then complete the call
- Lookup using IP (XML, SIP, ENUM)
The pulseINP NP modules
also provide enhanced reports such as:
- Reports on the number of DIPs performed for a specified
period of time
- Details on the DIPs
- New updates
- Other customized reports
|
|
|
