Functionalities for local number portability in a telecommunications network
View Patent ↗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.
1. A method comprising:
providing a computer-based portal;
receiving via the computer-based portal, from a customer that owns a telephone number (TN), a local number portability (LNP) order for the TN, wherein the customer utilizes a business to business application programming interface (B2B API) to submit the LNP order;
triggering a port of the TN in accordance with the LNP order; and
porting the TN from a first telecommunications carrier to a second telecommunications carrier, wherein the first telecommunications carrier handles activities of updating at least one of customer name database (CNAM) and number portability administration center (NPAC), and wherein the first 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, wherein the customer utilizes a business to business application programming interface (B2B API) to submit the LNP order directly to the first telecommunications carrier; and
trigger a port of the TN in accordance with the LNP order from a first core telecommunications carrier to a second core telecommunications carrier, wherein the second core telecommunications carrier that will service the TN after the LNP of the TN handles activities of updating at least one of customer name database (CNAM) and number portability administration center (NPAC), and wherein the second core 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 is enabled to manage 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 is enabled to manage 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 the customer is further enabled to manage:
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, wherein the customer utilizes a business to business application programming interface (B2B API) to submit the LNP order directly to the losing telecommunications carrier; and
porting the TN associated with then LNP order from a first telecommunications carrier, and wherein the first 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.