WO1999028827A1 - Method and system for media connectivity over a packet-based network - Google Patents
Method and system for media connectivity over a packet-based network Download PDFInfo
- Publication number
- WO1999028827A1 WO1999028827A1 PCT/US1998/025760 US9825760W WO9928827A1 WO 1999028827 A1 WO1999028827 A1 WO 1999028827A1 US 9825760 W US9825760 W US 9825760W WO 9928827 A1 WO9928827 A1 WO 9928827A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- call agent
- network
- information
- control device
- protocol
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1069—Session establishment or de-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/64—Hybrid switching systems
- H04L12/6418—Hybrid transport
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/06—Arrangements for interconnection between switching centres using auxiliary connections for control or supervision, e.g. where the auxiliary connection is a signalling system number 7 link
- H04M7/063—Arrangements for interconnection between switching centres using auxiliary connections for control or supervision, e.g. where the auxiliary connection is a signalling system number 7 link where the telephone network is a network other than PSTN/ISDN
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
- H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
- H04M7/1245—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks where a network other than PSTN/ISDN interconnects two PSTN/ISDN networks
-
- 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/0029—Provisions for intelligent networking
- H04Q3/0045—Provisions for intelligent networking involving hybrid, i.e. a mixture of public and private, or multi-vendor systems
-
- 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/5638—Services, e.g. multimedia, GOS, QOS
- H04L2012/5663—Support of N-ISDN
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/64—Hybrid switching systems
- H04L12/6418—Hybrid transport
- H04L2012/6472—Internet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/64—Hybrid switching systems
- H04L12/6418—Hybrid transport
- H04L2012/6475—N-ISDN, Public Switched Telephone Network [PSTN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/64—Hybrid switching systems
- H04L12/6418—Hybrid transport
- H04L2012/6486—Signalling Protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
- H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
- H04M7/126—Interworking of session control protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
- H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
- H04M7/128—Details of addressing, directories or routing tables
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
- H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
- H04M7/129—Details of providing call progress tones or announcements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13034—A/D conversion, code compression/expansion
-
- 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/13196—Connection circuit/link/trunk/junction, bridge, router, gateway
-
- 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/13388—Saturation signaling systems
Definitions
- the present invention relates generally to communications, and more particularly, to a method and system for managing media sessions.
- IP voice over Internet Protocol
- H.323 protocol standards represent one such attempt, but suffer from several disadvantages. In particular, these standards require a logical data connection between network elements, which limits flexibility, scalability, and efficiency.
- the present invention is directed to a communication system that substantially obviates one or more of the problems due to limitations and disadvantages of the prior art.
- the invention comprises a packet-based network, a first subscriber unit, a first media control device connecting the first subscriber unit to the packet-based network, a second subscriber unit, a second media control device connecting the second subscriber unit to the packet-based network, and a call agent.
- the call agent of this embodiment is a device for managing communications between the first and second subscriber units over the network, and a device for sending and/or receiving SS7 signaling information.
- the invention comprises a first subscriber unit coupled to a network through a first media control device, a second subscriber unit coupled to the network through a second media control device, and a call agent.
- the call agent of this embodiment includes a first call agent cluster coupled to the first subscriber unit through a media control device.
- the first call agent cluster includes a device for translating information received from the first media control device in a first protocol into a common protocol, a device for communicating with a second call agent cluster using the common protocol, a device for translating the information in the common protocol into the first protocol, and a device for controlling the first media control device for managing a media session between the first subscriber unit and the second subscriber unit over the network.
- the invention comprises a method of managing communications between a first subscriber unit and a second subscriber unit over a network, wherein this method includes the call agent sending and/or receiving SS7 signaling information regarding management of communications over a packet-based network, the call agent managing communications between the first and second subscriber units over the network, and the first and second subscriber units communicating over the network.
- the invention comprises a method of managing communications between a first subscriber unit and a second subscriber unit.
- This method comprises the steps of a first media control device coupled to the first subscriber unit transmitting information in a first protocol to a first call agent cluster regarding establishing a media session with the second subscriber unit over a packet-based network.
- the first call agent cluster translates the information in the first protocol to a common protocol and sets up a connection between the first call agent cluster and a second call agent cluster.
- the first call agent cluster and the second call agent cluster exchange information using the common protocol, the first call agent cluster translating information in the common protocol to the first protocol.
- the first call agent cluster transmits the information in the first protocol to the first media control device coupled to the first subscriber unit.
- the second call agent cluster translates information in the common protocol to a second protocol, and transmits the information in the second protocol to a second media control device coupled to the second subscriber unit.
- the first subscriber unit and the second subscriber unit then exchange information over the network.
- Fig. 1 is a block diagram of the IGCS system according to one embodiment of the invention.
- Fig. 2 is a diagram of a call agent according to one embodiment of the invention.
- Fig. 3 shows connectivity between two TGWs over a packet-based network according to one embodiment of the invention.
- Fig. 4 shows connectivity between a RGW and a TGW over a packet- based network according to one embodiment of the invention.
- Fig. 5 shows connectivity between two RGWs over a packet-based network according to one embodiment of the invention.
- Fig. 6 is a diagram of a call agent cluster for RGW connection management and a call agent cluster for TGW connection management according to one embodiment of the invention.
- Fig. 7 is a diagram of call models supported by call agent clusters according to one embodiment of the invention.
- Fig. 8 is a diagram of call models supported by a traditional switch.
- Fig. 9 is a flow diagram for RGW - RGW connection set-up according to one embodiment of the invention.
- Fig. 10 is a flow diagram for the call agent cluster supporting RGW - RGW connectivity according to one embodiment of the invention.
- Fig. 11 is a flow diagram for RGW - RGW connection tear down according to one embodiment of the invention.
- Fig. 12 is a flow diagram for TGW - TGW connection set-up according to one embodiment of the invention.
- Fig. 13 is a flow diagram for TGW - TGW connection tear down according to one embodiment of the invention.
- Fig. 14 is a flow diagram for RGW - TGW connection set-up according to one embodiment of the invention.
- Fig. 15 is a flow diagram for RGW - TGW connection tear down according to one embodiment of the invention.
- Fig. 16 is a flow diagram for TGW - RGW connection set-up according to one embodiment of the invention.
- Fig. 17 is a flow diagram for TGW - RGW tear down according to one embodiment of the invention.
- Fig. 18 is a flow diagram of a service broker for connection set-up according to one embodiment of the invention.
- an Internet Gateway Call Server is a distributed scalable hardware independent system that supports multiple functions regarding management and support of communications over a packet-based network.
- the communications supported by the IGCS include, but are not limited to, Voice Over Internet Protocol ("VOIP”), voice over Asynchronous Transfer Mode (“ATM”), video conferencing, data transfer, telephony, and downloading video or other data. These communications will be referred to as media sessions.
- VOIP Voice Over Internet Protocol
- ATM voice over Asynchronous Transfer Mode
- video conferencing video conferencing
- data transfer data transfer
- telephony and downloading video or other data.
- the IGCS may be divided into separate components, each of which may or may not be present in a particular IGCS deployment. As shown in Fig. 1 , these components include a call agent 160, SS7 gateways 170, an accounting gateway 182, and an announcement server 184.
- the SS7 gateway 170 within a preferred embodiment of the IGCS allows the IGCS to attach to and be part of the existing PSTN while other components within the system may interface with packet-based media devices.
- a call agent 160 sets-up a connection between subscriber units 110 and 130 over a network 150.
- the subscriber units 110 and 130 are telephones, and the network is an IP network 150.
- the subscriber units can be any user device for sending and receiving information.
- the network can be any packet- based network capable of carrying data information, including an ATM network.
- Media control devices 120 and 140 each connect a subscriber unit, 110 or 130, respectively, to the network 150.
- the media control devices 120 and 140 are termed VOIP gateways and in a preferred embodiment can be either a Trunking Gateway (“TGW”) 140 or a residential gateway (“RGW”) 120.
- TGW 140 connects a Public Switched Telephone Network (“PSTN”) 180 to the network 150, and thus provides the subscriber unit 130 with a connection to the network
- PSTN Public Switched Telephone Network
- signaling information such as call-set up, tear-down, and management signaling, i.e., SS7 signaling
- PSTN 180 For this type of connectivity, signaling information, such as call-set up, tear-down, and management signaling, i.e., SS7 signaling, is sent through the PSTN 180 to an SS7 gateway 170, which connects the SS7 signaling information to the call agent 160.
- the call agent uses this information to set-up, tear-down, or manage the connection by sending messages to the TGW 140.
- these messages are Simple Gateway Control Protocol ("SGCP") messages, however, other protocols may be supported depending on the type of media control device the call agent is supporting.
- SGCP Simple Gateway Control Protocol
- the call agent 160 sets-up a connection for the subscriber unit 130 over the network 150, information is exchanged between the subscriber units 110 and 130 over the network through their respective gateways 120 and 140.
- the call agent 160 is used for call management and the information exchanged between the subscriber units 110 and 130 does not pass through the call agent 160.
- the media control devices use Real Time Protocol (“RTP") and Real Time Control Protocol (“RTCP”) to communicate over an IP network.
- RTP Real Time Protocol
- RTCP Real Time Control Protocol
- the media control devices use an appropriate ATM Adaptation Layer (“AAL”) type to communicate over an ATM network.
- AAL ATM Adaptation Layer
- RGW 120 provides a traditional analog interface to the network.
- RGWs may include "set-top boxes.” Unlike a TGW, RGWs both send and receive signaling information to/from the call agent 160.
- the call agent of a preferred embodiment can communicate with various media control devices controlling various other types of subscriber units.
- an H.323 gateway 172 may be used as a media control device to provide an interface between the call agent and H.323 clients 174.
- the call agent objects consist of call agent clusters 210, an ingress service broker 220, an egress service broker 230, and a network resource database 240. These objects are distributed along a Common Object Request Broker Architecture (“CORBA”) software bus 250.
- CORBA allows applications to communicate with one another no matter where they are located or who has designed them, thus allowing for flexible placement of them to suit considerations of cost, performance, and availability.
- Call agent clusters are logical groupings of call agent components, and handle the specifics of call management. Their two central functions are exercising control over a media control device, which in a preferred embodiment is a VOIP gateway, and translating messages from one protocol, such as SGCP or ISDN User Part ("ISUP"), into a protocol that is common to all objects within the call agent.
- a media control device which in a preferred embodiment is a VOIP gateway, and translating messages from one protocol, such as SGCP or ISDN User Part ("ISUP"), into a protocol that is common to all objects within the call agent.
- this common protocol is the Multi Call Agent Protocol ("MCAP") developed by Bellcore, which is defined using the CORBA Interface Definition Language (“IDL").
- MCAP Multi Call Agent Protocol
- IDL CORBA Interface Definition Language
- connection types there are three possible connection types between subscriber units where the subscriber unit is connected to the network via a TGW or RGW.
- the first connection type is where both subscriber units are connected to the network via a TGW, as illustrated in Fig. 3.
- the second is where one subscriber unit is connected to the network via an RGW and another is connected to the network via a TGW, as illustrated in Fig. 4.
- the third connection type is where both subscriber units are connected to the network via RGWs as illustrated in Fig. 5.
- Fig. 3 illustrates the relevant system components for supporting communications between two subscriber units both connected to the network 150 via a TGW (a TGW-TGW connection).
- TGWs 310 and 312 an ingress call agent cluster 314, an egress call agent cluster 316, an ingress service broker 318, an egress service broker 320, a network resource database 322, SS7 gateways 326 and 328, and a CORBA software bus 324.
- Flow diagrams for connection set-up and tear down for this type of connection are shown in Figs. 12 and 13, respectively, which are
- Fig. 4 illustrates the relevant system components for supporting communications between two subscriber units where one is connected to the network 150 via an RGW and the other via a TGW.
- the relevant components include an RGW 410, a TGW 412, an ingress call agent cluster 414, an egress call agent cluster 416, an ingress service broker 418, an egress service broker 420, a network resource database 422, and a CORBA software bus 424.
- Flow diagrams for connection set-up and tear down for this type of connection are shown in Figs. 14 and 15, respectively, which are discussed later.
- Fig. 5 illustrates the relevant components where both subscriber units are connected to the 150 network via an RGW.
- These components preferably include RGWs 510 and 512, an ingress call agent cluster 514, an egress call agent cluster 516, an ingress service broker 518, an egress service broker 520, a network resource database 522, and a CORBA software bus 524.
- Flow diagrams for connection set-up and tear down for this type of connection are shown in Figs. 9 and 11 , respectively, which are discussed later.
- Fig. 6 provides a top level diagram of the objects of a generic call agent cluster for managing a TGW 640 and a call agent cluster for managing an RGW 660. These objects include a message queue 610 and 620, an endpoint manager 614 and 624, a state machine 616 and 626, and a media control device manager 618 and 628.
- the call agent cluster may also contain a message handler 612, which is used in TGW connection management. These components are distributed along a CORBA software bus 630.
- the message queue 610 and 620 of a call agent cluster temporarily stores messages received from a media control device 426 or 410, respectively.
- Each call agent cluster preferably contains at least one message queue, and different queues are used for managing different types of media control devices. For example, there are different message queues for RGW and TGW connection management.
- the message queue for TGW connection management is referred to as an ISUP message queue, and the message queue for RGW connection management is referred to as an SGCP message queue.
- a message queue for TGW connection management consists of an SS7 gateway 426 sending ISUP messages to the queue 610.
- the queue stores the messages and then forwards them to a message handler 612 on a first in first out basis.
- an RGW 410 sends SGCP messages to the queue 620.
- the messages are stored and then transmitted directly to an endpoint manager 624.
- a call agent cluster for RGW connection management need not contain a message handler.
- the endpoint manager 614 and 624 is responsible for managing the state of each call, and each call agent cluster contains at least one.
- the endpoint manager 614 and 624 has two principal functions. The first is receiving messages from the various components of the system, such as message queues 610 and 620, service brokers 418 and 420 and state machines of peer call agent clusters 616 and 626.
- connection set descriptor The second principal function of the endpoint manager 614 and 624 is storing information on the state of each connection.
- the endpoint manager 614 and 624 preferably stores this information in a construct called the connection set descriptor.
- This construct is sufficiently generic to contain information associated with the various possible types of endpoints, such as TGWs and RGWs.
- the contents of the connection set descriptor for the preferred embodiment are illustrated in the following table:
- the call agent cluster preferably stores these connection set descriptors in a connection set descriptor manager 670 and 680, an independent object visible only to the endpoint manager.
- the storage is in memory with backups written to disk, and there is one connection set descriptor manager per endpoint manager. Although, in other embodiments, there can be one per call agent cluster.
- the endpoint manager 614 and 624 upon receiving a message, determines the connection set descriptor associated with the connection, determines the appropriate state machine and then forwards both the connection set descriptor and message to the state machine 616 and 626.
- State machines 616 and 626 determine an associated action (transition) to take using a call model.
- the call model used by the state machine 616 and 626 depends upon the type of media control device that the call agent cluster exercises control over. For example, a call agent cluster uses an SGCP ingress/egress call model for RGW connection management, while an ISUP call model would be used for TGW connection management. Appendix B provides a call model script for a preferred embodiment.
- each call agent cluster preferably supports a half call model on either the ingress or egress side of the call. That is, the ingress call agent cluster 710 supports an ingress call model 720, and the egress call agent cluster 730 supports an egress call model 740. In contrast, as shown in Fig. 8, in traditional telephony, both the ingress switch 810 and egress switch 830 support both an ingress call model 820 and 840 and an egress call model 822 and 842, respectively.
- This action can involve a sequence of interactions and include transmitting messages to a gateway manager 618 and 628, service broker 418, or an endpoint manager of a peer call agent cluster 614 and 624. In a preferred embodiment, these messages are transmitted over a CORBA software bus using the MCAP protocol.
- the state machine can be described as "stateless,” meaning that the state machine has no independent knowledge of the state of a connection. It preferably receives this information from the endpoint manager as part of the connection set descriptor. This permits an endpoint manager to work with a number of different state machines over the course of a connection for management purposes. In addition, it permits the endpoint manager to work with the state machines of different network service providers that may perform unique functions.
- the media control device manager 618 and 628 preferably interacts with the state machine 616 and 626 to manage the respective media control device. It accomplishes this by receiving MCAP messages from the state manager 616 and 626, translating them to the appropriate protocol, and transmitting SGCP messages to the respective media control device 410 or 412, respectively.
- the call agent cluster may also contain a message handler.
- This component is preferably used for TGW connection management, and there is no counterpart for RGW connection management.
- the principal function of the message handler is determining which of a plurality of endpoint managers should service the call.
- the message handler receives an ISUP message from the message queue, determines which endpoint manager should receive the message, and forwards the message to this endpoint manager.
- Fig. 9 provides a flow diagram for describing the operation of the call agent for setting up a connection between end-users connected to the network via RGWs, such as illustrated in Fig. 5.
- the process is initialized by the RGW (Step 101).
- the ingress call agent cluster and the RGW then exchange several messages (Step 102). These messages may include messages to play a dial- tone, collect digits, and enter receive mode.
- the ingress call agent cluster then sends an MCAP message to the egress call agent cluster regarding setting up a connection between the call agent clusters (Step 103).
- the internal operations of the call agent clusters are discussed later.
- the egress call agent cluster then instructs, using SGCP, the RGW to setup a connection in send/receive mode and start a ringing signal in the subscriber unit (Step 104). After which, the egress call agent cluster sends an MCAP message to the ingress call agent cluster indicating that it created a connection (Step 105). The ingress call agent cluster then instructs, using SGCP, the RGW to start a ringing tone in the subscriber unit (Step 106). When the call is answered, the RGW sends an off-hook message to the egress call agent cluster (Step 107), which is forwarded, using MCAP, to the ingress call agent cluster (Step 108). After which, the ingress call agent cluster, using SGCP, instructs the RGW to enter send/receive mode (Step 109).
- Fig. 10 provides a more detailed flow diagram for describing the internal operations of the ingress call agent cluster for the above described RGW to RGW connection set-up.
- An RGW sends an SGCP message to the message queue of the ingress call agent cluster indicating that it wishes to establish a connection with a second media control device (Step 201). This message is placed in the queue. The message is then passed to the endpoint manager (Step 202) on a first in first out of the queue basis. The endpoint manager then transmits the connection set descriptor and message to the state machine (Step 203).
- the state machine uses the received message and connection set descriptor to take a specified action, determined by the applicable call model.
- the specified action is sending an MCAP message to the endpoint manager of the egress call agent cluster (Step 204).
- a service broker is used to establish the connection between call agent clusters; the operations of this process are discussed later.
- the state machine of the egress call agent cluster then sends an MCAP message to the endpoint manager of the ingress call agent cluster indicating that it set-up a connection with the RGW (Step 205).
- the endpoint manager forwards this message and the connection set descriptor to the state machine (Step 206).
- the state machine determines which action to take using this received information and the applicable call model.
- the state machine sends an MCAP message to the gateway manager instructing it to instruct the RGW gateway to start ringing (Step 207).
- the gateway manager sends an SGCP message to the RGW to start ringing (Step 208).
- the state machine of the egress call agent cluster When the call is answered, the state machine of the egress call agent cluster sends a message to the endpoint manager of the ingress call agent cluster indicating that the phone on the egress side is off-hook (Step 209). The endpoint manager then forwards this message along with the associated connection set descriptor to the state machine (Step 210).
- the state machine determines the action to take using this received information. In this case, the state machine transmits an MCAP message to the gateway manager indicating that the phone has been answered (Step 211). The gateway manager then forwards, using SGCP, this message to the RGW (Step 212).
- call agent cluster objects may be shadowed.
- a call agent cluster can contain an idle second state machine for use in the event the first state machine fails. Because a CORBA bus is used in the preferred embodiment and state machines are stateless, this second state machine need not share the same hardware environment as the primary object.
- Fig. 11 provides a flow diagram for tearing down a connection between RGWs.
- the process is initialized when an RGW sends an on-hook message to the ingress call agent cluster (Step 301), which is received by the message queue of the call agent cluster and forwarded to the state machine via the endpoint manager.
- the ingress call agent cluster then instructs the RGW to tear down the connection (Step 302).
- the ingress call agent cluster sends an MCAP message to the egress call agent cluster (Step 303), which instructs, using SGCP, its RGW to tear down the connection (Step 304).
- the egress call agent cluster then sends a message to the ingress call agent cluster indicating that the above action was taken (Step 305).
- Fig. 12 provides a flow diagram for setting up a TGW to TGW connection.
- the process is initialized by a switch sending an Initial Address Message ("IAM") message to the ingress call agent cluster indicating it wishes to establish a media session between two subscriber units (Step 401).
- the ingress call agent cluster then instructs, using SGCP, the TGW on the ingress side to set up a connection in receive mode.
- the ingress call agent then forwards an MCAP message indicating this information to the egress call agent cluster (Step 403).
- the egress call agent cluster instructs, using SGCP, the TGW to set-up a connection in send/receive mode (Step 404).
- the egress call agent cluster then sends an 1AM message to the switch (Step 405). After which, the switch sends an Address Complete Message (“ACM”) to the egress call agent cluster (Step 406). The egress call agent cluster then sends an MCAP message to the ingress call agent cluster indicating that it took the requested action (Step 407). The ingress call agent cluster then sends an ACM to the switch (Step 408). After which, the switch sends an Answer Message ("ANM”) to the egress call agent cluster (Step 409). The egress call agent cluster then sends an MCAP message to the ingress call agent cluster indicating that the call has been answered (Step 410). After which, the ingress call agent cluster instructs the TGW to enter send/receive mode (Step 411). The ingress call agent cluster then sends an ANM message to the switch (Step 412).
- ACM Address Complete Message
- Fig. 13 provides a flow diagram for tearing down a TGW to TGW connection.
- the process is initialized by a switch sending a Release Message ("REL") to the ingress call agent cluster (Step 501).
- the ingress call agent cluster then instructs the TGW to tear down the connection (Step 502).
- the ingress call agent cluster sends an MCAP message to the egress call agent cluster (Step 503).
- the egress call agent cluster then instructs the TGW to tear down the connection (Step 504).
- the egress call agent cluster then sends an REL to the switch (Step 505).
- the switch then sends a Release Confirm (“RLC”) to the egress call agent cluster (Step 506).
- the egress call agent cluster sends an MCAP message to the ingress call agent cluster indicating that the connection has been released (Step 507). After which, the ingress call agent cluster sends an RLC message to the switch.
- Fig. 14 provides a flow diagram for setting-up a connection between an RGW and a TGW.
- the process is initialized by the RGW and ingress call agent cluster exchanging several SGCP messages relating to setting up a connection. (Step 601). These messages include messages related to playing a dial-tone, collecting digits and entering receive mode.
- the ingress call agent cluster then sends an MCAP message to the egress call agent cluster indicating it wishes to set-up a media session (Step 602).
- the egress call agent cluster then instructs the TGW to set up a connection in send/receive mode (Step 603). After which, the egress call agent cluster constructs an IAM and sends it to the switch (Step 604).
- the switch then sends an ACM to the egress call agent cluster (Step 605).
- the egress call agent cluster then sends an MCAP message to the ingress call agent cluster indicating that it took the above action (Step 606).
- the ingress call agent cluster then instructs the RGW to start a ringing tone (Step 607).
- the switch then sends an ANM to the egress call agent cluster (Step 608).
- the egress call agent cluster sends an MCAP message indicating that the call was answered to the ingress call agent cluster (Step 609).
- the ingress call agent cluster then instructs the RGW to enter send/receive mode (Step 610).
- Fig. 15 provides a flow diagram for tearing down an RGW to TGW connection.
- the RGW initializes the process by sending an on-hook message to the ingress call agent cluster (Step 701), which instructs the RGW to tear down the connection (Step 702).
- the ingress call agent cluster then sends an MCAP message to the egress call agent cluster instructing it to tear down the connection (Step 703).
- the egress call agent cluster instructs the TGW to tear down the connection by sending it an SGCP message (Step 704).
- the egress call agent cluster then constructs a REL and sends it to the switch (Step 705).
- the switch sends an RLC to the egress call agent cluster (Step 706).
- the egress call agent cluster then sends an MCAP message to the ingress call agent cluster indicating that the connection has been released (Step 707).
- Fig. 16 provides a flow diagram for setting up a TGW to RGW connection.
- the switch initializes the process by sending an IAM to the ingress call agent cluster (Step 801). After which, the ingress call agent cluster instructs the TGW to set-up a connection in receive mode (Step 802). The ingress call agent cluster then sends an MCAP message to the egress call agent cluster regarding establishing a connection (Step 803). The egress call agent cluster then instructs the RGW to setup a connection in send/receive mode and start a ringing signal (Step 804). After which, the egress call agent cluster sends an MCAP message to the ingress call agent cluster indicating that it took the above action (Step 805).
- the egress call agent cluster then constructs an ACM and sends it to the switch (Step 806).
- the RGW then sends an off-hook message to the egress call agent cluster (Step 807).
- the egress call agent cluster then sends an MCAP message to the ingress call agent cluster indicating that the call was answered. (Step 808).
- the ingress call agent cluster then instructs the TGW to enter send/receive mode (Step 809). After which, the ingress call agent cluster constructs an ANM and sends it to the switch (Step 810).
- Fig. 17 provides a flow diagram for tearing down a TGW to RGW connection.
- the switch initializes the process by sending a REL to the ingress call agent cluster (Step 901 ).
- the ingress call agent cluster then instructs the TGW to tear down the connection (Step 902).
- the ingress call agent cluster then sends an MCAP message to the egress call agent cluster indicating that the connection is to be torn down. (Step 903).
- the egress call agent cluster then instructs the TGW to tear down the connection (Step 904).
- the egress call agent cluster then sends an MCAP message to the ingress call agent cluster indicating that the connection was released (Step 905).
- the ingress call agent cluster constructs an RLC and sends it to the switch (Step 906).
- the call agent uses a service broker for establishing communications between an ingress and egress call agent cluster.
- the ingress call agent cluster forwards the information to an ingress service broker.
- the ingress service broker performs an algorithm for determining the egress service broker for the egress call agent cluster of the subscriber unit it wishes to establish communications with.
- the egress service broker then performs an algorithm for determining the appropriate egress call agent cluster.
- the service brokers use routing engines for performing these algorithms, which use a routing table, a look-up table, for determining the appropriate information.
- the routing performs the functions of digit translation and classifying the connection (e.g., is it a 800 call or long distance call).
- the proper execution of the routing engine is assured by, during initialization, loading into a table in a high speed database the egress call agent cluster's endpoint manager's Interoperable Object Reference ("IOR").
- IOR Interoperable Object Reference
- the table points to a relationship between a given endpoint manager's IOR and a route path for a media session.
- the routing engine consults with this table and, depending on the number dialed, selects the appropriated endpoint manager's IOR and routes MCAP messages to it to establish a connection.
- Fig. 18 provides a flow diagram for this process.
- a call agent cluster receives a request from a subscriber unit to establish communications with a second subscriber unit, the message is forwarded from an endpoint manager to the state machine, as discussed above (Step 1001 ).
- the state machine then forwards this request using MCAP to the ingress service broker (Step 1002).
- the ingress service broker using a routing engine, determines the appropriate egress service broker and forwards the request to it using MCAP (Step 1003).
- the egress service broker determines the appropriate egress call agent cluster and, using MCAP, forwards the message to its endpoint manager (Step 1004).
- the ingress and egress call agent clusters communicate directly with one another (Step 1005).
- a network resource data base stores information regarding the network.
- This network resource database is coupled to the CORBA bus. As such, the service brokers and call agent clusters can access this database.
- the IGCS may include a call agent manager 186, accounting gateway 182 announcement server 184, and an IGCS management agent 188.
- the accounting gateway 182 in a preferred embodiment is a media control device by which start/stop call records are disseminated to a central point where they are translated from CORBA into Remote Authentication Dial-In User Service ("RADIUS"), then translated into industry standard BAF records for distribution to back-end billing systems. As shown in Fig. 2, the accounting gateway 182, in a preferred embodiment, communicates with a call agent cluster 210 of a call agent 160.
- RADIUS Remote Authentication Dial-In User Service
- the announcement server 184 is a media control device which responds to SGCP messages by playing recorded announcements. As shown in Fig. 2, the announcement server communicates with a call agent cluster 210 of a call agent 160.
- the call agent manager 186 is directly responsible for the local management of the call agent, for example: displaying the state of the call agent components, displaying alarms reported by the call agent components and object control, such as shutdown.
- the IGCS management agent 188 of a preferred embodiment manages all IGCS components including the call agent clusters, network resource database, accounting gateway and announcement server.
- the overall network management software is capable of displaying usage statistics accumulated in the call agent clusters.
- a call agent of a preferred embodiment is designed to be Simple Network Management Protocol ("SNMP") manageable by any third party SNMP management software, e.g., HP open view.
- SNMP Simple Network Management Protocol
- the architecture allows for SNMP sets, gets, and traps to be sent to a call agent SNMP agent whose function is the gathering of statistics via CORBA method invocations executed against call agent cluster objects. Also, SNMP sets are handled via method invocations that update data in the call agent cluster.
- MCAP Multi Call Agent Protocol
- Core information logically grouped in the following categories:
- Session A session ties users (calling party and called party) together,
- Connection A call is composed of a set of connections, each of which
- Manageme ties together a pair of Call Agent Clusters.
- the associated nt resources are keyed by a globally unique ID.
- Gateway A Call Agent controls a specific connection on an associated
- Manageme gateway by exchanging information keyed by a locally nt unique ID.
- Routing Routing specific information e.g. toll-free number
- the Service Execution nt Engine identifies the associated services and determines their application.
- Parameter MCAP message specific information e.g. version.
- a tunnel for messages of a specific protocol that can be carried as a payload either in a native or a parsed format.
- the native format is the given octet stream; the parsed format is the representation of the given octet stream in the MCAP definition language.
- MCAP .EVE Indicate an event that occurs during the lifetime of a
- NT connection This can serve as, for example, an acknowledgement or an indication of connection state change.
- MCAP .TUN Tunnel i.e. passthrough, a specific protocol message from
- MCAP_CREATE and MCAP_DELETE can be subsumed by MCAP_EVENT, but it is useful to distinguish these actions.
- MCAP_TUNNEL is provided to generically accommodate the needs of a specific protocol.
- the Call ID is a globally unique value defined by the Call Agent that is associated with the connection throughout its duration. It is used as the key to identify the associated resources.
- the return address is the handle to be used by the receiver to locate the sender in the event that subsequent messaging is needed.
- the Connection Descriptor contains the Connection ID, which is locally defined and used by the gateway, and specific Real Time Protocol (RTP) parameters; e.g. encoding method.
- RTP Real Time Protocol
- the tunnel message can be in either parsed or native format.
- the initial MCAP version was primarily the result of empirical work done in the development of the Call Agent. This version reflects the next step in addressing challenge presented by rapidly evolving Internet Protocol (IP) Telephony technology.
- IP Internet Protocol
- the formal MCAP reference definition uses the Common Object Request Broker Architecture (CORBA) 2.0 [1] [2] [2] Interface Definition Language (IDL) for the high level description and the associated Internet Inter-ORB Protocol (HOP) for the low-level "wire" encoding. This is similar to the use of Abstract Syntax Notation One (ASN.1) [3] [4] and the companion Basic Encoding Rules (BER) [4] [5]: the protocol designer is able to described structured information in a high-level, machine independent language and then mechanically derive the actual encoding.
- CORBA is chosen because it is used in the implementation of the Call Agent and has widespread interest and support throughout the industry.
- This version of MCAP supports the following tunnel protocols:
- SGCP Simple Gateway Control Protocol
- ISUP Integrated Services Digital Network User Part
- Appendix A2 VOIP Gateway IDL
- McapVoipGateway :ConnectionDescriptor connectionDescriptor
- connectionDescriptor
- TunnelMessage tunnelMessage ⁇ ; interface McapListener ⁇ void mcapCreate(in McapCreateMessage msg); void mcapEvent(in McapEventMessage msg); void mcapDelete(in McapDeleteMessage msg); void mcapTunnel(in McapTunnelMessage msg);
- Appendix A2 VOIP Gateway IDL
- connectionOptions connectionOptions; string sdpSessionDescriptor;
- RoutingData switch (RoutingType) ⁇ case REQUEST: RequestData requestData;
- RoutingParameter ⁇ RoutingType type
- RoutingData data
- Appendix A6 SGCP Tunnel IDL module McapSgcpTunnel ⁇ enum SgcpMessageType ⁇ NULL
- ACM ANM, BLO, BLA, CCR, CFN, CGB, CGBA, CGU, CGUA, COT, CPG, CQM, CQR, CRA, CRM, CVR, CVT, EXM, FAC, FOT, GRA, GRS, 1AM, INF, INR, LBA, PAM, REL, RES, RLC, RSC, SUS, UBA, UBL, USIS
- IAM_SEGMENTATION_INDICATOR iam_Segmentation_lndicator
- ISDN_USER_PARTJNDICATOR isdn_User_Part_lndicator
- ISDN_USER_PART_PREFERENCEJNDICATOR isdn_User_Part_Preference_lndicator;
- NATURE_OF_ADDRESSJNDICATOR_KIND ⁇ ; enum NATURE_OF_ADDRESSJNDICATOR_KIND ⁇ DIALED_DIGITS, SUPPLEMENTAL, COMPLETION, PORTED ⁇ ; union NATURE_OF_ADDRESSJNDICATORJJNION switch (NATURE_OF_ADDRESSJNDICATOR_KIND) ⁇ case DIALED_DIGITS: NATURE_OF_ADDRESS_INDICATOR_TYPE1 aDialedDigits; case SUPPLEMENTAL: NATURE_OF_ADDRESSJNDICATOR_TYPE2 aSupplemental; case COMPLETION: NATURE_OF_ADDRESS_INDICATOR_TYPE3 aCompletion; case PORTED: NATURE_OF_ADDRESSJNDICATOR_TYPE4 aPorted;
- NATURE_OF_ADDRESSJNDICATOR_UNION natureOfAddr ODD_EVEN_BIT oddEvenBit; NUMBERING_PLAN numberingPlan; PRESENTATION presentation; string addressSignal;
- NIDB_REPORT_VERIFY_AUTOMATED NIDB_REPORT_VERIFY_AUTOMATED
- NIDB_REPORT_VERIFY_OPERATOR NO_NIDB_QUERY
- NO_NIDB_RESPONSE NO_NIDB_REPORT_UNAVAILABLE
- NO_NIDB_RESPONSE_TIMEOUT NO_NIDB_RESPONSE_REJECT
- NO_NIDB_RESPONSE_ACG NO_NIDB_RESPONSE_SCCP_FAIL
- CIRCUIT_CODE circuit_code octet circuit_code_network_specific_use; octet ansi_network_specific_use;
- ITUStandardRateAdaptionV110 G771 ulawSpeech, G722andG725Audio, NONITUStandardRateAdaption, ITUStandardRateAdaptionVI 20, ITUStandardRateAdaptionX31 HDLC
- BACKWARD_CALLJNDICATOR backwardCalllndicators // Optional Parameters ACCESS_TRANSPORT accessTransport; BUSINESSJ3ROUP businessGroup; CALL_REFERENCE callReference; CAUSEJNDICATORS causelndicators; CONNECTION_REQUEST connectionRequest; INFORMATION JNDICATORS informationlndicators; NETWORK_TRANSPORT_PARAMETER networkTransportParameter; NOTIFICATIONJNDICATOR_ARRAY notificationlndicatorArray; OPTIONAL_BACKWARD_CALL_INDICATORS optionalBackwardCalllndicators;
- REMOTE_OPERATIONS remoteOperations RemoteOperations; SERVICE_ACTIVATION_ARRAY serviceActivationArray; TRANSMISSION_MEDIUM_USED TransmissionMediumUsed; USER T " OJJSERJNDICATOR userJo_userlndicators; USER_TO_USERJNFORMATION userJo_userlnformation;
- GENERIC_DIGITS genericDigits
- GENERICJMAME genericName
- octet hopCounter
- # #millsec indicates the length of timer in milliseconds.
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP98960747A EP1049981A1 (en) | 1997-12-03 | 1998-12-03 | Method and system for media connectivity over a packet-based network |
JP2000523608A JP2001525621A (en) | 1997-12-03 | 1998-12-03 | Methods and systems for media connectivity over packet-switched based networks |
CA002312325A CA2312325C (en) | 1997-12-03 | 1998-12-03 | Method and system for media connectivity over a packet-based network |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US6722497P | 1997-12-03 | 1997-12-03 | |
US60/067,224 | 1997-12-03 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO1999028827A1 true WO1999028827A1 (en) | 1999-06-10 |
Family
ID=22074553
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US1998/025760 WO1999028827A1 (en) | 1997-12-03 | 1998-12-03 | Method and system for media connectivity over a packet-based network |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP1049981A1 (en) |
JP (1) | JP2001525621A (en) |
CA (1) | CA2312325C (en) |
WO (1) | WO1999028827A1 (en) |
Cited By (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0924918A2 (en) | 1997-12-18 | 1999-06-23 | Nortel Networks Corporation | Multimedia call signalling system and method |
WO2001001293A2 (en) * | 1999-06-25 | 2001-01-04 | Jacobs Rimell Limited | Automated provisioning system |
WO2001008395A1 (en) * | 1999-07-22 | 2001-02-01 | Telefonaktiebolaget L M Ericsson | Transport of vertical control protocol messages on a switched communications network |
WO2001069697A2 (en) * | 2000-03-13 | 2001-09-20 | Sprint Communications Company, L.P. | Continuity testing in communication networks |
WO2002003649A1 (en) | 2000-06-30 | 2002-01-10 | Nokia Corporation | Opimization of service access |
KR100357850B1 (en) * | 2000-03-29 | 2002-10-25 | 삼성전자 주식회사 | Distributed objects oriented communication system and method for common service various protocolby used corba proxy module therefor |
US6640318B1 (en) | 2000-03-13 | 2003-10-28 | Sprint Communications Company, L.P. | Continuity testing in communication networks |
EP1143682A3 (en) * | 2000-04-06 | 2003-12-03 | The Distribution Systems Research Institute | Terminal-to-terminal communication connection control method using IP transfer network |
US6711623B1 (en) | 1999-05-10 | 2004-03-23 | The Distribution Systems Research Institute | Integrated IP network |
US6728362B1 (en) | 2000-03-28 | 2004-04-27 | Sprint Communications Company, L.P. | Continuity testing with call tone messaging in communication networks |
US6731738B1 (en) | 2000-03-28 | 2004-05-04 | Sprint Communications Company, L.P. | Call tones in communication networks |
AU2004202423B2 (en) * | 1999-06-25 | 2004-09-16 | Jacobs Rimell Limited | Automated provisioning system |
US7028100B2 (en) | 2000-07-12 | 2006-04-11 | The Distribution Systems Research Institute | Integrated information communication system for detecting and discarding external data packets that violate addressing rules |
US7042892B2 (en) | 2000-06-02 | 2006-05-09 | Radisys Corporation | Voice-over IP communication without echo cancellation |
US7301952B2 (en) | 2000-04-06 | 2007-11-27 | The Distribution Systems Research Institute | Terminal-to-terminal communication connection control method using IP transfer network |
US7440456B2 (en) | 2001-06-08 | 2008-10-21 | The Distribution Systems Research Institute | Terminal-to-terminal communication connection control system for IP full service |
US8072979B2 (en) | 2002-06-07 | 2011-12-06 | The Distribution Systems Research Institute | Terminal-to-terminal communication control system for IP full service |
CN102868681A (en) * | 2002-06-03 | 2013-01-09 | 阿尔卡塔尔公司 | Telecommunication system with packet-switched-multimedia-session-to-circuit-switched-call transferral |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4656624A (en) * | 1985-05-03 | 1987-04-07 | At&T Bell Laboratories | Operator communication arrangements for operator assistance systems |
US4949373A (en) * | 1989-01-06 | 1990-08-14 | International Business Machines Corporation | Host load balancing |
US5329619A (en) * | 1992-10-30 | 1994-07-12 | Software Ag | Cooperative processing interface and communication broker for heterogeneous computing environments |
US5550906A (en) * | 1994-08-05 | 1996-08-27 | Lucent Technologies Inc. | Telecommunications feature server |
US5581596A (en) * | 1994-06-13 | 1996-12-03 | U S West Technologies, Inc. | Method for controlling call processing in a microcellular personal communications services system |
US5706286A (en) * | 1995-04-19 | 1998-01-06 | Mci Communications Corporation | SS7 gateway |
-
1998
- 1998-12-03 WO PCT/US1998/025760 patent/WO1999028827A1/en not_active Application Discontinuation
- 1998-12-03 CA CA002312325A patent/CA2312325C/en not_active Expired - Fee Related
- 1998-12-03 EP EP98960747A patent/EP1049981A1/en not_active Withdrawn
- 1998-12-03 JP JP2000523608A patent/JP2001525621A/en active Pending
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4656624A (en) * | 1985-05-03 | 1987-04-07 | At&T Bell Laboratories | Operator communication arrangements for operator assistance systems |
US4949373A (en) * | 1989-01-06 | 1990-08-14 | International Business Machines Corporation | Host load balancing |
US5329619A (en) * | 1992-10-30 | 1994-07-12 | Software Ag | Cooperative processing interface and communication broker for heterogeneous computing environments |
US5581596A (en) * | 1994-06-13 | 1996-12-03 | U S West Technologies, Inc. | Method for controlling call processing in a microcellular personal communications services system |
US5550906A (en) * | 1994-08-05 | 1996-08-27 | Lucent Technologies Inc. | Telecommunications feature server |
US5764750A (en) * | 1994-08-05 | 1998-06-09 | Lucent Technologies, Inc. | Communicating between diverse communications environments |
US5706286A (en) * | 1995-04-19 | 1998-01-06 | Mci Communications Corporation | SS7 gateway |
Cited By (43)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2267992A1 (en) * | 1997-12-18 | 2010-12-29 | Nortel Networks Limited | Multimedia call signalling system and method |
EP0924918A2 (en) | 1997-12-18 | 1999-06-23 | Nortel Networks Corporation | Multimedia call signalling system and method |
EP0924918A3 (en) * | 1997-12-18 | 2001-11-21 | Nortel Networks Limited | Multimedia call signalling system and method |
US7373429B2 (en) | 1999-05-10 | 2008-05-13 | The Distribution Systems Research Institute | Integrated IP network |
US6711623B1 (en) | 1999-05-10 | 2004-03-23 | The Distribution Systems Research Institute | Integrated IP network |
AU775241B2 (en) * | 1999-06-25 | 2004-07-22 | Jacobs Rimell Limited | Automated provisioning system |
WO2001001293A3 (en) * | 1999-06-25 | 2002-05-23 | Jacobs Rimell Ltd | Automated provisioning system |
KR100744213B1 (en) * | 1999-06-25 | 2007-07-30 | 야콥스 리멜 리미티드 | Automated provisioning system |
US7313611B1 (en) | 1999-06-25 | 2007-12-25 | Jacob Rimmell Limited | Automated provisioning system |
JP2003526138A (en) * | 1999-06-25 | 2003-09-02 | ヤコブス リンメル リミテッド | Automated connection service system |
WO2001001293A2 (en) * | 1999-06-25 | 2001-01-04 | Jacobs Rimell Limited | Automated provisioning system |
US7962596B2 (en) | 1999-06-25 | 2011-06-14 | Jacobs Rimell Limited | Automated provisioning system |
AU2004202423B2 (en) * | 1999-06-25 | 2004-09-16 | Jacobs Rimell Limited | Automated provisioning system |
WO2001008395A1 (en) * | 1999-07-22 | 2001-02-01 | Telefonaktiebolaget L M Ericsson | Transport of vertical control protocol messages on a switched communications network |
WO2001069697A2 (en) * | 2000-03-13 | 2001-09-20 | Sprint Communications Company, L.P. | Continuity testing in communication networks |
US6640318B1 (en) | 2000-03-13 | 2003-10-28 | Sprint Communications Company, L.P. | Continuity testing in communication networks |
WO2001069697A3 (en) * | 2000-03-13 | 2003-04-03 | Sprint Communications Co | Continuity testing in communication networks |
US6731738B1 (en) | 2000-03-28 | 2004-05-04 | Sprint Communications Company, L.P. | Call tones in communication networks |
US6728362B1 (en) | 2000-03-28 | 2004-04-27 | Sprint Communications Company, L.P. | Continuity testing with call tone messaging in communication networks |
KR100357850B1 (en) * | 2000-03-29 | 2002-10-25 | 삼성전자 주식회사 | Distributed objects oriented communication system and method for common service various protocolby used corba proxy module therefor |
US7301952B2 (en) | 2000-04-06 | 2007-11-27 | The Distribution Systems Research Institute | Terminal-to-terminal communication connection control method using IP transfer network |
US8565245B2 (en) | 2000-04-06 | 2013-10-22 | The Distribution Systems Research Institute | Terminal-to-terminal communication connection control method using IP transfer network |
JP2016067007A (en) * | 2000-04-06 | 2016-04-28 | 一般財団法人流通システム開発センター | Communication system |
JP2015062305A (en) * | 2000-04-06 | 2015-04-02 | 一般財団法人流通システム開発センター | Communication system |
US7505471B2 (en) | 2000-04-06 | 2009-03-17 | The Distribution Systems Research Institute | Terminal-to-terminal communication connection control method using IP transfer network |
US8948161B2 (en) | 2000-04-06 | 2015-02-03 | The Distribution Systems Research Institute | Terminal-to-terminal communication connection control method using IP transfer network |
CN100512359C (en) * | 2000-04-06 | 2009-07-08 | 财团法人流通系统开发研究所 | Terminal to teminal communication connecting control method using IP transport network |
US7733882B2 (en) | 2000-04-06 | 2010-06-08 | The Distribution Systems Research Institute | Terminal-to-terminal communication connection control method using IP transfer network |
US7782883B2 (en) | 2000-04-06 | 2010-08-24 | The Distribution Systems Research Institute | Terminal-to-terminal communication connection control method using IP transfer network |
EP1143682A3 (en) * | 2000-04-06 | 2003-12-03 | The Distribution Systems Research Institute | Terminal-to-terminal communication connection control method using IP transfer network |
US7948995B2 (en) | 2000-04-06 | 2011-05-24 | The Distribution Systems Research Institute | Terminal-to-terminal communication connection control method using IP transfer network |
US8934484B2 (en) | 2000-04-06 | 2015-01-13 | The Distribution Systems Research Institute | Terminal-to-terminal communication connection control method using IP transfer network |
US8553677B2 (en) | 2000-04-06 | 2013-10-08 | The Distribution Systems Research Institute | Terminal to-terminal communication connection control method using IP transfer network |
US8121113B2 (en) | 2000-04-06 | 2012-02-21 | The Distribution Systems Research Institute | Terminal-to-terminal communication connection control method using IP transfer network |
US7042892B2 (en) | 2000-06-02 | 2006-05-09 | Radisys Corporation | Voice-over IP communication without echo cancellation |
WO2002003649A1 (en) | 2000-06-30 | 2002-01-10 | Nokia Corporation | Opimization of service access |
US7516242B2 (en) | 2000-07-12 | 2009-04-07 | The Distribution Systems Research Institute | Integrated information communication system using conversion table to convert an external packet into an internal packet by embedding a header |
US7028100B2 (en) | 2000-07-12 | 2006-04-11 | The Distribution Systems Research Institute | Integrated information communication system for detecting and discarding external data packets that violate addressing rules |
US7440456B2 (en) | 2001-06-08 | 2008-10-21 | The Distribution Systems Research Institute | Terminal-to-terminal communication connection control system for IP full service |
JP2016076934A (en) * | 2001-06-08 | 2016-05-12 | 一般財団法人流通システム開発センター | Communication system employing ip network |
CN102868681A (en) * | 2002-06-03 | 2013-01-09 | 阿尔卡塔尔公司 | Telecommunication system with packet-switched-multimedia-session-to-circuit-switched-call transferral |
US10841979B2 (en) | 2002-06-03 | 2020-11-17 | Nokia Technologies Oy | Telecommunication system with packet-switched-multimedia-session-to-circuit-switched-call transferral |
US8072979B2 (en) | 2002-06-07 | 2011-12-06 | The Distribution Systems Research Institute | Terminal-to-terminal communication control system for IP full service |
Also Published As
Publication number | Publication date |
---|---|
JP2001525621A (en) | 2001-12-11 |
CA2312325A1 (en) | 1999-06-10 |
CA2312325C (en) | 2004-11-09 |
EP1049981A1 (en) | 2000-11-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6724747B1 (en) | Method and system for media connectivity over a packet-based network | |
Greene et al. | Media gateway control protocol architecture and requirements | |
CA2312325C (en) | Method and system for media connectivity over a packet-based network | |
JP3880867B2 (en) | IP packet access gateway (IPPAG) system and method and computer program product for managing IP bearer paths between IP endpoints | |
US8270421B2 (en) | Voice over data telecommunications network architecture | |
KR100534141B1 (en) | APPARATUS FOR A VOICE OVER IP(VoIP) TELEPHONY GATEWAY AND METHODS FOR USE THEREIN | |
JP3961717B2 (en) | Optimal routing of calls over public switched telephone networks and the Internet | |
US8315251B2 (en) | Multi-mode endpoint in a communication network system and methods thereof | |
US7742467B1 (en) | Method for performing segmented resource reservation | |
US6574335B1 (en) | Method for simulating a ring back for a call between parties in different communication networks | |
US20100220715A1 (en) | Technique for providing translation between the packet environment and the pstn environment | |
US6603760B1 (en) | System and method for gradual transition of local phone services from PSTN to next generation network | |
US6707797B1 (en) | Multi-line telephony via network gateways | |
JP3887569B2 (en) | Method, computer program product, ATM packet access gateway system and ATM packet access gateway for managing ATM bearer paths | |
Cisco | Call Agent Provisioning | |
US7436851B1 (en) | Destination call routing apparatus and method | |
US6785264B1 (en) | Method and apparatus for inter-working line side signaling between circuit, packet and circuit packet networks | |
Greene et al. | RFC2805: Media Gateway Control Protocol Architecture and Requirements | |
KR100406234B1 (en) | Method For Exchange V5.2 Subscriber Status On Access Network | |
Rosen | Network Working Group N. Greene Request for Comments: 2805 Nortel Networks Category: Informational M. Ramalho Cisco Systems | |
GB2351415A (en) | Continuity checking in a telecommunications network | |
KR20040015959A (en) | Method for transmitting access gateway subscribe line information using media gateway control protocol | |
CN1205826A (en) | Call back service for regulatory restrictive area |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): CA JP |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 1998960747 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2312325 Country of ref document: CA Ref country code: CA Ref document number: 2312325 Kind code of ref document: A Format of ref document f/p: F |
|
ENP | Entry into the national phase |
Ref country code: JP Ref document number: 2000 523608 Kind code of ref document: A Format of ref document f/p: F |
|
WWP | Wipo information: published in national office |
Ref document number: 1998960747 Country of ref document: EP |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 1998960747 Country of ref document: EP |