Method and network for call processing

(74) Agent

Sprint Communications Co LP, 8140 Ward Parkway, Kansas City, MO 64114-0417, US Joseph Michael Christie, San Bruno, CA, US

Albert Daniel DuRee, Independence, MO, US

Michael Joseph Gardner, Overland Park, KS, US

William Lyle Wiley, Olathe, KS, US

Manu Chand Bahl, Hillsborough, CA, US

Daniel Charles Sbisa, Blue Springs, MO, US

Zacco Norway AS, PO Box 2003 Vika, 0125 OSLO

<td> (54)</td><td>Designation</td><td>Call handling and telecommunication networking methods</td>

<td> (56)</td><td>cited</td><td></td>

<td></td><td>publications</td><td>EP631 447 A2</td>

<td> (57)</td><td>Summary</td><td></td>

System for processing telecommunication signaling. Signaling for a call is received into a signaling processor (110). The signaling processor (110) processes the call and generates new signaling including the processing. The new signaling is transmitted to appropriate network elements (135).

The signaling processor (110) is not connected to a switching matrix and communicates only with the network elements (135) over the signaling links (140).

<img file="NO324343B1_D0001.tif" />

BACKGROUND OF THE INVENTION 1. Field of the Invention This invention relates to telecommunications and the management of telecommunications in the processing of signaling to generate new signaling for the network elements providing telecommunication services.

More particularly, the invention relates to a method of call processing, in which a telecommunications network comprises a network element receiving user communications from a user and a signaling processor receiving a call setup message from the user, the signaling processor being associated with the network element and the user, and the signaling processor being associated with the signaling processor. as stated in the preamble of the appended claim 1.

Furthermore, the invention relates to a telecommunications network comprising a network element configured to receive user communications from a user and a signaling processor configured to receive a call setup message from the user, wherein the signaling processor is associated with the network element and the user, and the signaling processor is in relation to the signaling processor. the network element, as defined in the preamble of the appended claim 11.

For the purpose of illustrating the prior art, reference is made to EP 631447 - A2 which discloses a method of call processing in a telecommunications network, wherein the network comprises a network element receiving user communication from a user and an external signaling processor linking to the network element and the user, the signaling processor receives a call connection message directly from the user and executes the call processing and delivers a new signaling message transmitted over the link to the network element for routing the network element to provide a telecommunication service which may be switching the user communication over a receiving network.

It is further mentioned that telecommunications networks use interchanges to process calls and set up connections. The exchanges must be able to communicate with each other in order to perform this function. The communications between the exchanges are known as signaling. A prominent example of signaling is the signaling system # 7 (SS7). It is important to note that signaling is different from the actual user traffic that is transported over the connections set up after dial-up. Signaling is the communication that takes place to set up and take down telephone connections.

A classic example of signaling is where a first dialer processes a dialed number and selects a second dialer to use for dialing. The first dial extends the dial-up connection to the second dial and signals the number dialed to it. This second exchange can repeat the process for a third exchange and the process will be repeated until the dialing connections are complete. To simplify this processing, the switch contains a central processing unit (CPU) and a signaling point. The CPU switch is connected to the switch matrix and controls the connections established with the matrix. The CPU switch processes the information, which can be a dialed number, to select a connection and directs a connected exchange matrix to set up the connection. The switch signaling point acts as the signaling interface of the CPU switcher by sending and receiving signaling and reshaping of call information between the signaling protocol and the switching CPU protocol.

Signaling has achieved additional features in the development of what is called an intelligent network. In the intelligent network, the exchanges are supported by external processors and databases. The exchangers process the signaling they receive to process calls. During this processing, the CPU may find that it needs support from external processing or data. To receive this support, the CPU switch and signaling point must produce a new signaling message to send to an external processor. The new signaling message is known as a request. The external processor will process the request and respond to the same exchange with a signal containing additional information to support the exchange.

A classic example of intelligent network operation is the 800 dial-up (also known as a free phone). For 800 dials, a switch will receive a dial-up setup message including the dialed number. ISS7, this is a origin address message (IAM). The exchange will process the IAM until it perceives that the dialed number had an area code of 800, and that the exchange would require support from an external database to obtain a standard telephone number it can use to route the call. This act of recognition is known as a trigger. This standard telephone number is known as a legacy old telephone service number (POTS). As such, the exchange will generate a signaling message and send to an external database. ISS7 is a Notice of Transaction Opportunities for Use (TCAP) and is commonly known as a Request. The external processor receiving the TCAP request is known as a service control point (SCP). SCP analyzes the request and will usually match the exchange with the correct POTS number. The exchange can then process the call in a normal way. Those skilled in the art are aware of many other special features of processing a call that can be realized with an SCP.

In this way, it is known in the art that an exchange who initially receives a message about the setup of a call should start processing the call. The switch can trigger while processing a call and invoke an external processor with a separate request message. After analysis, the external processor will respond to the same switch with its own message.

Currently, switches are devices that receive and process set-up signaling for a dial to rout the dials and invoke the intelligent network. As a result, regular networks are limited to what the exchange can perform in the form of a dial-up treatment. To add new features, the CPU switch must be reprogrammed with new dialing logic or an existing switch trigger must be reused. Both limit a network's ability to offer new services. Since the switchboard remains the main platform from which call processing is initialized and managed, the networks must wait until the switches have been developed with the necessary functionality before new services and collaboration can be deployed.

A current example of this problem is provided with asynchronous transfer mode (ATM) switches. Although ATM switches are currently functional in transporting broadband traffic, ATM switches capable of handling extensive dialing capacity and signaling are not available. Support systems for these bills of exchange, such as debit and trigger detection, have not gone very far in development. As a result, the networks have to wait until ATM switches have sufficient capacity before the functionality of broadband transport can be fully utilized. There is a need for systems that do not rely on the switches' ability to signal and process calls.

At least one system has proposed routing user service requests to a dial-up server external to the exchange. However, this system requires that the call processing be separate from the processing of the connection. This separation requires the deployment of an entirely new and owned signaling system. In this system, a dial-up server receives user signaling and selects services and route characteristics. A dedicated connection server selects the route and a dedicated channel server selects the special connections on the route. The servers communicate with a owned signaling protocol. This system has not yet progressed far enough to be realized. As such, the system could not be implemented as easily and smoothly as a system that integrates dialup processing with connection processing and uses standard signaling protocols.

The present invention therefore aims to solve some of the shortcomings associated with the prior art, and according to the invention, the method mentioned in the introduction is characterized by performing call processing in the signaling processor in response to the call setup message to generate an echo control message which directs an echo control unit to cancel echo from the user communications, and to generate a new signaling message as a new signaling message transmitting the echo control message from the signaling processor to the echo controller, and transmitting the new signaling message from the signaling processor to the network element.

Further characteristic features of the method are set forth in the appended subclaims 2-10.

Further, the invention aims to solve some of the aforementioned known shortcomings by providing a telecommunication network of the type mentioned in the introduction, which is characterized, according to the invention, in that the signaling processor is configured to perform call processing in response to the call setup message to generate an echo control message which directs an echo control unit to cancel echo from the user communications and to generate a new signaling message identifying a virtual connection for routing the user communications e to the echo controller and transmit the new signaling message to the network element.

Further embodiments of the telecommunications network are set forth in the appended subordinate claims 12-20.

The invention thus includes dial processing where a user transmits a signaling message about transmitting the setup of a dial to a communication network having at least one network element connected to a communication path. A signaling processor is also linked to the web element and the user. This involves receiving the signaling message about setting up the call to the signaling processor. The signaling processor only communicates with the network element over a signaling link and is not connected to an exchange matrix. The signaling processor performs all call processing in response to the signaling message to produce a new signaling message which orders the network elements to create a telecommunications service. The signaling processor sends the new signaling message to the network element associated with the communication path. The signaling message received by the signaling processor could be an output address message (IAM) for the signal system # 7 (SS7).

The processing of the call could include validation of the call, service identification, NOO processing of the call, processing of personal / terminal mobility for the call, processing of call with voice message, processing of call in a virtual private network, implementation of echo control, generation of billing information, choice of a virtual connection and processing of POTS calls. Signaling message cnc can be regular signaling. They may be from the same protocol or they may be from different signaling protocols such as SS7 Integrated Services User Part (ISUP) signaling and SS7 Broadband Integrated Services User Part (B-ISUP) message.

The invention further relates to signaling processing which includes a signaling interface for transmitting and receiving signaling messages over a signaling link and a dialing / connection processor coupled to the signaling interface. The call / connection processor is not connected to an exchange matrix and can make dial processing, generate a new signaling message based on the call processing and send the new signaling message through the signaling interface. The new signaling message commands a network element to set up a telecommunications service for the call. The network element is connected to a communication path for the call and did not produce the output signaling message received through the signaling interface. The dial-up / communication processor only communicates with the network element through the signaling interface. The dial-up / communication processor only communicates with the network element through the signaling interface.

One aspect of the invention involves the selective validation of dialers which involves accepting a call and receiving the caller's number and the caller's number. Before making the call valid, it is determined whether the call is of a type that requires validation, and if the call does not require validation, the number dialed is processed, but if validation is required, the call is transferred to a validation database with the caller's number before further processing of that number. that is beaten.

Another aspect relates to the selective validation of calls which involves accepting a call and receiving the caller's number and the dialed number for the call. It is then determined whether the dialed number is an 800 number and if the dialed number is an 800 number, it is transferred to an 800 number database with the dialed number before the dialed number is entered into a valid database, but if the dialed number is not an 800 number, it will be entered into a valid database of the caller's number before further processing of the dialed number.

The invention makes it possible to provide telecommunication services to users of the telecommunication network that is part of the invention, where use of ATM switches, ATM multiplexers, ATM connections, narrowband connections, signaling links and signal processors. The signal processors are external to the ATM switches and receive and process a signaling message from a user about a call. The signaling processors generate and send a new signaling message that directs an ATM switch to set up a telecommunications service to the user for the call.

These and further aspects of the invention will be better understood with reference to the following drawings in which:

Fig. 1 shows a block diagram of an embodiment of the invention.

FIG. 2 shows a logic diagram for an embodiment of the invention.

Fig. 3 shows a logic diagram for an embodiment of the invention.

Fig. 4 shows a logic diagram for an embodiment of the invention. Fig. 5 shows a logic diagram. for an embodiment of the invention. Fig. 6 shows a logic diagram for an embodiment of the invention. Fig. 7 shows a flow chart for an embodiment of the invention. Fig. 8 shows a flow chart for an embodiment of the invention. Fig. 9 shows a flow chart for an embodiment of the invention. Fig. 10 shows a block diagram of an embodiment of the invention.

The invention is to manage telecommunications that do not depend on alternating signals such as prior art systems. This is achieved by using a system which processes dialing signaling and does not need to be bound to an exchange and associated exchange matrix. Using the invention, the exchangers can be used to perform their toggle function and transport function regardless of their ability to handle other features. In addition, some embodiments of the invention may logically integrate dialing and processing of connections and may work together with conventional signaling systems.

In the figures, the connections that carry user information are shown as single lines and signaling links that carry signaling messages are shown in double lines. Fig. 1 shows a basic version of the unique invention. A signal processor 110 is shown connected to user 115 with link 120. The processor 110 is also connected to a switch 125 with a link 130 and to element 135 with a link 140. The user 115 is connected to the switch 125 over connection 145. The switch 125 is connected to the element 135 over the connection 150. Apart from the processor 110, these components are known from this range. The user 115 can be any device requesting a service that requires a communication path where a few examples are a telephone, a computer or a local exchange in a central carrier (LEC). The switch 125 may be any device that establishes communication paths in response to signaling where examples are a Northern Telecom DMS-250 or a Fore Systems ATM switch. The element 135 may be any device with which the dials are connected. A few examples would be a switch, cross-link, server, enhanced platform or even a destination phone or computer. The connections 145 and 150 can be any media that carries user information where a few examples are DS3 national networks, SONET / ATM virtual connections or wireless connections. Links 120,130 and 140 may be telecommunication signaling media where a few examples are a 56 kbit data line, a virtual channel carrying SS7 or a UDP / IP link. Those of skill in the art will appreciate that networks usually post many other exchanges, connections, links, and other network elements which, for the sake of overview, are not shown in Fig. 1. Among these other network elements may be SCP units, signal transmission points (STP), multiplexers and echosletters, but there are many others.

The processor 110 may be any processing platform designed to support the claims of the invention and will be described in detail below. In operation, user 115 will request a service that requires a communication path when signaling a network. These signals are directed to processor 110 over link 120. Those skilled in the art are aware that STP devices may be used for this purpose. In addition, in-band signals, such as those in a local loop, can pass through a switch before being separated out-of-band and routed to processor 110. Any technique for routing user signaling to processor 110 is contemplated by the invention. . This signaling is known as signaling for setting up a call, and for SS7 it is IAM.

It is important to note that signaling for setting up a call from user 115 is addressed to processor 110 and is not processed by switch 125 to recognize a trigger or establish a communication path. Processor 110 will not only receive requests made by switch 125 that appear in response to signaling setting up a call from user 115. It is also important to note that processor 110 does not accept connections 145 or 150 that direct actual user traffic. As such, processor 110 is linked to the switch only with a signaling link. It is not connected to an inverter matrix and may be external to the inverter. However, in reality, the signaling processor could physically be in a switch if it is not connected to the switch matrix and only communicates with the switch over a signaling link. Those of skill in the art will know how a switch CPU is connected to the switch matrix.

Processor 110 will process the call setup setup. For a typical dialing, this may include confirmation of the dialed number, rating of the caller, checking an echo bar, generating billing information, selecting dialing connections, and generating signals that include necessary information to complete the call. This signaling generated by processor 110 will be transmitted over link 130 to switch 125 to provide this service. This may include setting up communication paths over connections 145 and 150. If necessary, processor 110 could also generate and send the proper signaling to element 135 over link 140 or to user 115 over link 120. The signaling could be conventional signaling such as SS7.

Fig. 2 shows another embodiment of the invention, although the invention is not limited thereto. Narrow band switch 215 is shown connected to the ATM switch 225 at connection 205. The signaling processor 210 is shown linked to the narrow band switch 215 with the signaling link 220. The signaling processor 210 is also shown linked to an ATM switch 225 at the signaling link 230.

Those skilled in the art are well versed in the logical breakdown and functionality shown for the exchanges 215 and 225. Both exchanges 215 and 225 contain the exchange pattern associated with the connection 205. The exchange pattern and the connection 205 carry the user information for a call. Both the exchange pattern and the compound 205 are well known. A cooperating multiplexer will be used to convert traffic on the connection 205 between narrowband and broadband formats. The multiplexer is not shown for overview.

Signaling is required to control the alternation function. The signaling link 220 is associated with the message transmitting part (MTP) level 1. The signaling link is usually an SS7 link. MTP Level 1 defines the physical and electrical requirements of Link 220. MTP Level 2 sits at the top of Level 1 and maintains reliable transport across Link 220 by monitoring its status and performing troubleshooting. Together, the MTP levels 1-2 provide reliable transport over an individual link. A device would need MTP level 1-2 function for each link it uses. MTP level 3 sits at the top of level 2 and provides route control and management function for the entire signal system. MTP level 3 directs messages to the appropriate signaling link (in fact to MTP level 2 for this link). MTP level 3 directs messages to applications that use MTP levels to access the signaling system. MTP Level 3 also has a management function that monitors the status of the signaling system and can take the appropriate measures to restore service through the system. MTP levels 1-3 correspond to layers 1-3 of the Basic Reference Model (OSIBRF) for open systems with interconnection. Both MTP 1-3 and OSIBRF are well known in the art.

The switch 215 has an integrated digital service network with user part (ISUP) logic that supports basic dial processing. ISUP uses MTP to send messages over the signaling system. The information contained in ISUP messages was used by the telecommunications network to implement services and set up communication paths. A new example of ISUP information is the number dialed and the caller's number. ISUP uses many different message types to pass on this information, where a few examples are Exit Address Message (IAM) and Reply Message (ANM). ISUP is well known in the art.

The narrowband switch 215 has dialing process logic which processes the dialup information generated by ISUP to control the switching pattern and establish communication paths. A classic example of this would be the analysis of the number dialed to select a dialing route. Dial-up processors for narrowband switching are well known in the art.

The AT switch 225 has an ATM layer, signaling ATM adaptation layer (SAAL) and MTP level 3 logic that provides route control, management and transport across the signaling system. Signaling link 230, which is usually an ATM virtual connection transported with SONET or DS3 equipment, is connected to the ATM layer. The ATM layer is analogous to MTP level 1 and transmits and receives ATM cells containing signaling messages on the link specified in the cell header. SAAL collects and divides these cells, maintains individual virtual connections, performs troubleshooting, and is analogous to MTP level 2. MTP level 3 logic in ATM switch 225 performs the same basic functions as described above for MTP level 3, but the broadband version of MTP level 3 has been updated to support the needs of broadband systems. The ATM team, SAAL and the updated MTP level 3 are known in this area.

The ATM switch 225 has broadband coupon (B-ISUP) logic that supports basic processing of dialing in broadband environments to control the broadband exchange pattern. B-ISUP uses MTP level 3, SAAL and the ATM layer to send messages over the signaling system. The information contained in B-ISUP generated messages is used by the telecommunications network to set up communication paths. A few examples of BISUP information are the dialed number and the caller's number. B-ISUP uses many different types of messages to carry information, where a few examples are exit address message (IAM) and reply message (ANM). B-ISUP is known in this field.

The ATM switch 225 has dialing process logic and it processes the dialing information provided by B-ISUP to control the switching pattern and set up communication paths. An example of this would be the assignment of a virtual connection to a dialing based on a dialed number. The ATM dialer processor is well known in the art.

Processor 210 is connected to signaling links 220 and 230. Processor 210 has the MTP and ATM logic described above and which allows interfacing with components using either ISUP or B-ISUP. If ISUP or B-ISUP signaling is not required, the associated functions could be omitted.

Processor 210 has interface logic that transmits signaling between MTP level 3 and the dial-up / connection management (CCM). Processor 210 has CCM logic which is capable of processing the information in the signaling received from the interface. For a typical call, this may include confirmation of the dialed number, validation of the caller, control of an echo bar, generation of billing information, transfer of the dialed number, selection of a route for the call and generation of signaling to complete the call . The signaling generated by CCM will be transported back through the interface for transmission to the exchanges 215 or 225.

In one embodiment, narrowband switch 215 may be an LEC switch and ATM switch 225 may be an interchangeable carrier switch (IXC). IXC faces several problems when trying to interact with existing LEC narrowband exchanges with their own ATM exchanges. Current ATM switches do not support many of the features needed in an IXC in a robust way, such as route management and billing. In addition, exchanges 215 and 225 are not equipped to exchange signaling without modifying one of the exchanges with one ISUP to B-ISUP cooperating signaling unit. The present invention creates the cooperative function between the two exchanges and provides for the processing of dialing. This means that a much less complicated ATM exchange can be used.

In this embodiment, LEC switch 215 may request a connection through IXC. As a result, LEC switch 215 will signal IXC with an SS7IAM over signaling link 220. Processor 210 will accept the message through its MTP layers and interfaces.

The interface will deliver the signal to the CCM, and the CCM will process the signaling information in the IAM. This can confirm that the dialed number is legitimate and validates the caller by checking automatic number identification (ANI), generating geyser of debit register and controlling an echo barrier. CCM will also process the dialed number to select a dial-up connection. The parts of this information will be packaged in a suitable B-ISUP message and brought to the interface for subsequent transmission with MTP 3, SAAL and the ATM layer to the ATM switch 225 over signaling link 230. Based on the B-ISUP message, The ATM switch 225 connects to the dial. This will result in an extension of the communication path past the connection 205 based on the CCM signaling message. As such, a communication path will be set up through switch 215 and switch 225.

Figures 3-9 show an embodiment of the signaling processor which also applies to the dialer / connection controller. While this embodiment is preferred, the invention should not be limited to this embodiment.

Signaling processor 310 is shown. Reference numeral 315 indicates that signaling processor 310 may be equipped with an MTP level 1-2 signaling interface, an ATM layer / SAAL signaling interface, or both. Signaling processor 310 will be equipped with a MTP level 3 320 which operates as described above for ISUP and B-ISUP. For the signaling processor 310 there is also shown an Ethemet interface 335. The Ethemet interface 335 is a standard Ethernet bus that supports TCP / IP which transmits signaling messages from MTP level 3 to a platform handler 340. Together, the above components form a signaling interface for the signaling processor. Those skilled in the art will be aware of other interfaces and protocols which could form a signaling interface according to the invention.

The signaling interface will routinely route selected ISUP messages to platform handler 340. One technique to accomplish this would be to make signaling processor 310 a user part of STP. A point code converter could be placed between MTP level 2 and MTP level 3 in STP. The point code converter would transform the point code of the message destination to satisfy certain criteria of a point code identifying the signaling processor 310. The criteria would be loaded into a table and could include origin point code (OPC), destination point code (DPC), (circuit identification code) and various combinations of these criteria. The shuffling at this location 1 STP could be specific to the signal link used by the message, so that the conversion tables themselves take into account the link used by the message. After conversion, the MTP level 3 distribution function will forward signaling messages with the converted DPC to platform handler 340 over the Ethemet interface 335. A similar inverter function may be placed in front of the MTP level 3 routing function to convert point codes for messages sent by platform handler 340 out through STP.

Alternatively, an SS7 signaling interface to the platform manager can be built using commercially available SS7 software tools. An example of this tool would be the SS7 interface software provided by Trillium, Inc., USA Signaling messages with a destination code (DPC) that match the point code of the signal processor 310 would be routed to the signaling interface of the signaling processor 310 by STP. In addition, STP will be able to convert DPC for a signaling message to the point code of the signaling processor 310 as described above. However, since the signaling processor 310 is not a user part of the STP, the routing function of the MTP level 3 in the STP will route the signaling message to the signaling processor 310 over a signaling link. The signaling interface will receive the signaling message and transmit it to platform handler 340.

Although point code conversion facilitates transfer from existing systems to a system according to the invention, this is not essential. Any method for carrying out CCM signaling is sufficient.

A platform handler 340, a message handler 345, and a data handler 350 are also shown. The platform handler 340 is a system that accepts ISUP and B-ISUP messages from the Ethemet interface 335 and routes them to the message handler 345. The platform handler 340 is preferably designed to route messages to a particular message management processor based on the signaling link's choice code (SLS) in the message. The message handler 345 is a system that exchanges signaling with the platform handler 340 and controls the connection and switching requirements of the calls. It can select and implement services and initiate echo management. It also converts signaling between ISUP and B-ISUP. The data handler 350 is a set of logic connected to the message manager 345 which processes service requests and provides data to the message manager 345. The data manager 350 also manages the echo barriers and generates call lists for dialing.

In the description that follows, the term ISUP shall also include B-ISUP. In operation, ISUP messages that meet the proper criteria are routed by MTP and / or ATM interface 315, MTP level 3 320, and Ethemet interface 335 to platform handler 340. Platform handler 340 will route ISUP messages to message handler 345. Message handler 345 will process information comes. This may include validation, separation, and determination of whether additional data is required for processing a call. If so, the data handler 350 will be invoked and will provide the message handler 345 with relevant data so that the message handler 345 can complete the processing of the call. The message handler 345 would generate the appropriate ISUP message to implement the call and pass the signals to the platform handler 340 for later transmission to the assigned network elements.

The distribution of function units among message handler 345 and data handler 350 is shown. These functional units are well known in the art. The message handler 345 includes at least the call control (CCF) function and the service exchange function (SSF). CCF establishes and releases connections for the call, and SSF will detect triggers during the processing of a call by CCF and form an interface between CCF and the service control function (SCF). SCF identifies services and provides data for the service. In some embodiments, message handler 345 may include the SCF and the service data function (SDF). SDF provides service data in real time to SCF. Taken together, message manager 345 is able to at least control connections and perceive triggers. In some embodiments, message handler 345 may also identify services, obtain data for the services, and generate the signaling necessary to implement the services. The message manager 345 can provide signaling interaction (i.e. ISUP to BISUP), connection management, service selection and service implementation in a logically integrated package that interfaces with the network through standard devices.

The data handler 350 includes at least SCF and SDF. In some embodiments, both the message handler 345 and the data handler 350 include the SCF and SDF and the services are shared among the functional units. Two other functions are shown in the data manager, but these are not standardized functional units. Accounting generates a charge and echoes are handled by the echo barriers. As a rule, an echo barrier is switched off for a data call and reopened after the data call for use in subsequent voice calls, but other techniques may be used.

During operation, CCF would perform basic call processing until SSF perceived a trigger and called SCF. SCF would identify the service associated with the trigger. SCF would access data from SDF to implement the service. SCF would process data from SDF and pass data to CCF through SSF. CCF would then set up the connections by regular signaling to service switching points (SSPs). The service exchange points are connected to the communication path and make the connections. As a rule, an SSP is a bill of exchange. Also the echo barriers can be checked for dialing, and a charge would be made for this.

Those skilled in the art are aware of various machine components which can support the claims of the invention. For example, the Platform Manager, Message Manager and Data Manager may be located on a separate SPARC station 20.

Fig. 4 shows a possible version of the platform handler. Platform handler 410 includes STP handler 412, monitor 414, and CCM handler 416. Platform handler 410 sends and receives ISUP messages to / from a signaling interface. This STP routes ISUP messages with their own characteristics to an application that is at the top of the STP. The application could be CCM and the characteristics could be origin point code (OPC), destination code (DPC) for destination, signal selection (SLS), circuit identification code (CIC) and / or service information octet (SIO). The connection between the Platform Manager 410 and the STP could be an Ethernet LAN that carries ISUP messages encapsulated in TCPAP packets. The STP handler 412 would form the Ethemet-TCP / IP interface. The STP handler 412 has a process that will buffer and split the incoming packets into CCM and buffer and collect outgoing packets. The STP handler 412 could also check the messages for basic defects and errors. Any technique for transmitting signaling messages to the platform handler 410 is contemplated by the invention.

A Monitor 414 is responsible for managing and managing CCM activities. These include CCM start-up and shutdown, log-in and log-off for various CCM modules, handling of administrative messages (ie errors, notice, status, etc.) from the CCM modules and handling of messages from network operations such as requests , configuration instructions, and data updates. The connection to network operations is the man / machine interface that enables CCM to be controlled and monitored either by remote control or by a local operator. Monitor 414 has a process that retrieves configuration data from internal tables to initialize and configure CCM. The CCM modules also have internal tables used in conjunction with this procedure. The monitor 414 also communicates internally with the STP handler 412 and CCM handler 416.

CCM handler 416 exchanges ISUP information with STP handler 412. CCM handler 416 also exchanges ISUP messages and CCM monitoring messages with message manager. The connection between CCM handler 416 and the message manager may be an Ethernet LAN that transports these messages encapsulated in TCP / IP packets, but other methods are known. CCM handler 416 will form the Ethemet-TCP / IP interface. CCM handler 416 has a process for caching and splitting incoming packets from the message manager and caching and assembling outgoing packets to the message manager. CCM handler 416 will also check the messages for significant errors.

Internally, the platform handler 410 is provided with bidirectional channels that exchange information among the STP handler 412, the monitor 414 and the CCM handler 416. The channels between the STP handler 412, the CCM handler 415 and the monitor 412 provide monitoring information and administrative information. The channel between STP handler 412 and CCM handler 416 carries ISUP message information.

The Platform Manager 410 receives, splits, and buffers ISUP messages received from the network. It can perform basic checks of the messages before transferring them to the message manager. If more than one message handler is associated with the platform handler 410, the ISUP messages will be assigned to the message manager based on SLS for the particular ISUP message. CCM handler 416 receives route instructions from the message manager for routing certain ISUP messages to select the message manager processes. Platform Manager 410 also performs monitoring and forms a man / machine interface for CCM.

Fig. 5 shows a possible version of the message handler. The message handler 520 is shown and includes call center 521, originator 522, end controller 523, detection point controller 528, traction controller 524, auxiliary controller 525, exchange controller 526, and local resource 527. A primary function of message handler 520 is to modify ISUP messages.

Call Center 521 is the process that receives call setup messages from the platform manager. ISUP dial-up setup is initialized with IAM. When the call center 521 receives an IAM, an instance is created for an origin control process with data defined by the information in the IAM. The origin controller 522 represents any of the origin control processes occurring in the call center 521. The CCM handler is instructed from the new instance so that subsequent ISUP messages associated with this call can be transmitted directly to the appropriate instance of origin controller 522 with the platform handler.

The origin controller 522 sets up a memory block called a dial origin block. The dial control block creates a repository for information specific to a dial. For example, the call origin control block could identify the following: dialer block, origin manager, message manager, origin LEC, LEC national circuit (CIC), ATM virtual circuit, ATM virtual path, dialer number, dialed number, relocated dialed number, origin line information, ANI service class, selected route, number of the selected route, SLS, OPC, DPC, Service Indicator (SIO), echo blocking status, cause of release, dialing status and pointers to adjacent dialing control blocks. In addition, the control block would also contain the different times at which signaling messages are received, such as complete address message (ACM), response message (ANM), delayed message (SUS), resumed message (RES), and release message (REL), Professionals in the field will be aware of other related data that can be entered.

The originator performs call processing according to the Basic Call State Model (BCSM) recommended by the International Telecommunications Union (ITU), but with some exceptions. The origin controller 522 processes the IAM through each point of a call (PIC) until a detection point (DP) is encountered. When a detection point is encountered, a message is sent to the detection point controller 528 and processing is postponed at the origin controller 522 until the detection point controller 528 swayes. An example of a detection point of origin controller 522 would be to authorize an initial attempt.

The detection point controller 528 receives messages from the origin controller 522 when these are due to a detection point being encountered during the processing of a call. The detection point controller 528 will identify whether the detection point is amplified or not. An enhanced detection point has special criteria that can affect the processing of the call if they are satisfied. If the detection point is not amplified, the detection point controller 528 will send a continuation signal back to the origin controller 522. A continuation message instructs the origin controller 522 to continue processing the dial to the next detection point. If the detection point is reinforced, the detection point manager 528 will enter into operation to see if the detection point criteria are met. If the detection point controller 528 requires assistance in processing the enhanced detection point, it will send a message to the pull controller 524.

The traction controller 524 will accept messages from the detection point controller 528 and either forward to the auxiliary controller 525 or to the auxiliary controller 526. Specific feature messages will be routed to the auxiliary controller 525 which will process these features at the dial. These are typically non-IN features, such as echo control or POTS charging. Other feature messages will be routed to the switch controller 526. These are typically IN features. Examples of IN features are 800-digit displacement or a terminal mobility number displacement. The traction controller 524 will return information to the detection point controller 528 (then to the origin controller 522) when it is received back from the auxiliary controller 525 or the auxiliary controller 526.

Inverter 526 will determine whether the request will be handled by local resource 527 or by the data manager. The local resource 527 will be structured to provide data that is more efficiently stored by message manager 520. Examples of such data include: an automatic number identification (ANT) validity table that checks the caller's number, a dialed number transfer table to move POTS numbers into a routing instruction, or NOO transfer tables to move selected 800 numbers into routing instructions. Examples of a route instruction provided by the tables would be a switching / national network connection or a virtual connection. An example of data in the data manager would be virtual private network (VPN) routing tables or complex 800 routing schedules.

As a rule, origin controller 522 will work through the relevant points in a call to a point indicating that the setup is authorized. At this point, origin controller 522 will instruct a call center 521 to create a termination controller instance. The termination controller 523 represents any of these termination controllers. The origin controller 522 will transmit IAM information to the terminator controller 523. The terminator 523 sets up a memory block called a terminated dial control block. The dial control block forms a repository for information that is specific to a dial and has the same structure as the dial origin dial.

The Terminator 523 also works in accordance with the BCSM for ITU, but also with some exceptions. The exit controller 523 continues processing for the call through its own points in the call until detection points are encountered. When a detection point is encountered, a message is sent to the detection point controller 528 and processing is delayed by the terminating controller 523 until the detection point controller 528 responds. An example of the detection point of the termination controller 522 would be to authorize the termination which would authorize the caller setup of the originator 522. Messages from the terminator controller 523 to the detection point manager 528 are handled as described above for messages from the originator controller 522. When processing with the terminator controller 523 is completed, it generates an IAM to be transmitted through the platform handler 410 to the appropriate network elements.

The message manager 520 communicates with the data manager using a data transfer protocol. Examples include UDP / IP, or Intelligent Network Applications Protocol (INAP) contained in the Transaction Capabilities Application Part (TCAP) component layer.

Fig. 6 shows a possible version of the data handler. The data handler 630 includes service management center 631, service selection 632, service logic center 633, migration process 634, service data center 635, service data manager 635, echo control 637, and bookkeeping 638. The data handler 630 receives messages with service requests from the message manager. These messages result from a triggering of the message handler from an enhanced detection point to invoke the data handler 630. The messages are also the result of moves implemented by the help manager. The Service Management Center 631, the Service Logic Center 633 and the Service Data Center 635 are static processes created at startup. The Service Management Center 631 creates service selection administrators on a dial-by-dial basis. The Service Management Center 631 prompts the bill manager to issue subsequent service request messages for this call to the appropriate service selection manager. The service selection manager 632 represents any of the service selection managers created by the service management center 631.

The service selection manager 632 performs the service portion of the call processing. The Service Selection Manager 632 identifies the various services associated with each message and implements the service with messages to the Service Logic Center 633. The Service Logic Center 633 receives messages from the Service Selection 632 and creates instances for migration processes necessary for the identified services. Examples of migration processes are N00, messaging, personal / terminal mobility and virtual private networks (VPNs). The migration processes are service logic programs that implement the necessary services for a call. The migration process 634 represents any of the migration processes created by the service logic center 633. The migration process 634 gains access to network resources and the data needed to implement the service. This will involve the execution of service-independent blocks (SIB). A SIB is a set of functions. An example of a function would be to extract the dialed number from a signaling message. The SIBs are combined to build a service. An example of a SIB is the transfer of a dialed number.

Those skilled in the art are familiar with the above services, although they have never been implemented with a system of the present invention. NOO services are services such as 800, 900 or 500 dialing where the dialed number is used to access call processing and billing logic established for the subscriber of the service. Sending messages involves linking the caller to a voice message service. For example, receiving a release message (REL) due to the busy line could be a trigger recognized by the message handler. In response, the data handler will create an instance for the message pull process and decide whether a call placed on a particular dialed number would require the voice message platform. In this case, CCM will instruct SSP to connect the caller to the voice message platform. Personal / terminal mobility means that the number dialed has mobility that requires a database lookup to determine the number in question. The database is updated when the called party changes their whereabouts. VPN is a private dial-up plan. It is used for calls from specially dedicated lines, from special dialing numbers (ANI) or to special dialing numbers. Calls are routed as specified for the particular plan.

When executing the SIB to set up the service, the draw process 634 will invoke the service data center 635 to create an instance for the service data controller 636. The service data manager

636 accesses the web databases that provide the data needed for the service. Access could be simplified with TCAP messages to an SCP. The service data controller 636 represents any of the service managers formed by the service data center 635. Once the data is received, it is transferred back down to the migration process io 634 for further service implementation. When the pull processes terminate a call, the service information is returned to the message manager and finally to the origin or call end manager.

After a call release message, a debit request will be transmitted ice to bookkeeping 638. Bookkeeping 638 will use the caller's control block to set up a charge. The call control block will contain information from the ISUP messages from the call and from the CCM processing. From the address complete message (ACM), the dial control block will include the route control label, CIC, message type, and cause indicators. From the response message (ANM), the call control20 block will include the route control label, CIC, message type and reverse call indicators. From the original address message (IAM), the dial control block will include the route control label, CIC, message type, forwarded dialing indicators, user service information, dialed party number, dialing party number, carrier identification, carrier selection information, billing dialing number, generic address number, generic address number, number. From the release message is (REL), the dial control block will include the route control label, CIC, message type, and cause indicators. From the delay message (SUS) or the continuation message (PAM), the dial control block will include the route control label, CIC and message type. Those skilled in the art will know of other relevant information for debiting and will be aware that some of this information may be omitted.

For POTS calls, the charge request will come from the origin and termination boards through the auxiliary controller. For IN calls, the request will come from service choice 632. Bookkeeping 638 will set up a charge from the dial 35 control boards. The charge will be transferred to a billing system over a billing interface. An example of an interface of this type is the LE.EE 802.3 FTAM protocol.

At some point during a call setup, the origin manager, termination manager, or even the detection point process will check the user service information data and the origin line information to assess the need for echo control. If the call is a data call, a message is sent to the data handler 630. More specifically, the message is routed through the auxiliary controller of the echo control controller 637 in the data handler 630. Based on the CIC, the echo controller 637 can choose which echo barrier and DSO circuit need to be switched off. A message will be generated for this purpose and sent over a standard data link to the relevant echo or echo control system. As soon as a release message (REL) is received for the circuit, the echo barrier is opened again. For a typical call, this procedure will take place twice. Once for an echo barrier on the access side and again for an echo barrier on the exit side. The CCM that handles the IAM for a particular dialing segment will control the particular echo barriers for the segment.

Before describing the IAM treatment, a brief description of the SS7 message should be given. SS7 message is well known in the art. SS7 ISUP messages contain many fields of information. Each message will have a route control label containing a Destination Point Code (DPC), a Point of Origin Code (OPC), and a Signal Selection 20 (SLS) which is mainly used to route the message. Each message contains a circuit identification code (CIC) that identifies the circuit message to which it is associated. Each message contains the message type used to understand the message. ISUP messages also contain imposed parts that are filled with fixed length data and variable length data, in addition to a part that is available for optional data. These parts vary from message type to message type depending on the information needed.

The original address message (IAM) initializes the call and contains information on setting it up, such as the dialed number. The IAM is transmitted in the dialing instructions for setting up the dial. During this process, TCAP messages can be sent to access remote data and processing. When

The IAM has reached the final network element, an address complete message (ACM) is sent back to indicate that the necessary information is available and that the called party can be notified. If the called party answers, a reply message (ANM) is sent back indicating that the call / connection will be used. If the 35 calling party hangs up, a release message (REL) is sent to indicate that the connection will not be used and can be taken down. If the called party hangs up, a suspended message (SUS) is sent, and if the called party reconnects, a restore (RES) message will keep the line open, but if no recovery occurs, a release message (REL ) be sent. When the connections are free, complete message release (RLC) will be sent to indicate that the connections can be reused for another call. Professionals in the field will be aware of other ISUP messages, but these are the primary ones to consider. As seen, IAM is the message that sets up the call.

In the preferred embodiment, the dialing treatment differs from the basic model recommended by IHJ, although the model could be followed closely in other designs. Figures 7-10 show the preferred processing of the dial. Referring first to Fig. 7. When the IAM for a call is received at 705, the call center creates an instance for a origin controller at 710.

The origin manager begins processing the call by sending an authorization message to the detection point manager. The Detection Point Manager checks the IAM information, including the dialed number, CIC and origin line information to perform service discrimination at 715. This is done to determine if the service requested is validating at 720. Ordinary dialing systems and BCSM from ITU validate the call before service discrimination can be made. It is of substantial advantage to the prior art that the preferred embodiment deviates from known methods of processing a call by looking at the IAM information prior to validation to determine if validation is required at all. For example, the calling party may not pay the bill for the call. The called party pays the bill on 800 calls and validation may be unnecessary. If no validity is required at 720, the processing of the call proceeds directly to B. It is advantageous that this avoids unnecessary lookup in the validity tables for a significant percentage of the calls.

If validity is required at 720, a validity table is checked at 725. The validity check is to see if a call should be allowed and focuses on potential call charge issues. For example, calls from ANI people who are saddled with the payment create problems for charging and may not be valid. Validity will result in sending messages from the detection point manager through the draw manager and the toggle manager to the local resource to access the tables. The tables can list authorized ANI, unauthorized ANI, or both. If the call is not authorized at 730, processing (i.e. routing to an operator or message) is given to the call at 735.

If the call is authorized at 730, the services identified at 75 are checked at 740 to determine if the call can be routed. This will usually take place for POTS calls. If no additional services are required at 740, the dialed number is relocated in a route instruction at 745. The route instruction could be a particularly virtual connection in the network. The treatment then proceeds to A. If additional services are needed at 740, treatment continues to B.

Fig. 8 shows treatment A after a route has been selected. An exit controller is set up at 805. The exit manager is responsible for processing in accordance with the closing BCSM from TTU. However, in some embodiments, the treatment may exhibit some deviation. For example, detection points such as option and call validation can be omitted.

The ability of the carrier is analyzed at 810 to determine if the call is a data call at 815. This analysis could take place anywhere in the call processing (ie, at the origin manager after the route is selected). If a data call is found at 815, an echo control message is sent to the data handler at 820. The cut-out message is created at 825 and sent at 830. Echosphere instructions identify the route instruction selected for the call. The message could be sent to the ecosystem via a regular CCM data link to the ecosystem.

If the call is not a data call at 815 or after the echo cancellation at 830, an IAM message is generated at 835. The new IAM includes current information for processing the call such as the selected route. The new IAM is sent to the Platform Manager at 840. As a rule, the IAM will place the route instruction in the dialed number field. This means that the digits do not have to represent the actual dialed number, but will contain other route control information that can be recognized by the network elements. The grid elements would need to be able to process the routing instruction. The dialed number can be placed in another field in IAM.

Fig. 9 addresses the processing at B. At this point, a number of things are known about the dialing in terms of authorization and service requirements. The dialing information is then analyzed at 905 as it is required to introduce dialing services. If there is no need for the data manager at 910, the service is deployed and the route selected at 915. This can occur if a service can be implemented directly by the origin manager or using the local resource. For example, special 800 transfers or service profiles for dialed numbers (ie forwarding a call) can be stored in the local resource. In this case, the route selection would be performed by the local resource after the information has been analyzed to identify the correct entry to a database in the local resource. When using the local resource, the message must be routed from the detection point processor through the traction controller and the local resource switch controller.

If the data handler is needed for dialing at 910, a message is sent to the data handler at 920. The messages usually flow from the draw point processor to the trace controller and the data handler toggle controller. Upon receipt of the message by the data handler, the service control center creates an instance for the service selection process at 925. The service selection process analyzes the message from the detection point processor and selects the call pull processes at 930. For example, a call can be set up from a caller on a virtual private network (VPN) to a PCS number. In this case, both a VPN migration process and a PCS migration process will be initiated.

Each migration process will determine if data was needed at 940. For example, a migration process for personal mobility will need access to a database to locate the caller's current telephone number. If data is needed at 940, the service data center will create a service data manager at 945. The data manager controls the data session and has access to the appropriate database at 950. After data is collected (or no one is needed), the service is implemented by the pull process at 955. For some moves, ie 800 service, this may include route selection. The result of the analysis process is traced back to the collection originator. If the migration process does not offer the route, the origin manager must select the route through the local resource or through another migration process.

The IAM itself contains many fields of information. The following table describes the elements for an IAM in terms of the information content and processing of the call.

Table 1 - Description of the exit address message

<td colspan="2">ROUTE LABEL</td>

<td>Parameter Field Name</td><td>Description</td>

<td>service Indicator</td><td>Set on 0101-ISDN user part</td>

<td>Priority</td><td>0 or 1 based on destination</td>

<td>Web ID</td><td>10 for the national network or set based on the international national connection group</td>

<td>Determination Point Code</td><td>Destination of IAM</td>

<td>Originating Point Code</td><td>Origin of IAM</td>

<td>Signal Lenk Code</td><td>Link used for messages (same for all messages in the call)</td>

<td>Circuit ID code</td><td>Dialing circuit between OPC and DPCilAM</td>

<td>Message type</td><td>0000 or 0001 for IAM</td>

<td colspan="2">THE NATURE OF CONNECTION INDICATORS</td>

<td>Satellite Indicator</td><td>Increment for each satellite used</td>

<td>Continuity check indicator</td><td>00 - no control 01 - control and start COT timer 10 - start timer for COT message</td>

<td>Echo suppression indicator</td><td>Indicates whether echo management is already implemented or set if echo management is implemented</td>

<td colspan="2">INDICATORS FOR DRIVING UP</td>

<td>National / international dialing indicator</td><td>0 for national 1 for international</td>

<td>End to end method indicator</td><td>Please provide any information</td>

<td>Collaborating indicator</td><td>Please provide any information</td>

<td>IAM segmentation indicator</td><td>0 for POTS</td>

<td>ISDN User Part Indicator</td><td>Please provide any information</td>

<td>ISDN benefit indicator</td><td>Provide any information and go back to 00</td>

<td>ISDN access indicator</td><td>Please provide any information</td>

<td>SCCP method indicator</td><td> 00</td>

<td colspan="2">CALLING PARTY CATEGORY</td>

<td>Calling party category</td><td>00000000 for unknown 00001010 for regular dialer 00001101 for test calling</td>

<td colspan="2">USER SERVICE INFORMATION</td>

<td>Information transfer capacity</td><td>Provide any information unless the destination requires special settings, but always provide ISDN unlimited digital information</td>

<td>Code Standard</td><td> 00</td>

<td>extension</td><td> 1</td>

<td>Transfer rate for information</td><td>Provide any information (will be 10,000 for POTS)</td>

<td>Transfer Mode</td><td>Set to 00 for 64 kbit / sec</td>

<td>extension</td><td> 1</td>

<td>User ID for layer protocol</td><td>Set based on pace adjustment, usually 0100010 for user information layer 1</td>

<td>extension</td><td>1 for normal calls 0 for clock adjustment</td>

<td>Takt</td><td>Nothing for user information layer 1, but 0111 for other beat customization</td>

<td>extension</td><td> 1</td>

<td colspan="2">CALLED PART NUMBER</td>

<td>Nature by address indicator</td><td>Identifies the type of call: 0000001 - original NPA or 950 dial 0000011 - 1 + dial 0000100 - direct international call 1110001 - operator call 1110010 - back to operator 1110011 - International Operator Dialing 1110100 - long distance operator dialing 1110101 - cut through dial 1110110 - 950, hotel / motel or dial-up with different access 1110111 - sample call</td>

<td>UlikAik</td><td>Number of digits in a dialed number</td>

<td>Numbering plan</td><td>000 - normal 001 -for ISDN 101 - private</td>

<td>digit Field</td><td>Dialing party number</td>

<td colspan="2">ACCESS TRANSPORT</td>

<td>Access transport items</td><td>Please provide any information</td>

<td colspan="2">CALLING PARTS NUMBER</td>

<td>Nature of address indicator</td><td>Specifies type of caller address, unique numbers can be used for billing, but billing numbers are used for numbers that are not unique: 0000000 - unknown 0000001 - unique dialer number 0000011 - unique national number 0000100 - unique international number 1110001 - non- dialer unique number 1110011 - non-unique national number 1110100 ~ non-unique international number 1110111 - sample dial</td>

<td>UlikAik</td><td>Number of digits in the dialing number</td>

<td>Excretion</td><td>Not used</td>

<td>Presentation allowed / limited</td><td>Provide any information for POTS but limit for N00 calls that are not allowed</td>

<td>Numbering plan</td><td>000 - normal 001 -ISDN 101 - private</td>

<td>digit Field</td><td>Dialing party number</td>

<td colspan="2">CARRIER IDENTIFICATION</td>

<td>Identification plan for the web</td><td>The number of digits in the identification code of the carrier it is requested</td>

<td>Type of identification for the web</td><td>Identifies the network dialing plan - 010 for PECS dialing from LEC</td>

<td>Digit one</td><td>First digit of the carrier identification code</td>

<td>Number two</td><td>Other digits in the carrier identification code</td>

<td>Number three</td><td>Third digit of the carrier identification code</td>

<td>Number four or zero</td><td>Fourth digits of the carrier identification code (if there are four digits)</td>

<td colspan="2">CARRIER SELECTION INFORMATION</td>

<td>Carrying Options Indicator</td><td>Indicates whether the carrier identification code was pre-subscribed or inserted</td>

<td>DEBITERINl</td><td>SSNUMMER</td>

<td>Nature of address indicator</td><td>This information can be used for debiting. 00000001 - dialer number 00000010 - no ANI, route to operator 00000011 - dialer national number 00000101 - route if 800, or route to operator 0000110 - no ANI 0000111 - route if 800 or route to operator</td>

<td>Odd / Even</td><td>Number of digits in the calling number</td>

<td>Numbering plan</td><td>Please provide any information</td>

<td>digit Field</td><td>Dialing party number</td>

<td colspan="2">GENERIC ADDRESS</td>

<td>Nature of address indicator</td><td>Please provide any information</td>

<td>Odd / Even</td><td>Please provide any information</td>

<td>Excretion</td><td>Please provide any information</td>

<td>Presentation allowed / limited</td><td>Please provide any information</td>

<td>Numbering plan</td><td>Please provide any information</td>

<td>digit Field</td><td>Please provide any information</td>

<td colspan="2">ORIGINAL INFORMATION</td>

<td>Origin line information</td><td>Identifies special types of calls, such as: 00000000 - normal dialing 00000111 - dialing from a restricted phone 00111111 - dialing from a moving cell phone</td>

<td>ORIGINAL OP</td><td>CALL NUMBER</td>

<td>Nature of address indicator</td><td>Please provide any information</td>

<td>Odd / Even</td><td>Please provide any information</td>

<td>Excretion</td><td>Please provide any information</td>

<td>Presentation allowed / limited</td><td>Please provide any information</td>

<td>Nununerplan</td><td>Please provide any information</td>

<td>digit Field</td><td>Please provide any information</td>

<td colspan="2">NUMBER FORWARDING</td>

<td>Nature of address indicator</td><td>Please provide any information</td>

<td>Odd / Even</td><td>Please provide any information</td>

<td>Excretion</td><td>Please provide any information</td>

<td>Presentation of allowed / limited</td><td>Please provide any information</td>

<td>Nununerplan</td><td>Please provide any information</td>

<td>digit Field</td><td>Please provide any information</td>

<td colspan="2">DIRECTION INFORMATION</td>

<td>Omledningsindikator</td><td>Please provide any information</td>

<td>Original reason for diversion</td><td>Please provide any information</td>

<td>Omledningsteller</td><td>Please provide any information</td>

<td>Reason for diversion</td><td>Please provide any information</td>

<td colspan="2">SERVICE CODE</td>

<td>service Code</td><td>Please provide any information</td>

<td colspan="2">SELECTION OF TRANSFER NETWORKS</td>

<td>Online Identification Plan</td><td>Identifies the number of digits in the carrier identification code (3 or 4)</td>

<td>Type of web identification</td><td>Type of network identification for transmission network parameter</td>

<td>Digits © 1,2,3,4</td><td>Carrier Identification Code for International Transfer Carrier</td>

<td>circuit Code</td><td>Specifies how dialing was dialed: 0001 - international dialing, no operator requested 0010 - international call, operator requested</td>

<td colspan="2">ESCAPADE TELLER</td>

<td>Jumping Teller</td><td>Limits the number of times an IAM can transmit through a signal point. If the count reaches the limit, the call is canceled.</td>

The different fields in the message contain the relevant information needed to start the call processing. IAM messages generated by CCM could contain route instructions. These could be placed in the digit field of the number of the called party. The number of the called party could be redirected to another field.

The SSP units could then receive IAM and route control based on the route instruction in the digit field. For example, the information could identify a route code, telephone number, exchange, national network, platform or network. A network element receiving such an IAM would recognize the route instructions, such as a route code, and perform the corresponding telecommunications service.

Something will now be described about the subsequent processing of the ISUP message.

The treatment of IAM is discussed above. Those skilled in the art will appreciate how SS7 messages can be included in the processing of the invention. For example, the time when a complete address message (ACM) is received is recorded in the dialing control block for charging and maintenance. Triggers can also be based on receiving subsequent messages, such as ACM. The response message (ANM) process is basically the same.

Cross-cutting is the time when users are able to pass information along the dial-up connection from end to end. Messages from CCM to the correct network element are needed to enable call-through. As a rule, connections include both a transmitter path from the dialer and a receiver path to the dialer, and intersection is possible on the receiver path after ACM is received and on the transmit path after ANM is received.

After receiving a release (REL) message, CCM will write a time for the call control block message and search for triggers upon release (such as new call origin). In addition, any blocked echo equalizer will be reopened and the dial control block will be used to set up a charge registration. Upon receipt of a Release Full Message (RLC), CCM will send messages that reduce the dial path. This will clarify the process specific to the dialing and the dialing connections can be reused for subsequent dialing.

In addition, delayed messages (SUS) and continuation messages (PAM) can be processed by CCM. A delayed message (SUS) indicates that the called party has disconnected and a REL will follow if the called party does not restore the connection within a specified time. A PAM is simply a message between the signaling points and can contain different information and is used for several purposes.

From the above description, it will be seen that the invention can receive and process a signaling to select dialing connections. The invention is also capable of providing services during the processing of the call. Fig. 10 shows a particular embodiment of the invention connected to a network, but the invention can also be used for other scenarios.

Nets 1001,1002 and 1003 are shown. The network 1001 is formed by a narrowband exchange 1005 and signal transfer point (STP) 1010. The narrowband exchange is connected to the network 1002 with the connection 1015. The narrowband exchange is linked to STP 1010 with link 1020 and STP 1010 is linked to the network 1002 with link 1025. The connection 1015 leads to the user got. Links 1020 and 1025 carry signaling messages. The narrowband exchanges, STPs, connections and signal chains can take many different forms and are well known in the art. The network 1003 is similarly located with narrowband switch 1030, STP 1035, connection 1040, link 1045 and link 1050.

The network 1002 is shown with ATM switch 1055, ATM switch 1060, muks 1065, muks 1070, echo control 1068 and echo control 1078. muks 1065 is connected to echo control 1068.

Muks 1075 is connected to echo control 1078. Echo control 1068 is connected to narrow. band exchange 1005 with connection 1015. Muks 1065 is connected to ATM switch 1055 with connection 1075. ATM switch 1055 is connected to ATM switch 1060 with connection 1080. ATM switch 1060 is connected to muks 1070 with connection 1085.

Echo control 1078 is connected to narrowband switch 1030 with connection 1040. Also STP 1090 and STP 1095 are shown. STP 1090 is linked to STP 1010 over link 1025. STP 1090 is linked to ATM switch 1055 with link 1105. STP 1090 is linked to STP 1095 with link 1100. STP 1095 is linked to ATM switch 1060 with link 1110. STP 1095 is linked to STP 1035 with link 1050. All of these components are well known in the art.

The network 1002 also includes CCM 1115 and CCM 1120. CCM 1115 is linked to STP 1090 with link 1125 and to echo control 1068 with link 1128. CCM 1120 is linked to STP 1095 with link 1130 and to echo control 1078 with link 1138. The CCMs and Affiliate links are designed to act as described above with respect to the present invention. During operation, a call will be made as follows.

Network 1001 will send a call to network 1002. This means that exchange 1005 will use connection 1015 as connection to network 1002. A signaling message will also be sent over link 1020 through STP 1010 and over link 1025 to network 1002. Network 1002 will receive the signaling message at STP 1090. The signaling message could be an SS7

ISUP message, and especially an IAM. STP 1090 would route SS7 ISUP messages from switch 1005 to CCM 1115. It may be that the message was actually sent to a component other than CCM 1115, but was routed to CCM 1115 by network 1002. CCM 1115 would process the IAM. Processing could include validation, call information analysis and route selection as described above. In turn, this may include POTS calls or calls that require additional services such as N00, VPN, messaging or personal / terminal mobility. In this embodiment, CCM 1115 could select connection 1080 as route instruction for ATM switch 1055. An SS7 B-ISUP IAM would be formulated at CCM 1115 and sent to ATM switch 1055 over link 1125 through STP 1090 and over link 1105. ATM switch 1055 would accept the route instruction and select the specific VPI / VCI on connection 1080 and generate a B-ISUP IAM that reflects the selected VPI / VCI. In addition, the route instruction from CCM 1115 could have identified the real CPI and left the VCI selection to ATM switch 1055.

This IAM from ATM switch 1055 will be routed over link 1105 through STP 1090 and over link 1100 to STP 1095. STP 1095 will route this IAM over link 1130 to CCM 1120. CCM 1120 will process the B-ISUP IAM and select network 1003, and in particular connection 1085 and / or exchange 1030 as route instruction for exchange 1060. A B-ISUP IAM will be formulated by CCM 1120 and sent to exchange 1060 over link 1130 through STP 1095 and over link 1110. ATM switch 1060 will select the appropriate VPI / VCI (or optionally only VCI) on connection 1085 and produce a B-ISUP message reflecting the selection. This B-ISUP message will be routed over link 1110 through STP 1095 and over link 1130 to CCM 1120. CCM 1120 will process B-ISUP IAM to create an ISUP IAM for narrowband exchange 1030. ISUP IAM will be sent to exchange 1030 over link 1130, through STP 1095, over link 1050, through STP 1035 and over link 1045. Multiplexes 1065 and 1070 convert traffic between the narrow band format and the ATM format. CCM follows these compounds through the multiplexes so that it can smooth out the narrowband and ATM connections on either side of a given multiplexer.

CCM 1115 will check the IAM to determine if the call is a data call. In this case, the echo equalizer must be blocked on the selected connection. This will be achieved with a message from CCM 1115 to echo control 1068 over link 1128. The same procedure will take place between CCM 1120 and echo control 1078 over link 1138.

The narrowband exchange 1030 will usually generate an address complete message (ACM) to indicate that the called party has become aware of a reply message (ANM) to indicate that the called party has responded. These messages are routed back to the web

1002 and to CCM 1120. CCM 1120 and CCM 1115 instruct exchanges 1055 and 1060 to allow intersection on the selected connections and will signal network 1001 regarding the call status. When a party terminates the call, deferred (SUS), release (REL) and release complete (RLC) messages are transmitted by networks 1001 and 1003 as may be necessary to cancel the call. CCM 1115 and CCM 1120 will process the messages and instruct Exchange 1055 and Exchange 1060 to use these VPl / VCrer for other calls. At this point, each CCM will generate dialing information for the call.

The invention offers many advantages over prior art systems. The invention is not connected to an exchange matrix and thus does not depend on the possibilities that are bound to an exchange by the exchange supplier. The invention does not really accept user traffic and it is not necessary that it has transport options. The invention, however, accepts the signaling that a switch will receive, processes the signaling and provides a switch with a new signal which includes the processing. The processing can be route management, billing and special services so that the exchange does not have these options. The processing can also coordinate different types of signaling so that each switch receives signaling in its own format.

Current signaling processors do not offer these benefits. SCPs process TCAP message requests and do not process call setup messages sent from a user. SCPs process requests generated by one bill and correspond to the same bill. SCPs must be called by a bill of exchange and respond to that bill.

Signaling points and their associated switch CPUs are bound to the switch and the switch CPU is connected to a switch matrix. These additional features of this system increase costs and reduce flexibility.

Another proposed system for processing signaling is logically divided by dialing, service, connection and channel. As such, it must be based on a owned signaling protocol to communicate among the logically separate components. This system does not have a single logical component that processes signaling and generates signaling for a network element connected to the communication path.

Those skilled in the art will be aware of variants that will satisfy the invention.

As such, the invention should not be limited only to the embodiments discussed above. The invention is as set out in the following claims.