||Local Number Portability
||May 022 1997
||May 28, 1997
Review Meeting Title: LNP National Billing
Meeting Date: May 22, 1997 Next Meeting Date:
June 17, 18, 19 in San Ramon
Next Meeting will be held in San Ramon. June
17, 18, 19.
vendors to distribution and invitation list
directions to San Ramon complex to forum members
members to investigate if they have any special
terminating arrangements which require intercompany
settlements or agreements.
members to investigate their EAS, Zone Pricing
compensation arrangements between themselves and other
members to investigate any cross boundary situations in
which one rate center crosses a state boundary.
attached list of forum members. Highlighted names
participated on call.
All names on forum list.
Record significant Topics, Presenters,
- Jill Blakeley chaired this meeting and
opened with a request from the forum to add any issues
not covered by the Ca. Delta Document. The following 6
issues were added:
- EMS Services - Item #8 on Delta
- LRN assignment
- LRN use for rating
- Item #1 on the Delta
Doc. Is there a need for additional escape
criteria? What will happen if carriers cant
do query? What are the implications?
- Item #4/9 on Delta Doc.
Interim alternatives may be required since
vendors may not have this functionality ready at
the onset of local number portability.
- Use of LRN to determine
- Discussion followed around EMS and the LRN
scenarios. The other items were tabled for discussion at
the June 17, 18, 19 working session.
1. EMS Services
- After much lively discussion the
following points were noted:
- This is a
compensation issue between
impacts end user billing service
agreements will need to handle
this compensation issue
forum member is to go back to
their respective companies to see
if they have special terminating
arrangements that require special
pricing will also cause the same
type of problem as EMS. Wire
center V&Hs are needed
for end user billing. In some
areas each wire center has its
own mileage bands.
procedures will need to be
center to wire center ratings may
have to be looked at.
2. LRN for Assignment purposes
- Some companies have discussed the
possible use of a LRN per switch/per rate center.
The group discussed whether the CLC must have an
NPA NXX per rate center. If they have a switch
that serves two rate centers, do they need two
NPA NXXs or one? The team agreed that they will
need 2 if they will be assigning new customers in
both NPA NXXs. Otherwise, the forum members
determined that the CLC needed only one. The CLC
needs only one LRN for routing purposes
- Some CLCs may not want to
open a new code on a given switch (to be used as
LRN), when they only want to serve ported in
numbers. This is also a number exhaust issue.
- The Canada "PUC" has
mandated that each local service provider must
open 1 NPA/NXX for each LEC/ILEC exchange area
(a.k.a. rate center).
- Chicago is discussing a number
assignment change where they would assign 1000
bank numbers to CLCs by marking them as
ported to that company. This would be a way to
deal with the number exhaust issue on an interim
- We will be using zeroes in the
last 4 digits of an LRN. This could be an
assignable number. When we go to 10 digit
routing, this can be an issue if the number is
assigned and is used for the LRN. Companies do
not want to have to open up the call to check the
ported number GAP to determine if the called
number is an LRN or a DN. Some companies do plan
to assign LRNs as working TNs too,
others do not.
- It would be an administrative
nightmare to try to keep track of which
LRNs are also working TNs.
- How will LRN NPA NXXs be assigned?
This is an item that requires further discussion.
- For AIN services such as Calling
Party Pays, the network may need to recognize LRN
to make it work. Companies do not want to have to
open up the call to check the ported number GAP.
3. LRN used for Rating purposes
- LRN should not be used for rating with
SPLNP, since it will not necessarily translate to the
correct rate center. Not all companies agree on this.
- Stentor asked whether it should be a
mandatory requirement to assign an LRN per rate center.
Sarathy would like feedback on this issue.
- Note that Lucent and Nortel have indicated
that they will only pass the home LRN of the switch on
calls originating from a ported number. A switch vendor
change would be required to derive LRN by rate center.
- For Access Billing, companies must
continue to exclude Wireless NPA prefixes and Independent
Company NPA prefixes from the application of Carrier
Common line charges. Wireless NPA prefixes are not
affected by LNP. However, using NPA prefix for
independent company traffic is not sufficient in an LNP
- Another issue was raised about whether
more than one LRN is required if you have separate trunks
for EAS vs. Toll. Is this a SPLNP issue or a Location
issue? With consistent rate centers, analysis of the
called NPA/NXX should determine the type of call and
therefor the proper trunk. Is LRN being used to select
trunks in some companies? Why?
4. Delta Item Number 1 - Need for additional
5. Delta Item Numbers 4 & 9 - Need to discuss interim
alternatives. Vendors may not be ready.
6. LRN for Taxing Purposes
- Companies should investigate any cross
boundary situations in which one rate center crosses a
state boundary. A companies position may be that when a
customer crosses a state boundary, number portability is
not allowed, but the CLC may allow this type of porting.
- Canada has a situation where a rate center
crosses provinces. Today, customers are required to take
a number change if they move across province boundaries.
In Canada, they will allow full porting within the rate
center (vs. limiting it to wire center or existing
rules), so they will have a problem trying to determine
how to apply taxes. Today, the province id is determined
based on NPA/NXX. This will not work with LNP.
- Another lively discussion ensued about
whether you have to stay in place with SPLNP, whether you
can move within wire center boundaries, or have full
movement across the rate center.
- New entrants will not want to open an
NPA/NXX per existing LEC wire center boundaries.
- Another question was can you port your
number if you move across state boundaries if a rate
center includes more than one state.
- Team agreed this topic needed further
- June 17, 18, 19th logistics
- June 17, 1997 - Room-Willow Room
- June 18, 1997 - Room -
Class Room 5 (2N750A)
June 19, 1997 - Room - Oleander Room
- Meet Me Line: 800-828-4058
Participant Code 226681 is the same for all 3
- Hotels in close proximity to the San Ramon
- San Ramon Marriott - 510-867-9200
(Directly across the street from the PB building)
- San Ramon Residence Inn
- 510-277-9292 (Within 3 blocks of the PB
- Pleasanton Hilton -
510-463-8000 (Less than 10 miles and you would be
going against commute traffic)
- Let Marie know if you plan on attending
the working session by June 10th .
1. List of call participants
2. Map of Pacific Bells San Ramon complex
with room information
3. Regional and Site Map
4. Directions to PB center in San Ramon from
the San Francisco or Oakland airports.