JP2001525621A - Methods and systems for media connectivity over packet-switched based networks - Google Patents

Abstract

Abstract: A method for a hardware-independent distributed and scalable system that supports multiple functions for managing (186, 188) and supporting (182, 184) communications on a packet-switched based network And system. The communications supported by these methods and systems include Internet Protocol Voice Communications ("VOIP") (150), Asynchronous Transfer Mode ("ATM") Voice Communications, video conferencing, data transfer, and telephone (130). And download of video and other data (174), but are not limited to. These methods and systems use a call agent (160) composed of various objects distributed over a CORBA software bus to call two endpoints communicating over a packet-switched based network. Implement management.

Description

DETAILED DESCRIPTION OF THE INVENTION

This application claims the benefit of US Provisional Application No. 60 / 06,224, filed December 3, 1997, the contents of which are incorporated by reference.

BACKGROUND OF THE INVENTION [0002] The present invention relates generally to communications, and more particularly, to media sessions.
session management).

[0003] Telecommunications work has pushed the development of effective systems for implementing voice-based communications over packet-switched based networks, particularly voice communications over the Internet Protocol ("IP"). H. The H.323 protocol standard is one such attempt, but has some drawbacks. In particular, these standards require logical data connections between network elements, which limits flexibility, scalability, and efficiency.

[0004] It is desirable to devise a method and system for overcoming the shortcomings of conventional voice communications over packet-switched based network systems.

[0005] Accordingly, the present invention is directed to a communication system that substantially obviates one or more of the problems arising from the limitations and disadvantages of the prior art.

In accordance with the embodiments of the invention and the objects of the invention set forth in the broad description, the invention relates to a packet switched base network, a first subscriber unit (subscribe).
er unit), a first medium control unit connecting the first subscriber unit to the packet switched base network, a second medium connecting the second subscriber unit, the second subscriber unit to the packet switched base network. It consists of a control device and a call agent. The call agent of this embodiment is a device for controlling communication between a first subscriber unit and a second subscriber unit on a network and a device for transmitting and receiving SS7 signal information.

In another aspect, the invention is a first subscriber unit coupled to a network through a first media controller, a second subscriber unit coupled to a network through a second media controller. , And a call agent. The call agent of this embodiment comprises a first call agent cluster coupled to the first subscriber unit via the media controller.
cluster). A first call agent cluster for converting information received from the first media control device in a first protocol into a common protocol, for communicating with the second call agent cluster using the common protocol; Apparatus, apparatus for converting information according to a common protocol into a first protocol, and a first media controller for managing a media session between a first subscriber unit and a second subscriber unit over a network Including a device for controlling the

[0008] In another aspect, the invention comprises a method for managing communications between a first subscriber unit and a second subscriber unit on a network, the method comprising: A call agent for transmitting and receiving SS7 signaling information related to management, a call agent for managing communication between a first subscriber unit and a second subscriber unit on a network, and first and second subscriptions for communicating on a network. Includes user units.

In another aspect, the invention comprises a method for managing communication between a first subscriber unit and a second subscriber unit. The method includes a first media controller coupled to a first subscriber unit for transmitting information according to a first protocol regarding an operation of establishing a media session with a second subscriber unit over a packet-switched base network. Transmitting to the first call agent cluster. The first call agent cluster converts information according to the first protocol into a common protocol, and sets up a connection between the first call agent cluster and the second call agent cluster. The first call agent cluster and the second call agent cluster exchange information using a common protocol, and the first call agent cluster converts information according to the common protocol into the first protocol. The first call agent cluster sends information according to a first protocol to a first media controller coupled to the first subscriber unit. The second call agent cluster converts information according to the common protocol into a second protocol,
The information according to the second protocol is transmitted to a second media controller coupled to the second subscriber unit. The first subscriber unit and the second subscriber unit exchange information over a network.

[0010] The description of the invention, and the following description of the best mode for carrying out the invention, will not limit the scope of the claimed invention. Both provide examples and explanations so that others can practice the invention. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which form a part of the specification for carrying out the best mode of the present invention, illustrate several embodiments of the present invention and, together with the description, serve to explain the principles of the invention. .

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Reference will now be made in detail to the preferred embodiments of the invention, examples of which are illustrated in the accompanying drawings.
Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.

In a preferred embodiment of the invention, the Internet gateway call server (
"IGCS") is a hardware-independent, distributed, extensible system that supports multiple functions for managing and supporting communications over a packet-switched based network. The communications supported by IGCS include Internet Protocol Voice Communications ("VOIP"), Asynchronous Transfer Mode ("ATM") Voice Communications, Video Conferencing, Data Transfer, Telephony, and Video and Other Data Downloads. However, it is not limited to these. These communications are called a media session.

The IGCS can be broken down into multiple components to accommodate a variety of possible future requirements, each of which may or may not be included in a particular IGCS deployment. As shown in FIG. 1, these components include a call agent 160, an SS7 gateway 170, an accounting gateway 182, and an announcement server 184. IGC
By using the SS7 gateway 170 in the preferred embodiment of I.S.
S can be attached to and be part of an existing PSTN, but other components in the system can interface with packet-switched base media devices. In a preferred embodiment of the system, call agent 160 sets up a connection between subscriber units 110 and 130 over network 150.
In the preferred embodiment, subscriber units 110 and 130 are telephones and the network is IP network 150. However, the present invention is not limited to this application example, and the subscriber unit may be any user device for transmitting and receiving information. Further, the network can be any packet-switched based network capable of transmitting data information, including an ATM network.

Each of the media controllers 120 and 140 connects the subscriber unit 110 or 130 to the network 150. To support voice communication (VOIP) over the Internet protocol, media controllers 120 and 14
0 is called a VOIP gateway, and in a preferred embodiment, the relay gateway (
"TGW") 140 or residential gateway (residential ga)
teway) (“RGW”) 120. TGW 140 connects a public switched network (“PSTN”) 180 to network 150, thereby:
Subscriber unit 130 can connect to network 150.

In this type of connectivity, signaling information such as call setup, teardown, and management signals, ie, SS7 signals, are transmitted through the PSTN 180 to the SS7 gateway 170, which connects the SS7 signaling information to the call agent 160. . The call agent uses this information to send, send, or send a message to the TGW 140 to set up, destroy, or manage the connection. In a preferred embodiment, these messages are simple gateway control protocols ("SG
CP ") message, but other protocols may be supported depending on the type of media controller supported by the call agent.

After the call agent 160 sets up a connection to the subscriber unit 130 on the network 150, it exchanges information between the subscriber units 110 and 130 on the network through respective gateways 120 and 140. Thus, in a preferred embodiment, the call agent 160 is used for call management,
The information exchanged between subscriber units 110 and 130 is call agent 1
Do not pass through 60. In a preferred embodiment, the media controller communicates over an IP network using a real-time protocol ("RTP") and a real-time control protocol ("RTCP").

[0017] In another preferred embodiment, the media control unit includes an appropriate ATM adaptation layer ("AAL").
) Communicate over the ATM network using the type.

The RGW 120 has a conventional analog interface to a network. The RGW may include a “set-top-box”. Unlike the TGW, the RGW sends and receives signaling information to and from the call agent 160.

Further, the call agent of the preferred embodiment can communicate with various media controllers to control various other subscriber units. For example, FIG.
As shown in H. The H.323 gateway 172 communicates with the call agent and H.323. It can be used as a medium control device that realizes an interface with the H.323 client 174.

The call agent object shown in FIG. 2 includes a call agent cluster 210, an ingress service broker (ingress service br).
ok) 220, outgoing service broker (egress service br)
okker) 230 and a network resource database 240. These objects are based on the Common Object Request Broker Arc (Common Object Request Broker Arc).
("CORBA") software bus 250. Applications that use CORBA can communicate with each other no matter where they are located or who designs them, resulting in cost, performance,
It can be freely arranged in consideration of aspects such as availability.

A call agent cluster is a logical grouping of call agent components that handles call management details. The two core functions perform control of the media controller, which in the preferred embodiment is a VOIP gateway, and send messages to the SGCP or ISDN User Part ("ISUP").
Convert from a protocol such as to a common protocol for all objects in the call agent. In a preferred embodiment, the common protocol is Bell
A multi-call agent protocol ("MCAP") developed by core, defined using the CORBA interface definition language ("IDL"). The script for this protocol is listed in Appendix A.

The detailed operation of the call agent cluster differs depending on the type of the media control device managed by the call agent cluster. The operation of the call agent cluster for managing the RGW and the TGW will be described later.

In a preferred embodiment, there are three types of connections between subscriber units where the subscriber units are connected to the network via a TGW or RGW. The first connection type is one in which both subscriber units are connected to the network via the TGW as shown in FIG. In the second connection type, as shown in FIG. 4, one subscriber unit is connected to the network via the RGW, and the other subscriber unit is connected to the network via the TGW. A third connection type is one in which both subscriber units are connected to the network via the RGW as shown in FIG. These figures are described in detail in the following paragraphs.

FIG. 3 is a diagram of related system components that support communication between two subscriber units that are both connected to a network 150 via a TGW (TGW-TGW connection). These components include TGW 310 and 3
12, incoming call agent cluster 314, outgoing call agent cluster 3
16, incoming service broker 318, outgoing service broker 320, network resource database 322, SS7 gateways 326 and 328, and C
Preferably, an ORBA software bus 324 is included. Flowcharts of connection setup and connection teardown for this type of connection are shown in FIGS. 12 and 13, respectively, which will be described later.

FIG. 4 is a diagram of related system components that support communication between two subscriber units, one connected to the network 150 via the RGW and the other connected to the network 150 via the TGW. In this embodiment, the relevant components are RGW 410, TGW 412, incoming call agent cluster 414, outgoing call agent cluster 416, incoming service broker 418, outgoing service broker 420, network resource database 422, and C
ORBA software bus 424 is included. Flowcharts of connection setup and connection teardown for this type of connection are shown in FIGS. 14 and 15, respectively, which will be described later.

FIG. 5 is a diagram of the relevant components where both subscriber units are connected to the network 150 via the RGW. These components are RGW5
10 and 512, incoming call agent cluster 514, outgoing call agent cluster 516, incoming service broker 518, outgoing service broker 520, network resource database 522, and CORBA software bus 5.
24 is preferred. Flowcharts of connection setup and connection teardown for this type of connection are shown in FIGS. 9 and 11, respectively, which will be described later.

The objects that comprise a call agent cluster vary depending on the type of media controller managed by the cluster. FIG. 6 is a top-level diagram showing objects of a generic call agent cluster for managing the TGW 640 and a call agent cluster for managing the RGW 660. These objects are the message queues 610 and 620, the endpoint manager (en
dpoint managers 614 and 624, state machine (state)
machine) 616 and 626, and media controller managers 618 and 628. In addition, the call agent cluster may include a message handler 612 used in TGW connection management. These components are distributed along the CORBA software bus 630.

The message queues 610 and 620 of the call agent cluster temporarily store messages received from the media controller 426 or 410, respectively. Each call agent cluster preferably has at least one message queue, and uses a separate queue for each type of media controller it manages. For example, different message queues are prepared for connection management between the RGW and the TGW. The message queue for TGW connection management is called an ISUP message queue, and the message queue for RGW connection management is called an SGCP message queue.

In the TGW connection management message queue, the SS7 gateway 426 operates to transmit an ISUP message to the queue 610. After the messages are queued, they are transferred to the message handler 612 on a first-in first-out basis. In RGW connection management, the RGW 410 sends an SGCP message to the queue 620. The message is stored and then sent directly to the endpoint manager 624. Therefore, the call agent cluster for RGW connection management does not need to include a message handler.

The endpoint managers 614 and 624 need to manage the state of each call, and each call agent cluster has at least one call. Endpoint managers 614 and 624 have two main functions. The first is the ability to receive messages from various components of the system, such as message queues 610 and 620, service brokers 418 and 420, and peer call agent clusters 616 and 626.

A second main function of the endpoint managers 614 and 624 is a function of storing information regarding the status of each connection. In the endpoint managers 614 and 624, the connection setting descriptor (connection set descr.
Preferably, this information is stored in a structure called an (iptor). This structure is generic enough to contain information associated with various possible types of endpoints, such as TGW and RGW. The following table summarizes the contents of the connection setting descriptor in the preferred embodiment.

[0032]

[Table 1]

The above summary is used as a guideline specific to a particular type of endpoint.

The call agent cluster preferably stores these connection setting descriptors in connection setting descriptor managers 670 and 680, which are independent objects visible only to the endpoint manager. In the preferred embodiment, there is one connection setting descriptor manager per endpoint manager for storing in memory and writing backups to disk. However, in other embodiments,
There may be one for each call agent cluster.

After receiving the message, the endpoint managers 614 and 624
Determine the connection settings descriptor associated with the connection, determine the appropriate state machine,
It then forwards both the connection setup descriptor and the message to state machines 616 and 626.

The state machines 616 and 626 determine a related action (transition) to be executed using the call model based on the received message and the connection setting descriptor. The call model used in state machines 616 and 626 depends on the type of media controller that the call agent cluster controls. For example, a call agent cluster uses the SGCP in / out call model for RGW connection management,
The ISUP call model is used for GW connection management. Appendix B contains the call model script of the preferred embodiment.

As shown in FIG. 7, each call agent cluster preferably supports a call model on the ingress or egress of a call. That is, incoming call agent cluster 710 supports incoming call model 720, and outgoing call agent cluster 730 supports outgoing call model 740. In contrast, as shown in FIG. 8, in a conventional telephone, the incoming switch 810 and the outgoing switch 830 both support incoming call models 820 and 840 and outgoing call models 822 and 842, respectively.

After the action is determined, it is executed. This action involves a series of interactions, with the gateway managers 618 and 628, the service broker 418
, Or sending a message to the endpoint manager of the peer call agent clusters 614 and 624. In the preferred embodiment, these messages are sent over the CORBA software bus using the MCAP protocol.

A state machine is said to be “stateless” if it has no independent information about the state of the connection. Preferably, this information is received from the endpoint manager as part of the connection setup descriptor. This allows the endpoint manager to operate a number of different state machines during the connection process for management. In addition, the endpoint manager can operate state machines of different network service providers that can perform specific functions.

The media controller managers 618 and 628 preferably interact with state machines 616 and 626 to manage the respective media controllers. To do so, it receives MCAP messages from the state managers 616 and 626, converts them to the appropriate protocol, and passes the SGCP messages to the respective media controller 41.
0 or 412.

In addition to the above components, a call agent cluster can also include a message handler. This component is preferably used for TGW connection management, but there is no equivalent for RGW connection management. The primary function of the message handler is to determine which of multiple endpoint managers should handle the call. Thus, the message handler receives the ISUP message from the message queue, determines which endpoint manager should receive the message, and forwards the message to this endpoint manager.

From an object-oriented (“OO”) perspective, similar objects, eg, RG
Executions such as W and TGW message queues are candidates for inheritance, that is,
The objects specific to the call agent cluster are designed to be comprehensive in the structure, meaning that they can be reused for processing different protocols. In this way, this implementation can take advantage of the advantages gained by identifying common operations and design patterns.

FIG. 9 is a flowchart illustrating the operation of a call agent for setting up a connection between end users connected to a network via an RGW, as shown in FIG. This process is initialized by the RGW (step 101).
. The incoming call agent cluster and the RGW exchange a plurality of messages (step 102). These messages play a dial tone, collect phone numbers,
And a message to enter the receiving mode. Thereafter, the incoming call agent cluster establishes a connection MC between the call agent clusters.
Send an AP message to the outgoing call agent cluster (step 103)
. The internal operation of the call agent cluster will be described later.

Next, the outgoing call agent cluster uses the SGCP to set up the connection in transmit / receive mode and instruct the RGW to initiate a ring signal within the subscriber unit (step 104). Thereafter, the outgoing call agent cluster sends an MCAP message to the incoming call agent cluster indicating that the connection has been established (step 105). In addition, the outgoing call agent cluster is
Use P to instruct the RGW to ring the ring in the subscriber unit (step 106). When the call is answered, the RGW sends an off-hook message to the outgoing call agent cluster (step 107) and forwards it to the incoming call agent cluster using MCAP (step 108). Thereafter, the incoming call agent cluster uses SGCP to switch to the transmit / receive mode
An instruction is given to the GW (step 109).

FIG. 10 is a more detailed flowchart illustrating the internal operation of the incoming call agent cluster for the above RGW to RGW connection setting. The RGW sends an SGCP message to the message queue of the incoming call agent cluster, indicating that it wants to establish a connection with the second medium control device (step 201). This message is placed in the queue.

The message is passed to the endpoint manager based on a first in first out queue (step 202). The endpoint manager sends the connection setup descriptor and a message to the state machine (step 203).

Thus, the state machine uses the received message and the connection setting descriptor to execute a specified action determined by an applicable call model. In this case, the designated action sends an MCAP message to the endpoint manager of the outgoing call agent cluster (step 204). It should be noted that the connection between the call agent clusters is established using the service broker, the operation of which will be described later.

Thereafter, the state machine of the outgoing call agent cluster sends an MCAP message to the endpoint manager of the incoming call agent cluster indicating that the connection with the RGW has been established (step 205). The endpoint manager forwards this message and the connection setup descriptor to the state machine (step 206).
). The state machine uses this received information and the applicable call model to determine the action to take. In this case, the state machine tells the gateway manager
An MCAP message instructing the RGW gateway to start making a dial tone is transmitted (step 207). Thereafter, the gateway manager sends an SGCP message to the RGW and starts to ring (step 208).

When the call is answered, the state machine of the outgoing call agent cluster sends a message to the endpoint manager of the incoming call agent cluster indicating that the originating phone is off-hook (step 209). ). The endpoint manager then forwards this message to the state machine with the associated connection setup descriptor (step 210).

Thereafter, the state machine uses the received information to determine an action to perform. In this case, the state machine sends an MCAP message to the gateway manager indicating that the call was answered (step 211). The gateway manager forwards this message to the RGW using SGCP (step 212).

In a preferred embodiment, call agent cluster objects can be shadowed. For example, the call agent cluster may include a second state machine that is idle for use in the event that the first state machine fails. This second state machine does not need to share the same hardware environment as the primary object because the CORBA bus is used in the preferred embodiment and the state machine is stateless.

FIG. 11 is a flowchart of the operation of discarding the connection between the RGWs. This process involves the RGW sending an on-hook message to the incoming call agent cluster (
Initialized at step 301), when this message reaches the message queue of the call agent cluster, it is forwarded to the state machine via the endpoint manager. Incoming call agent cluster sends RG to drop connection
W is instructed (step 302). Then the incoming call agent cluster is M
Sends a CAP message to the outgoing call agent cluster (step 303)
, The outgoing call agent cluster uses SGCP to request that the connection be dropped.
An instruction is given to the GW (step 304). The outgoing call agent cluster then sends a message to the incoming call agent cluster indicating that the above action has been performed (step 305).

FIG. 12 is a flowchart of an operation for setting a connection between TGWs. The process is initialized by the switch sending an initial address message ("IAM") to the incoming call agent cluster, indicating that it is trying to establish a media session between the two subscriber units (step 401). The incoming call agent cluster uses the SGCP to instruct the receiving TGW to set up the connection in receive mode (step 402). Then, the incoming call agent transfers an MCAP message indicating this information to the outgoing call agent cluster (step 403). The outgoing call agent cluster then uses the SGCP to instruct the TGW to set up the connection in transmit / receive mode (step 404). The outgoing call agent cluster sends an IAM message to the switch (step 405). Thereafter, the switch sends an address completion message ("ACM") to the outgoing call agent cluster (step 406).
Then, the outgoing call agent cluster becomes the incoming call agent cluster,
Send an MCAP message indicating that the requested action has been performed (
Step 407). The incoming call agent cluster sends an ACM message to the switch (step 408). Thereafter, the switch sends a response message ("ANM") to the outgoing call agent cluster (step 409).
Then, the outgoing call agent cluster becomes the incoming call agent cluster,
Send an MCAP message indicating that the call was answered (step 410)
. Thereafter, the incoming call agent cluster sets the TG to enter transmit / receive mode.
W is instructed (step 411). The incoming call agent cluster sends an ANM message to the switch (step 412).

FIG. 13 is a flowchart of the operation of discarding the connection of the TGW to the TGW. The process is initialized by the switch sending a release message ("REL") to the incoming call agent cluster (step 501). The incoming call agent cluster instructs the TGW to drop the connection (step 502). Thereafter, the incoming call agent cluster sends the outgoing call agent cluster M
A CAP message is transmitted (step 503). The outgoing call agent cluster instructs the TGW to drop the connection (step 504). The outgoing call agent cluster sends a REL to the switch (step 505). The switch sends a release confirmation ("RLC") to the outgoing call agent cluster (step 506). The outgoing call agent cluster sends an MCAP message to the incoming call agent cluster indicating that the connection has been released (step 507). Thereafter, the incoming call agent cluster sends an RLC message to the switch.

FIG. 14 is a flowchart of an operation for setting a connection between the RGW and the TGW. The process comprises an RGW exchanging some SGCP messages related to the connection setup.
Is initialized by the incoming call agent cluster (step 601). These messages include those that pertain to playing a dial tone, collecting telephone numbers, and entering a receive mode. The incoming call agent cluster indicates to the outgoing call agent cluster that MC is about to set up a media session.
An AP message is transmitted (step 602). Next, the outgoing call agent cluster instructs the TGW to set up a connection in transmit / receive mode (step 603). Thereafter, the outgoing call agent cluster builds an IAM and sends it to the switch (step 604). The switch sends the ACM to the outgoing call agent cluster (step 605). The outgoing call agent cluster then sends an MCAP message to the incoming call agent cluster indicating that the above action has been performed (step 606). Next, the incoming call agent cluster instructs the RGW to start ringing (step 6).
07). The switch sends the ANM to the outgoing call agent cluster (step 608). Thereafter, the outgoing call agent cluster sends an MCAP message to the incoming call agent cluster indicating that the call has been answered (step 609). Then, the incoming call agent cluster instructs the RGW to enter the transmission / reception mode (step 610).

FIG. 15 is a flowchart of the operation of discarding the connection of the RGW to the TGW. RG
W initiates the process by sending an on-hook message to the incoming call agent cluster (step 701) and instructs the RGW to drop the connection (step 702). Then, the incoming call agent cluster sends an MCAP message instructing to cancel the connection to the outgoing call agent cluster (step 703). After that, the outgoing call agent cluster
Send a P message to instruct the TGW to drop the connection (step 70)
4). The outgoing call agent cluster builds a REL and sends it to the switch (step 705). Thereafter, the switch sends an RLC to the outgoing call agent cluster (step 706). Next, the outgoing call agent cluster sends an MCAP message to the incoming call agent cluster indicating that the connection has been released (step 707).

FIG. 16 is a flowchart of the operation of setting the connection of the TGW to the RGW. The switch initiates the process by sending an IAM to the incoming call agent cluster (step 801). Thereafter, the incoming call agent cluster instructs the TGW to set up a connection in receive mode (step 802). Then, the incoming call agent cluster sends an MCAP message regarding the establishment of the connection to the outgoing call agent cluster (step 803). Next, the outgoing call agent cluster sets up the connection in transmit / receive mode and instructs the RGW to start a ring signal (step 804). Thereafter, the outgoing call agent cluster sends an MCAP message to the incoming call agent cluster indicating that the above action has been performed (step 805). The outgoing call agent cluster builds an ACM and sends it to the switch (step 806). R
The GW sends an off-hook message to the outgoing call agent cluster (step 807). The outgoing call agent cluster then sends an MCAP message to the incoming call agent cluster indicating that the call has been answered (step 808). Next, the incoming call agent cluster instructs the TGW to enter transmit / receive mode (step 809). Thereafter, the incoming call agent cluster builds an ANM and sends it to the switch (step 810).
.

FIG. 17 is a flowchart of the operation of canceling the connection of the TGW to the RGW. The switch initializes the process by sending a REL to the incoming call agent cluster (step 901). The incoming call agent cluster instructs the TGW to drop the connection (step 902). Then, the incoming call agent cluster sends an MCAP message indicating that the connection has been discarded to the outgoing call agent cluster (step 903). The outgoing call agent cluster instructs the TGW to drop the connection (step 904). Next, the outgoing call agent cluster sends an MCAP message to the incoming call agent cluster indicating that the connection has been released (step 905). Thereafter, the incoming call agent cluster builds an RLC and sends it to the switch (step 906).

The call agent uses a service broker to establish communication between the incoming call agent cluster and the outgoing call agent cluster. If the subscriber unit wants to establish communication with another subscriber unit, the incoming call agent cluster forwards that information to the incoming service broker. The incoming service broker executes an algorithm for determining the outgoing service broker for the outgoing call agent cluster of the subscriber unit with which the communication is to be established. Next, the outgoing service broker executes an algorithm for determining the relevant outgoing call agent cluster. The service broker uses a routing engine to execute these algorithms, and determines appropriate information using a routing table and a look-up table. Further, in the routing, a function of performing telephone number conversion and connection classification is performed (for example, 800-line telephone or long-distance telephone).

In a preferred embodiment, during initialization, the outgoing call agent cluster's endpoint manager interoperability object reference (“IOR”) is stored in a table in the high speed database so that the routing engine runs properly. Read in. In the preferred embodiment, this table points to the relationship between the IOR of a given endpoint manager and the path of the media session. The routing engine consults this table and, depending on the number dialed, selects the assigned endpoint manager IOR and forwards the MCAP message there,
Establish a connection.

FIG. 18 is a flowchart illustrating this process. When the call agent cluster receives a request from a subscriber unit to establish communication with a second subscriber unit, the message is forwarded from the endpoint manager to the state machine as described above (step 1001). Next, the state machine forwards the request to the incoming service broker using MCAP (step 1002). The incoming service broker uses the routing engine to determine the appropriate outgoing service broker and
The request is transferred using the AP (step 1003). Next, the outgoing service broker uses the routing engine to determine the appropriate outgoing call agent cluster, and forwards the message to its endpoint manager using MCAP (step 1004). Thereafter, the incoming call agent cluster and the outgoing call agent cluster communicate directly with each other (step 1005).

In a preferred embodiment, the network resource database stores information about the network. This network resource database is CORBA
Connected to the bus. Thus, the service broker and the call agent cluster can access this database.

In addition to the call agent and SS7 gateway described above, the IGCS
Call agent manager 186, accounting gateway 182,
An announcement server 184 and an IGCS management agent 188 can be included.

The accounting gateway 182 in the preferred embodiment is a media controller, which communicates start / stop call records to a central point, where the records are sent from CORBA to a remote authentication dial-in user service (“RADIU”).
S ") and then to industry standard BAF records for distribution to back-end billing systems. As shown in FIG. 2, accounting gateway 182 communicates with call agent cluster 210 of call agent 160 in a preferred embodiment.

In a preferred embodiment, the announcement server 184 is a media controller and responds to SGCP messages by playing recorded announcements. As shown in FIG. 2, the announcement server communicates with the call agent cluster 210 of the call agent 160.

The call agent manager 186 is directly responsible for local management of the call agent, for example, displaying the state of the call agent component, and alarms reported by the call agent component and object controls, such as shutdown. Is displayed.

The IGCS management agent 188 of the preferred embodiment manages all IGCS components including the call agent cluster, network resource database, accounting gateway, and announcement server.

In a preferred embodiment, usage statistics accumulated in the call agent cluster can be displayed throughout the network management software. The design of the call agent of the preferred embodiment is based on a Simple Network that can be managed by third party SNMP management software, such as HP open view.
ork Management Protocol ("SNMP"). With this architecture, SNMP settings, acquisitions, and traps can be sent to the call agent SNMP agent, and its function is to collect statistics via CORBA method calls executed on the call agent cluster object. . In addition, SNMP settings are handled by method calls that update data in the call agent cluster.

While the preferred embodiments and methods of the present invention have been described above with reference to the figures, various changes and modifications may be made without departing from the true scope of the invention, and One skilled in the art will appreciate that equivalents can be substituted for the elements.

In addition, many modifications may be made to adapt a particular element, technique, or implementation in accordance with the teachings of the invention without departing from the central scope thereof. Thus, the present invention is not limited to the specific embodiments and methods disclosed, but is intended to include all embodiments falling within the scope of the claims appended hereto.

Appendix A The Multicall Agent Protocol (MCAP) is designed to have the following two functions. 1. Core information logically categorized as follows:

Session management A session connects users (calling party and called party) identified by means such as a calling subscriber number and a called subscriber number. A connection management call consists of a set of connections, each of which connects a pair of call agent clusters. Related resources are keyed by a globally unique ID. Gateway Management Call agents control specific connections on the associated gateway by exchanging information locally keyed by a unique ID. Routing management The routing of specific information. For example, converting toll-free numbers. Service Management Both the calling and called parties can implement certain services with potential interactions. The service execution engine (Service Execution Engine) identifies the related service and determines its application. Parameter Information specific to the MCAP message. For example, version. 2. Transmitted as payload in either native or pre-parsed format
Tunnel for messages of a particular protocol that can. The specific format is specified
It is a octet stream, and the parsed format is specified by the MCAP definition language
Octet stream representation. The following basic message types can support these functions: MCAP_CREATE Establish new connection between call agent clusters. MCAP_EVENT Indicates an event that occurs during the life of the connection. For example, it can be used as a response or notification of a change in connection status. MCAP_DELETE Deletes an existing connection between call agent clusters. MCAP_TUNNEL tunnel, through. A specific protocol message from one call agent cluster to another call agent cluster without giving any other information. Perhaps MCAP_CREATE and MCAP_DELETE are MCAP_
It may be included in EVENT, but it is convenient to distinguish these actions.
is there. MCAP_TUNNEL is generic when a specific protocol is needed
It is prepared so that it can correspond to. The MCAP is informally summarized as follows: NOTE • Items in italics are optional; others are required. • Call ID is a globally unique value defined by the call agent
Yes, and is associated with a connection throughout its lifetime. Related resources
Used as a key to identify・ The return address is used when the message needs to be sent / received later.
The handle that the side uses to find the sender. The connection descriptor is the connection defined and used locally by the gateway
ID and specific real-time protocol (RTP) parameters, such as encoding
Including the law. • Tunnel messages are either in parsed or proprietary format
It is. Early MCAP versions were mainly developed in the development of call agents.
It was the result of experimental work. This version is a rapidly evolving interface.
-Addressing issues presented by Internet Protocol (IP) telephony
Reflects the next steps to be addressed. The formal MCAP reference definition states that the Common Object Request Broker Architecture
(CORBA) 2.0 [1] [2] interface definition language (IDL)
The relevant Internet-to-ORB Protocol (IIOP)
Used for bell "wire" encoding. This is an abstract syntax notation 1 (ASN.1) [3
Using [4] and the accompanying basic coding rule (BER) [4] [5]
Similar to, protocol designers describe structured information in a high-level machine-independent language
Then, the actual encoding can be derived mechanically. I chose CORBA
Used in call agent implementations, and of wide interest within the industry,
This is because ports are also made. This version of MCAP supports the following tunnel protocols: • Simple Gateway Control Protocol (“SGCP”) [6] • Integrated Digital Network User Part (ISUP) [7] The complete MCAP IDL is listed below. • Appendix A1: MCAP IDL • Appendix A2: VOIP Gateway IDL • Appendix A3: Routing IDL • Appendix A4: Service IDL • Appendix A5: Parameter IDL • Appendix A6: SGCP Tunnel IDL • Appendix A7: ISUP Tunnel IDL • Appendix A8: ISUP Message IDL References [1] CORBA: Architecture and Specifica
, OMG, 1997. For CORBA V 2.0 generally supported by the current implementation
I have. For example, INPRISE VisiBroker, V3.2 (Java
). OMG has released V2.2. [2] A. Vogel & K. Duddy, Java Programmi
ng with CORBA, 2 ^nd edition, John Wiley
& Sons, 1998. [3] Recommendation X. 208, Open system
s interconnection: specification of
Abstract Syntax Notation (ASN.1), CCI
TT Blue Book, Fascicle VII. 4, ITU, 1989
Pp. 57-130. [4] D. Steedman, Abstract Syntax Notat
ion One (ASN.1), the Tutorial and Ref
erence, Technology Appraisals, 1993. [5] Recommendation X. 209, Open system
s interconnection: specification of
Basic Encoding Rules for Abstract Sy
ntax Notation (ASN.1), CCITT Blue Boo
k, Facial VII. 4, ITU, 1989, pp. 131-151
. [6] Arango, M .; Huitema, C .; , Simple Gate
way Control Protocol (SGCP), Version
1.0, May 15 '98. [7] GR-317-CORE, Switching Systems Ge
neric Requirements for Call Control
Using the Integrated Services Digita
l Network User Part (ISDN), Issue 2, D
ec. '97. Appendix A1: MCAP IDL #include "mcapVoipGateway.idl"#include"mcapRouting.idl"#include"mcapService.idl"#include"mcapParameter.idl"#include"mcapSgcpTunnel.idl"#include"mcapIsupTunnel.idl" module Mcap { // // MCAP version // const string version = "2.0"; // // Tunnel message definition // enum ProtocolType {SGCP, ISUP}; union TunnelMessage switch (ProtocolType) {case SGCP: McapSgcpTunnel :: SgcpTunnelMessage sgcpTunnelMessag
e; case ISUP: McapIsupTunnel :: IsupTunnelMessage isupTunnelMessag
e;}; union OptionalTunnelMessage switch (boolean) {case TRUE: TunnelMessage tunnelMessage;}; // // MCAP message definition // union OptionalCallingName switch (boolean) {case TRUE: string callingName;}; union OptionalCallingEmailAddress switch (boolean) { case TRUE: string callingEmailAddress;}; union OptionalConnectionDescriptor switch (boolean) {case TRUE: McapVoipGateway :: ConnectionDescriptor connectionDescr
iptor;}; typedef sequence <McapService :: ServiceParameter>ServiceParameters; struct McapCreateMessage {// version string version; // session data string callingNumber; OptionalCallingName callingName; string calledNumber; // connection data string callId; Object returnAddress; // gateway data McapVoipGateway :: ConnectionDescriptor connectionDescriptor; // No routing data // Service data ServiceParameters serviceParameters; // Parameter data McapParameter :: CreateParameter createParameter; // Tunnel data OptionalTunnelMessage tunnelMessage;}; struct McapEventMessage {// Version string version; // No session data // Connection data string callId; Object returnAddress; // gateway data OptionalConnectionDescriptor connectionDescriptor; // no routing data // no service data // parameter data McapParameter :: EventParameter eventParameter; // tunnel data OptionalTunnelMessage tunnelMessage;}; struct McapDeleteMessage {// version string version; // no session data // connection data string callId; // no gateway data // no routing data // no service data // no parameter data McapParameter :: DeleteParameter deleteParameter; // Tunnel data OptionalTunnelMessage tunnelMessage;}; struct McapTunnelMessage {// Version string version; // No session data // Connection data string callId; // No gateway data // No routing data // No service data // No parameter data // Tunnel data 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 module M capVoipGateway {enum AudioState {ON, OFF, UNDEFINED}; enum Mode {SEND_ONLY, RECV_ONLY, SEND_RECV}; union OptionalMode switch (boolean) {case TRUE: Mode mode;}; struct ConnectionOptions {short samplePeriod; // milliseconds string encodingMethod; AudioState audioState; OptionalMode mode; short bandwidth; // KB}; struct ConnectionDescriptor {string connectionId; ConnectionOptions connectionOptions; string sdpSessionDescriptor;};}; Appendix A3: Routing IDL module McapRouting {enum RoutingType {REQUEST, ANNOUNCEMENT, ROUTE, CONNECT}; struct Request Data {string clusterId; boolean onNet;}; union RoutingData switch (RoutingType) {case REQUEST: RequestData requestData;}; struct RoutingParameter {RoutingType type; RoutingData data;};}; Appendix A4: Service IDL module McapService {enum ServiceType {CALLER_ID_BLOCKING, CALL_FORWARDING}; struct CallerIdBlockingtData {boolean block;}; struct CallForwardingData {unsigned long hopCounter; Object returnAddress;}; union ServiceData switch (ServiceType) {case CALLER_ID_BLOCKING: CallerIdBlockingtData callerIdBlocking
Data; case CALL_FORWARDING: CallForwardingData callForwardingDa
ta;}; struct ServiceParameter {ServiceType type; ServiceData data;};}; Appendix A5: Parameter IDL module McapParameter {// // MCAP_CREATE parameter // enum CreateType {CALL, ANNOUNCEMENT}; struct AnnouncementData {long id;}; union CreateData switch (CreateType) {case ANNOUNCEMENT: AnnouncementData announcementData;}; struct CreateParameter {CreateType type; CreateData data;}; // // MCAP_EVENT parameter // enum EventType {CREATED, ANSWERED, SUSPEND, RESUME, RELEASED}; struct EventParameter { EventType type;}; // // MCAP_DELETE parameter // struct DeleteParameter {unsigned long cause;}; // // MCAP_TUNNEL parameter // // no parameters defined}; Appendix A6: SGCP tunnel IDL module McapSgcpTunnel {enum SgcpMessageType {NULL}; struct SgcpTunnelMessage {SgcpMessageType messageType;};}; Appendix A7: ISUP Tunnel IDL #include "mcapIsupMessage.idl" module McapIsupTunnel {enum IsupMessageType {ACM, ANM, BLO, BLA, C CR, CFN, CGB, CGBA, CGU, CGUA, COT, CPG, CQM, CQR, CRA, CRM, CVR, CVT, EXM, FAC, FOT, GRA, GRS, IAM, INF, INR, LBA, PAM, REL, RES, RLC, RSC, SUS, UBA, UBL, USIS}; union ParsedIsupMessage switch (IsupMessageType) {case ACM: McapIsupMessage :: ACMMessage acmMessage; case ANM: McapIsupMessage :: ANMMessage anmMessage; // No BLO parameter // No BLA parameter // no CCR parameter case CFN: McapIsupMessage :: CFNMessage cfnMessage; case CGB: McapIsupMessage :: CGBMessage cgbMessage; case CGBA: McapIsupMessage :: CGBAMessage cgbaMessage; case CGU: McapIsupMessage :: CGUMessage cguMessage; case CGUA: McapIsupMessage :: CGUAMessage case COT: McapIsupMessage :: COTMessage cotMessage; case CPG: McapIsupMessage :: CPGMessage cpgMessage; case CQM: McapIsupMessage :: CQMMessage cqmMessage; case CQR: McapIsupMessage :: CQRMessage cqrMessage; // No CRA parameters case CRM: McapIsupMessage :: CRMMessage crmMessage case CVR: McapIsupMessage :: CVRMessage cvrMessage; // CVR parameter Without meter case EXM: McapIsupMessage :: EXMMessage exmMessage; case FOT: McapIsupMessage :: FOTMessage fotMessage; // no FAC parameter case GRA: McapIsupMessage :: GRAMessage graMessage; case GRS: McapIsupMessage :: GRSMessage grsMessage; case IAM: McapIsupMessage :: IAMMessage iamMessage; case INF: McapIsupMessage :: INFMessage infMessage; case INR: McapIsupMessage :: INRMessage inrMessage; // no LBA parameter // no PAM parameter case REL: McapIsupMessage :: RELMessage relMessage; case RES: McapIsupMessage :: RESMessage resMessage; // No RLC parameter // no RSC parameter case SUS: McapIsupMessage :: SUSMessage susMessage; // no UBA parameter // no UBL parameter // no USIS parameter}; typedef sequence <octet>UnparsedIsupMessage; union IsupMessage switch (boolean) {case TRUE: ParsedIsupMessage parsedIsupMessage; case FALSE: UnparsedIsupMessage unparsedIsupMessage;}; struct IsupTunnelMessage {IsupMessageType messageType; IsupMessage message;};}; Appendix A8: ISUP message IDL module IsupMessage // // start of ISUP parameter definition section // // typedef sequence <octet>bytes; // // access transport // struct ACCESS_TRANSPORT {sequence <string>parmNames; sequence <bytes>parmValues; bytes accessTransport;}; // // automatic congestion level // enum AUTOMATIC_CONGESTION_LEVEL {SPARE, LEVEL1, LEVEL2, LEVEL3}; // // reverse call indicator // enum CHARGE_INDICATOR {NO_INDICATION, NO_CHARGE, CHARGE, SPARE}; enum CALLED_PARTY_STATUS_INDICATOR {NO_INDICATION, SUBSCRIBER_FREE, CONNECT_WHEN_FREE, EXCESSIVE_DELAY}; enum CALLED_PARTY_CATEGORY_INDICATOR {NO_INDICATION, ORDINARY_SUBSCRIBER, PAY_PHONE, SPARE}; enum END_TO_END_METHOD_INDICATOR {NO_END_TO_END_METHOD, PASS_ALONG_METHOD, SCCP_METHOD, PASS_ALONG_AND_SCCP_METHOD}; enum INTERWORKING_INDICATOR {NO_INTERWORKING, INTERWORKING}; enum IAM_SEGMENTATION_INDICATOR { NO_INDICATION, ADDITIONAL_INFO_ADDED}; enum ISDN_USER_PART_INDICATOR {ISUP_UNUSED, ISUP_USED}; enum HOLDING_INDICATOR {HOLDING_NOT_REQUIRED, HOLDING_REQUIRED}; ICE_INDICATOR {INCOMING_HALF_ECHO_DEV_NOT_INCLUDED, INCOMING_HALF_ECHO_DEV_INCLUDED, OUTGOING_HALF_ECHO_DEV_NOT_INCLUDED, OUTGOING_HALF_ECHO_DEV_INCLUDED}; enum SCCP_METHOD_INDICATOR {NO_INDICATION, CONNECTIONLESS, CONNECTION_ORIENTED, CONNECTIONLESS_AND_CONNECTION_ORIENTED_METHOD}; struct BACKWARD_CALL_INDICATOR {CHARGE_INDICATOR chargeIndicator; CALLED_PARTY_STATUS_INDICATOR calledPartyStsInd; CALLED_PARTY_CATEGORY_INDICATOR calledPartyCatInd; END_TO_END_METHOD_INDICATOR endToEndMethodInd; INTERWORKING_INDICATOR interworkingInd; IAM_SEGMENTATION_INDICATOR iamSegInd; ISDN_USER_PART_INDICATOR isdnUserInd; HOLDING_INDICATOR holdingInd; ISDN_ACCESS_INDICATOR isdnAccessInd; ECHO_CONTROL_DEVICE_INDICATOR echoControlDevInd; SCCP_METHOD_INDICATOR sccpMethodInd; D_LINE_PRIVILEGE, CUSTOMER_DEFINED_LINE_PRIVILEGE}; enum BUSINESS_GROUP_ID_TYPE {MULTILOCATION_ID, INTERWORKING_ID}; enum ATTENDANT_STATUS {NO_INDICATION, ATTENDANT_LINE}; enum BUSINESS_GROUP_ID {NO_INDICATION, PUBLIC_NETWORK, NETWORK_DEPENDENT}; enum SUBGROUP_ID {NO_SUBGROUP, SUBGROUP}; enum TERMINATING_LINE_PRIVILEGES {NOTPRESENT, UNRESTRICTED, SEMIRESTRICTED, FULLY_RESTRICTED, FULLY_RESTRICTED_INTRASWITCH, DENIED, SPARE}; enum ORIGINATING_RESTRICTIONS {nOTPRESENT, UNRESTRICTED, SEMIRESTRICTED, FULLY_RESTRICTED, FULLY_RESTRICTED_INTRASWITCH, DENIED, SPARE}; struct BUSINESS_GROUP {PARTY_SELECTOR partySelector; LINE_PRIVILEGE_INFO_IND linePriInfoInd; BUSINESS_GROUP_ID_TYPE businessGrpIDType; ATTENDANT_STATUS attendantSts; BUSINESS_GROUP_ID businessGrpID; bytes BUSINESS_GROUP_ID_network_dependant; SUBGROUP_ID subgroupID; bytes SUBGROUP_ID_subgroup; TERMINATING_LINE_PRIVILEGES terminatingLinePri; ORIGINATING_RESTRICTIONS origRestriction; octet customer_defined_line_pri_code ;}; // // call reference // struct CALL_REFERENCE {bytes CALL_IDENTITY_NUMBER; bytes POINT_CODE;}; // // called subscriber number // calling subscriber number // enum NATURE_OF_ADDRESS_INDICATOR_TYPE1 {SUBSCRIBER_NUMBER, NATIONAL, INTERNATIONAL_NUMBER, ABBREVIATED_BER }; enum NATURE_OF_ADDRESS_INDICATOR_TYPE2 {SPARE, UNIQUE_SUBSCRIBER_NUMBER, RESERVED_FOR_NATIONAL_USE, UNIQUE_NATIONAL_SIG_NUMBER, UNIQUE_INTERNATIONAL_NUMBER, NONUNIQUE_SUBSCRIBER_NUMBER, NONUNIQUE_NATIONAL_NUMBER, NONUNIQUE_INTERNATIONAL_NUMBER, TEST_LINE_CODE, RESERVED_FOR_NETWORK_SPECIFIC}; enum NATURE_OF_ADDRESS_INDICATOR_TYPE3 {SPRARE, SUBSCRIBER_NUMBER, RESERVED_FOR_NATIONAL_USE, NATIONAL_SIGNIFICANT_NUMBER, INTERNATIONAL_NUMBER, OP_REQ_SUBSCRIBER_NUMBER, OP_REQ_NATIONAL_NUMBER, OP_REQ_INTERNATIONAL_NUMBER, OP_REQ_NO_NUMBER_PRESENT, NO_NUMBER_PRESENT_CUT_THROUGH_CALL_TO_CARRIER, CALL_FROM_LOCAL_EXCHANGE , TEST_LINE_CODE, RESERVED_FOR_NETWORK_SPECIFIC}; enum NATURE_OF_ADDRESS_INDICATOR_TYPE4 {NATION AL_SIGNIFICANT_NUMBER}; enum ODD_EVEN_BIT {EVEN, ODD}; enum NUMBERING_PLAN {UNKNOWN, ISDN, SPARE, ITU_TS_DATA, ITU_TS_TELEX, PRIVATE}; enum SCREENING {USER_PROVIDED_NOT_SCREENED, USER_PROVIDED_SCREENING_PASSED, USER_PROVIDED_SCREENING_FAILED, NETWORK_PROVIDED}; enum PRESENTATION {PRESENTATION_ALLOWED, PRESENTATION_RESTRICTED, SPARE}; struct CALLED_PARTY_NUMBER {ODD_EVEN_BIT oddEvenBit; NATURE_OF_ADDRESS_INDICATOR_TYPE3 addressNatureInd; NUMBERING_PLAN numberingPlan; string addressSignal;}; struct CALLING_PARTY_NUMBER // NATCure_OF_ADDRESS_INDICATOR_TYPE2 enum CALLING_PARTY_CATEGORY {CALLING_PARTYS_CATEGORY_UNKNOWN, FRENCH_LANGUAGE_OPERATOR, ENGLISH_LANGUAGE_OPERATOR, GERMAN_LANGUAGE_OPERATOR, RUSSIAN_LANGUAGE_OPERATOR, SPANISH_LANGUAGE_OPERATOR, SPANISH_LANGUAGE_OPERATOR LING_SUBSCRIBER, CALLING_SUBSCRIBER_WITH_PRIORITY, DATA_CALL, TEST_CALL, PAY_PHONE, EMERGENCY_SERVICE_CALL_IN_PROGRESS, HIGH_PRIORITY_CALL_INDICATION, NSEP_CALL, NETWORK_SPECIFIC_USE, RESERVED}; // // carrier identification // enum CI_NETWORK_IDENTIFICATION_PLAN {UNKNOWN, THREE_DIGIT_CARRIER_IDENT_CODE, FOUR_DIGIT_CARRIER_IDENT_CODE, SPARE}; enum CI_TYPE_OF_NETWORK_IDENTIFICATION {SPARE, NATIONAL_NETWORK_IDENTIFICATION}; struct CARRIER_IDENTIFICATION {CI_NETWORK_IDENTIFICATION_PLAN networkIdentPlan; CI_TYPE_OF_NETWORK_IDENTIFICATION typeOfNetwork; string carrierID;}; // // carrier selection // enum CARRIER_SELECTION {NO_INDICATION, SUBS_DESIGNATED_PRESELECTED_CARRIER, SUBS_DESIGNATED_INPUT_CARRIER, SUBS_DESIGNATED_UNDETREMINED_CARRIER, DESIGNATED_BY_CALLER_CARRIER, SPARE, RESERVED}; // // causes indicator // enum CI_LOCATION { USER, LOCAL_PRIVATE_NETWORK, LOCAL_LOCAL_NETWORK, TRANSIT_NETWORK, REMOTE_LOCAL_NETWORK, REMOTE_PRIVATE_NETWORK, INTERNATIONAL_NETWORK, UNKNOWN, SPARE}; enum CI_CODING_STANDARD {ITU_TS_STANDARD, RESERVED_FOR_INTL, ANSI_STANDARD, RESERVED}; struct CAUSE_INDICATORS {sequence <CI_LOCATION>location; sequence <CI_CODING_STANDARD>codingStandard; Boolean diagnosticsFlag; bytes causeValue; bytes diagnostics; numberingPlan; string addressSignal;}; // // circuit assignment map // enum CIRCUIT_ASSIGNMENT_MAP_TYPE {DS1}; enum CIRCUIT_ASSIGNMENT_MAP_STATUS {CIRCUIT_USED, CIRCUIT_NOT_USED}; typedef sequence <CIRCUIT_ASSIGNMENT_MAP_STATUS> CIRCUIT_ASSIGNMENT_MAP
_STATUS_ARRAY; struct CIRCUIT_ASSIGNMENT_MAP {CIRCUIT_ASSIGNMENT_MAP_TYPE type; CIRCUIT_ASSIGNMENT_MAP_STATUS_ARRAY status_array; Unknown, SoftwareHandling, HardwareHandling}; enum CGCI_CONTINUITYCHKREQIND {Unknown, None, Statistical, PerCall}; struct CKT_GRP_CHAR_INDICATORS {CGCI_CARRIERINDICATOR carrierIndicator; CGCI_DOUBLESEIZINGCTRLIND doubleSeizingCtrlInd; CGCI_ALARMCARRIERIND alarmCarrierInd; CGCI_CONTINUITYCHKREQIND continuityChkReqInd;}; // // circuit group monitoring message type indicator // enum CGSMTI_BLOCKINGTYPEIND {WithoutRelease, WithImmediateRelease, RsvdForNationalUse}; struct CKT_GRP_SUPERVISION_MSG_TYPE_IND {CGSMTI_BLOCKINGTYPEIND blockingTypeInd;}; // // Circuit identifier // struct CKT_IDENT_NAME {string tru nkNumber; string CLLI_A; string CLLI_Z;}; // // circuit state indicator // enum CKT_STATE_IND {Transient, Unequiped, IncomingBusyActive, IncomingBusyLocallyBlocked, IncomingBusyRemotelyBlocked, IncomingBusyLocalAndRemoteBlocked, OutgoingBusyActive, OutgoingBusyLocallyBlocked, OutgoingBusyRemotelyBlocked, OutgoingBusyLocalAndRemoteBlocked, Idle, IdleLocallyBlocked, IdleRemotelyBlocked, IdleLocalAndRemoteBlocked} ; typedef sequence <CKT_STATE_IND>CKT_STATE_IND_ARRAY; // // Circuit validity response indicator // enum CVRI_STATE {Successful, Failure}; struct CKT_VALID_RESPONSE_IND {CVRI_STATE state;}; // // Common language location indicator (Common Language Location Indicato
r) // struct CLLI_STRUCT {string town; string state; string building; string building_subdivision;}; // // connection request // struct CONNECTION_REQUEST {bytes localReference; bytes pointCode; octet protocolClass; octet credit;}; // // conducting indicator // enum CONTINUITY_INDICATORS {CONTINUITY_CHECK_FAILED, CONTINUITY_CHECK_SUCCESSFUL}; // // Events // enum EVENT_INDICATOR {SPARE, ALERTING, PROGRESS, IN_BAND_INFO, CALL_FORWARDED_ON_BUSY, CALL_FORWARDED_ON_NO_REPLY, CALL_FORWARDED_UNCONDITIONAL, NOTIFICATION_FOR_SUPP_SRVC, SERVICE_INFO_INCLUDED, RESERVER}; enum EVENT_PRESENTATION {NO_INDICATION, PRESENTATION_RESTRICTED }; struct EVENT_INFORMATION {EVENT_INDICATOR eventIndicator; EVENT_PRESENTATION eventPresentation;}; // // forward call indicator // enum INCOMING_INTERNATIONAL_CALL_INDICATOR {NOT_AN_INCOMING_INTERNATIONAL_CALL, INCOMING_INTERNATIONAL_CALL}; enum ISDN_USER_PART_PREFER_SUPPORT _ALL_THE_WAY, ISUP_REQUIRED_ALL_THE_WAY}; enum PORTED_NUMBER_TRANSLATION_INDICATOR {NOT_TRANSLATED, TRANSLATED}; struct FORWARD_CALL_INDICATORS {INCOMING_INTERNATIONAL_CALL_INDICATOR incoming_International_Call_In
dicator; END_TO_END_METHOD_INDICATOR end_To_End_Method_Indicator; INTERWORKING_INDICATOR interworking_Indicator; IAM_SEGMENTATION_INDICATOR iam_Segmentation_Indicator; ISDN_USER_PART_INDICATOR isdn_User_Part_Indator;
tor; ISDN_ACCESS_INDICATOR isdn_Access_Indicator; SCCP_METHOD_INDICATOR sccp_Method_Indicator; PORTED_NUMBER_TRANSLATION_INDICATOR ported_Number_Translation_Indica
tor;}; // // inclusive address // enum TYPE_OF_ADDRESS {DialedNumber, DestinationNbr, NetworkScreening, NotNetworkScreening, CompletionNumber, PortedNumber, AlternatelyBilledNumber, AssociatedForwardNumber, TransferNumber6, TransferNumber5, TransferNumber4, TransferNumber3, TransferNumber2, TransferNumber1, CESID} _ enum NATURE_INDIC__DDR DIALED_DIGITS, SUPPLEMENTAL, CO
MPLETION, PORTED}; union NATURE_OF_ADDRESS_INDICATOR_UNION switch (NATURE_OF_ADDRESS_INDI
CATOR_KIND) {case DIALED_DIGITS: NATURE_OF_ADDRESS_INDICATOR_TYPE1 aDialedDigits; case SUPPLEMENTAL: NATURE_OF_ADDRESS_INDICATOR_TYPE2 aSupplemental; case COMPLETION: NATURE_OF_ADDRESS_INDICATOR_TYPE3 aCompletion; case PORTED: NATURE_OF_ADDRESS_INDICATOR_TYPE4 aPorted;}; struct GENERIC_ADDRESS {TYPE_OF_ADDRESS typeOfAddr; NATURE_OF_ADDRESS_INDICATOR_UNION natureOfAddr; ODD_EVEN_BIT oddEvenBit; NUMBERING_PLAN numberingPlan; PRESENTATION presentation; string addressSignal; }; // // comprehensive figures // enum TYPE_OF_DIGITS {ACCOUNT_CODE, aUTHORIZATION_CODE, PRIVATE_NETWORK_TRAVELLING_CLASS_MARK, CELL_SITE_SECTOR_IDENTIFIER, ORIGINATING_PARTY_SERVICE_PROVIDER, BILL_TO_NUMBER}; enum ENCODING_SCHEME {BCD_EVEN, BCD_ODD, IA5, BINARY}; struct GENERIC_DIGITS {TYPE_OF_DIGITS type_of_digits; ENCODING_SCHEME encoding_scheme; string digits ;}; // // inclusive names // enum AVAILABILITY {NAME_AVAILABLE, NAME_NOT_AVAILABLE}; enum TYPE_OF_NAME {CALLING_NAME, ORIGINAL_CALLED_NAME, REDIRECTING_N AME, CONNECTED_NAME}; enum GENERIC_NAME_PRESENTATION {PRESENTATION_ALLOWED, PRESENTATION_RESTRICTED, BLOCKING_TOGGLE, NO_INDICATION}; struct GENERIC_NAME {GENERIC_NAME_PRESENTATION presentation; AVAILABILITY availability; TYPE_OF_NAME type_of_NAME; , INCLUDED_HOLD_NOT_PROVIDED}; enum HOLD_PROVIDED_INDICATOR {NOT_PROVIDED, PROVIDED}; enum CALLING_PARTY_CATEGORY_RESPONSE_INDICATOR {NOT_INCLUDED, INCLUDED}; enum CHARGE_INFORMATION_RESPONSE_INDICATOR {NOT_INCLUDED, INCLUDED}; enum SOLICITED_INFORMATION_INDICATOR {SOLICITED, UNSOLICITED}; enum MULTILOCATION_BUSINESS_GROUP_INFO_RESPONSE_INDICATOR {NOT_INCLUDED, INCLUDED}; struct INFORMATION_INDICATORS {CALLING_PARTY_ADDRESS_RESPONSE_INDICATOR calling_party_address_response_indicator; HOLD_PROVIDED_INDICATOR hold_provided_indicator; CALLING_PARTY_CATEGORY_RESPONSE_INDICATOR calling_party_category_ response_indicator; CHARGE_INFORMATION_RESPONSE_INDICATOR charge_information_response_indicator; SOLICITED_INFORMATION_INDICATOR solicited_information_indicator; MULTILOCATION_BUSINESS_GROUP_INFO_RESPONSE_INDICATOR multilocation_business_group_info_response_indicator;}; // // information request indicator // enum CALLING_PARTY_ADDRESS_REQUEST_INDICATOR {NOT_REQUESTED, REQUESTED}; enum INFORMATION_REQUEST_HOLDING_INDICATOR {NOT_REQUESTED, REQUESTED}; enum CALLING_PARTY_CATEGORY_REQUEST_INDICATOR {NOT_REQUESTED, REQUESTED}; enum CHARGE_INFORMATION_REQUEST_INDICATOR {NOT_REQUESTED , REQUESTED}; enum MALICIOUS_CALL_ID_REQUEST_INDICATOR {NOT_REQUESTED, REQUESTED}; enum MULTILOCATION_BUSINESS_GROUP_INFO_INDICATOR {NOT_REQUESTED, REQUESTED}; struct INFORMATION_REQUEST_INDICATOR {CALLING_PARTY_ADDRESS_REQUEST_INDICATOR calling_party_address_request_indicator; INFORMATION_REQUEST_HOLDING_INDICATOR holding_indicator; CALLING_PARTY_CATEGORY_REQUEST_INDICATOR calling_party_category_r equest_indicator; CHARGE_INFORMATION_REQUEST_INDICATOR charge_information_request_indicator; MALICIOUS_CALL_ID_REQUEST_INDICATOR malicious_call_id_request_indicator; MULTILOCATION_BUSINESS_GROUP_INFO_INDICATOR multilocation_business_group_info_indicator;}; // // jurisdiction information // struct JURISDICTION_INFORMATION {string addressSignal;}; // // connection indicator properties // enum SATELLITE_INDICATOR {NO_SATELLITE_CIRCUIT, ONE_SATELLITE_CIRCUIT, TWO_SATELLITE_CIRCUIT, THREE_OR_MORE_SATELLITE_CIRCUIT }; enum CONTINUITY_CHECK_INDICATOR {CONTINUITY_CHECK_NOT_REQUIRED, CONTINUITY_CHECK_REQUIRED, CONTINUITY_CHECK_ON_PREVIOUS_CIRCUIT, SPARE}; struct NATURE_OF_CONNECTION_INDICATOR {SATELLITE_INDICATOR satellite_indicator; CONTINUITY_CHECK_INDICATOR continuity_check_indicator; ECHO_CONTROL_DEVICE_INDICATOR echo_control_device_indicator;}; // // network management control // enum TEMPORARY_ALTERNATIVE_ROUTING {TAR_NO_INDICATION, TAR_CONTROLLED_CALL}; struct NETWORK_MANAGEMENT_C ONTROLS {TEMPORARY_ALTERNATIVE_ROUTING temporaryAlternativeRouting;}; typedef sequence <NETWORK_MANAGEMENT_CONTROLS> NETWORK_MANAGEMENT_CONTR
OLS_ARRAY; // // network transport parameters // struct NETWORK_TRANSPORT_PARAMETER {sequence <string>parmNames; sequence <Bytes>parmValues; bytes networkTransport;}; // // Notification Indicator // enum NOTIFICATION_IND {CALL_COMPLETION_DELAY, CALL_IS_A_WAITING_CALL, TRANSFER_IN_PROGRESS, ISOLATED_FROM_CONFERENCE_CALL, SPLIT_FROM_CONFERENCE_CALL, REATTACHED_TO_CONFERENCE_CALL, ADDED_TO_CONFERENCE_CALL, REMOTE_HOLD, REMOTE_HOLD_RELEASED, CALL_IS_FORWARDED, SPARE, RESERVED}; struct NOTIFICATION_INDICATOR {NOTIFICATION_IND notification_ind;}; typedef sequence <NOTIFICATION_INDICATOR>NOTIFICATION_INDICATOR_ARRAY; // // operator services information // enum INFORMATION_TYPE {UNKNOWN, ORIGINAL_ACCESS_PREFIX, BILL_TO_INFO_ENTRY_TYPE_AND_HANDLE_TYPE, BILL_TO_TYPE, BILL_TO_SPECIFIC_INFO, SPECIAL_HANDLING, ACCESS_SIGNALING}; enum INFOMATION_VALUE_001 {UNKNOWN, A_1OR011, A_0OR01, A_0}; enum INFOMATION_VALUE_010 {UNKNOWN_UNKNOW_HANDLING, OPERATOR_STATION_HANDLING , OPERATOR_PERSON_HANDLING, TONE_INPUT_STATION_HANDLING, UNKNOWN_STATION_HANDLING, UNKNOWN_PERSON_HANDLING, OPERATOR_UNKNOWN_HANDLING, TONE_INPUT_UNKNOWN_HANDLING, TONE_INPUT_PERSON_HANDLING, SPOKEN_INPUT_UNKNOWN_HANDLING, SPOKEN_INPUT_STATION_HANDLING, SPOKEN_INPUT_PERSON_HANDLING}; enum INFOMATION_VALUE_011 {UNKNOWN, CARD14DIGIT, CARD89C, CARDOTHER, COLLECT, THIRDNUMBER, SENTPAID}; enum INFOMATION_VALUE_100 {UNKNOWN, NIDB_AUTHORIZE, NIDB_REPORT_VERIFY_AUTOMATED, NIDB_REPORT_VERIFY_OPERATOR , NO_NIDB_QUERY, NO_NIDB_RESPONSE, NIDB_REPORT_UNAVAILABLE, NO_NIDB_RESPONSE_TIMEOUT, NO _NIDB_RESPONSE_REJECT, NO_NIDB_RESPONSE_ACG, NO_NIDB_RESPONSE_SCCP_FAIL}; enum INFOMATION_VALUE_101 {UNKNOWN, CALL_COMPLETION, RATE_INFO, TROUBLE_REPORT, TIME_CHARGE, CREDIT_REPORT, GENERAL_ASSIST}; enum INFOMATION_VALUE_111 {UNKNOWN, DIAL_PULSE, DIAL_TONE}; enum INFORMATION_VALUE_KIND {kind_001, kind_010, kind_011, kind_100, k
ind_101, kind_111}; union INFORMATION_VALUE_UNION switch (INFORMATION_VALUE_KIND) {case kind_001: INFOMATION_VALUE_001 a001; case kind_010: INFOMATION_VALUE_010 a010; case kind_011: INFOMATION_VALUE_011 a011; case kind_100: INFOMATION_VALUE_100 a. struct OPERATOR_SERVICE_INFO {INFORMATION_TYPE informationType; INFORMATION_VALUE_UNION informationValue;}; typedef sequence <OPERATOR_SERVICE_INFO>OPERATOR_SERVICE_INFO_ARRAY; // // optional backward call indicator // enum IN_BAND_INFORMATION_INDICATOR {NO_INDICATION, IN_BAND_INFO_OR_A_PATTERN_IS_AVAIL}; enum CALL_FORWARDING_MAY_OCCUR_INDICATOR {NO_INDICATION, MAY_OCCUR}; enum NATIONAL_USE {NATIONAL}; enum NETWORK_EXCESSIVE_DELAY_INDICATOR {NO_INDICATION, NETWORK_EXCESSIVE_DELAY_ENCOUNTERED}; enum USER_NETWORK_INTERACTION_OCCURS { NO_INDICATION, CUT_THROUGH_IN_BOTH_DIR}; struct OPTIONAL_BACKWARD_CALL_INDICATORS {IN_BAND_INFORMATION_INDICATOR in_band_information_indicator; CALL_FORWARDING_MAY_OCCUR_INDICATOR call_forwarding_may_occur_indicator; NATIONAL_USE national_use; NETWORK_EXCESSIVE_DELAY_INDICATOR network_excessive_delay_indicator; USER_NETWORK_INTERACTION_OCCURS user_network_interaction_occurs;}; // // calling number // struct ORIGINAL_CALLED_NUMBER {NATURE_OF_ADDRESS_INDICATOR_TYPE2 addressNatureInd; ODD_EVEN_BIT oddEvenBit; PRESENTATION presentation; NUMBERING_PLAN numberingPlan; string addressSignal;}; // // outgoing line information // typedef octet BINARY_EQUIVALENT_OF_THE_II_DIGITS; struct ORIGINATING_LINE_INFORMATION {BINARY_EQUIVALENT_OF_THE_II_DIGITS binary_equivalent_of_the_two_digi
ts;}; // // Outgoing trunk number // enum MULTI_LVL_PP {DEFENSE_SWITCH_NETWORK, SPARE}; struct OUTGOING_TRUNK_GROUP_NUMBER {long outgoing_trunk_group_number;}; // // Priority level // enum PRECEDENCE_LEVEL {FLASH_OVERRIDE, FLASH, PRIMEITY SPARE}; enum LOOK_AHEAD_FOR_BUSY {LOOK_AHEAD_FOR_BUSY_ALLOWED, LOOK_AHEAD_FOR_BUSY_NOT_ALLOWED, PATH_RESERVED, RESERVED}; struct PRECEDENCE {PRECEDENCE_LEVEL precedence_level; LOOK_AHEAD_FOR_BUSY look_ahead_for_busy; long network_identity; long MLPP_service_domain;}; // // range and status // enum sTATUS {NO_BLOCKING, BLOCKING, BLOCKED, UNBLOCKED, NO_BLOCKING_ACKNOWLEDGMENT, BLOCKING_ACKNOWLEDGMENT, NO_UNBLOCKING, UNBLOCKING, NO_UNBLOCKING_ACKNOWLEDGMENT, UNBLOCKING_ACKNOWLEDGMENT}; typedef sequence <STATUS>STATUS_ARRAY; typedef short RANGE; struct RANGE_AND_STATUS {RANGE range; STATUS_ARRAY status_array;}; // // redirection function // enum REDIRECT_CAPABILITY_ENUM {REDIRECTION_POSSIBLE_BEFORE_ACM, REDIRECTION_POSSIBLE_BEFORE_EBM RETYPE <REDIRECT_CAPABILITY>REDIRECT_CAPABILITY_ARRAY; // // redirect counter // struct REDIRECT_COUNTER {octet redirectCounter;}; // // redirect numbers // struct REDIRECTING_NUMBER {NATURE_OF_ADDRESS_INDICATOR_TYPE2 addressNatureInd; ODD_EVEN_BIT oddEvenBit; PRESENTATION; // // redirection information // enum ORIGINAL_REDIRECTING_REASON {UNKNOWN_NOT_AVAILABLE, USER_BUSY, NO_REPLY, UNCONDITIONAL, SPARE, RESERVED}; enum REDIRECTION_COUNTER {NO_REDIRECTION_HAS_OCCURED, REDIRECTED_1_TIME, REDIRECTED_2_TIMES, REDIRECTED_3_TIMES, REDIRECTED_4_TIMES, REDIRECTED_5_TIMES, REDIRECTED_6_TIMES, REDIRECTED_7_TIMES, REDIRECTED_8_TIMES, REDIRECTED_9_TIMES, REDIRECTED_10_TIMES, REDIRECTED_11_TIMES , REDIRECTED_12_TIMES, REDIRECTED_13_TIMES, REDIRECTED_14_TIMES, REDIRECTED_15_TIMES}; enum REDIRECTING_REASON {UNKNOWN_NOT_AVAILABLE, USER_BUSY, NO_REPLY, UNCONDITIONAL, SPARE}; struct REDIRECTION_INFORMATION { REDIRECTION_COUNTER redirection_Counter; ORIGINAL_REDIRECTING_REASON original_redirecting_reason; REDIRECTING_REASON redirecting_reason;}; // // redirect number // struct REDIRECTION_NUMBER {NATURE_OF_ADDRESS_INDICATOR_TYPE3 addressNatureInd; ODD_EVEN_BIT; }; struct REMOTE_OPERATIONS {PROTOCOL_PROFILE protocol_profile; bytes components;}; // // service activation // enum SERVICE_ACTIVATION_ENUM {RESERVED_INTERNATIONAL, CALL_WAITING_ORIGINATING_INVOKED, DIAL_CALL_WAITING_INVOKED, COMPLETE_CALL_REQUEST_ISUP_USED_ALL_THE_WAY, COMPLETE_CALL_REQUEST_ISUP_NOT_USED_ALL_THE_WAY, SPARE, RESERVED_NETWORK_SPECIFIC}; struct SERVICE_ACTIVATION {SERVICE_ACTIVATION_ENUM service_activation_enum;}; typedef sequence <SERVICE_ACTIVATION>SERVICE_ACTIVATION_ARray;RESERVED_FOR_NATIONAL_USE; typedef octet RESERVED_FOR_NETWORK_SPECIFIC_USE; struct SPECIAL_PROCESSING_REQUEST {SPECIAL_PROCESSING_REQUEST_ENUM special_processing_rq; RESERVED_FOR_INTERNATIONAL_USE reserved_for_international_use; RESERVED_FOR_NATIONAL_USE reserved_for_national_use; RESERVED_FOR_NETWORK_SPECIFIC_USE reserved_for_network_specific_use;}; // // suspend resume indicator // enum SUSPEND_RESUME_INDICATOR {ISDN_SUBSCRIBER_INITIATED, NETWORK_INITIATED}; // // transaction request // struct TRANSACTION_REQUEST {bytes transactionID; bytes SCCP_Address;}; // // Over network selection // enum NETWORK_IDENTIFICATION_PLAN_NATIONAL_ANSI_NETWORKS {UNKNOWN, THREE_DIGIT_CARRIER_IDENTIFICATION_WITH_CIRCUIT_CODE, FOUR_DIGIT_CARRIER_IDENTIFICATION_WITH_CIRCUIT_CODE, RESERVED, RESERVED_FOR_NETWORK_SPECIFIC_USE_FLAG}; enum NETWORK_IDENTIFICATION_PLAN_INTERNATIONAL_NETWORKS {UNKNOWN, PUBLIC_DATA_NETWORK_IDENTIFICATION_CODE, PUBLIC_LAND_MOBILE_NETWORK_ID_CODE}; enum TYPE_OF_NETWORK_IDENTIFICATION {ITU_STANDARDIZED_IDENTIFICATION, NATIONAL_NETWORK_IDENTIFICATION}; enum TRANSIT_NETWORK_SELECTION_DIGIT {DIGIT0, DIGIT1, DIGIT2, DIGIT3, DIGIT4, DIGIT5, DIGIT6, DIGIT7, DIGIT8, DIGIT9, SPARE, CODE11, CODE12, END_OF_PULSE_SIGNAL}; enum CIRCUIT_CODE {UNSPECIFIED, INTERNATIONAL_CALL_NO_OPERATOR_REQUESTED, INTERNATIONAL_CALL_OPERATOR_REQUESTED, SPARE, RESERVED_FOR_NETWORK_SPECIFIC_USE_FLAG}; struct TRANSIT_NETWORK_SELECTION {NETWORK_IDENTIFICATION_PLAN_NATIONAL_ANSI_NETWORKS network_identific
ation_plan_ansi_networks; NETWORK_IDENTIFICATION_PLAN_INTERNATIONAL_NETWORKS network_identific
ation_plan_international_networks; TYPE_OF_NETWORK_IDENTIFICATION type_of_network_identification; TRANSIT_NETWORK_SELECTION_DIGIT digit_one; TRANSIT_NETWORK_SELECTION_DIGIT digit_two; TRANSIT_NETWORK_SELECTION_DIGIT digit_three; TRANSIT_NETWORK_SELECTION_DIGIT digit_four; CIRCUIT_CODE circuit_code; octet circuit_code_network_specific_use; octet ansi_network_specific_use;}; // // transmission medium // enum TRANSMISSION_MEDIUM_USED_VALUE {SPEECH, RESERVED_64KBPS_UNRESTRICTED, AUDIO31KHZ, RESERVED_64KBPS_PREFERRED}; struct TRANSMISSION_MEDIUM_USED {TRANSMISSION_MEDIUM_USED_VALUE transmission_medium_used_value;}; // // User service information // User service information prime // enum INFO_TRANSFER_CAPABILITY {Speech, UnrestrictedDigital, RestrictedDigital, Audio3100Hz, Audio7kHz}; kbps384, kbps1472, kbps1536, kbps1920, Multirate}; enum INFO_TRANSFER_MODE (circuit , Packet}; enum USER_INFO_ESTABLISHMENT {Demand}; enum USER_INFO_CONFIGURATION {PointtoPoint}; enum USER_INFO_STRUCTURE {Default, Integrity8kHz, ServiceDataUnitIntegrity, Unstructured}; enum USER_INFO_SYMMETRY {Bidirectional}; enum USER_INFO_LAYER1PROTOCOL {NotPresent, ITUStandardRateAdaptionV110, G771ulawSpeech, G722andG725Audio, NONITUStandardRateAdaption, ITUStandardRateAdaptionV120, ITUStandardRateAdaptionX31HDLC }; enum USER_INFO_LAYER2PROTOCOL {NotPresent, I144OrQ921, X25LinkLevel}; enum USER_INFO_LAYER3PROTOCOL {NotPresent, ANSIT1607, X25Packet}; struct USER_SERVICE_INFORMATION {INFO_TRANSFER_CAPABILITY transferCapability; INFO_CODINGSTANDARD codingStandard; INFO_TRANSFER_RATE transferRate; INFO_TRANSFER_MODE transferMode; USER_INFO_ESTABLISHMENT establishment; USER_INFO_CONFIGURATION configuration; USER_INFO_STRUCTURE structure; INFO_TRANSFER_RATE destToOriginationTransferRate; USER_INFO_SYMMETRY symmetry; octet multirateRateMultiple; USER_INFO_LAYER1PROTOCOL use rlayer1protocol; USER_INFO_LAYER2PROTOCOL userlayer2protocol; USER_INFO_LAYER3PROTOCOL userlayer3protocol;}; struct USER_SERVICE_INFORMATION_PRIME {INFO_TRANSFER_CAPABILITY transferCapability; INFO_CODINGSTANDARD codingStandard; INFO_TRANSFER_RATE transferRate; INFO_TRANSFER_MODE transferMode; USER_INFO_ESTABLISHMENT establishment; USER_INFO_CONFIGURATION configuration; USER_INFO_STRUCTURE structure; INFO_TRANSFER_RATE destToOriginationTransferRate; USER_INFO_SYMMETRY symmetry; octet multirateRateMultiple; USER_INFO_LAYER1PROTOCOL userlayer1protocol; USER_INFO_LAYER2PROTOCOL userlayer2protocol; USER_INFO_LAYER3PROTOCOL userlayer3protocol;}; // // user between the indicators // enum USER_TO_USER_INDICATOR_TYPE {REQUEST, RESPONSE}; enum USER_TO_USER_INDICATOR_RESPONSE {NONE, SERVICE}; enum NETWORK_DISCARD_INDICATOR {NO_INFORMATION, USER_TO_USER_INFORMATION_DISCARDED_BY_NETWORK}; struct USER_TO_USER_INDICATOR {USER_TO_USER_INDICATOR_TYPE user_to_user_indicator; USER_TO_USER_I NDICATOR_RESPONSE user_to_user_indicator_service1; USER_TO_USER_INDICATOR_RESPONSE user_to_user_indicator_service2; USER_TO_USER_INDICATOR_RESPONSE user_to_user_indicator_service3; NETWORK_DISCARD_INDICATOR network_discard_indicator;}; // // user intercellular // enum PROTOCOL_DISCRIMINATOR {USER_SPECIFIC, OSI_HIGH_LAYER, X244, RESERVED1, ASCII, X208X209, V120, T1607, RESERVED2, NATIONAL, RESERVED3}; struct USER_TO_USER_INFORMATION {PROTOCOL_DISCRIMINATOR protocolDiscriminator; octet protocolDiscriminatorReserved2; octet protocolDiscriminatorReserved3; octet protocolDiscriminatorNational; bytes user_to_user_info;}; // // // Start ISUP message definition section // // // // Address complete // Mandatory Fixed Message Part BACKWARD_CALL_INDICATOR backwardCallIndicators; // Optional Parameters ACCESS_TRANSPORT accessTransport; BUSINESS_GROUP businessGroup; CALL_REFERENCE callReference; CAUSE_INDICATORS causeIndicators; CONNECTION_REQUEST connection Request; INFORMATION_INDICATORS informationIndicators; NETWORK_TRANSPORT_PARAMETER networkTransportParameter; NOTIFICATION_INDICATOR_ARRAY notificationIndicatorArray; OPTIONAL_BACKWARD_CALL_INDICATORS optionalBackwardCallIndicators; REDIRECTION_INFORMATION redirectionInformation; REMOTE_OPERATIONS remoteOperations; SERVICE_ACTIVATION_ARRAY serviceActivationArray; TRANSMISSION_MEDIUM_USED TransmissionMediumUsed; USER_TO_USER_INDICATOR user_to_userIndicator; USER_TO_USER_INFORMATION user_to_userInformation;}; // // response // struct ANMMessage {// optional parameter ACCESS_TRANSPORT accessTransport ; BACKWARD_CALL_INDICATOR backwardCallIndicators; BUSINESS_GROUP businessGroup; CALL_REFERENCE callReference; CONNECTION_REQUEST connectionRequest; INFORMATION_INDICATORS informationIndicators; NETWORK_TRANSPORT_PARAMETER networkTransportParameter; IONS remoteOperations; SERVICE_ACTIVATION_ARRAY serviceActivationArray; TRANSMISSION_MEDIUM_USED TransmissionMediumUsed; USER_TO_USER_INDICATOR user_to_userIndicators; USER_TO_USER_INFORMATION user_to_userInformation;}; // // blocking // // struct BLOMessage {} // // struct blocking / // call progress // struct CPGMessage {// mandatory fixed part EVENT_INFORMATION eventInformation; // optional parameter ACCESS_TRANSPORT accessTransport; BACKWARD_CALL_INDICATOR backwardCallIndicators; BUSINESS_GROUP businessGroup; CALL_REFERENCE callReference; CAUSE_INDICATORS causeIndicators; INFORMATION_INDICATORS informationIndicators; NETWORK_TRANSPORT_PARAMETER networkTransportParameter; NOTIFICATION_INDICATOR_ARRAY notificationIndicatorArray; OPTIONAL_BACKWARD_CALL_INDICATORS optionalBackwardCallIndicators; REDIRECTION_NUMBER redirectionNumber; REMOTE_OPERATIONS remoteOperations; SERVICE_ACTIVATION_ARRAY serviceActivationArray; TRANSMISSION_MEDIUM_USED TransmissionMediumUsed; USER_TO_USER_INDICATOR user_to_userIndicator; USER_TO_USER_INFORMATION user_to_userInformation;}; // // Circuit group blocking // struct CGBMessage {// mandatory fixed part CKT_GRP_SUPERVISION_MSG_TYPE_IND circuitGroupSupervisionMessageI
ndicator; // Required variable part RANGE_AND_STATUS rangeAndStatus;}; // // Circuit group blocking acknowledgment // struct CGBAMessage {// Required fixed part CKT_GRP_SUPERVISION_MSG_TYPE_IND circuitGroupSupervisionMessageTypeI
ndicator; // Required variable part RANGE_AND_STATUS rangeAndStatus;}; // // Circuit group reset // struct GRSMessage {// Required variable part RANGE_AND_STATUS rangeAndStatus; // Optional parameter CIRCUIT_ASSIGNMENT_MAP circuitAssignmentMap;}; // // Circuit group reset acknowledgment // struct GRAMessage {// Required variable part RANGE_AND_STATUS rangeAndStatus; // Optional parameter CIRCUIT_ASSIGNMENT_MAP circuitAssignmentMap;}; // // Unblock circuit group // struct CGUMessage {// Required fixed part CKT_GRP_SUPERVISION_MSG_TYPE_IND circuitGroupSupervisionMessageTypeI
ndicator; // Required variable part RANGE_AND_STATUS rangeAndStatus;}; // // Circuit group blocking release acknowledgment // struct CGUAMessage {// Required fixed part CKT_GRP_SUPERVISION_MSG_TYPE_IND circuitGroupSupervisionMessageTypeI
ndicator; // Required variable part RANGE_AND_STATUS rangeAndStatus;}; // // Circuit inquiry // struct CQMMessage {// Required variable part RANGE_AND_STATUS rangeAndStatus; // Optional parameter CIRCUIT_ASSIGNMENT_MAP circuitAssignmentMap;}; // // Circuit inquiry response // struct CQRMessage {// mandatory variable part RANGE_AND_STATUS rangeAndStatus; CKT_STATE_IND_ARRAY circuitStateIndicatorArray;}; // // circuit reservation // struct CRMMessage {// mandatory fixed part NATURE_OF_CONNECTION_INDICATOR natureOfConnectionIndicators;}; // // circuit reservation acknowledgment // // struct CRAMessage {} // // // Circuit validity response // struct CVRMessage {// Required fixed part CKT_VALID_RESPONSE_IND circuitValidationResponseIndicator; CKT_GRP_CHAR_INDICATORS circuitGroupCharacteristicIndicators; // Optional parameter CKT_IDENT_NAME circuitIdentificationName; CLLI_STRUCT CLLICode; //; // struct CVTMessage {} // // // confusion // struct CFNMessage {// Mandatory Variable Part CAUSE_ INDICATORS causeIndicators;}; // // continuity // struct COTMessage {// mandatory fixed part CONTINUITY_INDICATORS continuityIndicators;}; // // continuity check request // // struct CCRMessage {} // // // end // struct EXMMessage {// Optional parameter OUTGOING_TRUNK_GROUP_NUMBER outgoingTrunkGroupNumber;}; // // Function // struct FACMessage {// Optional parameter REMOTE_OPERATIONS remoteOperations; SERVICE_ACTIVATION_ARRAY serviceActivationArray;}; // // Forward transfer // struct FOTMessage {// Optional parameter CALL_REFERENCE callReference;}; // // Information // struct INFMessage {// Required fixed part INFORMATION_INDICATORS informationIndicators; // Optional parameter ACCESS_TRANSPORT accessTransport; BUSINESS_GROUP businessGroup; CALL_REFERENCE callReference; CALLING_PARTY_NUMBER callingPartyNumber; CALLING_PARTY_CATEGORY callingPartyCATEgATION; tingLineInformation; REDIRECTING_NUMBER redirectingNumber; REDIRECTION_INFORMATION redirectionInformation; USER_TO_USER_INFORMATION user_to_userInformation; / initial address // struct IAMMessage {// mandatory fixed part NATURE_OF_CONNECTION_INDICATOR natureOfConnectionIndicators; FORWARD_CALL_INDICATORS forwardCallIndicators; CALLING_PARTY_CATEGORY callingPartyCategory; // mandatory variable part USER_SERVICE_INFORMATION userServiceInformation; CALLED_PARTY_NUMBER calledPartyNumber; // optional parameter ACCESS_TRANSPORT accessTransport; BUSINESS_GROUP businessGroup; CALL_REFERENCE callReference; CALLING_PARTY_NUMBER callingPartyNumber; CARRIER_IDENTIFICATION carrierIdentification; CARRIER_SELECTION carrierSelection; CHARGE_NUMBER chargeNumber; CIRCUIT_ASSIGNMENT_MAP circuitAssignmentMap; CONNECTION_REQUEST connectionRequest; bytes egressService; GENERIC_ADDRESS genericAddress; GENERIC_DIGITS genericDigits; GENERIC_NAME genericName; octet hopCounter; INFORMATION_REQUEST_INDICATOR informationRequestIndicators; JURISDICTION_INFORMATION jurisdictionInformation; NETWORK_MANAGEMENT_CONTROLS_ARRAY networkManagementControlsArray; NETWORK_TRANSPORT_PARAMETER networkTransportParameter; OPERATOR_SERVICE_INFO_ARRAY operatorServiceInfoArray; ORIGINAL_CALLED_NUMBER originalCalledNumber; ORIGINATING_LINE_INFORMATION originatingLineInformation; PRECEDENCE precedence; REDIRECT_CAPABILITY_ARRAY redirectCapabilityArray; REDIRECT_COUNTER redirectCounter; REDIRECTING_NUMBER redirectingNumber; REDIRECTION_INFORMATION redirectionInformation; REMOTE_OPERATIONS remoteOperations; SERVICE_ACTIVATION_ARRAY serviceActivationArray; SERVICE_CODE serviceCode; SPECIAL_PROCESSINGREST special request ; TRANSACTION_REQUEST transactionRequest; TRANSIT_NETWORK_SELECTION transitNetworkSelection; USER_SERVICE_INFORMATION_PRIME userServiceInformationPrime; USER_TO_USER_INFORMATION user_to_userInformation;}; // // Loopback acknowledgment // // struct LPAMessage {} // // // Passing // // struct PAMMessage // release // struct RELMessage {// mandatory variable part CAUSE_INDICATORS causeIndicators; // optional parameter ACCESS_TRANSPORT accessTransport; AUTOMATIC_CONGESTION_LEVEL automaticCongestionLevel; CALL_REFERENCE callReference; CHARGE_NUMBER chargeNumber; // release of GENERIC_ADDRESS generic_address; / // struct RLCMessage {} // // // circuit reset // // struct RSCMessage {} // // // resume // struct RESMessage {// mandatory fixed part SUSPEND_RESUME_INDICATOR suspend_resumeIndicators; // optional parameter CALL_REFERENCE callReference; }; // // suspend // struct SUSMessage {// mandatory fixed part SUSPEND_RESUME_INDICATOR suspend_resumeIndicators; // optional parameter CALL_REFERENCE callReference;}; // // unblocking // // struct UBLMessage {} // // // blocking Release acknowledgment // // struct UBAMessage {} // // // Unequipped Circuit Identification Code // // struct UCICMessage {} //}; Appendix B # SGCP Call Model # # = ================================================== ============== # Event: # # Format: Event <eventName><sideofcall>## SetTopBox Events # # Start OffHook call (in) or answer ring # DialComplete Collected digits for called number (in) # OnHook Hangup (in or out) # # Ingress Events # # Created Confirm creation # Answered View answered calls # Released Confirm deletion # Suspended Hang up # Resumed
# Select backup for # Delete Delete local connection # TimerExpired Timer timeout # Busy "Out", busy called number
# Announcement Announcement must be identified # InvalidEndpoint "Out" indicates an invalid called number # # Outgoing event # # Create Establish connection # Released Confirm delete # Delete Local connection Destroy # TimerExpired Timer timeout # Called number talks when Busy is established
# Announcement that was in the middle of the announcement must be played # InvalidEndpoint Received invalid called number # # Transition: # # Format: Transition <curState><nextState>## Idle connection is inactive # Dialing Collecting digits for the called number with "In"# Ringing Ringing the called number with "Out"# Active connection is made Full-duplex # Suspended Active session is suspended # Releasing Incoming or outgoing local resource release # Initiated "In" waiting for establishment confirmation # Delivered "In" waiting for "out" response # * (optional)-optional Wildcard in state # # "Wildcard" matches in supported transition states
# CurState = * nextState = * # However, * in curState means a match in any current state # * in nextState means that the state is not changed # # Action: # # Format: Action <actionName><parms>## CreateConnection Call VOIP gateway,
Establish a new connection # Call the ModifyConnection VOIP gateway,
Modify an existing connection # Call the DeleteConnection VOIP gateway,
Delete existing connection # Call NotifyRequest VOIP gateway
The event is notified. # # AccountingStart Call the accounting gateway interface with the start record. # AccountingStop Stop the record with the accounting gateway.
Call the gateway interface # # Call out the McapCreate establishment message
# McapEvent event message in / out Send to call agent partner # McapDelete event message in / out
Send to outgoing call agent partner # # StartTimer Call agent endpoint
Requests the point manager to start the timer # SequenceError Handles out-of-order event conditions # # Modifiers: # # These modifiers are valid for all actions. # Indicates whether to continue the transition to the next action, and stops if an error occurs. # # # FatalOnError Stop if error occurs # Continue OnError Continue # These qualifiers are used to identify the event type by the MCapEvent action. # # Created EventType = Create # Answered EventType = Answer # Released EventType = Release # Suspended EventType = Suspend # Resumed EventType = Resume # # These qualifiers are used by the MCapCreate action to identify the creation type. # # Announce CreateType = Announce # # These modifiers are valid for events that can have two flavors. Other events imply ingress / egress identity. # # Ingress Caller # Egress Callee # # These qualifiers identify the TimerType initiated by the StartTimer action. #millsec indicates the time of the timer in millisecond units. # # Dial <#millsec> Wait for DialComplete message # Create <#millsec> Wait for a message created from "Out"# Release <#millsec> Wait for connection to be deleted # # This modifier is used to identify the busy state of the mcapDelete event. # # Busy Line unavailable, busy, busy # # These qualifiers identify the action to take when passing # an event sequence error condition. # # Ignore Ignore out-of-order conditions # Report Only report out-of-order conditions # Reset Reset line to idle and
Release Local Resources # # These qualifiers specify the VOIP gateway attributes that are passed in CreateConnection, ModifyConnection, #DeleteConnection, and NotifyRequest. # # Set the ReceiveMode connection to receive-only mode # SendReceiveMode Set the connection to full-duplex mode # Set the SendMode connection to send-only mode # Set the InactiveMode connection to inactive # # LoopBackMode ??? # # Operate the OpCompleteNotify call agent Notify completion # OffHookNotify-Off hook to call agent
# OnHookNotify Call agent on-hook
# FlashHookNotify Notify a call agent of a flash hook # WinkNotify Call agent winks
# DTMFNotify DTMF to call agent
# ContinuityToneNotify # ContinuityDetectedNotify # ModemToneNotify Notify the call agent of the modem dial tone # Notify the FaxToneNotify call agent of the fax dial tone # DigitsNotify Number collected by the call agent
# RingingSignal Play ringtone # RingBackSignal Play ringback tone # DialToneSignal Play dial tone # BusyToneSignal Play busy tone # CongestionToneSignal Play congestion tone # AnnouncementSignal-Play announcement # ContinuitySignal Play continuity tone # CallWaitingSignal Play ringtone during a call # OffHookWarningSignal-Play off-hook alert tone # # ======================== ========================================== # --- # Calling party Set-Top-Box OffHook # --- Event OffHook Ingress Transition Idle Dialing Action NotifyRequest DigitsNotify DialToneSignal OnHookNotif
y Action StartTimer Dial 45 Transition Active Active # # Callee Set-Top-Box OffHook # Event OffHook Egress Transition Ringing Active Action McapEvent Answered Action NotifyRequest OnHookNotify Transition Active Active Transition Suspended Active Action McapEvent Resumed # #-# DialCompleted '' Only #-Event DialComplete Transition Dialing Initiated Action CreateConnection OnHookNotify ReceiveMode Action McapCreate Action StartTimer Create 45 Transition Idle Initiated Action CreateConnection OnHookNotify ReceiveMode Action McapCreate Action StartTimer Create 45 # # Create `` Out '' only # Event Create Transition Idle Ringing Action CreateConnection OffHookNotify RingingSignal SendRecei
veMode Action McapEvent Created # # Busy `` On '' only # Event Busy Ingress Transition Active Idle Action DeleteConnection OnHookNotify OffHookNotify BusyTo
neSignal # Transition Initiated Idle Transition Initiated * Action DeleteConnection OnHookNotify OffHookNotify BusyTo
neSignal Transition Delivered Idle Action DeleteConnection OnHookNotify OffHookNotify BusyTo
neSignal # # # Busy "Out" only # Event Busy Egress Transition * * Action McapDelete Busy # # # Announcement "In" only # Event Announcement Ingress Transition * * Action McapCreate Announce # # # Announcement "Out" only # Event Announcement Egress Transition * * Action CreateConnection OpCompleteNotify AnnouncementSignal Sen
dMode # # # InvalidEndpoint “On” # Event InvalidEndpoint Ingress Transition Active Idle Action DeleteConnection OnHookNotify OffHookNotify BusyT
oneSignal Transition Initiated Idle Action DeleteConnection OnHookNotify OffHookNotify BusyT
oneSignal Transition Delivered Idle Action DeleteConnection OnHookNotify OffHookNotify BusyT
oneSignal # # # InvalidEndpoint "Out"# Event InvalidEndpoint Egress Transition * * Action McapDelete InvalidEndpoint # # # Created "In" only # Event Created Transition Dialing Delivered Transition Initiated Delivered # Action ModifyConnection OnHookNotify RingBackSignal ReceiveMod
e Action ModifyConnection OnHookNotify RingBackSignal SendReceiv
eMode # # # Answered `` On '' only # Event Answered Transition Idle Active Transition Initiated Active # Action ModifyConnection OnHookNotify SendReceiveMode Action NotifyRequest OnHookNotify Action AccountingStart Transition Delivered Active # Action ModifyConnection OnHookNotify SendReceiveMode Action NotifyRequest OnHookNotify Action AccountingStart # # # Caller Set-Top −Box OnHook # Event OnHook Ingress Transition Releasing Idle Action NotifyRequest OnHookNotify OffHookNotify Transition Active Releasing Action McapDelete Action DeleteConnection OnHookNotify OffHookNotify Action StartTimer Release 45 Transition Dialing Idle Action NotifyRequest OnHookNotify OffHookNotify Transition Initiated Releasing Action MookDelete Action DeleteHatchNotifyAction Releasing Action McapDelete Action DeleteConnection OnHookNotify OffHookNotify Action StartTimer Release 45 Transition * Idle Ac tion NotifyRequest OnHookNotify OffHookNotify # # --- # OnHook of Callee Set-Top-Box # --- Event OnHook Egress Transition Releasing Idle Action NotifyRequest OnHookNotify OffHookNotify Transition Active Suspended Action NotifyRequest OnHookNotify OffHookNotify Action StartTimer Release 15 Action McapEvent Suspended Action Idle Action NotifyRequest OnHookNotify OffHookNotify # #-# Caller Set-Top-Box Delete #-Event Delete Ingress Transition Active Idle Action McapEvent Released Action DeleteConnection OnHookNotify OffHookNotify Action AccountingStop Transition Idle Idle Action McapEvent Released Action NotifyRequest OnHookNotify OffHookNotify Transition Dialing Dialing Action McapEvent Released Transition Releasing Idle Action NotifyRequest OnHookNotify OffHookNotify Action AccountingStop Transition Initiated Idle Action McapEvent Released Action DeleteConnection OnHookNotify OffHookNotify Action AccountingS top Transition Delivered Idle Action McapEvent Released Action DeleteConnection OnHookNotify OffHookNotify Action AccountingStop # # --- # Callee Set-Top-Box Delete # --- Event Delete Egress Transition Active Idle Action McapEvent Released Action DeleteConnection OnHookNotify OffHookNotify Transition Suspended Idle Action McapEvent Released Action DeleteConnection OnHookNotify OffHookNotify Transition Idle Idle Action McapEvent Released Action NotifyRequest OnHookNotify OffHookNotify Transition Ringing Idle Action McapEvent Released Action DeleteConnection OnHookNotify OffHookNotify Transition Releasing Idle Action NotifyRequest OnHookNotify OffHookNotify # # --- # Initiating SetoTopo -Event Released Ingress Transition Releasing Idle Action AccountingStop Action NotifyRequest OnHookNotify OffHookNotify Transition * * Action AccountingStop # #-# Callee Set-Top-Box Re used #-Event Released Egress Transition Releasing Idle Action NotifyRequest OnHookNotify OffHookNotify Transition Suspended Idle Action NotifyRequest OnHookNotify OffHookNotify Transition * * # # ------- # Expired Timer # before dialing the number # ------- Event TimerExpired Dial Transition Dialing Idle Action NotifyRequest OnHookNotify OffHookNotify DialToneSi
gnal # # --- # Expire Timer waiting for Create ACK # --- Event TimerExpired Create Transition Initiated Idle Action McapDelete Action DeleteConnection OnHookNotify OffHookNotify # # ------------- # Set hang-up delay interval Wait Expired Timer # ------------- Event TimerExpired Release Transition Suspended Releasing Action McapDelete Action DeleteConnection OnHookNotify OffHookNotify Transition Releasing Idle Action NotifyRequest OnHookNotify OffHookNotify

[Brief description of the drawings]

FIG. 1 is a block diagram of an IGCS system according to an embodiment of the present invention.

FIG. 2 is a diagram of a call agent according to one embodiment of the present invention.

FIG. 3 shows two TGWs on a packet-switched base network according to one embodiment of the present invention.
It is a figure which shows the connectivity between them.

FIG. 4 illustrates RGW and TG on a packet-switched base network according to an embodiment of the present invention.
FIG. 4 is a diagram showing connectivity with W.

FIG. 5 shows two RGWs on a packet-switched base network according to one embodiment of the present invention.
It is a figure which shows the connectivity between them.

FIG. 6 shows a call agent and TG for RGW connection management according to an embodiment of the present invention.
It is a figure of the call agent cluster for W connection management.

FIG. 7 is a diagram of a call model supported by a call agent cluster according to an embodiment of the present invention.

FIG. 8 is a diagram of a call model supported by a conventional switch.

FIG. 9 is a flowchart of an RGW-RGW connection setting according to an embodiment of the present invention;

FIG. 10 is a flowchart of a call agent cluster supporting RGW-RGW connectivity according to an embodiment of the present invention.

FIG. 11 is a flowchart of an RGW-RGW connection tear down according to an embodiment of the present invention;

FIG. 12 is a flowchart of a TGW-TGW connection setting according to an embodiment of the present invention;

FIG. 13 is a flowchart of discarding a TGW-TGW connection according to an embodiment of the present invention;

FIG. 14 is a flowchart of an RGW-TGW connection setting according to an embodiment of the present invention;

FIG. 15 is a flowchart of RGW-TGW connection discarding according to an embodiment of the present invention;

FIG. 16 is a flowchart of a TGW-RGW connection setting according to an embodiment of the present invention;

FIG. 17 is a flowchart of discarding a TGW-RGW connection according to an embodiment of the present invention;

FIG. 18 illustrates a service broker (connection service) of connection setting according to an embodiment of the present invention.
FIG.

──────────────────────────────────────────────────続 き Continued on the front page (72) Inventor Carl Lewis United States 07960 Mauricetown South Street 445, New Jersey Inventor Cook Michael United States 07960 Mauricetown South Street 445, New Jersey Inventor Ellie Thomas Chambers United States 08807 Bridgewater, Delaware Drive, New Jersey 1178 (72) Inventor Hutema Christian United States 10012 New York, New York Breaker Street 77 Apartment 119 N (72) Inventor Offlock Frederick United States 07960 Maurice, New Jersey Town South Street 445 (72) Inventor Smic Derek A. United States 08854 Piscataway, New Jersey Piscataway Zirkel Avenue 15 F-term (Reference) 5K030 GA11 HA08 HA10 HB01 HC01 HC02 HD03 JT01 KX30 LA14 MC09 5K034 AA05 BB06 CC05 DD03 EE11 EE12 HH01 HH02 HH63 TT02 5K05 AJ09 FF03 CC01 DD04

Claims (43)

[Claims] 1. A communication system, comprising: a packet-switched base network; a first subscriber unit; a first medium control device connecting the first subscriber unit to the packet-switched base network; 2 subscriber units, a second media control unit for connecting the second subscriber unit to the packet-switched base network, and a call agent, the call agent comprising: A communication system comprising: means for managing communication between a subscriber unit and said second subscriber unit; and means for transmitting and / or receiving SS7 signal information. 2. The system according to claim 1, wherein said first subscriber unit is coupled to said packet-switched base network via a public switched network. 3. The system of claim 1, wherein said packet-switched base network is an Internet Protocol network. 4. The system of claim 1, wherein said packet-switched base network is an asynchronous transfer mode network. 5. The system of claim 1, wherein said call agent further comprises means for transmitting information to a media controller. 6. The system according to claim 5, wherein a simple gateway control protocol is used for the information transmitted to the medium control device. 7. The system according to claim 5, wherein said medium control device is an Internet Protocol gateway. 8. A communication system, comprising: a first subscriber unit coupled to a network through a first media control device; and a second subscriber unit coupled to the network through a second media control device. And a call agent, the call agent comprising a first call agent cluster coupled to the first subscriber unit through a media control device, the call agent cluster comprising: a first call agent cluster according to a first protocol. Means for converting information received from the first media control device into a common protocol; means for communicating with a second call agent cluster using the common protocol; and converting the information according to the common protocol into the first protocol. Means for converting, the first subscriber unit and the second Means for controlling said first media control device for managing a media session with two subscriber units. 9. The system according to claim 8, wherein said first media control device is a residential gateway. 10. The system further comprising a third media controller, wherein the third media controller is a transit gateway, and wherein the first call agent comprises means for controlling the third media controller. The system of claim 8, wherein the first media controller is an SS7 gateway. 11. The medium control device according to claim 1, wherein The system of claim 8, wherein the system is a H.323 gateway. 12. The call agent further comprises a service broker, the service broker determining means for receiving information from the first call agent cluster, and determining the second call agent cluster from a plurality of call agent clusters. Means for transmitting to the second call agent cluster information relating to an operation for setting up communication with the first call agent cluster, and wherein the first call agent cluster transmits information to the service broker. 9. The system of claim 8, further comprising means for transmitting a. 13. The call agent further comprises a network resource database, the database comprising: means for storing data; means for receiving a request from the service broker; and means for transmitting information to the service broker. 13. The system according to claim 12, wherein: 14. The system according to claim 8, wherein said network is an IP network. 15. The system according to claim 8, wherein said network is an ATM network. 16. The system of claim 8, wherein said first call agent cluster and said second call agent cluster communicate over a CORBA software bus. 17. The system according to claim 8, further comprising an accounting gateway, said gateway comprising means for transmitting information to a billing system.
System. 18. The system of claim 8, further comprising an announcement server, said server comprising means for playing back pre-recorded messages. 19. The system of claim 8, wherein said common protocol is a multi-call agent protocol. 20. The first call agent cluster comprising: an endpoint manager; and a state machine, wherein the endpoint manager stores information in a media session; and transmits information to the state machine. 9. The system of claim 8, comprising: and wherein the state machine comprises: means for receiving information from the endpoint manager; and means for performing an action using the information. 21. The first call agent cluster further comprises a message queue, wherein the message queue receives information from a subscriber unit, stores the information, and stores information in the endpoint manager. 21. The system of claim 20, comprising means for transmitting 22. The first call agent cluster further comprises a gateway object, the gateway object comprising: means for communicating with the state machine; and means for managing a first gateway. Item 9. The system according to Item 8. 23. The first call agent cluster further comprises a message handler, the handler determining an endpoint manager from a plurality of endpoint managers, receiving information, the determined end. 9. A system according to claim 8, comprising means for transmitting information to a point manager. 24. The system of claim 8, further comprising a switch linking said first subscriber unit to said first media controller. 25. The system of claim 8, wherein the call agent further comprises means for embedding information according to a first protocol into a common protocol. 26. A method for managing communications between a first subscriber unit and a second subscriber unit on a network, the call agent comprising: Sending and / or receiving signaling information; the call agent managing communications between the first subscriber unit and the second subscriber unit over a network; the first subscription Communicating between a subscriber unit and the second subscriber unit over a network. 27. The method according to claim 26, wherein said first subscriber unit is connected to said call agent via a public switched network. 28. The method of claim 26, wherein said packet-switched based network is an Internet Protocol network. 29. The method of claim 26, wherein said packet-switched base network is an asynchronous transfer mode network. 30. The method of claim 26, further comprising the step of the call agent sending information to a media controller. 31. The method of claim 30, wherein a simple gateway control protocol is used for the information sent to the media controller. 32. The method of claim 30, wherein said media controller is an Internet Protocol gateway. 33. A method for managing communication between a first subscriber unit and a second subscriber unit, wherein the first medium control device coupled to the first subscriber unit comprises: Sending information according to a first protocol to a first call agent cluster regarding an operation of establishing a media session with the second subscriber unit over a packet-switched base network; and wherein the first call agent cluster Converting the information according to a first protocol into a common protocol; setting up a connection between the first call agent cluster and a second call agent cluster; The second call agent cluster exchanges information using a common protocol Step; the first call agent cluster converting information according to the common protocol into the first protocol; and the first call agent cluster converts the information according to the first protocol into the first subscription. Transmitting to the first medium control device coupled to the party unit; the second call agent cluster converting information according to the common protocol into a second protocol; and the second call agent. A cluster transmitting the information according to the second protocol to a second medium control device coupled to the second subscriber unit; and the first subscriber unit and the second subscriber unit. And exchanging information on the network. Law. 34. The method of claim 33, wherein said first media control device is a residential gateway. 35. The first medium control device, comprising: The method of claim 33, wherein the method is a H.323 gateway. 36. The first call agent cluster further comprising transmitting information to a third media control device, wherein the third media control device is a transit gateway, and the first media control The method of claim 33, wherein the device is an SS7 gateway. 37. Establishing a connection between the first call agent cluster and the second call agent cluster, wherein the first call agent cluster sends information to a service broker; The service broker comprises a sub-step of determining the second call agent cluster from a plurality of call agent clusters, and the service broker transmitting information to the second call agent cluster. 34. The method according to claim 33. 38. The method of claim 37, further comprising: the service broker sending a request to a network resource database; and the network resource database sending information to the service broker. the method of. 39. The method according to claim 33, wherein said network is an IP network. 40. The method according to claim 33, wherein said network is an ATM network. 41. The method of claim 33, wherein said call agent cluster communicates over a CORBA bus. 42. The method of claim 33, wherein said call agent cluster communicates using a multi-call agent protocol. 43. The method of claim 33, wherein the information according to the first protocol is embedded in the information according to the common protocol.