|
There are three LNP topics that cause the
greatest impact to the Wireless Service Providers (SP) that must be addressed
immediately according to the FCC mandates:
Major Impacts:
- Mobile Identification Number (MIN)/Mobile Directory
Number (MDN) separation:
In an LNP environment, mobile subscribers will require two
types of numbers: a MDN and a MSID. The MDN will be the dialable NANP
telephone number and will be portable in a SP portability environment. The
MSID will be non-portable and non-dialable. The MSID can be formatted as a
15 digit International Mobile Station Identifier (IMSI) or a 10-digit MIN
 | MDN – Mobile Directory number |
 | Portable phone number |
| Dialable |
| MSID – Mobile Station Identifier |
| Not Portable |
| Non-dialable |
| 10 digits |
| Programmed into mobile station |
| Assigned to wireless network providers in blocks of
10,000 |
| MSIDs must be mapped to a Location Routing Number
(LRN). |
| The LRN has the following characteristics: |
| 10-digit Network Routing Address w/ NPA-NXX
significance |
| Points to a specific switch |
| One LRN per LATA per switch |
| Associated with Directory Numbers |
| Chosen by provider from existing number block |
| Listed in Local Exchange Routing Guide (LERG) |
| Method of routing used by wireline and wireless
|
- Inter-Carrier Communications Process (ICP)
| The ICP addresses the communication process between the
New Service Provider (NSP) and the Old Service Provider (OSP) regardless
of the port direction (wireless to wireless, wireline to wireless, or
wireless to wireline). In order to process a port request, it will be
necessary to collect new porting data from the customer and populate new
fields on the service order. The ICP will generate the mechanized data
structure, i.e. forms, to be passed between the two SPs.
|
- Service Order Administration (SOA)
| The SOA provides a mechanized interface between the SP’s
OSS and the NPAC. Communication with the NPAC is critical to number
portability and the maintenance of the regional Number Portability
Database (NPDB). Communication is facilitated either by a mechanized SOA
system or NPAC Low Tech Interface (LTI). It is possible for a SOA to
interface with a SP's order entry system, number inventory system(s), and
customer account database(s). In addition, the SOA can include the
functionality of a database for retention of information sent to and
received from the NPAC, as well as generate reports. It is also possible
to have the SOA automatically respond to notifications from the NPAC. SOA
applications are used by SPs expecting medium to high porting activity. |
Porting activation timeframes are
anticipated to be between 2.5 hours to 4 business days depending on whether
the port is wireless to wireless or wireline to wireless.
|
