U.S. patent number 6,597,701 [Application Number 09/219,095] was granted by the patent office on 2003-07-22 for system and method for configuring a local service control point with a call processor in an architecture.
This patent grant is currently assigned to Sprint Communications Company L.P.. Invention is credited to Royal Dean Howell.
United States Patent |
6,597,701 |
Howell |
July 22, 2003 |
System and method for configuring a local service control point
with a call processor in an architecture
Abstract
A system and method for processing a call comprises a signaling
interface to receive and process call signaling and transmit call
signaling between a call processor and communication devices such
as a local number portability service control point. A call
processor processes call signaling to determine call connections. A
local service control point (local SCP) provides information such
as, for example, for N00 routing and virtual private network (VPN)
routing. The local SCP resides with the call processor on a single
platform so that they are connected, for example, through a
backplane or bus architecture. In this configuration, transaction
capabilities application part messages do not have to be
transmitted between the signaling interface and the local SCP.
Instead, direct communication can occur through control messages
transmitted between the local SCP and the call processor thereby
realizing increased speed and processing efficiency. Because the
local SCP resides with the call processor, two remote dips to an
SCP is not necessary.
Inventors: |
Howell; Royal Dean (Trimble,
MO) |
Assignee: |
Sprint Communications Company
L.P. (Overland Park, KS)
|
Family
ID: |
22817860 |
Appl.
No.: |
09/219,095 |
Filed: |
December 22, 1998 |
Current U.S.
Class: |
370/410; 370/360;
370/401 |
Current CPC
Class: |
H04L
12/5601 (20130101); H04Q 3/0025 (20130101); H04L
2012/5618 (20130101); H04L 2012/5626 (20130101); H04L
2012/563 (20130101) |
Current International
Class: |
H04L
12/56 (20060101); H04Q 3/00 (20060101); H04L
012/56 () |
Field of
Search: |
;370/351,357,360,384,385,386,395.1,396,400,401,410,352 |
References Cited
[Referenced By]
U.S. Patent Documents
Other References
Helen A. Bauer, John J. Kulzer, Edward G. Sable, "Designing
Service-Independent Capabilites for Intelligent Networks," IEEE,
Dec. 1988, pp. 31-41. .
ITU-T Q.1219, "Intelligent Network User's Guide For Capability Set
1," Apr., 1994. .
Thorner, "Intelligent Networks, Capter 2," 1994, Artech House, pp.
11-107. .
ITU-T, Recommendation Q.722, "Specifications of Signalling System
No. 7, General Function of Telephone Messages and Signals,"
1993..
|
Primary Examiner: Vanderpuye; Ken
Attorney, Agent or Firm: Ball; Harley R. Funk; Steven J.
Robb; Kevin D.
Claims
What is claimed is:
1. A communication system comprising: a Signaling System 7 (SS7)
interface configured to receive an SS7 initial address message for
a call indicating a called number and a first connection, transfer
an SS7 query message indicating a translation of the called number,
and receive an SS7 response message indicating call routing
information; a call processor coupled to the SS7 interface and
configured to process the called number from the initial address
message to transfer a first message indicating the called number,
process a second message indicating the translation of the called
number to initiate the transfer of the SS7 query message from the
SS7 interface, and process the call routing information from the
SS7 response message to transfer a third message indicating the
first connection and a second connection; a first service control
point configured to process the first message indicating the called
number to transfer the second message indicating the translation of
the called number; a means for connecting the call processor to the
first service control point to locate the call processor and the
first service control point on a same platform and for transferring
the first message and the second message between the call processor
and the first service control point without using SS7 formatted
messages; and an interworking unit configured to receive
communications for the call from the first connection in a time
division multiplex communication format, receive the third message,
and in response to the third message, convert the communications
from the time division multiplex communication format to an
asynchronous communication format and transfer the communications
in the asynchronous communication format over the second
connection.
2. The communication system of claim 1 further comprising a second
service control point configured to process the SS7 query message
indicating the translation of the called number to transfer the SS7
response message indicating the call routing information.
3. The communication system of claim 2 wherein the second service
control point comprises a local number portability database.
4. The communication system of claim 1 wherein the first connection
comprises a DS0 connection and the second connection comprises an
asynchronous transfer mode connection.
5. The communication system of claim 1 wherein the means comprises
a bus structure.
6. The communication system of claim 1 wherein the means comprises
a backplane.
7. The communication system of claim 1 wherein the means comprises
a motherboard.
8. A method of operating a communication system, the method
comprising: in a Signaling System 7 (SS7) interface, receiving an
SS7 initial address message for a call indicating a called number
and a first connection; in a call processor coupled to the SS7
interface, processing the called number from the initial address
message to transfer a first message indicating the called number;
in a means for connecting the call processor to a first service
control point to locate the call processor and the first service
control point on a same platform, transferring the first message
from the call processor to the first service control point without
using SS7 formatted messages; in the first service control point,
processing the first message indicating the called number to
transfer a second message indicating a translation of the called
number; in the means for connecting the call processor to the first
service control point, transferring the second message from the
first service control point to the call processor without using the
SS7 formatted messages; in the call processor, processing the
second message indicating the translation of the called number to
initiate a transfer of an SS7 query message from the SS7 interface;
in the SS7 interface, transferring an SS7 query message indicating
the translation of the called number and receiving an SS7 response
message indicating call routing information; in the call processor,
processing the call routing information from the SS7 response
message to transfer a third message indicating the first connection
and a second connection; and in an interworking unit, receiving
communications for the call from the first connection in a time
division multiplex communication format, receiving the third
message, and in response to the third message, converting the
communications from the time division multiplex communication
format to an asynchronous communication format and transferring the
communications in the asynchronous communication format over the
second connection.
9. The method of claim 8 further comprising, in a second service
control point, processing the SS7 query message indicating the
translation of the called number to transfer the SS7 response
message indicating the call routing information.
10. The method of claim 9 wherein the second service control point
comprises a local number portability database.
11. The method of claim 8 wherein the first connection comprises a
DS0 connection and the second connection comprises an asynchronous
transfer mode connection.
12. The method of claim 8 wherein the means comprises a bus
structure.
13. The method of claim 8 wherein the means comprises a
backplane.
14. The method of claim 8 wherein the means comprises a
motherboard.
Description
RELATED APPLICATIONS
Not Applicable
FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT
Not Applicable
MICROFICHE APPENDIX
Not Applicable
FIELD OF THE INVENTION
The present invention relates to the field of telecommunications
call switching and transport and, more particularly, for connecting
a database having call information to a call processor.
BACKGROUND OF THE INVENTION
Broadband systems provide telecommunications providers with many
benefits, including greater bandwidth, more efficient use of
bandwidth, and the ability to integrate voice, data, and video
communications. These broadband systems provide callers with
increased capabilities at lower costs. The broadband systems use
call signaling to determine call routing and processing.
During the call routing and call connection process, switches and
other communication devices obtain information for call routing and
processing from service control points (SCPs). These SCPs typically
contain information, such as for N00 routing and local number
portability (LNP). The switches and communication devices have to
send messages to the SCPs, and the information is returned to the
switch or communication device in a message. Typically, the
messages are formatted as transaction capabilities application part
(TCAP) queries and responses.
However, for a call sometimes several instances of transmitting the
messages back and forth between the switch and the SCP occur. This
increases the time in which a call can be connected. Thus, there is
a need to connect calls and obtain information at an increased rate
and efficiency.
SUMMARY OF THE INVENTION
The present invention comprises a system for processing a call
having call signaling and user communications. The system comprises
a signaling processor adapted to receive the call signaling and to
process the call signaling to select a connection for the user
communications and to transmit a control message that is not a
transaction capabilities application part message requesting
information for use in processing the call signaling. A local
service control point is adapted to receive the control message, to
process the control message to obtain response information, and to
provide a response message with the response information to the
signaling processor.
The present invention further comprises a system for processing a
call having call signaling and user communications. The system
comprises a signaling processor adapted to receive the call
signaling and to process the call signaling to select a connection
for the user communications and to transmit a control message
requesting information for use in processing the call signaling. A
local service control point is connected to the signaling processor
in a single computer architecture and is adapted to receive the
control message, to process the control message to obtain response
information, and to provide a response message with the response
information to the signaling processor.
The present invention further is directed to a system for
processing a call having call signaling and user communications.
The system comprises a signaling interface that is adapted to
receive and process the call signaling to determine call
information elements and to transmit the call information elements.
A call processor is adapted to receive the call information
elements from the signaling interface, to process the call
information elements to determine a connection for the user
communications and to transmit a control message that is not a
transaction capabilities application part message requesting
information for use in processing the call signaling. A local
service control point is adapted to receive the control message, to
process the control message to obtain response information, and to
provide a response message with the response information to the
signaling processor.
Still further, the present invention is directed to a system for
processing a call having call signaling and user communications.
The system comprises a signaling interface that is adapted to
receive and process the call signaling to determine call
information elements and to transmit the call information elements.
A call processor is adapted to receive the call information
elements from the signaling interface, to process the call
information elements to determine a connection for the user
communications and to transmit a control message that is not a
transaction capabilities application part message requesting
information for use in processing the call signaling. A local
service control point is connected to the signaling processor in a
single computer architecture and is adapted to receive the control
message, to process the control message to obtain response
information, and to provide a response message with the response
information to the signaling processor.
Further yet, the present invention is directed to a method for
processing a call having call signaling and user communications.
The method comprises receiving and processing the call signaling in
a signaling processor to determine a connection for the user
communications. A request for information for use in processing the
call signaling is transmitted to a local service control point in a
control message that is not a transaction capabilities application
part query message. The method further comprises receiving and
processing the control message to obtain response information. The
response information is provided in a response message that is not
a transaction capabilities application part response message.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram of a call processing system in accordance
with an embodiment of the present invention.
FIG. 2 is a block diagram of an expanded call processing system in
accordance with an embodiment of the present invention.
FIG. 3 is a block diagram of an expanded call processing system in
accordance with an embodiment of the present invention.
FIG. 4 is a functional diagram of a controllable asynchronous
transfer mode matrix in accordance with the present invention.
FIG. 5 is a functional diagram of a controllable asynchronous
transfer mode matrix with time division multiplex capability in
accordance with the present invention.
FIG. 6 is a functional diagram of an asynchronous transfer mode
interworking unit for use with a synchronous optical network system
in accordance with the present invention.
FIG. 7 is a functional diagram of an asynchronous transfer mode
interworking unit for use with a synchronous digital hierarchy
system in accordance with the present invention.
FIG. 8 is a block diagram of a signaling processor constructed in
accordance with the present system.
FIG. 9 is a block diagram of a data structure having tables that
are used in the signaling processor of FIG. 8.
FIG. 10 is a block diagram of additional tables that are used in
the signaling processor of FIG. 8.
FIG. 11 is a block diagram of additional tables that are used in
the signaling processor of FIG. 8.
FIG. 12 is a block diagram of additional tables that are used in
the signaling processor of FIG. 8.
FIG. 13 is a table diagram of a time division multiplex trunk
circuit table used in the signaling processor of FIG. 8.
FIG. 14 is a table diagram of an asynchronous transfer mode trunk
circuit table used in the signaling processor of FIG. 8.
FIG. 15A is a table diagram of a trunk group table used in the
signaling processor of FIG. 8.
FIG. 15B is a continuation table diagram of the trunk group table
of FIG. 15A.
FIG. 15C is a continuation table diagram of the trunk group table
of FIG. 15B.
FIG. 16 is a table diagram of a carrier table used in the signaling
processor of FIG. 8.
FIG. 17 is a table diagram of an exception table used in the
signaling processor of FIG. 8.
FIG. 18 is a table diagram of an originating line information table
used in the signaling processor of FIG. 8.
FIG. 19 is a table diagram of an automated number identification
table used in the signaling processor of FIG. 8.
FIG. 20 is a table diagram of a called number screening table used
in the signaling processor of FIG. 8.
FIG. 21 is a table diagram of a called number table used in the
signaling processor of FIG. 8.
FIG. 22 is a table diagram of a day of year table used in the
signaling processor of FIG. 8.
FIG. 23 is a table diagram of a day of week table used in the
signaling processor of FIG. 8.
FIG. 24 is a table diagram of a time of day table used in the
signaling processor of FIG. 8.
FIG. 25 is a table diagram of a time zone table used in the
signaling processor of FIG. 8.
FIG. 26 is a table diagram of a routing table used in the signaling
processor of FIG. 8.
FIG. 27 is a table diagram of a trunk group class of service table
used in the signaling processor of FIG. 8.
FIG. 28 is a table diagram of a treatment table used in the
signaling processor of FIG. 8.
FIG. 29 is a table diagram of an outgoing release table used in the
signaling processor of FIG. 8.
FIG. 30 is a table diagram of a percent control table used in the
signaling processor of FIG. 8.
FIG. 31 is a table diagram of a call rate table used in the
signaling processor of FIG. 8.
FIG. 32 is a table diagram of a database services table used in the
signaling processor of FIG. 8.
FIG. 33A is a table diagram of a signaling connection control part
table used in the signaling processor of FIG. 8.
FIG. 33B is a continuation table diagram of the signaling
connection control part table of FIG. 33A.
FIG. 33C is a continuation table diagram of the signaling
connection control part table of FIG. 33B.
FIG. 33D is a continuation table diagram of the signaling
connection control part table of FIG. 33C.
FIG. 34 is a table diagram of an intermediate signaling network
identification table used in the signaling processor of FIG. 8.
FIG. 35 is a table diagram of a transaction capabilities
application part table used in the signaling processor of FIG.
8.
FIG. 36 is a table diagram of a external echo canceller table used
in the signaling processor of FIG. 8.
FIG. 37 is a table diagram of an interworking unit used in the
signaling processor of FIG. 8.
FIG. 38 is a table diagram of a controllable asynchronous transfer
mode matrix interface table used in the signaling processor of FIG.
8.
FIG. 39 is a table diagram of a controllable asynchronous transfer
mode matrix table used in the signaling processor of FIG. 8.
FIG. 40A is a table diagram of a site office table used in the
signaling processor of FIG. 8.
FIG. 40B is a continuation table diagram of the site office table
of FIG. 40A.
FIG. 40C is a continuation table diagram of the site office table
of FIG. 40B.
FIG. 40D is a continuation table diagram of the site office table
of FIG. 40C.
FIG. 41A is a table diagram of an advanced intelligent network
event parameters table used in the signaling processor of FIG.
8.
FIG. 41B is a continuation table diagram of the advanced
intelligent network event parameters table of FIG. 41A.
FIG. 42 is a table diagram of a message mapping table used in the
signaling processor of FIG. 8.
DETAILED DESCRIPTION
Telecommunication systems have a number of communication devices in
local exchange and interexchange environments that interact to
provide call services to customers. Both traditional and
intelligent network (IN) services and resources are used to
process, route, or connect a call to a designated connection.
These systems typically obtain information from service control
points (SCPs) to assist in routing and processing of calls. When a
switch or communication device requires information from the SCP,
it sends a transaction capabilities application part (TCAP) query
message to the SCP. The SCP responds with a TCAP response. The TCAP
response contains the requested information if that information is
available.
In addition, new technologies have been implemented to process
calls that are to be ported for local number portability (LNP). For
calls that require LNP processing or routing, two TCAP queries and
two TCAP responses can be required. In a first method, a first
query to an SCP requests information for the call for routing and
processing. The response may contain information which allows the
switch or communication device to determine that the called number
is a ported number. Then, a second TCAP query is generated to an
LNP SCP to obtain the destination for the ported number.
In a second method, a first query to an SCP requests information
for the call for routing and processing. The SCP may determine that
the number is ported and initiate a TCAP query to an LNP SCP. The
LNP SCP responds with the ported number to the first SCP. The first
SCP then responds to the switch or communication device with the
information.
However, in the first method, the switch or communication device
must generate two TCAP queries and process two TCAP responses. This
process is time consuming and processing intensive.
In the second method, two TCAP queries and two TCAP responses still
are processed. However, in the second method, the first SCP must
have significant processing capacity. Not only is this process time
consuming, but also the first SCP is unlikely to be able to process
the increased load of generating and processing the increased TCAPs
from multiple carries such as from both local exchange carriers
(LECs) and interexchange carriers (IXCs) for all feature group
access.
Moreover, in the second method the response from the first SCP to
the switch or communication device would have to relay two pieces
of information: first it must identify that the first SCP queried
the LNP SCP for the ported number, and second it must specify that
the response to the switch or communications device contains the
ported number. Otherwise, without knowing this information, the
switch or communication device would have to initiate a query to
the LNP SCP requesting the ported number, thus completing double
the work necessary to process the call. Unfortunately, many
responses from the first SCP to the switch or call processor may
not contain these two required pieces of information.
The increase in TCAP queries and required responses for general
queries to the SCP, as well as for calls that are ported, places an
increased amount of traffic on the SCPs which can overload the
SCPs. In addition, processing of the queries can take an extended
time, more than the time allowed for call connections.
The present invention provides a system and method that increases
the speed of call processing by placing the SCP functionality with
the signaling processor. Functionally, the SCP becomes the local
node SCP database and can be configured to use legacy system data
feeds. This allows the signaling processor to obtain information
from the SCP without initiating a TCAP query. In addition, because
the system can be configured in a bus-type architecture,
information can be obtained much quicker without the need to
interface with multiple components.
The system of the present invention processes call information to
make call connections. A call has user communications and call
signaling. The user communications contain the caller's
information, such as a voice communication or data communication,
and they are transported over a connection. Call signaling contains
information that facilitates call processing, and it is
communicated over a link. Call signaling, for example, contains
information describing the called number and the calling number.
Examples of call signaling are standardized signaling, such as
signaling system #7 (SS7), C7, integrated services digital network
(ISDN), and digital private network signaling system (DPNSS), which
are based on ITU recommendation Q.933. A call can be connected to
and from communication devices.
Connections are used to transport user communications and other
device information between communication devices and between the
elements and devices of the system. The term "connection" as used
herein means the transmission media used to carry user
communications between elements of the various telecommunications
networks and systems. For example, a connection could carry a
user's voice, computer data, or other communication device data. A
connection can be associated with either in-band communications or
out-of-band communications.
Links are used to transport call signaling and control messages.
The term "link" as used herein means a transmission media used to
carry call signaling and control messages. For example, a link
would carry call signaling or a device control message containing
device instructions and data. A link can carry, for example,
out-of-band signaling such as that used in SS7, C7, ISDN, DPNSS,
B-ISDN, GR-303, or could be via local area network (LAN), or data
bus call signaling. A link can be, for example, an asynchronous
transfer mode (ATM) adaptation layer 5 (AAL5) data link, UDP/IP,
ethernet, DS0, or DS1. In addition, a link, as shown in the
figures, can represent a single physical link or multiple links,
such as one link or a combination of links of ISDN, SS7, TCP/IP, or
some other data link. The term "control message" as used herein
means a control or signaling message, a control or signaling
instruction, or a control or signaling signal, whether proprietary
or standardized, that conveys information from one point to
another.
FIG. 1 illustrates an exemplary embodiment of a call processing
system 102 of the present invention. The call processing system 102
comprises a non-local service control point (SCP), such as a local
number portability (LNP) SCP 104, linked to a call connection
system 106 having a signaling processor 108 linked to a local
service control point (local SCP) 110.
The LNP SCP 104 contains customer data including information for
telecommunication services available to a customer such as local
number portability. The LNP SCP 104 has tables identifying ported
numbers for each number plan area-number (NPA-NXX). The LNP SCP 104
receives, analyzes, and responds to TCAP messages formatted as
described in the Bellcore AIN 0.1 reference and its updates, the
contents of which are incorporated herein by reference.
The signaling processor 108 is a signaling platform that can
receive, process, and generate call signaling. Based on the
processed call signaling, the signaling processor 108 selects
processing options, services, or resources for the user
communications and generates and transmits control messages that
identify the communication device, processing option, service, or
resource that is to be used. The signaling processor 108 also
selects virtual connections and circuit-based connections for call
routing and generates and transports control messages that identify
the selected connections. The signaling processor 108 can process
various forms of signaling, including ISDN, GR-303, B-ISDN, SS7,
and C7. A preferred signaling processor is discussed below.
The local SCP 110 contains information about the system and how to
route calls through the system. The local SCP 110 is queried from
the signaling processor 108 to determine how to route calls with
advanced routing features such as N00 routing, routing menu, or
virtual private network (VPN) routing.
The signaling processor 108 and the local SCP 110 can be located on
the same platform and connected by a single architecture, such as a
backplane, a bus architecture, or in a single computer. For
example, the signaling processor 108 and the local SCP 110 can be
on a single motherboard with programmed processor chips. With
either structure, increased processing speed and efficiency is
obtained. An interface between the two components is not required
such that a TCAP query is not required to be generated between the
signaling processor 108 and the local SCP 110. In addition, a TCAP
response is not required to be generated between the local SCP 110
and the signaling processor 108. Information can be transferred
between the two components quickly and easily without having to
build messages to be transmitted to devices outside of the local
SCP 110 and signaling processor 108 architecture.
The call processing system of FIG. 1 operates as follows. In a
first example, the signaling processor 108 receives call processing
from a communication device (not shown). The signaling processor
108 processes the call signaling and determines that information is
required from the local SCP 110. In this example, the called number
is an 800 number that requires translation to a ten digit NPA-NXX
number. The signaling processor 108 passes a control message to the
local SCP 110 requesting the information. The control message is
not a TCAP message and therefore is not required to be formatted
through an SS7 stack. In this example, the control message is
transmitted to the local SCP 110 through a bus.
The local SCP 110 receives the control message from the signaling
processor 108 and processes the control message. The local SCP 110
responds to the signaling processor 108 with the requested
information. In this example, the local SCP 110 responds with a ten
digit translated called number. The response is a control message
that is sent from the local SCP 110 to the signaling processor 108.
The response is not a TCAP response and therefore is not required
to be formatted through an SS7 stack. In this example, the control
message is transmitted from the local SCP 110 to the signaling
processor 108 through a bus.
In another example, the signaling processor 108 receives call
processing from a communication device (not shown). The signaling
processor 108 processes the call signaling and determines that
information is required from the local SCP 110. In this example,
the called number is an 800 number that requires translation to a
ten digit NPA-NXX number. The signaling processor 108 passes a
control message to the local SCP 110 requesting the
information.
The local SCP 110 receives the control message from the signaling
processor 108 and processes the control message to obtain response
information. The response information may contain the requested
information, or it may specify that the requested information is
not available or unknown. The local SCP 110 responds to the
signaling processor 108 with the response information. In this
example, the local SCP 110 responds with a ten digit translation to
obtain the translated called number.
The signaling processor 108 processes the information that is
received from the local SCP 110 to determine if the NPA-NXX of the
ten digit number has been flagged as a ported number. If the
signaling processor 108 determines that the number has been flagged
as a ported number, it initiates a TCAP query to the LNP SCP 104.
The LNP SCP 104 receives the TCAP query and processes it. If the
LNP SCP 104 determines that the number is a ported number, it
transmits a location routing number (LRN) to the signaling
processor 108 in a TCAP response message. If the LNP SCP 104
determines that the number is not a ported number, it transmits the
ten digit translated called number back to the signaling processor
108 in the response message.
FIG. 2 illustrates an example of an expanded call processing system
102A. The call processing system 102A comprises, in addition to the
LNP SCP 104 and the local SCP 110 of FIG. 1, a signaling interface
202, a call processor 204, and a call process and control system
(CPCS) 206.
The signaling interface 202 receives, processes, and transmits call
signaling. The signaling interface 202 can obtain information from,
and transmit information to, a communication device. Such
information may be transferred, for example, as a TCAP message in
queries or responses or as other SS7 messages such as an initial
address message (IAM). The signaling interface 202 also passes
information to the call processor 204 for processing and passes
information from the call processor to other communication devices
(not shown).
The call processor 204 is a signaling platform that can receive and
process call signaling. The call processor 204 has data tables
which have call connection data and which are used to process the
call signaling. Based on the processed call signaling, the call
processor 204 selects processing options, services, resources, or
connections for the user communications. The call processor 204
generates and transmits control messages that identify the
communication device, processing option, service, or resource that
is to receive call signaling or that is be used in call connections
or further call processing. The call processor 204 also selects
virtual connections and circuit-based connections for routing of
call signaling and connections for user communications and
generates and transports control messages that identify the
selected connections.
The CPCS 206 is a management and administration system. The CPCS
206 is the user interface and external systems interface into the
call processor 204. The CPCS 206 serves as a collection point for
call-associated data such as translations having call routing data,
logs, operational measurement data, alarms, statistical
information, accounting information, and other call data. The CPCS
206 accepts data, such as the translations, from operations systems
and updates the data in the tables in the call processor 204. The
CPCS 206 also provides configuration data to the elements of the
call processing system 102A including to the signaling interface
202, the call processor 204, and any interworking units (not shown)
or any controllable ATM matrix devices (not shown). In addition,
the CPCS 206 provides for remote control of call monitoring and
call tapping applications from the call processor 204. The CPCS 206
may be a local CPCS that services only components of a local call
processing system or a regional CPCS that services components of
multiple call processing systems.
The call processor 204 and the local SCP 110 can be located on the
same platform and connected by a backplane or bus architecture. In
addition, the signaling processor 108 and the local SCP 110 can be
on a single motherboard with programmed processor chips.
Alternately, the signaling interface 202 can be combined with the
call processor 204 and the local SCP 110 in either
configuration.
With any herein described structure, increased processing speed and
efficiency is obtained. Cross office time limits can be maintained.
That is, for example, the time that it takes the call processor 204
to process a call from the originating side to the terminating side
so that a connection can be made, including the time to get
information from components such as the local SCP 110 can be
maintained within the required time limits.
Moreover, an interface between the components is not required such
that a TCAP query is not required to be generated from the call
processor 204, through the signaling interface 202, and to the
local SCP 110. In addition, a TCAP response is not required to be
generated from the local SCP 110, through the signaling interface
202, and to the call processor 204. Because the components may be
configured to transfer information, messages, or communications
with and between the other components in any format, standard, or
method, communications between the components can occur at a faster
rate and in a more efficient manner. Information can be transferred
between the components quickly and easily without having to build
messages to be transmitted to devices outside of the local SCP 110
and call processor 204, and optionally the signaling interface 202,
architecture.
The operation of the call processing system 102A of FIG. 2 will be
described below with reference to a call connection with user
communications. This will provide a more complete description of
the operation of the call processing system 102A when used with
user communication connection devices. It will be appreciated that
the whole of the call processing system with the user communication
devices, i.e. an interworking unit and an ATM matrix, for a total
call connection is an aspect of the present invention.
FIG. 3 illustrates a call processing system 102B for call
connection. In addition to the devices of FIG. 2, the call
processing system 102B of FIG. 3 comprises an interworking unit 302
connected to an ATM matrix 304 by a connection 306, each of which
is linked to the call processor 204 and the CPCS 206. A first
communication device 308 and a second communication device 310 are
connected to the system through connections 312 and 314,
respectively, and links.
The interworking unit 302 interworks traffic between various
protocols. Preferably, the interworking unit 302 interworks between
ATM traffic and non-ATM traffic. The interworking unit 302 operates
in accordance with control messages received from the call
processor 204. These control messages typically are provided on a
call-by-call basis and typically identify an assignment between a
DS0 and a VP/VC for which user communications are interworked. In
some instances, the interworking unit 302 may transport control
messages which may include data to the call processor 204.
The ATM matrix 304 is a controllable ATM matrix that establishes
connections in response to control messages received from the call
processor 204. The ATM matrix 304 is able to interwork between ATM
connections and time division multiplex (TDM) connections. The ATM
matrix 304 also cross connects ATM connections with other ATM
connections. In addition, the ATM matrix 304 can switch calls from
TDM connections to other TDM connections. The ATM matrix 304
transmits and receives call signaling and user communications over
the connections.
The communication devices 308 and 310 comprise customer premises
equipment (CPE), a service platform, a switch, a remote digital
terminal, a cross connect, an interworking unit, an ATM gateway, or
any other device capable of initiating, handling, or terminating a
call. CPE can be, for example, a telephone, a computer, a facsimile
machine, or a private branch exchange. A service platform can be,
for example, any enhanced computer platform that is capable of
processing calls. A remote digital terminal is a device that
concentrates analog twisted pairs from telephones and other like
devices and converts the analog signals to a digital format known
as GR-303. An ATM gateway is a device that changes ATM cell header
VP/VC identifiers. The communication devices 308 and 310 may be TDM
based or ATM based. In the system of FIG. 3, preferably the first
communication device 308 is TDM based, and the second communication
device 310 is ATM based.
In an example of the operation of the signaling system 102B, the
first communication device 308 transports user communications and
call signaling. The signaling interface 202 receives the call
signaling, and the interworking unit 302 receives the user
communications.
The signaling interface 202 processes the call signaling and
converts it to call information elements, such as message
parameters, that can be processed by the call processor 204. A call
information element may be, for example, an integrated services
user part initial address message (ISUP IAM) message parameter from
an MSU or other message parameters. The signaling interface 202
passes the message parameters to the call processor 204.
The call processor 204 processes the call signaling message
parameters and determines that information is required from the
local SCP 110 to complete call processing. In this example, the
call is a VPN call.
The call processor 204 passes a control message to the local SCP
110 requesting the information. The control message is not a TCAP
message and therefore is not required to be formatted through an
SS7 stack. In this example, the control message is transmitted to
the local SCP 110 through a backplane.
The local SCP 110 receives the control message from the call
processor 204 and processes the control message to obtain the
response information. The response information may contain the
requested information, or it may specify that the requested
information is not available or unknown.
The local SCP 110 responds to the call processor 204 with the
response information. In this example, the local SCP 110 responds
with a routing code. The response is a control message that is sent
from the local SCP 110 to the call processor 204. The response is
not a TCAP response and therefore is not required to be formatted
through an SS7 stack. In this example, the control message is
transmitted from the local SCP 110 to the call processor 204
through a backplane.
The call processor 204 receives and processes the information from
the local SCP 110. The call processor 204 determines that the call
is to be connected to the second communication device 310. In this
example, the second communication device is an ATM device.
The call processor 204 selects a connection, such as a VP/VC on the
connection 304, over which the user communications will be
transmitted between the interworking unit 302 and the ATM matrix
304 and a connection, such as a VP/VC on the connection 314, over
which the user communications will be transmitted between the ATM
matrix and the second communication device 310.
The call processor 204 transmits a control message to each of the
interworking unit 302 and the ATM matrix 304 identifying the
selected connections 306 and 314. In addition, the call processor
204 transmits the required call signaling to the signaling
interface 202 to be configured for transmission as, for example, an
SS7 message.
The interworking unit 302 receives the user communications from the
first communication device 308 and the control message from the
call processor 204. In response to the control message, the
interworking unit 302 interworks the user communications to the
designated connection 306.
The ATM matrix 304 receives the user communications from the
interworking unit 302 and the control message from the call
processor 204. In response to the control message, the ATM matrix
304 connects the user communications over the designated connection
314 to the second communication device 310.
In another example, the first communication device 308 transports
user communications and call signaling. The signaling interface 202
receives the call signaling, and the interworking unit 302 receives
the user communications.
The signaling interface 202 processes the call signaling and
converts it to call information elements, such as message
parameters, that can be processed by the call processor 204. The
signaling interface 202 passes the message parameters to the call
processor 204.
The call processor 204 processes the call signaling message
parameters and determines that information is required from the
local SCP 110 to complete call processing. In this example, the
called number is an N00 number that requires translation to a ten
digit NPA-NXX number.
The call processor 204 passes a control message to the local SCP
110 requesting the information. The control message is not a TCAP
message and therefore is not required to be formatted through an
SS7 stack. In this example, the control message is transmitted to
the local SCP 110 through a backplane.
The local SCP 110 receives the control message from the call
processor 204 and processes the control message to obtain the
response information. The response information may contain the
requested information, or it may specify that the requested
information is not available or unknown.
The local SCP 110 responds to the call processor 204 with the
response information. In this example, the local SCP 110 responds
with a ten digit translated called number. The response is a
control message that is sent from the local SCP 110 to the call
processor 204. The response is not a TCAP response and therefore is
not required to be formatted through an SS7 stack. In this example,
the control message is transmitted from the local SCP 110 to the
call processor 204 through a backplane.
The call processor 204 receives and processes the information from
the local SCP 110. The call processor 204 processes the information
that is received from the local SCP 110 to determine if the NPA-NXX
of the ten digit translated called number has been flagged as a
ported number. If the call processor 204 determines that the number
has been flagged as a ported number, it initiates a TCAP query by
transmitting call message parameters to the signaling interface
202. Otherwise processing continues as normal.
The signaling interface 202 receives the message parameters from
the call processor 204 and builds, for example, an AIN 0.1 SCP TCAP
query. The signaling interface 202 transmits the TCAP query to the
LNP SCP 104.
The LNP SCP 104 receives the TCAP query and processes it. If the
LNP SCP 104 determines that the number is a ported number, it
transmits an LRN to the signaling interface 202 in, for example, an
AIN 0.1 TCAP response message. If the LNP SCP 104 determines that
the number is not a ported number, it transmits the ten digit
translated called number back to the signaling interface 202 in the
response message.
The signaling interface 202 receives the TCAP response and
processes it to obtain the message parameters. The signaling
interface 202 transmits the message parameters to the call
processor 204.
The call processor 204 receives and processes the message
parameters and determines that the call is to be connected to the
second communication device 310. In this example, the second
communication device 310 is an ATM device.
The call processor 204 selects a connection, such as a VP/VC on the
connection 304, over which the user communications will be
transmitted between the interworking unit 302 and the ATM matrix
304 and a connection, such as a VP/VC on the connection 314, over
which the user communications will be transmitted between the ATM
matrix and the second communication device 310.
The call processor 204 transmits a control message to each of the
interworking unit 302 and the ATM matrix 304 identifying the
selected connections 306 and 314. In addition, the call processor
204 transmits the required call signaling to the signaling
interface 202 to be configured for transmission.
The interworking unit 302 receives the user communications from the
first communication device 308 and the control message from the
call processor 204. In response to the control message, the
interworking unit 302 interworks the user communications to the
designated connection 306.
The ATM matrix 304 receives the user communications from the
interworking unit 302 and the control message from the call
processor 204. In response to the control message, the ATM matrix
304 connects the user communications over the designated connection
314 to the second communication device 310.
THE CONTROLLABLE ATM MATRIX
FIG. 4 illustrates an exemplary embodiment of a controllable
asynchronous transfer mode (ATM) matrix (CAM), but other CAMs that
support the requirements of the invention also are applicable. The
CAM 402 may receive and transmit ATM formatted user communications
or call signaling.
The CAM 402 preferably has a control interface 404, a controllable
ATM matrix 406, an optical carrier-M/synchronous transport signal-M
(OC-M/STS-M) interface 408, and an OC-X/STS-X interface 410. As
used herein in conjunction with OC or STS, "M" refers to an
integer, and "X" refers to an integer.
The control interface 404 receives control messages originating
from the signaling processor 412, identifies virtual connection
assignments in the control messages, and provides these assignments
to the matrix 406 for implementation. The control messages may be
received over an ATM virtual connection and through either the
OC-M/STS-M interface 408 or the OC-XISTS-X interface 410 through
the matrix 406 to the control interface 404, through either the
OC-M/STS-M interface or the OC-XISTS-X interface directly to the
control interface, or through the control interface from a
link.
The matrix 406 is a controllable ATM matrix that provides cross
connect functionality in response to control messages from the
signaling processor 412. The matrix 406 has access to virtual
path/virtual channels (VP/VCs) over which it can connect calls. For
example, a call can come in over a VP/VC through the OC-M/STS-M
interface 408 and be connected through the matrix 406 over a VP/VC
through the OC-X/STS-X interface 410 in response to a control
message received by the signaling processor 412 through the control
interface 404. Alternately, a call can be connected in the opposite
direction. In addition, the a call can be received over a VP/VC
through the OC-MISTS-M interface 408 or the OC-X/STS-X interface
410 and be connected through the matrix 406 to a different VP/VC on
the same OC-M/STS-M interface or the same OC-XISTS-X interface.
The OC-M/STS-M interface 408 is operational to receive ATM cells
from the matrix 406 and to transmit the ATM cells over a connection
to the communication device 414. The OC-M/STS-M interface 408 also
may receive ATM cells in the OC or STS format and transmit them to
the matrix 406.
The OC-X/STS-X interface 410 is operational to receive ATM cells
from the matrix 406 and to transmit the ATM cells over a connection
to the communication device 416. The OC-XISTS-X interface 410 also
may receive ATM cells in the OC or STS format and transmit them to
the matrix 406.
Call signaling may be received through and transferred from the
OC-M/STS-M interface 408. Also, call signaling may be received
through and transferred from the OC-X/STS-X interface 410. The call
signaling may be connected on a connection or transmitted to the
control interface directly or via the matrix 406.
The signaling processor 412 is configured to send control messages
to the CAM 402 to implement particular features on particular VP/VC
circuits. Alternatively, lookup tables may be used to implement
particular features for particular VP/VCs.
FIG. 5 illustrates another exemplary embodiment of a CAM which has
time division multiplex (TDM) capability, but other CAMs that
support the requirements of the invention also are applicable. The
CAM 502 may receive and transmit in-band and out-of-band signaled
calls.
The CAM 502 preferably has a control interface 504, an OC-N/STS-N
interface 506, a digital signal level 3 (DS3) interface 508, a DS1
interface 510, a DS0 interface 512, an ATM adaptation layer (AAL)
514, a controllable ATM matrix 516, an OC-M/STS-M interface 518A,
an OC-X/STS-X interface 518B, and an ISDN/GR-303 interface 520. As
used herein in conjunction with OC or STS, "N" refers to an
integer, "M" refers to an integer, and "X" refers to an
integer.
The control interface 504 receives control messages originating
from the 25 signaling processor 522, identifies DS0 and virtual
connection assignments in the control messages, and provides these
assignments to the AAL 514 or the matrix 516 for implementation.
The control messages may be received over an ATM virtual connection
and through the OC-M/STS-M interface 518A to the control interface
504, through the OC-X/STS-X interface 518B and the matrix 516 to
the control interface, or directly through the control interface
from a link.
The OC-N/STS-N interface 506, the DS3 interface 508, the DS1
interface 510, the DS0 interface 512, and the ISDN/GR-303 interface
520 each can receive user communications from a communication
device 524. Likewise, the OC-M/STS-M interface 518A and the
OC-X/STS-X interface 518B can receive user communications from the
communication devices 526 and 528.
The OC-N/STS-N interface 506 receives OC-N formatted user
communications and STS-N formatted user communications and converts
the user communications to the DS3 format. The DS3 interface 508
receives user communications in the DS3 format and converts the
user communications to the DS1 format. The DS3 interface 508 can
receive DS3s from the OC-N/STS-N interface 506 or from an external
connection. The DS1 interface 510 receives the user communications
in the DS1 format and converts the user communications to the DS0
format. The DS1 interface 510 receives DS1s from the DS3 interface
508 or from an external connection. The DS0 interface 512 receives
user communications in the DS0 format and provides an interface to
the AAL 514. The ISDN/GR-303 interface 520 receives user
communications in either the ISDN format or the GR-303 format and
converts the user communications to the DS0 format. In addition,
each interface may transmit user communications in like manner to
the communication device 524.
The OC-M/STS-M interface 518A is operational to receive ATM cells
from the AAL 514 or from the matrix 516 and to transmit the ATM
cells over a connection to the communication device 526. The
OC-M/STS-M interface 518A also may receive ATM cells in the OC or
STS format and transmit them to the AAL 514 or to the matrix
516.
The OC-X/STS-X interface 518B is operational to receive ATM cells
from the AAL 514 or from the matrix 516 and to transmit the ATM
cells over a connection to the communication device 528. The
OC-X/STS-X interface 518B also may receive ATM cells in the OC or
STS format and transmit them to the AAL 514 or to the matrix
516.
Call signaling may be received through and transferred from the
OC-N/STS-N interface 506 and the ISDN/GR-303 interface 520. Also,
call signaling may be received through and transferred from the
OC-M/STS-M interface 518A and the OC-X/STS-X interface 518B. The
call signaling may be connected on a connection or transmitted to
the control interface directly or via an interface as explained
above.
The AAL 514 comprises both a convergence sublayer and a
segmentation and reassembly (SAR) sublayer. The AAL 514 obtains the
identity of the DS0 and the ATM VP/VC from the control interface
504. The AAL 514 is operational to convert between the DS0 format
and the ATM format. AALs are known in the art, and information
about AALs is provided by International Telecommunications Union
(ITU) documents in the series of I.363, which are incorporated
herein by reference. For example, ITU document I.363.1 discusses
AAL1. An AAL for voice calls is described in U.S. Pat. No.
5,806,553 entitled "Cell Processing for Voice Transmission," which
is incorporated herein by reference.
Calls with multiple 64 Kilo-bits per second (Kbps) DS0s are known
as N.times.64 calls. If desired, the AAL 514 can be configured to
accept control messages through the control interface 504 for
N.times.64 calls. The CAM 502 is able to interwork, multiplex, and
demultiplex for multiple DS0s. A technique for processing VP/VCs is
disclosed in U.S. patent application Ser. No. 08/653,852, which was
filed on May 28, 1996, and entitled "Telecommunications System with
a Connection Processing System," and which is incorporated herein
by reference.
DS0 connections are bidirectional and ATM connections are typically
uni-directional. As a result, two virtual connections in opposing
directions typically will be required for each DS0. Those skilled
in the art will appreciate how this can be accomplished in the
context of the invention. For example, the cross-connect can be
provisioned with a second set of VP/VCs in the opposite direction
as the original set of VP/VCs.
The matrix 516 is a controllable ATM matrix that provides cross
connect functionality in response to control messages from the
signaling processor 522. The matrix 516 has access to VP/VCs over
which it can connect calls. For example, a call can come in over a
VP/VC through the OC-M/STS-M interface 518A and be connected
through the matrix 516 over a VP/VC through the OC-X/STS-X
interface 518B in response to a control message received by the
signaling processor 522 through the control interface 504.
Alternately, the matrix 516 may transmit a call received over a
VP/VC through the OC-M/STS-M interface 518A to the AAL 514 in
response to a control message received by the signaling processor
522 through the control interface 504. Communications also may
occur in opposite directions through the various interfaces.
In some embodiments, it may be desirable to incorporate digital
signal processing capabilities at, for example, the DS0 level. It
also may be desired to apply echo control to selected DS0 circuits.
In these embodiments, a signal processor may be included. The
signaling processor 522 is configured to send control messages to
the CAM 502 to implement particular features on particular DS0 or
VP/VC circuits. Alternatively, lookup tables may be used to
implement particular features for particular circuits or
VP/VCs.
It will be appreciated from the teachings above for the CAMs and
for the teachings below for the ATM interworking units, that the
above described CAMs can be adapted for modification to transmit
and receive other formatted communications such as synchronous
transport module (STM) and European level (E) communications. For
example, the OC/STS, DS3, DS1, DS0, and ISDN/GR-303 interfaces can
be replaced by STM electrical/optical (E/O), E3, E1, E0, and
digital private network signaling system (DPNSS) interfaces,
respectively.
THE ATM INTERWORKING UNIT
FIG. 6 illustrates an exemplary embodiment of an interworking unit
which is an ATM interworking unit 602 suitable for the present
invention for use with a SONET system. Other interworking units
that support the requirements of the invention also are applicable.
The ATM interworking unit 602 may receive and transmit in-band and
out-of-band calls.
The ATM interworking unit 602 preferably has a control interface
604, an OC-N/STS-N interface 606, a DS3 interface 608, a DS1
interface 610, a DS0 interface 612, a signal processor 614, an AAL
616, an OC-M/STS-M interfaced, and an ISDN/GR-303 interface 620. As
used herein in conjunction with OC or STS, "N" refers to an
integer, and "M" refers to an integer.
The control interface 604 receives control messages originating
from the signaling processor 622, identifies DS0 and virtual
connection assignments in the control messages, and provides these
assignments to the AAL 616 for implementation. The control messages
are received over an ATM virtual connection and through the
OC-M/STS-M interface 618 to the control interface 604 or directly
through the control interface from a link.
The OC-N/STS-N interface 606, the DS3 interface 608, the DS1
interface 610, the DS0 interface 612, and the ISDN/GR-303 interface
620 each can receive user communications from a communication
device 624. Likewise, the OC-M/STS-M interface 618 can receive user
communications from a communication device 626.
The OC-N/STS-N interface 606 receives OC-N formatted user
communications and STS-N formatted user communications and
demultiplexes the user communications to the DS3 format. The DS3
interface 608 receives user communications in the DS3 format and
demultiplexes the user communications to the DS1 format. The DS3
interface 608 can receive DS3s from the OC-N/STS-N interface 606 or
from an external connection. The DS1 interface 610 receives the
user communications in the DS1 format and demultiplexes the user
communications to the DS0 format. The DS1 interface 610 receives
DS1s from the DS3 interface 608 or from an external connection. The
DS0 interface 612 receives user communications in the DS0 format
and provides an interface to the AAL 616. The ISDN/GR-303 interface
620 receives user communications in either the ISDN format or the
GR-303 format and converts the user communications to the DS0
format. In addition, each interface may transmit user
communications in like manner to the communication device 624.
The OC-M/STS-M interface 618 is operational to receive ATM cells
from the AAL 616 and to transmit the ATM cells over the connection
to the communication device 626. The OC-M/STS-M interface 618 also
may receive ATM cells in the OC or STS format and transmit them to
the AAL 616.
Call signaling may be received through and transferred from the
OC-N/STS-N interface 606 and the ISDN/GR-303 interface 620. Also,
call signaling may be received through and transferred from the
OC-M/STS-M interface 618. The call signaling may be connected on a
connection or transmitted to the control interface directly or via
another interface as explained above.
The AAL 616 comprises both a convergence sublayer and a
segmentation and reassembly (SAR) sublayer. The AAL 616 obtains the
identity of the DS0 and the ATM VP/VC from the control interface
604. The AAL 616 is operational to convert between the DS0 format
and the ATM format.
If desired, the AAL 616 can be configured to accept control
messages through the control interface 604 for N.times.64 calls.
The ATM interworking unit 602 is able to interwork, multiplex, and
demultiplex for multiple DS0s.
DS0 connections are bidirectional and ATM connections are typically
uni-directional. As a result, two virtual connections in opposing
directions typically will be required for each DS0. Those skilled
in the art will appreciate how this can be accomplished in the
context of the invention. For example, the cross-connect can be
provisioned with a second set of VP/VCs in the opposite direction
as the original set of VP/VCs.
In some embodiments, it may be desirable to incorporate digital
signal processing capabilities at the DS0 level. It may also be
desired to apply echo control to selected DS0 circuits. In these
embodiments, a signal processor 614 is included either separately
(as shown) or as a part of the DS0 interface 612. The signaling
processor 622 is configured to send control messages to the ATM
interworking unit 602 to implement particular features on
particular DS0 circuits. Alternatively, lookup tables may be used
to implement particular features for particular circuits or
VP/VCs.
FIG. 7 illustrates another exemplary embodiment of an interworking
unit which is an ATM interworking unit 702 suitable for the present
invention for use with an SDH system. The ATM interworking unit 702
preferably has a control interface 704, an STM-N electrical/optical
(E/O) interface 706, an E3 interface 708, an E1 interface 710, an
E0 interface 712, a signal processor 714, an AAL 716, an STM-M
electrical/optical (E/O) interface 718, and a DPNSS interface 720.
As used herein in conjunction with STM, "N" refers to an integer,
and "M" refers to an integer.
The control interface 704 receives control messages from the
signaling processor 722, identifies E0 and virtual connection
assignments in the control messages, and provides these assignments
to the AAL 716 for implementation. The control messages are
received over an ATM virtual connection and through the STM-M
interface 718 to the control interface 604 or directly through the
control interface from a link.
The STM-N E/O interface 706, the E3 interface 708, the E1 interface
710, the E0 interface 712, and the DPNSS interface 720 each can
receive user communications from a second communication device 724.
Likewise, the STM-M E/O interface 718 can receive user
communications from a third communication device 726.
The STM-N E/O interface 706 receives STM-N electrical or optical
formatted user communications and converts the user communications
from the STM-N electrical or STM-N optical format to the E3 format.
The E3 interface 708 receives user communications in the E3 format
and demultiplexes the user communications to the E1 format. The E3
interface 708 can receive E3s from the STM-N E/O interface 706 or
from an external connection. The E1 interface 710 receives the user
communications in the E1 format and demultiplexes the user
communications to the E0 format. The E1 interface 710 receives E1s
from the STM-N E/O interface 706 or the E3 interface 708 or from an
external connection. The E0 interface 712 receives user
communications in the E0 format and provides an interface to the
AAL 716. The DPNSS interface 720 receives user communications in
the DPNSS format and converts the user communications to the E0
format. In addition, each interface may transmit user
communications in a like manner to the communication device
724.
The STM-M E/O interface 718 is operational to receive ATM cells
from the AAL 716 and to transmit the ATM cells over the connection
to the communication device 726. The STM-M E/O interface 718 may
also receive ATM cells in the STM-M E/O format and transmit them to
the AAL 716. Call signaling may be received through and transferred
from the STM-N E/O interface 706 and the DPNSS interface 720. Also,
call signaling may be received through and transferred from the
STM-M E/O interface 718. The call signaling may be connected on a
connection or transmitted to the control interface directly or via
another interface as explained above.
The AAL 716 comprises both a convergence sublayer and a
segmentation and reassembly (SAR) sublayer. The AAL obtains the
identity of the E0 and the ATM VP/VC from the control interface
704. The AAL 716 is operational to convert between the E0 format
and the ATM format, either in response to a control instruction or
without a control instruction. AAL's are known in the art. If
desired, the AAL 716 can be configured to receive control messages
through the control interface 704 for N.times.64 user
communications.
E0 connections are bi-directional and ATM connections typically are
unidirectional. As a result, two virtual connections in opposing
directions typically will be required for each E0. Those skilled in
the art will appreciate how this can be accomplished in the context
of the invention.
In some instances, it may be desirable to incorporate digital
signal processing capabilities at the E0 level. Also, it may be
desirable to apply echo control. In these embodiments, a signal
processor 714 is included either separately (as shown) or as a part
of the E0 interface 712. The signaling processor 722 is configured
to send control messages to the ATM interworking unit 702 to
implement particular features on particular circuits.
Alternatively, lookup tables may be used to implement particular
features for particular circuits or VP/VCs.
THE SIGNALING PROCESSOR
The signaling processor receives and processes telecommunications
call signaling, control messages, and customer data to select
connections that establish communication paths for calls. In the
preferred embodiment, the signaling processor processes SS7
signaling to select connections for a call. An example of call
processing in a call processor and the associated maintenance that
is performed for call processing is described in a U.S. patent
application Ser. No. 09/026,766 entitled "System and Method for
Treating a Call for Call Processing," which is incorporated herein
by reference.
In addition to selecting connections, the signaling processor
performs many other functions in the context of call processing. It
not only can control routing and select the actual connections, but
it also can validate callers, control echo cancellers, generate
accounting information, invoke intelligent network functions,
access remote databases, manage traffic, and balance network loads.
One skilled in the art will appreciate how the signaling processor
described below can be adapted to operate in the above
embodiments.
FIG. 8 depicts an embodiment of a signaling processor. Other
versions also are contemplated. In the embodiment of FIG. 8, the
signaling processor 802 has a signaling interface 804, a call
processing control system 806 (CPCS), and a call processor 808. It
will be appreciated that the signaling processor 802 may be
constructed as modules in a single unit or as multiple units.
The signaling interface 804 is coupled externally to signaling
systems--preferably to signaling systems having a message transfer
part (MTP), an ISDN user part (ISUP), a signaling connection
control part (SCCP), an intelligent network application part
(INAP), and a transaction capabilities application part (TCAP). The
signaling interface 804 preferably is a platform that comprises an
MTP level 1 810, an MTP level 2 812, an MTP level 3 814, an SCCP
process 816, an ISUP process 818, and a TCAP process 820. The
signaling interface 804 also has INAP functionality.
The signaling interface 804 may be linked to a communication device
(not shown). For example, the communication device may be an SCP
which is queried by the signaling interface with a TCAP query to
obtain additional call-associated data. The answer message may have
additional information parameters that are required to complete
call processing. The communication device also may be an STP or
other device.
The signaling interface 804 is operational to transmit, process,
and receive call signaling. The TCAP, SCCP, ISUP, and INAP
functionality use the services of the MTP to transmit and receive
the messages. Preferably, the signaling interface 804 transmits and
receives SS7 messages for MTP, TCAP, SCCP, and ISUP. Together, this
functionality is referred to as an "SS7 stack," and it is well
known. The software required by one skilled in the art to configure
an SS7 stack is commercially available. One example is the OMNI SS7
stack from Dale, Gesek, McWilliams & Sheridan, Inc. (the
DGM&S company).
The processes of the signaling interface 804 process information
that is received in message signal units (MSUs) and convert the
information to call information elements that are sent to the call
processor 808 to be processed. A call information element may be,
for example, an ISUP IAM message parameter from the MSU. The
signaling interface 804 strips the unneeded header information from
the MSU to isolate the message information parameters and passes
the parameters to the call processor 808 as the call information
elements. Examples of these parameters are the called number, the
calling number, and user service information. Other examples of
messages with information elements are an ANM, an ACM, an REL, an
RLC, and an INF. In addition, call information elements are
transferred from the call processor 808 back to the signaling
interface 804, and the information elements are reassembled into
MSUs and transferred to a signaling point.
The CPCS 806 is a management and administration system. The CPCS
806 is the user interface and external systems interface into the
call processor 808.
The CPCS 806 serves as a collection point for call-associated data
such as logs, operational measurement data, statistical
information, accounting information, and other call data. The CPCS
806 can configure the call-associated data and/or transmit it to
reporting centers.
The CPCS 806 accepts data, such as the translations, from a source
such as an operations system and updates the data in the tables in
the call processor 808. The CPCS 806 ensures that this data is in
the correct format prior to transferring the data to the call
processor 808. The CPCS 806 also provides configuration data to
other devices including the call processor 808, the signaling
interface 804, the interworking unit (not shown), and the
controllable ATM matrix (not shown). In addition, the CPCS 806
provides for remote control of call monitoring and call tapping
applications from the call processor 808.
The CPCS 806 also serves as a collection point for alarms. Alarm
information is transferred to the CPCS 806. The CPCS 806 then
transports alarm messages to the required communication device. For
example, the CPCS 806 can transport alarms to an operations
center.
The CPCS 806 also has a human-machine interface (HMI). This allows
a person to log onto the CPCS 806 and manage data tables or review
data tables in the CPCS or provide maintenance services.
The call processor 808 processes call signaling and controls an ATM
interworking unit, such as an ATM interworking multiplexer (mux)
that performs interworking of DS0s and VP/VCs, and an ATM matrix.
However, the call processor 808 may control other communications
devices and connections in other embodiments.
The call processor 808 comprises a control platform 822 and an
application platform 824. Each platform 822 and 824 is coupled to
the other platform.
The control platform 822 is comprised of various external
interfaces including an interworking unit interface, a controllable
ATM matrix, an echo interface, a resource control interface, a call
information interface, and an operations interface. The control
platform 822 is externally coupled to an interworking unit control,
a controllable ATM matrix control, an echo control, a resource
control, accounting, and operations. The interworking unit
interface exchanges messages with at least one interworking unit.
These messages comprise DS0 to VP/VC assignments, acknowledgments,
and status information. The controllable ATM matrix interface
exchanges messages with at least one controllable ATM matrix. These
messages comprise DS0 to VP/VC assignments, VP/VC to VP/VC
assignments, acknowledgments, and status information. The echo
control interface exchanges messages with echo control systems.
Messages exchanged with echo control systems might include
instructions to enable or disable echo cancellation on particular
DS0s, acknowledgments, and status information.
The resource control interface exchanges messages with external
resources. Examples of such resources are devices that implement
continuity testing, encryption, compression, tone
detection/transmission, voice detection, and voice messaging. The
messages exchanged with resources are instructions to apply the
resource to particular DS0s, acknowledgments, and status
information. For example, a message may instruct a continuity
testing resource to provide a loopback or to send and detect a tone
for a continuity test.
The call information interface transfers pertinent call information
to a call information processing system, such as to the CPCS 806.
Typical call information includes accounting information, such as
the parties to the call, time points for the call, and any special
features applied to the call. One skilled in the art will
appreciate how to produce the software for the interfaces in the
control platform 822.
The application platform 824 processes signaling information from
the signaling interface 804 to select connections. The identity of
the selected connections are provided to the control platform 822
for the interworking unit interface and/or for the controllable ATM
matrix interface. The application platform 824 is responsible for
validation, translation, routing, call control, exceptions,
screening, and error handling. In addition to providing the control
requirements for the interworking unit and the controllable ATM
matrix, the application platform 824 also provides requirements for
echo control and resource control to the appropriate interface of
the control platform 822. In addition, the application platform 824
generates signaling information for transmission by the signaling
interface 804. The signaling information might be for ISUP, INAP,
or TCAP messages to external network elements. Pertinent
information for each call is stored in an enhanced circuit data
block (ECDB) for the call. The ECDB can be used for tracking and
accounting the call.
The application platform 824 preferably operates in general accord
with the Basic Call State Model (BCSM) defined by the ITU. An
instance of the BCSM is created to handle each call. The BCSM
includes an originating process and a terminating process. The
application platform 824 includes a service switching function
(SSF) that is used to invoke the service control function (SCF).
Typically, the SCF is contained in an SCP. The SCF is queried with
TCAP or INAP messages that are transported by the signaling
interface 804 and which are initiated with information from the SSF
in the application platform 824. The originating or terminating
processes will access remote databases with intelligent network
(IN) functionality via the SSF.
Software requirements for the application platform 824 can be
produced in specification and description language (SDL) defined in
ITU-T Z.100 or similar logic or description languages. The SDL can
be converted into C code. A real time case tool such as SDT from
Telelogic, Inc. or Object Time from Object Time, Inc. can be used.
Additional C and C++ code can be added as required to establish the
environment. It will be appreciated that other software languages
and tools may be used.
The call processor 808 can be comprised of the above-described
software loaded onto a computer. The computer can be a generally
available fault-tolerant Unix computer, such as those provided by
Sun, Tandem, or Hewlett Packard. It may be desirable to utilize the
multi-threading capability of a Unix operating system.
From FIG. 8, it can be seen that the application platform 824
processes signaling information to control numerous systems and
facilitate call connections and services. The SS7 signaling is
exchanged between the call processor 808 and external components
through the signaling interface 804, and control information is
exchanged with external systems through the control platform 822.
Advantageously, the signaling interface 804, the CPCS 806, and the
call processor 808 are not integrated into a switch central
processing unit (CPU) that is coupled to a switching matrix. Unlike
an SCP, the components of the signaling processor 802 are capable
of processing ISUP messages independently of TCAP queries.
SS7 MESSAGE DESIGNATIONS
SS7 messages are well known. Designations for various SS7 messages
commonly are used. Those skilled in the art are familiar with the
following message designations: ACM--Address Complete Message
ANM--Answer Message BLO--Blocking BLA--Blocking Acknowledgment
CPG--Call Progress CGB--Circuit Group Blocking CGBA--Circuit Group
Blocking Acknowledgment GRS--Circuit Group Reset. GRA--Circuit
Group Reset Acknowledgment CGU--Circuit Group Unblocking
CGUA--Circuit Group Unblocking Acknowledgment CQM--Circuit Group
Query CQR--Circuit Group Query Response CRM--Circuit Reservation
Message CRA--Circuit Reservation Acknowledgment CVT--Circuit
Validation Test CVR--Circuit Validation Response CFN--Confusion
COT--Continuity CCR--Continuity Check Request EXM--Exit Message
INF--Information INR--Information Request IAM--Initial Address
Message LPA--Loop Back Acknowledgment PAM--Pass Along Message
REL--Release RLC--Release Complete RSC--Reset Circuit RES--Resume
SUS--Suspend UBL--Unblocking UBA--Unblocking Acknowledgment
UCIC--Unequipped Circuit Identification Code.
CALL PROCESSOR TABLES
Call processing typically entails two aspects. First, an incoming
or "originating" connection is recognized by an originating call
process. For example, the initial connection that a call uses to
enter a network is the originating connection in that network.
Second, an outgoing or "terminating" connection is selected by a
terminating call process. For example, the terminating connection
is coupled to the originating connection in order to extend the
call through the network. These two aspects of call processing are
referred to as the originating side of the call and the terminating
side of the call.
FIG. 9 depicts an exemplary data structure preferably used by the
call processor 802 of FIG. 8 to execute the BCSM. This is
accomplished through a series of tables that point to one another
in various ways. The pointers typically are comprised of next
function and next label designations. The next function points to
the next table, and the next label points to an entry or a range of
entries in that table. It will be appreciated that the pointers for
the main call processing are illustrated in FIG. 9.
The primary data structure has a TDM trunk circuit table 902, an
ATM trunk circuit table 904, a trunk group table 906, a carrier
table 908, an exception table 910, an originating line information
(OLI) table 912, an automatic number identification (ANI) table
914, a called number screening table 916, a called number table
918, a routing table 920, a trunk group class of service (COS)
table 922, and a message mapping table 924. Also included in the
data structure are a day of year table 926, a day of week table
928, a time of day table 930, and a time zone table 932.
The TDM trunk circuit table 902 contains information required to
provision the TDM side of a connection from the call processor
site. Each circuit on the TDM side of a connection has an entry.
The TDM trunk circuit table 902 is accessed from the trunk group
table 906 or an external call process, and it points to the trunk
group table.
The ATM trunk circuit table 904 contains information required to
provision the ATM side of a connection. Typically, one record
appears in this table per ATM trunk group. Although, the system can
be configured alternately for multiple records per trunk group. The
ATM trunk circuit table 904 is accessed from the trunk group table
906 or an external call process, and it points to the trunk group
table.
The trunk group table 906 contains information that is required to
build trunk groups out of different trunk members identified in the
TDM and ATM trunk circuit tables 902 and 904. The trunk group table
906 contains information related to the originating and terminating
trunk groups. The trunk group table 906 typically points to the
carrier table 908. Although, the trunk group table 906 may point to
the exception table 910, the OLI table 912, the ANI table 914, the
called number screening table 916, the called number table 918, the
routing table 920, the day of year table 926, the day of week table
928, the time of day table 930, and the treatment table (see FIG.
10).
For default processing of an IAM of an outgoing call in the forward
direction, when the call process determines call setup and routing
parameters for user communications on the originating portion, the
trunk group table 906 is the next table after the TDM and ATM trunk
circuit tables 902 and 904, and the trunk group table points to the
carrier table 908. For default processing of an IAM of an outgoing
call in the forward direction, when the call process determines
call setup and routing parameters for user communications on the
terminating portion, the trunk group table 906 is the next table
after the routing table 920, and the trunk group table points to
the TDM or ATM trunk circuit table 902 or 904. For default
processing of an ACM or an ANM of an outgoing call in the
originating direction, when the call process determines parameters
for signaling, the trunk group table 906 is the next table after
the TDM or ATM trunk circuit table 902 or 904, and the trunk group
table points to the message mapping table 924. It will be
appreciated that this is the default method, and, as explained
herein, other implementations of table processing occur.
The carrier table 908 contains information that allows calls to be
screened based, at least in part, on the carrier information
parameter and the carrier selection parameter. The carrier table
908 typically points to the exception table 910. Although, the
carrier table 908 may point to the OLI table 912, the ANI table
914, the called number screening table 916, the called number table
918, the routing table 920, the day of year table 926, the day of
week table 928, the time of day table 930, the treatment table (see
FIG. 10), and the database services table (see FIG. 11).
The exception table 910 is used to identify various exception
conditions related to the call that may influence the routing or
handling of the call. The exception table 910 contains information
that allows calls to be screened based, at least in part, on the
called party number and the calling party's category. The exception
table 910 typically points to the OLI table 912. Although, the
exception table 910 can point to the ANI table 914, the called
number screening table 916, the called number table 918, the
routing table 920, the day of year table 926, the day of week table
928, the time of day table 930, the call rate table, the percent
control table, the treatment table (see FIG. 10), and the database
services table (see FIG. 11).
The OLI table 912 contains information that allows calls to be
screened based, at least in part, on originating line information
in an AM. The OLI table 912 typically points to the ANI table 914.
Although, the OLI table can point to the called number screening
table 916, the called number table 918, the routing table 920, the
day of year table 926, the day of week table 928, the time of day
table 930, and the treatment table (see FIG. 10).
The ANI table 914 is used to identify any special characteristics
related to the caller's number, which is commonly known as
automatic number identification. The ANI table 914 is used to
screen and validate an incoming ANI. ANI specific requirements such
as queuing, echo cancellation, time zone, and treatments can be
established. The ANI table 914 typically points to the called
number screening table 916. Although, the ANI table 914 can point
to the called number table 918, the routing table 920, the day of
year table 926, the day of week table 928, the time of day table
930, and the treatment table (see FIG. 10).
The called number screening table 916 is used to screen called
numbers.
The called number screening table 916 determines the disposition of
the called number and the nature of the called number. The called
number screening table 916 is used to provide the trigger detection
point (TDP) for an AIN SCP TCAP query. It is used, for example,
with the local number portability (LNP) feature. The called number
screening table can invoke a TCAP. The called number screening
table 916 typically points to the called number table 918.
Although, the called number screening table 916 can point to the
routing table 920, the treatment table, the call rate table, the
percent table (see FIG. 10), and the database services table (see
FIG. 11).
The called number table 918 is used to identify routing
requirements based on, for example, the called number. This will be
the case for standard calls. The called number table 918 typically
points to the routing table 910. In addition, the called number
table 926 can be configured to alternately point to the day of year
table 926. The called number table 918 can also point to the
treatment table (see FIG. 10) and the database services table (see
FIG. 11).
The routing table 920 contains information relating to the routing
of a call for various connections. The routing table 920 typically
points to the treatment table (see FIG. 10). Although, the routing
table also can point to the trunk group table 906 and the database
services table (see FIG. 11).
For default processing of an IAM of an outgoing call in the forward
direction, when the call process determines call setup and routing
parameters for user communications, the routing table 920 is the
next table after the called number table 918, and the routing table
points to the trunk group table 906. For default processing of an
LAM of an outgoing call in the forward direction, when the call
process determines parameters for signaling, the routing table 920
is the next table after the called number table 918, and the
routing table points to the message mapping table 924. It will be
appreciated that this is the default method, and, as explained
herein, other implementations of table processing occur.
The trunk group COS table 922 contains information that allows
calls to be routed differently based on the class of service
assigned to the originating trunk group and to the terminating
trunk group. The trunk group COS table can point to the routing
table 920 or the treatment table (see FIG. 10).
When the trunk group COS table 922 is used in processing, after the
routing table 920 and the trunk group table 906 are processed, the
trunk group table points to the trunk group COS table. The trunk
group COS table points back to the routing table 920 for further
processing. Processing then continues with the routing table 920
which points to the trunk group table 906, and the trunk group
table which points to the TDM or ATM trunk circuit table 902 or
904. It will be appreciated that this is the default method, and,
as explained herein, other implementations of table processing
occur.
The message mapping table 924 is used to provide instructions for
the formatting of signaling messages from the call processor. It
typically can be accessed by the routing table 920 or the trunk
group table 906 and typically determines the format of the outgoing
messages leaving the call processor.
The day of year table 926 contains information that allows calls to
be routed differently based.on the day of the year. The day of year
table typically points to the routing table 920 and references the
time zone table 932 for information. The day of year table 926 also
can point to the called number screening table 916, the called
number table 918, the routing table 920, the day of week table 928,
the time of day table 930, and the treatment table (see FIG.
10).
The day of week table 928 contains information that allows calls to
be routed differently based on the day of the week. The day of week
table typically points to the routing table 920 and references the
time zone table 932 for information. The day of week table 928 also
can point to the called number screening table 916, the called
number table 918, the time of day table 930, and the treatment
table (see FIG. 10).
The time of day table 930 contains information that allows calls to
be routed differently based on the time of the day. The time of day
table 930 typically points to the routing table 920 and references
the time zone table 932 for information. The time of day table 930
also can point to the called number screening table 916, the called
number table 918, and the treatment table (see FIG. 10). The time
zone table 932 contains information that allows call processing to
determine if the time associated with the call processing should be
offset based on the time zone or daylight savings time. The time
zone table 932 is referenced by, and provides information to, the
day of year table 926, the day of week table 928, and the time of
day table 930.
FIG. 10 is an overlay of FIG. 9. The tables from FIG. 9 are
present. However, for clarity, the table's pointers have been
omitted, and some tables have not been duplicated in FIG. 10. FIG.
10 illustrates additional tables that can be accessed from the
tables of FIG. 9. These include an outgoing release table 1002, a
treatment table 1004, a call rate table 1006, and a percent control
table 1008, and time/date tables 1010.
The outgoing release table 1002 contains information that allows
call processing to determine how an outgoing release message is to
be formatted. The outgoing release table 1002 typically points to
the treatment table 1006.
The treatment table 1004 identifies various special actions to be
taken in the course of call processing. For example, based on the
incoming trunk group or ANI, different treatments or cause codes
are used to convey problems to the called and calling parties. This
typically will result in the transmission of a release message
(REL) and a cause value. The treatment table 1004 typically points
to the outgoing release table 1002 and the database services table
(see FIG. 11).
The call rate table 1006 contains information that is used to
control call attempts on an attempt per second basis. Preferably,
attempts from 100 per second to 1 per minute are programmable. The
call rate table 1006 typically points to the called number
screening table 916, the called number table 918, the routing table
920, and the treatment table 1004.
The percent control table 1008 contains information that is used to
control call attempts based upon a percent value of the traffic
that is processed through call processing. The percent control
table 1008 typically points to the called number screening table
916, the called number table 918, the routing table 920, and the
treatment table 1004.
The date/time tables 1010 have been identified in FIG. 9 as the day
of year table 926, the day of week table 928, the time of day table
926, and the time zone table 932. They are illustrated in FIG. 10
as a single location for ease and clarity but need not be so
located.
FIG. 11 is an overlay of FIGS. 9-10. The tables from FIGS. 9-10 are
present. However, for clarity, the table's pointers have been
omitted, and some tables have not been duplicated in FIG. 11.
FIG. 11 illustrates additional tables that can be accessed from the
tables of FIGS. 9-10 and which are directed to the TCAP and the
SCCP message processes. These include a database services table
1102, a signaling connection control part (SCCP) table 1104, an
intermediate signaling network identification (ISNI) table 1106, a
transaction capabilities application part (TCAP) table 1108, and an
advanced intelligent network (AIN) event parameters table 1110.
The database services table 1102 contains information about the
type of database service requested by call processing. The database
services table 1102 references and obtains information from the
SCCP table 1104 and the TCAP table 1108. After the database
function is performed, the call is returned to normal call
processing. The database services table 1102 points to the called
number table 918.
The SCCP table 1104 contains information and parameters required to
build an SCCP message. The SCCP table 1104 is referenced by the
database services table 1102 and provides information to the
database services table.
The ISNI table 1106 contains network information that is used for
routing SCCP message to a destination node. The ISNI table 1106 is
referenced by the SCCP table 1104 and provides information to the
SCCP table.
The TCAP table 1108 contains information and parameters required to
build a TCAP message. The TCAP table 1108 is referenced by the
database services table 1102 and provides information to the
database services table.
The AIN event parameters table 1110 contains information and
parameters that are included in the parameters portion of a TCAP
event message. The AIN event parameters table 1110 is referenced by
the TCAP table 1108 and provides information to the TCAP table.
FIG. 12 is an overlay of FIGS. 9-11. The tables from FIGS. 9-11 are
present. However, for clarity, the tables have not been duplicated
in FIG. 12. FIG. 12 illustrates additional tables that can be used
to setup the call process so that the tables of FIGS. 9-11 may be
used. These setup tables 1202 include a site office table 1204, an
external echo canceller table 1206, an interworking unit (IWU)
table 1208, a controllable ATM matrix (CAM) interface table 1210,
and a controllable ATM matrix (CAM) table 1212.
The site office table 1204 contains information which lists
office-wide parameters, some of which are information-based and
others which affect call processing. The site office table 1204
provides information to the call processor or switch during
initialization or other setup procedures, such as population of
data or transfer of information to one or more memory locations for
use during call processing.
The external echo canceller 1206 contains information that provides
the interface identifier and the echo canceller type when an
external echo canceller is required. The external echo canceller
table 1206 provides information to the call processor or switch
during initialization or other setup procedures, such as population
of data or transfer of information to one or more memory locations
for use during call processing.
The IWU table 1208 contains the internet protocol (IP)
identification numbers for interfaces to the interworking units at
the call processor or switch site. The IWU table 1208 provides
information to the call processor or switch during initialization
or other setup procedures, such as population of data or transfer
of information to one or more memory locations for use during call
processing.
The CAM interface table 1210 contains information for the logical
interfaces associated with the CAM. The CAM interface table 1210
provides information to the call processor or switch during
initialization or other setup procedures, such as population of
data or transfer of information to one or more memory locations for
use during call processing.
The CAM table 1212 contains information associated with the logical
and physical setup properties of the CAM. The CAM table 1212
provides information to the call processor or switch during
initialization or other setup procedures, such as population of
data or transfer of information to one or more memory locations for
use during call processing.
FIGS. 13-42 depict examples of the various tables described above.
It will be appreciated that other versions of tables may be used.
In addition, information from the identified tables may be combined
or changed to form different tables.
FIG. 13 depicts an example of a TDM trunk circuit table. The TDM
trunk circuit table is used to access information about the
originating circuit for originating circuit call processing. It
also is used to provide information about the terminating circuit
for terminating circuit call processing. The trunk group number of
the circuit associated with the call is used to enter the table.
The group member is the second entry that is used as a key to
identify or fill information in the table. The group member
identifies the member number of the trunk group to which the
circuit is assigned, and it is used for the circuit selection
control.
The table also contains the trunk circuit identification code
(TCIC). The TCIC identifies the trunk circuit which is typically a
DS0. The echo canceller (EC) label entry identifies the echo
canceller, if any, which is connected to the circuit. The
interworking unit (IWU) label and the interworking unit (IWU) port
identify the hardware location and the port number, respectively,
of the interworking unit. The DS1/E1 label and the DS1/E1 channel
denote the DS1 or the E1 and the channel within the DS1 or E1,
respectively, that contains the circuit. The initial state
specifies the state of the circuit when it is installed. Valid
states include blocked if the circuit is installed and blocked from
usage, unequipped if the circuit is reserved, and normal if the
circuit is installed and available from usage.
FIG. 14 depicts an example of an ATM trunk circuit table. The ATM
trunk circuit table is used to access information about the
originating circuit for originating circuit call processing. It
also is used to provide information about the terminating circuit
for terminating circuit call processing.
The trunk group number of the circuit associated with the call is
used to enter the table. The group size denotes the number of
members in the trunk group. The starting trunk circuit
identification code (TCIC) is the starting TCIC for the trunk
group, and it is used in the routing label of an ISUP message. The
transmit interface label identifies the hardware location of the
virtual path on which the call will be transmitted. The transmit
interface label may designate either an interworking unit interface
or a CAM interface for the designated trunk members. The transmit
virtual path identifier (VPI) is the VP that will be used on the
transmission circuit side of the call. The receive interface label
identifies the hardware location of the virtual path on which the
call will be received. The receive interface label may designate
either an interworking unit interface or a CAM interface for the
designated trunk members. The receive virtual path identifier (VPI)
is the VP that will be used on the reception circuit side of the
call. The initial state specifies the state of the circuit when it
is installed. Valid states include blocked if the circuit is
installed and blocked from usage, unequipped if the circuit is
reserved, and normal if the circuit is installed and available from
usage.
FIG. 15A depicts an example of a trunk group table. The trunk group
number of the trunk group associated with the circuit is used to
key into the trunk group table. The administration information
field is used for information purposes concerning the trunk group
and typically is not used in call processing. The associated point
code is the point code for the far end switch or call processor to
which the trunk group is connected. The common language location
identifier (CLLI) entry is a standardized Bellcore entry for the
associated office to which the trunk group is connected. The trunk
type identifies the type of the trunk in the trunk group. The trunk
type may be a TDM trunk, an ATM trunk from the interworking unit,
or an ATM trunk from the CAM.
The associated numbering plan area (NPA) contains information
identifying the switch from which the trunk group is originating or
to which the trunk group is terminating. The associated
jurisdiction information parameter (JIP) contains information
identifying the switch from which the trunk group is originating or
to which the trunk group is terminating. If an ISUP JIP is not
received in an IAM, the default JIP is a value recorded on the call
processor ECDB. If an incoming LAM does not have a JIP, call
processing will populate the JIP of the outgoing IAM with the
default value from the trunk group table. If a JIP is not data
filled, an outgoing JIP is not transmitted.
The time zone label identifies the time zone that should be used
when computing a local date and a local time for use with a day of
year table, the day of week table, and the time of day table. The
echo canceller information field describes the trunk group echo
cancellation requirements. Valid entries for the echo canceller
information include normal for a trunk group that uses internal
echo cancellation, external for a trunk group that requires
external echo cancellers, and disable for a trunk group that
requires no echo cancellation for any call passing over the
group.
FIG. 15B is a continuation of FIG. 15A for the trunk group table.
The satellite entry specifies that the trunk group for the circuit
is connected through a satellite. If the trunk group uses too many
satellites, then a call should not use the identified trunk group.
This field is used in conjunction with the nature of connection
satellite indicator field from the incoming IAM to determine if the
outgoing call can be connected over this trunk group. The select
sequence indicates the methodology that will be used to select a
connection. Valid entries for the select sequence field include the
following: most idle, least idle, ascending, or descending. The
interworking unit (IWU) priority signifies that outgoing calls will
attempt to use a trunk circuit on the same interworking unit before
using a trunk circuit on a different interworking unit.
Glare resolution indicates how a glare situation is to be resolved.
Glare is the dual seizure of the same circuit. If the glare
resolution entry is set to "even/odd," the switch or the call
processor with the higher point code value will control the even
number TCICs within the trunk group. The switch or call processor
with the lower point code value will control the odd number TCICs.
If the glare resolution entry is set to "all," the call processor
controls all of the TCICs within the trunk group. If the glare
resolution entry is set to "none," the call processor will have no
glare control and will yield to all double seizures within the
trunk group.
Continuity control indicates whether continuity is to be checked.
Continuity for outgoing calls on the originating call processor are
controlled on a trunk group basis. This field specifies whether
continuity is not required or whether continuity is required and
the frequency of the required check. The field identifies a
percentage of the calls that require continuity check.
The reattempt entry specifies how many times the outgoing call will
be reattempted using a different circuit from the same trunk group
after a continuity check failure, a glare, or other connection
failure. The ignore local number portability (LNP) information
specifies whether or not the incoming LNP information is ignored.
The treatment label is a label into the treatment table for the
trunk group used on the call. Because specific trunk group
connections may require specific release causes or treatments for a
specific customer, this field identifies the type of treatment that
is required. The message mapping label is a label into the message
mapping table which specifies the backward message configuration
that will be used on the trunk group.
FIG. 15C is a continuation of FIG. 15B for the trunk group table.
The queue entry signifies that the terminating part of the trunk
group is capable of queuing calls originating from a subscriber
that called a number which terminates in this trunk group. The ring
no answer entry specifies whether the trunk group requires ring no
answer timing. If the entry is set to 0, the call processing will
not use the ring no answer timing for calls terminated on the trunk
group. A number other than 0 specifies the ring no answer timing in
seconds for calls terminating on this trunk group. The voice path
cut through entry identifies how and when the terminating call's
voice path will be cut through on the trunk group. The options for
this field include the following: connect for a cut through in both
directions after receipt of an ACM, answer for cut through in the
backward direction upon receipt of an ACM, then cut through in the
forward direction upon receipt of an ANM, or immediate for cut
through in both directions immediately after an IAM has been
sent.
The originating class of service (COS) label provides a label into
a class of service table that determines how a call is handled
based on the combination of the originating COS and the terminating
COS from another trunk group. Based on the combination of this
field and the terminating COS of another trunk group's field, the
call will be handled differently. For example, the call may be
denied, route advanced, or otherwise processed. The terminating
class of service (COS) label provides a label into a class of
service table that determines how a call is handled based on the
combination of the originating COS from another trunk group and the
terminating COS from the present trunk group. Based on a
combination of this field and the originating COS the call will be
handled differently. For example, the call may be denied, route
advanced, or otherwise processed.
Call control provides an index to a specific trunk group level
traffic management control. Valid entries include normal for no
control applied, skip control, applied wide area telecommunications
service (WATS) reroute functionality, cancel control, reroute
control overflow, and reroute immediate control. The next function
points to the next table, and the next label points to an entry or
a range of entries in that table.
FIG. 16 depicts an example of a carrier table. The carrier label is
the key to enter the table. The carrier identification (ID)
specifies the carrier to be used by the calling party. The carrier
selection entry identifies how the caller specifies the carrier.
For example, it identifies whether the caller dialed a prefix digit
or whether the caller was pre-subscribed. The carrier selection is
used to determine how the call will be routed. The next function
points to the next table, and the next label defines an area in
that table for further call processing.
FIG. 17 depicts an example of an exception table. The exception
label is used as a key to enter the table. The calling party's
category entry specifies how to process a call from an ordinary
subscriber, an unknown subscriber, or a test phone. The called
number nature of address differentiates between 0+ calls, 1+ calls,
test calls, local routing number (LRN) calls, and international
calls. For example, international calls might be routed to a
pre-selected international carrier. The called number "digits from"
and "digits to" focus further processing unique to a defined range
of called numbers. The "digits from" field is a decimal number
ranging from 1-15 digits. It can be any length and, if filled with
less than 15 digits, is filled with 0s for the remaining digits.
The "digits to" is a decimal number ranging from 1-15 digits. It
can be any length and, if filled with less than 15 digits, is
filled with 9s for the remaining digits. The next function and next
label entries point to the next table and the next entry within
that table for the next routing function.
FIG. 18 depicts an example of the originating line information
(OLI) table. The OLI label is used as a key to enter the table from
a prior next function operation. The originating line information
entry specifies the information digits that are being transmitted
from a carrier. Different calls are differentiated based on the
information digits. For example, the information digits may
identify an ordinary subscriber, a multi-party line, N00 service,
prison service, cellular service, or private pay station. The next
function and next label entries point to the next table and the
area within that table for the next routing function.
FIG. 19 depicts an example of an automatic number identification
(ANI) table. The ANI label is used as a key to enter the table from
a prior next option. The charge calling party number "digits from"
and "digits to" focus further processing unique to ANI within a
given range. These entries are looked at to determine if the
incoming calling number falls within the "digits from" and "digits
to" fields. The time zone label indicates the entry in the time
zone table that should be used when computing the local date and
time. The time zone label overrides the time zone information from
the trunk group table 906.
The customer information entry specifies further customer
information on the originating side for call process routing. The
echo cancellation (EC) information field specifies whether or not
to apply echo cancellation to the associated ANI. The queue entry
identifies whether or not queuing is available to the calling party
if the called party is busy. Queuing timers determine the length of
time that a call can be queued. The treatment label defines how a
call will be treated based on information in the treatment table.
For example, the treatment label may send a call to a specific
recording based on a dialed number. The next function and next
label point to the next table and an area within that table for
further call processing.
FIG. 20 depicts an example of a called number screening table. The
called number screening label is used as a key to enter the table.
The called number nature of address indicates the type of dialed
number, for example, national versus international. The nature of
address entry allows the call process to route a call differently
based on the nature of address value provided. The "digits from"
and "digits to" entries focus further processing unique to a range
of called numbers. The "digits from" and "digits to" columns both
contain called number digits, such as NPA-NXX ranges, that may
contain ported numbers and are checked for an LRN. This table
serves as the trigger detection point (TDP) for an LNP TCAP when,
for example, NPA-NXXs of donor switches that have had subscribers
port their numbers are data filled in the "digits from" and "digits
to" fields. The delete digits field provides the number of digits
to be deleted from the called number before processing continues.
The next function and next label point to the next table and the
area within that table for further call processing.
FIG. 21 depicts an example of a called number table. The called
number label is used as a key to enter the table. The called number
nature of address entry indicates the type of dialed number, for
example, national versus international. The "digits from" and
"digits to" entries focus further processing unique to a range of
numbers, including LRNs. The next function and next label point to
a next table and the area within that table used for further call
processing.
FIG. 22 depicts an example of a day of year table. The day of year
label is used as a key to enter the table. The date field indicates
the local date which is applicable to the action to be taken during
the processing of this table. The next function and next label
identify the table and the area within that table for further call
processing.
FIG. 23 depicts an example of a day of week table. The day of week
label is a key that is used to enter the table. The "day from"
field indicates the local day of the week on which the action to be
taken by this table line entry is to start. The "day to" field
indicates the local day of the week on which the action to be taken
by this table line entry is to end. The next function and next
label identify the next table and the area within that table for
further call processing.
FIG. 24 depicts an example of a time of day table. The time of day
label is used as a key to enter the table from a prior next
function. The "time from" entry indicates the local time on which
an action to be taken is to start. The "time to" field indicates
the local time just before which the action to be taken is to stop.
The next function and next label entries identify the next table
and the area within that table for further call processing.
FIG. 25 depicts an example of a time zone table. The time zone
label is used as a key to enter the table and to process an entry
so that a customer's local date and time may be computed. The
coordinated universal time (UTC) indicates a standard offset of
this time zone from the UTC. The UTC is also known as Greenwich
mean time, GMT, or Zulu. The UTC should be positive for time zones
east of Greenwich, such as Europe and Asia, and negative for time
zones west of Greenwich, such as North America. The daylight
savings entry indicates whether daylight savings time is used
during the summer in this time zone.
FIG. 26 depicts an example of a routing table. The routing label is
used as a key to enter the table from a prior next function. The
route number specifies a route within a route list. Call processing
will process the route choices for a given route label in the order
indicated by the route numbers. The next function and next label
identify the next table and the area within that table for further
call processing. The signal route label is associated with the next
action to be taken by call processing for this call. The signal
route label provides the index to access the message mapping label.
The signal route label is used in order to modify parameter data
fields in a signaling message that is being propagated to a next
switch or a next call processor.
FIG. 27 depicts an example of a trunk group class of service (COS)
table. The originating trunk COS label and the terminating trunk
COS label are used as keys to enter the table and define call
processing. The next function identifies the next action that will
be taken by call processing for this call. Valid entries in the
next function column may be continued, treat, route advanced, or
routing. Based on these entries call processing may continue using
the current trunk group, send the calls to treatment, skip he
current trunk group and the routing table and go to the next trunk
group on the list, or end the call to a different label in the
routing table. The next label entry is a pointer that defines the
trunk circuit group that the next function will use to process the
call. This field is ignored when the next function is continued or
route advanced.
FIG. 28 depicts an example of a treatment table. The treatment
label is a key that is used to enter the table. The treatment label
is a designation in a call process hat determines the disposition
of the call. The error/cause label correspond either to internally
generated error conditions and call processing or to incoming
release cause values. For each treatment label, there will be a set
of error conditions and cause values that will be associated with a
series of labels for the call processing error conditions and a
series of labels for all incoming release message cause values. The
next function and next label point to the next table and the area
within that table for further call processing.
FIG. 29 depicts an example of an outgoing release table. The
outgoing release label is used as a key to enter the table for
processing. The outgoing cause value location identifies the type
of network to be used. For example, the location entry may specify
a local or remote network or a private, transit, or international
network. The coding standard identifies the standard as an
International Telecommunications Union (ITU) standard or an
American National Standards Institute (ANSI) standard. The cause
value designates error, maintenance, or non-connection
processes.
FIG. 30 depicts an example of a percent control table. The percent
label is used as a key to enter the table. The control percentage
specifies the percentage of incoming calls that will be affected by
the control. The control next function allows attempts for call
connection to be routed to another table during call processing.
The control next label points to an area within that table for
further call processing. The passed next function allows only
incoming attempts to be routed to another table. The next label
points to an area in that table for further call processing.
FIG. 31 depicts an example of a call rate table. The call rate
label is used as a key to enter the table. The call rate specifies
the number of calls that will be passed by the control on or for
completion. Call processing will use this information to determine
if the incoming call number falls within this control. The control
next function allows a blocked call attempt to be routed to another
table. The control next label is a pointer that defines the area in
the next table for further call processing. The passed next
function allows only an incoming call attempt to be rerouted to
another table. The passed next function is a pointer that defines
an area in that table for further call processing.
FIG. 32 depicts an example of a database services table. The
database services label is used as a key to enter the table. The
service type determines the type of logic that is applied when
building and responding to database queries. Service types include
local number portability and N00 number translation. The signaling
connection control part (SCCP) label identifies a location within
an SCCP table for further call processing. The transaction
capabilities application part (TCAP) label identifies a location
within a TCAP table for further processing. The next function
identifies the location for the next routing function based on
information contained in the database services table as well as
information received from a database query. The next label entry
specifies an area within the table identified in the next function
for further processing.
FIG. 33A depicts an example of a signaling connection control part
(SCCP) table. The SCCP label is used as a key to enter the field.
The message type entry identifies the type of message that will be
sent in the SCCP message. Message types include Unitdata messages
and Extended Unitdata messages. The protocol class entry indicates
the type of protocol class that will be used for the message
specified in the message type field. The protocol class is used for
connectionless transactions to determine whether messages are
discarded or returned upon an error condition. The message handling
field identifies how the destination call processor or switch is to
handle the SCCP message if it is received with errors. This field
will designate that the message is to be discarded or returned. The
hop counter entry denotes the number of nodes through which the
SCCP message can route before the message is returned with an error
condition. The segmentation entry denotes whether or not this SCCP
message will use segmentation and send more than one SCCP message
to the destination.
FIG. 33B is a continuation of FIG. 33A for the SCCP table. The
intermediate signaling network identification (ISNI) fields allow
the SCCP message to traverse different networks in order to reach a
desired node. The ISNI type identifies the type of ISNI message
format that will be used for this SCCP message. The route indicator
subfield identifies whether or not this SCCP message requires a
special type of routing to go through other networks. The mark
identification subfield identifies whether or not network
identification will be used for this SCCP message. The label
subfield identifies a unique address into the ISNI table when the
route indicator sub-field is set to "constrained" and the mark
identification subfield is set to "yes."
FIG. 33C is a continuation of FIG. 33B for the SCCP table. FIG. 33C
identifies the called party address field and subfields to provide
information on how to route this SCCP message. The address
indicator subsystem number (SSN) indicates whether or not a
subsystem number will be included in the called party address. The
point code entry indicates whether or not a point code will be
included in the calling party address. The global title indicator
subfield identifies whether or not a global title translation will
be used to route the SCCP message. If a global title translation is
chosen, this subfield also identifies the type. The routing
indicator subfield identifies the elements that will be used to
route the message. Valid entries include global title and point
code. The national/international subfield identifies whether the
SCCP message will use national or international routing and set
up.
The subsystem number field identifies the subsystem number for the
SCCP message. The point code number indicates the destination point
code to which the SCCP message will be routed. This field will be
used for routing messages that do not require SCCP translation.
The global title translation field allows intermediate nodes to
translate SCCP messages so that the messages can be routed to the
correct destination with the correct point code. The global title
translation type entry directs the SCCP message to the correct
global title translation function. The encode scheme identifies how
the address type will be encoded. The number plan subfield
identifies the numbering plan that will be sent to the destination
node. The address type subfield will identify which address type to
use for address digits and the SCCP routing through the
network.
FIG. 33D is a continuation of FIG. 33C for the SCCP table. FIG. 33D
identifies the calling party address field which contains the
routing information that the destination database uses to retain
the SCCP message. The address indicator subsystem number (SSN)
indicates whether or not a subsystem number will be included in the
called party address. The point code subfield indicates whether or
not a point code will be included in the calling party address. The
global title indicator subfield identifies whether or not global
title translation will be used to route the SCCP message. The
routing indicator subfield identifies which elements will be used
throughout the message. This field may include global title
elements or point code elements. The national/international
subfield identifies whether the SCCP will use national or
international routing and set up.
The subsystem number identifies a subsystem number for the SCCP
message. The point code number field indicates the destination
point code to which the SCCP message will be routed. The global
title translations allow the intermediate nodes to translate SCCP
messages and to route the messages to the correct destination. The
global title translation type directs the SCCP message to the
correct global title translation function. The encode scheme
identifies how the address type will be encoded. The number plan
identifies the number plan that will be sent to the destination
node. The address type subfield identifies the address type to use
for address digits in the SCCP routing through the network.
FIG. 34 depicts an example of an intermediate signaling network
identification (ISNI) table. The ISNI table contains a list of
networks that will be used for routing SCCP messages to the
destination node. The ISNI label is used as a key to enter the
table. The network fields 1-16 identify the network number of up to
16 networks that may be used for routing the SCCP message.
FIG. 35 depicts an example of a transaction capabilities
application part (TCAP) table. The TCAP label is used as a key to
enter the table. The TCAP type identifies the type of the TCAP that
will be constructed. The TCAP types include advanced intelligent
network (AIN) and distributed intelligent network architecture
(DINA). The tag class indicates whether the message will use a
common or proprietary structure. The package type field identifies
the package type that will be used in the transaction portion of
the TCAP message. The component type field identifies the component
type that will be used in the component portion of the TCAP
message. The message type field identifies the type of TCAP
message. Message types include variable options depending on
whether they are AIN message types or DINA message types.
FIG. 36 depicts an example of an external echo canceller table. The
echo canceller type specifies if an external echo canceller is
being used on the circuit and, if so, the type of echo canceller.
The echo canceller label points to a location in the controllable
ATM matrix table for further call processing. The RS-232 address is
the address of the RS-232 interface that is used to communicate
with the external echo canceller. The module entry is the module
number of the external echo canceller.
FIG. 37 depicts an example of an interworking unit interface table.
The interworking unit (IWU) is a key that is used to enter the
table. The IWU identification (ID) identifies which interworking
unit is being addressed. The internet protocol(IP) sockets 1-4
specify the IP socket address of any of the four connections to the
interworking unit.
FIG. 38 depicts an example of a controllable ATM matrix (CAM)
interface table. The CAM interface label is used as a key to enter
the table. The CAM label indicates which CAM contains the
interface. The logical interface entry specifies a logical
interface or port number in the CAM.
FIG. 39 depicts an example of a controllable ATM matrix (CAM)
table. The CAM label is used as a key to enter the table. The CAM
type indicates the type of CAM control protocol. The CAM address
identifies the address of the CAM
FIG. 40A depicts an example of a call processor or switch site
office table. The office CLLI name identifies a CLLI of the
associated office for the call processor or switch. The call
processor or switch site node identifier (ID) specifies the call
processor or switch node identifier. The call processor or switch
origination identifier (ID) specifies a call processor or switch
origination identifier. The software identifier (ID) specifies a
software release identifier. The call processor identifier (ID)
specifies the call processor or switch identifier that is sent to
the inter working units.
FIG. 40B is a continuation of FIG. 40A of the call processor or
switch site office table. The automatic congestion control (ACC)
specifies whether ACC is enabled or disabled. The automatic
congestion control level (ACL) 1 onset identifies an onset
percentage value of a first buffer utilization. The ACL 1 abate
entry specifies an abatement percentage of utilization for a first
buffer. The ACL 2 onset entry specifies an onset level for a second
buffer. The ACL 2 abate entry specifies an abatement level
percentage of buffer utilization for a second buffer. The ACL 3
onset entry specifies an onset level percentage of buffer
utilization for a third buffer. The ACL 3 abate entry specifies an
abatement level percentage of buffer utilization for a third
buffer.
FIG. 40C is a continuation of FIG. 40B for the call processor or
switch site office table. The maximum trunks for the off hook
queuing (max trunks OHQ) specifies a maximum number of trunk groups
that can have the off hook queuing enabled. The OHQ timer one (TQ1)
entry specifies the number of milliseconds for the off hook timer
number one. The OHQ timer two (TQ2) entry specifies the number of
seconds for the off hook timer number two. The ring no answer timer
specifies the number of seconds for the ring no answer timer. The
billing active entry specifies whether ECDBs are being sent to the
call processing control system (CPCS). The network management (NWM)
allow entry identifies whether or not a selective trunk reservation
and group control are allowed or disallowed. The billing failure
free call entry specifies if a call will not be billed if the
billing process is unavailable. The billing failure free call will
either be enabled for free calls or disabled so that there are no
free calls.
FIG. 40D is a continuation of FIG. 40C for the call processor or
switch site office table. The maximum (max) hop counts identifies
the number of call processor or switch hops that may be made in a
single call. The maximum (max) table lookups identifies the number
of table lookups that may performed for a single call. This value
is used to detect loops in routing tables.
FIGS. 41A-41B depict an example of an advanced intelligent network
(AIN) event parameters table. The AIN event parameters table has
two columns. The first identifies the parameters that will be
included in the parameters portion of the TCAP event message. The
second entry may include information for analysis.
FIG. 42 depicts an example of a message mapping table. This table
allows the call processor to alter information in outgoing
messages. The message type field is used as a key to enter the
table and represents the outgoing standard message type. The
parameters entry is a pertinent parameter within the outgoing
message. The indexes point to various entries in the trunk group
and determine if parameters are passed unchanged, omitted, or
modified in the outgoing messages.
Those skilled in the art will appreciate that variations from the
specific embodiments disclosed above are contemplated by the
invention. The invention should not be restricted to the above
embodiments, but should be measured by the following claims.
* * * * *