LOCAL ROUTING MANAGEMENT IN A TELECOMMUNICATIONS NETWORK

• US 20090074173A1
• Filed: 05/30/2008
• Published: 03/19/2009
• Est. Priority Date: 05/31/2007
• Status: Active Grant

• Current Assignee: Level 3 Communications LLC (Lumen Technologies, Inc.)
• Original Assignee: Level 3 Communications LLC (Lumen Technologies, Inc.)
• Inventors: Jordan, Dan, Gualtieri, Greg, Terpstra, Richard, Davis, Matthew K., Saha, Susmita G., Nair, Murli S., Griffin, Janis
• Granted Patent: US 7,738,647 B2
• Time in Patent Office: Days
• US Class Current: 379/221.130
• CPC Class Codes: H04Q 2213/13138 Least cost routing, LCR
• CPC Class Codes: H04Q 2213/13141 Hunting for free outlet, circuit or channel
• CPC Class Codes: H04Q 2213/13349 Network management
• CPC Class Codes: H04Q 2213/13353 Routing table, map memory
• CPC Class Codes: H04Q 3/66 Traffic distributors

Abstract

An embodiment of a method includes generating one or more route plans, each route plan being associated with a service plan, and provisioning the one or more route plans on a core routing engine accessible by a softswitch for routing calls according to the one or more route plans. The one or more route plans may include an on-net route plan and an off-net route plan. An embodiment of a system includes a local route manager (LRM) configured to generate one or more route plans associated with one or more respective service levels that customers can subscribe to. The system may further include an inventory of trunk groups containing a plurality of trunk group identifiers (IDs), wherein trunk group IDs are marked as either on-net or off-net.

Claims

1. A method comprising:

generating one or more route plans, each route plan being associated with a service plan; and

provisioning the one or more route plans on a core routing engine accessible by a softswitch for routing calls according to the one or more route plans.

2. The method of claim 1 wherein the one or more route plans comprise an on-net route plan and an off-net route plan.

3. The method of claim 1 wherein generating a route plan comprises:

selecting a trunk group ID from a trunk group inventory, the TGID identifying a trunk group;

associating the trunk group ID with a plurality of local calling area numbers associated with end-office switches connected to the trunk group; and

inserting the TGID in a route plan useable to route calls to the local calling area.

4. The method of claim 3, further comprising determining the plurality of local calling area numbers, wherein determining the plurality of local calling area number comprises:

identifying a tandem switch associated with the selected TGID;

identifying one or more end-office switches associated with the tandem switch; and

identifying local calling area numbers associated with the one or more end-office switches.

5. The method of claim 4 wherein identifying the tandem switch, the one or more end-office switches and the local calling area numbers comprises performing a look-up in a local exchange routing guide (LERG).

6. The method of claim 1 wherein provisioning each of the one or more route plans comprises storing each route plan in a partition associated with the service plan.

7. The method of claim 1 wherein each of the one or more route plans comprises a list of TGIDs identifying trunk groups for use in terminating calls.

8. The method of claim 7 wherein the TGIDs are prioritized in the list.

9. The method of claim 7 wherein the route plan includes one or more of a transit path, a feature group D (FGD) path, or a co-carrier path.

10. A system comprising:

a local route manager (LRM) configured to generate one or more route plans associated with one or more respective service levels that customers can subscribe to.

11. The system of claim 10 further comprising:

an inventory of trunk groups containing a plurality of trunk group identifiers (IDs), wherein trunk group IDs are marked as either on-net or off-net.

12. The system of claim 11 wherein the LRM generates the one or more route plans by selecting one of the TGIDs of the TG inventory, determining all local calling area numbers that the identified TG can terminate calls to, and associating all the LCA numbers with the selected TGID.

13. The system of claim 11 further comprising a preferred least cost routes database storing off-net least cost carriers in prioritized order of preference.

14. The system of claim 13 wherein groups of the preferred least cost carriers are stored in association with respective LATA-OCNs, wherein a LATA-OCN designates an operating carrier number identifying a carrier associated with a given local access and transport area (LATA).

15. The system of claim 14 wherein the LRM generates off-net route plans by selecting one or more off-net TGIDs from a trunk group inventory based on one or more preferred off-net least cost carriers.

16. The system of claim 15 wherein the LRM further generates off-net route plans by identifying the one or more preferred off-net least cost carrier for a given LATA-OCN.

17. The system of claim 16 wherein identifying the one or more preferred off-net least cost carriers comprises indexing the data store by selected LATA-OCNs to look up the one or more preferred off-net least cost carrier in the data store.