BRIEF DESCRIPTION OF DRAWINGS
FIG. 1 is a schematic diagram of a network switch relationship from the end office perspective of a particular geographic region a portion in accordance with the principles of the present invention.
FIG. 2 is a schematic diagram of some components of a tandem management system in accordance with the principles of the present invention.
FIG. 3 is a block diagram illustrating the basic software modules of the tandem manager of the tandem management system shown in FIG. 2.
FIG. 4 is an illustration or screenshot of a GUI of the tandem manager shown in FIG. 3.
FIG. 5 is a block diagram illustrating the main functional components of the Customer Management Module.
FIG. 6 is an illustration or screenshot of a GUI for the Main Customer Screen with the Codes Owned Tab selected.
FIG. 7 is an illustration or screenshot of a GUI for the Main Customer Screen with the Routing Matrix Tab selected.
FIG. 8 is an illustration or screenshot of a GUI for the Manage Codes function.
FIG. 9 is an illustration or screenshot of a GUI for the Carrier Add function.
FIG. 10 is an illustration or screenshot of a GUI for an ASR data screen with the Main ASR Data Tab selected.
FIG. 11 is an illustration or screenshot of a GUI for an ASR data screen with the Contact Info Tab selected.
FIG. 12 is an illustration of a typical ASR form.
FIG. 13 is an illustration or screenshot of a GUI for the Main Customer Screen with the Trunk Groups Tab selected.
FIGS. 14-17 are respective illustrations or screenshots of GUIs for the invoice functionality of the tandem manager.
FIGS. 18-19 are respective illustrations of sample customer invoices/reports.
FIGS. 20-21 are respective illustrations of sample switch activity reports.
DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
The description that follows describes, illustrates and exemplifies one or more particular embodiments of the present invention in accordance with its principles. This description is not provided to limit the invention to the embodiments described herein, but rather to explain and teach the principles of the invention in such a way to enable one of ordinary skill in the art to understand these principles and, with that understanding, be able to apply them to practice not only the embodiments described herein, but other embodiments that may come to mind in accordance with these principles. The scope of the present invention is intended to cover all such embodiments that may fall within the scope of the appended claims, either literally or under the doctrine of equivalents.
It should be noted that in the description and drawings, like or substantially similar elements may be labeled with the same reference numerals. However, sometimes these elements may, but not always, be labeled with differing numbers in cases where such labeling may facilitate a more clear description. Additionally, the drawings set forth herein are not necessarily drawn to scale, and in some instances proportions may have been exaggerated to more clearly depict certain features.
Various aspects of the present invention are born out of concepts of information management associated with one or more switches, such as a tandem switch. Management of this information allows an entity or group to accomplish many things, including, but not limited to: (1) auditing of traffic activity on one or more particular switches; (2) control, routing, and transfer of traffic from exhausted tandem switches to under-utilized tandem switches to increase traffic efficiency; (3) control of traffic for defined members or subscribers of a group, such as a group of CLEC and wireless carrier customers; and (4) routing of subscriber traffic flow through subscriber-owned switches, or a third-party-tandem-manager-owned switch, as opposed to switches owned by a particular LEC or non-subscriber entity to effectuate cost savings and switching efficiency.
According to a particular aspect of the present invention, information management associated with one or more tandem switches gives rise to a business model for providing preferred rates, or other preferences, to a defined group of members or subscribers associated with tandem switch usage by managing and directing subscriber-associated call traffic from subscriber-owned switches to one or more tandem switches owned by a third-party tandem managing entity other than a LEC or ILEC (hereinafter referred to as a tandem manager, third-party tandem manager or third-party tandem service provider). In a preferred embodiment, the subscriber group is made up of CLECs and wireless carriers that operate and/or own one or more end office switches within the PSTN. Members benefit from utilizing one or more access tandem switches owned and/or operated by a third party tandem manager by avoiding higher fees typically associated with LEC-owned and operated access tandem switches. The third-party tandem manager benefits by collecting a usage fee which is less than the LEC fees charged for LEC-owned tandem switches.
The tandem manager provides a tandem access hub to which subscriber carriers can connect to, and have calls originating within the subscriber carrier's network distributed to, the proper switches as needed to complete the calls to their respective destination points. Carriers that subscribe to the tandem manager service not only benefit from lower fees (such as toll fees) associated with calls originating within their own networks, but also lower fees associated with calls to numbers owned by them that are placed within other subscriber carrier networks.
To orchestrate management of call traffic for the subscribers such that it is properly connected and distributed via the tandem manager tandem access hub or switch, the tandem manager utilizes methods to coordinate, audit, organize and manage subscriber number and switch information. In a preferred embodiment, the primary subscriber data or information relied upon are NPA-NXX codes for all subscriber-owned numbers. The “NPA-NXX” code represents the first 6 digits of a telephone number, starting with the area code. The “NPA” refers to “Number Plan Area,” commonly known as Area Code. “NXX” is the next finer number indicator within an Area Code and refers to a Central Office (or end office) of the phone service provider. Hence, by utilizing the NPA-NXX code, the tandem manager is able to determine the subscriber that owns the telephone number. The tandem manager keeps track of all NPA-NXX codes owned by subscribers to the system so that it can report these codes to all subscribers of the system and allow each subscriber switch to route all calls with these subscriber codes to the tandem manager tandem access switch. As a result, all participating subscribers will cooperate to direct all subscriber-code calls to the tandem manager tandem access switch, regardless of their point of origin, so that LEC-associated fees and tolls can be avoided. The LERG, or “Local Exchange Routing Guide,” can be utilized to effectuate these relationships. The LERG is a Bellcore document that lists all North American Class 5 offices (Central Offices, or end offices) and describes their relationship to Class 4 offices (Tandem Offices). The LERG can be accessed on a regular basis to identify new/additional NPA-NXX codes and changes associated with subscriber switches so that this information can be utilized in the tandem manager service process.
FIG. 1 schematically illustrates a typical network switch relationship from the end office perspective of a particular geographic region. As shown in FIG. 1, a plurality of end office switches 30 are in networked communication with a set of tandem switches 32, which provide an access hub to the PSTN. The end office tandem switches include a wireless subscriber end office switch 34, a CLEC subscriber end office switch 36, and a non-subscriber end office switch 38. The set of tandem switches 32 include an FE-D LEC tandem 40, a LEC tandem 42, a tandem manager tandem 44, and an IXC tandem 46. The subscriber end office switches 34, 36 communicate with the tandem switches 30 in an order of preference, the first preference being given to the tandem manager tandem 44 by virtue of the subscriber status of the end office switches 34, 36. Each of the end office switches 34, 36 has access to an NPA-NXX table to verify whether a particular number is that of a subscriber. If a particular NPA-NXX is identified on the table, the call is then routed to the tandem manager tandem 44. If not, the call is routed to the LEC tandem 42.
As information relating to subscribers and their network of switches is obtained, organized, managed and updated, it is provided by the tandem manager to each of the switches 34, 36 so that the NPA-NXX table can be updated with the latest subscriber data. As shown schematically in FIG. 2, a tandem manager system 50 comprises a tandem manager 52 and a tandem manager database 54, which stores all data associated with the system, including subscriber switch data, subscriber code data (NPA-NXXs), etc. The tandem manager 52 is also in communication with LERG 56, which provides data relating to routing information. As this data is collected, organized, managed and updated, it can be disseminated to subscribers so that future subscriber call traffic can be directed to the tandem manager tandem 44. The functionality and services provided by the tandem manager 52 are primarily driven by a tandem management system software application. In a preferred embodiment, the tandem management system software application provides GUIs, such as windows-based interfaces, for users to access and manage information. In a preferred embodiment, the software is developed on and Oracle database platform and a Visual Basic user interface platform.
Tandem Management System
In accordance with the principles of the present invention, and as shown in FIG. 3, methods of subscriber information management are preferably implemented through a software-enabled tandem manager system, preferably comprising a main Tandem Manager 102 and several modules, including a Customer Management Module 104, Control/Reference Data Module 106, Management/Operating Reporting Module 108, Custom Table View Module 110, and Other Function Module 112. To access these modules and their underlying functionality, a GUI is provided as shown in FIG. 4. The Tandem Manager 102 and the underlying modules can be used by a tandem manager (i.e., service provider) to manage information and functionality to effectuate the systems, methods, and business models in accordance with the principles of the present invention. Each of these modules will be described in more detail below.
Customer Management Module
As shown in FIG. 5, the Customer Management Module 104 includes access to the main functionality of the system: Main Customer Screen 120, Monthly LERG Reconciliation 122, and Invoice Generation 124.
An example of the Main Customer Screen 120 is shown in FIG. 6. The screen is preferably organized in two sections: a “Customer/Market/Switch Management” section 126 (left half of the screen) and an “Activities and Data Management for a Selected Switch” section 128 (right half of the screen). The screen section 126 is used to first select a customer (subscriber) of the system from a Customer List, then a customer market (preferably defined by a geographic region) from a Customer Market list, and then a switch for that particular customer from a Customer Switch list. Once a particular switch is selected, the information for that switch can be accessed and managed. For example, once a switch is selected, the “Manage Codes Owned” function can be selected to allow management of codes for that particular switch or the “Perform Carrier Add” function can be selected to add subscriber carriers and their associated codes to that switch. The screen section 126 also allows management of customer data. With appropriate privileges, Customers, Customer Markets, and Customer Switches can be created, edited or deleted.
The “Activities and Data Management for a Selected Switch” section 128 of the screen is shown in FIG. 6 divided into multiple tabs: a Codes Owned Tab 130, a Routing Matrix Tab 132, a Trunk Groups Tab 134, and an Invoicing Tab 136. Once a particular switch has been selected in the section 126 of the screen, these tabs allow viewing and editing information for the codes, traffic, trunk groups, or other information relating to the selected switch.
Customers can be added, deleted or edited within the Customer List. Customer data can be entered for a particular customer for use by the system, such as for routing or billing purposes. Customer markets can also be added, deleted or edited within the Customer Market List. Likewise, customer switches can be added, deleted or edited within the Customer Switch List.
As shown in FIG. 6, once a specific switch has been selected in the “Customer/Market/Switch Management” section 126 of the screen, the Code Owned Tab 130 displays the codes owned by that switch (or a Point of Interface (POI) of that switch) listed in a Codes Owned Window 138. Additionally, other information can be displayed, such as information utilized by the tandem manager and the latest LERG information for the selected code in the list. The tandem manager information relating to a specific code can be edited as appropriate. For example, a particular code can be designated as “Do Not Route” to indicate that the code is not routable, the designation of which will prevent a periodic LERG analysis performed by the system from identifying this as a new code that should be added to the system (in which case, it would be routed to the tandem manager tandem 44 contrary to its status as a non-routable code). A particular code may also be designated as “Ignore LERG” to indicate that the code is routable, the designation of which will prevent a periodic LERG analysis performed by the system from identifying this as a code that should be deleted.
As shown in FIG. 7, the Routing Matrix Tab 132 will display the routing assignments to and from a particular switch (i.e., inbound and outbound) when the switch is selected in the “Customer/Market/Switch Management” section 126 of the screen and a “Traffic Type” is selected. In the preferred embodiment shown in FIG. 7, the outbound routing assignments are shown on the left side of the screen and the inbound routing assignments are shown on the right side of the screen. From this screen, traffic can be verified or the routing method can be updated for a particular switch. Inbound and outbound relationships can also be modified.
Referring back to the Main Customer Screen 120 shown in FIGS. 6 and 7, a Manage Codes Owned button 150 is provided to allow codes to be added to the tandem manager database. When codes are added, they are associated with a Metasolv order for either a T1/initial trunk group order or an initial translations order. To add codes to the tandem manager database or change routing information, the Manage Codes Owned button 150 is clicked to display the “Manage Codes” window, as shown in FIG. 8, where the associated Metasolv order number must be entered and validated by clicking on “Validate Order.” After “Validate Order” is clicked, the “SWITCH INFO” data will populate the screen from the routing database, and “ORDER INFORMATION” data will populate the screen from Metasolv. Additionally, all codes for the particular switch (and any POIs for this switch) will be displayed as either “AVAILABLE” or “OWNED.” To “own” any available codes (i.e., add them to the tandem manager database), the codes must be selected and then placed in the “Codes Owned” window of the screen (the right side shown in FIG. 6) by clicking an arrow 152. Codes can likewise be moved back by clicking an arrow 154. When the code is moved over to the “Codes Owned” window, the LERG data will be displayed as well as routing information/options. As shown in FIG. 6, an appropriate routing method can be selected for each code. Once all information is entered, the “Execute” button can be clicked, which will add the codes to the tandem manager database.
Referring again back to the Main Customer Screen 120 shown in FIGS. 6 and 7, a Perform Carrier Add button 160 is provided to allow initiation of routing between customers via a Carrier Add screen, as shown in FIG. 9. The Perform Carrier Add function will generate an e-mail to send to the customer that includes the routing information spreadsheet as well as an ASR, if required. It will also create a Carrier Add order in Metasolv and link the spreadsheet of codes to the Carrier Add order in Metasolv.
Referring to FIG. 9, to enter a Carrier Add order an associated Metasolv order number must be entered and validated by clicking on the “Validate Order” button. After the “Validate Order” button is clicked, the “ORIG SWITCH INFO” data will populate the screen from the routing database and the “ORDER INFORMATION” data will populate the screen from Metasolv. If a “Destination Market” is selected and the “Query Switches” button is clicked, all of the switches in the destination market will be retrieved with information about any routing assignments already made. Each potential switch has an indicator to indicate whether the “ORIG SWITCH” is routing to it as well as how many codes it should be routing to and how many are possible.
As shown in FIG. 9, from the “Available Switches” list, switches and codes can be selected for routing as appropriate. To initiate routing for available codes, the appropriate codes are selected and an add arrow 162 is clicked. Once all switches/codes have been selected for routing, an order is created. Under the “E-Mail Options” heading on the screen in FIG. 9, an ASR can be created for the particular customer by clicking “Enter ASR” and populating the ASR data as appropriate. The ASR data screens are shown in FIGS. 10 and 11.
After the ASR is filled out, an e-mail template can be selected to use and enter a Required Due Date. When the “Generate E-mail” button is clicked on the screen shown in FIG. 7, an e-mail application will be launched with an order to send to the client (attached as a spreadsheet and/or ASR). The order attachments are automatically linked to the Metasolv order previously specified. A sample ASR is shown in FIG. 12.
As shown in FIG. 13, the Trunk Groups Tab 134 provides access to trunk group data and related information associated with a particular switch.
The Invoice Tab 136 of the Main Customer Screen 120 allows access to all invoice-related functionality for a particular customer, including generating invoices and other reports, such as, for example, usage summaries. FIGS. 14-17 illustrate some of the GUIs for this functionality. FIGS. 18 and 19 illustrate some sample generated reports.
Control/Reference Data Module
The Control/Reference Data Module 106 provides for direct access and editing of customer and account data, markets and tandem manager switches, routing and LERG data and system configuration.
Management/Operating Reporting Module
The Management/Operating Reporting Module 108 provides for reporting functionality relating to customers, accounts, billing, invoicing, routing, management reporting and traffic reporting. For example, traffic analysis reports can be generated to evaluate traffic through a particular switch. Such analytical reports provide an invaluable tool for managing all types of information associated with tandem switching and usage. FIGS. 20 and 21 illustrate some sample reports generated under this functionality.
Custom Table View Module
The Custom Table View Module 110 provides for viewing of various tables associated with either the tandem manager database or the LERG database.
Other Function Module
The Other Function Module 112 provides for access to software-related functions, such as password management and control, user control, customization, settings, and the like.
Agreement/Compliance Verification
The tandem manager system optionally may include an Agreement/Compliance Database containing information relating to existing customer agreements, ILEC agreements, authorization and compliance documentation with respect to various governing bodies, government agencies, or other state and federal government regulatory concerns. Such information can be incorporated into the tandem manager system such that it can be accessed with respect to a particular customer to verify, for example, whether the customer has an existing agreement with the third-party tandem service provider, whether the third-party tandem service provider is authorized to operate in a particular state, and to verify whether the third-party tandem service provider has an existing interconnection and operation agreement with one or more LECs or ILECs in a particular state. Other information may include codes or other information relating to governing agencies or regulatory bodies. In a preferred embodiment, this database is automatically checked to verify such information as it relates to a particular customer when a customer is set up or edited within the system. The Agreement/Compliance Database can also be accessed to provide reports and other summaries in connection with compliance verification, such as, for example, compliance verification in connection with Sarbanes-Oxley-type inquiries.
While one or more specific embodiments have been illustrated and described in connection with the present invention, it is understood that the present invention should not be limited to any single embodiment, but rather construed in breadth and scope in accordance with recitation of the appended claims.
Patent Application
20080080684
