U.S. patent application number 14/044996 was filed with the patent office on 2014-01-30 for systems and methods for using the advanced intelligent network to redirect data network traffic.
This patent application is currently assigned to VERIZON SERVICES CORP.. Invention is credited to Jeffrey R. Evans, Susan M. Middleswarth, John H. Wurster.
Application Number | 20140029740 14/044996 |
Document ID | / |
Family ID | 39498040 |
Filed Date | 2014-01-30 |
United States Patent
Application |
20140029740 |
Kind Code |
A1 |
Middleswarth; Susan M. ; et
al. |
January 30, 2014 |
SYSTEMS AND METHODS FOR USING THE ADVANCED INTELLIGENT NETWORK TO
REDIRECT DATA NETWORK TRAFFIC
Abstract
A method and system are disclosed for providing a low cost
mechanism for remotely rerouting queries in a telecommunications
network. A service control point (SCP) executes an application
which causes a queries to be launched over a LAN or WAN to a
remotely located data center. The system contains a primary and
secondary data center, in which the secondary data center
operations on a `hot-standby` basis. Based on a manually provided
indication, maintenance personnel may telephone and interact with a
voice response unit or a web-based interface, which indicates that
the SCP or SCP application should route queries to the secondary
data center. Similarly, the same mechanism can be used to indicate
that queries should be re-routed back to the primary data center.
This allows remote management for controlling the queries without
having to extensively modify the related infrastructure.
Inventors: |
Middleswarth; Susan M.;
(Silver Spring, MD) ; Evans; Jeffrey R.;
(Lovettsville, VA) ; Wurster; John H.; (Basking
Ridge, NJ) |
Assignee: |
VERIZON SERVICES CORP.
Arlington
VA
|
Family ID: |
39498040 |
Appl. No.: |
14/044996 |
Filed: |
October 3, 2013 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
11608675 |
Dec 8, 2006 |
8553853 |
|
|
14044996 |
|
|
|
|
Current U.S.
Class: |
379/221.09 |
Current CPC
Class: |
H04M 3/382 20130101;
H04M 3/493 20130101; H04M 3/38 20130101 |
Class at
Publication: |
379/221.09 |
International
Class: |
H04M 3/38 20060101
H04M003/38 |
Claims
1. A method comprising: receiving, at a web server, as part of a
switchover from a primary data center to a secondary data center, a
request from a user indicating that redirection of a query to the
secondary data center be initiated at a service control point;
transmitting, using an IP based communication protocol, an
indication from the web server to the service control point that
the query should be transmitted to the secondary data center; and
ascertaining, at the service control point, an IP address
associated with the secondary data center to be used for
transmitting said query.
2. The method of claim 1, further comprising: transmitting the
query from the service control point to the secondary data center
using the IP address associated with the secondary data center.
3. The method of claim 1, further comprising: routing the query
from the service control point over a data communications network
to the secondary data center using the IP address.
4. The method of claim 2, further comprising the steps of:
receiving a user identifier and a password from the user; verifying
the user identifier and the password, said transmitting said
indication from the web server to the service control point being
conditional on successful verification of the user identifier and
the password.
5. The method of claim 4, further comprising: receiving a
time-synchronized passcode from the user; and verifying the
time-synchronized passcode matches a second time-synchronized
passcode associated with the user identifier, said transmitting
said indication from the web server to the service control point
being conditional on successful verification of the
time-synchronized passcode.
6. The method of claim 4, wherein said receiving, at a web server,
the request from the user is performed as part of a manually
initiated switchover from a primary database to said secondary
database.
7. The method of claim 6, wherein said user identifier corresponds
to a maintenance person who manually controls said switchover from
the primary database to said secondary database.
8. The method of claim 7, wherein said secondary data center is
located outside of a public switched telephone network.
9. The method of claim 1, wherein said query is a query to said
service control point that is launched by a telephone switch.
10. The method of claim 9, wherein said query relates to how a call
should be handled at said telephone switch.
11. The method of claim 10, wherein said query is communicated to
said service control point using a protocol that is different from
the protocol used by said service control point to transmit the
query to said secondary database.
12. A system comprising: a web server capable of receiving an
indication of redirection from a user over the Internet, as part of
a switchover from a primary data center to a secondary data center,
indicating that a secondary address is to be used for transmitting
a query to the secondary data center; a service control point,
operatively connected to the web server and configured to receive
the indication of redirection from the web server and use the
secondary address for transmitting the query to the secondary data
center; and the secondary data center storing data, connected to a
data communications network, configured to receive the query from
the service control point transmitted using the secondary address,
the secondary data center being configured to provide a response
message in response to the query, the response message comprising
stored data.
13. The system of claim 12, wherein said primary data center is
connected to the data communications network and stores data that
is also stored in the secondary data center.
14. The system of claim 12, wherein the data communications network
is an IP based network and the secondary address is an IP-based
address.
15. The system of claim 12, wherein the web server is configured to
verify a time synchronized numerical passcode with a second
time-synchronized numerical passcode associated with a user
identifier and the web server is configured to transmit the
indication to the service control point conditional on successful
verification of the time-synchronized passcode.
16. The system of claim 12, wherein the web server is configured to
prompt the user to one of: select the service control point to use
the primary or secondary data center, select the service control
point to use whatever is the alternative database, or enter a
numerical IP address value of the primary or secondary data center,
and transmission of the indication to the service control point is
conditional on detection of the user in response respectively
selecting the secondary data center, selecting the service control
point to use the alternative database and the secondary data center
is the alternative database, or entering the numerical IP address
value of the secondary data center.
17. The system of claim 12, further comprising: a telephone switch
for launching said query to said service control point.
18. The system of claim 17, wherein said query relates to how a
telephone call should be handled by said telephone switch.
19. The system of claim 18, wherein said telephone switch is
configured to communicate said query using a different
communications protocol than a communications protocol that said
service control point uses to communicate with said secondary data
center.
20. The system of claim 19, wherein said secondary data center is
located outside of a public switched telephone network.
Description
RELATED APPLICATIONS
[0001] This application is a divisional of co-pending U.S. patent
application Ser. No. 11/608,675, titled "SYSTEMS AND METHODS FOR
USING THE ADVANCED INTELLIGENT NETWORK TO REDIRECT DATA NETWORK
TRAFFIC," filed on Dec. 8, 2006, which is hereby expressly
incorporated by reference in its entirety.
BACKGROUND INFORMATION
[0002] The development of the Advanced Intelligent Network (AIN)
has allowed telephone companies to offer various services that were
heretofore difficult and expensive to develop. A variety of new
services are possible by using the infrastructure of the AIN,
including the ability to provide custom services to a subscriber at
different locations.
[0003] The AIN architecture is dependent on network databases
called Service Control Points (SCPs) that store data and programs
used to control various switching structures in the telephone
network. Originally, the design of the AIN anticipated that the
SCPs would be flexible to meet future needs, and to a large extent
that has occurred. Because the SCPs are used to provide enhanced
services, the architecture was designed with redundancy. However,
the SCPs are specialized processors, and fairly expensive relative
to other types of processing equipment. Over time, the SCPs were
required to interface with other types of databases and data
centers. However, access to these databases and datacenters by the
SCPs was not designed within the AIN architecture, and hence the
robust reliability mechanisms were not readily applicable to the
SCP-to-database/data center portion of the network. Thus, there is
a need for flexible mechanisms to provide greater reliability and
control in regard to the SCP accessing various databases and
datacenters.
BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)
[0004] Reference will now be made to the accompanying drawings,
which are not necessarily drawn to scale, and wherein:
[0005] FIG. 1 illustrates an exemplary embodiment of the
architectural components of an AIN.
[0006] FIG. 2 illustrates an exemplary embodiment of two databases
are accessed by the SCPs.
[0007] FIG. 3 illustrates an exemplary embodiment of a user
interacting with a voice response unit.
[0008] FIG. 4 illustrates an exemplary embodiment of a user
interacting with a web-site.
DETAILED DESCRIPTION
[0009] Exemplary embodiments are described more fully hereinafter
with reference to the accompanying drawings, in which some, but not
all embodiments of the inventions are shown. These exemplary
embodiments are provided so that this disclosure will satisfy
applicable legal requirements. Like numbers refer to like elements
throughout. Although specific terms are employed herein, they are
used in a generic and descriptive sense only and not for purposes
of limitation.
[0010] In FIG. 1, illustrating an exemplary embodiment of a
switching service point (SSP) 102a, 102b represent telephone
switches capable of switching voice calls between users of the
telephone network, represented via the telephone icons 100a, 100b.
Although illustrated in terms of voice calls, the services used
could be data, voice-over-IP, wireless, etc. The SSPs communicate
using interoffice communication facilities 104, which typically are
based on optical fiber communication, but again can utilize various
other types of technology.
[0011] The SSPs use a signaling network, such as Signaling System
No. 7 (SS7), which comprises Signaling Transfer Points (STPs) 108a,
108b for routing signaling messages to the various network
elements. The STPS can be deployed in pairs, and each SSP is
connected via signaling links 106a, 106b to each STP. Thus, if one
of the STPs is unavailable, the mated STP in the pair is designed
to seamlessly pick up the load.
[0012] The STPs are used to route signaling messages to a
specialized database called a service control point (SCP). The SCP
112a, 112b is a combination database and application server, which
can handle queries launched by the SSPs. It stores data for
handling relatively simply queries, and also provides instructions
to the SSP for executing more complicated call handling
applications. The SCP communicates with the SSPs using an AIN
protocol, and provides the appropriate information regarding how a
call at the SSP should be handled. The SCPs are also deployed in
mated pairs, so that if one is unavailable, the other can
seamlessly pickup the load. This type of configuration is sometimes
called an "active-active" configuration as both SCPs are typically
running and handling queries. One complication of this type of
architecture is that data that is updated on one SCP should be
synchronized with the other SCP, since they are logically viewed as
a single SCPo
[0013] As noted, the SCPs communicate to the SSPs using a standard
AIN protocol, and execute custom applications designed around the
AIN protocol. Because the SCPs control the SSPs and potentially
impact millions of subscribers, they are thoroughly tested, and
operate on a highly reliable processing platform. As can be
expected, SCPs are fairly expensive, and their operation is
controlled by the telephone company. It is imperative to the
telephone network provider that these systems be "stable" and
reliable. Consequently, the whole telecommunications architecture
is designed to be tolerant of faults.
[0014] As a consequence, there is a tension between designing the
SCPs to be flexible platforms that can accommodate new service
offerings, and desiring the SCPs to be stable and reliable service
platforms for providing services. Typically, stable and reliable
service platforms are achieved by not adding new services (which
frequently can cause unexpected problems). However, as they are
also designed to be flexible service platforms, new applications
should be readily accommodated, and this typically requires
extensive testing.
[0015] One approach to achieving flexibility is to allow the SCPs
to access data stored in traditional databases. This provides
several benefits. First, there may be data already stored by a
telecommunications service provider in databases for other reasons.
Rather than duplicating the data in the SCP (which creates
additional issues regarding data synchronization), the SCP may
query the other database. Further, rather than expanding the data
storage capabilities, or deploying additional SCPs (which are
rather expensive), the existing SCPs can access the less expensive
database systems.
[0016] Thus, it would be helpful for SCPs to access databases in
datacenters using commonly available data communication networks.
These standard databases typically do not accommodate the AIN
protocols, nor are the data communications networks interconnecting
them designed to be as reliable as the telecommunications
networks.
[0017] An exemplary embodiment for providing a flexible service
architecture while maintaining stability via the SCPs is shown in
FIG. 2. FIG. 2 shows one embodiment in which readily available
database systems or servers 204a, 204b are accessible via a LAN 200
or other data communication network infrastructure for providing
data to an SCP 112a, 112b. For reliability and other reasons (such
as facilitating planned maintenance), the databases are deployed in
pairs, so that if one database 204a is unavailable, the other 204b
continues to run and provide data as needed to the SCP 112. Unlike
the SCPs which operate in an "active-active" configuration, the
off-site databases 204a, 204b operate in an "active-standby" mode.
This means that data may be updated in Site A, but not necessarily
updated in real time in Site B. Typically, data from Site A is used
to periodically (or in near-real-time) update the data in Site B.
The sooner that the alternative site is updated, the less
likelihood there is for data synchronization problems to occur if
there is a need to switch to the standby site, Site B. As for the
LAN, it is not necessarily limited to any particular technology,
and could implemented via a wide-area-network (WAN) or a
metropolitan area network (MAN).
[0018] The SCPs can access the necessary data in the database by
using the well known TCP/IP protocol. Thus, messages are sent from
the SCP to the appropriate database using an IP address that
identifies the primary site. For example, Site A 204a will have an
IP address, IPI distinct from Site B 204b, which would be IP2. In
the event of a Site A becoming unavailable, the SCP should use the
address for Site B. This requires each SCP to maintain a table of
each IP address for a given application, which is duplicated on
Site A and Site B. Maintaining a table with both IP addresses
values is not by itself difficult. Functionality must be defined so
that the SCP knows when to switch to using the alternative IP
address.
[0019] In SS7, this functionality is provided in part by the STPs,
which provide for `alias` addressing. An alias address is an
address which can be mapped to one of two other addresses, which
can result in routing the message to one of two elements, based on
which element is operation. Procedures are defined within SS7 for
the automatic detection and failover in case of a link or network
element failure and the use of an alias address. While these
procedures could be incorporated into the SCP for communication to
the datacenter, this would require functionality added to the LAN
infrastructure and the databases. Customizing the operation of the
LAN and database operation would negate part of the benefits of
using readily available platforms for the LAN and the
databases.
[0020] One approach is to provide a mechanism in the SCP allowing a
manual redirection of messages to the backup database. This would
direct the SCP to use the backup IP address. Essentially, a flag or
other type of status indication provides information as to whether
the primary or backup IP address would be used for messages sent
from the SCP. Since it is presumed that the primary database is
usually available, a manual mechanism would provide an effective
cost/benefit solution of providing backup access with minimal
infrastructure development cost. This would allow use of readily
available LANs and databases, with minimal impact to the SCP
functionality.
[0021] The mechanism for reconfiguring the SCPs to switch over from
a primary site (e.g., Site A) to a secondary site, Site B, can be
accomplished in multiple ways. One approach is to define procedures
in the SCP application level program to detect failure at the
application layer, and communicate the need to a management
application to switch over to the secondary site. This approach
requires the SCP application to be modified, and since an SCP may
be executing several applications, each would have to be
modified.
[0022] Another approach is to indicate the need to switch from the
primary to the secondary data center via human intervention. The
determination that there is a need to switch over is accomplished
by a human, most likely in response to observation of other
systems, notifications, alarms, or outputs. For example, alarms or
other notifications may bring to the attention of a systems
administrator that one of the data centers or databases is
inoperable. The determination that a datacenter is unavailable can
be due to a cataclysmic event, such as total failure of power,
destruction of the premises (e.g., fire, tidal wave, earthquake,
etc.), or can be a planned event (such as the primary data center
being taken off line for maintenance or upgrading).
[0023] The human interaction can occur in a variety of ways. As
shown in FIG. 2, an interactive voice response unit (IVR) 206 can
be used to provide a man-machine interface allowing the caller to
provide appropriate indicators as to which data site may be used.
IVRs are well known in the area of telecommunications and provide
prompts to a caller and receive DTMF signals in response. The IVR
collects information and instructs the SCP to set the flag
indicating whether the primary database is available or not.
Various embodiments are possible, such as the IVR instructing the
SCP to set a flag, which an application on the SCP then maps to an
IP address, or the IVR could simply indicate which IP address
should be used (primary or secondary).
[0024] Exemplary call flow for handling such an interaction is
shown in FIG. 3, wherein the IVR process begins in step 300 by
receiving a call from the public switched telephone network. In one
embodiment, the ANI (calling party number) is compared with a list
of values that represent authorized users that can request the
change. This step 302 is optional, and represents one form of
security mechanism. If the ANI is not on a list of approved
callers, or other security mechanism indicates unauthorized access,
the call ends at step 312. Otherwise, the IVR may prompt the caller
for another level a security and/or identification code in step
306. The security code or user ID could be a simple alpha-numeric
sequence, represented by DTMF tones. Other embodiments can use
speech analysis for determining whether the user is authorized,
which is compared against a file of authorized users' speech
patterns. Other embodiments for authenticating the user are
possible, and some may rely upon time-based passcodes entered by
the caller, where the code is time-synchronized in the IVR. Because
the IVR is reached by dialing a telephone number, even a
non-published telephone number is susceptible to hackers attempting
malicious entry.
[0025] In the next step 308, the user enters information and the
system validates the caller. If the information is not validated,
the call is ended at step 312. If the information is validated, the
process continues with the user indicating the desired action.
[0026] The particular form of the prompts and responses can be
designed in a number of ways. The user may be asked to select to
use the primary or secondary site. Alternatively, the user may
simply be asked whether the SCP would "toggle" and use whatever is
the alternative database (whether primary or secondary). In another
embodiment, the user could actually enter the numerical IP address
value.
[0027] As a result of the user's input in step 314, the IVR then
initiates a command to the SCP at step 316. The SCP processes the
command, and then confirms acting on the request in step 318. The
IVR, in turn, confirms the status with the user. At this point, the
caller has accomplished the function of manually causing the SCP to
redirect calls to another data center and the call is ended in step
320.
[0028] The IVR is one approach for allowing the user to indicate
the switchover to the alternate data site. This approach can be
embodied with other equipment, other than a dedicated IVR. For
example, the SSP has functionality that can be controlled by SCP so
as to provide an IVR-like functionality of providing prompts to a
caller, authorizing information entered by the caller, and setting
a flag based on analyzing the user's input. Essentially, the AIN
infrastructure of the SCP and SSP can be defined to accomplish the
SCP's switch over to a backup datacenter.
[0029] Another embodiment is to use a web-based interface for the
user to manually indicate a switchover to a backup database. In
this case, the user could log onto a secure web site, which prompts
the user for identification, passcode, and/or other forms of
security information. The user would then be prompted, via text or
graphics, as to what data center should be used. The system could
provide an immediate switch-over (as in the case of an unplanned
outage of the primary data center) or the system could request a
time for affecting the switch over (as in the case of a planned
outage of the primary data center).
[0030] FIG. 4 illustrates an embodiment using the web-based
interface. The process begins at step 400 when the user, such as
the appropriate maintenance or operations personnel, initiates
contact with the web server 402. The interaction could occur using
off-the-shelf web browsers and communication protocols, but other
embodiments using other proprietary or standardized data
communication protocols and methods can be used.
[0031] In the next step 404, the web server prompts the user to
enter identification and authentication information. The
information can be in various forms, including passwords, secret
keys, digital signatures, secure protocols, the aforementioned
time-synchronized numerical indicators, etc. The authentication and
identification information may further be provided in multiple
stages of interaction or prompting by the web server. The web
server may be able to authenticate the user locally, or may require
remote access to other servers to access information necessary to
validate the information provided by the user.
[0032] The next step 406 indicates the options available based on
whether the information is validated by the web-server. If the
information is not validated, then the communication may be
terminated 408. In various embodiments, the user may be provided
with multiple attempts, and the system may employ various well
known security schemes in an attempt to block the same user after
they have repeatedly failed.
[0033] Assuming that the information is validated, an indication
then is provided in step 410 to the SCP from the web-server that a
request was received for switching over to using the alternate
datacenter. This indication can be conveyed in different methods,
but typically is conveyed using a data communications network
allowing the SCP to communicate with the web server.
[0034] In the next step 412, the address for the alternative
datacenter is ascertained. The web server may indicate the address
to the SCP, or the SCP may retrieve the correct address from its
own memory, or by querying another database. Regardless, in step
414 the SCP then transmits the queries to the alternative database
using the updated address information. At this point, in step 418,
the changeover to the alternative database can be considered
completed.
[0035] Regardless of whether a voice or web-based interface is
used, the same mechanism can be used to redirect queries to the
secondary data center. Thus, when the primary data center is
returned to an operation or on-line status, queries can be
redirected via the same mechanism.
[0036] This provides an approach for quickly re-routing queries to
a secondary data center, located outside of the public switched
telephone network, without having to reprogram the service logic or
having to modify the routing tables in routers. This new approach
allows switchover to a secondary site even when communication links
are operational from the SCP to the primary data center, but
problems are encountered in the application layer, which the
application may not be able to readily detect. This approach also
allows maintenance personnel, who are trained to maintain the
day-to-day operations, to maintain operation without having to
involve trained support personnel who would otherwise have to be
involved in ascertaining and correcting the problem. Further, the
change can be made remotely, using any public telephone, which
facilitates timely changeover without having to wait for authorized
or trained personnel to be physically on-site.
[0037] Many modifications and other embodiments of the inventions
set forth herein will come to mind to one skilled in the art to
which these inventions pertain having the benefit of the teachings
presented in the foregoing descriptions and the associated
drawings. Therefore, it is to be understood that the inventions are
not to be limited to the specific embodiments disclosed and that
modifications and other embodiments are intended to be included
within the scope of the appended claims. Although specific terms
are employed herein, they are used in a generic and descriptive
sense only and not for purposes of limitation.
* * * * *