CA2231230C - System for managing telecommunications - Google Patents
System for managing telecommunications Download PDFInfo
- Publication number
- CA2231230C CA2231230C CA002231230A CA2231230A CA2231230C CA 2231230 C CA2231230 C CA 2231230C CA 002231230 A CA002231230 A CA 002231230A CA 2231230 A CA2231230 A CA 2231230A CA 2231230 C CA2231230 C CA 2231230C
- Authority
- CA
- Canada
- Prior art keywords
- message
- signaling
- call
- asynchronous
- connection
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
- 230000011664 signaling Effects 0.000 claims abstract description 200
- 238000000034 method Methods 0.000 claims abstract description 110
- 238000012545 processing Methods 0.000 claims abstract description 96
- 230000008569 process Effects 0.000 claims abstract description 85
- 238000004891 communication Methods 0.000 claims description 50
- 238000012546 transfer Methods 0.000 claims description 20
- 230000004044 response Effects 0.000 claims description 8
- 239000011159 matrix material Substances 0.000 abstract description 12
- 238000001514 detection method Methods 0.000 description 37
- 230000006870 function Effects 0.000 description 19
- 238000010200 validation analysis Methods 0.000 description 19
- 238000010586 diagram Methods 0.000 description 10
- 239000004744 fabric Substances 0.000 description 6
- 238000004458 analytical method Methods 0.000 description 5
- 239000000872 buffer Substances 0.000 description 5
- 238000006243 chemical reaction Methods 0.000 description 5
- 238000013519 translation Methods 0.000 description 5
- 230000014616 translation Effects 0.000 description 5
- 240000004760 Pimpinella anisum Species 0.000 description 4
- 238000012360 testing method Methods 0.000 description 3
- 241001108995 Messa Species 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- RGNPBRKPHBKNKX-UHFFFAOYSA-N hexaflumuron Chemical compound C1=C(Cl)C(OC(F)(F)C(F)F)=C(Cl)C=C1NC(=O)NC(=O)C1=C(F)C=CC=C1F RGNPBRKPHBKNKX-UHFFFAOYSA-N 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 241001203771 Eudonia echo Species 0.000 description 1
- 241000282320 Panthera leo Species 0.000 description 1
- 241000245032 Trillium Species 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 201000000760 cerebral cavernous malformation Diseases 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005315 distribution function Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/30—Peripheral units, e.g. input or output ports
- H04L49/3081—ATM peripheral units, e.g. policing, insertion or extraction
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/02—Details
- H04J3/12—Arrangements providing for calling or supervisory signals
- H04J3/125—One of the channel pulses or the synchronisation pulse is also used for transmitting monitoring or supervisory signals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/24—Time-division multiplex systems in which the allocation is indicated by an address the different channels being transmitted sequentially
- H04J3/247—ATM or packet multiplexing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/20—Support for services
- H04L49/205—Quality of Service based
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/25—Routing or path finding in a switch fabric
- H04L49/253—Routing or path finding in a switch fabric using establishment or release of connections between ports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/25—Routing or path finding in a switch fabric
- H04L49/253—Routing or path finding in a switch fabric using establishment or release of connections between ports
- H04L49/254—Centralised controller, i.e. arbitration or scheduling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/25—Routing or path finding in a switch fabric
- H04L49/253—Routing or path finding in a switch fabric using establishment or release of connections between ports
- H04L49/255—Control mechanisms for ATM switching fabrics
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/04—Selecting arrangements for multiplex systems for time-division multiplexing
- H04Q11/0428—Integrated services digital network, i.e. systems for transmission of different types of digitised signals, e.g. speech, data, telecentral, television signals
- H04Q11/0478—Provisions for broadband connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0025—Provisions for signalling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0029—Provisions for intelligent networking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/54—Store-and-forward switching systems
- H04L12/56—Packet switching systems
- H04L12/5601—Transfer mode dependent, e.g. ATM
- H04L2012/5603—Access techniques
- H04L2012/5609—Topology
- H04L2012/561—Star, e.g. cross-connect, concentrator, subscriber group equipment, remote electronics
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/54—Store-and-forward switching systems
- H04L12/56—Packet switching systems
- H04L12/5601—Transfer mode dependent, e.g. ATM
- H04L2012/5619—Network Node Interface, e.g. tandem connections, transit switching
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/54—Store-and-forward switching systems
- H04L12/56—Packet switching systems
- H04L12/5601—Transfer mode dependent, e.g. ATM
- H04L2012/5625—Operations, administration and maintenance [OAM]
- H04L2012/5626—Network management, e.g. Intelligent nets
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/54—Store-and-forward switching systems
- H04L12/56—Packet switching systems
- H04L12/5601—Transfer mode dependent, e.g. ATM
- H04L2012/5629—Admission control
- H04L2012/563—Signalling, e.g. protocols, reference model
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/54—Store-and-forward switching systems
- H04L12/56—Packet switching systems
- H04L12/5601—Transfer mode dependent, e.g. ATM
- H04L2012/5672—Multiplexing, e.g. coding, scrambling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/30—Peripheral units, e.g. input or output ports
- H04L49/3009—Header conversion, routing tables or routing tags
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13102—Common translator
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13104—Central control, computer control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/1313—Metering, billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13176—Common channel signaling, CCS7
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/1329—Asynchronous transfer mode, ATM
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13296—Packet switching, X.25, frame relay
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13375—Electronic mail
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/1338—Inter-exchange connection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13389—LAN, internet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13513—UPT - personal as opposed to terminal mobility, inc. number portability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13531—Indexing scheme relating to selecting arrangements in general and for multiplex systems virtual networks - inc. PVN
Abstract
A system for processing telecommunications signaling. Signaling for a call is received into a signaling processor (110). The signaling processor (110) processes the call and generates new signaling incorporating the processing.
The new signaling is transferred to network elements (135) as appropriate. The signaling processor (110) is not coupled to a switch matrix and only communicates with the network elements (135) over signaling links (140).
The new signaling is transferred to network elements (135) as appropriate. The signaling processor (110) is not coupled to a switch matrix and only communicates with the network elements (135) over signaling links (140).
Description
SYSTEM FOR MANAGING TELECOr~E~IUNICATIONS
Background of the Invention 1. Field of the Invention The invention relates to telecommunications and specifically to a system that manages telecommunications by processing signaling to generate new signaling for the network elements that provide the telecommunications services.
Background of the Invention 1. Field of the Invention The invention relates to telecommunications and specifically to a system that manages telecommunications by processing signaling to generate new signaling for the network elements that provide the telecommunications services.
2. Prior Art Telecommunications networks use switches to process calls and set-up connections. The switches need to communicate with one another in order to accomplish this function. These communications between switches are known as signaling. A prominent example of signaling is Signaling System #7 (SS7). It is important to point out that signaling is different than the actual user trafi'lc transported over the connections set-up by a call. Signaling is the communications which occur in order to set-up and tear down call connections.
A classic example of signaling is where a first switch processes a dialed number and selects a second switch to use on the call. The first switch extends the call connection to the second switch and signals the dialed number to the second switch.
This second switch may repeat the process for a third switch, and the process would repeat until the call connection is complete. To facilitate this processing, the switch contains a central processing unit (CPU) and a signaling point. The switch CPU
is coupled to the switch matrix and controls the connections established by the matrix. The switch CPU processes the information, such as a dialed number, to select a connection and direct its associated switch matrix to make the connection. The switch signaling point acts as the signaling interface for the switch CPU by transmitting and receiving signaling and converting call information between the signaling protocol and the switch CPU protocol.
Signaling has attained additional functionality with the evolution of what is called the intelligent network. In the intelligent network, switches are supported by external processors and databases. Switches process the signaling they receive to process calls.
During this processing, the switch CPU may recognize that it needs the support of external processing or data. To obtain this support, the switch CPU and signaling point will generate a new signaling message to send to an external processor. The new signaling message is known as a query. The external processor will process the query and respond to the same switch with a signal containing additional information to support the switch.
A classic example of intelligent network operation is the 800 call (also known as free phone). For 800 calls, a switch will receive a call set-up message including the dialed number. In SS7, this is an initial address message (IAM). The switch would process the IAM until it recognized that the dialed number had an area code of 800, and that the switch 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. The standard telephone number is known colloquially as a plain old telephone service (POTS) number. As such, the switch would generate a signaling message to send to an external database. In SS7, this is a transaction capabilities application part (TCAP) message and is commonly known as a query. The external processor that receives the TCAP query is known as a service control point (SCP). The SCP
analyzes the query and typically responds to the switch with the appropriate POTS
number. The switch can then process the call in a conventional fashion. Those skilled in the art are aware of the many special call processing features that can be implemented through an SCP.
Thus, it is known in the art that a switch initially receives a call set-up message n to begin call processing. The switch may trigger during call processing and invoke an
A classic example of signaling is where a first switch processes a dialed number and selects a second switch to use on the call. The first switch extends the call connection to the second switch and signals the dialed number to the second switch.
This second switch may repeat the process for a third switch, and the process would repeat until the call connection is complete. To facilitate this processing, the switch contains a central processing unit (CPU) and a signaling point. The switch CPU
is coupled to the switch matrix and controls the connections established by the matrix. The switch CPU processes the information, such as a dialed number, to select a connection and direct its associated switch matrix to make the connection. The switch signaling point acts as the signaling interface for the switch CPU by transmitting and receiving signaling and converting call information between the signaling protocol and the switch CPU protocol.
Signaling has attained additional functionality with the evolution of what is called the intelligent network. In the intelligent network, switches are supported by external processors and databases. Switches process the signaling they receive to process calls.
During this processing, the switch CPU may recognize that it needs the support of external processing or data. To obtain this support, the switch CPU and signaling point will generate a new signaling message to send to an external processor. The new signaling message is known as a query. The external processor will process the query and respond to the same switch with a signal containing additional information to support the switch.
A classic example of intelligent network operation is the 800 call (also known as free phone). For 800 calls, a switch will receive a call set-up message including the dialed number. In SS7, this is an initial address message (IAM). The switch would process the IAM until it recognized that the dialed number had an area code of 800, and that the switch 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. The standard telephone number is known colloquially as a plain old telephone service (POTS) number. As such, the switch would generate a signaling message to send to an external database. In SS7, this is a transaction capabilities application part (TCAP) message and is commonly known as a query. The external processor that receives the TCAP query is known as a service control point (SCP). The SCP
analyzes the query and typically responds to the switch with the appropriate POTS
number. The switch can then process the call in a conventional fashion. Those skilled in the art are aware of the many special call processing features that can be implemented through an SCP.
Thus, it is known in the art that a switch initially receives a call set-up message n to begin call processing. The switch may trigger during call processing and invoke an
-3-external processor with a separate query message. After analysis, the external processor will respond to that same switch with its own message.
At present, the switches are the devices which receive and process the call set-up signaling to route calls and invoke the intelligent network. As a result, current networks ' S are limited to what the switch can accomplish in the form of call processing. In order to add new functionality, the switch CPU must be re-programmed with new call-processing logic or an existing switch trigger must be re-used. Both restrict a network's ability to provide new services. Since the switch remains the primary platform from which call processing is initiated and controlled, networks must wait until switches are developed with the requisite functionality before new services and interworking can be deployed.
A current example of this problem is provided by asynchronous transfer mode (ATM) switches. Although ATM switches are currently functional to transport broadband tragic, ATM switches which can handle extensive call capacity and signaling are not available. Support systems for these switches, such as billing and trigger detection, are not at a robust stage of development. As a result, networks have to wait until ATM switches develop additional capability before the broadband transport functionality can be fully exploited. Systems are needed which do not rely on the signal processing and call processing capabilities of the switches.
At least one system has suggested routing user service requests to a call server that is external to a switch. However, this system requires that the call processing be separated from connection processing. This separation requires the deployment of an entirely new and proprietary signaling system. In this system, a call server receives user signaling and selects services and route characteristics. A separate connection server selects the route, and a separate channel server selects the specific connections on the route. The servers communicate with a proprietary signaling protocol. This system is not yet defined to a point suffcient for implementation. As such, the system could not be as readily implemented as a system which integrates call processing with connection processing and uses conventional signaling protocols.
At present, the switches are the devices which receive and process the call set-up signaling to route calls and invoke the intelligent network. As a result, current networks ' S are limited to what the switch can accomplish in the form of call processing. In order to add new functionality, the switch CPU must be re-programmed with new call-processing logic or an existing switch trigger must be re-used. Both restrict a network's ability to provide new services. Since the switch remains the primary platform from which call processing is initiated and controlled, networks must wait until switches are developed with the requisite functionality before new services and interworking can be deployed.
A current example of this problem is provided by asynchronous transfer mode (ATM) switches. Although ATM switches are currently functional to transport broadband tragic, ATM switches which can handle extensive call capacity and signaling are not available. Support systems for these switches, such as billing and trigger detection, are not at a robust stage of development. As a result, networks have to wait until ATM switches develop additional capability before the broadband transport functionality can be fully exploited. Systems are needed which do not rely on the signal processing and call processing capabilities of the switches.
At least one system has suggested routing user service requests to a call server that is external to a switch. However, this system requires that the call processing be separated from connection processing. This separation requires the deployment of an entirely new and proprietary signaling system. In this system, a call server receives user signaling and selects services and route characteristics. A separate connection server selects the route, and a separate channel server selects the specific connections on the route. The servers communicate with a proprietary signaling protocol. This system is not yet defined to a point suffcient for implementation. As such, the system could not be as readily implemented as a system which integrates call processing with connection processing and uses conventional signaling protocols.
-4-Summary of the Invention The invention includes a method of call processing where a user transfers a call set-up signaling message to a telecommunications network that comprises at least one network element connected to a communication path. A signaling processor is also linked to the network element and the user. The method comprises receiving the call set-up signaling message into the signaling processor. The signaling processor only communicates with the network element over a signaling link and is not coupled to a switch matrix. The signaling processor performs call processing in response to the call set-up signaling message to produce a new signaling message that directs the network element to provide a telecommunications service. The signaling processor transmits the new signaling message to the network element connected to the communication path.
The signaling message received by the signaling processor could be a Signaling System #7 (SS7) initial address message (IAM).
The call processing could include validating the call, service identification, call processing, personal/terminal mobility call processing, voice messaging call processing, virtual private network call processing, implementing echo control, generating billing information, selecting a virtual connection, and POTS call processing.
The signaling messages could be conventional signaling. They could be from the same protocol or they could 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 also includes a signaling processing system that comprises a signaling interface to transmit and receive signaling messages over a signaling link and a call/connection processor that is coupled to the signaling interface. The call connectionlprocessor is not coupled to a switch matrix and is operable to perform call processing, produce a new signaling message based on the call processing, and to transmit the new signaling message through the signaling interface. The new signaling message directs a network element to provide a telecommunications service for the call.
The network element is connected to a communications path for the call and did not generate the initial signaling message received through the signaling interface. The
The signaling message received by the signaling processor could be a Signaling System #7 (SS7) initial address message (IAM).
The call processing could include validating the call, service identification, call processing, personal/terminal mobility call processing, voice messaging call processing, virtual private network call processing, implementing echo control, generating billing information, selecting a virtual connection, and POTS call processing.
The signaling messages could be conventional signaling. They could be from the same protocol or they could 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 also includes a signaling processing system that comprises a signaling interface to transmit and receive signaling messages over a signaling link and a call/connection processor that is coupled to the signaling interface. The call connectionlprocessor is not coupled to a switch matrix and is operable to perform call processing, produce a new signaling message based on the call processing, and to transmit the new signaling message through the signaling interface. The new signaling message directs a network element to provide a telecommunications service for the call.
The network element is connected to a communications path for the call and did not generate the initial signaling message received through the signaling interface. The
-5-call/connection processor only communicates with the network element through the signaling interface.
Another embodiment of the invention is a method for selectively validating calls that comprises accepting a call and receiving the caller number and the called number.
Before validating the call, determining if the call is a type of call that requires validation, and if the call does not require validation, then processing the called number, but if the call requires validation, then entering a validation database with the caller number before further processing of the called number.
The invention also includes a method for selectively validating calls that comprises accepting a call and receiving the caller number and the called number for the call. Then, determining if the called number is an "800" number, and if the called number is an "800" number, then entering an "800" number database with the called number before entering a validation database with the caller number; but if the called number is not an "800" number, then entering a validation database with the caller number before further processing of the called number.
The invention also includes a telecommunications system that provides telecommunications services to users of the system. The system comprises ATM
switches, ATM multiplexers, ATM connections, narrowband connections, signaling links and signaling processors, The signaling processors reside externally to the ATM
switches and receive and process a signaling message from a user for a call.
The signaling processors generate and transmit a new signaling message that directs an ATM
switch to provide a telecommunications service to the user for the call.
Brief Description of the Drawings The invention can be better understood by reference to the following drawing figures where:.
Figure 1 depicts a block diagram of a version of the invention.
Figure 2 depicts a logic diagram of a version of the invention.
Figure 3 depicts a logic diagram of a version of the invention.
Figure 4 depicts a logic diagram of a version of the invention.
Another embodiment of the invention is a method for selectively validating calls that comprises accepting a call and receiving the caller number and the called number.
Before validating the call, determining if the call is a type of call that requires validation, and if the call does not require validation, then processing the called number, but if the call requires validation, then entering a validation database with the caller number before further processing of the called number.
The invention also includes a method for selectively validating calls that comprises accepting a call and receiving the caller number and the called number for the call. Then, determining if the called number is an "800" number, and if the called number is an "800" number, then entering an "800" number database with the called number before entering a validation database with the caller number; but if the called number is not an "800" number, then entering a validation database with the caller number before further processing of the called number.
The invention also includes a telecommunications system that provides telecommunications services to users of the system. The system comprises ATM
switches, ATM multiplexers, ATM connections, narrowband connections, signaling links and signaling processors, The signaling processors reside externally to the ATM
switches and receive and process a signaling message from a user for a call.
The signaling processors generate and transmit a new signaling message that directs an ATM
switch to provide a telecommunications service to the user for the call.
Brief Description of the Drawings The invention can be better understood by reference to the following drawing figures where:.
Figure 1 depicts a block diagram of a version of the invention.
Figure 2 depicts a logic diagram of a version of the invention.
Figure 3 depicts a logic diagram of a version of the invention.
Figure 4 depicts a logic diagram of a version of the invention.
-6-Figure 5 depicts a logic diagram of a version of the invention.
Figure 6 depicts a logic diagram of a version of the invention.
Figure 7 depicts a flow diagram of a version of the invention.
Figure 8 depicts a flow diagram of a version of the invention.
Figure 9 depicts a flow diagram of a version of the invention.
Figure 10 depicts a block diagram of a version of the invention.
Detailed Description of the Invention The invention provides a system for managing telecommunications which is not as dependent on switch fitnctionality as prior systems. This is accomplished by employing a system which processes call signaling and does not have to be bundled with a switch and associated switch matrix. Using the invention, the switches can be used to provide their switching and transport functions irrespective of their capability to provide other features. In addition, some embodiments of the invention can logically integrate call and connection processing, and can be operational with conventional signaling systems.
On the figures, connections that carry user information are shown as single lines and signaling links that carry signaling messages are shown as double lines.
Figure 1 depicts a basic version of the unique invention. Signaling processor 110 is shown connected to user 11 S by link 120. Processor 1 I 0 is also connected to switch 125 by link 13 0 and to element 13 S by link 140. User 115 is connected tn ~w;t.~h ~
~ c "<,o,.
connection 145. Switch 125 is connected to element 135 over connection 150.
Aside from processor 110, these components are known in the art. User 115 could be any entity requesting a service that requires a communication path with a few examples being a telephone, a computer, or a local exchange carrier (LEC) switch. Switch 125 could be any device which establishes communications paths in response to signaling with examples being a Northern Telecom DMS-250 or a Fore Systems ATM Switch.
Element 135 could be any device to which calls are connected. A few examples would be a switch, cross-connect, server, enhanced platform, or even, a destination telephone or computer. Connections 145 and 1 SO could be any media which carries user -'j-information with a few examples being DS3 trunks, SONET/ATM virtual connections, or wireless connections. Links 120, 130, and 140 could be media which transfers telecommunications signaling with a few examples being a S6 kbit data line, a virtual channel carrying SS7, or a UDP/IP link. Those skilled in the art will readily appreciate S that networks typically deploy numerous other switches, connections, links, and other network elements which are not shown on Figure I for purposes of clarity.
Among these other network elements might be SCPs, signal transfer points (STPs), multiplexers, and echo cancellers, but there are many others.
Processor 110 could be any processing platform configured to support the requirements of the invention and is discussed in detail below. In operation, user 11 S
would request a service that requires a communications path by signaling a network.
These signals are directed to processor 110 over link 120. Those skilled in the art are aware that STPs might be used for this purpose. In addition, in-band signals, such as those on a local loop, may pass through a switch before they are separated out-of band 1 S and directed to processor 1 I 0. Any technique for directing user signaling to processor 110 is contemplated by the invention. This signaling is known as call set-up signaling and for SS7, it is the IAM.
It is important to note that the call set-up signaling from user 11 S is directed to processor 110 and is not processed by switch 12S in order to recognize a trigger or establish a communication path. Processor 110 does not merely receive queries generated by switch 12S that are generated in response to the call set-up signaling from user I 1 S. It is also important to note that processor 1 I 0 does not accept connections 14S or 150 which carry the actual user traffic. As such, processor 110 is linked to the switch only by a signaling link. It is not coupled to a switch matrix and can be external 2S to the switch. However, the signaling processor could actually reside physically within a switch if it is not coupled to the switch matrix and only communicates with the switch over a signaling link. Those skilled in the art are aware of how a switch CPU
is coupled to the switch matrix.
Processor 110 would process the call-set up signaling. For a typical call, this might include verifying the dialed number, validating the caller, controlling an echo _g_ canceller, generating billing information, selecting connections for the call, and generating signaling incorporating the pertinent information to complete the call. This signaling generated by processor I 10 would be transmitted over link 130 to switch 125 in order to provide the service. This may include setting up the communications path S over connections 145 and 150. If required, processor 110 could also generate and transmit appropriate signaling to element 135 over link 140 or to user I 15 over link 120.
The signaling could be conventional signaling such as SS7.
Figure 2 depicts another embodiment of the invention, although the invention is not restricted to this embodiment. Narrowband switch 215 is shown connected to ATM
switch 225 by connection 205. Signaling processor 210 is shown linked to narrowband switch 215 by signaling link 220. Signaling processor 210 is also shown linked to ATM
switch 225 by signaling link 230.
Those skilled in the art are familiar with the logical breakdown and functionality shown for switches 215 and 225. Both switches 215 and 225 contain switching fabric that is connected by connection 205. The switch fabric and connection 205 carry the user information for a call. Both the switch fabric and connection 205 are well known.
An interworking multiplexer would be used to convert the traffc on connection between narrowband and broadband formats. The multiplexer is not shown for purposes of clarity.
Signaling is required to control the switching function. Signaling link 220 is connected to message transfer part (MTP) level 1. The signaling link is typically an SS7 link. MTP level 1 defines the physical and electrical requirements for link 220. MTp level 2 sits on top of level l and maintains reliable transport over link 220 by monitoring status and performing error checks. Together, MTP levels 1-2 provide reliable transport over an individual link. A device would need MTP level 1-2 functionality for each link it uses. MTP level 3 sits on top of level 2 and provides a routing and management function for the signaling system at large. MTP level 3 directs messages to the proper signaling link (actually to the MTP level 2 for that link). MTP level 3 directs messages to applications using the MTP levels for access the signaling system. MTP
level 3 also has a management function which monitors the status of the signaling system and can _g_ take appropriate measures to restore service through the system. MTP levels 1-correspond to layers 1-3 of the open systems interconnection basic reference model (OSIBRF). Both the MTP 1-3 and the OSIBRF are well known in the art Switch 21 S has integrated services digital network user part (ISUP) logic which supports basic call processing. ISUP uses MTP to transmit messages across the signaling system. The information contained in ISUP messages is used by telecommunications networks to implement services and establish communications paths. A few examples of ISUP information are the dialed number and the caller's number. ISUP employs many different message types to carry this information with a few examples being the initial address message (IAM) and the answer message (ANM).
ISUP is well known in the art.
Narrowband switch 215 has call process logic which processes the call information provided by ISUP in order to control the switch fabric and establish communication paths. A classic example of this would be the analysis of a dialed number to select a route for the call. Narrowband switch call processors are well known in the art.
ATM switch 225 has ATM layer, signaling ATM adaption layer (SAAL), and MTP level 3 logic which provide routing, management, and transport over the signaling system. Signaling link 230, typically an ATM virtual connection transported by SONET
or DS3 facilities, is connected to the ATM layer. The ATM layer is analogous to MTP
level l and transmits and receives ATM cells containing signaling messages on the link specified in the cell header. The SAAL assembles and disassembles these cells, maintains individual virtual connections, performs error checks and is analogous to MTP
level 2.
The 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 layer, the SAAL, and the updated MTP level 3 are known in the art.
ATM Switch 225 has broadband-ISUP (B-ISUP) logic which supports basic call processing in the broadband environment to control the broadband switch fabric. B
ISUP uses MTP level 3, the SAAL, and the ATM layer to transmit messages across the signaling system. The information contained in B-ISUP generated messages is used by telecommunications networks to establish communications paths. A few examples of B-ISUP information are the dialed number and the caller's number. B-ISUP
employs many different message types to carry this information with a few examples being the initial address message (IAM) and the answer message (ANM). B-ISUP is known in the ' art.
ATM switch 225 has call process logic which processes the call information provided by B-ISUP in order to control the switching fabric and establish communication paths. An example of this would be the assignment of a virtual connection to a call based on a dialed number. ATM switch call processors are known in the art.
Processor 210 is connected to signaling links 220 and 230. Processor 210 has the MTP and ATM logic described above which allow it to interface 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 which transfers signaling between MTP level 3 and the call/connection manager (CCM). Processor 210 has CCM logic which is able to process the information in the signaling received from the interface. For a typical call, this might include verifying the dialed number, validating the caller, controlling an echo canceller, generating billing information, translating the dialed number, selecting a route for the call, and generating signaling to complete the call. The signaling generated by the CCM would be transported back through the interface for transfer to switches 215 or 225.
In one embodiment, narrowband switch 215 might be a LEC switch and ATM
switch 225 might be an interexchange carrier (IXC) switch. The IXC faces several problems when trying to interwork existing LEC narrowband switches with its own ATM switches. Current ATM switches do not support many of the features required by an IXC in a robust manner, such as routing and billing. Additionally, switches 215 and 225 are not equipped to exchange signaling without modifying one of the switches with a ISUP to B-ISUP signaling interworking unit. The present invention provides the interworking function between the two switches and provides call processing.
This means a much less sophisticated ATM switch can be used.
In this embodiment LEC switch 215 might request a connection through the IXC. As a result, LEC switch 215 would signal the IXC with an SS7 IAM over ' S signaling link 220. Processor 210 would accept the message through its MTP
layers and interface. The interface would deliver the signal to the CCM, and the CCM
would process the signaling information in the IAM. This may include verifying that the dialed number is legitimate, validating the caller by checking the Automatic Number Identification (ANI), generating a billing record, and controlling an echo canceller. The CCM could also process the dialed number to select a connection for the call.
The pertinent portions of this information would be packed into an appropriate B-ISUP
message and passed to the interface for subsequent transfer by the MTP 3, the SAAL, and the ATM layer to ATM switch 225 over signaling link 230. Based on the B-ISUP
message, ATM switch 225 would connect the call. This would entail PxtPnr~ina tl,P
communications path beyond connection 205 based on the signaling message from the CCM. As such, a communications path would be set-up through switch 21 S and switch 225.
The Call/Connection Mana et (CCM,~
Figures 3-9 depict an embodiment of the signaling processor which is also referred to the a call/connection manager. Although this embodiment is preferred, the invention should not be restricted to this specific embodiment.
Signaling processor 310 is shown. Reference numeral 315 indicates that signaling processor 310 can be equipped with an MTP level 1-2 signaling interface, an ATM layer/SAAL signaling interface, or both. Signaling processor 310 would be equipped with MTP level 3 320 which operates as described above for ISUP and B-ISUP. Also shown for signaling processor 310 is ethernet interface 335.
Ethernet interface 335 is a standard ethernet bus supporting TCP/IP which transfers signaling messages from MTP level 3 to platform handler 340. Together, the above components provide a signaling interface for the signaling processor. Those skilled in the art will recognize other interfaces and protocols which could provide a signaling interface in accord with the invention.
The signaling interface would be operational to route select ISUP messages to platform handler 340. One technique for accomplishing this would be to make signaling processor 310 a user part of the STP. A point code converter could be placed between MTP level 2 and MTP level 3 of the STP. The point code converter would convert the destination point code of messages that meet certain criteria to a point code that identifies signaling processor 310. The criteria could be loaded into a table and could include the originating point code (OPC), the destination point code (DPC), the (circuit identification code), and various combinations of these criteria. The conversion at this location in the STP could be specific to the signaling link used by the message, so the conversion tables could inherently account for the link used by the message. After conversion, the distribution function of MTP level 3 would forward signaling messages with the converted DPC to platform handler 340 over ethernet interface 335. A similar conversion function could be placed prior to the route function of MTP level 3 to convert point codes for messages transmitted by platform handler 340 out through the STP.
Alternatively, an SS7 signaling interface to the platform handler could be conswcted using commercially available SS7 software tools. An example of such tools would be SS7 interface software provided by Trillium, Inc. Signaling messages with a destination point code (DPC) matching the point code for signaling processor 310 would be routed to the signaling interface of signaling processor 310 by the STP.
Additionally, the STP could convert the DPC of a signaling message to the point code of signaling processor 310 as described above. However, since signaling processor 310 is not a user part of the STP, the route function of MTP level 3 in the STP
would route the signaling message to signaling processor 310 over a signaling link. The signaling interface would receive the signaling message and transfer it to platform handler 340.
Although point code conversion facilitates a transition from existing systems to one of the present invention, it is not essential. Any method of forwarding signaling the CCM is sufficient.
Also shown are platform handler 340, message handler 345, and data handler 350. Platform handler 340 is a system which accepts ISUP and B-ISUP messages from ethernet interface 335 and routes them to message handler 345. Preferably, platform handler 340 is configured to route messages to a particular message handler processor based on the signaling link selection (SLS) code in the message. Message handler 345 is a system which exchanges signaling with platform handler 340 and controls the connection and switching requirements for the calls. It can select and implement services and initiate echo control. It also converts signaling between ISUP
and B-ISUP.
Data handler 350 is a set of logic coupled to message handler 345 which processes service requests and provides data to message handler 345. Data handler 350 also controls echo cancellers and generates billing records for the call.
In the discussions that follow, the term ISUP will include B-ISUP as well. In operation, ISUP messages that meet the proper criteria are routed by MTP
and/or ATM
interface 315, MTP level 3 320, and ethernet interface 335 to platform handler 340.
Platform handler 340 would route the ISUP messages to message handler 345.
Message handler 345 would process the ISUP information. This might include validation, screening, and determining if additional data is needed for call processing.
If so, data handler 350 would be invoked and would provide message handler 345 with the relevant data so message handler 345 could complete call processing. Message handler would generate the appropriate ISUP message to implement the call and pass the signals to platform handler 340 for subsequent transmission to the designated network elements.
The distribution of functional entities among message handler 345 and data handler 350 are shown. These functional entities are well known in the art.
Message handler 345 includes at least the call control function (CCF) and the service switching function (SSF). The CCF establishes and releases call connections, and the SSF
recognizes triggers during call processing by the CCF and provides an interface between the CCF and the service control function (SCF). The SCF identifies services and obtains data for the service. In some embodiments, message handler 345 can include the SCF
and the service data function (SDF). The SDF provides service data in real time to the SCF. Taken together, message handler 345 is able to at least control connections and recognize triggers. In some embodiments, message handler 345 can also identify services, obtain data for the services, and generate the signaling required to implement the services. Message handler 345 can provide signaling interworking (i.e.
ISUP to B
ISUP), connection control, service selection and service implementation in a logically integrated package that interfaces with the network through conventional means.
Data handler 350 includes at least the SCF and the SDF. In some embodiments, message handler 345 and data handler 350 both include the SCF and the SDF and services are partitioned among the functional entities. Two other functions are shown in data handler that are not standardized functional entities. ACC~untinss oPnPrarPC ~
billing record and echo handles the echo cancellers. Typically, an echo canceller is disabled for a data call and enabled after the data call for use on subsequent voice calls, however, other techniques are applicable.
In operation, the CCF would perform basic call processing until the SSF
recognized a trigger and invoked the SCF. The SCF would identify the service associated with the trigger. The SCF would access data from the SDF in order to implement the service. The SCF would process the data from the SDF and provide the data to the CCF through the SSF. The CCF would then set-up the connections through conventional signaling to service switching points (SSPs). The SSPs are connected to the communications path and make the connections. Typically, an SSP is a switch.
Also, echo cancelIers may be controlled for the call, and a billing record could be generated for the call.
Those skilled in the art are aware of various hardware components which can support the requirements of the invention. For example, the platform handler, message handler, and data handler could each reside on a separate SPARC station 20.
The Platform Han ler Figure 4 shows a possible version of the platform handler. Platform handler is shown. Platform handler 410 includes STP handler 412, supervisor 414, and CCM
handler 416 Platform handler 410 transmits and receives ISUP messages to/from a signaling interface. That STP routed ISUP messages with particular characteristics to an application residing on top of the STP. The application Could be the CCM and the characteristics could be the originating point code (OPC), destination point code (DPC), signaling link selection (SLS), circuit identification code (CIC), and/or the service information octet (SIO). The connection between platform handler 410 and the STP
could be an ethernet LAN transporting ISUP messages encapsulated in TCP/IP
packets.
STP handler 412 would provide the ethernet--TCP/IP interface. STP handler 412 has a process to buffer and dis-assemble the incoming packets to the CCM, and buffer and assemble outgoing packets. STP handler 412 could also check the messages for basic flaws. Any technique for transfer of signaling messages to platform handler 410 is contemplated by the invention.
Supervisor 414 is responsible for managing and monitoring CCM activities.
Among these are CCM start-up and shut-down, log-in and log-off of various CCM
modules, handling administrative messages (i.e. error, warning, status, etc.) from the CCM modules, and handling messages from network operations such as queries, configuration instructions, and data updates. The connection to network operations is the man machine interface which allows the CCM to be controlled and monitored by either a remote or a local operator. Supervisor 414 has a process which retrieves configuration data from internal tables to initialize and configure the CCM.
The CCM
modules also have internal tables which are used in conjunction with this procedure.
Supervisor 414 also communicates internally with 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 supervisory messages with the message handler. The connection between CCM handler 416 and the message handler could be an ethernet LAN transporting these messages encapsulated in TCP/IP
packets, but other methods are known. CCM handler 416 would provide the ethernet--TCP/IP
interface. CCM handler 416 has a process to buffer and dis-assemble the incoming -packets from the message handler, and buffer and assemble outgoing packets to the message handler. CCM handler 416 could also check the messages for basic flaws.
Internally, platform handler 410 is equipped with bi-directional channels which exchange information among STP handler 412, supervisor 414, and CCM handler 416.
The channels between STP handler 412, CCM handler 415, and supervisor 412 carry supervisory and administrative information. The channel between STP handler 412 and CCM handler 416 carries ISUP message information.
Platform handler 410 accepts, disassembles, and buffers ISUP messages received from the network. It can perform basic checks on the messages before transfernng them to the message handler. Should more than one message handler be connected to platform handler 410, the ISUP messages could be allocated to the message handlers based on the SLS of the particular ISUP message. CCM handler 416 accepts routing instructions from the message handler for routing certain ISUP messages to select processes of the message handler. Platform handler 410 also provides supervision and a man/machine interface for the CCM.
The Message Handler.
Figure S depicts a possible version of the message handler. Message handler 520 is shown and includes call center 521, origination manager 522, termination manager 523, detection point manager 528, feature manager 524, auxiliary manager 525, switching manager 526, and local resource 527. A primary function of message handler 520 is to modify ISUP messages.
Call center 521 is the process which receives call set-up messages from the platform handler. ISUP call set-up is initiated with the IAM. When call center receives an IAM, it creates an instance of an origination manager process with data defined by the information in the IAM. Origination manager 522 represents any of the origination manager processes spawned by call center 521. The CCM handler is instructed of the new instance so that subsequent ISUP messages related to that call can be transferred directly to the appropriate instance of origination manager 522 by the platform handler.
Origination manager 522 sets up a memory block called an originating call S control block. The call control block provides a repository for information specific to a call. For example, the originating call control block could identify the following: the call control block, the origination manager, the message handler, the originating LEC, the LEC trunk circuit (CIC), the ATM virtual circuit, the ATM virtual path, the caller's number, the dialed number, the translated dialed number, the originating line information, the ANI service class, the selected route, the number of the selected route, the SLS, the OPC, the DPC, the service indicator (SIO), echo cancellation status, reason of release, call status, and pointers to adjacent call control blocks. In addition, the call control block would also contain the various times that signaling messages are received, such the address complete message (ACM), the answer message (ANM), the suspend message (SUS), the resume message (RES), and the release message (REL). Those skilled in the art would be aware of other pertinent data to include.
Origination manager 522 executes call processing in accordance with the Basic Call State Model (BCSM) recommended by the International Telecommunications Union (ITU), but with some notable exceptions. Origination manager 522 processes the IAM through each point in call (PIC) until a detection point (DP) is encountered. When a detection point is encountered, a message is sent to detection point manager 528 and processing is suspended at origination manager 522 until detection point manager 528 responds. An example of a detection point for origination manager 522 would be to authorize an origination attempt.
Detection point manager 528 accepts messages from originating manager 522 caused by a detection point encountered during call processing. Detection point manager 528 will identify whether or not the detection point is armed. An armed detection point has specific criteria which can affect call processing if met.
If the - detection point is not armed, detection point manager 528 will send a continue signal back to origination manager 522. A continue message instructs origination manager 522 to continue call processing to the next detection point. If the detection point is armed, detection point manager 528 will take action to see if the detection point criteria are met.
If detection point manager 528 requires assistance to process the armed detection point, it will send a message to feature manager 524.
Feature manager 524 would accept messages from detection point manager 528 and either forward the a message to auxiliary manager 525 or to switching manager 526.
Particular feature messages would be routed to auxiliary manager 525 which will process these call features. These are typically non-IN features, such as echo control or POTS
billing. Other feature messages would be routed to switching manager 526.
These are typically IN features. Examples of IN features are 800 number translation or a terminal mobility number translation. Feature manager 524 will pass information back to detection point manager 528 (then to origination manager 522) when it is received back from auxiliary manager 525 or switching manager 526.
Switching manager 526 which will determine if the request will be handled by local resource 527 or by the data handler. Local resource 527 will be structured to provide data more efficiently stored at message handler 520. Examples of such data include: an automatic number identification (ANI) validation table which checks the caller's number, a dialed number translation table to translate POTS numbers into a routing instructions, or N00 translation tables to translate select 800 numbers into routing instructions. Examples of a routing instruction yielded by the tables would be a switch/trunk or a virtual connection. An example of data in the data handler would be virtual private network (VPN) routing tables or complex 800 routing plans.
Typically, originating manager 522 will execute through the pertinent points in call to a point indicating that set up is authorized. At this point, origination manager 522 will instruct call center 521 to create an instance of a termination manager.
Termination manager 523 represents any of these termination managers. Origination manager will also transfer IAM information to termination manager 523. Termination manager 523 sets up a memory block called a terminating call control block. The call control block provides a repository for information specific to a call and is similar in composition to the originating call control block.
Termination manager 523 also operates in accord with the BCSM of the ITU, but also with some exceptions. Termination manager 523 continues processing for the - call through its own points in call until detection points are encountered.
When a detection point is encountered, a message is sent to detection point manager 528 and processing is suspended at termination manager 523 until detection point manager 528 responds. An example of detection point for termination manager 522 would be to authorize termination which would entail authorizing the call as set-up by origination manager 522. Messages from termination manager 523 to detection point manager are handled as discussed above for messages from originating manager 522. When processing by termination manager 523 is complete, it will produce an IAM to transmit through platform handler 410 to the appropriate network elements.
Message handler 520 communicates with the data handler using a data transfer protocol. Examples include UDP/IP, or the Intelligent Network Applications Protocol (INAP) which is contained within the component sublayer of Transaction Capabilities Application Part (TCAP).
The Data Handler Figure 6 shows a possible version of the data handler. Data handler 630 is shown. Data handler 630 includes service control center 631, service selection 632, service logic center 633, feature process 634, service data center 635, service data manager 636, echo control 637, and accounting 638. Data handler 630 receives service request messages from the message handler. These messages result from an armed detection points triggering the message handler to invoke data handler 630.
The messages also result from features implemented through the auxiliary manager.
Service control center 631, service logic center 633, and service data center 635 are static processes created at start-up. Service control center 631 creates instances of service selection managers on a call by call basis. Service control center 631 notifies the Switching manager to route subsequent service request messages for that call to the . appropriate service selection manager. Service selection manager 632 represents any of the service selection managers created by service control center 631.
Service selection manager 632 executes the service portion of the call processing. Service selection manager 632 identifies the various services associated with each message and implements the service through messages to service logic center 633.
Service logic center 633 accepts messages from service selection 632 and creates instances of the feature processes required for the identified services.
Examples of feature processes are N00, messaging, personal/terminal mobility, and virtual private network (VPN). Feature processes are service logic programs which implement the required services for a call. Feature process 634 represents any of the feature processes created by service logic center 633. Feature process 634 accesses the network resources and data required to implement the service. This would entail executing service independent blocks (SIBs). A SIB is a set of functions. An example of a function would be to retrieve the called number from a signaling message. SIBS are combined to build a service. An example of a SIB is translating a called number.
Those skilled in the are familiar with the above services, although they have never been implemented by a system such as the present invention. N00 services are services such as 800, 900, or 500 calling in which the dialed number is used to access call processing and billing logic defined by the subscriber to the service.
Messaging entails connecting the caller to a voice messaging service. For example, the receipt of a release message (REL) with a cause of busy could be a trigger recognized by the message handler. In response, the data handler would create an instance of the messaging feature process and determined if a call placed to a particular dialed number would require the voice messaging platform. If so, the CCM would instruct an SSP to connect the caller to the voice message platform. Personal/Terminal mobility includes recognizing that the dialed number has mobility that requires a database look-up to determine the current number. The database is updated when the called party changes locations. VPN is a private dialing plan. It is used for calls from particular dedicated lines, from particular calling numbers (ANIs), or to particular dialed numbers. Calls are routed as def ned for the particular plan.
In the execution of the SIB to provide the service, feature process 634 would invoke service data center 635 to create an instance of service data manager 636.
Service data manager 636 accesses the network databases that provide the data required for the service. Access could be facilitated by TCAP messaging to an SCP.
Service data manager 636 represents any ofthe service managers created by service data center 635.
Once the data is retrieved, it is transferred back down to feature process 634 for further S service implementation. When the feature processes for a call finish execution, service information is passed back down to the message handler and ultimately to the origination or termination manager for the call.
After a release message on a call, billing requests will be forwarded to accounting 638. Accounting 638 will use the call control block to create a billing record. The call control block would contain information from the ISUP messages for the call and from CCM processing. From the address complete message (ACM), the call control block would include the routing label, CIC, message type, and cause indicators. From the answer message (ANM), the call control block would include the routing label, CIC, message type, and backward call indicators. From the initial address message (IAM), 1 S the call control block would include the routing label, CIC, message type, forward call indicators, user service information, called party number, calling party number, carrier identification, carrier selection information, charge number, generic address, origination line information, original called number, and redirecting number. From the release message (REL), the call control block would include the routing label, CIC, message type, and cause indicators. From the suspend message (SUS) or the pass along message (PAM), the call control block would include the routing label, CIC, and message type.
Those skilled in the art are familiar with other pertinent information for a billing record and appreciate that some of this information could be deleted.
For POTS calls, the billing request will come from the origination and termination managers through the auxiliary manager. For IN calls, the request will come from service selection 632. Accounting 638 will generate a billing record from the call control blocks. The billing record will be forwarded to a billing system over a billing interface. An example of such an interface is the LE.E.E. 802.3 FTAM protocol.
At some point during call set-up, the origination manager, termination manager or even the detection point process will check the user service information data and originating line information to assess the need for echo control. If the call is a data call, a message is sent to data handler 630. Specifically, the message is routed through the auxiliary manager to the echo control manager 637 in data handler 630. Based on the CIC, echo control manager 637 can select which echo canceller and DSO circuit needs S to be disabled. A message will be generated to that effect and transmitted over a standard data link to the pertinent echo canceller or echo control system.
Once a release (REL) message is received for the circuit, the echo canceller is re-enabled.
On a typical call, this procedure will occur twice. Once for an echo canceller on the access side, and again for an echo canceller on the terminating side. The CCM that handles the IAM for a particular call segment will control the particular echo cancellers for the segment.
IA~I~t Call Procecsine Prior to a description of IAM processing, a brief description of SS7 message is given. SS7 messaging is well known in the art. SS7 ISUP messages contain numerous 1 S fields of information. Each message will have a routing label containing a destination point code (DPC), an origination point code (OPC), and a signaling link selection (SLS) which are used primarily for routing the message. Each message contains a circuit identification code (CIC) which identifies the circuit to which the message relates. Each message contains the message type which is used to recognize the message. ISUP
messages also contain mandatory parts filled with fixed length data and variable length data, in addition to a part available for optional data. These parts vary from message type to message type depending on the information needed.
The initial address message (IAM) initiates the call and contains call set-up information, such as the dialed number. IAMs are transferred in the calling direction to set up the call. During this process, TCAP messages may be sent to access remote data and processing. When the IAMs have reached the final network element, an address complete message (AC1V>] is sent in the backward direction to indicate that the required .
information is available and the called party can be alerted. If the called party answers, an answer message (ANM) is sent in the backward direction indicating that the call/connection will be used. If the calling party hangs up, a release message (REL) is sent to indicate the connection is not being used and can be torn down. If the called party hangs up, a suspend message (SUS) is sent and if the called party reconnects, a resume (RES) message keeps the line open, but if their is no re-connection, a release message (REL) is sent. When the connections are free, release complete messages ' S (RLC) are sent to indicate that the connection can be re-used for another call. Those skilled in the art are aware of other ISUP messages, however, these are the primary ones to be considered. As can be seen, the IAM is the message that sets-up the call.
In the preferred embodiment, call processing deviates from the basic call model recommended by the ITU, although strict adherence to the model could be achieved in other embodiments. Figures 7-10 depicts the preferred call processing.
Referring first to Figure 7, When the IAM for a call is received at 705, the call center creates an instance of an origination manager at 710.
The origination manager begins call processing by sending an authorize message to the detection point manager. Detection point manager checks IAM
information, including the dialed number, the CIC, and the originating line information, to perform service discrimination at 71 S. This is done to determine if the service requested requires validation at 720. Current call processing systems and the BCSM of the ITU
both validate the call before performing service discrimination. In a significant advance over the prior art, the preferred embodiment deviates from known call processing methods by looking at the IAM information prior to validation to determine if validation is even required. For example, the calling party may not pay the bill for a call. The called party pays the bill on 800 calls and validation can be unnecessary. If validation is not required at 720, call processing proceeds directly to B. Advantageously, this avoids unnecessary look-ups in validation tables for a significant percentage of calls.
If validation is required at 720, a validation table is checked at 725.
Validation checks to see if a call should be allowed and focuses on potential billing problems for the call. For example, calls from ANIs that are delinquent on payments pose problems for billing and may not be validated. Validation would entail messaging from the detection point manager through the feature manager and the switching manager to the local resource to access the tables. The table may list authorized ANIs, unauthorized ANIs, " CA 02231230 1998-03-OS , PCT~',~~ 96/1~~ ~.0'~
~~~~ ~'~ ::: ~~ ~ A~G 1997 or both. Ifthe call is not authorized at 730, treatment (i.e. route 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 deterniine ifthe call can be routed. This would typically occur for POTS
calls. If no additional services are required at 740, the dialed number is translated into a route instruction at 745.
The route instruction could be a particular virtual connection in the network.
The processing then proceeds to A. If additional services are required at 740, processing proceeds to B.
Figure 8 picks up processing A after a route has been selected. A termination manager is created at 805. The termination manager is responsible for processing in accordance with the terminating BCSM of the ITU. However, in some embodiments, the processing can exhibit some deviation. For example detection points such as select facility '' and validate call may be skipped.
The bearer capability is analyzed at 810 to determine if the call is a data call at 815.
This analysis could occur elsewhere in the call processing (i.e. by the origination 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 disable message is created at 825 and is sent at 830. The echo cancellation instructions identify the route instruction selected for the call. The message could be sent to the echo canceler system over a conventional data link from the CCM to the echo canceler system.
If the call is not a data call at 815 or after echo canceler processing at 830, an IAM
message is created at 83 5. The new IAM incorporates pertinent call processing information -~ such as the selected route. The new IAM is sent to the platform handler at 840. Typically, the IAM will place the route instruction in the called number digits field.
This means the digits may not represent the actual called number, but will contain other routing information recognizable by the network elements. The network elements would have to be capable of processing the routing instruction. The called number can be placed in another field in the IAM.
Figure 9 picks up the processing at B. At this point, several things are known about the call concerning authorization and service requirements. The call information a ~r~aL~to~o s~~~~', is then analyzed at 905 as required to apply services to the call. If the data handler is not required at 910, the service is implemented and the route is selected at 915.
This may occur if a service can be directly implemented by the origination manager or through the local resource. For example, particular 800 translations or dialed number service profiles (i.e call forwarding) can be stored in the local resource. In this case, route selection would be performed by the local resource after the information is analyzed to identify the correct entry to a local resource database. When the local resource is used, the messages must be routed from the detection point processor through the feature manager and switching manager to the local resource.
If the data handler is required for the call at 910, a message is sent to the data handler at 920. The messaging typically flows from the detection point processor to the feature manager and switching manager to the data handler. Upon receipt of the message at the data handler, the service control center creates an instance of the service selection process at 925. The service selection process analyzes the message from the detection point processor and selects the feature processes for the call at 930. For example, a call may be placed from a caller in a virtual private network (VPN) to a PCS
number. In this case, both a VPN feature process and a PCS feature process would be created.
Each feature process would determine if data was required at 940. For example, a personal mobility feature process would need to access a database to locate the called party's current telephone number. If data is required at 940, the service data center creates a service data manager at 945. The data manager manages the data session and accesses the appropriate database at 950. After the data is collected (or none is needed), the service is implemented by the feature process at 955. For some features, i.e. 800 service, this may include route selection. The results of the feature process analysis are returned to the origination manager to assimilate. If the feature process does not provide the route, the origination manager must select the route through the local resource or through another feature process.
The IAM itself contains numerous fields of information. The following table describes the elements of an IAM with regard to the information content and call processing.
Table 1 -- Description of the Initial Address Message ' ROUTING LABEL
Parameter Field Name Descri Lion Service Indicator Set at 0101-ISDN user art Priorit 0 or 1 based on destination Network ID 10 for national network or set based on international trunk ou Destination Point Code Destination of IAM
Ori inatin Point Code Ori ination of IAM
1 Signaling Link Connection Link used for messages (same S for all messa es for the call Circuit ID Code Circuit used for the call between OPC and DPC in the IAM
Messa a T a 0000 or 0001 for IAM
NATURE OF CONNECTION INIDICATORS
Satellite Indicator Increment for each satellite used Continuity Check Indicator 00 -- no check O1 -- set up check and start COT timer 10 -- start timer for COT messa e.
Echo Suppresser Indicator Indicates if echo control already implemented or is set if echo control is im lemented FORWARD CALL INDICATORS
National/International Call Indicator0 for domestic 1 for international End to End Method Indicator Pass an information Interworkin Indicator Pass an information IAM Se mentation Indicator 0 for POTS
ISDN User Part Indicator Pass an information ISDN Preference Indicator Pass an information and default to 00 ISDN Access Indicator Pass an information SCCP Method Indicator 00 CALLING PARTIES CATEGORY
Calling Party Category 00000000 for unknown 00001010 for ordinary caller 00001101 for test call USER SERVICE INFORMATION
Information Transfer CapabilityPass any information unless destination requires particular settings, but always pass ISDN "unrestricted di ital information"
Codin Standard 00 Extension 1 Information Transfer Raze Pass any information (will be 10000 for POTS
Transfer Mode Set at 00 for 64 kbit/sec Extension 1 User Layer Protocol IdentificationSet based on rate adaption, typically 0100010 for user information la er 1 Extension 1 for normal calls 0 for rate ada tion Rate Nothing for user information layer 1, but 0111 for other rate ada tion Extension 1 CALLED PAR TY NUMBER
Nature of Address Identifies the type of call:
Indicator 0000001 -- original NPA or 950 call 0000011 -- I+ call 0000100 -- direct dial international call 1110001 -- operator call 1110010 -- operator default 1110011 -- international operator call 1110100 -- long distance operator call 1110101 -- cut through call 1 I 10110 -- 950, hoteUmotel, or non equal access call 1110111 -- test call Odd/Even number of di its in a called number Numbering Plan 000 -- default 001 -- for ISDN
101 -- rivate Di its Field number of the called art I ACCESS TRANSPORT
I Access Transport Elements I pass any information I
CALLING PARTY NUMBER
__ Nature of Address IndicatorIndicates the type of calling pa ress, unique numbers can be used for billing, but the charge number is used for non-unique numbers:
0000000 -- unknown 0000001 -- unique caller number 000001 I -- unique national number 0000100 -- unique international number I 110001 -- non-unique caller number 1 I 10011 -- non-unique national number I 110100 -- non-unique international number 1110111 -- test call Odd/Even Number of di its in the callin number Screenin Not a licable Presentation Allowed/RestrictedPass any information for POTS, bu ct for N00 calls that are not allowed Numbering Plan 000 -- default 101 -- rivate Di its Field Number of the callin art CARRIER IDENTIFICATION
Network Identification Plan Number of digits in identification code for the re uested earner T ype of Network IdentificationIdentifies the network numbering plan for the call -- O 10 for POTS call from LEC
Di it One First di it in earner identification code Di it Two Second di 't in earner identification code Di it Three Third di it in carrier identification code Digit Four or Null Fourth digit in carrier identification code (if there are four di its CARRIER SELECTION INFORMATION
Carner Selection Indicator Indicates whether the carrier identification code was resubscribed or in ut CHARGE
NUMBER
Nature of Address Indicator This information may be used for billing.
00000001 -- caller number 00000010 -- no ANI, route to operator 0000001 I -- caller's national number 00000101 -- route if 800, or route to operator 0000110 -- no ANI
0000111 -- route if 800 or route to o erator Odd/Even Number of di its in callin number Numberin Plan Pass an information Di its Field The number of callin art GENERIC ADDRESS
__ Nature of Address Indicator Pass an informati Odd/Even Pass an information Screenin Pass an information Presentation Allowed/RestrictedPass an information Numberin Plan Pass an information Di its Field Pass an information ORIGINATING LINE INFORMATION
Originating Line Information Identifies particular types of calls, for example:
00000000 -- normal call 00000111 -- call from a restricted phone 0011111 I -- call from a cellular roamer ORIGINAL CALLED NUMBER
Nature of address Indicator Pass information an Odd/Even Pass information an Screenin Pass information an Presentation Allowed/RestrictedPass information an Numberin Plan Pass information an Di its Field Pass information an REDIRECTING NUMBER
Nature of Address Indicator Pass an information Odd/Even Pass an information Screenin Pass an information Presentation Allowed/RestrictedPass an information Numberin Plan Pass an information Di its Field Pass an information REDIRECTION INFORMATION
Redirection Indicator Pass an information Ori final Redirectin Reason Pass an information Redirection Counter Pass an information Redirection Reason Pass an information SERVICE CODE
~ Service Code ~ Pass any information Hop Counter limits the number of times an IAM may transfer through a signaling point. If the count reaches the limit, release the call The various fields in the message contain the pertinent information required to initiate call processing. IAM messages that are generated by the CCM could contain routing instructions. These could be placed in the called party number digits field. The called party number could be relocated in another field. The SSPs could then receive the IAM and route based on the routing instruction in the digits field. For example, the information could identify a routing code, telephone number, switch, trunk, platform, or network. A network element receiving such an IAM would recognize the routing instruction, such as a routing code, and provide the corresponding telecommunications service.
Subsequent ISUP Message Processing The processing of the IAM is discussed above. Those skilled in the art are will appreciate how other SS7 messages can be incorporated into the processing of the present invention. For example, the time an address complete message (ACM) is S received is recorded in the call control block for billing and maintenance.
Triggers can also be based on receipt of subsequent messages, such as the ACM. The process for the answer message (ANM) is much the same.
Cut-through is the time point at which the users are able to pass information along the call connection from end to end. Messages from the CCM to the appropriate network elements are required to allow for cut-through of the call. Typically, call connections include both a transmit path from the caller and a receive path to the caller, and cut through is allowed on the receive path after the ACM is received and on the transmit path after the ANM is received.
Upon receipt of a release (REL) message, the CCM will write a time for the 1 S message to the call control block and check for triggers upon release (such as call re-originate). Additionally, any disabled echo canceller will be re-enabled, and the call control block will be used to create a billing record. Upon the receipt of a release complete message (RLC), the CCM will transmit messages directing tear down of the call path. It will clear its call specific processes and reuse the call connections for subsequent calls.
Additionally, suspend messages (SUS) and pass along messages (PAM) may be processed by the CCM. A suspend message (SUS) indicates that the called party has disconnected and a REL will follow if the called party does not re-connect with a specified time. A PAM is simply a message between signaling points and can contain a variety of information and be used for a variety of purposes.
Network Operation From the above discussion, it can be seen that the invention can receive and process an signaling to select connections for the call. The invention is also able to apply services during call processing. Figure 10 shows a specific embodiment of the present invention with relation to a network, but the invention is applicable in other scenarios.
Networks 1001, 1002, and 1003 are shown. Network 1001 is comprised of narrowband switch 1005 and signal transfer point (STP) 1010. Narrowband switch is connected to ' network 1002 by connection 1015. Narrowband switch is linked to STP 1010 by link 1020 and STP 1010 is linked to network 1002 by link 1025. Connection 1015 carries user traffic. Links 1020 and 1025 carry signaling messages. Narrowband switches, STPs, connections, and signaling links can take many various forms and are well known in the art. Network 1003 is similarly situated with narrowband switch 1030, STP 1035, connection 1040, link 1045, and link 1050.
Network 1002 is shown with ATM switch 1055, ATM switch 1060, mux 1065, mux 1070, echo control 1068, and echo control 1078. Mux 1065 is coupled to echo control 1068. Mux 1075 is coupled to echo control 1078. Echo control 1068 is connected to narrowband switch 1005 by connection 1015. Mux 1065 is connected to ATM switch 1055 by connection 1075. ATM switch 1055 is connected to ATM switch 1060 by connection 1080. ATM switch 1060 is connected to mux 1070 by connection 1085. Echo control 1078 is connected to narrowband switch 1030 by connection 1040.
Also shown are STP 1090 and STP 1095. STP 1090 is linked to STP 1010 over link 1025. STP 1090 is linked to ATM switch 1055 by link 1105. STP 1090 is linked to STP 1095 by link 1100. STP 1095 is linked to ATM switch 1060 by link 1110. STP
1095 is linked to STP 1035 by link 1050. These components are all well known in the art.
Network I 002 also includes CCM 1115 and CCM 1120. CCM 111 S is linked to STP 1090 by link 1125 and to echo control 1068 by link 1128. CCM 1120 is linked to STP 1095 by link 1130 and to echo control 1078 by link 1138. The CCMs and associated links are configured to operate as described above with respect to the present invention. In operation, a call would proceed as follows.
Network 1001 would send a call to network 1002. This means switch 1005 would use connection 1015 to connect to network 1002. A signaling message would also be sent over link 1020 through STP 1010 and over link 1025 to network 1002.
Network 1002 would receive the signaling message at STP 1090. The signaling message could be an SS7 ISUP message, and in particular and IAM. STP 1090 would route SS7 ISUP messages from switch 1005 to CCM 1 I IS. It may be the case that the message was actually sent to a component other than CCM 111 S, but was directed to CCM 111 S by network 1002. CCM 111 S would process the IAM. Processing could ' S include validation, call information analysis, and route selection as described above. In turn, this may include POTS calls or calls requiring additional services such as N00, VPN, messaging, or personal/terminal mobility. In this embodiment, CCM 111 S
might select connection 1080 as the route instruction for ATM switch IOSS. An SS7 B-ISUP
IAM would be formulated by CCM I I 1 S and sent to ATM switch l OSS over link through STP 1090 and over link 1105. ATM switch LOSS would accept the route instruction and select the specific VPI/VCI on connection 1080 and generate a B-ISUP
IAM reflecting the selected VPI/VCI. Additionally, the route instruction from CCM
1115 could have identified the actual VPI, and left VCI selection to ATM
switch LOSS.
This IAM from ATM switch LOSS would be routed over link 1 l OS through STP
1S 1090 and over link 1100 to STP 1095. STP 1095 would route this IAM over link 1130 to CCM 1120. CCM 1120 would process the B-ISUP IAM and select network 1003, and in particular, connection 1085 and/or switch 1030 as the route instruction for switch 1060. A B-ISUP IAM would be formulated by CCM 1120 and sent to switch 1060 over link I 130 through STP 1095 and over link I 110. ATM switch 1060 would select the proper VPI/VCI (or possibly only the VCI) on connection 1085 and generate a B-ISUP
message reflecting the selection. This B-ISUP message would be routed over link 1110 through STP 1095 and over link 1130 to CCM 1120. CCM I 120 would process the B-ISUP IAM to create an ISUP M for narrowband switch 1030. The ISUP IAM would be sent to switch 1030 over link 1130, through STP 1095, over link 1050, through STP
2S 1035, and over link 1045. Muxes 1065 and 1070 convert the trafl'tc between narrowband format and ATM format. The CCM tracks these connections through the muxes so it can equate narrow band connections and ATM connections on each side of a given mux.
CCM 1 I I S would check the IAM to determine if the call is a data call. If so, the echo canceller on the selected connection would need disabled. This would be WO 97/09808 PCT/iJS96/14105 accomplished by a message from CCM 1115 to echo control 1068 over link 1128.
The same procedure would occur between CCM 1120 and echo control 1078 over link 1138.
Narrowband switch 1030 will typically produce an address complete message (ACM) to signify the called party is being alerted and an answer message (ANM) to signify the called party has answered. These messages are routed back to network 1002 and to CCM 1120. CCM 1120 and CCM 1115 instruct switches 1055 and 1060 to allow cut-through on the selected connections and will signal network 1001 of the call status. When a party terminates the call, suspend (5U5), release (REL), and release complete (RLC) messages are transmitted by networks 1001 and 1003 as appropriate in order to tear down the call. CCM 1115 and CCM 1120 will process these messages and instruct switch 1055 and switch 1060 to use those VPINCIs for other calls.
At this time each CCM will generate billing information for the call.
The invention provides several advantages over prior systems. The invention is not coupled to a switching matrix and thus, it is not dependent on the capabilities bundled with a switch by the switch provider. The invention does not accept actual user traffc and is not required to have transport capability. However, the invention does accept the signaling that a switch would receive, processes the signaling, and provides a switch with a new signal that incorporates the processing. The processing can implement routing, billing, and special services so the switch does not need to have the capabilities. The processing can also interwork different signaling types so each switch receives signaling in its own format.
Current signaling processors cannot provide these advantages. SCPs process TCAP message queries and do not process call set-up messages sent from a user.
SCPs process queries generated by a switch and respond to that same switch. SCPs must be invoked by a switch and respond to that switch.
Signaling points and their associated switch CPUs are bundled with the switch and the switch CPU is coupled to a switch matrix. The added functionality of this , system increases its cost and reduces its flexibility.
Another proposed signaling processing system is logically segregated according to call, service, connection, and channel. As such, it must rely on a proprietary signaling protocol to communicate among the logically segregated components. This system does not provide 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 appreciate variations that will support the S requirements of the invention. As such, the invention should not be restricted to only the embodiments listed above. The invention should only be defined by the following claims.
Figure 6 depicts a logic diagram of a version of the invention.
Figure 7 depicts a flow diagram of a version of the invention.
Figure 8 depicts a flow diagram of a version of the invention.
Figure 9 depicts a flow diagram of a version of the invention.
Figure 10 depicts a block diagram of a version of the invention.
Detailed Description of the Invention The invention provides a system for managing telecommunications which is not as dependent on switch fitnctionality as prior systems. This is accomplished by employing a system which processes call signaling and does not have to be bundled with a switch and associated switch matrix. Using the invention, the switches can be used to provide their switching and transport functions irrespective of their capability to provide other features. In addition, some embodiments of the invention can logically integrate call and connection processing, and can be operational with conventional signaling systems.
On the figures, connections that carry user information are shown as single lines and signaling links that carry signaling messages are shown as double lines.
Figure 1 depicts a basic version of the unique invention. Signaling processor 110 is shown connected to user 11 S by link 120. Processor 1 I 0 is also connected to switch 125 by link 13 0 and to element 13 S by link 140. User 115 is connected tn ~w;t.~h ~
~ c "<,o,.
connection 145. Switch 125 is connected to element 135 over connection 150.
Aside from processor 110, these components are known in the art. User 115 could be any entity requesting a service that requires a communication path with a few examples being a telephone, a computer, or a local exchange carrier (LEC) switch. Switch 125 could be any device which establishes communications paths in response to signaling with examples being a Northern Telecom DMS-250 or a Fore Systems ATM Switch.
Element 135 could be any device to which calls are connected. A few examples would be a switch, cross-connect, server, enhanced platform, or even, a destination telephone or computer. Connections 145 and 1 SO could be any media which carries user -'j-information with a few examples being DS3 trunks, SONET/ATM virtual connections, or wireless connections. Links 120, 130, and 140 could be media which transfers telecommunications signaling with a few examples being a S6 kbit data line, a virtual channel carrying SS7, or a UDP/IP link. Those skilled in the art will readily appreciate S that networks typically deploy numerous other switches, connections, links, and other network elements which are not shown on Figure I for purposes of clarity.
Among these other network elements might be SCPs, signal transfer points (STPs), multiplexers, and echo cancellers, but there are many others.
Processor 110 could be any processing platform configured to support the requirements of the invention and is discussed in detail below. In operation, user 11 S
would request a service that requires a communications path by signaling a network.
These signals are directed to processor 110 over link 120. Those skilled in the art are aware that STPs might be used for this purpose. In addition, in-band signals, such as those on a local loop, may pass through a switch before they are separated out-of band 1 S and directed to processor 1 I 0. Any technique for directing user signaling to processor 110 is contemplated by the invention. This signaling is known as call set-up signaling and for SS7, it is the IAM.
It is important to note that the call set-up signaling from user 11 S is directed to processor 110 and is not processed by switch 12S in order to recognize a trigger or establish a communication path. Processor 110 does not merely receive queries generated by switch 12S that are generated in response to the call set-up signaling from user I 1 S. It is also important to note that processor 1 I 0 does not accept connections 14S or 150 which carry the actual user traffic. As such, processor 110 is linked to the switch only by a signaling link. It is not coupled to a switch matrix and can be external 2S to the switch. However, the signaling processor could actually reside physically within a switch if it is not coupled to the switch matrix and only communicates with the switch over a signaling link. Those skilled in the art are aware of how a switch CPU
is coupled to the switch matrix.
Processor 110 would process the call-set up signaling. For a typical call, this might include verifying the dialed number, validating the caller, controlling an echo _g_ canceller, generating billing information, selecting connections for the call, and generating signaling incorporating the pertinent information to complete the call. This signaling generated by processor I 10 would be transmitted over link 130 to switch 125 in order to provide the service. This may include setting up the communications path S over connections 145 and 150. If required, processor 110 could also generate and transmit appropriate signaling to element 135 over link 140 or to user I 15 over link 120.
The signaling could be conventional signaling such as SS7.
Figure 2 depicts another embodiment of the invention, although the invention is not restricted to this embodiment. Narrowband switch 215 is shown connected to ATM
switch 225 by connection 205. Signaling processor 210 is shown linked to narrowband switch 215 by signaling link 220. Signaling processor 210 is also shown linked to ATM
switch 225 by signaling link 230.
Those skilled in the art are familiar with the logical breakdown and functionality shown for switches 215 and 225. Both switches 215 and 225 contain switching fabric that is connected by connection 205. The switch fabric and connection 205 carry the user information for a call. Both the switch fabric and connection 205 are well known.
An interworking multiplexer would be used to convert the traffc on connection between narrowband and broadband formats. The multiplexer is not shown for purposes of clarity.
Signaling is required to control the switching function. Signaling link 220 is connected to message transfer part (MTP) level 1. The signaling link is typically an SS7 link. MTP level 1 defines the physical and electrical requirements for link 220. MTp level 2 sits on top of level l and maintains reliable transport over link 220 by monitoring status and performing error checks. Together, MTP levels 1-2 provide reliable transport over an individual link. A device would need MTP level 1-2 functionality for each link it uses. MTP level 3 sits on top of level 2 and provides a routing and management function for the signaling system at large. MTP level 3 directs messages to the proper signaling link (actually to the MTP level 2 for that link). MTP level 3 directs messages to applications using the MTP levels for access the signaling system. MTP
level 3 also has a management function which monitors the status of the signaling system and can _g_ take appropriate measures to restore service through the system. MTP levels 1-correspond to layers 1-3 of the open systems interconnection basic reference model (OSIBRF). Both the MTP 1-3 and the OSIBRF are well known in the art Switch 21 S has integrated services digital network user part (ISUP) logic which supports basic call processing. ISUP uses MTP to transmit messages across the signaling system. The information contained in ISUP messages is used by telecommunications networks to implement services and establish communications paths. A few examples of ISUP information are the dialed number and the caller's number. ISUP employs many different message types to carry this information with a few examples being the initial address message (IAM) and the answer message (ANM).
ISUP is well known in the art.
Narrowband switch 215 has call process logic which processes the call information provided by ISUP in order to control the switch fabric and establish communication paths. A classic example of this would be the analysis of a dialed number to select a route for the call. Narrowband switch call processors are well known in the art.
ATM switch 225 has ATM layer, signaling ATM adaption layer (SAAL), and MTP level 3 logic which provide routing, management, and transport over the signaling system. Signaling link 230, typically an ATM virtual connection transported by SONET
or DS3 facilities, is connected to the ATM layer. The ATM layer is analogous to MTP
level l and transmits and receives ATM cells containing signaling messages on the link specified in the cell header. The SAAL assembles and disassembles these cells, maintains individual virtual connections, performs error checks and is analogous to MTP
level 2.
The 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 layer, the SAAL, and the updated MTP level 3 are known in the art.
ATM Switch 225 has broadband-ISUP (B-ISUP) logic which supports basic call processing in the broadband environment to control the broadband switch fabric. B
ISUP uses MTP level 3, the SAAL, and the ATM layer to transmit messages across the signaling system. The information contained in B-ISUP generated messages is used by telecommunications networks to establish communications paths. A few examples of B-ISUP information are the dialed number and the caller's number. B-ISUP
employs many different message types to carry this information with a few examples being the initial address message (IAM) and the answer message (ANM). B-ISUP is known in the ' art.
ATM switch 225 has call process logic which processes the call information provided by B-ISUP in order to control the switching fabric and establish communication paths. An example of this would be the assignment of a virtual connection to a call based on a dialed number. ATM switch call processors are known in the art.
Processor 210 is connected to signaling links 220 and 230. Processor 210 has the MTP and ATM logic described above which allow it to interface 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 which transfers signaling between MTP level 3 and the call/connection manager (CCM). Processor 210 has CCM logic which is able to process the information in the signaling received from the interface. For a typical call, this might include verifying the dialed number, validating the caller, controlling an echo canceller, generating billing information, translating the dialed number, selecting a route for the call, and generating signaling to complete the call. The signaling generated by the CCM would be transported back through the interface for transfer to switches 215 or 225.
In one embodiment, narrowband switch 215 might be a LEC switch and ATM
switch 225 might be an interexchange carrier (IXC) switch. The IXC faces several problems when trying to interwork existing LEC narrowband switches with its own ATM switches. Current ATM switches do not support many of the features required by an IXC in a robust manner, such as routing and billing. Additionally, switches 215 and 225 are not equipped to exchange signaling without modifying one of the switches with a ISUP to B-ISUP signaling interworking unit. The present invention provides the interworking function between the two switches and provides call processing.
This means a much less sophisticated ATM switch can be used.
In this embodiment LEC switch 215 might request a connection through the IXC. As a result, LEC switch 215 would signal the IXC with an SS7 IAM over ' S signaling link 220. Processor 210 would accept the message through its MTP
layers and interface. The interface would deliver the signal to the CCM, and the CCM
would process the signaling information in the IAM. This may include verifying that the dialed number is legitimate, validating the caller by checking the Automatic Number Identification (ANI), generating a billing record, and controlling an echo canceller. The CCM could also process the dialed number to select a connection for the call.
The pertinent portions of this information would be packed into an appropriate B-ISUP
message and passed to the interface for subsequent transfer by the MTP 3, the SAAL, and the ATM layer to ATM switch 225 over signaling link 230. Based on the B-ISUP
message, ATM switch 225 would connect the call. This would entail PxtPnr~ina tl,P
communications path beyond connection 205 based on the signaling message from the CCM. As such, a communications path would be set-up through switch 21 S and switch 225.
The Call/Connection Mana et (CCM,~
Figures 3-9 depict an embodiment of the signaling processor which is also referred to the a call/connection manager. Although this embodiment is preferred, the invention should not be restricted to this specific embodiment.
Signaling processor 310 is shown. Reference numeral 315 indicates that signaling processor 310 can be equipped with an MTP level 1-2 signaling interface, an ATM layer/SAAL signaling interface, or both. Signaling processor 310 would be equipped with MTP level 3 320 which operates as described above for ISUP and B-ISUP. Also shown for signaling processor 310 is ethernet interface 335.
Ethernet interface 335 is a standard ethernet bus supporting TCP/IP which transfers signaling messages from MTP level 3 to platform handler 340. Together, the above components provide a signaling interface for the signaling processor. Those skilled in the art will recognize other interfaces and protocols which could provide a signaling interface in accord with the invention.
The signaling interface would be operational to route select ISUP messages to platform handler 340. One technique for accomplishing this would be to make signaling processor 310 a user part of the STP. A point code converter could be placed between MTP level 2 and MTP level 3 of the STP. The point code converter would convert the destination point code of messages that meet certain criteria to a point code that identifies signaling processor 310. The criteria could be loaded into a table and could include the originating point code (OPC), the destination point code (DPC), the (circuit identification code), and various combinations of these criteria. The conversion at this location in the STP could be specific to the signaling link used by the message, so the conversion tables could inherently account for the link used by the message. After conversion, the distribution function of MTP level 3 would forward signaling messages with the converted DPC to platform handler 340 over ethernet interface 335. A similar conversion function could be placed prior to the route function of MTP level 3 to convert point codes for messages transmitted by platform handler 340 out through the STP.
Alternatively, an SS7 signaling interface to the platform handler could be conswcted using commercially available SS7 software tools. An example of such tools would be SS7 interface software provided by Trillium, Inc. Signaling messages with a destination point code (DPC) matching the point code for signaling processor 310 would be routed to the signaling interface of signaling processor 310 by the STP.
Additionally, the STP could convert the DPC of a signaling message to the point code of signaling processor 310 as described above. However, since signaling processor 310 is not a user part of the STP, the route function of MTP level 3 in the STP
would route the signaling message to signaling processor 310 over a signaling link. The signaling interface would receive the signaling message and transfer it to platform handler 340.
Although point code conversion facilitates a transition from existing systems to one of the present invention, it is not essential. Any method of forwarding signaling the CCM is sufficient.
Also shown are platform handler 340, message handler 345, and data handler 350. Platform handler 340 is a system which accepts ISUP and B-ISUP messages from ethernet interface 335 and routes them to message handler 345. Preferably, platform handler 340 is configured to route messages to a particular message handler processor based on the signaling link selection (SLS) code in the message. Message handler 345 is a system which exchanges signaling with platform handler 340 and controls the connection and switching requirements for the calls. It can select and implement services and initiate echo control. It also converts signaling between ISUP
and B-ISUP.
Data handler 350 is a set of logic coupled to message handler 345 which processes service requests and provides data to message handler 345. Data handler 350 also controls echo cancellers and generates billing records for the call.
In the discussions that follow, the term ISUP will include B-ISUP as well. In operation, ISUP messages that meet the proper criteria are routed by MTP
and/or ATM
interface 315, MTP level 3 320, and ethernet interface 335 to platform handler 340.
Platform handler 340 would route the ISUP messages to message handler 345.
Message handler 345 would process the ISUP information. This might include validation, screening, and determining if additional data is needed for call processing.
If so, data handler 350 would be invoked and would provide message handler 345 with the relevant data so message handler 345 could complete call processing. Message handler would generate the appropriate ISUP message to implement the call and pass the signals to platform handler 340 for subsequent transmission to the designated network elements.
The distribution of functional entities among message handler 345 and data handler 350 are shown. These functional entities are well known in the art.
Message handler 345 includes at least the call control function (CCF) and the service switching function (SSF). The CCF establishes and releases call connections, and the SSF
recognizes triggers during call processing by the CCF and provides an interface between the CCF and the service control function (SCF). The SCF identifies services and obtains data for the service. In some embodiments, message handler 345 can include the SCF
and the service data function (SDF). The SDF provides service data in real time to the SCF. Taken together, message handler 345 is able to at least control connections and recognize triggers. In some embodiments, message handler 345 can also identify services, obtain data for the services, and generate the signaling required to implement the services. Message handler 345 can provide signaling interworking (i.e.
ISUP to B
ISUP), connection control, service selection and service implementation in a logically integrated package that interfaces with the network through conventional means.
Data handler 350 includes at least the SCF and the SDF. In some embodiments, message handler 345 and data handler 350 both include the SCF and the SDF and services are partitioned among the functional entities. Two other functions are shown in data handler that are not standardized functional entities. ACC~untinss oPnPrarPC ~
billing record and echo handles the echo cancellers. Typically, an echo canceller is disabled for a data call and enabled after the data call for use on subsequent voice calls, however, other techniques are applicable.
In operation, the CCF would perform basic call processing until the SSF
recognized a trigger and invoked the SCF. The SCF would identify the service associated with the trigger. The SCF would access data from the SDF in order to implement the service. The SCF would process the data from the SDF and provide the data to the CCF through the SSF. The CCF would then set-up the connections through conventional signaling to service switching points (SSPs). The SSPs are connected to the communications path and make the connections. Typically, an SSP is a switch.
Also, echo cancelIers may be controlled for the call, and a billing record could be generated for the call.
Those skilled in the art are aware of various hardware components which can support the requirements of the invention. For example, the platform handler, message handler, and data handler could each reside on a separate SPARC station 20.
The Platform Han ler Figure 4 shows a possible version of the platform handler. Platform handler is shown. Platform handler 410 includes STP handler 412, supervisor 414, and CCM
handler 416 Platform handler 410 transmits and receives ISUP messages to/from a signaling interface. That STP routed ISUP messages with particular characteristics to an application residing on top of the STP. The application Could be the CCM and the characteristics could be the originating point code (OPC), destination point code (DPC), signaling link selection (SLS), circuit identification code (CIC), and/or the service information octet (SIO). The connection between platform handler 410 and the STP
could be an ethernet LAN transporting ISUP messages encapsulated in TCP/IP
packets.
STP handler 412 would provide the ethernet--TCP/IP interface. STP handler 412 has a process to buffer and dis-assemble the incoming packets to the CCM, and buffer and assemble outgoing packets. STP handler 412 could also check the messages for basic flaws. Any technique for transfer of signaling messages to platform handler 410 is contemplated by the invention.
Supervisor 414 is responsible for managing and monitoring CCM activities.
Among these are CCM start-up and shut-down, log-in and log-off of various CCM
modules, handling administrative messages (i.e. error, warning, status, etc.) from the CCM modules, and handling messages from network operations such as queries, configuration instructions, and data updates. The connection to network operations is the man machine interface which allows the CCM to be controlled and monitored by either a remote or a local operator. Supervisor 414 has a process which retrieves configuration data from internal tables to initialize and configure the CCM.
The CCM
modules also have internal tables which are used in conjunction with this procedure.
Supervisor 414 also communicates internally with 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 supervisory messages with the message handler. The connection between CCM handler 416 and the message handler could be an ethernet LAN transporting these messages encapsulated in TCP/IP
packets, but other methods are known. CCM handler 416 would provide the ethernet--TCP/IP
interface. CCM handler 416 has a process to buffer and dis-assemble the incoming -packets from the message handler, and buffer and assemble outgoing packets to the message handler. CCM handler 416 could also check the messages for basic flaws.
Internally, platform handler 410 is equipped with bi-directional channels which exchange information among STP handler 412, supervisor 414, and CCM handler 416.
The channels between STP handler 412, CCM handler 415, and supervisor 412 carry supervisory and administrative information. The channel between STP handler 412 and CCM handler 416 carries ISUP message information.
Platform handler 410 accepts, disassembles, and buffers ISUP messages received from the network. It can perform basic checks on the messages before transfernng them to the message handler. Should more than one message handler be connected to platform handler 410, the ISUP messages could be allocated to the message handlers based on the SLS of the particular ISUP message. CCM handler 416 accepts routing instructions from the message handler for routing certain ISUP messages to select processes of the message handler. Platform handler 410 also provides supervision and a man/machine interface for the CCM.
The Message Handler.
Figure S depicts a possible version of the message handler. Message handler 520 is shown and includes call center 521, origination manager 522, termination manager 523, detection point manager 528, feature manager 524, auxiliary manager 525, switching manager 526, and local resource 527. A primary function of message handler 520 is to modify ISUP messages.
Call center 521 is the process which receives call set-up messages from the platform handler. ISUP call set-up is initiated with the IAM. When call center receives an IAM, it creates an instance of an origination manager process with data defined by the information in the IAM. Origination manager 522 represents any of the origination manager processes spawned by call center 521. The CCM handler is instructed of the new instance so that subsequent ISUP messages related to that call can be transferred directly to the appropriate instance of origination manager 522 by the platform handler.
Origination manager 522 sets up a memory block called an originating call S control block. The call control block provides a repository for information specific to a call. For example, the originating call control block could identify the following: the call control block, the origination manager, the message handler, the originating LEC, the LEC trunk circuit (CIC), the ATM virtual circuit, the ATM virtual path, the caller's number, the dialed number, the translated dialed number, the originating line information, the ANI service class, the selected route, the number of the selected route, the SLS, the OPC, the DPC, the service indicator (SIO), echo cancellation status, reason of release, call status, and pointers to adjacent call control blocks. In addition, the call control block would also contain the various times that signaling messages are received, such the address complete message (ACM), the answer message (ANM), the suspend message (SUS), the resume message (RES), and the release message (REL). Those skilled in the art would be aware of other pertinent data to include.
Origination manager 522 executes call processing in accordance with the Basic Call State Model (BCSM) recommended by the International Telecommunications Union (ITU), but with some notable exceptions. Origination manager 522 processes the IAM through each point in call (PIC) until a detection point (DP) is encountered. When a detection point is encountered, a message is sent to detection point manager 528 and processing is suspended at origination manager 522 until detection point manager 528 responds. An example of a detection point for origination manager 522 would be to authorize an origination attempt.
Detection point manager 528 accepts messages from originating manager 522 caused by a detection point encountered during call processing. Detection point manager 528 will identify whether or not the detection point is armed. An armed detection point has specific criteria which can affect call processing if met.
If the - detection point is not armed, detection point manager 528 will send a continue signal back to origination manager 522. A continue message instructs origination manager 522 to continue call processing to the next detection point. If the detection point is armed, detection point manager 528 will take action to see if the detection point criteria are met.
If detection point manager 528 requires assistance to process the armed detection point, it will send a message to feature manager 524.
Feature manager 524 would accept messages from detection point manager 528 and either forward the a message to auxiliary manager 525 or to switching manager 526.
Particular feature messages would be routed to auxiliary manager 525 which will process these call features. These are typically non-IN features, such as echo control or POTS
billing. Other feature messages would be routed to switching manager 526.
These are typically IN features. Examples of IN features are 800 number translation or a terminal mobility number translation. Feature manager 524 will pass information back to detection point manager 528 (then to origination manager 522) when it is received back from auxiliary manager 525 or switching manager 526.
Switching manager 526 which will determine if the request will be handled by local resource 527 or by the data handler. Local resource 527 will be structured to provide data more efficiently stored at message handler 520. Examples of such data include: an automatic number identification (ANI) validation table which checks the caller's number, a dialed number translation table to translate POTS numbers into a routing instructions, or N00 translation tables to translate select 800 numbers into routing instructions. Examples of a routing instruction yielded by the tables would be a switch/trunk or a virtual connection. An example of data in the data handler would be virtual private network (VPN) routing tables or complex 800 routing plans.
Typically, originating manager 522 will execute through the pertinent points in call to a point indicating that set up is authorized. At this point, origination manager 522 will instruct call center 521 to create an instance of a termination manager.
Termination manager 523 represents any of these termination managers. Origination manager will also transfer IAM information to termination manager 523. Termination manager 523 sets up a memory block called a terminating call control block. The call control block provides a repository for information specific to a call and is similar in composition to the originating call control block.
Termination manager 523 also operates in accord with the BCSM of the ITU, but also with some exceptions. Termination manager 523 continues processing for the - call through its own points in call until detection points are encountered.
When a detection point is encountered, a message is sent to detection point manager 528 and processing is suspended at termination manager 523 until detection point manager 528 responds. An example of detection point for termination manager 522 would be to authorize termination which would entail authorizing the call as set-up by origination manager 522. Messages from termination manager 523 to detection point manager are handled as discussed above for messages from originating manager 522. When processing by termination manager 523 is complete, it will produce an IAM to transmit through platform handler 410 to the appropriate network elements.
Message handler 520 communicates with the data handler using a data transfer protocol. Examples include UDP/IP, or the Intelligent Network Applications Protocol (INAP) which is contained within the component sublayer of Transaction Capabilities Application Part (TCAP).
The Data Handler Figure 6 shows a possible version of the data handler. Data handler 630 is shown. Data handler 630 includes service control center 631, service selection 632, service logic center 633, feature process 634, service data center 635, service data manager 636, echo control 637, and accounting 638. Data handler 630 receives service request messages from the message handler. These messages result from an armed detection points triggering the message handler to invoke data handler 630.
The messages also result from features implemented through the auxiliary manager.
Service control center 631, service logic center 633, and service data center 635 are static processes created at start-up. Service control center 631 creates instances of service selection managers on a call by call basis. Service control center 631 notifies the Switching manager to route subsequent service request messages for that call to the . appropriate service selection manager. Service selection manager 632 represents any of the service selection managers created by service control center 631.
Service selection manager 632 executes the service portion of the call processing. Service selection manager 632 identifies the various services associated with each message and implements the service through messages to service logic center 633.
Service logic center 633 accepts messages from service selection 632 and creates instances of the feature processes required for the identified services.
Examples of feature processes are N00, messaging, personal/terminal mobility, and virtual private network (VPN). Feature processes are service logic programs which implement the required services for a call. Feature process 634 represents any of the feature processes created by service logic center 633. Feature process 634 accesses the network resources and data required to implement the service. This would entail executing service independent blocks (SIBs). A SIB is a set of functions. An example of a function would be to retrieve the called number from a signaling message. SIBS are combined to build a service. An example of a SIB is translating a called number.
Those skilled in the are familiar with the above services, although they have never been implemented by a system such as the present invention. N00 services are services such as 800, 900, or 500 calling in which the dialed number is used to access call processing and billing logic defined by the subscriber to the service.
Messaging entails connecting the caller to a voice messaging service. For example, the receipt of a release message (REL) with a cause of busy could be a trigger recognized by the message handler. In response, the data handler would create an instance of the messaging feature process and determined if a call placed to a particular dialed number would require the voice messaging platform. If so, the CCM would instruct an SSP to connect the caller to the voice message platform. Personal/Terminal mobility includes recognizing that the dialed number has mobility that requires a database look-up to determine the current number. The database is updated when the called party changes locations. VPN is a private dialing plan. It is used for calls from particular dedicated lines, from particular calling numbers (ANIs), or to particular dialed numbers. Calls are routed as def ned for the particular plan.
In the execution of the SIB to provide the service, feature process 634 would invoke service data center 635 to create an instance of service data manager 636.
Service data manager 636 accesses the network databases that provide the data required for the service. Access could be facilitated by TCAP messaging to an SCP.
Service data manager 636 represents any ofthe service managers created by service data center 635.
Once the data is retrieved, it is transferred back down to feature process 634 for further S service implementation. When the feature processes for a call finish execution, service information is passed back down to the message handler and ultimately to the origination or termination manager for the call.
After a release message on a call, billing requests will be forwarded to accounting 638. Accounting 638 will use the call control block to create a billing record. The call control block would contain information from the ISUP messages for the call and from CCM processing. From the address complete message (ACM), the call control block would include the routing label, CIC, message type, and cause indicators. From the answer message (ANM), the call control block would include the routing label, CIC, message type, and backward call indicators. From the initial address message (IAM), 1 S the call control block would include the routing label, CIC, message type, forward call indicators, user service information, called party number, calling party number, carrier identification, carrier selection information, charge number, generic address, origination line information, original called number, and redirecting number. From the release message (REL), the call control block would include the routing label, CIC, message type, and cause indicators. From the suspend message (SUS) or the pass along message (PAM), the call control block would include the routing label, CIC, and message type.
Those skilled in the art are familiar with other pertinent information for a billing record and appreciate that some of this information could be deleted.
For POTS calls, the billing request will come from the origination and termination managers through the auxiliary manager. For IN calls, the request will come from service selection 632. Accounting 638 will generate a billing record from the call control blocks. The billing record will be forwarded to a billing system over a billing interface. An example of such an interface is the LE.E.E. 802.3 FTAM protocol.
At some point during call set-up, the origination manager, termination manager or even the detection point process will check the user service information data and originating line information to assess the need for echo control. If the call is a data call, a message is sent to data handler 630. Specifically, the message is routed through the auxiliary manager to the echo control manager 637 in data handler 630. Based on the CIC, echo control manager 637 can select which echo canceller and DSO circuit needs S to be disabled. A message will be generated to that effect and transmitted over a standard data link to the pertinent echo canceller or echo control system.
Once a release (REL) message is received for the circuit, the echo canceller is re-enabled.
On a typical call, this procedure will occur twice. Once for an echo canceller on the access side, and again for an echo canceller on the terminating side. The CCM that handles the IAM for a particular call segment will control the particular echo cancellers for the segment.
IA~I~t Call Procecsine Prior to a description of IAM processing, a brief description of SS7 message is given. SS7 messaging is well known in the art. SS7 ISUP messages contain numerous 1 S fields of information. Each message will have a routing label containing a destination point code (DPC), an origination point code (OPC), and a signaling link selection (SLS) which are used primarily for routing the message. Each message contains a circuit identification code (CIC) which identifies the circuit to which the message relates. Each message contains the message type which is used to recognize the message. ISUP
messages also contain mandatory parts filled with fixed length data and variable length data, in addition to a part available for optional data. These parts vary from message type to message type depending on the information needed.
The initial address message (IAM) initiates the call and contains call set-up information, such as the dialed number. IAMs are transferred in the calling direction to set up the call. During this process, TCAP messages may be sent to access remote data and processing. When the IAMs have reached the final network element, an address complete message (AC1V>] is sent in the backward direction to indicate that the required .
information is available and the called party can be alerted. If the called party answers, an answer message (ANM) is sent in the backward direction indicating that the call/connection will be used. If the calling party hangs up, a release message (REL) is sent to indicate the connection is not being used and can be torn down. If the called party hangs up, a suspend message (SUS) is sent and if the called party reconnects, a resume (RES) message keeps the line open, but if their is no re-connection, a release message (REL) is sent. When the connections are free, release complete messages ' S (RLC) are sent to indicate that the connection can be re-used for another call. Those skilled in the art are aware of other ISUP messages, however, these are the primary ones to be considered. As can be seen, the IAM is the message that sets-up the call.
In the preferred embodiment, call processing deviates from the basic call model recommended by the ITU, although strict adherence to the model could be achieved in other embodiments. Figures 7-10 depicts the preferred call processing.
Referring first to Figure 7, When the IAM for a call is received at 705, the call center creates an instance of an origination manager at 710.
The origination manager begins call processing by sending an authorize message to the detection point manager. Detection point manager checks IAM
information, including the dialed number, the CIC, and the originating line information, to perform service discrimination at 71 S. This is done to determine if the service requested requires validation at 720. Current call processing systems and the BCSM of the ITU
both validate the call before performing service discrimination. In a significant advance over the prior art, the preferred embodiment deviates from known call processing methods by looking at the IAM information prior to validation to determine if validation is even required. For example, the calling party may not pay the bill for a call. The called party pays the bill on 800 calls and validation can be unnecessary. If validation is not required at 720, call processing proceeds directly to B. Advantageously, this avoids unnecessary look-ups in validation tables for a significant percentage of calls.
If validation is required at 720, a validation table is checked at 725.
Validation checks to see if a call should be allowed and focuses on potential billing problems for the call. For example, calls from ANIs that are delinquent on payments pose problems for billing and may not be validated. Validation would entail messaging from the detection point manager through the feature manager and the switching manager to the local resource to access the tables. The table may list authorized ANIs, unauthorized ANIs, " CA 02231230 1998-03-OS , PCT~',~~ 96/1~~ ~.0'~
~~~~ ~'~ ::: ~~ ~ A~G 1997 or both. Ifthe call is not authorized at 730, treatment (i.e. route 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 deterniine ifthe call can be routed. This would typically occur for POTS
calls. If no additional services are required at 740, the dialed number is translated into a route instruction at 745.
The route instruction could be a particular virtual connection in the network.
The processing then proceeds to A. If additional services are required at 740, processing proceeds to B.
Figure 8 picks up processing A after a route has been selected. A termination manager is created at 805. The termination manager is responsible for processing in accordance with the terminating BCSM of the ITU. However, in some embodiments, the processing can exhibit some deviation. For example detection points such as select facility '' and validate call may be skipped.
The bearer capability is analyzed at 810 to determine if the call is a data call at 815.
This analysis could occur elsewhere in the call processing (i.e. by the origination 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 disable message is created at 825 and is sent at 830. The echo cancellation instructions identify the route instruction selected for the call. The message could be sent to the echo canceler system over a conventional data link from the CCM to the echo canceler system.
If the call is not a data call at 815 or after echo canceler processing at 830, an IAM
message is created at 83 5. The new IAM incorporates pertinent call processing information -~ such as the selected route. The new IAM is sent to the platform handler at 840. Typically, the IAM will place the route instruction in the called number digits field.
This means the digits may not represent the actual called number, but will contain other routing information recognizable by the network elements. The network elements would have to be capable of processing the routing instruction. The called number can be placed in another field in the IAM.
Figure 9 picks up the processing at B. At this point, several things are known about the call concerning authorization and service requirements. The call information a ~r~aL~to~o s~~~~', is then analyzed at 905 as required to apply services to the call. If the data handler is not required at 910, the service is implemented and the route is selected at 915.
This may occur if a service can be directly implemented by the origination manager or through the local resource. For example, particular 800 translations or dialed number service profiles (i.e call forwarding) can be stored in the local resource. In this case, route selection would be performed by the local resource after the information is analyzed to identify the correct entry to a local resource database. When the local resource is used, the messages must be routed from the detection point processor through the feature manager and switching manager to the local resource.
If the data handler is required for the call at 910, a message is sent to the data handler at 920. The messaging typically flows from the detection point processor to the feature manager and switching manager to the data handler. Upon receipt of the message at the data handler, the service control center creates an instance of the service selection process at 925. The service selection process analyzes the message from the detection point processor and selects the feature processes for the call at 930. For example, a call may be placed from a caller in a virtual private network (VPN) to a PCS
number. In this case, both a VPN feature process and a PCS feature process would be created.
Each feature process would determine if data was required at 940. For example, a personal mobility feature process would need to access a database to locate the called party's current telephone number. If data is required at 940, the service data center creates a service data manager at 945. The data manager manages the data session and accesses the appropriate database at 950. After the data is collected (or none is needed), the service is implemented by the feature process at 955. For some features, i.e. 800 service, this may include route selection. The results of the feature process analysis are returned to the origination manager to assimilate. If the feature process does not provide the route, the origination manager must select the route through the local resource or through another feature process.
The IAM itself contains numerous fields of information. The following table describes the elements of an IAM with regard to the information content and call processing.
Table 1 -- Description of the Initial Address Message ' ROUTING LABEL
Parameter Field Name Descri Lion Service Indicator Set at 0101-ISDN user art Priorit 0 or 1 based on destination Network ID 10 for national network or set based on international trunk ou Destination Point Code Destination of IAM
Ori inatin Point Code Ori ination of IAM
1 Signaling Link Connection Link used for messages (same S for all messa es for the call Circuit ID Code Circuit used for the call between OPC and DPC in the IAM
Messa a T a 0000 or 0001 for IAM
NATURE OF CONNECTION INIDICATORS
Satellite Indicator Increment for each satellite used Continuity Check Indicator 00 -- no check O1 -- set up check and start COT timer 10 -- start timer for COT messa e.
Echo Suppresser Indicator Indicates if echo control already implemented or is set if echo control is im lemented FORWARD CALL INDICATORS
National/International Call Indicator0 for domestic 1 for international End to End Method Indicator Pass an information Interworkin Indicator Pass an information IAM Se mentation Indicator 0 for POTS
ISDN User Part Indicator Pass an information ISDN Preference Indicator Pass an information and default to 00 ISDN Access Indicator Pass an information SCCP Method Indicator 00 CALLING PARTIES CATEGORY
Calling Party Category 00000000 for unknown 00001010 for ordinary caller 00001101 for test call USER SERVICE INFORMATION
Information Transfer CapabilityPass any information unless destination requires particular settings, but always pass ISDN "unrestricted di ital information"
Codin Standard 00 Extension 1 Information Transfer Raze Pass any information (will be 10000 for POTS
Transfer Mode Set at 00 for 64 kbit/sec Extension 1 User Layer Protocol IdentificationSet based on rate adaption, typically 0100010 for user information la er 1 Extension 1 for normal calls 0 for rate ada tion Rate Nothing for user information layer 1, but 0111 for other rate ada tion Extension 1 CALLED PAR TY NUMBER
Nature of Address Identifies the type of call:
Indicator 0000001 -- original NPA or 950 call 0000011 -- I+ call 0000100 -- direct dial international call 1110001 -- operator call 1110010 -- operator default 1110011 -- international operator call 1110100 -- long distance operator call 1110101 -- cut through call 1 I 10110 -- 950, hoteUmotel, or non equal access call 1110111 -- test call Odd/Even number of di its in a called number Numbering Plan 000 -- default 001 -- for ISDN
101 -- rivate Di its Field number of the called art I ACCESS TRANSPORT
I Access Transport Elements I pass any information I
CALLING PARTY NUMBER
__ Nature of Address IndicatorIndicates the type of calling pa ress, unique numbers can be used for billing, but the charge number is used for non-unique numbers:
0000000 -- unknown 0000001 -- unique caller number 000001 I -- unique national number 0000100 -- unique international number I 110001 -- non-unique caller number 1 I 10011 -- non-unique national number I 110100 -- non-unique international number 1110111 -- test call Odd/Even Number of di its in the callin number Screenin Not a licable Presentation Allowed/RestrictedPass any information for POTS, bu ct for N00 calls that are not allowed Numbering Plan 000 -- default 101 -- rivate Di its Field Number of the callin art CARRIER IDENTIFICATION
Network Identification Plan Number of digits in identification code for the re uested earner T ype of Network IdentificationIdentifies the network numbering plan for the call -- O 10 for POTS call from LEC
Di it One First di it in earner identification code Di it Two Second di 't in earner identification code Di it Three Third di it in carrier identification code Digit Four or Null Fourth digit in carrier identification code (if there are four di its CARRIER SELECTION INFORMATION
Carner Selection Indicator Indicates whether the carrier identification code was resubscribed or in ut CHARGE
NUMBER
Nature of Address Indicator This information may be used for billing.
00000001 -- caller number 00000010 -- no ANI, route to operator 0000001 I -- caller's national number 00000101 -- route if 800, or route to operator 0000110 -- no ANI
0000111 -- route if 800 or route to o erator Odd/Even Number of di its in callin number Numberin Plan Pass an information Di its Field The number of callin art GENERIC ADDRESS
__ Nature of Address Indicator Pass an informati Odd/Even Pass an information Screenin Pass an information Presentation Allowed/RestrictedPass an information Numberin Plan Pass an information Di its Field Pass an information ORIGINATING LINE INFORMATION
Originating Line Information Identifies particular types of calls, for example:
00000000 -- normal call 00000111 -- call from a restricted phone 0011111 I -- call from a cellular roamer ORIGINAL CALLED NUMBER
Nature of address Indicator Pass information an Odd/Even Pass information an Screenin Pass information an Presentation Allowed/RestrictedPass information an Numberin Plan Pass information an Di its Field Pass information an REDIRECTING NUMBER
Nature of Address Indicator Pass an information Odd/Even Pass an information Screenin Pass an information Presentation Allowed/RestrictedPass an information Numberin Plan Pass an information Di its Field Pass an information REDIRECTION INFORMATION
Redirection Indicator Pass an information Ori final Redirectin Reason Pass an information Redirection Counter Pass an information Redirection Reason Pass an information SERVICE CODE
~ Service Code ~ Pass any information Hop Counter limits the number of times an IAM may transfer through a signaling point. If the count reaches the limit, release the call The various fields in the message contain the pertinent information required to initiate call processing. IAM messages that are generated by the CCM could contain routing instructions. These could be placed in the called party number digits field. The called party number could be relocated in another field. The SSPs could then receive the IAM and route based on the routing instruction in the digits field. For example, the information could identify a routing code, telephone number, switch, trunk, platform, or network. A network element receiving such an IAM would recognize the routing instruction, such as a routing code, and provide the corresponding telecommunications service.
Subsequent ISUP Message Processing The processing of the IAM is discussed above. Those skilled in the art are will appreciate how other SS7 messages can be incorporated into the processing of the present invention. For example, the time an address complete message (ACM) is S received is recorded in the call control block for billing and maintenance.
Triggers can also be based on receipt of subsequent messages, such as the ACM. The process for the answer message (ANM) is much the same.
Cut-through is the time point at which the users are able to pass information along the call connection from end to end. Messages from the CCM to the appropriate network elements are required to allow for cut-through of the call. Typically, call connections include both a transmit path from the caller and a receive path to the caller, and cut through is allowed on the receive path after the ACM is received and on the transmit path after the ANM is received.
Upon receipt of a release (REL) message, the CCM will write a time for the 1 S message to the call control block and check for triggers upon release (such as call re-originate). Additionally, any disabled echo canceller will be re-enabled, and the call control block will be used to create a billing record. Upon the receipt of a release complete message (RLC), the CCM will transmit messages directing tear down of the call path. It will clear its call specific processes and reuse the call connections for subsequent calls.
Additionally, suspend messages (SUS) and pass along messages (PAM) may be processed by the CCM. A suspend message (SUS) indicates that the called party has disconnected and a REL will follow if the called party does not re-connect with a specified time. A PAM is simply a message between signaling points and can contain a variety of information and be used for a variety of purposes.
Network Operation From the above discussion, it can be seen that the invention can receive and process an signaling to select connections for the call. The invention is also able to apply services during call processing. Figure 10 shows a specific embodiment of the present invention with relation to a network, but the invention is applicable in other scenarios.
Networks 1001, 1002, and 1003 are shown. Network 1001 is comprised of narrowband switch 1005 and signal transfer point (STP) 1010. Narrowband switch is connected to ' network 1002 by connection 1015. Narrowband switch is linked to STP 1010 by link 1020 and STP 1010 is linked to network 1002 by link 1025. Connection 1015 carries user traffic. Links 1020 and 1025 carry signaling messages. Narrowband switches, STPs, connections, and signaling links can take many various forms and are well known in the art. Network 1003 is similarly situated with narrowband switch 1030, STP 1035, connection 1040, link 1045, and link 1050.
Network 1002 is shown with ATM switch 1055, ATM switch 1060, mux 1065, mux 1070, echo control 1068, and echo control 1078. Mux 1065 is coupled to echo control 1068. Mux 1075 is coupled to echo control 1078. Echo control 1068 is connected to narrowband switch 1005 by connection 1015. Mux 1065 is connected to ATM switch 1055 by connection 1075. ATM switch 1055 is connected to ATM switch 1060 by connection 1080. ATM switch 1060 is connected to mux 1070 by connection 1085. Echo control 1078 is connected to narrowband switch 1030 by connection 1040.
Also shown are STP 1090 and STP 1095. STP 1090 is linked to STP 1010 over link 1025. STP 1090 is linked to ATM switch 1055 by link 1105. STP 1090 is linked to STP 1095 by link 1100. STP 1095 is linked to ATM switch 1060 by link 1110. STP
1095 is linked to STP 1035 by link 1050. These components are all well known in the art.
Network I 002 also includes CCM 1115 and CCM 1120. CCM 111 S is linked to STP 1090 by link 1125 and to echo control 1068 by link 1128. CCM 1120 is linked to STP 1095 by link 1130 and to echo control 1078 by link 1138. The CCMs and associated links are configured to operate as described above with respect to the present invention. In operation, a call would proceed as follows.
Network 1001 would send a call to network 1002. This means switch 1005 would use connection 1015 to connect to network 1002. A signaling message would also be sent over link 1020 through STP 1010 and over link 1025 to network 1002.
Network 1002 would receive the signaling message at STP 1090. The signaling message could be an SS7 ISUP message, and in particular and IAM. STP 1090 would route SS7 ISUP messages from switch 1005 to CCM 1 I IS. It may be the case that the message was actually sent to a component other than CCM 111 S, but was directed to CCM 111 S by network 1002. CCM 111 S would process the IAM. Processing could ' S include validation, call information analysis, and route selection as described above. In turn, this may include POTS calls or calls requiring additional services such as N00, VPN, messaging, or personal/terminal mobility. In this embodiment, CCM 111 S
might select connection 1080 as the route instruction for ATM switch IOSS. An SS7 B-ISUP
IAM would be formulated by CCM I I 1 S and sent to ATM switch l OSS over link through STP 1090 and over link 1105. ATM switch LOSS would accept the route instruction and select the specific VPI/VCI on connection 1080 and generate a B-ISUP
IAM reflecting the selected VPI/VCI. Additionally, the route instruction from CCM
1115 could have identified the actual VPI, and left VCI selection to ATM
switch LOSS.
This IAM from ATM switch LOSS would be routed over link 1 l OS through STP
1S 1090 and over link 1100 to STP 1095. STP 1095 would route this IAM over link 1130 to CCM 1120. CCM 1120 would process the B-ISUP IAM and select network 1003, and in particular, connection 1085 and/or switch 1030 as the route instruction for switch 1060. A B-ISUP IAM would be formulated by CCM 1120 and sent to switch 1060 over link I 130 through STP 1095 and over link I 110. ATM switch 1060 would select the proper VPI/VCI (or possibly only the VCI) on connection 1085 and generate a B-ISUP
message reflecting the selection. This B-ISUP message would be routed over link 1110 through STP 1095 and over link 1130 to CCM 1120. CCM I 120 would process the B-ISUP IAM to create an ISUP M for narrowband switch 1030. The ISUP IAM would be sent to switch 1030 over link 1130, through STP 1095, over link 1050, through STP
2S 1035, and over link 1045. Muxes 1065 and 1070 convert the trafl'tc between narrowband format and ATM format. The CCM tracks these connections through the muxes so it can equate narrow band connections and ATM connections on each side of a given mux.
CCM 1 I I S would check the IAM to determine if the call is a data call. If so, the echo canceller on the selected connection would need disabled. This would be WO 97/09808 PCT/iJS96/14105 accomplished by a message from CCM 1115 to echo control 1068 over link 1128.
The same procedure would occur between CCM 1120 and echo control 1078 over link 1138.
Narrowband switch 1030 will typically produce an address complete message (ACM) to signify the called party is being alerted and an answer message (ANM) to signify the called party has answered. These messages are routed back to network 1002 and to CCM 1120. CCM 1120 and CCM 1115 instruct switches 1055 and 1060 to allow cut-through on the selected connections and will signal network 1001 of the call status. When a party terminates the call, suspend (5U5), release (REL), and release complete (RLC) messages are transmitted by networks 1001 and 1003 as appropriate in order to tear down the call. CCM 1115 and CCM 1120 will process these messages and instruct switch 1055 and switch 1060 to use those VPINCIs for other calls.
At this time each CCM will generate billing information for the call.
The invention provides several advantages over prior systems. The invention is not coupled to a switching matrix and thus, it is not dependent on the capabilities bundled with a switch by the switch provider. The invention does not accept actual user traffc and is not required to have transport capability. However, the invention does accept the signaling that a switch would receive, processes the signaling, and provides a switch with a new signal that incorporates the processing. The processing can implement routing, billing, and special services so the switch does not need to have the capabilities. The processing can also interwork different signaling types so each switch receives signaling in its own format.
Current signaling processors cannot provide these advantages. SCPs process TCAP message queries and do not process call set-up messages sent from a user.
SCPs process queries generated by a switch and respond to that same switch. SCPs must be invoked by a switch and respond to that switch.
Signaling points and their associated switch CPUs are bundled with the switch and the switch CPU is coupled to a switch matrix. The added functionality of this , system increases its cost and reduces its flexibility.
Another proposed signaling processing system is logically segregated according to call, service, connection, and channel. As such, it must rely on a proprietary signaling protocol to communicate among the logically segregated components. This system does not provide 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 appreciate variations that will support the S requirements of the invention. As such, the invention should not be restricted to only the embodiments listed above. The invention should only be defined by the following claims.
Claims (18)
1. A method for operating a communications system (1002) that receives user communications from a connection (1015) and receives a call set-up signaling message from a link (1125), the method characterized by:
in an echo control means, receiving the user communications from the connection (1015), receiving an echo control message over a link means from a signaling processing means, canceling echo in the user communications in response to the echo control message, and transferring the user communications to an asynchronous multiplexer means over a connection means;
in the asynchronous multiplexer means, receiving the user communications over the connection means from the echo control means, converting the user communications into asynchronous communications, and transferring the asynchronous communications over the connection means to an asynchronous routing means;
in the asynchronous routing means, receiving the asynchronous communications over the connection means from the asynchronous multiplexer means, receiving a connection control message over the link means from the signaling processing means, and transferring the asynchronous communications over a selected asynchronous connection in response to the connection control message; and in the signaling processing means that is external to the asynchronous routing means, receiving the call set-up signaling message from the link (1125), processing the call set-up signaling message to select the echo cancellation and the asynchronous connection, generating and transmitting the echo control message over the link means to the echo control means, and generating and transmitting the connection control message over the link means to the asynchronous routing means.
in an echo control means, receiving the user communications from the connection (1015), receiving an echo control message over a link means from a signaling processing means, canceling echo in the user communications in response to the echo control message, and transferring the user communications to an asynchronous multiplexer means over a connection means;
in the asynchronous multiplexer means, receiving the user communications over the connection means from the echo control means, converting the user communications into asynchronous communications, and transferring the asynchronous communications over the connection means to an asynchronous routing means;
in the asynchronous routing means, receiving the asynchronous communications over the connection means from the asynchronous multiplexer means, receiving a connection control message over the link means from the signaling processing means, and transferring the asynchronous communications over a selected asynchronous connection in response to the connection control message; and in the signaling processing means that is external to the asynchronous routing means, receiving the call set-up signaling message from the link (1125), processing the call set-up signaling message to select the echo cancellation and the asynchronous connection, generating and transmitting the echo control message over the link means to the echo control means, and generating and transmitting the connection control message over the link means to the asynchronous routing means.
2. The method of Claim 1 wherein the call set-up signaling message is an initial address message.
3. The method of Claim 2 wherein the processing means receives and processes a release message.
4. The method of Claim 3 wherein the processing means receives and processes an answer message.
5. The method of Claim 4 wherein the processing means receives and processes an address complete message.
6. The method of Claim 5 wherein the processing means receives and processes a release complete message.
7. The method of Claim 1 wherein the processing means processes a called number from the call set-up signaling message to select the asynchronous connection.
g. The method of Claim 1 wherein the processing means processes the call set-up signaling message to validate a call.
9. The method of Claim 1 wherein the processing means generates billing information for the asynchronous communications.
10. A communications system (1002) that receives user communications from a connection (1015) and that receives a call set-up signaling message from a link (1125), the communications system characterized in that:
an echo control means receives the user communications from the connection (1015), receives an echo control message from a signaling processing means, cancels echo in the user communications in response to the echo control message, and transfers the user communications to an asynchronous multiplexer means;
the asynchronous multiplexer means receives the user communications from the echo control means, converts the user communications to an asynchronous routing means;
the asynchronous routing means receives the asynchronous communications from the asynchronous multiplexer means, receives a connection control message from the signaling processing means, and transfers the asynchronous communications over a selected asynchronous connection in response to the connection control message;
the signaling processing means is external to the asynchronous routing means and receives the call set-up signaling message from the link(1125), processes the call set-up signaling message to select the echo cancellation and the asynchronous connection, generates and transmits the echo control message to the echo control means, and generates and transmits the connection control message to the asynchronous routing means;
a connection means from the echo control means to the asynchronous multiplexer means and from the asynchronous multiplexer means to the asynchronous routing means for transferring the communications; and a linking means from the signaling processing means to the echo control means and to the asynchronous routing means for transferring the control messages.
an echo control means receives the user communications from the connection (1015), receives an echo control message from a signaling processing means, cancels echo in the user communications in response to the echo control message, and transfers the user communications to an asynchronous multiplexer means;
the asynchronous multiplexer means receives the user communications from the echo control means, converts the user communications to an asynchronous routing means;
the asynchronous routing means receives the asynchronous communications from the asynchronous multiplexer means, receives a connection control message from the signaling processing means, and transfers the asynchronous communications over a selected asynchronous connection in response to the connection control message;
the signaling processing means is external to the asynchronous routing means and receives the call set-up signaling message from the link(1125), processes the call set-up signaling message to select the echo cancellation and the asynchronous connection, generates and transmits the echo control message to the echo control means, and generates and transmits the connection control message to the asynchronous routing means;
a connection means from the echo control means to the asynchronous multiplexer means and from the asynchronous multiplexer means to the asynchronous routing means for transferring the communications; and a linking means from the signaling processing means to the echo control means and to the asynchronous routing means for transferring the control messages.
11. The communication system of Claim 10 wherein the call set-up signaling message is an initial address message.
12. The communication system of Claim 11 wherein the processor is further configured to receive and process a release message.
13. The communication system of Claim 12 wherein the processor is further configured to receive and process an answer message.
14. The communication system of Claim 13 wherein the processor is further configured to receive and process an address complete message.
15. The communication system of Claim 14 wherein the processor is further configured to receive and process a release complete message.
16. The communication system of Claim 10 wherein the processor is further configured to process a called number from the call set-up signaling message to select the asynchronous connection.
17. The communication system of Claim 10 wherein the processor is further configured to process the call set-up signaling message to validate a call.
18. The communication system of Claim 10 wherein the processor is further configured to generating billing information for the asynchronous communications.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/525,050 US6181703B1 (en) | 1995-09-08 | 1995-09-08 | System for managing telecommunications |
US08/525,050 | 1995-09-08 | ||
PCT/US1996/014105 WO1997009808A1 (en) | 1995-09-08 | 1996-09-03 | System for managing telecommunications |
Publications (2)
Publication Number | Publication Date |
---|---|
CA2231230A1 CA2231230A1 (en) | 1997-03-13 |
CA2231230C true CA2231230C (en) | 2002-11-19 |
Family
ID=24091708
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002231230A Expired - Fee Related CA2231230C (en) | 1995-09-08 | 1996-09-03 | System for managing telecommunications |
Country Status (19)
Country | Link |
---|---|
US (8) | US6181703B1 (en) |
EP (1) | EP0848875B1 (en) |
JP (1) | JP3827329B2 (en) |
KR (1) | KR100319954B1 (en) |
CN (1) | CN1167232C (en) |
AT (1) | ATE283595T1 (en) |
AU (1) | AU701276B2 (en) |
BR (1) | BR9610459A (en) |
CA (1) | CA2231230C (en) |
CZ (1) | CZ299058B6 (en) |
DE (1) | DE69633928T2 (en) |
ES (1) | ES2229282T3 (en) |
HU (1) | HU221399B1 (en) |
NO (1) | NO324343B1 (en) |
NZ (1) | NZ316802A (en) |
PL (1) | PL180330B1 (en) |
RU (1) | RU2144271C1 (en) |
UA (1) | UA51673C2 (en) |
WO (1) | WO1997009808A1 (en) |
Families Citing this family (167)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5926482A (en) * | 1994-05-05 | 1999-07-20 | Sprint Communications Co. L.P. | Telecommunications apparatus, system, and method with an enhanced signal transfer point |
US6031840A (en) | 1995-12-07 | 2000-02-29 | Sprint Communications Co. L.P. | Telecommunications system |
US6430195B1 (en) | 1994-05-05 | 2002-08-06 | Sprint Communications Company L.P. | Broadband telecommunications system interface |
US5920562A (en) * | 1996-11-22 | 1999-07-06 | Sprint Communications Co. L.P. | Systems and methods for providing enhanced services for telecommunication call |
US6631133B1 (en) | 1994-05-05 | 2003-10-07 | Sprint Communications Company L.P. | Broadband telecommunications system |
US6172977B1 (en) | 1994-05-05 | 2001-01-09 | Sprint Communications Company, L. P. | ATM direct access line system |
US6181703B1 (en) | 1995-09-08 | 2001-01-30 | Sprint Communications Company L. P. | System for managing telecommunications |
US5991301A (en) | 1994-05-05 | 1999-11-23 | Sprint Communications Co. L.P. | Broadband telecommunications system |
US20100208634A1 (en) | 1994-10-11 | 2010-08-19 | Arbinet Corporation | System and Method For Managing Multimedia Communications Across Convergent Networks |
GB2305812B (en) * | 1995-09-29 | 1999-09-29 | Northern Telecom Ltd | Providing services in a telecommunications network |
GB9603582D0 (en) * | 1996-02-20 | 1996-04-17 | Hewlett Packard Co | Method of accessing service resource items that are for use in a telecommunications system |
US6041109A (en) * | 1995-12-29 | 2000-03-21 | Mci Communications Corporation | Telecommunications system having separate switch intelligence and switch fabric |
AU2257097A (en) * | 1996-02-02 | 1997-08-22 | Sprint Communications Company, L.P. | Atm gateway system |
US6154445A (en) | 1996-04-18 | 2000-11-28 | Bell Atlantic Network Services, Inc. | Telephony communication via varied redundant networks |
US6069890A (en) | 1996-06-26 | 2000-05-30 | Bell Atlantic Network Services, Inc. | Internet telephone service |
US8547849B2 (en) * | 1996-07-05 | 2013-10-01 | Rockstar Consortium Us Lp | ATM telecommunications systems and method for routing narrow band traffic |
US6115380A (en) * | 1996-11-22 | 2000-09-05 | Sprint Communications Co., L.P. | Broadband telecommunications system |
US6002689A (en) * | 1996-11-22 | 1999-12-14 | Sprint Communications Co. L.P. | System and method for interfacing a local communication device |
HUP0001114A3 (en) * | 1996-11-22 | 2003-01-28 | Sprint Comm Company L P Kansas | System and method for transporting a call in a telecommunication network |
US6014378A (en) | 1996-11-22 | 2000-01-11 | Sprint Communications Company, L.P. | Telecommunications tandem system for circuit-based traffic |
US6667982B2 (en) * | 1996-11-22 | 2003-12-23 | Sprint Communications Company, L.P. | Broadband telecommunications system interface |
US6078582A (en) | 1996-12-18 | 2000-06-20 | Bell Atlantic Network Services, Inc. | Internet long distance telephone service |
SE511581C2 (en) * | 1996-12-20 | 1999-10-25 | Ericsson Telefon Ab L M | System and method for ATM connection of a telephone connection |
EP0859527A1 (en) * | 1997-02-17 | 1998-08-19 | Siemens Aktiengesellschaft | Node supporting links having the ability to transfer longer messages than according to current MTP level 2 |
US6137869A (en) | 1997-09-16 | 2000-10-24 | Bell Atlantic Network Services, Inc. | Network session management |
US6574216B1 (en) | 1997-03-11 | 2003-06-03 | Verizon Services Corp. | Packet data network voice call quality monitoring |
US6870827B1 (en) | 1997-03-19 | 2005-03-22 | Verizon Services Corp. | Voice call alternative routing through PSTN and internet networks |
US6292479B1 (en) | 1997-03-19 | 2001-09-18 | Bell Atlantic Network Services, Inc. | Transport of caller identification information through diverse communication networks |
US6067299A (en) | 1997-04-16 | 2000-05-23 | Sprint Communications Company, L.P. | Communications system for providing ATM connections and echo cancellation |
US6137800A (en) | 1997-05-09 | 2000-10-24 | Sprint Communications Company, L. P. | System and method for connecting a call |
EP0997030B1 (en) * | 1997-07-15 | 2004-11-24 | BRITISH TELECOMMUNICATIONS public limited company | Multimedia call handling |
US6111893A (en) * | 1997-07-31 | 2000-08-29 | Cisco Technology, Inc. | Universal protocol conversion |
US6967972B1 (en) | 1997-07-31 | 2005-11-22 | Cisco Technology, Inc. | Universal protocol conversion |
US7406084B2 (en) * | 1997-09-19 | 2008-07-29 | Nokia Siemens Networks Gmbh & Co. Kg | Flexible software architecture for a call processing system |
US6418461B1 (en) * | 1997-10-06 | 2002-07-09 | Mci Communications Corporation | Intelligent call switching node in an intelligent distributed network architecture |
GB2330271A (en) * | 1997-10-08 | 1999-04-14 | Ericsson Telefon Ab L M | Handling telephone calls |
CA2221546A1 (en) * | 1997-11-19 | 1999-05-19 | Northern Telecom Limited | A telephony system and method of signalling |
GB2331659A (en) * | 1997-11-21 | 1999-05-26 | Ericsson Telefon Ab L M | Resource reservation |
GB2332590B (en) * | 1997-12-16 | 2002-10-09 | Dsc Telecom Lp | Handling of signalling information within a telecommunications system |
US6385196B1 (en) * | 1997-12-16 | 2002-05-07 | Nortel Networks Limited | Communication system architecture and a management control agent and operating protocol therefor |
US6154467A (en) * | 1997-12-30 | 2000-11-28 | Alcatel Usa Sourcing, L.P. | High speed SS7 signaling adaptation device |
US6574222B1 (en) * | 1998-02-20 | 2003-06-03 | Sprint Communications Company, L.P. | System and method for allocating bandwidth for a call |
US7079534B1 (en) | 1998-02-20 | 2006-07-18 | Sprint Communications Company L.P. | System and method for allocating bandwidth for a call |
US6470019B1 (en) | 1998-02-20 | 2002-10-22 | Sprint Communications Company L.P. | System and method for treating a call for call processing |
US6483837B1 (en) * | 1998-02-20 | 2002-11-19 | Sprint Communications Company L.P. | System and method for connecting a call with an interworking system |
US6563918B1 (en) | 1998-02-20 | 2003-05-13 | Sprint Communications Company, LP | Telecommunications system architecture for connecting a call |
US6922409B1 (en) | 1998-02-20 | 2005-07-26 | Sprint Communications Company L.P. | System and method for allocating bandwidth for a call |
US6888820B1 (en) * | 1998-02-20 | 2005-05-03 | Sprint Communications Company L.P. | System and method for treating a call for call processing |
US6546022B1 (en) | 1998-04-03 | 2003-04-08 | Sprint Communications Company, L.P. | Method, system and apparatus for processing information in a telecommunications system |
CA2268563C (en) * | 1998-04-10 | 2004-06-08 | Kabushiki Kaisha Toshiba | Atm transmission equipment |
US6169735B1 (en) * | 1998-04-30 | 2001-01-02 | Sbc Technology Resources, Inc. | ATM-based distributed virtual tandem switching system |
US7222165B1 (en) * | 1998-05-26 | 2007-05-22 | British Telecommunications Plc | Service provision support system |
US6332023B1 (en) * | 1998-06-04 | 2001-12-18 | Mci Communications Corporation | Method of and system for providing services in a communications network |
US6650632B1 (en) | 1998-06-30 | 2003-11-18 | Cisco Technology, Inc. | Feature transparency in a telecommunications network |
FI107857B (en) * | 1998-07-06 | 2001-10-15 | Ericsson Telefon Ab L M | Signaling in a telecommunications network |
US6252870B1 (en) * | 1998-07-22 | 2001-06-26 | Siemens Aktiengesellschaft | Method and adapter device for switching switched connections between time-division-multiplex-oriented components of a communications network via an ATM communications network |
US6560202B1 (en) * | 1998-07-27 | 2003-05-06 | Lucent Technologies Inc. | Control architecture using a multi-layer embedded signal status protocol |
US6229803B1 (en) * | 1998-08-05 | 2001-05-08 | Sprint Communications Co. L.P. | Telecommunications provider agent |
US6600741B1 (en) * | 1999-03-25 | 2003-07-29 | Lucent Technologies Inc. | Large combined broadband and narrowband switch |
WO2000018143A1 (en) * | 1998-09-22 | 2000-03-30 | Swisscom Ag | Method and device for connecting communication networks |
US6570869B1 (en) | 1998-09-30 | 2003-05-27 | Cisco Technology, Inc. | Communicating voice over a packet-switching network |
US6658022B1 (en) | 1998-09-30 | 2003-12-02 | Cisco Technology, Inc. | Signaling protocol for controlling voice calls in a packet switching network |
US7212522B1 (en) | 1998-09-30 | 2007-05-01 | Cisco Technology, Inc. | Communicating voice over a packet-switching network |
US6442169B1 (en) * | 1998-11-20 | 2002-08-27 | Level 3 Communications, Inc. | System and method for bypassing data from egress facilities |
US6614781B1 (en) * | 1998-11-20 | 2003-09-02 | Level 3 Communications, Inc. | Voice over data telecommunications network architecture |
US6707830B1 (en) * | 1998-11-20 | 2004-03-16 | Nortel Networks Limited | Method and system for upgrading a terminal to terminal link in a telecommunication system |
US6614757B1 (en) * | 1998-11-23 | 2003-09-02 | 3Com Corporation | Method of local flow control in an asynchronous transfer mode network utilizing PNNI routing protocol |
US6507649B1 (en) * | 1998-12-18 | 2003-01-14 | Ericsson Inc. | Mechanism and method for distributing ISUP stacks over multiple loosely coupled processors |
US6714217B2 (en) * | 1998-12-18 | 2004-03-30 | Sprint Communication Company, L.P. | System and method for providing a graphical user interface to, for building, and/or for monitoring a telecommunication network |
US6597701B1 (en) * | 1998-12-22 | 2003-07-22 | Sprint Communications Company L.P. | System and method for configuring a local service control point with a call processor in an architecture |
US6888833B1 (en) * | 1998-12-22 | 2005-05-03 | Sprint Communications Company L.P. | System and method for processing call signaling |
US6724765B1 (en) | 1998-12-22 | 2004-04-20 | Sprint Communications Company, L.P. | Telecommunication call processing and connection system architecture |
US6496512B1 (en) * | 1998-12-22 | 2002-12-17 | Sprint Communications Company L.P. | System and method for connecting calls with a time division multiplex matrix |
US6785282B1 (en) | 1998-12-22 | 2004-08-31 | Sprint Communications Company L.P. | System and method for connecting a call with a gateway system |
US6785280B1 (en) * | 1998-12-23 | 2004-08-31 | Ericsson Inc. | Mechanism and method dynamically allocating ATM connections between exchanges |
US6778538B2 (en) * | 1998-12-30 | 2004-08-17 | Nortel Networks Limited | Virtual junctors |
US6804229B2 (en) | 1998-12-30 | 2004-10-12 | Nortel Networks Limited | Multiple node network architecture |
US6885661B1 (en) | 1998-12-30 | 2005-04-26 | Nortel Networks Limited | Private branch exchange built using an ATM Network |
US6768736B1 (en) | 1998-12-30 | 2004-07-27 | Nortel Networks Limited | Using an ATM switch to grow the capacity of a switching stage |
US6788703B2 (en) | 1998-12-30 | 2004-09-07 | Nortel Networks Limited | DS0 on ATM, mapping and handling |
US6940847B1 (en) * | 1999-01-15 | 2005-09-06 | Telefonaktiebolaget Lm Ericsson (Publ) | System and method for providing access to service nodes from entities disposed in an integrated telecommunications network |
US7079530B1 (en) * | 1999-02-25 | 2006-07-18 | Sprint Communications Company L.P. | System and method for caching toll free number information |
US6560226B1 (en) | 1999-02-25 | 2003-05-06 | Sprint Communications Company, L.P. | System and method for caching ported number information |
FI106999B (en) | 1999-04-06 | 2001-05-15 | Nokia Networks Oy | Implementation of signaling in a telecommunications system |
US6690664B1 (en) * | 1999-04-27 | 2004-02-10 | Sprint Communications Company, L.P. | Call center communications system for handling calls to a call center |
US7103068B1 (en) * | 1999-05-04 | 2006-09-05 | Sprint Communication Company L.P. | System and method for configuring bandwidth transmission rates for call connections |
US6895088B1 (en) * | 1999-05-21 | 2005-05-17 | Sprint Communications Company L.P. | System and method for controlling a call processing system |
US6680952B1 (en) | 1999-06-01 | 2004-01-20 | Cisco Technology, Inc. | Method and apparatus for backhaul of telecommunications signaling protocols over packet-switching networks |
US6920214B1 (en) * | 1999-07-01 | 2005-07-19 | Sprint Communications Company L.P. | Telecommunications system with centralized call redirection control logic and speed dial translation logic |
US6775266B1 (en) * | 1999-07-14 | 2004-08-10 | Telefonaktiebolaget Lm Ericsson | Narrowband applications using ATM switching and transport |
US7263092B2 (en) * | 1999-07-14 | 2007-08-28 | Ericsson Inc. | Combining narrowband applications with broadband transport |
US6816483B1 (en) * | 1999-07-16 | 2004-11-09 | Cisco Technology, Inc. | Switched virtual circuit call processing/routing system |
KR100380027B1 (en) * | 1999-07-19 | 2003-04-14 | 주식회사 링프리 | Method for generating advertisement ringback tone and providing voice and text commercial advertisement during communication wait |
CN1197393C (en) * | 1999-09-21 | 2005-04-13 | 西门子公司 | Communications system |
KR100367657B1 (en) * | 1999-09-21 | 2003-01-10 | 가부시키가이샤 엔.티.티.도코모 | Data conversion apparatus, signal, data conversion method, dce, gateway and communication apparatus |
FR2800552B1 (en) * | 1999-10-28 | 2002-05-31 | Cit Alcatel | TELECOMMUNICATION EQUIPMENT |
US6816497B1 (en) * | 1999-11-05 | 2004-11-09 | Sprint Communications Company, L.P. | System and method for processing a call |
US6535599B1 (en) * | 1999-11-08 | 2003-03-18 | Sprint Communications Company, L.P. | System and method for processing ported calls |
US6621815B1 (en) | 1999-11-18 | 2003-09-16 | Sprint Communications Company L.P. | Communication interface system |
NL1013698C2 (en) | 1999-11-30 | 2001-06-01 | Koninkl Kpn Nv | Method, system, converter and switch for communication with asynchronous transmission mode (ATM). |
US6704314B1 (en) | 1999-12-15 | 2004-03-09 | Sprint Communications Company, L.P. | Method and apparatus to control cell substitution |
FI19992720A (en) * | 1999-12-17 | 2001-06-18 | Nokia Networks Oy | Directing a data call over IP connections |
KR100332552B1 (en) * | 1999-12-18 | 2002-04-17 | 서평원 | Hardware Resource Control Structure And Method Of ATM Exchange System |
US6606321B1 (en) * | 1999-12-29 | 2003-08-12 | 3Com Corporation | Method of establishing MPOA shortcut virtual channel connections |
US6836478B1 (en) * | 1999-12-30 | 2004-12-28 | At&T Corp. | Call hold with reminder and information push |
US6570855B1 (en) * | 1999-12-30 | 2003-05-27 | At&T Corp. | Automatic call manager traffic gate feature |
JP3522619B2 (en) * | 2000-01-05 | 2004-04-26 | 株式会社エヌ・ティ・ティ・ドコモ | Transmitter in multi-carrier CDMA transmission system |
US6781954B1 (en) * | 2000-01-12 | 2004-08-24 | Nokia Networks Oy | Transfer of SS7 signalling message contents over packet broadcasting network (LAN) from multiple signalling points to single point (multiple point-to-point) |
US6785377B1 (en) * | 2000-01-19 | 2004-08-31 | Sprint Communications Company L.P. | Data calls using both constant bit rate and variable bit rate connections |
US6931010B2 (en) * | 2000-01-20 | 2005-08-16 | Mci, Inc. | Intelligent network and method for providing voice telephony over ATM and private address translation |
US7110773B1 (en) * | 2000-04-11 | 2006-09-19 | Telecommunication Systems, Inc. | Mobile activity status tracker |
US6556662B1 (en) * | 2000-05-04 | 2003-04-29 | Worldcom, Inc. | Method and apparatus for providing dialed number verification |
KR100365045B1 (en) * | 2000-06-29 | 2002-12-16 | 엘지전자 주식회사 | Apparatus for B-ISDN and N-ISDN layer 3 protocol integrating |
AU2001276906A1 (en) * | 2000-07-14 | 2002-01-30 | Tekelec | Triggerless screening services |
US7076042B1 (en) * | 2000-09-06 | 2006-07-11 | Cisco Technology, Inc. | Processing a subscriber call in a telecommunications network |
WO2003043299A1 (en) * | 2000-09-22 | 2003-05-22 | Santera Systems Inc | System and method for telephony call control |
US6963583B1 (en) * | 2000-09-29 | 2005-11-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Generic call server and method of converting signaling protocols |
US6522629B1 (en) * | 2000-10-10 | 2003-02-18 | Tellicent Inc. | Traffic manager, gateway signaling and provisioning service for all packetized networks with total system-wide standards for broad-band applications including all legacy services |
US6870857B1 (en) * | 2000-10-18 | 2005-03-22 | Sprint Communications Company L.P. | Communication system for dedicated and switched communications |
US6760426B2 (en) | 2001-01-05 | 2004-07-06 | Sprint Communications Company, L.P. | Method and system for handling operator calls in a communication network |
US7133410B2 (en) * | 2001-02-12 | 2006-11-07 | Tellabs Operations, Inc. | Method and system for designing ring-based telecommunications networks |
US20020176378A1 (en) * | 2001-05-22 | 2002-11-28 | Hamilton Thomas E. | Platform and method for providing wireless data services |
US6967933B2 (en) * | 2001-07-12 | 2005-11-22 | Telcordia Technologies, Inc. | Processing multimedia calls in a packet-based network |
DE10147494A1 (en) * | 2001-09-26 | 2003-04-30 | Siemens Ag | Service control as part of the intelligent network concept for packet network connections |
DE10149297A1 (en) * | 2001-10-05 | 2003-04-24 | Siemens Ag | Device for connecting several link sets to switching center in telecommunications network, uses table to convert destination-point codes into originating-point codes |
US7170888B2 (en) * | 2001-11-24 | 2007-01-30 | Lg-Nortel Co., Ltd. | Call control method between a packet network and PSTNs in the next generation network |
US7099449B1 (en) | 2002-01-15 | 2006-08-29 | Sprint Communications Company L.P. | Telecommunication network that provides caller-entered information to multiple call destinations |
US7106847B1 (en) | 2002-01-15 | 2006-09-12 | Sprint Communications Company L.P. | Telecommunication network that provides caller-entered information to a call destination |
US20030177283A1 (en) * | 2002-03-18 | 2003-09-18 | Hamilton Thomas E. | Application program interface |
US7003088B1 (en) | 2002-07-11 | 2006-02-21 | Sprint Communications Company L.P. | Key to correlate a call with call-handling information |
US7298740B2 (en) | 2002-07-11 | 2007-11-20 | Sprint Communications Company L.P. | Centralized service control for a telecommunication system |
US8463947B2 (en) * | 2002-08-28 | 2013-06-11 | Tellabs Operations, Inc. | Method of finding rings for optimal routing of digital information |
US7346709B2 (en) * | 2002-08-28 | 2008-03-18 | Tellabs Operations, Inc. | Methods for assigning rings in a network |
US7099454B1 (en) | 2002-10-22 | 2006-08-29 | Sprint Communications Company L.P. | Caller identification in a communication system |
US7379464B2 (en) * | 2002-11-27 | 2008-05-27 | At&T Bls Intellectual Property, Inc. | Personal digital gateway |
US7263102B2 (en) * | 2002-11-27 | 2007-08-28 | At&T Intellectual Property, Inc. | Multi-path gateway communications device |
US7224698B2 (en) * | 2002-11-27 | 2007-05-29 | Bellsouth Intellectual Property Corporation | Edge side assembler |
US20040125810A1 (en) * | 2002-12-26 | 2004-07-01 | Flynn Eric P. | Method and apparatus for enabling POTS telephony functionality over a network |
US7127055B2 (en) | 2003-02-03 | 2006-10-24 | Sprint Communications Company L.P. | Internationally accessible communications |
US7945035B2 (en) * | 2003-02-28 | 2011-05-17 | Siemens Enterprise Communications, Inc. | Dynamic presence proxy for call sessions |
US7123711B1 (en) | 2003-03-31 | 2006-10-17 | Sprint Communications Company L.P. | Call handling system and method |
US6978002B1 (en) | 2003-05-13 | 2005-12-20 | Sprint Communications Company L.P. | Dynamic routing for a telephone conference call |
US8009572B2 (en) * | 2003-07-16 | 2011-08-30 | Skype Limited | Peer-to-peer telephone system |
US20050018652A1 (en) * | 2003-07-21 | 2005-01-27 | Siemens Information And Communication Networks, Inc. | System and method for proxy gatekeeper in H.323 based IP telephony systems |
US7920684B2 (en) * | 2003-08-11 | 2011-04-05 | Arbinet-Thexchange, Inc. | Method and system for processing call setup messages using call attributes |
US7076050B1 (en) | 2003-08-18 | 2006-07-11 | Sprint Communications Company L.P. | Information correlation system |
US20050123117A1 (en) * | 2003-10-16 | 2005-06-09 | Stockdale Robert S. | Method for providing third-party call control reuse of telephony features |
US7207112B2 (en) * | 2005-01-12 | 2007-04-24 | Wen-Ya Yeh | Combination hairdressing scissor assembly |
US7856094B2 (en) * | 2005-03-21 | 2010-12-21 | Tekelec | Methods, systems, and computer program products for providing telecommunications services between a session initiation protocol (SIP) network and a signaling system 7 (SS7) network |
US8213593B2 (en) | 2005-06-13 | 2012-07-03 | At&T Intellectual Property I, L.P. | Methods, systems, and computer program products for processing a nature of address indicator and/or calling party number to support telecommunication features |
CN1889536A (en) * | 2005-06-27 | 2007-01-03 | 华为技术有限公司 | Processing method for limiting multimedia information center retransmitting times of multimedia information |
CN100563353C (en) * | 2005-06-28 | 2009-11-25 | 华为技术有限公司 | Strengthen the method and the device of the control ability of service control point in communication process |
US8718257B2 (en) | 2006-07-10 | 2014-05-06 | Francesco Ricci | Systems and methods for providing answering services |
TWM308453U (en) * | 2006-08-04 | 2007-03-21 | Dexin Corp | Accommodating and positioning structure of mouse |
RU2455787C2 (en) * | 2007-12-21 | 2012-07-10 | Телефонактиеболагет Лм Эрикссон (Пабл) | Call termination control |
WO2010060082A2 (en) * | 2008-11-24 | 2010-05-27 | Tekelec | Systems. methods, and computer readable media for providing toll-free service in a telecommunications network |
US9712341B2 (en) | 2009-01-16 | 2017-07-18 | Tekelec, Inc. | Methods, systems, and computer readable media for providing E.164 number mapping (ENUM) translation at a bearer independent call control (BICC) and/or session intiation protocol (SIP) router |
US8238538B2 (en) | 2009-05-28 | 2012-08-07 | Comcast Cable Communications, Llc | Stateful home phone service |
KR101702417B1 (en) * | 2009-11-09 | 2017-02-06 | 삼성전자주식회사 | Method and apparatus for monopolizing call session of transmitting/receiving call system using universal plug and play |
US8675851B1 (en) * | 2012-09-14 | 2014-03-18 | Level 3 Communications, Llc | System and method for call routing management in a telecommunication network |
US9363204B2 (en) | 2013-04-22 | 2016-06-07 | Nant Holdings Ip, Llc | Harmonized control planes, systems and methods |
US9516172B2 (en) * | 2014-06-05 | 2016-12-06 | Verizon Patent And Licensing Inc. | Enriching and analyzing CDR data to identify voice traffic routing through an intermediate provider |
US10769212B2 (en) * | 2015-07-31 | 2020-09-08 | Netapp Inc. | Extensible and elastic data management services engine external to a storage domain |
US10826796B2 (en) | 2016-09-26 | 2020-11-03 | PacketFabric, LLC | Virtual circuits in cloud networks |
US10412217B1 (en) * | 2019-04-11 | 2019-09-10 | Republic Wireless, Inc. | Anti-spoofing techniques for outbound telephone calls |
US10375238B1 (en) * | 2019-04-15 | 2019-08-06 | Republic Wireless, Inc. | Anti-spoofing techniques for outbound telephone calls |
CN111600791B (en) * | 2020-06-03 | 2021-11-23 | 中铁二院工程集团有限责任公司 | Converged calling method for broadband and narrowband communication system |
Family Cites Families (272)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4201889A (en) | 1978-03-17 | 1980-05-06 | International Telephone And Telegraph | Distributed control digital switching system |
US4310727A (en) | 1980-02-04 | 1982-01-12 | Bell Telephone Laboratories, Incorporated | Method of processing special service telephone calls |
US4348554A (en) | 1980-03-21 | 1982-09-07 | Bell Telephone Laboratories, Incorporated | Method of providing virtual private network telephone service |
JPS57159192A (en) | 1981-03-27 | 1982-10-01 | Hitachi Ltd | Audio packet exchange system |
US4491945A (en) * | 1982-06-25 | 1985-01-01 | At&T Bell Laboratories | Fast packet switch |
US4565903A (en) | 1983-08-03 | 1986-01-21 | At&T Bell Laboratories | Telephone interexchange carrier selection |
US4554659A (en) | 1983-12-12 | 1985-11-19 | At&T Bell Laboratories | Data communication network |
US4683563A (en) | 1984-10-11 | 1987-07-28 | American Telephone And Telegraph Company, At&T Bell Laboratories | Data communication network |
US4686669A (en) | 1985-02-07 | 1987-08-11 | American Telephone And Telegraph Company, At&T Bell Laboratories | Path hunting in a distributed control switching system |
US4686701A (en) | 1985-02-07 | 1987-08-11 | American Telephone And Telegraph Company, At&T Bell Laboratories | Processing sequence calls in a distributed control switching system |
US4683584A (en) | 1985-02-07 | 1987-07-28 | American Telephone And Telegraph Company, At&T Bell Laboratories | Directory number translation in a distributed control switching system |
US5182550A (en) | 1985-05-31 | 1993-01-26 | Fujitsu Limited | Inter-network connection system |
US4763317A (en) | 1985-12-13 | 1988-08-09 | American Telephone And Telegraph Company, At&T Bell Laboratories | Digital communication network architecture for providing universal information services |
US4730312A (en) * | 1986-02-21 | 1988-03-08 | San/Bar Corporation | Voice, data or both over one telephone line in a T-1 carrier system |
US4736364A (en) | 1986-03-12 | 1988-04-05 | American Telephone And Telegraph Company, At&T Bell Laboratories | Switching system control arrangements |
US4720850A (en) | 1986-03-14 | 1988-01-19 | American Telephone And Telegraph Company At&T Bell Laboratories | Communication system control arrangement |
US4748658A (en) | 1986-07-16 | 1988-05-31 | Bell Communications Research, Inc. | Architecture for allocating resources in a telecommunications network |
ES2025099B3 (en) | 1986-07-23 | 1992-03-16 | Siemens Ag | MODULAR STRUCTURED ISDN COMMUNICATION SYSTEM WITH FORMATION AND ANNOUNCEMENT OF FAULTS TEXTS |
US4757526A (en) | 1987-04-16 | 1988-07-12 | American Telephone And Telegraph Company, At&T Bell Laboratories | Signal transfer arrangement |
BE1000512A7 (en) | 1987-05-07 | 1989-01-10 | Bell Telephone Mfg | Switching network. |
US4823338B1 (en) | 1987-08-03 | 1998-11-10 | At & T Information Systems Inc | Virtual local area network |
US5084816A (en) * | 1987-11-25 | 1992-01-28 | Bell Communications Research, Inc. | Real time fault tolerant transaction processing system |
DE3742939A1 (en) | 1987-12-18 | 1989-07-06 | Standard Elektrik Lorenz Ag | METHOD FOR HYBRID PACKING AND DEVICES THEREFOR |
GB8802533D0 (en) | 1988-02-04 | 1988-03-02 | Plessey Co Plc | Data packet switching |
US4896319A (en) | 1988-03-31 | 1990-01-23 | American Telephone And Telegraph Company, At&T Bell Laboratories | Identification and authentication of end user systems for packet communications network services |
US4866762A (en) * | 1988-04-04 | 1989-09-12 | Pintar Robert R | Apparatus for restricting telephone calls |
US4853955A (en) | 1988-04-27 | 1989-08-01 | Network Access Corporation | Apparatus and method for providing existing telephone switching equipment with the capability of using the SS7 protocol |
US5058104A (en) | 1988-07-26 | 1991-10-15 | Nec Corporation | Tdm demultiplexer with dedicated maintenance channels to indicate high-speed line faults to low speed circuits |
US4991169A (en) * | 1988-08-02 | 1991-02-05 | International Business Machines Corporation | Real-time digital signal processing relative to multiple digital communication channels |
US5089954A (en) | 1988-08-08 | 1992-02-18 | Bell Communications Research, Inc. | Method for handling conversational transactions in a distributed processing environment |
US5101404A (en) | 1988-08-26 | 1992-03-31 | Hitachi, Ltd. | Signalling apparatus for use in an ATM switching system |
JP2865675B2 (en) | 1988-09-12 | 1999-03-08 | 株式会社日立製作所 | Communication network control method |
EP0363499B1 (en) | 1988-09-23 | 1993-11-18 | Siemens Aktiengesellschaft | Method and circuit arrangement for the transmission of voice signals in a broadband communication network |
EP0437422B1 (en) | 1988-09-30 | 1993-11-18 | Siemens Aktiengesellschaft | Communication system for forming virtual annular networks in a fast packet switching network |
US4991172A (en) * | 1988-10-28 | 1991-02-05 | International Business Machines Corporation | Design of a high speed packet switching node |
US5258752A (en) | 1988-11-25 | 1993-11-02 | Sumitomo Electric Industries, Ltd. | Broad band digital exchange |
CA2002613C (en) | 1988-12-05 | 1996-02-27 | Hisao Yamamoto | Adaptive routing control method |
JPH02215247A (en) | 1989-02-16 | 1990-08-28 | Fujitsu Ltd | Communication path selection system |
US5274698A (en) * | 1989-02-28 | 1993-12-28 | Samsung Electronics Co., Ltd. | Method of restricting telephone calls in a private branch exchange system |
US4979118A (en) | 1989-03-10 | 1990-12-18 | Gte Laboratories Incorporated | Predictive access-control and routing system for integrated services telecommunication networks |
DE3912660C1 (en) | 1989-04-18 | 1990-08-30 | Wandel & Goltermann Gmbh & Co, 7412 Eningen, De | |
US5018191A (en) | 1989-10-23 | 1991-05-21 | At&T Bell Laboratories | Special service call routing |
JP2964151B2 (en) | 1989-07-03 | 1999-10-18 | 富士通株式会社 | Communication control method |
DE4020775A1 (en) | 1989-08-09 | 1991-02-14 | Standard Elektrik Lorenz Ag | COUPLING NETWORK AND COUPLING NETWORK MODULE FOR AN ATM SYSTEM |
US5029199A (en) | 1989-08-10 | 1991-07-02 | Boston Technology | Distributed control and storage for a large capacity messaging system |
US4993104A (en) | 1989-08-11 | 1991-02-19 | Rexair, Inc. | Electrical safety interlock and pulse-type reset circuit for a vacuum cleaner system |
US5231631A (en) | 1989-08-15 | 1993-07-27 | At&T Bell Laboratories | Arrangement for regulating traffic in a high speed data network |
JPH03104451A (en) | 1989-09-19 | 1991-05-01 | Fujitsu Ltd | Route changeover system for multi-stage link exchange system |
US5434981A (en) | 1989-09-28 | 1995-07-18 | Rockwell International Corporation | Functionally programmable PCM data analyzer and transmitter for use in telecommunication equipment |
CA1331215C (en) * | 1989-09-29 | 1994-08-02 | Andrew Lazlo Aczel | Resource-decoupled architecture for a telecommunications switching system |
US5048081A (en) | 1989-12-28 | 1991-09-10 | At&T Bell Laboratories | Arrangement for routing packetized messages |
US5086461A (en) | 1990-01-23 | 1992-02-04 | Network Access Corporation | Apparatus and method for providing existing 1ESS and 1AESS telephone switching equipment with the capability of using the SS7 protocol |
JPH03234137A (en) | 1990-02-08 | 1991-10-18 | Fujitsu Ltd | Signaling cell switching method and signaling cell switching system |
US5095505A (en) * | 1990-02-28 | 1992-03-10 | Mci Communications Corp. | Efficient flexible special service call processing |
JP2957223B2 (en) | 1990-03-20 | 1999-10-04 | 富士通株式会社 | Load distribution control method for call processor |
JPH03270342A (en) | 1990-03-20 | 1991-12-02 | Fujitsu Ltd | Atm communication network |
CA2038646C (en) | 1990-03-20 | 1995-02-07 | Katsumi Oomuro | Atm communication system with optimal traffic control by changing the allocated bandwidth |
ATE127988T1 (en) | 1990-03-23 | 1995-09-15 | Siemens Ag | METHOD FOR SETTING UP VIRTUAL CONNECTIONS IN EXCHANGE FACILITIES WORKING IN AN ASYNCHRONOUS TRANSFER MODE. |
US5115427A (en) | 1990-03-30 | 1992-05-19 | At&T Bell Laboratories | Arrangements for switching multiple packet types combined in a single packet stream |
US5115426A (en) * | 1990-03-30 | 1992-05-19 | At&T Bell Laboratories | Broadband isdn packet switching arrangements |
US5003584A (en) * | 1990-04-16 | 1991-03-26 | At&T Bell Laboratories | Method and apparatus for the billing of value-added communication calls |
JP2555907B2 (en) | 1990-05-23 | 1996-11-20 | 日本電気株式会社 | Complex network address routing control system |
US5214688A (en) | 1990-06-05 | 1993-05-25 | Inventions, Inc. | Method and apparatus for dynamic and interdependent processing of inbound calls and outbound calls |
WO1992000642A1 (en) | 1990-06-26 | 1992-01-09 | Australian And Overseas Telecommunications Corporation Limited | Enhanced telephony apparatus and system |
US5231633A (en) | 1990-07-11 | 1993-07-27 | Codex Corporation | Method for prioritizing, selectively discarding, and multiplexing differing traffic type fast packets |
EP0810806A3 (en) | 1990-07-26 | 2001-04-11 | Nec Corporation | Method of transmitting a plurality of asynchronous cells |
JP2878805B2 (en) | 1990-08-20 | 1999-04-05 | 株式会社東芝 | ATM switch |
JPH04100342A (en) | 1990-08-20 | 1992-04-02 | Toshiba Corp | Traffic control system |
US5115431A (en) | 1990-09-28 | 1992-05-19 | Stratacom, Inc. | Method and apparatus for packet communications signaling |
US5335266A (en) * | 1990-10-01 | 1994-08-02 | United States Advance Network, Inc. | Automated telecommunication peripheral system |
US5193110A (en) | 1990-10-09 | 1993-03-09 | Boston Technology, Incorporated | Integrated services platform for telephone communication system |
US5453981A (en) | 1990-10-16 | 1995-09-26 | Kabushiki Kaisha Toshiba | Method of controlling communication network incorporating virtual channels exchange nodes and virtual paths exchange nodes |
JP3001953B2 (en) | 1990-10-20 | 2000-01-24 | 富士通株式会社 | Virtual identifier conversion device |
US5255266A (en) | 1990-10-20 | 1993-10-19 | Fujitsu Limited | ATM switching unit |
EP0482989B1 (en) | 1990-10-22 | 1997-07-09 | Canon Kabushiki Kaisha | Telephone exchange apparatus |
JPH04180324A (en) | 1990-11-15 | 1992-06-26 | Oki Electric Ind Co Ltd | Atm node system |
US5278972A (en) * | 1990-11-21 | 1994-01-11 | At&T Bell Laboratories | Communication system for converting ISDN signaling protocol between local and public network having first group of mandatory elements and second group of non-mandatory elements |
FR2669798B1 (en) | 1990-11-23 | 1994-09-16 | Lmt Radio Professionelle | DEVICE FOR TRANSMITTING SYNCHRONOUS INFORMATION OVER AN ASYNCHRONOUS NETWORK, ESPECIALLY AN ATM NETWORK. |
JP2890348B2 (en) | 1990-11-30 | 1999-05-10 | 富士通株式会社 | Telephone subscriber accommodation in broadband networks. |
US6847611B1 (en) | 1990-12-10 | 2005-01-25 | At&T Corp. | Traffic management for frame relay switched data service |
JP2679500B2 (en) * | 1990-12-17 | 1997-11-19 | モトローラ・インコーポレイテッド | Method for calculating overall system yield |
US5163087A (en) * | 1990-12-31 | 1992-11-10 | At&T Bell Laboratories | Delivery of customer data base key using automatic number identification |
US5136636A (en) * | 1991-02-07 | 1992-08-04 | At&T Bell Laboratories | Telephone connection to a nearby dealer |
JP2680198B2 (en) * | 1991-02-08 | 1997-11-19 | 三菱電機株式会社 | Audio digital 1-link connection system |
WO1992016066A1 (en) | 1991-02-28 | 1992-09-17 | Stratacom, Inc. | Method and apparatus for routing cell messages using delay |
JPH04276942A (en) | 1991-03-05 | 1992-10-02 | Fujitsu Ltd | Setting system for logic channel in atm network |
JP2770592B2 (en) | 1991-03-20 | 1998-07-02 | 日本電気株式会社 | switch |
US5218602A (en) | 1991-04-04 | 1993-06-08 | Dsc Communications Corporation | Interprocessor switching network |
US5168492A (en) | 1991-04-11 | 1992-12-01 | Northern Telecom Limited | Rotating-access ATM-STM packet switch |
US5251255A (en) | 1991-04-17 | 1993-10-05 | At&T Bell Laboratories | Processing interactions among telecommunications call features |
JPH05122391A (en) * | 1991-05-08 | 1993-05-18 | Fujitsu Ltd | Information collection service system |
JP2938611B2 (en) | 1991-05-14 | 1999-08-23 | 富士通株式会社 | TV signal exchange system |
US5506894A (en) | 1991-06-03 | 1996-04-09 | At&T Corp. | System for processing calling party information for international communications services |
US5282244A (en) | 1991-06-24 | 1994-01-25 | At&T Bell Laboratories | Virtual signaling network method |
US5291479A (en) | 1991-07-16 | 1994-03-01 | Digital Technics, Inc. | Modular user programmable telecommunications system with distributed processing |
US5765108A (en) | 1991-07-31 | 1998-06-09 | Telstra Corporation Limited | Telecommunications system |
US5179556A (en) | 1991-08-02 | 1993-01-12 | Washington University | Bandwidth management and congestion control scheme for multicast ATM networks |
JP3051210B2 (en) * | 1991-08-05 | 2000-06-12 | 富士通株式会社 | Test method for ATM multiplex transmission equipment |
US5146491A (en) * | 1991-08-08 | 1992-09-08 | Pilgrim Telephone, Inc. | Telephone billing method |
US5490251A (en) | 1991-08-09 | 1996-02-06 | First Data Resources Inc. | Method and apparatus for transmitting data over a signalling channel in a digital telecommunications network |
US5327433A (en) | 1991-08-30 | 1994-07-05 | Adtran Corporation | Digital tandem channel unit interface for telecommunications network |
FR2681164A1 (en) | 1991-09-06 | 1993-03-12 | Thomson Csf | Process for routing a data packet within a digital transmission network |
HUT62831A (en) | 1991-09-12 | 1993-06-28 | Gen Electric | Method for producing covered cubed leather-nitride abrasive grain, abrasive grain and grinding tool by using the same |
DE69129851T2 (en) | 1991-09-13 | 1999-03-25 | Ibm | Configurable gigabit / s switch adapter |
CA2078246C (en) * | 1991-09-23 | 1998-02-03 | Randolph J. Pilc | Improved method for secure access control |
JPH05122240A (en) | 1991-10-24 | 1993-05-18 | Fujitsu Ltd | Vpi vci allocation system in atm transmission |
US5291492A (en) | 1991-12-18 | 1994-03-01 | Unifi Communications Corporation | Externally controlled call processing system |
JPH05168073A (en) | 1991-12-19 | 1993-07-02 | Mitsubishi Electric Corp | Device for inserting and extracting common line signal |
US5367566A (en) | 1991-12-27 | 1994-11-22 | At&T Corp. | Common channel signaling message intercept system |
US5289472A (en) | 1992-02-05 | 1994-02-22 | At&T Bell Laboratories | Method for the tranmission of message associated user-to-user information |
US5295137A (en) | 1992-02-12 | 1994-03-15 | Sprint International Communications Corp. | Connection establishment in a flat distributed packet switch architecture |
US5357510A (en) | 1992-02-19 | 1994-10-18 | Fujitsu Limited | Apparatus and a method for supervising and controlling ATM traffic |
US5375124A (en) * | 1992-02-20 | 1994-12-20 | At&T Corp. | Method and apparatus for providing ISDN access |
JPH05236024A (en) | 1992-02-20 | 1993-09-10 | Nec Corp | Intelligent network data transfer system |
JPH05236138A (en) | 1992-02-20 | 1993-09-10 | Nec Corp | Electronic exchange |
US5701419A (en) * | 1992-03-06 | 1997-12-23 | Bell Atlantic Network Services, Inc. | Telecommunications service creation apparatus and method |
US5452350A (en) * | 1992-03-09 | 1995-09-19 | Advantis | Subscriber call routing processing system |
US5285441A (en) | 1992-03-17 | 1994-02-08 | At&T Bell Laboratories | Errorless line protection switching in asynchronous transer mode (ATM) communications systems |
US5400339A (en) | 1992-03-18 | 1995-03-21 | Fujitsu Limited | Bidirectional communication apparatus for reducing transmitted data |
JPH05292114A (en) | 1992-04-09 | 1993-11-05 | Fujitsu Ltd | Communication path setting device and its method |
US5345443A (en) | 1992-04-30 | 1994-09-06 | At&T Bell Laboratories | Network-based digital bandwidth-on-demand |
US5329578A (en) * | 1992-05-26 | 1994-07-12 | Northern Telecom Limited | Personal communication service with mobility manager |
US5329308A (en) | 1992-07-29 | 1994-07-12 | At&T Bell Laboratories | Bidirectional video telephony between cable television and switched telephone systems |
FR2694466B1 (en) | 1992-07-29 | 1994-09-02 | Cit Alcatel | Telecommunication network carrying out call processing and connection processing separately. |
US5278889A (en) | 1992-07-29 | 1994-01-11 | At&T Bell Laboratories | Video telephony dialing |
US5588048A (en) * | 1992-07-31 | 1996-12-24 | 800 Adept, Inc. | Geographically mapped telephone routing method and system |
US5805689A (en) * | 1992-07-31 | 1998-09-08 | 800 Adept, Inc. | Geographically mapped telephone routing method and system |
US5323389A (en) | 1992-08-14 | 1994-06-21 | Fore Systems, Inc. | ATM cell interface and method for dispatching an ATM cell |
JP2839714B2 (en) | 1992-08-25 | 1998-12-16 | シーメンス アクチエンゲゼルシヤフト | Switching system with call processing system for connection control |
ATE162034T1 (en) | 1992-08-28 | 1998-01-15 | Siemens Ag | METHOD AND CIRCUIT ARRANGEMENT FOR TRANSMITTING MESSAGE CELLS WITHIN AN ATM NETWORK |
JP3305769B2 (en) * | 1992-09-18 | 2002-07-24 | 株式会社東芝 | Communication device |
US5850599A (en) * | 1992-09-25 | 1998-12-15 | Ecs Enhanced Cellular Systems Manufacturing Inc. | Portable cellular telephone with credit card debit system |
JPH06169320A (en) | 1992-10-02 | 1994-06-14 | Toshiba Corp | Atm cell making device |
US5384840A (en) | 1992-10-09 | 1995-01-24 | At&T Corp. | Telecommunications system SS7 signaling interface with signal transfer capability |
US5519707A (en) | 1992-10-13 | 1996-05-21 | Synoptics Communications, Inc. | Multiplexing of communications services on a virtual service path in an ATM network or the like |
JPH06132972A (en) | 1992-10-20 | 1994-05-13 | Fujitsu Ltd | Broad band isdn remote multiplexer |
CA2104753C (en) | 1992-10-29 | 1999-02-16 | Kotikalapudi Sriram | Bandwidth allocation, transmission scheduling, and congestion avoidance in broadband atm networks |
US5327421A (en) | 1992-11-06 | 1994-07-05 | At&T Bell Laboratories | Apparatus for interfacing between telecommunications call signals and broadband signals |
US5345445A (en) | 1992-11-06 | 1994-09-06 | At&T Bell Laboratories | Establishing telecommunications calls in a broadband network |
US5365524A (en) | 1992-11-06 | 1994-11-15 | At&T Bell Laboratories | Establishing telecommunications call paths between clustered switching entities |
US5345446A (en) | 1992-11-06 | 1994-09-06 | At&T Bell Laboratories | Establishing telecommunications call paths in broadband communication networks |
JPH07107990B2 (en) | 1992-11-12 | 1995-11-15 | 日本電気株式会社 | ATM-based transmitter and communication system |
US5274635A (en) * | 1992-11-18 | 1993-12-28 | Stratacom, Inc. | Method and apparatus for aligning a digital communication data stream across a cell network |
KR960003505B1 (en) | 1992-12-29 | 1996-03-14 | 재단법인 한국전자통신연구소 | Atm multiplexing processor |
US5394463A (en) * | 1992-12-31 | 1995-02-28 | At&T Corp. | Telephone call processing arrangement based on calling and called party telephone services |
US5499290A (en) | 1993-01-28 | 1996-03-12 | Bellsouth Corporation | AIN non-call associated signalling for service nodes and service control points in a telephone system |
US5506897C1 (en) * | 1993-02-22 | 2001-12-11 | Murex Securities Ltd | Automatic routing system for telephonic services |
JPH06276214A (en) * | 1993-03-18 | 1994-09-30 | Hitachi Ltd | Stm/atm signal mixture processing method and switching system |
JPH077524A (en) | 1993-04-06 | 1995-01-10 | Siemens Ag | Method for accessing of communication subscriber to address identifier |
CA2114274C (en) * | 1993-04-21 | 1997-12-02 | Michael L. Bridges | Information services platform |
US5420858A (en) | 1993-05-05 | 1995-05-30 | Synoptics Communications, Inc. | Method and apparatus for communications from a non-ATM communication medium to an ATM communication medium |
JPH06335079A (en) | 1993-05-19 | 1994-12-02 | Fujitsu Ltd | Cell multiplexer in atm network |
US5539884A (en) | 1993-05-20 | 1996-07-23 | Bell Communications Research, Inc. | Intelligent broadband communication system and method employing fast-packet switches |
JP2518515B2 (en) | 1993-05-27 | 1996-07-24 | 日本電気株式会社 | High-speed connection setup packet switch |
US5673262A (en) | 1993-06-03 | 1997-09-30 | Nec Corporation | Communication network comprising transit switches without asynchronous transfer mode switching capability |
JP2508594B2 (en) | 1993-06-18 | 1996-06-19 | 日本電気株式会社 | A method for selecting a called side device in the ISDN packet switching mode |
US5473677A (en) | 1993-06-23 | 1995-12-05 | At&T Corp. | Telecommunications network architecture and system |
CA2124379C (en) | 1993-06-25 | 1998-10-27 | Thomas F. La Porta | Distributed processing architecture for control of broadband and narrowband communications networks |
ES2137960T3 (en) | 1993-06-25 | 2000-01-01 | Siemens Ag | PROCEDURE FOR ESTABLISHING VIRTUAL COMMUNICATIONS IN PACKET SWITCHING NETWORKS. |
US5509010A (en) | 1993-06-25 | 1996-04-16 | At&T Corp. | Communications signaling protocols |
US5701301A (en) | 1993-06-28 | 1997-12-23 | Bellsouth Corporation | Mediation of open advanced intelligent network in SS7 protocol open access environment |
US5392402A (en) | 1993-06-29 | 1995-02-21 | Bell Communications Research, Inc. | Broadband intelligent telecommunications network and method employing a resource system to support network services |
US5377186A (en) * | 1993-07-21 | 1994-12-27 | Telefonaktiebolaget L M Ericsson | System for providing enhanced subscriber services using ISUP call-setup protocol |
US5384771A (en) | 1993-08-27 | 1995-01-24 | At&T Corp. | Multimedia call configuration system |
CA2131234A1 (en) * | 1993-09-02 | 1995-03-03 | Karl M. Lewis | Technique for providing an improved signaling network for telephone systems |
NL9301544A (en) * | 1993-09-07 | 1995-04-03 | Nederland Ptt | Method for selecting connections in networks, and networks in which the method is applied. |
US5444713A (en) | 1993-09-14 | 1995-08-22 | At&T Corp. | Telephone information service system using digital and out-of-band signaling |
GB9319449D0 (en) | 1993-09-21 | 1993-11-03 | Plessey Telecomm | Telecommunications switching |
US5600643A (en) | 1993-09-23 | 1997-02-04 | Bell Communications Research, Inc. | Broadband intelligent telecommunications network and method providing enhanced capabilities for customer premises equipment |
DE4332824C1 (en) | 1993-09-27 | 1995-03-16 | Siemens Ag | Method and circuit arrangement for transmitting message cells over virtual paths of an ATM communication system |
US5479495A (en) | 1993-10-01 | 1995-12-26 | U S West Advanced Technologies, Inc. | Method and system for automatically accessing and invoking switch-based services in an advanced intelligent network |
US5440563A (en) | 1993-10-12 | 1995-08-08 | At&T Corp. | Service circuit allocation in large networks |
US5495484A (en) | 1993-10-12 | 1996-02-27 | Dsc Communications Corporation | Distributed telecommunications switching system |
EP0649234B1 (en) | 1993-10-14 | 2001-09-19 | International Business Machines Corporation | Method and apparatus of transferring data in an ATM network |
US5590181A (en) | 1993-10-15 | 1996-12-31 | Link Usa Corporation | Call-processing system and method |
ATE230190T1 (en) * | 1993-10-28 | 2003-01-15 | Maldes Phoenix Ltd | LOCKING DEVICE FOR A TELEPHONE SYSTEM |
US5519690A (en) * | 1993-11-08 | 1996-05-21 | Hitachi, Ltd. | Communication control apparatus having function for limiting frame reception and switching system with the same |
US5454034A (en) | 1993-11-23 | 1995-09-26 | At&T Corp. | Arrangement for sharing a telephone office code |
US5440626A (en) * | 1993-11-23 | 1995-08-08 | At&T Corp. | Arrangement for sharing a telephone office code |
CA2110643C (en) | 1993-12-03 | 1997-07-08 | Deborah L. Pinard | Method of telephone signalling via data link |
US5425090A (en) | 1993-12-07 | 1995-06-13 | Bell Communications Research, Inc. | System and method for providing advanced intelligent network services |
DE4341888C1 (en) | 1993-12-08 | 1995-04-06 | Siemens Ag | Method for controlling components of a communications system |
US5473679A (en) | 1993-12-09 | 1995-12-05 | At&T Corp. | Signaling system for broadband communications networks |
US5563939A (en) | 1993-12-09 | 1996-10-08 | At&T | Method and system for delivering a communication service |
US5422882A (en) | 1993-12-20 | 1995-06-06 | At&T Corp. | ATM networks for narrow band communications |
US5452297A (en) | 1993-12-20 | 1995-09-19 | At&T Corp. | Access switches for large ATM networks |
US5428607A (en) | 1993-12-20 | 1995-06-27 | At&T Corp. | Intra-switch communications in narrow band ATM networks |
US5426636A (en) | 1993-12-20 | 1995-06-20 | At&T Corp. | ATM distribution networks for narrow band communications |
US5457684A (en) | 1993-12-21 | 1995-10-10 | At&T Ipm Corp. | Delay-less signal processing arrangement for use in an ATM network |
US5438570A (en) | 1993-12-29 | 1995-08-01 | Tekno Industries, Inc. | Service observing equipment for signalling System Seven telephone network |
US5526359A (en) | 1993-12-30 | 1996-06-11 | Dsc Communications Corporation | Integrated multi-fabric digital cross-connect timing architecture |
US5428609A (en) | 1994-01-03 | 1995-06-27 | At&T Corp. | STM-to-ATM converters |
JP3386547B2 (en) | 1994-01-26 | 2003-03-17 | 株式会社東芝 | Redundancy circuit device |
US5522042A (en) | 1994-01-28 | 1996-05-28 | Cabletron Systems, Inc. | Distributed chassis agent for distributed network management |
US5485455A (en) | 1994-01-28 | 1996-01-16 | Cabletron Systems, Inc. | Network having secure fast packet switching and guaranteed quality of service |
US5533115A (en) * | 1994-01-31 | 1996-07-02 | Bell Communications Research, Inc. | Network-based telephone system providing coordinated voice and data delivery |
DE69530534T2 (en) | 1994-02-25 | 2004-03-18 | Hewlett-Packard Co. (N.D.Ges.D.Staates Delaware), Palo Alto | Message receiving circuit for a signaling network |
US5544163A (en) | 1994-03-08 | 1996-08-06 | Excel, Inc. | Expandable telecommunications system |
US5509123A (en) | 1994-03-22 | 1996-04-16 | Cabletron Systems, Inc. | Distributed autonomous object architectures for network layer routing |
CA2145017C (en) | 1994-03-31 | 2000-02-15 | Masaru Murakami | Cell multiplexer having cell delineation function |
JPH07297830A (en) | 1994-04-21 | 1995-11-10 | Mitsubishi Electric Corp | Multiplexer, non-multiplexer, switching device, and network adapter |
US5991301A (en) | 1994-05-05 | 1999-11-23 | Sprint Communications Co. L.P. | Broadband telecommunications system |
US6181703B1 (en) | 1995-09-08 | 2001-01-30 | Sprint Communications Company L. P. | System for managing telecommunications |
US5926482A (en) | 1994-05-05 | 1999-07-20 | Sprint Communications Co. L.P. | Telecommunications apparatus, system, and method with an enhanced signal transfer point |
US5703876A (en) | 1994-05-05 | 1997-12-30 | Christie; Joseph Michael | ATM transport system |
DE69533831T2 (en) * | 1994-05-05 | 2005-04-21 | Sprint Communications Co | METHOD, SYSTEM AND TRANSMISSION CONTROL DEVICE |
US6314103B1 (en) * | 1994-05-05 | 2001-11-06 | Sprint Communications Company, L.P. | System and method for allocating bandwidth for a call |
FI98683C (en) * | 1994-05-09 | 1997-07-25 | Helsingin Puhelin Oy | Procedure for control of telephone exchange centers |
US5506844A (en) | 1994-05-20 | 1996-04-09 | Compression Labs, Inc. | Method for configuring a statistical multiplexer to dynamically allocate communication channel bandwidth |
US5592537A (en) * | 1994-05-20 | 1997-01-07 | Moen; Arthur J. | Method of providing message service for limited access telecommunications |
US5533106A (en) | 1994-06-27 | 1996-07-02 | Us West Technologies, Inc. | Method and system for processing calls wherein the display of calling party ID information has been inhibited |
US5459722A (en) | 1994-06-30 | 1995-10-17 | At&T Ipm Corp. | Asynchronous transfer mode (ATM) transport of voice-band signals |
CA2127521C (en) | 1994-07-06 | 2002-02-05 | Kenneth M. Buckland | Method and apparatus for recovering a variable bit rate service clock |
CA2153281C (en) * | 1994-07-08 | 2000-05-16 | Ronald Schwartz | Mediated access to an intelligent network |
US5414701A (en) | 1994-07-22 | 1995-05-09 | Motorola, Inc. | Method and data structure for performing address compression in an asynchronous transfer mode (ATM) system |
US5689550A (en) * | 1994-08-08 | 1997-11-18 | Voice-Tel Enterprises, Inc. | Interface enabling voice messaging systems to interact with communications networks |
JP2812205B2 (en) | 1994-08-12 | 1998-10-22 | 日本電気株式会社 | D channel packet communication system |
US5592477A (en) | 1994-09-12 | 1997-01-07 | Bell Atlantic Network Services, Inc. | Video and TELCO network control functionality |
US5621728A (en) | 1994-09-12 | 1997-04-15 | Bell Atlantic Network Services, Inc. | Level 1 gateway controlling broadband communications for video dial tone networks |
US5541917A (en) | 1994-09-12 | 1996-07-30 | Bell Atlantic | Video and TELCO network control functionality |
US5621727A (en) | 1994-09-16 | 1997-04-15 | Octel Communications Corporation | System and method for private addressing plans using community addressing |
US5566173A (en) | 1994-10-12 | 1996-10-15 | Steinbrecher Corporation | Communication system |
US5550909A (en) * | 1994-10-14 | 1996-08-27 | At & T Corp. | International toll-free calling process |
JPH08125591A (en) | 1994-10-20 | 1996-05-17 | Fujitsu Ltd | Echo canceller system |
US5526414A (en) | 1994-10-26 | 1996-06-11 | Northern Telecom Limited | Dynamically controlled routing using virtual nodes |
US5563933A (en) * | 1994-11-02 | 1996-10-08 | At&T | Method and apparatus for facilitating the completing of telephone regional toll-free calls from outside the region |
FI99187C (en) | 1994-11-24 | 1997-10-10 | Tecnomen Oy | A method and apparatus for adding intelligent functions to a telecommunications network |
US5530724A (en) | 1994-11-29 | 1996-06-25 | At&T Corp. | Echo canceler with automatic enablement/disablement on a per-call basis |
CA2159392C (en) * | 1994-12-07 | 1999-09-07 | David B. Smith | Notification of toll free call charging status |
JPH08172659A (en) | 1994-12-19 | 1996-07-02 | Nec Corp | Mobile communication system |
US5568475A (en) | 1994-12-21 | 1996-10-22 | Lucent Technologies Inc. | ATM network architecture employing an out-of-band signaling network |
US5483527A (en) | 1994-12-21 | 1996-01-09 | At&T Corp. | Terminal adapter for interfacing an ATM network with a STM network |
US6324179B1 (en) * | 1994-12-21 | 2001-11-27 | Lucent Technologies Inc. | ATM network arranged to interface with STM in-band signaling |
JP2921424B2 (en) * | 1995-01-13 | 1999-07-19 | 日本電気株式会社 | ATM electronic exchange network system and electronic exchange used in the system |
DE19502414C1 (en) | 1995-01-26 | 1996-02-08 | Siemens Ag | Rapid through switching of virtual connections in ATM communication system |
US5541918A (en) | 1995-01-31 | 1996-07-30 | Fore Systems, Inc. | Method and apparatus for manipulating an ATM cell |
US5627836A (en) | 1995-01-31 | 1997-05-06 | Bell Atlantic Network Services, Inc. | VPI/VCI administration |
US5539815A (en) | 1995-02-24 | 1996-07-23 | At&T Corp. | Network call routing controlled by a management node |
US5623491A (en) | 1995-03-21 | 1997-04-22 | Dsc Communications Corporation | Device for adapting narrowband voice traffic of a local access network to allow transmission over a broadband asynchronous transfer mode network |
US5544161A (en) | 1995-03-28 | 1996-08-06 | Bell Atlantic Network Services, Inc. | ATM packet demultiplexer for use in full service network having distributed architecture |
US5666399A (en) * | 1995-03-31 | 1997-09-09 | Lucent Technologies Inc. | Software architecture for providing communication features to different types of wireless telephones via different communication switching systems |
US5635980A (en) | 1995-04-04 | 1997-06-03 | Bell Communications Research, Inc. | System and method for customer premises broadband interface with on-hook alerting |
US5706286A (en) * | 1995-04-19 | 1998-01-06 | Mci Communications Corporation | SS7 gateway |
US5640446A (en) | 1995-05-01 | 1997-06-17 | Mci Corporation | System and method of validating special service calls having different signaling protocols |
JPH08307423A (en) | 1995-05-08 | 1996-11-22 | Fujitsu Ltd | Format conversion communication method and format conversion device |
EP0742677A3 (en) * | 1995-05-08 | 1999-09-15 | Fujitsu Limited | Header converting method |
US5680390A (en) | 1995-06-06 | 1997-10-21 | Bell Communications Research, Inc. | Broadband telecommunications network and method of having operations systems support |
US5577039A (en) | 1995-06-07 | 1996-11-19 | Samsung Electronics, Inc. | System and method of signal transmission within a plesiochronous digital hierarchy unit using ATM adaptation layers |
US5619561A (en) * | 1995-06-22 | 1997-04-08 | Reese; Morris | Call-waiting and caller identification with three-way conversations arrangements |
DE19523986A1 (en) | 1995-06-30 | 1997-01-02 | Siemens Ag | ATM communication network |
US5689555A (en) * | 1995-06-30 | 1997-11-18 | Siemens Stromberg-Carlson | Method for transferring a subscriber to a new local service provider |
US5970131A (en) | 1995-06-30 | 1999-10-19 | Siemens Information And Communication Networks, Inc. | Method for providing location/geographic portability in a system having different service providers within a common numbering plan area |
WO1997002685A1 (en) | 1995-07-03 | 1997-01-23 | Nippon Telegraph And Telephone Corporation | Variable band communication network |
AU6501496A (en) | 1995-07-19 | 1997-02-18 | Ascom Nexion Inc. | Point-to-multipoint transmission using subqueues |
US5708702A (en) | 1995-07-28 | 1998-01-13 | Bell Atlantic Network Services, Inc. | Dynamic STP routing in response to triggering |
US5636210A (en) | 1995-08-02 | 1997-06-03 | Agrawal; Jagannath P. | Asynchronous transfer mode packet switch |
US5610910A (en) * | 1995-08-17 | 1997-03-11 | Northern Telecom Limited | Access to telecommunications networks in multi-service environment |
US5680446A (en) * | 1995-08-24 | 1997-10-21 | Southwestern Bell Technology Resources, Inc. | Advanced intelligent network screening |
JPH0964987A (en) | 1995-08-30 | 1997-03-07 | Fujitsu Ltd | Signal station congestion control system |
US5661725A (en) | 1995-09-12 | 1997-08-26 | At&T | Trunk-conditioning for reconfigurable T1 access to nodal services |
DE19534754C1 (en) * | 1995-09-19 | 1996-11-07 | Siemens Ag | Narrowband cable bundle exchange method |
US5629930A (en) | 1995-10-31 | 1997-05-13 | Northern Telecom Limited | Call routing in an ATM switching network |
JP3444068B2 (en) | 1995-12-21 | 2003-09-08 | 株式会社日立製作所 | Mobile communication network and communication control method |
US5867571A (en) | 1996-02-23 | 1999-02-02 | Lucent Technologies Inc. | Method and arrangement for establishing call connections in a telecommunications network using a virtual transport server |
US5710769A (en) | 1996-02-29 | 1998-01-20 | Lucent Technologies Inc. | Merging the functions of switching and cross connect in telecommunications networks |
US5848128A (en) | 1996-02-29 | 1998-12-08 | Lucent Technologies Inc. | Telecommunications call preservation in the presence of control failure |
US5940393A (en) * | 1996-05-28 | 1999-08-17 | Sprint Communications Co. L.P. | Telecommunications system with a connection processing system |
US5751706A (en) | 1996-06-05 | 1998-05-12 | Cignal Global Communications, Inc. | System and method for establishing a call telecommunications path |
US5818919A (en) | 1996-07-15 | 1998-10-06 | At&T Corp. | Inter-network call forwarding with subscriber identity |
US5867570A (en) | 1996-07-29 | 1999-02-02 | Northern Telecom Limited | Directory number portability in telephone networks |
US5854836A (en) | 1996-10-25 | 1998-12-29 | Bellsouth Corporation | Method and system for utilizing an information delivery service in a local number portability environment |
US6115380A (en) * | 1996-11-22 | 2000-09-05 | Sprint Communications Co., L.P. | Broadband telecommunications system |
-
1995
- 1995-09-08 US US08/525,050 patent/US6181703B1/en not_active Expired - Lifetime
-
1996
- 1996-02-02 US US08/594,660 patent/US6081525A/en not_active Expired - Lifetime
- 1996-03-09 UA UA98041752A patent/UA51673C2/en unknown
- 1996-09-03 AU AU69117/96A patent/AU701276B2/en not_active Ceased
- 1996-09-03 JP JP51132897A patent/JP3827329B2/en not_active Expired - Lifetime
- 1996-09-03 HU HU9903113A patent/HU221399B1/en not_active IP Right Cessation
- 1996-09-03 NZ NZ316802A patent/NZ316802A/en not_active IP Right Cessation
- 1996-09-03 WO PCT/US1996/014105 patent/WO1997009808A1/en active IP Right Grant
- 1996-09-03 CZ CZ0068898A patent/CZ299058B6/en not_active IP Right Cessation
- 1996-09-03 BR BR9610459A patent/BR9610459A/en not_active IP Right Cessation
- 1996-09-03 CA CA002231230A patent/CA2231230C/en not_active Expired - Fee Related
- 1996-09-03 DE DE69633928T patent/DE69633928T2/en not_active Expired - Lifetime
- 1996-09-03 EP EP96929866A patent/EP0848875B1/en not_active Expired - Lifetime
- 1996-09-03 ES ES96929866T patent/ES2229282T3/en not_active Expired - Lifetime
- 1996-09-03 RU RU98106231A patent/RU2144271C1/en not_active IP Right Cessation
- 1996-09-03 CN CNB961976187A patent/CN1167232C/en not_active Expired - Fee Related
- 1996-09-03 AT AT96929866T patent/ATE283595T1/en not_active IP Right Cessation
- 1996-09-03 PL PL96325415A patent/PL180330B1/en not_active IP Right Cessation
- 1996-09-03 KR KR1019980701764A patent/KR100319954B1/en not_active IP Right Cessation
-
1998
- 1998-03-06 NO NO19980998A patent/NO324343B1/en not_active IP Right Cessation
-
1999
- 1999-03-25 US US09/276,042 patent/US7085362B1/en not_active Expired - Lifetime
- 1999-03-25 US US09/276,217 patent/US6480493B1/en not_active Expired - Lifetime
- 1999-03-25 US US09/276,601 patent/US6674759B1/en not_active Expired - Lifetime
- 1999-03-25 US US09/276,290 patent/US6690656B1/en not_active Expired - Lifetime
-
2003
- 2003-12-11 US US10/733,917 patent/US20040125814A1/en not_active Abandoned
-
2006
- 2006-05-16 US US11/434,843 patent/US7394894B2/en not_active Expired - Lifetime
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2231230C (en) | System for managing telecommunications | |
US6452928B1 (en) | Broadband telecommunications system | |
JP3833717B2 (en) | Communication tandem system for line-based traffic | |
US6683878B2 (en) | ATM gateway system | |
NZ283630A (en) | Telecommunications signalling processed externally to switched network pathway to select network characteristics | |
MXPA98001825A (en) | System to manage telecommunication |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
MKLA | Lapsed |
Effective date: 20150903 |