1 / 8

Wireless Local Number Portability and Roaming

Wireless Local Number Portability and Roaming. June 23, 2005 Lynette Rainey. Outline. WLNP Mandate and Who Is Required To Port MIN Separation CIBER Impacts and Billing Issues. WLNP Defined. Porting is an FCC Mandate, and per the Telecommunications Act of 1996, Wireless LNP is defined as:

dacian
Télécharger la présentation

Wireless Local Number Portability and Roaming

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Wireless Local Number Portability and Roaming June 23, 2005 Lynette Rainey

  2. Outline • WLNP Mandate and Who Is Required To Port • MIN Separation • CIBER Impacts and Billing Issues

  3. WLNP Defined Porting is an FCC Mandate, and per the Telecommunications Act of 1996, Wireless LNP is defined as: “ . . . . the ability of users of telecommunications services to retain, at the same location, existing telecommunications numbers without impairment of quality, reliability, or convenience when switching from one telecommunications carrier to another.”

  4. Who is required to port? • Carriers who operate in any of the top 100 MSAs are required to comply with the FCC mandate. Carriers outside of the top 100 MSAs must comply within 6 months of receiving a bona fide request to port. • There are 72+ wireless carriers and 250+ wireline carriers represented in the top 100 MSAs that Sprint PCS must interact with. • Beginning May 2004, customers in areas outside the 100 largest MSAs will also be able to experience the benefits of WLNP. Wireless carriers serving areas outside of the 100 largest markets must be capable of porting by May 24, 2004, or six months after they first receive a request to port. • Since November 24, 2003, more than 8.5 million consumers have taken advantage of WLNP. 10% of those, “cut the cord” and moved a landline number to a wireless phone.

  5. (Mobile Identification Number) + Customer’s Dialable Number + Provisioning + Handset Programming + Registration + Network Routing + Customer Service + Billing/Invoicing MIN MIN MDN MSID (Mobile Directory Number) + Customer’s Dialable Number + Portable Number + Provisioning + Handset Programming + Network Routing + Mobile Station Display + Caller ID + Billing/Invoicing + Customer Service + Tied to Wireline Rate Center MDN - How Used MSID - How Used (Mobile Station Identifier) + Initially copied from MIN + Not Dialable + Not Portable + Registration on Network + Provisioning + Handset Programming + Identifies Wireless Service Provider + Settlement by BID + Troubleshooting + Not geographic (as defined by industry) Reference Documents: + CTIA Report on Wireless Number Portability Version 2.0 + Wireless Number Portability Subcommittee - Wireless Number Portability Technical, Operational and Implementation Requirements (Version 1.6) MIN Separation

  6. MIN Separation Further Defined • To support Number Pooling and Portability in the wireless space, mobile stations must possess two types of identification numbers: a Mobile Directory Number (MDN) and a Mobile Station Identifier (MSID). • Mobile Directory Number - The MDN is a dialable NANP directory number, in the 10-digit NANP format (NPA-NXX-XXXX), and may be pooled and/or ported. • Mobile Station Identifier - The MSID can be either a 15-digit International Mobile Station Identifier (IMSI) or a 10-digit NANP-like Mobile Identification Number (MIN), and can not be ported - it is controlled by the wireless service provider. • MSID and MIN are often used interchangeably in industry documentation, MIN being the 10-digit format of the MSID.

  7. Impacts to the CIBER Record • CIBER format modified to capture additional WLNP fields. • X2 record types. • MSID, MDN, LRN, others. • CIBER 10 & 20 – MSID should be populated in the record • CIBER 22 – MDN & MSID should be populated in the record. • Both the MDN and MSID values are used for end-user usage routing/guiding processes.

  8. Impacts to Billing • Clearinghouse MSID/BID edit • CIBER 10/20 • Unbillable usage • Records error in mediation system if a valid MSID/MDN combination is not present. • Risk to invoice incorrect subscriber for roaming usage • Manual work around necessary requiring maintenance.

More Related