Note: Descriptions are shown in the official language in which they were submitted.
CA 02605345 2014-08-19
SYSTEM AND METHODS FOR
MANAGING TANDEM SWITCH INFORMATION
10 Technical Field
[0002] The present invention relates to the field of telecommunications,
and more
particularly to automation and management of trunk routing among tandem
switches in a
telecommunications network.
Background
[0003] The following background information will be helpful in
understanding the field of
telecommunications as it relates to the present invention.
MON] 1. Acronyms
[00051 The written description herein may contain acronyms that refer to
various
telecommunications services, components and techniques, as well as features
relating to the
present invention. Although some of these acronyms are known, use of these
acronyms is not
strictly standardized in the art. Accordingly, for purposes of the written
description herein, the
acronyms are defined as follows:
1
CA 02605345 2014-08-19
[0006] Access Service Request (ASR)
[0007] Call Detail Record (CDR)
[0008] Central Exchange Service (Centrex)
[0009] Carrier Identification Code (CIC)
[0010] Competitive Local Exchange Carrier (CLEC)
[0011] Generic Access Profile (GAP)
[0012] Grade of Service (GOS)
[0013] Graphical User Interface (GUI)
[0014] Incumbent Local Exchange Carrier (ILEC)
[0015] Interexchange Carrier (IXC)
[0016] Internet Service Provider (ISP)
[0017] Local Exchange (NXX)
[0018] Local Exchange Routing Guide (LERG)
[0019] Local Routing Number (LRN)
[0020] Numbering Plan Area (NPA)
[0021] Plain Old Telephone Service (POTS)
2
CA 02605345 2014-08-19
[0022] Point of Interface (P01)
[0023] Private Branch Exchange (PBX)
[0024] Public Switched Telephone Network (PSTN)
[0025] Release (REL)
[0026] Release Complete (RLC)
[0027] Service Control Point (SCP)
[0028] Service Switching Point (SSP)
[0029] Signaling System 7 (SS7)
[0030] Signaling Transfer Point (STP)
[0031] Transmission Control Protocol/Internet Protocol (TCP/IP)
[0032] Trunk Circuit Identification Code (TCIC)
[0033] Trunk Integrated Records Keeping System (T1RKS)
[0034] Total Network Data System (TNDS)
[0035] 2. Background Information
[0036] In its most basic sense, a telephone call is placed from an
origination point (call
origin) and is connected to a destination point (call destination). The
origination point will be
3
CA 02605345 2014-08-19
associated with an originating end office and the destination point will be
associated with a
destination or terminating end office. A telecommunications network is
utilized to effectuate a
connection between the end offices, and ultimately between the origination and
destination
points. An important component of this network is the public switched
telephone network
(PSTN). The PSTN generally consists of a series of switches capable of
logically routing calls
through the telecommunications network based, in part, on information relating
to the call origin
and the call destination.
100371 The PSTN typically employs two types of switches within the
network: (1) Class 5
switches (also known as an end office switch, telephone company end office
switch, central
office switch, Class 5 office switch, or a service switching point (SSP)), and
(2) Class 4 switches,
also known as a tandem switch, which is an intermediate network switch. These
switches are
controlled by associated signaling transfer points (STPs) and service control
points (SCPs),
which provide instruction on call routing, as well as a variety of network
implemented call
services.
[00381 A telephone company end office (or central office) connects a
network customers'
telephone system to the PSTN via a Class 5 office switch. The network
customers' telephone
system may be a business telephone system, such as a Centrex or private branch
exchange (PBX)
system, or it may be a plain old telephone service (POTS) system, which is the
telephone system
utilized by most residential customers. Other customers may be entire
networks, such as Internet
service providers (ISP) and the like. The tandem switches are intennediate
switches,
incorporated in routing between the originating end office and the terminating
end office.
4
CA 02605345 2014-08-19
Communication lines, or trunks, are interconnected by one or more switches
within the PSTN. A
group of similar trunks that connect the same geographic locations are
referred to as trunk
groups. Depending on the volume of traffic, several trunk groups may
simultaneously service
two particular points in the PSTN.
[0039] Trunk groups are designed and implemented based on analysis of
telecommunications
traffic. Traffic associated with many trunk groups has significantly increased
over the last
several years due primarily to population growth in certain geographic
regions. Trunk planners
and network design engineers attempt to identify communications paths among
switches that
carry an especially high amount of traffic or load from point to point.
Switches carrying
especially high loads are connected with direct trunk groups, rather than
trunk groups that may
be routed indirectly between two geographic locations, to help alleviate
traffic concerns.
However, this is not always a viable and economical option. PSTN traffic
continues to increase,
due not only to population (network user) growth, but also due to the
increasing number of
interconnecting carriers utilizing the network. Such carriers include
competitive local exchange
carriers (CLECs), interexchange carriers (DCCs), wireless carriers, and
independent carriers.
These carriers also bring new traffic to the network and most depend largely
on tandem switches
as primary hubs. The increased traffic loads and carriers have spurred the
addition of tandem
switches and associated trunk groups without resort to analysis of traffic
loads and routing. As a
result, many times tandem switches and trunk groups are added to relieve
overburdened
resources, while other existing tandem switches and trunk groups are not being
used to their
fullest capacity. This misuse of resources is due to the limited ability to
accurately quantify and
analyze the actual traffic loads at each tandem switch. And because most of
the costs associated
5
CA 02605345 2014-08-19
with network and switch expansion falls on the Incumbent Local Exchange
Carrier (II,EC)
(sometimes simply referred to as the Local Exchange Carrier (LEC)), the LECs
typically pass
these costs to other carriers in one form or another and may include increased
charges associated
with use of a particular LECs tandem switch.
[0040] The dynamic nature of network traffic, ownership of infrastructure,
and government
regulation, often creates opportunities for solutions to problems associated
with traffic between
end offices. Such opportunities for solutions include avoidance of associated
expenses with
particular tandem switches and off-load of traffic from exhausted tandem
switches to increase
traffic efficiency, i.e., purposeful or managed routing of call traffic via
tandem switches. Many
groups of commonly-situated members, particularly CLECs and wireless carriers,
could benefit
from such solutions to increase profit margins. With such a market defined,
these solutions can
often give birth to a new business model.
[0041] The present invention provides, among other things, business
models, methods,
software, and associated systems for quantifying, managing, directing,
auditing, and analyzing
the actual traffic loads of tandem switches and associated numbers and codes
for a defined
group. Among other things, this information can be used to minimize costs
associated with
tandem traffic for the defined group ¨ made up of subscribers or members ¨ by
purposely
routing subscriber traffic flow through switches owned by a subscriber or a
third-party tandem
manager as opposed to switches owned by a particular LEC or non-subscriber
entity.
[0042] Other aspects of the present invention will become apparent and be
more fully
understood from the drawings, descriptions, and claims set forth herein.
6
CA 02605345 2014-08-19
Summary of the Invention
100431 A system and associated methods for automation and management of
trunk routing
among switches in a telecommunications network between carriers connected to a
third party
tandem services provider or manager (a "neutral tandem network.")
[0044] According to a particular aspect of the invention, the system and
associated methods
can be used to effectuate a business model for providing preferred rates, or
other preferences, to
a defined group of members or subscribers 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. 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.
[0045] The management system includes information management methods
preferably
implemented by software for effectuating the business model. The management
system provides
for additional functions, such as switch traffic analysis and data tracking.
Brief Description of Drawings
[0046] 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.
7
CA 02605345 2014-08-19
[0047] FIG. 2 is a schematic diagram of some components of a tandem
management system
in accordance with the principles of the present invention.
[0048] FIG. 3 is a block diagram illustrating the basic software modules
of the tandem
manager of the tandem management system shown in FIG. 2.
[0049] FIG. 4 is an illustration or screenshot of a GUI of the tandem
manager shown in FIG.
3.
[0050] FIG. 5 is a block diagram illustrating the main functional
components of the
Customer Management Module.
[0051] FIG. 6 is an illustration or screenshot of a GUI for the Main
Customer Screen with
the Codes Owned Tab selected.
[0052] FIG. 7 is an illustration or screenshot of a GUI for the Main
Customer Screen with
the Routing Matrix Tab selected.
[0053] FIG. 8 is an illustration or screenshot of a GUI for the Manage
Codes function.
[0054] FIG. 9 is an illustration or screenshot of a GUI for the Carrier
Add function.
[0055] FIG. 10 is an illustration or screenshot of a GUI for an ASR data
screen with the
Main ASR Data Tab selected.
[0056] FIG. 11 is an illustration or screenshot of a GUI for an ASR data
screen with the
Contact Info Tab selected.
8
CA 02605345 2014-08-19
[0057] FIG. 12 is an illustration of a typical ASR form.
[0058] FIG. 13 is an illustration or screenshot of a GUI for the Main
Customer Screen with
the Trunk Groups Tab selected.
[0059] FIGS. 14-17 are respective illustrations or screenshots of GUIs
for the invoice
functionality of the tandem manager.
[0060] FIGS. 18-19 are respective illustrations of sample customer
invoices/reports.
[0061] FIGS. 20-21 are respective illustrations of sample switch
activity reports.
Detailed Description of Preferred Embodiments
[0062] 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.
[0063] 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
9
CA 02605345 2014-08-19
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.
[0064]
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.
[0065]
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
CA 02605345 2014-08-19
end office switches within the PS TN. 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.
[0066] 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.
[0067] 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
11
CA 02605345 2014-08-19
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.
[00681 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
12
CA 02605345 2014-08-19
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.
[0069] 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-1130C 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-NXX.$), 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
[0070] 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
13
CA 02605345 2014-08-19
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.
[0071] Customer Management Module
[0072] 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.
[0073] 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
14
CA 02605345 2014-08-19
appropriate privileges, Customers, Customer Markets, and Customer Switches can
be created,
edited or deleted.
[0074] 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.
100751 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.
[0076] 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 (P01) 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
CA 02605345 2014-08-19
(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.
100771 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.
100781 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 Ti/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
16
CA 02605345 2014-08-19
"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.
10079] 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.
[0080] 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
17
CA 02605345 2014-08-19
"ORIG SWITCH" is routing to it as well as how many codes it should be routing
to and how
many are possible.
[0081] 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.
[0082] 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.
[0083] As shown in FIG. 13, the Trunk Groups Tab 134 provides access to
trunk group data
and related information associated with a particular switch.
[0084] 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.
18
CA 02605345 2014-08-19
[0085] Control/Reference Data Module
[0086] The Control/Reference Data Module 106 provides for direct access
and editing of
customer and account data, markets and tandem manager switches, muting and
LERG data and
system configuration.
[0087] Management/Operating Reporting Module
[0088] 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.
[0089] Custom Table View Module
[0090] The Custom Table View Module 110 provides for viewing of various
tables
associated with either the tandem manager database or the LERG database.
[0091] Other Function Module
[0092] 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.
19
CA 02605345 2014-08-19
[0093] Agreement/Compliance Verification
[0094] 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.
[0095] 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
CA 02605345 2014-08-19
limited to any single embodiment, but rather construed in breadth and scope in
accordance with
recitation of the appended claims.
21
