System and method for transporting a call in a telecommunication network

RELATED APPLICATIONS

0001This patent application is a continuation of patent application Ser. No. 09/790,114, entitled “System and Method for Transporting A Call in a Telecommunication Network,” filed on Feb. 20, 2001, which is a continuation of U.S. Pat. No. 6,262,992, entitled “System and Method for Transporting A Call in a Telecommunication Network,” filed May 18, 1998, which is a continuation of patent application Ser. No. 08/754,846, entitled “System and Method for Transporting A Call in a Telecommunication Network,” filed Nov. 22, 1996, now abandoned, and which is hereby incorporated by reference into this patent application.

FEDERALLY SPONSERED RESEARCH OR DEVELOPMENT

0002Not applicable

MICROFICHE APPENDIX

0003Not applicable

FIELD OF THE INVENTION

0005The present invention relates to the field of telecommunication communications transport and processing.

SUMMARY OF THE INVENTION

0006Examples of the invention include a communication system and its method of operation. The communication system comprises a signaling processor and an interworking unit. The signaling processor receives and processes a first message for a call to select a time division multiplex connection for the call and transfers a second message indicating the selected time division multiplex connection. The interworking unit receives the second message indicating the selected time division multiplex connection, receives user communications for the call in a packet format, converts the user communications from the packet format to a time division multiplex format, and transfers the user communications in the time division multiplex format over the selected time division multiplex connection. The interworking unit monitors the user communications for a trigger after call set-up and during the call, and if the trigger is detected, transfers a third message indicating the trigger. The signaling processor receives and processes the third message to select routing information for routing the call to a service platform and transfers a fourth message indicating the selected routing information to route the call to the service platform.

DESCRIPTION OF THE DRAWINGS

0007<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram of the system for detecting a call trigger.

0008<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram of a system for detecting a tone with a tone detector internal to an interworking unit.

0009<figref idref="DRAWINGS">FIG. 3</figref> is a block diagram of a system for detecting a tone with a tone detector external to an interworking unit.

0010<figref idref="DRAWINGS">FIG. 4</figref> is a block diagram of a system for processing a call trigger using a service platform.

0011<figref idref="DRAWINGS">FIG. 5</figref> is a block diagram of a system for detecting a call trigger in which the system interacts with local communication devices.

0012<figref idref="DRAWINGS">FIG. 6</figref> is a process diagram of message sequences for a system for detecting a call trigger.

0013<figref idref="DRAWINGS">FIG. 7</figref> is a message sequence chart for a system for detecting a call trigger.

0014<figref idref="DRAWINGS">FIG. 8</figref> is a functional diagram of an interworking unit for use in a synchronous optical network system.

0015<figref idref="DRAWINGS">FIG. 9</figref> is a functional diagram of an interworking unit for use in a synchronous digital hierarchy system.

0016<figref idref="DRAWINGS">FIG. 10</figref> is a block diagram of a signaling processor constructed in accordance with the present system.

0017<figref idref="DRAWINGS">FIG. 11</figref> is a block diagram of a data structure having tables that are used in the signaling processor of <figref idref="DRAWINGS">FIG. 10</figref>.

0018<figref idref="DRAWINGS">FIG. 12</figref> is a block diagram of additional tables that are used in the signaling processor of <figref idref="DRAWINGS">FIG. 11</figref>.

0019<figref idref="DRAWINGS">FIG. 13</figref> is a table diagram of a trunk circuit table used in the signaling processor of <figref idref="DRAWINGS">FIG. 12</figref>.

0020<figref idref="DRAWINGS">FIG. 14</figref> is a table diagram of a trunk group table used in the signaling processor of <figref idref="DRAWINGS">FIG. 12</figref>.

0021<figref idref="DRAWINGS">FIG. 15</figref> is a table diagram of an exception circuit table used in the signaling processor of <figref idref="DRAWINGS">FIG. 12</figref>.

0022<figref idref="DRAWINGS">FIG. 16</figref> is a table diagram of an automated number index table used in the signaling processor of <figref idref="DRAWINGS">FIG. 12</figref>.

0023<figref idref="DRAWINGS">FIG. 17</figref> is a table diagram of a called number table used in the signaling processor of <figref idref="DRAWINGS">FIG. 12</figref>.

0024<figref idref="DRAWINGS">FIG. 18</figref> is a table diagram of a routing table used in the signaling processor of <figref idref="DRAWINGS">FIG. 12</figref>.

0025<figref idref="DRAWINGS">FIG. 19</figref> is a table diagram of a treatment table used in the signaling processor of <figref idref="DRAWINGS">FIG. 12</figref>.

0026<figref idref="DRAWINGS">FIG. 20</figref> is a table diagram of a message table used in the signaling processor of <figref idref="DRAWINGS">FIG. 12</figref>.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

0027Telecommunication systems provide services and processing for telecommunication calls between communication devices. Each call has call signaling and user communications. The user communications contain the caller's information, such as a voice communication or data communication, and they are communicated over a connection. Call signaling contains information that facilitates call processing, and it is communicated over a link. Call signaling, for example, contains information describing the called number and the calling number. Examples of call signaling are standardized signaling, such as SS7, C7, integrated services data network (ISDN), and digital private network signaling system (DPNSS), which are based on ITU recommendation Q.933.

0028A call can be transmitted from a communication device. A communication device can be, for example, customer premises equipment, a call processing platform, a switch, or any other device capable of initiating, handling, or terminating a call. Customer premises equipment can be, for example, a telephone, a computer, a facsimile machine, or a private branch exchange. A call processing platform can be, for example, a service platform or any other enhanced platform that is capable of processing calls.

0029The user communications and the call signaling may be transported by a communication device through an in-band transmission, such as superframe (SF) or extended superframe (ESF), over a time division multiplex (TDM) carrier Such as a digital signal (DS) level communication line. Digital signal level zero (DS0), digital signal level one (DS1), and digital signal level three (DS3) are common designations that carry in-band communications. Other equivalent designations also carry in-band traffic. For example, European communication systems such as European level one (E1), European level 2 (E2), European level 3 (E3), and European level four (E4) are common designations that carry in-band communications.

0030In addition, call signaling and user communications may be transported out-of-band on separate transport paths, separate transport channels, separate transport connections, or separate transport media. These transports may be carried over DS level or equivalent European level media, as well as higher speed optical and electrical systems, such as synchronous optical network (SONET) and synchronous digital hierarchy (SDH). For example, signaling system 7 (SS7) and the European equivalent, C7, transport signaling traffic out-of-band. Moreover, narrowband systems such as ISDN and broadband systems such as broadband integrated services data network (B-ISDN), including B-ISDN over asynchronous transfer mode (ATM), transport call signaling and user communications out-of-band.

0031Broadband systems provide greater bandwidth than narrowband systems for calls, in addition to providing digital processing of the calls, error checking, and correction. ATM is one technology that is being used in conjunction with SONET and SDH to provide broadband call switching and call transport for telecommunication services.

0032ATM is a protocol that describes communication of user communications in ATM cells. Because the protocol uses cells, calls can be transported on demand for connection-oriented traffic, connectionless-oriented traffic, constant-bit traffic, variable-bit traffic including bursty traffic, and between equipment that either requires timing or does not require timing.

0033ATM systems handle calls over switched virtual paths (SVPs) and switched virtual circuits (SVCs). The virtual nature of ATM allows multiple communication devices to use a physical communication line at different times. This type of virtual connection more efficiently uses bandwidth, and thereby provides more cost efficient transport for customer calls, than permanent virtual circuits (PVCs) or other dedicated circuits.

0034The ATM system is able to connect a caller from an origination point to a destination point by selecting a connection from the origination point to the destination point. The connection contains a virtual path (VP) and a virtual channel (VC). A VC is a logical connection between two end points for the transfer of ATM cells. A VP is a logical combination of VCs. The ATM system designates the selected connection by specifying a virtual path identifier (VPI) that identifies the selected VP and a virtual channel identifier (VCI) that identifies the selected VC within the selected VP. Because ATM connections are uni-directional, bi-directional communications in an ATM system usually require companion VPIs/VCIs.

0035The SONET and SDH protocols describe the physical media and protocols upon which the communication of ATM cells takes place. SONET includes optical transmission of optical carrier (OC) signals and electrical transmission of synchronous transport signals (STSs). SONET signals transmit at a and synchronous transport signal level one (STS-1). Also transmitted are multiples thereof, such as an STS level three (STS-3) and an OC level three (OC-3) at rates of 155.52 Mbps and an STS level twelve (STS-12) and an OC level 12 (OC-12) at rates of 622.08 Mbps, and fractions thereof, such as a virtual tributary group (VTG) at a rate of 6.912 Mbps. SDH includes transmission of optical synchronous transport module (STM O) signals and electrical synchronous transport module (STM E) signals. SDH signals transmit at a base rate of 155.52 Mbps for synchronous transport module level one electrical and optical (STM-1 E/O). Also transmitted are multiples thereof, such as an STM level four electrical/optical (STM-4 E/O) at rates of 622.08 Mbps, and fractions thereof, such as a tributary unit group (TUG) at a rate of 6.912 Mbps.

0036Telecommunication systems require call setup information to initiate a connection between communication devices. The call setup uses information in the call signaling to make the correct connection between the communication devices so that the user communications can be transported across the connection between the communication devices.

0037Enhanced services may be required during call setup for call routing and call signaling processing. Such enhanced services are provided by service providers such as service platforms. The service platforms are used to provide interactive applications with communication devices via voice commands, tones, or in-band protocols such as facsimile protocols. The calls are connected to the service platform through a port on the service platform. Once a service platform interacts with the communication devices and obtains the information needed to complete the call routing or processing, the service platform typically is released from the call, and the port can be used to connect to another call.

0038However, some calls require processing of a call trigger in mid-call after the setup is complete and while the call is connected between communication devices. A call trigger is an event or signal that causes some call processing, call translation, or call routing to occur when trigger criteria is satisfied. For example, a call trigger could be a tone, such as a tone which occurs when the number five is pressed on a telephone keypad, some other dial pad, or other tone generating device. If a communication device such as, for example, a service platform, is receiving the call, and if the call trigger satisfies a criterion that is recognized by the communication device as being valid and causing some processing to occur, then the communication device, or the system controlling the communication device, can cause the processing to occur. For example, transmitting a tone, an on-hook signal, a voice command, or an in-band protocol could cause the call to be routed to another communication device or cause menu options to be transmitted to the communication device that is originating the call.

0039Unfortunately, many conventional systems require that the service platform remain connected to the call to detect a call trigger. Therefore, a system is needed to detect a call trigger without requiring a service platform to remain connected to the call.

0000The Embodiments of <figref idref="DRAWINGS">FIGS. 1-7</figref>

0040The system of the present invention allows calls to be released from a service provider, such as a service platform, after the service platfomm's interactive applications have been completed. Therefore, the service platform is not required to remain on the connection for the duration of the call to detect a call trigger. Thus, the interactive applications that require call triggers to initiate their implementation use fewer service platform ports because the service platform only needs to be in the call for the time period during which the interactive application is implemented. This time period is typically much shorter than the duration of the entire call.

0041<figref idref="DRAWINGS">FIG. 1</figref> illustrates the use of a call trigger system in accordance with the present invention. In <figref idref="DRAWINGS">FIG. 1</figref>, a telecommunication system <b>102</b> has a call trigger system <b>104</b>. The call trigger system <b>104</b> can receive one or more calls and route the calls to the appropriate device.

0042The call trigger system <b>104</b> interacts with a first communication device <b>106</b>, a second communication device <b>108</b>, and a third communication device <b>110</b>. Each of the communication devices <b>106</b>, <b>108</b>, and <b>110</b> comprises customer premises equipment, a call processing platform, a switch, or any other device capable of initiating, handling, or terminating a call, including a telephone, a computer, a facsimile machine, a private branch exchange, a service platform, or an enhanced platform that is capable of processing calls. The call trigger system <b>104</b> contains a signaling processor <b>112</b> and an interworking unit <b>114</b>. It will be appreciated that other communication devices may be included. However, the number of communication devices shown has been restricted for clarity.

0043Links are used to transport call signaling and control messages. The term “link” as used herein means a transmission media used to carry call signaling and control messages. For example, a link would carry call signaling or a device control message containing device instructions and data. A link can carry, for example, out-of-band signaling such as SS7; C7, ISDN, B-ISDN, GR-303, local area network (LAN), or data bus call signaling. A link can be, for example, an AAL5 data link, UDP/IP, ethernet, or DS0 over TI. In addition, a link, as shown in the figures, can represent a single physical link or multiple links, such as one link or a combination of links of ISDN, SS7, TCP/IP, or some other data link. The term “control message” as used herein means a control or signaling message, a control or signaling instruction, a control or signaling signal, or signaling instructions, whether proprietary or standardized, that convey information from one point to another.

0044Connections are used to transport user communications and other device information between the elements and devices of the telecommunication system <b>102</b>. The term “connection” as used herein means the transmission media used to carry user communications between communication devices or between the elements of the telecommunication system <b>102</b>. For example, a connection could carry a user's voice, computer data, or other communication device data. A connection can be associated with either in-band communications or out-of-band communications.

0045A system of links and connections connect the elements of the telecommunication system <b>102</b>. The signaling processor <b>112</b> communicates with the first communication device <b>106</b> through a link <b>116</b>, with the interworking unit <b>114</b> through a link <b>118</b>, with the second communication device <b>108</b> through a link <b>120</b>, and with the third communication device <b>110</b> through a link <b>122</b>. The interworking unit <b>114</b> communicates with the first communication device <b>106</b> over a connection <b>124</b>, with the second communication device <b>108</b> over a connection <b>126</b>, and with the third communication device <b>110</b> over a connection <b>128</b>. It shall be appreciated that other links can extend from the signaling processor <b>112</b> to other systems, networks, or devices. In addition, other connections may extend from the interworking unit <b>114</b> or the communication devices <b>1</b>.<b>06</b>, <b>108</b>, and <b>110</b> to other systems, networks, or devices.

0046The signaling processor <b>112</b> accepts call signaling or control messages from, or transmits call signaling or control messages to, other elements or devices in the telecommunication system <b>102</b>. The signaling processor <b>112</b> thereby controls call routing and call processing in the telecommunication system <b>102</b>. One embodiment of the signaling processor <b>112</b> is discussed in more detail below.

0047The interworking unit <b>114</b> interworks connections on a call-by-call basis. The interworking unit <b>114</b> may be an ATM interworking multiplexer that interworks between the ATM format and other formats while providing multiplexing and demultiplexing functions, or it may be an ATM interworking unit that interworks between different types of ATM systems and provides domain addressing. In addition, the interworking unit <b>114</b> may be a unit with domain addressing capabilities only, an ATM multiplexer that provides multiplexing and demultiplexing functions for ATM cells, or other types of interworking units.

0048The interworking unit <b>114</b> accepts user communications from, and transports user communications to, the first communication device <b>106</b>, the second communication device <b>108</b>, and the third communication device <b>110</b>. Preferably, the interworking unit <b>114</b> is an ATM interworking multiplexer that interworks between a first communication device <b>106</b> that communicates user communications in a TDM format over a DSO and either a second or third communication device <b>108</b> or <b>110</b> that communicates user communications in the ATM format over a SONET pipe or an SDH pipe. However, it will be appreciated that the communication devices <b>106</b>, <b>108</b>, and <b>110</b> may be either TDM or ATM devices and interworking can be completed between any formats. One type of interworking unit that is compatible with the present system is discussed more fully below.

0049The interworking unit <b>114</b> accepts control messages from, and sends control messages to, the signaling processor <b>112</b>. The interworking unit <b>114</b> uses the information gained from the signaling processor's control message to identify the required interworking assignment so that the user communications are converted between the format that is compatible with the first communication device <b>106</b> and the formats that are compatible with the second or third communication devices <b>108</b> and <b>110</b>.

0050The control message from the signaling processor <b>112</b> designates a selected connection between the first communication device <b>106</b> over its connection <b>124</b> and the second communication device <b>108</b> over its connection <b>126</b>. Alternatively, the control message designates a selected connection between the first communication device <b>106</b> over its connection <b>124</b> and the third communication device <b>110</b> over its connection <b>128</b>. Both of the connections are connected at the interworking unit <b>114</b>.

0051For DS0to ATM interworking, a selected connection is designated by a selected VPI/VCI for ATM formatted communications, or a selected DS0 for TDM communications. The interworking unit <b>114</b> interworks the user communications between the devices over the selected connection. Thus, for example, user communications can be converted between ATM VPI/VCIs and TDM DS0s. In such an example, user communications are mapped dynamically from selected VPI/VCIs to selected DS0s, and user communications are mapped dynamically from selected DSOs to selected VPI/VCIs.

0052Referring still to <figref idref="DRAWINGS">FIG. 1</figref>, the interworking unit <b>114</b> is a monitoring interworking unit. The monitoring interworking unit <b>114</b> is capable of detecting a call trigger in the user communications as the user communications enter the interworking unit. Generally, the interworking unit <b>114</b> detects the call trigger from TDM formatted user communications. Thus, where, for example, user communications are converted from a TDM format originating from the first communication device <b>106</b> over a DSO connection <b>124</b> to the ATM format destined for a second communication device <b>108</b> over a SONET connection <b>126</b>, the call trigger would be detected from the DS0 connection <b>124</b> as the user communications enter the interworking unit <b>114</b>.

0053The interworking unit <b>114</b> can contain either hardware or software that detects the call trigger. Preferably, the interworking unit <b>114</b> has a digital signal processor, discussed hereafter, that is programmed to process the user communications and to detect the call trigger as the user communications pass through the interworking-unit. For example, if the telecommunication system <b>102</b> uses a dual tone multi-frequency signal (DTMF, hereinafter “a tone”) as a call trigger, the interworking unit <b>114</b> can be programmed through software in the digital signal processor to detect the tone during user communications processing. Alternately, a processor card can be installed in the interworking unit <b>114</b> to detect the call trigger.

0054The interworking unit <b>114</b> can be configured for multiple detection options. The interworking unit <b>114</b> can be configured to detect a call trigger, such as a tone, and strictly transmit the call trigger data to the signaling processor <b>112</b> without first processing the call trigger data. In this option, all call trigger data is sent to the signaling processor <b>112</b> without validation in screening.

0055Alternately, the interworking unit <b>114</b> can be configured to detect a call trigger, such as a tone, and transmit the call trigger data to the signaling processor <b>112</b> after processing the call trigger data to determine what the call trigger is thereby defining the type of call trigger and after completing validation and screening. In this second option, the interworking unit <b>114</b> could, for example, detect a tone as a call trigger, determine that the tone is a “3,” and notify the signaling processor <b>112</b> that a tone “3” was received.

0056In addition, the interworking unit <b>114</b> can be configured to detect a call trigger, but to only accept and process call trigger data that is within a subset of call trigger data. In this instance, the interworking unit <b>114</b> completes call validation and screening. In this third option, the interworking unit <b>114</b> could, for example, only accept call trigger data that is a tone “3” or a tone “*” and transmit the call trigger data to the signaling processor <b>112</b> if the call trigger is valid.

0057If the interworking unit <b>114</b> detects a call trigger, it reports the detection to the signaling processor <b>112</b> in an interworking unit control message. The signaling processor <b>112</b> determines if the call trigger is a valid call trigger. If the call trigger is valid, then the signaling processor <b>112</b> determines what processing option is to be implemented in response to the call trigger. Processing options include implementing an interactive application in a service platform to process the user communications and selecting a connection to a third communication device <b>110</b> so that the user communications can be transported thereon.

0058For example, the user communications may be transported from a first communication device <b>106</b> over a connection <b>124</b>, through the interworking unit <b>114</b>, and to a second communication device <b>108</b> over a connection <b>126</b>. When a call trigger is detected by the interworking unit <b>114</b>, the interworking unit transmits an interworking unit control message containing the call trigger data associated with the coil trigger, such as a tone, to the signaling processor <b>112</b>. If the signaling processor <b>112</b> determines that the call trigger is valid, the signaling processor may transmit a processor control message to the interworking unit <b>114</b> instructing the interworking unit to route the user communications to the third communication device <b>110</b> over a selected connection <b>128</b>.

0059Referring again to <figref idref="DRAWINGS">FIG. 1</figref>, the processing of a call in the preferred call trigger system <b>104</b>, wherein, for example, the call is communicated between a TDM system and an ATM system, operates as follows. It will be appreciated that the following process description is exemplary, and many other types of interworking and call communications can occur.

0060A call is initiated from the first communication device <b>106</b>. The call signaling is transported from the first communication device <b>106</b> to the signaling processor <b>112</b>. The user communications are transported in a TDM format over a DSO from the first communication device <b>106</b> to the interworking unit <b>114</b>. The DSO may be contained within a DS3 or other high speed carrier and directed to the interworking unit <b>114</b> by a digital cross connect (not shown).

0061The signaling processor <b>112</b> processes the call signaling. The signaling processor <b>112</b> reads the call characteristics such as the routing label, including the origination point code (OPC), the destination point code (DPC), the circuit identification code (CIC), or the signaling link selection (SLS). Based on the processing of the call characteristics in the call signaling, the signaling processor <b>112</b> determines what action is to be taken. Presently, the signaling processor <b>112</b> determines which communication device <b>108</b> or <b>110</b> to which the call is to be transported and, when a service platform is the communication device <b>108</b> or <b>110</b>, which interactive application or other processing option the service platform can provide. In addition, the signaling processor <b>112</b> determines if the interworking unit <b>114</b> is to be configured to detect a call trigger and which subset of tones to process.

0062For example, based on the call signaling processing, the signaling processor <b>112</b> selects the connection <b>126</b> from the interworking unit <b>114</b> to the second communication device <b>108</b> for the user communications. The signaling processor <b>112</b> sends a processor control message to the interworking unit <b>114</b> designating the selected connection <b>126</b> and configuring the interworking unit to process a subset of tones as call triggers and to complete validation and screening. The signaling processor <b>112</b> also sends a processor control message to the selected second communication device <b>108</b> notifying the second communication device <b>108</b> that user communications will be transported to the second communication device over a selected connection <b>126</b>.

0063Referring still to <figref idref="DRAWINGS">FIG. 1</figref>, the interworking unit <b>114</b> receives both the user communications from the first communication device <b>106</b> and the processor control message from the signaling processor <b>112</b>. The interworking unit <b>114</b> converts the user communications from the TDM format to a format that is compatible with the second communication device <b>108</b>. Generally, the user communications are converted to ATM cells that identify the selected connection <b>126</b>. The ATM cells would identify the VPI/VCI of the selected connection <b>126</b> to the second communication device <b>108</b>.

0064The interworking unit <b>114</b> transports the ATM cells over the selected connection <b>126</b> to the second communication device <b>108</b>. Generally, a cross connect (not shown) is located between the interworking unit <b>114</b> and the second communication device <b>108</b>. The cross connect receives the ATM cells from the interworking unit <b>114</b> and directs the ATM cells to the second communication device <b>108</b>. The interworking from the first connection <b>124</b> to the selected connection <b>126</b>, including the reception of the TDM formatted user communications over the first connection <b>124</b>, the conversion of the user communications to ATM cells that identify the selected connection <b>126</b>, and the transport of the ATM cells over the selected connection <b>126</b>, occurs dynamically in real time.

0065It will be appreciated that the call can be initiated from the opposite direction such that the second communication device <b>108</b> initiates a call to the first communication device <b>106</b>. In such a case, a process opposite of the one described above is used. In that case, the interworking unit <b>114</b> receives the user communications from the second communication device <b>108</b> over the connection <b>126</b>. The interworking unit <b>114</b> also receives a processor control message from the signaling processor <b>112</b> designating a selected DSO connection <b>124</b> to the selected first communication device <b>106</b>. The interworking unit <b>114</b> then converts the ATM cells containing the user communications that are received from the connection <b>126</b> to user communications in the TDM format. The interworking unit <b>114</b> transports the converted user communications over the selected connection <b>124</b> to the first communication device <b>106</b>.

0066At this point, the call setup is complete and the first communication device <b>106</b> and the second communication device <b>108</b> are interacting over the connection through the interworking unit <b>114</b>. During the call, either the first communication device <b>106</b> or the second communication device <b>108</b> can initiate a call trigger.

0067The interworking unit <b>114</b> detects the call trigger in the user communications. Upon detecting the call trigger, the interworking unit <b>114</b> processes the call trigger data to determine if the call trigger is a valid call trigger. If the call trigger is not valid, no action is taken or an error signal is generated to the signaling processor <b>112</b>. If the call trigger is valid and within the subset of call trigger tones, the interworking unit <b>114</b> transmits an interworking unit control message to the signaling processor <b>112</b>. The interworking unit control message contains the data and information in the call trigger.

0068The signaling processor <b>112</b> further processes the call trigger data to determine what processing option to implement in response to the call trigger. Typically the processing options include connection selection for connection reassignment to forward a call to another communication device or implementation of an interactive application.

0069The signaling processor <b>112</b> may, for example, determine that the call is to be forwarded to the third communication device <b>110</b> in response to the call trigger. The signaling processor <b>112</b> then selects a connection <b>128</b> to the third communication device and transmits a processor control message to the interworking unit <b>114</b> requiring the interworking unit <b>114</b> to transport the user communications over the selected connection <b>128</b> to the third communication device <b>110</b>.

0070The interworking unit <b>110</b> then converts the user communications received from the first communication device <b>106</b> to ATM cells that identify the selected connection <b>128</b>. The ATM cells are transported to the third communication device <b>110</b> over the selected connection <b>126</b>.

0071Illustrated in <figref idref="DRAWINGS">FIG. 2</figref> is another embodiment of the call trigger system <b>104</b>A of the present invention. In this embodiment, the interworking unit <b>114</b>A has a tone detector <b>230</b>. Tone detectors are known in the art and can be inserted as a card in the interworking unit <b>114</b>A. Control messages, including data and information detected from a call trigger, would continue to be communicated to the signaling processor <b>112</b> through the link <b>118</b>. Processor control messages would continue to be communicated to the interworking unit <b>114</b>A from the signaling processor <b>112</b> through the link <b>118</b>.

0072In yet another embodiment, the call trigger system <b>104</b>B illustrated in <figref idref="DRAWINGS">FIG. 3</figref>, the interworking unit <b>114</b>B includes an external tone detector <b>332</b> attached to the backside of the interworking unit. In such a case, the interworking unit <b>114</b>B is connected to the tone detector <b>332</b> via a bus <b>334</b> or other appropriate connection. The tone detector <b>332</b> communicates control messages in a tone detector control message to the signaling processor <b>112</b> via the link <b>336</b> and receives control messages from the signaling processor <b>122</b> via the link <b>336</b>.

0073A telecommunication system <b>102</b> comprising a service platform <b>438</b> is illustrated in <figref idref="DRAWINGS">FIG. 4</figref>. The service platform <b>438</b> provides interactive applications having processing options for the user communications. For example, the service platform <b>438</b> may be configured to perform conference bridging. The service platform <b>438</b> communicates with the interworking unit <b>114</b> over a connection <b>440</b> and with the signaling processor over the link <b>442</b>. As stated above, when a call trigger is detected by the interworking unit <b>114</b>, the interworking unit transmits an interworking unit control message containing the call trigger data associated with the call trigger, such as a tone, to the signaling processor <b>112</b>.

0074If the signaling processor <b>112</b> determines that the call trigger is valid, the signaling processor may determine that a processing option in an interactive application residing on the service platform <b>438</b> is to be implemented to process the user communications. In such a case, the signaling processor <b>112</b> transmits a processor control message to the interworking unit <b>114</b> instructing the interworking unit to transport the user communications to the service platform <b>438</b> over the connection <b>440</b>. At the same time, the signaling processor <b>112</b> transmits a processor control message to the service platform <b>438</b> over the link <b>442</b> instructing the service platform to process the user communications using a selected interactive application or other selected processing option.

0075The service platform <b>438</b> receives the user communications over the selected connection <b>440</b> and processes the user communications using the selected interactive application or another selected processing option. The service platform <b>438</b> then reports the results of the user communications processing back to the signaling processor <b>112</b> in a service platform control message.

0076It will be appreciated that the call trigger system can handle calls from local communication devices as well as long distance communication devices. <figref idref="DRAWINGS">FIG. 5</figref> illustrates a first call trigger system <b>104</b>C and a second call trigger system <b>104</b>D. The first call trigger system <b>104</b>C handles calls from a local switch <b>502</b> that can originate or terminate at a local communication device <b>504</b>. Likewise, the second call trigger system <b>104</b>D handles calls from a local switch <b>506</b> that can originate or terminate at a local communication device <b>508</b>.

0077The user communications of the call are interworked by the interworking units <b>114</b>C and <b>114</b>D. A cross connect <b>510</b> directs ATM communications of ATM cells between the interworking units <b>114</b>C and <b>114</b>D of the two call trigger systems <b>104</b>C and <b>104</b>D. SS7 devices <b>512</b> and <b>514</b> direct call signaling to the respective signaling processors <b>112</b>C and <b>112</b>D of the call trigger systems <b>104</b>C and <b>104</b>D.

0078Thus, it will be appreciated that a call can originate or terminate from either local communication device <b>504</b> or <b>508</b>. In addition, either call trigger system <b>104</b>C or <b>104</b>D can detect a call trigger from the local communication devices <b>504</b> or <b>508</b> and process the call trigger.

0079<figref idref="DRAWINGS">FIG. 6</figref> procedurally illustrates the paths of the instruction transmissions for the call trigger processing and the control messages that are communicated between the various communication devices to process the user communications and the call trigger in the telecommunication system <b>102</b> of <figref idref="DRAWINGS">FIG. 1</figref>. The instruction sequences illustrate the method for detecting a call trigger in an ATM system on the DS0 side of the connection and processing the call trigger after a call setup has been completed.

0080With reference to <figref idref="DRAWINGS">FIG. 6</figref> and to <figref idref="DRAWINGS">FIG. 1</figref>, a call is connected between the first communication device <b>106</b> and the second communication device <b>108</b> such that interaction occurs between them. In this instance, the first communication device <b>106</b> initiates a call trigger. However, it will be appreciated that any element, including the second communication device <b>108</b> and the signaling processor <b>112</b>, can initiate a call trigger.

0081The interworking unit <b>114</b> detects the call trigger and transmits the call trigger data to the signaling processor <b>112</b> in an interworking unit control message over the link <b>116</b> (<figref idref="DRAWINGS">FIG. 1</figref>). The interworking unit <b>114</b> processes the call trigger data and, upon determining call trigger validity, determines the call is to be rerouted to the third communication device <b>110</b> over a selected connection <b>128</b> (<figref idref="DRAWINGS">FIG. 1</figref>).

0082The signaling processor <b>112</b> transmits a release connection message to the second communication device <b>108</b> instructing the second communication device that the call is to be released. The signaling processor <b>112</b> also transmits a control message to the third communication device <b>110</b> instructing the third communication device to initiate a connection to the interworking unit <b>114</b>. This will require the third communication device <b>110</b> to follow call setup procedures.

0083In addition, the signaling processor <b>112</b> transmits a processor control message to the interworking unit <b>114</b> reassigning the connection to the selected connection <b>128</b> to the third communication device <b>110</b>. The processor control message contains the DS0 port to VPI/VCI port interworking information required by the interworking unit <b>114</b> to interwork the user communications to the designated port.

0084The interworking unit <b>114</b> releases the connection to the second communication device <b>108</b>. The interworking unit <b>114</b> then converts the user communications to ATM cells that identify the selected VPI/VCI connection to the third communication device <b>110</b>. The interworking unit <b>114</b> transports the ATM cells containing the user communications over the selected connection <b>128</b> to the third communication device <b>110</b>. The call then is connected between the first communication device <b>106</b> and the third communication device <b>110</b> so that interaction occurs between them. Upon completion of user communications processing, or at the end of the call, either the first communication device <b>106</b> or the third communication device <b>110</b> can initiate a disconnect of the call.

0085<figref idref="DRAWINGS">FIG. 7</figref> illustrates a sequence chart for the call trigger processing and the control messages that take place between the various communication devices to process the user communications and the call trigger in the telecommunication system <b>102</b> of <figref idref="DRAWINGS">FIG. 1</figref>. The message sequences illustrate the method for detecting a call trigger in an ATM system on the DS0 side of the connection and processing the call trigger after a call setup has been completed.

0086With reference to <figref idref="DRAWINGS">FIG. 7</figref> and to <figref idref="DRAWINGS">FIG. 1</figref>, a call is connected between the first communication device <b>106</b> and the second communication device <b>108</b> such that interaction occurs between them. A call trigger in the form of a DTMF tone is initiated from the first communication device <b>106</b>. The interworking unit <b>114</b> detects the DTMF tone and transmits a notify signal with the call trigger data to the signaling processor <b>112</b>. After processing the call trigger data, the signaling processor <b>112</b> selects a connection. The signaling processor <b>112</b> sends a release message (REL) to the second communication device <b>108</b> to release the connection between the first communication device <b>106</b> and the second communication device. Upon receiving the REL message, the second communication device <b>108</b> sends a release complete (RLC) back to the signaling processor <b>112</b>. At that point, the connection is released between the interworking unit <b>114</b> and the second communication device <b>108</b>, but remains connected between the first communication device <b>106</b> and the interworking unit.

0087The signaling processor <b>112</b> sends an initial address message (IAM) to the third communication device <b>110</b>. The signaling processor <b>112</b> generates a control message to the interworking unit <b>114</b> identifying the DS0 and the selected VPI/VCI to the third communication device <b>110</b>. An address complete message (ACM) is sent from the third communication device <b>110</b> to the signaling processor <b>112</b>. A connection then is complete between the first communication device <b>106</b> and the third communication device <b>110</b>. If the third communication device <b>110</b> answers the call on the connection, the signaling processor <b>112</b> will receive an answer message (ANM) from the third communication device. At that point, interaction occurs between the first communication device <b>106</b> and the third communication device <b>110</b>. Upon completion of the user communications processing, or at completion of the call, either of the communication devices <b>106</b> or <b>110</b>, or in some instances the signaling processor <b>112</b>, can initiate a disconnect.

0000The Interworking Unit Embodiments of <figref idref="DRAWINGS">FIGS. 8-9</figref>

0088<figref idref="DRAWINGS">FIG. 8</figref> shows one embodiment of an ATM interworking multiplexer (mux) <b>802</b> that is suitable for the present invention, but other multiplexers that support the requirements of the invention are also applicable. The ATM interworking mux <b>802</b> has a control interface <b>804</b>, an OC-N/STS-N interface <b>806</b>, a DS3 interface <b>808</b>, a DS1 interface <b>810</b>, a DS0 interface <b>812</b>, a signal processor <b>814</b>, an ATM adaptation layer (AAL) <b>816</b>, and an OC-M/STS-interface <b>818</b>.

0089The control interface <b>802</b> accepts control messages from the signaling processor <b>820</b>. In particular, the control interface <b>804</b> identifies DS0 connections and virtual connection assignments in the control messages from the signaling processor <b>820</b>. These assignments are provided to the AAL <b>816</b> for implementation.

0090The OC-N/STS-N interface <b>806</b>, the DS3 interface <b>808</b>, the DS1 interface <b>810</b>, and the DS0 interface <b>812</b> each can accept calls, including user communications, from a first communication device <b>822</b>. Likewise, the OC-M/STS-M interface SIS can accept calls, including user communications, from a second communication device <b>824</b>.

0091The OC-N/STS-N interface <b>806</b> accepts OC-N formatted communication signals, such as calls, and STS-N formatted communication signals and converts the communication signals from the OC-N or STS-N formats to the DS3 format. The DS3 interface <b>808</b> accepts communication signals in the DS3 format and converts the communication signals to the DS1 format. The DS3 interface <b>808</b> can accept DS3s from the OC-N/STS-N interface <b>806</b> or from an external connection. The DS1 interface <b>810</b> accepts the communication signals in the DS 1 format and converts the communication signals to the DS0 format. The DSI interface <b>810</b> can accept DS1s from the DS3 interface <b>808</b> or from an external connection. The DS0 interface <b>812</b> accepts communication signals in the DS0 format and provides an interface to the AAL <b>816</b>. In addition, each interface may transmit signals in like manner to the communication device <b>822</b>.

0092The OC-M/STS-M interface <b>818</b> is operational to accept ATM cells from the AAL <b>816</b> and to transmit the ATM cells over the connection to the communication device <b>824</b>. The OC-M/STS-M interface <b>818</b> may also accept ATM cells in the OC or STS format and transmit them to the AAL <b>816</b>.

0093The AAL <b>816</b> comprises both a convergence sublayer and a segmentation and reassembly (SAR) sublayer. The AAL <b>816</b> is operational to accept communication device information in the DS0 format from the DS0 interface <b>812</b> and to convert the communication device information into ATM cells. AALs are known in the art and information about AALs is provided by International Telecommunications Union (ITU) document 1.363, which is hereby incorporated fully herein by reference. An AAL for voice communication signals is described in U.S. patent application Ser. No. 08/395,745, which was filed on Feb. 28, 1995, and entitled “Cell Processing for Voice Transmission,” and which is incorporated herein by reference.

0094The AAL <b>816</b> obtains from the control interface <b>804</b> the virtual path identifier (VPI) and the virtual channel identifier (VCI) for each DS0 for each call connection. The AAL <b>816</b> also obtains the identity of the DS0 for each call (or the DS0s for an Nx64 call). The AAL <b>816</b> then transfers the communication device information between the identified DS0 and the identified ATM virtual connection. An acknowledgment that the assignments have been implemented may be sent back to the signaling processor <b>820</b> if desired. Calls with multiple 64 Kilo-bits per second (Kbps) DSOs are known as Nx64 calls. If desired, the AAL <b>816</b> can be configured to accept control messages through the control interface <b>804</b> for Nx64 calls.

0095As discussed above, the ATM interworking mux <b>802</b> also handles calls in the opposite direction, that is, in the direction from the OC-M/STS-M interface <b>818</b> to the DS0 interface <b>812</b>, including calls exiting from the DS1 interface <b>810</b>, the DS3 interface <b>808</b>, and the OC-N/STS-N interface <b>806</b>. For this traffic, the VPI/VCI has been selected already and the traffic has been routed through the cross-connect (not shown). As a result, the AAL <b>816</b> only needs to identify the pre-assigned DSO for the selected VPI/VCI. This can be accomplished through a look-up table. In alternative embodiments, the signaling processor <b>820</b> can provide this DSO-VPI/VCI assignment through the control interface <b>804</b> to the AAL <b>816</b>.

0096A technique for processing VPI/VCIs is disclosed in U.S. patent application Ser. No. 08/653,852, which was filed on May 28, 1996, and entitled “Teleconmunications System with a Connection Processing System,” and which is incorporated herein by reference.

0097DS0 connections are bidirectional and ATM connections are typically uni-directional. As a result, two virtual connections in opposing directions will typically be required for each DS0. Those skilled in the art will appreciate how this can be accomplished in the context of the invention. For example, the cross-connect can be provisioned with a second set of VPI/VCIs in the opposite direction as the original set of VPI/VCIs. For each call, ATM interworking multiplexers would be configured to invoke automatically this second VPI/VCI to provide a bi-directional virtual connection to match the bi-directional DS0 on the call.

0098In some embodiments, it may be desirable to incorporate digital signal processing capabilities at the DS0 level. For example, in the present invention, digital signal processing is used to detect the call trigger. It may also be desired to apply echo cancellation or encryption to selected DS0 circuits. In these embodiments, a signal processor <b>814</b> would be included either separately (as shown) or as a part of the DS0 interface <b>812</b>. The signaling processor <b>820</b> would be configured to send control messages to the ATM interworking mux <b>802</b> to implement particular features on particular DS0 circuits.

0099<figref idref="DRAWINGS">FIG. 9</figref> shows another embodiment of an ATM interworking multiplexer (mux) <b>902</b> that is suitable for the present invention. The ATM interworking mux <b>902</b> has a control interface <b>904</b>, an STM-N electrical/optical (E/O) interface <b>906</b>, an E3 interface <b>908</b>, an E1 interface <b>910</b>, an E0 interface <b>912</b>, a signal processor <b>914</b>, an ATM adaptation layer (AAL) <b>916</b>, and an STM-M electrical/optical (E/O) interface <b>918</b>.

0100The control interface <b>904</b> accepts control messages from the signaling processor <b>920</b>. In particular, the control interface <b>904</b> identifies E0 connections and virtual connection assignments in the control messages from the signaling processor <b>920</b>. These assignments are provided to the AAL <b>916</b> for implementation.

0101The STM-N E/O interface <b>906</b>, the E3 interface <b>908</b>, the E1 interface <b>910</b>, and the E0 interface <b>912</b> each can accept calls, including user communications, from a first communication device <b>922</b>. Likewise, the STM-M E/O interface <b>918</b> can accept calls, including user communications, from a second communication device <b>924</b>.

0102The STM-N E/O interface <b>906</b> accepts STM-N electrical or optical formatted communication signals, such as calls, and converts the communication signals from the STM-N electrical or STM-N optical format to the E3 format. The E3 interface <b>908</b> accepts communication signals in the E3 format and converts the communication signals to the E1 format. The E3 interface <b>908</b> can accept E3s from the STM-N E/O interface <b>906</b> or from an external connection. The E1 interface <b>910</b> accepts the communication signals in the E1 format and converts the communication signals to the E0 format. The E1 interface <b>910</b> can accept E1s from the STM-N E/O interface <b>906</b> or the E3 interface <b>908</b> or from an external connection. The E0 interface <b>912</b> accepts communication signals in the E0 format and provides an interface to the AAL <b>916</b>. In addition, each interface may transmit signals in a like manner to the communication device <b>922</b>.

0103The STM-M E/O interface <b>918</b> is operational to accept ATM cells from the AAL <b>916</b> and to transmit the ATM cells over the connection to the communication device <b>924</b>. The STM-M E/O interface <b>918</b> may also accept ATM cells in the STM-M E/O format and transmit them to the AAL <b>916</b>.

0104The AAL <b>916</b> comprises both a convergence sublayer and a segmentation and reassembly (SAR) sublayer. The AAL <b>916</b> is operational to accept communication device information in the E0 format from the E0 interface <b>912</b> and to convert the communication device information into ATM cells.

0105The AAL <b>916</b> obtains from the control interface <b>904</b> the virtual path identifier and the virtual channel identifier for each call connection. The AAL <b>916</b> also obtains the identity of each call. The AAL <b>916</b> then transfers the communication device information between the identified E0 and the identified ATM virtual connection. An acknowledgment that the assignments have been implemented may be sent back to the signaling processor <b>920</b> if desired. If desired, the AAL <b>916</b> can be configured to accept control messages through the control interface <b>904</b> for Nx64 calls.

0106As discussed above, the ATM interworking mux <b>902</b> also handles calls in the opposite direction that is, in the direction from the STM-M E/O interface <b>918</b> to the E0 interface <b>912</b>, including calls exiting from the E1 interface <b>910</b>, the E3 interface <b>908</b>, and the STM-N E/O interface <b>906</b>. For this traffic, the VPI/VCI has been selected already and the traffic has been routed through the cross-connect (not shown). As a result, the AAL <b>916</b> only needs to identify the pro-assigned E0 for the selected VPI/VCI. This can be accomplished through a look-up table. In alternative embodiments, the signaling processor <b>920</b> can provide this VPI/VCI assignment through the control interface <b>904</b> to the AAL <b>916</b>.

0107E0 connections are bidirectional and ATM connections typically are unidirectional. As a result, two virtual connections in opposing directions typically will be required for each E0. Those skilled in the art will appreciate how this can be accomplished in the context of the invention. For example, the cross-connect can be provisioned with a second set of VPI/VCIs in the opposite direction as the original set of VPI/VCIs. For each call, ATM interworking multiplexers would be configured to automatically invoke this second VPI/VCI to provide a bi-directional virtual connection to match the bidirectional E0 on the call.

0108In some instances, it may be desirable to incorporate digital signal processing capabilities at the E0 level. For example, in the present invention, digital signal processing is used to detect the call trigger. Also, it may be desirable apply echo cancellation. In these embodiments, a signal processor <b>914</b> would be included either separately (as shown) or as a part of the E0 interface <b>912</b>. The signaling processor <b>920</b> would be configured to send control messages to the ATM interworking mux <b>902</b> to implement particular features on particular circuits.

0000The Signaling Processor of <figref idref="DRAWINGS">FIGS. 10-20</figref>

0109The signaling processor is referred to as a call/connection manager (CCM), and it receives and processes telecommunications call signaling and control messages to select connections that establish communication paths for calls.

0110In the preferred embodiment, the CCM processes SS7 signaling to select connections for a call. CCM processing is described in a U.S. Patent Application having attorney docket number 1148, which is entitled “Telecommunication System,” which is assigned to the same assignee as this patent application, and which is incorporated herein by reference.

0111In addition to selecting connections, the CCM performs many other functions in the context of call processing. It not only can control routing and select the actual connections, but it can also validate callers, control echo cancelers, generate billing information, invoke intelligent network functions, access remote databases, manage traffic, and balance network loads. One skilled in the art will appreciate how the CCM described below can be adapted to operate in the above embodiments.

0112<figref idref="DRAWINGS">FIG. 10</figref> depicts a version of the CCM. Other versions are also contemplated. In the embodiment of <figref idref="DRAWINGS">FIG. 10</figref>, the CCM <b>1002</b> controls an ATM interworking multiplexer (mux) that performs interworking of DSOs and VPI/VCIs. However, the CCM may control other communications devices and connections in other embodiments.

0113The CCM <b>1002</b> comprises a signaling platform <b>1004</b>, a control platform <b>1006</b>, and an application platform <b>1008</b>. Each of the platforms <b>1004</b>, <b>1006</b>, and <b>1008</b> is coupled to the other platforms.

0114The signaling platform <b>1004</b> is externally coupled to the SS7 systems—in particular to systems having a message transfer part (MTP), an ISDN user part (ISUP), a signaling connection control part (SCCP), an intelligent network application part (INAP), and a transaction capabilities application part (TCAP). The control platform <b>1006</b> is externally coupled to a mux control, an echo control, a resource control, billing, and operations.

0115The signaling platform <b>1004</b> comprises MTP levels 1-3, ISUP, TCAP, SCCP, and INAP functionality and is operational to transmit and receive the SS7 messages. The ISUP, SCCP, INAP, and TCAP functionality use MTP to transmit and receive the SS7 messages. Together, this functionality is referred as an “SS7 stack,” and it is well known. The software required by one skilled in the art to configure an SS7 stack is commercially available, for example, from the Trillium company.

0116The control platform <b>1006</b> is comprised of various external interfaces including a mux interface, an echo interface, a resource control interface, a billing interface, and an operations interface. The mux interface exchanges messages with at least one mux. These messages comprise DS0 to VPI/VCI assignments, acknowledgments, and status information. The echo control interface exchanges messages with echo control systems. Messages exchanged with echo control systems might include instructions to enable or disable echo cancellation on particular DS0s, acknowledgments, and status information.

0117The resource control interface exchanges messages with external resources. Examples of such resources are devices that implement continuity testing, encryption, compression, tone detection/transmission, voice detection, and voice messaging. The messages exchanged with resources are instructions to apply the resource to particular DS0s, acknowledgments, and status information. For example, a message may instruct a continuity testing resource to provide a loopback or to send and detect a tone for a continuity test.

0118The billing interface transfers pertinent billing information to a billing system. Typical billing information includes the parties to the call, time points for the call, and any special features applied to the call. The operations interface allows for the configuration and control of the CCM <b>1002</b>. One skilled in the art will appreciate how to produce the software for the interfaces in the control platform <b>1006</b>.

0119The application platform <b>1008</b> is functional to process signaling information from the signaling platform <b>1004</b> in order to select connections. The identity of the selected connections are provided to the control platform <b>1006</b> for the mux interface. The application platform <b>1008</b> is responsible for validation, translation, routing, call control, exceptions, screening, and error handling. In addition to providing the control requirements for the mux, the application platform <b>1008</b> also provides requirements for echo control and resource control to the appropriate interface of the control platform <b>1006</b>. In addition, the application platform <b>1008</b> generates signaling information for transmission by the signaling platform <b>1004</b>. The signaling information might be ISUP, INAP, or TCAP messages to external network elements. Pertinent information for each call is stored in a call control block (CCB) for the call. The CCB can be used for tracking and billing the call.

0120The application platform <b>1008</b> operates in general accord with the Basic Call Model (BCM) defined by the ITU. An instance of the BCM is created to handle each call. The BCM includes an originating process and a terminating process. The application platform <b>1008</b> includes a service switching function (SSF) that is used to invoke the service control function (SCF). Typically, the SCF is contained in a service control point (SCP). The SCF is queried with TCAP or INAP messages. The originating or terminating processes will access remote databases with intelligent network (IN) functionality via the SSF function.

0121Software requirements for the application platform <b>1008</b> can be produced in specification and description language (SDL) defined in ITU-T Z. 100. The SDL can be converted into C code. Additional C and C++ code can be added as required to establish the environment.

0122The CCM <b>1002</b> can be comprised of the above-described software loaded onto a computer. The computer can be an Integrated Micro Products (IMP) FT-Sparc 600 using the Solaris operating system and conventional database systems. It may be desirable to utilize the multi-threading capability of a Unix operating system.

0123From <figref idref="DRAWINGS">FIG. 10</figref>, it can be seen that the application platform <b>1008</b> processes signaling information to control numerous systems and facilitate call connections and services. The SS7 signaling is exchanged with external components through the signaling platform <b>1004</b>, and control information is exchanged with external systems through the control platform <b>1006</b>. Advantageously, the CCM <b>1002</b> is not integrated into a switch CPU that is coupled to a switching matrix. Unlike an SCP, the CCM <b>1002</b> is capable of processing ISUP messages independently of TCAP queries.

0000SS7 Message Designations

0124SS7 messages are well known. Designations for various SS7 messages commonly are used. Those skilled in the art are familiar with the following message designations:

0125ACM—Address Complete Message

0126ANM—Answer Message

0127BLO—Blocking

0128BLA—Blocking Acknowledgement

0129CPG—Call Progress

0130CRG—Charge Information

0131CGB—Circuit Group Blocking

0132CGBA—Circuit Group Blocking Acknowledgement

0133GRS—Circuit Group Reset

0134GRA—Circuit Group Reset Acknowledgment

0135CGU—Circuit Group Unblocking

0136CGUA—Circuit Group Unblocking Acknowledgment

0137CQM—Circuit Group Query

0138CQR—Circuit Group Query Response

0139CRM—Circuit Reservation Message

0140CRA—Circuit Reservation Acknowledgment

0141CVT—Circuit Validation Test

0142CVR—Circuit Validation Response

0143CFN—Confusion

0144COT—Continuity

0145CCR—Continuity Check Request

0146EXM—Exit Message

0147INF—Information

0148INR—Information Request

0149IAM—Initial Address

0150LPA—Loop Back Acknowledgment

0151PAM—Pass Along

0152REL—Release

0153RLC—Release Complete

0154RSC—Reset Circuit

0155RES—Resume

0156SUS—Suspend

0157UBL—Unblocking

0158UBA—Unblocking Acknowledgement

0159UCIC—Unequipped Circuit Identification Code

0000CCM Tables

0160Call processing typically entails two aspects. First, an incoming or “originating” connection is recognized by an originating call process. For example, the initial connection that a call uses to enter a network is the originating connection in that network. Second, an outgoing or “terminating” connection is selected by a terminating call process. For example, the terminating connection is coupled to the originating connection in order to extend the call through the network. These two aspects of call processing are referenced to as the originating side of the call and the terminating side of the call.

0161<figref idref="DRAWINGS">FIG. 11</figref> depicts a data structure used by the application platform <b>1008</b> to execute the BCM. This is accomplished through a series of tables that point to one another in various ways. The pointers are typically comprised of next function and next index designations. The next function points to the next table, and the next index points to an entry or a range of entries in that table. The data structure has a trunk circuit table <b>1102</b>, a trunk group table <b>1104</b>, an exception table <b>1106</b>, an ANI table <b>1108</b>, a called number table <b>1110</b>, and a routing table <b>112</b>.

0162The trunk circuit table <b>1102</b> contains information related to the connections. Typically, the connections are DS0 or ATM connections. Initially, the trunk circuit table <b>1102</b> is used to retrieve information about the originating connection. Later, the table is used to retrieve information about the terminating connection. When the originating connection is being processed, the trunk group number in the trunk circuit table <b>1102</b> points to the applicable trunk group for the originating connection in the trunk group table <b>1104</b>.

0163The trunk group table <b>1104</b> contains information related to the originating and terminating trunk groups. When the originating connection is being processed, the trunk group table <b>1104</b> provides information relevant to the trunk group for the originating connection and typically points to the exception table <b>1106</b>.

0164The exception table <b>1106</b> is used to identify various exception conditions related to the call that may influence the routing or other handling of the call. Typically, the exception table <b>1106</b> points to the ANI table <b>1108</b>. Although, the exception table <b>1106</b> may point directly to the trunk group table <b>1104</b>, the called number table <b>1110</b>, or the routing table <b>1112</b>.

0165The ANI table <b>1108</b> is used to identify any special characteristics related to the caller's number. The caller's number is commonly known as automatic number identification (ANI). The ANI table <b>1108</b> typically points to the called number table <b>1110</b>. Although, the ANI table <b>1108</b> may point directly to the trunk group table <b>1104</b> or the routing table <b>1112</b>.

0166The called number table <b>1110</b> is used to identify routing requirements based on the called number. This will be the case for standard telephone calls. The called number table <b>1110</b> typically points to the routing table <b>1112</b>. Although, it may point to the trunk group table <b>1104</b>.

0167The routing table <b>1112</b> has information relating to the routing of the call for the various connections. The routing table <b>1112</b> is entered from a pointer in either the exception table <b>1106</b>, the ANI table <b>1108</b>, or the called number table <b>1110</b>. The routing table <b>1112</b> typically points to a trunk group in the trunk group table <b>1104</b>.

0168When the exception table <b>1106</b>, the ANI table <b>1108</b>, the called number table <b>1110</b>, or the routing table <b>1112</b> point to the trunk group table <b>1104</b>, they effectively select the terminating trunk group. When the terminating connection is being processed, the trunk group number in the trunk group table <b>1104</b> points to the trunk group that contains the applicable terminating connection in the trunk circuit table <b>1104</b>.

0169The terminating trunk circuit is used to extend the call. The trunk circuit is typically a VPI/VCI or a DS0. Thus it can be seen that by migrating through the tables, a terminating connection can be selected for a call.

0170<figref idref="DRAWINGS">FIG. 12</figref> is an overlay of <figref idref="DRAWINGS">FIG. 11</figref>. The tables from <figref idref="DRAWINGS">FIG. 11</figref> are present, but for clarity, their pointers have been omitted. <figref idref="DRAWINGS">FIG. 12</figref> illustrates additional tables that can be accessed from the tables of <figref idref="DRAWINGS">FIG. 11</figref>. These include a CCM ID table <b>1202</b>, a treatment table <b>1204</b>, a query/response table <b>1206</b>, and a message table <b>1208</b>.

0171The CCM ID table <b>1202</b> contains various CCM SS7 point codes. It can be accessed from the trunk group table <b>1104</b>, and it points back to the trunk group table <b>1104</b>.

0172The treatment table <b>1204</b> identifies various special actions to be taken in the course of call processing. This will typically result in the transmission of a release message (REL) and a cause value. The treatment table <b>1204</b> can be accessed from the trunk circuit table <b>1102</b>, the trunk group table <b>1104</b>, the exception table <b>1106</b>, the ANI table <b>1108</b>, the called number table <b>1110</b>, the routing table <b>1112</b>, and the query/response table <b>1206</b>.

0173The query/response table <b>1206</b> has information used to invoke the SCF. It can be accessed by the trunk group table <b>1104</b>, the exception table <b>1106</b>, the ANI table <b>1108</b>, the called number table <b>1110</b>, and the routing table <b>1112</b>. It points to the trunk group table <b>1104</b>, the exception table <b>1106</b>, the ANI table <b>1108</b>, the called number table <b>1110</b>, the routing table <b>1112</b>, and the treatment table <b>1204</b>.

0174The message table <b>1208</b> is used to provide instructions for messages from the termination side of the call. It can be accessed by the trunk group table <b>1104</b> and points to the trunk group table <b>1104</b>.

0175<figref idref="DRAWINGS">FIGS. 13-20</figref> depict examples of the various tables described above. <figref idref="DRAWINGS">FIG. 13</figref> depicts an example of the trunk circuit table. Initially, the trunk circuit table is used to access information about the originating circuit. Later in the processing, it is used to provide information about the terminating circuit. For originating circuit processing, the associated point code is used to enter the table. This is the point code of the switch or CCM associated with the originating circuit. For terminating circuit processing, the trunk group number is used to enter the table.

0176The table also contains the circuit identification code (CIC). The CIC identifies the circuit which is typically a DS0 or a VPI/VCI. Thus, the invention is capable of mapping the SS7 CICs to the ATM VPI/VCI. If the circuit is ATM, the virtual path (VP) and the virtual channel (VC) also can be used for identification. The group member number is a numeric code that is used for terminating circuit selection. The hardware identifier identifies the location of the hardware associated with the originating circuit. The echo canceler (EC) identification (ID) entry identifies the echo canceler for the originating circuit.

0177The remaining fields are dynamic in that they are filled during call processing. The echo control entry is filled based on three fields in signaling messages: the echo suppresser indicator in the IAM or CRM, the echo control device indicator in the ACM or CPM, and the information transfer capability in the IAM. This information is used to determine if echo control is required on the call. The satellite indicator is filled with the satellite indicator in the IAM or CRM. It may be used to reject a call if too many satellites are used. The circuit status indicates if the given circuit is idle, blocked, or not blocked. The circuit state indicates the current state of the circuit, for example, active or transient. The time/date indicates when the idle circuit went idle.

0178<figref idref="DRAWINGS">FIG. 14</figref> depicts an example of the trunk group table. During origination processing, the trunk group number from the trunk circuit table is used to key into the trunk table. Glare resolution indicates how a glare situation is to be resolved. Glare is dual seizure of the same circuit. If the glare resolution entry is set to “even/odd,” the network element with the higher point code controls the even circuits, and the network element with the lower point code controls the odd circuits. If the glare resolution entry is set to “all,” the CCM controls all of the circuits. If the glare resolution entry is set to, “none,” the CCM yields. The continuity control entry lists the percent of calls requiring continuity tests on the trunk group.

0179The common language location identifier (CLLI) entry is a Bellcore standardized entry. The satellite trunk group entry indicates that the trunk group uses a satellite. The satellite trunk group entry is used in conjunction with the satellite indicator field described above to determine if the call has used too many satellite connections and, therefore, must be rejected. The service indicator indicates if the incoming message is from a CCM (ATM) or a switch (TDM). The outgoing message index (OMI) points to the message table so that outgoing messages can obtain parameters. The associated number plan area (NPA) entry identifies the area code.

0180Selection sequence indicates the methodology that will be used to select a connection. The selection sequence field designations tell the trunk group to select circuits based on the following: least idle, most idle, ascending, descending, clockwise, and counterclockwise. The hop counter is decremented from the IAM. If the hop counter is zero, the call is released. Automatic congestion control (ACC) active indicates whether or not congestion control is active. If automatic congestion control is active, the CCM may release the call. During termination processing, the next function and index are used to enter the trunk circuit table.

0181<figref idref="DRAWINGS">FIG. 15</figref> depicts an example of the exception table. The index is used as a pointer to enter the table. The carrier selection identification (ID) parameter indicates how the caller reached the network and is used for routing certain types of calls. The following are used for this field: spare or no indication, selected carrier identification code presubscribed and input by the calling party, selected carrier identification code presubscribed and not input by the calling party, selected carrier identification code presubscribed and no indication of input by the calling party, and selected carrier identification code not presubscribed and input by the calling party. The carrier identification (ID) indicates the network that the caller wants to use. This is used to route calls directly to the desired network. The called party number nature of address differentiates between 0+ calls, 1+ calls, test calls, and international calls. For example, international calls might be routed to a pre-selected international carrier.

0182The called party “digits from” and “digits to” focus further processing unique to a defined range of called numbers. The “digits from” field is a decimal number ranging from 0.1-15 digits. It can be any length and, if filled with less than 15 digits, is filled with 0s for the remaining digits. The “digits to” field is a decimal number ranging from 1-15 digits. It can be any length and, if filled with less than 15 digits, is filled with 9s for the remaining digits. The next function and next index entries point to the next table which is typically the ANI table.

0183<figref idref="DRAWINGS">FIG. 16</figref> depicts an example of the ANI table. The index is used to enter the fields of the table. The calling party category differentiates among types of calling parties, for example, test calls, emergency calls, and ordinary calls. The calling party\charge number entry nature of address indicates how the ANI is to be obtained. The following is the table fill that is used in this field: unknown, unique subscriber numbers, ANI not available or not provided, unique national number, ANI of the called party included, ANI of the called party not included, ANI of the called party includes national number, non-unique subscriber number, non-unique national number, non-unique international number, test line test code, and all other parameter values.

0184The “digits from” and “digits to” focus further processing unique to ANI within a given range. The data entry indicates if the ANI represents a data device that does not need echo control. Originating line information (OLI) differentiates among ordinary subscriber, multiparty line, ANI failure, station level rating, special operator handling, automatic identified outward dialing, coin or non-coin call using database access, 800\888 service call, coin, prison/inmate service, intercept (blank, trouble, and regular), operator handled call, outward wide area telecommunications service, telecommunications relay service (TRS), cellular services, private paystation, and access for private virtual network types of service. The next function and next index point to the next table which is typically the called number table.

0185<figref idref="DRAWINGS">FIG. 17</figref> depicts an example of the called number table. The index is used to enter the fields of the table. The called number nature of address entry indicates the type of dialed number, for example, national versus international. The “digits from” and “digits to” entries focus further processing unique to a range of called numbers. The processing follows the processing logic of the “digits from” and “digits to” fields in <figref idref="DRAWINGS">FIG. 15</figref>. The next function and next index point to the next table which is typically the routing table.

0186<figref idref="DRAWINGS">FIG. 18</figref> depicts an example of the routing table. The index is used to enter the table. The transit network selection (TNS) network identification (ID) plan indicates the number of digits to use for the CIC. The transit network selection “digits from” and “digits to” fields define the range of numbers to identify an international carrier. The circuit code indicates the need for an operator on the call. The next function and next index entries in the routing table are used to identify a trunk group. The second and third next function/index entries define alternate routes. The third next function entry can also point back to another set of next functions in the routing table in order to expand the number of alternate route choices. The only other entries allowed are pointers to the treatment table. If the routing table points to the trunk group table, then the trunk group table typically points to a trunk circuit in the trunk circuit table. The yield from the trunk circuit table is the terminating connection for the call.

0187It can be seen from <figref idref="DRAWINGS">FIGS. 13-18</figref> that the tables can be configured and relate to one another in such a way that call processes can enter the trunk circuit table for the originating connection and can traverse through the tables by keying on information and using pointers. The yield of the tables is typically a terminating connection identified by the trunk circuit table. In some cases, treatment is specified by the treatment table instead of a connection. If, at any point during the processing, a trunk group can be selected, processing may proceed directly to the trunk group table for terminating circuit selection. For example, it may be desirable to route calls from a particular ANI over a particular set of trunk groups. In this case, the ANI table would point directly to the trunk group table, and the trunk group table would point to the trunk circuit table for a terminating circuit. The default path through the tables is: trunk circuit, trunk group, exception, ANI, called number, routing, trunk group, and trunk circuit.

0188<figref idref="DRAWINGS">FIG. 19</figref> depicts an example of the treatment table. Either the index or the message received cause number are filled and are used to enter the table. If the index is filled and used to enter the table, the general location, coding standard, and cause value indicator are used to generate an SS7 REL. The message received cause value entry is the cause value in a received SS7 message. If the message received cause value is filled and used to enter the table, then tile cause value from that message is used in a REL from the CCM. The next function and next index point to the next table.

0189<figref idref="DRAWINGS">FIG. 20</figref> depicts an example of the message table. This table allows the CCM to alter information in outgoing messages. Message type is used to enter the table, and it represents the outgoing standard SS7 message type. The parameter is the pertinent parameter within the outgoing SS7 message. The indexes point to various entries in the trunk group table and determine if parameters can be unchanged, omitted, or modified in the outgoing messages.

0190It shall be recognized that the system of the present invention provides the capability to use an interworking unit as a monitoring interworking unit to monitor a call for a call trigger during the entire duration of a call. When used in conjunction with a signaling processor, the system of the present invention can implement routing procedures or interactive applications at a service platform at any time during the call without requiring the service platform to remain connected to the call. The system more efficiently uses available connections and ports in the telecommunication network, especially those ports and connections to the service platforms.

0191Moreover, it will be appreciated that the combination of the signaling processor, the interworking unit, and a service platform can be used to emulate telecommunication switch services, such as services provided by remote switches and class five switches. This also reduces the number of switching ports and associated connection required in a telecommunication network.

0192Those skilled in the art will appreciate that variations from the specific embodiments disclosed above are contemplated by the invention. The invention should not be restricted to the above embodiments, but should be measured by the following claims.