JP4961368B2 - Terminal device, NAT traversal method, and program - Google Patents

Description

  The present invention relates to a NAT traversal technique in which a terminal device under a NAT (Network Address Translation) device communicates with another terminal device through the NAT device.

  2. Description of the Related Art NAT devices (such as NAT routers) that allow access to the Internet from a terminal assigned with a private IP address by converting a private IP address and a global IP address to each other have become widespread.

  Now, IP media communication services using VoIP technology are popular, but terminal devices in private networks such as home networks and company networks are generally under the control of NAT devices. Communicates with an external terminal device via a NAT device. In the present specification and claims, NAT is used to include NAPT (Network Address Port Translation).

  Here, SIP (Session Initiation Protocol) is generally used as a signaling protocol in a media communication service using VoIP technology that is currently in widespread use. However, in SIP, the address used for SIP message transmission and reception and the address used for media communication are written inside the SIP message, so even if the IP packet address is converted by the NAT device, the address inside the SIP message is Since it is not converted, it is usually difficult to perform media communication based on SIP between terminal devices via a NAT device. Note that transmission / reception of SIP messages and transmission / reception of media are performed by UDP (User Datagram Protocol).

  STUN-bis (Session Traversal Utilities for NAT, Non-Patent Document 1), TURN (Traversal Using Relays around NAT, Non-Patent Document 2) are the main technologies for enabling communication using SIP via a NAT device. ), HTTP tunneling, etc. In the following, STUN-bis is simply described as STUN.

  STUN is a technology that enables a terminal device to obtain a global IP address and port number outside the NAT device. This allows the terminal device to communicate the global IP address and port number to the communication partner. it can.

  TURN is a technology that places a TURN server for relaying media (UDP data) on the global network side so that terminal devices under the NAT device can communicate with external terminal devices via the TURN server. .

  In HTTP tunneling, an HTTP tunneling server for relaying media (UDP data) is placed on the global network side, and the data (UDP data, etc.) that you want to communicate with is encapsulated with the HTTP header, so that the terminal device under the NAT device And an external terminal device can communicate with each other via an HTTP tunneling server. From the NAT device, communication is performed as if it is normal HTTP communication.

  In addition to the above, for example, each terminal device subordinate to the NAT device transmits a UDP packet from the inside, pierces the NAT device, and the terminal devices subordinate to the NAT device do not pass through a third party. In addition, there is a technology called UDP Hole Punching for performing UDP communication.

  However, STUN and UDP Hole Punching cannot be applied to NAT devices that do not transmit UDP packets and symmetric NAT devices. TURN can be applied to a symmetric NAT device, but cannot be applied to a NAT device that does not transmit UDP packets. HTTP tunneling is generally applicable to any NAT device.

On the other hand, the HTTP tunneling technology requires processing of relaying communication data to the server and encapsulation / decapsulation processing, so STUN-bis and UDP Hole Punching that can perform media communication directly between terminal devices Also increases the delay. TURN also has a larger delay than STUN-bis and UDP Hole Punching because of the process of relaying communication data to the server. In addition, in TURN and HTTP tunneling, a load is applied to the server, and when access is concentrated on the server, the delay is further increased. There is also a technology called UPnP (Universal Plug and Play) as a NAT traversal method, but there are many devices that do not implement the function or have the function stopped by default at the time of shipment. Is not common.
JP 2005-198181 A RFC3489bis February 24, 2008 Search, Internet, <URL: http://tools.ietf.org/html/draft-ietf-behave-turn-06> February 24, 2008 Search, Internet, <URL: http://tools.ietf.org/html/draft-ietf-mmusic-ice-19

  From the above background art, it is necessary to select an appropriate NAT traversal method according to the type of NAT device. As for TURN and STUN among the NAT traversal methods, there is a technology called ICE (Interactive Connectivity Establishment, Non-Patent Document 3) that can select an optimum one of these.

  In ICE, a terminal device equipped with a SIP function acquires address information that can be used by STUN or TURN before starting communication, and includes the obtained address information and its own address information in a SIP message. The counterpart terminal device that supports the ICE that transmitted and received the message checks with which address communication is possible, and performs communication by selecting the most efficient address among communicable addresses based on a predetermined rule. Considering the efficiency of communication, the priority of selection is the highest in its own address (that is, when performing local communication not via a NAT device), then the STUN address, and then the TURN address in general. Is.

  However, the prior art does not consider HTTP tunneling as an option for NAT traversal. Therefore, in the conventional technology, because HTTP tunneling basically enables communication under any NAT device, regardless of the availability of other methods, only the HTTP tunneling method is used. It can happen. However, as described above, the HTTP tunneling method increases the load on the server and the communication delay, so that it can be used for real-time media communication such as an IP phone for other types of communication with a smaller delay. If it is, it is better to avoid it as much as possible.

  The present invention has been made in view of the above points, and when performing media communication such as VoIP based on SIP between terminal devices via a NAT device, HTTP tunneling is selected as necessary as a NAT traversal method. It is an object to provide a technology that makes it possible.

  In order to solve the above problems, the present invention provides a terminal device provided under the control of a NAT device, and transmits a UDP transmission determination message to a predetermined device connected to a communication network outside the NAT device. And a UDP transmission determination unit that determines whether or not to receive a response message from the predetermined device in response to the UDP transmission determination message, and a response message from the predetermined device is not received by the UDP transmission determination unit. An HTTP tunnel setting means for setting an HTTP tunnel with an HTTP tunneling device connected to an external communication network of the NAT device, and another terminal device via the HTTP tunnel. A signaling message communication means for transmitting and receiving signaling messages for media communication between Configured.

The terminal device may include means for terminating the HTTP tunnel when it is detected that the operation of the function using the signaling message is terminated in the terminal device.
Further, the terminal device has an address assignment requesting unit that requests the HTTP tunneling device to assign an address for external communication for communicating with an external device connected to a communication network outside the NAT device, The terminal device may include the external communication address assigned by the HTTP tunneling device in the signaling message as a destination address for communication from the external device to the terminal device.

  The HTTP tunnel setting means has means for setting an HTTP tunnel for media communication with the HTTP tunneling device, and the terminal device receives media communication data from the other terminal device. Transmission means for transmitting at least the address of the terminal device itself and the external communication address assigned for media communication of the terminal device in the HTTP tunneling device to the other terminal device as candidate addresses. In the other terminal device having the ICE function, when the external communication address for media communication is not selected as an address for media transmission to the terminal device, the HTTP tunnel for media communication is terminated. It is good also as having a means.

  Further, the present invention can be configured as a NAT traversal method executed by the terminal device, and can also be configured as a program for causing a computer to realize each means in the terminal device.

  According to the present invention, an HTTP tunnel is set when it is determined that UDP is not transparent by the UDP transmission determining means, and a signaling message for media communication with another terminal device via the HTTP tunnel Therefore, HTTP tunneling can be selected as necessary as a NAT traversal method.

  Embodiments of the present invention will be described below with reference to the drawings. In the following description, unless otherwise specified, an address is an IP address, and a port is a port number.

(System configuration)
FIG. 1 shows the overall configuration of the system in the present embodiment. As shown in FIG. 1, the system of this embodiment includes a NAT device N1, a terminal device T1 under the NAT device N1, a NAT device N2, a terminal device T2 under the NAT device N2, a SIP server S1, and a STUN server ST1. HTTP tunneling server HP1 (also serving as a TURN server) and HTTP tunneling server HP2 (also serving as a TURN server). SIP server S1 and STUN server ST1 may be provided in the same apparatus. Moreover, it is good also as providing the TURN server which does not have the function of an HTTP tunneling server.

  In this system, the NAT device N1 is connected to the Internet 6 which is a global network and to a private network 7. The terminal device T1 is connected to the private network 7. The NAT device N2 is connected to the Internet 6 and to the private network 8. The terminal device T2 is connected to the private network 8.

  The HTTP tunneling server HP1 is assumed to provide a service to the terminal device T1, and the HTTP tunneling server HP2 is assumed to provide a service to the terminal device T2.

  The SIP server S1 in this system is a server that performs SIP relay processing. The STUN server ST1 is a server having a function conforming to the STUN specification, and is a server having a function of returning address information outside the NAT device based on a request from the terminal device. The HTTP tunneling server HP1 assigns address information for data relay based on the request from the terminal device in accordance with the function of forming an HTTP tunnel with the terminal device T1 and the specification of TURN, and assigns it to the terminal device. This is a server having a function of returning to, a function of holding address binding information and relaying data. The HTTP tunneling server HP2 has the same function as the HTTP tunneling server H1. That is, the HTTP tunneling servers HP1 and HP2 each have an HTTP tunneling server function and a TURN server function.

  FIG. 2 shows a functional configuration diagram of the terminal device T1. Since the terminal device T2 has exactly the same configuration as the terminal device T1, only the terminal device T1 will be described. As shown in FIG. 2, the terminal device T1 includes a communication interface unit 11, a control unit 12, an HTTP tunneling function unit 13, a media communication unit 14, a SIP function unit 15, a STUN function unit 16, a TURN function unit 17, and an ICE function unit. 18 The communication interface unit 11 is a functional unit for performing data communication with an external device via a communication network. The control unit 12 includes a UDP transmission determination function, a SIP communication end determination function, an HTTP tunnel end determination function, and the like, and is a function unit for controlling the operation of each function unit and for coordinating between the function units. The HTTP tunneling function unit 13 is a function unit for constructing an HTTP tunnel with the HTTP tunneling server HP1 and performing data communication using the HTTP tunnel. The media communication unit 14 is a functional unit for performing media communication such as voice communication with another terminal device. The SIP function unit 15 is a function unit having functions on the terminal side in the SIP specification. The STUN function unit 16 is a function unit having functions on the terminal side in the STUN specification. The TURN function unit 17 is a function unit having a function on the terminal side in the TURN specification. The ICE function unit 18 is a function unit that operates according to the specifications of the ICE. Although not shown, it is assumed that an application using SIP is installed in the terminal device T1.

  The terminal device T1 can be realized by causing a computer having a CPU, a storage device, and the like to execute programs for realizing the above functions. The program may be installed in a computer from a recording medium such as a portable memory, or may be downloaded from a server on the network.

(Overview of operation)
Next, an outline of the operation of the terminal device T1 in the present embodiment will be described with reference to FIG. Since the same operation is performed for the terminal device T2, only the terminal device T1 will be described. As a premise, it is assumed that the user of the terminal device T1 uses the terminal device T1 to perform media communication such as voice communication with other terminal devices.

  Based on an operation from the user, first, the terminal device T1 tests whether or not UDP data can be transmitted / received to / from an external device via the NAT device N1. That is, the terminal device T1 determines whether or not the NAT device N1 transmits UDP data (step 1).

  If the NAT device N1 is UDP transparent (Yes in step 2), the terminal device T1 performs call connection processing using a SIP message (signaling message) in the same manner as before, and performs media communication with other devices. (Step 3). In step 3, processing based on the ICE function is performed as appropriate, and the terminal apparatus T1 performs media communication with the other apparatus using an address and port based on the determined NAT traversal method.

  When the determination result in step 2 is UDP non-transparent (No in step 2), the terminal device T1 establishes an HTTP tunnel for performing UDP communication such as transmission / reception of a SIP message with the HTTP tunneling server HP1 ( Step 4). HTTP tunneling communication is performed by adding an HTTP header to data to be actually communicated, and constructing (setting) an HTTP tunnel is preparation for performing such HTTP tunneling communication. For example, it includes starting a program module for HTTP tunneling communication (corresponding to the HTTP tunneling function unit 13), accessing the HTTP tunneling server HP1, and requesting HTTP tunnel construction. The HTTP tunneling technology itself is an existing technology.

  Then, the terminal device T1 performs media communication by exchanging SIP messages with other devices using the HTTP tunnel constructed in Step 4 (Step 5). In step 5, processing based on the ICE function is executed. In step 5, an HTTP tunnel for media communication is established with the HTTP tunneling server HP1, but a route that does not use the HTTP tunnel is selected for media communication by the ICE function, or media communication is performed. In the case of termination (call termination), the HTTP tunnel for media communication is terminated. To terminate the HTTP tunnel, for example, the terminal device T1 sends a request to the HTTP tunneling server HP1 to terminate the HTTP tunnel, and the HTTP tunneling server HP1 releases the settings for the HTTP tunnel or releases resources. It is to do.

  When the terminal device T1 determines that the SIP message transmission / reception operation has ended, such as when the control unit 12 detects the end of an application using SIP (Yes in step 6), the terminal device T1 constructed in step 4 The tunnel is terminated (step 7).

(Details of operation)
Hereinafter, the operation of the terminal device T1 will be described in more detail.

<UDP transparency judgment processing>
First, the UDP transmission determination process will be described with reference to the flowchart of FIG. First, the terminal device T1 transmits an address request message (UDP data) based on STUN to the STUN server ST1 by the function of the control unit 13 (step 11). Alternatively, a SIP-based Register message or INVITE message (both UDP data) is transmitted to the SIP server S1 (step 11). These messages are called UDP transparency determination messages. The terminal device T1 determines whether or not there is a response to the transmitted message (step 12). If there is a response, the terminal device T1 determines that the NAT device N1 is UDP transparent (step 13) and responds to the transmitted message. Otherwise, it is determined that the NAT device N1 is UDP non-transparent (step 14).

  FIG. 5 shows a sequence chart showing an example of the above processing. In the sequence chart shown in FIG. 5 and the subsequent sequence charts, the system configuration is as shown in FIG. Further, in each of the following sequence charts, the addresses and ports of the SIP server S1 and the STUN server ST1 are the same, and the ports for transmitting and receiving the SIP message and STUN message in each of the terminal devices T1 and T2 are the same. To do. Therefore, in the sequence chart, the address of the STUN server ST1 is described as S1, and the port as SP1.

  Also, in each sequence chart, A: B => C: D written at the bottom of the message indicates that the source address of the message is A, the source port is B, the destination address is C, and the destination port is D. Further, the reference symbol of the device indicates the address of the device. For example, the address of the terminal device T1 is denoted as T1. The reference symbol with P and parentheses indicates a port. For example, TP (SIP) 1 indicates a port used for SIP communication in the terminal device T1. However, as described above, the address of the STUN server ST1 is S1, and the port is SP1.

  In the example shown in FIG. 5A, a Binding Request that is an STUN address request message is transmitted to the STUN server (Step 21), and a Binding Response that is a response is returned to the terminal device T1 (Step 22). As shown in FIG. 5A, the source address and port of the Binding Request message are converted to the address and port of the NAT device N1 when passing through the NAT device N1.

  In the case shown in FIG. 5A, since a response is returned, the terminal device T1 determines that the network in which the terminal device T1 exists (that is, the NAT device N1) is UDP transparent. FIG. 5B shows an example when no response is returned from the STUN server. In this case, the terminal device T1 determines that the NAT device N1 is UDP non-transparent.

<HTTP tunnel construction, address assignment, etc.>
FIG. 6 shows a sequence chart regarding HTTP tunnel construction, address assignment, and the like. When UDP is not transparent, an HTTP tunnel is established between the terminal device T1 and the HTTP tunneling server HP1 as described above. Here, the terminal apparatus T1 sends a tunnel connection request to the HTTP tunneling server HP1 (step 24), the HTTP tunneling server HP1 makes settings necessary for HTTP tunnel communication, and a tunnel connection response is returned (step 25).

  Thereafter, the terminal device T1 transmits an address assignment request to the HTTP tunneling server HP1 to enable SIP communication with other devices such as a SIP server via the HTTP tunneling server HP1 (Step S1). 26) A response is received (step 27). Making an address assignment request and receiving an address assignment is exactly the same as making an address assignment request to the TURN server and receiving an address assignment in TURN. That is, this address request and assignment operation is performed by the TURN function unit 17 of the terminal device T1 and the TURN function in the HTTP tunneling server HP1.

  In the message returned from the HTTP tunneling server HP1 in step 27 of FIG. 6, the external communication address (AT (SIP) 1) of the terminal device T1 allocated in the HTTP tunneling server HP1 for SIP communication, and the port (ATP (SIP) 1) is included. Note that the address and port for external communication assigned by the HTTP tunneling server HP1 for the protocol X are denoted as AT (X) 1 and ATP (X) 1, respectively.

  The concept of this address assignment is shown in FIG. As shown in FIG. 7, AT (SIP) 1 and ATP (SIP) 1 are assigned to the HTTP tunneling server HP1, and when an external device (SIP server or the like) communicates with the terminal device T1, the transmission destination Specify AT (SIP) 1 and ATP (SIP) 1 as addresses. In addition, in the HTTP tunnel server HP1, at least the assigned address / port (AT (SIP) 1: ATP (SIP) 1) and the address / port outside the NAT device N1 for HTTP communication (N1: NP (HTTP) 1) is associated with the address / port (T1: TP (SIP) 1) of the terminal device T1, and is stored in the storage device.

  In FIG. 6, the terminal device T1 to subsequently perform SIP communication transmits a REGISTER message to the SIP server S1 using an HTTP tunnel (steps 28 and 29), and the SIP server S1 is the terminal device T1. Address (AT (SIP) 1: ATP (SIP) 1) is registered, and the response is returned to the terminal device T1 (steps 30, 31).

  As shown in FIG. 6, the destination address / port of the REGISTER message sent from the terminal device T1 is the address / port of the HTTP tunneling server HP1. Further, the address / port assigned by the HTTP tunneling server HP1 is set as the value of contact and via in the REGISTER message. Note that “A” in A @ AT (SIP) 1: ATP (SIP) 1 in contact indicates a user name. As a result, the SIP server S1 returns a response message (200 OK) to the AT (SIP) 1: ATP (SIP) 1 of the HTTP tunneling server HP1, and the HTTP tunneling server HP1 uses the HTTP tunnel to return the response message (200 OK) is returned to the terminal device T1.

<Detailed processing for SIP communication>
When it is determined in step 2 shown in FIG. 3 that UDP transmission is performed, SIP communication processing including ICE processing is performed.

  In the following, SIP message communication processing including ICE processing when it is determined that UDP is non-transparent will be described using the flowchart of FIG. 8 and the sequence charts of FIGS.

  In FIG. 8, for example, when the REGISTER ends in the terminal device T1 and an operation to start using the IP phone function is detected, or when an INVITE is received from another communication partner terminal, the ICE function Is activated (step 41). Activating the ICE function means activating a software module for realizing the ICE function.

  Further, the terminal device T1 constructs an HTTP tunnel for media communication with the HTTP tunneling server HP1 (step 42). Here, instead of constructing an HTTP tunnel, a SIP HTTP tunnel that has already been constructed may be used for media communication. Even when an already-established SIP HTTP tunnel is used for media communication, media communication uses a larger bandwidth than SIP communication, so a request to allocate bandwidth for media communication is sent from terminal device T1 to HTTP. Upon receiving the request from the tunneling server HP1, the HTTP tunneling server HP1 may allocate a bandwidth for media communication in the HTTP tunnel. It should be noted that such a bandwidth allocation is also included in the construction (setting) of an HTTP tunnel for media communication.

  After that, the SIP message that is a precondition for performing media communication using the HTTP communication HTTP tunnel constructed in step 4 of FIG. 3 and the external communication address / port assigned to the HTTP tunneling server HP1. In addition to the exchange, a determination is made as to which address of the plurality of candidates is used for media communication based on the ICE (step 43).

  Here, when the terminal device T1 determines not to perform media communication using HTTP tunneling by the ICE function (No in step 43), the HTTP tunnel constructed for media communication is terminated (step 44). Terminating an HTTP tunnel established for media communication means that if an HTTP tunnel is established for media communication separately from SIP, it is terminated, and the SIP HTTP tunnel is also used for media communication. For example, the bandwidth allocated for media communication in the HTTP tunnel is released. To terminate an HTTP tunnel constructed for media communication, for example, the terminal device T1 sends a request for terminating the HTTP tunnel to the HTTP tunneling server HP1, and the HTTP tunneling server HP1 releases the bandwidth and cancels the setting. The response is returned to the terminal device T1.

  If it is determined that media communication using HTTP tunneling is to be performed (Yes in step 43), media communication (call) using HTTP tunneling is performed, and if media communication ends (Yes in step 45), the media communication The HTTP tunnel is terminated (step 46). Note that the end of media communication can be determined by, for example, detecting (transmitting or receiving by yourself) a message (Bye or the like) notifying the end of media communication in the control unit 12 of the terminal device T1.

  Next, FIG. 9 to FIG. 11 show sequence charts related to INVITE message transmission and response reception when the NAT device N1 is UDP non-transparent and the NAT device N2 is UDP transparent in the system of FIG. The terminal device T2 has the same function as the terminal device T1, and if the terminal device T2 is UDP transparent, an HTTP tunnel for SIP communication is not established between the HTTP tunneling server HP2 and UDP non-transparent. Then, it is assumed that an HTTP tunnel for SIP communication is established with the HTTP tunneling server HP2. In the following description, message transmission / reception between a terminal device on the UDP non-transparent side and the HTTP tunneling server is performed using an HTTP tunnel.

  9 to 11, the TURN server TU is used on the terminal device T2 side that is transparent to UDP. However, the TURN server TU may be the same device as the HTTP tunneling server HP2.

  In FIG. 9, the terminal device T1 requests the HTTP tunneling server HP1 to assign an external communication address for media communication using the TURN function based on the control of the ICE (step 61). The request includes an address / port (T1: TP (RTP) 1) for media communication in the terminal device T1. The HTTP tunneling server HP1 assigns an external communication address (AT (RTP) 1: ATP (RTP) 1) for media communication to the request, and assigns it to the address for media communication (T1: TP (RTP) 1) and the external address (N1: NP (HTTP) 1) of the NAT device N1 in HTTP tunnel communication.

  Then, the HTTP tunneling server HP1 returns an allocation response including the allocated address / port (AT (RTP) 1: ATP (RTP) 1) to the terminal device T1 (step 62).

  Thereafter, the terminal device T1 transmits an INVITE message using the HTTP tunnel (steps 63 and 64). In this INVITE message, as in the REGISTER message, the external communication address / port for SIP communication is set as the values of contact and via.

  Also, the ICE function includes (T1: TP (RTP) 1) for media communication of the terminal device T1 as a host candidate address in the INVITE message, and is assigned to the HTTP tunneling server HP1 as a relayed candidate address. The external communication address for the media is included.

  Here, a general ICE function will be described. In the configuration shown in FIG. 15, the terminal device 10 that supports the ICE function includes an address / port of the terminal device 10 itself, an address / port outside the NAT device 30 (obtained using STUN), and an external assigned by the TURN server 50. The communication address / port is acquired and notified to the other terminal device 20 using a SIP message. The terminal device 20 that supports the ICE function also includes the address / port of the terminal device 20 itself, the address / port outside the NAT device 40 (obtained using STUN), and the address / port for external communication assigned in the TURN server 50. Acquire it and notify it to the other terminal device 10. Each terminal device that has received the address information about the other party tries to communicate with the received address, and performs media communication with an address having a high priority among addresses where communication is possible. Here, the address of the terminal device itself is called Host Candidate, the address outside the NAT device is called Server Reflexive candidate, and the address for external communication assigned by the TURN server is called Relayed Candidate.

  In the INVITE transmission in UDP non-transparent shown in FIG. 9, Server Reflexive candidates are not included, but in the case of UDP non-transparent, communication using Server Reflexive candidates cannot be performed in the first place.

  The INVITE message transmitted from the terminal device T1 is sent to the SIP server S1 via the HTTP tunneling server HP1 (step 64). The SIP server S1 transmits the INVITE message toward the terminal device T2 (step 65). Since the terminal device T2 side is UDP transparent, it is assumed that the SIP server S1 holds the external address of the NAT device N2 as a message transmission destination to the terminal device T2.

  The terminal device T2 that has received the INVITE message acquires Server Reflexive candidates by control based on the ICE function (Steps 66 and 67 in FIG. 10), and further acquires Relayed Candidate (Steps 68 and 69). Then, a 200 OK message including the host candidate, Server Reflexive candidate, and Relayed Candidate is transmitted to the SIP server S1 (step 70 in FIG. 11). The SIP server S1 transmits the 200 OK message to the external communication address of the terminal device T1 (step 71). Then, the HTTP tunneling server HP1 transmits a 200 OK message to the terminal device T1 using the HTTP tunnel (step 72). The terminal device T1 that has received the 200 OK message returns ACK (steps 73 to 75).

  After that, the optimum address is determined based on the ICE specification. That is, the communication path is determined by the Nomination defined in the ICE. Here, the external communication address for the terminal device T1 assigned to the HTTP tunneling server HP1 is defined in the ICE in the same position as the external communication address (Relayed Candidate) in the TURN server specified in the ICE. The selection process is performed. Here, when a route using the HTTP tunnel between the HTTP tunneling server HP1 and the terminal device TP1 is selected, the HTTP tunnel is continuously used. Further, for example, when communication between the host candidates of the terminal device T1 and the terminal device T2 is possible, a route using the HTTP tunnel is not selected, and the HTTP tunnel for media communication is terminated. For example, the terminal device T1 determines that the route using the HTTP tunnel has not been selected by not receiving a communication confirmation message (using a relayed candidate) using the route using the HTTP tunnel from the terminal device T2. it can.

  Next, FIGS. 12 to 14 show sequences of INVITE message transmission and response reception when both the terminal device T1 side and the terminal device T2 side are UDP non-transparent. In this case, on the terminal device T2 side, similarly to the terminal device T1 side, an HTTP tunnel for SIP communication is established with the HTTP tunneling server HP2, and REGISTER is also completed.

  Steps 81 to 84 in the sequence shown in FIG. 12 are the same as steps 61 to 64 in FIG. In steps 85 and 86 of FIG. 12, unlike the case of FIG. 9, the INVITE message transmitted from the SIP server S1 is transmitted to the terminal apparatus T2 via the HTTP tunneling server HP2 via the HTTP tunnel. Thereafter, the terminal device T2 receives a relayed candidate assignment in the same manner as when the terminal device T1 transmits INVITE in steps 87 and 88 in FIG. 13, and sends a 200 OK message including the host candidate and the relayed candidate through the HTTP tunnel. (Steps 89 and 90 in FIG. 14).

  The SIP server S1 that has received the 200 OK message transmits the 200 OK message to the terminal device T1 in the same manner as in FIG. 11 (steps 91 and 92). Then, ACK is returned from the terminal device T1 (steps 93 to 96).

  Also in this case, after that, when the route selection process is performed and a route using the HTTP tunnel between the HTTP tunneling server HP1 and the terminal device T1 is selected, the HTTP tunnel continues on the terminal device T1 side. Used. Further, when a route using an HTTP tunnel between the HTTP tunneling server HP2 and the terminal device T2 is selected, the HTTP tunnel is continuously used on the terminal device T2 side. In addition, when the route using the HTTP tunnel is not selected on each of the terminal device T1 side and the terminal device TP1 side, the HTTP tunnel for media communication ends.

  As described above, according to the system of the present embodiment, when media communication such as VoIP based on SIP is performed between terminal devices via a NAT device, HTTP tunneling is selected as a NAT traversal method as necessary. It is possible to provide a technology that makes it possible. In addition, according to the present embodiment, an HTTP tunnel is not always established, the time for using the HTTP tunnel is suppressed, and the cost burden of the HTTP tunneling server can be suppressed.

  The present invention is not limited to the above-described embodiments, and various modifications and applications are possible within the scope of the claims.

1 is an overall configuration diagram of a system in an embodiment of the present invention. It is a functional block diagram of a terminal device. It is a flowchart for demonstrating the outline | summary of operation | movement of a terminal device. It is a flowchart for demonstrating a UDP transparent determination process. It is a sequence chart for demonstrating UDP permeation | transmission determination processing. It is a sequence chart regarding HTTP tunnel construction, address allocation, and the like. It is a figure which shows the concept of the address assignment for external communications. It is a flowchart for demonstrating the process when it determines with it being UDP non-transparent. It is a sequence chart (1) for demonstrating a message communication process. It is a sequence chart (2) for demonstrating a message communication process. It is a sequence chart (3) for demonstrating a message communication process. It is a sequence chart (4) for demonstrating a message communication process. It is a sequence chart (5) for demonstrating a message communication process. It is a sequence chart (6) for demonstrating a message communication process. It is a figure for demonstrating the function of ICE.

Explanation of symbols

N1, N2, 30, 40 NAT device
T1, T2, 10, 20 Terminal equipment
S1 SIP server
ST1 STUN server
HP1, HP2 HTTP tunneling server 6 Internet 7, 8 Private network 11 Communication interface unit 12 Control unit 13 HTTP tunneling function unit 14 Media communication unit 15 SIP function unit 16 STUN function unit 17 TURN function unit 18 ICE function unit
50 TURN server

Claims (6)

A terminal device provided under the NAT device,
UDP that transmits a UDP transmission determination message to a predetermined device connected to a communication network outside the NAT device and determines whether to receive a response message from the predetermined device in response to the UDP transmission determination message Transmission determining means;
When the UDP transmission determining means determines that the response message from the predetermined device has not been received, an HTTP tunnel is set up with the HTTP tunneling device connected to the communication network outside the NAT device. HTTP tunnel setting means,
A terminal device comprising signaling message communication means for transmitting and receiving a signaling message for media communication with another terminal device via the HTTP tunnel.   The terminal device according to claim 1, further comprising means for terminating the HTTP tunnel when the terminal device detects that the operation of the function using the signaling message is terminated in the terminal device. The terminal device has address assignment request means for requesting the HTTP tunneling device to assign an external communication address for communicating with an external device connected to a communication network outside the NAT device;
The terminal device includes the external communication address assigned by the HTTP tunneling device as a destination address for communication from the external device to the terminal device in the signaling message. The terminal device according to 1 or 2. The HTTP tunnel setting means has means for setting an HTTP tunnel for media communication with the HTTP tunneling device,
The terminal device
As an address that is a candidate for receiving media communication data from the other terminal device, at least the address of the terminal device itself, and an external communication address assigned for media communication of the terminal device in the HTTP tunneling device; Transmitting means for transmitting to the other terminal device;
Means for terminating the HTTP tunnel for media communication when the external communication address for media communication is not selected as an address for media transmission to the terminal device in the other terminal device having the ICE function The terminal device according to claim 1, further comprising: A NAT traversing method executed by a terminal device provided under a NAT device,
UDP that transmits a UDP transmission determination message to a predetermined device connected to a communication network outside the NAT device and determines whether to receive a response message from the predetermined device in response to the UDP transmission determination message A transmission determination step;
If it is determined by the UDP transparency determination step that a response message from the predetermined device has not been received, an HTTP tunnel is set up with an HTTP tunneling device connected to a communication network outside the NAT device. HTTP tunnel setup step,
And a signaling message communication step of transmitting and receiving a signaling message for media communication with another terminal device via the HTTP tunnel. A program for causing a computer to function as a terminal device provided under a NAT device, the computer comprising:
UDP that transmits a UDP transmission determination message to a predetermined device connected to a communication network outside the NAT device and determines whether to receive a response message from the predetermined device in response to the UDP transmission determination message Transmission judging means,
When the UDP transmission determining means determines that the response message from the predetermined device has not been received, an HTTP tunnel is set up with the HTTP tunneling device connected to the communication network outside the NAT device. HTTP tunnel setting means,
Signaling message communication means for transmitting and receiving a signaling message for media communication with other terminal devices via the HTTP tunnel,
Program to function as.

Images