Transcript Document

Number Portability Administration Center
Change Orders NANC 399 & NANC 400
NANC Meeting
March 15, 2005
Tom McGarry
NeuStar, Inc.
[email protected]
1
NPAC: Vital Role within Industry

Centralized master (authoritative) provisioning system for ported and pooled
telephone numbers (TNs), regardless of underlying network technology employed
(wireline, wireless, cable, IP)

Service providers provision NPAC with routing data for ported and pooled TNs via
the Service Order Administration (SOA) Interface and via a web-based graphical
user interface (GUI)

Current routing information for ported and pooled TNs includes:
–
–
Location Routing Number (LRN) – terminating PSTN switch identification
DPC/SSN - SS7 routing information for the following services:
•
•
•
•
•
CLASS - enhanced services such as incoming call screening and missed-call return (*69)
LIDB - Line Information Database for enhanced services
CNAM – Enhanced Caller ID – calling name display
ISVM - enhanced services for voice mail
SMS - text messaging for cell phones
2
NPAC: Vital Role within Industry Cont’d

NPAC broadcasts routing and administrative data to all NPAC LSMS users
simultaneously upon record activation

NPAC ensures that routing information is current and in sync, and that NANC
business processes have been followed prior to accepting any provisioning
changes for activation

Law Enforcement and Public Safety agencies depend on NPAC IVR to
determine facilities-based carrier for surveillance purposes and emergency
assistance

NPAC is used to generate lists (TNs that have been ported from wireline to
wireless and vice versa) for telemarketers to comply with Telephone Consumer
Protection Act (TCPA)
3
NANC 399: Description
•
Currently in the NPAC:
– Wireline and wireless service is designated at the service provider level not at the TN
level
– There is no ability to designate alternate service provider arrangements such as
reseller and Mobile Virtual Network Operator (MVNO)
•
NANC 399 adds two data fields to each ported & pooled TN record:
– A Service Type
• Can be wireline, wireless, VoWiFi, or VoIP; more could be added later
– An Alternate SPID, for example:
• Can indicate the reseller
• Can indicate the MVNO
• Can indicate the serving VoIP provider which uses a facilities-based carrier to receive its
PSTN-routed traffic
•
NANC 399 does not change any business rules
4
NANC 399: Applications
Network Routing
•
Allows for service providers to directly determine the proper Service Type
during call processing
Billing
•
Allows the billing records to show the correct service provider and service
type
Administrative Use
•
•
PSAP access to alternate service provider information
CALEA access to alternate service provider information
Porting Process
• Allows identification of any reseller associated with a ported/pooled TN
5
NANC 400: Description
•
NANC 400 adds four new fields to each ported & pooled TN record
– Analogous to existing LRN & DPC/SSN routing information in NPAC
•
Does not change any business processes
– New routing fields would be broadcast alongside existing fields
– No behavior, process, or timer changes
•
These new fields contain IP routing information to ensure correct operation of
service features offered by carriers today, associated with ported/pooled TNs
•
New fields are motivated by the deployment of new service provider features and
supporting network infrastructure
•
The proposed new fields are Universal Resource Indicators (URIs):
–
–
–
–
Multimedia Message Service (MMS) URI
Voice gateway URI
Push-to-talk Over Cellular (POC) URI
Presence server URI
6
NANC 400: Applications
• Multimedia Messaging Service (MMS)
– MMS is a wireless service for sending and receiving multimedia
messages, such as pictures
– MMS service is provided via an Internet Protocol (IP) network within
and between the wireless carrier’s networks
– IP networks use Internet addresses (URIs) for routing
• MMS controllers (MMSCs) uses an MMS URI for routing
– Carriers today use the SPID field in the NPAC to “approximate” the
MMS URI for ported and pooled TNs
• This solution is not likely to be able to support future growth and
configurations such as multiple MMSCs and MVNO architecture
– NANC 400 allows wireless carrier to provision the MMS URI for ported
and pooled TNs, ensuring the integrity of routing and addressing
• No longer need to “approximate” routing information from SPID
7
NANC 400: Applications Cont’d
• Voice over IP
–
–
–
–
Service providers are porting VoIP enabled TNs today
Service providers are acquiring pooled TNs for enabling VoIP service today
VoIP routing works very much like MMS routing
The VoIP URI field can be used to designate the VoIP gateway address for
a ported/pooled number
– Allows for the ability to synchronize PSTN and VoIP addressing updates for
ported and pooled TNs
• Push to Talk Over Cellular (PoC) and Presence
– Like MMS and VoIP, both of these applications require mapping a TN to a
URI for ported & pooled TNs
8
NANC 399 & NANC 400: Technical Implementation
•
Both change orders are fully backward-compatible:
–
•
Both change orders are optional on a SP by SP basis:
–
–
•
•
No requirement that a SP and/or vendor take any action to accommodate either change
order; their systems do not have to be changed at all unless they want to support the fields;
this is similar to the way pooling EDR was implemented
Election by one service provider does not impact another
Use of the NANC 400 is optional at the field level, so even if a service provider elects to use
the change order, population/receipt of data for each of the fields can be elected individually
Even if a SP elects to participate in the change orders, there is no
requirement that any new data field actually be populated or that any of the
new data fields received actually be used.
Implemented using embedded XML over the existing NPAC SMS CMIP
interfaces
–
–
XML is an established and well understood protocol used by carriers and vendors that
participate in the LNPA
The extensible nature of XML means it is flexible and can be easily modified
9
NANC 399 & NANC 400: Summary
• The change orders:
– Add 6 fields to existing ported and pooled TN records
– Do not require any business rule changes in the NPAC
– Are fully backwards-compatible
– Are optional by field, system, and service provider
– Have completed their technical review at the LNPA WG
10
Glossary
•CALEA - Communications Assistance for Law Enforcement Act
•CLASS - customer local area signaling services
•CMIP - common management information protocol
•CNAM - calling name
•DPC - destination point code
•EDR - efficient data representation
•GUI - graphical user interface
•IP - Internet protocol
•ISVM - inter-switch voice messaging
•IVR - interactive voice response
•LIDB - line identification database
•LNPA WG - local number portability working group
•LRN - location routing number
•MMS - multimedia service
•MMSC - multimedia service controller
•MVNO - mobile virtual network operator
•NANC - North American Numbering Council
•NPAC - number portability administration center
•OCN - operating company number
•PoC - push-to-talk over cellular
•PSTN - public switched telephone network
•SMS - short message service
•SOA - service order administration
•SP - service provider
•SPID - service provider identification
•SS7 - signaling system 7
•SSN - sub-system number
•TCPA - Telephone Consumer Protection Act
•TN - telephone number
•URI - uniform resource identifier
•VoIP - voice over Internet protocol
•VoWiFi - voice over WiFi
•XML - eXtensible markup language
11
Appendix : Example of how NANC 400
Works
Routing for MMS Messages
•Since MMS is IP and customers input a TN, the TN is
translated to an Internet address - a URI
•The TN 202-233-1234 is mapped to the URI
MMS:[email protected]
12
Appendix : Example of how NANC 400
Works
MMS Provisioning for Ported and Pooled TNs
•Service providers use the SPID in the TN record to
“approximate” the URI, e.g., this SPID always = this URI
13
Appendix : Example of how NANC 400
Works
MMS Provisioning with NANC 400
•With NANC 400 the service providers can
provision the URI with the TN record
•No need to “approximate” TN-URI relationship
14