US8462800B2 - Gateway device and port number assignment method - Google Patents

Gateway device and port number assignment method Download PDF

Info

Publication number
US8462800B2
US8462800B2 US12/943,726 US94372610A US8462800B2 US 8462800 B2 US8462800 B2 US 8462800B2 US 94372610 A US94372610 A US 94372610A US 8462800 B2 US8462800 B2 US 8462800B2
Authority
US
United States
Prior art keywords
port number
address
gateway device
message
conversion
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related, expires
Application number
US12/943,726
Other languages
English (en)
Other versions
US20110122880A1 (en
Inventor
Shinichiro Saito
Shigehiro Onizawa
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hitachi Ltd
Original Assignee
Hitachi Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hitachi Ltd filed Critical Hitachi Ltd
Assigned to HITACHI, LTD. reassignment HITACHI, LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ONIZAWA, SHIGEHIRO, SAITO, SHINICHIRO
Publication of US20110122880A1 publication Critical patent/US20110122880A1/en
Application granted granted Critical
Publication of US8462800B2 publication Critical patent/US8462800B2/en
Expired - Fee Related legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2514—Translation of Internet protocol [IP] addresses between local and global IP addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2517—Translation of Internet protocol [IP] addresses using port numbers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1033—Signalling gateways
    • H04L65/104—Signalling gateways in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]

Definitions

  • the present invention relates to a gateway device and a port number assignment method, and more particularly, to a gateway device and a port number assignment method using a real-time packet.
  • NAPT Network Address Translator
  • NAT-PT network address translation-protocol translation
  • IPv4 Internet protocol version 4
  • IPv6 Internet protocol version 6
  • NAPT and NAT-PT enable interconnection between different networks by appropriately converting a port number of an IP header and a transmission control protocol (TCP)/user datagram protocol (UDP) header.
  • TCP transmission control protocol
  • UDP user datagram protocol
  • an address and a port number are described in a payload according to an application.
  • NAPT and NAT-PT there is a need to rewrite an address and port number information in the payload part in addition to the IP header and the TCP/UDP header.
  • ALG application level gateway
  • a session initiation protocol (SIP) message needs rewrite of the payload part.
  • SIP session initiation protocol
  • JP-A-2005-073302 enables interconnection using the SIP message in an environment of using NAT-PT by converting the SIP message.
  • a real time streaming protocol is a protocol controlling streaming delivery of a voice, a video signal, and the like, and also corresponds to a protocol where information needing conversion is written in the payload part.
  • a client port number to be used for a real-time transport protocol (RTP)/RTP control protocol (RTCP) is described in a message of a SETUP method. Accordingly, the SETUP message needs to be rewritten by an RTSP-ALG in an environment where NAPT processing or NAT-PT is performed.
  • a segment length of TCP is different with respect to before conversion and after conversion.
  • an acknowledgment number with respect to a corresponding message and a sequence number of a subsequent packet may also change. This is because a value in which the TCP segment length is added to the sequence number is used as the acknowledgement number. Also, this is because a value in which this TCP segment length is added to a previous sequence number is used as the sequence number.
  • a converter for performing NAPT processing or NAT-PT needs to have a difference list with respect to the sequence number and the acknowledgement number, and then needs to rewrite the sequence number and the acknowledgement number with respect to a packet received thereafter (see “network address translation-protocol translation (NAT-PT)”).
  • NAT-PT network address translation-protocol translation
  • RTSP RTSP
  • UDP delivery UDP delivery
  • IL interleave
  • the IL delivery superimposes RTP/RTCP data on a TCP session for an RTSP control message. Accordingly, when the segment length changes, conversion cost of the sequence number and the acknowledgement number may increase significantly.
  • JP-A-2009-015392 discloses a study that may not decrease a transfer rate when a packet is lost by transmitting a proxy ACK in addition to the aforementioned difference list.
  • NAT-PT Network Address Translation-Protocol Translation
  • JP-A-2009-015392 JP-A-2009-015392
  • the present invention relates to a technique that may not change a segment length when an RTSP SETUP message is rewritten.
  • the present invention provides a gateway device and a port number assignment method that may have no need to rewrite a sequence number and an acknowledgment number of a subsequent packet.
  • a gateway device including a packet distribution processing unit, a header converting unit, and a transfer processing unit, and converting a first Internet protocol (IP) address and a second IP address by referring to an IP address conversion table.
  • the gateway device may further include a payload IP address converting unit.
  • the payload IP address converting unit may acquire a number of digits of a second port number included in a payload of a control message, convert the second port number to a first port number having the same number of digits, store the second port number and the first port number in the IP address conversion table, and convert, to the second port number, the first port number included in a response message with respect to the control message.
  • a method for assigning a port number including the steps of: receiving a message to determine a destination IP address; determining an application protocol; determining a method; determining a transfer direction; when the transfer direction is upstream, acquiring a number of digits of a request port number described in a payload of the message, assigning a port number having the same number of digits, and recording the assigned port number in the IP address conversion table; when the transfer direction is downstream, acquiring a request port number from the IP address conversion table; updating the payload; and converting an IP address and a port number described in a header of the message.
  • FIG. 1 is a hardware block diagram of a network system
  • FIG. 2A is a diagram to describe a SETUP packet and a response packet thereof;
  • FIG. 2B is a diagram to describe a SETUP packet and a response packet thereof;
  • FIG. 2C is a diagram to describe a SETUP packet and a response packet thereof
  • FIG. 2D is a diagram to describe a SETUP packet and a response packet thereof
  • FIG. 3 is a diagram to describe a network address port translation (NAPT) table
  • FIG. 4 is a block diagram to describe a configuration of a gateway device
  • FIG. 5 is a flowchart to describe processing of a gateway device
  • FIG. 6 is a flowchart to describe gateway processing
  • FIG. 7 is a sequence diagram from an RTSP session establishment to disconnection
  • FIG. 8A shows a real time streaming protocol (RTSP) SETUP message (four-digit port number);
  • RTSP real time streaming protocol
  • FIG. 8B shows an RTSP SETUP response message (four-digit port number).
  • FIG. 9A shows an RTSP SETUP message (five-digit port number).
  • FIG. 9B shows an RTSP SETUP response message (five-digit port number).
  • FIG. 10 is a sequence diagram to describe a sequence number and an acknowledgement number before and after a message rewrite.
  • the network system 500 includes a plurality of terminals 100 connected to a local area network (LAN) 102 , the gateway device 200 connecting the LAN 102 and a wide area network (WAN) 103 , and a contents server 300 connected to the WAN 300 .
  • LAN local area network
  • WAN wide area network
  • Private Internet protocol (IP) addresses 113 - 1 to 113 - 3 are assigned to terminals 100 - 1 to 100 - 3 .
  • the WAN 103 is connected to the Internet and a regional network where a communication carrier is installed, and uses a global IP address.
  • the terminals 100 - 1 to 100 - 3 belonging to the LAN side network 102 access the contents server 300 of the WAN side network 103 , the terminals 100 - 1 to 100 - 3 may perform communication by address and port conversion using a network address translation (NAT) function.
  • NAT network address translation
  • FIG. 2 briefly shows an IP header 109 of a message 108 , a transmission control protocol (TCP) header 110 , and a message 111 of a data part.
  • TCP transmission control protocol
  • a SETUP message 108 - 1 is transmitted from the terminal 100 - 1 to the contents server 300 .
  • the gateway device 200 converts Src IP (source IP address) 192.168.1.10 to IP address 2.2.2.2 of WAN side interface (I/F) 113 - 4 of the gateway device 200 , in order to transfer the packet 108 - 1 to the contents server 300 belonging to the WAN 103 .
  • Src port (source port number) 6001 is also converted to a port number 40001 secured by the gateway device 200 .
  • the gateway device 200 stores a corresponding relation in a NAPT table 220 . Even when the gateway device 200 receives a response message 108 - 3 from the contents server 300 , the gateway device 200 reversely converts Dst IP 2.2.2.2 (destination IP address) to 192.168.1.10, and converts Dst Port (destination port number) 40001 to 6001 by referring to the above corresponding relation. As a result, the packet reaches the terminal 100 - 1 . A basic operation of NAPT has been described so far.
  • FIG. 2C and FIG. 2D show a response message from the contents server 300 and a reversely converted message thereof.
  • a port number having the same number of digits as the notified port number is assigned, which will be described below.
  • the NAPT table 220 will be described with reference to FIG. 3 .
  • the NAPT table 220 includes a source IP address 221 , a source port number 222 , a conversion IP address 223 , a conversion port number 224 , and a final use date and time 225 .
  • the source IP address 221 is a private IP address used for the LAN 102 .
  • the source port number 222 is a port number of the terminal 100 - 1 connected to the LAN 102 .
  • the conversion IP address 223 is a WAN side IP address of the gateway device 200 .
  • the conversion port number 224 is a WAN side port number of the gateway device 200 .
  • the final use date and time 225 is a date and time when a corresponding entry is finally generated or referred to. The final use date and time 225 is used for deletion of the corresponding entry.
  • an upstream packet refers to the conversion IP address 223 and the conversion port number 224 using, as a key, the source IP address 221 and the source port number 222 .
  • a downstream packet refers to the source IP address 221 and the source port number 222 using, as a key, the conversion IP address 223 and the conversion port number 224 .
  • Entries 2 , 3 , 6 , and 7 emphasized in FIG. 3 are entries registered by RTSP-application level gateway (ALG) processing. Since a source port number of each of the entries 2 and 3 is of four digits, a four-digit port number is assigned as a conversion port number. Since a source port number of each of the entries 6 and 7 is of five digits, a five-digit port number is assigned as the conversion port number. Entries 1 , 4 , 5 , and 8 entered by general NAPT processing may be assigned with the conversion port number regardless of a number of digits of the source port number. Accordingly, empty port numbers are sequentially assigned regardless of the number of digits.
  • the gateway device 200 includes a packet reception processing unit 201 , a packet distribution processing unit 202 , a transfer processing unit 203 , a packet transmission processing unit 204 , a NAPT processing unit 205 , an RTSP-ALG processing unit 206 , a conversion port number pool 207 , an aging processing unit 208 , and a NAPT table 220 .
  • the packet reception processing unit 201 of LAN I/F or WAN I/F receives a packet from LAN or WAN.
  • the packet reception processing unit 201 transfers the received packet to the packet distribution processing unit 202 .
  • the packet distribution processing unit 202 distributes the packet to the transfer processing unit 203 , the NAPT processing unit 205 , or the RTSP-ALG processing unit 206 based on contents of the packet.
  • NAPT processing such as transferring within the same network is not required
  • the packet distribution processing unit 202 distributes the packet to the transfer processing unit 203 .
  • the packet distribution processing unit 202 distributes the packet to the NAPT processing unit 205 .
  • the NAPT processing unit 205 refers to the NAPT table 220 .
  • the NAPT processing unit 205 is assigned with a port number available as a conversion port number from the conversion port number pool 207 , as an initially passing packet.
  • the NAPT processing unit 205 rewrites an IP address and a port number included in an IP header and a TCP header.
  • the NAPT processing unit 205 makes an entry in the NAPT table 220 .
  • the NAPT processing unit 205 With respect to a packet received after a second time and a response packet from the server, the NAPT processing unit 205 rewrites and thereby transfers the packet by referring to the NAPT table 220 .
  • the packet distribution processing unit 202 distributes the packet to the RTSP-ALG processing unit 206 .
  • the RTSP-ALG processing unit 206 detects the port number used in real-time transport protocol (RTP) and RTP control protocol (RTCP) based on contents written in the message.
  • the RTSP-ALG processing unit 206 assigns a port number having the same number of digits as the detected port number from the conversion port number pool 207 , and rewrites the message.
  • the RTSP-ALG processing unit 206 registers the rewritten message in the NAPT table 220 .
  • the RTSP-ALG processing unit 206 When a SETUP response message is received, reversely, the RTSP-ALG processing unit 206 rewrites the message by referring to the NAPT table 220 .
  • the RTSP-ALG processing unit 206 transmits the message to the NAPT processing unit 205 .
  • the NAPT processing unit 205 performs NAPT processing and transfers the message to the transfer processing unit 203 .
  • the aging processing unit 208 refers to the final use date and time 225 of the NAPT table 220 at predetermined cycles.
  • the aging processing unit 208 deletes, from the NAPT table 220 , an entry not used for a predetermined amount of time, and returns the assigned port number to the conversion port number pool 207 .
  • a processing flow of the gateway device 200 will be described with reference to FIG. 5 .
  • This flow is initiated by packet reception.
  • the gateway device 200 determines whether the received packet corresponds to NAPT target by referring to a destination IP address (S 401 ).
  • the gateway device 200 performs general transfer processing (S 402 ) and then terminates.
  • the gateway device 200 determines an application protocol (S 403 ).
  • the gateway device 200 performs NAPT processing (S 404 ).
  • NAPT processing performs source address conversion and source port conversion.
  • NAPT processing performs destination address conversion and destination port conversion.
  • upstream herein is communication from the terminal 100 to the contents server 300
  • downstream is communication from the contents server 300 to the terminal 100 .
  • the gateway device 200 determines an RTSP method (S 405 ). Specifically, the gateway device 200 determines whether the method is SETUP. When the method is determined as a method excluding the SETUP method, the gateway device 200 goes to step 404 . When the method is determined as the SETUP method (including Reply) in step 405 , the gateway device 200 executes gateway processing (S 406 ) and goes to step 404 .
  • the gateway processing (S 406 ) will be described with reference to FIG. 6 .
  • the RTSP-ALG processing unit 206 determines a transfer direction (S 501 ). In the case of upstream direction, the RTSP-ALG processing unit 206 reads a number of digits of a request port from a SETUP message (S 502 ). The RTSP-ALG processing unit 206 assigns a port number having the same number of digits (S 503 ). Next, the RTSP-ALG processing unit 206 makes an entry in the NAPT table 220 by making, as a set, a source address, a source port number, and a conversion address with the assigned port number.
  • the RTSP-ALG processing unit 206 rewrites the message with the assigned port number (S 505 ). Meanwhile, in the case of downstream direction in step 501 , the RTSP-ALG processing unit 206 goes to step 505 by searching and referring to the NAPT table 220 (S 506 ).
  • RTSP A sequence from RTSP session establishment to termination in an environment using the gateway device 200 will be described with reference to FIG. 7 .
  • the terminal 100 - 1 and the contents server 300 initially exchange available function information using an OPTION method.
  • the terminal 100 - 1 acquires contents information using a DESCRIBE method.
  • the terminal 100 - 1 determines a transmission scheme using a SETUP method.
  • the above sequence will be described in detail.
  • the terminal 100 - 1 transmits an OPTION message describing an available function to the gateway device 200 (S 601 ).
  • the gateway device 200 converts a source IP address and a source port number and transmits the OPTION message to the contents server 300 (S 602 ).
  • the contents server 300 transmits 200 OK describing an available function to the gateway device 200 (S 603 ).
  • the gateway device 200 converts a destination IP address and a destination port number and transmits 200 OK to the terminal 100 - 1 (S 604 ).
  • the terminal 100 - 1 transmits a DESCRIBE message for acquiring contents information to the gateway device 200 (S 606 ).
  • the gateway device 200 converts a source IP address and a source port number and transmits the DESCRIBE message to the contents server 300 (S 607 ).
  • the contents server 300 transmits 200 OK describing contents information to the gateway device (S 608 ).
  • the gateway device 200 converts a destination IP address and a destination port number and transmits 200 OK to the terminal 100 - 1 (S 609 ).
  • the terminal 100 - 1 transmits a SETUP message describing available Transport to the gateway device 200 (S 611 ).
  • the gateway device 200 reads a source port number from the SETUP message and converts the read source number to a port number having the same number of digits (S 612 ).
  • the gateway device 200 converts a source IP address and a source port number of a header and transmits the SETUP message to the contents server 300 (S 613 ).
  • the contents server 300 transmits 200 OK describing selected Transport to the gateway device 200 (S 614 ).
  • the gateway device 200 reads a destination port number from 200 OK, and converts the read destination port number to an original source port number (S 616 ).
  • the gateway device 200 converts the destination IP address and the destination port number and transmits 200 OK to the terminal 100 - 1 (S 617 ).
  • the terminal 100 - 1 transmits a PLAY message to the gateway device 200 (S 618 ).
  • the gateway device 200 converts a source IP address and a source port number, and transmits the PLAY message to the contents server 300 (S 619 ).
  • the contents server 300 transmits 200 OK to the gateway device 200 (S 621 ).
  • the gateway device 200 converts a destination IP address and a destination port number, and transmits 200 OK to the terminal 100 - 1 (S 622 ).
  • the terminal 100 - 1 and the contents server 300 start exchanging of an RTP packet and an RTCP packet. Subsequently, the terminal 100 - 1 transmits, to the gateway device 200 , a TEARDOWN message that is an end of reproduction (S 623 ).
  • the gateway device 200 converts a source IP address and a source port number and transmits the TEARDOWN message to the contents server 300 (S 624 ).
  • the contents server 300 transmits 200 OK to the gateway device 200 (S 626 ).
  • the gateway device 200 converts a destination IP address and a destination port number and transmits 200 OK to the terminal 100 - 1 (S 627 ).
  • the terminal (RTSP client) 100 - 1 notifies a port number to be used. However, since the port number is changed in an NAT environment, the gateway device 200 rewrites a message to a conversion port number having the same number of digits. The gateway device 200 also rewrites a response message (200 OK) by referring to the NAPT table 220 . Reproduction of contents uses the PLAY method. Next, streaming transfer is performed by the RTP packet and RTCP packets using a transmission method determined by the SETUP method. Finally, reproduction of contents is terminated by the TEARDOWN method.
  • FIG. 8 A(a) shows a message 108 A- 1 of the SETUP method transmitted by the terminal 100 - 1 .
  • FIG. 8 A(b) shows a message 108 A- 2 of the SETUP message transmitted by the gateway device 200 .
  • the SETUP method may be determined depending on whether a character string of “SETUP” exists in a front part of a payload.
  • the gateway device 200 acquires a number of digits of this port number and assigns a conversion port number having the same number of digits, and rewrites the message in FIG. 8 A(b).
  • FIG. 8 B(a) shows a response message 108 A- 3 of the SETUP method transmitted by the contents server 300 .
  • FIG. 8 B(b) shows a response message 108 A- 4 of the SETUP method transmitted by the gateway device 200 .
  • FIG. 8A and FIG. 8B show a case where a port number has four digits.
  • FIG. 9A and FIG. 9B show a case where the port number has five digits.
  • FIG. 10 shows a circumstance where data only from a client to a server is described. Also, a round value is used as a segment length.
  • the gateway device 200 converts a source IP address and a source port number and transfers the packet to the contents server 300 (S 902 ).
  • the gateway device 200 converts a destination IP address and a destination port number and transfers Ack to the terminal 100 - 1 (S 904 ).
  • the terminal 100 - 1 transmits a SETUP message 903 of the segment length 100 (S 906 ).
  • the gateway device 200 rewrites the message (S 907 ).
  • the gateway device 200 transmits the rewritten message to the contents server 300 (S 908 ). In this case, when the message is rewritten, the number of digits of the port number is matched and thus, the segment length does not change.
  • the gateway device 200 may need to rewrite the sequence number and the acknowledgement number indicated by the square within the range indicated in FIG. 10 in order to maintain a consistency of TCP sequence. Also, since the influence on all the subsequent acknowledgement numbers of sequence and sequence numbers is exerted, there is a need to rewrite the sequence number and the acknowledgement number.
  • the gateway device 200 converts the destination IP address and the destination port number and transfers Ack to the terminal 100 - 1 (S 911 ).
  • the gateway device 200 converts the source IP address and the source port number and transfers the packet to the contents server 300 (S 913 ).
  • the gateway device 200 converts the destination IP address and the destination port number and transfers Ack to the terminal 100 - 1 (S 916 ).
  • a port number having the same number of digits is assigned as the conversion port number. Specifically, it is guaranteed that the segment length after a message rewrite does not change. Accordingly, with respect to a following sequence, there is no need to rewrite the acknowledgement number and the sequence number.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
US12/943,726 2009-11-11 2010-11-10 Gateway device and port number assignment method Expired - Fee Related US8462800B2 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2009-257722 2009-11-11
JP2009257722A JP5357707B2 (ja) 2009-11-11 2009-11-11 ゲートウェイ装置およびポート番号割当て方法

Publications (2)

Publication Number Publication Date
US20110122880A1 US20110122880A1 (en) 2011-05-26
US8462800B2 true US8462800B2 (en) 2013-06-11

Family

ID=44062041

Family Applications (1)

Application Number Title Priority Date Filing Date
US12/943,726 Expired - Fee Related US8462800B2 (en) 2009-11-11 2010-11-10 Gateway device and port number assignment method

Country Status (2)

Country Link
US (1) US8462800B2 (enrdf_load_stackoverflow)
JP (1) JP5357707B2 (enrdf_load_stackoverflow)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130301650A1 (en) * 2012-05-14 2013-11-14 Futurewei Technologies, Inc. Stateless NAT44
US20190191014A1 (en) * 2017-12-19 2019-06-20 Beijing Baidu Netcom Science And Technology Co., Ltd. Data transmission method and gateway as well as server and computer-readable storage medium

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5760901B2 (ja) * 2011-09-26 2015-08-12 ブラザー工業株式会社 通信装置及び通信システム
US8837474B2 (en) * 2011-12-19 2014-09-16 Qualcomm Incorporated Apparatus and methods for efficient network address translation and application level gateway processing
TW201345237A (zh) * 2012-04-27 2013-11-01 Univ Nat Taipei Technology Ｔｃｐ穿越ｎａｔ於ｒｔｓｐ上應用
US10097454B1 (en) * 2015-06-10 2018-10-09 Amazon Technologies, Inc. Flexible packet rewriting framework
US10749808B1 (en) 2015-06-10 2020-08-18 Amazon Technologies, Inc. Network flow management for isolated virtual networks
CN106331194A (zh) * 2015-06-23 2017-01-11 中兴通讯股份有限公司 一种域名解析方法及装置
IL240909A (en) 2015-08-27 2017-04-30 Syber 2 0 (2015) Ltd Mixing communication inlets for computer networks
KR20180099683A (ko) 2015-12-31 2018-09-05 사이버 2.0 (2015) 엘티디. 컴퓨터 네트워크에서 트래픽 모니터링
US10397196B2 (en) 2017-02-28 2019-08-27 Cyber 2.0 (2015) Ltd. Port-scrambling-based networks
US10645437B2 (en) 2017-04-03 2020-05-05 Sling Media Pvt Ltd Systems and methods for achieving optimal network bitrate
CN110324159B (zh) * 2018-03-28 2020-11-03 华为技术有限公司 链路配置方法、控制器和存储介质
US11082338B1 (en) 2018-04-17 2021-08-03 Amazon Technologies, Inc. Distributed connection state tracking for large-volume network flows
US11108687B1 (en) 2018-09-12 2021-08-31 Amazon Technologies, Inc. Scalable network function virtualization service
US10897417B2 (en) 2018-09-19 2021-01-19 Amazon Technologies, Inc. Automated route propagation among networks attached to scalable virtual traffic hubs
US10834044B2 (en) 2018-09-19 2020-11-10 Amazon Technologies, Inc. Domain name system operations implemented using scalable virtual traffic hub
WO2023032210A1 (ja) * 2021-09-06 2023-03-09 日本電信電話株式会社 ゲートウェイ装置、通信方法、及びプログラム
CN114244908B (zh) * 2021-11-05 2024-08-23 浙江蓝卓工业互联网信息技术有限公司 一种跨网域的rtsp流媒体传输方法
US11765238B1 (en) * 2022-06-21 2023-09-19 Juniper Networks, Inc. Non-translated port oversubscribing for a proxy device

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6611533B1 (en) * 1999-01-13 2003-08-26 Nortel Networks Limited Public telephone network, intelligent network, and internet protocol network services interworking
US20050018651A1 (en) * 2003-07-22 2005-01-27 Innomedia Pte Ltd. Stand alone multi-media terminal adapter with network address translation and port partitioning
JP2005073302A (ja) 2004-11-29 2005-03-17 Hitachi Ltd アドレス変換方法
US20050117605A1 (en) * 2003-07-22 2005-06-02 Innomedia Pte Ltd. Network address and port translation gateway with real-time media channel management
US20050254482A1 (en) * 2004-05-14 2005-11-17 Eung-Moon Yeom Apparatus and method for voice processing of voice over internet protocol (VoIP)
JP2009015392A (ja) 2007-06-29 2009-01-22 Mitsubishi Electric Corp 通信装置および通信方法
US20110026537A1 (en) * 2008-03-20 2011-02-03 Telefonaktiebolaget Lm Ericsson (Publ) Method and Apparatus for Communication of Data Packets between Local Networks
US20110064075A1 (en) * 1998-12-04 2011-03-17 David Michael Sprague METHODS AND SYSTEMS FOR COMMUNICATING SIGNALING SYSTEM 7 (SS7) USER PART MESSAGES AMONG SS7 SIGNALING POINTS (SPs) AND INTERNET PROTOCOL (IP) NODES USING SIGNAL TRANSFER POINTS (STPs)
US8145788B1 (en) * 2002-05-31 2012-03-27 Emc Corporation Distributed ISP load balancer

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002152256A (ja) * 2000-11-09 2002-05-24 Sony Corp アドレス変換装置及びその方法
JP4334505B2 (ja) * 2005-05-31 2009-09-30 日本電信電話株式会社 中継装置およびデータ中継方法

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110064075A1 (en) * 1998-12-04 2011-03-17 David Michael Sprague METHODS AND SYSTEMS FOR COMMUNICATING SIGNALING SYSTEM 7 (SS7) USER PART MESSAGES AMONG SS7 SIGNALING POINTS (SPs) AND INTERNET PROTOCOL (IP) NODES USING SIGNAL TRANSFER POINTS (STPs)
US6611533B1 (en) * 1999-01-13 2003-08-26 Nortel Networks Limited Public telephone network, intelligent network, and internet protocol network services interworking
US8145788B1 (en) * 2002-05-31 2012-03-27 Emc Corporation Distributed ISP load balancer
US20050018651A1 (en) * 2003-07-22 2005-01-27 Innomedia Pte Ltd. Stand alone multi-media terminal adapter with network address translation and port partitioning
US20050117605A1 (en) * 2003-07-22 2005-06-02 Innomedia Pte Ltd. Network address and port translation gateway with real-time media channel management
US20050254482A1 (en) * 2004-05-14 2005-11-17 Eung-Moon Yeom Apparatus and method for voice processing of voice over internet protocol (VoIP)
JP2005073302A (ja) 2004-11-29 2005-03-17 Hitachi Ltd アドレス変換方法
JP2009015392A (ja) 2007-06-29 2009-01-22 Mitsubishi Electric Corp 通信装置および通信方法
US20110026537A1 (en) * 2008-03-20 2011-02-03 Telefonaktiebolaget Lm Ericsson (Publ) Method and Apparatus for Communication of Data Packets between Local Networks

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
Srisuresh, P., et al.; IP Network Address Translator (NAT) Terminology and Considerations; Aug. 1999, 26 pages; http://www.ietf.org/rfc/rfc2663.txt.
Tsirtsis, G., et al.; IP Network Address Translation-Protocol Translation (NAT-PT); Feb. 2000, 19 pages; http://www.ietf.org/rfc/rfc2766.txt.
Tsirtsis, G., et al.; IP Network Address Translation—Protocol Translation (NAT-PT); Feb. 2000, 19 pages; http://www.ietf.org/rfc/rfc2766.txt.

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130301650A1 (en) * 2012-05-14 2013-11-14 Futurewei Technologies, Inc. Stateless NAT44
US9185072B2 (en) * 2012-05-14 2015-11-10 Futurewei Technologies, Inc. Stateless NAT44
US20190191014A1 (en) * 2017-12-19 2019-06-20 Beijing Baidu Netcom Science And Technology Co., Ltd. Data transmission method and gateway as well as server and computer-readable storage medium
US10848599B2 (en) * 2017-12-19 2020-11-24 Beijing Baidu Netcom Science And Technology Co., Ltd. Data transmission method and gateway as well as server and computer-readable storage medium

Also Published As

Publication number Publication date
US20110122880A1 (en) 2011-05-26
JP2011103566A (ja) 2011-05-26
JP5357707B2 (ja) 2013-12-04

Similar Documents

Publication Publication Date Title
US8462800B2 (en) Gateway device and port number assignment method
JP3972733B2 (ja) アドレス変換装置、アドレス変換システム、及びｓｉｐサーバ
EP1892927B1 (en) Address translator, message processing method and equipment
US6993595B1 (en) Address translation change identification
US20040246991A1 (en) IP address translator and packet transfer apparatus
EP2449749B1 (en) Method and apparatus for relaying packets
CA2884683C (en) Split network address translation
US20070198735A1 (en) Method and system for supporting RSVP in IPv4/IPv6 hybrid network
CN101107833A (zh) 通信系统、数据处理装置、服务器、数据处理方法、执行数据处理方法的程序和记录程序的记录媒体
CN1384644B (zh) 用于连接网络的方法和装置
US7356031B1 (en) Inter-v4 realm routing
US8223762B2 (en) Method and device for translating internet protocol addresses inside a communications network
US20080198851A1 (en) Information processing system including information processing apparatus and terminals, and information processing method for the same
CN100505754C (zh) 一种实现动态4-in-6隧道建立的方法
JP3928664B2 (ja) アドレス変換装置、メッセージ処理方法および装置
JP2004165823A (ja) Ｉｐアドレス変換装置
JP3928663B2 (ja) アドレス変換装置、メッセージ処理方法および装置
JP3928662B2 (ja) アドレス変換装置、メッセージ処理方法および装置
JP4311471B2 (ja) アドレス変換装置、アドレス変換システム、及びｓｉｐサーバ
JP5023672B2 (ja) パケット中継装置
JP6807962B2 (ja) 中継装置、通信システム、及び通信方法
CN100574254C (zh) 穿越网络地址转换装置的处理方法及通话启始协议服务器
FR2953355A1 (fr) Technique d'etablissement d'un tunnel entre une passerelle et un equipement de translation

Legal Events

Date Code Title Description
AS Assignment

Owner name: HITACHI, LTD., JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SAITO, SHINICHIRO;ONIZAWA, SHIGEHIRO;REEL/FRAME:025755/0178

Effective date: 20101115

REMI Maintenance fee reminder mailed
LAPS Lapse for failure to pay maintenance fees
STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20170611