US8224928B2 - Methods and systems for distributing operating status information within a converged network - Google Patents

Abstract

Disclosed is a communications network element that is capable of routing signaling messages and also performing inter-network management functions in a converged telephony-data network environment. A signaling gateway routing node is adapted to facilitate signaling communication between nodes in a signaling system 7 network and nodes in an Internet protocol (IP) type network. In addition to basic message routing functionality, the signaling gateway routing node is adapted to notify nodes in the IP network when a node in the SS7 network becomes congested or unavailable. In certain cases, the signaling gateway selectively notifies only IP nodes that are concerned with the status of the troubled SS7 node, while in other cases, notification messages are broadcast to all relevant IP nodes. The signaling gateway also serves to filter redundant congestion status queries or polling type messages that are conveyed from IP nodes through to the distressed SS7 node.

Description

RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No. 09/770,316, filed Jan. 26, 2001 now U.S. Pat. No. 7,318,091, which claims the benefit of U.S. Provisional Patent Application No. 60/208,523 filed Jun. 1, 2000, the disclosure of each of which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

The present invention relates to the distribution of network management information in a non-homogeneous communications network environment, and more particularly to methods and systems for generating and routing network management type signaling messages in a network environment that employs both a signaling system 7 (SS7) message transfer part (MTP) based network component and an Internet protocol (IP) based network component.

BACKGROUND

In modern telephony networks, service control points (SCPs) serve as an interface to telephony related databases, such as: call management service databases (CMSDB); line information databases (LIDB); and business services databases (BSDB). These databases are used, at least in part, to facilitate a variety of intelligent network (IN) type services including: find me service, follow me service, computer security service, call pickup service, store locator service, call waiting service, call block service, calling name delivery service, three way calling service, 800 number services, etc. Such telephony service databases may also be employed to provide communication service subscribers the flexibility to easily port their service from one communication service provider to another (i.e., number portability or local number portability).

It will be appreciated that the application of such SCP-type database services is not limited to the traditional wired public switched telephone network (PSTN), but is also widely implemented in the wireless telecommunications industry. Typical wireless network communication database applications include: home location registers (HLRs), visitor location registers (VLRs), authentication centers (AuCs), short message service centers (SMSCs), and equipment identification registers (EIRs). The term SCP is commonly used to broadly refer to a network element that includes a database system for providing database-intensive services, such as those discussed above.

It will also be appreciated that with the continuing convergence of traditional telecommunication networks and traditional data networks, the number and variety of converged or inter-network service related database applications designed to service the needs of combined data-telecommunications subscribers (e.g., presence service databases, telephony-to-WWW domain name servers, etc.) will increase dramatically in the future. As this converged network environment continues to evolve, so will the tendency of network operators to place SCP-like database nodes within the data network component of the converged network environment. That is to say, PSTN and wireless telephone network operators will likely find the economics of data network operation favorable to the placement of SCP-like database nodes within the data sub-network of the converged network environment, as opposed to the traditional PSTN—signaling system 7 (SS7) sub-network. As such, SCP and SCP-like network elements that have traditionally resided within an SS7 signaling network and been assigned a unique SS7 network address (point code and subsystem) would instead be placed within a data network, such as a transmission control protocol/Internet protocol (TCP/IP) based network, and would consequently be assigned an Internet protocol (IP) network address, hostname, and port number.

It will also be appreciated that in addition to database nodes, the convergence of telephony and data networks has led to the advent of numerous network elements that are associated with call setup and teardown functions which reside in or on the edge of the data network component of the converged communications network environment. Such network elements include media gateways (MGs), media gateway controllers (MGCs), and softswitch (SS) nodes, all of which are well known to those skilled in the art of Internet telephony. These nodes typically communicate using a data network based protocol (e.g., TCP/IP) in a manner similar to that of the SCP and SCP-like database nodes discussed above.

Shown inFIG. 1 is a sample converged communication network, generally indicated by thenumeral100. Convergednetwork100 includes a signaling system 7 (SS7) network component and an Internet protocol (IP) network component. The SS7 network component includes a service control point (SCP)104, a signal transfer point (STP)106, and an end office (EO) or service switching point (SSP)108. It will be appreciated that these SS7 nodes are connected via dedicated SS7 communication links, and consequently communicate using SS7 formatted signaling messages. The IP network component includes an IP based database server (DBS)112, a first media gateway controller (MGC)114, and a second MGC116. These IP nodes are connected via IP communication links, and consequently communicate using IP formatted signaling messages. A signaling gateway node (SG)120 facilitates inter-network communication. SG120 is adapted to communicate via one or more SS7 links with the SS7 network component, while simultaneously communicating with the IP network component via one or more TCP/IP connections or sockets. SG120 provides a degree of signaling message protocol translation, such that signaling messages originating in the IP network may be properly communicated to the appropriate destination node in the SS7 network, and vice versa.

An example of this inter-network message communication functionality is also provided inFIG. 1. In this example,MGC node116 formulates and transmits an IP-based query message, Q, that is ultimately destined forSCP node104 in the SS7 network. However, it will be appreciated that the SS7 and IP sub-networks are separate and distinct entities that have a limited knowledge of each other's architecture or communication protocols. The query message passes through the IP network and eventually arrives at thesignaling gateway node120, where it is received, processed, and re-formatted into a form suitable for transmission through the SS7 network. A new SS7 query message, Q*, is subsequently generated and routed viaSTP106 to the destination node,SCP104. In response,SCP104 generates an SS7 reply message, R*, which is routed viaSTP106 back to SG120. SG120 again receives, processes, and re-formats the reply message into a form that is suitable for transmission through the IP network. The new IP reply message, R, is subsequently routed through the IP network back to MGC116 in response to the original query.

The converged network architecture described above functions reasonably well; however, efficient and effective network management can become a significant problem in such networks. This difficulty arises from the same basic issue that was raised previously with regard to message routing; i.e., the SS7 and IP sub-networks are separate and distinct entities which have a limited knowledge of each other's architecture, communication protocols, and network management procedures.

With particular regard to the issue of network management, in a traditional SS7 signaling network there exist three categories of network management: traffic management, link management, and route management. Traffic management is the process of diverting messages away from failed links, while link management involves the activation and deactivation of signaling links. Route management is responsible for both re-routing messages around failed SS7 signaling points and controlling the flow of messages to any given signaling point in the network. Those skilled in the art of SS7 signaling network operation will appreciate such a network management strategy provides a layered approach to managing anomalistic events in an SS7 network. The SS7 protocol provides procedures designed to minimize the effects of network congestion and outages from the link level all the way up to the route level. Within the SS7 message transfer part (MTP) protocol, level two facilitates the detection of errors on individual signaling links. Level two is not concerned with communication abnormalities that arise outside the signaling point, but instead is adapted to resolve those issues associated with an individual signaling link. Again, it will be appreciated that every SS7 signaling link incorporates this function, which is controlled by level-three link management.

When an error is encountered, level two reports the error to level three, which in turn must then determine which error resolution procedures to invoke. In general, SS7 error resolution procedures begin at the lowest level, the link level, and work their way up to the highest level, the route level. While these procedures do not have a direct impact on routing or the status of signaling points, they do, however, trigger other level-three network management events.

Traffic management is effected by link management, primarily because traffic management must divert traffic away from a link that link management has failed and removed from service. For example, each SS7 signaling link may have a link buffer that stores messages to be transmitted. Once an acknowledgement is received from the receiving node, the corresponding message can be over-written or removed from the link buffer. If a message is not acknowledged within a predetermined time period, it will be retransmitted. Thus, messages must be stored in the link buffer until they are acknowledged.

When a signaling link fails, its associated link buffer in the transmitting node may contain many unacknowledged messages because the original messages may not have reached the destination or the acknowledgements may not have reached the source. Traffic management diverts traffic from the failed link to a new link and copies any unacknowledged messages from the link buffer associated with the failed link to the link buffer for the new link. The unacknowledged messages transferred to the new link buffer may then be retransmitted. In this manner, traffic management ensures the orderly delivery of all diverted traffic.

It should be noted that the traffic management process does not divert traffic away from a signaling point. The purpose of traffic management is simply to redirect traffic at a signaling point to a different signaling link associated with the signaling point. It is true, however, that the traffic management process does impact routes and route-sets to specific destinations. If a particular route is used by another signaling point to reach a destination, and traffic management has diverted traffic away from that route, adjacent signaling points may have to invoke route management procedures.

At the highest level, route management, unlike traffic management, diverts traffic away from signaling points that have become unavailable or congested. Regardless of the root cause, traffic management and link management will be involved at the affected signaling point. At the same time, all the signaling points around the affected signaling point are forced to invoke route management procedures to prevent messages from becoming lost.

In an SS7 network the above-described network management functionality is accomplished, in part, through the use of specific network management messages. A sample structure of a typical SS7 network management message or message signaling unit (MSU)150 is illustrated inFIG. 2. It will be appreciated by those skilled in the art of SS7 signaling communications that signaling information field (SIF)152 ofMSU150 contains data associated with a particular point code that is experiencing difficulty or a particular link that has failed. Additional status information, priority codes, and other relevant maintenance codes may also be included inSIF parameter152, depending upon the particular type of network management message being sent.

There are a number of routing management messages that are commonly employed to re-direct traffic around a failed or congested route. Again, it will be appreciated that such messages may be sent by an SS7 signaling point in response to the failure of one or more provisioned links. More particularly, when a route fails, a routing management message is sent to all neighboring SS7 signaling nodes (i.e., those SS7 signaling nodes that are adjacent to the troubled signaling node). This routing management message informs the neighboring SS7 signaling nodes of the problem at the troubled node and also provides instructions regarding future routing to the troubled node. It will also be appreciated that routing management messages are also used to inform neighboring SS7 signaling nodes of the recovery of a previously troubled node. Such SS7 routing management messages include: transfer prohibited (TFP), transfer restricted (TFR), transfer controlled (TFC), transfer allowed (TFA) messages, transfer cluster prohibited (TCP), and transfer cluster allowed (TCA). These messages are only a subset of all network management messages defined in the SS7 protocol. A comprehensive discussion of SS7 network management and related issues can be found inSignaling System #7 by Travis Russell, McGraw-Hill Publishing 1998.

A transfer prohibited (TFP) message is generated and transmitted by an SS7 signaling point (e.g., an STP) in response to determining that communication with an SS7 node is no longer possible. In response to determining that communication with an SS7 node is possible, but sub-optimal, a transfer restricted (TFR) message is sent. A TFR message essentially requests that adjacent SS7 signaling points use alternate routes when sending messages to the troubled SS7 node. If alternate routes are not available, messages may continue to be routed normally. A transfer controlled (TFC) message is sent by an SS7 signaling point (e.g., STP) in response to the receipt of an MSU that is destined for a congested route. In such a scenario, the MSU is discarded and a TFC message is returned to the originator or sender of the MSU. A transfer allowed (TFA) message is sent by an SS7 signaling point when a previously failed route once again becomes available.

Shown inFIG. 3 is a scenario involving network management message flow in convergedcommunications network100 described above with regard toFIG. 1. In this example, it is assumed that the SS7 communication link that connectsSTP106 andSCP104 has failed. In response to the detection of this failure,STP106 transmits a transfer prohibited (TFP) network management message to each of it's neighboring SS7 signaling points,SSP108 andSG120. Consequently, bothSSP108 andSG120 are made aware that they should not attempt to send any SS7 MSU traffic toSCP104 via a route that involvesSTP106.

It will be appreciated that, in the absence of such proactive network management procedures,SSP108 andSG120 might floodSTP106 with MSUs as a result of continuous, repeated attempts to obtain a response from the failed orinaccessible SCP104. In such a scenario,STP106 could incur significant congestion that might interfere with or prevent the routing of messages to other available SS7 signaling nodes in the network. As such, it is possible that the failure of one node in the network could potentially lead to the failure of another, and so on. It is precisely this situation that SS7 network management procedures are designed to prevent.

Given the discussion above, a significant problem encountered with converged networks now becomes more apparent. As shown inFIG. 3,SSP108 andSG120 are notified that they should no longer send messages toSCP104. However, since nodes in the IP component of the converged network are not capable of directly receiving and interpreting SS7 messages, there is no method of notifying any IP nodes in the IP sub-network that messages destined forSCP104 should not be sent. Those skilled in the art of IP network operation will appreciate that some transport and higher layer protocols in the IP protocol stack employ periodic retransmission of messages if no response or acknowledgment is received within a pre-defined acknowledgment interval. As such,SG120 may become flooded with re-transmitted query messages, destined forSCP104, from nodes within the IP network. Again, it will be appreciated by those skilled in the art of communication network operations that such a scenario can have significant adverse impacts on the overall viability of the converged network.

Therefore, what is needed is a system and method of extending network management functionality in converged communication network environment such that anomalistic events, and any subsequent resolution procedures, occurring in one sub-network component of the converged network can be effectively communicated to another sub-network component of the converged network.

SUMMARY

The present invention includes a communications network element that is capable of routing messages and also performing inter-network management functions in a converged telephony-data network environment. In one embodiment, the present invention is implemented in the form of a signaling gateway routing node which is adapted to facilitate signaling communication between nodes in a signaling system 7 network and nodes in an Internet protocol (IP) network. In addition to basic message routing functionality, the signaling gateway routing node is adapted to notify nodes in the IP network when a node in the SS7 network becomes congested or unavailable. In certain cases, the signaling gateway selectively notifies only IP nodes that are concerned with the status of the troubled SS7 node; while in other cases, notification messages are broadcast to all relevant IP nodes. The signaling gateway also serves to limit the number of status queries or polling messages that are conveyed from IP nodes through to the distressed SS7 node, thereby reducing needless congestion in the SS7 network during a node distress episode. By doing so, the signaling gateway routing node according to an embodiment of the present invention provides much needed network management service in the converged telephony-data network environment.

The functions for providing converged network management are described herein as modules or processes. It is understood that these modules or processes may be implemented as computer-executable instructions embodied in a computer-readable medium. Alternatively, the modules or processes described herein may be implemented entirely in hardware. In yet another alternative embodiment, the modules or processes described herein may be implemented as a combination of hardware and software.

The processes and modules for providing converged network management functionality are described below as being associated with cards or subsystems within a gateway routing node. It is understood that these cards or subsystems include hardware for storing and executing the processes and modules. For example, each card or subsystems described below may include one or more microprocessors, such as an x86 microprocessor available from Intel Corporation, and associated memory.

Accordingly, it is an object of the present invention to provide a routing node that facilitates the inter-network communication of network management type messages in a converged network environment.

It is another object of the present invention to provide a system and method for use in a converged network environment whereby an Internet protocol (IP) device is able to divert traffic from one of a mated pair of signaling gateway (SG) nodes to the other in the event that one of the mated SG nodes is not able to access a particular destination point code.

It is yet another object of the present invention to provide a system and method for use in a converged network environment whereby an IP device is able to audit the status of a point code associated with an SS7 signaling point.

It is yet another object of the present invention to provide a system and method for use in a converged network environment whereby network management information associated with a distressed SS7 node is distributed to concerned nodes in an IP network.

It is yet another object of the present invention to provide a system and method for use in a converged network environment whereby an IP device may be notified of congestion in an SS7 sub-network component of the converged network environment.

It is yet another object of the present invention to provide a system and method for use in a converged network environment whereby an IP device is able to assist in the abatement of congestion in an SS7 sub-network component of the converged network environment.

It is yet another object of the present invention to provide a system and method for use in a converged network environment whereby an IP device is able to obtain SS7 User Part Unavailability status from in an SS7 sub-network component of the converged network environment.

It is yet another object of the present invention to provide a system and method for use in a converged network environment whereby only one of a plurality of similar status request queries or polling messages sent by IP nodes is permitted to enter an SS7 network component of the converged network.

It is yet another object of the present invention to provide a system and method for use in a converged network environment whereby the receipt of a single SS7 network management message results in the distribution of multiple IP messages containing the SS7 network management message information.

Some of the objects of the invention having been stated hereinabove, other objects will become evident as the description proceeds, when taken in connection with the accompanying drawings as best described hereinbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a network diagram illustrating signaling message flow through a conventional converged telephony-data network.

FIG. 2 is a schematic diagram of a conventional signaling system 7 (SS7) network management message structure.

FIG. 3 is a network diagram illustrating conventional signaling message flow through a converged telephony-data network in the event of an SS7 signaling link failure.

FIG. 4 is a block diagram of a conventional signaling gateway routing node architecture suitable for use with embodiments of the present invention.

FIG. 5 is a schematic diagram of a signaling gateway routing node according to an embodiment of the present invention.

FIG. 6 is a schematic diagram of an SS7 link interface module (LIM) illustrating message flow associated with the receipt of a network management message according to an embodiment of the present invention.

FIG. 7 is diagram illustrating sample linkset and link selector tables associated withLIM300 illustrated inFIG. 6.

FIG. 8 is a schematic diagram of an Internet protocol (IP) capable enhanced data communication module (eDCM) according to an embodiment of the present invention.

FIG. 9 is a diagram illustrating a sample routing key table associated witheDCM350 illustrated inFIG. 8.

FIG. 10 is a diagram illustrating a sample socket table associated witheDCM350 illustrated inFIG. 8.

FIG. 11 is a network diagram that illustrates the flow of network management messages associated with an SS7 link failure episode according to an embodiment of the present invention.

FIG. 12 is a schematic diagram of an eDCM including internal message flows associated with an SS7 link failure episode according to an embodiment of the present invention.

FIG. 13 is a network diagram that illustrates message flows associated with a point code availability poll that is initiated by an IP node according to an embodiment of the present invention.

FIG. 14 is a network diagram that illustrates message flows associated with a point code availability poll that is initiated by one of many IP nodes that are aliased to the same SS7 point code according to an embodiment of the present invention.

FIG. 15 is a schematic diagram of an eDCM including internal message flows associated with a point code availability poll that is initiated by an IP node according to an embodiment of the present invention.

FIG. 16 is a network diagram that illustrates message flows associated with simultaneous point code congestion polls that are initiated by multiple IP nodes according to an embodiment of the present invention.

FIG. 17 is a network diagram that illustrates message flows associated with a point code congestion poll and subsequent distribution of a congestion response message according to an embodiment of the present invention.

DETAILED DESCRIPTION

Disclosed herein are several embodiments of the present invention, all of which include a network element that performs functions similar to that of a traditional telecommunications network packet routing switch, such as a signaling gateway routing node (SG). Each of the embodiments described and discussed below, employs an internal architecture similar to that of high performance signal transfer point (STP) and SG products which are marketed by the assignee of the present application as the Eagle® STP and IP⁷Secure Gateway™, respectively. A block diagram that generally illustrates the base internal architecture of the IP⁷Secure Gateway™ product is shown inFIG. 4. A detailed description of the IP⁷Secure Gateway™ may be found in Tekelec publication PN/909-0767-01, Rev B, August 1999, entitledFeature Notice IP⁷Secure Gateway™ Release1.0, the disclosure of which is incorporated by reference in its entirety. Similarly, a detailed description of the Eagle® STP may be found in theEagle® Feature GuidePN/910-1225-01, Rev. B, January 1998, published by Tekelec, the disclosure of which is incorporated herein by reference in its entirety. The specific functional components of an IP⁷Secure Gateway™ for transmitting and receiving transaction capabilities application part (TCAP) messages over an Internet Protocol (IP) network are described in commonly-assigned, co-pending International Patent Publication No. WO 00/35155, the disclosure of which is incorporated herein by reference in its entirety. Similarly, the functional components of an IP⁷Secure Gateway™ for transmitting and receiving ISDN user part (ISUP) messages over an Internet Protocol (IP) network are described in commonly-assigned, co-pending International Patent Publication No. WO 00/35156, the disclosure of which is also incorporated herein by reference in its entirety. As described in the above referencedFeature Notice IP⁷Secure Gateway™, an IP⁷Secure Gateway™250 includes the following subsystems: a Maintenance and Administration Subsystem (MAS)252; acommunication subsystem254 and anapplication subsystem256.MAS252 provides maintenance communications, initial program load, peripheral services, alarm processing and system disks.Communication subsystem254 includes an Interprocessor Message Transport (IMT) bus that is the main communication bus among all subsystems in the IP⁷Secure Gateway™250. This high-speed communications system functions as two 125 Mbps counter-rotating serial buses.

Application subsystem256 includes application cards that are capable of communicating with the other cards through the IMT buses. Numerous types of application cards can be incorporated intoSG250, including but not limited to: a link interface module (LIM)258 that interfaces with SS7 links and X.25 links, an data communication module (DCM)260 that provides an Internet Protocol (IP) interface using Transmission Control Protocol (TCP), and an application service module (ASM)262 that provides global title translation, gateway screening, and other services.DCM260 sends and receives Internet Protocol (IP) encapsulated SS7 messages over an IP network, as described in the above referencedFeature Notice IP⁷Secure Gateway™ Release1.0 publication.

Signaling Gateway Architecture

FIG. 5 illustrates a signaling gateway (SG) routing node according to an embodiment of the present invention that is generally indicated by the numeral270. InFIG. 5,SG routing node270 is communicatively coupled to a signaling system 7 (SS7) signalingnetwork274 via anSS7 signaling link276, and to an Internet Protocol (IP)data network278 via anIP connection280. It will be appreciated that these networks, taken together, constitute the functional network components of a converged telephony-data network. As such, telephony-related signaling information may be transported through either network sub-component. As further illustrated inFIG. 5,SG routing node270 includes a high-speed interprocessor message transport (IMT)communications bus320. Communicatively coupled toIMT bus320 are a number of distributed processing modules or cards including: a pair of maintenance and administration subsystem processors (MASPs)272, an SS7 capable link Interface module (LIM)300, and an Internet protocol (IP) capable enhanced data communication module (eDCM)350. These modules are physically connected to theIMT bus320 such that signaling and other types of messages may be routed internally between all active cards or modules. For simplicity of illustration, only asingle LIM300 andDCM350 are included inFIG. 5. However, it should be appreciated that the distributed, multi-processor architecture of theSG routing node270 facilitates the deployment of multiple LIM, DCM and other cards, all of which could be simultaneously connected to and communicating viaIMT bus320.

From a hardware perspective,LIM300 andeDCM350 may each comprise a printed circuit board physically connected toIMT bus320. Each printed circuit board may include a communication processor programmed to send and receive messages viaIMT bus320. Each printed circuit board may also include an application processor programmed to perform various functions. For example, the application processor ofeDCM350 may be programmed to perform the functions described herein for sending SS7 network management messages to IP nodes.

MASP pair272 implement the maintenance and administration subsystem functions described above. AsMASP pair272 are not particularly relevant to a discussion of the flexible routing attributes of the present invention, a detailed discussion of their function is not provided herein. For a comprehensive discussion of additional MASP operations and functionality, the above-referenced Tekelec IP⁷Secure Gateway™ and Eagle® STP publications can be consulted.

Given the SG routing node internal architecture shown inFIG. 5 and briefly discussed above, it will be appreciated that the most fundamental operation of theSG270 involves the receipt of a signaling message atLIM300 from an SS7 network and the subsequent internal routing of this message toeDCM350 for transmission into theIP network278, and vice versa.

Link Interface Module (LIM) Architecture

Referring toFIG. 6 and focusing now on LIM card functionality, it will be appreciated thatLIM300 is comprised of a number of sub-component processes including, but not limited to: an SS7 message transfer part (MTP)level 1process302, an SS7 message transfer part (MTP)level 2process304, an I/O buffer orqueue306, anSS7 MTP level 3 message handling and discrimination (HMDC)process308, a message handling and routing (HMRT)process310, and a message handling and distribution (HMDT)process312.MTP level 1process302 is adapted to provide the facilities necessary to send and receive digital data over a particular physical media/physical interface, such as a DS0 type communication link. Working in conjunction with theMTP level 1process302,MTP level 2process304 provides for basic error detection/correction and sequenced delivery of all SS7 message packets. I/O queue306 provides for temporary buffering of incoming and outgoing SS7 signaling message packets.HMDC process308 receives signaling messages from the lower processing layers and performs a discrimination function, effectively determining whether an incoming SS7 message packet requires internal processing or is simply to be through switched.HMRT process310 is adapted to receive and route messages from thediscrimination process308 that do not require further processing at the SG and are simply to be through switched.HMDT process312 is adapted to facilitate the internal routing of SS7 message packets, received from thediscrimination process308, that do require additional SG based processing prior to final routing.

Also included onLIM300 are a functional group of processes that are generally associated with the routing of signaling messages, at both an internal and external level. That is, the information contained in this group of functional processes comprises a set of rules for the routing of a received signaling message within an associated signaling network. Tightly coupled or closely related to this set of network routing rules is an associated set of rules that describe and define the routing of the signaling message within the SG node.

As indicated inFIG. 6, these functional routing processes include a link selection manager (LSM)process314, a linkset selector table316, and a link selector table318. Tables316 and318 contain signaling route and signaling route status information, along with internal IMT bus routing information. As mentioned above, these tables facilitate the overall routing of an SS7 signaling message received by theLIM300.LSM process314 is adapted to perform a number of functions including the administration of routing data within the linkset and link selector tables316 and318, respectively.LSM314 is further adapted to notify other communication modules, generally within the SG, and coupled toIMT bus320 of changes in the status of links and other nodes in the SS7 network. In one embodiment of the present invention,LSM314 is adapted to receive an SS7 network management (NM) message, use information contained within the NM message to update route status information in linkset selector table316 and link selector table318, respectively, and subsequently distribute the NM information to other communication modules connected toIMT bus320.

FIG. 7 includes sample table structures and data associated with linkset and link selector tables316 and318, respectively. Example linkset selector table316 includes a key field that is used to effectively index the data table. This index is comprised of an SS7 destination point code (DPC)322. Linkset selector table316 also includes aroute cost field324, alinkset status field326, an adjacentnode status field328, anoverall status field330, and a linkset identifier orpointer field332.

Link selector table318 includes a compound key that is comprised of alinkset identifier336 and asignaling link field338. Link selector table318 also includes anIMT address field340, which contains IMT bus address information associated with communication modules that are connected to theIMT bus320. More particularly, a record in the table318 includes an IMT address value that is associated with the communication module that supports the specific link identified in the record key. For example, as shown inFIG. 7, link0 oflinkset1 resides on a communication module that has an IMT bus address of1305. Furthermore alink status field342, indicates thatlink0 oflinkset1 is available for service.

It will be appreciated, as generally indicated inFIG. 6, that a first database lookup in linkset selector table316 returns an index value or pointer that is subsequently used in a second database lookup in link selector table318. The ultimate result of this two-stage lookup procedure is an IMT bus address associated with a communication module. It will also be appreciated that any number of database configurations or structures could be effectively employed to achieve a functionality similar to that described above. The database table structures shown inFIG. 7 merely illustrate one example implementation.

Once again, it should be appreciated that a LIM card may contain more functional processes than those described above. The above discussion is limited to LIM functionality associated with the basic processing of inbound SS7 signaling messages.

Enhanced Data Communication Module (eDCM) Architecture

FIG. 8 illustrates an enhanced data communication module (eDCM) according to an embodiment of the present invention, generally indicated by the numeral350.eDCM350 is connected toIMT communication bus320 and is comprised of a number of functional modules or processes. These modules include: alayers 1 and 2module352, alayers 3 and 4module354, an I/O buffer orqueue358, an HMDC (message discrimination)process360, an HMDT (message distribution)process362, an HMRT (message routing)process364, a linkselection manager process366, a linkset selector table368, and a link selector table370.

Layers 1 and 2module352 provides physical and data link layer functions for upper layer services. For example, layers 1 and 2module352 may implement a digital communication link that delivers bits over a physical medium. In addition, layers 1 and 2module352 may frame packets so that the receiver can recover the packets and can arrange for retransmission of packets.

Layers 3 and 4module354 provides network and transport layer services for incoming and outgoing packets. Exemplary network layer services that may be provided bylayers 3 and 4module354 include routing packets from source to destination along a path that may comprise a number of links. Exemplary transport layer services that may be provided include message sequencing, timeouts, and retransmissions.

In addition to theconventional layers 3 and 4 functions,module354 may translate between SS7 and IP address schemes. In order to perform such translation,layer3process354 may utilize the procedures described in one or more of the existing standards for such conversions, such as that described in IETF Internet Draft draft-benedyk-sigtran-tali-01.txt, the disclosure of which is incorporated herein by reference in its entirety. Alternatively, such a mapping may be performed using the packet formats as described in RFC 2960: Stream Control Transmission Protocol, October 2000, the disclosure of which is incorporated herein by reference in its entirety.

I/O queue358 provides for temporary buffering of incoming and outgoing IP signaling message packets.HMDC process360 receives signaling message packets from the lower processing layers and performs a discrimination function, effectively determining whether an incoming IP message packet requires internal processing or is simply to be through switched.HMRT process364 is adapted to receive and route messages frommessage discrimination process360 that do not require further processing at the SG and are simply to be through switched.HMDT process362 is adapted to facilitate the internal routing of IP message packets, received frommessage discrimination process360, that do require additional SG based processing prior to final routing.

Linkselection manager process366 is adapted to perform a number of functions including the administration of routing data within the linkset and link selector tables368 and370, respectively. It will be appreciated that the linkset and link selector tables368 and370 are similar in structure and form to the corresponding LIM based databases illustrated inFIG. 7. As such, these linkset and link selector tables contain signaling route and signaling route status information, along with internal IMT bus routing instructions.LSM360 is further adapted to notify other communication modules, generally within the SG, and coupled toIMT bus320 of changes in the status of links and other nodes in both the SS7 and IP network components. In one embodiment of the present invention,LSM360 is adapted to receive an IP-based TALI or SCTP network management (NM) message, use information contained within the NM message to update route status information in the linkset and link selector tables368 and370, respectively, and subsequently distribute the NM information to other communication modules connected toIMT bus320.

It will be appreciated fromFIG. 8 that layers 3 and 4process354 is further comprised of an inboundmessage manager process372, an MTPprimitive controller process374, an outboundmessage manager process376, a routingkey database378, and asocket database380. An incoming IP message fromIP network278 is received by inboundmessage manager process372 which subsequently examines the message packet and determines the appropriate response or processing action that is required. For instance, if the incoming IP signaling message packet is a call setup type message, the inbound message manager (IMM)process372 may simply de-capsulate the SS7 portion of the message packet and subsequently pass the message to the I/O queue358. If, however, the incoming IP signaling message packet is a network management information request or polling type message,IMM process372 may extract relevant information from the message packet and consult MTPprimitive controller process374. MTPprimitive controller process374 examines the extracted information and generates an appropriate, related SS7 MTP message that can be routed to and interpreted by other SS7 nodes in an SS7 network. In some instances, the MTPprimitive controller process374 need not be consulted, and in such cases theIMM process372 will respond directly. The particular response provided depends on the character of the original received IP network management message, and several such response scenarios will be discussed in more detail below.

Outbound message manager (OMM)process376 is adapted to receive an outbound data packet from I/O queue358 and begin the process of preparing the data packet for transmission into an IP network. As discussed above, exemplary packet structures that may be used to transmit SS7 messages over an IP network include TALI over TCP/IP or SCTP/IP.OMM process360 receives a data packet from I/O queue358 and, using information contained in the data packet, consults the routing key and socket tables378 and380, respectively, for appropriate routing address information.

FIG. 9 illustrates an example of routing key table378. More particularly, sample routing key table378 is comprised of multiple routing key fields including: an SS7 destination point code (DPC)382, an SS7 origination point code (OPC)384, a service indicator (SI)386, a circuit identification code (CIC)388, and a sub-system number (SSN)390. Those skilled in the art of SS7 network operation will appreciate that such routing keys are commonly employed in SS7 routing nodes (i.e., STPs) to determine how and to where a signaling message packet should be routed. It will also be appreciated that many different combinations of signaling message parameters may be used to form a routing key, and as such, the particular structure presented inFIG. 9 is simply one of many possible routing key table structures.

Associated with each routing key record in the routing key table378 is a socket identifier orpointer392. This socket identifier is used to access data in the associated socket table380, shown inFIG. 10. Referring toFIG. 10, socket table380 includes information that defines a particular IP socket connection. More particularly, table380 includes asocket identifier394, and associated local IP addresses andport numbers395 and distant IP addresses andport numbers396. Socket table380 also includes asocket status field397, which contains availability status information related to each socket that is defined in the table.

Once again, it will be appreciated that the database structures and tables described above are merely illustrative of the types of data that can be employed to provide the functionality of an eDCM of the present invention.

SG Functionality Associated with an SS7 Node or Link Failure

Shown inFIG. 11 is a simplified converged SS7-IP communication network, generally indicated by the numeral400.Network400 is comprised of a number of SS7 network elements including a service control point (SCP)104 and a signal transfer point (STP)106. Convergednetwork400 also includes anIP network110 and a number of IP connected network elements such as a database server node (DBS)112, a first media gateway controller (MGC)114, and asecond MGC node116.

As further indicated inFIG. 11, it will be appreciated that each of the SS7 network elements is assigned a unique SS7 address or point code (PC), such thatSCP104 is identified in the SS7 network as PC=6-1-1,STP106 is identified as PC=5-1-1. In a similar manner, each IP network element is assigned a unique IP address, such thatDBS node112 is identified in the IP network as IP=10.10.10.1:Port24,MGC114 is identified as IP=10.10.10.2:Port12, andMGC116 is identified as IP=10.10.10.3:Port54. In the converged network environment, it will be further appreciated that each IP network element is assigned an SS7 network address or alias, such thatDBS node112 is also identified by the SS7 point code PC=3-1-1,MGC114 is identified by PC=3-1-2, andMGC116 is identified by PC=3-1-3.

Also included in convergednetwork400 is a signaling gateway (SG)routing node402 of the present invention. As such, it will be appreciated thatSG402 includes both LIM and eDCM communication modules, as described above. In the simplified network diagram shown inFIG. 11,SG402 communicates with adjacentSS7 STP node106 via a single SS7 signaling link.SG402 communicates withIP DBS node112,IP MGC node114, andIP MGC node116 via a plurality of IP sockets. Furthermore, in the examples discussed herein, it is assumed thatSG402 and the IP nodes connected thereto all implement an appropriate stream-oriented communication protocol, such as TALI over TCP/IP or SCTP/IP. Again, it will be appreciated that a number of functionally similar protocols that provide reliable, stream-oriented communication could also be employed by the SG and IP nodes to facilitate communication.

The particular scenario presented inFIG. 11 corresponds to the case where a node in an SS7 network fails or becomes inaccessible. Such a situation may arise from one or more signaling link failures or possibly a higher level failure within the node. In any event, in the example shown inFIG. 11,SCP node104 is assumed to experience a signaling link failure that effectively isolates the node from all other elements in the converged network. Upon determination thatSCP node104 is unavailable,SG402 generates an SS7 transfer prohibited (TFP) network management message and subsequently sends copies of the TFP message to other SS7 nodes in the network. In this particular example,STP106 is notified of the problem withSCP node104 via the TFP message. Once notified and made aware of the unavailable status ofSCP104, SS7 nodes will not attempt to route SS7 signaling messages toSCP104 until such time as they are again notified bySG402 thatSCP104 has recovered.

Prior toSG402 according to an embodiment of the present invention, an efficient and effective technique whereby IP nodes in the converged network could take advantage of network management information generated within the SS7 component of a converged network environment did not exist. It is at this point that one of the significant advantages of the present invention will be appreciated. More particularly, it will be appreciated from the message flows illustrated inFIG. 11 thatSG402 is adapted to generate a related, IP-formatted, TALI- or SCTP-based point code unavailable (PCUA) message that is effectively and efficiently distributed to relevant nodes in the IP component of the converged network environment. As such,SG402 of the present invention is capable of generating and distributing a plurality of IP network management messages that are associated with or analogous to an SS7 network management message (e.g., a TFP message).

Upon receipt of a TALI PCUA message,DBS node112,MGC node114, andMGC node116 are effectively notified of the SS7 network difficulty and further transmission of IP originated signaling messages that would be destined forSCP104 is halted.

eDCM Response to an SS7 TFP Network Management Message

FIG. 12 illustrateseDCM communication module350 and relevant message flows associated with the SS7 node or link failure discussed above and generally illustrated inFIG. 11. For the purposes of example, it is assumed that the SS7 TFP network management message is generated atSG402 by the SS7 link interface module300 (illustrated inFIG. 6). TFP message creation and subsequent distribution is performed by one ormore MTP level 3 processes. In any event, a TFP message is generated and route availability information is updated in linkset and link selector tables316 and318, respectively. More particularly, route status information associated with failedSCP node104 needs to be updated to reflect the SCP node's unavailable state. As such,LSM314 facilitates the updating of linkset and link selector tables316 and318, respectively.

HMDT process312 determines that other communication modules connected toIMT bus320 also need to update their local linkset and link selector tables, and consequently distributes copies of the TFP network management message to other communication modules in the SG viaIMT bus320.

Returning toFIG. 12, it will be appreciated that a copy of the TFP network management message or at least a portion of the information originally contained therein is received ateDCM350 viaIMT bus320. More particularly, the TFP message is received by the local eDCM link selection manager (LSM)process366, which in turn uses the network management information to update route and link status information contained in linkset andlink selector databases368 and370, respectively.LSM390 forwards the TFP message to MTPprimitive controller374 andOMM376 processes which determine, based on information contained in the routing key and socket tables378 and380, respectively, that there are several provisioned IP communication links which have the capability of receiving IP node originated signaling messages that might be destined for the failedSCP node104. In the example shown inFIG. 11, the affected IP nodes includeDBS node112,MGC node114, andMGC node116. Consequently, these IP nodes need to be notified of the unavailable status ofSCP node104.

It will be appreciated that information may be stored in the routing key and socket databases that indicate whether a particular IP node prefers to receive broadcast type network management messages or instead to receive network management messages associated with a more selective response method. In the event that a network management (NM) message requiring broadcast distribution is received bySG402, all concerned nodes or point codes that are configured to accept broadcast type messages will receive the NM message, such as generally indicated inFIG. 11.

In the event that a NM message is received bySG402 that does not require broadcast distribution, a more selective response method may be employed. For example, a NM message could be received bySG402 which does not require broadcast distribution and which is specifically addressed to PC=3-1-1, the point code ofDBS node112. In such a case, the NM message may be selectively distributed toDBS node112, as shown inFIG. 13. As multiple sockets may be aliased to a single SS7 point code, it will be appreciated that in certain instances, a selective response method of the present invention may result in the distribution of a NM message to multiple IP nodes which all share the same SS7 point code address. In any event, the present invention is adapted to accommodate both broadcast and selective response type methods.

As such,LSM366 passes the TFP network management message to the outbound message manager (OMM)process376, via I/O queue358. Using information contained in the TFP message,OMM376 consults MTPprimitive controller process374 in order to formulate a IP-based network management message that is equivalent or related to the original SS7 TFP network management message. Once again, in this embodiment, the IP-based network management protocol may be TALI or SCTP. However, any stream-oriented mechanism for reliably transporting SS7 messages over an IP network may be employed.

MTPprimitive controller process372 returns an IP-based TALI or SCTP point code unavailable (PCUA) network management message toOMM376. In response,OMM376 consults the routing key and socket tables378 and380, respectively, to determine the particular socket or sockets over which the PCUA message should be transmitted. In the example routing key table378 shown inFIG. 9, there are three IP sockets that support communication withSCP node104. These sockets are identified as sock1, sock2, and sock3. Consequently,OMM process376 replicates the PCUA message so as to effectively produce one copy of the PCUA message for each of the three sockets. Each copy of the PCUA message is appropriately addressed, using IP address and TCP port information returned by the socket table380. The three PCUA messages are subsequently passed throughlayers 1 and 2 processing and transmitted into theIP network110 where they are eventually received by the three IP nodes:DBS112,MGC114, andMGC116. Again, it will be appreciated that upon receipt of a PCUA message, each of the above mentioned IP nodes is made aware of theSCP104 node or link failure, and further transmission of signaling messages from these IP nodes toSCP104 is halted. As such SS7 network management information has effectively been communicated to and acted upon by nodes in an IP network.

SG Functionality Associated with IP Availability Pollinq

Continuing with the failed SS7 node scenario presented inFIG. 11 and discussed in detail above,FIG. 13 illustrates a subsequent attempt by IP-basedDBS node112 to obtain information regarding the availability status of the failedSS7 SCP node104.

More particularly, it will be appreciated from the message flows illustrated inFIG. 13 thatDBS node112 is adapted to periodically poll the SS7 network component of the convergednetwork400 regarding the availability status ofSCP104. In the embodiment illustrated, such availability status polling may be accomplished or facilitated via a point code availability audit (PCAUD) TALI- or SCTP-formatted message.

As indicated inFIG. 13,DBS node112 generates and transmits a PCAUD message intoIP network110. The PCAUD message is received and subsequently processed bySG402. In the particular example shown inFIG. 13, it is assumed thatSCP104 continues to be unavailable for service andSG402 consequently responds with a TALI or SCTP point code unavailable (PCUA) message. It will be appreciated thatSTP106, which is the routing node immediately adjacent the failedSCP104, is not consulted forSCP104 status.SG402 of the present invention is adapted to utilize on-board route status information when generating a response to a PCAUD or similar type availability status poll from an IP-based node. As indicated inFIG. 13, it will also be appreciated thatSG402 responds with a single PCUA message that is sent to the PCAUD message originator over the socket through which the PCAUD message was received.

It will be appreciated that multiple IP nodes and/or socket connections may be aliased to the same SS7 point code in a converged network environment, as described in commonly-assigned, co-pending International Patent Publication No. WO 00/60812, the disclosure of which is incorporated herein by reference in its entirety. Such a scenario is generally illustrated inFIG. 14, and it will be appreciated that in such analiasing configuration SG402 is adapted to respond only to the specific DBS node that originated the PCAUD polling message. By doing so, network management signaling traffic withinIP network110 is kept to a minimum, thereby avoiding congestive conditions within the IP network. If a converged network operator were so inclined, however,SG402 could be configured to respond to all of the IP nodes (i.e., DBS nodes112a,112b, and112c) that are aliased to the SS7 point code 3-1-1.

eDCM Functionality Related to IP Availability Polling

FIG. 15 illustrateseDCM communication module350, and relevant message flows associated with the SS7 node availability poll discussed above and generally illustrated inFIGS. 13 and 14. For the purposes of example, it is assumed that the SS7 PCAUD network management message is received atSG402 byeDCM communication module350. As in previous figures, the dashed lines represent routing of the inbound messages, while the solid lines represent communication between processes. As generally indicated inFIG. 15, the PCAUD message is received viaIP layers 1 and 2process352, and is subsequently processed and directed toIP layers 3 and 4process354.

Withinlayers 3 and 4process354, the PCAUD message is received by inbound message manager (IMM)process372. In one embodiment,IMM process372 consults linkset selection manager (LSM)process366, which examines information contained in the received PCAUD network management message and determines the availability status of the SS7 node in question. This SS7 point code availability status determination is facilitated by SS7 point code/route status information that is maintained in link selector table370.

For the purposes of this example, it is assumed that the point code/route status information returned byLSM process366 indicates thatSCP node104 is still unavailable. This status information is returned toIMM process372 which subsequently generates a TALI PCUA network management response message and passes this message to outbound message manager (OMM)process376 via I/O queue358. It will be appreciated that in this case, information identifying the originating socket over which the PCAUD message was received is placed in the PCUA message packet byIMM process372. Consequently,OMM process376 need not necessarily consult the routing key andsocket databases378 and380, respectively, to determine the particular IP socket or sockets over which the PCUA message should be transmitted. Instead the PCUA message packet is passed tolayers 1 and 2352 and subsequently transmitted to and received byDBS node112, as shown inFIG. 13.

Again, it will be appreciated that upon receipt of a PCUA message,DBS node112 is again made aware of the continuingSCP104 node or link failure, and transmission of signaling messages from this IP node toSCP104 remains suspended.

SG Functionality Related to IP Congestion Poll Filtering

Shown inFIG. 16 is a converged network scenario that involves an SS7 node that is in a congested state. More particularly, convergednetwork420 includesSCP node104 that is experiencing congestion, possibly due to an abnormally high volume of signaling traffic across the SS7 communication link that connects the node toSTP106. It will be appreciated that upon receipt of an MSU destined for thecongested SCP104,STP106 would typically generate an SS7 transfer controlled (TFC) network management message and subsequently notifies the MSU originator of the congested status ofSCP104. It should also be appreciated that this initial SS7 TFC network management message is not broadcast to all concerned IP nodes in a manner analogous to that described above for TFP type messages. With TFC type congestion NM messages, more selective response methods may be employed bySG402.

Subsequent to the initial TFC notification, an affected IP node is adapted to periodically poll the congested SS7 node in an attempt to determine when the congestion has abated, and normal routing can resume. The particular example scenario illustrated inFIG. 16 involves the simultaneous or near simultaneous polling by the three IP nodes:DBS112;MGC114; andMGC116. Once again, assuming that a TALI or SCTP signaling protocol is employed, the IP node generated polling messages are in the form of a congestion status audit (CONGAUD) type network management message. As indicated inFIG. 16, while all three independently generated CONGAUD messages are received atSG402 simultaneously or nearly simultaneously, only one SS7 route set congestion test (RCT) message is generated bySG402 and subsequently routed toSTP106. As such,SG402 effectively filters redundant congestion status polls received from theIP network110, and consequently reduces congestion on the SS7 signaling link that connectsSG402 andSTP106.

With regard to eDCM operation in such a scenario, it will be appreciated that in one embodiment such filtering is accomplished by an inbound message manger (IMM) process which is similar to the IMM processes previously disclosed herein. More particularly, an eDCM based IMM process is adapted to utilize a timer such that only a single CONGAUD message related to a specific SS7 node is conveyed through to the SS7 network in a pre-determined time period. A CONGAUD message that satisfies the time-filter criteria would be processed by an MTP primitive controller similar to those discussed previously, which would produce an equivalent, related SS7 RCT network management message. In a manner similar to those already described in detail herein, the SS7 RCT message would be internally routed within the SG to an appropriate LIM module via an IMT bus, where the RCT message would be transmitted toSTP106.

SG Functionality Related to Congestion Response Message Distribution

Shown inFIG. 17 is a converged network scenario that is related to that presented inFIG. 16 and discussed in detail above. Once again, convergednetwork430 includesSCP node104 that is experiencing congestion, possibly due to an abnormally high volume of signaling traffic across the SS7 communication link that connects the node toSTP106. As discussed previously,STP106 would have previously generated an initial SS7 transfer controlled (TFC) network management message and subsequently notified the DBS nodes corresponding to SS7 PC=1-1-1 (i.e., nodes112aand112b) of the congested status ofSCP104.

Subsequent to the initial TFC notification, the two affected IP nodes are adapted to periodically poll the congested SS7 node in an attempt to determine if the congestion atSCP104 has abated, and normal routing can resume. The particular example scenario illustrated inFIG. 17 involves a congestion status audit (CONGAUD) network management message that is originated by IP based DBS node112a. As indicated inFIG. 17, the CONGAUD message is received atSG402 and an SS7 route set congestion test (RCT) message is subsequently generated atSG402 in a manner similar to that previously described. The RCT message is routed toSTP106, which determines thatSCP104 is still congested and subsequently responds toSG402 with a TFC network management message that effectively confirms the congested status ofSCP node104.

In much the same manner as the TFP message in the example scenario presented inFIG. 11 and described in detail above, the TFC message is received by a LIM in theSG402 and subsequently routed internally via an IMT bus to an eDCM communication module. Again, at the eDCM module, the SS7 TFC network management message flow is similar to that generally illustrated inFIG. 12.

As such, it will be appreciated that a copy of the TFC network management message or at least a portion of the information originally contained therein is received ateDCM350 viaIMT bus320. MTPprimitive controller358 andOMM360 determine, based on the information contained in the routing key andsocket databases362 and364, respectively, that there are two provisioned IP communication sockets which are aliased to the point code (i.e., PC=1-1-1) that generated the original congestion audit NM message. In the example shown inFIG. 17, the concerned IP nodes include DBS nodes112aand112b.

Returning to the discussion of eDCM operation, as indicated inFIG. 12,LSM390 passes the TFC network management message to the outbound message manager (OMM)process360, via I/O queue376. Using information contained in the TFC message,OMM360 consults MTPprimitive controller process358 in order to formulate a IP-based network management message that is equivalent or related to the original SS7 TFC network management message. Once again, in this embodiment, it is assumed that the IP-based network management protocol is TALI- or SCTP-based. However, other reliable stream-oriented procedures may be used. In addition, any application layer protocol, such as SIP, may be used to communicate with the IP nodes.

MTPprimitive controller process358 returns an IP-based TALI point code congested (CONGLVL) network management message toOMM360. It will be appreciated that a CONGLVL type congestion message may include information that indicates the degree or level of congestion. In any event,OMM360 subsequently consults the routing key andsocket databases362 and364, respectively, to determine the particular socket or sockets over which the CONGLVL message should be transmitted. In the example routing key table362 shown inFIG. 9, there are two sockets that support communication withSCP node104. These sockets are identified as sock4, and sock5. Consequently,OMM process360 replicates the CONGLVL message so as to effectively produce one copy of the CONGLVL message for each of the two sockets. Each copy of the CONGLVL message is appropriately addressed, using IP address and TCP port information returned by thesocket database process364. The two CONGLVL messages are subsequently passed throughIP level 1 processing and transmitted into theIP network110 where they are eventually received by the two IP nodes: DBS112aand112b. Again, it will be appreciated that upon receipt of a CONGLVL message, each of the above mentioned IP nodes is made aware of the congested status ofSCP104 node so that alternate routes may be employed, if possible. It will be appreciated thatMGC node114 andMGC node116 do not receive copies of the congestion response message, as they are not associated with the PC 1-1-1.

Again, it should be noted that other signaling protocols and network management messages may be employed within the context of the present invention. Those skilled in the art of SS7 telecommunication networks will appreciate that functionality similar to that described above could be implement at a cluster routing level. Such a cluster routing scenario would involve different SS7 MTP network management messages and their corresponding TALI or SCTP equivalents, however the basic processing within a SG of the present invention would be similar. Again, it is the ability to effectively and efficiently communicate network management type information between different network components in a converged network environment that is key to the present invention. It will also be appreciated that various details of the invention may be changed without departing from the scope of the invention. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation—the invention being defined by the claims.

It will be understood that various details of the presently disclosed subject matter may be changed without departing from the scope of the presently disclosed subject matter. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation.

Claims (19)

1. A method for use at a gateway node in a converged telephony/data network for distributing operating status information associated with a node in a signaling system 7 (SS7) network of the converged network to nodes in an Internet protocol (IP) network of the converged network, the method comprising:

(a) receiving, at a gateway node, an SS7 network management message including operating status information associated with an SS7 node in the SS7 network;

(b) performing, at the gateway node, a routing key database lookup using information contained in the SS7 network management message and identifying a node in the IP network capable of communicating with the SS7 node; and

(c) in response to receiving the SS7 network management message and identifying the node in the IP network via the routing key database lookup, communicating, from the gateway node, the operating status information to the identified node in the IP network, wherein the identified node is located external to the gateway node.

2. The method ofclaim 1 wherein communicating the operating status information to an IP node in an IP network includes communicating the operating status information in a transport adapter layer interface (TALI) message.

3. The method ofclaim 1 wherein communicating the operating status information to an IP node in the IP network includes communicating the operating status information in a stream control transmission protocol (SCTP) message.

4. The method ofclaim 1 wherein communicating the operating status information to an IP node in the IP network includes communicating a point code unavailable (PCUA) message.

5. The method ofclaim 1 wherein communicating the operating status information to an IP node in the IP network includes communicating a point code available (PCAV) message.

6. The method ofclaim 1 comprising receiving a point code status audit message for requesting point code status information for the SS7 node from a node in the IP network, and, in response to the request, communicating the point code status information to the requesting node.

7. The method ofclaim 1 comprising receiving a point code congestion audit message from a node in the data network, the point code congestion audit message requesting point code congestion for the SS7 node and, in response to the congestion audit message, sending the point code congestion information to the requesting node.

8. The method ofclaim 1 wherein communicating the operating status information includes communicating a session initiation protocol (SIP) message.

9. The method ofclaim 1 wherein receiving an SS7 network management message includes receiving a transfer prohibited (TFP) message.

10. The method ofclaim 1 wherein receiving an SS7 network management message includes receiving a transfer allowed (TFA) message.

11. The method ofclaim 1 wherein receiving an SS7 network management message includes receiving a transfer restricted (TFR) message.

12. The method ofclaim 1 wherein receiving an SS7 network management message includes receiving a transfer controlled (TFC) message.

13. The method ofclaim 1 wherein performing a routing key database lookup using information contained in the SS7 network management message includes performing a routing key database lookup using an SS7 destination point code (DPC) value extracted from the SS7 network management message.

14. The method ofclaim 1 wherein performing a routing key database lookup using information contained in the SS7 network management message includes performing a routing key database lookup using an SS7 origination point code (OPC) value extracted from the SS7 network management message.

15. The method ofclaim 1 wherein performing a routing key database lookup using information contained in the SS7 network management message includes performing a routing key database lookup using an SS7 service indicator (SI) value extracted from the SS7 network management message.

16. The method ofclaim 1 wherein performing a routing key database lookup using information contained in the SS7 network management message includes performing a routing key database lookup using an SS7 circuit identification code (CIC) value extracted from the SS7 network management message.

17. The method ofclaim 1 wherein performing a routing key database lookup using information contained in the SS7 network management message includes performing a routing key database lookup using an SS7 subsystem (SSN) value extracted from the SS7 network management message.

18. The method ofclaim 1 wherein identifying a node in the data network capable of communicating with the SS7 node includes identifying a socket associated with the node in the data network.

19. A signaling gateway comprising:

(a) a routing key table for storing routing key information for identifying IP nodes in an IP network that are configured to communicate with an SS7 node in an SS7 network;

(b) a status manager process for determining or receiving status information relating to the SS7 node; and

(c) a communications module operatively associated with the routing key table and the status manager process for communicating, in response to receiving the status information and identifying the IP nodes in the routing key table, the status information to the identified IP nodes, wherein the identified IP nodes are located external to the signaling gateway and configured to communicate with the SS7 node using the routing key information.

Images