IP Library Granted Patent US 8,265,258
Granted Patent B2
US 8,265,258 · App. 11/929,336 · Granted Sep 11, 2012

Functionalities for local number portability in a telecommunications network

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,265,258
App. No.
11/929,336
Granted
Sep 11, 2012
Kind
B2
Abstract

According to various embodiments of the present invention, systems and methods for local number portability in a telecommunication network are disclosed. An embodiment of a method includes submitting a local number portability (LNP) order for the TN directly to a first telecommunications carrier that the TN is to be transferred from, triggering a port of the TN in accordance with the LNP order, and porting the TN from the first telecommunications carrier to the second telecommunications carrier, wherein the second telecommunications carrier is bypassed by the customer during the submitting and the triggering of the LNP order. Other embodiments are also disclosed.

Claims (38)

1. A method comprising:

providing a computer-based portal;

submitting via the computer-based portal, by a customer that owns a telephone number (TN), a local number portability (LNP) order for the TN directly to a first telecommunications carrier that the TN is to be transferred from, wherein the customer utilizes a business to business application programming interface (B2B API) to submit the LNP order directly to the first telecommunications carrier;

triggering, by the customer that owns the TN, a port of the TN in accordance with the LNP order; and

porting, by a second telecommunications carrier that will service the TN after the LNP of the TN, the TN from the first telecommunications carrier to the second telecommunications carrier,

wherein the second telecommunications carrier is bypassed by the customer during the submitting and the triggering of the LNP order, and wherein the second telecommunications carrier handles activities of updating at least one of customer name database (CNAM) and number portability administration center (NPAC), and wherein the second telecommunications carrier handles any errors associated with the updating at least one of CNAM and NPAC activities.

2. The method of claim 1 , wherein the customer manages activities including at least one of customer service records, local service requests, firm order commitments, and directory listing.

3. The method of claim 2 , wherein the customer manages any errors associated with the at least one of customer service records, local service requests, firm order commitments, and directory listing activities.

4. The method of claim 1 , wherein submitting the LNP order further comprises the customer:

determining service availability from the second telecommunications carrier;

requesting a customer service record from the first telecommunications carrier;

requesting a local service request from the first telecommunications carrier; and

obtaining a firm order committing date for the LNP order from the first telecommunications carrier.

5. A system, comprising:

a customer that owns a telephone number (TN), the customer enabled to:

submit via a computer-based portal a local number portability (LNP) order for the TN directly to a first telecommunications carrier that the TN is to be transferred from, wherein the customer utilizes a business to business application programming interface (B2B API) to submit the LNP order directly to the first telecommunications carrier;

trigger a port of the TN in accordance with the LNP order; and

a core telecommunications carrier that will service the TN after the LNP of the TN, the core telecommunications carrier to port the TN from the first telecommunications carrier to the second telecommunications carrier,

wherein the second telecommunications carrier is bypassed by the customer during the submitting and the triggering of the LNP order, and wherein the second telecommunications carrier handles activities of updating at least one of customer name database (CNAM) and number portability administration center (NPAC), and wherein the second telecommunications carrier handles any errors associated with the updating at least one of CNAM and NPAC activities.

6. The system of claim 5 , wherein the customer manages activities including at least one of customer service records, local service requests, firm order commitments, and directory listing.

7. The system of claim 6 , wherein the customer manages any errors associated with the at least one of customer service records, local service requests, firm order commitments, and directory listing activities.

8. The system of claim 5 , wherein submitting the LNP order further comprises the customer:

determining service availability from the second telecommunications carrier;

requesting a customer service record from the first telecommunications carrier;

requesting a local service request from the first telecommunications carrier; and

obtaining a firm order committing date for the LNP order from the first telecommunications carrier.

9. An article of manufacture, comprising:

a non-transitory computer-accessible medium including data that, when accessed by a computer, causes the computer to perform operations comprising:

receiving information via a portal from a customer who owns a TN associated with a local number portability (LNP) order submitted the LNP order directly to a losing telecommunications carrier and triggered a port of the TN, the LNP order to transfer servicing of the TN from the losing telecommunications carrier, wherein the customer utilizes a business to business application programming interface (B2B API) to submit the LNP order directly to the losing telecommunications carrier;

porting the TN associated with then LNP order from the losing telecommunications carrier,

wherein the customer bypasses the losing telecommunications carrier during the submitting and the triggering of the LNP order, and wherein the telecommunications carrier that is to receive the TN handles activities including at least one of customer name database (CNAM) and number portability administration center (NPAC), and handles any errors associated with the at least one of CNAM and NPAC activities.

10. The article of manufacture of claim 9 , wherein the customer manages activities including at least one of customer service records, local service requests, firm order commitments, and directory listing.

11. The article of manufacture of claim 10 , wherein the customer manages any errors associated with the at least one of customer service records, local service requests, firm order commitments, and directory listing activities.

12. The article of manufacture of claim 9 , wherein the customer submitting the LNP order further includes the customer to:

determine service availability from the telecommunications carrier that is to receive the TN;

request a customer service record from the losing telecommunications carrier;

request a local service request from the losing telecommunications carrier; and

obtain a firm order committing date for the LNP order from the losing telecommunications carrier.

Assignments (3)
NOTICE OF GRANT OF SECURITY INTEREST IN INTELLECTUAL PROPERTY (SECOND LIEN) Recorded Nov 4, 2024
From: LEVEL 3 COMMUNICATIONS, LLC; GLOBAL CROSSING TELECOMMUNICATIONS, INC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 069295/0749 →
NOTICE OF GRANT OF SECURITY INTEREST IN INTELLECTUAL PROPERTY (FIRST LIEN) Recorded Nov 4, 2024
From: LEVEL 3 COMMUNICATIONS, LLC; GLOBAL CROSSING TELECOMMUNICATIONS, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 069295/0858 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 27, 2008
From: BROWN, GREGORY K.; CARLSON, JAMES; FARNON, MARIA; LAND, GREG A.; LONG, BILL; LYNETTE, TROY D.; MOORE, RICHARD D.
To: LEVEL 3 COMMUNICATIONS, LLC
Reel/Frame 020712/0003 →