KR100758971B1 - System for internetwork communication using stun binding message of extended stun binding protocol, gateway device, server and method thereof - Google Patents

Abstract

A communication system for interworking between different IP(Internet Protocol) domains using a STUN(Simple Traversal of UDP(User Datagram Protocol) NATs(Network Address Translations)) binding message of an extended STUN binding protocol, an application layer gateway device, a STUN server and a communication method are provided to make interworking between IPv4 and IPv6 networks possible without a dual-stack function of simultaneously supporting the IPv4 and the IPv6, thereby significantly reducing transient costs necessary for evolution of the IPv6 network. An application layer gateway device(200) selects a binding mode by using header information of a received call connection request packet, obtains information where origination address demonstrated in a payload of the call connection request packet is bound with address information of a receiving IP domain by using a first binding message corresponding to the selected binding mode, applies the obtained information to the call connection request packet and transmits the information to the receiving IP domain. An STUN(400) provides the information to the application layer gateway device, wherein the information is made by binding origination information, demonstrated in a payload of the call connection request packet, with address information of the receiving IP by using a second binding message corresponding to a binding mode selected by using the first binding message received from the application layer gateway device.

Description

System for internetwork communication using STUN binding message of extended STUN binding protocol, gateway device for interworking between different IP domains using stun binding message that extends stun binding protocol , server and method according}

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

FIG. 2 is a detailed configuration diagram of the application layer gateway device of FIG. 1.

3 is a detailed configuration diagram of the stern server of FIG. 1.

4 is a diagram illustrating a configuration example of a stun binding message format according to an embodiment of the present invention.

5 to 8 illustrate a stun binding message according to an embodiment of the present invention.

9 illustrates a schematic communication method according to an embodiment of the present invention.

10 is a diagram illustrating a detailed communication method according to an embodiment of the present invention.

The present invention relates to a communication system, an application layer gateway device, a stun server, and a communication method for interworking between different IP domains using a stun binding message that extends the stun binding protocol.

IMS (IP Multimedia Subsystem), called the third generation network platform, is a technology that provides all services based on IP, unlike a circuit-oriented network system. IMS, the third-generation switching system, followed by circuit switches and softswitches, integrates voice and data services into a single structure and delivers them to fixed or mobile devices on an IP network.

It also has the meaning of turning the network open using the Internet protocol. Technology that accelerates network convergence by increasing the service flexibility of wired and wireless networks is a concern of the telecom industry in that it not only reduces application development and management costs, but also increases the diversity of new services.

Such an IP network assigns a common IP address, ie, a global IP address (hereinafter, referred to as a public IP address) to each terminal, to identify a sender address when communicating between terminals. At present, the Internet network is widely distributed around IPv4.

However, as IP network applications expand, the increase in utilization leads to the lack of public IP addresses.

Therefore, as one solution to this problem, an IPv6 protocol having an extended address space has been proposed.

However, the transition from the current IPv4-based Internet to the next-generation Internet based on IPv6 will not be accomplished in the short term and will gradually evolve. Thus, there is a need for mutual communication between IPv4 / IPv6 hosts that occur while the network evolves. To solve this problem, NAT-PT technology has been proposed.

Network Address Translation-Protocol Translation (NAT-PT) exists in the border router between IPv4 and IPv6 networks to convert packet headers between IPv4 and IPv6 protocols.

However, when a session information is included in a message such as SIP (Session Initiation Protocol, hereinafter referred to as SIP) which is the most actively discussed as a technology for supporting multimedia services in an IP network, the problem of NAT-Traversal is caused by this. Occurs.

On the other hand, as a conventional technique for solving the problem of NAT-Traversal, there is a Simple Traversal under UDP through NAT (hereinafter referred to as STUN).

The STUN method is a technology based on a server-client, and individual terminals driving the STUN-client can obtain NAT-translated IP address information from the STUN server located outside the NAT-PT.

However, the STUN-Client must be driven for each individual terminal, so it is difficult to apply it directly to the network and acts as a kind of burden on the terminal.

In addition, the calling terminal may not know whether the called terminal exists on the same IP version network before the call connection. In this case, even though the called terminal exists in its own network that does not need NAT-PT traversal, an unnecessary process of accessing the STUN server through NAT-PT is performed. This causes irrationality in call processing and waste of radio channels.

Accordingly, the technical problem to be achieved by the present invention is a communication system, an application layer gateway device, a stun server, and a communication method for interworking between different IP domains using a stun binding protocol in which a stun binding message extended according to a destination IP domain is defined. To provide.

According to a feature of the present invention in order to achieve the above problems,

Communication system,
In a communication system of a network environment interworking between different IP domains using NAT-PT (Network Address Translation-Protocol Translation), a binding mode is selected by using header information of an incoming call connection request packet, Obtain the information of binding the source address specified in the payload of the call connection request packet to the address information of the destination IP domain using the corresponding first binding message, and apply the obtained information to the call connection request packet. An application layer gateway device for delivering to an IP domain; And the source address of the destination IP domain using the source address specified in the payload of the call connection request packet using a second binding message corresponding to the binding mode selected using the first binding message received from the application layer gateway device. A STUN (Simple Traversal of UDP through NATs) server that provides information bound to the application layer gateway device, wherein the binding mode is the same as the IP version of the originating IP domain and the destination IP domain of the call connection request packet. It includes one or more modes depending on whether or not.

delete

According to another feature of the invention,

Gateway device,
In a gateway device of a network environment interworking between different IP domains using NAT-PT (Network Address Translation-Protocol Translation), an originating IP configured by configuring a node of a specific network and extracting header information of an incoming call connection request packet And a binding mode selection unit for selecting a binding mode based on the called IP, wherein the binding mode includes one or more modes according to whether the domain of the originating IP and the domain of the destination IP are the same as the IP version. The binding mode selection unit transmits the source IP of the IP header of the first binding message according to the binding mode selected by the binding mode selection to the source address specified in the payload of the call connection request packet, so that the source IP of the first binding message is the NAT. A binding operation driver for receiving a second binding message including information bound through the PT and bound to the domain of the called IP; And an address translator configured to apply the information bound to the destination IP domain included in the second binding message to the call connection request packet and transmit the information to the destination.

delete

According to another feature of the invention,

Stern server,
Simple Traversal of UDP through NATs (STUN) server located outside of Network Address Translation-Protocol Translation (NAT-PT) and providing binding information in a network environment interworking between different IP domains. A database storing a binding mode including one or more modes according to whether the IP version of the IP domain and the destination IP domain are the same, and format information of the binding message according to the binding mode; A first binding message for querying information in which the NAT-PT binds the source address of the call connection request packet from an application layer gateway device located in a specific network that receives the call connection request packet from the calling terminal and delivers it to the called terminal; A receiving unit for receiving a source IP of an IP header of a first binding message, wherein the source IP is replaced with a source address of the call connection request packet; An extraction unit for extracting a source IP converted by the NAT-PT from the IP header of the first binding message; A binding operation driver configured to apply a message format obtained by obtaining a binding message format corresponding to the binding mode selected by using the first binding message from the database, and to configure a second binding message including a source IP extracted by the extractor; And a transmitter for transmitting the second binding message to the application layer gateway device by using the binding response address specified in the first binding message.

delete

According to another feature of the invention,
The communication method is
A communication method of a network environment interworking between different IP domains using NAT-PT (Network Address Translation-Protocol Translation), comprising: (a) header information of a call connection request packet received by an application layer gateway device located in a specific network; Selecting a binding mode, wherein the binding mode includes one or more modes depending on whether the IP version of the call IP request domain and the destination IP domain of the call connection request packet are the same; (b) a first binding message to which the message format corresponding to the selected binding mode is applied, wherein the first binding message is information for binding the source address specified in the payload of the received call connection request packet to the address of the destination IP domain; Constructing a message to query a query; (c) a second message containing the information binding the first binding message to a STUN (Simple Traversal of UDP through NATs) server connected to the outside of the NAT-PT and binding to the address of the called IP domain queried; Receiving a binding message; And (d) applying the information bound to the address of the destination IP domain included in the second binding message to the received call connection request packet and transmitting the information to the destination.

delete

delete

According to another feature of the invention,

The communication method is
A communication method of a network environment interworking between different IP domains using NAT-PT (Network Address Translation-Protocol Translation), comprising: (a) an application in which a stun server located outside of the NAT-PT is located in a specific network; Receiving a first binding message for querying information bound by the NAT-PT from a layer gateway device; (b) the binding mode included in the first binding message, wherein the binding mode includes one or more modes according to whether the source IP domain and the destination IP domain have the same IP version of the call connection request packet received by the application layer gateway device. Confirming and selecting a corresponding message format; And (c) the binding information queried by the first binding message by applying the selected message format, wherein the binding information is information of binding the source address specified in the payload of the call connection request packet to the address of the destination IP domain. Constructing a second binding message that provides-and sending the second binding message to the application layer gateway device.

delete

Now, a communication system, an application layer gateway device, a stun server, and a communication method for interworking between different IP domains using a stun binding message that extends the stun binding protocol according to an embodiment of the present invention will be described.

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

According to FIG. 1, the communication system includes an originating terminal 100, an application layer gateway device 200, a NAT-PT 300, a stun server 400, and a called terminal 500.

Here, the first network 1 and the second network 2 using different IP domains may be networks using IPv4 or IPv6. It may also be a private network using a private IP or a public network using a public IP.

The communication system uses a protocol in which a signaling process for call setup and a media session process for data transmission and reception are separated, and negotiation information of the media session process is included in a packet payload. The protocol includes host information in a payload of an application itself, and thus media session negotiation is performed between an end host, that is, the originating terminal 100 and the called terminal 500. In this case, the host information is more specifically, media reception information for actually exchanging multimedia such as voice and video between end hosts. That is, it means the address information of the caller terminal (100, 500) for the media reception.

As such a protocol, a Session Initiation Protocol (SIP) protocol can be used.

In addition, the first network 1 receives the binding information by the NAT-PT 300 from the stun server 400 connected to the outside of the NAT-PT 300 to communicate with the second network 2. This is called STUN (Simple Traversal of UDP through NATs) binding operation, and uses a stun binding protocol that provides a stun binding message extended according to an IP domain.

The originating terminal 100 and the terminating terminal 500 are terminating hosts on communication lines of the corresponding networks 1 and 2, respectively.

The application layer gateway device 200 performs a binding operation according to the selected binding mode based on the header information of the call connection request packet transmitted from the originating terminal 100. That is, the information obtained by binding the address information of the originating terminal 100 specified in the payload of the call connection request packet to the destination IP domain of the packet is obtained using the binding message according to the binding mode. The obtained bound information is applied to the call connection request packet and transmitted to the called terminal 500.

The application layer gateway device 200 may be located on a node of the first network 1 to convert address information of an application layer (ALG) that the NAT-PT 300 cannot convert, and It acts as a stun binding client. In this case, a more detailed configuration may be implemented as shown in FIG. 2.

According to FIG. 2, the application layer gateway device 200 includes a binding mode selector 210, a binding operation driver 220, and an address translator 230.

The binding mode selection unit 210 checks the source IP and the destination IP of the received packet header and selects the corresponding binding mode. Here, the binding mode is specifically, a first mode in which the source IP is IPv4, private IP, and the destination IP is IPv4, the public IP, the source IP is IPv6, the second mode where the destination IP is IPv4, and the source IP is IPv4 and the destination IP. May include at least one of the third modes of IPv6.

The binding operation driver 220 is a means for driving a binding operation according to the binding mode selected by the binding mode selection unit 210, and may be configured as a plurality of binding operation drivers for each binding mode. The binding operation driver 220 includes a DB 222 storing binding message format information negotiated between the application layer gateway device 200 and the stun server 400.

The binding operation driver 220 extracts the corresponding binding message format information from the message format DB 222 and applies it to the binding message. The originating IP is replaced with the address information of the originating terminal extracted from the packet payload in the IP header of the first binding message for the binding request. The first binding message is transmitted to the stun server 400, and a second binding message is received in response thereto.

The address translator 230 obtains an originating IP bound by the NAT-PT 300, that is, an originating IP bound to the destination IP domain, from the second binding message. In this case, since the source IP is replaced with the address information of the originating terminal extracted from the packet payload, eventually, binding information about the address information of the originating terminal is obtained. The address conversion unit 230 may include an address mapping module 232 and a packet conversion module 234 as detailed functional modules.

That is, the address mapping module 232 maps the address information of the originating terminal 100 specified as the originating IP to the obtained binding information in the payload of the call connection request packet transmitted by the originating terminal 100, and stores and manages it in the address table. do.

The packet conversion module 234 changes the recognition information of the originating terminal 100 specified in the payload of the call connection request packet to the obtained binding information and transmits it to the called terminal 500.

NAT-PT (300) serves to convert the IP address information to each other to enable communication between networks using different IP domains. That is, the source IP address of the IP header of the calling terminal 100 is converted into the IP address of the called terminal 500. And it is registered and managed in the mapping table.

The stern server 400 is connected to the outside of the NAT-PT 300 to provide the address, that is, the binding information translated by the NAT-PT 300. That is, it corresponds to the stun binding client of the application layer gateway device 200. At this time, the binding operation according to the binding mode determined through the stun binding message received from the application layer gateway device 200 is performed.

At this time, the stern server 400 may be implemented in more detail as shown in FIG.

That is, according to FIG. 3, the stun server 400 includes a database 410, a receiver 420, an extractor 430, a binding operation driver 440, and a transmitter 450.

The database 410 stores setting information of the binding mode and the binding message format. That is, the binding mode is information for performing each binding operation according to different IP domains. The binding message format information is message information applying each IP domain according to the binding mode.

The receiver 420 receives a first binding message for requesting binding information from the application layer gateway device 200. That is, a query for bound information is requested while passing through the NAT-PT 300.

The extractor 430 extracts the source IP converted by the NAT-PT 300 from the IP header of the received first binding message.

The binding operation driver 440 determines the binding mode specified in the first binding message with reference to the database 410. The second binding message including the source IP extracted by the extracting unit 430 is configured by applying the binding message format according to the determined binding mode.

The transmitter 450 transmits the second binding message configured by the binding operation driver 440 to the application layer gateway device 200 using the binding response address specified in the first binding message.

4 is a diagram illustrating a configuration example of a binding message format according to an embodiment of the present invention, and FIGS. 5 to 7 are diagrams illustrating a binding message according to an embodiment of the present invention. In this case, an example of applying to the stun binding protocol according to the RFC 3489 standard is shown.

That is, according to FIG. 4, the binding message format P100 defines a 'Family' parameter P107 and a 'Address' parameter P109 in the binding message.

Here, the 'Family' parameter P107 is determined as '0x01' according to the existing stun protocol. However, the 'Family' parameter P107 according to the embodiment of the present invention is extended to '0x02' and '0x03' for each binding mode. At this time, the 'Case' parameter (P101) distinguishes the binding mode.

In addition, the 'Address' parameter (P109) is defined for the 'Address' (P111, P113) of each of the 'Binding Request' and 'Binding Response'.

The 'Address' parameter (P111) of the 'Binding Request' is defined as the same IP domain as the originating IP.

The 'Address' parameter (P113) of 'Binding Respone' is defined as the same IP domain as the destination IP.

At this time, the IP domain defined in the 'Address' parameters P111 and P113 is applied to the 'attribute' including the address information in the stun binding message. Such 'attribute' includes 'MAPPED-ADDRESS', 'RESPONSE-ADDRESS', 'CHANGED-ADDRESS', 'SOURCE-ADDRESS', and 'REFLECTED-FROM'.

A stun binding message to which the binding message format (P100) is applied, in particular, is shown in an example of being applied to "MAPPED-ADDRESS" "attribute" of the stun binding message.

First, the basic message format of "MAPPED-ADDRESS" "attribute" (P200) is shown in FIG.

The first 8 bits P201 of the mapping address are ignored. Next is the IP address and port being mapped. That is, it consists of an 8-bit address family P203, a 16-bit port P205, followed by a fixed length value P207 representing an IP address. Here, the 8-bit address family P203 represents the same value as the “Family” parameter P107 of FIG. 4. The fixed length value representing the IP address represents a value defined in the 'Address' parameter (P109).

An example of applying such a message format to each binding mode is as follows.

That is, FIG. 6 is a diagram illustrating a 'Binding Request' and a 'Binding Response' when the 'Case' parameter P101 corresponds to (1).

According to FIG. 6, 'Binding Request' and 'Binding Response' are the same. 'Address Family' (P301) stands for '0x01', 'a fixed length value representing IP address' (P303) stands for 'IPv4'.

Next, FIG. 7A illustrates a 'Binding Request' when the 'Case' parameter P101 corresponds to (2), and FIG. 7B illustrates a 'Binding Request' when the 'Case' parameter P101 corresponds to (2). Binding Response '.

According to FIG. 7A, 'Address Family' (P401) represents '0x02'. 'Fixed length value representing IP address' (P403) represents 'IPv6'.

According to FIG. 7B, 'Address Family' (P405) represents '0x02'. 'Fixed length value representing IP address' (P407) represents 'IPv4'.

FIG. 8A illustrates a 'Binding Request' when the 'Case' parameter P101 corresponds to (3), and FIG. 8B illustrates a 'Binding Response' when the 'Case' parameter P101 corresponds to (3). 'Is shown.

According to FIG. 8A, 'Address Family' (P501) represents '0x03'. The fixed length value P503 representing the IP address represents 'IPv4'.

According to FIG. 8B, 'Address Family' (P505) represents '0x03'. 'Fixed length value representing IP address' (P507) represents 'IPv6'.

Now, a communication method using NAT-PT in a network environment where different IP domains interwork based on the configuration of the above-described communication system will be described.

9 is a view showing a schematic communication method according to an embodiment of the present invention, Figure 10 is a view showing a detailed communication method according to an embodiment of the present invention.

That is, according to Figure 9, the originating terminal 100 transmits a call connection request packet to the application layer gateway device 200 using the same IP domain (S101).

Then, the application layer gateway device 200 performs a binding operation (S103).

That is, the binding mode is selected based on the header information of the call connection request packet (S105). In this case, the binding mode may be set based on any one of the information for distinguishing whether the network to which the IP domain and the address are allocated is a private network or a public network.

The first binding message is configured by applying a message format according to the selected binding mode (S107). According to this message format, the first field of the first binding message indicates the binding mode and the second field indicates address information according to the IP domain of the calling terminal. In this case, the header of the first binding message is replaced with address information of the originating terminal 100 specified in the packet payload.

Then, the first binding message configured in the step (S107) is transmitted to the stern server 400 through the NAT-PT (300) (S109).

Then, the stun server 400 receives the second binding message in which the header of the first binding message includes information bound to the destination IP domain by the NAT-PT 300 (S111). In this case, the second binding message is a message format of the binding mode selected in step S105 is applied. In this case, the first field of the second binding message indicates the binding mode and the second field indicates address information according to the called IP domain.

Then, the application layer gateway device 200 performs an ALG operation (S113). That is, binding information is extracted from the received second binding message (S115). And it applies to the call connection request packet (S117).

Then, the call connection request packet changed in the step (S113, S115, S117) is transmitted to the destination terminal (500) (S119).

Now, if the communication method is more specifically implemented using the SIP message and the stun binding message, it is as shown in FIG. 10.

That is, according to FIG. 10, the originating terminal 100 transmits INVITE to the application layer gateway device 200 (S201).

Then, the application layer gateway device 200 checks the source IP and the destination IP in the IP header of the INVITE message (S203).

The corresponding binding mode is selected based on the result confirmed in the step S203 (S205).

The format of the stun binding message negotiated between the application layer gateway device 200 and the stun server 400 according to the binding mode selected in step S205 is extracted (S207).

In operation S209, a binding operation for setting the STUN Binding Request and the STUN Binding Request to which the message format is applied is driven.

Then, session negotiation information specified in the Session Description Protocol (SDP) of the INVITE is extracted according to the driving of the binding operation set in the step S211 (S211).

Subsequently, the extracted session negotiation information is replaced with a header of the STUN Binding Request, and the response address is set to the IP of the application layer gateway device 200 (S213).

The STUN Binding Request configured in step S213 is transmitted to the stun server 400 (S215).

Then, the stun server 400 checks the binding mode in the STUN Binding Request (S217). At this time, the binding mode uses the information set in step S237. In step S237, a binding mode for performing each binding operation according to different IP domains and a message format according to the binding mode are set.

A format of the STUN binding message corresponding to the binding mode checked in step S217 is selected (S219).

In operation S221, a binding operation of applying a format of the selected STUN binding message is applied.

Then, the source IP converted by the NAT-PT 300 is extracted from the IP header of the STUN Binding Request (S223).

Then, a STUN Binding Response is set in which the source IP extracted in the step S223 is set to the Mapped Address attribute (S225).

Then, the STUN Binding Response configured in step S225 is transmitted to the application layer gateway device 200 (S227).

Then, the application layer gateway device 200 obtains the source IP set in the Mapped Address attribute of the STUN Binding Response (S229). At this time, the obtained source IP is a binding value of the session negotiation information specified in the SDP substituted in the step S211.

Then, the IP information for session negotiation included in the SDP of INVITE transmitted in step S201 is converted into the source IP obtained in step S229 (S231).

The converted INVITE is transmitted to the called terminal 500 (S233).

The controller stores the mapping information on the IP information for session negotiation included in the SDP of the INVITE in the address table (S235).

Thereafter, using the IP information of the SDP to which the binding value obtained in step S229 is applied, the calling terminal 100 and the called terminal 500 establish a multimedia session negotiation and implement a multimedia service.

In this case, since the INVITE message includes Proxy route information, the SIP message is exchanged between the calling terminal 100 and the called terminal 500 using the proxy route information. Session negotiation by the SIP protocol is established through a plurality of SIP message exchange processes, but a specific SIP message exchange process is referred to SIP standard: IETF RFC 3261.

The embodiments of the present invention described above are not implemented only through the apparatus and the method, but may be implemented through a program for realizing a function corresponding to the configuration of the embodiment of the present invention or a recording medium on which the program is recorded. Implementation may be easily implemented by those skilled in the art from the description of the above-described embodiments.

The scope of the present invention is not limited to the above-described embodiments, but various modifications and improvements of those skilled in the art using the basic concept of the present invention as defined in the following claims are also within the scope of the present invention.

By the above-described configuration, when interworking between IPv4 and IPv6 networks, in principle, all network nodes can interwork between IPv4 and IPv6 networks without the need for a dual-stack function that simultaneously supports IPv4 / IPv6. This greatly reduces the transitional costs of IPv6 network evolution.

In addition, STUNv6 or STUNv6 based on IPv4 can be simultaneously provided by one node by setting STUNv6 or STUN in advance. This provides the effect of being fully compatible with the existing STUN protocol.

Claims (18)

In a communication system of a network environment interworking between different IP domains using NAT-PT (Network Address Translation-Protocol Translation), Select the binding mode using the header information of the received call connection request packet and use the first binding message corresponding to the selected binding mode to obtain the source address specified in the payload of the call connection request packet, and the address information of the destination IP domain. An application layer gateway device for acquiring the bound information and applying the obtained information to the call connection request packet and delivering the information to the destination IP domain; And By using the second binding message corresponding to the binding mode selected by using the first binding message received from the application layer gateway device, the source address specified in the payload of the call connection request packet is used as the address information of the destination IP domain. A STUN (Simple Traversal of UDP through NATs) server for providing the bound information to the application layer gateway device, The binding mode includes at least one mode according to whether the IP version of the call IP request and the destination IP domain of the call connection request packet is the same. The method of claim 1, The application layer gateway device, A binding mode selection unit that selects the binding mode based on an originating IP and a destination IP identified in header information of the call connection request packet; A binding operation for receiving the second binding message by transmitting the first binding message to which the message format corresponding to the selected binding mode is applied, wherein the format is a format previously negotiated between the application layer gateway device and the stun server. A drive unit; And An address conversion unit for converting an originating address specified in a payload of the call connection request packet into information bound to address information of the destination IP domain included in the second binding message Communication system comprising a. The method of claim 2, The first binding message and the second binding message, A first field indicating the binding mode; And a second field representing address information, A second field of the first binding message indicates address information according to the originating IP domain version, And a second field of the second binding message indicates address information according to the called IP domain. The method according to claim 2 or 3, The binding operation driver, The source IP of the IP header of the first binding message is replaced with the source address specified in the payload of the call connection request packet and transmitted to the stun server, and the source IP of the IP header of the first binding message is the NAT-PT. And receive the second binding message that includes information bound to the destination IP domain through. The method of claim 4, wherein The binding mode is, It is set based on the information that distinguishes the IP domain of the source IP and the destination IP and whether the private IP or public IP, A first mode in which the source IP of the call connection request packet is an IP version 4 and a private IP and the destination IP of the call connection request packet is an IP version 4 and a public IP; A second mode in which the source IP of the call connection request packet is IP version 6 and the destination IP of the call connection request packet is IP version 4, and And a third mode in which the source IP of the call connection request packet is IP version 4 and the destination IP of the call connection request packet is IP version 6. The method of claim 5, The address conversion unit, An address mapping module for mapping the source address specified in the payload of the call connection request packet with the information binding the source address to the destination IP domain, and storing and managing the same in an address table; And A packet conversion module for converting a source address specified in a payload of the call connection request packet into information bound to address information of the destination IP domain Communication system comprising a. The method of claim 6, The originating terminal and the called terminal for transmitting / receiving the call connection request packet, A communication system using a protocol to which a media session is connected using host awareness information contained in a payload of a packet, wherein the protocol includes a Session Initiation Protocol (SIP). In a gateway device of a network environment that interworks between different IP domains using NAT-PT (Network Address Translation-Protocol Translation), Configure nodes on a particular network, Binding mode based on the source IP and the destination IP extracted from the header information of the incoming call connection request packet, wherein the binding mode includes one or more modes depending on whether the domain of the source IP and the domain of the destination IP are the same. A binding mode selection unit for selecting a; The binding mode selection unit transmits the source IP of the IP header of the first binding message according to the binding mode selected by the binding mode selection to the source address specified in the payload of the call connection request packet, so that the source IP of the first binding message is the NAT. A binding operation driver for receiving a second binding message including information bound through the PT and bound to the domain of the called IP; And An address translator configured to apply the information bound to the destination IP domain included in the second binding message to the call connection request packet and transmit the information to the destination; Gateway device comprising a. In the STUN (Simple Traversal of UDP through NATs) server, which is located outside the Network Address Translation-Protocol Translation (NAT-PT) and provides binding information in a network environment interworking between different IP domains,  A database for storing a binding mode including one or more modes according to whether an IP version of a call connection request packet and an IP version of a destination IP domain are the same, and format information of a binding message according to the binding mode; A first binding message for querying information in which the NAT-PT binds the source address of the call connection request packet from an application layer gateway device located in a specific network that receives the call connection request packet from the calling terminal and delivers it to the called terminal; A receiving unit for receiving a source IP of an IP header of a first binding message, wherein the source IP is replaced with a source address of the call connection request packet; An extraction unit for extracting a source IP converted by the NAT-PT from the IP header of the first binding message; A binding operation driver configured to apply a message format obtained by obtaining a binding message format corresponding to the binding mode selected by using the first binding message from the database, and to configure a second binding message including a source IP extracted by the extractor; And Transmitter for transmitting the second binding message to the application layer gateway device using the binding response address specified in the first binding message. Stern server including. In a communication method of a network environment interworking between different IP domains using NAT-PT (Network Address Translation-Protocol Translation), (a) The binding mode using the header information of the call connection request packet received by an application layer gateway device located in a specific network, wherein the binding mode is determined whether the IP version of the call connection request packet and the destination IP domain are the same. Selecting one or more modes in accordance with the method; (b) a first binding message to which the message format corresponding to the selected binding mode is applied, wherein the first binding message is information for binding the source address specified in the payload of the received call connection request packet to the address of the destination IP domain; Constructing a message to query a query; (c) a second message containing the information binding the first binding message to a STUN (Simple Traversal of UDP through NATs) server connected to the outside of the NAT-PT and binding to the address of the called IP domain queried; Receiving a binding message; And (d) applying the information bound to the address of the destination IP domain included in the second binding message to the received call connection request packet and transmitting the received information to the destination; Communication method comprising a. The method of claim 10, In step (a), Selecting a corresponding binding mode based on the source IP and the destination IP identified in the header information of the call connection request packet; Extracting a message format corresponding to the selected binding mode, wherein the message format is a message format negotiated between the application layer gateway device and the stun server; And Setting up transmission of the first binding message and reception of the second binding message to which the extracted message format is applied; Communication method comprising a. The method of claim 11, The first binding message and the second binding message, A first field indicating the binding mode; And a second field representing address information, A second field of the first binding message indicates address information according to the originating IP domain version, And a second field of the second binding message indicates address information according to the called IP domain. The method according to any one of claims 10 to 12, The binding mode is, It is set based on the information that distinguishes the IP domain of the source IP and the destination IP and whether the private IP or public IP, A first mode in which the source IP of the call connection request packet is an IP version 4 and a private IP and the destination IP of the call connection request packet is an IP version 4 and a public IP; A second mode in which the source IP of the call connection request packet is IP version 6 and the destination IP of the call connection request packet is IP version 4, and A third mode in which the source IP of the call connection request packet is IP version 4 and the destination IP of the call connection request packet is IP version 6 Communication method comprising a. The method of claim 13, In step (b), Replacing the source IP of the IP header of the first binding message with the source address specified in the payload of the call connection request packet received in step (a); And Setting a reception address of the second binding message to the IP address assigned to the application layer gateway device in the first binding message; Communication method comprising a. The method of claim 14, Step (c) is, Receiving the second binding message including information that the source IP of the first binding message passes through the NAT-PT to bind to the destination IP domain; And Address table, wherein the information bound to the destination IP domain included in the second binding message is an address table, wherein the address table includes information about the source address specified in the payload of the call connection request packet and the information bound to the destination IP domain. Steps to Archive and Manage-Save Mapping Information Communication method comprising a. In a communication method of a network environment interworking between different IP domains using NAT-PT (Network Address Translation-Protocol Translation), (a) receiving a first binding message for querying information bound by the NAT-PT from an application layer gateway device located in a specific network by a stun server located outside the NAT-PT; (b) the binding mode included in the first binding message, wherein the binding mode includes one or more modes according to whether the source IP domain and the destination IP domain have the same IP version of the call connection request packet received by the application layer gateway device. Confirming and selecting a corresponding message format; And (c) binding information queried by the first binding message by applying the selected message format, wherein the binding information is information of binding the source address specified in the payload of the call connection request packet to the address of the destination IP domain; Constructing a second binding message providing a second binding message and transmitting the second binding message to the application layer gateway device; Communication method comprising a. The method of claim 16, Before step (a) above, Setting a binding mode for performing each binding operation according to different IP domains and a message format according to the binding mode; The binding mode set on the basis of information distinguishing the IP domains of the source IP and the destination IP and whether the private IP or the public IP is the originating IP of the call connection request packet is IP version 4 and the private IP, and the call A first mode in which the destination IP of the connection request packet is IP version 4 and public IP, a second mode in which the source IP of the call connection request packet is IP version 6 and the destination IP of the call connection request packet is IP version 4, and the A third mode in which the source IP of the call connection request packet is IP version 4 and the destination IP of the call connection request packet is IP version 6, The message format according to the binding mode may include: a first field indicating the binding mode; And a second field in the first binding message indicating address information according to the originating IP domain version, and in the second binding message indicative of address information according to the called IP domain. The method of claim 16, Step (c) is, Extracting a source IP converted by the NAT-PT from an IP header of the first binding message; And Including the extracted source IP in the second binding message and transmitting the extracted source IP to the application layer gateway device; Communication method comprising a.

Images