Method and Apparatus for Achieving Fabric Independent Routing Technique

This invention relates to a technique for routing calls from one telecommunication switching system to another switching system independent of the fabric in each system.

Present day telecommunications networks typically include a plurality of switching systems linked via transmission facilities (e.g., trunks and/or channels) that carry "calls" (in the form of voice, video or data) between switching systems. Additionally, these switching systems are typically linked via a signaling (data) network that transmits signaling messages between switching systems. Further, within a given telecommunications network, control information may flow between switching systems and databases, intelligent peripherals, or other specialized resources, as is well known in the art.

A present day switching system includes a switching fabric and a control mechanism as a single integrated system. The control mechanism of a switching system provides the intelligence to operate a specific switching fabric and some (or possibly all) of the intelligence required to interpret and respond to signals. The switching fabric includes devices for the termination of transmission facilities, as well as devices that provide multiple stages of space and time switching as is understood in the art. Additionally, the switching fabric may also include local intelligence, in the form of a processor or the like, for acting upon commands from the control mechanism. Within prior art switching systems, the control mechanism includes one or more special purpose computers that control such functions as connecting communications paths, and to varying degrees, receiving and sending signaling messages, performing operations, administration and maintenance functions, and providing call processing and customer services (e.g., service logic).

The switching fabric of present day switching systems controls call routing. In other words, the switching fabric, under control of its associated intelligence, makes decisions regarding trunk selection in order to transmit calls to another fabric of another switching system. Various techniques presently exist for routing calls and will not be discussed in detail. Examples of call routing techniques include Real-Time Network Routing (RTNR), Success to the Top Routing (STT) as well as Class-Of-Service Routing.

The nature of the switching fabric in present day switching systems is dependent on the nature of the calls carried by that fabric. For example, circuit-switch type switching systems typically utilize one type of fabric for carrying voice calls. In contrast, Asynchronous Transfer Mode (ATM) switching systems typically utilize a packet-type fabric for carrying data calls. Different types of fabrics route calls differently. Even though two different types of fabrics may utilize a particular routing technique, the implementation of that technique within one type of fabric is often necessarily different from its implementation in another type of fabric. Thus, when implementing a new routing technique, different implementations must be provided for different types of fabrics. As a result, development costs for implementing a new routing technique tend to be expensive.

Thus, there is need for a technique for achieving fabric-independent routing.

In its most general sense, the invention is directed to a novel apparatus and method for controlling routing in a switching system. Specifically, the invention comprises a routing processor (RP) for controlling routing independent of the fabric within the switching system. Note that the switching fabric within the switching system may be a packet-based fabric or a circuit-switched fabric.

The invention also provides a method for separation of the routing function from the connection functions, the latter occurring within the switching fabric. The routing processor of the invention maintains a dynamic routing data base that track calls in progress as well as the traffic load. The routing processor also allocates, and when necessary, reserves bandwidth among idle networks. The routing processor actually selects the route for each call by specifying a channel to a neighboring switching system that carries the call. Further, the routing processor has the capability to respond to queries from other switching systems regarding traffic load to enable the processor to assist the routing processor of the other switching system to make routing decisions.

FIG. 1 illustrates a block schematic diagram of telecommunications network that includes a plurality of switching systems each in accordance with the invention;

FIG. 2 illustrates a call flow diagram showing the manner in which calls are routed within the network of FIG. 1; and

FIG. 3 is a block schematic diagram of a second embodiment of the network of the invention.

FIG. 1 depicts a telecommunication network 10 comprising a first and second switching systems 12.sub.1 and 12.sub.2, each constructed in accordance with the invention. The switching systems 12.sub.1 and 12.sub.2 each includes multiple call processors 14--14, each of which possesses the call associated logic necessary to process a call within the corresponding switching system. For example, the call processor 14 of each switching system performs call processing, service logic, signaling message processing, and address translation. A bus 16 within each of the switching systems 12.sub.1 and 12.sub.2 connects the call processor 14 to a signaling interface 18 that links its respective switching system to a signaling network 20, such as the AT&T Common Channel Signaling System 7, as is well known in the art. The signaling network 20 communicates out-of-band signaling information between the switching systems 12.sub.1 and 12.sub.2 in connection with call set-up and tear-down.

The switching system 12.sub.1 includes a first and second switching fabrics 22.sub.1 and 22.sub.2 that terminating transmission facilities 24.sub.1 and 24.sub.2, respectively, that may take the form of one or more trunks or channels. Each of the fabrics 22.sub.1 and 22.sub.2 also include devices (not shown) that provide multiple stages of space and time switching as is understood in the art. The fabrics 22.sub.1 and 22.sub.2 may take different forms for terminating different types of calls. For example, the fabric 22.sub.1 may comprise a circuit switch fabric whereas the fabric 22.sub.2 may comprise a packet-switch fabric.

The fabrics 22.sub.1 and 22.sub.2 are each controlled by fabric controllers 26.sub.1 and 26.sub.2, respectively, that are linked to the call processor 14 via the bus 16. Each of the fabric controllers 26.sub.1 and 26.sub.2 within the switching system 12.sub.1 comprises a processor or group of processors specifically designed for controlling a corresponding one of fabrics 22.sub.1 and 22.sub.2, respectively. In practice, each of the fabric controllers 26.sub.1 and 26.sub.2 facilitates the connection functions performed by its corresponding fabric, including functions such as: receiving dialed digits, determining whether a call can be established, setting up a channel, maintaining the channel, and taking down the channel.

Like the switching system 12.sub.1, the switching system 12.sub.2 includes at least one switching fabric 22.sub.3 for terminating transmission facilities 24.sub.3 and 24.sub.4, each taking the form of one or more trunks or channels. A fabric controller 26.sub.3, comprising a processor or a group of processors, controls the fabric 22.sub.3 to facilitate the connection functions performed by the fabric. The fabric controller 26.sub.3, is linked to the call processor 14 within the switching system 12.sub.2 via the bus 16.

In the past, the fabrics 22.sub.1 -22.sub.3, under the control of their fabric controllers 26.sub.1 -26.sub.3, respectively, performed call routing. In other words, the fabrics 22.sub.1 -22.sub.3 would select, assign and reserve trunks or channels based on various criterion to route calls from one switching system to another. The disadvantage associated with performing the call routing functions within each of the fabrics 22.sub.1 -22.sub.3 is that the fabrics are typically different. Thus, implementation of a particular routing techniques, say Class-of Service Routing, in a particular fabric is different because of the particular nature of that fabric. Thus, implementing new routing techniques tends to be complex and expensive because of the need to tailor the routing techniques for each different type of fabric. Furthermore, implementing routing functions in multiple fabrics is not cost effective.

In accordance with the invention, the routing function previously performed in each fabric is performed by a separate, fabric-independent routing processor 28 within each of the switching systems 12.sub.1 and 12.sub.2. The routing processor 28 in each switching system is linked by the bus 16 to the call processor 14. The routing processor 28 includes a dynamic routing data base 29 that tracks all dynamic data, including, for example calls-in-progress, traffic load, bandwidth reservation, trunk group load status as well as trunk busy/idle status. In response to commands from the call processor 14 in each switching system, the routing processor 28 systems performs call routing functions, including selecting a route by selecting, assigning and reserving the required trunk or channel. The routing processor 28 also allocates, and when necessary, reserves bandwidth among idle networks. The routing processor 28 actually selects the route for each call by specifying a channel to a neighboring switching system that carries the call. Further, the routing processor 28 has the capability to respond to queries from other switching systems regarding trunk group load status and traffic load to enable the processor to assist the routing processor of the other switching system to make routing decisions as described below with respect to FIG. 2. With the routing functions performed by the routing processor 28, the fabric controllers 26.sub.1 -26.sub.3 simply control their corresponding fabrics 22.sub.1 -22.sub.3, respectively, to perform cross-connect functions or other fabrics related hardware control functions, such as per-call-control execution of echo cancellation or other voice processing functions. Thus with fabric independent routing, most routing functionality and data reside within each routing processor 28 designated to do the routing processing function. Hence, the routing processor 28 performs all logical routing functions, while each of the fabric controllers 26.sub.1 and 26.sub.2 performs fabric-specific hardware related routing functions.

In one implementation, the routing processor 28 and each of the call processors 14--14 use the same hardware/software platform to simplify operation, administration, maintenance, and provisioning. A call is processed by one of many call processor 14--14. However, routing is performed in one centralized routing processor 28 (with a back up, not shown), where dynamic data is stored in the centralized database 29. The call processors 14--14 and the routing processor 28 have the same software, but a primary routing processor 28 and backup are designated from the pool of call processors 14--14. The backup routing processor becomes the primary routing processor when the primary routing processor fails, and any other call processor 14 can then be designated to perform the backup routing processor function, where that call processor is then initialized to be the new back-up routing processor.

In a distributed fabric independent routing implementation option, the routing processor 28 still maintains the centralized database 29, but communicates information from this database every 1-2 seconds to each call processor 14. In this option, trunk status and trunk hunt could be done in each of the fabric controllers 26.sub.1 and 26.sub.2, and the fabric controller would update the routing processor with each trunk busy/idle status change. Every 1-2 seconds the routing processor 28 updates each call processor 14 with the number of busy/idle trunks, and with all traffic related data, including calls-in-progress, blocking rates, number of blocked calls, completion rates, and other traffic related data needed for routing processing in the call processors. (With an ATM fabric controller, the total idle/busy bandwidth slots are communicated.) The routing processor 28 does the processing of all traffic data collection and summarization for external operations system use, such as Real-Time network surveillance.

Each call processor 14 performs normal routing processing using the 1-2 second old status/traffic data received from the RP 28. The call processor 14 specifies to one of the fabric controllers 26.sub.1 and 26.sub.2 on call setup: (a) trunk group choices, including the direct trunk sub-groups in the direct/engineered route, if it exists and is not in a reserved state in which the direct route is not allowed, and the via trunk sub-groups, (b) the trunk hunt method to be used, such as randomize/load balance, sequential, or other, and (c) per-call-control execution data, such as activate echo cancellation. The fabric controller responds to the call processor 14 with the trunk selected, or all trunks busy. The call processor 14 sets up the call with normal routing processing, or blocks the call if all trunks busy is received from the fabric controller. The call processor 14 notifies the routing processor 28 of every completed call, every disconnected call, every crankback event, every blocked call, and all traffic related events.

The advantages of a distributed fabric independent routing option are: (a) balancing of Real-Time work between the call processors 14--14, the routing processor 28, and the fabric controllers 26.sub.1 and 26.sub.2, (b) reducing call setup delay since the call processor 14 sets up a call directly to the fabric controller, and not through the routing processor 28, (c) making the architecture more robust, since in one embodiment, the call processors are independent of a dual routing processor failure by using a simple back up routing strategy, such as Success-To-the-Top (STT) routing.

Referring to FIG. 2, there is shown a call flow diagram illustrating the manner in which the routing processor 28 within the switching system 12.sub.1 routes calls. (Although not shown, the routing processor 28 within the switching system 12.sub.2 operates in substantially the same manner as the routing processor 28 within the switching system 12.sub.1.) Call routing commences upon receipt of an Initial Address Message (IAM) at the signaling interface 18 within the switching system 12.sub.1 that sets up a call. The IAM received by the signaling interface 18 is forwarded to the call processor 14, which, in response, commands the routing processor 28 to get a route for the call. The routing processor 28 selects a route by selecting the trunk or channel on which an outgoing leg of a call should be placed. For purposes of discussion, the selected route is assumed to encompass only the transmission facilities terminated by the fabric 22.sub.1 of FIG. 1 although the selected route could include one or more transmission facilities terminated by the fabric 22.sub.2 of FIG. 1. After selecting the route, the routing processor 28 advises the call processor 14, which, in turn, instructs the fabric controller 26.sub.1 controlling the fabric 22.sub.1 to reserve the required transmission facilities. (Note that if the route selected by the routing processor 28 had involved the transmission facilities terminated by the fabric 22.sub.2, then the call processor 14 would have commanded the fabric controller 26.sub.2 to reserve the appropriate connections.) After reserving the connections, the fabric controller 28 signals the call processor 14 within the switching system 12.sub.1 that this task has been completed. Upon receipt of the connection reserved signal, the call processor 14 within the switching system 12.sub.1 generates an IAM for transmission via the signaling interface 18 to the signaling network 20 for receipt by a downstream switching system to signal set-up of a call.

In some instances, the routing processor 28 within the switching system 12.sub.1 may wish to retrieve load state information from a far end switching system, e.g., switching system 12.sub.2, for the purpose of routing the next call. (Note that the routing processor 28.sub.1 could query the far end switch 12.sub.2 for the current call. However, doing so would possibly delay routing.) To determine the load state of the far-end switch 12.sub.1, the routing processor 28 within the switching system 12.sub.1 sends a Transactional Capabilities Application Part (TCAP) query to the signaling interface 18, In response, the signaling interface 18 within the switching system 12.sub.1 sends the TCAP inquiry across the signaling network 20 of FIG. 1 to the signaling interface 18 within the far-end switching system 12.sub.2. The signaling interface 18 within the switching 12.sub.2 passes the TCAP query to the routing processor 28 within that switching system. The routing processor 28 within the far end switching system 12.sub.2 consults its data base 29 to obtain the requested information and provides the requested information via a TCAP query response. The TCAP query response generated by the routing processing 28 within the switching system 12.sub.2 passes to the signaling interface 18 within that switching system for transmission via the signaling network 20 to the switching system 12.sub.1 whose routing processor 28 had requested the information. The routing processor 28 utilizes the TCAP query response from switching system 12.sub.2 to make subsequent routing decisions.

Thus far, what has been described is the manner of call set-up. Ultimately, however, one or both parties to the call will ultimately hang-up, necessitating tear-down of the connection that previously carried the call. Call tear-down commences upon receipt at the switching system 12.sub.1 of a Release message received by the signaling interface 18 from the signaling network 20. The signaling interface 18 passes the release message to the call processor 14, which, in response, commands the fabric controller 26.sub.1 to release connection. After releasing the connection, the fabric controller 26.sub.1 alerts the call processor 14 of the release. After being notified of the released connection, the call processor 14 of the switching system 12.sub.1 sends a release completed message to the signaling interface 18 for transmission via the signaling network 20 of FIG. 1. In the process of generating the release complete message, the call processor 14 also confirms to the routing processor 28 that the connection has been released, allowing the routing processor to update its data base 29 regarding calls in progress, idle link band width, as well as trunk busy/idle status.

As may be appreciated, migrating the routing functions to the routing processor 28 within each switching system eliminates the need to duplicate the routing technique in multiple fabric controllers and to tailor the routing technique to the particular fabric, thus reducing development costs. By migrating the routing functions to the routing processor 28, call routing becomes independent of each fabric. Moreover, migrating the routing functions to the routing processor 28 helps reduce the load on each call processor 14. Additionally, employing a separate intelligence, in the form of routing processor 28, to perform the routing functions allows the processor to be optimized for routing.

The fabric independent routing concept can evolve the routing processing implemented within the routing processor 28 to support both voice and data services in an integrated network, such that the services are offered on different fabrics, as illustrated in FIG. 3. As seen in FIG. 3 a single switching system 12', configured in the same manner as the Switching systems 12.sub.1 and 12.sub.2 of FIG. 1 may be associated a circuit switch fabric 22.sub.1 ' and an ATM fabric 12.sub.2 ' controlled by fabric controllers 26.sub.1 ' and 26.sub.2 ', respectively. Typically data services can be quite bursty in nature and are often implemented on a network with a packet based fabric, such as the ATM fabric 22.sub.2 ' and with virtual circuit routing for bandwidth allocation. Virtual circuit routing for constant bit rate (CBR) services, such as voice services, or near CBR services, such as compressed voice services, can use routing methods quite analogous to those used in circuit-switched networks. For example, the concept of a bandwidth slot, or segment of bandwidth, can be used in lieu of the time-division multiplex slot, or trunk, in the circuit-switched network. However, for very bursty data traffic, such as computer communications services, routing methods more specialized to such data traffic are employed.

As illustrated in FIG. 3, such data services routing methods can be implemented on the routing processor 28 for use with the data services in question, which are routed on the packet based fabric, (e.g., the ATM fabric 22.sub.2 '). In addition, bandwidth on the ATM fabric can be allocated between the CBR and near-CBR services, and the bursty data services, for assurance of meeting performance objectives for all service classes. For example, the assurance of cell dropping rate below a certain objective can be achieved by defining a boundary in the bandwidth allocated, as illustrated in FIG. 3, in which neither service class can use more than its total allocated bandwidth. In this way, for example, highly bursty data traffic can not cause performance degradation such as higher cell dropping rates (due to overflow of buffer queues) of the CBR traffic in the short, bursty data traffic intervals. For this purpose, the bandwidth allocation can be periodically adjusted, as shown, by load set period (LSP) to allow for the variability of the total traffic demand among the traffic classes.

By implementing fabric independent routing, routing processing is re-used for new fabric capacity, and is readily extended to accommodate new service types, such as bursty data services. Fabric independent routing achieves lower development cost by avoiding re-development of routing functions on new fabric controllers, as they are added, and the addition of new routing features is made on a single routing processor function versus multiple fabric controllers. Fabric independent routing allows routing processing to be implemented on processors with essentially unlimited Real-Time and memory resources by riding the processor technology curve, and achieves performance advantages such as reduced call set up delay and improved overall switch reliability.

It is to be understood that the above-described embodiments are merely illustrative of the principles of the invention. Various modifications and changes may be made thereto by those skilled in the art which will embody the principles of the invention and fall within the spirit and scope thereof.