|
1.
I have heard references made to differing software in the Number
Portability Administration Center (NPAC) system. What software release
is required to start pooling?
CIS can perform the pooling administration function with NPAC Release
1.4, 2.0, or 3.0. Currently Release 2.0 (which has Release 1.4 capability)
is available throughout the U.S. However, as of November 1, 1999,
only the Mid-West Regional LLC has paid the licensing fee and activated
Release 1.4 to support the Illinois pooling trial. Other LLCs that
want to use the Release 1.4 pooling functionality found in Release
2.0 would have to agree to turn on that feature in the NPAC. Some
Service Providers will also need to undergo NPAC interface testing
before Release 1.4 functionally can be used for pooling.
NPAC
Release 3.0 also supports number pooling and contains the ability
to assign a block of numbers to a service provider in one transaction
process in the NPAC. This capability meets national industry standards
identified by the NANC's LNPA WG (known as the national pooling
NPAC release). Release 3.0 will be available to begin service provider
testing on 6/30/99. This interface testing for Release 3.0 is expected
to last 4 - 6 months. As of November 1, 1999, the Mid-Atlantic,
Southwestern, Southeastern, Western and West Coast LLCs have ordered
Release 3.0.
2. What is the difference between NPAC Release
1.4 or 2.0 and software Release 3.0?
Release 3.0 provides all of the standard national number pooling
functionality required by the NANC LNPA Working Group and industry
technical standards bodies. Release 1.4 was a customized release
designed for the Midwest LLC's use. The initial purpose of Release
1.4 was in support of a number pooling test in the Illinois trial.
The critical difference between the two releases is the inclusion
of Efficient Data Representation (EDR) in Release 3.0 which permits
downloading and storage in an SP's database 1,000 numbers "as a
single record" instead of 1,000 records. This capability, only available
in Release 3.0, was developed to resolve LNP database capacity issues
associated with widespread telephone number pooling deployment.
For this reason, it is considered to be a critical requirement by
many service providers.
CIS,
as the NPAC provider, is prepared to support pooling under software
Release 2.0 (which contains the Release 1.4 pooling functionality,
but requires turn up authorization from other LLCs). Release 2.0
contains only a small percentage of the national telephone number
pooling requirements. Due to carriers database capacity concerns,
carriers see the need for NPAC records created using Release 1.4
to undergo an additional step of record migration (from Release
1.4) to the national uniform industry pooling Release 3.0. The customer
and administrative impacts from this record migration are currently
unknown.
3. Have issues been raised about service provider
LNP database capacity?
Certain service providers have identified an LNP database limitation
constraining the quantity of records that can be stored in their
databases. Questions concerning service provider LNP database capacity
should be directed to Service Providers.
As
stated above, the "EDR" capability in Release 3.0 was developed
to overcome service provider LNP database capacity constraints.
Using NPA 847 as an example, there have been approximately 250,000
numbers ported due to pooling since the trial started in June of
1998. This equates to 250,000 records in each service provider's
LNP databases. With NPAC Release 3.0, service providers that require
or will use this capability could potentially reduce this quantity
to few as 250 records - a reduction in storage needs by a factor
of 1000.
4. Have other issues been raised?
Yes, some industry members have identified the need for modifications
to national systems (Telcordia National Routing Database) and individual
service provider's may require modifications to Operations Support
Systems (e.g., telephone number assignment, billing, maintenance,
provisioning) to accommodate the requirements of telephone number
pooling.
Additionally,
there are LNP database download issues, which may affect block allocation
to Service Providers, and subsequently, activation of customer telephone
number assignments. Requirements that describe the procedure to
migrate records from Release 1.4 to Release 3.0 need to be developed.
Numerous
Service Providers have indicated that their current OSSs rely on
the association of an NPA-NXX with one specific Service Provider
end office. These Service Providers may require significant OSS
enhancements to support the administration, provisioning, billing,
and maintenance of thousand blocks.
5.
How did the Service Providers in Illinois and New York get around
these obstacles?
Each
Service Provider may have a different system and method of operating
and they would have to individually answer this question. As for
the LNP download concern, CIS, in conjunction with the industry,
has modified the NPAC download schedule and put NPAC personnel on
notice to monitor LNP downloads to reduce issues with data acceptance
and ensure service providers' systems are online.
6.
What date should be used as the most realistic date for National
Pooling to begin?
The
most realistic date to expect national pooling administration and
pooling software to be implemented depend on when a national regulatory
order is released and service provider testing is completed. If
an order is released by March 2000, the pooling administration system
will be ready within 7-9 months. NPAC software Release 3.0 will
be released for testing by service providers in July 2000.
Service provider/NPAC testing is scheduled to begin completion in
October 2000. The industry is currently reviewing this test plan.
Individual
service provider implementation constraints vary and it is suggested
interested parties review the NANC's Numbering Resource Optimization
(NRO) Report to the FCC to get a full understanding of some of the
work effort and resources necessary to implement thousand block
number pooling.
back
to top
|