MXPA01006300A - System and method for connecting a call in a tandem architecture - Google Patents

Abstract

A system, (202) and method for connecting a call in a tandem architecture comprises a signaling processor (224) for processing call signaling to determine connections for the user communications. A controllable asynchronous transfer mode (ATM) matrix (226) accepts control messages from the signaling processor (224) and accepts user communications from switching systems (206). In response to the control message, the ATM matrix connects the user communications to the designated connection.

Description

SYSTEM AND METHOD FOR CONNECTING A CALL IN AN ARCHITECTURE IN "TANDEM" FIELD OF THE INVENTION The present invention is concerned with the field of commutation and transport of telecommunication calls and more particularly to connect calls on tandem connections.

BACKGROUND OF THE INVENTION Broadband or broadband systems provide telecommunications providers with many benefits in which they include 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. Telecommunications systems often have a hierarchy of switching systems to connect calls over long distance and local networks. Normally, a series of edge switching systems connect to a more core type switching system. The edge switching systems connect the calls to the core switching system, and the core switching system connects the calls to other edge switching systems. These switching systems of type REF: 129655 core are sometimes referred to as tandem switches. Figure 1 illustrates such a prior art system having two edge switches 102 and 104 and a tandem switch 106. It will be appreciated that the first edge switch 102 transmits the call to the tandem switch 106 and the tandem switch 106 transmits the call to edge switch 104. Typically, tandem switching systems do not provide distributed call processing and call connection functions. In these systems, the switching matrix is co-resident with the call processing. Thus, a system is needed to provide distributed call processing. In addition, the prior art systems do not provide telephony call services. On the other hand, a tandem type switching system is needed for the asynchronous transfer (ATM) call connection systems. The increased speed and efficiencies of cost and processing time can be realized by such system. The present invention meets these needs.

BRIEF DESCRIPTION OF THE INVENTION The present invention comprises a system for connecting a call having call signaling and user communications. The system comprises a signaling processor that receives and processes the call signaling, to select an asynchronous transfer mode (ATM) connection for user communications. The signaling processor transmits a control message identifying the selected ATM connection. An asynchronous transfer mode matrix (ATM) receives the user's communications over another ATM connection and receives the control message from the signaling processor. In response to the control message, the ATM matrix connects the user's communications over the selected ATM connection. The present invention also comprises a system for connecting a call having call signaling and user communications. The system comprises a first switching system that carries the user's communications over a first connection. A signaling processor receives and processes the call signaling to select a second connection for the user's communications. The signaling processor transmits a control message identifying the second selected connection. An asynchronous transfer mode (ATM) matrix receives the user's communications that were transported on the first connection and receives the control message from the signaling processor. In response to the control message, the ATM matrix connects the user's communications on the second selected connection. A second switching system receives the user's communications that were transported on the second connection. The present invention is also concerned with a system for connecting a call having call signaling and user communications. The system comprises a signaling processor that receives and processes the call signaling to select a first, second and third connection for user communications. The signaling processor transmits a first, second and third control message identifying the first, second and third connections selected, respectively. A first interleaving unit receives the user's communications, receives the first control message and in response to the first control message, interleaves the user's communications on the first connection. An asynchronous transfer mode (ATM) matrix receives the communications from the user that were transported on the first connection, receives the second control message and in response to the second control message, connects the user's communications on the second selected connection. A second interleaving unit receives the user's communications that were connected on the second connection, receives the third control message - and in response to the third control message, interleaves the user's communications on the third connection. In addition, the present invention is concerned with a method for connecting a call having call signaling and user communications. The method comprises receiving and processing call signaling to select an ATM connection for user communications. A control message identifying the selected ATM connection is transmitted. The user communications are received over another ATM connection of an asynchronous transfer mode array, and the control message is received in an asynchronous transfer mode array. The user's communications are connected over the selected ATM connection, in response to the control message using the ATM matrix.

BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 is a block diagram of a tandem system of the prior art. Figure 2 is a block diagram of a call connection system having a tandem system with an asynchronous transfer mode array according to an embodiment of the present invention. Figure 3 is a block diagram of a call connection system having a tandem system with an interleaving unit and a controllable asynchronous transfer mode array according to one embodiment of the present invention. Figure 4 is a functional diagram of a controllable asynchronous transfer mode array according to the present invention. Figure 5 is a functional diagram of a controllable, asynchronous transfer mode array with time division multiplex capability according to the present invention. Figure 6 is a functional diagram of an asynchronous transfer mode interleaving unit for use with an optical, synchronous network system, according to the present invention. Figure 7 is a functional diagram of an asynchronous transfer mode interleaving unit for use with a synchronous, digital hierarchy system in accordance with the present invention. Figure 8 is a block diagram of a signaling processor constructed in accordance with the present invention.

Fig. 9 is a block diagram of a data structure having tables, which are used in the signaling processor of Fig. 8. Fig. 10 is a block diagram of additional tables used in the signaling processor of Figs. Figure 8. Figure 11 is a block diagram of additional tables that are used in the signaling processor of Figure 8. Figure 12 is a block diagram of additional tables that are used in the signaling processor of Figure 8. Figure 13 is a schematic diagram of a time division multiplexing backbone circuit board, used in the signaling processor of the figure Figure 14 is a schematic diagram of a trunk circuit table asynchronous transfer mode used in the signaling processor of Figure 8. Figure 15A is a schematic diagram of a trunk group table used in the signaling processor Figure 8. Figure 15B is a schematic continuation diagram of the trunk group table of Figure 15A.

Figure 15C in a continuation schematic diagram of the trunk group table of Figure 15B. 'Fig. 16 is a schematic diagram of a carrier or carrier wave table used in the signaling processor of Fig. 8. Fig. 17 is a schematic diagram of an exception table used in the signaling processor of Fig. 8. Fig. 18 is a schematic diagram of a source line information table used in the signaling processor of Fig. 8. Fig. 19 is a schematic diagram of an automated number identification table used in the signaling processor of Figure 8. Figure 20 is a schematic diagram of a selection or filtering table of the called number used in the signaling processor of Figure 8. Figure 21 is a schematic diagram of a called number table used in the signal processor. signaling of Figure 8. Figure 22 is a schematic diagram of a day of the year table used in the signaling processor of Figure 8.

Fig. 23 is a schematic diagram of a table of day of the week used in the signaling processor of Fig. 8. Fig. 24 is a schematic diagram of a time table of the day used in the signaling processor of Fig. 8. Figure 25 is a schematic diagram of a time zone table used in the signaling processor of Figure 8. Figure 26 is a schematic diagram of a routing table used in the signaling processor of Figure 8. Figure 27 is a schematic diagram of a service class table of the trunk group, used in the signaling processor of Figure 8. Figure 28 is a schematic diagram of a treatment table used in the signaling processor of Figure 8. Figure 29 is a schematic diagram of an outgoing release table used in the signaling processor of Figure 8. Figure 30 is a schematic diagram of a percent control board used in the signaling processor of Figure 8.

Figure 31 is a schematic diagram of a call proportion table used in the signaling processor of Figure 8. Figure 32 is a schematic diagram of a database services table, used in the signaling processor of Figure 8. Figure 33A is a schematic diagram of a signaling connection control part table used in the signaling processor of Figure 8. Figure 33B is a schematic continuation diagram of the control part table. signaling connection of figure 33A. • Figure 33C is a schematic continuation diagram of the signaling connection control part table of Figure 33B. Figure 33D is a schematic continuation diagram of the signaling connection control part table of Figure 33C. Fig. 34 is a schematic diagram of an intermediate signaling network identification table used in the signaling processor of Fig. 8. Fig. 35 is a schematic diagram of a transaction capability application part table used in the signaling processor of Figure 9.

Fig. 36 is a schematic diagram of an external echo canceller table used in the signaling processor of Fig. 8. Fig. 37 is a schematic diagram of an interleaving unit used in the signaling processor of Fig. 8. Figure 38 is a schematic diagram of a controllable, asynchronous transfer mode matrix table used in the signaling processor of Figure 8. Figure 39 is a schematic diagram of an asynchronous transfer mode matrix table. , controllable, used in the signaling processor of FIG. 8. FIG. 0A is a schematic diagram of a site exchange table, used in the signaling processor of FIG. 8. FIG. 40B is a schematic continuation diagram of FIG. the central table of the site of Figure 40A. Figure 40C is a schematic continuation diagram of the center table of the site of Figure 40B.

Figure 40D is a schematic continuation diagram of the center table of the site of Figure 40C. Figure 41A is a schematic diagram of an advanced intelligent network event parameter table used in the signaling processor of Figure 8. Figure IB is a schematic continuation diagram of the advanced intelligent network event parameter table of Figure 41A. Figure 42 is a schematic diagram of a message mapping table used in the signaling processor of Figure 8.

DETAILED DESCRIPTION Telecommunications systems have a diversity of communications devices in urban and interurban central environments that interact to provide call services to customers. Both services and resources of intelligent network (IN) and traditions are used to process, channel or connect a call or a designated connection. A call has user communications and call signaling. The user communications contains the caller information, such as a voice communication or data communication and are transported over a connection. The call signaling contains information that facilitates call processing and is communicated over a link. Call signaling, for example, contains information describing the called number and the caller's number. Examples of call signaling are standardized signaling, such as signaling system # 7 (SS7), Cl, integrated services digital network (ISDN) and digital private network signaling system (DPNSS), which are based on the recommendation of ITU Q.931. A call can be connected to - and from - the communications devices. The connections are used to transport user communications and other device information between the communication devices and between the elements and devices of the system. The term "connection" as used in this, means the transmission medium used to carry the user's communications between the elements of the various networks and telecommunications systems. For example, a connection could carry a user's voice, computer data or other data of the communication device. A connection can be associated with either in-band communications or out-of-band communications. The links are used to carry the call signaling and the control messages. The term "link" as used herein, means a transmission medium used to carry call signaling and control messages. For example, a link will carry the call signaling or a device control message containing instructions and device data. For example, a link may carry out-of-band signaling such as that used in SS7, C7, ISDN, DPNSS, B-ISDN, GR-303, or it could be via the local area network (LAN) or the call signaling by distribution bar or data bus. For example, a link could be an adaptation layer 5 data link (AAL5) asynchronous transfer mode (ATM), user datagram protocol / internet protocol (UDP / IP), ethernet, digital signal zero level (DSO), or level one digital signal (DSl). In addition, a link, as shown in the figures, can represent a single physical link or multiple links, such as a link or a combination of ISDN links, SS7, transmission control protocol / internet protocol (TCP / IP) or some other data link. The term "control message" as used herein, means a signaling control message, an instruction or signaling, or a control or signaling signal, whether patented or normalized, conveying information from a point to other. The system of the present invention provides distributed call processing and connection functionalities. The present invention includes a system and method for implementing the tandem type switching system with a switching matrix that can be non-resident of the call processing portion. In addition, the present invention includes a system for providing a tandem switching system for an asynchronous transfer mode (ATM) network. Figure 2 illustrates an exemplary embodiment of a call connection system 202 of the present invention. The call connection system 202 has a tandem system 204 connected to a first switching system 206 and a second switching system 208 through the connections 210 and 212, respectively. A connection 214 connects the switching systems 206 and 208. The connections 216 and 218 connect to the first switching system 206, and the connections 220 and 222 connect to the second switching system 208. The tandem system 204 connects the call between the systems of switching 206 and 208 and with other communication devices (not shown). The tandem system 204 switches the calls to the ATM layer. In addition, calls based on time division multiplexing (TDM) can be connected by the tandem system.204. The tandem system 204 provides real-time call control for telephony services on a switching platform. In addition, the tandem system 204 provides overflow channeling, so that it handles calls from other systems and switching devices that have a real or potential Quality of Service (QoS) degradation. Moreover, in addition to providing more tandem, basic routing functions, the tandem system 204 provides durability for networks, so that alternate routes are available between the switching systems 206 and 208 and between other devices of the system (not shown). ). Switching systems 206 and 208 connect calls to and from the tandem system 204 and to and from each other. The switching systems 206 and 208 comprise a tandem system, such as the tandem system 204 or the tandem system which is described below, customer facility equipment (CPE), an ATM switch, a TDM switch with a remote digital terminal, a cross connection, an interlacing unit, an ATM gate, or any other device capable of handling a call. For example, the CPE may be an urban branch office with a private branch or other communication device. An ATM gateway is a device for changing the virtual path / virtual channel (VP / VC) identifiers of the ATM cell header.

In one embodiment, the tandem system 204 comprises a signaling processor 224 and a matrix of ATM 226 linked by a link 228. A first link 230 and a second link 232 extend from the signaling processor 224. The signaling processor 224 is a signaling platform that can receive, process, and generate call signaling. Based on the processed call signaling, the signal processor 224 selects processing options, services or resources for user communications and generates and transmits control messages identifying the communication device, the processing and service option or the resource which is going to be used. Signaling processor 224 also selects virtual connections and circuit-based connections for call routing and generates and transports control messages identifying the selected connections. Signaling processor 224 can process various forms of signaling, including ISDN, GR-303, B-ISDN, SS7 and C7. ATM matrix 226 is a controllable ATM matrix that establishes connections in response to control messages received from signaling processor 224. ATM matrix 226 is suitable for interleaving between ATM connections and division multiplex connections. of time (TDM). ATM matrix 226 also cross-connects ATM connections with other ATM connections. In addition, the ATM matrix 226 can switch calls from the TDM connections to other TDM connections. The ATM matrix 226 transmits and receives the call signaling and user communications over the connections. Normally, ATM matrix 226 transmits call signaling to, and from, signaling processor 224. The system of Figure 2 operates as follows. In a first example, a call is handled by the first switching system 206. In this example, the first switching system 206 is a carrier switch or urban carrier bearer (LEC) wave. The user's communications are transported from the first switching system 206 to the ATM matrix over the connection 210. The call signaling is received by the signaling processor 224 over the link 230. The signaling processor 224 processes the call signaling to determine a connection for the call. Signaling processor 224 selects connection 212 for the call and transmits a control message to ATM matrix 226 identifying the selected connection. The signaling processor 224 also transmits the new call signaling on the link 232. The ATM matrix 236 receives the user's communications on the connection 210 and receives the control message on the link 228. In response to the control message, the ATM matrix 226 connects the user's communications to the selected connection 212, and the call is received by the second switching system 208. In this example, the connection 212 is an ATM connection. In another example, the first switching system 206 is a tandem system of the present invention, such as the tandem system 204 or the tandem system to be described later, and the second switching system 208 is another type of switching. In this example, connection 214 will be the preferred connection of the first switching system 206 to the second switching system 208. However, connection 214 is not available. As a measure of durability, the call is alternately routed through the tandem system 204. The first switching system 206 carries the user's communications to the ATM matrix 226 over the connection 210. In this example, the connection 210 is a ATM connection. The call signaling is transmitted from the first switching system 206 to the signaling processor 224 through a link (not shown).

Signaling processor 224 processes the call signaling to determine a connection for the call. Signaling processor 224 selects connection 212 for the call and transmits a control message to ATM matrix 226 identifying the selected connection. In addition, the signaling processor 224 transmits new call signaling according to the switching systems 208 over a link (not shown) identifying the connection 212 over which the user's communications will be transported. The ATM matrix 226 receives the user's communications on the connection 210 and receives the control message on the link 228. In response to the control message, the ATM matrix 226 connects the call to the selected connection 212. The second system switch 208 receives user communications over connection 212 and call signaling over a link (not shown). In this example, connection 212 is an ATM connection. In another example, the first and the second switching system 206 and 208 are tandem systems of the present invention, such as the tandem system 204 or the tandem system which is described below. In this example, connection 210 is an ATM connection. Also, in this example, connection 214 will be the preferable connection of switching system 206 to the second switching system 208. However, connection 214 is not available due to the use of high traffic and QoS degradations. As a call control measure, the call is routed through the tandem system 204. The switching system 206 carries the user's communications to the ATM matrix 226 on a VP / VC on the connection 210 to the ATM matrix. 226. The first switching system 206 transmits the call signaling on another VP / VC on the connection 210 to the ATM matrix 226. The ATM matrix 226 then transmits the call signaling to the signaling processor 224 on the link 228. Signaling processor 224 processes the call signaling to determine a connection for the call. Signaling processor 224 selects connection 212 for the call. Signaling processor 224 transmits call signaling to ATM matrix 226 and * transmits a control message to ATM matrix 226 identifying the selected connection for user communications and, in some cases, a connection for signaling of call. The ATM matrix 226 receives the user's communications on the connection 210 and receives the control message and the call signaling on the link 228. In response to the control message, the ATM matrix 226 connects the user's communications to the VP / VC selected in connection 212 and transmits call signaling in another VP / VC in connection 212. In this example, connection 212 is an ATM connection. The second switching system 208 receives the call signaling and the user communications on the respective VP / VCs on the connection 212. Figure 3 illustrates another embodiment of a call connection system 202A with a tandem system 204A of the present invention. The tandem system 204A comprises a 224A signaling processor, an ATM matrix 226A, a first interleaving unit 302 and a second interleaving unit 304. The signaling processor 224A and the ATM matrix 226A are the same as those elements described above. The ATM matrix is connected to the first interlacing unit 302 by a connection 306 and to the second interlacing unit 304 by a connection 308. Two connections 310 and 312 extend from the ATM matrix 226A. A connection 314 connects the first interlacing unit 302 with the second interlacing unit 304. A connection 316 connects the first interlacing unit 302, and a connection 318 connects the second interlacing unit 304. The interlacing units 302 and 304 intertwine the traffic between several protocols. Preferably, the interleaving units 302 and 304 intertwine between the ATM traffic and the non-ATM traffic. The interleaving units 302 and 304 operate in accordance with the control messages received from the call processor 224A. These control messages are usually provided on a call-by-call basis and typically identify an assignment between a DSO and a VP / VC for which the user's communications are intertwined. In some cases, the interleaving units 302 and 304 may carry control messages that may include data to the call processor 224A. The system of Figure 3 operates as follows. In a first example, the signaling processor 224 receives call signaling and the first interleaving unit 302 receives the user's communications on the connection 316. The signaling processor 224A processes the call signaling to determine the connections for the call. In this example, connection 314 is the preferred connection for the call, but it is not available. Signaling processor 224 selects connections 306, 308 and 318 for the call. The signaling processor 224A transmits a control message to each of the first interleaving unit 302, the ATM matrix 226A and the second interleaving unit 304 which identifies the respective connections 306, 308 and 318 for the call. The first interleaving unit 302 receives the user's communications and the control message. In response to the control message, the first interworking unit 302 interleaves the user's communications to the selected connection 306. Preferably, the first interworking unit 302 interleaves the user's communications from TDM to ATM. The ATM matrix 226A receives the user communications and the control message. In response to the control message, the ATM matrix 226A connects the user communications of the connection 306 to the selected connection 308. The second interleaving unit 304 receives the user's communications and the control message. In response to the control message, the second interleaving unit 304 interleaves the user's communications from the connection 308 to the selected connection 318. Preferably, the second interleaving unit 304 interleaves the communications of the user from ATM to TDM. In another example, signaling processor 224A receives call signaling. Signaling Processor 224A processes the call signaling to determine the connections for the call. Signaling processor 224A selects connections 306 and 312 for the call. The signaling processor 224A transmits a control message to each of the first interleaving unit 302 and the ATM matrix 226A which identifies the respective connections 306 and 312 for the call. The first interleaving unit 302 receives the user communications for the call on the connection 316 and the control message of the signaling processor 224A. In response to the control message, the first interleaver unit 302 interleaves the user's communications to the selected connection 306. The ATM matrix 226A receives the user's communications and the control message. In response to the control message, the ATM matrix 226A connects the user communications of the connection 306 to the selected connection 312. In a third example the signaling processor 224A receives the call signaling and processes the call signaling to determine the connections for the call. Signaling processor 224A selects connections 314 and 318 for the call. The signaling processor 224A transmits a control message to each of the first interleaving unit 302 and the second interleaving unit 304 which identifies the respective connections 314 and 318 for the call. The first interleaving unit 302 receives the user communications for the call on the connection 316 and the control message of the signaling processor 224A. In response to the control message, the first interleaver unit 302 interleaves the user's communications to the selected connection 314. The second interleaver unit 304 receives the user's communications and the control message. In response to the control message, the second interleaving unit 304 interleaves the communications of the user of the connection 314 to the selected connection 318. In a fourth example the signaling processor 224A receives and processes the call signaling for a call, to determine the connections for the call. Signaling processor 224A selects connection 312 for the call. The signaling processor 224A transmits a control message to the ATM matrix 226A identifying the connection 312 for the call. The ATM matrix 226A receives the user communications on the connection 310 and the control message of the signaling processor 224A. In response to the control message, the ATM matrix 226A connects the user communications of the connection 310 to the selected connection 312. It will be appreciated that the calls can be connected in the opposite direction as described above. In addition, one, multiple or all elements of the call connection systems described above, can be used to connect calls. On the other hand, the above examples are only exemplary embodiments of the present invention, and any of the methods described above can be used with any of the other elements described above.

THE CONTROLLABLE ATM MATRIX Figure 4 illustrates an exemplary embodiment of a controllable asynchronous transfer (ATM) matrix (CAM), but other CAMs that support the requirements of the invention are also applicable. The CAM 402 can receive and transmit user communications or call signaling in ATM format. The CAM 402 preferably has a control interface 404, a controllable ATM array 406, an optical M-bearer / synchronous transport-M-interface (0C-M / STS-M) 408 interface and an OC-X interphase. / STS-X 410. As used herein in conjunction with OC or STS, "M" refers to a number and "X" refers to an integer. The control interface 404 receives the control messages originating from the signaling processor 412, identifies the virtual connection assignments in the control messages and provides these assignments to the array 406 for implementation. Control messages can be received over an ATM virtual connection and through either the OC-M / STS-M 408 interface or the OC-X / STS-X 410 interface through the 406 matrix to the interphase of control 404, through either the OC-M / STS-M interface or the OC-X / STS-X interface directly to the control interface, or through the control interface from a link. Matrix 406 is a controllable ATM matrix that provides cross-connect functionality in response to control messages from signaling processor 412. Matrix 406 has access to virtual path / virtual channels (VP / VC) over which it can be connected the calls. For example a call can arrive on a VP / VC through the interface of OC-M / STS-M 408 and be connected through the matrix 406 on a VP / VC through the OC-X / STS interface -X 410 in response to a control message received by the signaling processor 412 through the control interface 404. Alternatively, a call can be connected in the opposite direction. In addition, a call can be received on a VP / VC through the interface of OC-M / STS-M 408 or the interface of OC-X / STS-X '410 and be connected through the matrix 406 to a VP / VC different in the same OC-M / STS-M interface or the same OC-X / STS-X interface. The OC-M / STS-M 408 interface is operational to receive ATM cells from the array 406 and to transmit the ATM cells over a connection to the communication device 414. The OC-M / STS-M 408 interface can also be receiving ATM cells in the OC or STS format and transmitting them to the array 406. The OC-X / STS-X interface 410 is operational to receive ATM cells from the array 406 and to transmit the ATM cells over a connection to communication device 416. The OC-X / STS-X interface 410 can also receive ATM cells in the OC or STS format and transmit them to matrix 406. Call signaling can be received from and transferred from the interface of OC-M / STS-M 408. Also, call signaling can be received through, and transferred from, the OC-X / STS-X interface 410. The call signaling can be connected in a connection or transmit to the control interface or via matrix 406. The processor signaling 412 is configured to send control messages to CAM 402 to implement particular characteristics in particular VP / VC circuits. Alternatively, search tables can be used to implement particular characteristics for particular VP / VCs. Figure 5 illustrates another exemplary embodiment having time division multiplexing (TDM) capability, but other CAMs that support the requirements of the invention are also applicable. The CAM 502 can receive and transmit signals signaled in band and out of band. The CAM 502 preferably has a control interface 504, an OC-M / STS-M 506 interface, a digital signal level 3 (DS3) 508 interface as a DSl 510 interface, a DSO interface, a layer ATM adaptation (AAL) 514, a controllable ATM array 516, an OC-M / STS-M 518A interface, an OC-X / STS-X 518B interface, and an ISDN / GR-303 interface. 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 the control messages originating from the signaling processor 522, identifies the virtual connection and DSO assignments in the control messages and provides these assignments to the AAL 514 or the array 516 for implementation. The control messages can be received over an ATM virtual connection and through the interface of OC-M / STS-M 518A to the control interface 504, through the interface of OC-X / STS-X 518B and the matrix 516 to the control interface, or directly through the control interface from a link. The OC-M / STS-M 506 interface, the DS3 508 interface, the DSl 510 interface, the DSO 512 interface and the ISDN / GR-303 520 interface can each receive communications from the user from a 524 communication device. Similarly, the interface of OC-M / STS-M 518A and the interface of OC-X / STS-X 518B can receive communications from the user of the communication devices 526 and 528. The interface of. OC-M / STS-M 506 receives user communications with OC-N format and user communications with STS-N format and converts user communications to DS3 format. The DS3 508 interface receives the user's communications in the DS3 format and converts the user's communications to the DSl format. The DS3 508 interface can withstand the DS3s of the OC-N / STS-N 506 interface or an external connection. The DSl 510 interface receives the user's communications in the DSl format and converts the user's communications to the DSO format. The DSl 510 interface receives DSls from the DS3 508 interface or from an external connection. The DSO 512 interface receives the user's communications in the DSO format and provides an interface to the AAL 514. The ISDN / GR-303 520 interface receives the user's communications in either the ISDN format or the GR-303 format and converts the user's communications to the DSO format. further, each interface can transmit user communications in a manner similar to communication device 524.

The OC-M / STS-M 518A interface is operational to receive ATM cells from the AAL 514 or from the array 516 and to transmit the ATM cells over a connection to the communication device 526. The OC-M interface / STS-M 518A can also receive ATM cells in the OC or STS format and transmit them to AAL 514 or matrix 516. The OC-X / STS-X 518B interface is operational to receive ATM cells from the AAL 514 or matrix 516 and for transmitting ATM cells over a connection to communication device 528. The OC-X / STS-X 518B interface can also receive ATM cells in the OC or STS format and transmit them to AAL 514 or matrix 516. Call signaling can be received through and transferred from the OC-M / STS-M 506 interface and the ISDN / GR-303 520 interface. Also, the call signaling is can receive through, and transfer from, the OC-M / STS-M 518A interface and the OC- interface X / STS-X 518B. The call signaling can be connected in 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 sub-layer (SAR).

The AAL 514 obtains the identity of the DSO and ATM VP / VC from the control interface 504. The AAL 514 is operational to convert between the DSO format and the ATM format. The AALs are known in the art, and the information about the AALs is provided by the documents of the International Telecommunication Union (ITU) of the series of 1,363, which is incorporated herein by reference. For example, ITU document 1.363.1 discusses AALl. An AAL for voice calls is described in U.S. Patent No. 5,806,553 entitled "Cell Processing for Voice Transmission", which is incorporated herein by reference. Calls with multiple DSOs of 64 Kilo-bits per second (Kbps) are known as Nx64 calls. If desired, the AAL 514 can be configured to accept control messages through the control interface 504 for Nx64 calls. The CAM 502 is suitable for interleaving, multiplexing and demultiplexing for multiple DSOs. A technique for processing VP / VCs is described in the US patent application No. 08 / 653,852, which was filed on May 28, 1996 and was titled "Telecommunications System with a Connection Processing System", and which is incorporated in the present by reference. DSO connections are bidirectional and ATM connections are normally unidirectional. As a result, two virtual connections in opposite directions will normally be required for each DSO. Those skilled in the art will appreciate how this can be done in the context of the invention. For example, the cross connection can be provided with a second set of VP / VCs in the opposite direction as the original VP / VC set. Matrix 516 is a controllable ATM array that provides cross-connect functionality in response to control messages from signaling processor 522. Matrix 516 has access to VP / VCs on which calls can be connected. For example, a call may arrive on a VP / VC through the interface of OC-M / STS-M 518A and be connected through matrix 516 on a VP / VC through the interface of OC-X / STS-X 518B in response to a control message received by the signaling processor 522 through the control interface 504. Alternatively, the matrix 516 can transmit a received call on a VP / VC through the OC-interface. M / STS-M 518A to AAL 514 in response to a control message received by signaling processor 522 through control interface 504. Communications may also occur in opposite directions, through the various interfaces. In some embodiments it may be desirable to incorporate digital signal processing capabilities, for example, at the DSO level. It may also be desirable to apply echo control to the selected DSO 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 characteristics in particular DSO or VP / VC circuits. Alternatively, search tables can be used to implement particular characteristics for particular VP / VC circuits. It will be appreciated from the foregoing teachings for the CAMs and subsequent teachings for ATM interleaving units, that the CAMs described above can be adapted for modification, to transmit and receive other formatted communications such as module communications. of synchronous transport (ATM) and of European level (E). For example, the interfaces of OC / STS, DS3, DSl, DSO and ISDN / GR-303 can be replaced by the interfaces of STM electrical / optical (E / O), E2, El, EO and private network signaling system digital (DPNSS), respectively.

THE ATM INTERLACEMENT UNIT Figure 6 illustrates an exemplary embodiment of an interleaving unit that is an ATM interleaving unit 602 suitable for the present invention, for use with a SONET system. Other interlacing units that support the requirements of the invention are also applicable. The ATM interleaving unit 602 can receive and transmit in-band and out-of-band calls. The ATM interleaving unit 602 preferably has a control interface 604, an interface of OC-N / STS-N 606, a DS3 interface 608, a DSI interface 610, a DSO interface 612, a signal processor 614 , an AAL 616, an interface of OC-M / STS-M 618 and an interface of ISDN / GR-303 620. As used in "this in conjunction with OC or STS," N "refers to an integer and "M" refers to an integer.The control interface 604 receives control messages which is original from the signaling processor 622, which identifies the DSO and virtual connection assignments in the control messages and provides these assignments to the AAL 616 for implementation Control messages are received over an ATM virtual connection and through the interface of OC-M / STS-M 618 to the control interface 604 or directly through the control interface from a link The OC-N / STS-N 606 interface, the DS3 608 interface, the DSl 6 interface 10, the DSO interface 612 and the ISDN / GR-303 620 interface each can receive communications from the user of a 624 communication device. Similarly, the OC-M / STS-M 618 interface can receive communications from the user of a communication device 626. The interface of OC-N / STS-N 606 receives the user communications with OC-N format and the user communications with STS-N format and demultiplexes the user's communications to the DS3 format. The DS3 608 interface receives the user's communications in the DS3 format and demultiplexes the user's communications to the DSl format. The DS3 608 interface can receive the DS3 from the OC-N / STS-N 606 interface or from an external connection. The DSl 610 interface receives the user's communications in the DSl format and demultiplexes the user's communications to the DSO format. The DSL 610 interface receives the DSls from the DS3 608 interface or from an external connection. The DSO 612 interface receives the user's communications in the DSO format and provides an interface to the AAL 616. The ISDN / GR-303 620 interface receives the user's communications either in the ISDN format or in the format of GR-303 and convert the user's communications to the DSO format. In addition, each interface can transmit the user's communications in a manner similar to the communication device 624. The interface of OC-M / STS-M 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 interface of OC-M / STS-M 618 can also receive ATM cells in the OC or STS format and transmit them to the AAL 616. The call signaling can be received through, and transfer from, the OC-N / STS-N 606 interface and the ISDN / GR-303 620 interface. Also, the call signaling can be received through, and transferred from, the OC-M interface / STS-M 618. Call signaling can be connected to 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 layer (SAR). The AAL 616 obtains the identity of the DSO and the ATM VP / VC from the control interface 604. The AAL 616 is operational to convert between the DSO format and the ATM format. If desired, the AAL 616 can be configured to accept control messages through the control interface 604 for Nx64 calls. The ATM interleaving unit 602 is suitable for interleaving, multiplexing and demultiplexing for multiple DSOs. DSO connections are bidirectional and ATM connections are normally unidirectional. As a result, two virtual connections in opposite directions will normally be required for each DSO. Those skilled in the art will appreciate how this can be done in the context of the invention. For example, the cross connection may be provided with a second set of VP / VCs in the address set as the original set of VP / VCs. In some embodiments, it may be desirable to incorporate digital signal processing capabilities at the DSO level. It may also be desirable to apply echo control to selected DSO circuits. In these modes, a 614 signal processor is included either separately (as shown) or as a part of the DSO interface 612. Signaling processor 622 is configured to send control messages to the interleaving unit of ATM 602 to implement particular characteristics in particular DSO circuits. Alternatively, search tables can be used to implement particular features or particular VP / VC circuits. Figure 7 illustrates another exemplary embodiment of an interlacing unit that is an interlacing unit 702 suitable for the present invention, for use with an SDH system. The ATM interleaving unit 702 preferably has a control interface 704, an electrical / optical (E / O) STM-M interface 706, an E3 708 interface, an El 710 interface, an E0 712 interface, a signal processor 714, an AAL 716, an electrical / optical (E / O) STM-M interface and a DPNSS 720 interface. As used herein in conjunction with STM, "N" refers to a number integer and "M" refers to an integer. The control interface 704 receives control messages from the signaling processor 722, identifies the EO and virtual connection assignments in the control messages, and provides these assignments to the AAL 716 for implementation. The control messages are received in an ATM virtual connection and through the interface of STM-M 718 to the control interface 604 or directly through the control interface from a link. - The interface of STM-N E / O 706, the interface of E3, the interface of the 710, the interface of E0 712 and the interface of DPNSS 720 each can receive communications from the user of a second communication device. Likewise, the interface of STM-M E / O 718 can receive communications from the user of a third communication device 726. The interface of STM-N E / 0 706 receives the user communications with electric or optical STM-N format and converts user communications from the electric STM-N or optical STM-N format to the E3 format. The E3 708 interface receives the user's communications in the E3 format and demultiplexes the user's communications to the El format. The E3 708 interface can receive E3s from the STM-N E / O 706 interface or from an external connection . The 710 interface receives the user's communications in the El format and demultiplexes the user's communications to the EO format. The interface of the 710 receives the Els from the interface of STM-N E / 0 706 or the interface of E3 708 or from an external connection. The E0 712 interface receives the user's communications in the E0 format and provides an interface to the AAL 716. The DPNSS 720 interface receives the user's communications in the DPNSS format and converts the user's communications to the E0 format. In addition, each interface can transmit user communications in a manner similar to the communication device 724. The interface of STM-M E / 0 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 interface of STM-M E / 0 718 can also receive ATM cells in the STM-M E / 0 format and transmit them to the AAL 716. The call signaling can be received through, and transfer from, the interface of STM-N E / 0 706 and the DPNSS 720 interface. Also the call signaling can be received through, and transferred from, the STM-M interface E / 0 718. The signaling can be connected in a connection or transmitted to the control interface directly or via another interface as explained above. The AAL 716 comprises both a convergence sub-layer and a segmentation and reassembly sub-layer (SAR). The AAL obtains the identity of the EO and the ATM VP / VC from the control interface 704. The AAL 716 is operational to convert between the EO format and the ATM format, either in response to a control instruction or without a control instruction. The 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 Nx64 user communications. EO connections are bidirectional and ATM connections are usually unidirectional. As a result, two virtual connections in opposite directions will usually be required for each EO. Those skilled in the art will appreciate how this can be done in the context of the invention. In some cases, it may be desirable to incorporate digital signal processing capabilities at the EO 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 EO 712 interface. Signaling processor 722 is configured to send control messages to the ATM interleaving unit. 702 to implement particular characteristics in particular circuits. Alternatively, search tables can be used to implement particular characteristics for particular circuits or VP / VCs.

THE ALIZATION PROCESSOR The signaling processor receives and processes telecommunications call signaling, control messages and customer data to select connections that establish the communication paths for the calls. In the preferred embodiment, the signaling processor processed the SS7 signaling to select connections for a call. An example of call processing in a call processor and associated maintenance that is performed for call processing is described in US Patent Application Serial No. 09 / 026,766 entitled "System and Method for Treating Cali for Cali 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. Not only can you control the channeling and select the actual connections, but you can also validate the callers, echo control cancellers, generate accounting information, call intelligent network functions, access remote databases, handle traffic and balance loads in network. One skilled in the art will appreciate how the signaling processor described later can be adapted to operate in the above modes. Figure 8 illustrates a mode of a signaling processor. Other versions are also contemplated. In the embodiment of Figure 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 signaling processor 802 can be constructed as modules in a single unit or as multiple units. The signaling interface 804 is externally coupled to signaling systems - preferably to signaling systems having a message transfer part (MTP), a part of the ISDN user (ISUP), a signaling connection control part (SCCP), an intelligent network application part (INAP), and a transaction capability application part (TCAP).

The signaling interface 804 is preferably a platform comprising a level of 1 of MTP 810, a level of 2 of MTP 812, a level 3 of MTP 814, a process of SCCP 816, an ISUP 818 process and a process of TCAP 820. The signaling interface 804 also has INAP functionality. The signaling interface 804 can be linked to a communication device (not shown). For example, the communication device may be an SCP which is interrogated by the signaling interface with a TCAP interrogation to obtain additional data associated with the call. The response message may have additional information parameters that are required to complete the call processing. The communication device can also be an STP or another device. The signaling interface 804 is operational to transmit, process and to receive call signaling. The functionality of TCAP, SCCP, ISUP and INAP uses the services of the MTP to transmit and receive 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 is well known. The programming elements required by a person skilled in the art to configure an SS7 stack are commercially available. An example is the OMNI SS7 stack from Dale, Gesek, McIliams & Sheridan, Inc., (the company DGM &S).

The processes of the signaling interface 804 process the 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 removes the unnecessary header information from the MSU to isolate the message information parameters and passes the parameters to the called processor 808 as the information elements of the call. Examples of these parameters are the called number, the number of the caller and the user service information. Other examples of messages with information elements are an ANM, an ACM, a REL, an RLC, and an INF. In addition, the information elements of the call are transferred from the call processor 808 back to the signaling interfaces 804, and the information elements are traced back to the MSUs and transferred to a signaling point. The CPCS 806 is a management and administration system. The CPCS 806 is the user interface and the interface of external systems in the so-called 808 processor. The CPCS 806 serves as a collector point for data associated with the call such as registers, operational measurement data, statistical information, accounting information and other call data. The CPCS 806 can configure the data associated with the call and / or transmit it to the reporting centers. The CPCS 806 accepts data, such as translations, from a source such as an operations system and updates the data in the tables in the 808 call processor. The CPCS 806 ensures that this data is in the correct format before transferring the data. data to the call processor 808. The CPCS 806 also provides data configuration to other devices including the call processor 808, the signaling interface 804, the interleaving unit (not shown) and the controllable ATM array (not shown). In addition, the CPCS 806 takes into account the remote control of call verification monitoring and call pickup applications from the 808 call processor. The CPCS 806 also serves as a collection point for alarms. The alarm information is transferred to the CPCS 806. The CPCS 806 then transports the 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 register on the CPCS 806 and manage data tables or review data tables at the CPCS or provide maintenance services. The call processor 808 processes the call signaling and controls an ATM interleaving unit, such as an ATM interleaving multiplexer (mux) performing the interleaving of DSOs and VP / VCs and an ATM matrix. However, the so-called 808 processor could control other communication devices and connections in other modes. 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 platform 822 comprises several external interfaces that include an interleaving unit interface, a controllable ATM matrix, an echo interface, a resource control interface, a call information interface and an operations interface. • Control platform 822 is externally coupled to an interlacing unit control, controllable ATM matrix control, echo control, resource control, accounting and operations. The interleaving unit interface exchanges messages with at least one interleaving unit. These messages comprise assignments from DSO to VP / VC, recognition and status information. The controllable ATM matrix interface exchanges messages with at least one controllable ATM matrix. These messages comprise assignments from DSO to VP / VC, assignments from VP / VC to VP / VC, acknowledgments and status information. The echo control interface exchanges messages with echo control systems. Messages exchanged with echo control systems could include instructions to enable or disable echo cancellation in particular DSOs, acknowledgments and status information. The resource control interface exchanges messages with external resources. Examples of such resources are devices that implement the continuity test, encryption, compression, tone detection / transmission, voice detection and voice messaging. The messages exchanged with resources are instructions to apply the resource to the particular DSOs, recognition and state information. For example, a message may instruct a continuity test resource to provide a cycle or to send and detect a tone for a continuity test. The call information interface transfers the relevant call information to a call information processing system, such as to CPCS 806. Typical call information includes the accounting information, such as the parties to the call, the points in the time for the call, and some special features applied to the call. One skilled in the art will appreciate how to produce the programming elements for the interfaces on the control platform 822. The application platform 824 processes the signaling information of the signaling interface 804 to select connections. The identity of the selected connections are provided to the control platform 822 for the interleaving unit interface and / or for the controllable ATM matrix interface. The 824 application platform is responsible for validation, translation, channeling, call control, exceptions, filtering and error handling. In addition to providing the control requirements for the interleaving 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 822 control platform. the application platform 824 generates signaling information for transmission over the signaling interface 804. The signaling information could be for ISUP, INAP or TCAP messages to external network elements. The relevant information for each call is stored in an improved circuit data block (ECDB) for the call. The ECDB can be used to track and post the call.

The application platform 824 preferably operates, in general, in accordance with the basic call state model (BCSM) defined by the ITU. An example of the BCSM is created to handle each call. The BCSM includes a process of origin and a process of termination. The application platform 824 includes a service switching function (SSF) which is used to call the service control function (SCF). Usually, the SCF is contained in an SCP. The SCF is interrogated with TCAP or INAP messages that are transported by the signaling interface 804 and that are initialized or adjusted in initial values with information of the SCF in the application platform 824. The originating or terminating processes will access the remote databases with intelligent network (IN) functionality via the SSF. . The requirements of programming elements for the 824 application platform can be produced in specification and description (SDL) languages defined in ITU-T Z.100 or similar logical or description languages. The SDL can be converted into C code. A real-time case tool such as Telelogic, Inc. SDT or Object Time, Object Time, Inc. can be used. Additional C and C ++ code can be added as required to set the ambient. It will be appreciated that other languages of programming elements and tools can be used.

The call processor 808 may consist of the programming elements described above loaded to a computer. The computer can be a fault-tolerant Unix computer, generally available, such as those provided by Sun, Tandem or Hewlett Packard. It may be desirable to use the multihenebration capability of a Unix operating system. From Figure 8, it can be seen that the application platform 824 processes the signaling information to control numerous systems and to facilitate call connections and services. The signaling of SS7 is exchanged to the so-called processor 808 and the external components via the signaling interface 804, and the control information is exchanged with external systems through the control platform 822. Advantageously, the interface of signaling 804, CPCS 806 and call processor 808 are not integrated into a central processing unit (CPU) of the switch, which is coupled to a switching matrix. Other than an SCP, the components of signaling processor 802 are capable of processing ISUP messages independently of the TCAP queries.

MESSAGE APPOINTMENTS SS7 SS7 messages are well known. Common designations are used for several SS7 messages. Those skilled in the art are familiar with the following message designations: ACM Address Complete Message ANM Response Message BLO Blocking BLA Blocking Recognition CPG Call Progress CGB Blocking Circuit Group CGBA Recognition Blocking Circuit Group GRS Readjustment of the Circuit Group GRA Recognition of the Adjustment of the Circuit Group CGU Unlocking the CGUA Circuit Group Recognition of the Unlocking Group CQM Circuit Interrogating Circuit Group CQR Interrogation Response CRM Circuit Group CRA Circuit Reservation Message CVT Circuit Reservation Recognition CVR Circuit Validation Test CFN Circuit Validation Response COT Confusion CCR Continuity Continuity Verification Request EXM Message Outputs INF Information INR Request Information IAM Initial Address Message LPA PAM Cycle Recognition REL Relay Message RLC Release Complete RSC Release Reset Circuit RES Summary SUS Suspended UBL Unlocking UBA Unblocking Recognition UCIC Uncovered Circuit Identification Code CALL PROCESSOR TABLES Call processing normally covers two aspects. First, an incoming "source" connection is recognized by a call origin 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 termination call process. For example, the termination connection is coupled to the source 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. Figure 9 illustrates an exemplary data structure preferably used by the call processor 802 of Figure 8 to execute the BCSM. This is done through a series of tables that indicate each other in several ways. Indicators usually consist of near-function designations and nearby labels. The next function indicates the next table and the next label indicates an entry or an entry range in that table. It will be appreciated that the indicators for the main call processing are illustrated in Figure 9. The primary data structure has a TDM trunk circuit board 902, an ATM circuit table 904, a trunk group table 906, a table carrier carrier or wave 908, an exception table 910, a table of origin line information (OLI) 912, a table-automatic number identification (ANI) 914, a number filtering table called 916, a number table called 918, a routing table 920, a group service class table (COS) of the trunk group 922 and a message mapping table 924. Also included in the data structure is a table of day of year 926, a table of day of week 928, a table of time of day 930 and a table of time zone 932.

The TDM trunk circuit board 902 contains information required to provide the TDM side of a connection from the call processor site. Each circuit on the TDM side of a connection has an input. The TDM trunk circuit board 902 is accessed from the trunk group table 906 or an external call process, and this indicates the trunk group table. The ATM 904 trunk circuit table contains information required to provide the ATM side of a connection. Normally, a record is presented in this table by ATM trunk group. However, the system can be configured alternatively for multiple registers per trunk group. The ATM trunk circuit table 904 is accessed from the trunk group table 906 or an external call process, and this indicates 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 backbone trunk groups. origin and termination. The trunk group table 906 normally indicates the bearer table 908. However, the trunk group table 906 may indicate the exception table 910, the OLI table 912, the ANI table 914, the number filtering table called 916, the number table called 918, the routing table 920, the day table of the year 926, the day table of the week 928, the time table of the day 930 and the treatment table (see figure 10) . For the predetermined processing of an IAM of an outbound call in the forward direction, when the calling process determines the call tuning and channeling parameters for user communications in 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 indicates the carrier or carrier wave table 908. For the predetermined processing of an IAM of an outgoing call in the direction towards further, when the calling process determines the tuning and channeling parameters of the call for the user communications in the terminating portion, the trunk group table 906 is the next table after the routing table 920 and the group table trunk indicates the TDM or ATM 902 or 904 trunk circuit table. For the default processing of an ACM or ANM of an outgoing call on the dir source ection, when the calling process determines the parameters for signaling, the trunk group table 906 is the next table after the TDM trunk circuit table or ATM 902 or 904 and the trunk group table indicates the message mapping table 924. It will be appreciated that this is the predetermined method and as explained herein, other implementations of table processing may be presented. The bearer table 908 contains information that allows calls to be filtered based on, at least in part, the carrier information parameter and the bearer selection parameter. Carrier table 908 normally indicates exception table 910. However, carrier table 908 can indicate to OLI table 912, table of ANI 914, filtering table of number called 916, table of number called 918, the channeling table 920, the day table of the year 926, the table of day of the week 928, the table of time of day 930, the treatment table (see figure 10), and the table of basic services of data (see figure 11). Exception table 910 is used to identify several exception conditions related to the call that may influence the channeling or handling of the call. Exception table 910 contains information that allows calls to be filtered based on, at least in part, the called party number and the calling party's category. Exception table 910 normally indicates table OLI 912. However, exception table 910 may indicate to table ANI 914, filtering table of called number, table of number called 918, table of channeling 920 , the table of day of the year 926, the table of day of the week 928, the table of time of day 930, the table of proportion of call, the table of control in percent, the table of treatment (see figure 10) and the table of database services (see figure 11). The OLI 912 table contains information that allows calls to be filtered based on, at least in part, the origin line information in an IAM. The OLI 912 table usually indicates the ANI 914 table. However, the OLI table can tell the number filtering table called 916, the number table called 918, the routing table 920, the table of day of year 926, the table of day of the week 928, the table of time of day 930 and the treatment table (see figure 10). The ANI 914 table is used to identify some special features related to the caller's number, which is commonly known as automatic number identification. The ANI 914 table is used to filter and validate an incoming ANI. Specific ANI requirements can be established such as row formation, echo cancellation, time zone and treatment. The ANI 914 table usually indicates the number filtering table called 916. However, the ANI 914 table can tell the number table 918, the routing table 920, the day table of the year 926, the table of day of the week 928, table of time of day 930 and table of treatment (see figure 10). The selection or filtering table of the number called 916 is used to filter called numbers. The selection or filtering table of the number called 916 determines the arrangement of the called number and the nature of the called number. The number filtering table named 916 is used to provide the trigger detection point (TDP) for an AIN SCP TCAP question. This is used, for example, with the local number portability (LNP) feature. The called number filtering table can call a TCAP. The number filtering table called 916 normally indicates the number table called 918. However, the number filtering table 916 may indicate to the routing table 920, the treatment table, the call proportion table, the table of percent (see figure 10), and the table of database services (see figure 11). The table of the number called 918 is used to identify channeling requirements based on, for example, the called number. This will be in case for normal calls. The number table called 918 normally indicates the routing table 910. In addition, the number table called 926 can be configured to alternatively indicate the day table of the year 926. The number table named 918 can also indicate the table of treatment (see figure ) and the table of database services (see figure 11) • The routing table 920 contains information related to the channeling of a call for several connections. The routing table 920 usually indicates the treatment table (see Figure 10). However, the routing table may also indicate the trunk group table 906 and the database services table (see FIG. 11). For the predetermined processing of an IAM of an outgoing call in the forward direction, when the calling process determines the tuning and call routing parameters for user communications, the routing table 920 is the next table after the call. number table 918, and the routing table indicates the trunk group table 906. For the predetermined processing of an IAM of an outgoing call in the forward direction, when the calling process determines the parameters for signaling, the routing table 920 is the next table after the called number table 918, and the routing table indicates the message mapping table 924. It will be appreciated that this is the predetermined method and as explained herein, can be present other implementations of table processing. The trunk group COS table 922 contains information that allows calls to be routed differently based on the service class assigned to the trunk group of origin and the trunk trunk group. The trunk group COS table can indicate the routing table 920 or the treatment table (see figure 10). When the trunk group COS table 922 is used in the processing, after the routing table 920 and the trunk group table 906 are processed, the trunk group table indicates the COS table of the trunk group. The trunk group COS table again indicates the routing table 920 for further processing. The processing then continues with the routing table 920 which indicates the trunk group table 906, and the trunk group table indicating the TDM or ATM 902 trunk circuit board. It will be appreciated that this is the method precletermined and as explained in the present, other implementations of table processing can be presented. The mapping table or message representation 924 is used to provide instructions for the signaling message format of the call processor. This can usually be accessed by the routing table 920 or the trunk group table 906 and usually determines the format of the outgoing messages left by the call processor. The day table of year 926 contains information that allows calls to be routed differently based on the day of the year. The day of the year table normally indicates the routing table 920 which references the time zone table 932 for the information. The day table of year 926 can also indicate the number filtering table called 916, the number table called 918, the routing table 920, the day table of the week 928, the time table of day 930 and the treatment table (see figure 10). The table of the day of the week 928 contains information that allows calls to be routed differently based on the day of the week. The day of the week table normally indicates the routing table 920 and refers to the time zone table 932 for the information. The day table of the week 928 can also indicate the number filtering table called 916, the number table called 918, the time table of day 930 and the treatment table (see figure 10). The time table of day 930 contains information that allows calls to be routed differently based on the time of day. The time table of the day 930 usually indicates the routing table 920 and refers to the time zone table 932 for the information. The 930 day time table can also indicate the number filtering table called 916, the number table called 918 and the treatment table (see figure 10). The time zone table 932 contains information that allows the processing of the call to determine if the time associated with the call processing should be diverted based on the time zone or daylight saving time. The time zone table 932 refers to, and provides information to, the day table of year 926, the table of day of week 928 and the time table of day 930. Figure 10 is an overlay of the figure 9.

The tables of figure 9 are present. However, for clarity, the indicators of the table have been omitted, and some tables have not been duplicated in Figure 10. Figure 10 illustrates additional tables that can be accessed from the tables of Figure 9. These include a table of outbound release 1002, a treatment table 1004, a call proportion table 1006 and a control table in percent 1008 and time / date tables 1010. Outbound release table 1002 contains information that allows call processing to determine how to format an outbound release message Outbound release table 1002 normally indicates treatment table 1006. Treatment table 1004 identifies several special actions that are taken in the course of call processing. For example, based on the incoming trunk group or ANI, different treatments or cause code are used to transport the problems to the called and called parties. This will normally result in the transmission of a release message (REL) and a cause value. The treatment table 1004 normally indicates the outbound release table 1002 and the database services table (see figure 11). The call proportion table 1006 contains information that is used to control call attempts on a basis of one attempt per second. Preferably, attempts of 100 per second to 1 per minute are programmable. The call proportion table 1006 normally indicates the number filtering table 916, the number table 918, the routing table 920 and the treatment table 1004. The control table in percent 1008 contains information that is Use to control call attempts based on a value in percent of traffic that is processed through call processing. The control table in percent 1008 normally indicates the number filtering table 916, the number table 918, the channeling table 920 and the treatment table 1004. The date / time tables 1010 have been identified in Figure 9 as the day table of year 926, the table of the day of the week 928, the table of time of day 926 and the table of time zone 932. This is illustrated in figure 10 as a single location for ease of clarity, but it does not need to be located in this way. Figure 11 is an overlay of Figures 9-10. The tables of Figures 9-10 are present. However, for clarity, the indicators of the table have been omitted, and some tables have not been duplicated in Figure 11. Figure 11 illustrates additional tables that can be accessed from the tables of Figures 9-10 and that are addressed to the TCAP and 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 performance capabilities application part table. transaction (TCAP) 1108 and an advanced intelligent network event (AIN) parameter table 1110. The database services table 1102 contains information about the type of database service requested by the 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 indicates the number table 918. The SCCP table 1104 contains the information and parameters required to construct 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 to route the SCCP message to a destination node. The ISNI table 1106 is referenced by the SCCP table 1104 and provides information to the table of SCCP. The TCAP table 1108 contains the information and parameters required to construct 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 parameter table 1110 contains the information and parameters that are included in the TCAP event message parameter portion. The AIN event parameter table 1110 is referenced by the TCAP table 1108 and provides information to the TCAP table. Figure 12 is an overlay of Figures 9-11. The tables of figures 9-11 are present. However, for clarity, the tables have not been duplicated in Figure 12. Figure 12 illustrates additional tables that can be used to adjust the calling process so that the tables of Figures 9-11 can be used. These adjustment tables 1202 include a site exchange table 1204, an external echo canceller table 1206, an interleaving unit table (IU) 1208, a control matrix ATM (CAM) table 1210 and a table of matrix (CAM) of controllable ATM 1212. The site table of central 1204 contains information that lists the parameters at the central level, some of which are based on information and others that affect the processing of the call. The site central table 1204 provides information to the call processor or switch during initialization or other adjustment procedures, such as the data population or transfer of information to one or more memory locations for use during call processing. External echo canceller 1206 contains information that provides the identifier of the interface and the type of echo canceller when an external echo canceller is required. External echo canceller table 1206 provides information to the call processor or switch during initialization or other tuning procedures, such as data population 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 the interfaces to the interleaving units at the call processor or switch site. The I U table 1208 provides information to the call processor or switch during initialization or other adjustment procedures, such as the data population or transfer of information to one or more memory locations for use during call processing. The interface table of CAM 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 adjustment procedures, such as the data population or transfer of information to one or more memory locations for use during call processing. The tables of CAM 1212 contain information associated with the logical and physical adjustment properties of the CAM. The table of CAM 1212 provides information to the call processor or switch during initialization or other adjustment procedures, such as the data population or transfer of information to one or more memory locations for use during call processing. Figures 13 -42 illustrate examples of the various tables described above. It will be appreciated that other versions of tables can be used. In addition, the information of the identified tables can be combined or changed to form different tables. Figure 13 illustrates an example of a TDM trunk circuit board. The TDM trunk circuit board is used to access information about the source circuit for origin circuit call processing. It is also used to provide information about the terminating circuit for call processing of the terminating circuit. 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 trunk group member number to which the circuit is assigned, and it is used for circuit selection control. The table also contains the trunk circuit identification code (TCIC). The TCIC identifies the trunk circuit that is normally a DSO. The echo canceller (EC) tag entry identifies the echo canceller, if any, that is connected to the circuit. The interleaving unit label (IWU) and the interleaving unit port (IU) identify the location of the physical elements and the port number, respectively, of the interleaving unit. The DS1 / E1 tag and the DS1 / E1 channel denote the DSl or El and the channel within DS1 / 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 use, not equipped if the circuit is reserved and normal if the circuit is installed and available for use. Figure 14 illustrates an example of an ATM trunk circuit table. The ATM trunk circuit table is used to access information about the source circuit for origin circuit call processing. It is also used to provide information about the termination circuit for the termination 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 initial Trunk Circuit Identification Code (TCIC) is the starting TCIC for the trunk group, and is used in the channeling tag of an ISUP message. The transmission interface label identifies the location of the physical elements of the virtual path in which the call will be transmitted. The transmission interface label may designate either an interleaving unit interface or a CAM interface for the designated trunk members. The transmission virtual path identifier (VPI) is the VP that will be used on the side of the transmission circuit of the call. The reception interface tag identifies the location of the physical elements of the virtual path in which the call will be received. The reception interface label may designate either an interleaving unit interface or a CAM interface for the designated trunk members. The receiver virtual path identifier (VTI) is the VP that will be used on the circuit side of receiving the call. The initial state specifies the circuit status when it is installed. Valid states include blocked, if the circuit is installed and blocked from use, not equipped if the circuit is reserved and normal if the circuit is installed and available for use. Figure 15A illustrates an example of a trunk group table. The trunk group number of the trunk group associated with the circuit is used for the key in the trunk group table. The management information field is used for information purposes related to the trunk group and is not normally used in call processing. The associated point code is the point code for the remote end call switch or processor to which the trunk group is connected. The common language location identifier (CLLI) entry is a normalized Bellcore entry for the associated exchange to which the trunk group connects. The trunk type identifies the type of trunk in the trunk group. The trunk type can be a TDM trunk, an ATM trunk of the interleaving unit, or an ATM trunk of the CAM. The associated numbering plan area (NPA) contains information that identifies the switch from which the trunk group originates or to which the trunk group is terminated. The associated jurisdiction information parameter (JIP) contains information that identifies the switch from which the trunk group originates or to which the trunk group is terminated. If an ISUP JIP is not received in an IAM, the default JIP is a value registered in the ECDB of the call processor. If an incoming IAM does not have a JIP, the call processing will populate the outgoing IAM JIP with the default value of the trunk group table. If a JIP is not filled with data, an outgoing JIP is not allowed. 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 the year table, the day of the week table, and the time of day table. The echo canceller information field describes the echo cancellation requirements of the trunk group. Valid entries for 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 disabled for a trunk group that does not require echo cancellation for a call what happens about the group. Figure 15B is a continuation of Figure 15A for the trunk group table. The satellite input specifies that the trunk group for the circuit is connected through a satellite. If the trunk group uses too many satellites, then a call must not use the identified trunk group. This field is used in conjunction with the nature of the connection satellite indicator field from the incoming IAM to determine if the outgoing call can be connected over this trunk group. The selection sequence indicates the methodology that will be used to select a connection. Valid entries for the selection sequence field include the following: busiest, least busy, ascending or descending. The interleaving unit priority (IU) means that outgoing calls will attempt to use a trunk circuit in the same interleaving unit before using a trunk circuit in a different interleaving unit. The glare resolution indicates how a glare situation is going to be resolved. The glare is the double capture of the same circuit. If the glare resolution input is set to "odd / even", the switch or call processor with the highest point code value will control the odd-numbered TCICs within the trunk group. The switch or call processor with the lowest point code value will control the odd-numbered TCICs. If the glare resolution input is set to "all", the call processor controls all the TCICs within the trunk group. If the glare resolution input is set to "none", the call processor will have no glare control and will produce all double captures within the trunk group. The continuity check indicates whether the continuity is to be verified. The continuity for outgoing calls in the originating call processor is controlled in a trunk group base. This field specifies whether continuity is not required or if continuity is required and the frequency of verification required. The field identifies a percentage of calls that require continuity verification. The retry entry specifies how many times the outgoing call will be retested using a different circuit of the same trunk group after a continuity check failure, a glare, or other connection failure. The local number portability (LNP) ignorance information specifies whether or not the incoming LNP information is ignored. The treatment tag is a label in the treatment table for the trunk group used in the call. Because specific trunk group connections may require specific release causes or treatments for a specific client, this field identifies the type of treatment that is required. Message Mapping Label is a label in the message mapping table that specifies the configuration backward message that will be used in the trunk group. Figure 15C is a continuation of Figure 15B for the trunk group table. The row formation entry means that the termination part of the trunk group is capable of forming in rows the calls that originate from a subscriber who called a number ending in this trunk group. The ringing input without response specifies whether the trunk group requires ring timing without response. If the entry is set to zero, the call processing will not use the ringing timer without answer for calls terminated in the trunk group. A non-zero number specifies the ring time without answer in seconds for calls ending in this trunk group. The speech path cut input identifies how much and when the voice path of the termination call will be cut off in the trunk group. Options for this field include the following: connect for a cut in both directions after receipt of an ACM, answer to cut in the backward direction on receipt of an ACM, then cut in the forward direction on receiving an ANM or immediate to cut in both directions immediately after an IAM has been sent. The source class of service (COS) tag provides a label in a class of service table that determines how a call is handled based on the combination of the originating COS and the terminating COS of another trunk group. Based on the combination of this field and the termination COS of another trunk group field, the call will be handled differently. For example, the call can be denied, advanced en route or processed in another way. The termination service class (COS) tag provides a label in a class of service table that determines how a call is handled based on the combination of the origin COS of another trunk group and the termination COS of the present trunk group . Based on a combination of this field and the COS of origin, the call will be handled differently. For example, the call can be denied, advanced en route or processed in another way. Call control provides an Index to a specific trunk group level traffic management control. Valid entries include normal for unapplied control, jump control, extended area telecommunication service (WAN) re-channeling functionality, cancellation control, re-channel control overflow, and immediate redirection control. The next function indicates the next table, and the next label indicates an entry or range of entries in that table. Figure 16 illustrates an example of a carrier table. The carrier label is the key to enter the table. Carrier identification (ID) specifies the carrier to be used by the caller's party. The bearer selection entry identifies how the caller specifies the bearer. For example, this identifies if the caller dialed a prefix digit or if the caller was pre-paid. Carrier selection is used to determine how the call will be routed. The next function indicates the next table, and the next label defines an area in that table for additional call processing. Figure 17 illustrates 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 telephone. The nature of the address number of the called number is differentiated between 0+ calls, 1+ calls, test calls, local routing number (LRN) calls, and international calls. For example, international calls could be routed to a pre-selected international carrier. The "digits from" and the "digits towards" the called number focus on the additional processing unique to a defined range of called numbers. The "digits from" field is a decimal number that varies from 1-15 digits. This can be of any length and, if filling with less than 15 digits, it is filled with zeros for the remaining digits. The "digits to" field is a decimal number that varies from 1-15 digits. This can be of any length and, if it is filled with less than 15 digits, it is filled with 9s for the remaining digits. The next function and next label entries indicate the next table and the next entry within that table for the next channeling function. Figure 18 illustrates an example of the source line information table (OLI). The OLI tag is used as a key to enter the table from a previous next function operation. The origin line information entry specifies the information digits that are being transmitted from a carrier or carrier wave. Different calls are differentiated based on the information digits. For example, the information digits can identify an ordinary subscriber, a multipart line, N00 service, prison service, cellular service or private payment station. The next function and next label entries indicate the next table and the area within that table for the next channeling function. Figure 19 illustrates an example of an automatic number identification table (ANI). The ANI tag is used co or a key to enter the table from a previous next option. The "digits from" and "digits towards" the calling party's number with charge focus the additional processing unique to the ANI within a given range. These entries are considered to determine if the number of the incoming caller falls within the "digits from" and "digits towards" fields. The time zone label indicates the entry in the time zone table that should be used when the date and local time are computed. The time zone label passes over the time zone information of the trunk group table 906. The customer information entry specifies the additional client information on the originating side for the routing of the calling process. The echo cancellation information field (EC) specifies whether or not to apply echo cancellation to the associated ANI. The row formation entry identifies whether or not row information is available to the calling party if the called party is busy. The row formation timers determine the length of time that a call can be formed in a row. The treatment label defines how a call will be treated based on the information in the treatment table. For example, the treatment tag can send a call to a specific record based on a dialed number. The next function and the next label indicate the next table and an area within that table for additional call processing. Figure 20 illustrates an example of a called number filtering table. The called number filtering tag is used as a key to enter the table. The nature of the address of the called number indicates the type of number dialed, for example, national versus international. The address nature entry allows the calling process to route a call differently based on the nature of the address value provided. The entries of "digits from" and "digits towards" focus the additional processing unique to a range of called numbers. The "digits from" and "digits towards" columns both contain digits of the called number, such as the ranges of NPA-NXX that may contain port numbers and are verified by an LRN. This table serves as the trigger detection point (TDP) for a TCAP LNP, for example, when the NPA-NXXs of the donor switches that have had a subscriber port, their numbers are filled with data in the "digit from" fields. "and" digits to ". The field of deleted digits provides the number of digits that will be deleted from the called number before processing continues. The next function and the next label indicate the next table and the area within that table for additional call processing. Figure 21 illustrates an example of a called number table. The called number table is used as a key to enter the table. The address nature of the called number indicates the type of number dialed, for example, national versus international. The entries of "digits from" and "digits towards" focus the additional processing unique to a range of numbers, including the LRNs. The next function and the next label indicate a nearby table and the area within that table used by the additional call processing. Figure 22 illustrates an example of a day of the year table. The day of the year label is used as a key to enter the table. The date field indicates the local date that is applicable to the action that will be taken during the processing of this table. The next function and the next label identify the table and the area within that table for the additional call processing. Figure 23 illustrates an example of a table of day of the week. The day of the week label is a key used to enter the table. The "day from" field indicates the local day of the week in which the action to be taken by this table line entry is to be initiated. The "day to" field indicates the local day of the week in which the action to be taken by this table line entry is to be completed. The next function and the next label identify the next table and the area within that table for additional call processing. Figure 24 illustrates an example of a time of day table. The daytime tag is used as a key to enter the table from a previous next function. The "time from" entry indicates the local time at which the action to be taken will begin. The "time to" field indicates the local time just before the action to be taken stops. The next and next label function entries identify the next table and the area within that table for additional call processing. Figure 25 illustrates 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 the customer's local time and date can be completed. Coordinated universal time (UTC) indicates a deviation from this time zone of UTC. UTC is also known as the GMT or Zulu Greenwich Mean Time. 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. Figure 26 illustrates an example of a channeling table. The channeling table is used as a key to enter the table from a previous next function. The route number specifies a route within a list of routes. The call processing will process the route selections for a given route label in the order indicated by the route numbers. The next function and the next label identify the next table and the area within that table for additional call processing. The signal path tag is associated with the next action that is going to be taken by the call processing, for this call. The signal path tag provides the Index to access the message mapping tag. The signal path tag is used in order to modify the parameter data fields in a signaling message that is being propagated to a nearby switch or a near call processor. Figure 27 illustrates an example of a service class (COS) table of the trunk group. The COS backbone COS label and the TERM backbone COS label are used as keys to enter the table and define the call processing. The next function identifies the next action that will be taken by the call processing for this call. Valid entries in the next function column can be continued, processed, advanced en route or routed. Based on these inputs, the call processing can continue using the current trunk group, send the calls to the treatment, skip the current trunk group and the route table and go to the next trunk group in the list or send the call to a label different in the channeling table. The next label entry is an indicator that defines the trunk group that the next function will use to process the call. This field is ignored when the next function is continued or advanced en route. Figure 28 illustrates an example of a treatment table. The treatment tag is a key used to enter the table. The treatment tag is a designation in a call process that determines the disposition of the call. The error / cause label corresponds to either the internally generated error conditions and the call processing or the 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 error conditions of the call processing and a series of labels for all the incoming release message cause values . The next function and the next label indicate the next table and the area within that table for additional call processing. Figure 29 illustrates an example of an outbound release table. The outbound release label is used as a key to enter the table for processing. The location of the outgoing cause value identifies the type of network that will be used. For example, the location entry can specify a local or remote network or a private, international transit network. The coding standard identifies the standard with a standard of the International Telecommunication Union (ITU) or a standard of the National Standards Institute of America (ANSÍ). The cause value designates the error, maintenance or offline processes. Figure 30 illustrates an example of a percent control board. 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 function The next control allows attempts to connect to another table during call processing to be channeled. The next control label indicates an area within that for additional call processing. The next passed function allows only incoming attempts to be routed to another table. The next label indicates an area in that table for additional call processing. Figure 31 illustrates an example of a call proportion table. The call proportion label is used as a key to enter the table. The call proportion specifies the number of calls that will be passed by the control at termination or for termination. Call processing will use this information to determine if the incoming call number falls within this control. The next control function allows one blocked call attempt to be routed to another table. The next control label is an indicator that defines the area in the next table for additional call processing. The next-pass function allows only one incoming call attempt to be redirected to another table. The next passed function is an indicator that defines an area in that table for additional call processing. Figure 32 illustrates an example of a database services table. The database services label is used as a key to enter the table. The type of service determines the type of logic that is applied when it is constructed and answers to the database queries. The types of service include local number portability and translation of number N00.

The signaling connection control part label (SCCP) identifies a location within an SCCP table for additional 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 the information contained in the database services table, as well as the information received from a database query. The next label entry specifies an area within the table identified in the next function for further processing. Figure 33A illustrates 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 unit data messages and extended unit data 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 offline transactions to determine if messages are discarded or returned in an error condition. The message handling field identifies the call processor or destination switch to handle the SCCP message if it is received with errors. This field will designate that the message will be discarded or returned. The hop counter input (jump of the radio wave from the ground to the ionosphere and back) denotes the number of nodes through which the SCCP message can be routed before the message is returned with a condition of error. 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. Intermediate signaling network identification (ISNI) fields allow the SCCP message to traverse different networks in order to reach a desired node. The ISDNI 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 channeling to go through other networks. The brand identification subfield identifies whether or not the network identification will be used for this SCCP message. The tag subfield identifies a unique address in the ISNI table when the route indicator subfield is set to "restricted" and the brand identification subfield is set to "yes". Figure 33C is a continuation of Figure 33B for the SCCP table. Figure 33C identifies the field and subfields of the called party address to provide information as to how to channel this SCCP message. The address indicator subsystem (SSN) number indicates whether or not a subsystem number will be included in the address of the called party. The point code entry indicates whether or not a point code will be included in the address of the caller's party. The global title indicator subfield identifies whether or not a global title translation will be used to channel the SCCP message. If a global title translation is selected, this subfield also identifies the type. The channeling indicator subfield identifies the elements that will be used to channel the message. Valid entries include the global title and the point code. The national / international subfield identifies whether the SCCP message will use national or international channeling and tuning. 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 to channel messages that do not require SCCP translation. The global title translation field allows intermediate nodes to translate SCCP messages, so that the messages can channel to the correct destination with the correct point code. The global type translation type entry directs the SCCP message to the correct global title translation function. The coding scheme identifies how the type of address will be coded. The number plan subfield identifies the numbering plan that will be sent to the destination node. The address type subfield will identify what type of address to use for the address digits and the SCCP routing through the network.

Figure 33D is a continuation of Figure 33C for the SCCP table. Figure 33D identifies the address field of the calling party that contains the channeling information that the destination database uses to retain the SCCP message. The address indicator subsystem (SSN) number indicates whether or not a subsystem number will be included in the address of the called party. The dot code subfield indicates whether or not a point code will be included in the address of the caller's party. The global title indicator subfield identifies whether or not global title translation will be used to channel the SCCP message. The channel indicator subfield identifies which elements will be used throughout the message. This field can include global title elements or point code elements. The national / international subfield identifies whether the SCCP will use national or international channeling and adjustment. The subsystem number identifies a subsystem number for the SCCP message. The point code number field identifies the destination point code to which the SCCP message will be routed. Global title translations allow intermediate nodes to translate SCCP messages and channel messages to the correct destination. The type of global title translation directs the SCCP message to the correct global title translation function. The coding scheme identifies how it will be coded is type of address. The number plan identifies the number plan that will be sent to the destination node. The address type subfield identifies what type of address to use for address digits in the SCCP routing through the network. Figure 34 illustrates an example of an intermediate identification network identification (ISNI) table. The ISNI table contains a list of networks that will be used to route SCCP messages to the destination node. The ISNI tag is used as a key to enter the table. Network fields 1-16 identify the network number of up to 16 networks that can be used to route the SCCP message. "Figure 35 illustrates an example of a Transaction Capabilities Application Part Table (TCAP) The TCAP label is used as a key to enter the table The type of TCAP identifies the type of TCAP that will be constructed The TCAP types include the Advanced Intelligent Network (AIN) and Distributed Intelligent Network Architecture (DINA) .The tag class indicates whether the message will use a common or patented structure.The packet type field identifies the type of packet which will be used in the transaction portion of the TCAP message.The component type field identifies the type of component that will be used in the component portion of the TCAP message.The message type field identifies the type of TCAP message The message types include variable options depending on whether they are AIN message types or DINA message types Figure 36 illustrates an example of an external echo canceller table. If an external echo canceller is being used in the circuit, and if so, the type of echo canceller. The echo canceller label indicates a location in the controllable ATM matrix for additional 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 illustrates an example of an interlacing unit interface table. The interleaving unit (IWU) is a key that is used to enter the table. The identification (ID) of IWU identifies which interlacing unit is being addressed. Receptacles 1-4 of the internet protocol (IP) specify the IP plug address of any of the four connections to the interlacing unit. Figure 38 illustrates an example of a controllable ATM matrix interchange (CAM) table. The CAM interface tag is used as a key to enter the table. The CAM tag indicates that CAM contains the interface. The logical interface input specifies a logical interface or port number in the CAM. Figure 39 illustrates an example of a controllable ATM ATM (CAM) matrix table. The CAM tag is used as a key to enter the table. The CAM type indicates the type of CAM control protocol. The CAM address identifies the CAM address. Figure 40A illustrates an example of a central table of the call processor or switch site. The CLLI name of the exchange indicates a CLLI of the associated exchange for the call processor or switch. The identifier (ID) of the site node of the call processor or switch specifies the identifier of the node of the call processor or switch. The originator identifier (ID) of the call processor or switch specifies a source identifier of the call processor or switch. The identifier (ID) of programming elements specifies a release identifier of programming elements. The identifier (ID) of the call processor specifies the identifier of the call processor or switch that is sent to the interleaving units. Figure 40B is a continuation of Figure 40A of the central table of the call processor or switch site. The automatic congestion control (ACC) specifies whether the ACC is enabled or disabled. The start of level 1 of automatic congestion control (ACL) identifies a value in percentage of start of use of a first temporary buffer. The abatement entry of ACL1 specifies a utilization abate percentage for a first temporary buffer. The ACL start entry 2 specifies a start level for a second temporary buffer. The ACL abatement input 2 specifies a percentage of abatement utilization level of the buffer or temporary memory for a second buffer. The start input of ACL 3 specifies a percentage of start level of utilization of the buffer for a third buffer. The ACL abatement entry 3 specifies a percentage of abatement level of buffer utilization for a third buffer or temporary. Figure 40C is a continuation of Figure 40B for the central table of the call processor or switch site. The maximum trunks for the pick-up queue (OHQ of trunk trunks) specifies a maximum number of trunk groups that can have the pick-up waiting queue enabled. The OHQ timer 1 input (TQ1) specifies the number of milliseconds for off-hook timer No. 1. OHQ timer input 2 (TQ2) specifies the number of seconds for off-hook timer number 2. The unanswered ringing timer specifies the number of seconds for the ringing timer without answer. The active billing entry specifies whether the ECDBs are being sent to the call processing control system (CPCS). The entry that allows network management (NWM) identifies whether or not allowed or not allowed a selective trunk reservation and group control. The free call entry without billing specifies whether a call will not be billed if the billing process is not available. The free call without billing will be already enabled for free calls or disabled so that there are no free calls. Fig. 40D is a continuation of Fig. 40C for the central table of the call processor or switch site. The maximum hop counts (max) identify the number of hops of the call or switch processor that can be made in a single call. The maximum searches (max) in table identify the table search number that can be made for a single call. This value is used to detect closed circuits in channeling tables.

Figures 41A-41B depict an example of advanced intelligent network event (AIN) parameter table. The AIN event parameter table has two columns. The first identifies the parameters that will be included in the parameter portion of the TCAP event message. The second entry may include information for analysis. Figure 42 illustrates an example of a message mapping table. This table allows the call processor to alter the information in outgoing messages. The message type field is used as a key to enter the table and illustrates the type of outgoing normal message. The parameter input is a relevant parameter within the outgoing message. The indices indicate several entries in the trunk group and determine if the parameters are based without change, omitted, or modified in outgoing messages. Those skilled in the art will appreciate that variations of the specific embodiments described above are contemplated by the invention. The invention should not be restricted to the above modalities, but must be commensurate with the following claims. It is noted that, in relation to this date, the best method known to the applicant to carry out the aforementioned invention, is that which is clear from the present description of the invention.

Claims (20)

1. CLAIMS Having described the invention as above, it is claimed as property, contained in the following claims: 1. A communication system comprising a first switching system coupled to a first connection and a second connection and configured to transfer first communications for a first call on the first connection and to transfer second communications for a second call on the second connection when the first connection is not available for the second call, a second switching system coupled to the first connection and a third connection and configured to receive the first communications for the first call on the first connection and for receiving the second communications for the second call on the third connection, the connection system is characterized in that it comprises: a matrix of asynchronous transfer mode coupled to a first link, to the second Connection and the third connection and configured to receive a control message on the first link, to receive the second communications for the second call on the second connection and to channel the second "communications for the second call to the third connection using a mode connection. asynchronous transfer in response to the control message; and a signal processor coupled to the first link and a second link and configured to receive an initial address message for the second call of the second link, to process the initial address message to select the asynchronous transfer mode connection, to indicate the asynchronous transfer mode connection in the control message and to transfer the control message to the first link. The communication system according to claim 1, characterized in that the first connection, the second and the third connection use a time division multiplexing protocol and wherein the asynchronous transfer mode matrix further includes a first time unit. interleaving configured to convert the communications for the second call of the time division multiplexing protocol to an asynchronous transfer mode protocol and a second interleaving unit configured to convert the communications for the second call of the transfer asynchronous mode protocol again to the multiplexing protocol by time division. The communication system according to claim 1, characterized in that the asynchronous transfer mode matrix further includes an interleaving unit configured to convert the communications for the second call into an asynchronous transfer mode protocol. The communication system according to claim 1, characterized in that the asynchronous transfer mode matrix is configured to cancel the echo of the communications for the second call. The communication system according to claim 1, characterized in that the signaling processor is configured to process the initial address message to select echo cancellation and to indicate. the echo cancellation in the control message and wherein the asynchronous transfer mode matrix is configured to cancel the echo of the second communications for the second call in response to the control message. The communication system according to claim 1, characterized in that the signaling processor is configured to process the initial address message to select the third connection for the second call and to indicate the third connection in the control message. The communication system according to claim 1, characterized in that the signaling processor is configured to process a called number in the initial address message to select the asynchronous transfer mode connection. 8. The communication system according to claim 1, characterized in that the signaling processor is configured to process a caller number in the initial address message to select the asynchronous transfer mode connection. The communication system according to claim 1, characterized in that the signaling processor is configured to process the initial address message to access a service control point to select the asynchronous transfer mode connection. The communication system according to claim 1, characterized in that the first connection is not available for the second call due to high traffic. A method for putting into operation a communication system comprising a first switching system coupled to a first connection and a second connection and a second switching system coupled to a first connection and a third connection, wherein the communication system uses the steps of transferring the first communications for a first call of the first switching system on the first connection to the second switching system, transferring the second communications for a second call of the first switching system on the second connection when the first connection is not available for the second call, and receiving the second communications for the second call on the third connection, the method is characterized in that it comprises the steps of: receiving an initial address message for the second call of a second link in a signaling processor and process the address message Initial setting to select an asynchronous transfer mode connection; , transferring a control message indicating the asynchronous transfer mode of the signaling processor on a first link to an asynchronous transfer mode array; receive the second communications for the second call on the second connection in the asynchronous transfer mode matrix; and in the asynchronous transfer mode array, channeling the second communications for the second call to the third connection using the asynchronous transfer mode connection in response to the control message. The method according to claim 11, wherein the first connection, the second connection and the third connection use a time division multiplexing protocol and characterized in that it further comprises, in the asynchronous transfer mode matrix, converting the communications for the second call of the time division multiplexing protocol to an asynchronous transfer mode protocol and convert the communications for the second call of the asynchronous transfer protocol again to the time division multiplexing protocol. Í3. The method in accordance with the claim 11, characterized in that it further comprises converting the communications for the second call into an asynchronous transfer mode protocol. The method according to claim 11, characterized in that it further comprises canceling the echo of the communications for the second call in the asynchronous transfer mode matrix. The method according to claim 11, characterized in that it further comprises processing the initial address message in the signaling processor to select echo cancellation, indicate echo cancellation in the control message and cancel the echo of the second communications for the second call in the asynchronous transfer mode array in response to the control message. 16. The method according to claim 11, characterized in that it further comprises processing the initial address message in the signaling processor to select the third connection for the second call and indicating the third connection in the control message. The method according to claim 11, characterized in that it further comprises processing a called number in the initial address message in the signaling processor to select the asynchronous transfer mode connection. The method according to claim 11, further comprising processing a calling number in the initial address message in the signaling processor to select the asynchronous transfer mode connection. The method according to claim 11, characterized in that it further comprises processing the initial address message in the signaling processor to access a service control point to select the asynchronous transfer mode connection. 20. The method according to claim 11, characterized in that the first connection is not available for the second call due to high traffic.