KR100798189B1 - Method for confirmating of a situation terminal different protocol - Google Patents

Abstract

It is published about a method of checking terminal status between heterogeneous protocols.

A method for checking a terminal state between different protocols of the present invention includes transmitting a call connection request message to a user terminal based on an arbitrary protocol to receive an ACD service; Any protocol server to which the user terminal is subscribed receives a call connection request message and checks the status of all ACD terminals that provide the ACD service received through the multiprotocol address and port; Any protocol server to which a user terminal is subscribed searches for an ACD terminal capable of making a call connection and performs a call connection with the user terminal. It includes the steps provided to all protocol servers that are provided with.

Therefore, since a server based on a specific protocol can check the state of a terminal based on a heterogeneous protocol in real time, a more efficient ACD service can be provided.

Protocol, ACD terminal, terminal status confirmation message

Description

How to check terminal status in heterogeneous protocol environment {METHOD FOR CONFIRMATING OF A SITUATION TERMINAL DIFFERENT PROTOCOL}

1 is a schematic diagram showing a call connection system between conventional heterogeneous protocols.

Figure 2 is a schematic diagram showing a system for making a call connection through a multiprotocol server in a conventional heterogeneous protocol.

3 is a schematic diagram showing call connectivity in a heterogeneous protocol according to a preferred embodiment of the present invention.

4 is a flowchart illustrating a call connection method in a heterogeneous protocol according to a preferred embodiment of the present invention.

<Description of reference numerals appearing in the drawing>

300: multicast port 310: H.323 user terminal

320: SIP user terminal 330: H.323 ACD terminal

340: gatekeeper 350: SIP ACD terminal

360: H.323 / SIP Gateway

The present invention relates to a method for checking a terminal state in a heterogeneous protocol environment. More specifically, a predetermined protocol server providing an ACD service checks in real time an ACD terminal state based on a heterogeneous protocol through a multicast address and a port. The present invention relates to a terminal state checking method in a heterogeneous protocol environment.

In recent years, information and communication technologies centered on networks have been rapidly developed. The information communication technology is moving away from the technology of transmitting only data and transmitting video and voice together. Such a technology for enabling voice communication in a data network is called VoIP (Voice over Internet Protocol).

There are various protocols for supporting such VoIP services, and the representative ones are H.323 protocol and Session Initiation Protocol (SIP) protocol.

The H.323 protocol is a standard proposed by the International Telecommunication Union Telecommunication Standardization Sector (ITU-T), and the SIP protocol is defined by the Internet Engineering Task Force (IETF).

Currently, most commercial solutions (Solution) consists of a system based on the H.323 protocol, but because the H.323 protocol is difficult to support such as lack of scalability, security, and additional services, As a protocol, the SIP protocol, which refers to the protocol communication method of HTTP as it is, is gradually spreading as an Internet telephony protocol.

1 is a schematic diagram showing a call connection system in a conventional heterogeneous protocol.

As illustrated in FIG. 1, the H.323 terminal 110 based on the gatekeeper 100 and the SIP terminal 130 based on the SIP server 120 will be described below.

When the H.323 terminal 110 transmits a call connection request message for a call with a terminal based on the H.323 protocol, a gatekeeper 100 serving as an intermediate server is used. Connect the call between the H.323 terminal 110.

When the SIP terminal 130 also wants to call the SIP terminal 130 based on the SIP protocol, the SIP server 120 connects the calls between the SIP terminals 130.

Meanwhile, when the H.323 terminal 110 (or the SIP terminal) requests a call connection with the terminal 130 (or the terminal based on the H.323 protocol) based on the SIP protocol, H. 323. The 323 / SIP gateway 140 converts the call connection request message to the SIP / H.323 protocol and then connects the call.

At this time, the H.323 terminal 110 to call the SIP server 120 through the gatekeeper 100, H.323 / SIP gateway (Gateway) 140 to make a call with the SIP terminal 130 After receiving the permission for call connection, the H.323 terminal 110 and the SIP terminal 130 can make a call.

In this case, only when the gatekeeper 100 and the SIP server 120 are manufactured by the same company, a private channel or a communication message may be arbitrarily set to check the state of the terminal in real time.

However, in the above method, the gatekeeper 100 cannot check the state of the terminal belonging to the SIP server of another company product, and the SIP server 120 also belongs to the gatekeeper of another company product. There is a problem that cannot be confirmed.

2 is a schematic diagram illustrating a system for performing a call connection through a multiprotocol server in a conventional heterogeneous protocol.

As shown in FIG. 2, a call connection service using a multiprotocol includes a plurality of H.323 terminals 210, a plurality of SIP terminals 220, and a multiprotocol server 200.

The multiprotocol server 200 includes the functions of the gatekeeper 202 and the SIP server 204, and manages the states of all terminals based on the gatekeeper 202 and the SIP server 204.

Accordingly, the multiprotocol server 200 receiving the call connection request message from any H.323 terminal 210 or the SIP terminal 220 manages the state of all terminals by performing a call connection to each protocol terminal. can do.

However, when the multiprotocol server 200 performs the upgrade, only the software produced by the manufacturer of the multiprotocol server 200 should be used.

In order to effectively solve the above problems of the prior art, a first server based on a predetermined protocol and a second protocol server based on a different protocol from the first server provide efficient ACD services. It is an object of the present invention to provide a method for checking a terminal state in a heterogeneous protocol environment capable of checking in real time the state of terminals belonging to a heterogeneous protocol through a predetermined multicast address and port.

In order to achieve the above technical problem, a method for checking a terminal state between heterogeneous protocols includes transmitting a call connection request message to a user terminal based on an arbitrary protocol to receive an ACD service;

Checking, by any protocol server to which the user terminal is subscribed, all ACD terminal states that receive the call connection request message and provide the ACD service received through a multiprotocol address and port;

Any protocol server to which the user terminal is subscribed searches for an ACD terminal capable of call connection, performs a call connection with the user terminal, and displays the state of the ACD terminal where the call connection is performed through the multiprotocol address and port. It includes the steps provided to all protocol servers provided by the ACD service provider.

Hereinafter, a method of checking a terminal state in a heterogeneous protocol according to an exemplary embodiment of the present invention will be described in detail with reference to FIGS. 3 and 4.

In order to explain a method for checking a terminal state in a heterogeneous protocol environment of the present invention, an H.323 and a SIP protocol, which are representatively used protocols, will be described as an embodiment.

3 is a schematic diagram illustrating a system for checking a terminal state in a heterogeneous protocol environment according to an embodiment of the present invention.

As shown in FIG. 3, a system for providing an ACD service by checking a terminal state between heterogeneous protocols includes a plurality of H.323 user terminals 310, a SIP user terminal 320, and a plurality of Hs for providing an ACD service. A gatekeeper 340 for performing a call connection between the .323 ACD terminal 330 and the terminal, a plurality of SIP ACD terminals 350, a SIP server 360 for performing a call connection, and the H.323 ACD terminal 330 and a multicast address and port 300 for receiving a terminal status message from the SIP ACD terminal 350 and transmitting the terminal status message to the gatekeeper 340 and the SIP server 360.

The H.323 ACD terminal 330 and the SIP ACD terminal 350 transmit a terminal status confirmation message through a predetermined multicast address and port 300 to provide an ACD service more efficiently. The server 360 transmits to the terminals joined to the multicast address and the port 300.

In this case, the terminal status confirmation message is transmitted to the gatekeeper 340 and the SIP server 360 or predetermined terminals connected through the multicast address and the port 300 as follows, and the port number and the terminal. Define the status display table.

For example, the multicast address for transmitting the terminal status confirmation message to the gatekeeper 340 and the SIP server 360 includes an alias name, an IP address, and a port number as follows.

<"h.323-sip.mcast.net", 224.0.1.90,6060>

In addition, the terminal status confirmation message is shown in Table 1.                     

Herein, the detailed message regarding the 4. terminal state is shown in Table 2 below.

As shown in Table 2, the terminal status confirmation message according to the present invention includes both the state data suitable for the H.323 protocol and the data suitable for the SIP protocol, the gatekeeper 340 and SIP server 360 Is to check the terminal state based on other protocols through the state data.

Looking at the call connection process using the system of the present invention, when the H.323 user terminal transmits a call connection request message to receive the ACD service, the H.323 ACD terminal 330 is first confirmed in real time ) And the SIP ACD terminal 350 to detect the state of the SIP ACD terminal 350 and connect the SIP ACD terminal 350 capable of call connection according to a preset call connection order.

4 is a block diagram illustrating a terminal state checking method in a heterogeneous protocol according to an embodiment of the present invention.

As shown in FIG. 4, any H.323 user terminal 330 (or SIP user terminal) wishing to receive ACD service transmits a call connection request message for receiving ACD service (S400).

In this case, the gatekeeper 340 and the SIP server 360 possessed by the ACD service provider include a multicast address and a port 300 from a plurality of H.323 ACD terminals 330 and a plurality of SIP ACD terminals 350. Receive the first terminal status confirmation message in real time through the (S410).

In addition, since the ACD service provider has a predetermined call connection order, the ACD service provider checks the ACD terminal capable of call connection with the H.323 user terminal 310 in a predetermined order (S420).

In the checking step (s420), when the ACD terminal capable of call connection with the H.323 user terminal 310 is a terminal that supports the H.323 protocol, the H.323 user terminal through the gatekeeper 340 ( 310 and the H.323 ACD terminal 330 is connected.

On the other hand, in the checking step (s420), when the terminal capable of call connection with the H.323 user terminal 310 is a SIP ACD terminal 350 based on the SIP protocol, the H.323 user terminal 310 ) Is connected to the SIP server 360 through the H.323 / SIP gateway 360 to be connected to the SIP ACD terminal 350, the SIP server 360 is connected to the SIP ACD terminal 350. (S440).

Then, the SIP ACD terminal 350 transmits an indication that the call is being connected to the gatekeeper 340 and the SIP server 360 through the multicast port 300 through the second terminal status confirmation message (s450). .

Although the present invention has been described with reference to one embodiment shown in the drawings, this is merely exemplary, and those skilled in the art will understand that various modifications and equivalent other embodiments are possible therefrom. . Therefore, the true technical protection scope of the present invention will be defined by the technical spirit of the appended claims.

As described above, according to the terminal state transmission method between heterogeneous protocols according to the present invention, since a server based on a specific protocol can check the state of the terminal based on the heterogeneous protocol in real time, a more efficient ACD service can be provided. Can be.

Claims (2)

As a terminal state checking method between heterogeneous protocols Transmitting, by a user terminal based on any first protocol, a call connection request message to receive an automatic call distribution (ACD) service; The first protocol server to which the user terminal is subscribed receives the call connection request message, and the server of the first protocol provides the ACD service and the second protocol of the first protocol through the multicast address and port. Receiving a first terminal status confirmation message of the ACD terminal of the terminal; Identifying, by the server of the first protocol, an ACD terminal capable of call connection among the ACD terminal of the first protocol and the ACD terminal of the second protocol; Performing a call connection between the callable ACD terminal and the user terminal through the server of the first protocol or the server of the second protocol; And providing a second terminal status confirmation message indicating a state that the ACD terminal is connected to the call to the server of the first protocol and the second protocol server through the multicast address and port. Method of checking terminal status between heterogeneous protocols. The method of claim 1, And the first and second terminal state confirmation messages each include data of a first protocol and data of a second protocol.

Images